1. Home
  2. Field-Programmable Gate Arrays
  3. Xilinx USB Platform Cable not working anymore

Xilinx USB Platform Cable not working anymore

Dear,

I received last week a Xilinx USB Platform Cable. Using ISE 7.1.04i and EDK 7.1.2 under Fedora core 2 with kernel

2.6.6-1.435.2.3smp, the precompiled driver is not suitable. I successfully made the cable working by using the Jungo windrvr6 driver. I successfully run impact and programmed more than 10 fpga and PROM.

Then i tried to use XMD (we bought the cable for PPC405 debugging purpose) and the application apply a firmware update to the cable. Since nothing working, neither impact or XMD. When i try to detect JTAG chain in Impact, it give me a lot of "unknown" devices.

This is my impact log :

************************************ CABLE DETECTION ************************************

// *** BATCH CMD : setPreference -pref UserLevel:NOVICE // *** BATCH CMD : setPreference -pref MessageLevel:DETAILED // *** BATCH CMD : setPreference -pref ConcurrentMode:FALSE // *** BATCH CMD : setPreference -pref UseHighz:FALSE // *** BATCH CMD : setPreference -pref ConfigOnFailure:STOP // *** BATCH CMD : setPreference -pref StartupCLock:AUTO_CORRECTION // *** BATCH CMD : setPreference -pref AutoSignature:FALSE // *** BATCH CMD : setPreference -pref KeepSVF:FALSE // *** BATCH CMD : setPreference -pref svfUseTime:FALSE // *** BATCH CMD : setPreference -pref UserLevel:NOVICE // *** BATCH CMD : setPreference -pref MessageLevel:DETAILED // *** BATCH CMD : setPreference -pref ConcurrentMode:FALSE // *** BATCH CMD : setPreference -pref UseHighz:FALSE // *** BATCH CMD : setPreference -pref ConfigOnFailure:STOP // *** BATCH CMD : setPreference -pref StartupCLock:AUTO_CORRECTION // *** BATCH CMD : setPreference -pref AutoSignature:FALSE // *** BATCH CMD : setPreference -pref KeepSVF:FALSE // *** BATCH CMD : setPreference -pref svfUseTime:FALSE // *** BATCH CMD : setMode -bs GUI --- Auto connect to cable... // *** BATCH CMD : setCable -port auto AutoDetecting cable. Please wait. CB_PROGRESS_START - Starting Operation. Connecting to cable (Parallel Port - parport0). WARNING:iMPACT:2377 - Module parport_pc is not loaded. Please reinstall the cable drivers. See Answer Record 18612. Cable connection failed. Connecting to cable (Parallel Port - parport1). WARNING:iMPACT:2377 - Module parport_pc is not loaded. Please reinstall the cable drivers. See Answer Record 18612. Cable connection failed. Connecting to cable (Parallel Port - parport2). WARNING:iMPACT:2377 - Module parport_pc is not loaded. Please reinstall the cable drivers. See Answer Record 18612. Cable connection failed. Connecting to cable (Parallel Port - parport3). WARNING:iMPACT:2377 - Module parport_pc is not loaded. Please reinstall the cable drivers. See Answer Record 18612. Cable connection failed. Connecting to cable (Usb Port - USB21). Checking cable driver. File version of /local/xilinx/bin/lin/xusbdfwu.hex = 1018(dec), 03FA. File version of /etc/hotplug/usb/xusbdfwu.fw/xusbdfwu.hex = 1018(dec), 03FA. Max current requested during enumeration is 150 mA. Cable Type = 3, Revision = 0. Setting cable speed to 6 MHz. Cable connection established. Firmware version = 1018. CPLD file version = 0006h. CPLD version = 1648h. CB_PROGRESS_END - End Operation. Elapsed time = 7 sec.

*********************************************** JTAG IDENTIFICATION ***********************************************

// *** BATCH CMD : Identify PROGRESS_START - Starting Operation. Identifying chain contents ....read count != nBytes, rc = 20000015. read failed 20000015. '1': : Manufacturer's ID =Unknown INFO:iMPACT:501 - '1': Added Device UNKNOWN successfully.

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

---------------------------------------------------------------------- write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. '2': : Manufacturer's ID =Unknown INFO:iMPACT:501 - '1': Added Device UNKNOWN successfully.

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

---------------------------------------------------------------------- write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. '3': : Manufacturer's ID =Unknown INFO:iMPACT:501 - '1': Added Device UNKNOWN successfully.

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

