thor连接usb,进行刷机,偶尔出现刷机失败([flash_bsp_jetson-t264_die0]: [executeShellCommand(173)] : Output: ERROR: might be timeout in USB read),换个端口或者换个线或者重启。之后可以刷写成功。如何解决?
If you haven’t already, you could try turning off usb autosuspend to see if it helps.
sudo sh -c ‘echo -1 > /sys/module/usbcore/parameters/autosuspend’
To make change persistent:
sudo tee /etc/modprobe.d/usbcore-no-autosuspend.conf >/dev/null <<‘EOF’
options usbcore autosuspend=-1
EOF
我们试试,看看能不能起作用
Hi @mingkuo2010,
According to the log, the device can communicate through RCM, read the BR_CID, and transfer bct_br, mb1, psc_bl1, and bct_mb1. The failure occurs while downloading the applet and waiting for its response:
--chip 0x26 --pollbl --download applet applet/applet_blob.bin
ERROR: might be timeout in USB read
This identifies the stage where the failure occurs, but it does not yet confirm that USB autosuspend is the root cause.
When testing with autosuspend disabled, please use the following sequence:
-
Run these commands on the host PC and confirm that the output is
-1:sudo sh -c 'echo -1 > /sys/module/usbcore/parameters/autosuspend' cat /sys/module/usbcore/parameters/autosuspend -
Disconnect the flashing USB cable.
-
Put the Thor device back into Force Recovery Mode.
-
For an official Developer Kit, reconnect the flashing cable to the J81 recovery port. For a custom carrier board, use its designated recovery USB port. Then retry the flash.
Please also provide the following environment details so that we can verify the applicable platform and documentation:
- The complete JetPack / Jetson Linux (L4T) version
- Whether this is an official Jetson AGX Thor Developer Kit or a custom carrier board, and whether the module is T5000 or T4000
- The host Ubuntu version and whether the host is a physical machine or a VM
For the location of the J81 recovery port, see:
Jetson AGX Thor Developer Kit Hardware Layout
Please share the result after testing with the sequence above. If the failure persists, please also provide the UART serial-console log from that failed attempt so we can distinguish a host USB communication issue from the target applet not starting correctly.
Thanks.

