We aim to flash a custom-made image on our devices—a process that has successfully worked for the past 8 devices. However, we are now encountering an error during the flashing process.
Error Details
[ 0.3219 ] Sending bct_mem
[ 0.3516 ] Sending blob
[ 0.4906 ] ERROR: might be timeout in USB write. Error: Return value 3
We are using the 14t_backup_restore.sh function with the following parameters: -r tools/kernel_flash/flash_14t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" p3509-a02+p3767-0000
Troubleshooting Steps Taken
Deactivated USB autosuspend via GRUB.
Tested various cables.
Tried different Ubuntu versions (20.04 and 18.04).
Not only the backup restore but also a “normal” flashing approach is not working
Despite these efforts, the issue remains inconsistent, with additional errors such as an inability to read the RMC state of the device.
Questions
What can cause this “sending blob” issue?
Is this always related to the USB port, or is this error indicative of a general connection issue with the device?
Can this be caused by different Versions: Image we want to flash R35 , REVISION: 3.1 and the Current Base Image on the Device R35 , REVISION: 4.1 ?
Your question 1 does not really matter and the reason will be answered in (2).
It is not related to usb port. It is just a general error. Everything could lead to that so there is no need to investigate why sending blob has issue.
It is most likely due to PCN update. You can try latest jetpack version first and that will confirm my assumption.
If you don’t know what is PCN update, it means some components may got updated (most cases are the DRAM) in new module and old Jetpack won’t support them directly.
I now tried to flash an Image Jetpack 6.1 with the SDK Manager on my device. It gives me an error:
The connected Jetson device is not ready to flash. non optimal Usb connection.
I tried again with different cable and different Host Usb port and restarting both devices.
Also tried to flash via terminal which now gives out: