- CONFIG_TFM_MCUBOOT_IMAGE_NUMBER¶
Granularity of FW updates of TFM and app
Granularity of FW updates of TFM and app
Type: int
Help¶
How many images the bootloader sees when it looks at TFM and the app.
When this is 1, the S and NS are considered as 1 image and must be
updated in one atomic operation. When this is 2, they are split and
can be updated independently if dependency requirements are met.
Help¶
How many images the bootloader sees when it looks at TFM and the app.
When this is 1, the S and NS are considered as 1 image and must be
updated in one atomic operation. When this is 2, they are split and
can be updated independently if dependency requirements are met.
Direct dependencies¶
BUILD_WITH_TFM || (BUILD_WITH_TFM && 0)
(Includes any dependencies from ifs and menus.)
Defaults¶
2
2
Kconfig definitions¶
At modules/trusted-firmware-m/Kconfig:149
Included via Kconfig:8 → Kconfig.zephyr:23 → modules/Kconfig:6 → doc/_build/Kconfig/Kconfig.modules:26
Menu path: (Top) → Modules → trusted-firmware-m (/home/nashif/zephyrproject/modules/tee/tfm) → Build with TF-M as the Secure Execution Environment
config TFM_MCUBOOT_IMAGE_NUMBER
int "Granularity of FW updates of TFM and app"
range 1 2
default 2
depends on BUILD_WITH_TFM
help
How many images the bootloader sees when it looks at TFM and the app.
When this is 1, the S and NS are considered as 1 image and must be
updated in one atomic operation. When this is 2, they are split and
can be updated independently if dependency requirements are met.
At modules/trusted-firmware-m/Kconfig:149
Included via Kconfig:8 → Kconfig.zephyr:23 → modules/Kconfig:66
Menu path: (Top) → Modules → Build with TF-M as the Secure Execution Environment
config TFM_MCUBOOT_IMAGE_NUMBER
int "Granularity of FW updates of TFM and app"
range 1 2
default 2
depends on BUILD_WITH_TFM && 0
help
How many images the bootloader sees when it looks at TFM and the app.
When this is 1, the S and NS are considered as 1 image and must be
updated in one atomic operation. When this is 2, they are split and
can be updated independently if dependency requirements are met.
(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)