Kms Specificities; Figure 24. Key Provisioning - ST X-CUBE-SBSFU STM32Cube Integration Manual
Expansion package
Hide thumbs
Also See for X-CUBE-SBSFU STM32Cube:
- Quick start manual (66 pages) ,
- User manual (42 pages) ,
- Quick start manual (50 pages)
Table of Contents
Advertisement
AN5056
5.4
KMS specificities
With KMS middleware integration, SBSFU keys are no longer stored in a section under
PCROP protection. They are stored inside the KMS code as static embedded keys.
Figure 25
The same applied for active slot #2 or #3:
1.
Change the key value in file OEM_KEY_COMPANY1_keys_AES_xxx.bin
2.
Compile SECoreBin: prebuild.bat is executed and kms_platf_objects_config.h is
generated
3.
Compile UserApp: postbuild.bat is executed and UserApp is encrypted
The same process is applied for firmware ECDSA verification key, BLOB AES encryption
key, and BLOB ECDSA verification key.
Figure 24. Key provisioning
shows an example of the firmware encryption key modification of active slot #1.
AN5056 Rev 8
Generating a cryptographic key
29/49
48
Advertisement
Table of Contents
Need help?
Do you have a question about the X-CUBE-SBSFU STM32Cube and is the answer not in the manual?