The software environment is setup using modules, see section Software Overview. For hardware execution, FPGA nodes with the correct configuration and driver version (so-called board support package or BSP) need to be allocated, see section FPGA System Access to FPGA Partition.
The software environment is setup using modules. Depending on the user requirements, different development flows for the FPGA cards are supported.
Xilinx Alveo U280
Vitis Design Flow (recommended)
Vivado Design Flow
Intel Stratix 10
OpenCL (recommended for projects with exisiting OpenCL code base or for usage of serial channels)
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 Noctua 2 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.
To use Noctua 2 nodes with FPGAs, along with your Slurm command, you need to select the FPGA partition and provide a constraint to specify the configuration of FPGAs (shell, driver, board support package (BSP)) that your designs have been built for.
For Xilinx Alveo U280 cards you can use
srun --partition=fpga --constraint=xilinx_u280_xrt2.12 -A [YOUR_PROJECT_ACCOUNT] -t 2:00:00 --pty bash
For Bittware 520n cards with Intel Stratix 10 FPGAs you can use
srun --partition=fpga --constraint=bittware_520n_20.4.0_max -A [YOUR_PROJECT_ACCOUNT] -t 2:00:00 --pty bash
Constraints can be used together with srun, sbatch and salloc, however under some conditions salloc will fail, for details click the expansion box below. We recommend to always use srun or sbatch.
A problem occurs when one of the nodes to be allocated is configured for a different constraint and is currently in use. Then salloc will fail with the following error message.
salloc: error: Job submit/allocate failed: Requested node configuration is not available
Workaround: use an allocation without requesting specific node names.
A problem also occurs when one of the nodes to be allocated is configured for a different constraint and is currently free. The allocation succeeds while the nodes are still reconfigured, programs or scripts starting during this time will fail, actual errors encountered differ.
When configured with a correct BSP, all FPGA boards offer 4 point-to-point connections to other FPGA boards. FPGA Serial Channels have an own documentation page with various examples and a graphical input tool (see figure below).
In order to help you as quickly as possible, please follow these guidelines
Use [Noctua2-FPGA] as a prefix in your email subject line.
Where did the problem occur and what did you expect to happen?
If possible, how can we reproduce the error in a systematic manner?
Did you attempt to fix/troubleshoot the problem? If you attempted to debug the problem, provide us the steps you already took and the intermediate results.
For general questions, acceleration support or project ideas with regarding FPGAs, please reach out to the FPGA domain-expects.
Available FPGA Libraries and Applications
We and others have developed several ready to use libraries and applications that use FPGAs to accelerate the computation. Please use the links to get examples and the documentation. You can contact us, if you need guidance to accelerate your target code with our FPGAs libraries.