QSPI Flashing Issues on Jetson Orin Nano for Mass Production

Issue Overview

Users are experiencing difficulties when attempting to flash QSPI on Jetson Orin Nano boards for mass production using the provided flashing scripts. The main symptoms include:

• The device attempting to boot from SDMMC interface instead of QSPI
• The device trying to boot over HTTP when Ethernet is connected
• Inconsistent behavior when running the flashing command multiple times
• Issues occurring on both custom carrier boards and devkits

These problems are preventing users from successfully flashing QSPI using Jetpack 5.1.2 to boot from cloned NVME, which is crucial for their mass production process.

Possible Causes

1. SDK folder integrity: Deleting and redownloading the SDK folder may have led to inconsistent behavior in the flashing process.

2. Command argument issues: Incorrect or incompatible arguments in the flashing command could cause unexpected boot behavior.

3. QSPI persistence: The QSPI may not be properly erased or overwritten when the flashing command is run multiple times, leading to inconsistent results.

4. Custom carrier board compatibility: Differences between custom carrier boards and devkits may introduce unforeseen issues in the flashing process.

5. Boot order configuration: Incorrect boot order settings might cause the device to attempt booting from unintended interfaces.

6. Software calling the flashing script: As mentioned by the user, the issue was ultimately traced to the program used to call the flashing script.

Troubleshooting Steps, Solutions & Fixes

1. Verify SDK integrity:

   • Ensure you have the correct and complete SDK folder for Jetpack 5.1.2.
   • If issues persist after redownloading, try using a known good copy of the SDK.

2. Use the correct flashing command:
   For Orin Nano devkits or custom boards, try the following command:

   sudo ./flash.sh -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal
   

   Note: This command may only work once on boards that do not come from devkits.

3. For multiple flashing attempts:
   Use the l4t_initrd_flash.sh script with appropriate arguments:

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

4. Check boot order configuration:

   • Review and modify the boot order settings to ensure QSPI is prioritized over SDMMC and HTTP.
   • Consult the Jetson Orin Nano documentation for specific instructions on configuring boot order.

5. Isolate Ethernet-related issues:

   • If the device attempts to boot over HTTP when Ethernet is connected, try disconnecting the Ethernet cable during the flashing process.
   • After successful flashing, reconnect Ethernet and verify that the boot order is correct.

6. Verify custom carrier board compatibility:

   • Ensure that your custom carrier board is fully compatible with the Jetson Orin Nano module.
   • Check for any known issues or required modifications for your specific custom board.

7. Review the program calling the flashing script:

   • As the user mentioned that the issue was in the program calling the flashing script, carefully review and debug this program.
   • Ensure that it’s correctly passing arguments and handling the flashing process as expected.

8. Consider using force flash option:
   If QSPI is not being properly erased between flashing attempts, try adding the --force-flash option to the command:

   ./tools/kernel_flash/l4t_initrd_flash.sh --force-flash -p "--no-systemimg -c bootloader/t186ref/cfg/flash_t234_qspi.xml" --network usb0 --external-device nvme0n1p1 jetson-orin-nano-devkit-nvme internal
   

9. Check for updates and patches:

   • Visit the NVIDIA Developer website for any recent updates, patches, or known issues related to QSPI flashing on Jetson Orin Nano.
   • Consider upgrading to the latest Jetpack version if available, as it may include fixes for these issues.

10. Seek support from NVIDIA:
    If issues persist after trying these solutions, consider reaching out to NVIDIA’s developer support or community forums for more specialized assistance with your specific setup and requirements.