Could not detect correct NVIDIA Jetson device connected to USB
Issue Overview
Users are experiencing difficulties detecting and flashing their NVIDIA Jetson Orin Nano 8GB Developer Kit with JetPack 6.0 DP. The primary symptom is an error message stating "Could not detect correct NVIDIA Jetson device connected to USB" when attempting to use the SDK Manager. This issue occurs during the initial setup and configuration process, preventing users from successfully updating the device’s software.
The problem manifests in two main scenarios:
- When trying to boot from a newly flashed SD card with the JetPack 6.0 DP image.
- When attempting to use the SDK Manager CLI through Docker on a Mac host machine connected to the Jetson Orin Nano via USB-C.
Users report that while the device is visible in lsusb output and network connectivity (ping) is established, the SDK Manager fails to recognize the Jetson device properly.
Possible Causes
-
Incorrect boot mode: The Jetson Orin Nano is not in the required force recovery mode for flashing and detection.
-
QSPI bootloader incompatibility: The existing bootloader may not be compatible with JetPack 6.0 DP, requiring an update.
-
USB connection issues: Faulty USB cables or ports could prevent proper device detection.
-
SDK Manager version mismatch: An outdated or incompatible version of the SDK Manager might not recognize newer Jetson devices.
-
Host system compatibility: Using a Mac as the host system might introduce compatibility issues with the SDK Manager or Docker setup.
-
Network configuration: Incorrect IP address settings or network connectivity problems between the host and Jetson device.
-
Developer Preview limitations: As JetPack 6.0 is a Developer Preview, it may have unresolved issues or limited device support.
Troubleshooting Steps, Solutions & Fixes
-
Enter Force Recovery Mode:
- Power off the Jetson Orin Nano.
- Connect the USB cable between the host computer and the Jetson device.
- Press and hold the Force Recovery button (located under the module).
- While holding the Force Recovery button, press the Power button.
- Release the Power button, then release the Force Recovery button after 2 seconds.
-
Verify USB Connection:
- Try different USB cables and ports.
- Ensure the USB-C cable supports both power and data transfer.
- Check lsusb output for "NVIDIA Corp." entry after entering force recovery mode.
-
Update QSPI Bootloader:
- Use JetPack 5.1.2 (stable release) to flash the device first:
sudo ./flash.sh jetson-orin-nano-devkit-qspi mmcblk1p1
- After successful flashing with JetPack 5.1.2, attempt to upgrade to JetPack 6.0 DP.
- Use JetPack 5.1.2 (stable release) to flash the device first:
-
Use SDK Manager on a Linux Host:
- If possible, switch to a Linux host machine instead of Mac for better compatibility.
- Install the latest SDK Manager from the NVIDIA website.
- Run SDK Manager with sudo privileges:
sudo sdkmanager
-
Manually Configure Network:
- Set a static IP on the host machine’s USB network interface:
sudo ifconfig [usb_interface] 192.168.55.1 netmask 255.255.255.0
- Ensure the Jetson device is set to 192.168.55.100.
- Set a static IP on the host machine’s USB network interface:
-
Use Command-Line Flashing:
- Download the JetPack 6.0 DP package and extract it.
- Navigate to the Linux_for_Tegra directory.
- Run the flash command:
sudo ./flash.sh jetson-orin-nano-devkit mmcblk0p1
-
Check SDK Manager Logs:
- Look for detailed error messages in the SDK Manager logs.
- On Linux: ~/.nvsdkm/sdkm.log
- On macOS: ~/Library/Logs/NVIDIA/sdkm.log
-
Use a Stable JetPack Release:
- If issues persist, consider using the latest stable JetPack release (e.g., 5.1.2) instead of the Developer Preview.
-
Community Support:
- If the problem remains unresolved, post detailed logs and steps taken on the NVIDIA Developer Forums for further assistance.
Remember to always back up important data before attempting any flashing or major system changes. If hardware issues are suspected, contact NVIDIA support or the retailer for potential RMA procedures.