Intel® FPGA SDK for OpenCL™: Stratix® V Network Reference Platform Porting Guide
ID
683645
Date
11/06/2017
Public
2.1. Initializing Your Custom Platform
2.2. Removing Unused Hardware
2.3. Integrating Your Custom Platform with the Intel® FPGA SDK for OpenCL™
2.4. Setting up the Software Development Environment
2.5. Building the Software in Your Custom Platform
2.6. Establishing Host Communication
2.7. Connecting the Memory
2.8. Integrating an OpenCL Kernel
2.9. Programming Your FPGA Quickly Using CvP
2.10. Guaranteeing Timing Closure
2.11. Troubleshooting
3.1. Host-FPGA Communication over PCIe
3.2. DDR3 as Global Memory for OpenCL Applications
3.3. QDRII as Heterogeneous Memory for OpenCL Applications
3.4. Host Connection to OpenCL Kernels
3.5. Implementation of UDP Cores as OpenCL Channels
3.6. FPGA System Design
3.7. Guaranteed Timing Closure
3.8. Addition of Timing Constraints
3.9. Connection to the Intel® FPGA SDK for OpenCL™
3.10. FPGA Programming Flow
3.11. Host-to-Device MMD Software Implementation
3.12. OpenCL Utilities Implementation
3.13. Stratix V Network Reference Platform Implementation Considerations
3.9.1. Describe s5_net to the Intel® FPGA SDK for OpenCL™
The board_env.xml file describes a Custom Platform to the Intel® FPGA SDK for OpenCL™ . Details of each field in the board_env.xml file is available in the Creating the board_env.xml File section of the Intel® FPGA SDK for OpenCL™ Custom Platform Toolkit User Guide .
In the Stratix® V Network Reference Platform, Intel® uses the bin directory for Windows dynamic link libraries, lib directory for delivering libraries, and libexec directory for delivering the SDK utility executables. This directory structure allows the PATH environment variable to point to the location of the dynamic link libraries (that is, bin) in isolation of the SDK utility executables.
The s5_net Reference Platform also supplies an end-user API for UDP initialization. The header in the <path_to_s5_net>/include/aocl_net.h file provides this API. The compileflags element in the board_env.xml file points the compiler to this directory when the SDK user invokes the aocl compile-config utility command to derive compiler arguments.
Related Information