Virtual JTAG on remote machine (instead of local F1 instance)

Hello,

Thank you for bringing the documentation hole to our attention! We will fix it asap.
Can yo make sure firewalld is either disabled or is allowing connections for those two ports.

Maybe this is a big hammer, but for debug purposes, lets stop firewalld first on both instances:

sudo systemctl stop firewalld

Second thing is to make sure both instances allow ports 3121 and 10201, not just the F1 instance. One way is to allow all connections between two instances: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-group-rules-reference.html#sg-rules-other-instances

Please let me know if this does not help or work for you.

-Deep

Hi,

In addition to Deep's suggestion above, please follow below mentioned steps:

1. Start hw_server in the target F1 instance, and then fpga-start-virtual-jtag:

[$] sudo su 
[$]# hw_server &
****** Xilinx hw_server v2019.2
  **** Build date : Oct 24 2019 at 19:23:45
    ** 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:ip-xxx-xx-xx-xxx.ec2.internal:3121

[$]# fpga-start-virtual-jtag -P 10201 -S 0
Starting Virtual JTAG XVC Server for FPGA slot id 0, listening to TCP port 10201.
Press CTRL-C to stop the service.

2. Then, on the Remote Machine (where you run Vivado) follow the steps described here:
   https://github.com/aws/aws-fpga/blob/master/hdk/docs/Virtual_JTAG_XVC.md#connecting-xilinx-hardware-manager-vivado-lab-edition-running-on-a-remote-machine-to-the-debug-target-fpga-enabled-ec2-instance
   NOTE: the <host name or IP address> mentioned in the link above refers to the public IP address of your target F1 instance.

Please contact us if you run into any issues.

Thanks!
Chakra

Hi Deep,

Thanks for you suggestions, but as I have lot of other setups working on my on-prem server, I won't be able to disable the firewall and open all ports.

Can you please advise on how to do it specifically for a port?

Thanks!

Ronak

Hi Deep, Chakra,

Step1 provided by Chakra solved the issue, without disabling firewall and opening all ports.
In AWS documentation, it was not mentioned that I need to start hw_server as well on the instances, in addition to Xilinx's Virtual Cable service.

Just to recap for anyone who might be facing similar issue:
Step1: Whitelist ports 3121 and 10201 in AWS Security Group.
Step2: Start hw_server and XVC service on F1 instance.
Step3: On local server - start Vivado, connect to hw_server, then open_hw_target (as instructed on https://github.com/aws/aws-fpga/blob/master/hdk/docs/Virtual_JTAG_XVC.md#connecting-xilinx-hardware-manager-vivado-lab-edition-running-on-a-remote-machine-to-the-debug-target-fpga-enabled-ec2-instance). Use Public IP for URL.

Process summarized in comment by OP.