5509a JTAG and Xilinx Impact
Started by ●October 30, 2007
Does anyone know if it's possible to use Xilinx's Impact and usb
platform cable to do a boundary scan on the 5509a? Specifically the spectrum
digital TMS320VC5509a DSK board.
Reply by ●October 30, 20072007-10-30
M Gora-
> Does anyone know if it's possible to use Xilinx's Impact and usb platform
> cable to do a boundary scan on the 5509a? Specifically the spectrum
> digital TMS320VC5509a DSK board.
It may not work because the iMPACT setup doesn't handle EMU0 and EMU1 connections.
But what's the point of a boundary scan on a DSK board? The DSK board is a "known
good" -- it works. JTAG is used with this board in conjunction with Code Composer
Studio (CCS) software, in order to debug run-time DSP code. Certainly the Xilinx
tools can't be used with CCS for this purpose.
-Jeff
> Does anyone know if it's possible to use Xilinx's Impact and usb platform
> cable to do a boundary scan on the 5509a? Specifically the spectrum
> digital TMS320VC5509a DSK board.
It may not work because the iMPACT setup doesn't handle EMU0 and EMU1 connections.
But what's the point of a boundary scan on a DSK board? The DSK board is a "known
good" -- it works. JTAG is used with this board in conjunction with Code Composer
Studio (CCS) software, in order to debug run-time DSP code. Certainly the Xilinx
tools can't be used with CCS for this purpose.
-Jeff
Reply by ●October 30, 20072007-10-30
Well long story short I need to test the effects of a JTAG boundary scan on
certain system software that has been developed. I was hoping to have a more
controlled boundary scan than using code composer studio as I don't know
exactly what it's doing when it connects to the board.
Reply by ●October 30, 20072007-10-30
M Gora-
> Well long story short I need to test the effects of a JTAG boundary scan on certain system software that has been developed. I was hoping to have a more controlled boundary scan than using code composer studio as I don't know exactly what it's doing when it connects to the board.
You're going to run boundary scan with DSP software running, correct? Hope not --
that's a sure recipe for disaster. You must mean host software or other external
software connect to I/O (USB, McBSP etc). Please clarify.
-Jeff
> Well long story short I need to test the effects of a JTAG boundary scan on certain system software that has been developed. I was hoping to have a more controlled boundary scan than using code composer studio as I don't know exactly what it's doing when it connects to the board.
You're going to run boundary scan with DSP software running, correct? Hope not --
that's a sure recipe for disaster. You must mean host software or other external
software connect to I/O (USB, McBSP etc). Please clarify.
-Jeff
Reply by ●October 31, 20072007-10-31
The software that will be running is very simple, this is rather an attempt to
look at the behavior of the DSP during a boundary scan. Specifically I am
curious as to the activity of the watchdog timer and it's ability to reset
the DSP or fire an interrupt during a boundary scan.
-Mike
-Mike
Reply by ●October 31, 20072007-10-31
M Gora-
> The software that will be running is very simple, this is rather an
> attempt to look at the behavior of the DSP during a boundary scan.
> Specifically I am curious as to the activity of the watchdog timer
> and it's ability to reset the DSP or fire an interrupt during a
> boundary scan.
My understanding is that in boundary scan mode (indicated to the DSP by state of EMU0
+ EMU1 lines on the JTAG interface) no circuitry on the DSP will be running.
This could be wrong, or newer TI DSPs may act differently -- if that's the case
hopefully someone like Mike Dunn who knows more about JTAG interface than I do would
provide correct information.
-Jeff
> The software that will be running is very simple, this is rather an
> attempt to look at the behavior of the DSP during a boundary scan.
> Specifically I am curious as to the activity of the watchdog timer
> and it's ability to reset the DSP or fire an interrupt during a
> boundary scan.
My understanding is that in boundary scan mode (indicated to the DSP by state of EMU0
+ EMU1 lines on the JTAG interface) no circuitry on the DSP will be running.
This could be wrong, or newer TI DSPs may act differently -- if that's the case
hopefully someone like Mike Dunn who knows more about JTAG interface than I do would
provide correct information.
-Jeff
Reply by ●November 1, 20072007-11-01
