pls help me to check if understand correct?
1. for hse basic secure boot, the app integrity check is by bootloader, so it need a additional software (bootloader ) to do it. bootloader maybe a normal app and not started with secure boot, so it may be modified and app cant be fully trusted.
2. in HSE demoExample-Advanced_secure_boot project, it just run once to setup the SMR data. after reset, it can be erased and hse firmware check the smr data and jump to the app if passed check.
Hi @fantong9
To better understand the Secure Boot we provide an application note including demo projects which explains all the steps in detail. It can be downloaded from:
S32K3 Microcontrollers for Automotive General Purpose
Application note can be found here:
Documentation -> Secure Files -> Secure Boot Application note v0.1.1.0 (AN744511)
Associated demo project can be downloaded here:
Design Resources -> Software -> Secure Files -> SecureBootAppNoteDemo (SW745310)
BR, VaneB