[U-Boot-Users] Debugging U-Boot with BDI3000

[onyxtape <onyxtape@hotmail.com>]

Hi there,

I have a BDI3000, and I was starting a remote GDB debugging session per the
instructions on http://www.denx.de/wiki/DULG/DebuggingUBoot. I reset the
target prior to running these commands. I've tried this with both U-Boot
1.3.2 and 1.3.3.

When I enter the "target remote" command, it ends up in 0x00000000 instead
of the reset vector at 0xfffffffc. I have pasted my commands below. Can
anyone tell me what I'm missing? I just want to step through a few
instructions and verify that the reset vector code jumps to _start (or
_start_440 in my case), and then step through _start afterwards.


user at SW:~/work/src/eldk/ppc_4xxFP/usr/src/u-boot-1.3.3$ ppc_4xxFP-gdb u-boot
GNU gdb Red Hat Linux (6.3.0.0-1.21_3rh)
Copyright 2004 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=i386-redhat-linux --target=ppc-linux".
The target architecture is set automatically (currently powerpc:403)
..
(gdb) target remote 192.168.1.64:2001
Remote debugging using 192.168.1.64:2001
0x00000000 in ?? ()
(gdb) b cpu_init_f
Breakpoint 1 at 0xfff82898: file cpu_init.c, line 211.
(gdb) c
Continuing.

Program received signal SIGSTOP, Stopped (signal).
0xbebebebe in ?? ()
(gdb) quit
The program is running.  Exit anyway? (y or n) y
user at SW:~/work/src/eldk/ppc_4xxFP/usr/src/u-boot-1.3.3$ 

-- 
View this message in context: http://www.nabble.com/Debugging-U-Boot-with-BDI3000-tp17346329p17346329.html
Sent from the Uboot - Users mailing list archive at Nabble.com.