From: Mandeep Sandhu <mandeepsandhu.chd@gmail.com>
To: Simon Kallweit <simon.kallweit@intefo.ch>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] ecos memory footprint
Date: Tue, 14 Jul 2009 10:28:00 -0000 [thread overview]
Message-ID: <b18c5f790907140327h65cda8d6q1df5fa7937f3be2b@mail.gmail.com> (raw)
In-Reply-To: <4A5C453C.4090907@intefo.ch>
On Tue, Jul 14, 2009 at 2:13 PM, Simon Kallweit<simon.kallweit@intefo.ch> wrote:
> Mandeep Sandhu schrieb:
>>
>> Hi All,
>>
>> 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.
Ok. Any idea how to resolve this dependency? W/o this feature the USB device
is useless:
* CYGFUN_DEVS_USB_AT91_EP0 requires CYGPKG_IO_USB and
CYGPKG_IO_USB_SLAVE.
Another simple question:
How do I figure out the runtime size of my ecos installation?
Is it the size of libtarget.a ? Is this compressed?
W/o the USB feature and rest of the basic stuff including lwIP stack
enabl3d, I'm getting
around 1.2MB in size!
Thanks,
-mandeep
>
> Simon
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-07-14 10:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 13:14 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 [this message]
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
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=b18c5f790907140327h65cda8d6q1df5fa7937f3be2b@mail.gmail.com \
--to=mandeepsandhu.chd@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=simon.kallweit@intefo.ch \
/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).