Jetson Xavier NX not being detected

I have developed a custom carrierboard following NVIDIA examples (P3509-A01)


I have flashed Ubuntu 20.04 JetPack 5.x onto it. The power logic seems to work as jetson seems to boot up normally. As I copied the Module Power ON/OFF logic from P3449_B01 carrier board. Always enabling Auto Power

I haver another carrier which i previously used, and currently for testing purposes the RTSO-6002-V3.2
Product Manual for RTSO-6002.pdf (1.4 MB)

When I connect my computer with a microusb to the RTSO-6002-V3.2 carrierboard then i can see that my computer has detected a new device. In addition if i use Debug uart RX and TX to see what is going on at the kernel level, then i can see that upon inserting USB Jetson detects it or basically does something.

When I connect it to my carrierboard then the logic seems to work GPIO 87 USB0_VBUS_Jetson is at 1.8V untill i connect the USB, when I connect the usb to my carrierboard then GPIO 87 USB0_VBUS_Jetson is grounded, at 0V. When measuring N and P datalines with multimeter then P upon being connected is usually at around 100mV and N jumps between 1V-3V so it seems that something is happening.

When I use Debug UART RX and TX to see what is going on then when connecting the USB absolutely nothing new is logged, not even an error message.

When routing i used altiums impedence calculator and diff pair settings to get the Trace impedance: Diff pair to 90 ohms, and their differences in length under 7.5 ps. The total lenght of one trace is 94.66 mm which is smaller than the maximum of 150mm.


It is a 6 layer board where it goes Signal - GND - PWR - SIGN - GND - Signal. The Micro USB is entirely on the top layer.

Coming back to power logic there doesn’t seem to be any issues because my carrierboard behaves very closely RTSO-6002-V3.2 where the consuption at 5V goes from 600mA to 1.3A to backto 600mA with a lot of jumps but stabilizing at that point.

Measuring the TVS diodes they seems to work fine, doesn’t seem like they’re broken. Visually it doesn’t seem like N or P datalines have been damaged.

Have I understood correctly that Jetson detects that it has been connected to a device if GPIO 87 (USB_VBUS_EN0 from pinmux table) is grounded. Then it should send out information to the device and everything should be working.

The RTC 3V3 coin battery seems to work aswell. The power pins i have left floating are PIN 178 MOD_SLEEP, PIN 210 CLK_32K_OUT, PIN 240 SLEEP/WAKE. Because the only functionalities I need are USB 3.0, UART, SPI, CAN, USB 2.0.

Is there any other way I could test what could be the issue?

Hi h15485545,

It seems your board not working after some connections.

What’s the exact Jetpack version in use?

Please just connect the debug UART and power it up check if there’s any log at this moment.
Or can you try if it could be detected in force recovery state?

I know that jetpack version is 5.x something, will edit or reply once i find out again

The log of dmseg when booted up and could access with uart
dmseg.txt (73.0 KB)

The log of initial bootup
bootup.txt (78.2 KB)

When i start the jetson in recovery mode nothing is logged in uart and no respone happens untill i press sys reset then it gets stuck in reset to recovery mode. After a very long period it seemed to exit recovery mode and boot up normally.

start_in_recovery_then_reset.txt (4.1 KB)

startup_from_stuck_in_recovery.txt (118.6 KB)

Also tried to turn off auto power on in. power control from auto to on. Did not help. It doesn’t seem like the problem is in the usb cable like it could hint to in the first photo because the usb cable works with other devices.

Afterwards i’ve also installed a custom linux onto jetson which was made for the RTSO6002 carrierboard it was a custom 18.02. With that i started detecting alteast something with UART related to usb but connections are still broken for both the micro usb and USB-A (3.0)
rtso_linux.txt (135.4 KB)

I’ve read in some other forums that another thing to try would be usb compliance and tuning test, but i don’t exactly get how it would help. How would it explain that the usb conenction works with the rtso-6002 but not with my custom one?

From the log you shared, it seems you are using JP5.1.4(r35.6.0) with K5.10.216.
Your board seems boot as expected but with several display related errors.

Have you tried running $ sudo reboot forced-recovery on your board to enter into force-recovery state?
You have to connect the microUSB port with host PC so that it can be detected through lsusb to check.