Jetson Xavier NX USB port issue


Recently I used Jetpack 4.6.3 to reflash my Jetson Xavier NX.
I used USB port to conntect to my keyboard, mouse and two GNSS receivers. My GNSS receivers are: Sparkfun Ublox receiver.
However, the problem I encountered was that when I boot my Jetson Xavier NX I found that some USB ports could not recongnize the keyboard/GNSS receiver, and even I plugged two GNSS receivers, it could only recongized one, as far as I know, in the Jetson the name of the USB port should be: /dev/ttyACM0 and /dev/ttyACM0 or /dev/ttyUSB0 or /dev/ttyUSB1. However, there was just one device to be recongnized: /dev/ttyACM0.

Do you have any idea about that? Thanks.


This topic belongs in the Jetson category. I have moved it over for you.

Which port is being used on the Jetson? Is this a dev kit (SD card model, versus eMMC model)?

In particular, are you looking at plugging those devices into the Jetson’s full-sized USB type-A ports (the “standard front panel port” of a PC)? Or are you working with the micro-OTG port?

I’ve never seen one of these, but I looked this up, and it looks like the Ublox has a micro-B (or micro-OTG) connector on it for a USB serial UART (setting 38400 8N1 over USB). Is it correct that you are using a micro-B cable at the Ublox end, and a full-sized type-A connector at the Jetson end? If you monitor “dmesg --follow” on the Jetson, and then plug in the Ublox, what additional log lines occur as a result of plugging in the Ublox?

Thanks for your quick reply!
I used the version “emmc model”. I used the Jetson USB type-A port as you said, my Ublox GNSS was sparkfun with one side type-C while another side was type-A (to Jetson). I will consider using dmesg --follow and give you feedback, thx for you help!


When I plugged the GNSS receiver to another Jetson it worked, another Jetson was Jetson Nano with Jetpack 4.6.1. I did not get it why I have this problem.

I found the problem. I used Jetson Xavier NX emmc version, however when I used this: GitHub - jetsonhacks/rootOnNVMe: Switch the rootfs to a NVMe SSD on the Jetson Xavier NX and Jetson AGX Xavier to let my Jetson boot from NMVE SSD card, the problem occurred that when I plug the USB the was not USB device detected… Do you think it is the problem from device tree? Thx

Yes, odds are quite high that this is a device tree not setting up the drivers to find the USB correctly. The eMMC models of NX are sold separately, and you have to use a third party carrier board (I suppose you could have both an SD card model and the eMMC model, and then transfer the eMMC module onto the SD card carrier board, but the device tree might need to be adjusted for that too). The basic question is whether you have a third party carrier board, and if so, did you get the flash software from the third party? This is usually how one would get the correct device tree.

Many thanks for your quick reply!

Yes I used the third party carrier board here: NVIDIA Nano/Xavier NX/TX2 NX Carrier PCB | MYBOTSHOP.DE, 277,95 € A206 version here. I did not get the flash software from the third part. Do you have any idea about how to solve this device tree problem.

I found an interesting solution, it seems to be another solution for this issue. However I did not really get how to solve it: [BUG]USB mouse and keyboard not functioning after reboot · Issue #3 · jetsonhacks/rootOnNVMe · GitHub

I see three different carrier boards at that URL. Which carrier board? For that particular board they should have a software download, or instructions on how to update the NVIDIA content.

Usually the only problem with an external boot device is that an update might install the wrong device tree if it thinks this is the NVIDIA carrier board. One detail of using someone else’s device tree is that they should provide this as a package, or else in such a way that a package won’t overwrite it. Is there any kind of download or board support package (BSP) provided with that carrier board? Or is there a statement that this carrier board uses the NVIDIA BSP?

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.