Intel® FPGA SDK for OpenCL™ Standard Edition: Cyclone® V SoC Getting Started Guide

Download PDF
ID 683030
Date 4/20/2022
Public
Document Table of Contents
Document Table of Contents x
1. Intel® FPGA SDK for OpenCL™ Standard Edition Cyclone V SoC Getting Started Guide 2. Setting Up the Intel® FPGA SDK for OpenCL™ , Intel® SoC FPGA Embedded Design Suite, and the Cyclone V SoC Development Kit for Windows 3. Setting Up the Intel® FPGA SDK for OpenCL™ , Intel® SoC FPGA Embedded Design Suite, and the Cyclone V SoC Development Kit for Linux A. Document Revision History of the Intel® FPGA SDK for OpenCL™ Standard Edition Cyclone® V SoC Getting Started Guide
1. Intel® FPGA SDK for OpenCL™ Standard Edition Cyclone V SoC Getting Started Guide x
1.1. Prerequisites for the Intel® FPGA SDK for OpenCL™ Standard Edition 1.2. Contents of the Intel® FPGA SDK for OpenCL™ Standard Edition 1.3. Overview of the Intel® FPGA SDK for OpenCL™ Standard Edition and Cyclone® V SoC Development Kit Setup Processes 1.4. Overview of the Intel® FPGA SDK for OpenCL™ Cyclone V SoC Programming Flow 1.5. Cyclone V SoC Development Kit Reference Platform Board Variants 1.6. Cyclone V SoC FPGA-Specific OpenCL Design Considerations
2. Setting Up the Intel® FPGA SDK for OpenCL™ , Intel® SoC FPGA Embedded Design Suite, and the Cyclone V SoC Development Kit for Windows x
2.1. Upgrading to Current Version of Intel FPGA SDK for OpenCL for Cyclone® V SoC FPGA 2.2. Downloading the Intel® FPGA SDK for OpenCL™ Standard Edition 2.3. Downloading the Intel® SoC FPGA Embedded Development Suite 2.4. Installing the Intel® FPGA SDK for OpenCL™ 2.5. Setting the Intel® FPGA SDK for OpenCL™ User Environment Variables for SoC FPGA 2.6. Installing the Intel® SoC FPGA Embedded Development Suite Standard Edition 2.7. Installing the Cyclone V SoC Development Kit 2.8. Downloading an OpenCL Design Example 2.9. Creating the Hardware Configuration File of an OpenCL Kernel for SoC FPGA 2.10. Executing an OpenCL Kernel on an SoC FPGA 2.11. Uninstalling the Software
2.7. Installing the Cyclone V SoC Development Kit x
2.7.1. Writing an SD Card Image onto the Micro SD Flash Card 2.7.2. Configuring the SW3 Switches 2.7.3. Setting Up Terminal Connection 2.7.4. Setting Environment Variables and Loading OpenCL Linux Kernel Driver 2.7.5. Connecting the Board to Network via Ethernet
2.7.5. Connecting the Board to Network via Ethernet x
2.7.5.1. Ensuring IP Address Acquisition 2.7.5.2. Using SSH and SCP
2.10. Executing an OpenCL Kernel on an SoC FPGA x
2.10.1. Building the Host Application 2.10.2. Running the Host Application 2.10.3. Output from Successful Kernel Execution on the Cyclone V SoC Development Kit
3. Setting Up the Intel® FPGA SDK for OpenCL™ , Intel® SoC FPGA Embedded Design Suite, and the Cyclone V SoC Development Kit for Linux x
3.1. Upgrading to Current Version of Intel FPGA SDK for OpenCL for Cyclone® V SoC FPGA 3.2. Downloading the Intel® FPGA SDK for OpenCL™ Standard Edition 3.3. Downloading the Intel® SoC FPGA Embedded Development Suite 3.4. Installing the Intel® FPGA SDK for OpenCL™ 3.5. Setting the Intel® FPGA SDK for OpenCL™ User Environment Variables for SoC FPGA 3.6. Installing the Intel® SoC FPGA Embedded Development Suite Pro Edition 3.7. Installing the Cyclone V SoC Development Kit 3.8. Verifying Host Runtime Functionality via Emulation 3.9. Creating the Hardware Configuration File of an OpenCL Kernel for SoC FPGA 3.10. Executing an OpenCL Kernel on an SoC FPGA 3.11. Uninstalling the Software
3.7. Installing the Cyclone V SoC Development Kit x
3.7.1. Writing an SD Card Image onto the Micro SD Flash Card 3.7.2. Configuring the SW3 Switches 3.7.3. Setting Up Terminal Connection 3.7.4. Setting Environment Variables and Loading OpenCL Linux Kernel Driver 3.7.5. Connecting the Board to Network via Ethernet
3.7.5. Connecting the Board to Network via Ethernet x
3.7.5.1. Ensuring IP Address Acquisition 3.7.5.2. Mounting a Shared Drive 3.7.5.3. Using SSH and SCP
3.8. Verifying Host Runtime Functionality via Emulation x
3.8.1. Downloading an OpenCL Design Example 3.8.2. Compiling a Kernel for Emulation (-march=emulator) 3.8.3. Building the Host Application 3.8.4. Emulating Your OpenCL Kernel
3.10. Executing an OpenCL Kernel on an SoC FPGA x
3.10.1. Running the Host Application 3.10.2. Output from Successful Kernel Execution on the Cyclone V SoC Development Kit
1. Intel® FPGA SDK for OpenCL™ Standard Edition Cyclone V SoC Getting Started Guide
2. Setting Up the Intel® FPGA SDK for OpenCL™ , Intel® SoC FPGA Embedded Design Suite, and the Cyclone V SoC Development Kit for Windows
3. Setting Up the Intel® FPGA SDK for OpenCL™ , Intel® SoC FPGA Embedded Design Suite, and the Cyclone V SoC Development Kit for Linux
A. Document Revision History of the Intel® FPGA SDK for OpenCL™ Standard Edition Cyclone® V SoC Getting Started Guide

