Please Nvidia how do I troubleshoot "Cannot Open USB"?

Autonomous Machines Jetson & Embedded Systems Jetson TX1
21

My TX1 in recovery mode:

> lsusb -d 0955:7721
Bus 003 Device 010: ID 0955:7721 NVidia Corp.

> cat /dev/bus/usb/003/010 | head -c 1024 | hexdump
0000000 0112 0200 0000 4000 0955 7721 0102 0201
0000010 0100 0209 0020 0101 c000 0910 0004 0200
0000020 ffff 00ff 0507 0281 0200 0700 0105 0002
0000030 0002                                   
0000032
1 Like
22

Fantastic, thank you very much indeed. That output is the device descriptor and the current configuration descriptor. In your case a lot of stuff is missing, should go up to 0000055

23

I’ve the same issue. how did you solve it?

24

Hello,

Can you tell me how to use vusb-analyzer in jetson nano?
it seems like that vusb-analyzer tool use usbmon logs.

Thank you.

25

I have not used vusb-analyzer before, but looked it up. URL here for those interested:
http://vusb-analyzer.sourceforge.net/

This looks like an interesting and useful tool, but I have no experience with it. Keep in mind that a virtual tool cannot help with PHY issues like signal quality, but in terms of actual USB protocol errors, this could prove useful. Looks like it uses existing USB services and improves how the logs are used. There might be some kernel features in need of enable, but those services could already be there (e.g., looks like CONFIG_USB_MON already exists as a module by default).

1 Like
26

Hello,

In general ubuntu pc, it seems to check USB_MON as follows.

grep USB_MON /boot/config-5.9.*

/boot/config-5.9.11-100.fc32.x86_64:CONFIG_USB_MON=y
/boot/config-5.9.8-100.fc32.x86_64:CONFIG_USB_MON=y
/boot/config-5.9.9-100.fc32.x86_64:CONFIG_USB_MON=y

How to check CONFIG_USB_MON in jetson?

Thank you.

27

zcat /boot/config.gz | grep CONFIG_USB_MON

1 Like
28

Hello,

When I run the above command, it says that config.gz cannot be found as shown below.
On Friday, October 16, 2020, R32 revision 4.4 performed the above command.

gzip: /boot/config.gz: No such file or directory

Thank you.

29

If that command fails on a Jetson, then something is very wrong. The file is itself not a “real” file, but a reflection of a feature of the kernel in RAM. This means the kernel is missing the configuration of that item. Was the default kernel replaced?