Partition map migratation from ncs 2.2 -> ncs 2.7 (sysbuild)

RE: Partition map migratation from ncs 2.2 -> ncs 2.7 (sysbuild)

Christoffer Brask — Wed, 06 Nov 2024 13:50:20 GMT

For anyone interested this was the solution

devzone.nordicsemi.com/.../4370.pm_5F00_static.txt

RE: Partition map migratation from ncs 2.2 -> ncs 2.7 (sysbuild)

Christoffer Brask — Tue, 05 Nov 2024 14:41:21 GMT

I tried to add the following code before the warning line

struct image_header *out_hdr = boot_img_hdr(state, 0);

uint32_t load_addr = out_hdr->ih_load_addr;

BOOT_LOG_INF("Image header: %d", load_addr);

And the output was

I: Image header: 165481 <-- 0x28669
W: Failed reading image headers; Image=0

Should image header be placed from the very first byte of the application?

RE: Partition map migratation from ncs 2.2 -> ncs 2.7 (sysbuild)

Christoffer Brask — Tue, 05 Nov 2024 13:08:13 GMT

Update: Setting SB_CONFIG_SECURE_BOOT_APPCORE=y in sysbuild.conf helped including the nordic secure immutable bootloader however mcuboot still seems to fail at boot

*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.
Hash: 0x77...5f
Firmware signature verified.
Firmware version 1
Setting monotonic counter (version: 1, slot: 0)
*** Booting MCUboot v2.1.0-dev-daf2946a0f07 ***
*** Using nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
W: Failed reading image headers; Image=0
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 1, Swap type: none
E: Image in the primary slot is not valid!
E: Unable to find bootable image

One thing i notice is that if I add the merged.hex to nRF Desktop Programmer it looks like the app layer is placed from 0x27e00 and I assume it would be from 0x28000