12-03-2013 03:35 PM
With Vivado 2013.2 I am unable to connect to a Xilinx Platform Cable USB. On the same computer with the same hardware I am able to connect using ISE 14.4
Here are the steps and symptoms:
1. With a cold boot of the PC and all hardware
2. Launch Vivado 2013.2. Open Hardware Session. Open New Hardware Target. I get the following error:
3. Try again, but this time manually launch vcse_server.
Try 'Open New Hardware Target' in Vivado again.
Same error message in Vivado. Here is a capture of the command window
4. Try with TCL commands
INFO: [Labtools 27-147] vcse_server: Connecting to TCF agent...
INFO: [Labtools 27-147] vcse_server: Attempting to launch hw_server...
WARNING: [Labtoolstcl 44-26] No hardware targets exist on the server [localhost]
Check to make sure the cable targets connected to this machine are properly connected
and powered up, then use the disconnect_hw_server and connect_hw_server commands
to re-register the hardware targets.
5. Same results if I try with a different vcse_server port.
6. Cable drivers appear to be current. The install_debug.log shows they were properly installed.
INFO ::Fri Nov 22 17:41:32 TZ 2013:: Execute: C:\Xilinx\Vivado\2013.2\data\xicom\cable_drivers\nt\install_drivers_wrapper.bat C:\Xilinx\Vivado\2013.2\data\xicom\cable_drivers\nt C:\Xilinx\Vivado\2013.2\.xinstall\install.log C:\Xilinx\Vivado\2013.2\.
INFO ::Fri Nov 22 17:42:16 TZ 2013:: Driver installation successful. The machine has to be rebooted to properly complete the driver installation.
7. The ISE 14.4 tools work just fine on the same computer with the same hardware.
12-03-2013 09:20 PM
12-04-2013 08:22 PM
01-30-2014 07:01 AM
02-04-2014 01:19 AM
Check with latest version of Vivado i.e., 2013.4
02-12-2014 01:23 AM
Does not help. I'm using Vivado 2013.4 and using a Microzed Board, however, I still get the same "There is no valid target connected to the server ...." error.
Any solution would be greatly appreciated.
O/S : Windows 7 32-bit home edition
02-12-2014 01:25 AM
Instead of putting localhost:60001, try setting <your_machine_name>:60001.
05-30-2014 02:09 PM
Any resolution for this problem? I'm having the same issue (vivado 2014.1, Windows 7 64 bit). ISE is also installed - Impact and Chipscope Analyser work fine.
The suggestion of using <your_machine_name>:60001 does not even seem to be possible in "Open new Hardware Target" dialog.
I've followed the reinstall instructions from http://forums.xilinx.com/t5/Design-Tools-Others/Vivado-2013-3-Hardware-session-don-t-detect-valid-target/m-p/438512#M5873 but still no luck.
06-02-2014 09:15 AM
Fixed it. I had to re-install the cable driver in Vivado. I did it using the short-cut described here http://forums.xilinx.com/t5/Installation-and-Licensing/Problem-adding-cable-drivers-to-Vivado-2014-1/td-p/441188
07-09-2014 05:52 AM
I am using 2014.2 and have a kintex7 board connected to the local machine using a digilent usb cable. I could't get my xilinx hardware session create a connection with the board.
1. So I gave up using the Digilent cable and connected the board using a Platform USB cable.
2. Reinstalled the cable drivers (Xilinx Cable Drivers) using the 'Hardware Standalone' option in the setup.
3. Open a hardware session using the vivado. Able to successfully connect to the board.
04-28-2015 09:05 AM
I have the exactly same problem. I've tried all the suggestions above but there is no solution, no connection..
OS is Windows 7 64-bit , Vivado version is 2014.4 and board is Zybo.
05-24-2016 03:13 PM
Hi, same here for Win 10 64bit Vivado 2016.1:
Am not able cannot connect the Platform Cable USB II using any method discussed. Jungo and Programming cables Xilinx USB Cable showing up in Device Manager, they can be easily re-installed etc. JTAG Pins have been check several times for Arty and Zybo boards. Green-light is also ON. All I get is 'localhost'. Flashing per Digilent/FTDI/JTAG no problem whatsoever, but with the actual Xilinx debugger...nope. I sometimes have faulty micro-USB cables and all sorts of things...can't get hw target...
What can I check next? Any ideas, solutions?
04-04-2017 03:58 AM
I have this very same issue with Vivado 2016.4, Windows 7 64-bit using original Xilinx Platform Cable USB II. As others, driver seems installed correctly and LED turns from red to green as I attach the target.
Though, Vivado works just fine with Digilent Basys 3 board which uses FTDI onboard JTAG adapter.
None of the above solutions worked unfortunately.
04-04-2017 12:08 PM
Really strange that so many people have this experience. Also I actually do not see the big advantage of the debugger compared to FTDI devices. KR
06-29-2017 03:58 PM
Hi, I'm using Vivado 2016.4, Kernel is 4.4.0-64-generic, Ubuntu 16.04 LTS , and a Kintex-7 FPGA. It works fine at first, the hardware server could detect the device but later on when I try to reprogram the board with the newly generated bitstream, probably because of the PCIe slot issue, the system reboot suddenly. Before rebooting, I try the command Ctrl-c to stop programming but it doesn't. After the rebooting, though the hardware server is connected, it shows that there's no valid hardware target connected. Could someone help me with this issue?