Overview

The software environment is setup using modules. Depending on the user requirements, different development flows for the FPGA cards are supported.

Otus

• see Otus Pilot Phase

Noctua 2

• Xilinx Alveo U280

  • Vitis Design Flow (recommended)

  • Vivado Design Flow

• Intel Stratix 10

  • oneAPI (recommended)

  • OpenCL (recommended for projects with exisiting OpenCL code base or for usage of serial channels)

  • DSP Builder

The development (including emulation to check functional correctness, report generation to get indications of expected performance, and synthesis with bittstream generation) can be done on any node. Just load the corresponding modules for the target FPGA platform and Development Tool flow.

To execute designs on actual FPGAs, the same modules are required and additionally an FPGA node needs to be allocated with a fitting constraint, to get FPGAs with the expected configuration and drivers.

FPGA Software and Firmware Stacks (included page)

Constraint Overview (included page)

FPGA and Tool Specific Details

Otus

• see Otus Pilot Phase

Noctua 2

Xilinx Alveo U280

Xilinx Vitis Design Flow

Xilinx Vivado Design Flow

You can use Vivado to create and simulate components via RTL that can be included as components into a Vitis project and the provided shells.

Intel Stratix 10

Intel oneAPI Design Flow

Intel FPGA SDK for OpenCL Design Flow

DSP Builder for Intel FPGAs

You can use the Intel FPGA DSP builder to create and simulate components that can be included as components into an OpenCL or oneAPI project.

Intel Quartus Prime

You can use the Intel Quartus to create and simulate components that can be included as components into an OpenCL or oneAPI project.