Stefano - You should be able to run with quite a bit less stack than 65k, although I seem to remember some routines that may have auto-stack allocations that are large. You will have to set the ALLOCA define in include/device.h in order to have the system allocate large values from the heap.
With regards to building, I don't know which order is required. I suggest starting with building the win32 api stuff first, as it doesn't have the complexity of the LINK_APP_INTO_SERVER that will be required for nano-X apps, since all eCos apps run fully linked instead of separate processes. Regards, Greg On Jun 6, 2012, at 10:41 AM, Stefano Cordibella wrote: > Hi Greg, > today I have work on compilation inside the eCos tree. I was able to build > the nanoX part for my eCos target. > Now I have some link issue, but I think that I will resolve quickly. > > Working on the predefined ecos_app.c I see that the value for each eCos > thread stack size is defined at 65536, for my target board this is a very > high value because it has 56kB of SRAM... And there are many thread that run > together. > > Do you think that this value can be reduced or it is mandatory? > > Thank in advance. > Best regards, > Stefano. > > -- > Dott. Stefano Cordibella > --------------------------------------------- > EDALab - Networked Embedded Systems > C.S. Dept - University of Verona - IT > --------------------------------------------- > email : stefano.cordibe...@edalab.it > skype : stefano.cordibella > tel. : +39 045 802 70 85 > web : www.edalab.it > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: nanogui-unsubscr...@linuxhacker.org > For additional commands, e-mail: nanogui-h...@linuxhacker.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: nanogui-unsubscr...@linuxhacker.org For additional commands, e-mail: nanogui-h...@linuxhacker.org
