I’m trying to update my Jetson Orin Nano Developer Kit firmware so I can upgrade from JetPack 5.1.2 (Jetson Linux 35.5) to JetPack 6.x. SDK Manager can’t detect the board.
Here’s what I did. I’m running Windows 11 on my laptop. The Jetson is powered through the barrel jack and connected to the laptop with a USB-C data cable (I confirmed it can transfer data by testing it with my phone). Inside VirtualBox I have an Ubuntu 24.04 VM with the NVIDIA SDK Manager installed. VirtualBox Extension Pack is installed, I set the VM USB controller to USB 3.0, and I added USB filters for “NVIDIA Corp. APX” and “NVIDIA Linux for Tegra.”
The problem is that nothing shows up in lsusb inside the VM. Running lsusb | grep -i nvidia gives no output. SDK Manager says “could not detect a board.” On Windows, I do hear the USB connection chime when I plug the Jetson in, but Device Manager doesn’t show anything obvious for NVIDIA APX.
If I skip the REC jumper, the board boots normally into Ubuntu, so the board itself is fine. The issue only happens when I try to enter recovery mode: the VM never sees the APX device. I also tried different USB ports and a second cable, but the result is the same.
Is my jumper sequence correct for putting the Orin Nano into recovery mode? Should I expect to see an APX device appear in Windows Device Manager, and if it doesn’t, does that mean I’m not actually in recovery mode?
Is it possible that using VirtualBox for this flashing step is the root cause, and I should be running SDK Manager directly on Windows or on a native Ubuntu machine instead?
*** Please note that this reply is generated by LLM automatically ***
To address the issue of updating the Jetson Orin Nano Developer Kit firmware and entering recovery mode, let’s break down the steps and troubleshoot the process.
Recovery Mode Sequence:
The jumper sequence you used to put the Jetson Orin Nano into recovery mode is correct:
Power off the Jetson.
Place a jumper between REC and GND (second and third pin).
Plug in the barrel power and the USB-C cable to the host.
Short RST to GND (fourth and fifth pin) and then remove both jumpers.
This sequence should put the Jetson Orin Nano into recovery mode.
Expected Behavior:
When the Jetson is in recovery mode, you should see the APX device appear in the Windows Device Manager. The APX device is a virtual device that represents the Jetson in recovery mode.
Troubleshooting Steps:
Verify the USB connection: Ensure that the USB-C cable is securely connected to both the Jetson and the host machine. Try using a different USB port or a different cable to rule out any issues with the current setup.
Check the VirtualBox USB settings: Ensure that the VirtualBox USB controller is set to USB 3.0 and that the USB filters are correctly configured for the NVIDIA APX device.
Verify the SDK Manager version: Ensure that the SDK Manager version is compatible with the Jetson Orin Nano and the host machine’s operating system.
Try running SDK Manager directly on Windows or a native Ubuntu machine: As you mentioned, it’s possible that using VirtualBox for this flashing step is the root cause of the issue. Try running SDK Manager directly on Windows or a native Ubuntu machine to see if the issue persists.
Comparison with Other Scenarios:
In the provided context, there are several other scenarios related to Jetson Orin Nano and recovery mode:
“Jetson Orin Nano Developer Kit – Black Screen and Fan Stops After Boot (JetPack 5.1.3)” suggests that there might be an issue with the boot process, but it’s not directly related to the recovery mode sequence.
“Booting issue” mentions a booting issue with the Jetson Orin Nano, but it’s not clear if it’s related to the recovery mode sequence.
“Optimizing Boot Time on Jetson Orin with Jetpack 6.2” provides information on optimizing boot time, but it’s not directly related to the recovery mode sequence.
In summary, the issue you’re experiencing is likely related to the VirtualBox setup or the USB connection. Try the troubleshooting steps mentioned above, and if the issue persists, consider running SDK Manager directly on Windows or a native Ubuntu machine.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
The fan DOES stop while in, supposedly, recovery mode. Does that indicate it is not in recovery mode? And I don’t see anything related to Nvidia in my windows device manager, but since the filters in VM show Nvidia related options, I’m assuming the device gets recognized by VM but not by Windows device manager.
I have had similar issues i used a high spped usb 3 cable that was 2 foot long longer cables or low end cables often just fall short also i used a usb2 port with the faster usb3 wire and sdk manager is a must will not work with out it try getting a dedicated cable that worked for me also i used ubunto 20.04 for compatability with nano
I make it work through in virtual box 6.1 and just add new usb APX driver for my virtual machine in settings of VM please find bellow pictures .but I have both MicroSD and SSD in Jetson Orin Nano Super dev Kit and want to boot from micro sd not from SSD let’s see what will happen .make sure you download apx driver in windows and make usb visible from your virtual box and if you try and showing you from VM apx driver try to remove and add power again for the kit.
so no need for Ubuntu native any more.
