I have been using my Jetson Xavier in my graduate school research for over a year and it has been performing well without any issues. I booted it up this morning and tried connecting to via ssh as I usually do every morning, but it failed to connect. I figured the jetson just did not connect to the network on boot up like it usually does so I plugged in the HDMI and tried to get in that way. However, that did not work because there was no HDMI output. Additionally, I connected my laptop to the jetson with the micro-usb, and tried “ssh 192.168.55.1” but that did not work (pinging also did not work). So since I couldn’t get in wireless, through hdmi, or through USB, I decided to just try and reflash the board (my code is backed up on github anyways). I was able to get the Jetson Xavier into recovery mode and the SDK Manager was able to identify my device, but I was unable to reflash the board since my USB connection isn’t working.
The light indicating power is on and the fan on the Jetson is spinning so its not a complete brick right now but I cannot find a way to get in. Additionally, my laptop is able to identify that it is connected via usb because it shows up when I run “lsusb” . Also, when I run “sudo dmesg --follow” and connect my laptop with the jetson xavier via micro-usb, I get this:
[438948.542669] usb 1-1: new high-speed USB device number 56 using xhci_hcd
[438948.691030] usb 1-1: New USB device found, idVendor=0403, idProduct=6011, bcdDevice= 8.00
[438948.691045] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[438948.691053] usb 1-1: Product: Quad RS232-HS
[438948.691059] usb 1-1: Manufacturer: FTDI
[438948.697746] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
[438948.697829] usb 1-1: Detected FT4232H
[438948.698197] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
[438948.699063] ftdi_sio 1-1:1.1: FTDI USB Serial Device converter detected
[438948.699185] usb 1-1: Detected FT4232H
[438948.699435] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB1
[438948.700072] ftdi_sio 1-1:1.2: FTDI USB Serial Device converter detected
[438948.700151] usb 1-1: Detected FT4232H
[438948.700417] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB2
[438948.701030] ftdi_sio 1-1:1.3: FTDI USB Serial Device converter detected
[438948.701094] usb 1-1: Detected FT4232H
[438948.701417] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB3
I’m not really sure where to go from here. If anyone can help me find a solution and help me recover this board I would really appreciate it as it would save me a ton of time and effort!
Hi @jfernandez75,
Have you tried to connect via serial? That since it looks like the serial devices are detected.
You can check how to do do in this link
Do you have the failing flash logs? Maybe thay have a bit more info.
Regards,
Andres
Embedded SW Engineer at RidgeRun Contact us:support@ridgerun.com Developers wiki:https://developer.ridgerun.com/ Website:www.ridgerun.com
I attempted to connect to through the serial device via gtkterm but I just get a black screen for all the /dev/USB* ports I connect to.
When I flash I get to the part where it wants me to use the jetson to setup password and username, but I can’t do that because nothing is coming out of the hdmi. Additionally, I tried setting it up headless with USB but I can’t get in through the USB either. So when the screen below pops up in the sdkmanager I have to just skip it:
The logs for the “flash” also show that nothing can be found on that ip adress (the usb one):
7:47:51 INFO: Start to check if if default ip avaliable in ip addr
07:47:51 DEBUG: running command < true >
07:47:51 INFO: CUDA Cross Compile Package on Host - host: Preparing to unpack .../00-libctf0_2.38-4ubuntu2.5_amd64.deb ...
07:47:51 INFO: command finished successfully
07:47:51 DEBUG: running command < ip addr | grep 192.168.55.1 >
07:47:51 INFO: exec_command: ip addr | grep 192.168.55.1
07:47:51 DEBUG: command terminated with error
07:47:51 ERROR: Default ip is not available. Please make sure the default ip is shown in ip addr, or use a custom ip instead.
07:47:51 INFO: CUDA Cross Compile Package on Host - host: Unpacking libctf0:amd64 (2.38-4ubuntu2.5) over (2.38-4ubuntu2.4) ...
07:47:51 INFO: CUDA Cross Compile Package on Host - host: Preparing to unpack .../01-binutils-x86-64-linux-gnu_2.38-4ubuntu2.5_amd64.deb ...
07:47:51 INFO: CUDA Cross Compile Package on Host - host: Unpacking binutils-x86-64-linux-gnu (2.38-4ubuntu2.5) over (2.38-4ubuntu2.4) ...
07:47:51 INFO: CUDA Cross Compile Package on Host - host: Preparing to unpack .../02-libbinutils_2.38-4ubuntu2.5_amd64.deb ...
07:47:51 INFO: CUDA Cross Compile Package on Host - host: Unpacking libbinutils:amd64 (2.38-4ubuntu2.5) over (2.38-4ubuntu2.4) ...
Let me know if anyone things this can be salvaged!
Have you tried without the sdk manager?
You can follow this guide NVIDIA Jetson Xavier - Flashing Board.
One thing to verify the serial port easily is, first unplug it from the pc, then do:
ls /dev/tty*
Take note of the devices and plug the Jetson back to the pc and do the ls cmd again, and check if any new device appeared. I usually use minicom like:
sudo minicom -D /dev/ttyNAME
Where name is the dev name that appeared on the ls cmd. And then when is connected I go to config and disable Hardware Flow Control. Ctrl-a z and then press O, go to Serial port setup and press F, then esc to go back. Reboot the xavier and then check if there is any log at all.
Thank you for this suggestion! By looking through the site you sent I figured out that my flashing issue came from the fact that my host computer running the sdk manager software was running Ubuntu 22. Since the Jetson Xavier is older, I believe the newest jetpack version available is 5.2 which is only able to be installed by a host computer running Ubuntu 18 and 20. I was able to find a linux laptop running Ubuntu 20 in lab and this allowed me to reflash my Xavier! Now I just need to redownload all my packages and dependencies. I am still unsure what the cause of the original issue was (no hdmi out, no network connection, and no usb connection), but at least I was able to recover the xavier. Thank you for all your help!
