Visible to Intel only — GUID: ewa1400597445683
Ixiasoft
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
Visible to Intel only — GUID: ewa1400597445683
Ixiasoft
2.7. Connecting the Memory
Calibrate the external memory IP and controllers in your Custom Platform, and connect them to the host.
- In your Custom Platform, instantiate your external memory IP based on the information in the DDR3 as Global Memory for OpenCL Applications section.
- Update the <your_custom_platform_name>/hardware/<board_name>/board_spec.xml file to reflect the modifications.
- Remove the boardtest hardware configuration file that you created during the integration of your Custom Platform with the Intel® FPGA SDK for OpenCL™ .
- Recompile the INTELFPGAOCLSDKROOT/board/custom_platform_toolkit/tests/boardtest/boardtest.cl kernel source file.
The environment variable INTELFPGAOCLSDKROOT points to the location of the SDK installation.
- Reprogram the FPGA with the new boardtest hardware configuration file and then reboot your machine.
- Modify the MMD source code to exit after checking the UniPHY status register in the function wait_for_uniphy. Rebuild the MMD software.
- Run the aocl diagnose utility command and confirm that the host reads back both the version ID and the value 0 from the uniphy_status component.
The utility should return the message Uniphy are calibrated.
- Consider using the Signal Tap logic analyzer to confirm the successful calibration of all memory controllers.
Related Information