Optimizing MCUboot RAM Partition Size on nRF52833

[sensorbee-dev]

Hello everyone,

I'm currently working with an nRF52833 that utilizes MCUboot. I've noticed that the allocated RAM partition for MCUboot is set at 128 KB, but in practice, it only utilizes approximately 25 KB. This allocation seems excessively large and somewhat inefficient, considering the actual usage. I'm interested in optimizing this setup to allocate more memory to the main application.

From what I understand, adjusting the partition configuration might involve creating or modifying a pm_static.yml file. However, I'm uncertain about the specifics of configuring the MCUboot RAM partition size. My key questions are:

1. Is it sufficient to adjust the MCUboot RAM section alone, or is it necessary to redefine the configurations for all partitions involved?
2. Could someone provide guidance or a sample configuration on how to properly adjust the MCUboot RAM partition size within the pm_static.yml file?

The goal is to reduce the MCUboot RAM partition to a size closer to its actual usage, thereby freeing up memory for the main application. Any insights, examples, or recommendations on how to achieve this would be greatly appreciated.

Thank you for your assistance!

[Sigurd Hellesvik]

Hi,

I'm interested in optimizing this setup to allocate more memory to the main application.

MCUboot runs before the main application, and therefore these two do not compete for RAM.

There are some secure/non-secure RAM considerations for devices with TF-M, but these are not important for the nRF52 series.

Regards,
Sigurd Hellesvik

[sensorbee-dev]

Right of course, I just realized that I checked the wrong MCU when looking at the RAM size specification. Sorry about that.

Thank you for your answer.