Jetson TX1-Kernel 3.10 -Jetpack 3.0 , need USB camer support

Hi ,

I just received Jetson Tx1 with jetpack3.0 (kernel 3.10). I tried to get USB camera image from USB /OTG port .

It is detecting as a USB port if i give lsusb . But failed to get the active driver .

Can anybody help me ?

Thanks & Regards
Raghu Ramaraj

If you run lsusb you’ll see an “ID” field with a format like “1234:5678”. Run lsusb and find out which ID goes with your camera. Then look at a verbose listing specifically for that device, and paste it here in the forums. Example, adjust for your ID:

sudo lsusb -d 1234:5678 -vvv

Also run “lsusb -t” so the speeds can be examined.

If possible run the tests from the full-sized USB connector (a USB3-capable connector is required if anything USB3 is to be examined…USB3 capabilities may not show up on the micro connector).

If you examine dmesg while plugging in the device (e.g., “dmesg --follow”), go ahead and post that log too.

Hi,

I tried with two different vendor’s USB camera .Pls find the logs

T: Bus=01 Lev=02 Prnt=11 Port=03 Cnt=03 Dev#= 14 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=eb1a ProdID=2860 Rev=01.00
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none)

T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0471 ProdID=0327 Rev=01.01
S: Product=USB camera
C: #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio
I: If#= 2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio

I didnt understand , why its not fetching the driver

could you help me to enable it ?

I’m unsure of what logs you posted (consider using the “</>” icon in the upper right to turn those logs into code blocks).

The original question still remains…have you tried this on the full-sized USB connector? The micro connector does not support USB3…any camera which requires USB3 will not have implemented USB2 compatibility on the camera data and USB2 will not even be aware of that function. The full-sized connector supports USB3 and sometimes something invisible on the micro connector will suddenly show up on the full-sized connector (this is true only if the function is purely USB3).

In general, USB is just a data pipe with the ability to announce the plugin or unplug of a device from USB. No device specific driver is ever touched by USB itself. The hotplug layer receives an announcement of plug/unplug events, along with the device identity information, and a driver which thinks it can handle the device will take ownership; if no such driver exists (meaning no driver understands the device class), then no driver takes ownership…USB succeeded, but nobody was there to take ownership.

There are a number of standardized USB classes which will always have a driver available for. An example would be human interface devices (HID). There is a generic driver which can handle any brand of keyboard or mouse which follows that standard. For cameras there is the USB Video Class (UVC)…if the camera follows that, then there will always be a driver to handle the camera with no special effort required (hotplug will always have a driver for this class to take ownership).

Devices not in a standardized USB class are not unusual…these require a driver specific to that device, usually enabled in a kernel config or downloaded from the manufacturer site (preferably downloaded in source form so you can compile for your kernel…a binary only format will almost always fail because manufacturers do not make the aarch64 architecture available). Earlier questions from comment #2 must be answered if useful information is to be provided. The result of answering comment #2 may differ depending on whether the micro port is used or if the full-sized port is used (should the camera be purely USB2 or slower then port won’t change answers…it’s the case of USB3 capability additions which might change the answer depending on port).

Hi ,

Thanks for your repose . I am using full -sized USB connector(big one ) only .

My Ubuntu PC is detecting this as a camera device. But jetson is detected as USB device only and not fetching the UVC driver .

Pls find the logs…

ubuntu@tegra-ubuntu:~$ dmesg

[ 264.405714] usb 1-3.4: new high-speed USB device number 12 using tegra-xhci
[ 264.427114] usb 1-3.4: New USB device found, idVendor=eb1a, idProduct=2860
[ 264.427228] usb 1-3.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
ubuntu@tegra-ubuntu:~ sudo lsusb Bus 002 Device 002: ID 0955:09ff NVidia Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 012: ID eb1a:2860 eMPIA Technology, Inc. Bus 001 Device 011: ID 413c:2003 Dell Computer Corp. Keyboard Bus 001 Device 010: ID 04ca:0061 Lite-On Technology Corp. Bus 001 Device 009: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ubuntu@tegra-ubuntu:~ sudo lsusb -d eb1a:2860 -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xhci/4p, 5000M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xhci/5p, 480M
|__ Port 3: Dev 9, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 10, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 3: Dev 11, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 4: Dev 12, If 0, Class=Vendor Specific Class, Driver=, 480M
ubuntu@tegra-ubuntu:~$ sudo lsusb -d eb1a:2860 -vvv

