Error - Could not open NCS device.

idata · ‎05-10-2018

Hello movidius friends!

I have a problem with my new fancy movidius, I can run it in my personal computer (macbook air) using a virtualbox following the install instructions and in a raspberry pi 3.

But in my work computer (Ubuntu 16.04) I get the:

Error - Could not open NCS device.

dmesg give me the following message :

[609776.694043] usb 3-3: new high-speed USB device number 16 using xhci_hcd
[609776.834588] usb 3-3: New USB device found, idVendor=03e7, idProduct=2150
[609776.834590] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[609776.834591] usb 3-3: Product: Movidius MA2X5X
[609776.834592] usb 3-3: Manufacturer: Movidius Ltd.
[609776.834593] usb 3-3: SerialNumber: 03e72150

lsusb give me the following message:

Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
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 016: ID 03e7:2150  
Bus 003 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 003 Device 002: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I also have tried to install a virtual box with Ubuntu 16.04 inside my Ubuntu and the curious thing is that the movidius don't appear in the devices-usb bar menu while in the macbook it appear.

I am with the last ncsdk version.

Hope you can help me.

Thanks!

idata · ‎05-10-2018

@fdnn It looks like your Ubuntu 16.04 machine sees the NCS device initially. In case you didn't know, the NCS device initially enumerates as a USB 2 device. When the device is used via the API, the NCS device re-enumerates as a USB 3 device. After doing it's work, it re-enumerates as a USB 2 device at idle. It looks like the device is able to enumerate as a USB 2 device.

Can you provide more information about your machine and instructions to reproduce the issue you faced (which app did you run?).

To test if your NCS device can enumerate as a USB 3 device, please try the following:

Unplug your NCS from your NCS machine.

Try clearing your dmesg log using : sudo dmesg -C.

Then plug in the NCS device and run hello_ncs_py using the following command inside of the ncsdk/examples/apps/hello_ncs_py: python3 hello_ncs.py.

Then run dmesg again and post the log back here.

idata · ‎05-11-2018

Hello @Tome_at_Intel the output is the following while running hello_ncs.py:

[690845.554975] usb 3-3: new high-speed USB device number 17 using xhci_hcd
[690845.699499] usb 3-3: New USB device found, idVendor=03e7, idProduct=2150
[690845.699501] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[690845.699502] usb 3-3: Product: Movidius MA2X5X
[690845.699503] usb 3-3: Manufacturer: Movidius Ltd.
[690845.699503] usb 3-3: SerialNumber: 03e72150

idata · ‎05-11-2018

@fdnn Since the NCS device was working on your other machines, I assume that your NCS device is in working condition. I have a few questions, are you using a USB hub? If you are running it through a USB hub and if you aren't already using a powered hub, can you try using a powered hub? Try using a different USB port and see if you can isolate the issue.

idata · ‎10-17-2018

Hi @Tome_at_Intel

I am also facing same error as when i do "make run" for apps/hello_ncs_cpp"

"Error - Could not open NCS device.

mvncStatus value: -2"

Setup: Virtualbox with Ubuntu 16.04, no USB hub used

Dmesg cleared before NCS plugged

5940.168142] usb 1-1: new high-speed USB device number 11 using ehci-pci

[ 5940.340261] usb 1-1: New USB device found, idVendor=03e7, idProduct=2150

[ 5940.340263] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 5940.340264] usb 1-1: Product: Movidius MA2X5X

[ 5940.340266] usb 1-1: Manufacturer: Movidius Ltd.

[ 5940.340266] usb 1-1: SerialNumber: 03e72150

[ 5965.228555] usb 1-1: USB disconnect, device number 11

idata · ‎10-22-2018

@Vunny Unfortunately there is a device re-enumeration bug with the NCSDK 2 and VM that we are working on at the moment. I'll let you know as soon as we figure out a solution. Thanks for reporting this.

idata · ‎11-29-2018

@Tome_at_Intel Excuse me~ I am now using the latest NCSDK 2 and Docker , the same problem happened. Ubuntu 16.04

root@dengta-XPS-8700:/ncsdk# lsusb -t

/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M

/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M

|** Port 2: Dev 26, If 0, Class=Vendor Specific Class, Driver=, 480M**

| Port 7: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 480M

|__ Port 13: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M

|__ Port 13: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M

/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M

|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M

/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M

|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M

dmesg

[75013.233023] usb 3-10: new high-speed USB device number 24 using xhci_hcd

[75013.385574] usb 3-10: New USB device found, idVendor=03e7, idProduct=2485

[75013.385577] usb 3-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[75013.385578] usb 3-10: Product: Movidius MyriadX

[75013.385580] usb 3-10: Manufacturer: Movidius Ltd.

[75013.385581] usb 3-10: SerialNumber: 03e72485

[75013.431110] [UFW BLOCK] IN=enp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:d10c:0a95:5d4a:d78a DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=757631 PROTO=UDP SPT=8612 DPT=8612 LEN=24

[75013.431121] [UFW BLOCK] IN=enp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:d10c:0a95:5d4a:d78a DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=389803 PROTO=UDP SPT=8612 DPT=8610 LEN=24

[75038.064065] usb 3-10: USB disconnect, device number 24

[75038.105781] [UFW BLOCK] IN=enp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:d10c:0a95:5d4a:d78a DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=757631 PROTO=UDP SPT=8612 DPT=8612 LEN=24

[75041.368535] usb 3-9: new high-speed USB device number 25 using xhci_hcd

[75041.517264] usb 3-9: New USB device found, idVendor=03e7, idProduct=2485

[75041.517266] usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[75041.517268] usb 3-9: Product: Movidius MyriadX

[75041.517269] usb 3-9: Manufacturer: Movidius Ltd.

[75041.517271] usb 3-9: SerialNumber: 03e72485

[75053.512607] usb 3-9: USB disconnect, device number 25

[75053.552916] [UFW BLOCK] IN=enp3s0 OUT= MAC= SRC=fe80:0000:0000:0000:d10c:0a95:5d4a:d78a DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=757631 PROTO=UDP SPT=8612 DPT=8612 LEN=24

[75055.540290] usb 3-2: new high-speed USB device number 26 using xhci_hcd

[75055.692871] usb 3-2: New USB device found, idVendor=03e7, idProduct=2485

[75055.692874] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[75055.692876] usb 3-2: Product: Movidius MyriadX

[75055.692878] usb 3-2: Manufacturer: Movidius Ltd.

[75055.692879] usb 3-2: SerialNumber: 03e72485

which i plungged many times.

I am not sure if it is the bug remind here.

idata · ‎12-02-2018

@Tome_at_Intel

Hi, I am running hello_ncs.py and i get the below error. i am using NCS 2 in ubuntu Virtual box on windows

making run

python3 hello_ncs.py;

D: [ 0] ncDeviceCreate:308 ncDeviceCreate index 0

D: [ 0] ncDeviceCreate:308 ncDeviceCreate index 1

D: [ 0] ncDeviceOpen:524 File path /usr/local/lib/mvnc/MvNCAPI-ma2480.mvcmd

W: [ 0] ncDeviceOpen:528 ncDeviceOpen() XLinkBootRemote returned error 3

Please help

idata · ‎12-02-2018

https://ncsforum.movidius.com/discussion/1360/problem-running-hello-ncs-py#latest

NCS2(MvNCAPI-ma2480.mvcmd) is not supported.