devices cannot be found with digilent utilities

perdue · June 19, 2020

After installation runtime, no devices can be found.

system:
centos-release-7-5.1804.el7.centos.x86_64
uname -r
3.10.0-1062.4.1.el7.x86_64

runtime/utilities:
digilent.adept.runtime_2.20.1-x86_64
ftdi.drivers_1.4.8-x86_64
digilent.adept.utilities_2.3.2-x86_64

Error Messages:
dadutil enum
unable to receive message
No devices found

export ADEPT_RT_LOGFILE=adept_err.log
ADEPT_RT_LOGDETAIL=5 djtgcfg enum && cat adept_err.log
System Time     Process     Thread        ERC     ERC String                  Message
3352196176      3852        4160378752    3080    ercInternalError            FTDIC::FEnumAndUpdateCache call to ListDevices failed
3352196183      3852        4160378752    3080    ercInternalError            FTDIC::FEnum FEnumAndUpdateCache() failed

dmsg
[    1.626436] usb 3-2: New USB device found, idVendor=0403, idProduct=6014, bcdDevice= 9.00
[    1.626441] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.626444] usb 3-2: Product: Digilent USB Device
[    1.626447] usb 3-2: Manufacturer: Digilent
[    1.626450] usb 3-2: SerialNumber: 210308A1D31D

Is that an installation problem ?

JColvin · June 19, 2020

Hi @perdue,

What device are you attempting to detect?

Thanks,
JColvin

perdue · June 29, 2020

Hi JColvin,

we have used a xilinx VCU118 Evaluation Board with Virtex UltraScale+ XCVU9P-L2FLGA2104 Device.
For connection we have checked over usb- cable with adept- tools.

Thanks,
perdue.

JColvin · June 29, 2020

Hi @perdue,

My understanding is that the Adept tools are not configured to detect the on-board Ultrascale+ board as it is not built into the Adept system. You would need to use the Xilinx hardware manager to program and otherwise interact with the VCU118.

Thank you,
JColvin

perdue · July 9, 2020

Hi JColvin,
On bord is:

VCU118 Board User Guide40UG1224 (v1.4) October 17, 2018 www.xilinx.com Chapter 3:Board Component Descriptions
...
Digilent USB JTAG Module [Figure 2-1, callout 8, 9] JTAG configuration is provided through a Digilent onboard USB-to-JTAG configuration logic module (U115) where a host computer accesses the VCU118 board JTAG chain through a type-A (host side) to micro-B (VCU118 board side J106) USB cable.

So i am think, that digilent tools, or tools, that use the digilent runtime should work with this bord.

So my question is, do i need a driver update, or its a general driver problem (See error messages in previous Entrie from 19.Jun.)?

Thanks,
Percy

JColvin · July 9, 2020

Hi @perdue,

Unfortunately no, despite the VCU118 including a Digilent USB JTAG module does not mean the Digilent made Adept tools will detect the board. I confirmed with the engineer who did a lot work on the Adept software that the downstream Ultrascale+ module will not be detected by the Adept software. If you want to detect the VCU118 board through the USB-JTAG module, you will need to use Xilinx tools such as the Vivado Hardware Manager.

Let me know if you have any questions about this.

Thanks,
JColvin

perdue · July 10, 2020

Hi JColvin,

For understanding, we have a own tool, which uses the digilent api (runtime libraries) to connect to programmer.
After that, we use own bitstream to detect the fpga.

But the detect from programmer does not work, so i described in my first forum entry.
I have used dadutil only as a reference to detect the programmer device,
but i see same negative results how with digilent runtime api.

Here was my question, have current digilent driver (- or the installation) problems with linux 7x?

The VCU118 board works without problems with vivado, but vivado do not use the digilent runtime.

So i have now the question, wy should the digilent runtime api not detect the programmer device on VCU118 board ?

Thanks,
Percy

mmueller · July 10, 2020

Hi @JColvin,

I'm a colleague from perdue. Let me explain what we are doing. We have our own tool which perform the JTAG bondary-scan and detect the FPGAs in the chain. Means we understand the FPGAs on the JTAG chain. We just need the ability to send TMS / TDI JTAG commands to the JTAG chain. We support multiple programmer like Flashpro, Byteblaster and of curse the Digilent USB JTAG programmer. To be able to support the Digilent programmer we use the Adept runtime SDK. That was working so far for multiple boards on multiple OS's. However on this board / RHEL7 OS we have now some problems. We try to install the digilent driver multiple times. But the adept 2 runtime API is not able to find the programmer. I assume there is some problem with the driver. But so far we couldn't figure out what the problem is. Do you have some hints on how to debug the problem?

Thanks,

Matthias

malexander · July 14, 2020

@perdue

How did you install the software? Was it through the rpm packages or did you perform a manual installation using the tar.gz archives?

Can you try running "sudo dadutil enum" to see if the results are any different?

Thanks,
Michael

perdue · July 20, 2020

Hi Michael,

Installation is done with gz archives.

The result with sudo is same without:

sudo dadutil enum
unable to receive message
No devices found

malexander · July 23, 2020

@perdue

Can you please do the following:

