This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
AW: Dependency between eCos and RedBoot
- From: "Richard Rauch" <rrauch at itrgmbh dot de>
- To: "'Lukas Riezler'" <lukas dot riezler at gmx dot net>, <ecos-discuss at sourceware dot org>
- Date: Wed, 10 Apr 2013 09:06:38 +0200
- Subject: AW: Dependency between eCos and RedBoot
- References: <trinity-66c4e736-1abb-4c7c-afdd-dee3758b9298-1365371708219 at 3capp-gmx-bs37>
Hi,
eCos is able to run without Redboot, too!
Specially for debugging with JTAG you could load your application binary directly to RAM and debug there.
Regarding your questions about files ".elf" and "libtarget.a"
Maybe you have a general misunderstanding, how eCos is working!
eCos is only a library, which you have to link to your application. You do not load eCos as operating system like linux to the target.
So the libtarget.a is a library file, not an executable binary!
By the way, if you are generating the tests within eCos Config Tool, you will get a lot of executable binary files for loading to the target (e.g. tm-basic).
Additional hint:
If you run eCos without Redboot, you need to take care about virtual vector table. As default an eCos application is calling some functions from Redboot. The linking mechanism is called "virtual vector tables", which is initialized from Redboot at startup. There are some options in eCos configuration to tell not to use this functionality. You need to change this, because as default this mechanism is enabled
Richard Rauch
ITR GmbH Informationstechnologie Rauch
Nuremberg/Germany
web: http://www.itrgmbh.de
email: info@itrgmbh.de
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss