Static partition manager with Mcuboot and Sysbuild

RE: Static partition manager with Mcuboot and Sysbuild

DmytroSes — Fri, 07 Feb 2025 13:52:50 GMT

I have checked the files you had provided and was able to successfully compile and run my code. I have adjusted the pm_static.yml and added the following to my overlay file:

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

&cpuapp_sram { //! Without this the only 188Kb of RAM is available
	reg = <0x20000000 DT_SIZE_K(256)>;
	ranges = <0x0 0x20000000 DT_SIZE_K(256)>;
};

There is also some amount of RAM reserved for the cpuflpr by default (in the nrf54l15.dtsi). So that should be modified to, if you don't use the co-processor.

RE: Static partition manager with Mcuboot and Sysbuild

Hieu — Thu, 06 Feb 2025 20:06:49 GMT

Hi DmytroSes,

You are right. If I have to guess, the reason is that the Partition Manager was made a while ago, before the need to share RRAM between two cores. This need only arose recently with the release of the nRF54L series.

I will leave a word with our R&D and documentation team to resolve this conflicting information in the next SDK release.

RE: Static partition manager with Mcuboot and Sysbuild

DmytroSes — Wed, 05 Feb 2025 11:26:54 GMT

Hi!
Thanks for the reply. I will try it later and will tell the result.

It is a bit confusing, that you need to adjust the DeviceTree as well. In the documentation it is said:

When you build a multi-image application using the Partition Manager, the devicetree source flash partitions are ignored.

So I thought, you do nothing in DeviceTree, when you use the Partition Manager.

RE: Static partition manager with Mcuboot and Sysbuild

Hieu — Wed, 05 Feb 2025 11:02:46 GMT

Hi DmytroSes,

Thank you for the patience. Sorry I am a little late. I ended up being unexpectedly out of office.

The problem with the nRF Desktop pm_static.yml turns out to be that it uses the entire RRAM of the nRF54L15. Meanwhile, by default, a portion of the RRAM is reserved for the FLPR core.

You need to overlay the DeviceTree to give the entire RRAM to cpuapp like done in nRF Desktop: https://github.com/nrfconnect/sdk-nrf/blob/v2.9.0/applications/nrf_desktop/configuration/nrf54l15dk_nrf54l15_cpuapp/app_common.dtsi#L7-L10.

However, that alone will eventually lead to another build failure. The nRF Desktop application optimizes MCUboot memory footprint and allocates a smaller region for it. You will have to either make the same optimization or adjust the partitioning to give MCUboot more space.

Hieu

RE: Static partition manager with Mcuboot and Sysbuild

Hieu — Thu, 30 Jan 2025 21:17:30 GMT

Hi DmytroSes,

I can reproduce your issue. The same pm_static.yml seems to work for the nRF Desktop app, but not the setup I created from the Hello World sample.

I will look into it and follow-up with you early next week.

Hieu