Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
17041 Discussions

OpenCL issue on Angstrom custom build for DE1-SoC

Altera_Forum
Honored Contributor II
1,128 Views

Hi, all! 

 

Could you help me to solve the following issue. 

 

I am trying to launch OpenCL examples on Angstrom custom build for DE1-SoC. 

The version of OpenCL SDK, Quartus and other tools is 16.1 

Firstly I've built vector_add example and successfully launch it on standard Angstrom image (3.12 ltsi kernel) for DE1-Soc 

 

Then I created Angstrom 2015 with 4.2 kernel according to these instructions: https://rocketboards.org/foswiki/view/documentation/angstromonsocfpga_1 

I copied kernel, rootfs and dts files created be Angstrom to sdcard as recommended here: https://rocketboards.org/foswiki/view/documentation/gsrd131sdcard#updating_individual_elements_on_the_sd_card 

Angstrom Linux launched successfully. 

After that I downloaded OpenCL RTE for 16.1 version and compiled OpenCL driver for new 4.2 kernel. After running opencl_init.sh driver loaded successfully. 

 

aocl diagnostic also finished with success: 

 

aocl diagnose: running diagnostic from /home/root/aocl-rte-16.1.0-1.arm32/board/c5soc/arm32/bin 

 

verified that the kernel mode driver is installed on the host machine. 

 

using platform: intel(r) fpga sdk for opencl(tm) 

board vendor name: intel(r) corporation 

board name: de1soc_sharedonly : cyclone v soc development kit 

 

buffer read/write test passed. 

 

diagnostic_passed 

 

 

Then I slightly change and recompile examples (change platform name from Altera to Intel). 

 

Unfortunately for this new configuration examples hangs. 

 

Result of launching hello_world example: 

 

querying platform for info: 

========================== 

cl_platform_name = intel(r) fpga sdk for opencl(tm) 

cl_platform_vendor = altera corporation 

cl_platform_version = opencl 1.0 intel(r) fpga sdk for opencl(tm), version 16.1 

 

querying device for info: 

======================== 

cl_device_name = de1soc_sharedonly : cyclone v soc development kit 

cl_device_vendor = intel(r) corporation 

cl_device_vendor_id = 4466 

cl_device_version = opencl 1.0 intel(r) fpga sdk for opencl(tm), version 16.1 

cl_driver_version = 16.1 

cl_device_address_bits = 64 

cl_device_available = true 

cl_device_endian_little = true 

cl_device_global_mem_cache_size = 32768 

cl_device_global_mem_cacheline_size = 0 

cl_device_global_mem_size = 536870912 

cl_device_image_support = true 

cl_device_local_mem_size = 16384 

cl_device_max_clock_frequency = 1000 

cl_device_max_compute_units = 1 

cl_device_max_constant_args = 8 

cl_device_max_constant_buffer_size = 134217728 

cl_device_max_work_item_dimensions = 3 

cl_device_max_work_item_dimensions = 8192 

cl_device_min_data_type_align_size = 1024 

cl_device_preferred_vector_width_char = 4 

cl_device_preferred_vector_width_short = 2 

cl_device_preferred_vector_width_int = 1 

cl_device_preferred_vector_width_long = 1 

cl_device_preferred_vector_width_float = 1 

cl_device_preferred_vector_width_double = 0 

command queue out of order? = false 

command queue profiling enabled? = true 

using aocx: hello_world.aocx 

reprogramming device [0] with handle 1 

 

kernel initialization is complete. 

launching the kernel... (after this line program hangs) 

 

 

Result of launching vector_add example: 

 

initializing opencl 

platform: intel(r) fpga sdk for opencl(tm) 

using 1 device(s) 

de1soc_sharedonly : cyclone v soc development kit 

using aocx: vectoradd.aocx 

reprogramming device [0] with handle 1 

launching for device 0 (1000000 elements) (after this line program hangs) 

 

I tried took top.rbf file created by OPenCL SDK for hello_world example, rename this file to opencl.rbf and exchange this file with original one on my sdcard. It is not help. 

 

Could you help me to solve this issue or recommend the way for debugging the system?
0 Kudos
0 Replies
Reply