BOOT_SWAP_USING_MOVE set more than once.

[simonhwm]

I have just upgraded my project to NCS 3.1.0 and I'm now getting this error

BOOT_SWAP_USING_MOVE (defined at C:/ncs/v3.1.0/bootloader/mcuboot/boot/zephyr/Kconfig:575) set more than once.

If I look at that file in the build directory I do indeed see conflicting settings

# sysbuild controlled configuration settings

...

CONFIG_SINGLE_APPLICATION_SLOT=n

CONFIG_BOOT_SWAP_USING_MOVE=n

CONFIG_BOOT_SWAP_USING_SCRATCH=n

CONFIG_BOOT_UPGRADE_ONLY=n

...

CONFIG_SINGLE_APPLICATION_SLOT=n

CONFIG_BOOT_SWAP_USING_OFFSET=n

CONFIG_BOOT_SWAP_USING_SCRATCH=n

CONFIG_BOOT_UPGRADE_ONLY=n

CONFIG_BOOT_SWAP_USING_MOVE=y

...

I don't set these values in my own config file as far as I can tell, so looks like this conflict comes from NCS 3.1.0 itself

Am I doing something wrong?

Simon

[Hayden Ball]

Adding, though, that it is still defined twice.

Just that both are set to the same value now.

[Hayden Ball]

Ah. Looks like this was fixed last week:

github.com/.../4930977becfe68a5577eb4b8337b391ec0defbe8

[AHaug]

Hayden Ball said:

I suspect this is `zephyr/share/sysbuild/image_configurations/BOOTLOADER_image_default.cmake` and `nrf/sysbuild/CMakeLists.txt` fighting.

You are 100% right, this is indeed the culprit. I see that Jamie was already on top of this (which he typically tends to be)

So to confirm; with commit 4930977 added you also see that MCUboot mode is just configured once and thus the issue is resolved?

Kind regards,
Andreas

[Hayden Ball]

Yes - the issue is resolved for me having applied that commit.

[AHaug]

Great, sorry I couldn't find that issue before you did, but nonetheless I'm glad that the original issue is resolved

I'll mark your comment as the answer, and as always please feel free to open new cases for new questions

Kind regards,
Andreas