Hi everyone,
I’m facing with issue while flashing my Jetson device using the SDK Manager.
System Information:
Problem:
16:39:31.680 - Info: [ 0.0977 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
16:39:31.701 - Info: [ 0.0978 ] Added binary blob_boot0.img of size 55590912
16:39:31.707 - Info: [ 0.1188 ] Added binary blob_tegra234-p3767-0003-p3768-0000-a0.dtb of size 347610
16:39:31.892 - Info: [ 0.1545 ] tegrarcm_v2 --instance 1-3.1 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
16:39:31.892 - Info: [ 0.1551 ] BL: version 1.2.0.0-t234-54845784-562369e5 last_boot_error: 0
16:39:31.901 - Info: [ 0.3103 ] Sending bct_mem
16:39:31.979 - Info: [ 0.3188 ] Sending blob
16:39:37.149 - Info: [ 0.3973 ] ERROR: might be timeout in USB write.
16:39:37.161 - Info: Error: Return value 3
16:39:37.161 - Info: Command tegrarcm_v2 --instance 1-3.1 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
16:39:37.166 - Info: Cleaning up...
16:39:37.201 - Error: [exec_command]: /bin/bash -c /home/alex/.nvsdkm/replays/scripts/JetPack_5.1.2_Linux/NV_L4T_FLASH_JETSON_LINUX_COMP.sh; [error]: 84422 blocks
16:39:37.201 - Info: [ Component Install Finished with Error ]16:39:37.201 - Info: [host] [ 12.93 MB released. Disk Avail on Partition /dev/nvme0n1p2: 48.71 GB ]16:39:37.201 - Info: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 3m10s ]
Additional Information:
This error occurs only with JetPack 5.1.2 .
When I use JetPack 5.1.4 or JetPack 6.2 , everything goes without any issues.
I tried two different host machines with ubuntu 20.04, several different USB ports. Every time, I got the same error.
Could someone please help me to fix it?SDKM_logs_JetPack_5.1.2_Linux_for_Jetson_Orin_Nano_[8GB_developer_kit_version]_2025-02-25_16-35-49.zip (149.8 KB)
Thank you!
Hi @aalex6219
Could you test again after desabling the autosuspend?
sudo bash -c "echo -1 > /sys/module/usbcore/parameters/autosuspend"
Regards,
Ricardo González Víquezsupport@ridgerun.com https://developer.ridgerun.com www.ridgerun.com
Hi, I have tried it right now. Unfortunately, the result is the same.
alex@alex-ps-2:~$ cat /sys/module/usbcore/parameters/autosuspend
-1
20:04:43.394 - Info: [ 0.0843 ] Added binary blob_display-t234-dce_sigheader.bin.encrypt of size 9097216
20:04:43.395 - Info: [ 0.0872 ] Added binary blob_nvdec_t234_prod_sigheader.fw.encrypt of size 294912
20:04:43.395 - Info: [ 0.0882 ] Added binary blob_bpmp_t234-TE950M-A1_prod_sigheader.bin.encrypt of size 1051136
20:04:43.395 - Info: [ 0.0884 ] Added binary blob_tegra234-bpmp-3767-0003-3509-a02_with_odm_sigheader.dtb.encrypt of size 110080
20:04:43.396 - Info: [ 0.0885 ] Added binary blob_camera-rtcpu-sce_sigheader.img.encrypt of size 166304
20:04:43.396 - Info: [ 0.0886 ] Added binary blob_camera-rtcpu-t234-rce_sigheader.img.encrypt of size 537952
20:04:43.396 - Info: [ 0.0887 ] Added binary blob_adsp-fw_sigheader.bin.encrypt of size 400864
20:04:43.396 - Info: [ 0.0888 ] Added binary blob_spe_t234_sigheader.bin.encrypt of size 270336
20:04:43.396 - Info: [ 0.0889 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1127568
20:04:43.396 - Info: [ 0.0892 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
20:04:43.416 - Info: [ 0.0893 ] Added binary blob_boot0.img of size 55590912
20:04:43.422 - Info: [ 0.1086 ] Added binary blob_tegra234-p3767-0003-p3768-0000-a0.dtb of size 347610
20:04:43.612 - Info: [ 0.1420 ] tegrarcm_v2 --instance 1-3.1 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
20:04:43.612 - Info: [ 0.1426 ] BL: version 1.2.0.0-t234-54845784-562369e5 last_boot_error: 0
20:04:43.623 - Info: [ 0.3054 ] Sending bct_mem
20:04:43.701 - Info: [ 0.3163 ] Sending blob
20:04:48.864 - Info: [ 0.3937 ] ERROR: might be timeout in USB write.
20:04:48.879 - Info: Error: Return value 3
20:04:48.879 - Info: Command tegrarcm_v2 --instance 1-3.1 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
Is it possible that this error occurred due to I am trying to install an old jetpack 5.1.2, but my device has an incompatible new QSPI 6.0-37391689 ?
@aalex6219
You could also try disabling the firewall while doing the tests:
sudo ufw disable
sudo ufw status
# Ouput
Status: inactive
I had recently a similar issue and it was because it didn’t have the fan connected to the SOM: Orin NX flash error - #7 by ricardo.gonzalez1 . Is it possible that your SOM doesn’t have the fan connected?
I would also recommend you delete the JP 5.1.2 directory (~/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_ORIN_NANO_TARGETS) and reinstall it with the SDKManager. Sometimes there is something broken inside of it that makes the flash process fail.
Regards,
Ricardo González Víquezsupport@ridgerun.com https://developer.ridgerun.com www.ridgerun.com
Is it possible that your SOM doesn’t have the fan connected?
I can see that the fan is turning when I start the device. I guess that means it’s connected.
Thanks for your suggestions. I have tried:
Disabling the firewall (it was actually disabled at startup)
Deleting the JP 5.1.2 directory
Disabling the autosuspend
Unfortunately, the result is the same:
20:46:14.448 - Info: [ 0.1512 ] BL: version 1.2.0.0-t234-54845784-562369e5 last_boot_error: 0
20:46:14.456 - Info: [ 0.3108 ] Sending bct_mem
20:46:14.537 - Info: [ 0.3193 ] Sending blob
20:46:19.648 - Info: [ 0.4001 ] ERROR: might be timeout in USB write.
20:46:19.660 - Info: Error: Return value 3
Hi,
Please record the serial console log first.
Thanks
aalex6219:
When I use JetPack 5.1.4 or JetPack 6.2 , everything goes without any issues.
According to this comment, it is most likely this issue is related to new PCN update that the DRAM on your Orin Nano might be new that is not supported in old software release. You have to use new Jetpack release then.
Unfortunately, at the moment, I don’t have a TTL cable. I can only record the display. Would it be helpful?
system
March 26, 2025, 2:42am
14
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
