Jetson Nano 2GB USB ports not working

root@JetsonNano-2GB:~# uname -a
Linux JetsonNano-2GB 4.9.337-tegra #1 SMP PREEMPT Thu Jun 8 21:19:14 PDT 2023 aarch64 aarch64 aarch64 GNU/Linux

From dmesg:- Only touchscreen works
[Thu Mar 2 12:58:00 2023] usb usb2: usb_suspend_both: status 0
[Thu Mar 2 12:58:09 2023] usb0: HOST MAC 02:17:46:5a:b4:fa
[Thu Mar 2 12:58:09 2023] usb0: MAC 02:17:46:5a:b4:fb
[Thu Mar 2 12:58:09 2023] l4tbr0: port 2(usb0) entered blocking state
[Thu Mar 2 12:58:09 2023] l4tbr0: port 2(usb0) entered disabled state
[Thu Mar 2 12:58:09 2023] device usb0 entered promiscuous mode
[Thu Mar 2 12:58:09 2023] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[Thu Mar 2 12:58:12 2023] device usb0 left promiscuous mode
[Thu Mar 2 12:58:12 2023] l4tbr0: port 2(usb0) entered disabled state
[Thu Mar 2 12:58:30 2023] vdd-usb-vbus: disabling
[Thu Mar 2 12:58:30 2023] vdd-usb-vbus2: disabling
[Thu Mar 2 12:58:30 2023] vdd-usb-hub-en: disabling

You would have to post a full serial console boot log. Also, is this on one of NVIDIA’s carrier boards, or does it use something from a third party? I’m guessing third party, which would imply it might also need a different device tree (part of firmware). If the device tree being used makes the assumption of a different carrier board, then power rails are a likely candidate for failure until device tree is told about the different carrier board. If this is in fact entirely NVIDIA, then you would still need to flash this. For the case of a third party carrier board, then you need to check with the manufacturer for flash software, or patches they might use to the NVIDIA flash software. Models which run on an SD card also need to have the module itself flashed, and not just the SD card (eMMC models flash all at the same time).

It’s a Waveshare Jetson Nano 2GB from Amazon UK. USB used to work until about a month ago. I am going to burn a new microSD card with the file I used jetson-nano-2gb-jp461-sd-card-image.zip

Does Waveshare produce alternate software? It seems likely that the power rails are wrong because of using the dev kit software instead of the Waveshare software. It’s critical to find out from Waveshare what the flash procedure is. It is possible that an SD card image might work without reflash, but even if that is the case, then the boot content would have to be a valid release for that SD card. Most of the time if something like USB fails in this way we would be telling you to flash the module itself (with Waveshare’s software), which is separate from the SD card, and which contains the device tree.

I have raised the problem with Waveshare, awaiting a response.

If they have a product listing, then they might have a “downloads” URL as well which could answer.

Waveshare have responded: USB touch (cable changed), a video of the boot up supplied.
I’ve also supplied power – +5.45V 8A supply.
Could be a genuine USB hardware problem.

Can you post a full serial console boot log? I am assuming you have something simple with USB connected during the boot, e.g., mouse and keyboard. That way everything leading up to this can be examined.

I can’t find the order. I wonder if this is one of your boards, says
NVIDIA on the back.
Regards
Sid

[linuxdev] linuxdev https://forums.developer.nvidia.com/u/linuxdev
Top Contributor
April 30

Can you post a full serial console boot log? I am assuming you have
something simple with USB connected during the boot, e.g., mouse and
keyboard. That way everything leading up to this can be examined.


Visit Topic
https://forums.developer.nvidia.com/t/jetson-nano-2gb-usb-ports-not-working/290513/8
or reply to this email to respond.

To unsubscribe from these emails, click here
https://forums.developer.nvidia.com/email/unsubscribe/e4cc9c2e489540da0b77e0e26723c8fd8958d922b11049983ccc57fb8522d9bc.

I’ve linked 1 file to this email:

yM0mRzK6tW74wVYo.png

box32.png

(Attachment 20240501_003742.mp4.html is missing)

URL for the video Box

It is waiting for you to complete first boot setup to log in. Your touch screen is not configured or set up on any default Jetson, so screen touches won’t do this. You’ll probably need either serial console to finish this, or an actual keyboard/mouse. Touchscreen setup could require a number of things depending on how it works, e.g., maybe it is just a USB configuration, but it could use GPIO in which case it needs a device tree edit. If the touchscreen comes with this, then this isn’t something NVIDIA sells despite the module being NVIDIA’s.

Waveshare does make its own products for mounting modules onto. I suspect the carrier board is their own. There is no way to know if their carrier board exactly matches the NVIDIA reference design (in which case no device tree edit is needed), or if there are differences (in which case the device tree needs editing and Waveshare would provide this).

Note: A USB touchscreen failing is not the same as USB failing. Have you tried an actual USB mouse and keyboard?

Both keyboard and mouse are also inoperative. I’ll have a look at serial console access.
The Ethernet works but sshd isn’t configured.

ping JetsonNano-2GB

PING JetsonNano-2GB.site (192.168.10.226) 56(84) bytes of data.
64 bytes from JetsonNano-2GB.site (192.168.10.226): icmp_seq=1 ttl=64 time=0.347 ms
64 bytes from JetsonNano-2GB.site (192.168.10.226): icmp_seq=2 ttl=64 time=0.154 ms
64 bytes from JetsonNano-2GB.site (192.168.10.226): icmp_seq=3 ttl=64 time=0.136 ms
64 bytes from JetsonNano-2GB.site (192.168.10.226): icmp_seq=4 ttl=64 time=0.157 ms
64 bytes from JetsonNano-2GB.site (192.168.10.226): icmp_seq=5 ttl=64 time=0.143 ms
64 bytes from JetsonNano-2GB.site (192.168.10.226): icmp_seq=6 ttl=64 time=0.132 ms
64 bytes from JetsonNano-2GB.site (192.168.10.226): icmp_seq=7 ttl=64 time=0.148 ms
64 bytes from JetsonNano-2GB.site (192.168.10.226): icmp_seq=8 ttl=64 time=0.144 ms

Can you provide a full serial console boot log?

I’ll need to rig up a serial console.
Does the serial console provide more information than the video capture?

Far more information. Serial console runs in boot stages, and can provide access before Linux even begins. Quite useful.

Regarding your “/boot/extlinux/extlinux.conf”, if you see “quiet”, then you should remove that token for more verbose logging. I’m hoping you can log in via serial console or ssh to remove that token, but if not, then it is still very useful to have the serial console log.

Incidentally, the Linux kernel inherits an environment just like most programs do, but what it inherits is from boot stages. Some of the setup regarding USB occurs before Linux starts.

I have done a video. Yet to set up a serial console