[ECOS] eCos Footprint

Jonathan Larmour jlarmour@redhat.com
Wed Jan 16 08:11:00 GMT 2002


Stass Desyatnikov wrote:
> 
> Dear All,
> 
> I'm trying to select an OS for my new project. The requirements dictated by
> the customer are:
> 1) Small RAM/ROM footprint - 350k/400k

Shouldn't be a problem at all. eCos can be configured real small. Of course
it may depend on the target you want to use but I can't think of any that
would definitely use more than that. And certainly of that most of the RAM
space would be occupied by TCP buffers (which you can configurably size),
which is no real surprise. But perhaps your figure wasn't even accounting
for that!

> 2) TCP/IP
> 3) UDP slave

Definitely :-).

> 4) 80% Source code portability to Linux
> 
> Well it sounds like eCos but I have my doubts about the portability issue
> and the footprint.

Hate to say it but "80% source code portability" sounds like a very vague
term! Remembering, of course, that eCos is single process multi-threaded
(it's meant to be lightweight after all!), it implements most of the
standard APIs anyone on an embedded system would want to use. As a guide,
eCos implements EL/IX level 1, a Linux compatibility interface optimized
for the embedded space: http://sources.redhat.com/elix/

Of course if there were any specific omissions, it's Open Source so you can
add them, or easier, contract some experts (like Red Hat :-)) to do it all
for you, test it and provide support etc.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine



More information about the Ecos-discuss mailing list