We have designed Jetson Thor T5000 CVB Y903, now we flash with T5000 and 1TB SSD, failed with “${s_ERROR_ADB_TIMEOUT}”. Please help to check the log and reason.
#Flash command T5000
sudo ./l4t_initrd_flash.sh --flash-only jetson-agx-thor-devkit internal
....
[flash_bsp_jetson-t264_die0]: [executeShellCommand(156)] : command = timeout 5 /home/fz/sda/nvidia_sdk/Linux_for_Tegra_JP7.2.1/unified_flash/out/bsp_images/tools/flashtools/flash/adb -s 2U24K03I000000A020E0 wait-for-device
cwd = /home/fz/sda/nvidia_sdk/Linux_for_Tegra_JP7.2.1/unified_flash/out/bsp_images/flash_workspace/flash-images
[flash_bsp_jetson-t264_die0]: [executeShellCommand(171)] : shell command -- timeout 5 /home/fz/sda/nvidia_sdk/Linux_for_Tegra_JP7.2.1/unified_flash/out/bsp_images/tools/flashtools/flash/adb -s 2U24K03I000000A020E0 wait-for-device failed
[flash_bsp_jetson-t264_die0]: [executeShellCommand(173)] : Output:
[flash_bsp_jetson-t264_die0]: [executeShellCommand(175)] : Return code: 124
[flash_bsp_jetson-t264_die0]: [executeShellCommand(177)] : stdout: b''
[flash_bsp_jetson-t264_die0]: [executeShellCommand(179)] : stderr: None
[flash_bsp_jetson-t264_die0]: [AdbFindDevice(214)] : the ADB device is not yet found online : 2U24K03I000000A020E0
[flash_bsp_jetson-t264_die0]: [AdbFindDevice(215)] : current totaltime in finding device online : 95
[flash_bsp_jetson-t264_die0]: [AdbFindDevice(219)] : failed to find the device :2U24K03I000000A020E0 online at the end of :100 seconds
[flash_bsp_jetson-t264_die0]: [CheckUSBServiceInit(292)] : Could not find a device online, after killing and re-starting ADBserver
Traceback (most recent call last):
File "/home/fz/sda/nvidia_sdk/Linux_for_Tegra_JP7.2.1/unified_flash/out/bsp_images/tools/flashtools/bootburn/../bootburn_t264_py/flash_bsp_images.py", line 118, in flash_bsp_active
bootburnThor.FlashImages(binaryLocationPath)
File "/home/fz/sda/nvidia_sdk/Linux_for_Tegra_JP7.2.1/unified_flash/out/bsp_images/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_lib.py", line 3198, in FlashImages
adbObj.CheckUSBServiceInit(timeout, self.sudoRequired)
File "/home/fz/sda/nvidia_sdk/Linux_for_Tegra_JP7.2.1/unified_flash/out/bsp_images/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_adb.py", line 293, in CheckUSBServiceInit
AbnormalTermination("${s_ERROR_ADB_TIMEOUT}", nverror.NvError_Timeout)
File "/home/fz/sda/nvidia_sdk/Linux_for_Tegra_JP7.2.1/unified_flash/out/bsp_images/tools/flashtools/bootburn/../bootburn_t264_py/flashtools_nverror.py", line 263, in AbnormalTermination
raise OSError(errorCode)
OSError: 5
command line used was:
['/home/fz/sda/nvidia_sdk/Linux_for_Tegra_JP7.2.1/unified_flash/out/bsp_images/tools/flashtools/bootburn/flash_bsp_images.py', '-b', 'jetson-t264', '--l4t', '-D', '-P', '/home/fz/sda/nvidia_sdk/Linux_for_Tegra_JP7.2.1/unified_flash/out/bsp_images/flash_workspace', '--l4t_boot_chain_select', 'A', '--usb-instance', '1-5.3']
${s_ERROR_ADB_TIMEOUT}
Exception raised in flash BSP ACTIVE
5
[flash_bsp_jetson-t264]: start time = 1791281475.5878491
[flash_bsp_jetson-t264]: end time = 1791281697.5221796
[flash_bsp_jetson-t264]: Total Time = 221.93433046340942
[flash_bsp_jetson-t264]: Image Flashing took 221.93433046340942
[flash_bsp_jetson-t264]: Flashing finished Unsuccessfully!!
Cleaning up...
Your log looks like you have a usb hub between your board and host pc. You could try direct connect a known good usb-c data cable connected straight into a usb port on your host pc. Then
After several days of troubleshooting and comparison, we found that our custom Thor carrier board can enter Recovery mode but can’t bootup (Thor & SSD flashed with Thor Devkit).
In Recovery mode both MODULE_POWER_ON and CARRIER_POWER_ON are at 3.3V and remain stable.
But booting up MODULE_POWER_ON and CARRIER_POWER_ON goes to 3.3V then Thor CARRIER_POWER_ON output down to 0V.
The behavior is identical when running Flash commands (erase-all and qspi-only)
sending bct_mem completes normally
the next stage downloading blob ./rcm_blob.bin — the operation fails, and both MODULE_POWER_ON and CARRIER_POWER_ON drop to 0V.
