[U-Boot-Users] Debugging U-Boot on 440GP

Chuck Meade chuck at ThePTRGroup.com
Tue Nov 25 18:26:18 CET 2003

Hi Brian,

Take a look in U-Boot code for _start_440.  The debug registers
are immediately initialized, which will throw the BDI2000 HW
brkpts off.  I have had similar experiences debugging through
other architectures' U-Boot startup sequences as well.

The 0x700 and 0x1400 are standard 440GP exception vector
locations that will be documented fully in a 440GP manual.

Hope this helps explain things,
Chuck Meade
The PTR Group, Inc.

> -----Original Message-----
> From: u-boot-users-admin at lists.sourceforge.net
> [mailto:u-boot-users-admin at lists.sourceforge.net]On Behalf Of Brian
> Padalino
> Sent: Tuesday, November 25, 2003 11:22 AM
> To: U-Boot Mailing List
> Subject: [U-Boot-Users] Debugging U-Boot on 440GP
> I have a BDI2000 and a custom target board.  I am can successfully connect
> to it and step through single instructions.  I can also set a breakpoint at
> _start_440, but any breakpoints after that do not get noticed.  I have the
> BDI setup for HARD breakpoints.  Should I have it setup for SOFT instead?
> What I am seeing is that when I stop the CPU, it's either at 0x700 or
> 0x1400 -- both of which are defined in the kgdb.c file, but I don't know
> what they mean.  Can anyone shed any light on the situation for me?  I am
> very new to both the BDI and using gdb (but I learn quickly).
> Thank you, and much is appreciated.
> Brian Padalino
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?  SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users

More information about the U-Boot mailing list