From: "Richard Rauch" <rrauch@itrgmbh.de>
To: "'Lukas Riezler'" <lukas.riezler@gmx.net>, <ecos-discuss@sourceware.org>
Subject: AW: [ECOS] Dependency between eCos and RedBoot
Date: Wed, 10 Apr 2013 07:06:00 -0000 [thread overview]
Message-ID: <001a01ce35b9$f22cb080$d6861180$@itrgmbh.de> (raw)
In-Reply-To: <trinity-66c4e736-1abb-4c7c-afdd-dee3758b9298-1365371708219@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
prev parent reply other threads:[~2013-04-10 7:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 21:55 Lukas Riezler
2013-04-08 7:28 ` Ross Younger
2013-04-08 9:07 ` Ilija Kocho
2013-04-10 7:06 ` Richard Rauch [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001a01ce35b9$f22cb080$d6861180$@itrgmbh.de' \
--to=rrauch@itrgmbh.de \
--cc=ecos-discuss@sourceware.org \
--cc=lukas.riezler@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).