This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

gdb and BDI2000 for MIPS5kc


Hi,

I try to use the BDI2000 box in order to debug a uClinux kernel source code
on 
a custom board with MIPS5kc (no MMU).

I have compiled gdb-5.3 for mips64 as follows:

gdb compilation
---------------
tar -xzf gdb-5.3.tar.gz
cd gdb-5.3
./configure --target=mipseb64-unknown-elf
make

I have opened a telnet session to the bdi box and did the 
following steps:


on the telnet session to bdi
----------------------------
BDI>reset
- TARGET: processing user reset request
- TARGET: reseting target passed
- TARGET: processing target startup ....
- TARGET: processing target startup passed
BDI>go
BDI>halt
    Target state      : debug mode
    Debug entry cause : JTAG break request
    Current PC        : 0xffffffff83feb6b4
    Current SR        : 0x00407f00
    Current LR  (r31) : 0xffffffff83feb674
    Current SP  (r29) : 0xffffffff83f8fe60
BDI>bi 0x80216904
Breakpoint identification is 0
BDI>go
- TARGET: target has entered debug mode
BDI>

after the reset and go command on the telnet session to the 
bdi box I have loaded the uClinux kernel to the ram of the board
and after inserting the breakpoint I have jumped to the code and
started execution of the kernel. (serial connection).

after this stage I have started the gdb session and got the following.

on the host
-----------
[test@lubovsky_pc linux-2.4.x]$ /tmp/gdb
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu
--target=mipseb64-unknown-elf".
(gdb) target remote bdi:2001      
Remote debugging using bdi:2001
Remote packet too long:
00000000000000000000000000000000ffffffff80216904ffffffff80216904ffffffff8022
d54cffffffff80219f740000000000000000ffffffff8108bef8000000005758595affffffff
8108befc00000000000000000000000000000000fffffffffffffffbffffffffffffffff0000
00000000000a0000000000000000ffffffff80219f74ffffffff8022d54c0000000000000000
ffffffffffffffffffffffffffffffffffffffff8019fc0cffffffff8022d7f4000000000000
0000ffffffff8108bdba0000000000000002ffffffff8108bf38ffffffff8108bf38ffffffff
8108a000ffffffff8108bee8ffffffff83ff1450ffffffff80216670000000001000fc010000
000000000180000000000000000000880018008829600000000000808000ffffffff80216904
ffffffffdeadbeefffffffffdeadbeefffffffffdeadbeefffffffffdeadbeefffffffffdead
beefffffffffdeadbeefffffffffdeadbeefffffffffdeadbeefffffffffdeadbee
Ignoring packet error, continuing...
0x00000000 in ?? ()
(gdb) 

Any idea what is wrong ?,
Thanks a lot,
Amit.




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