[JetPack 6.2.1/Jetson Orin Nano 4GB] Flash failure - USB write timeout & Parsing board info failed

Hello, I’m trying to install Linux on my Jetson Orin Nano 4GB development board using Manager CDK and Jetpack 6.2.1, but I’m having trouble flashing it. So, I tried a manual installation using the Ubuntu terminal. I flashed the OS on my Jetson Orin Nano 4GB development board using the following command: sudo ./flash.sh jetson-orin-nano-devkit nvme0n1p1

However, flashing always fails with the following error message:

ERROR: might be timeout in USB write..

Parsing board information failed.

Here are the steps I tried:

  1. Use a 1m USB-C to USB-C data cable that complies with the USB 3.1 Gen 2 standard.
  2. Disable the USB auto-suspend feature.
    echo -1 > /sys/module/usbcore/parameters/autosuspend
  3. I swapped out several USB ports and verified that the Jetson entered recovery mode (lsusb output: 0955:7033).
  4. I’m running Ubuntu 22.04 LTS on my host PC.

However, the flash failed.

I’ve attached the following two log files:

  1. jetson_flash_log.txt – Flash attempt log
  2. jetson_board_info_log.txt – Board information read log

I’m wondering if this issue occurs with JetPack 6.2.1 and the Orin Nano 4GB. I’ve tried everything I can, including replacing the cable, but the flash continues to fail. Thank you for your advice. Thanks for reading this long post.

jetson__flash_log.txt (21.2 KB)
jetson_board_info_log.txt (12.8 KB)

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

I understand that you’re experiencing issues with flashing your Jetson Orin Nano 4GB development board using the SDK Manager and Jetpack 6.2.1. You’ve tried a manual installation using the Ubuntu terminal, but it always fails with the error message “ERROR: might be timeout in USB write Parsing board information failed”.

To help you troubleshoot this issue, I’ll provide some insights and suggestions.

USB Connection and Cable

You’ve mentioned using a 1m USB-C to USB-C data cable that complies with the USB 3.1 Gen 2 standard, which is a good start. However, I’d like to suggest a few more things to check:

  1. USB port: Try using a different USB port on your host PC to rule out any issues with the specific port.
  2. USB hub: If you’re using a USB hub, try connecting the Jetson Orin Nano directly to the host PC to eliminate any potential issues with the hub.
  3. Cable quality: Although you’ve mentioned using a compliant cable, it’s possible that the cable might be faulty. Try using a different cable to see if the issue persists.

USB Autosuspend Feature

You’ve disabled the USB autosuspend feature by running the command echo 1 > /sys/module/usbcore/parameters/autosuspend. This is a good step, as autosuspend can sometimes cause issues with USB connections.

Recovery Mode

You’ve verified that the Jetson Orin Nano enters recovery mode by checking the lsusb output, which shows the device as 0955:7033. This suggests that the device is properly connected and recognized by the host PC.

Log Files

You’ve attached two log files: jetsonflashlog.txt and jetsonboardinfolog.txt. Unfortunately, I’m a large language model, I don’t have the capability to access or analyze these files directly. However, I can suggest some general troubleshooting steps based on the error message you provided.

Error Message

The error message “ERROR: might be timeout in USB write Parsing board information failed” suggests that there might be an issue with the USB connection or the board information parsing process.

To troubleshoot this further, you can try the following:

  1. Check the USB connection: Verify that the USB connection is stable and not causing any issues.
  2. Check the board information: Ensure that the board information is correct and properly configured.
  3. Try a different flashing method: Instead of using the flash.sh command, try using the l4t_initrd_flash.sh script to flash the device.

Comparison with Other Issues

Based on the context you provided, I noticed that there are other issues related to flashing and booting on the Jetson Orin Nano. For example, there’s a topic on “Copy And Flash Jetson Orin with Jetpack 6.2” that discusses similar issues.

While I couldn’t find an exact match for your issue, I suggest checking the NVIDIA forums and documentation for any known issues or workarounds related to flashing and booting on the Jetson Orin Nano with Jetpack 6.2.1.

Conclusion

In conclusion, I’ve provided some suggestions to help you troubleshoot the issue with flashing your Jetson Orin Nano 4GB development board using the SDK Manager and Jetpack 6.2.1. If you’ve tried all the steps I mentioned and the issue persists, I recommend reaching out to NVIDIA support for further assistance.

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

Hi,

Please make sure you do after you download bsp and rootfs.

$ tar xf ${L4T_RELEASE_PACKAGE}
$ sudo tar xpf ${SAMPLE_FS_PACKAGE} -C Linux_for_Tegra/rootfs/
$ cd Linux_for_Tegra/
$ sudo ./tools/l4t_flash_prerequisites.sh
$ sudo ./apply_binaries.sh

Also please refer to Quick Start — NVIDIA Jetson Linux Developer Guide.

To flash Orin Nano dev kit with NVMe :

$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
  -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
  --showlogs --network usb0 jetson-orin-nano-devkit internal

Thanks

Hi David, thank you so much for your reply. I read it carefully. I did what you said, but I’m still getting the same error. I don’t think it’s a cable issue. I bought a ton of cables. I’m desperate to flash


Thank you so much for your kind and detailed reply. I followed every step carefully, exactly as you described — downloading the correct BSP and rootfs, extracting them, running l4t_flash_prerequisites.sh and apply_binaries.sh, and finally executing the l4t_initrd_flash.sh command with the correct parameters.

However, I’m still getting the same USB timeout error when it tries to communicate with the board. I’ve tested with multiple cables, including data-capable ones, and I don’t think the issue is related to the cable itself. I’ve spent a lot of time and tried many combinations, but I still haven’t been able to flash successfully.

I’m really desperate to get this working and would greatly appreciate any further advice or troubleshooting steps. Is there anything else I might be missing?

Thanks again for your help.



I’m desperate to flash… Currently, Ubuntu 20.04 is installed on Jetson Nano, but I’m trying to reinstall 22.04 on it.

Hi,

Please record the serial console log for us to review.

Also press EXPORT LOGS button in sdk manager to upload the flashing logs.

Thanks

SDKM_logs_2025-07-31_21-53-36.zip (523.1 KB)
Hi David! Thank you so much for your reply. Here’s the log from the Manager SDK

Hi,

Sorry, but the zip file you provided isn’t what I was looking for.
Please refer to the video and record the serial log accordingly.

Thanks

Is this still an issue to support? Any result can be shared?

Thank you for your attention! I have already completed it.

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