mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-27 03:16:30 +00:00
When we build Zephyr for a Non-Secure image, using TFM as the Secure counterpart, we may or may not use BL2 (e.g. MCUboot in TFM). If we build with BL2 we need to account for a ROM offset before the start of the non-secure image where TFM BL2 expects the BL2 header. This offset is not needed when TFM is built without BL2. We use the existing Kconfig options to determine whether we need a ROM offset or not. We use the value of 0x400 for the BL2 header, which is the default value used in TFM, but the option is non-hidden, allowing the user to overwrite the default value if needed. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no> |
||
---|---|---|
.. | ||
Kconfig | ||
Kconfig.altera | ||
Kconfig.atmel | ||
Kconfig.canopennode | ||
Kconfig.civetweb | ||
Kconfig.cmsis | ||
Kconfig.cmsis_dsp | ||
Kconfig.cypress | ||
Kconfig.eos_s3 | ||
Kconfig.imx | ||
Kconfig.infineon | ||
Kconfig.libmetal | ||
Kconfig.loramac-node | ||
Kconfig.mbedtls | ||
Kconfig.mcux | ||
Kconfig.microchip | ||
Kconfig.nordic | ||
Kconfig.nuvoton | ||
Kconfig.open-amp | ||
Kconfig.silabs | ||
Kconfig.simplelink | ||
Kconfig.st | ||
Kconfig.stm32 | ||
Kconfig.syst | ||
Kconfig.tfm | ||
Kconfig.tinycbor | ||
Kconfig.tinycrypt | ||
Kconfig.tls-generic | ||
Kconfig.vega | ||
Kconfig.xtensa |