[U-Boot] U-Boot hangs when board is attached to BDI2000

[Dunda, Matthias]

Hi all,

I am trying to debug u-boot following the instructions in DULG 10.1.

As mentioned in 10.1.1. before relocation I connect to the target an get
desired first output:

Remote debugging using jtag:3333
0xfffffffc in ?? ()

Even without setting a breakpoint then, I just say gdb to continue:

(gdb) c
Continuing.

The output in the console then is:

U-Boot 2009.08 (Nov 25 2009 - 09:18:37)

CPU:   8568E, Version: 1.1, (0x807d0011)
Core:  E500, Version: 2.2, (0x80210022)
Clock Configuration:
       CPU0:1320 MHz,
       CCB:528  MHz,
       DDR:264  MHz (528 MT/s data rate), LBC:66   MHz
       QE:528  MHz
L1:    D-cache 32 kB enabled
       I-cache 32 kB enabled
Board: 8568 MDS
I2C:   ready
DRAM:  Initializing
    SDRAM: 64 MB
    DDR: 512 MB (DDR2, 64-bit, CL=4, ECC off)

...and nothing further happens.

After 30 secs or so, I simply hit Ctrl-C and get:

^C
Program received signal SIGSTOP, Stopped (signal).
0x1ff70700 in ?? ()
(gdb) bt
#0  0x1ff70700 in ?? ()
#1  0x1ff71574 in ?? ()
Cannot access memory at address 0xdeadbef3
(gdb) 

When I issue a "reset run" within the BDI shell, the target boots as
expected, but when I start the target with "reset halt" to debug it from the
first instruction it behaves at described above.

I am using a BDI2000 on a Freescale MPC8568E-MDS board. U-boot 2009.08 is
compiled with

  make CROSS_COMPILE=ppc_85xx- MPC8568MDS_config
  make CROSS_COMPILE=ppc_85xx- all

Any ideas? Is there some watchdog issue to cope with, maybe? 

Cheers
Matthias