.. |br| raw:: html
.. _secureboot-guide-index:
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 :doc:`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 :doc:`stm32mp1`.
For all other modules, Secure Boot is **not yet supported by our BSPs** — please refer to the
vendor documentation of the respective processor:
.. list-table::
:header-rows: 1
:widths: 20 30 20 20 30
* - SoC family
- Module series
- Mechanism
- Status
- Documentation
* - STM32MP1
- QSMP-1xxx, TXMP-1xxx
- TF-A trusted boot
- supported
- :doc:`step-by-step with our BSP ` + `ST Wiki - Secure Boot `_
* - STM32MP2
- QSMP-2xxx, TXMP-2xxx
- TF-A trusted boot
- not yet supported
- `ST Wiki - Secure Boot `__
* - i.MX9
- TX91, QS91, TX93, QS93
- AHAB
- not yet supported
- `i.MX Security User's Guide `_
* - NXP i.MX8
- TX8M, TX8P, QS8M, QSXM, QSXP
- HAB
- not yet supported
- `i.MX Security User's Guide `__
* - NXP i.MX6
- TX6, TXUL
- HAB
- not planned
- `i.MX Security User's Guide `__
* - Renesas RZ/G2L
- QSRZ-G2Lx, TXRZ-G2Lx
- —
- not planned
- —
.. toctree::
:maxdepth: 1
:hidden:
stm32mp1