cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Observer
Observer
3,133 Views
Registered: ‎04-20-2017

digilent jtag not detected in hw_manager

I have been using Digilent HS-2 with my development system for some months with no issues.

Recently, I needed to move the target board (a pci plug in board) to a new target system.

The new system would not accommodate the HS-2 due to physical constraints, so I got an HS-3.

The HS-3 in the new system did not work, so I moved the board back to my development system, and it did not work there either.  I went back to the HS-2 and now it does not work either.  In all cases the hw_server can be connected to, but says "No Target."  I'm running various versions of Ubuntu, and may have done an apt update in the mean time.  Thinking I may have blown out the board moving it around, I sent it back to the manufacturer for repair, but they found it to run properly in their factory, so the board seems ok.

Summary:

  board is ok

  Hardware Manager used to see the device using HS-2, no problems

  neither HS-2 nor HS-3 works now, on either original system or new one

  os: Ubuntu 16.04 LTS

  Vivado 2017.4 (tried 2017.3 also, same results)

 

I've found various suggestions related to loading cable drivers, tried many, with no change in results, but may have screwed up udev rules, etc in the process.

 

Any ideas please?

 

Addendum: lsusb shows "Bus 001 Device 005: ID 03fd:000d Xilinx, Inc. " for the HS-3 (fwiw)

0 Kudos
12 Replies
Highlighted
Scholar
Scholar
3,123 Views
Registered: ‎02-27-2008

jcz,

 

Yes, you must have updated or changed something as they should 'just work' once the drivers are installed.  I suspect you somehow over-wrote the good driver file.  I would go back, remove the drivers, and re-install them freshly.  Note that some versions of tools are not supported by Ubuntu 16.04:

 

https://www.xilinx.com/support/answers/54242.html

Austin Lesea
Principal Engineer
Xilinx San Jose
0 Kudos
Highlighted
Observer
Observer
3,109 Views
Registered: ‎04-20-2017

OK, did:

jcz@t3:~$ sudo rm -f etc/udev/rules.d/52-xilinx-digilent-usb.rules
jcz@t3:~$ sudo rm -f /etc/udev/rules.d/52-xilinx-ftdi-usb.rules
jcz@t3:~$ sudo rm -f /etc/udev/rules.d/52-xilinx-pcusb.rules

jcz@t3:~$ cd /opt/Xilinx/HWSRVR/2017.4/data/xicom/cable_drivers/lin64/install_script/install_drivers

jcz@t3:/opt/Xilinx/HWSRVR/2017.4/data/xicom/cable_drivers/lin64/install_script/install_drivers$ sudo ./install_drivers
INFO: Installing cable drivers.
INFO: Script name = ./install_drivers
INFO: HostName = t3
INFO: Current working dir = /opt/Xilinx/HWSRVR/2017.4/data/xicom/cable_drivers/lin64/install_script/install_drivers
INFO: Kernel version = 4.4.0-116-generic.
INFO: Arch = x86_64.
USB udev file exists and will not be updated.
--File /etc/udev/rules.d/52-xilinx-ftdi-usb.rules does not exist.
--File version of /etc/udev/rules.d/52-xilinx-ftdi-usb.rules = 0000.
--Updating rules file.
--File /etc/udev/rules.d/52-xilinx-pcusb.rules does not exist.
--File version of /etc/udev/rules.d/52-xilinx-pcusb.rules = 0000.
--Updating rules file.

INFO: Digilent Return code = 0
INFO: Xilinx Return code = 0
INFO: Xilinx FTDI Return code = 0
INFO: Return code = 0
INFO: Driver installation successful.
CRITICAL WARNING: Cable(s) on the system must be unplugged then plugged back in order for the driver scripts to update the cables.

 

Then I rebooted system, unplugged and replugged usb cable, ran vivado, opened hardware manager, clicked open target, clicked auto, and still no target found.

 

0 Kudos
Highlighted
Scholar
Scholar
3,097 Views
Registered: ‎02-27-2008

"USB udev file exists and will not be updated."  ....

 

That may be the missing piece.  The one file that appears to be there, not rewritten nor replaced, and correct, but is not?

 

Otherwise, I agree, it should just work after that!

 

Also:

 

https://www.xilinx.com/support/answers/70395.html

 

 

Austin Lesea
Principal Engineer
Xilinx San Jose
0 Kudos
Highlighted
Observer
Observer
3,089 Views
Registered: ‎04-20-2017

Hmmm, one of the devices is now working, the other may be a Digilent problem, I'm working with them now.

0 Kudos
Highlighted
Observer
Observer
2,999 Views
Registered: ‎04-20-2017

Well we have the HS-2 working.

Turns out the other adapter is an XUP USB-JTAG, not an HS-3.

The XUP is not seen by hardware manager.

lsusb shows:

Bus 003 Device 011: ID 03fd:000d Xilinx, Inc.

for the device.

What else can I check?

0 Kudos
Highlighted
Scholar
Scholar
2,990 Views
Registered: ‎02-27-2008

Don't know,

 

Might be a bad cable interface (something is broken),

 

 

Austin Lesea
Principal Engineer
Xilinx San Jose
0 Kudos
Highlighted
Observer
Observer
2,988 Views
Registered: ‎04-20-2017

Tried with 2 different cables, both of which work with the HS-2.

0 Kudos
Highlighted
Observer
Observer
2,967 Views
Registered: ‎04-20-2017

So Digilent says the XUP is supplied to them by Xilinix and they can't support it.

When plugged in, the XUP shows up in lusb as

Bus 003 Device 011: ID 03fd:000d Xilinx, Inc.

but it is not recognized by Vivado hardware manager.

What do I do next?

0 Kudos
Highlighted
Scholar
Scholar
2,960 Views
Registered: ‎02-27-2008

Contact xup:

 

xup@xilinx.com

 

As a professor signed up with xup, you may also seek support:

 

https://www.xilinx.com/support/university/professors.html#support

Austin Lesea
Principal Engineer
Xilinx San Jose
0 Kudos
Highlighted
Observer
Observer
2,091 Views
Registered: ‎04-20-2017

I sent email to xup as you suggested, in response, I got:

Message not delivered
There was a problem delivering your message to xup@xilinix.com. See the technical details below.
LEARN MORE
The response was:

The recipient server did not accept our requests to connect. Learn more at https://support.google.com/mail/answer/7720 [xilinix.com 63.241.181.135: timed out]


Final-Recipient: rfc822; xup@xilinix.com
Action: failed
Status: 4.4.1
Diagnostic-Code: smtp; The recipient server did not accept our requests to connect. Learn more at https://support.google.com/mail/answer/7720
 [xilinix.com 63.241.181.135: timed out]
Last-Attempt-Date: Sun, 18 Mar 2018 15:11:07 -0700 (PDT)

0 Kudos
Highlighted
Scholar
Scholar
2,086 Views
Registered: ‎02-27-2008

will check, but

 

Seems to be working for me.

Austin Lesea
Principal Engineer
Xilinx San Jose
0 Kudos
Highlighted
Observer
Observer
1,804 Views
Registered: ‎04-02-2011

Was there any resolution to this? 

0 Kudos