From: Alexander Neundorf <neundorf@kde.org>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] ecos memory footprint
Date: Mon, 13 Jul 2009 22:09:00 -0000 [thread overview]
Message-ID: <200907140008.02330.neundorf@kde.org> (raw)
In-Reply-To: <b18c5f790907130614p4be978b4he0447d03c0197794@mail.gmail.com>
On Monday 13 July 2009, Mandeep Sandhu wrote:
> 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)
This looks like a bit much for 64KB RAM. Maybe you can get it to work.
> 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.
Some ARM7 devices like the AT91SAM7 are well supported.
Alex
--
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-13 22:09 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 [this message]
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
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=200907140008.02330.neundorf@kde.org \
--to=neundorf@kde.org \
--cc=ecos-discuss@ecos.sourceware.org \
/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).