1. execute "/sbin/ldconfig -p | grep ftd2xx" and paste the output
2. execute "cat /etc/udev/rules.d/52-digilent-usb.rules" and paste the output
3. execute "cat /etc/ld.so.conf.d/digilent-adept-libraries.conf" and paste the output

Do you have any other system that you can attach the VCU118 USB interface to see if the issue is limited to your Centos 7.5 installation?

Thanks,
Michael

perdue · July 24, 2020

1. -------------------------------------------------------------------------------------------------------------------------------------------------------------------

libdftd2xx.so.1 (libc6,x86-64) => /lib64/libdftd2xx.so.1
libdftd2xx.so (libc6,x86-64) => /lib64/libdftd2xx.so

2. -------------------------------------------------------------------------------------------------------------------------------------------------------------------

###########################################################################
# #

# 52-digilent-usb.rules -- UDEV rules for Digilent USB Devices #

# #

###########################################################################

# Author: MTA #

###########################################################################

# File Description: #

# #

# This file contains the rules used by UDEV when creating entries for #

# Digilent USB devices. In order for Digilent's shared libraries and #

# applications to access these devices without root privalages it is #

# necessary for UDEV to create entries for which all users have read #

# and write permission. #

# #

# Usage: #

# #

# Copy this file to "/etc/udev/rules.d/" and execute #

# "/sbin/udevcontrol reload_rules" as root. This only needs to be done #

# immediately after installation. Each time you reboot your system the #

# rules are automatically loaded by UDEV. #

# #

###########################################################################

# Revision History: #

# #

# 04/15/2010(MTA): created #

# 02/28/2011(MTA): modified to support FTDI based devices #

# 07/10/2012(MTA): modified to work with UDEV versions 098 or newer #

# 04/19/2013(MTA): modified mode assignment to use ":=" insetead of "=" #

# so that our permission settings can't be overwritten by other #

# rules files #

# 07/28/2014(MTA): changed default application path #

# #

###########################################################################

# Create "/dev" entries for Digilent device's with read and write

# permission granted to all users.

ATTR{idVendor}=="1443", MODE:="666"

ACTION=="add", ATTR{idVendor}=="0403", ATTR{manufacturer}=="Digilent", MODE:="666", RUN+="/usr/sbin/dftdrvdtch %s{busnum} %s{devnum}"

# The following rules (if present) cause UDEV to ignore all UEVENTS for

# which the subsystem is "usb_endpoint" and the action is "add" or

# "remove". These rules are necessary to work around what appears to be a

# bug in the Kernel used by Red Hat Enterprise Linux 5/CentOS 5. The Kernel

# sends UEVENTS to remove and then add entries for the endpoints of a USB

# device in "/dev" each time a process releases an interface. This occurs

# each time a data transaction occurs. When an FPGA is configured or flash

# device is written a large number of transactions take place. If the

# following lines are commented out then UDEV will be overloaded for a long

# period of time while it tries to process the massive number of UEVENTS it

# receives from the kernel. Please note that this work around only applies

# to systems running RHEL5 or CentOS 5 and as a result the rules will only

# be present on those systems.

3. -------------------------------------------------------------------------------------------------------------------------------------------------------------------

###########################################################################

# #

# digilent-adept-libraries.conf -- Adept Dynamic Loader Configuration #

# #

###########################################################################

# Author: MTA #

###########################################################################

# File Description: #

# #

# This file contains the path of the directory that contains the #

# shared libraries that make up Digilent's Adept Runtime on Unix #

# systems. The dynamic loader uses this configuration file to locate #

# Digilent's shared libraries. #

# #

# Usage: #

# #

# Copy this file to "/etc/ld.so.conf.d" and execute "ldconfig" as root. #

# This only needs to be done immediately after installation. The #

# configuration file is automatically read each time you reboot. #

# #

###########################################################################

# Revision History: #

# #

# 04/16/2010(MTA): created #

# #

###########################################################################

/usr/lib/digilent/adept # Path to 32-bit runtime libraries.

/usr/lib64/digilent/adept # Path to 64-bit runtime libraries.

Centos: ------------------------------------------------------------------------------------------------------------------------------------------------------------------

For moment we have this new driver set only used on Centos 7.5.

malexander · July 24, 2020

@perdue

Based on the output it doesn't look like you have libftd2xx.so installed, which is the full FTDI driver. The libdftd2xx.so library is only a partial implementation that we use for enumeration purposes to work around a bug in FTDI's driver. It should look something like this if properly installed:

    libftd2xx.so (libc6,x86-64) => /usr/lib64/digilent/adept/libftd2xx.so
   libdftd2xx.so.1 (libc6,x86-64) => /usr/lib64/digilent/adept/libdftd2xx.so.1
   libdftd2xx.so (libc6,x86-64) => /usr/lib64/digilent/adept/libdftd2xx.so

Did you run the install script for the FTDI driver? Btw we normally recommend using one the rpm or debian package for installation and not the tar.gz. We only provide the tar.gz for platforms that use package managers that aren't compatible with rpm or debian package files.

Thanks,
Michael

perdue · July 29, 2020

After (re-) installation it works now !!

Very many thanks,

Percy

devices cannot be found with digilent utilities

Question

Link to comment

Share on other sites

13 answers to this question

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Archived