Forum Discussion
OpenCL Compiler Local Memory Address Space Splitter fails
- 7 years ago
Thank you for your reply, AKert. It is great to hear that my report is of some value. Meanwhile, I have found that the issue seems to be caused by reading from global memory and writing to an Intel FPGA channel in a single statement. When replacing
UTL_WRITE_CH(ch_1, data1[j]); UTL_WRITE_CH(ch_2, buf_d2[i]);with (make sure to use the actual types)
const my_type1 temp1 data1[j] UTL_WRITE_CH(ch_1, temp1); const my_type2 temp2 buf_d2[i] UTL_WRITE_CH(ch_2, temp2);the error goes away. It may or may not be related to also using char (8 bits) buffers.
Thanks for your reply! Unfortunately I cannot use the 18.0 SDK as there is no 18.0 BSP for the Terasic DE1-SoC available yet. Maybe I could try an older version and see if it has the same issue or not. However, I would have to re-write large parts of the design that make use of features introduced in recent versions of the SDK.
Is there any chance Intel employees are going to see this message and provide a brief explanation what could be causing the crash? At least the call stack and error message could give them a hint and allow them to help me narrow down the possible reasons.