Jetson AGX Orin 64GB - USB timeout on flash, GUI broken after flash.sh, SDK Manager "No SDKs" on Windows

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

Jetson AGX Orin 64GB - Cannot complete clean flash, multiple methods tried

Hi,

I’ve been trying to flash JetPack 6.2.2 on my Jetson AGX Orin 64GB Developer Kit for several days. The device was originally on JetPack 5.1.3. I’ve tried every method I can think of and none have worked. Hardware is confirmed working — CLI boots fine, internet works, nvidia kernel modules load.

Here’s everything I’ve tried:

  1. Windows WSL2 + SDK Manager
  • USBIPD USB binding errors
  • “non-optimal USB connection” error
  • Flash was “Skipped”
  • APX driver installed via Zadig successfully, but flash still failed
  1. Ubuntu 22.04 Live Boot (USB) + SDK Manager
  • RAM-based storage (~7GB /cow) too small
  • NTFS symlink/permission issues caused tar errors
  • Image build succeeded but flash failed with USB timeout
  1. Ubuntu Live Boot + flash.sh (command line)
  • “ERROR: might be timeout in USB write” repeatedly
  • Tried disabling USB autosuspend (echo -1 > /sys/module/usbcore/parameters/autosuspend) — same error
  1. Ubuntu 22.04 Native Install (ext4, on external SSD) + SDK Manager
  • Jetson detected in recovery mode (APX confirmed via lsusb)
  • “The connected Jetson device is not ready for flash” / “non-optimal USB connection”
  1. Windows SDK Manager after update to 2.4.0.13236
  • “No SDKs are available for your account” — persists after reinstall, logout/login, reboot
  • Same account works fine on Ubuntu SDK Manager 2.4.0.13236
  1. Current Jetson state (after partial flash.sh)
  • R36 REVISION 5.0 (JP6.2.2) is on eMMC
  • CLI works via tty, internet works, nvidia kernel modules loaded
  • GUI does not work:
    • Xorg: “eglInitialize() failed”, “No modes”, “no screens found”
    • Weston: “NvRmMemInitNvmap failed with Permission denied”, “NvRmMemMgrInit failed error type: 196626”
    • /dev/nvhost* devices do not exist
    • /dev/dri/card1-DP-1 status: Connected
    • nvidia-l4t packages (36.5.0) all installed

Host PC: AMD desktop (B650 AORUS ELITE V2, RTX 4060 Ti)
USB cable: USB-A to USB-C (connected to USB-C port next to 40-pin header on Jetson)

Questions:

  1. Is the USB timeout issue related to the AMD USB controller? Would an Intel-based host resolve this?
  2. Is there a way to fix the current partial flash state from tty (restore /dev/nvhost* devices, fix GUI) without a full reflash?
  3. Any known fix for SDK Manager 2.4.0.13236 on Windows showing “No SDKs available”?

Any help would be greatly appreciated. Thank you.

3

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

Based on the provided context, it appears that the user is experiencing issues with flashing their Jetson AGX Orin 64GB Developer Kit with JetPack 6.2.2. The user has tried multiple methods, including using Windows WSL2, Ubuntu 22.04 Live Boot, and Ubuntu 22.04 Native Install, but none have been successful.

The user has encountered various errors, including:

  1. USB binding errors and non-optimal USB connection errors when using Windows WSL2.
  2. RAM-based storage issues and NTFS symlink permission issues when using Ubuntu 22.04 Live Boot.
  3. USB timeout errors when using Ubuntu 22.04 Live Boot and Ubuntu 22.04 Native Install.
  4. Issues with the SDK Manager, including “No SDKs are available for your account” errors on Windows.

The user is seeking help to resolve these issues and is asking several questions:

  1. Is the USB timeout issue related to the AMD USB controller?
  2. Would an Intel-based host resolve this issue?
  3. Is there a way to fix the current partial flash state from tty, restore devnvhost devices, and fix the GUI without a full reflash?
  4. Is there a known fix for the SDK Manager 2.4.0.13236 issue on Windows showing “No SDKs available”?

To address these questions, here are some potential solutions and comparisons:

  1. USB timeout issue: The USB timeout issue may be related to the AMD USB controller, as some users have reported similar issues with AMD-based systems. However, it’s also possible that the issue is related to the USB cable or the Jetson device itself. To troubleshoot this issue, the user can try using a different USB cable or a different USB port on the host PC. If the issue persists, an Intel-based host may be worth trying, as some users have reported better compatibility with Intel-based systems.
  2. Intel-based host: While an Intel-based host may resolve the USB timeout issue, it’s not a guarantee. The user should also consider other factors, such as the USB cable and the Jetson device itself, when troubleshooting the issue.
  3. Fixing the partial flash state: To fix the partial flash state, the user can try using the flash.sh command with the --recovery option. This will attempt to recover the device from the partial flash state. Additionally, the user can try restoring the devnvhost devices by running the sudo systemctl start nvhost command. If the GUI is not working, the user can try reinstalling the NVIDIA drivers and restarting the device.
  4. SDK Manager issue: The “No SDKs available for your account” error on Windows may be related to a bug in the SDK Manager. The user can try reinstalling the SDK Manager and restarting the device. If the issue persists, the user can try using the SDK Manager on a different platform, such as Ubuntu.

In summary, the user’s issues with flashing their Jetson AGX Orin 64GB Developer Kit may be related to the AMD USB controller, but it’s also possible that the issue is related to the USB cable or the Jetson device itself. The user can try troubleshooting the issue by using a different USB cable or a different USB port on the host PC. If the issue persists, an Intel-based host may be worth trying. To fix the partial flash state, the user can try using the flash.sh command with the --recovery option and restoring the devnvhost devices. The SDK Manager issue may be related to a bug, and the user can try reinstalling the SDK Manager and restarting the device.

Comparison of methods:

  • Windows WSL2: This method may be prone to USB binding errors and non-optimal USB connection errors.
  • Ubuntu 22.04 Live Boot: This method may be prone to RAM-based storage issues and NTFS symlink permission issues.
  • Ubuntu 22.04 Native Install: This method may be more stable than the Live Boot method, but the user may still encounter USB timeout errors.
  • Intel-based host: This method may be more compatible with the Jetson device, but it’s not a guarantee.

Recommendation:

  • Try using a different USB cable or a different USB port on the host PC to troubleshoot the USB timeout issue.
  • If the issue persists, try using an Intel-based host.
  • To fix the partial flash state, try using the flash.sh command with the --recovery option and restoring the devnvhost devices.
  • If the SDK Manager issue persists, try reinstalling the SDK Manager and restarting the device.

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

5

[ 0.2574 ] Sending bct_br
[ 0.2576 ] ERROR: might be timeout in USB write.
Error: Return value 3

7

Resolved. The root cause was the AMD B650 USB controller — tegrarcm_v2 fails with USB write timeout consistently on this chipset, regardless of host OS.

The solution was switching to an Intel-based laptop (Samsung NT930SBE, Intel i5-8265U). On Intel USB, tegrarcm_v2 completed with zero errors.

Since the laptop only had 8GB RAM and couldn’t boot directly from the external SSD, I used a chroot-based approach:

  1. Boot Ubuntu 22.04 Live from USB stick in CLI mode (systemd.unit=multi-user.target)
  2. Mount the external SSD (which had SDK Manager files from previous attempts)
  3. chroot into the SSD’s Ubuntu installation
  4. Run flash.sh from inside the chroot

This avoided both RAM exhaustion (no GUI) and SQUASHFS corruption (all binaries loaded from SSD, not USB stick).

Result: JetPack 6.2.2 flashed successfully, GUI working, /dev/nvhost* all present.

Detailed writeup here: