Skip to content

Commit 9d27a75

Browse files
committed
sysbuild: bootloader: fix 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 <git@jarmouni.me>
1 parent 322da1d commit 9d27a75

File tree

1 file changed

+3
-2
lines changed
  • share/sysbuild/images/bootloader

1 file changed

+3
-2
lines changed

share/sysbuild/images/bootloader/Kconfig

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -126,8 +126,11 @@ config MCUBOOT_MODE_FIRMWARE_UPDATER
126126
mechanism defined for entering the slot1_partition which is a dedicated firmware updater
127127
application used to update the slot0_partition application.
128128

129+
endchoice
130+
129131
config MCUBOOT_MODE_SINGLE_APP_RAM_LOAD
130132
bool "Single app RAM load mode"
133+
depends on MCUBOOT_MODE_RAM_LOAD
131134
help
132135
MCUboot can load the image to RAM from an arbitrary location. In this mode,
133136
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
139142
not possible to swap back to older version of the application. In fact, none
140143
of the swap operations are supported in this mode.
141144

142-
endchoice
143-
144145
config MCUBOOT_MODE_FIRMWARE_UPDATER_BOOT_MODE_ENTRANCE
145146
bool "Firmware updater retention boot mode entrance"
146147
depends on MCUBOOT_MODE_FIRMWARE_UPDATER

0 commit comments

Comments
 (0)