[Error 7] Toolkit Error: USB Failure. Code: Error opening device

[idata]

If I plug the NCS directly into one of the USB 3.0 ports on my Ubuntu 16.04 x86_64 machine (native) I get the USB Failure error when doing "make example01", and if I run "ncs-check -1" it fails with the error message "OpenDevice 11 failed, rc=-2"

In USBView it shows the Movidius MX2X5X device with the vendor ID of 03e7, and product ID of 2150. But, oddly it shows the USB version as 2.0 and the speed as 480Mb/s (high). Which I find odd because by appearance it's a USB 3.0 device. It's also only reporting needing 500ma. So is the NCS device a USB 2.0 device or USB 3.0 device?

What I find truly odd is if I use a USB 2.0 extension cable everything appears to work correctly. As far as I can tell all the information under USBView is the same.

There could be something about my machine that's messed up. Previously I was using it for Camera testing with the Aravis project, and that uses the libusb. But, I don't remember changing anything.

[idata]

I'm having a similar issue. It's weird.

Using Ubuntu 16.04 guest on Windows 10 with VirtualBox.If I add as a USB 3.0 The Movidius does not appear at all. USB 2.0 it's there

andrew@Movidius:~$ lsusb -v | grep ovid

Couldn't open device, some information will be missing Couldn't open device, some information will be missing iManufacturer 1 Movidius Ltd. iProduct 2 Movidius MA2X5X

When I run 'make examples', it gets down to "making check" when you hear the USB unplug sound and get the error "[Error 7] Toolkit Error: USB Failure. Code: Error opening device" and lsusb no longer finds it/

andrew@Movidius:~$ lsusb -v | grep ovid

Couldn't open device, some information will be missing Couldn't open device, some information will be missing Couldn't open device, some information will be missing

Any ideas?

[idata]

@RiceAD We are aware of this issue. At the moment, the current NCSDK (2.05) has an issue running on virtual machines. Other threads: https://ncsforum.movidius.com/discussion/919/ncsdk-2-05-not-working-in-virtualbox-5-2-with-ubuntu-16-04-04#latest

[idata]

@Tome_at_Intel Dear Tome, I installed it successfully month ago (not VM, VB…etc) on Raspberry Pi. Unluckily, I am facing the same problem today. One difference is python 2.7 (success) v.s. python 3.5 (fail)

/usr/local/bin/ncsdk/Controllers/FileIO.py:65: UserWarning: You are using a large type. Consider reducing your data sizes for best performance

Blob generatedW: [ 0] ncDeviceOpen:533 failed to find device[Error 7] Toolkit Error: USB Failure. Code: Error opening deviceMakefile:30: recipe for target 'profile' failedmake[3]: *** [profile] Error 255

I have no idea why and how to deal with.

Thanks a lot

[idata]

@Sramctc Which version of the NCSDK are you using? Can you share which applications you tried to run and failed with?

[idata]

@Tome_at_Intel

I use the latest version (2.05) of NCSDK today (download from web site). I am not sure (really forget) which version was installed last time, as I used git clone https://github.com/movidius/ncsdk. But I still keep the working one in other SD.

Thanks

[idata]

@Sramctc Can you share which application you were using that failed with python3?

[idata]

@Tome_at_Intel Dear Tome,

pi@raspberrypi:~/workspace/ncappzoo/apps/hello_ncs_py $ python3 hello_ncs.py

Traceback (most recent call last): File "hello_ncs.py", line 14, in fx.SetGlobalOption(fx.GlobalOption.LOG_LEVEL, 0)AttributeError: module 'mvnc.mvncapi' has no attribute 'SetGlobalOption'

Thanks

[idata]

@Sramctc So it seems like you cloned the NCSDK 1 version of the NCAPPZOO and you have NCSDK 2 installed. Try cloning the NCSDK 2 version using this command: git clone -b ncsdk2 https://github.com/movidius/ncappzoo and running the same application. Please let me know if this works for you. Thanks.

[idata]

@Tome_at_Intel

pi@raspberrypi:~/workspace/ncappzoo/apps/hello_ncs_py $ make run

making run

python3 hello_ncs.py;E: [ 0] dispatcherEventSend:730 Write failed -1

Hello NCS! Device opened normally.

Goodbye NCS! Device closed normally.NCS device working.pi@raspberrypi:~/workspace/ncappzoo/apps/hello_ncs_py $ python3 hello_ncs.pyHello NCS! Device opened normally.Goodbye NCS! Device closed normally.NCS device working.pi@raspberrypi:~/workspace/ncappzoo/apps/hello_ncs_py $

Just do it again , is it OK?

Thanks

[idata]

@Sramctc Looks like it worked. Please try other applications and let me know if they work for you also.

[idata]

@Tome_at_Intel Many thanks, I will try other applications in few days and let you know at once.

[idata]

@Tome_at_Intel

It is working but I am facing another problem :confounded:

https://ncsforum.movidius.com/discussion/1026/exception-status-invalid-data-length

[idata]

@Tome_at_Intel

Is this issue resolved? let me know if any solution.

I still get the error "error 7 toolkit error usb failure. code error opening device". I am using Ubuntu Virtual box on WIndows 7.

PLease let me know if any solution is found.

[idata]

I get this error

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

Error - Could not open NCS device.

My Host is mac and i can see device configuration.

Movidius MyriadX: Product ID: 0x2485 Vendor ID: 0x03e7 Version: 0.01 Speed: Up to 480 Mb/sec Manufacturer: Movidius Ltd. Location ID: 0x14100000 / 10 Current Available (mA): 500 Current Required (mA): 500 Extra Operating Current (mA): 0

I'm using Virtualbox and i can also see device in there

Bus 001 Device 002: ID 03e7:2485Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x03e7 idProduct 0x2485 bcdDevice 0.01 iManufacturer 1 Movidius Ltd. iProduct 2 Movidius MyriadX

Still test programs don't work? Anyone have any insights?

[idata]

Hi @ashwin.rayaprolu

Did you create filters for your virtual machine when installing? Here is the link for instructions on how to do that (this page is for installing the ncsdk on a virtual machine, but the process is almost the same for OpenVINO).

Sincerely,

Sahira