SWCU195A December 2024 – May 2025 CC2744R7-Q1 , CC2745P10-Q1 , CC2745R10-Q1 , CC2745R7-Q1 , CC2755R10
Secure Boot is a verification mechanism that ensures that the firmware to be booted is trusted, in that the code to be executed originates from a known source. Therefore, it prevents unauthorized firmware from booting.
The System ROM is the root of trust. The ROM Secure Boot verifies that the next boot stage, either an Application (App 0 or App 1) or a Secondary Secure Bootloader (SSB), is trusted. In this context, the next boot stage is trusted if it complies with the properties of integrity (hash) and authenticity (signature).
In general, the following are the steps required to enable Secure Boot in the system and generate compatible images.
Generate private keys of the same type as configured in the Authentication Algorithm for:
Key updates
App updates (only necessary if Secure Boot will boot Application images)
SSB updates (only required if Secure Boot will boot a Secondary Secure Bootloader)
Configure SCFG fields as desired:
Application and/or secondary secure bootloader slots
Authentication method, algorithm, and update mode
Key Update Key Hash
Initial key ring entries for application and/or secondary secure bootloader
Boot Seed
Note that SCFG needs to be programmed only once. After that, additional images can be programmed separately without the need to program SCFG again. SCFG only needs to be reprogrammed if a change in the security configuration needs to be made.
Refer to the Secure Boot example project in the SDK to learn how to perform the steps described above using the tools provided in the Code Composer IDE.