Intel® Acceleration Stack for Intel® Xeon® CPU with FPGAs Release Notes

ID 683415
Date 4/11/2018

Known Issues

Table 4.  Known Issues for the Intel Acceleration Stack 1.0 Production
Known Issue Details
A different OPN is used in the design examples. The Intel® Quartus® Prime Pro Edition license uses a design example OPN of 10AX115N3F40E2SG, instead of the Intel® PAC with Intel® Arria® 10 GX FPGA OPN of 10AX115N2F40E2LG. This difference does not impact your design. The design example OPN variance will be corrected to match the platform OPN in the Intel® Acceleration Stack 1.1 version.
PCIe directed speed changes are not supported. Only automatic down-training at boot time is supported.
Virtual Function (VF) may fail to attach or detach when using the Linux* Red Hat* 3.10 kernel. This is a known issue with qemu/kvm and libvirt. Refer to the Red Hat* website for more information about this issue.
The Intel® FPGA Dynamic Profiler Tool for OpenCL* GUI reports frequency and bandwidth incorrectly. This issue will be resolved in a future version of Intel® Acceleration Stack.
fpgainfo may raise a UnicodeEncodeError when the Python* interpreter cannot determine what encoding to use. This issue typically occurs when redirecting or piping output. The fpgabist tool calls fpgainfo and is also impacted. There are two workarounds for this issue:
  • Set the PYTHONENCODING environment variable to UTF-8.
  • Modify the fpgainfo script to force the use of UTF-8:
    • Add an import codecs statement at the top of the file with the other import statements.
    • Before the line that calls args.func(args), insert this comment and code line:
      # wrap stdout with the StreamWriter that does unicode
      sys.stdout = codecs.getwriter('UTF-8')(sys.stdout)
When simulating the hello_intr_afu sample code, the af2cp_sTxPort.c1.hdr.rsvd2[5:4] has a value of X. This issue will be resolved in the Intel® Acceleration Stack 1.1 version.

Did you find the information on this page useful?

Characters remaining:

Feedback Message