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 TEXT_LOAD_OFFSET to a default value that allows space for the MCUboot image header

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

Including dts/common/mcuboot.overlay when building the Device Tree in order to place and link the image at the slot0 offset

Defaults¶

No defaults. Implicitly defaults to n.

Kconfig definition¶

At misc/Kconfig:323

Included via Kconfig:10 → Kconfig.zephyr:31

Menu path: (top menu) → Boot Options

config BOOTLOADER_MCUBOOT
    bool
    prompt "MCUboot bootloader support"
    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 TEXT_LOAD_OFFSET to a default value that allows space for
          the MCUboot image header
        * Activating SW_VECTOR_RELAY on Cortex-M0 (or Armv8-M baseline)
          targets with no built-in vector relocation mechanisms
        * Including dts/common/mcuboot.overlay when building the Device
          Tree in order to place and link the image at the slot0 offset

(Definitions include propagated dependencies, including from if’s and menus.)