From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmytro Bablinyuk Date: Wed, 05 Oct 2005 17:05:45 +1000 Subject: [U-Boot-Users] Re: BDI and u-boot In-Reply-To: References: Message-ID: <43437B49.9020008@rftechnology.com.au> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de > Try `ti` instead of `go` to see where it resets. ... (gdb) ni (gdb) disassemble Dump of assembler code for function boot_cold: 0xfff00118 : lis r3,3841 0xfff0011c : nop 0xfff00120 : lwz r4,0(r3) 0xfff00124 : nop 0xfff00128 : rlwinm r4,r4,0,8,5 0xfff0012c : nop 0xfff00130 : oris r4,r4,512 0xfff00134 : nop 0xfff00138 : stw r4,0(r3) 0xfff0013c : 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. BUT - if I do (gdb) reset (gdb) c Continuing. Program received signal SIGSTOP, Stopped (signal). AND If I do (gdb) reset (gdb) ni (gdb) ni (gdb) c Continuing. Breakpoint 2, (gdb) p dest_addr $1 = 0x3fc7000 ... It's like a delay required or I don't know what it is - I just need to do a few 'ni' before 'c', otherwise I have SIGSTOP. I think I am missing something. ALSO if I type (gdb) n then it will never come back and I can see on BDI - TARGET: stepped - TARGET: stepped - TARGET: stepped ... Have you seen this before? What I missed? Thank you