Tried initrd flashing of Jetson orin nx using this command: sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p “-c ./bootloader/generic/cfg/flash_t234_qspi.xml” -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1 and failed.
Tried the flashing with rootfs A/B enabled method also but failed.
Able to flash with this command : 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 external
Hi,
Is your Orin NX connected to two NVMe drives?
- If yes, please refer to the document.
- If no, provide the flash log and UART log for our review.
Additionally, please confirm the following:
- Is your Orin NX a development kit or a custom carrier board?
- Is your host PC running Ubuntu 18.04 or Ubuntu 20.04 on a physical machine, rather than a virtual machine (such as VMware, VirtualBox, or WSL)?
Thanks
My Orin NX is connected to only one NVMe drive.
Below flashing log when using this command: sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p “-c ./bootloader/generic/cfg/flash_t234_qspi.xml” -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1
Finish generating flash package.
/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --network usb0 --usb-instance 3-9 --device-instance 0 --flash-only --external-device nvme0n1p1 -c "./tools/kernel_flash/flash_l4t_t234_nvme.xml" --network usb0 jetson-orin-nano-devkit nvme0n1p1
**********************************************
* *
* Step 1: Build the flashing environment *
* *
**********************************************
Create flash environment 0
/Linux_for_Tegra/bootloader /Linux_for_Tegra
/Linux_for_Tegra
Finish creating flash environment 0.
****************************************************
* *
* Step 2: Boot the device with flash initrd image *
* *
****************************************************
/Linux_for_Tegra/temp_initrdflash/bootloader0 /Linux_for_Tegra
./tegraflash.py --bl uefi_jetson_with_dtb_sigheader.bin.encrypt --bct br_bct_BR.bct --securedev --bldtb tegra234-p3767-0000-p3768-0000-a0.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-0000-a02-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-0000-p3768-0000-a0.dtb" --secondary_gpt_backup --bct_backup --instance 3-9
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
Entering RCM boot
[ 0.0289 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from --mb1_bin
[ 0.0289 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from --psc_bl1_bin
[ 0.0289 ] rcm boot with presigned binaries
[ 0.0299 ] tegrarcm_v2 --instance 3-9 --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.0308 ] BR_CID: 0x80012344705DD5233C0000000E008240
[ 0.0376 ] Sending bct_br
[ 0.0436 ] Sending mb1
[ 0.0440 ] Sending psc_bl1
[ 0.0853 ] Sending bct_mb1
[ 0.1008 ] Generating blob for T23x
[ 0.1042 ] tegrahost_v2 --chip 0x23 0 --generateblob blob.xml blob.bin
[ 0.1057 ] The number of images in blob is 18
[ 0.1061 ] blobsize is 73448575
[ 0.1062 ] Added binary blob_uefi_jetson_with_dtb_sigheader.bin.encrypt of size 2924608
[ 0.1328 ] Added binary blob_pscfw_t234_prod_sigheader.bin.encrypt of size 375168
[ 0.1331 ] Added binary blob_mce_flash_o10_cr_prod_sigheader.bin.encrypt of size 190592
[ 0.1333 ] Added binary blob_applet_t234_sigheader.bin.encrypt of size 277312
[ 0.1334 ] Not supported type: mb2_applet
[ 0.1334 ] Added binary blob_mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt of size 438768
[ 0.1336 ] Added binary blob_xusb_t234_prod_sigheader.bin.encrypt of size 164864
[ 0.1337 ] Added binary blob_display-t234-dce_sigheader.bin.encrypt of size 9097216
[ 0.1377 ] Added binary blob_nvdec_t234_prod_sigheader.fw.encrypt of size 294912
[ 0.1392 ] Added binary blob_bpmp_t234-TE980M-A1_prod_sigheader.bin.encrypt of size 1051136
[ 0.1396 ] Added binary blob_tegra234-bpmp-3767-0000-a02-3509-a02_with_odm_sigheader.dtb.encrypt of size 258688
[ 0.1398 ] Added binary blob_camera-rtcpu-sce_sigheader.img.encrypt of size 166304
[ 0.1399 ] Added binary blob_camera-rtcpu-t234-rce_sigheader.img.encrypt of size 537952
[ 0.1401 ] Added binary blob_adsp-fw_sigheader.bin.encrypt of size 400864
[ 0.1402 ] Added binary blob_spe_t234_sigheader.bin.encrypt of size 270336
[ 0.1403 ] Added binary blob_tos-optee_t234_sigheader.img.encrypt of size 1127568
[ 0.1406 ] Added binary blob_eks_t234_sigheader.img.encrypt of size 9232
[ 0.1407 ] Added binary blob_boot0.img of size 55515136
[ 0.1655 ] Added binary blob_tegra234-p3767-0000-p3768-0000-a0.dtb of size 346815
[ 0.2081 ] tegrarcm_v2 --instance 3-9 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[ 0.2088 ] BL: version 1.2.0.0-t234-54845784-562369e5 last_boot_error: 0
[ 0.3346 ] Sending bct_mem
[ 0.3772 ] Sending blob
[ 3.6845 ] RCM-boot started
/Linux_for_Tegra
***************************************
* *
* Step 3: Start the flashing process *
* *
***************************************
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for device to expose ssh ......RTNETLINK answers: File exists
RTNETLINK answers: File exists
Waiting for device to expose ssh ...Run command: flash on fc00:1:1:0::2
SSH ready
blockdev: cannot open /dev/mmcblk0boot0: No such file or directory
[ 0]: l4t_flash_from_kernel: Starting to create gpt for emmc
Active index file is /mnt/internal/flash.idx
Number of lines is 76
max_index=75
writing item=59, 6:0:primary_gpt, 512, 19968, gpt_primary_6_0.bin, 16896, fixed-<reserved>-0, 42697fcca798f650d9caac849cfa0e3ec311a1b9
Error: Could not stat device /dev/mmcblk0 - No such file or directory.
Flash failure
Cleaning up...
uart log :
[ 1995.749957] NFS: state manager: check lease failed on NFSv4 server fc00:1:1:0::1 with error 13
[ 2000.870157] NFS: state manager: check lease failed on NFSv4 server fc00:1:1:0::1 with error 13
[ 2005.990096] NFS: state manager: check lease failed on NFSv4 server fc00:1:1:0::1 with error 13
[ 2011.110172] NFS: state manager: check lease failed on NFSv4 server fc00:1:1:0::1 with error 13
[ 2016.231063] NFS: state manager: check lease failed on NFSv4 server fc00:1:1:0::1 with error 13
[ 2021.350171] NFS: state manager: check lease failed on NFSv4 server fc00:1:1:0::1 with error 13
[ 2026.469792] NFS: state manager: check lease failed on NFSv4 server fc00:1:1:0::1 with error 13
[ 2031.590453] NFS: state manager: check lease failed on NFSv4 server fc00:1:1:0::1 with error 13
[ 2036.710014] NFS: state manager: check lease failed on NFSv4 server fc00:1:1:0::1 with error 13
[ 2041.829682] NFS: state manager: check lease failed on NFSv4 server fc00:1:1:0::1 with error 13
I used this command : sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p “-c ./bootloader/t186ref/cfg/flash_t234_qspi.xml” -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit nvme0n1p1
The flash was successful but couldn’t access the device using usb or uart. lsusb it’s not detecting the device. But using hdmi I was able to access the device. The minicom also showed the bootup log when tried software reboot but I couldn’t access the device using minicom.
I wonder what is the exact command you are using to flash. Could you share the screenshot of how your command looks like from your terminal? Actually copy and paste the log in forum is not a good idea because forum will change the format of your command.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.