Honored Contributor
New ContributorI am having the same problem - and I can provide more details. Perhaps answering my issue will help us both... I have the exact same issue: OpenCL doesn't know about my PAC card.
PLEASE help educate us about how to debug/solve this...
(I have ENVIRONMENT variables in NEXT post)...
My QUESTION: How do I debug (and solve) a “ERROR: CL_DEVICE_NOT_FOUND” for a system with a PAC card installed?
I think my issue is this: OpenCL can’t find the PAC card.
Here is an example of trying to use it:
% ~/inference_engine_samples/intel64/Release/security_barrier_camera_sample -d CPU -d_va FPGA -d_lpr CPU -i /opt/intel/computer_vision_sdk_fpga_2018.3.343/deployment_tools/demo/../demo/car_1.bmp -m /opt/intel/computer_vision_sdk_fpga_2018.3.343/deployment_tools/demo/../intel_models/vehicle-license-plate-detection-barrier-0106/FP32/vehicle-license-plate-detection-barrier-0106.xml -m_va /opt/intel/computer_vision_sdk_fpga_2018.3.343/deployment_tools/demo/../intel_models/vehicle-attributes-recognition-barrier-0039/FP32/vehicle-attributes-recognition-barrier-0039.xml -m_lpr /opt/intel/computer_vision_sdk_fpga_2018.3.343/deployment_tools/demo/../intel_models/license-plate-recognition-barrier-0001/FP32/license-plate-recognition-barrier-0001.xml
InferenceEngine:
API version ............ 1.2
Build .................. 13911
[ INFO ] Parsing input parameters
[ INFO ] Reading input
[ INFO ] Loading plugin CPU
API version ............ 1.2
Build .................. lnx_20180510
Description ....... MKLDNNPlugin
[ INFO ] Loading plugin FPGA
API version ............ 1.2
Build .................. dliaPlugin
Description ....... dliaPlugin
[ INFO ] Loading network files for VehicleDetection
[ INFO ] Batch size is forced to 1
[ INFO ] Checking Vehicle Detection inputs
[ INFO ] Checking Vehicle Detection outputs
[ INFO ] Loading Vehicle Detection model to the CPU plugin
[ INFO ] Loading network files for VehicleAttribs
[ INFO ] Batch size is forced to 1 for Vehicle Attribs
[ INFO ] Checking VehicleAttribs inputs
[ INFO ] Checking Vehicle Attribs outputs
[ INFO ] Loading Vehicle Attribs model to the FPGA plugin
ERROR: CL_DEVICE_NOT_FOUND
Location: /home/user/teamcity/work/scoring_engine_build/releases_openvino-2018-r3/thirdparty/dla/api/src/AOCL_Utils.cpp:398
Query for number of devices failed
Here is evidence that the card is plugged in (with BOARD info and everything!)…
% bwconfig --list
There are no mapped devices in your system.
% bwconfig --scan=usb
Scanning for devices
[result]: Board Type (Name), Serial, VendorID, DeviceID, USB-Address
[0]: 0x5f (A10SA4) 202101 0x2528 0x0004 0x6
% bwconfig --add=usb --result=0
Scanning for devices
[result]: Board Type (Name), Serial, VendorID, DeviceID, USB-Address
[0]: 0x5f (A10SA4) 202101 0x2528 0x0004 0x6
Device added as device "0".
% bwconfig --list
------------------------------------------------------------------------------
Name Number ID Location Status
------------------------------------------------------------------------------
A10SA4 0 202101 Local USB Device Installed (New)
I did this after trying the run, and then tried the run again… NO change, OpenCL still doesn’t see the card… see this:
% aocl diagnose
--------------------------------------------------------------------
Warning:
No devices attached for package:
/home/james/inteldevstack/intelFPGA_pro/hld/board/a10_ref
--------------------------------------------------------------------
Call "aocl diagnose <device-names>" to run diagnose for specified devices
Call "aocl diagnose all" to run diagnose for all devices
I’m wondering - is “a10_ref” appropriate for a PAC (Arria 10)? I have NO other board reference files to point to - but the name does concern me. If there are OpenCL files for the PAC card to try… I’m eager to know that.
% aocl diagnose all
(no output)
% aocl diagnose 202101
--------------------------------------------------------------------
202101 is not a valid device name.
--------------------------------------------------------------------
% aocl diagnose 0
--------------------------------------------------------------------
0 is not a valid device name.
--------------------------------------------------------------------
% aocl diagnose 1
--------------------------------------------------------------------
1 is not a valid device name.
--------------------------------------------------------------------
% aocl diagnose dev0
--------------------------------------------------------------------
dev0 is not a valid device name.
--------------------------------------------------------------------
% aocl diagnose dev1
--------------------------------------------------------------------
dev1 is not a valid device name.
