Jetson Orin Nano Boot Issue: Unresponsive Input Devices After Flashing to NVME SSD

Issue Overview

Users of the Nvidia Jetson Orin Nano 4GB with NVME SSD on an A603 Carrier board are experiencing a critical boot issue after flashing the Nvidia Ubuntu image using the SDK Manager. The problem manifests as follows:

• After flashing and rebooting, the system reaches the Ubuntu "License Agreement" prompt or login screen.
• At this point, both keyboard and mouse inputs become unresponsive, preventing any user interaction.
• The issue occurs consistently after flashing, regardless of using Runtime or Pre-Config OEM options.
• During the boot process, the keyboard appears to be functional (num-lock light responds, characters appear in boot log).
• Users cannot access the Setup (Esc) or Boot-Menu (F11) during startup.
• The blue LED stops flashing around the time the login screen appears.
• This problem seems specific to the A603 Carrier board setup, as the Orin Nano 8GB Dev-Kit works correctly with the same image on an SD card.

Possible Causes

1. Driver Incompatibility: The flashed image may lack proper drivers for the A603 Carrier board’s USB controller or input devices.

2. Firmware Mismatch: There could be a discrepancy between the firmware version and the flashed Ubuntu image.

3. Hardware Recognition Issue: The system might fail to recognize or initialize the USB ports or input devices after booting from the NVME SSD.

4. Boot Configuration Error: The boot process may be incorrectly configured for the NVME SSD, leading to partial initialization of system components.

5. Power Management Problem: There might be an issue with power delivery to USB ports or other peripherals after the initial boot stages.

6. Software Bug: A bug in the Jetpack 6.0 (rev.2) release could be causing this specific issue on the A603 Carrier board.

Troubleshooting Steps, Solutions & Fixes

1. Use Alternative Flashing Method:

   • Utilize the flashing scripts from the JetsonHacks GitHub repository.
   • Clone the repository:

     git clone https://github.com/jetsonhacks/bootFromExternalStorage.git
     

   • Follow the instructions in the repository to flash the system.
   • This method has been reported to resolve the issue for some users.

2. Check UART Console Logs:

   • Set up a serial debug console to access UART logs.
   • Use a USB to TTL serial cable connected to the Jetson’s UART pins.
   • Monitor the boot process and look for any error messages or abnormal behavior.
   • This can provide crucial information about where the boot process is failing.

3. Try Different Jetpack Versions:

   • If possible, attempt to flash an earlier or later version of Jetpack to isolate if the issue is version-specific.

4. Verify Hardware Connections:

   • Ensure all cables, especially those related to the NVME SSD and USB ports, are securely connected.
   • Try different USB ports for the keyboard and mouse, if available.

5. Update Firmware and BIOS:

   • Check for any available firmware updates for the A603 Carrier board.
   • Update the BIOS/UEFI if an update is available.

6. Modify Boot Arguments:

   • If you can access the bootloader, try adding or modifying boot arguments to enable more verbose logging or disable potentially problematic drivers.

7. Clean Installation:

   • Perform a complete wipe of the NVME SSD before flashing.
   • Ensure there are no remnants of previous installations that could interfere with the new setup.

8. Contact Nvidia Support:

   • If the issue persists, reach out to Nvidia support with detailed logs and system information.
   • Provide information about the specific hardware configuration, including the A603 Carrier board details.

9. Community Forums:

   • Post detailed information about the issue on Nvidia Developer Forums or other relevant community platforms.
   • Include logs, hardware specifications, and steps you’ve already taken to troubleshoot.

Remember to document each step of the troubleshooting process, noting any changes in behavior or new error messages that appear. This information can be crucial for diagnosing and resolving the issue, especially if escalation to Nvidia support becomes necessary.