Intel® Compute Stick
Discussions Regarding Intel® Compute Sticks and Cards
Announcements
All support for Intel® NUC 7 - 13 systems is transitioning to ASUS. Read more.
548 Discussions

HDDL mPCIe | devices not found when I try to run any of the demos using the option -d HDDL

Omar-AE
Beginner
1,132 Views

I have been having this issue since around a week and still have no idea how to solve it.

Here is the last part of the output I get when I run any one of the demos by running:
sudo -E ./demo_squeezenet_download_convert_run.sh -d HDDL

 

 

Run Inference Engine classification sample

Run ./classification_sample_async -d HDDL -i /opt/intel/openvino_2020.2.120/deployment_tools/demo/car.png -m /home/nvr/openvino_models/ir/public/squeezenet1.1/FP16/squeezenet1.1.xml

[ INFO ] InferenceEngine: 
	API version ............ 2.1
	Build .................. 42025
	Description ....... API
[ INFO ] Parsing input parameters
[ INFO ] Parsing input parameters
[ INFO ] Files were added: 1
[ INFO ]     /opt/intel/openvino_2020.2.120/deployment_tools/demo/car.png
[ INFO ] Creating Inference Engine
	HDDL
	HDDLPlugin version ......... 2.1
	Build ........... custom_releases/2020/2_d8830cd2bfe6199444299be1d92b281e5459f195

[ INFO ] Loading network files
[ INFO ] Preparing input blobs
[ WARNING ] Image is resized from (787, 259) to (227, 227)
[ INFO ] Batch size is 1
[ INFO ] Loading model to the device
[14:12:30.8923][24788]I[main.cpp:243] ## HDDL_INSTALL_DIR: /opt/intel/openvino_2020.2.120/deployment_tools/inference_engine/external/hddl
[14:12:30.8927][24788]I[main.cpp:245] Config file '/opt/intel/openvino_2020.2.120/deployment_tools/inference_engine/external/hddl/config/hddl_service.config' has been loaded
[14:12:30.8947][24788]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_service_alive.mutex owner: user-'no_change', group-'users', mode-'0660'
[14:12:30.8949][24788]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_service_ready.mutex owner: user-'no_change', group-'users', mode-'0660'
[14:12:30.8951][24788]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_start_exit.mutex owner: user-'no_change', group-'users', mode-'0660'
[14:12:30.8994][24788]I[AutobootStarter.cpp:156] Info: No running autoboot process. Start autoboot daemon...
[14:12:30.9794][24792]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_autoboot_alive.mutex owner: user-'no_change', group-'users', mode-'0660'
[14:12:30.9802][24792]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_autoboot_ready.mutex owner: user-'no_change', group-'users', mode-'0660'
[14:12:30.9807][24792]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_autoboot_start_exit.mutex owner: user-'no_change', group-'users', mode-'0660'
[14:12:30.9812][24792]I[FileHelper.cpp:272] Set file:/tmp/hddl_autoboot_device.map owner: user-'no_change', group-'users', mode-'0660'
[14:12:30.9838][24792]I[AutoBoot.cpp:308] [Firmware Config] deviceName=default deviceNum=0 firmwarePath=/opt/intel/openvino_2020.2.120/deployment_tools/inference_engine/external/hddl/lib/mvnc/usb-ma2x8x.mvcmd
[14:12:51.3108][24788]I[AutobootStarter.cpp:85] Info: Autoboot is running.
[14:12:51.3492][24788]I[TaskSchedulerFactory.cpp:45] Info: ## TaskSchedulerFactory ## Created Polling Task-Scheduler.
[14:12:51.3514][24788]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_snapshot.sock owner: user-'no_change', group-'users', mode-'0660'
[14:12:51.3557][24788]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_service.sock owner: user-'no_change', group-'users', mode-'0660'
[14:12:51.3564][24788]I[MessageDispatcher.cpp:87] Message Dispatcher initialization finished
[14:12:51.3567][24788]I[main.cpp:103] SERVICE IS READY ...
[14:12:51.4492][24847]I[ClientManager.cpp:159] client(id:1) registered: clientName=HDDLPlugin socket=2
[14:12:51.4813][24847]I[ClientManager.cpp:189] client(id:1) unregistered: clientName=HDDLPlugin socket=2
[ ERROR ] no devices found
Error on or near line 217; exiting with status 1

 

I tried two mPCIe boards from two different vendors: vega-300 and EDL-mPCIe-MA2485

