Secure Boot Guide¶
Secure Boot ensures that a module only executes authorized, signed firmware and software — establishing an unbroken chain of trust from the hardware up to the operating system. See the CRA Guide’s Secure Boot chapter for the regulatory background (Cyber Resilience Act).
Note
Enabling Secure Boot on a module is irreversible in practice — once closed, only signed images boot. Test thoroughly on development units before rolling it out.
Currently, our BSPs only provide the tooling to set up Secure Boot on STM32MP1 modules (Mainline BSP, karo-bsp): key generation, image signing and fusing the public key hash are described step by step in Secure Boot on QSMP-15* modules.
For all other modules, Secure Boot is not yet supported by our BSPs — please refer to the vendor documentation of the respective processor:
SoC family |
Module series |
Mechanism |
Status |
Documentation |
|---|---|---|---|---|
STM32MP1 |
QSMP-1xxx, TXMP-1xxx |
TF-A trusted boot |
supported |
|
STM32MP2 |
QSMP-2xxx, TXMP-2xxx |
TF-A trusted boot |
not yet supported |
|
i.MX9 |
TX91, QS91, TX93, QS93 |
AHAB |
not yet supported |
|
NXP i.MX8 |
TX8M, TX8P, QS8M, QSXM, QSXP |
HAB |
not yet supported |
|
NXP i.MX6 |
TX6, TXUL |
HAB |
not planned |
|
Renesas RZ/G2L |
QSRZ-G2Lx, TXRZ-G2Lx |
— |
not planned |
— |