Xilinx Multilink Connection not working

Hi

I have a Xilinx Multilink cable that I would like to use to communicate with a Xilinx VirtexII that is hosted on a PCI Mezzanine board. I connected the PCI Mezzanine board with the cable following the guidelines in the User Guide for Xilinx Impact. In other words, I connected the GND, VCC, TDO, TDI, TCK and TMS. There is a green led on the Multilink cable, which is not flashing although power supply should be provided by the PCI card. The PCI card itself is working, so I dont know if I have to switch into a special kind of mode so that the JTAG interface is enabled? Does anyone have any experience with that? Or is the Multilink cable probably broken?

Thanks for any assistance! Philipp

Reply to
Philipp
Loading thread data ...

Alright, at least the multilinx cable is working, so the LED flashes. I connected the GND, VCC, TDO, TDI, TCK and TMS. Still I cant get a connection over the serial port which is quite weird. I used automatic detection but I get the following error blog from Impact. Is there an issue with the drivers? In addition, I use two DB25 adapters in order to connect the cable to the board. Shouldnt be an issue either, is that correct?

iMPACT Version: H.38 iMPACT log file started on 2007/11/27 17:22:31 // *** 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 GUI --- Boundary-Scan Mode selected // *** 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 (USB Port). Cable connection failed. Connecting to cable (Parallel Port - LPT1). Checking cable driver. Driver windrvr6.sys version = 8.1.1.0. LPT base address = 0378h. ECP base address = 0778h. Cable connection failed. Connecting to cable (Parallel Port - LPT2). Checking cable driver. Driver windrvr6.sys version = 8.1.1.0.Cable connection failed. Connecting to cable (Parallel Port - LPT3). Checking cable driver. Driver windrvr6.sys version = 8.1.1.0.Cable connection failed. Connecting to cable (Parallel Port - LPT4). Checking cable driver. Driver windrvr6.sys version = 8.1.1.0.Cable connection failed. Connecting to cable (Usb Port - USB21). Checking cable driver. File C:\WINDOWS\system32\drivers\xusbdfwu.sys not found. Driver file not found. Inf file version = 0. Driver xusbdfwu.sys version: 1017 (2001). Driver windrvr6.sys version = 8.1.1.0.Cable connection failed. Connecting to cable (COM1 Port). Cable connection failed. Cable connection failed. Cable connection failed. Cable connection failed. CB_PROGRESS_END - End Operation. Elapsed time = 16 sec. Cable autodetection failed.

***** Closing iMPACT program. *****
Reply to
Philipp

Philipp, I have some suggestions:

1- Look around for a patch of multilinx on Xilinx website. Although it solved my problem but many of the usb devices (including my mouse) stopped functioning after applying this patch.

2- Try changing the PC-connectivity of multilinx (from USB to serial).

Hope this helps.

Regards /MH

Reply to
mh

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.