UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Contributor
Contributor
10,906 Views
Registered: ‎10-26-2011

Platform Cable USB II DS10 detects devices in chain but fail when programming

Jump to solution

Hi all,

 

I'm using a JTAG chain composed by 3 devices:

 

  • An xc3s1400a - an Spartan 3 1400A FPGA. The part number is XC3S1400A-4FTG256I.
  • An xcf08p - a Platform Flash in-system programmable configuration PROM memory for the Spartan 3.
  • An xc95144xl - an XC95144XL CPLD. The part number is XC95144XL-10TQG100I.

For programming the PROM and the CPLD I'm using Xilinx ISE 13.4 and the iMPACT version is 0.87xd (nt64).

 

In order to program the PROM and the CPLD I have several cables Platform Cable USB II DS10 with the following serial numbers: 11755, 20262, 40040, 80377, 87037 and 88116. The first two programming cables were bought 5 years ago, the next two ones where bought several years ago and the last two were bought at the end of last year 2015.

 

When I try to program either the PROM or the CPLD using the Platform Cable USB II DS10 with serial numbers 11755 and 20262 all is working perfectly. But, when I use the Platform Cable USB II DS10 with serial numbers 40040, 80377, 87037 and 88116 the programming process fails asserting the following error messages:

 

  • "ERROR:iMPACT:2598 - Operation time out."
  • "Failed at address, 0'2': Verification Terminated"

I'm not able to load MCS file data in the PROM and I'm not be able to load the JED file data in the CPLD.

 

In a successful programming process the log from iMPACT is the following:

 

"Cable is not connected.
GUI --- Auto connect to cable...
// *** BATCH CMD : setCable -port auto
AutoDetecting cable. Please wait.
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
Driver file xusb_xp2.sys found.
Driver version: src=2301, dest=2301.
Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 x86_64 64bit SYS 14:14:44, version = 1021.
Cable PID = 0008.
Max current requested during enumeration is 300 mA.
Type = 0x0005.
write (count, cmdBuffer, dataBuffer) failed C0000004.
Cable Type = 3, Revision = 0.
Setting cable speed to 6 MHz.
Cable connection established.
Firmware version = 2301.
File version of C:/Xilinx/13.4/ISE_DS/ISE/data/xusb_xp2.hex = 2401.
Firmware hex file version = 2401.
Downloading C:/Xilinx/13.4/ISE_DS/ISE/data/xusb_xp2.hex.
Downloaded firmware version = 2401.
PLD file version = 200Dh.
PLD version = 200Dh.
PROGRESS_END - End Operation.
Elapsed time = 1 sec.
Type = 0x0005.
ESN option: 00001319D23C01.
INFO:iMPACT - Current time: 08/03/2016 15:21:21
// *** BATCH CMD : Program -p 2 -e -v -defaultVersion 0
PROGRESS_START - Starting Operation.
'2': Putting device in ISP mode...done.
Maximum TCK operating frequency for this device chain: 10000000.
Validating chain...
Boundary-scan chain validated successfully.
'2': Erasing device...
'2': Erasure completed successfully.
'2': Putting device in ISP mode...done.
'2': Putting device in ISP mode...done.
done.
'2': Putting device in ISP mode...done.
'2': Putting device in ISP mode...done.
'2': Putting device in ISP mode...done.
'2': Putting device in ISP mode...done.
'2': Programming revision selection to 0.
done.
'2': Putting device in ISP mode...done.
done.
done.
'2': Putting device in ISP mode...done.
'2': Putting device in ISP mode...done.
'2': Verifying device...
done.
'2': Verification completed.
'2': Putting device in ISP mode...done.
done.
'2': Putting device in ISP mode...done.
'2': Programming completed successfully.
'2': Programming completed successfully.
PROGRESS_END - End Operation.
Elapsed time = 31 sec."

 

In a failed programming process the log from iMPACT is the following:

 

