MCUBOOT + Multi NVS partition

RE: MCUBOOT + Multi NVS partition

Amanda Hsieh — Tue, 23 Jan 2024 14:31:11 GMT

That looks fine. Let me know if you have any issues regarding the modification.

RE: MCUBOOT + Multi NVS partition

kyozc — Tue, 23 Jan 2024 00:44:19 GMT

Hi Amanda,

We are using a custom board with no external flash. and we just modify the partition size with pm_static.yml like that

EMPTY_0:
  address: 0xfe000
  end_address: 0x100000
  placement:
    after:
    - settings_storage
  region: flash_primary
  size: 0x2000
app:
  address: 0xc200
  end_address: 0x80000
  region: flash_primary
  size: 0x73e00
mcuboot:
  address: 0x0
  end_address: 0xc000
  placement:
    before:
    - mcuboot_primary
  region: flash_primary
  size: 0xc000
mcuboot_pad:
  address: 0xc000
  end_address: 0xc200
  placement:
    before:
    - mcuboot_primary_app
  region: flash_primary
  size: 0x200
mcuboot_primary:
  address: 0xc000
  end_address: 0x80000
  orig_span: &id001
  - mcuboot_pad
  - app
  region: flash_primary
  sharers: 0x1
  size: 0x74000
  span: *id001
mcuboot_primary_app:
  address: 0xc200
  end_address: 0x80000
  orig_span: &id002
  - app
  region: flash_primary
  size: 0x73e00
  span: *id002
mcuboot_secondary:
  address: 0x80000
  end_address: 0xfc000
  placement:
    after:
    - mcuboot_primary
    align:
      start: 0x4000
  region: flash_primary
  share_size:
  - mcuboot_primary
  size: 0x74000
otp:
  address: 0xff8100
  end_address: 0xff83fc
  region: otp
  size: 0x2fc
pcd_sram:
  address: 0x20000000
  end_address: 0x20002000
  placement:
    after:
    - start
  region: sram_primary
  size: 0x2000
rpmsg_nrf53_sram:
  address: 0x20070000
  end_address: 0x20080000
  placement:
    before:
    - end
  region: sram_primary
  size: 0x10000
settings_storage:
  address: 0xfc000
  end_address: 0xfe000
  placement:
    align:
      start: 0x4000
    before:
    - end
  region: flash_primary
  size: 0x2000
config2_storage:
  address: 0xf8000
  end_address: 0xfc000
  placement:
    before:
    - settings_storage
  region: flash_primary
  size: 0x4000
config1_storage:
  address: 0xf4000
  end_address: 0xf8000
  placement:
    before:
    - config2_storage
  region: flash_primary
  size: 0x4000
sram_primary:
  address: 0x20002000
  end_address: 0x20070000
  region: sram_primary
  size: 0x6e000

for now it just works (but not suitable for simultaneous DFU ) And Is there any other problem with that modity?

Thanks

Chen

RE: MCUBOOT + Multi NVS partition

Amanda Hsieh — Mon, 22 Jan 2024 14:30:48 GMT

Hi,

[quote user="kyozc"]

if i want to place the config partion at config1_partition at 0xe0000 and config2_partition at 0xe8000

what should i do to moditify the dts file?

[/quote]

Those addressed are overlapped with mcuboot_secondary, so they cannot use that address. The size of mcuboot_secondary must be the same as mcuboot_primary. You could move the mcuboot_secondary to external flash. Are you using nRF53DK or a custom board? If a custom board, is there an external flash on it? Connected via SPI or QSPI? What is the external flash name?

[quote user="kyozc"]And Why we have modify the dts file to make the app slot size 0x40000 but have no sense.[/quote]

Try to modify the app size with pm_static.yml.

-Amanda H.

RE: MCUBOOT + Multi NVS partition

kyozc — Mon, 22 Jan 2024 01:03:17 GMT

Hi Amanda,

The EMPTY_0 is too small for two config partition(eath config need 2 sector at least)

if i want to place the config partion at config1_partition at 0xe0000 and config2_partition at 0xe8000

what should i do to moditify the dts file?

