Intel® Distribution of OpenVINO™ Toolkit
Community assistance about the Intel® Distribution of OpenVINO™ toolkit, OpenCV, and all aspects of computer vision-related on Intel® platforms.
6404 Discussions

Up Squared with UP AI Core X not working

breschi__iacopo
Beginner
‎08-06-2019 10:19 AM
872 Views

Dear all thanks for your time,

Setup : 

  • Up Squared
  • Intel® Pentium® Processor N4200
  • UP AI Core X with the Myriad 2485
  • Ubuntu 18.04.2 LTS
  • linux 4.15.0-55-generic

I'm trying to install the Version 2019_R2 on the card, so I just followed:

The demo on CPU work correctly.

But neither on MYRIAD nor the HDDL work. It seems like the chip is not recognized by the OS.

 

The MYRIAD test:

###################################################

Run Inference Engine classification sample

Run ./classification_sample_async -d MYRIAD -i /opt/intel/openvino/deployment_tools/demo/car.png -m /home/deepo/openvino_models/ir/FP16//classification/squeezenet/1.1/caffe/squeezenet1.1.xml

[ INFO ] InferenceEngine:
        API version ............ 2.0
        Build .................. custom_releases/2019/R2_f5827d4773ebbe727c9acac5f007f7d94dd4be4e
        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.0
        Build ........... 27579

[ 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
Error on or near line 238; exiting with status 1

The HDDL test:

###################################################

Run Inference Engine classification sample

Run ./classification_sample_async -d HDDL -i /opt/intel/openvino/deployment_tools/demo/car.png -m /home/deepo/openvino_models/ir/FP16//classification/squeezenet/1.1/caffe/squeezenet1.1.xml 

[ INFO ] InferenceEngine: 
        API version ............ 2.0
        Build .................. custom_releases/2019/R2_f5827d4773ebbe727c9acac5f007f7d94dd4be4e
        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.0
        Build ........... 27579

[ INFO ] Loading network files
[17:10:46.5933][5128]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_autoboot_ready.mutex owner: user-'no_change', group-'users', mode-'0660'
[17:10:46.5934][5128]I[FileHelper.cpp:272] Set file:/var/tmp/hddl_autoboot_start_exit.mutex owner: user-'no_change', group-'users', mode-'0660'
[17:10:46.5935][5128]I[FileHelper.cpp:272] Set file:/tmp/hddl_autoboot_device.map owner: user-'no_change', group-'users', mode-'0660'
[17:10:46.5936][5128]I[AutoBoot.cpp:300] [Firmware Config] deviceName=default deviceNum=0 firmwarePath=/opt/intel/openvino_2019.2.242/deployment_tools/inference_engine/external/hddl/lib/mvnc/MvNCAPI-ma2x8x.mvcmd
 Config file detected at /opt/intel/openvino_2019.2.242/deployment_tools/inference_engine/external/hddl/config/bsl.json
[ion_close][69]close ion_fd = 3
[17:10:47.5840][5126]I[AutobootStarter.cpp:78] Info: Service has been waiting for Autoboot to boot up for 1 seconds ...                                                                                   [0/18126]
[17:10:48.5867][5126]I[AutobootStarter.cpp:78] Info: Service has been waiting for Autoboot to boot up for 2 seconds ...
[17:10:49.5886][5126]I[AutobootStarter.cpp:78] Info: Service has been waiting for Autoboot to boot up for 3 seconds ...
[17:11:16.6564][5126]W[AutobootStarter.cpp:98] 
      ** Suggestion: The timeout by default is 10 seconds, and you can increase it by following steps:                                                                                                             
            (1) Add following entry in $HDDL_INSTALL_DIR/config/hddl_service.config like this:                                                                                                                     
                   "service_settings":                                                                                                                                                                             
                   {                                                                                                                                                                                               
                     "autoboot_boot_timeout_sec":   10,                                                                                                                                                            
                      ...                                                                                                                                                                                          
                   }                                                                                                                                                                                               
            (2) Change the '10' to a larger value to increase the time out window, then try again.                                                                                                                 
                                                                                                                                                                                                                   
[17:11:16.6565][5126]ERROR[AutobootStarter.cpp:48] Error: Failed to start autoboot
[17:11:16.6565][5126]ERROR[main.cpp:76] Error: Start Service failed due to autoboot failure
[ion_close][69]close ion_fd = 3

 

Can you help me to figure out where I'm making a mistake ?

Thanks!!

 

 

0 Kudos

Link Copied

5 Replies
Shubha_R_Intel
Employee
‎08-07-2019 11:15 AM
872 Views

Dear breschi, iacopo,

you probably need to revisit the details of the below doc:

https://docs.openvinotoolkit.org/latest/_docs_install_guides_installing_openvino_linux.html#additional-NCS-steps

Or maybe just reboot if you really performed all HDDL installation steps.

Hope it helps,

Thanks,

Shubha

 

0 Kudos
Copy link
breschi__iacopo
Beginner
‎08-07-2019 01:06 PM
872 Views

Dear Shubha,

many thanks for your reply. It's three days that I'm stuck on this problem and it's very frustrating.

Your advice is interesting. Should I really follow the additional-NCS-steps even if I have the mini pcie card?

Anyway I followed the doc many times installing, uninstalling and reinstalling. Rebooted numerous times, checked every step but unfortunately without success. Here follow few logs of my system, I hope you can help me debug a little! THANKS

This are my usb devices:

lsusb 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Here the top part of lspci:

lspci 
00:00.0 Host bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Graphics Controller (rev 0b)
00:0e.0 Multimedia audio controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster (rev 0b)
00:0f.0 Communication controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Trusted Execution Engine (rev 0b)
00:11.0 Unclassified device [0050]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated Sensor Hub (rev 0b)
00:12.0 SATA controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller (rev 0b)
00:13.0 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 (rev fb)      <--- Behind this one I think should be the pcie card with the Myriad
00:13.1 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #2 (rev fb)
00:13.2 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #3 (rev fb)
00:13.3 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #4 (rev fb)
00:14.0 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 (rev fb)
00:14.1 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #2 (rev fb)
00:15.0 USB controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI (rev 0b)
00:15.1 USB controller: Intel Corporation Device 5aaa (rev 0b)

I'm thinking that the OS is having problem to talk to the card. I have this series of logs in the dmesg on the usb3 that I suppose being the one connected to the pci card. 

[    2.575378] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.577469] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.579512] usb usb3: Product: xHCI Host Controller 
[    2.581550] usb usb3: Manufacturer: Linux 4.15.0-55-generic xhci-hcd
[    2.583604] usb usb3: SerialNumber: 0000:01:00.0
[    2.928065] usb 3-1: new full-speed USB device number 2 using xhci_hcd
[    2.929352] usb 3-1: Device not responding to setup address.
[    3.136610] usb 3-1: Device not responding to setup address.
[    3.344282] usb 3-1: device not accepting address 2, error -71
[    3.472284] usb 3-1: new full-speed USB device number 3 using xhci_hcd
[    3.474243] usb 3-1: Device not responding to setup address.
[    3.680564] usb 3-1: Device not responding to setup address.
[    3.888178] usb 3-1: device not accepting address 3, error -71
[    3.888267] usb usb3-port1: attempt power cycle 
[    4.540025] usb 3-1: new full-speed USB device number 4 using xhci_hcd
[    4.668026] usb 3-1: device descriptor read/64, error -71
[    4.904485] usb 3-1: device descriptor read/64, error -71
[    5.140284] usb 3-1: new full-speed USB device number 5 using xhci_hcd
[    5.268568] usb 3-1: device descriptor read/64, error -71
[    5.504577] usb 3-1: device descriptor read/64, error -71
[    5.612388] usb usb3-port1: unable to enumerate USB device:

