RE: Current best dynamic memory allocation method

Hakon — Mon, 06 Dec 2021 12:51:58 GMT

Hello,

[quote user=""]I've found numerous references to modifying sdk_config.h, which is not a file I have in my project.[/quote]

This is for when you are building with the nRF5 SDK, not with Zephyr/NCS.

[quote user="BDA"]Without that stack definition the code seems to just endlessly get stuck in the startup code before it ever branches to main.[/quote]

Can you set CONFIG_RESET_ON_FATAL_ERROR=n and post the serial output log here so I can see what is going wrong? It would be nice if you could share the code as well, or the part of the code that fails.

RE: Current best dynamic memory allocation method

BDA — Thu, 02 Dec 2021 19:23:41 GMT

After a lot of trial and error I've made some progress. I needed to define the stack space as well as the heap in order for it to work with k_malloc. Here is the relevant portion of my current prj.conf:

CONFIG_HEAP_MEM_POOL_SIZE=2048

CONFIG_MAIN_STACK_SIZE=16384

Without that stack definition the code seems to just endlessly get stuck in the startup code before it ever branches to main.

But, I can't increase my heap size beyond 2048 or it goes back to failing in the same way as before. This seems similar to this issue. This is certainly not right: I'm compiling a test application, and even with that 16k stack and 2k heap I'm only using a tiny portion of the available ram:

Memory region Used Size Region Size %age Used

FLASH: 24460 B 1 MB 2.33%

SRAM: 20896 B 256 KB 7.97%

Can someone help me increase that heap size to more than 2k...? And confirm for me if k_malloc is the recommended way of doing dynamic allocation with a zephyr based project built with 1.7.1?