3.8.4. Emulating Your OpenCL Kernel

To emulate your OpenCL™ kernel, run the emulation .aocx file on the platform on which you built your kernel. The OpenCL Emulator uses a different OpenCL platform than when targeting FPGA hardware.

To emulate your kernel, perform the following steps:

  1. Run the utility command aocl linkflags to find out which libraries are necessary for building a host application. The software lists the libraries for both emulation and regular kernel compilation flows.
  2. Build a host application and link it to the libraries from Step 1.
    Note: To emulate multiple devices alongside other OpenCL SDKs, link your host application to the Khronos ICD Loader Library before linking it to the host runtime libraries. Link the host application to the ICD Loader Library by modifying the Makefile for the host application. Refer to Linking Your Host Application to the Khronos ICD Loader Library for more information.
  3. If necessary, move the <your_kernel_filename>.aocx file to a location where the host can find it easily, preferably the current working directory.
  4. To run the host application for emulation:
    • For Windows, first define the number of emulated devices by invoking the set CL_CONTEXT_EMULATOR_DEVICE_INTELFPGA=<number_of_devices> command and then run the host application. After you run the host application, invoke set CL_CONTEXT_EMULATOR_DEVICE_INTELFPGA= to unset the variable.
    • For Linux, invoke the env CL_CONTEXT_EMULATOR_DEVICE_INTELFPGA=<number_of_devices> <host_application_filename> command.
    This command specifies the number of identical emulation devices that the Emulator needs to provide.
    Note: When the environment variable CL_CONTEXT_EMULATOR_DEVICE_INTELFPGA is set, only the emulated devices are available, i.e., access to all physical boards is disabled.
  5. If you change your host or kernel program and you want to test it, only recompile the modified host or kernel program and then rerun emulation.
Each invocation of the emulated kernel creates a shared library copy called <process_ID>-libkernel.so in a default temporary directory, where <process_ID> is a unique numerical value assigned to each emulation run. You may override the default directory by setting the TMP or TEMP environment variable on Windows, or setting TMPDIR on Linux.
Level Two Title