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.
6403 Discussions

About {Toolkit Error: USB Failure. Code: Error opening device} in case of "make example02"

idata
Employee
‎08-12-2017 03:11 AM
979 Views

First of all, I have booted my Ubuntu 16.04/X64 by pressing power button after plugging-in Movidius USB stick into USB3.0 port,

 

When I try to run "make example02" command, I have got {[Error 7] Toolkit Error: USB Failure. Code: Error opening device

 

with "make example02" command} error message.

 

with "make example02" command

 

invain@u1604:/work/ad/movidius/1.07.07/bin$ time make example02 echo "example02 - lenet8 profiling" example02 - lenet8 profiling python3 ./mvNCProfile.pyc data/lenet8.prototxt -s 12 mvNCProfile v02.00, Copyright @ Movidius Ltd 2016 [Error 7] Toolkit Error: USB Failure. Code: Error opening device real 0m2.946s user 0m0.804s sys 0m0.344s

 

Then, I ran "lsusb" command in order to check connection status of the Movidus USB stick.

 

I could not find any information about Movidius/Myraid device.

 

with lsusb command

 

invain@u1604:/work/ad/movidius/1.07.07/bin$ lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f3:0234 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub 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 003: ID 03e7:2150 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

with "dmesg | grep USB" command

 

invain@u1604:/work/ad/movidius/1.07.07/bin$ dmesg | grep USB [ 0.136308] ACPI: bus type USB registered [ 0.669969] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 0.671386] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1 [ 0.688113] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00 [ 0.688566] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 0.688987] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.691240] hub 1-0:1.0: USB hub found [ 0.692634] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2 [ 0.708138] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00 [ 0.708593] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 0.708983] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.711099] hub 2-0:1.0: USB hub found [ 0.712364] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 0.713538] uhci_hcd: USB Universal Host Controller Interface driver [ 0.714395] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3 [ 0.717108] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [ 0.717522] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.719724] hub 3-0:1.0: USB hub found [ 0.721199] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4 [ 0.722040] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003 [ 0.722469] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 0.724740] hub 4-0:1.0: USB hub found [ 1.004136] usb 1-1: new high-speed USB device number 2 using ehci-pci [ 1.024138] usb 2-1: new high-speed USB device number 2 using ehci-pci [ 1.036140] usb 3-3: new high-speed USB device number 2 using xhci_hcd [ 1.136982] usb 1-1: New USB device found, idVendor=8087, idProduct=0024 [ 1.137000] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1.137256] hub 1-1:1.0: USB hub found [ 1.156955] usb 2-1: New USB device found, idVendor=8087, idProduct=0024 [ 1.156959] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1.157295] hub 2-1:1.0: USB hub found [ 1.364177] usb 3-3: new high-speed USB device number 3 using xhci_hcd [ 1.408189] usb 1-1.6: new low-speed USB device number 3 using ehci-pci [ 1.492900] usb 3-3: New USB device found, idVendor=03e7, idProduct=2150 [ 1.492903] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1.531756] usb 1-1.6: New USB device found, idVendor=04f3, idProduct=0234 [ 1.531758] usb 1-1.6: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 1.539032] usbhid: USB HID core driver [ 1.540793] hid-generic 0003:04F3:0234.0001: input,hidraw0: USB HID v1.11 Mouse [OM] on usb-0000:00:1a.0-1.6/input0 invain@u1604:/work/ad/movidius/1.07.07/bin$

 

Debugging with strace command

 

.......... Omission ............. stat("Makefile", {st_mode=S_IFREG|0664, st_size=904, ...}) = 0 <0.000009> fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 5), ...}) = 0 <0.000009> write(1, "echo \"example02 - lenet8 profili"..., 36echo "example02 - lenet8 profiling" ) = 36 <0.000013> pipe([3, 4]) = 0 <0.000012> close(4) = 0 <0.000009> fcntl(3, F_SETFD, FD_CLOEXEC) = 0 <0.000008> rt_sigprocmask(SIG_BLOCK, [HUP INT TERM XCPU XFSZ], NULL, 8) = 0 <0.000008> clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f9bca59b9d0) = 21889 <0.000051> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 <0.000008> wait4(-1, example02 - lenet8 profiling [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 21889 <0.000610> --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=21889, si_uid=1000, si_status=0, si_utime=0, si_stime=0} --- rt_sigreturn({mask=[]}) = 21889 <0.000013> write(1, "python3 ./mvNCProfile.pyc data/l"..., 53python3 ./mvNCProfile.pyc data/lenet8.prototxt -s 12 ) = 53 <0.000036> rt_sigprocmask(SIG_BLOCK, [HUP INT TERM XCPU XFSZ], NULL, 8) = 0 <0.000009> clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7f9bca59b9d0) = 21890 <0.000063> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 <0.000008> wait4(-1, mvNCProfile v02.00, Copyright @ Movidius Ltd 2016 [Error 7] Toolkit Error: USB Failure. Code: Error opening device [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 21890 <2.924880> --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=21890, si_uid=1000, si_status=0, si_utime=82, si_stime=34} --- rt_sigreturn({mask=[]}) = 21890 <0.000037> rt_sigprocmask(SIG_BLOCK, [HUP INT TERM XCPU XFSZ], NULL, 8) = 0 <0.000040> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 <0.000008> chdir("/work/ad/movidius/1.07.07/bin") = 0 <0.000048> close(1) = 0 <0.000013> exit_group(0) = ? +++ exited with 0 +++

 

I have two questions to fix this issue generated on my Ubuntu 16.04.1LTS-64bit/Intel-i5-3570.

 

First, Which USB version (e.g., USB 1.0, 2.0, and 3.0) does Movidius support officially?

 

Second, Does the Movidius USB stick support both Cold-plug and Hot-plug?
0 Kudos

Link Copied

0 Replies
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.