Flashing not working

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

Hi,
I am not able to flash the Jetson Xavier. The flash script gets stuck after a while with the following output:

...
*** Flashing target device started. ***
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.0012 ] tegrasign_v2 --key None --getmode mode.txt
[   0.0021 ] Assuming zero filled SBK key
[   0.0052 ] 
[   0.0052 ] Generating RCM messages
[   0.0066 ] tegrahost_v2 --chip 0x19 0 --magicid MB1B --appendsigheader mb1_t194_prod.bin zerosbk
[   0.0072 ] Header already present for mb1_t194_prod.bin
[   0.0109 ] 
[   0.0116 ] tegrasign_v2 --key None --getmode mode.txt
[   0.0122 ] Assuming zero filled SBK key
[   0.0123 ] 
[   0.0129 ] tegrasign_v2 --key None --file mb1_t194_prod_sigheader.bin --offset 2960 --length 1136 --pubkeyhash pub_key.key
[   0.0134 ] Assuming zero filled SBK key
[   0.0138 ] 
[   0.0144 ] tegrahost_v2 --chip 0x19 0 --updatesigheader mb1_t194_prod_sigheader.bin mb1_t194_prod_sigheader.hash zerosbk
[   0.0172 ] 
[   0.0208 ] tegrabct_v2 --chip 0x19 0 --sfuse tegra194-mb1-soft-fuses-l4t.cfg sfuse.bin
[   0.0233 ] 
[   0.0243 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x19 0 --sfuses sfuse.bin --download rcm mb1_t194_prod_sigheader.bin 0 0
[   0.0248 ] RCM 0 is saved as rcm_0.rcm
[   0.0279 ] RCM 1 is saved as rcm_1.rcm
[   0.0279 ] RCM 2 is saved as rcm_2.rcm
[   0.0279 ] List of rcm files are saved in rcm_list.xml
[   0.0279 ] 
[   0.0279 ] Signing RCM messages
[   0.0285 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key --getmontgomeryvalues montgomery.bin
[   0.0290 ] Assuming zero filled SBK key
[   0.0294 ] 
[   0.0294 ] Copying signature to RCM mesages
[   0.0300 ] tegrarcm_v2 --chip 0x19 0 --updatesig rcm_list_signed.xml
[   0.0309 ] 
[   0.0310 ] Parsing partition layout
[   0.0347 ] tegraparser_v2 --pt flash.xml.tmp
[   0.0380 ] 
[   0.0380 ] Creating list of images to be signed
[   0.0385 ] tegrahost_v2 --chip 0x19 0 --partitionlayout flash.xml.bin --list images_list.xml zerosbk
[   0.0391 ] MB1: Nvheader already present is mb1_t194_prod.bin
[   0.0396 ] Header already present for mb1_t194_prod_sigheader.bin
[   0.0400 ] MB1: Nvheader already present is mb1_t194_prod.bin
[   0.0421 ] Header already present for mb1_t194_prod_sigheader.bin
[   0.0427 ] adding BCH for spe_t194.bin
[   0.0452 ] adding BCH for spe_t194.bin
[   0.0468 ] adding BCH for nvtboot_t194.bin
[   0.0491 ] adding BCH for nvtboot_t194.bin
[   0.0520 ] Header already present for preboot_c10_prod_cr.bin
[   0.0553 ] Header already present for preboot_c10_prod_cr.bin
[   0.0557 ] Header already present for mce_c10_prod_cr.bin
[   0.0565 ] Header already present for mce_c10_prod_cr.bin
[   0.0578 ] adding BCH for mts_c10_prod_cr.bin
[   0.0643 ] adding BCH for mts_c10_prod_cr.bin
[   0.1213 ] adding BCH for cboot_t194.bin
[   0.1789 ] adding BCH for cboot_t194.bin
[   0.1867 ] adding BCH for tegra194-p2888-0001-p2822-0000-imx377.dtb
[   0.1942 ] adding BCH for tegra194-p2888-0001-p2822-0000-imx377.dtb
[   0.1977 ] adding BCH for tos-mon-only_t194.img
[   0.2014 ] adding BCH for tos-mon-only_t194.img
[   0.2032 ] adding BCH for eks.img
[   0.2051 ] adding BCH for eks.img
[   0.2052 ] adding BCH for bpmp_t194.bin
[   0.2070 ] adding BCH for bpmp_t194.bin
[   0.2216 ] adding BCH for tegra194-a02-bpmp-p2888-a04.dtb
[   0.2405 ] adding BCH for tegra194-a02-bpmp-p2888-a04.dtb
[   0.2511 ] adding BCH for camera-rtcpu-rce.img
[   0.2622 ] adding BCH for camera-rtcpu-rce.img
[   0.2668 ] adding BCH for adsp-fw.bin
[   0.2718 ] adding BCH for adsp-fw.bin
[   0.2737 ] Header already present for warmboot_t194_prod.bin
[   0.2760 ] Header already present for warmboot_t194_prod.bin
[   0.2767 ] adding BCH for boot.img
[   0.2927 ] adding BCH for boot.img
[   0.8733 ] adding BCH for tegra194-p2888-0001-p2822-0000-imx377.dtb
[   1.4725 ] adding BCH for tegra194-p2888-0001-p2822-0000-imx377.dtb
[   1.4800 ] 
[   1.4800 ] Filling MB1 storage info
[   1.4801 ] Generating br-bct
[   1.4808 ] Performing cfg overlay
[   1.4808 ] ['tegra194-mb1-bct-memcfg-p2888.cfg', 'tegra194-memcfg-sw-override.cfg']
[   1.4814 ] sw_memcfg_overlay.pl -c tegra194-mb1-bct-memcfg-p2888.cfg -s tegra194-memcfg-sw-override.cfg -o /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1.cfg
[   1.5234 ] 
[   1.5235 ] Updating dev and MSS params in BR BCT
[   1.5235 ] tegrabct_v2 --dev_param tegra194-br-bct-sdmmc.cfg --sdram /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1.cfg --brbct br_bct.cfg --sfuse tegra194-mb1-soft-fuses-l4t.cfg --chip 0x19 0
[   1.5596 ] 
[   1.5597 ] Updating bl info
[   1.5604 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x19 0 --updateblinfo flash.xml.bin
[   1.5620 ] 
[   1.5620 ] Generating signatures
[   1.5626 ] tegrasign_v2 --key None --list images_list.xml --pubkeyhash pub_key.key
[   1.5633 ] Assuming zero filled SBK key
[   1.6530 ] 
[   1.6531 ] Generating br-bct
[   1.6538 ] Performing cfg overlay
[   1.6538 ] ['/home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1.cfg']
[   1.6539 ] Updating dev and MSS params in BR BCT
[   1.6539 ] tegrabct_v2 --dev_param tegra194-br-bct-sdmmc.cfg --sdram /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1.cfg --brbct br_bct.cfg --sfuse tegra194-mb1-soft-fuses-l4t.cfg --chip 0x19 0
[   1.6879 ] 
[   1.6879 ] Updating bl info
[   1.6886 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x19 0 --updateblinfo flash.xml.bin --updatesig images_list_signed.xml
[   1.6907 ] 
[   1.6908 ] Updating smd info
[   1.6914 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x19 --updatesmdinfo flash.xml.bin
[   1.6923 ] 
[   1.6923 ] Updating Odmdata
[   1.6929 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x19 0 --updatefields Odmdata =0x9190000
[   1.6938 ] 
[   1.6938 ] Get Signed section of bct
[   1.6944 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x19 0 --listbct bct_list.xml
[   1.6951 ] 
[   1.6957 ] tegrasign_v2 --key None --list bct_list.xml --pubkeyhash pub_key.key --getmontgomeryvalues montgomery.bin
[   1.6963 ] Assuming zero filled SBK key
[   1.6964 ] 
[   1.6964 ] Updating BCT with signature
[   1.6971 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x19 0 --updatesig bct_list_signed.xml
[   1.6979 ] 
[   1.6979 ] Generating coldboot mb1-bct
[   1.6989 ] tegrabct_v2 --chip 0x19 0 --mb1bct mb1_cold_boot_bct.cfg --sdram /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1.cfg --misc tegra194-mb1-bct-misc-l4t.cfg --scr tegra194-mb1-bct-scr-cbb-mini.cfg --pinmux tegra19x-mb1-pinmux-p2888-0000-a04-p2822-0000-b01.cfg --pmc tegra19x-mb1-padvoltage-p2888-0000-a00-p2822-0000-a00.cfg --pmic tegra194-mb1-bct-pmic-p2888-0001-a04-E-0-p2822-0000.cfg --brcommand tegra194-mb1-bct-reset-p2888-0000-p2822-0000.cfg --prod tegra19x-mb1-prod-p2888-0000-p2822-0000.cfg --gpioint tegra194-mb1-bct-gpioint-p2888-0000-p2822-0000.cfg --uphy tegra194-mb1-uphy-lane-p2888-0000-p2822-0000.cfg --device tegra19x-mb1-bct-device-sdmmc.cfg
[   1.6995 ] MB1-BCT version: 0x1

[   1.6997 ] Parsing config file :tegra19x-mb1-pinmux-p2888-0000-a04-p2822-0000-b01.cfg 
[   1.7002 ] Added Platform Config 0 data with size :- 3008

[   1.7014 ] Parsing config file :tegra194-mb1-bct-scr-cbb-mini.cfg 
[   1.7016 ] Added Platform Config 1 data with size :- 19640

[   1.7119 ] Parsing config file :tegra19x-mb1-padvoltage-p2888-0000-a00-p2822-0000-a00.cfg 
[   1.7123 ] Added Platform Config 2 data with size :- 24

[   1.7125 ] Parsing config file :tegra194-mb1-bct-pmic-p2888-0001-a04-E-0-p2822-0000.cfg 
[   1.7129 ] Added Platform Config 4 data with size :- 348

[   1.7131 ] Parsing config file :tegra194-mb1-bct-reset-p2888-0000-p2822-0000.cfg 
[   1.7135 ] Added Platform Config 3 data with size :- 92

[   1.7137 ] Parsing config file :tegra19x-mb1-prod-p2888-0000-p2822-0000.cfg 
[   1.7140 ] Added Platform Config 5 data with size :- 56

[   1.7142 ] Parsing config file :tegra194-mb1-bct-gpioint-p2888-0000-p2822-0000.cfg 
[   1.7144 ] Added Platform Config 7 data with size :- 392
[   1.7144 ] 
[   1.7144 ] Parsing config file :tegra194-mb1-uphy-lane-p2888-0000-p2822-0000.cfg 
[   1.7144 ] Added Platform Config 8 data with size :- 12
[   1.7144 ] 
[   1.7144 ] Parsing config file :tegra19x-mb1-bct-device-sdmmc.cfg 
[   1.7144 ] Added Platform Config 9 data with size :- 32
[   1.7144 ] 
[   1.7144 ] Updating mb1-bct with firmware information
[   1.7151 ] tegrabct_v2 --chip 0x19 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo flash.xml.bin
[   1.7157 ] MB1-BCT version: 0x1
[   1.7159 ] 
[   1.7159 ] Updating mb1-bct with storage information
[   1.7165 ] tegrabct_v2 --chip 0x19 --mb1bct mb1_cold_boot_bct_MB1.bct --updatestorageinfo flash.xml.bin
[   1.7171 ] MB1-BCT version: 0x1
[   1.7173 ] 
[   1.7179 ] tegrahost_v2 --chip 0x19 --align mb1_cold_boot_bct_MB1.bct
[   1.7185 ] 
[   1.7192 ] tegrahost_v2 --chip 0x19 0 --magicid MBCT --appendsigheader mb1_cold_boot_bct_MB1.bct zerosbk
[   1.7199 ] adding BCH for mb1_cold_boot_bct_MB1.bct
[   1.7204 ] 
[   1.7213 ] tegrasign_v2 --key None --list mb1_cold_boot_bct_MB1_sigheader.bct_list.xml
[   1.7219 ] Assuming zero filled SBK key
[   1.7220 ] 
[   1.7230 ] tegrahost_v2 --chip 0x19 0 --updatesigheader mb1_cold_boot_bct_MB1_sigheader.bct.encrypt mb1_cold_boot_bct_MB1_sigheader.bct.hash zerosbk
[   1.7239 ] 
[   1.7240 ] Generating recovery mb1-bct
[   1.7247 ] tegrabct_v2 --chip 0x19 0 --mb1bct mb1_bct.cfg --sdram /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1.cfg --misc tegra194-mb1-bct-misc-flash.cfg --scr tegra194-mb1-bct-scr-cbb-mini.cfg --pinmux tegra19x-mb1-pinmux-p2888-0000-a04-p2822-0000-b01.cfg --pmc tegra19x-mb1-padvoltage-p2888-0000-a00-p2822-0000-a00.cfg --pmic tegra194-mb1-bct-pmic-p2888-0001-a04-E-0-p2822-0000.cfg --brcommand tegra194-mb1-bct-reset-p2888-0000-p2822-0000.cfg --prod tegra19x-mb1-prod-p2888-0000-p2822-0000.cfg --gpioint tegra194-mb1-bct-gpioint-p2888-0000-p2822-0000.cfg --uphy tegra194-mb1-uphy-lane-p2888-0000-p2822-0000.cfg --device tegra19x-mb1-bct-device-sdmmc.cfg
[   1.7254 ] MB1-BCT version: 0x1

[   1.7256 ] Parsing config file :tegra19x-mb1-pinmux-p2888-0000-a04-p2822-0000-b01.cfg 
[   1.7259 ] Added Platform Config 0 data with size :- 3008

[   1.7270 ] Parsing config file :tegra194-mb1-bct-scr-cbb-mini.cfg 
[   1.7274 ] Added Platform Config 1 data with size :- 19640

[   1.7373 ] Parsing config file :tegra19x-mb1-padvoltage-p2888-0000-a00-p2822-0000-a00.cfg 
[   1.7377 ] Added Platform Config 2 data with size :- 24

[   1.7379 ] Parsing config file :tegra194-mb1-bct-pmic-p2888-0001-a04-E-0-p2822-0000.cfg 
[   1.7382 ] Added Platform Config 4 data with size :- 348
[   1.7382 ] 
[   1.7382 ] Parsing config file :tegra194-mb1-bct-reset-p2888-0000-p2822-0000.cfg 
[   1.7382 ] Added Platform Config 3 data with size :- 92
[   1.7383 ] 
[   1.7383 ] Parsing config file :tegra19x-mb1-prod-p2888-0000-p2822-0000.cfg 
[   1.7383 ] Added Platform Config 5 data with size :- 56
[   1.7383 ] 
[   1.7383 ] Parsing config file :tegra194-mb1-bct-gpioint-p2888-0000-p2822-0000.cfg 
[   1.7383 ] Added Platform Config 7 data with size :- 392
[   1.7383 ] 
[   1.7383 ] Parsing config file :tegra194-mb1-uphy-lane-p2888-0000-p2822-0000.cfg 
[   1.7383 ] Added Platform Config 8 data with size :- 12
[   1.7383 ] 
[   1.7383 ] Parsing config file :tegra19x-mb1-bct-device-sdmmc.cfg 
[   1.7383 ] Added Platform Config 9 data with size :- 32
[   1.7383 ] 
[   1.7383 ] Updating mb1-bct with firmware information
[   1.7391 ] tegrabct_v2 --chip 0x19 --mb1bct mb1_bct_MB1.bct --updatefwinfo flash.xml.bin
[   1.7398 ] MB1-BCT version: 0x1
[   1.7402 ] 
[   1.7402 ] Updating mb1-bct with storage information
[   1.7408 ] tegrabct_v2 --chip 0x19 --mb1bct mb1_bct_MB1.bct --updatestorageinfo flash.xml.bin
[   1.7413 ] MB1-BCT version: 0x1
[   1.7416 ] 
[   1.7422 ] tegrahost_v2 --chip 0x19 --align mb1_bct_MB1.bct
[   1.7428 ] 
[   1.7434 ] tegrahost_v2 --chip 0x19 0 --magicid MBCT --appendsigheader mb1_bct_MB1.bct zerosbk
[   1.7440 ] adding BCH for mb1_bct_MB1.bct
[   1.7446 ] 
[   1.7454 ] tegrasign_v2 --key None --list mb1_bct_MB1_sigheader.bct_list.xml
[   1.7460 ] Assuming zero filled SBK key
[   1.7461 ] 
[   1.7471 ] tegrahost_v2 --chip 0x19 0 --updatesigheader mb1_bct_MB1_sigheader.bct.encrypt mb1_bct_MB1_sigheader.bct.hash zerosbk
[   1.7480 ] 
[   1.7480 ] Generating coldboot mem-bct
[   1.7486 ] tegrabct_v2 --chip 0x19 0 --sdram /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1.cfg --membct /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_1.bct /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_2.bct /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_3.bct /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_4.bct
[   1.7492 ] Packing sdram param for instance[0]
[   1.7866 ] Packing sdram param for instance[1]
[   1.7868 ] Packing sdram param for instance[2]
[   1.7870 ] Packing sdram param for instance[3]
[   1.7870 ] Packing sdram param for instance[4]
[   1.7870 ] Packing sdram param for instance[5]
[   1.7870 ] Packing sdram param for instance[6]
[   1.7870 ] Packing sdram param for instance[7]
[   1.7870 ] Packing sdram param for instance[8]
[   1.7870 ] Packing sdram param for instance[9]
[   1.7870 ] Packing sdram param for instance[10]
[   1.7870 ] Packing sdram param for instance[11]
[   1.7870 ] Packing sdram param for instance[12]
[   1.7870 ] Packing sdram param for instance[13]
[   1.7870 ] Packing sdram param for instance[14]
[   1.7870 ] Packing sdram param for instance[15]
[   1.7870 ] 
[   1.7871 ] Getting sector size from pt
[   1.7878 ] tegraparser_v2 --getsectorsize flash.xml.bin sector_info.bin
[   1.7885 ] 
[   1.7885 ] BlockSize read from layout is 200

[   1.7892 ] tegrahost_v2 --chip 0x19 0 --blocksize 512 --magicid MEMB --addsigheader_multi /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_1.bct /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_2.bct /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_3.bct /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_4.bct
[   1.7898 ] adding BCH for /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_1.bct
[   1.7917 ] 
[   1.7923 ] tegrahost_v2 --chip 0x19 --align mem_coldboot.bct
[   1.7929 ] 
[   1.7936 ] tegrahost_v2 --chip 0x19 0 --magicid MEMB --appendsigheader mem_coldboot.bct zerosbk
[   1.7942 ] Header already present for mem_coldboot.bct
[   1.7944 ] 
[   1.7953 ] tegrasign_v2 --key None --list mem_coldboot_sigheader.bct_list.xml
[   1.7959 ] Assuming zero filled SBK key
[   1.7962 ] 
[   1.7971 ] tegrahost_v2 --chip 0x19 0 --updatesigheader mem_coldboot_sigheader.bct.encrypt mem_coldboot_sigheader.bct.hash zerosbk
[   1.7980 ] 
[   1.7981 ] Generating recovery mem-bct
[   1.7987 ] tegrabct_v2 --chip 0x19 0 --sdram /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1.cfg --membct /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_1.bct /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_2.bct /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_3.bct /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_4.bct
[   1.7994 ] Packing sdram param for instance[0]
[   1.8366 ] Packing sdram param for instance[1]
[   1.8367 ] Packing sdram param for instance[2]
[   1.8369 ] Packing sdram param for instance[3]
[   1.8372 ] Packing sdram param for instance[4]
[   1.8372 ] Packing sdram param for instance[5]
[   1.8372 ] Packing sdram param for instance[6]
[   1.8372 ] Packing sdram param for instance[7]
[   1.8372 ] Packing sdram param for instance[8]
[   1.8372 ] Packing sdram param for instance[9]
[   1.8372 ] Packing sdram param for instance[10]
[   1.8372 ] Packing sdram param for instance[11]
[   1.8372 ] Packing sdram param for instance[12]
[   1.8372 ] Packing sdram param for instance[13]
[   1.8372 ] Packing sdram param for instance[14]
[   1.8372 ] Packing sdram param for instance[15]
[   1.8372 ] 
[   1.8379 ] tegrahost_v2 --chip 0x19 --align /home/hesmar/Development/3dvisionlabs/embedded/nvidia/L4T-32.1/Linux_for_Tegra/bootloader/18942/tmp3z7_ic1_1.bct
[   1.8386 ] 
[   1.8392 ] tegrahost_v2 --chip 0x19 0 --magicid MEMB --appendsigheader tmp3z7_ic1_1.bct zerosbk
[   1.8398 ] adding BCH for tmp3z7_ic1_1.bct
[   1.8407 ] 
[   1.8415 ] tegrasign_v2 --key None --list tmp3z7_ic1_1_sigheader.bct_list.xml
[   1.8421 ] Assuming zero filled SBK key
[   1.8423 ] 
[   1.8432 ] tegrahost_v2 --chip 0x19 0 --updatesigheader tmp3z7_ic1_1_sigheader.bct.encrypt tmp3z7_ic1_1_sigheader.bct.hash zerosbk
[   1.8445 ] 
[   1.8445 ] Copying signatures
[   1.8452 ] tegrahost_v2 --chip 0x19 0 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
[   2.6805 ] 
[   2.6806 ] Boot Rom communication
[   2.6813 ] tegrarcm_v2 --chip 0x19 0 --rcm rcm_list_signed.xml
[   2.6820 ] BootRom is not running
[   8.2717 ] 
[   9.2758 ] tegrarcm_v2 --isapplet

KDE neon is running on my host, which is based on Ubuntu 18.04. The Jetson is directly connected to the laptop, no external USB hub is in between. Any idea what could be the reason for this issue?

2

Hi MarkusHeĂź,

Your issue seems to be similar as below one:
[url]https://devtalk.nvidia.com/default/topic/1044499/jetson-agx-xavier/cpu-bootloader-is-not-running-on-jetson-xavier/post/5299368/#5299368[/url]

Thanks

3

Hi kayccc,

yes I also found this thread before, but I am not using a VM host for flashing. So it is slightly different to the issue in the other thread. I was able to flash the Jetson from another PC, so the Jetson itself should be ok. Therefore, it is somehow related to my host system. It is a Dell XPS 15 9570. The weird thing is, that even the flashing of the TX2 stopped working. It was working before, so maybe it it related to a kernel update or something similar. Maybe someone else encounter similar issues with the Dell XPS 15 and/or KDE neon/Ubuntu 18.04? How could I further debug this issue?

4

Try simplifying by just flashing on command line as a test (you can always run package install steps later). Wheever you ran SDK Manager or JetPack from there will be a “Linux_for_Tegra/” subdirectory (which is actually from the driver package). From there, assuming you find content in “Linux_for_Tegra/rootfs/”:

Put Xavier in recovery mode with the right USB cables attached.

sudo ./flash.sh jetson-xavier mmcblk0p1

To instead log while flashing (I recommend):

sudo ./flash.sh jetson-xavier mmcblk0p1 2>&1 | tee log_flash.txt
5

Hi linuxdev,
I already use the flash script and not the SDK Manager.

6

Can you post a log?

This will produce a log with much of the progress bar removed for a shorter log:

sudo ./flash.sh jetson-xavier mmcblk0p1 2>&1 | gawk '{gsub("[0-9][0-9]+[/][0-9[0-9]+ bytes sent..",".");print}' | tee log.txt
7

The log in my first post is the result from

sudo ./flash.sh jetson-xavier mmcblk0p1

Only the image preparation part was removed to reduce the log size. I can try it again tomorrow with your command and post the full log.

8

So this does indicate a problem that the last lines are:

[   2.6820 ] BootRom is not running
[   8.2717 ] 
[   9.2758 ] tegrarcm_v2 --isapplet

Someone else will need to answer since I do not know what causes there are for “Bootrom is not running”. Seeing as this is on command line using flash.sh it does eliminate SDK Manager and JetPack as being the issue.

9

Ok, thanks linuxdev!

Maybe someone else could help to resolve this issue?

10

ubuntu 18.04 works just fine.
Can you try rebooting your system and also changing the usb port/cable
system is not going to recovery state on that host machine
lsusb should show you nvidia

11

Hi bbasu,

lsusb shows me nvidia, so it should be in recovery mode. If I do not put it into recovery mode, the flash.sh script also stops already at the beginning with

Error: probing the target board failed.
       Make sure the target board is connected through 
       micro-B USB port and is in recovery mode.

With recovery mode enabled, it starts generating the system image and fails afterwards when it tries to flash the boards (see the log in the first post). I also tried different USB ports and cables with no success. Any ideas, how to further debug the issue?

12

Hi,

You have not attached the complete log.
Target goes to recovery twice during flashing.
First time when you put it to recovery and then tegraflash reads chipid, eeprom etc.
And then 2nd time when tegraflash puts the board to recovery to flash it. that is not happening.
Your log is from the 2nd point.

Can you add a 3sec sleep before the below line in flash.sh and try

sleep 3
echo “*** Flashing target device started. ***”

13

Oh sorry, I didn’t attach the whole log because it was too big. If you want to have a look on it, you can find it here: [url]3dvisionlabs Cloud
Please note that the log is from flashing a TX2 with L4T 28.2 because I can not use the Xavier at the moment. Nevertheless, the behavior is the same.

Adding the sleep did not help. I tried also to increase the sleep time to 10s but it still says “BootRom is not running”.

14

Can you connect to a USB2.0 port in your host machine and confirm?

15

The Dell XPS 15 9570 only has two USB3.1 Gen1 ports, so I can not use a USB2.0 port.

16

Can you connect a hub with 2.0 port on it and then connect to target?

17

Ok, I used a USB 2.0 hub, but unfortunately this also did not help.

18

sorry, I am running out of ideas.
Now the only option left is to capture and analyze the USB traces.

Now , we should concentrate on Dell XPS 15 9570.
Is this the only system not working or all Dell XPS 15 9570?
May be we can flash from a VM environment in your existing setup.

19

I tried to flash the board using an Ubuntu 18.04 live USB and it was successful. So it seems to be OS related. I will prepare a KDE neon live USB and try it again.

20

Ok, it also works with a KDE neon live USB. I have no idea what’s wrong with my system. Do you have any idea, what I could check next?