01-07-2018 04:46 PM
I have a Kintex KC-705 FPGA connected via UART-USB to a Windows 10 x64 PC with Vivado 2017.3. I was able to run the BIST on it according to this manual: https://www.xilinx.com/support/documentation/boards_and_kits/kc705/2014_3/ug883_K7_KC705_Eval_Kit.pdf.
I'm currently running into issues when I try to test the IBERT banks using this manual: https://www.xilinx.com/support/documentation/boards_and_kits/kc705/2014_3/xtp200-kc705-ibert-c-2014-3.pdf. The issues I get are:
1. When I run the command source ibert_bank_117_118.tcl on page 13 of the PDF in the IBERT link, I get the following error in Vivado.
ERROR: [Common 17-170] Unknown option '-host', please type 'connect_hw_server -help' for usage info.
I suspect this may be a syntax error in the script code, and the newer version of Vivado hasn't upgraded.
2. The Hardware Manager says that it's unconnected, but the Hardware tab says that its connected to localhost(0), but the FPGA device is not connected. Below is a snapshot of the Vivado console.
If anyone is able to help me could they please point me in the right direction?
02-19-2018 07:55 AM - edited 02-19-2018 07:56 AM
@malharjereCould you please elaborate how you solved it so that those of us with the same problem can try your solution?
02-19-2018 08:28 AM
It seems like the script does this:
connect_hw_server -host localhost -port 60001 -url localhost:3121
current_hw_target [get_hw_targets */xilinx_tcf/Digilent/*]
set_property PARAM.FREQUENCY 15000000 [get_hw_targets */xilinx_tcf/Digilent/*]
If I connect to a HW target via the GUI to "Open New Hardware Target" the TCL commands used are like this in the console.
connect_hw_server -url localhost:3121
INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121
current_hw_target [get_hw_targets */xilinx_tcf/Digilent/210203335965A]
set_property PARAM.FREQUENCY 15000000 [get_hw_targets */xilinx_tcf/Digilent/210203335965A]
If I try to use the -host option for connect_hw_server it errors out for me.
I am pretty sure the -host was deprecated because we needed to make the port selection more transparent to the user
02-19-2018 08:31 AM
I was able to solve it shortly after posting my reply. I had installed Vivado on Linux and didn't realize that the cable drives were not installed automatically with Vivado, but had to be installed separately. Once I followed the instructions in UG973, the Hardware Manager was able to detect my board.