RAM allocation

RE: RAM allocation

Simonr — Mon, 18 Jul 2022 13:07:32 GMT

So everything works as expected in NCS 1.8.0 but not in 2.0.0? Is this a new project in 2.0.0 or are you trying to move your existing project to 2.0.0? If so, we have a migration guide that you should follow in order to move existing projects from NCS 1.x.x to 2.0.0 here.

Best regards,

Simon

RE: RAM allocation

Georgiy Lutsenko — Sun, 17 Jul 2022 14:21:59 GMT

What worries me is that the error is being returned from ram_report. Everything else works when using SDK version 1.8.0, but as soon as I tried to build everything on version 2.0.0 I see this error:

RE: RAM allocation

Simonr — Tue, 31 May 2022 12:40:35 GMT

Hi again

When you build an application using the partition manager, the device tree source flash partitions are ignored.

Are you worried that there will be an error or is there an error returned from the ram_report? If so, what error or error code is this specifically?

Best regards,

Simon

RE: RAM allocation

Georgiy Lutsenko — Mon, 30 May 2022 22:49:30 GMT

Hi Simonr
Thanks for the answer
I was able to increase the size of Sram non secure. To do this, I added the pm_static.yml file to the root directory, changing the sizes and addresses of existing partitions, but I'm worried that when partition_manager_report is run, there are no changes, and when ram_report is run, it gives an error. Also, there are no changes in the device tree.

Best regards,

Georgiy

RE: RAM allocation

Simonr — Mon, 30 May 2022 12:02:55 GMT

This is not the file to increase/edit the allocated memory in, as this file will be overwritten by the Partition Manager which is a Python script that sets the start address and size of Flash/RAM partitions in a multi-image build context. Please check out the documentation, as I think that should explain pretty well how to allocate RAM as you wish.

Best regards,

Simon