migrating app using mcuboot to NCS 3.2.3 - issue with MCUboot image IDs automatically assigned?

[Achim Kraus]

I migrate an app from NCS 3.1.0 to NCS 3.2.3.

Using mcuboot with a Thingy:91 or Thingy:91X fails.

flash_img_init results in a flash_img_context, which uses ID 2, the application_slot0, where the app runs from. That obviously crashes on executing an update.

This seems to be caused by 

CONFIG_FLASH_LOAD_OFFSET=0x0

instead of

CONFIG_FLASH_LOAD_OFFSET=0x50000

which, then causes to use slot0 instead of slot1

According the migration guide 3.2 , the 

"MCUboot image IDs are no longer taken from sysbuild Kconfig options and are instead automatically assigned."

but that seems to fail.

The app uses a static partition file (the same as the Thingy:91). The intention is to use only the internal flash (Thingy:91X, nRF9151-DK).

Currently resulting .configs:

thingy91x_nrf9151dk.config.zip

[Achim Kraus]

Hmmmm, adding 

DT_CHOSEN_Z_CODE_PARTITION := zephyr,code-partition

to boards/nordic/thingy91x/Kconfig.defconfig.nrf9151 , as in boards/nordic/thingy91x/Kconfig.defconfig.nrf5340 , seems to be one possibility to fix it ;-(. The zephyr board definition for the nRF9151-DK seems to use an different approach.

Not sure, which approach would be the preferred by Nordic, but it would help, if the stuff would be more aligned.