AMD Alveo V80 Server Accelerator Card: Complete Development Guide

Foreword: The AMD Alveo V80 is built on the Versal HBM XCV80 adaptive SoC architecture — a high-end server accelerator card for data-center high-bandwidth, high-throughput, large-scale parallel computing, widely used in HPC, quantitative finance, big data analytics and network acceleration. The V80 adopts a brand-new Versal HBM architecture with strictly version-locked development environments. Standardized deployment of prerequisite drivers, toolchains and base frameworks is the core prerequisite for stable engineering compilation, on-board debugging and hardware development later on.

Foreword:

The AMD Alveo V80 is built on the Versal HBM XCV80 adaptive SoC architecture — a high-end server accelerator card for data-center high-bandwidth, high-throughput, large-scale parallel computing, widely used in HPC, quantitative finance, big data analytics and network acceleration. The V80 adopts a brand-new Versal HBM architecture with strictly version-locked development environments. Standardized deployment of prerequisite drivers, toolchains and base frameworks is the core prerequisite for stable engineering compilation, on-board debugging and hardware development later on.

This article focuses on the FPGA low-level prerequisite development of the V80, fully covering hardware adaptation verification, system environment setup, low-level driver deployment, Vivado tool installation and the AVED core development framework deployment — a hands-on prerequisite guide for adapting V80 low-level hardware development.

I. Core Overview of Development Prerequisites

1.1 Key Characteristics of Environment Deployment

The Alveo V80 Versal HBM architecture has strict compatibility requirements: it is only compatible with the Vivado toolchain 2023.1 or later and the corresponding framework versions. Older toolchains cause device recognition failures, IP adaptation errors, engineering compilation errors and on-board debug issues. The development environment must strictly follow version-matching rules.

1.2 Required Development Components

The V80 low-level FPGA development environment consists of three parts — the basic required components for project setup, low-level debugging and hardware adaptation:

• System base dependencies: ensure tool operation, code compilation, framework pull and permission invocation
• Vivado toolchain: core development/compilation tool, shipping the Versal HBM device support libraries
• AVED development framework: the V80-dedicated low-level project framework, pre-integrating the full set of low-level IPs — PCIe, DMA, clock/reset, board management and hardware self-test

1.3 Core Hardware Parameters for Development (Environment Adaptation Reference)

• Bus interface: PCIe Gen5 x16 (requires both motherboard hardware and BIOS support)
• Power rating: 190W TDP; the PCIe slot must deliver 200W or more full-load power
• Cooling form: passive cooling, relying on the server chassis airflow, no independent active fan
• Core architecture: Versal HBM XCV80, adapted to the new toolchain and AVED framework
• On-board modules: integrated native PCIe controller, high-speed DMA engine, AMI management module and XBTEST self-test module

1.4 Core Goals of Prerequisite Deployment

• Complete hardware physical installation and recognition, ensuring the server enumerates the V80 device normally;
• Set up a clean, adapted system environment with all base dependencies installed;
• Deploy the complete Vivado toolchain and Versal HBM device support package;
• Install the matching AVED framework so V80 low-level projects can be created and compiled directly;
• Complete hardware self-test and link verification to avoid hardware compatibility and firmware risks.

II. Hardware Environment Adaptation and Physical Installation Specification

2.1 Server Hardware Adaptation Requirements

• Slot requirement: standard PCIe Gen5 x16 physical slot; a Gen4 slot causes bandwidth downgrade, protocol negotiation errors and halved performance;
• Power requirement: full-load slot power ≥200W; insufficient power triggers card drop-out, resets or throttling under high load;
• Cooling requirement: unobstructed server chassis airflow matching passive cooling conditions;
• System requirement: Ubuntu 20.04/22.04 or RHEL 8/9 64-bit server systems; desktop systems and legacy server systems are not supported.

2.2 Physical Installation and BIOS Configuration

• Power the server down completely, discharge static, insert the V80 card into the dual-slot PCIe slot and secure the bracket;
• Boot into the motherboard BIOS, enable PCIe Gen5 full-speed mode, disable PCIe power-saving, throttling and auto-suspend policies;
• Disable PCIe compatibility mode and enable high-performance mode;
• Save the BIOS configuration and reboot the server to apply the settings.

2.3 Basic Hardware Recognition Verification

After the server reboots, run the following commands to verify the hardware mount state and confirm normal device recognition:

| `lspci | grep -i alveo` |
| `lspci | grep -i versal` |

