Hi Nvidia team, I was able to flash the device with no error before. Recently I have enabled secure boot, and the have seen the issue (log attached). Here is step I did:
1.python3 ./source/public/optee/samples/hwkey-agent/host/tool/gen_ekb/gen_ekb.py -chip t234 -oem_k2_key kek_optee.key -fv fv_ekb_t234 -in_sym_key sym_t234.key -in_sym_key2 sym2_t234.key -out bootloader/eks_t234.img
2. sudo ./tools/kernel_flash/l4t_initrd_flash.sh --network usb0 -u ./rsa.pem -v ./sbk.key --no-flash --showlogs -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” jetson-orin-nano-devkit internal
3. sudo ROOTFS_ENC=1 ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs -u ./rsa.pem -v ./sbk.key --no-flash --external-device nvme0n1p1 --uefi-keys uefi_keys/uefi_keys.conf -i ./sym2_t234.key -c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_enc.xml --external-only --append --network usb0 jetson-orin-nano-devkit external
4. sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs -u rsa.pem -v sbk.key --network usb0 --flash-only
uartlog.txt (600.2 KB)
host.txt (42.9 KB)
please help me take a look on it
Thank you.
hello anhhao.hcmus,
it looks like failure has reported due to it cannot mount filesystem.
Add /dev/nvme0n1
[ 10.200892] rndis0: HOST MAC 2a:87:8a:78:dd:3b
[ 10.201020] rndis0: MAC 22:4c:3d:91:93:4d
[ 10.202026] tegra-xudc 3550000.xudc: EP 0 (type: ctrl, dir: out) enabled
[ 10.441966] random: crng init done
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
could you please double check you’re using the same release version (r35.4.1) of public sources to create EKS image.
hello anhhao.hcmus,
we’ve test this locally, could you please refer to Topic 284400 for the steps.
Hi Jerry,
I configured the fuse.xml like this
echo “<genericfuse MagicId="0x45535546" version="1.0.0">” > fuse.xml
echo " <fuse name="PublicKeyHash" size="64" value="${PKCS_KEY_XML_HASH}"/>" >> fuse.xml
echo " <fuse name="SecureBootKey" size="32" value="${SBK_KEY_XML}"/>" >> fuse.xml
echo " <fuse name="OemK2" size="32" value="${KEK_2_KEY_XML}"/>" >> fuse.xml
echo " <fuse name="BootSecurityInfo" size="4" value="0x209"/>" >> fuse.xml
echo “” >> fuse.xml
python3 ./source/public/optee/samples/hwkey-agent/host/tool/gen_ekb/gen_ekb.py -chip t234 -oem_k2_key kek_optee.key -fv fv_ekb_t234 -in_sym_key sym_t234.key -in_sym_key2 sym2_t234.key -out bootloader/eks_t234.img
may I miss something?
I flash and re-flash so many times, issue still occurs on my side.
hello anhhao.hcmus,
you may running with odmfuseread.sh to check fuse variables.
please double check those fused value (on the target) were identical with your command-line.
Hi Jerry, I got the error to run odmfuseread.sh
vaasroot@HP-SERVER:~/disk3/hao/Linux_for_Tegra$ sudo ./odmfuseread.sh -i 0x23 -k rsa.pem -S sbk.key jetson-orin-nano-devkit
./tegraflash.py --chip 0x23 --applet “/home/vaasroot/disk3/hao/Linux_for_Tegra/bootloader/mb1_t234_prod.bin” --skipuid --cfg readinfo_t234_min_prod.xml --dev_params tegra234-br-bct-diag-boot.dts --device_config tegra234-mb1-bct-device-p3767-0000.dts --misc_config tegra234-mb1-bct-misc-p3767-0000.dts --bins “mb2_applet applet_t234.bin” --cmd “dump eeprom cvm cvm.bin; dump custinfo custinfo_out.bin; reboot recovery” --encrypt_key “sbk.key” --key “rsa.pem”
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
[ 0.0443 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 0.0456 ] File rcm_state open failed
[ 0.0456 ] ERROR: failed to read rcm_state
[ 0.0457 ]
[ 0.0468 ] tegrasign_v3.py --key rsa.pem --getmode mode.txt
[ 0.0472 ] Assuming zero filled SBK key : not reading rsa.pem
[ 0.0463 ] Pre-processing config: tegra234-mb1-bct-device-p3767-0000.dts
[ 0.0561 ] Pre-processing config: tegra234-mb1-bct-misc-p3767-0000.dts
[ 0.0714 ] Parsing partition layout
[ 0.0741 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.0784 ] Kernel DTB used: None
[ 0.0784 ] WARNING: dce base dtb is not provided
[ 0.0785 ] Parsing partition layout
[ 0.0810 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.0839 ] Creating list of images to be encrypted and signed
[ 0.0866 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml zerosbk
[ 0.0891 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.0912 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.0918 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.1015 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.1020 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.1088 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.1093 ] adding BCH for mb2_t234_aligned.bin
[ 0.1129 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.1310 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.1315 ] adding BCH for mb2_t234_aligned.bin
[ 0.1544 ] tegrasign_v3.py --file mb1_t234_prod_aligned_sigheader.bin --key sbk.key --kdf kdf_file=kdf_args_mb1_t234_prod_aligned_sigheader.yaml
[ 0.1569 ] Perform key derivation on mb1_t234_prod_aligned_sigheader.bin
[ 0.2198 ] Performing aes-gcm encryption
[ 0.2210 ] --key eb10074e46567037cb7b6b25b11032a98f0cdeef6d6fd530ebfc011aa0c4984a
[ 0.2227 ] --iv 000000000000000000000000
[ 0.2234 ] --aad 4d42314290290400000000500000005001020100000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.2446 ] Sha saved in mb1_t234_prod_aligned_sigheader_tmp0_encrypt.sha
[ 0.2487 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename A_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin
[ 0.2509 ] INFO: updated file for <A_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.2544 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename B_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin
[ 0.2567 ] INFO: updated file for <B_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.2589 ] tegrasign_v3.py --file mb1_t234_prod_aligned_sigheader.bin --key sbk.key --kdf kdf_file=kdf_args_mb1_t234_prod_aligned_sigheader.yaml
[ 0.2629 ] Perform key derivation on mb1_t234_prod_aligned_sigheader.bin
[ 0.3300 ] Performing aes-gcm encryption
[ 0.3308 ] --key eb10074e46567037cb7b6b25b11032a98f0cdeef6d6fd530ebfc011aa0c4984a
[ 0.3317 ] --iv 000000000000000000000000
[ 0.3321 ] --aad 4d42314290290400000000500000005001020100000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.3503 ] Sha saved in mb1_t234_prod_aligned_sigheader_tmp0_encrypt.sha
[ 0.3531 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename A_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin
[ 0.3555 ] INFO: updated file for <A_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.3583 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename B_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin
[ 0.3604 ] INFO: updated file for <B_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.3623 ] tegrasign_v3.py --file psc_bl1_t234_prod_aligned_sigheader.bin --key sbk.key --kdf kdf_file=kdf_args_psc_bl1_t234_prod_aligned_sigheader.yaml
[ 0.3647 ] Perform key derivation on psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.4226 ] Performing aes-gcm encryption
[ 0.4235 ] --key 13d777ac81f457f211f3ef5ff84f33e6270113ae5110083ad111be0256bc3f69
[ 0.4243 ] --iv 000000000000000000000000
[ 0.4247 ] --aad 50534342f0bf0100000012000004120006010200000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.4335 ] Sha saved in psc_bl1_t234_prod_aligned_sigheader_tmp0_encrypt.sha
[ 0.4359 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename A_psc_bl1 psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin
[ 0.4376 ] INFO: updated file for <A_psc_bl1 psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.4402 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename B_psc_bl1 psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin
[ 0.4420 ] INFO: updated file for <B_psc_bl1 psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.4439 ] tegrasign_v3.py --file mb2_t234_sigheader.bin --key sbk.key --kdf kdf_file=kdf_args_mb2_t234_sigheader.yaml
[ 0.4468 ] Perform key derivation on mb2_t234_sigheader.bin
[ 0.5061 ] Performing aes-gcm encryption
[ 0.5071 ] --key 56f4c98a5aeff4dafaa19c51e25cf7c184adefd3b756f0e21dece8838b56a048
[ 0.5080 ] --iv 000000000000000000000000
[ 0.5084 ] --aad 4d423242a0f10500000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.5349 ] Sha saved in mb2_t234_sigheader_tmp0_encrypt.sha
[ 0.5382 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename A_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin
[ 0.5396 ] INFO: updated file for <A_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin> successfully
[ 0.5418 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename B_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin
[ 0.5434 ] INFO: updated file for <B_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin> successfully
[ 0.5450 ] tegrasign_v3.py --file psc_bl1_t234_prod_aligned_sigheader.bin --key sbk.key --kdf kdf_file=kdf_args_psc_bl1_t234_prod_aligned_sigheader.yaml
[ 0.5464 ] Perform key derivation on psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.6036 ] Performing aes-gcm encryption
[ 0.6043 ] --key 13d777ac81f457f211f3ef5ff84f33e6270113ae5110083ad111be0256bc3f69
[ 0.6052 ] --iv 000000000000000000000000
[ 0.6055 ] --aad 50534342f0bf0100000012000004120006010200000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.6158 ] Sha saved in psc_bl1_t234_prod_aligned_sigheader_tmp0_encrypt.sha
[ 0.6185 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename A_psc_bl1 psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin
[ 0.6203 ] INFO: updated file for <A_psc_bl1 psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.6231 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename B_psc_bl1 psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin
[ 0.6253 ] INFO: updated file for <B_psc_bl1 psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.6272 ] tegrasign_v3.py --file mb2_t234_sigheader.bin --key sbk.key --kdf kdf_file=kdf_args_mb2_t234_sigheader.yaml
[ 0.6299 ] Perform key derivation on mb2_t234_sigheader.bin
[ 0.6924 ] Performing aes-gcm encryption
[ 0.6936 ] --key 56f4c98a5aeff4dafaa19c51e25cf7c184adefd3b756f0e21dece8838b56a048
[ 0.6946 ] --iv 000000000000000000000000
[ 0.6951 ] --aad 4d423242a0f10500000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.7277 ] Sha saved in mb2_t234_sigheader_tmp0_encrypt.sha
[ 0.7320 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename A_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin
[ 0.7342 ] INFO: updated file for <A_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin> successfully
[ 0.7372 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename B_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin
[ 0.7396 ] INFO: updated file for <B_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin> successfully
[ 0.7418 ] tegrasign_v3.py --key rsa.pem --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.7423 ] Assuming zero filled SBK key : not reading rsa.pem
[ 0.7711 ] Warning: pub_key.key is not found
[ 0.7702 ] Parsing dev params for multi chains
[ 0.7855 ] Generating br-bct
[ 0.7884 ] Updating dev and MSS params in BR BCT
[ 0.7887 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[ 0.7918 ] Updating bl info
[ 0.7948 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.7973 ] WARNING: boot chain is not completed. set to 0
[ 0.7993 ] Perform encryption on bct
[ 0.8006 ] tegrasign_v3.py --file br_bct_BR.bct --key sbk.key --kdf kdf_file=kdf_args_br_bct_BR.yaml
[ 0.8030 ] Perform key derivation on br_bct_BR.bct
[ 0.8057 ] ERROR: 0 pay load offset 6544
[ 0.8624 ] Performing aes-gcm encryption–key 08b959fa2cebb79a101f95803abced330f308729cfbb99de87c40687b855c97f
[ 0.8633 ] --iv 000000000000000000000000
[ 0.8633 ] --aad 0000000000000000000000000000000042435442000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.8669 ] Sha saved in br_bct_BR_tmp_encrypt.sha
[ 0.8673 ] Get Signed section of bct
[ 0.8701 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[ 0.8727 ] Signing BCT
[ 0.8740 ] tegrasign_v3.py --key rsa.pem --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.8746 ] Assuming zero filled SBK key : not reading rsa.pem
[ 0.8825 ] Sha saved in br_bct_BR.sha
[ 0.8836 ] Warning: pub_key.key is not found
[ 0.8827 ] Updating BCT with signature
[ 0.8854 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[ 0.8881 ] Offset :4608 Len :3584
[ 0.8892 ] Generating SHA2 Hash
[ 0.8904 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[ 0.8910 ] Assuming zero filled SBK key
[ 0.8911 ] Assuming zero filled SBK key
[ 0.8996 ] Sha saved in br_bct_BR.sha
[ 0.8997 ] Updating BCT with SHA2 Hash
[ 0.9024 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[ 0.9049 ] Offset :4608 Len :3584
[ 0.9057 ] Offset :68 Len :8124
[ 0.9058 ]
[ 0.9061 ] Generating coldboot mb1-bct
[ 0.9088 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct.cfg --misc tegra234-mb1-bct-misc-p3767-0000_cpp.dtb --device tegra234-mb1-bct-device-p3767-0000_cpp.dtb
[ 0.9113 ] MB1-BCT version: 0.10
[ 0.9120 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.9139 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.9154 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.9155 ] ERROR: /misc/tsc_controls/tsc_locking_config is not supported
[ 0.9155 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported
[ 0.9155 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported
[ 0.9156 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported
[ 0.9156 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_configuration is not supported
[ 0.9156 ] ERROR: /misc/tsc_controls/tsc_locking_fast_adjust_configuration is not supported
[ 0.9156 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported
[ 0.9157 ] ERROR: /misc/tsc_controls/tsc_capture_control_ptx is not supported
[ 0.9157 ] ERROR: /misc/tsc_controls/tsc_capture_config_ptx is not supported
[ 0.9157 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported
[ 0.9158 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_num_control is not supported
[ 0.9158 ]
[ 0.9158 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb
[ 0.9158 ] Added Platform Config 9 data with size :- 100
[ 0.9159 ]
[ 0.9160 ] Updating mb1-bct with firmware information
[ 0.9188 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.9255 ] mb1_cold_boot_bct_MB1.bct
[ 0.9255 ] Encrypting and signing mb1_cold_boot_bct_MB1.bct
[ 0.9257 ] header_magic: 4d423142
[ 0.9285 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[ 0.9341 ] tegrahost_v2 --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk --chip 0x23 0 --magicid MBCT
[ 0.9369 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[ 0.9391 ] tegrasign_v3.py --file mb1_cold_boot_bct_MB1_aligned_sigheader.bct --key sbk.key --kdf kdf_file=kdf_args_mb1_cold_boot_bct_MB1_aligned_sigheader.yaml
[ 0.9403 ] Perform key derivation on mb1_cold_boot_bct_MB1_aligned_sigheader.bct
[ 0.9990 ] Performing aes-gcm encryption
[ 0.9993 ] --key 353fd4db59aa5bed12216ad633123fc407e67133861b3c2182325ff08ee41bb0
[ 0.9995 ] --iv 000000000000000000000000
[ 0.9996 ] --aad 4d42435430150000000004400000044001010000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 1.0030 ] Sha saved in mb1_cold_boot_bct_MB1_aligned_sigheader_tmp0_encrypt.sha
[ 1.0048 ] tegrasign_v3.py --key rsa.pem --list mb1_cold_boot_bct_MB1_aligned_sigheader_encrypt.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 1.0053 ] Assuming zero filled SBK key : not reading rsa.pem
[ 1.0099 ] Warning: pub_key.key is not found
[ 1.0115 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_cold_boot_bct_MB1_aligned_sigheader_encrypt.bct mb1_cold_boot_bct_MB1_aligned_sigheader_encrypt.bct.hash zerosbk
[ 1.0169 ] Generating recovery mb1-bct
[ 1.0193 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct.cfg --misc tegra234-mb1-bct-misc-p3767-0000_cpp.dtb --device tegra234-mb1-bct-device-p3767-0000_cpp.dtb
[ 1.0210 ] MB1-BCT version: 0.10
[ 1.0214 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 1.0221 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 1.0228 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 1.0237 ] ERROR: /misc/tsc_controls/tsc_locking_config is not supported
[ 1.0237 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported
[ 1.0237 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported
[ 1.0237 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported
[ 1.0237 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_configuration is not supported
[ 1.0237 ] ERROR: /misc/tsc_controls/tsc_locking_fast_adjust_configuration is not supported
[ 1.0237 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported
[ 1.0237 ] ERROR: /misc/tsc_controls/tsc_capture_control_ptx is not supported
[ 1.0237 ] ERROR: /misc/tsc_controls/tsc_capture_config_ptx is not supported
[ 1.0238 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported
[ 1.0238 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_num_control is not supported
[ 1.0238 ]
[ 1.0238 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb
[ 1.0238 ] Added Platform Config 9 data with size :- 100
[ 1.0238 ]
[ 1.0239 ] Updating mb1-bct with firmware information
[ 1.0262 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 1.0290 ] mb1_bct_MB1.bct
[ 1.0291 ] Encrypting and signing mb1_bct_MB1.bct
[ 1.0292 ] header_magic: 4d423142
[ 1.0310 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[ 1.0359 ] tegrahost_v2 --appendsigheader mb1_bct_MB1_aligned.bct zerosbk --chip 0x23 0 --magicid MBCT
[ 1.0376 ] adding BCH for mb1_bct_MB1_aligned.bct
[ 1.0399 ] tegrasign_v3.py --file mb1_bct_MB1_aligned_sigheader.bct --key sbk.key --kdf kdf_file=kdf_args_mb1_bct_MB1_aligned_sigheader.yaml
[ 1.0416 ] Perform key derivation on mb1_bct_MB1_aligned_sigheader.bct
[ 1.1004 ] Performing aes-gcm encryption
[ 1.1008 ] --key 353fd4db59aa5bed12216ad633123fc407e67133861b3c2182325ff08ee41bb0
[ 1.1011 ] --iv 000000000000000000000000
[ 1.1011 ] --aad 4d42435430150000000004400000044001010000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 1.1038 ] Sha saved in mb1_bct_MB1_aligned_sigheader_tmp0_encrypt.sha
[ 1.1049 ] tegrasign_v3.py --key rsa.pem --list mb1_bct_MB1_aligned_sigheader_encrypt.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 1.1052 ] Assuming zero filled SBK key : not reading rsa.pem
[ 1.1088 ] Warning: pub_key.key is not found
[ 1.1102 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader_encrypt.bct mb1_bct_MB1_aligned_sigheader_encrypt.bct.hash zerosbk
[ 1.1137 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 1.1137 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 1.1137 ] Copying signatures
[ 1.1158 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 1.1238 ] mb1_t234_prod_aligned_sigheader_encrypt.bin.signed filename is from images_list
[ 1.1241 ] psc_bl1_t234_prod_aligned_sigheader_encrypt.bin.signed filename is from images_list
[ 1.1242 ] Boot Rom communication
[ 1.1262 ] tegrarcm_v2 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader_encrypt.bin.signed --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin.signed --download bct_mb1 mb1_bct_MB1_sigheader_encrypt.bct
[ 1.1280 ] BR_CID: 0xE9012344705DD4456400000018FF0200
[ 1.1597 ] Sending bct_br
[ 1.2023 ] Sending mb1
[ 1.2031 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader_encrypt.bin.signed --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin.signed --download bct_mb1 mb1_bct_MB1_sigheader_encrypt.bct
Reading board information failed.
Hi Jerry, I read these informations directly on the device. hope it enough
l6a@motorolasolutions:~$ sudo nv_fuse_read.sh
[sudo] password for l6a:
revoke_pk_h0: 0x00000000
revoke_pk_h1: 0x00000000
pk_h1: 0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
odminfo: 0x00000000
pk_h2: 0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
odmid: 0x0000000000000000
system_fw_field_ratchet1: 0x00000000
system_fw_field_ratchet0: 0x00000000
system_fw_field_ratchet3: 0x00000000
system_fw_field_ratchet2: 0x00000000
optin_enable: 0x00000000
public_key_hash: 0xd840a43ee1139efb7767deb5586dff7c69263986e7ccfee52d1887834eaec9e34d755ac3b349774be01960ff5d84386e3e3b9517ef144e4b4a4e4dfebc7b3268
ecid: 0x847262731D63FC08
reserved_odm2: 0x00000000
reserved_odm3: 0x00000000
reserved_odm0: 0x00000000
reserved_odm1: 0x00000000
reserved_odm6: 0x00000000
reserved_odm7: 0x00000000
reserved_odm4: 0x00000000
reserved_odm5: 0x00000000
boot_security_info: 0x00000209
security_mode: 0x00000001
odm_lock: 0x00000000
Hi Jerry, the first time the issue happen, I also enable uefi secure boot along with fuse burnt.
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -u ./rsa.pem -v ./sbk.key --uefi-keys uefi_keys/uefi_keys.conf -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 internal
hello anhhao.hcmus,
it’s known with r35.4.1, which using a sample key with a specific value in gen_ekb python script.
you may refer to example.sh,
for example, this is default oem_k1 key for creating EKS image on r35.4.1
$ echo "2d4a614e645267556b58703273357638792f423f4428472b4b6250655368566d" > oem_k1.key
did you have oem_k1 burn into the target?
besides, instead of running gen_ekb.py, could you please try running with example.sh by updating your keys.
Hi Jerry,
I have not burnt OEM_K1 to the board,
Hi Jerry, I’m not sure my SOM was burnt before or not. could I swap SOM with a new one.
yes, fuse were on the module, you may swap with different SOM to have quick confirmation.
Hi Jerry,
I use the new SOM and l4t 35.5.0. However I’m still seeing the error
[ 10.144692] systemd-journald[235]: Received client request to flush runtime journal.
[ 10.755694] nvidia: loading out-of-tree module taints kernel.
[ 10.768009] imx219 9-0010: imx219_board_setup: error during i2c read probe (-121)
[ 10.783301] imx219 9-0010: board setup failed
[ 10.801970] hot-surface-alert cooling state: 0 → 1
[ 10.811367] imx219: probe of 9-0010 failed with error -121
[ 10.853319] imx219 10-0010: imx219_board_setup: error during i2c read probe (-121)
[ 10.878075] imx219 10-0010: board setup failed
[ 10.889857] imx219: probe of 10-0010 failed with error -121
[ 11.643904] using random self ethernet address
[ 11.648506] using random host ethernet address
[ 11.908233] using random self ethernet address
[ 11.915999] using random host ethernet address
[ 16.100215] nvadsp 2993000.adsp: ADSP OS loading timed out
[ 16.105907] nvadsp 2993000.adsp: Unable to start ADSP OS
[ 16.111424] nvadsp 2993000.adsp: adsp failed to boot with ret = -62
[ 16.117888] nvadsp 2993000.adsp: Dumping ADSP logs …
[ 16.124032] nvadsp 2993000.adsp: End of ADSP log dump …
[ 16.129868] nvadsp 2993000.adsp: dumping fault frame…
[ 16.135269] nvadsp 2993000.adsp: r0 0x00000000 r1 0x00000000 r2 0x00000000 r3 0x00000000
[ 16.143983] nvadsp 2993000.adsp: r4 0x00000000 r5 0x00000000 r6 0x00000000 r7 0x00000000
[ 16.152698] nvadsp 2993000.adsp: r8 0x00000000 r9 0x00000000 r10 0x00000000 r11 0x00000000
[ 16.161427] nvadsp 2993000.adsp: r12 0x00000000 usp 0x00000000 ulr 0x00000000 pc 0x00000000
[ 16.170111] nvadsp 2993000.adsp: spsr 0x00000000
[ 16.174860] nvadsp 2993000.adsp: dumping arm mode register data…
[ 16.181218] nvadsp 2993000.adsp: fiq r13 0x00000000 r14 0x00000000
[ 16.187765] nvadsp 2993000.adsp: irq r13 0x00000000 r14 0x00000000
[ 16.194322] nvadsp 2993000.adsp: svc r13 0x00000000 r14 0x00000000
[ 16.200883] nvadsp 2993000.adsp: und r13 0x00000000 r14 0x00000000
[ 16.207441] nvadsp 2993000.adsp: sys r13 0x00000000 r14 0x00000000
[ 16.213990] nvadsp 2993000.adsp: abt r13 0x00000000 r14 0x00000000
[ 16.221411] tegra210-adsp tegra210-adsp: Failed to start OS
[ 16.227172] tegra210-adsp tegra210-adsp: Failed to init ADSP.
[ 16.265062] tegra210-adsp: probe of tegra210-adsp failed with error -62
is it the same with the previous?
hello anhhao.hcmus,
there’re probing errors, which should not cause boot hang.
besides, please share complete booting logs as a single text file for reference.
Hi Jerry
I’m successfully booting, just out of curious about this error, which I didn’t see after enable secure boot.
Hi Jerry,
May I know if there are any major changes from version R35.4.1 to r35.5.0?
Our device is running R35.3.1 and want to upgrade to newer version with security enabled. Could you please suggest which version should be chosen.
Thank you for your supporting!
hello anhhao.hcmus,
I doubt the root cause was due to incorrect EKS image creation.
anyways, did you meant issue gone by moving to r35.5.0 release version?
please refer Release Notes (r35.5.0) as see-also.
Yes, I dont see the error of cbb like this
CPU:0, Error: cbb-fabric@0x13a00000, irq=25