Jetson Orin Nano – EEPROM Layout Issue and Flashing Failure

Issue Overview

Users of the Nvidia Jetson Orin Nano Developer Kit are experiencing boot failures and flashing issues. The problem typically occurs after attempting to upgrade JetPack from version 5.1.1 to 5.1.3 using OTA (Jetson Linux 1). After the upgrade and subsequent reboot, the device gets stuck during the boot process, displaying only the NVIDIA logo.

When attempting to re-flash the SSD using NVIDIA SDK-Manager, users encounter a CRC8 checksum mismatch error. This error suggests potential EEPROM modifications or corruption. The issue affects the device’s ability to boot properly and prevents successful flashing of the system.

Possible Causes

1. Corrupted EEPROM Data: The EEPROM layout appears to be incorrect or corrupted, not matching the expected layout for the Jetson Orin Nano.

2. Failed OTA Update: The upgrade process from JetPack 5.1.1 to 5.1.3 may have been interrupted or failed, leaving the system in an inconsistent state.

3. Incompatible Firmware: The attempted upgrade might have introduced firmware incompatibilities with the existing hardware configuration.

4. Hardware Issues: There could be underlying hardware problems affecting the EEPROM or other critical components.

5. Incorrect Board Identification: The system might be failing to correctly identify the board parameters (BOARDID, FAB, BOARDSKU) during the flashing process.

Troubleshooting Steps, Solutions & Fixes

1. Verify Board Information:

   • Confirm the correct board details:
     • SKU: 0003 or 0005 for Jetson Orin Nano 8GB
     • Module ID: 3767 for NVIDIA Jetson Orin NX and Nano module

2. Custom Flashing Command:
   Try flashing the board using the following command, which bypasses some checks:

   sudo BOARDID=3767 FAB=300 BOARDSKU=0003 ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-orin-nano-devkit internal
   

   Note: Adjust the path to flash_t234_qspi.xml if necessary.

3. Skip EEPROM Check:
   If the above command fails, try this alternative that skips the EEPROM check:

   sudo SKIP_EEPROM_CHECK=1 BOARDID=3767 BOARDSKU=0003 ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-orin-nano-devkit internal
   

   This command may help if the EEPROM data is incorrect.

4. Downgrade to Previous JetPack Version:
   If issues persist, try flashing with an earlier version, such as JP5.1.3 (L4T R35.5.0):

   a. Download the Driver Package (BSP) and Sample Root Filesystem from Jetson-Linux-r35.5.0.

   b. Set up the flashing environment:

   mkdir jetson_linux
   cd jetson_linux
   sudo tar -xpvf Jetson_Linux_R35.5.0_aarch64.tbz2
   cd Linux_for_Tegra/rootfs/
   sudo tar -xpvf ../../Tegra_Linux_Sample-Root-Filesystem_R35.5.0_aarch64.tbz2
   cd ..
   sudo ./apply_binaries.sh
   sudo ./tools/l4t_flash_prerequisites.sh
   

   c. Flash using the command from step 2 or 3.

5. Serial Console Debugging:
   If boot issues persist, use a USB-to-TTL cable to access the serial console for more detailed boot logs. This can help identify where exactly the boot process is failing.

6. Check for Hardware Issues:
   If all software-based solutions fail, consider the possibility of hardware problems. Consult with NVIDIA support or your hardware provider for potential RMA or repair options.

7. Prevent Future Issues:

   • Always create a backup before performing major updates.
   • Ensure stable power supply during flashing and update processes.
   • Keep your JetPack and L4T versions up to date, but research compatibility before upgrading.

By following these steps, users should be able to recover their Jetson Orin Nano Developer Kit from boot failures and flashing issues. If problems persist, it’s recommended to contact NVIDIA support for further assistance.