Normal terminal output of the AMD Versal XCV80 device information means the hardware is seated correctly and the slot is working; no output means re-check the card seating, slot state and BIOS configuration.

III. Complete Driver and Development Framework Installation Procedure

3.1 Mandatory Software Version Specification

The V80 low-level development versions are strictly bound; all component versions must match each other, as specified below:

• Vivado toolchain: 2023.1 or later, with the complete Versal HBM XCV80 device support package
• Core development framework: AVED (Alveo Versal Example Design) 1.x matching the Vivado version
• Supporting management tools: AMI device management tool, XBTEST hardware self-test tool

3.2 System Base Dependency Installation

Before deploying drivers and frameworks, install the system base dependencies to ensure normal tool operation, code compilation and source pulling:

| `sudo apt update && sudo apt upgrade -y` |
| `sudo apt install -y git make gcc g++ libssl-dev libudev-dev` |

3.3 Vivado Toolchain Installation and Environment Configuration

Vivado is the core compilation tool for V80 low-level development, shipping hardware adaptation drivers and device libraries — the foundation for hardware recognition, project compilation and bitstream generation:

• Install Vivado 2023.1 or later; during installation you must select the Versal HBM XCV80 device support package — without the device library the chip cannot be recognized or the low-level IP adapted;
• After installation, configure the global environment variables so tools are callable from any terminal and hardware devices resolve correctly:

| `echo "source /tools/Xilinx/Vivado/2023.1/settings64.sh" >> ~/.bashrc` |
| `source ~/.bashrc` |

3.4 AVED Official Development Framework Installation

AVED is the V80-dedicated low-level project framework, integrating the full set of officially adapted low-level driver IPs — PCIe Gen5, high-speed DMA, clock/reset, hardware monitoring and self-test — so developers do not manually adapt low-level protocols. It is the engineering foundation for all secondary development:

| `# Pull the AMD official Alveo Versal low-level framework source` |
| `git clone https://github.com/Xilinx/alveo-versal-examples.git` |
| `# Enter the project root` |
| `cd alveo-versal-examples` |
| `# Match the Vivado version, switch to the v2023.1 stable branch` |
| `git checkout v2023.1` |

Once the framework is installed, V80-dedicated projects can be created directly from the built-in templates, quickly completing low-level hardware adaptation development.

IV. Environment Integrity Verification and Hardware Self-Test

After all drivers, tools and frameworks are deployed, verify environment integrity with the official self-test tool, confirming no hardware adaptation issues or version conflicts.

4.1 Basic Hardware Function Self-Test

| `xbtest -basic` |

A 100% pass rate on all test items with no errors means the hardware driver adaptation and framework environment are running normally.

4.2 Full Device Status Verification

| `# View device firmware version, hardware revision and adaptation status` |
| `alveo-ami status` |
| `# View real-time power, temperature and operating conditions` |
| `alveo-ami telemetry` |

V. Common Prerequisite Environment Faults and Quick Troubleshooting

5.1 Device Recognition Failure

Symptom: lspci cannot enumerate the V80 device.

Troubleshooting: check PCIe slot power, card seating contact, BIOS Gen5 configuration, then reboot the server and re-verify recognition.

5.2 Device Recognition Failure at Project Initialization

Symptom: Vivado reports errors opening the AVED project and cannot recognize the XCV80 device.

Troubleshooting: install the Versal HBM device support package and ensure the Vivado version fully matches the AVED framework version.

5.3 Abnormal Hardware Self-Test Link

Symptom: xbtest self-test fails, PCIe link downgraded.

Troubleshooting: verify the hardware production revision and native firmware, lock PCIe Gen5 full speed in BIOS, and check slot power stability.

5.4 Compilation Environment Dependency Errors

Symptom: AVED project compilation reports missing dependencies or command execution failures.

Troubleshooting: reinstall the system base dependencies, refresh environment variables and ensure the Vivado toolchain takes effect globally.

VI. Prerequisite Environment Deployment Summary

The core of AMD Alveo V80 low-level development prerequisite deployment is completing the standardized, version-matched installation of system dependencies, Vivado toolchain and drivers, and the AVED low-level framework. The full environment provides complete low-level support for V80 hardware recognition, low-level IP adaptation, project compilation and on-board debugging.

During development, strictly following the version-matching specification, fully installing the device support libraries and avoiding unofficial hardware adaptation risks in advance is enough to set up a stable, clean V80 low-level development environment, laying the foundation for subsequent FPGA logic development and hardware debugging.