This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
RE: build/config/run problems
- To: Paul Kinzelman <PaulK at isdcorp dot com>
- Subject: RE: [ECOS] build/config/run problems
- From: Gary Thomas <gthomas at redhat dot com>
- Date: Fri, 07 Apr 2000 15:47:39 -0600 (MDT)
- Cc: ecos-discuss at sourceware dot cygnus dot com
On 07-Apr-00 Paul Kinzelman wrote:
> I'm trying to follow the ecos web page instructions to run
> ecos on a Cirrus EP7211 board. I have gotten to the
> thread_gdb.exe test (as described on 'ecos-tutorial.e.html').
>
> It appears that this test does not run under the insight
> window debugger. I have to use 'arm-elf-gdb -nw thread_gdb.exe',
> is this right? The web page says the filename should be 'thread_gdb'.
>
The distributed file is named 'thread_gdb.exe' for consistency
between Linux and Windows. Use whatever works :-)
> The 'set mips-force-32bit-saved-gpregs' command (strange that
> I would need to do a 'mips' command in 'arm') as described
> in the target setup instructions always results in an error:
> No symbol table is loaded. Use the "file" command.
> What does that mean?
>
This is an error in the documentation. Simply leave it out.
> If I just don't do that command, I get the
> <GDB Thread test OK>
> EXIT:<done>
> as described, but it's hung after that. From what I read, it
> sounds like it's supposed to work like this (hang after the end)?
>
Yes, eCos tests just hang in a tight loop. If you wanted to catch
this, you could set a breakpoint at 'cyg_test_exit' (we left this
out of this introduction in the manual for similicity)
> Then I make a config according to the page ecos-tutorial.11.html
> under 'Selecting a Target':
> cd <work directory>
> ecosconfig new edb7211
> ecosconfig tree
> under 'Using the command line'. I connect to the work area and do:
> make tests
> but I get a pile of 'nothing to be done for...' printouts, then:
> headers finished
> make -r -C hal/arm/arch/v1_3_1 arm.inc
> make[1]: Entering directory
> `/misc/exp/linux/research/ecos/wk/hal/arm/arch/v1_3_1'
> arm-elf-gcc -mcpu=arm7tdmi -Wall -Wpointer-arith -Wstrict-prototypes
> -Winline -Wundef -Woverloaded-virtual -g -O2 -ffunction-sections
> -fdata-sections -fno-rtti -fno-exceptions -fvtable- gc -finit-priority
> -I/misc/exp/linux/research/ecos/wk/install/include -I/opt/ecos/ecos-
> 1.3.1/packages/hal/arm/arch/v1_3_1
> -I/opt/ecos/ecos-1.3.1/packages/hal/arm/arch/v1_3_1/src -
> I/opt/ecos/ecos-1.3.1/packages/hal/arm/arch/v1_3_1/tests -I. -Wp,-MD,arm.tmp
> -o hal_mk_defs.tmp -S
> /opt/ecos/ecos-1.3.1/packages/hal/arm/arch/v1_3_1/src/hal_mk_defs.c
> cpp: too many input files
> make[1]: *** [arm.inc] Error 1
> make[1]: Leaving directory
> `/misc/exp/linux/research/ecos/wk/hal/arm/arch/v1_3_1'
> make: *** [build] Error 2
>
> I did build arm-elf-gcc on a server (Pent-3 I think), and am
> trying to run it on my Pentium-233 so maybe gcc built on the
> server won't run correctly?
>
> But the above error sounds like it would be something else.
>
This one's a bit harder. What version of the tools, etc, and what
platform are you running on?