Error Flashing NVMe on Nvidia Jetson Orin Nano Dev Board

Issue Overview

Users of the Nvidia Jetson Orin Nano Dev Board are experiencing issues while attempting to flash NVMe storage. The symptoms include error messages during the flashing process, specifically indicating failures related to non-QSPI storage. The errors appear when executing the command:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p“-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 p3509-a02+p3767-0000 internal

The logs show warnings about skipping certain partitions due to unspecified images and ultimately result in a failure to initialize the NVMe device. After rebooting, users encounter a "Busy Pin" message in the serial output, indicating that the system is unable to initialize the storage device.

The issue occurs during the setup phase when users attempt to flash their custom-designed boards based on the Orin Nano architecture. The hardware specifications include a custom board with an 8GB Orin Nano processor, and the software version used is Jetson Linux R35.3.1. The frequency of this issue appears to be consistent among users who have similar setups.

The impact of this problem significantly disrupts user experience, as it prevents successful system boot and operation, thereby hindering development efforts.

Possible Causes

• Hardware Incompatibilities: Custom board designs may not match the specifications required for proper flashing.

• Software Bugs or Conflicts: Issues in the flashing scripts or incompatibility with the selected configuration files can lead to errors.

• Configuration Errors: Using incorrect configuration files (e.g., p3509-a02+p3767-0000 instead of jetson-orin-nano-devkit.conf) can result in improper initialization of components.

• Driver Issues: Missing or incorrect drivers for NVMe or PCIe controllers may prevent successful device detection and initialization.

• Environmental Factors: Power supply issues or overheating may affect hardware performance during flashing.

• User Errors: Misconfigurations in device tree settings or command parameters can lead to failures.

Troubleshooting Steps, Solutions & Fixes

1. Verify Configuration Files:

   • Ensure that you are using the correct configuration file for your specific board design.
   • If using a custom board, compare your configuration against the official jetson-orin-nano-devkit.conf file.

2. Check Device Tree Settings:

   • Open the device tree source (DTS) file associated with your configuration and verify that PCIe settings are enabled.
   • For example, ensure that the PCIe controller is correctly configured in your device tree:

     pcie@141e0000 {
         ...
         status = "okay";
     };
     

3. Run Flash Commands with Correct Parameters:

   • Use this command if you are using the Orin Nano Dev Kit:

     sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p"-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-orin-nano-devkit internal
     

4. Check Logs for Errors:

   • Review both flashing logs (flash_nvme.log) and UART logs (uart_log.log) for any specific error messages that could provide insights into what went wrong during flashing.

5. Update Drivers and Firmware:

   • Ensure that all drivers and firmware are up-to-date as per Nvidia’s documentation.

6. Test with Different Hardware Configurations:

   • If possible, test your NVMe drive with another setup or use a different NVMe drive to rule out hardware defects.

7. Consult Documentation:

   • Refer to Nvidia’s official documentation on Jetson Module Adaptation and Bring-Up for guidance on configuring custom boards:
     Nvidia Jetson Developer Guide

8. Seek Community Support:

   • If issues persist, consider posting detailed logs and configurations on forums for community assistance.

9. Best Practices:

   • Always back up existing configurations before making changes.
   • Use stable power supplies during flashing processes to avoid interruptions.
   • Document any changes made to configurations for future reference.

Unresolved aspects include specific details about certain configurations that may still need clarification from Nvidia or community experts regarding compatibility between different modules and board designs.