Hello Tegra Society,
I have a problem with the keyboard and mouse connection through the USB hub to Nvidia Tegra TX2.
Everything was fine when I connected these devices for the first time.
But after reboot, I do not see the mouse and keyboard.
It looks like it doesn’t connect.
Then if I reconnect my mouse and keyboard it will work again.
How to fix this problem.
I have this before rebooting :
nvidia@tegra-ubuntu:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 001 Device 003: ID 03f0:2b4a Hewlett-Packard
Bus 001 Device 005: ID 03f0:094a Hewlett-Packard Optical Mouse [672662-001]
Bus 001 Device 002: ID 214b:7250
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
nvidia@tegra-ubuntu:~$
and this after rebooting :
nvidia@tegra-ubuntu:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 214b:7250
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
nvidia@tegra-ubuntu:~$
Thank you
A minor possibility is that it is a power delivery issue. Do you have a powered HUB you can test with (power delivered by something other than the Jetson)?
Hi,
I was thinking about power. In my configuration, I use USB3.0 hub. I connect the keyboard, mouse and USB-Ethernet adapter to this Hub. But if the problem is the power supply. Why does everything work when reconnection one of the devices?
It certainly could still be software, but the amount of power required for working (stable working) might be wrong for just a tiny fraction of a second and cause a failure. Booting one way might get around this, but booting another way might just have that tiny power spike the USB doesn’t work well with. The idea here is merely as a test to see if providing all power to the HUB using a separate power supply differs from a HUB pulling power from the Jetson.
Most people tend to think of power delivery as a certain voltage and current, but as you go into computing the moment of power stability might change from a small fraction of a second stability requirement to something on the order of a tiny fraction of a microsecond. Some of the stability requirements during power on (or power reset) are why this comes to mind for me, and is perhaps the only simple test to start with. There may be other ways to test, but if you live in the embedded world you’ll still find it handy to have an externally powered HUB for testing.