public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mandeep Sandhu <mandeepsandhu.chd@gmail.com>
To: Grant Edwards <grant.b.edwards@gmail.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: ecos memory footprint
Date: Wed, 15 Jul 2009 04:34:00 -0000	[thread overview]
Message-ID: <b18c5f790907142134s5a8f7873j168c7110b138453e@mail.gmail.com> (raw)
In-Reply-To: <h3i49j$fm5$1@ger.gmane.org>

On Tue, Jul 14, 2009 at 7:51 PM, Grant Edwards<grant.b.edwards@gmail.com> wrote:
> On 2009-07-14, Simon Kallweit <simon.kallweit@intefo.ch> wrote:
>> Mandeep Sandhu schrieb:
>>
>>> Anybody knows if ECOS can run in 64KB mem (or lesser) with the
>>> following features:
>>>
>>> * USB Device/slave support
>>> * SPI Driver support
>>> * Networking support (for running a small webserver)
>>>
>>> I've not yet narrowed down on my h/w yet...but Microchips
>>> PIC32MX460F128H seems promising? But the sad part is that ecos
>>> doesn't show this in their list of supported h/w.
>>>
>>> Have ppl run ecos on microcontrollers w/o external SDRAM (I'm
>>> trying to conserve power by not having ext RAM)?
>>
>> This will be rather tough, but probably possible. You should use the
>> lwIP networking stack to keep memory usage low. Also, try to use as few
>> threads as possible, as this saves you valuable stack memory.
>
> I agree that it's probably possible, but IMO you're going to
> spend a lot of time trying to make everything fit -- effort
> that could be better spent on developing and testing your
> application.  I'd recommend a serious look at using something
> intended for a smaller footprint (XMK, FreeRTOS, uC/OS-II, etc.).

Yes, I'm evaluating FreeRTOS as well for my requirements. I've just
compiled their
sample webserver app for the same Atmel platform. And that doesn't look too good
as well! :(

~/freeRTOS/FreeRTOS/Demo/lwIP_Demo_Rowley_ARM7$ arm-elf-size rtosdemo.elf
   text	   data	    bss	    dec	    hex	filename
 119096	   2016	  62736	 183848	  2ce28	rtosdemo.elf

~/freeRTOS/FreeRTOS/Demo/lwIP_Demo_Rowley_ARM7$ arm-elf-objdump -h rtosdemo.elf

rtosdemo.elf:     file format elf32-littlearm

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 startup       00000044  00100000  00100000  00008000  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 prog          0001d0f4  00100044  00100044  00008044  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  2 .data         000007e0  00200000  0011d138  00028000  2**2
                  CONTENTS, ALLOC, LOAD, DATA
  3 .bss          0000f510  002007e0  002007e0  000287e0  2**3
                  ALLOC
  4 .debug_abbrev 00007274  00000000  00000000  000287e0  2**0
                  CONTENTS, READONLY, DEBUGGING
  5 .debug_info   0002cb4d  00000000  00000000  0002fa54  2**0
                  CONTENTS, READONLY, DEBUGGING
  6 .debug_line   00007e5c  00000000  00000000  0005c5a1  2**0
                  CONTENTS, READONLY, DEBUGGING
  7 .debug_frame  00003400  00000000  00000000  00064400  2**2
                  CONTENTS, READONLY, DEBUGGING
  8 .debug_pubnames 0000213a  00000000  00000000  00067800  2**0
                  CONTENTS, READONLY, DEBUGGING
  9 .debug_aranges 00000ba8  00000000  00000000  00069940  2**3
                  CONTENTS, READONLY, DEBUGGING
 10 .debug_str    00002410  00000000  00000000  0006a4e8  2**0
                  CONTENTS, READONLY, DEBUGGING
 11 .comment      000005fa  00000000  00000000  0006c8f8  2**0
                  CONTENTS, READONLY
 12 .debug_ranges 000001d8  00000000  00000000  0006cef2  2**0
                  CONTENTS, READONLY, DEBUGGING

This does not give the exact figure (as I think the config here does
not have the
SPI driver built-in), but I'm using the results here to just get some
rough comparative
figure vis-a-vis ecos with roughly the same config.

I think i'll have to "up" my RAM  requirements to have at least 256KB
RAM. Though
I'm not sure if i'll be able to meet my price budget constraints.

-mandeep

>
> --
> Grant Edwards                   grante             Yow! I had pancake makeup
>                                  at               for brunch!
>                               visi.com
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
>

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2009-07-15  4:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 13:14 [ECOS] " Mandeep Sandhu
2009-07-13 22:09 ` Alexander Neundorf
2009-07-14  4:52   ` Mandeep Sandhu
2009-07-14  8:43 ` Simon Kallweit
2009-07-14 10:28   ` Mandeep Sandhu
2009-07-14 10:34     ` Sergei Gavrikov
2009-07-14 11:04       ` Mandeep Sandhu
2009-07-14 13:18         ` Mandeep Sandhu
2009-07-14 13:22           ` Mandeep Sandhu
2009-07-14 13:31             ` Sergei Gavrikov
2009-07-14 13:30           ` Andrew Lunn
2009-07-14 10:43     ` Ross Younger
2009-07-14 11:16       ` Mandeep Sandhu
2009-07-14 12:26     ` [ECOS] USB on at91sam7xek [ was Re: ecos memory footprint ] John Dallaway
2009-07-14 12:47       ` [ECOS] " Mandeep Sandhu
2009-07-14 14:22   ` [ECOS] Re: ecos memory footprint Grant Edwards
2009-07-15  4:34     ` Mandeep Sandhu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b18c5f790907142134s5a8f7873j168c7110b138453e@mail.gmail.com \
    --to=mandeepsandhu.chd@gmail.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=grant.b.edwards@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).