2020-02-25 05:55 PM
I started a new project, and my security requirement states that user authentication is required when updating firmware.
I wonder if there's a feature for this, and if not, can the bootload side be modified to meet this requirement?
I searched and found a concept like SFU. The chip used is stm32l0x2.
Solved! Go to Solution.
2020-02-25 09:04 PM
Perhaps there is a requirement to only apply newer firmware, preventing the refreshing of the current firmware, or older versions, or firmware for a different variant of the same product.
Usually one would use a product unique key or identifier, and then a date or sequence number for each firmware release.
2020-02-25 06:36 PM
That the user has a password, or a signed key?
Perhaps discuss with the individuals who created the requirements?
2020-02-25 06:37 PM
It's an requirement of certification, and maybe both methods don't matter, and just need to prevent the firmware from being updated unintentionally.
Thanks for ur apply!
2020-02-25 09:04 PM
Perhaps there is a requirement to only apply newer firmware, preventing the refreshing of the current firmware, or older versions, or firmware for a different variant of the same product.
Usually one would use a product unique key or identifier, and then a date or sequence number for each firmware release.
2020-02-25 09:34 PM
This certificate is a security certificate.
It seems to be a specification that requires a specific product to not be able to update the firmware except the manufacturer.