From: Bart Veer <bartv@cygnus.co.uk>
To: mickp@cadence.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Re: Path from eCos to ARM 'aif' format?
Date: Mon, 22 Nov 1999 07:17:00 -0000 [thread overview]
Message-ID: <199911221517.PAA25829@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <38391F13.31BFF7D4@cadence.com>
>>>>> "Mick" == Mick Patrick <mickp@cadence.com> writes:
Mick> We want to target code developed using eCos to a particular
Mick> HW/SW co-verifier. This tool has an ARM7TDMI model but
Mick> unfortunately it at present requires the older aif (Arm
Mick> Intermediate Format) as source to their proprietary utility
Mick> that generates S-Records and associated debug information
Mick> files.
Mick> We looked at using ARM's fromelf utility to translate elf
Mick> generated using arm-elf-gcc, but it transpires that fromelf
Mick> is very ARM toolchain specific.
Mick> Can anyone help with the immediate problem of getting code
Mick> with eCos compiled and down to aif?
If you can make do with just S-Records at the end of the day, it
should be possible to coax objcopy into generating those.
If you really do need aif support then I do not think there is a
simple solution. There is no support in the GNU tools for that format,
and it seems unlikely that any such support will be added at this
stage. Unless you can coax the ARM tools into doing the right thing
somehow I suspect you are out of luck.
Bart Veer // eCos net maintainer
next prev parent reply other threads:[~1999-11-22 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-22 2:49 [ECOS] " Mick Patrick
1999-11-22 7:17 ` Bart Veer [this message]
1999-11-24 18:48 ` [ECOS] elf for thumb Lance Uyehara
1999-11-25 8:08 ` Jonathan Larmour
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=199911221517.PAA25829@sheesh.cygnus.co.uk \
--to=bartv@cygnus.co.uk \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=mickp@cadence.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).