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: 
Visitor pbagsdab
Visitor
13,478 Views
Registered: ‎04-06-2013

How to connect Kintex 7 KC705 via Digilent USB port to impact?

Jump to solution

Hello,

now it's day two to try to connect my evaluation board to my linux debian wheezy 64 bit amd workstation with an connection with impact.

I've installed ISE 14.5. As described in iMPACT User Guide I try to connect the board instead with the delivered usb cable to the Digilent usb port and use impact to identify the device.
But I get only messages that the cable is not found.

If I connect the KC705 to my box I get from dmesg following messages:

[439809.148272] usb 1-2.3: new high-speed USB device number 38 using ehci_hcd
[439809.262006] usb 1-2.3: New USB device found, idVendor=0403, idProduct=6010
[439809.262020] usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[439809.262030] usb 1-2.3: Product: Digilent Adept USB Device
[439809.262038] usb 1-2.3: Manufacturer: Digilent
[439809.262044] usb 1-2.3: SerialNumber: 210203339781
[439809.310951] USB Serial support registered for FTDI USB Serial Device
[439809.311388] ftdi_sio 1-2.3:1.0: FTDI USB Serial Device converter detected
[439809.311467] usb 1-2.3: Detected FT2232H
[439809.311474] usb 1-2.3: Number of endpoints 2
[439809.311482] usb 1-2.3: Endpoint 1 MaxPacketSize 512
[439809.311489] usb 1-2.3: Endpoint 2 MaxPacketSize 512
[439809.311496] usb 1-2.3: Setting MaxPacketSize 512
[439809.311961] usb 1-2.3: FTDI USB Serial Device converter now attached to ttyUSB0
[439809.311995] ftdi_sio 1-2.3:1.1: FTDI USB Serial Device converter detected
[439809.312105] usb 1-2.3: Detected FT2232H
[439809.312115] usb 1-2.3: Number of endpoints 2
[439809.312125] usb 1-2.3: Endpoint 1 MaxPacketSize 512
[439809.312135] usb 1-2.3: Endpoint 2 MaxPacketSize 512
[439809.312145] usb 1-2.3: Setting MaxPacketSize 512
[439809.312626] usb 1-2.3: FTDI USB Serial Device converter now attached to ttyUSB1
[439809.312680] usbcore: registered new interface driver ftdi_sio
[439809.312688] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver



lsusb shows that here which looks ok:
pierre@nihilnihil:~/test/usb-driver$ lsusb -s 1:38
Bus 001 Device 038: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC

Both are found also here and access by dialout group is granted:
pierre@nihilnihil:~/test/usb-driver$ ls -l /dev/ttyUSB*
crw-rw---T 1 root dialout 188, 0 Mai 14 00:51 /dev/ttyUSB0
crw-rw---T 1 root dialout 188, 1 Mai 14 00:51 /dev/ttyUSB1

I used strace on impact to find an hint how the ports are could used. First I checked the loading of libusb:
...
32751 open("/usr/lib/x86_64-linux-gnu/libusb.so", O_RDONLY|O_CLOEXEC)                                                                        = 12
...
Looks first ok, but then I checked in which package the lib is found:
oot@nihilnihil:~# dpkg -l libusb-*dev
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
         Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name                          Version             Architektur         Beschreibung
+++-=============================-===================-===================-===============================================================
ii  libusb-1.0-0-dev              2:1.0.11-1          amd64               userspace USB programming library development files
ii  libusb-dev                    2:0.1.12-20+nmu1    amd64               userspace USB programming library development files

Checking for libs in 1.0.0 package which looks like have a different library name:
root@nihilnihil:~# dpkg -L libusb-1.0-0-dev |grep -e 'libusb.*so$'
/usr/lib/x86_64-linux-gnu/libusb-1.0.so

