SWCU195A December 2024 – May 2025 CC2744R7-Q1 , CC2745P10-Q1 , CC2745R10-Q1 , CC2745R7-Q1 , CC2755R10
Figure 11-1 Secure Boot Flow. In the Execution Flow depicted above, the ROM Boot Sequence will invoke Secure Boot only if enabled. In general, Secure Boot is configured in SCFG (Secure Configuration). For Secure Boot to be considered enabled, the field scfg.secBootCfg.authMethod must be set to either SCFG_POLICY_SIGNATURE or SCFG_POLICY_HASH_LOCK. If scfg.secBootCfg.authMethod is set to SCFG_POLICY_NO_AUTH, Secure Boot is considered disabled.
Secure Boot will return the target address to transfer control to the ROM Boot Sequence, unless it is determined that there is no target to boot, in which case the system will enter ROM Panic.
For Secure Boot to boot or update a given target, it is required that the verification and antirollback checks are successful. Otherwise, the target image will be rejected.