Dependency between eCos and RedBoot

["Lukas Riezler" <lukas dot riezler at gmx dot net>]

Hello ecos-guys :-)

I have modified both the variant HAL and platform HAL in a minimal way, to get eCos ported
on my FM3 (IAR KickStart Kit: MB9BF506R-SK).
Modifying the CDL-Files will be my next step.

But now I have a question about the dependency between eCos and RedBoot.
If I'm rigt, Redboot comes with two elementary functions:
- bootstrapping
- debbuging

My eval board has a kind of JTAG, so RedBoot's debugging facility isn't really needed by me. (?)
In the documentation and the book it's the suggestion first to run RedBoot.
But is RedBoot really essential to get eCos run on my board? Or are there any other ways to get this goal?
I don't have any experience with bootsrapping/-loading because I'm quite new in this
hardware-closeness business. Maybe I can burn ecos into flash? But I think for developing this won't be
the best way, is it?

I have built some libraries for test cases with the config-tool, but I have never seen any elf-file which
I could load on my board - only if I used the RedBoot package! In this case an elf-file was generated.
Okay, what I have now is "redboot.elf".
So I have to load RedBoot on my board. But how does RedBoot "load" my minimal eCos application on the
board?

Is the following chain of thougt correct?
1) load "redboot.elf" on the board
2) RedBoot can handle the generated ecos-file "libtarget.a" (and eCos will be started in this way?)

Is it possible that anybody throws some light in this issue? :)
Â
With kind regards,
Lukas

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