CONFIG_TFM_MCUBOOT_IMAGE_NUMBER

Granularity of FW updates of TFM and app

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.

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

(Includes any dependencies from ifs and menus.)

Defaults

  • 2

  • 1

  • 2

  • 2

Kconfig definitions

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

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:31<Zephyr>/modules/Kconfig:6<nRF>/doc/_build/kconfig/Kconfig.modules:14<nRF>/modules/trusted-firmware-m/Kconfig:34<Zephyr>/modules/trusted-firmware-m/Kconfig:7

Menu path: (Top) → Modules → trusted-firmware-m (/home/runner/work/sdk-nrf/sdk-nrf/ncs/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 && !TFM_MINIMAL
    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 <nRF>/modules/trusted-firmware-m/Kconfig.tfm_minimal.defconfig:1

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:31<Zephyr>/modules/Kconfig:6<nRF>/doc/_build/kconfig/Kconfig.modules:14<nRF>/modules/trusted-firmware-m/Kconfig:41

Menu path: (Top) → Modules → trusted-firmware-m (/home/runner/work/sdk-nrf/sdk-nrf/ncs/modules/tee/tfm)

config TFM_MCUBOOT_IMAGE_NUMBER
    int
    default 1
    depends on TFM_MINIMAL

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

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:31<Zephyr>/modules/Kconfig:6<nRF>/doc/_build/kconfig/Kconfig.modules:14<nRF>/modules/trusted-firmware-m/Kconfig:43

Menu path: (Top) → Modules → trusted-firmware-m (/home/runner/work/sdk-nrf/sdk-nrf/ncs/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 && TFM_MINIMAL
    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 <Zephyr>/modules/trusted-firmware-m/Kconfig.tfm:151

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:31<Zephyr>/modules/Kconfig:74<Zephyr>/modules/trusted-firmware-m/Kconfig:7

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.)