-
Notifications
You must be signed in to change notification settings - Fork 7.6k
sysbuild: bootloader: fix MCUboot Kconfig symbol placement #93076
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
sysbuild: bootloader: fix MCUboot Kconfig symbol placement #93076
Conversation
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>
9d27a75
to
53b4f3b
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Incorrect, it is a mode and remains part of the choice. If you get an error about modes then the image configuration script is wrong and that should be fixed
It is enabling |
If you don't mind, which part of it? |
MCUBOOT_MODE_SINGLE_APP_RAM_LOAD
shoud not be aMCUBOOT_MODE
choice because it is not a separate load mode but rather a specific case ofMCUBOOT_MODE_RAM_LOAD
Without this change, building with
SB_CONFIG_MCUBOOT_MODE_SINGLE_APP_RAM_LOAD=y
leads to multiple modes being selected if a default mode is set on MCUboot side (for ex. https://github.com/mcu-tools/mcuboot/blob/5eaf190a8a9d8fc032b989bf96fc56b3b756dd55/boot/zephyr/boards/stm32h7s78_dk.conf#L1) and MCUboot build failing with the errorTested with