Jetson Nano 2GB USB 3.0 Issue

Hey, today I started having a problem with the usb 3.0 port on my jetson nano dev kit.
For the past year, I have been using a UVC camera without any problems. Today, gstreamer v4l2src pipeline just hangs unless I plug into a hub which plugs into jetson, in which case everything seems to work fine.
I tried using the same exact UVC device plugged direct, power supply, even the same sd card/image in another jetson nano 2gb I have and it works fine. Any clue what might have happened? Or how else I could troubleshoot?

On the problematic device, plugin the camera and share the dmesg and lsusb result.

Thank you @WayneWWW
I just tried swapping the modules, and unfortunately it doesn’t seem to be a problem with the carrier board…

mark@jetson2:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:c811 Realtek Semiconductor Corp.
Bus 001 Device 006: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 2109:2813 VIA Labs, Inc.
Bus 001 Device 002: ID 1a40:0801 Terminus Technology Inc.
Bus 001 Device 012: ID 0fd9:0067 Elgato Systems GmbH
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and

[deleted]

Hi,

[ 10.618923] usb 1-2: new high-speed USB device number 12 using tegra-xusb
[ 10.860334] usb 1-2: New USB device found, idVendor=0fd9, idProduct=0067
[ 10.860342] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=4
[ 10.860346] usb 1-2: Product: Cam Link 4K
[ 10.860350] usb 1-2: Manufacturer: Elgato
[ 10.860353] usb 1-2: SerialNumber: 00057605B6000

Is this the usb camera you are talking about?

Right…

Is there any difference between the working case and the NG case in lsusb?

For example, I see in current log, your camera is a high speed device, which means usb2.0 device. Did you see it as s super speed device on the good board?

lsusb is same besides different bus and device.

mark@jetson2:~$ lsusb
Bus 002 Device 003: ID 0fd9:0066 Elgato Systems GmbH
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:c811 Realtek Semiconductor Corp.
Bus 001 Device 006: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 2109:2813 VIA Labs, Inc.
Bus 001 Device 002: ID 1a40:0801 Terminus Technology Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It seems the camlink identifies as high-speed. Here is the dmesg from the working kit.

[deleted]

Hi,

On the NG device, could you

  1. Remove all the other devices, including hub and only connect the camera to default usb hub on jetson and see if it can work as super speed device?

  2. Have you tried to reflash the board with sdkmanager? (not sdcard image)

Ok one moment please.
I have tried sdcard image so far. not sdkmanager

This is the dmesg when I boot up with just the camera attached. I had to plug in keyboard to get to terminal, and was able to record with the camera.
However, if I boot with even so much as the usb wifi dongle, camera hangs again.

[deleted]

And “working” lsusb on the NG jetson:

Bus 002 Device 002: ID 0fd9:0066 Elgato Systems GmbH

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 005: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory

Bus 001 Device 002: ID 1a40:0801 Terminus Technology Inc.

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Sorry, need to clarify the case.

So what is the case here? Do you mean you can see the camera as super speed device after removing all the other usb devices?

Jetson Nano 2GB USB 3.0 Issue - #11 by mhd0425

And what do you mean a “working” lsusb on the NG jetson…? Are you saying that you managed to make the device work as superspeed again on the NG board?

By “working” lsusb I meant the lsusb from the time the camera was able to record ie when I didn’t have any other usb device plugged in on boot.
I was merely able to get the gst-pipeline to save a file again on the board that is No Good. Yes, I believe the elgato it is being picked up as superspeed. But only if I don’t have any other peripherals i.e. wifi connected, which is not the solution I am looking for. It is not in the working condition I am after.
What do you suppose is the reason for this behavior?

@WayneWWW Is it something to do with sleepwalk?

Hi,

Does only “wifi” will make your usb cam to usb2.0 or even other usb device can make this behavior?

Hi @WayneWWW,
THank you for your help so far.

Few more quick tests shows that if anything is plugged into either usb 2.0 port on boot, the camera device will not work at superspeed. This is not just wifi dongle, but mouse and/or keyboard too. Plugging in peripherals to usb 2.0 after boot does not cause problems with the camera.

I have some questions regarding the devices here.

Is that “VIA lab” hub added by you? When you test this do you always connect to that hub?

Just make a more clear one for what I want to say

  1. Can you just use the default hub on jetson nano 2gb to do the test, without adding any extra hub to test?

  2. You said this issue only happened to one jetson nano 2gb. Have you checked the software version of these two boards? Are they using same jetapck version?

  3. Have you tried any other usb3 device other than the usb camera? Will they hit this issue?

Yes, the “VIA lab” is the usb hub I’m using just so I can connect wifi, keyboard, and mouse via usb2 ports. I do not always connect this hub. The camera is connected directly to the usb3 port in every test.

  1. Can you just use the default hub on jetson nano 2gb to do the test, without adding any extra hub to test?

The latest tests I ran are without the VIA hub connected. The camera works fine if nothing else is connected to either usb2 port during boot. After boot, I can plug anything into usb2 ports and the camera will continue to work as expected.

  1. You said this issue only happened to one jetson nano 2gb. Have you checked the software version of these two boards? Are they using same jetapck version?

That is correct. Only one of the jetson modules has this problem. Everything else is identical in the tests: dev board, power supply, cables, jetpack version, installed software.

  1. Have you tried any other usb3 device other than the usb camera? Will they hit this issue?

If I plug a usb3 hub into the usb3 port, and connect the camera into the usb3 hub, the camera works fine no matter what else is plugged into the usb2 ports during boot.