Why does fpgaOpen() API fail with error message “resource busy” when it is called explicitly in a OpenCL host code? - Why does fpgaOpen() API fail with error message “resource busy” when it is called explicitly in a OpenCL host code? Description Due to the limitation that OpenCL MMD doesn't support other driver level applications to be built on top of it, you will see the error “resource busy” when you instance custom IP in OpenCL BSP design and would like to access it using fpgaOpen() API in OpenCL host code. Resolution The OpenCL MMD full code will be Open Sourced with IOFS so that customers can make the modification based on their needs. To work around this problem, you can change the fpgaOpen() code located in ccip_mmd_device.cpp as follows: from original one: fpgaOpen(afc_token, &afc_handle,0); change to: fpgaOpen(afc_token, &afc_handle, FPGA_OPEN_SHARED); Custom Fields values: ['novalue'] Troubleshooting 1507352754, 2205748806 False ['novalue'] ['FPGA Dev Tools Quartus® Prime Software Pro'] novalue 18.1 ['Programmable Logic Devices'] ['HLD Tools OpenCL'] ['novalue'] ['novalue']