Hello, I’m a first time user of Jetson boards and the flashing process failed. I don’t know how to continue trying. The board is a Jetson Orin NX 120 and I’m using Ubuntu 26.04 LTS.
What i did:
I downloaded the recent Firmaware (Jetpack 6.2.2 ) extracted it and ran “sudo ./prepare_JP6_2_2_L4T_folder.sh”. I had to insert a custom script that replaces all occourances of “qemu-user-static” and “qemu-aarch64-static” with their “non-static”-equivalence since they are not available anymore. This custom script is executed before the “apply-binaries”-script is run. then i ran “sudo ./tools/l4t_create_default_user.sh -u user_name -p password -n system_name”. I connected the USB0 to my pc and powered up the board. While running "sudo ./flash_orin_nx_nano_jnx120.sh " the error occured.
Here are the last console outputs that contains information that seems relevant to me:
[ 0.2369 ] Assuming zero filled SBK key
[ 0.2382 ] Warning: pub_key.key is not found
[ 0.2330 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[ 0.2337 ] Info: Skip generating mem_bct because sdram_config is not defined
[ 0.2337 ] Info: Skip generating mem_bct because sdram_config is not defined
[ 0.2337 ] Copying signatures
[ 0.2340 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.2384 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[ 0.2386 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[ 0.2386 ] Boot Rom communication
[ 0.2390 ] tegrarcm_v2 --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
Error: Return value 8
Command tegrarcm_v2 --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.2636 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 0.2649 ] Retrieving board information
[ 0.2653 ] tegrarcm_v2 --chip 0x23 0 --oem platformdetails chip chip_info.bin
[ 0.2660 ] Retrieving EEPROM data
[ 0.2660 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/Firmware/attempt_2/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0
[ 0.2682 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 0.2688 ] Dumping customer Info
[ 0.2691 ] tegrarcm_v2 --chip 0x23 0 --oem dump bct tmp.bct
[ 0.2700 ] tegrabct_v2 --brbct tmp.bct --chip 0x23 0 --custinfo /home/Jetson/Firmware/attempt_2/Linux_for_Tegra/bootloader/custinfo_out.bin
[ 0.2703 ] File tmp.bct open failed
[ 0.2705 ] Error: try getting custinfo fail. Moving on
[ 0.2705 ] Rebooting to recovery mode
[ 0.2710 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[ 0.2714 ] Rebooting to recovery mode
[ 0.2717 ] tegrarcm_v2 --chip 0x23 0 --reboot recovery
Parsing board information failed.
Error: failed to generate images
Cleaning up…
I am grateful for any advice.
EDIT:
I disabled the USB auto suspend and got a bit further. Now a Boot image is made but after that There still comes a “failed to generate images”-Error. I don’t know what’s going on in this process.
Here the newer console output:
…
Making Boot image… done.
Not signing of boot.img
Making recovery ramdisk for recovery image…
Re-generating recovery ramdisk for recovery image…
/home/Jetson/Firmware/Jetson_Linux_r36.5.0_aarch64/Linux_for_Tegra/bootloader/ramdisk_tmp /home/Jetson/Firmware/Jetson_Linux_r36.5.0_aarch64/Linux_for_Tegra/bootloader /home/Jetson/Firmware/Jetson_Linux_r36.5.0_aarch64/Linux_for_Tegra
73771 blocks
_BASE_KERNEL_VERSION=5.15.185-tegra
command is failed
Error: failed to generate images
Cleaning up…
EDIT2:
I traced the error via echo-commads to find which command is failed. when I inserted those echo-commands into the “prepare_sshd_files”-function the flashing process came through. since I haven’t made any functional changes I suspend some kind of race condition as the culprit. Now there is the problem that it cannot connect to its ssh-server.