> > There is no expansion of the linker-defined sections. Thread-local > variables are stored on the thread stacks. These stacks are typically > allocated as static arrays. Some packages use their own > statically-allocated memory pools. You must decide how large these > stacks and memory pools need to be where necessary. > > If you must use malloc() and related functions, the eCos dynamic memory > allocation package will allocate memory from the heap. The heap > typically occupies all remaining RAM above the application code and > data. Clearly, allocations from the heap are additional to anything > known to the linker and reported by the "size" tool. > >> Say my bss+data+rwdata comes to around 55KB...is it safe to go with a >> system with 64KB on-chip RAM? Is 9KB margin safe enough? > > You need no margin at all if you avoid dynamic memory allocation. > > I hope this helps...
Thanks for clearing this. This does help a lot! Regards, -mandeep > > John Dallaway > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
