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

Download PDF
ID 683645
Date 11/06/2017
Public
Document Table of Contents
Document Table of Contents x
1. Intel® FPGA SDK for OpenCL™ Stratix® V Network Reference Platform Porting Guide 2. Developing Your Custom Platform 3. Stratix V Network Reference Platform Design Architecture A. Document Revision History
1. Intel® FPGA SDK for OpenCL™ Stratix® V Network Reference Platform Porting Guide x
1.1. Stratix V Network Reference Platform: Prerequisites 1.2. Features of the Stratix V Network Reference Platform 1.3. Contents of the Stratix V Network Reference Platform
1.1. Stratix V Network Reference Platform: Prerequisites x
1.1.1. Legacy Board Support
2. Developing Your Custom Platform x
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
2.4. Setting up the Software Development Environment x
2.4.1. Setting Up Software Development Environment for Windows 2.4.2. Setting Up the Software Development Environment for Linux
3. Stratix V Network Reference Platform Design Architecture x
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.1. Host-FPGA Communication over PCIe x
3.1.1. Parameter Settings for PCIe Instantiation 3.1.2. PCIe Device Identification Registers 3.1.3. Version ID 3.1.4. Definitions of Hardware Constants in Software Header Files 3.1.5. PCIe Kernel Driver 3.1.6. SG-DMA
3.2. DDR3 as Global Memory for OpenCL Applications x
3.2.1. DDR3 IP Instantiation 3.2.2. DDR3 Connection to PCIe Host 3.2.3. DDR3 Connection to OpenCL Kernel
3.5. Implementation of UDP Cores as OpenCL Channels x
3.5.1. QuickUDP IP Instantiation 3.5.2. QuickUDP Configuration via PCIe-Based Host 3.5.3. QuickUDP Connection to OpenCL Kernel
3.6. FPGA System Design x
3.6.1. Clocks 3.6.2. Resets 3.6.3. Floorplan 3.6.4. Global Routing 3.6.5. Pipelining 3.6.6. Encrypted IPs
3.7. Guaranteed Timing Closure x
3.7.1. Supply the Kernel Clock 3.7.2. Guarantee Kernel Clock Timing 3.7.3. Provide a Timing-Closed Post-Fit Netlist
3.9. Connection to the Intel® FPGA SDK for OpenCL™ x
3.9.1. Describe s5_net to the Intel® FPGA SDK for OpenCL™ 3.9.2. Describe the s5_net Hardware to the Intel® FPGA SDK for OpenCL™
3.10. FPGA Programming Flow x
3.10.1. CvP 3.10.2. Flash 3.10.3. Defining the Contents of the fpga.bin File
3.10.1. CvP x
3.10.1.1. Replacing FPGA Core Logic via CvP Programming 3.10.1.2. Specifying Configuration via PCI Express Options 3.10.1.3. Base versus CvP Update Revisions in CvP Programming
3.12. OpenCL Utilities Implementation x
3.12.1. aocl install 3.12.2. aocl uninstall 3.12.3. aocl program 3.12.4. aocl flash 3.12.5. aocl diagnose 3.12.6. aocl list-devices
1. Intel® FPGA SDK for OpenCL™ Stratix® V Network Reference Platform Porting Guide
2. Developing Your Custom Platform
3. Stratix V Network Reference Platform Design Architecture
A. Document Revision History

3.3. QDRII as Heterogeneous Memory for OpenCL Applications

The OpenCL™ heterogeneous memory feature allows Intel® FPGA SDK for OpenCL™ users to take advantage of the nonuniform memory architecture in a Custom Platform.

An SDK Custom Platform groups memories with similar characteristics into a single global memory system. Each Custom Platform has a designated default global memory system. In the case of the Stratix® V Network Reference Platform, the default global memory system consists of the two DDR3 memory banks. The default global memory system must start at base address 0 from the host's perspective. Both the hardware design and the board_spec.xml file in the Custom Platform reflect this address assignment. In s5_net, the DDR global memory system is named DDR.

In addition to the DDR global memory system, the computing card that s5_net targets includes four banks of QDR memory. These four banks belong to a global memory system named QDR. SDK users can only allocate memory in the QDR global memory system using an attribute on their global memory buffers. All addressable global memory must be contiguous from the host's perspective; therefore, the QDR memory base address must start where the DDR memory ends.

For more information on the QDR UniPHY IP, refer to the QDR II and QDR IV SRAM Board Design Guidelines in Volume 2 of the External Memory Interface Handbook.

The procedure for implementing the QDR subsystem is similar to the one outlined in the Developing Your Custom Platform section. Below is a list of high-level tasks:

  1. Instantiate and parameterize the UniPHY memory controllers.
  2. Connect the UniPHY memory controllers to the host via a new OpenCL Memory Bank Divider instance.
  3. Connect the UniPHY memory controller to the UniPHY Status to AVS component.
  4. Export the UniPHY memory controller to the OpenCL kernel via clock-crossing bridges.

Below are special QDR subsystem design considerations for s5_net:

  • QDR provides separate read and write ports.

    By default, the OpenCL Memory Bank Divider produces a single bidirectional master for each memory controller. In Platform Designer (Standard), select the Separate read/write ports option to support separate read and write masters. With respect to the kernel, instantiate clock crosses and separate read and write interfaces.

  • The 275 MHz QDR afi clock and 4-to-1 multiplexing in the bank divider make it difficult to meet timing.

    To achieve timing closure robustly, open the qdr.qsys file in Platform Designer (Standard), and select the option to pipeline the outputs in the OpenCL Memory Bank Divider memory_bank_divider_1. Doing so adds a pipeline stage for each master that the bank divider creates.

Related Information
Level Two Title