[U-Boot-Users] Hardware Debuggers for 8280 :: More Thoughts :: Trace-32
Hello U-Booters-
To debug, as well as observe the operation of U-boot on PQ2FADS (MPC8280), I have been using for several months -- with fairly good results -- the in-circuit debugger Trace-32, from Lauterbach, a German company. This JTAG interface tool allows me to write scripts in their debugger language, "Practice", which erase the flash memory on the PQ2FADS and iteratively reprogram it with successive versions of u-boot, so I can see the effects of adding and removing various u-boot features.
I have also had good success in using this tool (after some initial configuration headaches) to set breakpoints at high-level code after U-boot relocates to RAM. I have briefly experimented with kernel debugging, but we really aren't at that point yet, still bringing up our custom PPC hardware.
If anyone else is using Trace-32 ICD (In-Circuit Debugger, note -- not IC(E)mulator), I would have interest in contacting you offline in order to discuss some of the finer points of using this tool in the development process.
Sincerely,
Kip Leitner
In message 1B1B671D73FED2119B1000A0C9B8A96087FCC7@ORBNET Kip Leitner wrote:
To debug, as well as observe the operation of U-boot on PQ2FADS (MPC8280), I have been using for several months -- with fairly good results -- the in-circuit debugger Trace-32, from Lauterbach, a German company. This JTAG interface tool allows me to write scripts in their debugger language, "Practice", which erase the flash memory on the PQ2FADS and iteratively reprogram it with successive versions of u-boot, so I can see the effects of adding and removing various u-boot features.
Just to point out: you can do the same using the BDI2000, but without need to learn a new, proprietarty language. I normally use the BDI's telnet interface in combination with expect / tcl scripts. The same can be done using the GDB command line interface and definitions of GDB macros, or again expect.
Once more this is an area where one group of people will ask for the fancy GUI tool with "extended features", while others are happy with a standard command line interface which is scriptable using standard tools of the Unix toolbox.
If anyone else is using Trace-32 ICD (In-Circuit Debugger, note -- not IC(E)mulator), I would have interest in contacting you offline in order to discuss some of the finer points of using this tool in the development process.
Sorry, I can't help here.
Best regards,
Wolfgang Denk
participants (2)
-
Kip Leitner -
Wolfgang Denk