:orphan:

.. title:: BOOTLOADER_MCUBOOT

.. option:: 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 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.

Direct dependencies
===================

!\ :option:`MCUBOOT <CONFIG_MCUBOOT>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Symbols selected by this symbol
===============================

- \ :option:`USE_DT_CODE_PARTITION <CONFIG_USE_DT_CODE_PARTITION>`

Symbols implied by this symbol
==============================

- \ :option:`INIT_ARCH_HW_AT_BOOT <CONFIG_INIT_ARCH_HW_AT_BOOT>` if \ :option:`ARCH_SUPPORTS_ARCH_HW_INIT <CONFIG_ARCH_SUPPORTS_ARCH_HW_INIT>`

Symbols that select this symbol
===============================

- \ :option:`HAWKBIT <CONFIG_HAWKBIT>`
- \ :option:`UPDATEHUB <CONFIG_UPDATEHUB>`

Kconfig definition
==================

.. highlight:: kconfig

At ``Kconfig.zephyr:403``

Included via ``Kconfig:8``

Menu path: (Top) → Boot Options

.. parsed-literal::

    config BOOTLOADER_MCUBOOT
    	bool "MCUboot bootloader support"
    	select \ :option:`USE_DT_CODE_PARTITION <CONFIG_USE_DT_CODE_PARTITION>`
    	imply \ :option:`INIT_ARCH_HW_AT_BOOT <CONFIG_INIT_ARCH_HW_AT_BOOT>` if \ :option:`ARCH_SUPPORTS_ARCH_HW_INIT <CONFIG_ARCH_SUPPORTS_ARCH_HW_INIT>`
    	depends on !\ :option:`MCUBOOT <CONFIG_MCUBOOT>`
    	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.)*