This is the mail archive of the ecos-discuss@sourceware.cygnus.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

[Fwd: MBX Stub]


 


I went back and follow the instructions very carefully.  When I try to build
the stub I get the following error message:

//D/PROGRA~1/REDHAT~1/eCos/packages/hal/common/v1_3_1/src/stubrom/stubrom.c
powerpc-eabi-gcc -msoft-float -mcpu=860 -g -nostdlib -Wl,--gc-sections -Wl,-
static -L//D/Projects/Blackbird/Tornado/newstub/mbx_install/lib -Ttarget.ld 
-o //D/Projects/Blackbird/Tornado/newstub/mbx_install/bin/gdb_module.img
src/stubrom/gdb_module.o
/tools/H-i686-pc-cygwin/powerpc-eabi/bin/ld: address 0xfe007dd0 of
//D/Projects/Blackbird/Tornado/newstub/mbx_install/bin/gdb_module.img
section .data is not within region ram
/tools/H-i686-pc-cygwin/powerpc-eabi/bin/ld: address 0xfe007e10 of
//D/Projects/Blackbird/Tornado/newstub/mbx_install/bin/gdb_module.img
section .sbss is not within region ram
/tools/H-i686-pc-cygwin/powerpc-eabi/bin/ld: address 0xfe00a6d4 of
//D/Projects/Blackbird/Tornado/newstub/mbx_install/bin/gdb_module.img
section .bss is not within region ram
collect2: ld returned 1 exit status
make[1]: ***
[//D/Projects/Blackbird/Tornado/newstub/mbx_install/bin/gdb_module.img]
Error 1
make[1]: Leaving directory
`/d/Projects/Blackbird/Tornado/newstub/mbx_build/hal/common/v1_3_1'
make: *** [build] Error 2


I also tried the image from the loaders subdirectory and couldn't get any
output from the board with it either.

Any other suggestions would be a great help.

Thanks,
Anthony

-----Original Message-----
From: jlarmour@cygnus.co.uk [mailto:jlarmour@cygnus.co.uk]On Behalf Of
Jonathan Larmour
Sent: Monday, June 05, 2000 11:24 AM
To: amassa@cts.com
Subject: Re: MBX Stub


"amassa@cts.com" wrote:
>
> Is there any specific terminal emulation or other settings I should look
> into more carefully?

Make sure flow control is disabled on your serial port.

> Does the stub expect a \r\n or just \n or can it handle both cases?

Actually what happens is that it sees the character (whatever it is), sees
it isn't a GDB packet, and outputs another 't' packet in response.

Perhaps go back to the hardware setup section in the docs, and double-check
you followed it all to the letter.

Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]