From: Andrew Lunn <andrew@lunn.ch>
To: "Moussa A. Ba" <mba@embedded-zone.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] ECOS Memory Requirements
Date: Thu, 01 Jun 2006 19:28:00 -0000 [thread overview]
Message-ID: <20060601192809.GB15114@lunn.ch> (raw)
In-Reply-To: <447F2C35.9070402@embedded-zone.com>
On Thu, Jun 01, 2006 at 02:04:37PM -0400, Moussa A. Ba wrote:
> Are these high memory requirement because the code is loaded from flash
> to RAM and then executed or is it just that ECOS data structures need so
> much RAM (not that much compared to bigger processors).
eCos can run from ROM. That is the normal setup for AT91SAM7 devices.
To get an idea of code size i suggest you download anoncvs and play
with the build for the AT91SAM7S. Look at the binaries for the
tests.
Andrew
--
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:[~2006-06-01 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 17:39 Moussa A. Ba
2006-06-01 18:23 ` Andrew Lunn
2006-06-01 18:39 ` Moussa A. Ba
2006-06-01 18:39 ` Moussa A. Ba
2006-06-01 19:28 ` Andrew Lunn [this message]
2006-06-02 7:15 ` Ilija Koco
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=20060601192809.GB15114@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=mba@embedded-zone.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).