I have two jetson orin nano supers that will not recognize anything plugged into the USB ports. No keyboard or mouse combo has worked to try to control the system. I have tried to reflash them with SDK manager on a linux host, but they will not enter forced recovery mode (both via software or manually shorting the pins on the carrier board). Any ideas how to resurrect them, or is this a hardware fault?
*** Please note that this reply is generated by LLM automatically ***
Based on the provided information, it seems like you are experiencing issues with your Jetson Orin Nano Developer Kit with Super Configuration, specifically with the USB ports not recognizing any devices. You have tried reflashing the devices using SDK Manager on a Linux host, but they will not enter Forced Recovery Mode.
Here are some potential solutions and troubleshooting steps to help you resurrect your Jetson Orin Nano Developer Kits:
- Verify the USB ports: Ensure that the USB ports on the carrier board are not damaged and are functioning correctly. Try using a different USB port or a USB hub to rule out any issues with the port itself.
- Check the power sequencing: According to the Jetson Orin NX Series and Jetson Orin Nano Series Product Design Guide, the Orin module is powered up before the carrier board. Verify that the power sequencing is correct and that the carrier board is receiving power.
- Verify the ODMDATA configuration: The ODMDATA configuration is used to set the hsio-uphy-config-41, which is required for PCIe endpoint mode. Ensure that the ODMDATA configuration is correct and that the hsio-uphy-config-41 is set correctly.
- Try a different flashing method: Instead of using SDK Manager, try flashing the device using the
l4t_initrd_flash.shscript. This script can be used to flash the device in Forced Recovery Mode. - Verify the Forced Recovery Mode: Ensure that the device is in Forced Recovery Mode by checking the
lsusboutput. The device should be listed asBus <bbb> Device <ddd>: ID 0955: <nnnn> Nvidia Corp.If the device is not listed, try shorting the pins on the carrier board to force the device into Recovery Mode. - Check for hardware faults: If none of the above steps work, it is possible that there is a hardware fault with the device. Check the device for any physical damage or signs of wear.
Comparison with other Jetson modules:
- The Jetson Orin Nano Developer Kit with Super Configuration has a similar design to the Jetson Orin NX Developer Kit, but with some differences in the configuration and hardware.
- The Jetson AGX Orin Developer Kit has a different design and configuration compared to the Jetson Orin Nano Developer Kit.
- The Jetson Orin Nano Developer Kit without Super Configuration has a different configuration and hardware compared to the Jetson Orin Nano Developer Kit with Super Configuration.
In conclusion, it is recommended to try the above troubleshooting steps to resurrect your Jetson Orin Nano Developer Kits. If none of the steps work, it is possible that there is a hardware fault with the device, and you may need to contact NVIDIA support for further assistance.
Here is a sample command to flash the device using the l4t_initrd_flash.sh script:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
--showlogs --network usb0 jetson-orin-nano-devkit-super internal
Note: Replace the nvme0n1p1 with the actual device name of your USB drive or NVMe device.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
Hi @david.haggerty,
Could you help us isolate whether this is a USB peripheral/cable issue or the board not entering Force Recovery Mode?
-
JetPack/L4T version
Please share the JetPack/L4T version or the SD card image version used on these Jetson Orin Nano Super Developer Kits. -
USB keyboard/mouse check
Please try one simple wired USB keyboard and one wired USB mouse directly on the USB Type-A ports, without a hub or wireless combo receiver. If available, please also try another known-good keyboard/mouse set and let us know whether the behavior changes on either board. -
Force Recovery Mode check
Please use a known-good USB data cable from the Jetson USB-C data port to a native Ubuntu 20.04/22.04 host PC. With the Jetson powered off, short J14 pins 9 and 10, then plug in DC power while the pins are shorted.On the host PC, please check:
lsusb sudo dmesg -wIn Force Recovery Mode,
lsusbshould show an NVIDIA device such as0955:7523for Jetson Orin Nano 8GB. Also, the Jetson should not continue a normal boot or show the usual boot display while it is actually in Force Recovery Mode.
The official Jetson Orin Nano Developer Kit guide documents entering Force Recovery Mode by shorting J14 pins 9 and 10, and the hardware guide notes that the USB-C port supports USB Recovery mode while the Type-A ports are host-only:
- Jetson Orin Nano Developer Kit User Guide - How-to | NVIDIA Developer
- Jetson Orin Nano Developer Kit User Guide - Hardware Specs | NVIDIA Developer
If the issue still happens with a wired keyboard/mouse and the host PC never sees any NVIDIA USB device with a known-good data cable and the documented recovery pins, please share a photo of the J14 jumper/cable/power setup and the lsusb/dmesg result so we can check the recovery setup first.
Hope this helps!
Are you sure your host + usb cable able to flash any kind of Jetson before?
The cable looks like it only supports charging. It has a lightening bolt, not a USB icon.
Yes - I have 10 other Jetson’s running all flashed with this host + cable combo. It is a thunderbolt cable - so it clearly does data.
If you are sure this host + cable could flash your board with recovery mode + sdkmanager, then those modules which could not be detected through RCM might have hardware problem.
Sometimes we saw newbie users tried the wrong cable or VM host which are not stable for flashing.
I would still suggest you try other host PC+ USB cable first to confirm that.
Please go ahead with RMA