Bus 001 Device 012: ID eb1a:2860 eMPIA Technology, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0xeb1a eMPIA Technology, Inc.
idProduct 0x2860
bcdDevice 1.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 249
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0ad4 2x 724 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0c00 2x 1024 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 4
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1300 3x 768 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 5
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x135c 3x 860 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 6
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x13c4 3x 964 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 7
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1400 3x 1024 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
ubuntu@tegra-ubuntu:~$

The first place giving information on what’s wrong is from the “lsusb -t”. This is the line for the camera:

Port 4: Dev 12, If 0, Class=<b>Vendor Specific Class</b>, Driver=, 480M

As you can see the camera is not a UVC camera with a standard interface. This particular camera requires a vendor specific driver. So probably a module exists on your host by default for that driver, but you may need to compile this on your Jetson (embedded systems never include everything under the sun, only PCs do that…so I’m not surprised the Jetson doesn’t have the driver built by default…your desktop is also likely a 4.x series kernel, while the 3.10 kernel of a Jetson is older).

One way to find out which driver is to research on the internet…a model plus “linux driver” usually gets what is needed. However, if your PC has the driver as a module, then you might run “lsmod” to see what is currently loaded on the PC, then plug in the camera, and see what changed in both dmesg and lsmod. Or even “lsusb -t” (this is probably the easiest check for driver name).

Based on the suggestion , i have added em28xx driver is added in to kernel . Please find the logs

ubuntu@tegra-ubuntu:~$ sudo lsusb -vvv -d eb1a:2860 -t
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=tegra-ehci/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 4: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 4: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xhci/4p, 5000M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xhci/5p, 480M
|__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=em28xx, 480M

[ 3881.497278] usb 1-3: new high-speed USB device number 8 using tegra-xhci
[ 3881.517611] usb 1-3: New USB device found, idVendor=eb1a, idProduct=2860
[ 3881.517620] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3881.518376] em28xx: New device @ 480 Mbps (eb1a:2860, interface 0, class 0)
[ 3881.518383] em28xx: Video interface 0 found: isoc
[ 3881.518474] em28xx: chip ID is em2860
[ 3881.637688] em2860 #0: board has no eeprom
[ 3881.737338] em2860 #0: No sensor detected
[ 3881.746801] em2860 #0: found i2c device @ 0x4a on bus 0 [saa7113h]
[ 3881.769051] em2860 #0: Your board has no unique USB ID.
[ 3881.774270] em2860 #0: A hint were successfully done, based on i2c devicelist hash.
[ 3881.782126] em2860 #0: This method is not 100% failproof.
[ 3881.787564] em2860 #0: If the board were missdetected, please email this log to:
[ 3881.794945] em2860 #0: V4L Mailing List linux-media@vger.kernel.org
[ 3881.801570] em2860 #0: Board detected as EM2860/SAA711X Reference Design
[ 3881.907282] em2860 #0: Identified as EM2860/SAA711X Reference Design (card=19)
[ 3881.910089] em2860 #0: Config register raw data: 0x00
[ 3881.910097] em2860 #0: v4l2 driver version 0.2.0
[ 3882.847460] em2860 #0: V4L2 video device registered as video1
[ 3882.847467] em2860 #0: V4L2 VBI device registered as vbi0
[ 3882.847471] em2860 #0: analog set to isoc mode.
ubuntu@tegra-ubuntu:~$

But i couldnt get any video and tried with VLC , ffplay and gst-launch

Thanks & Regards
Raghu Ramaraj

It looks like good progress…now USB sees the device and assigns the correct driver. One observation which might or might not matter is that the device has connected on a USB2 port (or USB3 port using USB2 speeds and standards…this is the “480M” of “lsusb -t”…USB3 shows as “5000M”). Does this camera require USB3?

The reason I ask is because some cameras require USB3 to work correctly…they absolutely require the bandwidth (moving the camera to a USB3 port would fix the issue). Most (all?) USB cameras consist of independent devices on a single cable where one or more devices are based on control signals, or perhaps secondary functions like audio. Those functions always work with USB2, nobody has made one yet which requires or benefits from USB3. The camera sensor itself is a different story…if the camera is a high-bandwidth device then no USB2 driver will be written for it…query about what is there on a USB2 port will never know anything about the sensor because USB won’t broadcast this device as existing without USB3. Start by making sure the camera supports full operation with USB2.

Assuming the camera should work with USB2 it may just be a case of udev not having a rule with this driver to rename the device special file to what you are expecting. You added a driver the system did not know about before, perhaps udev just doesn’t know what to rename the device as, so the device exists with some unknown name. You could find such a name by monitoring dmesg while inserting or removing the device (e.g., “dmesg --follow”).

I am using Host USB port (not a OTG) . As per the camera’s spec its using USB 2.0

Please find the dmesg log