"GUI --- Auto connect to cable...
// *** BATCH CMD : setCable -port auto
AutoDetecting cable. Please wait.
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
Driver file xusb_xp2.sys found.
Driver version: src=2301, dest=2301.
Driver windrvr6.sys version = 10.2.1.0. WinDriver v10.21 Jungo (c) 1997 - 2010 Build Date: Aug 31 2010 x86_64 64bit SYS 14:14:44, version = 1021.
Cable PID = 0008.
Max current requested during enumeration is 300 mA.
Type = 0x0005.
write (count, cmdBuffer, dataBuffer) failed C0000004.
Cable Type = 3, Revision = 0.
Setting cable speed to 6 MHz.
Cable connection established.
Firmware version = 2301.
File version of C:/Xilinx/13.4/ISE_DS/ISE/data/xusb_xp2.hex = 2401.
Firmware hex file version = 2401.
Downloading C:/Xilinx/13.4/ISE_DS/ISE/data/xusb_xp2.hex.
Downloaded firmware version = 2401.
PLD file version = 200Dh.
PLD version = 200Dh.
PROGRESS_END - End Operation.
Elapsed time = 0 sec.
Type = 0x0005.
ESN option: 0000153A76E101.
INFO:iMPACT - Current time: 08/03/2016 15:24:18
// *** BATCH CMD : Program -p 2 -e -v -defaultVersion 0
PROGRESS_START - Starting Operation.
'2': Putting device in ISP mode...done.
Maximum TCK operating frequency for this device chain: 10000000.
Validating chain...
Boundary-scan chain validated successfully.
'2': Erasing device...
'2': Erasure completed successfully.
'2': Putting device in ISP mode...done.
'2': Putting device in ISP mode...done.
done.
ERROR:iMPACT:2598 - Operation time out.
'2': Putting device in ISP mode...done.
'2': Putting device in ISP mode...done.
'2': Putting device in ISP mode...done.
'2': Putting device in ISP mode...done.
'2': Programming revision selection to 0.
done.
'2': Putting device in ISP mode...done.
done.
done.
'2': Putting device in ISP mode...done.
'2': Putting device in ISP mode...done.
'2': Verifying device...
Failed at address, 0'2': Verification Terminated
'2': Putting device in ISP mode...done.
done.
'2': Putting device in ISP mode...done.
'2': Programming completed successfully.
'2': Programming completed successfully.
PROGRESS_END - End Operation.
Elapsed time = 9 sec."

 

I have tried with different PCs: laptop and desktop. I have also tried with different OS version: Windows XP and Windows 7. The result was the showed above, I have not been able to program neither the PROM or the CPLD.

 

Has anyone experienced something similar? Is there an issue with the newest manufactured Platform Cable USB II DS10 and the old PROM and CPLD devices? Does anyone fixed something similar?

 

Has anything change in the Platform Cable USB II DS10 during the last few years? - Hardware or Firmware. In this case, is downgrade of the Platform Cable USB II DS10 a possible solution?

 

Thanks in advance.

 

Regards!

 

Pedro.

 

0 Kudos
1 Solution

Accepted Solutions
Contributor
Contributor
20,231 Views
Registered: ‎10-26-2011

Re: Platform Cable USB II DS10 detects devices in chain but fail when programming

Jump to solution

Hi all,

 

We have gotten a home-made solution by cutting the ribbon cable. The original ribbon cable lenght is equal to 15.5 cm approximately. Using this ribbon cable lenght of 5 cm we are able to program all the devices of the long chain: xc3s1400a, xcf08p and xc95144xl. In this case, we have not noticed any programming error such as the time out error.

 

Thanks for your support.

 

Regards,

 

Pedro.

0 Kudos
5 Replies
Contributor
Contributor
10,796 Views
Registered: ‎10-26-2011

Re: Platform Cable USB II DS10 detects devices in chain but fail when programming

Jump to solution

I made an additional try with the last version of ISE, version 14.7, which uses the iMPACT version P.20131013. The result was the same.

0 Kudos
Xilinx Employee
Xilinx Employee
10,704 Views
Registered: ‎07-21-2014

Re: Platform Cable USB II DS10 detects devices in chain but fail when programming

Jump to solution
Hi,

Do you see issue if you configure spartan-3 device with bit file (using jtag interface) using any of these plotform usb?

-Shreyas
----------------------------------------------------------------------------------------------
Try to search answer for your issue in forums or xilinx user guides before you post a new thread.

Kindly note- Please mark the Answer as "Accept as solution" if information provided solves your query.
Give Kudos (star provided in right) to a post which you think is helpful and reply oriented.
----------------------------------------------------------------------------------------------
0 Kudos
Contributor
Contributor
10,664 Views
Registered: ‎10-26-2011

Re: Platform Cable USB II DS10 detects devices in chain but fail when programming

Jump to solution

Hi,

 

Thanks for your proposal. I have tried it but the Spartan-3 is programmed correctly.

 

Regards!

 

Pedro.

0 Kudos
Contributor
Contributor
10,569 Views
Registered: ‎10-26-2011

Re: Platform Cable USB II DS10 detects devices in chain but fail when programming

Jump to solution

Hi all again,

 

Does anyone know any JTAG chain maximum lenght limit from the Platform Cable conector?

 

Does anyone know any critical signal integrity values for JTAG programming lines (TDO, TDI, TCK oand/or TMS) like voltage level or slew rate?

 

Thanks in advance!

 

Regards,

 

Pedro.

0 Kudos
Contributor
Contributor
20,232 Views
Registered: ‎10-26-2011

Re: Platform Cable USB II DS10 detects devices in chain but fail when programming

Jump to solution

Hi all,

 

We have gotten a home-made solution by cutting the ribbon cable. The original ribbon cable lenght is equal to 15.5 cm approximately. Using this ribbon cable lenght of 5 cm we are able to program all the devices of the long chain: xc3s1400a, xcf08p and xc95144xl. In this case, we have not noticed any programming error such as the time out error.

 

Thanks for your support.

 

Regards,

 

Pedro.

0 Kudos