when I run the python script hello_query_device.py, both the CPU and HDDL devices appear:

 

 

/opt/intel/openvino_2020.2.120/deployment_tools/inference_engine/samples/python/hello_query_device$ python3 hello_query_device.py 
Available devices:
	Device: CPU
	Metrics:
		AVAILABLE_DEVICES: 
		SUPPORTED_METRICS: AVAILABLE_DEVICES, SUPPORTED_METRICS, FULL_DEVICE_NAME, OPTIMIZATION_CAPABILITIES, SUPPORTED_CONFIG_KEYS, RANGE_FOR_ASYNC_INFER_REQUESTS, RANGE_FOR_STREAMS
		FULL_DEVICE_NAME:       Intel(R) Celeron(R) CPU  J1900  @ 1.99GHz
		OPTIMIZATION_CAPABILITIES: FP32, INT8, BIN
		SUPPORTED_CONFIG_KEYS: CPU_BIND_THREAD, CPU_THREADS_NUM, CPU_THROUGHPUT_STREAMS, DUMP_EXEC_GRAPH_AS_DOT, DYN_BATCH_ENABLED, DYN_BATCH_LIMIT, EXCLUSIVE_ASYNC_REQUESTS, PERF_COUNT
		RANGE_FOR_ASYNC_INFER_REQUESTS: 1, 1, 1
		RANGE_FOR_STREAMS: 1, 4

	Default values for device configuration keys:
		CPU_BIND_THREAD: YES
		CPU_THREADS_NUM: 0
		CPU_THROUGHPUT_STREAMS: 1
		DUMP_EXEC_GRAPH_AS_DOT: 
		DYN_BATCH_ENABLED: NO
		DYN_BATCH_LIMIT: 0
		EXCLUSIVE_ASYNC_REQUESTS: NO
		PERF_COUNT: NO
	Device: HDDL
	Metrics:
		AVAILABLE_DEVICES: 
		SUPPORTED_METRICS: AVAILABLE_DEVICES, SUPPORTED_METRICS, SUPPORTED_CONFIG_KEYS, FULL_DEVICE_NAME, OPTIMIZATION_CAPABILITIES, RANGE_FOR_ASYNC_INFER_REQUESTS, VPU_HDDL_DEVICE_NUM, VPU_HDDL_DEVICE_NAME, VPU_HDDL_DEVICE_THERMAL, VPU_HDDL_DEVICE_ID, VPU_HDDL_DEVICE_SUBCLASS, VPU_HDDL_DEVICE_MEMORY_TOTAL, VPU_HDDL_DEVICE_MEMORY_USED, VPU_HDDL_DEVICE_UTILIZATION, VPU_HDDL_DEVICE_TAG, VPU_HDDL_STREAM_ID
		SUPPORTED_CONFIG_KEYS: PERF_COUNT, VPU_INPUT_NORM, VPU_INPUT_BIAS, VPU_HDDL_GRAPH_TAG, VPU_HDDL_STREAM_ID, VPU_HDDL_DEVICE_TAG, VPU_HDDL_BIND_DEVICE, VPU_HDDL_RUNTIME_PRIORITY, VPU_HDDL_USE_SGAD, VPU_COPY_OPTIMIZATION, LOG_LEVEL, VPU_IGNORE_UNKNOWN_LAYERS, VPU_HW_STAGES_OPTIMIZATION, VPU_NONE_LAYERS, VPU_NUMBER_OF_SHAVES, VPU_NUMBER_OF_CMX_SLICES, VPU_HW_INJECT_STAGES, VPU_HW_POOL_CONV_MERGE, VPU_HW_STAGES_OPTIMIZATION, EXCLUSIVE_ASYNC_REQUESTS
		FULL_DEVICE_NAME: Intel Vision Accelerator Design with Intel Movidius VPUs
		OPTIMIZATION_CAPABILITIES: FP16
		RANGE_FOR_ASYNC_INFER_REQUESTS: 0, 2000, 1
		VPU_HDDL_DEVICE_NUM: 0
		VPU_HDDL_DEVICE_NAME: 
		VPU_HDDL_DEVICE_THERMAL: 
		VPU_HDDL_DEVICE_ID: 
		VPU_HDDL_DEVICE_SUBCLASS: 
		VPU_HDDL_DEVICE_MEMORY_TOTAL: 
		VPU_HDDL_DEVICE_MEMORY_USED: 
		VPU_HDDL_DEVICE_UTILIZATION: 
		VPU_HDDL_DEVICE_TAG: 
		VPU_HDDL_STREAM_ID: 

	Default values for device configuration keys:
		PERF_COUNT: 
		VPU_INPUT_NORM: 
		VPU_INPUT_BIAS: 
		VPU_HDDL_GRAPH_TAG: 
		VPU_HDDL_STREAM_ID: 
		VPU_HDDL_DEVICE_TAG: 
		VPU_HDDL_BIND_DEVICE: 
		VPU_HDDL_RUNTIME_PRIORITY: 
		VPU_HDDL_USE_SGAD: 
		VPU_COPY_OPTIMIZATION: 
		LOG_LEVEL: 
		VPU_IGNORE_UNKNOWN_LAYERS: 
		VPU_HW_STAGES_OPTIMIZATION: 
		VPU_NONE_LAYERS: 
		VPU_NUMBER_OF_SHAVES: 
		VPU_NUMBER_OF_CMX_SLICES: 
		VPU_HW_INJECT_STAGES: 
		VPU_HW_POOL_CONV_MERGE: 
		VPU_HW_STAGES_OPTIMIZATION: 
		EXCLUSIVE_ASYNC_REQUESTS: 

 

