I have a new NVIDIA Jetson Orin Nano and I’m performing the initial setup. I am following the official documents for booting through NVMe SSD on the Jetson directly. I have done the following:
Attached 2 TB NVMe SSD securely into the Jetson (no microSD)
Install Ubuntu 22.04 on WSL 2 as I have a Windows laptop
Download the SDK and launch via WSL2’s Ubuntu22 environment
Short the pins 9 and 10 to go into recovery mode
Connect the USB-C cable to my laptop and the Jetson (C-type at the Jetson end)
Plug in the power and switch on
I see the Jetson turn ON and the fan start. I have checked the connection of my USB-C cable and it works fine.
After all this, the SDK manager is unable to detect the target. Please help me resolve this.
Connect a display to the Jetson board to verify the board is properly booting in recovery mode. If you boot the board in what you think is recovery mode, and the display still shows video, then something is wrong there.. it could even be a bad jumper.
Try running lsusb on your computer to see if the board is being recognized by the computer.
I would suggest dual booting your Windows machine with Ubuntu so you can use Ubuntu natively, that is always better than WSL 2 or virtual machines.
Please keep us posted.
best regards,
Andrew
Embedded Software Engineer at ProventusNova
*** Please note that this reply is generated by LLM automatically ***
To resolve the issue of the SDK manager not detecting the target, let’s go through the steps you’ve taken and provide additional troubleshooting steps.
Initial Setup: You’ve followed the official documents for booting through NVMe SSD on the Jetson directly. This is correct, as the Jetson Orin Nano supports booting from an NVMe SSD.
NVMe SSD Installation: You’ve attached a 2 TB NVMe SSD securely into the Jetson, which is a compatible storage device.
Ubuntu Installation: You’ve installed Ubuntu 22.04 on WSL 2, which is a supported environment for the SDK manager.
SDK Manager Launch: You’ve launched the SDK manager via WSL 2’s Ubuntu 22 environment, which is the correct way to launch the SDK manager.
Recovery Mode: You’ve shorted the pins 9 and 10 to put the Jetson into recovery mode, which is necessary for the SDK manager to detect the target.
USB Connection: You’ve connected the USB-C cable to your laptop and the Jetson, with the C-type connector at the Jetson end. This is the correct connection.
Power On: You’ve plugged in the power and switched on the Jetson, and you see the Jetson turn on and the fan start.
Given that you’ve followed the correct steps, here are some additional troubleshooting steps to resolve the issue:
Check the USB Connection: Although you’ve checked the connection, try swapping the USB-C cable with a different one to rule out any issues with the cable.
Verify the Recovery Mode: Ensure that the Jetson is in recovery mode by checking the lsusb output on your laptop. You should see a message indicating that the Jetson is in recovery mode.
Check the SDK Manager Version: Ensure that you’re using the latest version of the SDK manager. You can check the version by running sdkmanager --version in the terminal.
Try a Different USB Port: Try connecting the Jetson to a different USB port on your laptop to rule out any issues with the USB port.
Reset the Jetson: If none of the above steps work, try resetting the Jetson to its default settings. This will erase all data on the Jetson, so be sure to back up any important data before doing so.
If none of these steps resolve the issue, it’s possible that there’s a hardware issue with the Jetson or the NVMe SSD. You may want to try using a different NVMe SSD or contacting NVIDIA support for further assistance.
In comparison to other Jetson modules, the Jetson Orin Nano has similar requirements for booting and setup. However, the specific steps may vary depending on the module and the environment. For example, the Jetson AGX Orin requires a different setup process, and the Jetson Xavier NX has different requirements for booting from an NVMe SSD.
Here’s a comparison of the setup processes for different Jetson modules:
Jetson Orin Nano: Requires a 2 TB NVMe SSD, Ubuntu 22.04 on WSL 2, and the SDK manager launched via WSL 2’s Ubuntu 22 environment.
Jetson AGX Orin: Requires a different setup process, including the use of a microSD card and a different version of the SDK manager.
Jetson Xavier NX: Requires a different setup process, including the use of a microSD card and a different version of the SDK manager.
In summary, the issue you’re experiencing is likely due to a specific configuration or setup issue, rather than a hardware problem. By following the troubleshooting steps outlined above, you should be able to resolve the issue and get the SDK manager to detect the target.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Thanks for the quick reply, Andrew. I tried your suggestions:
I connected a display and when I switched on the board in recovery mode, I could just a Nvidia started screen for few seconds displaying the firmware version and other basic info. And the screen went to shell kind of terminal within a few seconds.
lsusb is not showing up anything on the Ubuntu terminal (WSL).
I do not have enough space to dual boot. I’m thinking I’ll try with Docker image, do you know if that’ll help?
If after booting in recovery mode you are still able to interact with the board, that means is not in recovery mode. The display should show a black screen.
What happens if you don’t boot it in recovery mode?
best regards,
Andrew
Embedded Software Engineer at ProventusNova
Oh okay, even without the shorted pins, I see the same screen.
You’re right, it does not seem to be going to recovery mode. Let me try to short it with another cable. Unfortunately I dont have a jumper cap at the moment so will have to try a workaround.
Hey Andrew,
I’m still trying to get the board to go into Recovery mode. I still see the Nividia starter screen which stays for few seconds before the UEFI Interactive Shell pops up (on which no command works).
Can I be sure that its just the 2 pins not being short properly (I have ordered a jumper wait, will try shorting with that)? Or can I try something else in the meanwhile? Will running Ubuntu through Docker help? (I’m assuming not, since that is not ‘native’ Ubuntu)
Yeah, I’ll stick to WSL until the Recovery mode issue is solved.
Yes, the board does turn ON, but I dont see a ‘setup’ screen per se on the monitor that I’ve connected. And the lsusb on my ubuntu (WSL) still does not show anything.
Yeah sure, this is what I see on-screen. But pressing the Esc/ Enter button does not do anything. Once the white progress bar below completes, it goes into UEFI shell.
And this happens with and without the recovery mode.
Please set up a native Ubuntu system (version 20.04 or later) to flash your device.
Using Windows or a virtual environment (such as WSL, VirtualBox, or VMware) may cause detection issues.
