cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
carson
Visitor
Visitor
408 Views
Registered: ‎05-15-2013

XSCT Unable to Connect to ZC702 Eval Board Under Ubuntu Linux

Jump to solution

We are trying to get a small single board computer (SBC) to flash our hardware, but XSCT cannot connect.

So I tested the hardware both under Win10 and a Debian system and the Xilinx SDK (using the XSCT Console), as well as on a different Ubuntu system with XSCT tools (see below) and was able to connect via:

rlwrap: warning: your $TERM is 'xterm' but rlwrap couldn't find it in the terminfo database. Expect some problems.

****** Xilinx Software Commandline Tool (XSCT) v2019.1
**** SW Build 2541975 on Sat May 11 11:07:19 MDT 2019
** Copyright 1986-2019 Xilinx, Inc. All Rights Reserved.


xsct% connect -url tcp:127.0.0.1:3121

attempting to launch hw_server

****** Xilinx hw_server v2019.1
**** Build date : May 11 2019 at 11:28:07
** Copyright 1986-2019 Xilinx, Inc. All Rights Reserved.

INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application

INFO: To connect to this hw_server instance use url: TCP:127.0.0.1:3121

tcfchan#0


xsct% targets
1 APU
2 ARM Cortex-A9 MPCore #0 (Running)
3 ARM Cortex-A9 MPCore #1 (Running)
4 xc7z020
xsct% jtag targets
1 Digilent JTAG-SMT2 210251AC2ED6
2 arm_dap (idcode 4ba00477 irlen 4)
3 xc7z020 (idcode 23727093 irlen 6 fpga)
xsct%

The SBC is an Intel Atom (https://www.aaeon.com/en/p/iot-gateway-maker-boards-up-core) with Ubuntu 18.04.1 LTS and a 5.4.0 kernel. A lsusb shows both the USB serial and USB JTAG devices. However, when I try using the XSCT tool, I don't get any connect response. Also, the hw_server application message doesn't show up. This SBC only has the XSCT tools installed, while the other computers had the full SDK. Here is what I see from the SBC:

rlwrap: warning: your $TERM is 'xterm' but rlwrap couldn't find it in the terminfo database. Expect some problems.

****** Xilinx Software Commandline Tool (XSCT) v2019.1
**** SW Build 2552052 on Fri May 24 14:47:09 MDT 2019
** Copyright 1986-2019 Xilinx, Inc. All Rights Reserved.


xsct% connect -url tcp:127.0.0.1:3121
tcfchan#0
xsct% targets
xsct% jtag targets
xsct%

Does anyone have suggestions for troubleshooting?

The only differences I can see are the full SDK version, and also that the hw_server doesn't appear to start.

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
hj
Moderator
Moderator
387 Views
Registered: ‎06-05-2013
Have you installed the Digilent drivers on this Intel Atom machine?

To install the Linux driver, do the following:

1. Enter the following commands as root: ${vivado_install_dir}/data/xicom/cable_drivers/lin64/install_script/ install_drivers/install_drivers
* Note: Replace ${vivado_install_dir} with the location of your Vivado install location.
2. https://www.xilinx.com/support/answers/66440.html

At least XSCT would have shown the Digilent cable even if it cannot find the part.

XSCT should work. For JTAG, you don't need the full SDK version. Try to disconnect and start the same steps.

xsct%connect

xsct%jtag targets
-------------------------------------------------------------------------------------
For more information please refer to configuration resources https://forums.xilinx.com/t5/FPGA-Configuration/Configuration-Resources/m-p/753763/highlight/true#M5891
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

View solution in original post

2 Replies
hj
Moderator
Moderator
388 Views
Registered: ‎06-05-2013
Have you installed the Digilent drivers on this Intel Atom machine?

To install the Linux driver, do the following:

1. Enter the following commands as root: ${vivado_install_dir}/data/xicom/cable_drivers/lin64/install_script/ install_drivers/install_drivers
* Note: Replace ${vivado_install_dir} with the location of your Vivado install location.
2. https://www.xilinx.com/support/answers/66440.html

At least XSCT would have shown the Digilent cable even if it cannot find the part.

XSCT should work. For JTAG, you don't need the full SDK version. Try to disconnect and start the same steps.

xsct%connect

xsct%jtag targets
-------------------------------------------------------------------------------------
For more information please refer to configuration resources https://forums.xilinx.com/t5/FPGA-Configuration/Configuration-Resources/m-p/753763/highlight/true#M5891
-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

View solution in original post

carson
Visitor
Visitor
298 Views
Registered: ‎05-15-2013

Thank you hj!

That worked. I had presumed that the driver was already installed.
I did the following to install the driver: 

sudo ./opt/xilinx/SDK/2019.1/data/xicom/cable_drivers/lin64/install_script/install_drivers/install_drivers

The Digilent cable now shows up properly in dmesg as well.

Thank you for the quick response!