Intel® FPGA SDK for OpenCL™: Stratix® V Network Reference Platform Porting Guide

ID 683645
Date 11/06/2017
Document Table of Contents

3.13. Stratix V Network Reference Platform Implementation Considerations

The implementation of the Stratix® V Network Reference Platform includes some workarounds that address certain Intel® Quartus® Prime software known issues.
  1. The quartus_map executable reads the SDC files. However, it does not support the Tcl command get_current_revision. Therefore, in the top_post.sdc file, a check is in place to determine whether quartus_map has read the file before checking the current version.
  2. Configuration via PCIe® requires the force_hrc parameter to have a value of 1, and the inclusion of the three PCIe INI settings described in the CvP section.
  3. The kernel clock requires a lot of connectivity. Therefore, Intel® recommends compiling the base revision using the super_kernel_clock.rcf Routing Constraints File.
  4. Use the INI setting bpm_hard_block_partition=off to improve version compatibility.
  5. Use the INI setting qic_pf_no_input_rotation=on to prevent certain failures to route.
  6. The CvP revision (that is, top), which imports the .personax file, must include auto global clock promotion for clocks, resets, and clock enable signalss.
  7. To avoid certain routing failures, set the Fitter Preservation Level for the Top partition to Netlist Only. You may assign the setting via the Design Partitions Window or the Tcl Console.

In addition to these workarounds, take into account the following considerations:

  1. The pll_rom.hex file exists before compilation.
  2. Intel® Quartus® Prime compilation is only ever performed after the Intel® FPGA SDK for OpenCL™ Offline Compiler has embedded an OpenCL™ kernel inside the system.
  3. Perform Intel® Quartus® Prime compilation after you install the Intel® FPGA SDK for OpenCL™ and set the INTELFPGAOCLSDKROOT environment variable to point to the SDK installation.
  4. The name of the directory where the Intel® Quartus® Prime project resides must match the name field in the board_spec.xml file within the Custom Platform. The name must be case sensitive.
  5. The PATH or LD_LIBRARY_PATH environment variable must point to the MMD library in the Custom Platform.