ERROR: might be timeout in USB write after Fuse burning

Hello,
System:
HOST: ubuntu 18.04, latest Jetpack 5.1.2
Target: Jetson orin NX 16GB (Not devkit ) on Waveshare Devkit copy motherboard

the problem is that i stuck with a problem when I followed the guide
Secure Boot — Jetson Linux Developer Guide documentation for securing the bootloader Witk PKC and SBK Keys, and after launching This command:
sudo ./odmfuse.sh -X fuses.xml -i 0x23 jetson-orin-nano-devkit --test and
sudo ./odmfuse.sh -X fuses.xml -i 0x23 jetson-orin-nano-devkit

sudo BOARDID=3767 BOARDSKU=0000 FAB=300 ./tools/kernel_flash/l4t_initrd_flash.sh --network usb0 --usb-instance 1-1 --device-instance 0 --no-flash --external-device nvme0n1p1 -c “tools/kernel_flash/flash_l4t_t234_nvme.xml” -u …/rsa_priv.pem -v …/sbk.xml --network usb0 jetson-orin-nano-devkit external

(Vars for this cmd were double-checked to be same as sdkmanager used (env vars, usb, externav device)

Everything was OK and successful, But when I tried to flash it like this:
cd bootloader
sudo bash ./flashcmd.txt

I found out that this error occurs:

[ 0.0164 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 0.0171 ] File rcm_state open failed
[ 0.0173 ] ERROR: failed to read rcm_state
[ 0.0173 ]
[ 0.0184 ] tegrasign_v3.py --key /mnt/archive/crypto_backup/pkc.pem --getmode mode.txt
[ 0.0193 ] Key size is 384 bytes
[ 0.0189 ] Pre-processing config: tegra234-mb1-bct-device-p3767-0000.dts
[ 0.0227 ] Pre-processing config: tegra234-mb1-bct-misc-p3767-0000.dts
[ 0.0288 ] Parsing partition layout
[ 0.0294 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.0305 ] Kernel DTB used: None
[ 0.0305 ] WARNING: dce base dtb is not provided

[ 0.0305 ] Parsing partition layout
[ 0.0311 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.0318 ] Creating list of images to be encrypted and signed
[ 0.0324 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --list images_list.xml oem-rsa
[ 0.0330 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.0335 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.0337 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.0375 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.0381 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.0423 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.0426 ] adding BCH for mb2_t234_aligned.bin
[ 0.0448 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.0551 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.0553 ] adding BCH for mb2_t234_aligned.bin
[ 0.0687 ] tegrasign_v3.py --file mb1_t234_prod_aligned_sigheader.bin --key /mnt/archive/crypto_backup/Linux_for_Tegra/sbk4.xml --kdf kdf_file=kdf_args_mb1_t234_prod_aligned_sigheader.yaml
[ 0.0698 ] Perform key derivation on mb1_t234_prod_aligned_sigheader.bin
[ 0.0958 ] Key Size is 32 bytes
[ 0.0968 ] Performing aes-gcm encryption
[ 0.0971 ] --key 873bd5043cdff9d91921748e9f405bae7d3dc80e4f6750236b6543277520fd09
[ 0.0974 ] --iv 000000000000000000000000
[ 0.0975 ] --aad 4d42314290290400000000500000005001020100000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.1057 ] Sha saved in mb1_t234_prod_aligned_sigheader_tmp0_encrypt.sha
[ 0.1064 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename A_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin
[ 0.1078 ] INFO: updated file for <A_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.1099 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename B_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin
[ 0.1107 ] INFO: updated file for <B_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.1120 ] tegrasign_v3.py --file mb1_t234_prod_aligned_sigheader.bin --key /mnt/archive/crypto_backup/Linux_for_Tegra/sbk4.xml --kdf kdf_file=kdf_args_mb1_t234_prod_aligned_sigheader.yaml
[ 0.1129 ] Perform key derivation on mb1_t234_prod_aligned_sigheader.bin
[ 0.1393 ] Key Size is 32 bytes
[ 0.1404 ] Performing aes-gcm encryption
[ 0.1407 ] --key 873bd5043cdff9d91921748e9f405bae7d3dc80e4f6750236b6543277520fd09
[ 0.1409 ] --iv 000000000000000000000000
[ 0.1410 ] --aad 4d42314290290400000000500000005001020100000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.1498 ] Sha saved in mb1_t234_prod_aligned_sigheader_tmp0_encrypt.sha
[ 0.1502 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename A_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin
[ 0.1508 ] INFO: updated file for <A_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.1515 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename B_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin
[ 0.1521 ] INFO: updated file for <B_mb1 mb1_bootloader mb1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.1533 ] tegrasign_v3.py --file psc_bl1_t234_prod_aligned_sigheader.bin --key /mnt/archive/crypto_backup/Linux_for_Tegra/sbk4.xml --kdf kdf_file=kdf_args_psc_bl1_t234_prod_aligned_sigheader.yaml
[ 0.1540 ] Perform key derivation on psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.1798 ] Key Size is 32 bytes
[ 0.1808 ] Performing aes-gcm encryption
[ 0.1810 ] --key 5f3959d2e7d57c8d90a79c6a057538e23fb4d1d6694b440d192db3e85adb7c40
[ 0.1813 ] --iv 000000000000000000000000
[ 0.1814 ] --aad 50534342f0bf0100000012000004120006010200000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.1853 ] Sha saved in psc_bl1_t234_prod_aligned_sigheader_tmp0_encrypt.sha
[ 0.1855 ] 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.1861 ] INFO: updated file for <A_psc_bl1 psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.1870 ] 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.1878 ] INFO: updated file for <B_psc_bl1 psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.1890 ] tegrasign_v3.py --file mb2_t234_sigheader.bin --key /mnt/archive/crypto_backup/Linux_for_Tegra/sbk4.xml --kdf kdf_file=kdf_args_mb2_t234_sigheader.yaml
[ 0.1901 ] Perform key derivation on mb2_t234_sigheader.bin
[ 0.2161 ] Key Size is 32 bytes
[ 0.2172 ] Performing aes-gcm encryption
[ 0.2176 ] --key aa2159b6e4f654081a656727e71cce3bb09add3045289c2c4965e3b949dac267
[ 0.2178 ] --iv 000000000000000000000000
[ 0.2179 ] --aad 4d423242a0f10500000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.2296 ] Sha saved in mb2_t234_sigheader_tmp0_encrypt.sha
[ 0.2304 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename A_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin
[ 0.2311 ] INFO: updated file for <A_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin> successfully
[ 0.2324 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename B_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin
[ 0.2330 ] INFO: updated file for <B_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin> successfully
[ 0.2343 ] tegrasign_v3.py --file psc_bl1_t234_prod_aligned_sigheader.bin --key /mnt/archive/crypto_backup/Linux_for_Tegra/sbk4.xml --kdf kdf_file=kdf_args_psc_bl1_t234_prod_aligned_sigheader.yaml
[ 0.2350 ] Perform key derivation on psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.2603 ] Key Size is 32 bytes
[ 0.2613 ] Performing aes-gcm encryption
[ 0.2616 ] --key 5f3959d2e7d57c8d90a79c6a057538e23fb4d1d6694b440d192db3e85adb7c40
[ 0.2618 ] --iv 000000000000000000000000
[ 0.2619 ] --aad 50534342f0bf0100000012000004120006010200000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.2663 ] Sha saved in psc_bl1_t234_prod_aligned_sigheader_tmp0_encrypt.sha
[ 0.2666 ] 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.2672 ] INFO: updated file for <A_psc_bl1 psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.2680 ] 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.2685 ] INFO: updated file for <B_psc_bl1 psc_bl1 psc_bl1_t234_prod_aligned_sigheader_encrypt.bin> successfully
[ 0.2698 ] tegrasign_v3.py --file mb2_t234_sigheader.bin --key /mnt/archive/crypto_backup/Linux_for_Tegra/sbk4.xml --kdf kdf_file=kdf_args_mb2_t234_sigheader.yaml
[ 0.2708 ] Perform key derivation on mb2_t234_sigheader.bin
[ 0.2969 ] Key Size is 32 bytes
[ 0.2979 ] Performing aes-gcm encryption
[ 0.2983 ] --key aa2159b6e4f654081a656727e71cce3bb09add3045289c2c4965e3b949dac267
[ 0.2987 ] --iv 000000000000000000000000
[ 0.2989 ] --aad 4d423242a0f10500000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.3105 ] Sha saved in mb2_t234_sigheader_tmp0_encrypt.sha
[ 0.3115 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename A_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin
[ 0.3122 ] INFO: updated file for <A_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin> successfully
[ 0.3129 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.bin --update_part_filename B_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin
[ 0.3135 ] INFO: updated file for <B_mb2 mb2_bootloader mb2_t234_sigheader_encrypt.bin> successfully
[ 0.3149 ] tegrasign_v3.py --key /mnt/archive/crypto_backup/pkc.pem --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.3158 ] Key size is 384 bytes
[ 0.5390 ] Saving pkc public key in pub_key.key
[ 0.5382 ] Parsing dev params for multi chains
[ 0.5424 ] Generating br-bct
[ 0.5431 ] Updating dev and MSS params in BR BCT
[ 0.5432 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[ 0.5440 ] Updating bl info
[ 0.5446 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.5452 ] WARNING: boot chain is not completed. set to 0
[ 0.5458 ] Perform encryption on bct
[ 0.5469 ] tegrasign_v3.py --file br_bct_BR.bct --key /mnt/archive/crypto_backup/Linux_for_Tegra/sbk4.xml --kdf kdf_file=kdf_args_br_bct_BR.yaml
[ 0.5475 ] Perform key derivation on br_bct_BR.bct
[ 0.5482 ] ERROR: 0 pay load offset 6544
[ 0.5727 ] Key Size is 32 bytes
[ 0.5736 ] Performing aes-gcm encryption
[ 0.5738 ] --key 118a90ef99e4e412824bebbbe83c26feff08c8e3a884107c2ea21beec144a155
[ 0.5739 ] --iv 000000000000000000000000
[ 0.5739 ] --aad 0000000000000000000000000000000042435442000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.5749 ] Sha saved in br_bct_BR_tmp_encrypt.sha
[ 0.5743 ] Get Signed section of bct
[ 0.5758 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[ 0.5775 ] Signing BCT
[ 0.5785 ] tegrasign_v3.py --key /mnt/archive/crypto_backup/pkc.pem --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.5796 ] Key size is 384 bytes
[ 0.6169 ] Saving pkc public key in pub_key.key
[ 0.6160 ] Updating BCT with signature
[ 0.6168 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml --pubkeyhash pub_key.key
[ 0.6174 ] Offset :4608 Len :3584
[ 0.6177 ] Generating SHA2 Hash
[ 0.6186 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[ 0.6188 ] Assuming zero filled SBK key
[ 0.6188 ] Assuming zero filled SBK key
[ 0.6207 ] Sha saved in br_bct_BR.sha
[ 0.6200 ] Updating BCT with SHA2 Hash
[ 0.6207 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[ 0.6217 ] Offset :4608 Len :3584
[ 0.6220 ] Offset :68 Len :8124
[ 0.6221 ] Generating coldboot mb1-bct
[ 0.6231 ] 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.6240 ] MB1-BCT version: 0.10
[ 0.6242 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.6245 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.6248 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.6251 ] ERROR: /misc/tsc_controls/tsc_locking_config is not supported
[ 0.6254 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported
[ 0.6257 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported
[ 0.6259 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported
[ 0.6259 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_configuration is not supported
[ 0.6259 ] ERROR: /misc/tsc_controls/tsc_locking_fast_adjust_configuration is not supported
[ 0.6259 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported
[ 0.6259 ] ERROR: /misc/tsc_controls/tsc_capture_control_ptx is not supported
[ 0.6259 ] ERROR: /misc/tsc_controls/tsc_capture_config_ptx is not supported
[ 0.6259 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported
[ 0.6259 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_num_control is not supported
[ 0.6260 ]
[ 0.6260 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb
[ 0.6260 ] Added Platform Config 9 data with size :- 100
[ 0.6260 ]
[ 0.6260 ] Updating mb1-bct with firmware information
[ 0.6283 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.6293 ] mb1_cold_boot_bct_MB1.bct
[ 0.6293 ] Encrypting and signing mb1_cold_boot_bct_MB1.bct
[ 0.6294 ] header_magic: 4d423142
[ 0.6303 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[ 0.6318 ] tegrahost_v2 --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct oem-rsa --chip 0x23 0 --magicid MBCT
[ 0.6324 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[ 0.6338 ] tegrasign_v3.py --file mb1_cold_boot_bct_MB1_aligned_sigheader.bct --key /mnt/archive/crypto_backup/Linux_for_Tegra/sbk4.xml --kdf kdf_file=kdf_args_mb1_cold_boot_bct_MB1_aligned_sigheader.yaml
[ 0.6345 ] Perform key derivation on mb1_cold_boot_bct_MB1_aligned_sigheader.bct
[ 0.6601 ] Key Size is 32 bytes
[ 0.6611 ] Performing aes-gcm encryption
[ 0.6613 ] --key 3ee45e0867d2fbb74a18b05d436fdfc3242a5cb78cb688511d374c3da5d355f8
[ 0.6618 ] --iv 000000000000000000000000
[ 0.6618 ] --aad 4d42435430150000000004400000044001010000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.6630 ] Sha saved in mb1_cold_boot_bct_MB1_aligned_sigheader_tmp0_encrypt.sha
[ 0.6634 ] tegrasign_v3.py --key /mnt/archive/crypto_backup/pkc.pem --list mb1_cold_boot_bct_MB1_aligned_sigheader_encrypt.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.6641 ] Key size is 384 bytes
[ 0.7020 ] Saving pkc public key in pub_key.key
[ 0.7020 ] tegrahost_v2 --chip 0x23 0 --pubkeyhash pub_key.key --updatesigheader mb1_cold_boot_bct_MB1_aligned_sigheader_encrypt.bct.signed mb1_cold_boot_bct_MB1_aligned_sigheader_encrypt.bct.sig oem-rsa
[ 0.7032 ] Generating recovery mb1-bct
[ 0.7038 ] 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
[ 0.7045 ] MB1-BCT version: 0.10
[ 0.7046 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.7050 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.7052 ] ERROR: carveout /misc/carveout/aux_info@CARVEOUT_UNUSED1/ is not supported
[ 0.7054 ] ERROR: /misc/tsc_controls/tsc_locking_config is not supported
[ 0.7056 ] ERROR: /misc/tsc_controls/tsc_locking_diff_configuration is not supported
[ 0.7058 ] ERROR: /misc/tsc_controls/tsc_locking_ref_frequency_configuration is not supported
[ 0.7061 ] ERROR: /misc/tsc_controls/tsc_locking_control is not supported
[ 0.7063 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_configuration is not supported
[ 0.7063 ] ERROR: /misc/tsc_controls/tsc_locking_fast_adjust_configuration is not supported
[ 0.7063 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_delta_control is not supported
[ 0.7063 ] ERROR: /misc/tsc_controls/tsc_capture_control_ptx is not supported
[ 0.7063 ] ERROR: /misc/tsc_controls/tsc_capture_config_ptx is not supported
[ 0.7063 ] ERROR: /misc/tsc_controls/tsc_stscrsr is not supported
[ 0.7063 ] ERROR: /misc/tsc_controls/tsc_locking_adjust_num_control is not supported
[ 0.7063 ]
[ 0.7063 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb
[ 0.7063 ] Added Platform Config 9 data with size :- 100
[ 0.7063 ]
[ 0.7063 ] Updating mb1-bct with firmware information
[ 0.7070 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.7079 ] mb1_bct_MB1.bct
[ 0.7080 ] Encrypting and signing mb1_bct_MB1.bct
[ 0.7080 ] header_magic: 4d423142
[ 0.7088 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[ 0.7102 ] tegrahost_v2 --appendsigheader mb1_bct_MB1_aligned.bct oem-rsa --chip 0x23 0 --magicid MBCT
[ 0.7109 ] adding BCH for mb1_bct_MB1_aligned.bct
[ 0.7124 ] tegrasign_v3.py --file mb1_bct_MB1_aligned_sigheader.bct --key /mnt/archive/crypto_backup/Linux_for_Tegra/sbk4.xml --kdf kdf_file=kdf_args_mb1_bct_MB1_aligned_sigheader.yaml
[ 0.7130 ] Perform key derivation on mb1_bct_MB1_aligned_sigheader.bct
[ 0.7417 ] Key Size is 32 bytes
[ 0.7437 ] Performing aes-gcm encryption
[ 0.7441 ] --key 3ee45e0867d2fbb74a18b05d436fdfc3242a5cb78cb688511d374c3da5d355f8
[ 0.7444 ] --iv 000000000000000000000000
[ 0.7444 ] --aad 4d42435430150000000004400000044001010000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[ 0.7464 ] Sha saved in mb1_bct_MB1_aligned_sigheader_tmp0_encrypt.sha
[ 0.7469 ] tegrasign_v3.py --key /mnt/archive/crypto_backup/pkc.pem --list mb1_bct_MB1_aligned_sigheader_encrypt.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.7477 ] Key size is 384 bytes
[ 0.7851 ] Saving pkc public key in pub_key.key
[ 0.7852 ] tegrahost_v2 --chip 0x23 0 --pubkeyhash pub_key.key --updatesigheader mb1_bct_MB1_aligned_sigheader_encrypt.bct.signed mb1_bct_MB1_aligned_sigheader_encrypt.bct.sig oem-rsa
[ 0.7863 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 0.7863 ] Error: Skip generating mem_bct because sdram_config is not defined
[ 0.7863 ] Copying signatures
[ 0.7869 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml --pubkeyhash pub_key.key
[ 0.7910 ] mb1_t234_prod_aligned_sigheader_encrypt.bin.signed filename is from images_list
[ 0.7911 ] psc_bl1_t234_prod_aligned_sigheader_encrypt.bin.signed filename is from images_list
[ 0.7911 ] Boot Rom communication
[ 0.7919 ] 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.signed
[ 0.7925 ] BR_CID: 0xEB012344705DD10F2400000011008100
[ 0.9939 ] Sending bct_br
[ 1.2046 ] Sending mb1
[ 1.2054 ] 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.signed
Reading board information failed.
Cleaning up…

Then i tried to call odmfuse once more as stated in guide:
sudo ./odmfuse.sh -X fuses.xml -i 0x23 --auth SBKPKC -k pkc.pem -S sbk.yml jetson-orin-nano-devkit --test

and now even this script fails with this error.

fuses.yml file:

“genericfuse MagicId=“0x45535546” version=“1.0.0”>”
fuse name=“PublicKeyHash” size=“64” value=“0x84e0afc5f0a676b5a78334faa44ad9eb8e73a53dd83554bef4ffdcd63b4b2161cf93fc5c467d5a4b77a7242ab37c5aecc1b3fa9e688215af596565df0ff991b6”/>
fuse name=“SecureBootKey” size=“32” value=“0x09debc22c0c2b521e92538ac8742f3e06d6466b43e42456c68e7e429c9354c0e”/>
fuse name=“OemK1” size=“32” value=“0xf7c8c72d36fbee4763cb2ff7c9ff61f179edad3153ba8f68aa446dc600fb2136”/>
fuse name=“BootSecurityInfo” size=“4” value=“0x20b”/>
fuse name=“SecurityMode” size=“4” value=“0x1”/>
\genericfuse>

Tried many cables and before fusing both flashing through sdkmanager or command line worked fine, but now Jetson can’t be flashed or booted.
Also, I tried to use recover script:
sudo ./tools/backup_restore/l4t_backup_restore.sh -u …/pkc.pem -v sbk4.xml -b -c jetson-orin-nano-devkit

but it also encounters the same error, so now I cant use the device. Could you suggest please what i could do wrong or some steps to fix this. I have all the keys, but i believe the script doesn’t even reach the encryption check stage (I’m not sure). I would be happy if I could get some help. Thank you.

this is incorrect commands for fuse burning.
the --auth options means the current board state, it should be --auth NS since you’ve never fuse before.

so.. do you test flashing the Jetpack release? for example, can board configuration file, jetson-orin-nano-devkit works with this target?

Hello,
the cmd for fuse with --auth flag I used for testing only after I saw that I can’t flash it anymore, just to check if I can re-fuse it. For first fuse I didn’t provide it, so it was like this:
sudo ./odmfuse.sh -X fuses.xml -i 0x23 jetson-orin-nano-devkit

Jetpack release worked fine with jetson-orin-nano-devkit, I did flashing many times for this setup through SDKmanager and before fusing I also tested that I could flash Jetson from command line with the same config file.
The problem occured straight after i fused it.
Also, at this moment, when I try to re-fuse it, odmfuse.sh asks for SBKPKC keys specifically, so if I understood everything correctly, keys were written to it when I fused for first time, but after that it fails.

hello oskaracerlalala,

we’ve test locally without actually burn the target, the test results looks positive.
here’s a valid XML file for your reference.

<genericfuse MagicId="0x45535546" version="1.0.0">
<fuse name="PscOdmStatic" size="4" value="0x00000c60"/>
<fuse name="EndorseKey" size="68" value="0x00001fe07a06789531a60c6823ac90c45c16db9c432b7f0a5b84406263f784fc507c2d0ff93ce820959f404f787bb69c915f902b3d64bffc444b0b8820cb25b38bfca5c7"/>
<fuse name="SecureBootKey" size="32" value="0x123456789abcdef0fedcba987654321023456789abcdef01edcba9876543210f"/>
<fuse name="Kdk0" size="32" value="0x6208e3cd81ed0cd77b214db0c875ade40c26bca09382ad82cd0e24046cc8c64e"/>
<fuse name="OemK1" size="32" value="0xf3bedbff9cea44c05b08124e8242a71ec1871d55ef4841eb4e59a56b5f88fb2b"/>
<fuse name="OemK2" size="32" value="0x76d723099bc81a39cfc8bd109deb7ef39aa1d0f5ab4658180ad33e1d983a2e84"/>
<fuse name="PublicKeyHash" size="64" value="0x18e984f7d79f7a185039ec413ed2ff86227c8f0be639edde0cf23ab1f7910b759ede8fb0c20d02c68deb04a75226d632f9fe24c71dad4b302acdba13db658130"/>
<fuse name="BootSecurityInfo" size="4" value="0x2a09"/>
<fuse name="SecurityMode" size="4" value="0x1"/>
</genericfuse>

Hello, yes, i also had positive results when using --test argument, but after actual fusing this error occured, maybe you can suggest some techniques how to recover it?

hello oskaracerlalala.

we’ve check and confirm fuse burning, and image flashing on Orin NX with a success.
it’s verified with Orin-NX-8GB / l4t-r35.4.1

here’re test steps for your reference,
(1) $ sudo ./odmfuse.sh -X fuses.xml -i 0x23 jetson-orin-nano-devkit
(2) $ sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" -u rsa_priv-3k.pem -v sbk.key --showlogs --network usb0 jetson-orin-nano-devkit internal
(3) $ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only -u rsa_priv-3k.pem -v sbk.key jetson-agx-orin-devkit internal