SRAM image allocation

RE: SRAM image allocation

Didrik Rokhaug — Mon, 20 Jul 2020 13:33:50 GMT

Hi.

First, are you absolutely 100% sure you need a buffer that large?

As the bsdlib partition cannot be moved, the non-secure SRAM partition can not be expanded to 160kB while you also use the bsdlib, which is necessary to use the modem.

You might be able to free up the necessary RAM by reducing the number of Zephyr's features you use, and by reducing the stack used by all the threads in the system.

You might also be able to split up the buffer into smaller pieces and allocate those separately.

Best regards,

Didrik

RE: SRAM image allocation

meqyj. — Sat, 18 Jul 2020 10:01:16 GMT

sir,I'm afraid that now don't partition the system's ram,based on the original:

&sram0 {
reg = <0x20000000 DT_SIZE_K(64)>;
};

&sram0_bsd {
reg = <0x20010000 DT_SIZE_K(64)>;
};

&sram0_ns {
reg = <0x20020000 DT_SIZE_K(128)>;
};

here,'sram0_ns' what way rise to 160KB???

RE: SRAM image allocation

Simon — Wed, 15 Jul 2020 20:44:56 GMT

Is your problem solved? Should I close the ticket?

Best regards,

Simon

RE: SRAM image allocation

meqyj. — Tue, 14 Jul 2020 08:59:27 GMT

Or, using another function, you might want to augment it: CONFIG_HEAP_MEM_POOL_SIZE=122880,this will also fulfill my needs