From: "Backhaus Willy" <w.backhaus@newage-avkseg.com>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] RE: FW: ecos on OMAP710 using CCS
Date: Wed, 22 Oct 2003 08:20:00 -0000 [thread overview]
Message-ID: <001501c39875$e02f55e0$f30210ac@backhaus> (raw)
In-Reply-To: <1066769041.8370.ezmlm@sources.redhat.com>
hello,
I have the same problem.
which CCS Version do you use?
I found this on TIs Website:
////////////////////////////////////////////////////////////////////////////
///////////////
Problem:
Can you load executables created from non-TI compilers into CCS?
Solution:
Yes. The ARM CCS v2.20 is capable of reading in executables produced by:
a. The ARM Ltd `ARM Developer Suite` v1.0.1, v1.1, and v1.2.
b. The GNU ARM compiler, version `2.9-psion-98r2`. (Run gcc with
the --version switch).
c. The Green Hills ARM compiler, v2.1.
Restriction #1: you must have 3 .dll`s in cc\bin updated to v1.8.14 or
higher: tiofr11.dll, tiofr_tial.dll, tiofr_gnu.dll
d. The MontaVista Linux GNU ARM compiler.
Testing has included using v3.2.1 with the -gdwarf-2 switch, and v2.95.3
with the -g switch (to get the old-style GNU stabs).
Restriction #1: the C/C++ code must ALL be compiled with the -gdwarf-2
switch, or ALL should be compiled with the -g switch. If there is any DWARF
in the executable, any non-DWARF (e.g. -g only) code will not have debug
info.
Restriction #2: you must have 3 .dll`s in cc\bin updated to v1.8.15 or
higher:
tiofr11.dll, tiofr_tial.dll, tiofr_gnu.dll
////////////////////////////////////////////////////////////////////////////
///////////////
I have CCS version 2.10
maybe a CCS upgrade will help.
Regards,
Willy Backhaus
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
parent reply other threads:[~2003-10-22 8:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1066769041.8370.ezmlm@sources.redhat.com>]
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='001501c39875$e02f55e0$f30210ac@backhaus' \
--to=w.backhaus@newage-avkseg.com \
--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).