So removed the libusb-dev package, because I understood that 1.0 is needed and not 0.1.
But there still used to search for libusb.so instead libusb-1.0-0-dev :-(

So I manually linked them by symbolic link:
root@nihilnihil:~# ln -s /usr/lib/x86_64-linux-gnu/libusb-1.0.so /usr/lib/x86_64-linux-gnu/libusb.so

The linked lib is found:

2589  open("/usr/lib/x86_64-linux-gnu/libusb.so", O_RDONLY|O_CLOEXEC)                                                                        = 11

But the errors still occurs:
GUI --- Auto connect to cable...
INFO:iMPACT - Connecting to TCF agent...
AutoDetecting cable. Please wait.
*** WARNING ***: When port is set to auto detect mode, cable speed is set to default 6 MHz regardless of explicit arguments supplied for setting the baud rates
PROGRESS_START - Starting Operation.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
 Linux release = 3.2.0-4-amd64.
WARNING:iMPACT -  Module windrvr6 is not loaded. Please reinstall the cable drivers. See Answer Record 22648.
Cable connection failed.
Connecting to cable (Parallel Port - parport0).
 Linux release = 3.2.0-4-amd64.
WARNING:iMPACT -  Module windrvr6 is not loaded. Please reinstall the cable drivers. See Answer Record 22648.
Cable connection failed.
Connecting to cable (Parallel Port - parport1).
 Linux release = 3.2.0-4-amd64.
WARNING:iMPACT -  Module windrvr6 is not loaded. Please reinstall the cable drivers. See Answer Record 22648.
Cable connection failed.
Connecting to cable (Parallel Port - parport2).
 Linux release = 3.2.0-4-amd64.
WARNING:iMPACT -  Module windrvr6 is not loaded. Please reinstall the cable drivers. See Answer Record 22648.
Cable connection failed.
Connecting to cable (Parallel Port - parport3).
 Linux release = 3.2.0-4-amd64.
WARNING:iMPACT -  Module windrvr6 is not loaded. Please reinstall the cable drivers. See Answer Record 22648.
Cable connection failed.
PROGRESS_END - End Operation.
Elapsed time =      0 sec.
Cable autodetection failed.
WARNING:iMPACT:923 - Can not find cable, check cable setup !

I understood that windrv6 is not needed for usb Digilent connection, so I had to gave up installing them. The compilation messages shows me incompatible kernel release after I'd manually fixed a problem with missing not found files by linking them to the source dir which the installation procedure searched for.

checking for linux kernel source... found at /lib/modules/3.2.0-4-amd64/build
checking for lib directory... ln -sf $(ROOT_DIR)/lib/$(SHARED_OBJECT)_32.so /usr/lib/$(SHARED_OBJECT).so; ln -sf $(ROOT_DIR)/lib/$(SHARED_OBJECT).so /usr/lib64/$(SHARED_OBJECT).so
checking which directories to include... -I/lib/modules/3.2.0-4-amd64/source/include
checking linux kernel version... 3.2.0-4-amd64
checking for modules installation directory... /lib/modules/3.2.0-4-amd64/kernel/drivers/misc
checking for gcc kernel version... 4
checking output directory... LINUX.3.2.0-4-amd64.x86_64
checking target... LINUX.3.2.0-4-amd64.x86_64/windrvr6.o
checking for right linked object... windrvr_gcc_v3.a
configure.wd: creating ./config.status
config.status: creating makefile.wd
make -f makefile.wd clean
make[1]: Entering directory `/home/pierre/opt/Xilinx/14.5/LabTools/common/bin/lin64/install_script/install_drivers/linux_drivers/windriver64/windrvr'
rm -rf core .*.cmd Module.symvers modules.order .tmp_versions LINUX.3.2.0-4-amd64.x86_64/*
make[1]: Leaving directory `/home/pierre/opt/Xilinx/14.5/LabTools/common/bin/lin64/install_script/install_drivers/linux_drivers/windriver64/windrvr'
make -f makefile.wd
make[1]: Entering directory `/home/pierre/opt/Xilinx/14.5/LabTools/common/bin/lin64/install_script/install_drivers/linux_drivers/windriver64/windrvr'
cc -c -O2 -Wall -D__KERNEL__ -DMODULE  -Wstrict-prototypes -Wno-trigraphs -fno-common           -fomit-frame-pointer -pipe -mno-red-zone -mcmodel=kernel -fno-reorder-blocks                -Wno-sign-compare -fno-strict-aliasing -DLINUX -DWINDRIVER_KERNEL  -I/lib/modules/3.2.0-4-amd64/source/include -I/home/pierre/opt/Xilinx/14.5/LabTools/common/bin/lin64/install_script/install_drivers/linux_drivers/windriver64/include -I/home/pierre/opt/Xilinx/14.5/LabTools/common/bin/lin64/install_script/install_drivers/linux_drivers/windriver64  -c -o LINUX.3.2.0-4-amd64.x86_64/linux_wrappers.o linux_wrappers.c
In file included from linux_wrappers.c:15:0:
linux_common.h:29:4: error: #error "This kernel is too recent: not supported by this file"
linux_common.h:51:2: error: #error "unsupported linux kernel version"
In file included from /lib/modules/3.2.0-4-amd64/source/include/linux/sysfs.h:20:0,
                 from /lib/modules/3.2.0-4-amd64/source/include/linux/kobject.h:21,
                 from /lib/modules/3.2.0-4-amd64/source/include/linux/pci.h:51,
                 from linux_wrappers.c:19:
/lib/modules/3.2.0-4-amd64/source/include/linux/atomic.h:4:24: fatal error: asm/atomic.h: Datei oder Verzeichnis nicht gefunden
compilation terminated.
make[1]: *** [LINUX.3.2.0-4-amd64.x86_64/linux_wrappers.o] Fehler 1
make[1]: Leaving directory `/home/pierre/opt/Xilinx/14.5/LabTools/common/bin/lin64/install_script/install_drivers/linux_drivers/windriver64/windrvr'
make: *** [all] Fehler 2
make -f makefile.wd
make[1]: Entering directory `/home/pierre/opt/Xilinx/14.5/LabTools/common/bin/lin64/install_script/install_drivers/linux_drivers/windriver64/windrvr'
cc -c -O2 -Wall -D__KERNEL__ -DMODULE  -Wstrict-prototypes -Wno-trigraphs -fno-common           -fomit-frame-pointer -pipe -mno-red-zone -mcmodel=kernel -fno-reorder-blocks                -Wno-sign-compare -fno-strict-aliasing -DLINUX -DWINDRIVER_KERNEL  -I/lib/modules/3.2.0-4-amd64/source/include -I/home/pierre/opt/Xilinx/14.5/LabTools/common/bin/lin64/install_script/install_drivers/linux_drivers/windriver64/include -I/home/pierre/opt/Xilinx/14.5/LabTools/common/bin/lin64/install_script/install_drivers/linux_drivers/windriver64  -c -o LINUX.3.2.0-4-amd64.x86_64/linux_wrappers.o linux_wrappers.c
In file included from linux_wrappers.c:15:0:
linux_common.h:29:4: error: #error "This kernel is too recent: not supported by this file"
linux_common.h:51:2: error: #error "unsupported linux kernel version"
In file included from /lib/modules/3.2.0-4-amd64/source/include/linux/sysfs.h:20:0,
                 from /lib/modules/3.2.0-4-amd64/source/include/linux/kobject.h:21,
                 from /lib/modules/3.2.0-4-amd64/source/include/linux/pci.h:51,
                 from linux_wrappers.c:19:
/lib/modules/3.2.0-4-amd64/source/include/linux/atomic.h:4:24: fatal error: asm/atomic.h: Datei oder Verzeichnis nicht gefunden
compilation terminated.
make[1]: *** [LINUX.3.2.0-4-amd64.x86_64/linux_wrappers.o] Fehler 1
make[1]: Leaving directory `/home/pierre/opt/Xilinx/14.5/LabTools/common/bin/lin64/install_script/install_drivers/linux_drivers/windriver64/windrvr'
make: *** [all] Fehler 2
--make windrvr install rc= 2
--install_windrvr6 rc = 2
--Module windrvr6 is not running.
--Module xpc4drvr is not running.
--Note: By default, the file permission of /dev/windrvr6 is enabled for the root user only
  and must be changed to allow access to other users.

--real rc=2

--Driver installation failed.

--Digilent Return code = 0
--Xilinx Return code = 1
--Return code = 1


I allready tried to use usb-driver. As I understood the 64bit lib creation is not the case because I use the 64bit release of ise and tools. The 64 bit generation of the lib was ok and the lib has to been preloaded before I start again impact.
But then at time of checking cable setup I get still the following box, but now not further the other messages:

WARNING:iMPACT:923 - Can not find cable, check cable setup !

Welcome to iMPACT
iMPACT Version: 14.5
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
// *** BATCH CMD : setMode -bs
GUI --- Auto connect to cable...
// *** BATCH CMD : setCable -port auto
INFO:iMPACT - Connecting to TCF agent...
AutoDetecting cable. Please wait.
*** WARNING ***: When port is set to auto detect mode, cable speed is set to default 6 MHz regardless of explicit arguments supplied for setting the baud rates
PROGRESS_START - Starting Operation.
 Using windrvr6 driver.
Connecting to cable (Usb Port - USB21).
Checking cable driver.
File version of /home/pierre/opt/Xilinx/14.5/ISE_DS/ISE/bin/lin64/xusbdfwu.hex = 1030.
File version of /etc/hotplug/usb/xusbdfwu.fw/xusbdfwu.hex = 1030.
 libusb-driver.so version: 2013-05-12 22:23:37.
Cable connection failed.
Connecting to cable (Parallel Port - parport0).
 libusb-driver.so version: 2013-05-12 22:23:37.
 parport0:
 parport1:
 parport2:
 parport3:
 LPT1 Base Address set from env variable = 0.
 LPT base address = 0000h.
 LPT1 Ecp Address set from env variable = 400.
 ECP base address = 0400h.
Cable connection failed.
Connecting to cable (Parallel Port - parport1).
 libusb-driver.so version: 2013-05-12 22:23:37.
 LPT2 Base Address set from env variable = 10.
 LPT base address = 0010h.
 LPT2 Ecp Address set from env variable = 410.
 ECP base address = 0410h.
LPT port is already in use. rc = FFFFFFFFh
Cable connection failed.
Connecting to cable (Parallel Port - parport2).
 libusb-driver.so version: 2013-05-12 22:23:37.
 LPT3 Base Address set from env variable = 20.
 LPT base address = 0020h.
 LPT3 Ecp Address set from env variable = 420.
 ECP base address = 0420h.
LPT port is already in use. rc = FFFFFFFFh
Cable connection failed.
Connecting to cable (Parallel Port - parport3).
 libusb-driver.so version: 2013-05-12 22:23:37.
 LPT4 Base Address set from env variable = 30.
 LPT base address = 0030h.
 LPT4 Ecp Address set from env variable = 430.
 ECP base address = 0430h.
LPT port is already in use. rc = FFFFFFFFh
Cable connection failed.
PROGRESS_END - End Operation.
Elapsed time =      2 sec.
Cable autodetection failed.
WARNING:iMPACT:923 - Can not find cable, check cable setup !

It looks like parport0 is the real on-board parport on my host. But which also the one which should been generated by usb-driver?

I tried to use from cable commnication setup Digilent USB JTAG Cable, but now I get message box at OK:
WARNING:iMPACT - The cable selected is not avaliable, please select a different one.

I allready tried to check with lib32 library of usb-dev, but I have many trouble to compile them alghough I mean I allready installed all relevant parts:

Sorry, but I lost now more and more new ideas to check more options. So my biggest questions are:

Does anybody has run
1. Impact connected to an Digilent USB device best on K705 under Linux?
2. under 64bit Linux
3. under 64bit Linux used with actual 14.x ISE and there impact?
4. under debian 64bit?
5. under debian wheezy 64bit?

and
6. how they are connected the board...


0 Kudos
1 Solution

Accepted Solutions
Visitor pbagsdab
Visitor
22,007 Views
Registered: ‎04-06-2013

Re: How to connect Kintex 7 KC705 via Digilent USB port to impact?

Jump to solution
It was all really simple and stupid, if anybody knows what's missing.

It was hazard to found that under linux the ftdi drivers must installed manually by starting sudo /opt/Xilinx/14.5/ISE_DS/ISE/bin/lin64/digilent/install_digilent.sh .

The only problem at the moment still exists is the incorrect permission settings which I have fixed by adding manually GROUP="dialout", in /etc/udev/rules.d/52-digilent-usb.rules.

Thats looks like hopefully all.
0 Kudos
4 Replies
Visitor pbagsdab
Visitor
22,008 Views
Registered: ‎04-06-2013

Re: How to connect Kintex 7 KC705 via Digilent USB port to impact?

Jump to solution
It was all really simple and stupid, if anybody knows what's missing.

It was hazard to found that under linux the ftdi drivers must installed manually by starting sudo /opt/Xilinx/14.5/ISE_DS/ISE/bin/lin64/digilent/install_digilent.sh .

The only problem at the moment still exists is the incorrect permission settings which I have fixed by adding manually GROUP="dialout", in /etc/udev/rules.d/52-digilent-usb.rules.

Thats looks like hopefully all.
0 Kudos
Visitor pbagsdab
Visitor
13,472 Views
Registered: ‎04-06-2013

Re: How to connect Kintex 7 KC705 via Digilent USB port to impact?

Jump to solution
'at the moment still exists is the incorrect' --> 'not any more exists was the incorrect'
0 Kudos
Visitor kusumiuac
Visitor
12,256 Views
Registered: ‎02-12-2014

Re:ft2232h and xilinx programming tool IMPACT

Jump to solution

I am using ft2232h mini board to program the xilionx fpga thriugh impact, but it always shows " cable not found". MPSSE mode is enable in FT2232h which is essential for JTAG mode. Any suggetion, what else I can try

0 Kudos
Highlighted
Newbie nyd
Newbie
1,802 Views
Registered: ‎05-17-2018

Re: How to connect Kintex 7 KC705 via Digilent USB port to impact?

Jump to solution

Can you please share the Syntax to give permission by adding it into "dailout" group manually. Where should I write GROUP="dailout" in rule file. 

0 Kudos