arm-none-eabi/bin/ld: region RAM overflowed with stack

RE: arm-none-eabi/bin/ld: region RAM overflowed with stack

Jim — Wed, 22 Jan 2014 02:24:18 GMT

OK, I've resolve the mystery of the out-of-order linking. It's actually an Eclipse issue. The Eclipse console cannot properly interleave stdout and stderr from the build. I guess that's hard to do. I am resisting challenging that notion with all my might.

So, if you get confused by Eclipse build output, try breaking the build up with some intermediate targets.

Silly silly silly.

RE: arm-none-eabi/bin/ld: region RAM overflowed with stack

Jim — Wed, 22 Jan 2014 01:46:17 GMT

I'm definitely picking up libraries I shouldn't. A lot of libc.a in the map file. Any way to control what gcc decides to include on it's own?

RE: arm-none-eabi/bin/ld: region RAM overflowed with stack

Jim — Wed, 22 Jan 2014 01:10:56 GMT

OK, I'm looking at the .map file and it looks like I've somehow inherited a whole load of libraries, courtesy of gcc. My suspicion is that they are related to the existence of "printf" statements in my code which are intended to send messages out through the UART, so I'm trying to figure out how to re-implement the functionality of retarget.c that I had been using. I'll post another question on this topic to avoid confusion...