"region RAM overflowed with stack" error while using TLS

RE: "region RAM overflowed with stack" error while using TLS

Jawad — Mon, 02 Jan 2017 08:18:24 GMT

Hi Petter, I have posted the issue as a new question here. Could you please comment there about what should I do?

RE: "region RAM overflowed with stack" error while using TLS

Petter Myhre — Mon, 02 Jan 2017 07:55:12 GMT

Great! I converted my comment to an answer, please consider accepting it by clicking the grey circle next to it. If you have unrelated questions please add them separately, so you should add a new question.

RE: "region RAM overflowed with stack" error while using TLS

Jawad — Fri, 30 Dec 2016 10:53:32 GMT

Thanks Petter, I changed the heap to zero and I dont get the region RAM overflowed with stack anymore but now I am facing another issue. While running mqtt I can only do a fixed number (15) of mqtt publish or subscribe requests and then mqtt stops responding to received messages. I am suspecting this as a memory issue where stack pointer reaches an undefined location. Do you have any suggestion to debug such an issue while the project is running? Thanks a lot

RE: "region RAM overflowed with stack" error while using TLS

Petter Myhre — Fri, 30 Dec 2016 10:09:45 GMT

I'm testing with \examples\iot\mqtt\subscriber\boards\pca10040\armgcc

RE: "region RAM overflowed with stack" error while using TLS

Petter Myhre — Fri, 30 Dec 2016 10:08:56 GMT

If I set ASMFLAGS += -D__HEAP_SIZE=0 I get:

.heap           0x2000e1e8        0x0
                0x2000e1e8                __end__ = .
                0x2000e1e8                end = __end__
 *(.heap*)
 .heap          0x2000e1e8        0x0 _build/gcc_startup_nrf52.o
                0x2000e1e8                __HeapLimit = .

.stack_dummy    0x2000e1e8     0x1200
 *(.stack*)
 .stack         0x2000e1e8     0x1200 _build/gcc_startup_nrf52.o
                0x20010000                __StackTop = (ORIGIN (RAM) + 0xd800)
                0x2000ee00                __StackLimit = (__StackTop - SIZEOF (.stack_dummy))
                0x20010000                PROVIDE (__stack, __StackTop)
                0x00000001                ASSERT ((__StackLimit >= __HeapLimit), region RAM overflowed with stack)

RE: "region RAM overflowed with stack" error while using TLS

Petter Myhre — Fri, 30 Dec 2016 10:05:31 GMT

I don't have too much experience with gcc, but you can find it here:

.heap           0x2000fd40      0x200
                0x2000fd40                __end__ = .
                0x2000fd40                PROVIDE (end, .)
 *(.heap*)
 .heap          0x2000fd40      0x200 _build/gcc_startup_nrf52.o
                0x2000fd40                __HeapBase
                0x2000ff40                __HeapLimit = .

.stack_dummy    0x2000fd40     0x3c00
 *(.stack*)
 .stack         0x2000fd40     0x3c00 _build/gcc_startup_nrf52.o
                0x20010000                __StackTop = (ORIGIN (RAM) + LENGTH (RAM))
                0x2000c400                __StackLimit = (__StackTop - SIZEOF (.stack_dummy))
                0x20010000                PROVIDE (__stack, __StackTop)
                0x00000000                ASSERT ((__StackLimit >= __HeapLimit), region RAM overflowed with stack)

RE: "region RAM overflowed with stack" error while using TLS

Jawad — Fri, 30 Dec 2016 08:18:23 GMT

Hi Petter, Thanks a lot for the helpful feedback. Could you please elaborate where I can see the heap size in .map file and how can I modify heap size to 0? I am doing it this way in Makefile ASMFLAGS += -D__STACK_SIZE=8192 ASMFLAGS += -D__HEAP_SIZE=0 is it correct? Thanks

RE: "region RAM overflowed with stack" error while using TLS

Petter Myhre — Thu, 29 Dec 2016 13:28:13 GMT

From your .map file it seems that heap is 0x200 not 0, and because (__StackLimit >= __HeapLimit) evaluates to 0 you get an assert.

RE: "region RAM overflowed with stack" error while using TLS

Jawad — Tue, 27 Dec 2016 09:54:49 GMT

Thanks Petter, I checked the link and it doesn't seem very relevant.

RE: "region RAM overflowed with stack" error while using TLS

Petter Myhre — Fri, 23 Dec 2016 11:36:40 GMT

I'm not sure why you are getting this assert. Have you seen this?