Question: Jetson AGX Orin flash write error

Hello !

  • I’m using real Ubuntu PC and a custom board (Connected with USB2.0)

  • I completed two steps before flashing using SDK manager

  • Now I’m trying to reflash with the command.

  • but an error occurs when flashing from CLI or SDK manager.
    (with Recovery Mode)

  • Jetson_Linux_R35.4.1_aarch64.tbz2

  • Tegra_Linux_Sample-Root-Filesystem_R35.4.1_aarch64.tbz2


is the custom board made by a third-party vendor or yourself?

If it’s made by yourself, then you should know how to deal with device tree stuffs.
If it’s made by a third-party vendor, then ask the vendor for the correct way to flash the device.

Picture 2 is only applicable when you want to install JetPack component on a device on which L4T has been installed, and since not even the OS itself is flashed, what you are doing is definitely not feasible. You should also note that SDK Manager would not work with custom boards.

Finally, please at least take a screenshot instead of such a blurry picture…

1 Like

Incidentally, JetPack/SDKM can package its logs and you can post those (though it won’t matter if the custom carrier board requires different software from the third party manufacturer). For any command line you can log it via this appended to the end of the command:
2>&1 | tee log.txt

Example (I am making this up, I don’t know what the actual specifics are for your board, but it would be similar):

sudo ./ jetson-agx-orin-devkit mmcblk0p1 2>&1 | tee log_flash.txt

Then you wouldn’t need to use screenshots (much of those screenshots look unreadable).

Incidentally, the AGX Orin has USB 3 on the dev kit’s type-C port that is used for flashing. Does the third party carrier board not have a USB3 type-C? If not, what is the actual port?

H/W: I’m using a customer carrier board that I designed myself based on the schematic released by NVIDIA (Not a third party board)

Thank you for your help

log_flash.txt (480.4 KB)


Question about Recovery mode turn off method.
After entering Recovery Mode, I would like to know how to exit Recovery mode again.
(Even after attempting to turn the current Power Off/On or reset system, it continues to remain in Recovery Mode)
→ Is this a H/W problem?

Thank you

The actual flash appears to be successful. If there is a failure, then it is from what the flash installed, and not from the flash process itself.

Any flash in recovery mode, once flash completes, reboot is automatic. You might have noticed that first boot setup is automatic (not easy to tell if flash or boot failed), and that JetPack/SDKM installs optional components (such as CUDA) only after first boot account setup. This is because a fully booted Jetson’s ssh is used for the content copy. So what you think is “still recovery mode” is most likely not recovery mode, but is probably instead a full boot with video configuration failing.

What you will want to do is to monitor serial console on the Jetson itself during boot (which can also offer an alternate way to complete first boot account setup). Additionally, if you do not have graphics, and if for some reason first boot setup via serial console does not work, then you can also run this script in the “Linux_for_Tegra/” subdirectory prior to flashing to preinstall the admin account:
sudo ./

Do you have a serial console boot log from the Jetson itself?


First of all, I would like to thank you for your help.

I need to check two issues first.

  1. Serial console port
  2. Display

1. Serial port
I am not using Debug MCU (ATSAMD21G16B-AU) in the circuit and
After level shifting, I changed Orin’s UART3 port (H62, K60) to RS232 communication. (Figure below).
Is it OK?

2. Display (HDMI using)
In the P3737_A04_OrCAD_schematics file, Orin Module J60 (MODULE_SLEEP_N) was not used for VDD_3V3_HDMI output enable but was used for other control functions.
Do I need to reapply the actual DT file?

Thank you so much


Since your topic is “Jetson AGX Orin flash error” and currently there is no “flash write error”. Please file new topic for your next question…

I will also suggest this needs a new post for the other topic. One other suggestion though is that serial console is quite valuable, and short of an ARM DStream debugger (many thousands of dollars), it is going to be very difficult to debug the schematics. So if serial console does not work, then I would start with that. Then take a close look at whether you see a clock and query on the hot plug detect, SCL, and SDA. Many of the rearranged layouts simply lack device tree edits related to this.


sudo ./
“command not found” ?

This is at the host PC side where flash software is located. It would require you to first cd to the location of the “Linux_for_Tegra/” subdirectory. Somewhere under:

This only needs to be run once, and from that time forward, each flash will already have first boot setup complete with the name/password that you used.

1 Like


I succeeded in Flash writing.

Thanks for your help

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