This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: insight-5.1 build problems
- From: David Oberbeck <dgo at microsynetics dot com>
- To: "'ecos-discuss at sources dot redhat dot com'" <ecos-discuss at sources dot redhat dot com>
- Date: Tue, 26 Feb 2002 08:16:59 -0700
- Subject: Re: [ECOS] insight-5.1 build problems
- Organization: Microsynetics
- References: <AB439ADBB821D41181CC00D0B7458AEB01AF9FD5@SRV-EXCHANGE>
- Reply-to: dgo at microsynetics dot com
On Tuesday 26 February 2002 03:29, Jesper Kjeldsen Wrote Thusly:
> I have tried to build insight-5.1 for target = arm-elf for use with eCos on
> the Atmel EB40 board, but this doesn't seem to work. Has anybody tried to
> use Insight-5.1 (with success) together with this configuration (or any
> other configuration with eCos). I am using binutils, gcc and so on, as
> described on the redhat home page.
Jesper,
Some questions / checklists:
-> What host platform: Linux, Win / Cygwin...?
-> Did the build fail?
-> Or does it fail when you attempt to use it?
-> Are you using the Angel debugger which comes with the
board, or did you install RedBoot per the docs? Or are you
using a JTAG emulator?
-> When you built eCos did you enable debugging (-g option);
you must see this in the global compiler flags area and the
global linker flags area in the configtool.
-> When you build your app which links to eCos did you enable
debugging (-g option in your makefile)?
FWIW, we use the Gnu ARM tool chain / eCos for development on EB40
as well as a number of custom ARM7 & StrongARM targets; this whole
setup works extremely well.
We use newer versions of the tools on Linux hosts than on the Red
Hat eCos pages. We use Mandrake 8.1 on our hosts, and a number of our
clients use Red Hat 7.1 and 7.2; this tool setup has also been tested
on those hosts as well. Specifically the tools:
binutils-2.11.2
gcc-3.0.3
insight-5.1
From our build scripts, this is how we built insight / gdb 5.1:
mkdir /tools/arm_tools_src/gdb
cp -p fromwherever/insight-5.1.tar.bz2 /tools/arm_tools/gdb
cd /tools/arm_tools_src/gdb
tar jxvf insight-5.1.tar.bz2
mkdir /tools/arm_tools_src/gdb/insight-build
cd /tools/arm_tools_src/gdb/insight-build
/tools/arm_tools_src/gdb/insight-5.1/configure --target=arm-elf --prefix=/tools/arm_tools --exec-prefix=/tools/arm_tools/H-i686-pc-linux-gnu -v 2>&1 | tee configure.out
make -w all 2>&1 | tee make.out
make -w install 2>&1 | tee make_install.out
With this we can connect to the remote targets (including EB40)
using either RedBoot over a serial port (gdb target remote serial) to
a RedBoot monitor, or through a JEENIE emulator (gdb target remote
Angel / Ethernet). We have RedBoot installed on our EB40s, and on
custom hardware... We use EB40s to write and test as much code as we
can before the final ARM7 target hardware is available; this way we
can "pipeline" the software development this way resulting in shorter
overall development times.
The only problem we see is with this tool chain is that gdb /
Insight segfaults when we attempt to expand a C++ "this" pointer;
everything else seems to work really well.
When I have some spare time I was going to try and build 5.1.1 and
see if the "this" problem has been corrected; but only so many hours
in the day...
HTH,
DGO
> Best Regards
> Jesper Kjeldsen
> Project Engineer, E.E.
>
> Phone direct: +45 9652 0345
> E-mail: jk@penell.com <mailto:jk@penell.com>
> ---------------------------------------------------------------------------
>- -------------
> Penell A/S - An RTX Company
> Plastvaenget 9
> DK-9560 Hadsund
> Denmark.
> Phone: +45 9857 2666
> Fax: +45 9857 2664
> Website: www.penell.com <http://www.penell.com>
> ---------------------------------------------------------------------------
>- -------------
--
"Entropy Requires No Maintenance"
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss