The latest development version of this page may be more current than this released 2.1.0 version.
CONFIG_BOOTLOADER_MCUBOOT

MCUboot bootloader support

Type: bool

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

Symbols selected by this symbol

Symbols that select this symbol

Kconfig definition

At Kconfig.zephyr:352

Included via Kconfig:8

Menu path: (Top) → Boot Options

config BOOTLOADER_MCUBOOT
    bool "MCUboot bootloader support"
    select USE_CODE_PARTITION
    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_SECTION_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

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