The connected Jetson device is not ready for flash

Hi,

I’m reaching out regarding an issue I encountered while using the Jetson AGX Orin Development Kit for the first time. I’ve attached a folder containing relevant photos of the error messages and connections.

Here’s a summary of the steps and the problem:

  1. After opening the terminal on the Jetson, I ran sudo apt upgrade. However, midway through the upgrade, the device unexpectedly suspended.
  2. When attempting to reboot, the screen displayed only a blue screen. I tried several reboots, but the issue persisted. Additionally, I couldn’t access the Jetson terminal from my PC via SSH as the SSH package wasn’t installed.
  3. I downloaded SDK Manager on my PC, set the Jetson to recovery mode, and verified recovery mode via the PC terminal. However, when attempting to flash the Jetson, I received an error stating, “The connected Jetson device is not ready for flash.”
  4. I also tried flashing directly from the terminal, but I encountered another error.

I am using the original USB cable provided with the Jetson kit, and all photos, including error messages and wiring, are included in the attached folder.

Thank you for your time and assistance.
jetson-error.zip (1.4 MB)

Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device:
Jetson/General debug - eLinux.org
And get logs of host PC and Jetson device for reference. If you are using custom board, you can compare uart log of developer kit and custom board to get more information.
Also please check FAQs:
Jetson AGX Orin FAQ
If possible, we would suggest follow quick start in developer guide to re-flash the system:
Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
And see if the issue still persists on a clean-flashed system.
Thanks!

Hi mostafa20497225,

I’ve checked the blue screen image shared from you.
It seems the board has booted up and the issue is relating to gdm.

About the flash issue, have you referred to the instruction to reconnect USB cable and reflash again?
Are you using standalone Ubuntu host PC and confirm that there’s only one devkit connected?

You can also refer to the following instruction to capture serial console log for further check.
NVIDIA Jetson Orin AGX - In Board - Getting in Board - Serial Console

Hi Kevin,
The problem was resolved. Interestingly, I had my Bluetooth mouse USB plugged into my laptop, and after removing it, the flashing started, so it is not only about the usb hub i think it better to every one to take off any other connected usb from the host pc.

Do you mean the issue is relating to your USB device(Bluetooth mouse) connected on your host?

yes exactly

Okay, thanks for sharing the experience since we’ve not received similar behavior before.

Hi, I have the same problem, but I haven’t solved this yet, I don’t have any USB device connected, just the cable connected from the AI ​​device to the Host PC with UBUNTU, where exactly should I connect the Jumper? (model: reComputer J40)

Hi,
İf you are using the development kit it is better to use the usb cable that comes with it, because some usb cables can not send data, if you can check if your jetson is on recovery mode from your host pc that mean everything is fine, considering the usb pc port i don’t have information about it but probably this isn’t the problem. One thing also so important there is only one jetson type c port that you can detect from it that is the jetson is on recovery mode and you can flash on it.

Hello, thanks for your reply, the device does not have a USB cable, I got a USB cable via Amazon, which works perfectly with other devices to send data (mobile, external hard drive, etc.), I have even tried with a couple of USB cables and it shows me the same error.
Is the jumper connected correctly? I’m attaching an image…

You are welcom, notice that i didn’t use jumbers in the process, i think you are using another method maybe because your jetson kind is different from mine

Oh… you didn’t use jumpers… well, I have to use them because otherwise I can’t access recovery mode