[U-Boot-Users] Debugging U-boot with BDI-2000 on MPC8349

[Ben Warren]

Hello,

Has anybody been able to successfully single step through U-boot code on
an MPC8349 CPU using a BDI-2000?  I've been working with an FAE at the
company that represents Abatron in the US, and he seems to think it's a
GDB problem.  Of course, I'd prefer it to be something else...  I'm
using the ppc_6xx-gdb version 6.3 that's part of ELDK 4.0.  I've also
built the latest gdb 6.5, but no dice there either.

Here's a snippet:

(gdb) target remote 10.69.69.200:2001
Remote debugging using 10.69.69.200:2001
0x00000100 in ?? ()
(gdb) b board_init_f
Breakpoint 1 at 0xfe0044a4: file board.c, line 374.
(gdb) c
Continuing.

Breakpoint 1, board_init_f (bootflag=1) at board.c:374
374     {
(gdb) list
369      *
370
************************************************************************
371      */
372
373     void board_init_f (ulong bootflag)
374     {
375             bd_t *bd;
376             ulong len, addr, addr_sp;
377             ulong *s;
378             gd_t *id;
(gdb) next
Cannot access memory at address 0xfd000efc
	
/****** This isn't an address in Flash!  The BDI-2000 shows the PC
incrementing, so 'next' did advance things ******/  

(gdb) del 1
(gdb) b relocate_code
Breakpoint 2 at 0xfe0035a0:
file /bld_home/bwarren/fpga/u-boot/cpu/mpc83xx/start.S, line 888.
(gdb) c
Continuing.

Breakpoint 2, relocate_code ()
    at /bld_home/bwarren/fpga/u-boot/cpu/mpc83xx/start.S:889
889             mr      r9,  r4         /* Save copy of Global Data
pointer */
(gdb) next
890             mr      r10, r5         /* Save copy of Destination
Address */

/****** We can single step through this code for some reason ******/

If anybody's seen this behavior and has any clues, please let me know.
I apologize if this is a bit off-topic.

regards,
Ben