RE: u-boot debugging

Besides, the BDI has only a 10Mbps Ethernet interface.  It might be enough for simple debug operation but they should

Have put a 100Mbps link to put it on a shared network.  For an isolated network configuration, it should suffice...

 

The Metrowerks debugger is USB 2.0 based, so on a isolated network and faster data throughput for easy symbol/code

cross referencing.

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Atul Sabharwal

c/o Azad. Inc.

503-962-9395

________________________________

From: Sabharwal, Atul 
Sent: Friday, January 20, 2006 10:00 AM
To: Sabharwal, Atul; 'Mustafa Çayır'; 'linuxppc-embedded@ozlabs.org'
Subject: RE: u-boot debugging

 

My best guess is the PowerTap Pro supports code tracing from a trace buffer on the board or processor... Not sure if

you can sample the processor instruction stream over the JTAG chain as its too slow.  You could use a logic analyzer

or an in-circuit emulator to capture all signals.  The power pc has a SIU to pass the instruction stream for a logic analyzer

to use...

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Atul Sabharwal

c/o Azad. Inc.

503-962-9395

________________________________

From: Sabharwal, Atul 
Sent: Friday, January 20, 2006 9:57 AM
To: 'Mustafa Çayır'; linuxppc-embedded@ozlabs.org
Subject: RE: u-boot debugging

 

BDI works but PowerTap Pro from Metrowerks is better.  The debug interface is windows based and more user friendly than

Ddd on Linux.  Take your pick as a commercial product would be better than an opensource product till it has been perfected

(i.e. customized, all bugs fixed and usability issues resolved).  And no service from the community on occasion.

 

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Atul Sabharwal

c/o Azad. Inc.

503-962-9395

________________________________

From: linuxppc-embedded-bounces@ozlabs.org [mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of Mustafa Çayir
Sent: Thursday, January 19, 2006 10:51 PM
To: linuxppc-embedded@ozlabs.org
Subject: u-boot debugging

 

Hi,

 

Which tool must i use to debuggin u-boot codes. BDI2000 or windriver visionclick, which one do you prefer? is step by step code tracing possible?

 

thanks