Help¶

This option signifies that the target uses MCUboot as a bootloader, or in other words that the image is to be chain-loaded by MCUboot. This sets several required build system and Device Tree options in order for the image generated to be bootable using the MCUboot open source bootloader. Currently this includes:

Setting ROM_START_OFFSET to a default value that allows space for the MCUboot image header

Activating SW_VECTOR_RELAY_CLIENT on Cortex-M0 (or Armv8-M baseline) targets with no built-in vector relocation mechanisms

By default, this option instructs Zephyr to initialize the core architecture HW registers during boot, when this is supported by the application. This removes the need by MCUboot to reset the core registers’ state itself.

Defaults¶

No defaults. Implicitly defaults to n.

Symbols selected by this symbol¶

USE_DT_CODE_PARTITION

Symbols implied by this symbol¶

INIT_ARCH_HW_AT_BOOT if ARCH_SUPPORTS_ARCH_HW_INIT

Symbols that select this symbol¶

Symbols that imply this symbol¶

ZIGBEE_FOTA

Kconfig definition¶

At <Zephyr>/Kconfig.zephyr:382

Included via <Zephyr>/Kconfig:8

Menu path: (Top) → Boot Options

config BOOTLOADER_MCUBOOT
    bool "MCUboot bootloader support"
    select USE_DT_CODE_PARTITION
    imply INIT_ARCH_HW_AT_BOOT if ARCH_SUPPORTS_ARCH_HW_INIT
    help
      This option signifies that the target uses MCUboot as a bootloader,
      or in other words that the image is to be chain-loaded by MCUboot.
      This sets several required build system and Device Tree options in
      order for the image generated to be bootable using the MCUboot open
      source bootloader. Currently this includes:

        * Setting ROM_START_OFFSET to a default value that allows space
          for the MCUboot image header
        * Activating SW_VECTOR_RELAY_CLIENT on Cortex-M0
          (or Armv8-M baseline) targets with no built-in vector relocation
          mechanisms

      By default, this option instructs Zephyr to initialize the core
      architecture HW registers during boot, when this is supported by
      the application. This removes the need by MCUboot to reset
      the core registers' state itself.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)