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.

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) || (TFM_BL2 && BUILD_WITH_TFM && 0)

(Includes any dependencies from ifs and menus.)

Defaults

Choice options

Kconfig definitions

At <Zephyr>/modules/trusted-firmware-m/Kconfig.tfm:191

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:33 → <Zephyr>/modules/Kconfig:6 → <nRF>/doc/_build/kconfig/Kconfig.modules:20 → <nRF>/modules/trusted-firmware-m/Kconfig:44

Menu path: (Top) → Modules → trusted-firmware-m (/home/runner/work/sdk-nrf/sdk-nrf/ncs/modules/tee/tf-m/trusted-firmware-m) → 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
    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.

At <Zephyr>/modules/trusted-firmware-m/Kconfig.tfm:191

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:33 → <Zephyr>/modules/Kconfig:80 → <Zephyr>/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.)