USB Write Timeout Error During Jetson AGX Orin OS Flashing

Device Information

Model: JETSON AGX ORIN 32GB H01 KIT WIT
Product Page: https://www.digikey.jp/ja/products/detail/seeed-technology-co-ltd/114110207/18092924?s=N4IgTCBcDaIIxwCwIAxhQdhAXQL5A


Inquery

Reference Page: NVIDIA® Jetson AGX Orin 32GB H01 Kit | Seeed Studio Wiki

I followed the instructions on the above page to install the OS on my Jetson AGX Orin using JetPack, but I encountered an error when executing the following command:

sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1

The error message is as follows:

[   3.2033 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1030896  
[   3.2036 ] Added binary blob_eks_sigheader.img.encrypt of size 9232  
[   3.2095 ] Sending membct and RCM blob  
[   3.2099 ] tegrarcm_v2 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin  
[   3.2102 ] BL: version 0.23.0.0-t234-54845784-92215740 last_boot_error: 0  
[   3.2517 ] Sending bct_mem  
[   3.3135 ] Sending blob  
[   3.3583 ] ERROR: might be timeout in USB write.  
Error: Return value 3  
Command tegrarcm_v2 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin  
Failed flashing t186ref.

What I Have Tried / Verified

  • Host OS: Tried both Ubuntu 20.04 and 22.04 — same error occurred.
  • USB Cables: Replaced and tested multiple USB cables — no change.
  • Device Recognition: Confirmed the Jetson is correctly detected via lsusb.
  • Execution Environment: Attempted flashing from both WSL and live USB Ubuntu environments — same result.
  • JetPack Versions: Tried JetPack 5.1.1, 6.0, and 6.1 — same error in all cases.

Question

How can I resolve the USB write timeout error above and successfully flash the OS onto my Jetson AGX Orin?
Any guidance or advice would be greatly appreciated.

Hi there,

Is it shutting down for thermal protection? during update? I have seen that in past threads. Try putting a small fan on it while updating?
my .02 :v:

HTH
GL :slight_smile: PJ :+1:

you using NVME ? or straight to EMMC ? or SSD?

Thank you for your reply.
The error appears just a few seconds after executing the command, so I believe it’s occurring before the update process even begins. Therefore, it seems unlikely that it’s caused by thermal protection.

I’m installing directly to the eMMC.