[ 49.177615] em2860 #0: disconnecting em2860 #0 video
[ 49.177699] em2860 #0: V4L2 device vbi0 deregistered
[ 49.179813] em2860 #0: V4L2 device video1 deregistered
[ 132.728771] usb 1-3: new high-speed USB device number 4 using tegra-xhci
[ 132.750422] usb 1-3: New USB device found, idVendor=eb1a, idProduct=2860
[ 132.750538] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 132.755461] em28xx: New device @ 480 Mbps (eb1a:2860, interface 0, class 0)
[ 132.755547] em28xx: Video interface 0 found: isoc
[ 132.756002] em28xx: chip ID is em2860
[ 132.872062] em2860 #0: board has no eeprom
[ 132.969002] em2860 #0: No sensor detected
[ 132.997614] em2860 #0: found i2c device @ 0x4a on bus 0 [saa7113h]
[ 133.041412] em2860 #0: Your board has no unique USB ID.
[ 133.046669] em2860 #0: A hint were successfully done, based on i2c devicelist hash.
[ 133.054927] em2860 #0: This method is not 100% failproof.
[ 133.060479] em2860 #0: If the board were missdetected, please email this log to:
[ 133.067882] em2860 #0: V4L Mailing List linux-media@vger.kernel.org
[ 133.074712] em2860 #0: Board detected as EM2860/SAA711X Reference Design
[ 133.178819] em2860 #0: Identified as EM2860/SAA711X Reference Design (card=19)
[ 133.204413] em2860 #0: Config register raw data: 0x00
[ 133.204465] em2860 #0: v4l2 driver version 0.2.0
[ 134.161443] em2860 #0: V4L2 video device registered as video1
[ 134.161528] em2860 #0: V4L2 VBI device registered as vbi0
[ 134.161590] em2860 #0: analog set to isoc mode.
[ 141.559431] usb 1-3: USB disconnect, device number 4
[ 141.560678] em2860 #0: disconnecting em2860 #0 video
[ 141.560760] em2860 #0: V4L2 device vbi0 deregistered
[ 141.561842] em2860 #0: V4L2 device video1 deregistered
[ 159.168832] usb 1-3: new high-speed USB device number 5 using tegra-xhci
[ 159.190556] usb 1-3: New USB device found, idVendor=eb1a, idProduct=2860
[ 159.190671] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 159.195731] em28xx: New device @ 480 Mbps (eb1a:2860, interface 0, class 0)
[ 159.195817] em28xx: Video interface 0 found: isoc
[ 159.196240] em28xx: chip ID is em2860
[ 159.312465] em2860 #0: board has no eeprom
[ 159.408650] em2860 #0: No sensor detected
[ 159.427272] em2860 #0: found i2c device @ 0x4a on bus 0 [saa7113h]
[ 159.465803] em2860 #0: Your board has no unique USB ID.
[ 159.471603] em2860 #0: A hint were successfully done, based on i2c devicelist hash.
[ 159.479314] em2860 #0: This method is not 100% failproof.
[ 159.484799] em2860 #0: If the board were missdetected, please email this log to:
[ 159.493342] em2860 #0: V4L Mailing List linux-media@vger.kernel.org
[ 159.499964] em2860 #0: Board detected as EM2860/SAA711X Reference Design
[ 159.598629] em2860 #0: Identified as EM2860/SAA711X Reference Design (card=19)
[ 159.632723] em2860 #0: Config register raw data: 0x00
[ 159.632823] em2860 #0: v4l2 driver version 0.2.0
[ 160.570831] em2860 #0: V4L2 video device registered as video1
[ 160.570921] em2860 #0: V4L2 VBI device registered as vbi0
[ 160.570990] em2860 #0: analog set to isoc mode.
ubuntu@tegra-ubuntu:~$

Even i removed the camera interface board & tried … its not fetching any frames from USB .

It would be great if you share ,any working converter card (from s-video to USB ) with jetson tx1 .

Thanks
Raghu Ramaraj

The reason I wonder about which port is used is because in the “lsusb -t” of post #7 I see this:

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xhci/4p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xhci/5p, 480M
    |__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=em28xx, 480M

Notice that your em28xx driver is running at 480M, the speed of USB2. The root_hub of this tree is also running at 480M. The other bus listed for root_hub has speed of 5000M (USB3). If you have a sensor which is high bandwidth the vendor would not have created any USB2 compatibility…only the camera control side would show up. If this is the case the sensor will show up only on the 5000M speed port. Try the other port and verify in “lsusb -t” that the em28xx is loaded on a USB3 port. It may be that this doesn’t matter if the sensor is USB2 compatible, but it is an easy test.