This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: usage of *.ecm files ?
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Armin Steinhoff <A-Steinhoff at web dot de>
- Cc: NickGarnett <nickg at ecoscentric dot com>, ecos-discuss at ecos dot sourceware dot org
- Date: Wed, 9 Feb 2005 15:52:58 +0100
- Subject: Re: [ECOS] usage of *.ecm files ?
- References: <547358011@web.de>
On Wed, Feb 09, 2005 at 03:22:42PM +0100, Armin Steinhoff wrote:
> 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 ...
>
> > Use the .ecm file if you want to build a GRUB version of RedBoot.
>
> Hm .. how can I use it ... is there a tool ?
ecosconfig import
The gui tool has a similar functionality.
>
> > 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 images contain both the eCos and the application statically
linked together. There is no concept of just a kernel and a shell
which you can use to load other applications.
What Nick is refering to us an application image which does the real
application, as opposed to a RedBoot image which is just a bootloader.
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