From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4291 invoked by alias); 15 Jul 2009 14:05:11 -0000 Received: (qmail 4275 invoked by uid 22791); 15 Jul 2009 14:05:10 -0000 X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_83,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from wf-out-1314.google.com (HELO wf-out-1314.google.com) (209.85.200.170) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 15 Jul 2009 14:05:03 +0000 Received: by wf-out-1314.google.com with SMTP id 23so1293507wfg.24 for ; Wed, 15 Jul 2009 07:05:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.143.18.16 with SMTP id v16mr1827874wfi.26.1247666701682; Wed, 15 Jul 2009 07:05:01 -0700 (PDT) In-Reply-To: <20090715135722.GA8730@sg-ubuntu.local> References: <4A5DB80E.7090604@dallaway.org.uk> <20090715131830.GA7572@sg-ubuntu.local> <20090715135722.GA8730@sg-ubuntu.local> Date: Wed, 15 Jul 2009 14:05:00 -0000 Message-ID: From: Mandeep Sandhu To: Sergei Gavrikov Cc: John Dallaway , ecos-discuss@ecos.sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] Re: ecos mem footprint with HTTPD support X-SW-Source: 2009-07/txt/msg00138.txt.bz2 On Wed, Jul 15, 2009 at 7:27 PM, Sergei Gavrikov 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