On Wed, Jul 15, 2009 at 7:27 PM, Sergei Gavrikov<[email protected]> wrote: > Mandeep Sandhu wrote: >> >> seems like a std error? now back to reading your reply :) ..... > > That error is not surprise for small memory footprint targets. I hope > you get it. That trick did not fit an external RAM on your board, It did > deceive linker and then you can use `size' utility.
Yes, I suspected that much. But tell me, where does the linker get the RAM size constraint for the atmel board...i.e the sam7ex256? It must be configured somewhere...as part of a template...no? Couldn't we have "added" RAM there? BTW, your trick worked...I pretty much get the same numbers as you had shown... Before reducing PBUF pool size: arm-eabi-size test_install/tests/net/lwip_tcpip/v3_0/tests/httpd text data bss dec hex filename 71512 5440 102796 179748 2be24 test_install/tests/net/lwip_tcpip/v3_0/tests/httpd After reducing it to 6: arm-eabi-size test_install/tests/net/lwip_tcpip/v3_0/tests/httpd text data bss dec hex filename 71512 5440 46636 123588 1e2c4 test_install/tests/net/lwip_tcpip/v3_0/tests/http So this figure is not too different from the FreeRTOS numbers for similar app :)... ~/freeRTOS/FreeRTOS/Demo/lwIP_Demo_Rowley_ARM7$ ~/gnuarm/gnuarm-3.4.3/bin/arm-elf-size rtosdemo.elf text data bss dec hex filename 119096 2016 62736 183848 2ce28 rtosdemo.elf Do you think 256K RAM will be enough to run a similarly configured system (with additional USB device and SPI driver support) on ARM7 based embedded SoC? -mandeep > > > Sergei > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
