Using NCS 1.2 SMP_SVR example compiled with custom board DT

RE: Using NCS 1.2 SMP_SVR example compiled with custom board DT

eshaul — Thu, 19 Mar 2020 18:01:12 GMT

The below pm_static.yml is compiling ok (I have removed the scratch partition and added that space to the storage), but I have a few follow-up questions

mcuboot:
  address: 0x0
  size: 0xc000

mcuboot_primary:
  address: 0xc000
  orig_span: &id001
  - mcuboot_pad
  - app
  sharers: 0x1
  size: 0x36000
  span: *id001

mcuboot_secondary:
  address: 0x42000
  size: 0x36000

littlefs_storage:
  address: 0x78000
  size: 0x88000

In the mcuboot_primary section, I must add the "orig_span", "sharers" & "span" sections (or else I get the same error as above), I got them from the partition.yml on my build folder but I don't know their meaning & why are they needed, can you share your thoughts?

The storage partition seems ok to me as it is exactly filling up space till 0x100000. Anyway, it is not preventing the compilation (i will check the storage partition later on)

During the build both memory maps are confirming that the partitions for mcuboot and the application are on the right size:

For MCUBOOT, 48K = 0xC000

Memory region         Used Size  Region Size  %age Used
           FLASH:       35680 B        48 KB     72.59%
            SRAM:       23764 B       256 KB      9.07%
        IDT_LIST:          56 B         2 KB      2.73%
        
For APP, 220672B = 0x35E00

Memory region         Used Size  Region Size  %age Used
           FLASH:      121848 B     220672 B     55.22%
            SRAM:       26124 B       256 KB      9.97%
        IDT_LIST:         120 B         2 KB      5.86%

I managed to get a cycle of mcumgr commands and DFU the board using the 2nd partition

RE: Using NCS 1.2 SMP_SVR example compiled with custom board DT

sigvartmh — Thu, 19 Mar 2020 11:26:51 GMT

mcuboot:
  address: 0x0
  size: 0xc000
mcuboot_primary:
  address: 0xc000
  size: 0x36000
mcuboot_secondary:
  address: 0x42000
  size: 0x36000
mcuboot_scratch:
  address: 0x78000
  size: 0x8000
littlefs_storage:
  address: 0x80000
  size: 0x7f000

I guess that would be the simplest way of representing what you are trying to write. I don't think you can have 0x80000 in your storage partition it seems as you hit 0x100000. Maybe there is a bug in the partition manager that doesn't do a proper check.

So I guess that's what is failing for you since partition manager is thinking you are going out of bounds of the flash. I would agree that the error message is not telling you what's failing.

Just an FYI you don't need a scratch partition anymore: https://github.com/JuulLabs-OSS/mcuboot/pull/645

Edit: Tested it and it seems that it doesn't work as expected :/ Seems truncates the space of MCUBoot

RE: Using NCS 1.2 SMP_SVR example compiled with custom board DT

eshaul — Thu, 19 Mar 2020 11:22:32 GMT

According to my understanding, they are perfectly aligned, which means there are no gaps that I know of, I am not sure if the syntax of the pm_static.yml is correct

It was copied from the partitions.yml and changed addresses and sizes only.

I am not aware of this keywoards:

orig_span:

sharers:

RE: Using NCS 1.2 SMP_SVR example compiled with custom board DT

sigvartmh — Thu, 19 Mar 2020 11:06:40 GMT

[quote userid="83877" url="~/f/nordic-q-a/58972/using-ncs-1-2-smp_svr-example-compiled-with-custom-board-dt/239847"]File "/home/eshaul/workspace/ncs/nrf/scripts/partition_manager.py", line 490, in get_dynamic_area_start_and_size
assert len(gaps) == 1, "Incorrect amount of gaps found"[/quote]

So this error comes if your partitions are not address aligned directly after each other. Try to create an empty partition between the sections which are not aligned. So that you fill the gaps which are between your partitions.

RE: Using NCS 1.2 SMP_SVR example compiled with custom board DT

eshaul — Sun, 15 Mar 2020 18:21:24 GMT

dear sigvartmh

Thanks for your reply it's very helpful,

I generated this pm_ststic.yml, it supposes (according to my understanding) to correspond with the DTS partitions configuration

