doonny / PipeCNN

An OpenCL-based FPGA Accelerator for Convolutional Neural Networks
Apache License 2.0
1.26k stars 369 forks source link

Error message by SDAccel 2017.4 #47

Closed nslmike closed 6 years ago

nslmike commented 6 years ago
  1. It is needed to rename platform to xilinx_kcu1500_dynamic_5_0 for SDAccel 2017.4

  2. A lot of warnings like this "device/conv_pipe_xilinx.cl:680:708: warning: double precision constant requires cl_khr_fp64, casting to single precision"

  3. Finally an error message: ERROR: [XOCC 60-896] For unified platforms, please use -c or -l ERROR: [XOCC 60-598] Kernel build setup failed to complete ERROR: [XOCC 60-702] Failed to finish compilation and linking Makefile:142: recipe for target 'conv.xclbin' failed make: *** [conv.xclbin] Error 1

nslmike commented 6 years ago

I've added '-c' option before '-o' and it works.

doonny commented 6 years ago

Great. However, 2017.4 generates bad results, so we do not suggests to use this version.

nslmike commented 6 years ago

Do you talk about this error:

Executing Layer 1:

Launching single work-item kernel winbuffer

Launching single work-item kernel Conv

Launching single work-item kernel Pooling

Launching kernel MemWr with local size: 1, 1, 16  (global size: 27, 27, 96)

Launching kernel lrn with local size: 1, 1, 24  (global size: 27, 27, 24)
ERROR: ClEnqueueNDRangeKernel : CL_INVALID_WORK_GROUP_SIZE case 6
ERROR: CL_INVALID_WORK_GROUP_SIZE
Location: host/main.cpp:865
Failed to launch kernel lrn
WARNING: Profiling may contain incomplete information. Please ensure all OpenCL objects are released by your host code (e.g., clReleaseProgram()).
terminate called after throwing an instance of 'std::runtime_error'
  what():  software scheduler stopping while there are active commands
CPU emulation compute unit exited unexpectedly*** Error in `*** Error in `project/run.exe': corrupted size vs. prev_size: 0x0000000004c19ac0 ***
project/run.exe': free(): corrupted unsorted chunks: 0x0000000004c19ad0 ***
mattpcaswell commented 6 years ago

Did you ever find a solution to that error @nslmike?

Mashahed commented 5 years ago

@nslmike I am facing the same CL_INVALID_WORK_GROUP_SIZE issue. Did you find a solution?