[U-Boot] U-boot debug<Program received signal SIGSTOP, Stopped (signal).0xfff00134 in boot_warm ()>

Hi WD,
Now we're debugging Microsys PM520 U-boot-1.2.0, and facing a huge problem, we can NOT debug the u-boot via BDI2000.
The below are our u-boot debugging procedures for your reference. Microsys PM520 (we used 2pcs Intel 28F128J3)
BDI2000 - Telnet BDI - reset - Unlock 0xfff00000 1000
GDB - ppc-linux-gdb u-boot - target remote bdi:2001 - (gdb) stepi
It looks like the "Program received signal SIGSTOP, Stopped (signal)." stopped in "bl fff03178 <init_5xxx_core>".
And "x/i $pc" reading was very unstable, so could you please give me some ideas about this point?
gdb -------------------------------------------------------------------------------------------- 0xfff00100 in _start () (gdb) stepi 0xfff00104 in _start () (gdb) 0xfff00108 in _start () (gdb) 0xfff00118 in boot_warm () (gdb) 0xfff0011c in boot_warm () (gdb) 0xfff00120 in boot_warm () (gdb) 0xfff00124 in boot_warm () (gdb) 0xfff00128 in boot_warm () (gdb) 0xfff0012c in boot_warm () (gdb) 0xfff00130 in boot_warm () (gdb)
Program received signal SIGSTOP, Stopped (signal). 0xfff00134 in boot_warm () (gdb) (gdb) x/i $pc 0xfff00134 <boot_warm+28>: bl 0xfff03178 <init_5xxx_core> (gdb) x/i $pc 0xfff00134 <boot_warm+28>: .long 0x0 (gdb) x/i $pc 0xfff00134 <boot_warm+28>: .long 0x0 (gdb) x/i $pc 0xfff00134 <boot_warm+28>: .long 0x0 (gdb) -----------------------------------------------------------------------------------------------
u-boot.s ----------------------------------------------------------------------------------------------- fff00118 <boot_cold>: fff00118: 7c a0 00 a6 mfmsr r5 fff0011c: 3c 60 f0 00 lis r3,-4096 fff00120: 60 63 00 00 ori r3,r3,0 fff00124: 7c 77 4b a6 mtspr 311,r3 fff00128: 54 63 84 3e rlwinm r3,r3,16,16,31 fff0012c: 3c 80 80 00 lis r4,-32768 fff00130: 90 64 00 00 stw r3,0(r4) fff00134: 48 00 30 45 bl fff03178 <init_5xxx_core> -----------------------------------------------------------------------------------------------
Thanks Kelven

Dear Kelven Huai,
In message F36C6302717C59478890A7775A4C8CC72540446445@MILEXCH2.ds.jdsu.net you wrote:
Now we're debugging Microsys PM520 U-boot-1.2.0, and facing a huge problem, we can NOT debug the u-boot via BDI2000.
U-Boot 1.2.0 is way over two years old. Don't expect much support for such old code. Is there any reason why you do not use a current version?
The below are our u-boot debugging procedures for your reference. Microsys PM520 (we used 2pcs Intel 28F128J3)
What does that mean "we used"? Did you modify the hardware?
Best regards,
Wolfgang Denk
participants (2)
-
Kelven Huai
-
Wolfgang Denk