When I run lsusb, the mpcie does not appear. I have the mpcie connected to the mpcie port on the motherboard.

The demo runs successfully using the option -d CPU (intel J1900)

The demo also runs successfully using the option -d MYRIAD, as I have a neural compute stick 2 (NCS2)

I am using ubuntu 18.04

One last note: I was able to run the demo successfully on the HDDL only once, and immediately after that, I ran the same command and the same error above came back.

0 Kudos
1 Solution
IntelSupport
Community Manager
1,102 Views

Hi Omar-AE,


When you run a sample/demo with HDDL as the target device (-d HDDL) the hddldaemon will find any Intel Myriad X VPU and place them into inference mode, this will also include the Intel NCS if connected. This is the reason why you see “Can not init Myriad device: NC_ERROR”. You will need to stop the hddldaemon and run the bsl_reset (${HDDL_INSTALL_DIR}/bin/bsl_reset).


https://docs.openvinotoolkit.org/latest/_docs_install_guides_installing_openvino_linux_ivad_vpu.html#unable_to_run_inference_with_the_myriad_plugin_after_running_with_the_hddl_plugin


Also, I noticed you have a separate discussion with my peer Luis on GitHub and your issue has been resolved after doing a fresh install on a different system. Please let me know if you have any additional questions or we can proceed to close this thread as well.


Regards,

Jesus


View solution in original post

3 Replies
IntelSupport
Community Manager
1,122 Views

Hi Omar-AE,


Thanks for reaching out, could you try to reset all the Intel® Movidius™ VPUs before running the applications? Looking at the output of the hello_query application, there are no VPUs detected (VPU_HDDL_DEVICE_NUM: 0). If you could please provide the full output of the following commands.


kill -9 $(pidof hddldaemon autoboot)

pidof hddldaemon autoboot # Make sure none of them is alive

source /opt/intel/openvino/bin/setupvars.sh

${HDDL_INSTALL_DIR}/bin/bsl_reset

${HDDL_INSTALL_DIR}/bin/hddldaemon #Run on a second terminal or in the background

lsusb


Have you completed all the steps in the following link for the HDDL card?

https://docs.openvinotoolkit.org/latest/_docs_install_guides_installing_openvino_linux_ivad_vpu.html


Also, please note that there is a newer version of the OpenVINO toolkit 2020.3 available.


Regards,

Jesus



0 Kudos
Omar-AE
Beginner
1,112 Views

Hi Jesus,

Thank you for your response.

 

Yes I have completed all the steps in the link, and tried to reset intel movidius vpus following yours steps, and no change. Here is the output after killing the process:

 