I tried many things to solve usb error -71, such as setting in the grub to the following line, but nothing changed.

GRUB_CMDLINE_LINUX_DEFAULT="usbcore.autosuspend=-1 usbcore.old_scheme_first=y"

Maybe Ubuntu 18.04 is conflicting somehow. What do you think? 

Thanks again for the help!

0 Kudos
Copy link
Shubha_R_Intel
Employee
‎08-07-2019 02:42 PM
872 Views

Dear breschi, iacopo,

Ubuntu 18 could indeed be the issue. Please see Jesus's response to this IDZ post .Please study the workaround Jesus suggests.  I guess that the OS can't find the drivers.

The workaround is to extract package intel-openvino-ie-rt-vpu-ubuntu-bionic-2019.1.094-2019.1-094.x86_64.rpm manually. 

Hope it helps.

Thanks,

Shubha

0 Kudos
Copy link
breschi__iacopo
Beginner
‎08-08-2019 06:20 AM
872 Views

Dear Shubha,

thanks for your help.

I already tried to check if the rpm was correctly extracted, and it was.

I was desperate so I bought a new Movidious pcie card. I plugged into my up2board and now it's working! I really think it was an hardware problem.

For record here few logs:

As you can see now the usb 3-1 is able to recognize the card. Here my dmesg:

[    2.514846] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.514858] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.514867] usb usb3: Product: xHCI Host Controller
[    2.514874] usb usb3: Manufacturer: Linux 4.15.0-55-generic xhci-hcd
[    2.514882] usb usb3: SerialNumber: 0000:01:00.0
[    2.860068] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[    2.885285] usb 3-1: New USB device found, idVendor=03e7, idProduct=2150    <--------- Good
[    2.885291] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.885296] usb 3-1: Product: Movidius MA2X5X
[    2.885299] usb 3-1: Manufacturer: Movidius Ltd.
[    2.885302] usb 3-1: SerialNumber: 03e72150
[    8.053229] usbcore: registered new interface driver myriad_usb_vsc
[  500.562932] usb 3-1: USB disconnect, device number 2
[  502.674870] usb 3-1: new high-speed USB device number 3 using xhci_hcd
[  502.695476] usb 3-1: New USB device found, idVendor=03e7, idProduct=2150
[  502.695480] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  502.695482] usb 3-1: Product: Movidius MA2X5X
[  502.695484] usb 3-1: Manufacturer: Movidius Ltd.
[  502.695486] usb 3-1: SerialNumber: 03e72150

 

when before I had:

[    2.575378] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    2.577469] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.579512] usb usb3: Product: xHCI Host Controller 
[    2.581550] usb usb3: Manufacturer: Linux 4.15.0-55-generic xhci-hcd
[    2.583604] usb usb3: SerialNumber: 0000:01:00.0
[    2.928065] usb 3-1: new full-speed USB device number 2 using xhci_hcd
[    2.929352] usb 3-1: Device not responding to setup address.        <---------  Bad
[    3.136610] usb 3-1: Device not responding to setup address.
[    3.344282] usb 3-1: device not accepting address 2, error -71

 

Thanks again and regards

 

 

 

0 Kudos
Copy link
Shubha_R_Intel
Employee
‎08-08-2019 11:25 AM
872 Views

Dearest breschi, iacopo,

I certainly understand that feeling of desperation ! I have been there before too ! But I'm super glad you finally got it working. Thanks so much for sharing your success with the OpenVino community !

Shubha

 

0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.