Hi Forum,
We have an Jetson Orin NX 8GB SoM and it seems not possible to flash the NVMe attached to it even though it is still recognized in Recovery Mode. Below is the flashing logs :
SDKM_logs_JetPack_5.1.2_Linux_for_Jetson_Orin_NX_modules_2024-07-06_11-34-39.zip (305.2 KB)
SDKM_logs_JetPack_5.1.2_Linux_for_Jetson_Orin_NX_modules_2024-11-07_08-41-11.zip (865.4 KB)
Could you help to figure out what is the problem, please ?
Thanks in advance,
Khang
Hi khang.l4es,
Are you using the devkit or custom board for Orin NX 8GB?
11:41:36.070 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: Error: Could not stat device /dev/nvme0n1 - No such file or directory.
11:41:36.070 - info: Event: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS - error is: Error: Could not stat device /dev/nvme0n1 - No such file or directory.
11:41:36.083 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: Flash failure
For the 1st log, it seems NVMe SSD is not detected corretly.
08:46:19.222 - error: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: [ 0.4595 ] ERROR: might be timeout in USB write.
08:46:19.222 - info: Event: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS - error is: [ 0.4595 ] ERROR: might be timeout in USB write.
For the 2nd log, it seems there’s USB connection issue, please change another USB cable or port on your host.
Hi @KevinFFF,
Are you using the devkit or custom board for Orin NX 8GB?
I am using the Connecttech’s Boson for Framos Carrier Board.
For the 1st log, it seems NVMe SSD is not detected corretly.
Same carrier board + same NVMe SSD were recognized by another Jetson Orin NX 16GB SoM, however
For the 2nd log, it seems there’s USB connection issue, please change another USB cable or port on your host.
I noticed above error, and also did :
# echo -1 > /sys/module/usbcore/parameters/autosuspend
then flashed using
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --showlogs --network usb0 p3509-a02+p3767-0000 internal
but got error at the end :
…
Cleaning up…
Finish generating flash package.
/workspace/Ref/Platforms/Nvidia-Jetson/Software/SDK_installs/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --network usb0 --usb-instance 1-8 --device-instance 0 --flash-only --external-device nvme0n1p1 -c “tools/kernel_flash/flash_l4t_external.xml” --network usb0 p3509-a02+p3767-0000 internal
*- Step 1: Build the flashing environment *
*
Create flash environment 0
/workspace/Ref/Platforms/Nvidia-Jetson/Software/SDK_installs/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/bootloader /workspace/Ref/Platforms/Nvidia-Jetson/Software/SDK_installs/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra
/workspace/Ref/Platforms/Nvidia-Jetson/Software/SDK_installs/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra
Finish creating flash environment 0.
*- Step 2: Boot the device with flash initrd image *
*
/workspace/Ref/Platforms/Nvidia-Jetson/Software/SDK_installs/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/temp_initrdflash/bootloader0 /workspace/Ref/Platforms/Nvidia-Jetson/Software/SDK_installs/JetPack_5.1.2_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra
./tegraflash.py --bl uefi_jetson_with_dtb_sigheader.bin.encrypt --bct br_bct_BR.bct --securedev --bldtb tegra234-p3767-0001-p3509-a02.dtb --applet rcm_2_encrypt.rcm --applet_softfuse rcm_1_encrypt.rcm --cmd “rcmboot” --cfg secureflash.xml --chip 0x23 --mb1_bct mb1_bct_MB1_sigheader.bct.encrypt --mem_bct mem_rcm_sigheader.bct.encrypt --mb1_cold_boot_bct mb1_cold_boot_bct_MB1_sigheader.bct.encrypt --mb1_bin mb1_t234_prod_aligned_sigheader.bin.encrypt --psc_bl1_bin psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --mem_bct_cold_boot mem_coldboot_sigheader.bct.encrypt --bins “psc_fw pscfw_t234_prod_sigheader.bin.encrypt; mts_mce mce_flash_o10_cr_prod_sigheader.bin.encrypt; mb2_applet applet_t234_sigheader.bin.encrypt; mb2_bootloader mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt; xusb_fw xusb_t234_prod_sigheader.bin.encrypt; dce_fw display-t234-dce_sigheader.bin.encrypt; nvdec nvdec_t234_prod_sigheader.fw.encrypt; bpmp_fw bpmp_t234-TE980M-A1_prod_sigheader.bin.encrypt; bpmp_fw_dtb tegra234-bpmp-3767-0001-3509-a02_with_odm_sigheader.dtb.encrypt; sce_fw camera-rtcpu-sce_sigheader.img.encrypt; rce_fw camera-rtcpu-t234-rce_sigheader.img.encrypt; ape_fw adsp-fw_sigheader.bin.encrypt; spe_fw spe_t234_sigheader.bin.encrypt; tos tos-optee_t234_sigheader.img.encrypt; eks eks_t234_sigheader.img.encrypt; kernel boot0.img; kernel_dtb tegra234-p3767-0001-p3509-a02.dtb” --secondary_gpt_backup --bct_backup --instance 1-8
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commandsEntering RCM boot
[ 0.0476 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from --mb1_bin
[ 0.0476 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from --psc_bl1_bin
[ 0.0476 ] rcm boot with presigned binaries
[ 0.0488 ] tegrarcm_v2 --instance 1-8 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[ 0.0499 ] BR_CID: 0x80012344705DD41E8000000004008200
[ 0.0637 ] Sending bct_br
[ 0.0763 ] Sending mb1
[ 0.0771 ] Sending psc_bl1
[ 0.0880 ] Sending bct_mb1
[ 0.0937 ] Generating blob for T23x
[ 0.0964 ] tegrahost_v2 --chip 0x23 0 --generateblob blob.xml blob.bin
[ 0.0977 ] The number of images in blob is 18
[ 0.0982 ] blobsize is 73396726
[ 0.0983 ] Added binary blob_uefi_jetson_with_dtb_sigheader.bin.encrypt of size 2920512
[ 0.1463 ] Added binary blob_pscfw_t234_prod_sigheader.bin.encrypt of size 375168
[ 0.1470 ] Added binary blob_mce_flash_o10_cr_prod_sigheader.bin.encrypt of size 190592
[ 0.1474 ] Added binary blob_applet_t234_sigheader.bin.encrypt of size 277312
[ 0.1477 ] Not supported type: mb2_applet
[ 0.1478 ] Added binary blob_mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt of size 438768
[ 0.1482 ] Added binary blob_xusb_t234_prod_sigheader.bin.encrypt of size 164864
[ 0.1485 ] Added binary blob_display-t234-dce_sigheader.bin.encrypt of size 9097216
[ 0.1558 ] Added binary blob_nvdec_t234_prod_sigheader.fw.encrypt of size 294912
[ 0.1570 ] Added binary blob_bpmp_t234-TE980M-A1_prod_sigheader.bin.encrypt of size 1051136
[ 0.1577 ] Added binary blob_tegra234-bpmp-3767-0001-3509-a02_with_odm_sigheader.dtb.encrypt of size 138880
[ 0.1582 ] Added binary blob_camera-rtcpu-sce_sigheader.img.encrypt of size 166304
[ 0.1585 ] Added binary blob_camera-rtcpu-t234-rce_sigheader.img.encrypt of size 540000
[ 0.1589 ] Added binary blob_adsp-fw_sigheader.bin.encrypt of size 400864
[ 0.1592 ] Added binary blob_spe_t234_sigheader.bin.encrypt of size 270336
[ 0.1595 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1127568
[ 0.1598 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
[ 0.1601 ] Added binary blob_boot0.img of size 55584768
[ 0.2015 ] Added binary blob_tegra234-p3767-0001-p3509-a02.dtb of size 347190
[ 0.2639 ] tegrarcm_v2 --instance 1-8 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[ 0.2651 ] BL: version 1.2.0.0-t234-54845784-562369e5 last_boot_error: 0
[ 0.3376 ] Sending bct_mem
[ 0.3731 ] Sending blob
[ 0.4654 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --instance 1-8 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
Cleaning up…
For the custom carrier board, please get the custom BSP package from your vendor instead of using SDK Manager to flash the board.
[ 0.4654 ] ERROR: might be timeout in USB write.
For this issue, please refer to Q: I get a USB timeout error during flash Orin. How to resolve that? to check if it could help. You may need to reboot the host or replug USB several times.
Thanks @KevinFFF for your support. The problem happened with a specific carrier board. I suppose that its USB OTG port is not good.
By the way, it seems that if I flashed a Jetson Orin NX with certain NVMe SSD, then replace this NVMe SSD by another also successfully flashed, it cannot boot. Do you confirm?
Best Regards,
Khang
Do you mean only one carrier board hit the issue but not for other boards?
Do you flash both NVMe SSD with the exact same BSP package?
If so, you can check full serial console log during boot for details.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.