[U-Boot-Users] debug uboot-1.1.1 with BDI2000 after it relocated

olivier at singla.us olivier at singla.us
Thu Dec 2 17:18:45 CET 2004


I am having trouble to debug u-boot-1.1. 1 once it has relocated itself.
The platform I am using is the LITE5200 (64 MB RAM).
For these tests, I am loading uboot in RAM ("TEXT_BASE = 0x00020000"),
so starting address is 20100. I am using gdb 6.3 with the BDI2000 debug

I can debug fine until u-boot relocate to the end of the available RAM:

/phoenix/uboot-1.1.1$ powerpc-linux-gdb --nx
GNU gdb 6.3
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=i686-pc-linux-gnu --target=powerpc-linux".
(gdb) target remote bdi:2001
Remote debugging using bdi:2001
<signal handler called>
(gdb) symbol-file u-boot
Reading symbols from /phoenix/uboot-1.1.1/u-boot...done.
(gdb) break relocate_code
Breakpoint 1 at 0x2333c: file /phoenix/uboot-1.1.1/cpu/mpc5xxx/start.S,
line 572.
(gdb) c

Breakpoint 1, relocate_code () at
573             mr      r9,  r4         /* Save copy of Global Data
pointer     */
(gdb) break 661
Breakpoint 2 at 0x23424: file /phoenix/uboot-1.1.1/cpu/mpc5xxx/start.S,
line 661.
(gdb) del 1
(gdb) c

Breakpoint 2, relocate_code () at
661             blr
(gdb) si
Cannot access memory at address 0x206d6ff5
(gdb) bt
#0  <signal handler called>
Cannot access memory at address 0x206d6ff5

More information about the U-Boot mailing list