RE: Migrating partition configuration from Partition Manager to devicetree

ael-mess — Tue, 11 Aug 2026 23:44:48 GMT

Thank you Vidar, it was the `zephyr,code-partition = &boot_partition;`

RE: Migrating partition configuration from Partition Manager to devicetree

Vidar Berg — Tue, 11 Aug 2026 07:31:29 GMT

Hello,

This looks like it may be a bug in the script. Perhaps the "firmware_loader" was supposed to be a sub partition of "slot1_partition". However, based on the DT overlay for the Single slot sample which uses the FW loader mode, you should not need to define the firmware_loader partition, not in SDK v3.4.0, at least.

[quote user=""]When removing the firmware loader partition, the application does not boot, and from comparing .elf files, DTS is starting the application at 0x6000 instead of 0x6800.[/quote]

The *.elf file will only include padding between 0x6000 and 0x6800 to leave room for the mcuboot pad included in the signed FW image.

Another important thing to remember when using DT partitions is to configure the bootloader to start from the boot_partition and not from the default slot0 partition by setting the chosen property like here: https://github.com/nrfconnect/sdk-nrf/blob/afd3c3ea56431659dc4513428b6bb9edd59bb225/samples/dfu/single_slot/sysbuild/mcuboot/boards/nrf54l15dk_nrf54l15_cpuapp.overlay#L11.

Best regards,

Vidar