but unfortunately, I am getting error in compilation:

File "/home/eshaul/workspace/ncs/nrf/scripts/partition_manager.py", line 490, in get_dynamic_area_start_and_size
assert len(gaps) == 1, "Incorrect amount of gaps found"

Can you help my understanding if indeed the pm_static.yml is corresponding with DTS partition configuration?

For example, I don't have the scratch partition there...

Is there any documentation specific to how pm_static.yml structure should be?

Thanks

Erez.

app:
  address: 0xc200
  size: 0x35e00
littlefs_storage:
  address: 0x80000
  placement:
    after:
    - app
  size: 0x80000
mcuboot:
  address: 0x0
  placement:
    before:
    - mcuboot_primary
  size: 0xc000
mcuboot_pad:
  address: 0xc000
  placement:
    align:
      start: 0x1000
    before:
    - mcuboot_primary_app
  size: 0x200
mcuboot_primary:
  address: 0xc000
  orig_span: &id001
  - mcuboot_pad
  - app
  sharers: 0x1
  size: 0x36000
  span: *id001
mcuboot_primary_app:
  address: 0xc200
  orig_span: &id002
  - app
  size: 0x35e00
  span: *id002
mcuboot_secondary:
  address: 0x42000
  placement:
    after:
    - mcuboot_primary
    align:
      start: 0x1000
  share_size:
  - mcuboot_primary
  size: 0x36000

boot_partition: partition@0 {
label = "mcuboot";
reg = <0x00000000 0x0000C000>;
};
slot0_partition: partition@c000 {
label = "image-0";
reg = <0x0000C000 0x000036000>;
};
slot1_partition: partition@42000 {
label = "image-1";
reg = <0x00042000 0x000036000>;
};
scratch_partition: partition@78000 {
label = "image-scratch";
reg = <0x00078000 0x00008000>;
};
storage_partition: partition@80000 {
label = "storage";
reg = <0x00080000 0x00080000>;
};

RE: Using NCS 1.2 SMP_SVR example compiled with custom board DT

sigvartmh — Thu, 12 Mar 2020 20:34:56 GMT

eshaul If you want to enter the configuration of mcuboot to configure the partition configurations

ninja/make mcuboot_menuconfig

To change the configuration, you could either specify a specific config file for MCUBoot

Through

CmakeFile:

set(mcuboot_CONF_FILE mcuboot.conf)

or
cmake -Dmcuboot_CONF_FILE=mcuboot.conf

or change

<NCS root dir>/bootloader/mcuboot/boot/zephyr/pm.yml

If you want a specific configuration, I would recommend trying to define a pm_static.yml file in your project folder.

If you want to look at what is generated, look in your <build_root>/partitions.yml or pm.config depending on what you prefer to read.

The generated correlated

<build root>mcuboot/zephyr/include/generated/pm_config.h
<build root>zephyr/include/generated/pm_config.h

header files are found at:

To better answer, your question is that you would have to set:

PM_PARTITION_SIZE_MCUBOOT=0xc000
PM_PARTITION_SIZE_MCUBOOT_STORAGE=0x80000
PM_PARTITION_SIZE_MCUBOOT_SCRATCH=8000

Unfortunately, you won't be able to set the partition size as that's what partition manager will calculate for you so the rest of the space will be split in to and be slot_0 and slot_1 and both storage and scratch is placed accordingly. So if you want a 1:1 match you'll have to use pm_static.yml. Look at the generated partitions.yml after setting the configuration you want and tune the placement afterward would be my suggestion.

RE: Using NCS 1.2 SMP_SVR example compiled with custom board DT

eshaul — Thu, 12 Mar 2020 06:33:03 GMT

Dear Øyvind,

Partition manager is NCS related module, I am asking what is the designed way to configure partitions, SMP_SVR is a Zephyr example included in the NCS package and uses Partition Manager

RE: Using NCS 1.2 SMP_SVR example compiled with custom board DT

Øyvind — Wed, 11 Mar 2020 15:57:42 GMT

Hello,

The Zephyr SMP Server Sample (SMP_SVR) is a sample made by the Zephyr community for nRF52x, and not by the NCS team in Nordic. At the moment NCS is lacking full support for nRF52 devices. Therefore I would recommend asking the Zephyr community for help.

Kind regards,
Øyvind