This table provides an overview how the components for the different target platforms and development tools relate to each other.
Entries with
ml <name>show modules that need to be loaded both for development and hardware execution with the respective FPGA platform and development tool. Here specific version names are omitted, which loads always the latest version of the module.
FPGA Platform | Xilinx Alveo U280 with Virtex Ultrascale+ FPGA | Bittware 520N with Stratix 10 FPGA | ||
|---|---|---|---|---|
Development Tool | This contains the compiler with high-level-synthesis features, report generation, and an emulator for testing. New optimizaiton features depend mostly on this tool. | Xilinx Vitits
| Intel oneAPI
| Intel FPGA SDK for OpenCL
|
FPGA Synthesis Backend | This translates and maps your design to a bitstream, roughly the FPGA counterpart to an assembler in the CPU world. Since the FPGA backend has millions of registers, lookup tables and wires to chose from, this process takes a long time. | Xilinx Vivado, version selected and automatically loaded along with Vitis (above). | Intel Quartus, version selected and automatically loaded along with the BSP (below). | Intel Quartus, version selected and automatically loaded along with the BSP (below). |
FPGA Shell | This component is configured on the FPGA and provides base funtionality like PCIe, and DDR or HBM2 controllers. | Xilinx shell
| Part of Bittware Board Support Package (BSP), available with (
| |
Device Driver | This is a software component that controls the interaction with the FPGA shell. | Xilinx XRT
| Part of Bittware Board Support Package (BSP), available with (
| |
Rules | A specific coupling of XRT and Vitis versions is recommended and automatically resolved by the modules (version strings don’t match). Multiple pairs of XRT+Vitis can use the same shell. Detail page. | Development tools need a sufficiently recent BSP version to work with. Detail page. | ||
Node Allocation Constraint | When you submit a job into the fpga partition for hardware execution, with this contraint you request a fitting FPGA platform, shell and driver. You still need to load the corresponding modules. For synthesis and emulation, no constraint is needed, but you need to use the same modules as for later hardware execution. | Constraints named by xrt Version and shell, e.g.
| ||