CONFIG_MCUBOOT_GENERATE_CONFIRMED_IMAGE

Also generate a padded, confirmed image

Type: bool

Help

The signed, padded, and confirmed binaries are placed in the build
directory at zephyr/zephyr.signed.confirmed.bin and
zephyr/zephyr.signed.confirmed.hex.

The file names can be customized with CONFIG_KERNEL_BIN_NAME.
The existence of bin and hex files depends on CONFIG_BUILD_OUTPUT_BIN
and CONFIG_BUILD_OUTPUT_HEX.

Direct dependencies

(BOOTLOADER_MCUBOOT && SOC_ESP32C3) || (BOOTLOADER_MCUBOOT && SOC_ESP32) || BOOTLOADER_MCUBOOT

(Includes any dependencies from ifs and menus.)

Defaults

y
y

Kconfig definitions

At <SoC>/riscv/esp32c3/Kconfig.defconfig:19

Included via Kconfig:8 → Kconfig.zephyr:27

Menu path: (Top)

config MCUBOOT_GENERATE_CONFIRMED_IMAGE
    bool
    default y
    depends on BOOTLOADER_MCUBOOT && SOC_ESP32C3

At <SoC>/xtensa/esp32/Kconfig.defconfig:18

Included via Kconfig:8 → Kconfig.zephyr:27

Menu path: (Top)

config MCUBOOT_GENERATE_CONFIRMED_IMAGE
    bool
    default y
    depends on BOOTLOADER_MCUBOOT && SOC_ESP32

At Kconfig.zephyr:727

Included via Kconfig:8

Menu path: (Top) → Boot Options → MCUboot bootloader support

config MCUBOOT_GENERATE_CONFIRMED_IMAGE
    bool "Also generate a padded, confirmed image"
    depends on BOOTLOADER_MCUBOOT
    help
      The signed, padded, and confirmed binaries are placed in the build
      directory at zephyr/zephyr.signed.confirmed.bin and
      zephyr/zephyr.signed.confirmed.hex.

      The file names can be customized with CONFIG_KERNEL_BIN_NAME.
      The existence of bin and hex files depends on CONFIG_BUILD_OUTPUT_BIN
      and CONFIG_BUILD_OUTPUT_HEX.

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