nvr@nvr:~/inference_engine_samples_build/intel64/Release$ ps -ef | grep hddl
nvr       3441  3091  0 09:22 pts/3    00:00:00 grep --color=auto hddl
nvr@nvr:~/inference_engine_samples_build/intel64/Release$ pidof hddldaemon autoboot
nvr@nvr:~/inference_engine_samples_build/intel64/Release$ source /opt/intel/openvino/bin/setupvars.sh
[setupvars.sh] OpenVINO environment initialized
nvr@nvr:~/inference_engine_samples_build/intel64/Release$ ${HDDL_INSTALL_DIR}/bin/bsl_reset
Success
nvr@nvr:~/inference_engine_samples_build/intel64/Release$ ${HDDL_INSTALL_DIR}/bin/hddldaemon
[09:25:28.9769][4018]I[main.cpp:243] ## HDDL_INSTALL_DIR: /opt/intel/openvino_2020.3.194/deployment_tools/inference_engine/external/hddl
[09:25:28.9771][4018]I[main.cpp:245] Config file '/opt/intel/openvino_2020.3.194/deployment_tools/inference_engine/external/hddl/config/hddl_service.config' has been loaded
[09:25:28.9792][4018]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_service_alive.mutex owner: user-'no_change', group-'users', mode-'0660'
[09:25:28.9795][4018]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_service_ready.mutex owner: user-'no_change', group-'users', mode-'0660'
[09:25:28.9796][4018]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_start_exit.mutex owner: user-'no_change', group-'users', mode-'0660'
[09:25:28.9801][4018]I[AutobootStarter.cpp:156] Info: No running autoboot process. Start autoboot daemon...
[09:25:29.0217][4020]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_autoboot_alive.mutex owner: user-'no_change', group-'users', mode-'0660'
[09:25:29.0220][4020]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_autoboot_ready.mutex owner: user-'no_change', group-'users', mode-'0660'
[09:25:29.0221][4020]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_autoboot_start_exit.mutex owner: user-'no_change', group-'users', mode-'0660'
[09:25:29.0223][4020]I[FileHelper.cpp:272] Set file:/tmp/hddl_autoboot_device.map owner: user-'no_change', group-'users', mode-'0660'
[09:25:29.0224][4020]I[AutoBoot.cpp:308] [Firmware Config] deviceName=default deviceNum=0 firmwarePath=/opt/intel/openvino_2020.3.194/deployment_tools/inference_engine/external/hddl/lib/mvnc/usb-ma2x8x.mvcmd
[09:25:49.3348][4018]I[AutobootStarter.cpp:85] Info: Autoboot is running.
[09:25:49.3484][4018]I[TaskSchedulerFactory.cpp:45] Info: ## TaskSchedulerFactory ## Created Polling Task-Scheduler.
[09:25:49.3493][4018]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_snapshot.sock owner: user-'no_change', group-'users', mode-'0660'
[09:25:49.3499][4018]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_service.sock owner: user-'no_change', group-'users', mode-'0660'
[09:25:49.3500][4018]I[MessageDispatcher.cpp:87] Message Dispatcher initialization finished
[09:25:49.3501][4018]I[main.cpp:103] SERVICE IS READY ...
nvr@nvr:~$ lsusb
Bus 001 Device 004: ID 2c42:5114  
Bus 001 Device 027: ID 18d1:4ee3 Google Inc. Nexus 4 (tether)
Bus 001 Device 024: ID 14cd:8601 Super Top
Bus 001 Device 021: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 018: ID 14cd:8601 Super Top
Bus 001 Device 017: ID 14cd:8601 Super Top
Bus 001 Device 002: ID 8087:07e6 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 

 

When I remove the mpcie and try to run the hello_query application, the HDDL device doesn't appear. Does it mean that the mpcie is detected and the vpus are not?!

 

I have removed the previous versions and installed 2020.3 LTS.

I am also getting strange results when both the NCS2 and the mpcie are inserted:

 

nvr@nvr:~/inference_engine_samples_build/intel64/Release$ ./classification_sample_async -i /opt/intel/openvino/deployment_tools/demo/car.png -m ~/openvino_models/ir/public/squeezenet1.1/FP16/squeezenet1.1.xml -d MYRIAD
[ INFO ] InferenceEngine:
API version ............ 2.1
Build .................. 2020.3.0-3467-15f2c61a-releases/2020/3
Description ....... API
[ INFO ] Parsing input parameters
[ INFO ] Parsing input parameters
[ INFO ] Files were added: 1
[ INFO ]     /opt/intel/openvino/deployment_tools/demo/car.png
[ INFO ] Creating Inference Engine
MYRIAD
myriadPlugin version ......... 2.1
Build ........... 2020.3.0-3467-15f2c61a-releases/2020/3

