<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Hardware Debuggers for 8280 :: More Thoughts :: Trace-32 </TITLE>
</HEAD>
<BODY>
<P><FONT FACE="Arial">Hello U-Booters-</FONT>
</P>
<P><FONT FACE="Arial">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.</FONT></P>
<P><FONT FACE="Arial">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. </FONT></P>
<P><FONT FACE="Arial">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.</FONT></P>
<P><FONT FACE="Arial">Sincerely, </FONT>
</P>
<P><FONT FACE="Arial">Kip Leitner</FONT>
</P>
<P><FONT FACE="Arial"> </FONT>
</P>
</BODY>
</HTML>