USB issue on TX1 after set up by JetPack

Autonomous Machines Jetson & Embedded Systems Jetson TX1
1

We tried to set up by JetPack-L4T-3.1-linux-x64.run order by LT4_jetson_X1Development_kid_kIT_USER_gUIDE.PDF

After finish set up, we cannot access one of the USB port.

Result as ‘lssub -t’ follows.

Could you advice us?

/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-tegra/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=xhci-tegra/5p, 480M
|__ Port 3: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 3: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M

Thansk for supporting us always.

Asai

2

Hi k_asai,
Which port is not working at your side? I see same ‘lsusb -t’ and both micro AB and type A work well.

3

Thans for reply

Port 4 is not working now.

Before : as follows

/: 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=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 3: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

    |__ Port 1: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M

However now : Port 4 is not working.

/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-tegra/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=xhci-tegra/5p, 480M
|__ Port 3: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 3: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M

4

Note that the root_hub is the USB port of the Jetson. What you show as Port 4 is an external HUB. In all cases the USB port of the Jetson shows as working from the “lsusb -t” view (there are two root_hubs…the micro-USB has speed 480M, the USB3 speed of the full-sized USB is 5000M for speed).

This doesn’t mean there isn’t an issue if your HUB connected to the port does not work, but it changes where the issue might be.

Is this a powered HUB? Does this HUB have anything plugged in to it? It looks like the port the HUB plugs in to in which it now fails is the micro-USB port…is this correct? Can you describe any cables or adapters used with the HUB? Does the HUB show up if used with the other port?

5

Dear Unixdev-san,

Thanks for reply.

I tried as following.

sudo gedit /etc/modules

added,

usb-storage

then restart TX1

However it not work tow USB port (only one (USB under:NOT mini usb).

We feel strange,

Is there any idea to fix this issu for Tx1?

Thanks for reading.

Asai

6

You shouldn’t need to edit the modules file for a standard USB class (such as mass storage). That file is for items needing load at boot time and not late in boot…if you have already booted and are checking “lsusb -t” at later times then the module would already be loaded and you would see the result in lsusb.

Is there hardware associated with what you are trying to view, or is this something entirely in software (such as USB emulating something)? Please describe any hardware being connected…some model and brand name which we can look up driver requirements for…there may be a different driver for what you are doing under the 4.x kernel version versus the older 3.x kernel version.

7

Hi Unixdev-san

Thanks for the reply.

I got an information from my college , NVIDIA will release new patch until next week include this issue.

I am waiting for it, then try it then write down result on this Q&A.

Again thank you so much.

Asai

8

Hi k_asai, have your issue been fixed?

9

Dear DaneLLL-san

Thanks fpr asking.

I cannot resolved yet.

10

Hi k_asia,
Have you tried other USB HUBs? It’s worth trying USB HUBs with external power.

11

Thanks for gave an advice, we already using,

However we need to the products of company, means need to fix this issue.

Regards,
Asai

12

Can it be verified this is a regular dev carrier board and not a custom board? Can I verify this is connected to the full-size USB connector (it sounds like this is the case, but I want to verify)?

What is the output from “cat /proc/cmdline”? Has the device tree been modified at all?

If you run “dmesg --follow” while you plug in or unplug the HUB, with nothing else connected to the HUB itself, what does dmesg show?

Is there any difference in how “lsusb -t” looks when the HUB (with nothing connected to the HUB) shows up if connected before boot versus connected only after boot? Try a clean boot with the HUB connected (nothing connected to the HUB), show “lsusb -t”. Try another clean boot without the HUB, run “lsusb -t”, save this, connect the HUB (with nothing on the HUB), and show “lsusb -t” again. I’m looking at the “Dev” number and trying to figure out how it is enumerating (note that you have on device with multiple functions…this will have two entries, but the same “Dev” number…this is normal).

Does this HUB have a different cable you can test with?