Skip to content

XVC server on AWS F2 instance fails with "Loopback test FAILED" after XVC PCIe driver installation

0

Hello, AWS team. I'm trying to run the XVC server on an AWS F2 instance, but I'm encountering a problem where the server fails to start due to a loopback test failure. I followed the official instructions to install the XVC driver from this page:

https://github.com/aws/aws-fpga/blob/f2/hdk/docs/Virtual_JTAG_XVC.md#install-xvc-driver-on-f2-instances

After building and loading the driver, it appears to be correctly loaded:

# lsmod
Module                  Size  Used by
xilinx_xvc_pci_driver    16384  0

However, when I try to launch the XVC server, I get the following output:

# cd /opt/Xilinx/Vivado/2024.1/bin
# ./xvc_pcie

Description:
Xilinx xvc_pcie v2024.1
Build date : May 22 2024-19:19:01
Copyright 1986-2018 Xilinx, Inc. All Rights Reserved.

INFO: XVC PCIe Driver character file - /dev/xil_xvc/cfg_ioc0
INFO: XVC PCIe Driver configured to communicate with Debug Bridge IP in AXI mode (PCIe BAR space).
INFO: PCIe BAR index=0x0002 and PCIe BAR offset=0x0000
Loopback test length: 32, pattern abcdefgHIJKLMOP FAILURE
        Byte 0 did not match (0x61 != 0x00 mask 0xFF), pattern abcdefgHIJKLMOP
ERROR: XVC PCIE Driver Loopback test failed. Error: Success
Exiting xvc_pcie application.

I'm unsure what could be causing the loopback test to fail. The driver appears to load without errors, but the xvc_pcie application fails at runtime.

Has anyone encountered a similar issue? Any advice would be appreciated.

Thank you.

Best Regards,

ywvec

asked 10 months ago196 views
5 Answers
1

I apologize, but I don't have specific information about the XVC server or F2 instances in the provided sources to directly address your issue. However, I can offer some general troubleshooting advice for EC2 instances:

  1. Check the system logs for any error messages or warnings that might provide more insight into the problem. You can use commands like dmesg or examine logs in /var/log/ to look for relevant information.

  2. Ensure that your instance has the latest updates and patches installed. Sometimes, updating the system can resolve compatibility issues.

  3. Verify that your instance meets all the prerequisites for running the XVC server, including having the correct instance type, AMI, and necessary dependencies.

  4. If possible, try recreating the issue on a fresh instance to rule out any configuration problems with your current instance.

  5. Check if there are any known issues or recent changes with the XVC server software that might be causing this problem. You may want to consult the official documentation or support channels for the XVC server.

  6. If the problem persists, you may need to contact AWS support for more specialized assistance, as they would have more detailed knowledge about F2 instances and potential issues with the XVC server.

Remember to always back up your data before making any significant changes to your instance.
Sources
Troubleshoot Amazon EC2 Linux instances with failed status checks - Amazon Elastic Compute Cloud
Problem with RDC | AWS re:Post

answered 10 months ago
EXPERT
reviewed 10 months ago
0

Thank you for your reply. I’ll definitely take a closer look at the system logs as you suggested.

However, I just wanted to clarify one thing. According to the documentation at the following link:

https://github.com/aws/aws-fpga/blob/f2/hdk/docs/Virtual_JTAG_XVC.md#install-xvc-driver-on-f2-instances it seems that the guide refers to Vivado version 2024.2.

In my case, I’m currently using Vivado 2024.1. Could this version mismatch be related to the loopback test failure I’m experiencing with the xvc_pcie server?

I’d really appreciate it if you could confirm whether version compatibility might be the cause of the issue.

Thanks again for your help.

answered 10 months ago
0

Hello!

Thanks for bringing this issue to our attention. We have tested the xvc_pcie driver on our latest FPGA developer AMI with Vivado 2024.2. We could look at more information if you shared the region and instance ID of where you tested this. Could you share the AMI/OS you're using? Did you install Vivado yourself?

Additionally, there could be some kernel compatibility issues if you've performed updates. Can you provide your output from running uname -a?

Thanks!

  • Joe
answered 10 months ago
0

Hi Joe,

Thank you very much for your response.

Please find below the details of our environment:

  • Region: us-east1

  • Instance ID: i-0e08d5193ad0db9e9

  • AMI/OS: FPGA Developer AMI (Ubuntu) - 1.16.1 - prod-byisb4uqt2pwc

The output of uname -a is as follows:

Linux ip-10-0-10-221 5.15.0-1084-aws #91~20.04.1-Ubuntu SMP Fri May 2 06:59:36 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

Additionally, please note that we did not install Vivado manually; we are using the pre-installed version of Vivado ML included in the AMI.

Thank you again for your support.

Best regards, ywvec

answered 10 months ago
0

Hi ywvec,

I launched a fresh f2.6xlarge instance using our FPGA Developer AMI 1.16.1 and follow the documentation for XVC. With that, I was able to obtain a passing result.

root@ip-172-31-62-89:/home/ubuntu/aws-fpga/driver_v0.4# lsmod | grep xilinx
xilinx_xvc_pci_driver    16384  0
root@ip-172-31-62-89:/home/ubuntu/aws-fpga/driver_v0.4# cd /opt/Xilinx/Vivado/2024.1/bin/
root@ip-172-31-62-89:/opt/Xilinx/Vivado/2024.1/bin# ./xvc_pcie 

Description:
Xilinx xvc_pcie v2024.1
Build date : May 22 2024-19:19:01
Copyright 1986-2018 Xilinx, Inc. All Rights Reserved.

INFO: XVC PCIe Driver character file - /dev/xil_xvc/cfg_ioc0
INFO: XVC PCIe Driver configured to communicate with Debug Bridge IP in AXI mode (PCIe BAR space).
INFO: PCIe BAR index=0x0002 and PCIe BAR offset=0x0000
INFO: XVC PCIE Driver Loopback test successful.

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

INFO: To connect to this xvc_pcie instance use url: tcp:ip-172-31-62-89:10200

Did you remember to run all required steps using sudo su?

Best, Max - AWS FPGA Team

answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.