R200 Camera not detected by UP Board
Karthik
New Member Posts: 2 ✭
in Peripherals
Hi,
I received my new intel robotic kit yesterday and I followed all the instructions here: https://01.org/developerjourney/recipe/intel-realsense-robotic-development-kit . But the board does not recognize the camera. There is no /dev/video* on the system. lsusb does not show anything as connected. Please let me know if this points to a faulty hardware.
lsmod | grep -q uvcvideo && echo "Kernel module foundlsmod | grep -q uvcvideo && echo "Kernel module found."
Kernel module found.
ls /dev/vi*
ls: cannot access '/dev/vi*': No such file or directory
robot@robot:/opt/ros/kinetic/share/realsense_camera$ sudo modprobe uvcvideo
uname -r
4.4.0-2-upboard
Here is the output from dmesg.
robot@robot:/opt/ros/kinetic/share/realsense_camera$ sudo dmesg | tail -n50
[ 6.429320] audit: type=1400 audit(1483761819.460:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=759 comm="apparmor_parser"
[ 6.430515] audit: type=1400 audit(1483761819.460:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=758 comm="apparmor_parser"
[ 6.430544] audit: type=1400 audit(1483761819.460:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session//chromium" pid=758 comm="apparmor_parser"
[ 6.435185] audit: type=1400 audit(1483761819.464:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=765 comm="apparmor_parser"
[ 6.435383] audit: type=1400 audit(1483761819.464:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=764 comm="apparmor_parser"
[ 7.264244] i2c i2c-0: i2c read failed
[ 7.581669] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 7.626280] r8169 0000:01:00.0 enp1s0: link down
[ 7.626285] r8169 0000:01:00.0 enp1s0: link down
[ 7.626394] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 9.197402] r8169 0000:01:00.0 enp1s0: link up
[ 9.197431] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready
[ 429.082584] media: Linux media interface: v0.10
[ 429.100828] Linux video capture interface: v2.00
[ 429.126723] uvcvideo: module verification failed: signature and/or required key missing - tainting kernel
[ 429.128030] usbcore: registered new interface driver uvcvideo
[ 429.128038] USB Video Class driver (1.1.1-3-realsense)
[ 715.355708] xhci_hcd 0000:00:14.0: port 0 resume PLC timeout
[ 733.529406] xhci_hcd 0000:00:14.0: port 0 resume PLC timeout
[ 800.328064] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 800.348323] usb 2-1: New USB device found, idVendor=8086, idProduct=0a80
[ 800.348341] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 800.348352] usb 2-1: Product: Intel RealSense 3D Camera R200
[ 800.348361] usb 2-1: Manufacturer: Intel Corp
[ 800.348368] usb 2-1: SerialNumber: SN_2431001013
[ 800.352869] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 800.361497] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 800.366297] uvcvideo: Unable to create debugfs 2-2 directory.
[ 800.367679] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.2/input/input7
[ 800.370139] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 800.375455] uvcvideo: Unable to create debugfs 2-2 directory.
[ 800.376641] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.4/input/input8
[ 802.199835] usb 2-1: USB disconnect, device number 2
[ 804.636414] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 858.251124] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd
[ 858.274840] usb 2-1: New USB device found, idVendor=8086, idProduct=0a80
[ 858.274852] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 858.274858] usb 2-1: Product: Intel RealSense 3D Camera R200
[ 858.274863] usb 2-1: Manufacturer: Intel Corp
[ 858.274868] usb 2-1: SerialNumber: SN_2431001013
[ 858.279594] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 858.287037] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 858.290680] uvcvideo: Unable to create debugfs 2-3 directory.
[ 858.291813] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.2/input/input9
[ 858.293709] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 858.297782] uvcvideo: Unable to create debugfs 2-3 directory.
[ 858.298565] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.4/input/input10
[ 858.798815] usb 2-1: USB disconnect, device number 3
[ 1215.129883] xhci_hcd 0000:00:14.0: port 0 resume PLC timeout
[ 1219.536023] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
I do not have a windows system to test the camera, but when connected to my macbook I do see the camera in the usb connections.
Thank you for your help
Karthik
I received my new intel robotic kit yesterday and I followed all the instructions here: https://01.org/developerjourney/recipe/intel-realsense-robotic-development-kit . But the board does not recognize the camera. There is no /dev/video* on the system. lsusb does not show anything as connected. Please let me know if this points to a faulty hardware.
lsmod | grep -q uvcvideo && echo "Kernel module foundlsmod | grep -q uvcvideo && echo "Kernel module found."
Kernel module found.
ls /dev/vi*
ls: cannot access '/dev/vi*': No such file or directory
robot@robot:/opt/ros/kinetic/share/realsense_camera$ sudo modprobe uvcvideo
uname -r
4.4.0-2-upboard
Here is the output from dmesg.
robot@robot:/opt/ros/kinetic/share/realsense_camera$ sudo dmesg | tail -n50
[ 6.429320] audit: type=1400 audit(1483761819.460:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=759 comm="apparmor_parser"
[ 6.430515] audit: type=1400 audit(1483761819.460:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=758 comm="apparmor_parser"
[ 6.430544] audit: type=1400 audit(1483761819.460:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session//chromium" pid=758 comm="apparmor_parser"
[ 6.435185] audit: type=1400 audit(1483761819.464:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=765 comm="apparmor_parser"
[ 6.435383] audit: type=1400 audit(1483761819.464:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=764 comm="apparmor_parser"
[ 7.264244] i2c i2c-0: i2c read failed
[ 7.581669] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 7.626280] r8169 0000:01:00.0 enp1s0: link down
[ 7.626285] r8169 0000:01:00.0 enp1s0: link down
[ 7.626394] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
[ 9.197402] r8169 0000:01:00.0 enp1s0: link up
[ 9.197431] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready
[ 429.082584] media: Linux media interface: v0.10
[ 429.100828] Linux video capture interface: v2.00
[ 429.126723] uvcvideo: module verification failed: signature and/or required key missing - tainting kernel
[ 429.128030] usbcore: registered new interface driver uvcvideo
[ 429.128038] USB Video Class driver (1.1.1-3-realsense)
[ 715.355708] xhci_hcd 0000:00:14.0: port 0 resume PLC timeout
[ 733.529406] xhci_hcd 0000:00:14.0: port 0 resume PLC timeout
[ 800.328064] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 800.348323] usb 2-1: New USB device found, idVendor=8086, idProduct=0a80
[ 800.348341] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 800.348352] usb 2-1: Product: Intel RealSense 3D Camera R200
[ 800.348361] usb 2-1: Manufacturer: Intel Corp
[ 800.348368] usb 2-1: SerialNumber: SN_2431001013
[ 800.352869] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 800.361497] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 800.366297] uvcvideo: Unable to create debugfs 2-2 directory.
[ 800.367679] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.2/input/input7
[ 800.370139] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 800.375455] uvcvideo: Unable to create debugfs 2-2 directory.
[ 800.376641] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.4/input/input8
[ 802.199835] usb 2-1: USB disconnect, device number 2
[ 804.636414] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[ 858.251124] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd
[ 858.274840] usb 2-1: New USB device found, idVendor=8086, idProduct=0a80
[ 858.274852] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 858.274858] usb 2-1: Product: Intel RealSense 3D Camera R200
[ 858.274863] usb 2-1: Manufacturer: Intel Corp
[ 858.274868] usb 2-1: SerialNumber: SN_2431001013
[ 858.279594] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 858.287037] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 858.290680] uvcvideo: Unable to create debugfs 2-3 directory.
[ 858.291813] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.2/input/input9
[ 858.293709] uvcvideo: Found UVC 1.10 device Intel RealSense 3D Camera R200 (8086:0a80)
[ 858.297782] uvcvideo: Unable to create debugfs 2-3 directory.
[ 858.298565] input: Intel RealSense 3D Camera R200 as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.4/input/input10
[ 858.798815] usb 2-1: USB disconnect, device number 3
[ 1215.129883] xhci_hcd 0000:00:14.0: port 0 resume PLC timeout
[ 1219.536023] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
I do not have a windows system to test the camera, but when connected to my macbook I do see the camera in the usb connections.
Thank you for your help
Karthik
Comments
-
The issue was with the cable.. I was using the cable that was provided as part of the kit so had assumed it to be of good quality. Apparently now. Once I replaced the cable the camera is now working.
Thanks -
Thanks for letting us now. We do test the cable compatibility before we include it into the kit. We will collect more feedback from the users. Appreciating your information.