Visible to Intel only — GUID: ewa1456172001391
Ixiasoft
1.1. Overview of the Cyclone V SoC Development Kit Reference Platform
1.2. Porting the Reference Platform to Your SoC FPGA Board
1.3. Software Support for Shared Memory
1.4. FPGA Reconfiguration
1.5. Building an SD Flash Card Image
1.6. Compiling the Linux Kernel for Cyclone V SoC FPGA
1.7. Known Issues
1.8. Document Revision History
Visible to Intel only — GUID: ewa1456172001391
Ixiasoft
1.6.2. Compiling and Installing the OpenCL Linux Kernel Driver
Compile the OpenCL™ Linux kernel driver against the compiled kernel source.
The driver source is available in the Cyclone® V SoC FPGA version of the Intel® FPGA Runtime Environment for OpenCL. In addition, ensure that you have loaded an Intel® FPGA SDK for OpenCL™ -generated .rbf file into the FPGA to prevent incorrect installation of the Linux kernel module.
- Download the Cyclone V SoC FPGA version of the Intel® FPGA Runtime Environment for OpenCL package from the Download Center on the Altera website.
- Click the Download button beside Intel® Quartus® Prime software edition.
- Specify the release version, the operating system, and the download method.
- Click the Additional Software tab, and select to download Intel® FPGA Runtime Environment for OpenCL Linux Cyclone V SoC TGZ.
- After you download the aocl-rte-<version>.arm32.tgz file, unpack it to a directory that you own.
The driver source is in the aocl-rte-<version>.arm32/board/c5soc/driver directory. - To recompile the OpenCL Linux kernel driver, set the KDIR value in the driver's Makefile to the directory containing the Linux kernel source files.
- Run the export CROSS_COMPILE=arm-linux-gnueabihf- command to indicate the prefix of your tool chain.
- Run the make clean command.
- Run the make command to create the aclsoc_drv.ko file.
- Transfer the opencl_arm32_rte directory to the Cyclone V SoC FPGA board.
Running the scp -r <path_to_opencl_arm32_rte> root@your-ip-address:<directory> command places the runtime environment in the /home/root directory.
- Run the init_opencl.sh script that you created when you built the SD card image.
- Invoke the aocl diagnose utility command. The diagnose utility will return a passing result after you run init_opencl.sh successfully.