public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Moussa A. Ba" <mba@embedded-zone.com>
To: "Moussa A. Ba" <mba@embedded-zone.com>, ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] ECOS Memory Requirements
Date: Thu, 01 Jun 2006 18:39:00 -0000	[thread overview]
Message-ID: <447F2C35.9070402@embedded-zone.com> (raw)
In-Reply-To: <20060601180003.GL2478@lunn.ch>

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).

Moussa

Andrew Lunn wrote:
> On Thu, Jun 01, 2006 at 12:39:34PM -0400, Moussa A. Ba wrote:
>   
>> I am porting ecos to an OKI 4061 with 128K Flash and 16K RAM.  Can this 
>> handle ecos? If so how much of that space will still remain for 
>> application code?
>>     
>
> 128K flash is O.K.
>
> 16K RAM is probably too small. I would say that 64K RAM is a
> reasonable minimum. Some things will be possible with 32K RAM. I think
> with 16K RAM you are going to have problems.
>
> Maybe take a look at the ATMEL AT91SAM7 family. There are devices with
> 256K Flash and 64K RAM with eCos support already in anoncvs. There are
> also similar devices from Philips in there LPC family.
>
>      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

  reply	other threads:[~2006-06-01 18:39 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 [this message]
2006-06-01 19:28     ` Andrew Lunn
2006-06-02  7:15       ` Ilija Koco
2006-06-01 18:39   ` Moussa A. Ba

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=447F2C35.9070402@embedded-zone.com \
    --to=mba@embedded-zone.com \
    --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).