Maximum limit of stack size using flag -D__STACK_SIZE NRF52382

RE: Maximum limit of stack size using flag -D__STACK_SIZE NRF52382

Prashant Singh — Wed, 05 Apr 2017 07:29:42 GMT

Thanks Bjorn no further question on this topic.

RE: Maximum limit of stack size using flag -D__STACK_SIZE NRF52382

bjorn-spockeli — Wed, 05 Apr 2017 06:09:46 GMT

Happy to help. :) Let me know if you have any further questions.

RE: Maximum limit of stack size using flag -D__STACK_SIZE NRF52382

Prashant Singh — Tue, 04 Apr 2017 14:06:00 GMT

Thanks Bjorn In your answer, you mentioned taking a look at the .map file to find out how much RAM the application uses if I am getting it correct you are referring to .bss section and .data section

RE: Maximum limit of stack size using flag -D__STACK_SIZE NRF52382

bjorn-spockeli — Tue, 04 Apr 2017 12:01:38 GMT

Hi Prashant,

I am assuming that you referring to the portioning of the RAM shown below, when you say that RAM is divided in to four blocks.

The maximum limit that __STACK_SIZE can be set to will depend on how much RAM the application needs, but the absolute limit, i.e. if the application does not use RAM will be 0x20000000 + - APP_RAM_BASE. Usually, that is not the case, so you'll have to take a look in the .map file to find out how much RAM the application uses and then adjust the stack size accordingly. If you get linker error when compiling then you know that the stack is to large and you will have to reduce the size until it successfully compiles and then use the .map file as mentioned above.

If you do not define__STACK_SIZE, then it is usually set to 8192 bytes, see the gcc_startup_nrf52.S file in components\toolchain\gcc\

Bjørn