AGX Xavier can power on cannot reach OS as if it hasn't been flashed

Dear all,

I encountered a strange and very annoying problem today.
As usual, I tried to connect in ssh to my AGX Xavier. Nothing happened. So I tried to observe if the card connection is detected via the command dmesg --follow, without consequences.
My cable is not faulty, since the card is detected if it is started in recovery mode.
So I tried to connect a screen in hdmi, but without effect. The card behaves as if it had never been flashed, whereas only yesterday I was using it.

Has anyone come across this problem before ? How to solve it?
I would like, if possible, not to have to reflash my card

Thx

Nothing happened

Really nothing? Usually it will time out, or the connection will be rejected or something ‘nothing’ is a rare result.

I’ve had some similar-sounding problems recently that I’m still troubleshooting. But in my case it seems to be an SSD connected with a SATA to USB adapter - the Xavier completely fails to boot if the drive is connected, but it happy to access if it is plugged in after boot.

Consider unplugging peripherals and retrying.

You also don’t mention what version of the system you have installed, which can have a significant impact on what things are broken.

Can you log in via serial console? If so, then what is the output of “dmesg” and “ifconfig”?

If you know the IP address of the Xavier, then can your host PC ping that address?

If the above fails, and you connect the USB-C to your host PC, and put the Xavier in recovery mode, then do you see anything from “lsusb -d 0955:7019”?

I flashed my Jetson Monthes ago with the Jetpack 4.4 DP
I’he tried to plug and unplug my device many times but the problem remains the same.
indeed, I had a timeout

The card behaves exactly as if it was not flashed

I’m actually trying to log via serial console
surprisingly, the ping works

I’ didn’t mentioned it but I detected the card while using recovery mode.
The command lsusb -d 0955:7019 showed me Bus 001 Device 006: ID 0955:7019 NVidia Corp.

Once again, the card behaves exactly as if it was not flashed

If you can ping, then perhaps it is fully functional, but video failing and making function invisible. Can you ssh to the Jetson?

Has your monitor changed? Is the monitor purely HDMI without adapters?

So connected to a serial console directly via UART1 on the RasPi connector allows you to login? If not, try it.

usually i use the ssh connection only, this is the first thing i tried to do. No connection, timeout
I also have a monitor (with pure hdmi) that I use from time to time, which has not been changed

I don’t have all the necessary connectors for a connection to the pins.
So I tried a serial console connection via the micro usb port using minicom 2.7.1.
/ dev / ttyUSB3 is detected but “disconnected”

About:

…the micro-B USB is the correct method of reaching the serial console on the Xavier.

If you monitor “dmesg --follow” on the host PC as you plug in the micro-B USB cable what do you see? It should mention the ttyUSB being created (power has to be applied to the Jetson, but it won’t matter if it is booted or not, it should work).

There is more than one serial USB device on that micro-B connection…and since I have a lot of serial devices on my PC it doesn’t start at ttyUSB0. For my case (as an example), the plugin results in:

[15893.930863] usb 1-12.4.3: new high-speed USB device number 11 using xhci_hcd
[15894.039287] usb 1-12.4.3: New USB device found, idVendor=0403, idProduct=6011, bcdDevice= 8.00
[15894.039291] usb 1-12.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15894.039294] usb 1-12.4.3: Product: Quad RS232-HS
[15894.039296] usb 1-12.4.3: Manufacturer: FTDI
[15894.099314] ftdi_sio 1-12.4.3:1.0: FTDI USB Serial Device converter detected
[15894.099331] usb 1-12.4.3: Detected FT4232H
[15894.104566] usb 1-12.4.3: FTDI USB Serial Device converter now attached to ttyUSB5
[15894.107297] ftdi_sio 1-12.4.3:1.1: FTDI USB Serial Device converter detected
[15894.107309] usb 1-12.4.3: Detected FT4232H
[15894.112363] usb 1-12.4.3: FTDI USB Serial Device converter now attached to ttyUSB6
[15894.115310] ftdi_sio 1-12.4.3:1.2: FTDI USB Serial Device converter detected
[15894.115324] usb 1-12.4.3: Detected FT4232H
[15894.120356] usb 1-12.4.3: FTDI USB Serial Device converter now attached to ttyUSB7
[15894.123309] ftdi_sio 1-12.4.3:1.3: FTDI USB Serial Device converter detected
[15894.123324] usb 1-12.4.3: Detected FT4232H
[15894.128361] usb 1-12.4.3: FTDI USB Serial Device converter now attached to ttyUSB8

My Fedora host uses the last of the devices, ttyUSB8, not the first device. Possibly your host will enumerate in a different order than mine. Make sure both first and last serial devices have no serial console activity.

I like gtkterm, and an example in using this (my user is a member of group dialout, and so I don’t need to use sudo):
gtkterm -b 8 -t 1 -s 115200 -p /dev/ttyUSB8
(if you don’t have this, then “sudo apt-get install gtkterm”)

One of the reasons I like gtkterm (aside from a more modern interface than minicom) is the ease of logging.

If you can verify serial console does not correctly output, then you probably have an actual hardware failure.

As I said before, dmesg --follow did showed anything when I plug the usb-c cable.
Finally, I decided to reflash my card, so thank you for your help

I’have a contact in nvidia, I’ll post here a solution when I have one

The “default” console is TCU0, which I guess is the HDMI screen. I tried changing it to UART1 in the extconf file in /boot but there are a few other places to change it to move the bootup console.

This happened to us on our OEM device – we swapped the module and “retired” the old one.

Good luck

Larry