This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: zImage Help.
"Vijay Jayaraman" <Vijay.Jayaraman@Colorado.edu> writes:
> Nick,
> I am just trying to figure out where to go next after configuring Redboot
> and successfully testing all the tests from a normal ecosconfig new pc
> build. I had this notion that I need to install the kernel into the hard
> disk some how (or run it from memory) so that I can run my custom program on
> it. I didnt realize that all you need to do is write your code compile it
> and then load it via tftpboot. (Please correct me if I am wrong, This is
> just my guess from reading the posts online...)
You compile your application against the set of headers supplied by
eCos and then link it with the ecos library to generate an ELF
executable, which includes all of eCos kernel and all. This is then
loaded directly by GDB or can be converted to a binary or S-Record
image for loading in RedBoot.
>
> Also, one more question, when I wanted to write the ip_address configured
> Redboot onto a bootable floppy, I need to import a file called Floppy.ecm
> file or so. If I did not do that, all I get is an elf image and I am unable
> to boot with that. I thought elf images were some sort of linux executables.
> I dont know why they cannot be used to boot from floppy... So I suppose one
> needs to import the .ecm file everytime he wants to create a Redboot.bin
> file.
You must always use the .ecm file for generating RedBoot.
I think you need to go back and read the documentation again.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss