Jetson Thor Dev Kit - unable to boot, no display

Robotics & Edge Computing Jetson & Embedded Systems Jetson Thor
,
1

Jetson Thor dev kit is unable to boot and the the external monitor shows no signal. Unable to access UEFI by pressing esc key.

Initially, OS was installed by using USB thumb drive. It was booting to Ubuntu desktop at that point .

$ sudo apt upgrade
$ sudo apt install nvidia-jetpack
Restarted > no display, no visible option to boot, no Nvidia logo or UEFI access

The Jetson device is detected (while connected to the right/data/j81 USB port, the one closer to the HDMI port).
$ lsusb :
Bus 003 Device 011: ID 0955:7026 NVIDIA Corp. APX

With the USB cable connected to debug port on top:
$ sudo minicom -D /dev/ttyACM0 -8 -b 115200

Restarted Jetson Thor, last two lines displayed were:

"[0000.117] I> BR last_boot_error2: 0x0 
[0000.1"

Seems to hang after step 0000.117.
Attempted to flash using SDK manager 4 times. Failed every time, the host was left without interruption to complete the process. Partial error log of last attempt:

12:35:44.797 - Info:   File "/home/guest/nvidia/nvidia_sdk/JetPack_7.0_Linux_JETSON_AGX_THOR_TARGETS/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn/../bootburn_t264_py/bootburn_lib.py", line 3262, in FlashImages
12:35:44.797 - Info:     AbnormalTermination("Flashing failed and target was not bricked as per configuration", flashExceptRetCode)
12:35:44.797 - Info:   File "/home/guest/nvidia/nvidia_sdk/JetPack_7.0_Linux_JETSON_AGX_THOR_TARGETS/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn/../bootburn_t264_py/flashtools_nverror.py", line 260, in AbnormalTermination
12:35:44.797 - Info:     raise OSError(errorCode)
12:35:44.797 - Info: OSError: 121
12:35:44.797 - Info: command line used was:
12:35:44.797 - Info: ['/home/guest/nvidia/nvidia_sdk/
JetPack_7.0_Linux_JETSON_AGX_THOR_TARGETS/Linux_for_Tegra/unified_flash/out/bsp_images/tools/flashtools/bootburn/flash_bsp_images.py', '-b', 'jetson-t264', '--l4t', '-D', '-P', '/home/guest/nvidia/nvidia_sdk/JetPack_7.0_Linux_JETSON_AGX_THOR_TARGETS/Linux_for_Tegra/unified_flash/out/bsp_images/flash_workspace', '--usb-instance', '3-6']
12:35:44.798 - Info: 
12:35:44.798 - Info: 
12:35:44.798 - Info: [01;31mFlashing failed and target was not bricked as per configuration[0m

Any ideas on how I can resolve this?

3

Hi evokristov,

What’s the Jetpack version at that point?

Are you trying to flash into USB driver or NVMe SSD currently?

Could you share the full flash log as file here for further check?

4

Hi KevinFFF,

It was likely jetpack 7.0. The original OS was installed using jetsoninstaller-0.2.0-r38.2-2025-08-22-01-33-29-arm64.iso

I am attempting to flash the NVMe on the dev kit. On the host laptop the OS is installed on an USB drive. I saw ‘/dev/sdb3’ in the logs - this is the host laptop and not the dev kit.

Attached is the log file NV_L4T_JETSON_LINUX_OPENRM_FLASH_COMP.log. Other available logs are:
NV_L4T_DRIVERS_OPENRM_IMAGE_COMP.log
NV_L4T_FILE_SYSTEM_AND_OS_OPENRM_IMAGE_COMP.log
sdkm-2025-10-19-10-42-26.log

Thank you

NV_L4T_JETSON_LINUX_OPENRM_FLASH_COMP.log (8.6 MB)

5

Also, attached is the boot log from the debug port.

serial_debug_output_during_boot_attempt.txt (60.0 KB)

6

In the serial console log, it is not complete and the log seems corrupted in MB2.

12:35:44.777 - Info: [flash_bsp_jetson-t264_die0]: [executeShellCommand(175)] : Return code: 1
12:35:44.778 - Info: [flash_bsp_jetson-t264_die0]: [executeShellCommand(177)] : stdout: b"error: device '2U1TS9418000002FS040' not found\n"

From the flash log you shared, it seems the USB connection is unstable and you board cannot be recognized in the middle of flash process.

Could you try using another USB cable and flash again?

7

On host usb autosuspend might be involved.

Check the current setting: Open a terminal and run the following command to see the current autosuspend value. A value of 2 (enabled) is the default.
cat /sys/module/usbcore/parameters/autosuspend

Disable autosuspend: This sets the value to -1, which prevents autosuspend. Setting is temporary until reboot.
echo -1 | sudo tee /sys/module/usbcore/parameters/autosuspend

8

Thank you both for the suggestions. It turned out to be a bad USB cable. Flash completed and I am able to boot again.

10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.