[ INFO ] Loading network files
[ INFO ] Preparing input blobs
[ WARNING ] Image is resized from (787, 259) to (227, 227)
[ INFO ] Batch size is 1
[ INFO ] Loading model to the device
[ INFO ] Create infer request
[ INFO ] Start inference (10 asynchronous executions)
[ INFO ] Completed 1 async request execution
[ INFO ] Completed 2 async request execution
[ INFO ] Completed 3 async request execution
[ INFO ] Completed 4 async request execution
[ INFO ] Completed 5 async request execution
[ INFO ] Completed 6 async request execution
[ INFO ] Completed 7 async request execution
[ INFO ] Completed 8 async request execution
[ INFO ] Completed 9 async request execution
[ INFO ] Completed 10 async request execution
[ INFO ] Processing output blobs

Top 10 results:

Image /opt/intel/openvino/deployment_tools/demo/car.png

classid probability label
------- ----------- -----
817     0.6708984   sports car, sport car
479     0.1922607   car wheel
511     0.0936890   convertible
436     0.0216064   beach wagon, station wagon, wagon, estate car, beach waggon, station waggon, waggon
751     0.0075760   racer, race car, racing car
656     0.0049667   minivan
717     0.0027428   pickup, pickup truck
581     0.0019779   grille, radiator grille
468     0.0014219   cab, hack, taxi, taxicab
661     0.0008636   Model T

[ INFO ] Execution successful

[ INFO ] This sample is an API example, for any performance measurements please use the dedicated benchmark_app tool
nvr@nvr:~/inference_engine_samples_build/intel64/Release$ ./classification_sample_async -i /opt/intel/openvino/deployment_tools/demo/car.png -m ~/openvino_models/ir/public/squeezenet1.1/FP16/squeezenet1.1.xml -d HDDL
[ INFO ] InferenceEngine:
API version ............ 2.1
Build .................. 2020.3.0-3467-15f2c61a-releases/2020/3
Description ....... API
[ INFO ] Parsing input parameters
[ INFO ] Parsing input parameters
[ INFO ] Files were added: 1
[ INFO ]     /opt/intel/openvino/deployment_tools/demo/car.png
[ INFO ] Creating Inference Engine
HDDL
HDDLPlugin version ......... 2.1
Build ........... 2020.3.0-3467-15f2c61a-releases/2020/3

[ INFO ] Loading network files
[ INFO ] Preparing input blobs
[ WARNING ] Image is resized from (787, 259) to (227, 227)
[ INFO ] Batch size is 1
[ INFO ] Loading model to the device
[09:33:32.0661][2112]I[main.cpp:243] ## HDDL_INSTALL_DIR: /opt/intel/openvino_2020.3.194/deployment_tools/inference_engine/external/hddl
[09:33:32.0663][2112]I[main.cpp:245] Config file '/opt/intel/openvino_2020.3.194/deployment_tools/inference_engine/external/hddl/config/hddl_service.config' has been loaded
[09:33:32.0678][2112]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_service_alive.mutex owner: user-'no_change', group-'users', mode-'0660'
[09:33:32.0680][2112]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_service_ready.mutex owner: user-'no_change', group-'users', mode-'0660'
[09:33:32.0681][2112]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_start_exit.mutex owner: user-'no_change', group-'users', mode-'0660'
[09:33:32.0705][2112]I[AutobootStarter.cpp:156] Info: No running autoboot process. Start autoboot daemon...
[09:33:32.1178][2114]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_autoboot_alive.mutex owner: user-'no_change', group-'users', mode-'0660'
[09:33:32.1181][2114]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_autoboot_ready.mutex owner: user-'no_change', group-'users', mode-'0660'
[09:33:32.1182][2114]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_autoboot_start_exit.mutex owner: user-'no_change', group-'users', mode-'0660'
[09:33:32.1184][2114]I[FileHelper.cpp:272] Set file:/tmp/hddl_autoboot_device.map owner: user-'no_change', group-'users', mode-'0660'
[09:33:32.1188][2114]I[AutoBoot.cpp:308] [Firmware Config] deviceName=default deviceNum=0 firmwarePath=/opt/intel/openvino_2020.3.194/deployment_tools/inference_engine/external/hddl/lib/mvnc/usb-ma2x8x.mvcmd
[09:33:33.4278][2117]I[AutoBoot.cpp:197] Start boot device 1.1.1.3.1-ma2480
[09:33:33.6189][2117]I[AutoBoot.cpp:199] Device 1.1.1.3.1-ma2480 boot success, firmware=/opt/intel/openvino_2020.3.194/deployment_tools/inference_engine/external/hddl/lib/mvnc/usb-ma2x8x.mvcmd
[09:33:53.6220][2112]I[AutobootStarter.cpp:85] Info: Autoboot is running.
[09:33:53.6377][2112]W[ConfigParser.cpp:269] Warning: Cannot find key, path=scheduler_config.max_graph_per_device subclass=0, use default value: 1.
[09:33:53.6378][2112]W[ConfigParser.cpp:292] Warning: Cannot find key, path=scheduler_config.use_sgad_by_default subclass=0, use default value: false.
[09:33:53.6380][2112]I[DeviceSchedulerFactory.cpp:56] Info: ## DeviceSchedulerFacotry ## Created Squeeze Device-Scheduler2.
[09:33:53.6408][2112]I[DeviceManager.cpp:551] ## SqueezeScheduler created ##
[09:33:53.6409][2112]I[DeviceManager.cpp:649] times 0: try to create worker on device(1.1.1.3.1)
[09:33:55.6465][2112]I[DeviceManager.cpp:670] [SUCCESS] times 0: create worker on device(1.1.1.3.1)
[09:33:55.6466][2112]I[DeviceManager.cpp:719] worker(Wt1.1.1.3.1) created on device(1.1.1.3.1), type(0)
[09:33:55.6466][2112]I[DeviceManager.cpp:145] DEVICE FOUND : 1
[09:33:55.6467][2112]I[DeviceManager.cpp:146] DEVICE OPENED : 1
[09:33:55.6468][2112]I[DeviceManagerCreator.cpp:81] New device manager(DeviceManager0) created with subclass(0), deviceCount(1)
[09:33:55.6481][2112]I[TaskSchedulerFactory.cpp:45] Info: ## TaskSchedulerFactory ## Created Polling Task-Scheduler.
[09:33:55.6491][2112]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_snapshot.sock owner: user-'no_change', group-'users', mode-'0660'
[09:33:55.6500][2112]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_service.sock owner: user-'no_change', group-'users', mode-'0660'
[09:33:55.6504][2112]I[MessageDispatcher.cpp:87] Message Dispatcher initialization finished
[09:33:55.6507][2112]I[main.cpp:103] SERVICE IS READY ...
[09:33:55.7272][2258]I[ClientManager.cpp:159] client(id:1) registered: clientName=HDDLPlugin socket=2
[09:33:56.0986][2259]I[GraphManager.cpp:491] Load graph success, graphId=1 graphName=squeezenet1.1
[ INFO ] Create infer request
[ INFO ] Start inference (10 asynchronous executions)
[ INFO ] Completed 1 async request execution
[ INFO ] Completed 2 async request execution
[ INFO ] Completed 3 async request execution
[ INFO ] Completed 4 async request execution
[ INFO ] Completed 5 async request execution
[ INFO ] Completed 6 async request execution
[ INFO ] Completed 7 async request execution
[ INFO ] Completed 8 async request execution
[ INFO ] Completed 9 async request execution
[ INFO ] Completed 10 async request execution
[ INFO ] Processing output blobs

Top 10 results:

Image /opt/intel/openvino/deployment_tools/demo/car.png

classid probability label
------- ----------- -----
817     0.6708984   sports car, sport car
479     0.1922607   car wheel
511     0.0936890   convertible
436     0.0216064   beach wagon, station wagon, wagon, estate car, beach waggon, station waggon, waggon
751     0.0075760   racer, race car, racing car
656     0.0049667   minivan
717     0.0027428   pickup, pickup truck
581     0.0019779   grille, radiator grille
468     0.0014219   cab, hack, taxi, taxicab
661     0.0008636   Model T

[09:33:56.2579][2258]I[ClientManager.cpp:189] client(id:1) unregistered: clientName=HDDLPlugin socket=2
[09:33:56.2665][2259]I[GraphManager.cpp:539] graph(1) destroyed
[ INFO ] Execution successful

[ INFO ] This sample is an API example, for any performance measurements please use the dedicated benchmark_app tool
nvr@nvr:~/inference_engine_samples_build/intel64/Release$ ./classification_sample_async -i /opt/intel/openvino/deployment_tools/demo/car.png -m ~/openvino_models/ir/public/squeezenet1.1/FP16/squeezenet1.1.xml -d MYRIAD
[ INFO ] InferenceEngine:
API version ............ 2.1
Build .................. 2020.3.0-3467-15f2c61a-releases/2020/3
Description ....... API
[ INFO ] Parsing input parameters
[ INFO ] Parsing input parameters
[ INFO ] Files were added: 1
[ INFO ]     /opt/intel/openvino/deployment_tools/demo/car.png
[ INFO ] Creating Inference Engine
MYRIAD
myriadPlugin version ......... 2.1
Build ........... 2020.3.0-3467-15f2c61a-releases/2020/3

