Re: [ECOS] usage of *.ecm files ?

[Nick Garnett <nickg at ecoscentric dot com>]

"Armin Steinhoff" <A-Steinhoff@web.de> writes:

> Nick Garnett <nickg@ecoscentric.com> schrieb am 09.02.2005 13:39:04:
> 
> > Documentation on GRUB startup is here:
> > 
> > http://ecos.sourceware.org/docs-latest/user-guide/setup-i386-pc.html
> 
> OK, I tried it ... but the test executables have the wrong format for the Linux version of GRUB.
> I simply can't boot with it ... 

They ought to be ELF executables, which GRUB should be able to load
directly. Unless red Hat have removed that ability from their version
of GRUB. I would doubt that, though.

>  
> > Use the .ecm file if you want to build a GRUB version of RedBoot.
> 
> Hm .. how can I use it ... is there a tool ?


Configtool has an Import menu item. ecosconfig has an import
keyword. Take a look at the RedBoot documentation for how to build
RedBoot in general.

> 
> > Select GRUB startup in the configtool if you want to build a
> > stand-alone eCos application.
> 
> 'stand-alone application' means it is an image which is build by
> linking the kernel with an application together ?  Is it not
> possible to build a 'stand-alone' kernel running with a shell?

eCos does not have a shell. You link your application against the ecos
library to generate a single self-contained executable that contains
everything. Interactive use is either via RedBoot, or via GDB.

-- 
Nick Garnett                                          eCos Kernel Architect
http://www.ecoscentric.com                     The eCos and RedBoot experts
Besuchen Sie uns vom 22.-24.02.05 auf der Embedded World 2005, Stand 11-124
Visit us at Embedded World 2005, NÃrnberg, Germany, 22-24 Feb, Stand 11-124


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss