Migrating partition configuration from Partition Manager to devicetree

Question

I am using ncs v3.3.0, and since Partition Manager will be deprecated, I followed the migration guide to use DTS board configuration. I am using mcuboot in firmware loader mode, so the overlay generation script produced overlapping partitions:

	slot1_partition: partition@133000 {
		label = "image-1";
		reg = <0x133000 0x40000>;
	};

	firmware_loader: partition@133800 {
		label = "firmware-loader";
		reg = <0x133800 0x3f800>;
	};

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.

I am not sure how to move partition maanager to DTS configuraation, here is the full DTS node:

&cpuapp_rram {
    reg = <0x0 DT_SIZE_K(1524)>;

    /delete-node/ partitions;

    partitions {
        compatible = "fixed-partitions";
        #address-cells = <1>;
        #size-cells = <1>;

        boot_partition: partition@0 {
            label = "mcuboot";
            reg = <0x0 DT_SIZE_K(24)>;
        };

        slot0_partition: partition@6000 {
            label = "image-0";
            reg = <0x6000 DT_SIZE_K(1204)>;
        };

        slot1_partition: partition@133000 {
            label = "image-1";
            reg = <0x133000 DT_SIZE_K(256)>;
        };

        coredump_partition: partition@173000 {
            label = "coredump_partition";
            reg = <0x173000 DT_SIZE_K(4)>;
        };

        storage_partition: partition@174000 {
            label = "storage";
            reg = <0x174000 DT_SIZE_K(36)>;
        };
    };
};

Vidar Berg · Accepted Answer

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. 
 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 . 
 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

Migrating partition configuration from Partition Manager to devicetree

Top Replies