| Compilation of nlb_mode_3 AFU from source produces incorrect nlb_400.gbs output. |
- Workaround:
- Change the default setting in $OPAE_PLATFORM_ROOT/hw/samples/nlb_mode_3/hw/rtl/filelist.txt from
C:filelist_mode_0.txt
to C:filelist_mode_3.txt
- Follow the AFU compilation steps as detailed in the Accelerator Functional Unit (AFU) Developer's Guide.
- Status: This limitation will be fixed in a future version of the Intel® Acceleration Stack.
|
| The streaming_dma_afu may contain timing violations. |
- Workaround: No workaround available.
- Status: This limitation will be fixed in a future version of the Intel® Acceleration Stack.
|
| The dma_afu may access an invalid host memory address causing a Translation Layer Packet Completion Status error (TLP CPL status error). |
- The dma_afu may attempt to fetch descriptors after the driver has deallocated memory.
- Workaround: None available.
- Status: Fix targeted for a future version of the Intel® Acceleration Stack.
|
| When you test the 10Gbps Ethernet AFU in loopback mode, it loses a single packet after hot plug. |
- Workaround: Reset the Intel® FPGA Low Latency 10GbE MAC IP core before transmitting data as described in the Accelerator Functional Unit (AFU) Developer's Guide for the Intel FPGA Programmable Acceleration Card.
- Status: Fix targeted for a future version of the Intel® Acceleration Stack.
|
| After initial programming of the dma_afu subsequent partial reconfigurations may cause the kernel message to report errors. |
- You can ignore the kernel messages because they do not affect functionality of the dma_afu.
- Workaround: None available.
- Status: Fix targeted for a future version of the Intel® Acceleration Stack.
|