Re: [U-Boot-Users] Re: BDI and u-boot

... (gdb) ni
<signal handler called> (gdb) disassemble Dump of assembler code for function boot_cold: 0xfff00118 <boot_cold+0>: lis r3,3841 0xfff0011c <boot_cold+4>: nop 0xfff00120 <boot_cold+8>: lwz r4,0(r3) 0xfff00124 <boot_cold+12>: nop (gdb) ni Cannot access memory at address 0x3b87018 (gdb) info program Debugging a target over a serial line. Program stopped at 0xfff00124. It stopped with signal SIGTRAP, Trace/breakpoint trap. (gdb)
I have discovered that if I use IMMR from default config for BDI WM32 0x0F0101A8 0x04700000 ;IMMR : internal space @ 0x04700000 ... then on 'ti' or 'go' it resetting after only a few commands (see above). If I comment the IMMR in ads8272.cfg (BDI config) then I can debug through BDI or gdb.
It resets as expected. BDI changes the IMMR from the HRCW to 0x04700000 and the u-boot code snippet shown is accessing address 3841 which is 0x0F010000 in hex which is no longer there....

It resets as expected. BDI changes the IMMR from the HRCW to 0x04700000 and the u-boot code snippet shown is accessing address 3841 which is 0x0F010000 in hex which is no longer there....
Thank you very much for your help. Indeed now it makes sense. Also (sorry) when I try to debug and on breakpoint I do (gdb) n It never comes back, and BDI shows that it 'stepping, stepping...' Have you or somebody seen this before? I really appreciate all your help. Thank you
participants (2)
-
Dmytro Bablinyuk
-
KokHow Teh