thanks
sujith

thanks
sujith

I would like to test Hailo-8 module with iMX8MPlus and I was wondering if you have a recommended SoM or SBC to do this?

Regards.

At this link (https://downloads.up-community.org/download/hailo-8-setup/),
it only has old version and there seems to be a download error.

Could you check the latest S/W version and access authorization to Hailo?

Thanks

*A photo of the login display:

The kit is comprised of a QCS610 module with 4GB RAM and 16GB eMMC flash and carrier board designed by VVDN Technologies, as well as e-con Systems 4K camera module, and designed to run vision machine learning and deep learning models at the edge.

https://www.youtube.com/watch?v=D7D1vne5r_U

I have no idea how to use this module, once the sim has been activated.
Can you point me to a documentation, on how to use the LTE connectivity, send data, connect to an FTP, setup a PPP, etc.

I'm working in Python3.

Thanks,

I completed installation according to
https://docs.openvinotoolkit.org/latest/_docs_install_guides_installing_openvino_linux.html#install-openvino
and successful run demo_security_barrier_camera.sh on 1. CPU 2. GPU and 3. MYRIAD* (on either Neural Stick 2 or XM 2280). * I tested them separately by unplugging one.

I proceed with the steps for the VPU installation
https://docs.openvinotoolkit.org/latest/_docs_install_guides_installing_openvino_linux_ivad_vpu.html but FAIL.

Here is the error I obtain.

root@thamml-NUC8i7BEH:/opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl# ./
bin/ etc/ include/
config/ generate_udev_rules.sh install_IVAD_VPU_dependencies.sh
drivers/ hddl-bsl/ lib/
root@thamml-NUC8i7BEH:/opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl# ./
bin/ etc/ include/
config/ generate_udev_rules.sh install_IVAD_VPU_dependencies.sh
drivers/ hddl-bsl/ lib/
root@thamml-NUC8i7BEH:/opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl# ./install_IVAD_VPU_dependencies.sh
Can't get HDDL_INSTALL_DIR env. Please source your_openvino_intall_path/openvino/bin/setupvars.sh before running.
root@thamml-NUC8i7BEH:/opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl# source /opt/intel/openvino/bin/setupvars.sh
[setupvars.sh] OpenVINO environment initialized
root@thamml-NUC8i7BEH:/opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl# ./install_IVAD_VPU_dependencies.sh
Ubuntu18.04
Reading package lists... Done
Building dependency tree
Reading state information... Done
libboost-program-options1.65.1 is already the newest version (1.65.1+dfsg-0ubuntu5).
libusb-1.0-0 is already the newest version (2:1.0.21-2).
libelf-dev is already the newest version (0.170-0.4ubuntu0.1).
libjson-c3 is already the newest version (0.12.1-1.3ubuntu0.3).
libssl1.0.0 is already the newest version (1.0.2n-1ubuntu5.4).
libudev1 is already the newest version (237-3ubuntu10.42).
The following packages were automatically installed and are no longer required:
gir1.2-geocodeglib-1.0 libegl1-mesa libfwup1 libllvm8 ubuntu-web-launchers
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Copying to /etc/udev/rules.d/98-hddlbsl.rules
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Running install for component drv_vsc
if [[ "" != "" ]]; then sudo rmmod myd_vsc; fi;
make[1]: Entering directory '/opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl/drivers/drv_vsc'
rm -f .o *.ko *.order *.mod.c *.symvers ..cmd
rm -rf .tmp_versions
make[1]: Leaving directory '/opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl/drivers/drv_vsc'
make[1]: Entering directory '/opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl/drivers/drv_vsc'
make -C /lib/modules/uname -r/build M=$PWD ccflags-y+=
make[2]: Entering directory '/usr/src/linux-headers-5.4.0-48-generic'
AR /opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl/drivers/drv_vsc/built-in.a
CC [M] /opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl/drivers/drv_vsc/myd_vsc.o
Building modules, stage 2.
MODPOST 1 modules
CC [M] /opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl/drivers/drv_vsc/myd_vsc.mod.o
LD [M] /opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl/drivers/drv_vsc/myd_vsc.ko
make[2]: Leaving directory '/usr/src/linux-headers-5.4.0-48-generic'
make[1]: Leaving directory '/opt/intel/openvino_2020.4.287/deployment_tools/inference_engine/external/hddl/drivers/drv_vsc'
mkdir -p /lib/modules/5.4.0-48-generic/kernel/drivers/myd/
cp myd_vsc.ko /lib/modules/5.4.0-48-generic/kernel/drivers/myd/myd_vsc.ko
Driver myd_vsc.ko is installed to /lib/modules/5.4.0-48-generic/kernel/drivers/myd/myd_vsc.ko
sudo depmod
modprobe: ERROR: could not insert 'myd_vsc': Operation not permitted
Makefile:74: recipe for target 'install' failed
make: *** [install] Error 1
Fail: myd_vsc don't been loaded!

Kindly advise.
Tham

Is there any way to use the AI core without (too much) touching the OpenVino kit?

Regards,
Darek

jens

For instance, I am developing the PCIe interface for an embedded processor in an FPGA, and I intend to test the FPGA - AI Core interface separately from the processor. This is to make sure things are working on this level before I make changes in my OS, which is not natively supported by OpenVino, and possibly in the toolkit itself.

For doing so, my idea is to build some basic data packages in the FPGA (e.g. load an image in the VPU) and make sure they are correctly being transmitted through the interface.

Therefore, I would need to understand how to build the instructions to be sent through the PCIe, but I have not found any documentation on it so far. Can anyone please provide me this material or give me instructions on how to get it (if it is even possible)?

I have installed OpenVino in ubuntu 16.04 system .

In lsub i have "Bus 004 Device 002: ID 03e7:2485 "

When i try some demos samples from OpenVino toolkit (latest release) and MobileNet or Yolo as network , i got the following error

• using -d MYRIAD option

" E: [xLink] [ 673769] dispatcherEventSend:934 Write failed event -7

E: [xLink] [ 675144] dispatcherEventReceive:347 dispatcherEventReceive() Read failed -4 | event 0x7efdeedaec60 XLINK_WRITE_RESP

E: [xLink] [ 675144] eventReader:233 eventReader stopped
E: [watchdog] [ 675146] sendPingMessage:132 Failed send ping message: X_LINK_ERROR
E: [xLink] [ 675148] XLinkReadDataWithTimeOut:1343 Event data is invalid
E: [ncAPI] [ 675148] ncGraphAllocate:1822 Can't read input tensor descriptors of the graph, rc: X_LINK_ERROR
"

*** using -d HDDL as device**

" [17:40:52.3660][1710]ERROR[HddlMyriadXDevice.cpp:327] Error: ncGraphAllocate() failed, device=4.1 rc=-6
[17:40:52.3663][1710]W[HddlMyriadXDevice.cpp:351]
** Suggestion: This error is probably caused by the graph allocation requires more time than the set timeout (30000 ms)
due to the large graph size 36 MB.
You can try to increase the timeout with following steps:
(1) increasing the "alloc_graph_timeout" value in $HDDL_INSTALL_DIR/hddl_service.config;
(2) kill hddldaemon: [Linux] kill -9 $(pidof hddldaemon); [Windows] kill with Windows Task Manager;
(3) restart your application again.
** OR caused by the graph used doesn't match to firmware running on MyriadX.
In this case, you need to check your network to see whether it's supported by MyriadX. "

Can you help me ? Thank you

In particular, I wonder if:

• the DISABLE and RESET pins work in synchronous or asynchronous mode? In the sencond case, is there a minimum time during which they should be active for taking effect?
• Is there any difference in terms of configuration/driver between using USB2 and PCIe configuration?

I am making such questions because I have not found anything in the documentation at the afortmentioned webpage that would specify them. In case it is available somewhere else, please let me know.

Thank you

we have an AI core module https://up-board.org/ai-edge/ai-core/ connected through PCIe to main Xeon Processor running Linux Centos.

In reality we can see Movidius MyriadX connected directly via USB to root Hub onboard :

lsusb

Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 03e7:2485 Intel Movidius MyriadX
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 006: ID 04e2:1410 Exar Corp. XR21V1410 USB-UART IC
Bus 002 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 003: ID 2c42:5114
Bus 002 Device 004: ID 0424:4050 Standard Microsystems Corp.
Bus 002 Device 002: ID 0424:2640 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

later on lsusb -t gives :
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 96, If 0, Class=Vendor Specific Class, Driver=, 480M

lsusb -v :

Bus 004 Device 096: ID 03e7:2485 Intel Movidius MyriadX
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x03e7 Intel
idProduct 0x2485 Movidius MyriadX
bcdDevice 0.01
iManufacturer 1 Movidius Ltd.
iProduct 2 Movidius MyriadX
iSerial 3 03e72485
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80

We can usually run the benchmark demo OpenVINO application without problems but we sometimes see benchmark OpenVINO demo crashing with segmentation fault or other occasions where Movidius is not enumerated.

I can now trigger the segmentation fault with 100% success by continuously launching benchmark demo and stopping it with Ctrl-C. If I stop it near the very beginning and immediately restart it, after few attempts I get the Movidius and the benchmark demo completely stuck.

here is one of the log when we get into error :

[root@xxx]# /root/inference_engine_samples_build/intel64/Release/benchmark_app -i /root/inference_engine_samples_build/intel64/Release/car.png -m /root/squeezenet1.1_FP16/squeezenet1.1.xml -d MYRIAD
[ INFO ] InferenceEngine:
API version ............ 1.6
Build .................. custom_releases/2019/R1_c9b66a26e4d65bb986bb740e73f58c6e9e84c7c2

[Step 1/8] Parsing and validation of input args
[ INFO ] Parsing input parameters
[ INFO ] Files were added: 1
[ INFO ] /root/inference_engine_samples_build/intel64/Release/car.png
Progress: [....................] 100.00% done

[Step 2/8] Loading plugin
[ INFO ]
API version ............ 1.6
Build .................. 22443
Description ....... myriadPlugin
Progress: [....................] 100.00% done

[Step 3/8] Read IR network
[ INFO ] Loading network files
[ INFO ] Network batch size: 1, precision: FP32
Progress: [....................] 100.00% done

[Step 4/8] Configure input & output of the model
[ INFO ] Preparing output blobs
Progress: [....................] 100.00% done

[Step 5/8] Loading model to the plugin
I: [ncAPI] [ 280563] ncDeviceOpen:737 ncDeviceOpen() XLinkBootRemote is running for 4.1-ma2480...

W: [ncAPI] [ 285664] ncDeviceOpen:750 ncDeviceOpen() XLinkBootRemote returned error X_LINK_COMMUNICATION_FAIL for 4.1-ma2480
E: [ncAPI] [ 253.882114] benchmark_app[2398]: segfault at 0 ip 00007f0a965fcb20 sp 00007ffe09c07968 error 4[ 300664] ncD in libc-2.17.so[7f0a964bd000+1c3000]
eviceOpen:799 Failed connection to device (4.1-ma2480) with error 5
Segmentation fault
[root@xxxt]#

At this point we have seen at least in one occasion where ProductID and manufacturer appear with "Error" on output to lsusb command regarding Movidius. But other times Movidius still looks being there in the lsusb enumerated peripherals.

Once the system is in this state it is not possible to run again benchmark test correctly even after reboot command, that issues an entire reboot of the main processor operating system.

After reboot command, Movidius is not enumerated as connected peripheral through USB and lsusb command does not list it anymore.

Of course at this point benchmark demo OpenVINO still crashes .

Only a power cycling the entire system allows to recover correct communication and allows to run again the benchmark OpenVINO demo successfully.

Do you have any suggestion or idea what we could try in order to make the system more robust and avoid this problem to occur ?

I updated to OpenVino latest version 3.1 and problem still happens
[Step 1/11] Parsing and validating input arguments
[ INFO ] Parsing input parameters
[ INFO ] Files were added: 1
[ INFO ] /root/inference_engine_samples_build/intel64/Release/car.png
[ WARNING ] -nstreams default value is determined automatically for a device. Although the automatic selection usually provides a reasonable performance,but it still may be non-optimal for some cases, for more information look at README.

[Step 2/11] Loading Inference Engine
[ INFO ] InferenceEngine:
API version ............ 2.1
Build .................. custom_releases/2019/R3_ac8584cb714a697a12f1f30b7a3b78a5b9ac5e05
Description ....... API
[ INFO ] Device info:
MYRIAD
myriadPlugin version ......... 2.1
Build ........... 32974

[Step 3/11] Reading the Intermediate Representation network
[ INFO ] Loading network files
[ INFO ] Read network took 9.01 ms
[Step 4/11] Resizing network to match image sizes and given batch
[ INFO ] Network batch size: 1, precision: FP16
[Step 5/11] Configuring input of the model
[Step 6/11] Setting device configuration
[Step 7/11] Loading the model to the device
W: [ncAPI] [ 890412] [benchmark_app] ncDeviceOpen:651 Failed to find a device, rc: X_LINK_DEVICE_NOT_FOUND
[ ERROR ] Can not init Myriad device: NC_ERROR

but with this latest version 3.1 I cannot see "segmentation fault" , however it suffers of same problem of not communicating anymore with Movidius correctly if I CTRL-C while the benchmark test is starting up.
and Myriad disappears from lsusb list :
lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 03e7:f63b Intel
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 006: ID 04e2:1410 Exar Corp. XR21V1410 USB-UART IC
Bus 002 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 003: ID 2c42:5114
Bus 002 Device 004: ID 0424:4050 Standard Microsystems Corp.
Bus 002 Device 002: ID 0424:2640 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Do you have any idea what the cause of this could be ?

thank you
Kind Regards

I know the UP AI Core X has a single onboard PCI-e USB host controller. Is this also true for the AI Core XM 2242, AI Core XM 2280, AI Vision Plus X, and AI Core XP4/XP8?

If so, are you going to release a true PCI-e accelerator now that OpenVINO supports them?

Cheers,
Mono

https://up-board.org/wp-content/uploads/ai-edge/blockdiagram_aicore-768x318.png

I use the latest version of OpenVINO toolkit(2019.1.133) to detect objects from the webcam.

But I sometimes get these error messages:
1.

E: [ncAPI] [    183032] ncDeviceOpen:799    Failed connection to device (3.1-ma2480) with error 5

2. Traceback (most recent call last):
     File "/usr/lib/python3.5/threading.py", line 914, in _bootstrap_inner
       self.run()
     File "/home/tk/DeliveryVan/openvino_inference/obstacle_detect.py", line 50, in run
       detector = ObjectDetect(detect_model=detect_model, detect_mode=detect_mode, confidence=detect_thresh)
     File "/home/tk/DeliveryVan/openvino_inference/object_detect.py", line 33, in __init__
       detector = OpenVinoDetectSSDInceptionV2(threshold=confidence)
     File "/home/tk/DeliveryVan/openvino_inference/openvino_detect_ssd_inception_v2.py", line 23, in __init__
       self.exec_net = self.plugin.load(network=net, num_requests=2)
     File "ie_api.pyx", line 395, in openvino.inference_engine.ie_api.IEPlugin.load
     File "ie_api.pyx", line 406, in openvino.inference_engine.ie_api.IEPlugin.load
   RuntimeError: Can not init USB device: NC_ERROR
   

3.

E: [xLink] [    973107] dispatcherEventReceive:368      dispatcherEventReceive() Read failed -4 | event 0x7f38f2339ee0 XLINK_READ_REL_REQ

E: [xLink] [    973107] eventReader:230 eventReader stopped
E: [xLink] [    973107] XLinkReadDataWithTimeOut:1377   Event data is invalid
E: [ncAPI] [    973107] ncFifoReadElem:3313     Packet reading is failed.
E: [watchdog] [    973222] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    974221] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    975220] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    976219] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    977219] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    978218] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    979217] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    980216] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    981215] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    982214] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    983218] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    984217] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    985217] sendPingMessage:132  Failed send ping message: X_LINK_ERROR
E: [watchdog] [    985217] watchdog_routine:327 [0x7f38ec08bbe0] device, not respond, removing from watchdog

