Problem during the flash procedure

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

Hi,

I am using a AGX Orin dev kit and JetPack 6.2.2.

When I am flashing, I am getting the following error:

[ 0.0969 ] Added binary blob_boot0.img of size 90476544
[ 0.1302 ] Added binary blob_tegra234-p3737-0000+p3701-0005-nv.dtb of size 255392
[ 0.1816 ] tegrarcm_v2 --instance 1-3 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[ 0.1821 ] BL: version 1.4.0.7-t234-54845784-56c609fa last_boot_error: 0
[ 0.3134 ] Sending bct_mem
[ 0.3220 ] Sending blob
[ 0.4212 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --instance 1-3 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
Cleaning up…

What would cause such as error?

Malcolm

2

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

The error you’re encountering while flashing your Jetson AGX Orin Developer Kit with JetPack 4.6.2 appears to be related to a timeout in the USB write process. Here are some potential causes and troubleshooting steps:

  1. USB Connection Issues: Ensure that the USB connection between your host machine and the Jetson AGX Orin Developer Kit is stable and secure. Try using a different USB port or cable to rule out any issues with the current connection.

  2. Power Supply: Verify that the Developer Kit is receiving sufficient power. If you’re using a USB hub, try connecting the kit directly to the host machine or using a powered USB hub.

  3. USB Write Speed: The error might be caused by a slow USB write speed. You can try increasing the USB write speed by using a faster USB port (e.g., USB 3.0 instead of USB 2.0) or by using a USB write speed booster.

  4. Timeout Value: The timeout value in the tegrarcmv2 command might be too low, causing the error. You can try increasing the timeout value by adding the --timeout option followed by a higher value (in milliseconds) to the tegrarcmv2 command. For example:

$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash -u <pkc_keyfile> [-v <sbk_keyfile>] --timeout 30000 jetson-agx-orin-devkit internal

   This will set the timeout value to 30 seconds (30000 milliseconds).

5. **Firmware Version**: Ensure that the firmware version on your Jetson AGX Orin Developer Kit is compatible with JetPack 4.6.2. You can check the firmware version by running the following command:

$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --query-firmware-version jetson-agx-orin-devkit

   If the firmware version is outdated, you might need to update it before flashing the kit.

6. **Host Machine Configuration**: The error might be caused by a configuration issue on the host machine. Ensure that the host machine meets the system requirements for flashing the Jetson AGX Orin Developer Kit, and that the necessary dependencies are installed.

7. **Flashing Command**: Verify that the flashing command you're using is correct and complete. Compare your command with the examples provided in the documentation to ensure that you're using the correct options and parameters.

8. **SBKPKC Fusing**: If you're using SBKPKC fusing, ensure that the signing process is complete and that the signed images are correctly generated. You can try re-signing the images and then flashing the kit again.

By troubleshooting these potential causes, you should be able to identify and resolve the issue causing the error. If the problem persists, you may want to seek further assistance from NVIDIA support or the Jetson community forums.

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

Thanks. I would like to have a non LLM response as well

Malcolm

5

There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks ~0603

Hi,

Please provide the full log for us to review.

Thanks