[ INFO ] Loading network files
[ INFO ] Preparing input blobs
[ WARNING ] Image is resized from (787, 259) to (227, 227)
[ INFO ] Batch size is 1
[ INFO ] Loading model to the device
[ ERROR ] Can not init Myriad device: NC_ERROR

 

And when I run hello_query_device.py, I get the following: (note the 'GNA' device appeard and VPU_HDDL_DEVICE_NUM is 1 now)

nvr@nvr:/opt/intel/openvino_2020.3.194/deployment_tools/inference_engine/samples/python/hello_query_device$ python3 hello_query_device.py
Available devices:
Device: CPU
Metrics:
AVAILABLE_DEVICES:
SUPPORTED_METRICS: AVAILABLE_DEVICES, SUPPORTED_METRICS, FULL_DEVICE_NAME, OPTIMIZATION_CAPABILITIES, SUPPORTED_CONFIG_KEYS, RANGE_FOR_ASYNC_INFER_REQUESTS, RANGE_FOR_STREAMS
FULL_DEVICE_NAME:       Intel(R) Celeron(R) CPU  J1900  @ 1.99GHz
OPTIMIZATION_CAPABILITIES: FP32, INT8, BIN
SUPPORTED_CONFIG_KEYS: CPU_BIND_THREAD, CPU_THREADS_NUM, CPU_THROUGHPUT_STREAMS, DUMP_EXEC_GRAPH_AS_DOT, DYN_BATCH_ENABLED, DYN_BATCH_LIMIT, EXCLUSIVE_ASYNC_REQUESTS, PERF_COUNT
RANGE_FOR_ASYNC_INFER_REQUESTS: 1, 1, 1
RANGE_FOR_STREAMS: 1, 4

Default values for device configuration keys:
CPU_BIND_THREAD: YES
CPU_THREADS_NUM: 0
CPU_THROUGHPUT_STREAMS: 1
DUMP_EXEC_GRAPH_AS_DOT:
DYN_BATCH_ENABLED: NO
DYN_BATCH_LIMIT: 0
EXCLUSIVE_ASYNC_REQUESTS: NO
PERF_COUNT: NO
Device: GNA
Metrics:
SUPPORTED_METRICS: SUPPORTED_METRICS, FULL_DEVICE_NAME, SUPPORTED_CONFIG_KEYS, AVAILABLE_DEVICES
FULL_DEVICE_NAME: GNA_SW
SUPPORTED_CONFIG_KEYS: EXCLUSIVE_ASYNC_REQUESTS, GNA_COMPACT_MODE, GNA_DEVICE_MODE, GNA_FIRMWARE_MODEL_IMAGE, GNA_FIRMWARE_MODEL_IMAGE_GENERATION, GNA_LIB_N_THREADS, GNA_PRECISION, GNA_PWL_UNIFORM_DESIGN, GNA_SCALE_FACTOR, PERF_COUNT, SINGLE_THREAD
AVAILABLE_DEVICES: GNA_SW

