ML605 JTAG problem

DominicB · ‎11-18-2011

Hello,

I have just puchased an ML605 dev board, but I am havin problems in seeing the JTAG chain on the board. The USB driver has installed correctlly as I can see the Digilent JTAG-HS1 via Impact. The problem is the chain, when I initialise it, no matte what jumper setting for J17 and J18 I get the following;

"There are many unknown devices being detected. Press Yes to continu or press No to stop."

Even with no jumpers attached I still get the same response from Impact which is not what I would expect (I would expect a broken chain response). I suspect there is a short somewhere close to the Digilent chip or am I going nuts.

Help!

Kind Regards.

Dominic

KountryK · ‎07-09-2009

The Digilent JTAG HS1 is meant to plug into a JTAG PC4 connector such as that found on many other boards such as the Avnet Spartan-6 LX150T board. It serves the same function as the Xilinx Platform Cable USB II. The PC4 Option (J24) is typically not populated on the ML605.

What happens if you use just a simple UCB Cable from your PC (Type-A) to the USB (Typ-Mini-B) JTAG port (labeled JTAG on faceplate)?

If you investigate the schematics of the ML605, you will find the design utilizes a Cypress CYC6801 to implement a USB-JTAG Bridge to the on-board JTAG Chain.

If you do not have an FMC populated that supports JTAG, then J17 and J18 should both be set to 1-2. Looking at board with FMC connectors on top, this would be J18 Pins Left, J17 Pins Top.

Here’s what I get with Impact, using the simple USB cable described above.

// *** BATCH CMD : setCable -port auto

AutoDetecting cable. Please wait.

PROGRESS_START - Starting Operation.

Connecting to cable (Usb Port - USB21).

Checking cable driver.

Driver file xusbdfwu.sys found.

Driver version: src=1027, dest=1027.

Cable PID = 0008.

Max current requested during enumeration is 74 mA.

Type = 0x0004.

Cable Type = 3, Revision = 0.

Setting cable speed to 6 MHz.

Cable connection established.

Firmware version = 1029.

File version of C:/Xilinx/13.2/ISE_DS/ISE/data/xusb_xlp.hex = 1303.

Firmware hex file version = 1303.

Downloading C:/Xilinx/13.2/ISE_DS/ISE/data/xusb_xlp.hex.

Downloaded firmware version = 1303.

PLD file version = 0012h.

PLD version = 0012h.

PROGRESS_END - End Operation.

Elapsed time = 0 sec.

Type = 0x0004.

ESN option: 000013EA95C401.

Attempting to identify devices in the boundary-scan chain configuration...

INFO:iMPACT - Current time: 12/22/2011 12:13:48 PM

// *** BATCH CMD : Identify -inferir

PROGRESS_START - Starting Operation.

Identifying chain contents...'0': : Manufacturer's ID = Xilinx xc6vlx240t, Version : 4

INFO:iMPACT:1777 -

Reading C:/Xilinx/13.2/ISE_DS/ISE/virtex6/data/xc6vlx240t.bsd...

INFO:iMPACT:501 - '1': Added Device xc6vlx240t successfully.

----------------------------------------------------------------------

'1': : Manufacturer's ID = Xilinx xccace, Version : 0

INFO:iMPACT:1777 -

Reading C:/Xilinx/13.2/ISE_DS/ISE/acecf/data/xccace.bsd...

INFO:iMPACT:501 - '1': Added Device xccace successfully.

----------------------------------------------------------------------

done.

PROGRESS_END - End Operation.

Elapsed time = 1 sec.

// *** BATCH CMD : identifyMPM

+++++++++

B/r,

Russ

DominicB · ‎11-18-2011

Russ,

Thanks for the log. This helped solve the problem. The PC also had a Digilent JTAG-HS cable connected. Impact was picking this up rather that the bridge chip on the ML605. Once the Digilent JTAG-HS cable was removed, up popped the ML605 JTAG chain.

Thanks for this.

Dominic

Virtex-6 DSP Development Kit

ML605 JTAG problem

Re: ML605 JTAG problem

Re: ML605 JTAG problem