---------------------------------------------------------------------- write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. INFO:iMPACT:1588 - '4':The part does not appear to be Xilinx Part. '4': : Manufacturer's ID =Unknown , Version : 14 INFO:iMPACT:501 - '1': Added Device UNKNOWN successfully.

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

---------------------------------------------------------------------- GUI --- ************* Process Interrupted by User ************* Process Interrupted by User----------------------------------------------------------------------

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

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

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

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

---------------------------------------------------------------------- write cmdbuffer failed 20000015. Validating chain... write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. Boundary-scan chain validated successfully. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015. write cmdbuffer failed 20000015.

I have tried to force CPLD update several times but i allways get the same working.

Can someone help please.

I there a possibilty to reprogram the CPLD with the default firmware ?

Best regards,

Gilles

Reply to
Gilles GEORGES
Loading thread data ...

"Gilles GEORGES" schrieb im Newsbeitrag news:dpteh3$9hk$ snipped-for-privacy@amma.irisa.fr...

from 2 of cables here, one of them started to fail after firmware update, but multiply firmware updates did not help, etc.. to my very very very big surprise the reason for the failure was the Fairchild buffer chip on TMS being dead. so I ended up soldering a short circuit over it, then it worked again.

you can test if your cable is electrically intact with the impact debug chain

first make short TDO-TDI and check that the readback is echoed, then measure the TMS and TCK with some multimeter, and force them from impact

hum,. if you CPLD is really bad bad then you may get communication error even before that

that is weird on WinXP the file version and CPLD version are the same as displayed

I dont think xilinx ever tried CPLD update on Linux, so get and Windows box and try again yes I know Linuxfans dont like this type of advice, but some things are the way they are, and FPGA tools come with Windows support in first line, and all Linux support is a bit behind, this may get better (for linuxfans) but currently there are less problems on non-linux hosts

take the old firmware file from old Xilinx install replace it and force update that should write the old version

6.3 has CPLD version 0004 included, all never have CPLD ver 0006, if you dont have it I can send

optionally the CPLD can be reprogrammed by another cable as the PCB inside the platform cable has an unfitted Cable IV header so you can connect another cable to it and program the CPLD I have a JEDEC readback of CPLD ver 0006 which I can send, if you need, but it is only helping if you have another working cable and are willing to open the platform cable casing

--
Antti Lukats
http://www.xilant.com
Reply to
Antti Lukats

"Antti Lukats" schrieb im Newsbeitrag news:dptig7$jk$01$ snipped-for-privacy@news.t-online.com...

[snip]

sorry I meant displayed should be

CPLD file version = 0006h. CPLD version = 0006h.

antti

Reply to
Antti Lukats

Dear Antti,

I just tried the cable with same board on a Win XP computer and it works. I previously downgrade to cpld firmware V4 (taken in a ISE 6.3 linux install) => not working under linux but working under windows. Then i upgrade to version 6 and still working under windows.

Going back to my Linux workstation nothing works.

There is a strange thing with Impact, the "CPLD version" differs with the "CPLD file version" while the two match on Windows.

Connecting to cable (Usb Port - USB22). Checking cable driver. File version of /local/xilinx/bin/lin/xusbdfwu.hex = 1018(dec), 03FA. File version of /etc/hotplug/usb/xusbdfwu.fw/xusbdfwu.hex = 1018(dec), 03FA. Max current requested during enumeration is 150 mA. Cable Type = 3, Revision = 0. Setting cable speed to 6 MHz. Cable connection established. Firmware version = 1018. CPLD file version = 0006h. CPLD version = 0021h.

Any idea.

Gilles

Reply to
Gilles GEORGES

We have seen some strange things happening from time to time with these cables. We have seen them appear to stop working only to recover the next day and start working again.

John Adair Enterpoint Ltd. - Home of Raggedstone1. The Low Cost Spartan-3 Development Board.

formatting link

Reply to
John Adair

tell Xilinx to hire professianals to write and test their software

seriously Linux support just is behind, so all Linux users just have to accept WAY more problems as WinXP users.

also different departments of Xilinx have their own JTAG drivers and low level access API so when one departments gets something working then others do not, then comes new Cable or firmware/PLD update and the game begins all over, something will brake each time

either impact or XMD server or Chipscope will fail

not really fun

Antti

Reply to
Antti Lukats

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.