Default values for device configuration keys:
EXCLUSIVE_ASYNC_REQUESTS: NO
GNA_COMPACT_MODE: NO
GNA_DEVICE_MODE: GNA_AUTO
GNA_FIRMWARE_MODEL_IMAGE:
GNA_FIRMWARE_MODEL_IMAGE_GENERATION:
GNA_LIB_N_THREADS: 1
GNA_PRECISION: I8
GNA_PWL_UNIFORM_DESIGN: YES
GNA_SCALE_FACTOR: 1.0
PERF_COUNT: NO
SINGLE_THREAD: YES
Device: HDDL
Metrics:
AVAILABLE_DEVICES:
SUPPORTED_METRICS: AVAILABLE_DEVICES, SUPPORTED_METRICS, SUPPORTED_CONFIG_KEYS, FULL_DEVICE_NAME, OPTIMIZATION_CAPABILITIES, RANGE_FOR_ASYNC_INFER_REQUESTS, VPU_HDDL_DEVICE_NUM, VPU_HDDL_DEVICE_NAME, VPU_HDDL_DEVICE_THERMAL, VPU_HDDL_DEVICE_ID, VPU_HDDL_DEVICE_SUBCLASS, VPU_HDDL_DEVICE_MEMORY_TOTAL, VPU_HDDL_DEVICE_MEMORY_USED, VPU_HDDL_DEVICE_UTILIZATION, VPU_HDDL_DEVICE_TAG, VPU_HDDL_STREAM_ID
SUPPORTED_CONFIG_KEYS: PERF_COUNT, VPU_INPUT_NORM, VPU_INPUT_BIAS, VPU_HDDL_GRAPH_TAG, VPU_HDDL_STREAM_ID, VPU_HDDL_DEVICE_TAG, VPU_HDDL_BIND_DEVICE, VPU_HDDL_RUNTIME_PRIORITY, VPU_HDDL_USE_SGAD, VPU_COPY_OPTIMIZATION, LOG_LEVEL, VPU_IGNORE_UNKNOWN_LAYERS, VPU_HW_STAGES_OPTIMIZATION, VPU_NONE_LAYERS, VPU_NUMBER_OF_SHAVES, VPU_NUMBER_OF_CMX_SLICES, VPU_HW_INJECT_STAGES, VPU_HW_POOL_CONV_MERGE, VPU_HW_STAGES_OPTIMIZATION, EXCLUSIVE_ASYNC_REQUESTS
FULL_DEVICE_NAME: Intel Vision Accelerator Design with Intel Movidius VPUs
OPTIMIZATION_CAPABILITIES: FP16
RANGE_FOR_ASYNC_INFER_REQUESTS: 4, 150, 1
VPU_HDDL_DEVICE_NUM: 1
VPU_HDDL_DEVICE_NAME: 1.1.1.3.1
VPU_HDDL_DEVICE_THERMAL: 63.561153411865234
VPU_HDDL_DEVICE_ID: 0
VPU_HDDL_DEVICE_SUBCLASS: 0
VPU_HDDL_DEVICE_MEMORY_TOTAL: 483
VPU_HDDL_DEVICE_MEMORY_USED: 0
VPU_HDDL_DEVICE_UTILIZATION: 0.0
VPU_HDDL_DEVICE_TAG:
VPU_HDDL_STREAM_ID:

Default values for device configuration keys:
PERF_COUNT:
VPU_INPUT_NORM:
VPU_INPUT_BIAS:
VPU_HDDL_GRAPH_TAG:
VPU_HDDL_STREAM_ID:
VPU_HDDL_DEVICE_TAG:
VPU_HDDL_BIND_DEVICE:
VPU_HDDL_RUNTIME_PRIORITY:
VPU_HDDL_USE_SGAD:
VPU_COPY_OPTIMIZATION:
LOG_LEVEL:
VPU_IGNORE_UNKNOWN_LAYERS:
VPU_HW_STAGES_OPTIMIZATION:
VPU_NONE_LAYERS:
VPU_NUMBER_OF_SHAVES:
VPU_NUMBER_OF_CMX_SLICES:
VPU_HW_INJECT_STAGES:
VPU_HW_POOL_CONV_MERGE:
VPU_HW_STAGES_OPTIMIZATION:
EXCLUSIVE_ASYNC_REQUESTS:


And when I remove the NCS2, both MYRIAD and HDDL don't work.

Is it detecting the NCS2 as an mpcie?!

Could it be a hardware issue?

@IntelSupport 

0 Kudos
IntelSupport
Community Manager
1,103 Views

Hi Omar-AE,


When you run a sample/demo with HDDL as the target device (-d HDDL) the hddldaemon will find any Intel Myriad X VPU and place them into inference mode, this will also include the Intel NCS if connected. This is the reason why you see “Can not init Myriad device: NC_ERROR”. You will need to stop the hddldaemon and run the bsl_reset (${HDDL_INSTALL_DIR}/bin/bsl_reset).


https://docs.openvinotoolkit.org/latest/_docs_install_guides_installing_openvino_linux_ivad_vpu.html#unable_to_run_inference_with_the_myriad_plugin_after_running_with_the_hddl_plugin


Also, I noticed you have a separate discussion with my peer Luis on GitHub and your issue has been resolved after doing a fresh install on a different system. Please let me know if you have any additional questions or we can proceed to close this thread as well.


Regards,

Jesus


Reply