- choice TFM_MCUBOOT_PATH: Path to MCUboot or DOWNLOAD to fetch automatically
Path to MCUboot or DOWNLOAD to fetch automatically
Type: bool
Help¶
Path to MCUboot for TF-M builds. The default option
is to use Zephyr's MCUboot module. As an alternative,
users may switch to the 'download' version; in that
case MCUboot will be fetched by the TF-M build during
build time. The default option ensures that Zephyr builds
with TF-M do not fetch external trees.
Direct dependencies¶
TFM_BL2 && BUILD_WITH_TFM && 0
(Includes any dependencies from ifs and menus.)
Default¶
Choice options¶
Kconfig definition¶
At modules/trusted-firmware-m/Kconfig.tfm:161
Included via Kconfig:8 → Kconfig.zephyr:33 → modules/Kconfig:74 → modules/trusted-firmware-m/Kconfig:7
Menu path: (Top) → Modules → Build with TF-M as the Secure Execution Environment → Add MCUboot to TFM
choice TFM_MCUBOOT_PATH
bool "Path to MCUboot or DOWNLOAD to fetch automatically"
default TFM_MCUBOOT_PATH_LOCAL
depends on TFM_BL2 && BUILD_WITH_TFM && 0
help
Path to MCUboot for TF-M builds. The default option
is to use Zephyr's MCUboot module. As an alternative,
users may switch to the 'download' version; in that
case MCUboot will be fetched by the TF-M build during
build time. The default option ensures that Zephyr builds
with TF-M do not fetch external trees.
(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)