Jetson AGX Orin flash success, but boot always reboot

I used SDKmanger to flash the latest version of Jetson Linux to Jetson’s EMMC, but the flash failed.

Version information:
JetPack_6.2.1
Jetson Linux_36.4.4

I downloaded the BSP and Simple root filesystem sources from the website, and recompiled a new image.

Flash uses the command:
sudo BOARDID=3701 FAB=500 BOARDSKU=0000 BOARDREV=P.0 . /flash.sh jetson-agx-orin-devkit internal

The flash shows success, but the boot always rebooting and won’t go to the desktop.
I don’t know what the problem is and how to fix it.
Please help me to solve the problem. Thank you.

I will provide the boot log.
boot.log (72.1 KB)

*** Please note that this reply is generated by LLM automatically ***

To address the issue you’re experiencing with flashing and booting the Jetson AGX Orin, let’s break down the key points from your description and the context provided:

  1. Flashing Process: You used SDK Manager to flash the latest version of Jetson Linux to the Jetson’s eMMC, but the flash failed. You then downloaded the BSP and Simple root filesystem sources, recompiled a new image, and flashed it using a specific command.

  2. Version Information: You’re working with JetPack 6.2 and Jetson Linux 3.6.44.

  3. Flashing Command: The command you used for flashing is sudo BOARDID=3701 FAB=500 BOARDSKU=0000 BOARDREV=P0 flash.sh jetson-agx-orin-devkit internal. This command specifies the board ID, fabrication number, board SKU, and board revision, indicating a customized flashing process for the Jetson AGX Orin development kit.

  4. Symptoms: After flashing, the system shows a successful flash but always reboots and fails to reach the desktop. You’ve provided a boot log (721 KB) which could contain crucial information for diagnosing the issue.

Given the context and your description, here are several potential issues and steps you could take to troubleshoot and possibly resolve the problem:

  • Boot Log Analysis: The first step would be to carefully analyze the provided boot log. Look for any error messages, warnings, or unusual behavior that could indicate why the system is rebooting. Common issues might include driver problems, filesystem errors, or configuration mistakes.

  • Comparison with Known Issues: The context mentions several issues related to boot failures, secure boot, and flashing problems on various Jetson devices, including the Jetson AGX Orin. Comparing your symptoms and boot log with these known issues might provide insights or solutions. For example, issues like “Boot fails after restoring a Jetson Orin NX” or “Call trace observed during boot in preempt-rt kernel on Jetson AGX Orin” could be relevant if they discuss similar error messages or system behaviors.

  • Secure Boot and Encryption: Since you’re flashing a new image, ensure that secure boot settings and any encryption (like ROOTFS_ENC=1 mentioned in the context) are properly configured. Misconfiguration in these areas could lead to boot failures.

  • Flashing Process Verification: Double-check the flashing process, especially the command used. Verify that the BOARDID, FAB, BOARDSKU, and BOARDREV parameters match your hardware. Incorrect parameters could result in a flash that appears successful but leads to boot issues.

  • Recompilation of BSP and Root Filesystem: You’ve recompiled the BSP and Simple root filesystem sources. Ensure that this process was done correctly, and all necessary patches or configurations for your specific hardware and JetPack version were applied.

  • Comparison with Jetson Orin Nano Issues: Although your issue is with the Jetson AGX Orin, comparing notes with issues experienced by Jetson Orin Nano users (like flashing failures or boot loops) might provide useful insights, given the similarities between the devices.

  • Seeking Community or Official Support: If the issue persists, consider seeking help from the NVIDIA developer community or official NVIDIA support channels. They might have encountered similar issues or have specific guidance for your setup.

In conclusion, resolving your issue will likely involve a detailed analysis of the boot log, careful verification of the flashing process and parameters, and potentially seeking support from communities or official channels familiar with Jetson devices and JetPack.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

I use command as sudo BOARDID=3701 FAB=500 BOARDSKU=0000 BOARDREV=P.0 . /flash.sh jetson-agx-orin-devkit internal

Verify that the BOARDID, FAB, BOARDSKU, and BOARDREV parameters match your hardware is OK.

I need help detailed analysis of the boot log, find to problem.

I will look again to see if the Jetson Orin Nano has a similar problem.

Hi,

Some questions to confirm:

  • Is your AGX Orin using a devkit or a carrier board?

Thanks

I use Jetson AGX Orin Devkit.

Hi,

How do you get those parameters?
Do you use below sections to get the board config?

Have you flashed with r36.4.3 or r36.4 successfully before?

Thanks

Have you flashed with r36.4.3 or r36.4 successfully before?

NO! Not used these version.

How do you get those parameters?
Do you use below sections to get the board config?

There’s a problem with this one, so there’s an error in the version, so I’m retesting on a different one.
And I’m changing the version to BOARDID=3701 FAB=500 BOARDSKU=0000 BOARDREV=J.0

The cofig get to flash log
image
And then re-flash, flash command:
sudo BOARDID=3701 FAB=500 BOARDSKU=0000 BOARDREV=J.0 ./flash.sh jetson-agx-orin-devkit internal
And flash after boot log, it has same problem
devkit_boot.log (80.4 KB)

Hi,

Some questions to confirm:

  • Is your AGX Orin a dev kit or a custom board?

If you are using a dev kit, could you do below steps

  • Make the AGX Orin in recovery mode
  • Use lsusb to check whether in recovery mode
  • Run below commands as doc suggest
$ sudo ./flash.sh jetson-agx-orin-devkit internal

Thanks

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