Jetson AGX Orin can't flash. The device ID in WSL are changing

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

I was attempting to flash my Jetson AGX Orin, following a tutorial provided by GPT, but I’ve gotten stuck at this specific step. I am running Ubuntu 22.04 within WSL2, and I connected the Jetson AGX Orin to my Windows host PC via USB, ensuring the device was successfully attached. However, the process failed during the actual flashing phase. I noticed that while the flash was in progress, the list of devices within Ubuntu would refresh, and the Device ID for the Jetson AGX Orin would change. Could this failure be caused by the data cable? I would like to know what specific requirements the Jetson AGX Orin has regarding data cables; I have misplaced my original cable and am currently using a third-party, non-official replacement.

image
image1006×624 105 KB

2

*** Please note that this reply is generated by LLM automatically ***

The issue you’re experiencing with the Jetson AGX Orin flashing process failing during the actual flashing phase, accompanied by the device ID changing, could be related to the data cable you’re using.

The original cable provided with the Jetson AGX Orin is a USB-C cable that supports USB 3.2 Gen 2 speeds, which is necessary for the flashing process. This cable is designed to handle the high-speed data transfer required for flashing the device.

Using a third-party, non-official replacement cable may cause issues with the flashing process, especially if the cable doesn’t support the required USB speed. Here are some specific requirements for the data cable:

  1. USB-C connector: The Jetson AGX Orin uses a USB-C connector, which is reversible and can be inserted either way.
  2. USB 3.2 Gen 2 speed: The cable should support USB 3.2 Gen 2 speeds, which is necessary for the high-speed data transfer required during the flashing process.
  3. High-quality cable: A high-quality cable with good shielding and insulation is essential to prevent data corruption and ensure reliable data transfer.

If you’re using a third-party cable, it’s possible that it may not meet these requirements, which could be causing the flashing process to fail.

To troubleshoot the issue, you can try the following:

  1. Use the original cable: If you can find the original cable that came with the Jetson AGX Orin, try using it to see if the flashing process completes successfully.
  2. Check the cable specifications: Verify that the third-party cable you’re using meets the required USB speed and quality standards.
  3. Try a different USB port: Try using a different USB port on your Windows host PC to see if the issue is specific to the port or the cable.
  4. Check for loose connections: Ensure that the cable is securely connected to both the Jetson AGX Orin and the Windows host PC.

If none of these troubleshooting steps resolve the issue, it’s possible that there may be a problem with the Jetson AGX Orin itself or the flashing process. You may want to try seeking further assistance from the manufacturer’s support team or a professional developer community.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4 
# This might be a better place to start.
https://developer.nvidia.com/embedded/learn/get-started-jetson-agx-orin-devkit

# And instructions to use WSL for sdkmanager
https://docs.nvidia.com/sdk-manager/wsl-systems/index.html
5

Don’t use WSL(2) or any other virtualisation. Use a native Ubuntu 22.04 on a bare metal amd64/x86-64 PC without any hypervisor below it. This is the most reliably way. If you don’t like dual-booting then a small box pc with Intel Atom or N100 and 8G RAM or something used is enough.

6

Thanks. I resolved this issue by using a machine running native Ubuntu; a third-party data cable worked just fine as well. In fact, device disconnections still occurred even on the native Ubuntu system, but the SDK Manager did not report any errors—so it is indeed quite possible that the issue was caused by virtualization.