Shall I use bdi telnet interface to set hardware break point or use
gdb, or they are the same? I set break point mode into "HARD", then
using gdb set break point, it never stops; if I use bdi interface to
set, I saw following message when continue in gdb:<br>
<br>
(gdb) c<br>
Continuing.<br>
Warning:<br>
Cannot insert breakpoint -31.<br>
Error accessing memory address 0xfff00100: Unknown error 4294967295.<br>
<br>
I think we should be able to use software break point in RAM image,
right? I really appreciate if you could give a hand on this issue. I
need it urgently to debug further issues.<br>
<br>
Regards,<br>
<br>
- Reeve<br><br><div><span class="gmail_quote">On 10/13/06, <b class="gmail_sendername">Reeve Yang</b> <<a href="mailto:yang.reeve@gmail.com">yang.reeve@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
My CPU is MPC8345E, it's same as MPC8349E with e300 core. Yes, it only
supports on hardware break point. I tried it and it didn't work either.
When I try to single step the code, I got following message on gdb
session:<br>
<br>
Cannot find bounds of current function<br>
<br>
Is it possible to debug ROM image? Can bdi2000 debug ram image
directly? I assume the "load" command is to load image into any memory
space, including ram, right?<div><span class="e" id="q_10e42dfae7155234_1"><br><br><div><span class="gmail_quote">On 10/13/06, <b class="gmail_sendername">Ben Warren</b> <<a href="mailto:bwarren@qstreams.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
bwarren@qstreams.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, 2006-10-13 at 17:41 +0000, Reeve Yang wrote:<br>> I'm trying to use bdi2000+gdb to debug u-boot. The image is ROM image<br>> on flash, whenever I connect gdb to bdi, I saw execution stops at:<br>><br>> _start: /* time t 0 */
<br>> li r21, BOOTFLAG_COLD /* Normal Power-On: Boot from FLASH*/<br>> ===>here<br>> nop<br>> b boot_cold<br>><br>> Then though I can set break point, e.g. cpu_init_f, but when continue
<br>> running break point never stops execution and u-boot just runs by<br>> itself.<br>><br>> Does it mean I can only debug ram image? does anyone has experience on<br>> this could shed some lights?<br>>
<br>> Thanks.<br>><br>> - Reeve<br>Remember to use hardware breakpoints, and that your CPU (you didn't<br>mention what type) may only have one. You'll have to clear it after<br>reaching each breakpoint. Read the BREAKMODE and STEPMODE entries
<br>(TARGET chapter) in your BDI manual. Also, can you single step through<br>the ROM code?<br><br>regards,<br>Ben<br><br><br></blockquote></div><br>
</span></div></blockquote></div><br>