From: Bart Veer <bartv@redhat.com>
To: ahwa@fudan.edu
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] object format conversion
Date: Mon, 19 Feb 2001 06:47:00 -0000 [thread overview]
Message-ID: <200102191447.f1JElEJ02388@sheesh.cambridge.redhat.com> (raw)
In-Reply-To: <200102190615.WAA23573@cygnus.com>
>>>>> "Li" == Li Xinghua <ahwa@fudan.edu> writes:
Li> Hi,all
Li> I have a SuperTAP 386EX emulator with CAD-UL XDB debugger. And
Li> I want to run eCos based 386EX platform.
Li> As a new comer to ecos,the HAL porting is very difficult to
Li> me.
Li> Then I want to compile ecos source and applications using GNU
Li> complier and debug them using CAD-UL XDB and SuperTAP. But gcc
Li> generated ELF/a.out/COFF object file format ,and CAD-UL link
Li> tool produced OMF386 format. Is there any tool that can
Li> implement this conversion? Any advices to my development will
Li> be appreciated.
eCos has a number of dependencies on the GNU tools, including the
linker. Specifically it requires support for constructor priority
ordering, and it is very desirable for the linker to support
section-based garbage collection as well. See
http://sources.redhat.com/ecos/faq.html#porting_compiler for more
details.
This is all relatively straightforward when using the ELF format, but
some older formats are incapable of containing the relevant
information. I do not know the details of OMF386 or the CAD-UL tools,
so I cannot comment further on those. Ideally you would use gdb for
debugging purposes, but you would have to check with the gdb folks and
the emulator manufacturers to find out whether or not anybody has
contributed the appropriate code so that gdb can interact with the
SuperTAP.
Bart
next parent reply other threads:[~2001-02-19 6:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200102190615.WAA23573@cygnus.com>
2001-02-19 6:47 ` Bart Veer [this message]
2001-02-18 22:14 Li Xinghua
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=200102191447.f1JElEJ02388@sheesh.cambridge.redhat.com \
--to=bartv@redhat.com \
--cc=ahwa@fudan.edu \
--cc=ecos-discuss@sources.redhat.com \
/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).