This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Does 256kByte flash and 64kByte RAM + TCP/IP make sense for eCos?
- From: Andrew Lunn <andrew at lunn dot ch>
- To: ?yvind Harboe <oyvind dot harboe at zylin dot com>
- Cc: eCos Disuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Fri, 13 Jun 2008 12:25:13 +0200
- Subject: Re: [ECOS] Does 256kByte flash and 64kByte RAM + TCP/IP make sense for eCos?
- References: <c09652430806130235l6d2c8a0fraa246fd2081a7ea3@mail.gmail.com>
> It seems like the amount of flash + ram available inside a
> microcontroller has been stuck at or below 256kBytes and 64kByte RAM
> the last 5 years.
Im guessing this has to do with the silicon processes being used, but
im no expert in this area.
> However, eCos is not in the game if flash/ram is stuck at 256kBytes/64kBytes
> respectively.
The AT91SAM7X256 has exactly this combination. There is also a
AT91SAM7X512 with double the flash.
I know of people who have used these devices with eCos, including the
company i work for. With careful tuning, LwIP can be used. RAM is more
of an issues than FLASH, so you need to design your system with
limited number of threads since stacks are expensive, avoid putting
big objects on the stack and tune your stacks etc. Use the const
keyword where ever possible so that it stays in the rodata segment
which stays in flash etc.
eCos is usable on such systems, but requires a bit more thought and
design work to live with the RAM restrictions.
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