Utilize device tree partition with MCU boot

RE: Utilize device tree partition with MCU boot

Ankit_chauhan — Tue, 24 Dec 2024 07:03:22 GMT

Hi Hung,

Sorry for my late reply and thank you for the clarification.

So, I decided to go with the pm_static.yml file to manage my storage where I removed the scratch partition. So now I can manage my partition using the .yml file and it is working now.

Thanks for the support.

RE: Utilize device tree partition with MCU boot

Hung Bui — Thu, 19 Dec 2024 11:50:07 GMT

Hi Ankit,
I don't think the Partition manager will look into the device tree partition location to inherit from there.
What you should do is to define your pm_static.yml based on build\partitions.yml file and modify to what you need.

For SDK v2.6.2 you can't do pm_static_<boardname>.yml but need to define the PM_STATIC_YML_FILE when you build.
You cant take a look at CMakeLists.txt file in \nrf\samples\matter\lock to see how it work.

Regarding your question about scratch area, as far as I know, we switch to swap move algorithm and don't use scratch move algorithm.

Do you have any reason that you prefer scratch move ? It make flash wear fast ter.

RE: Utilize device tree partition with MCU boot

Ankit_chauhan — Thu, 19 Dec 2024 11:11:08 GMT

Also, your suggestion to use the board-specific pm_static.yml did not work for me. The generated partition.yml does not have my updated partition. It has the default partitions.

I am using the custom board so I append my board name after pm_static_<board_name>.yml. But that did not work.

Instead of using a custom board, I have used the defined board like pm_static_nrf5284dk_nrf52840.yml which did not work as well.

Is this feature supported by a specific nRF SDK version? Currently, I am running on 2.6.2.

RE: Utilize device tree partition with MCU boot

Ankit_chauhan — Thu, 19 Dec 2024 10:44:08 GMT

Hi Hung,

I see. That should resolve my concern.

So what I understood is that the pm_statuc.yml file is the only way to define a custom flash partition when the MCUBoot is enabled.

I am running another project where I found the partition.yml file in the build/ directory which has the generated partition. Here is the partition.yml

app:
  address: 0xc200
  end_address: 0x83000
  region: flash_primary
  size: 0x76e00
mcuboot:
  address: 0x0
  end_address: 0xc000
  placement:
    before:
    - mcuboot_primary
  region: flash_primary
  size: 0xc000
mcuboot_pad:
  address: 0xc000
  end_address: 0xc200
  placement:
    align:
      start: 0x1000
    before:
    - mcuboot_primary_app
  region: flash_primary
  size: 0x200
mcuboot_primary:
  address: 0xc000
  end_address: 0x83000
  orig_span: &id001
  - app
  - mcuboot_pad
  region: flash_primary
  sharers: 0x1
  size: 0x77000
  span: *id001
mcuboot_primary_app:
  address: 0xc200
  end_address: 0x83000
  orig_span: &id002
  - app
  region: flash_primary
  size: 0x76e00
  span: *id002
mcuboot_secondary:
  address: 0x83000
  end_address: 0xfa000
  placement:
    after:
    - mcuboot_primary
    align:
      start: 0x1000
  region: flash_primary
  share_size:
  - mcuboot_primary
  size: 0x77000
nvs_storage:
  address: 0xfa000
  end_address: 0x100000
  placement:
    align:
      start: 0x1000
    before:
    - end
  region: flash_primary
  size: 0x6000
sram_primary:
  address: 0x20000000
  end_address: 0x20040000
  region: sram_primary
  size: 0x40000

When I saw the file and compared the partition with the device tree partition, I did not find any scratch partition in the partition.yml file. Below are my device tree partition details.

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

		boot_partition: partition@0 {
			label = "mcuboot";
			reg = <0x0 0xc000>;
		};
		slot0_partition: partition@c000 {
			label = "image-0";
			reg = <0xc000 0x72000>;
		};
		slot1_partition: partition@7e000 {
			label = "image-1";
			reg = <0x7e000 0x72000>;
		};
		scratch_partition: partition@f0000 {
			label = "image-scratch";
			reg = <0xf0000 0xa000>;
		};
		storage_partition: partition@f8000 {
			label = "storage";
			reg = <0xf8000 0x6000>;
		};
	};
};

However, my MCUboot is configured to handle the dual image partition with the Swap With the Scratch option enabled. I am curious to know how the OTA is performing without scratch partition.

Can you please help me to understand this concept?

RE: Utilize device tree partition with MCU boot

Hung Bui — Thu, 19 Dec 2024 10:21:49 GMT

Hi Ankit,
It's actually possible to make pm_static file for each board. Just name it pm_static_*boardname*.yml
You can take a look at our sample for reference:

RE: Utilize device tree partition with MCU boot

Ankit_chauhan — Thu, 19 Dec 2024 05:46:03 GMT

Hi Hung,

Thanks for your reply.

Your suggestion to enable PM will allow me to configure the partition using the pm.yml file. And as I mentioned my application code is distinct amongst the different boards (like nrf52 and nrf53). I have different sensors one is using nRF52 and the other is using nRF53.

The partitions for nRF52 and nRF53 will differ, so using pm.yml is not an option for me as it will freeze the partition for all boards.

Please current my understanding if I am wrong with this terminology.

RE: Utilize device tree partition with MCU boot

Hung Bui — Mon, 16 Dec 2024 15:30:00 GMT

Hi Ankit,
I will look deeper at the ticket tomorrow. But I just want to point to where the partition manager "overwrite" the configuration of the partition in device tree: \nrf\include\flash_map_pm.h

/* Aliases for zephyr - mcuboot/ncs style naming */
#define image_0 mcuboot_primary
#define slot0_partition mcuboot_primary
#define image_1 mcuboot_secondary
#define slot1_partition mcuboot_secondary
#define image_0_nonsecure mcuboot_primary
#define slot0_ns_partition mcuboot_primary
#define image_1_nonsecure mcuboot_secondary
#define slot1_ns_partition mcuboot_secondary
#define image_2 mcuboot_primary_1
#define image_3 mcuboot_secondary_1
#define slot2_partition mcuboot_primary_1
#define slot3_partition mcuboot_secondary_1
#define slot4_partition mcuboot_primary_2
#define slot5_partition mcuboot_secondary_2
#define image_scratch mcuboot_scratch
#define image_scratch mcuboot_scratch

When multiple image is compiled, partition manager will be used. You can see in the doc here: https://docs.nordicsemi.com/bundle/ncs-2.2.0/page/nrf/scripts/partition_manager/partition_manager.html

I'm not sure if you can remove partition manager in a multi images build, but have you looked at the option to use pm ? You just need to configure the partitions correctly.

RE: Utilize device tree partition with MCU boot

Ankit_chauhan — Fri, 13 Dec 2024 11:52:02 GMT

devzone.nordicsemi.com/.../5280.partitions.txt