&flash0 {

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

        boot_partition: partition@0 {
            label = "mcuboot";
            reg = <0x00000000 0x00010000>;
        };
        slot0_partition: partition@10000 {
            label = "image-0";
        };
        slot1_partition: partition@50000 {
            label = "image-1";
        };
        slot2_partition: partition@90000 {
            label = "image-2";
        };
        config1_partition: partition@e0000 {
            label = "config1";
            reg = <0x000e0000 0x00008000>;
        };
        config2_partition: partition@e8000 {
            label = "config2";
            reg = <0x000e8000 0x00008000>;
        };
        /* 0xf0000 to 0xf7fff reserved for TF-M partitions */
        storage_partition: partition@f8000 {
            label = "storage";
            reg = <0x000f8000 0x00008000>;
        };
    };
};

&slot0_partition {
	reg = <0x00010000 0x40000>;
};

&slot1_partition {
	reg = <0x00050000 0x40000>;
};

&slot2_partition {
	reg = <0x00090000 0x40000>;
};

And Why we have modify the dts file to make the app slot size 0x40000 but have no sense.

Thanks

Chen

RE: MCUBOOT + Multi NVS partition

Amanda Hsieh — Fri, 19 Jan 2024 22:57:38 GMT

Hi,

[quote user="kyozc"]config1_partition at 0xe0000 and config2_partition at 0xe8000 [/quote]

They are overlapped with the mcuboot_secondary. You could put them at 0xfe000 to replace the EMPTY_0.

-Amanda H.

RE: MCUBOOT + Multi NVS partition

kyozc — Fri, 19 Jan 2024 01:28:44 GMT

Hi Amanda,

Thanks for the guide, but i got the build error with custom pm_static.yml

EMPTY_0:
  address: 0xfe000
  end_address: 0x100000
  placement:
    after:
    - settings_storage
  region: flash_primary
  size: 0x2000
app:
  address: 0xc200
  end_address: 0x84000
  region: flash_primary
  size: 0x77e00
mcuboot:
  address: 0x0
  end_address: 0xc000
  placement:
    before:
    - mcuboot_primary
  region: flash_primary
  size: 0xc000
mcuboot_pad:
  address: 0xc000
  end_address: 0xc200
  placement:
    before:
    - mcuboot_primary_app
  region: flash_primary
  size: 0x200
mcuboot_primary:
  address: 0xc000
  end_address: 0x84000
  orig_span: &id001
  - app
  - mcuboot_pad
  region: flash_primary
  sharers: 0x1
  size: 0x78000
  span: *id001
mcuboot_primary_app:
  address: 0xc200
  end_address: 0x84000
  orig_span: &id002
  - app
  region: flash_primary
  size: 0x77e00
  span: *id002
mcuboot_secondary:
  address: 0x84000
  end_address: 0xfc000
  placement:
    after:
    - mcuboot_primary
    align:
      start: 0x4000
  region: flash_primary
  share_size:
  - mcuboot_primary
  size: 0x78000
otp:
  address: 0xff8100
  end_address: 0xff83fc
  region: otp
  size: 0x2fc
rpmsg_nrf53_sram:
  address: 0x20070000
  end_address: 0x20080000
  placement:
    before:
    - end
  region: sram_primary
  size: 0x10000
settings_storage:
  address: 0xfc000
  end_address: 0xfe000
  placement:
    align:
      start: 0x4000
    before:
    - end
  region: flash_primary
  size: 0x2000
config1_partition:
  address: 0xe0000
  end_address: 0xe8000
  placement:
    align:
      start: 0x20000
    before:
    - end
  region: flash_primary
  size: 0x8000
config2_partition:
  address: 0xe8000
  end_address: 0xf0000
  placement:
    align:
      start: 0x18000
    before:
    - end
  region: flash_primary
  size: 0x8000
sram_primary:
  address: 0x20000000
  end_address: 0x20070000
  region: sram_primary
  size: 0x70000

How could i modify the pm_static.yml if we want to add

config1_partition at 0xe0000 and config2_partition at 0xe8000

Thanks

Chen

RE: MCUBOOT + Multi NVS partition

Amanda Hsieh — Thu, 18 Jan 2024 15:24:07 GMT

Hi,

You can use the partitions.yml under the build folder to modify and rename it as pm_static.yml, then place it under the application folder.

Regards,
Amanda H.