Any idea?

but, at "Step 4. Test the installation", an error occured.

[phenomenon]

• the device could be seen as Movidius Myriad X on device manager.
• after the error occurd, the device can not be seen.

[my opinion]
*UP AI CORE X says it requires "Ubuntu" OS, but NCS2 (also Myriad X inside) supports Windows 10 OS.
So, I think there is no problem to run the device in my Windows 10 PC... Is this opition wrong ?

Best Regards.

I show a part of the Error

classification_sample.exe -i "C:\Program Files (x86)\IntelSWTools\openvino\deployment_tools\demo\car.png" -m "C:\Users(myname)\Documents\Intel\OpenVINO\openvino_models\ir\FP16\classification\squeezenet\1.1\caffe\squeezenet1.1.xml" -d MYRIAD
[ INFO ] InferenceEngine:
API version ............ 1.6
Build .................. 23224
[ INFO ] Parsing input parameters
[ INFO ] Files were added: 1
[ INFO ] C:\Program Files (x86)\IntelSWTools\openvino\deployment_tools\demo\car.png
[ INFO ] Loading plugin

API version ............ 1.6
Build .................. 23224
Description ....... myriadPlugin

[ INFO ] Loading network files:
C:\Users(myname)\Documents\Intel\OpenVINO\openvino_models\ir\FP16\classification\squeezenet\1.1\caffe\squeezenet1.1.xml
C:\Users(myname)\Documents\Intel\OpenVINO\openvino_models\ir\FP16\classification\squeezenet\1.1\caffe\squeezenet1.1.bin
[ INFO ] Preparing input blobs
[ WARNING ] Image is resized from (787, 259) to (227, 227)
[ INFO ] Batch size is 1
[ INFO ] Preparing output blobs
[ INFO ] Loading model to the plugin
[35mE: [ncAPI] [ 0] ncDeviceOpen:799 Failed connection to device (3.1-ma2480) with error 5[0m
Error

Is active cooling required or can passive cooling be implemented?
Are there thermal specs available for the chips?

I'm interested in experimenting with UP AI Core on a 3rd party SBC (e.g. Firefly RK3399 via M.2 or mPCIe interface) via standard PCIe interface.
The AI Core's product brief says x86_64 architecture is a minimum requirement.

Has anyone experimented with AI Core on ARM architecture, or any architecture other than x86_64, or know about if there any potential issues, e.g. firmware limitations?

I am developing an ALPR system which consists of IP camera and a few digital inputs and outputs. So far we use deep learning engine for both license plate detection and character recognition. Can someone suggest me a suitable hardware (processors, components and accessories) for my application. I'm a bit confuse because there are so many types of hardware here.

Thank you

I'm using the UP Square board (Celeron) and the AI Core Movidius Myriad 2 2450, which is connected via mini pci-e.

I followed the installation of ubuntu 16.04 using this guide: https://wiki.up-community.org/Ubuntu

That went smooth, I also connected the wifi module m.2, it works great.

The next step was to installing the OpenVINO toolkit, for that I used this guide: https://software.intel.com/en-us/articles/OpenVINO-Install-Linux

I'm unsure what to do to enable/install/use the Movidius mini pcie board... there is not too much documentation about it. The OpenVINO demos crash several times (perhaps due to my low ram memory 2GB).

The first demo ./demo_squeezenet_download_convert_run.sh runs well after trying the command for 3 times (it was crashing at compilation)

The second demo ./demo_security_barrier_camera.sh took me around 9 runs to finish compilation, crash after crash after crash. The first run is with the CPU, it runs a 8 FPS or less...

Then I tried using the option "-d MYRIAD" and its giving me the next error:

[ INFO ] InferenceEngine: 
    API version ............ 1.4
    Build .................. 17328
[ INFO ] Parsing input parameters
[ INFO ] Capturing video streams from the video files or loading images
[ INFO ] Files were added: 1
[ INFO ]     /opt/intel/computer_vision_sdk/deployment_tools/demo/../demo/car_1.bmp
[ INFO ] Number of input image files: 1
[ INFO ] Number of input video files: 0
[ INFO ] Number of input channels:    1
[ INFO ] Loading plugin MYRIAD

    API version ............ 1.4
    Build .................. 17328
    Description ....... myriadPlugin
[ 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 MYRIAD plugin
E: [ncAPI] [         0] ncDeviceOpen:668    failed to find device

[ ERROR ] Can not init USB device: NC_DEVICE_NOT_FOUND
Error on or near line 150; exiting with status 1

After hours of troubleshooting, I discovered that I have to manually PIP install Tensorflow 1.5 (1.7 is installed by default) before trying to MAKE the examples.

Have I missed something? The version included with the NCSDK is already 3 versions behind the current Tensorflow release, but even it doesn't actually seem compatible.

Is there any way to get the Up board working with the AI Core and the NCSDK with a more recent version of Tensorflow?

Thanks,
-jim

I am trying to make my Up AI Core work with OpenVINO Toolkit, but met with some issues.

This is a small box with Atom x5-E3940, 1.6GHz (4 Cores) & 12 Execution Units and 8GB RAM, and I installed Ubuntu 16.04 there.

I got Up AI Core hardware detected at boot time with dmesg as below:

[    2.272246] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[    2.421164] usb 3-1: New USB device found, idVendor=03e7, idProduct=2150
[    2.421259] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.421345] usb 3-1: Product: Movidius MA2X5X
[    2.421428] usb 3-1: Manufacturer: Movidius Ltd.
[    2.421510] usb 3-1: SerialNumber: 03e72150

I followed closely with guidance at https://software.intel.com/en-us/articles/OpenVINO-Install-Linux to enable user access to the mPCIe card before reboot the box.

Then I executed ./demo_security_barrier_camera.sh -d MYRIAD in folder opt/intel/computer_vision_sdk/deployment_tools/demo/. To be noticed that I executed same cmd with parameters -d GPU/CPU and got the result well already before I tried MYRIAD.

And I got error output like this:

InferenceEngine: 
    API version ............ 1.2
    Build .................. 13911
[ INFO ] Parsing input parameters
[ INFO ] Reading input
[ INFO ] Loading plugin MYRIAD

    API version ............ 1.2
    Build .................. 13911
    Description ....... myriadPlugin
[ 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 MYRIAD plugin
[ ERROR ] The plugin does not support networks with FP32 format.
Supported format: FP16.
Error on or near line 142; exiting with status 1

Anyone has a hint on how to fix this?

Thanks,

Gavin

Edited by Admin: Fixed code formatting

Specifically; PCIe voltage rails used, maximum power consumption etc...

Any information would be appreciated.

W: [         0] ncDeviceOpen:533    failed to find device

ncDeviceOpen Failed [-2]: Could not open the device.

and

E: [         0] dispatcherEventSend:730 Write failed -4

Hello NCS! Device opened normally.
Goodbye NCS!  Device Closed normally.
NCS device working.

Log of a successful run (dmesg):

[Sep19 07:29] usb 3-1: USB disconnect, device number 2
[  +0.248874] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[  +0.020071] usb 4-1: New USB device found, idVendor=03e7, idProduct=f63b
[  +0.006850] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.008001] usb 4-1: Product: VSC Loopback Device
[  +0.005103] usb 4-1: Manufacturer: Intel Corporation
[  +0.005347] usb 4-1: SerialNumber: 1FF861D5542010
[  +1.242801] usb 3-1: new high-speed USB device number 3 using xhci_hcd
[  +0.134026] usb 3-1: New USB device found, idVendor=03e7, idProduct=2150
[  +0.006821] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.007819] usb 3-1: Product: Movidius MA2X5X
[  +0.004701] usb 3-1: Manufacturer: Movidius Ltd.
[  +0.004939] usb 3-1: SerialNumber: 03e72150
[  +0.351915] xhci_hcd 0000:02:00.0: Cannot set link state.
[  +0.007609] usb usb4-port1: cannot disable (err = -32)
[  +0.005258] usb 4-1: USB disconnect, device number 2

Log of a unsuccessful run:

[  +0.250331] usb 4-1: new SuperSpeed USB device number 33 using xhci_hcd
[  +0.019707] usb 4-1: New USB device found, idVendor=03e7, idProduct=f63b
[  +0.006873] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.007885] usb 4-1: Product: VSC Loopback Device
[  +0.005087] usb 4-1: Manufacturer: Intel Corporation
[  +0.005335] usb 4-1: SerialNumber: 1FF861D5542010

It seems like when switching from USB2.0 to USB3.0 it gets stuck.
This happens both using the hello_ncs_cpp example and the python examples from the ncappzoo. After a few tries the examples start, other times (more commonly) the examples starts right away.

Notes:

• This problem emerged using both the Movidius Neural Compute Stick and the UP AI Core.
• The USB connection is provided by an internal USB hub.

What could be the possible cause of this behaviour?