Jump to content
  • 0

How to install and use djtgcfg?


aeon20

Question

This thread is related to my first thread here:

However, since every problem I encounter is complex, it is hard to keep it all in just one thread, so I'm moving this issue here. I'm trying to debug why my card doesn't show up and to do that I've been recommended to use djtgcfg. However, djtgcfg itself doesn't work!

I have djtgcfg installed:

# djtgcfg -v
Digilent JTAG Config Utility v2.2.1
Copyright (C) 2010 Digilent, Inc.
support@digilentinc.com

With these dependencies:

# ldd /usr/local/bin/djtgcfg
        linux-vdso.so.1 (0x00007ffcb4141000)
        libdabs.so.2 => /usr/lib/x86_64-linux-gnu/libdabs.so.2 (0x00007f8d50c52000)
        libdpcomm.so.2 => /usr/lib/x86_64-linux-gnu/libdpcomm.so.2 (0x00007f8d50806000)
        libdmgr.so.2 => /usr/lib/x86_64-linux-gnu/libdmgr.so.2 (0x00007f8d50603000)
        libdepp.so.2 => /usr/lib/x86_64-linux-gnu/libdepp.so.2 (0x00007f8d50400000)
        libdjtg.so.2 => /usr/lib/x86_64-linux-gnu/libdjtg.so.2 (0x00007f8d501fb000)
        libdpio.so.2 => /usr/lib/x86_64-linux-gnu/libdpio.so.2 (0x00007f8d4fff8000)
        libdspi.so.2 => /usr/lib/x86_64-linux-gnu/libdspi.so.2 (0x00007f8d4fdf5000)
        libdstm.so.2 => /usr/lib/x86_64-linux-gnu/libdstm.so.2 (0x00007f8d4fbf3000)
        libdpcutil.so.2 => /usr/lib/x86_64-linux-gnu/libdpcutil.so.2 (0x00007f8d4f9e8000)
        libjtsc.so.2 => /usr/lib/x86_64-linux-gnu/libjtsc.so.2 (0x00007f8d4f7b5000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f8d4f42c000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f8d4f08e000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f8d4ee76000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f8d4ea85000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f8d4e866000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f8d4e65e000)
        libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 (0x00007f8d4e446000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f8d4e242000)
        libdftd2xx.so.1 => /usr/lib/x86_64-linux-gnu/libdftd2xx.so.1 (0x00007f8d4e03e000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f8d50e73000)
        libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f8d4de20000)

On Ubuntu 18.04, a clean install with no clutter and no weirdness.

However, when I try to run djtgcfg I get this:

# djtgcfg --verbose enum
ERROR: failed to enumerate devices, erc = 3090

I've Googled this problem, but I only find this:

Which isn't helpful at all.

Link to comment
Share on other sites

8 answers to this question

Recommended Posts

Hi @aeon20,

ERC 3090 means that there was an error while initializing DPCOMM. There are a number of reasons why this could happen. Thankfully there is a way to enable an error log. Can you please do the following:

1. Execute "export ADEPT_RT_LOGDETAIL=1"

2. Execute "export ADEPT_RT_LOGFILE=~/adept_erc.log"

3. Re-run your modified version of digi_enum.py and post the output of the log file here.

thank you,

Jon

Link to comment
Share on other sites

1 hour ago, jpeyron said:

Hi @aeon20,

ERC 3090 means that there was an error while initializing DPCOMM. There are a number of reasons why this could happen. Thankfully there is a way to enable an error log. Can you please do the following:

1. Execute "export ADEPT_RT_LOGDETAIL=1"

2. Execute "export ADEPT_RT_LOGFILE=~/adept_erc.log"

3. Re-run your modified version of digi_enum.py and post the output of the log file here.

thank you,

Jon

I managed to resolve this problem by reinstalling my operating system, I'm now using Debian instead.

djtgcfg now shows something:
 

# djtgcfg enum
Found 1 device(s)

Device: NexysA7
    Product Name:   Digilent Nexys A7 -100T
    User Name:      NexysA7
    Serial Number:  210292AA7671

However, in the hardware manager in Vivado I still see nothing. :(

Does this mean that at least djtgcfg is working? Or is it supposed to show more?

Link to comment
Share on other sites

Hi @aeon20,

Glad to hear that you have some progress. Thank you for sharing what you had to do.

Make sure to install the digilent cable drivers.

1. Execute "cd /opt/Xilinx/Vivado/2018.3/data/xicom/cable_drivers/lin64/install_script/install_drivers/"
2. Execute "sudo ./install_drivers"
3. Execute “source /opt/Xilinx/Vivado/2018.3/settings64.sh
4. Execute “vivado” to launch the application.
5. Open hardware manager and click auto connect.

The PC might need to be restarted as well.

thank you,

Jon

Link to comment
Share on other sites

6 minutes ago, jpeyron said:

Hi @aeon20,

Glad to hear that you have some progress. Thank you for sharing what you had to do.

Make sure to install the digilent cable drivers.

1. Execute "cd /opt/Xilinx/Vivado/2018.3/data/xicom/cable_drivers/lin64/install_script/install_drivers/"
2. Execute "sudo ./install_drivers"
3. Execute “source /opt/Xilinx/Vivado/2018.3/settings64.sh
4. Execute “vivado” to launch the application.
5. Open hardware manager and click auto connect.

The PC might need to be restarted as well.

thank you,

Jon

Thanks for the help.

I've now completed all of these steps, including rebooting. However, it still looks like this:

 

hardware_not_detected.jpg

Link to comment
Share on other sites

On 2/18/2019 at 5:42 PM, jpeyron said:

Hi @aeon20,

Could your firewall be interfering.

The link works for me and others in the office. 

1)  Are you able to select this link here?

thank you,

Jon

I'm sorry, I meant that the link you posted in the other thread doesn't go anywhere. I don't know why I replied here, I got confused.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...