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)
Question
jcz
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)
Link to comment
Share on other sites
41 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.