[U-Boot-Users] debug u-boot using bdi2000
Reeve Yang
yang.reeve at gmail.com
Fri Oct 13 20:23:34 CEST 2006
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:
(gdb) c
Continuing.
Warning:
Cannot insert breakpoint -31.
Error accessing memory address 0xfff00100: Unknown error 4294967295.
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.
Regards,
- Reeve
On 10/13/06, Reeve Yang <yang.reeve at gmail.com> wrote:
>
> 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:
>
> Cannot find bounds of current function
>
> 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?
>
> On 10/13/06, Ben Warren <bwarren at qstreams.com> wrote:
> >
> > On Fri, 2006-10-13 at 17:41 +0000, Reeve Yang wrote:
> > > I'm trying to use bdi2000+gdb to debug u-boot. The image is ROM image
> > > on flash, whenever I connect gdb to bdi, I saw execution stops at:
> > >
> > > _start: /* time t 0 */
> > > li r21, BOOTFLAG_COLD /* Normal Power-On: Boot from FLASH*/
> > > ===>here
> > > nop
> > > b boot_cold
> > >
> > > Then though I can set break point, e.g. cpu_init_f, but when continue
> > > running break point never stops execution and u-boot just runs by
> > > itself.
> > >
> > > Does it mean I can only debug ram image? does anyone has experience on
> > > this could shed some lights?
> > >
> > > Thanks.
> > >
> > > - Reeve
> > Remember to use hardware breakpoints, and that your CPU (you didn't
> > mention what type) may only have one. You'll have to clear it after
> > reaching each breakpoint. Read the BREAKMODE and STEPMODE entries
> > (TARGET chapter) in your BDI manual. Also, can you single step through
> > the ROM code?
> >
> > regards,
> > Ben
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20061013/b1d8c61a/attachment.htm
More information about the U-Boot
mailing list