From 53b4f3b863c50c3a873dee4bf9043d845e300d02 Mon Sep 17 00:00:00 2001 From: Abderrahmane JARMOUNI Date: Mon, 14 Jul 2025 01:06:57 +0200 Subject: [PATCH] sysbuild: bootloader: fix MCUboot Kconfig symbol placement MCUBOOT_MODE_SINGLE_APP_RAM_LOAD shoud not be a MCUBOOT_MODE choice because it is not a separate load mode but rather a specific case of MCUBOOT_MODE_RAM_LOAD Signed-off-by: Abderrahmane JARMOUNI --- share/sysbuild/images/bootloader/Kconfig | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/share/sysbuild/images/bootloader/Kconfig b/share/sysbuild/images/bootloader/Kconfig index 31d866b4a55f..c8829e75b10c 100644 --- a/share/sysbuild/images/bootloader/Kconfig +++ b/share/sysbuild/images/bootloader/Kconfig @@ -126,8 +126,11 @@ config MCUBOOT_MODE_FIRMWARE_UPDATER mechanism defined for entering the slot1_partition which is a dedicated firmware updater application used to update the slot0_partition application. +endchoice + config MCUBOOT_MODE_SINGLE_APP_RAM_LOAD bool "Single app RAM load mode" + depends on MCUBOOT_MODE_RAM_LOAD help MCUboot can load the image to RAM from an arbitrary location. In this mode, MCUboot will copy the image to RAM and begin execution from there. The image @@ -139,8 +142,6 @@ config MCUBOOT_MODE_SINGLE_APP_RAM_LOAD not possible to swap back to older version of the application. In fact, none of the swap operations are supported in this mode. -endchoice - config MCUBOOT_MODE_FIRMWARE_UPDATER_BOOT_MODE_ENTRANCE bool "Firmware updater retention boot mode entrance" depends on MCUBOOT_MODE_FIRMWARE_UPDATER