TX2 not booting after successful flash of cloned image

I have a frozen image that I took after developing on a TX2 board, and then I tried to reflash it on the jetson I am working on and it works out of the box.

We wanted to use this cloned image on the rest of the Jetson TX2 we have, and then unfortunately it blows up while booting even after a successful flashing. I have the TX2 frozen at the following screen and couldn’t do much, and I was not able to put it back to the recovery mode to flash the fresh image. I completely lost control of it. Any help would be appreciated.

@linuxdev @WayneWWW

I was not even able to detect theTX2 anymore in the lsusb from the host PC

You’ll need to provide the exact clone steps and which L4T release the clone is from, and what you did to install the clone, including if the flash software which created the original L4T install is the same as the release used to restore the clone.

I do see lots of ext4 errors. Do you have both a raw and sparse clone?

@linuxdev Sure.
Thanks for the imminent response.
I used the following command to take the clone of the image :
./flash.sh -r -k APP -G backup.img cti/tx2/quasar mmcblk0p1
Once the cloning is done, I have both the raw and sparse image in the folder.

Clone and the flashed image are both from : L4T R32.4 with Jetpack 4.4

Yes the flash software that created the L4T install is same as that of the release.

What I did to install the clone is:

  1. I added the saved clone image as the system.img inside the bootloader folder
  2. I ran the following command ./flash.sh -r cti/tx2/quasar mmcblk0p1
  3. The flash was successful indeed.

I am attaching the flash log for your reference:

saving flash command in /Linux_for_Tegra/bootloader/flashcmd.txt
saving Windows flash command to /Linux_for_Tegra/bootloader/flash_win.bat
* 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.0008 ] tegrasign_v2 --key None --getmode mode.txt
[   0.0015 ] Assuming zero filled SBK key
[   0.0018 ] 
[   0.0019 ] Generating RCM messages
[   0.0026 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x18 0 --download rcm mb1_recovery_prod.bin 0 0
[   0.0033 ] RCM 0 is saved as rcm_0.rcm
[   0.0036 ] RCM 1 is saved as rcm_1.rcm
[   0.0036 ] List of rcm files are saved in rcm_list.xml
[   0.0036 ] 
[   0.0037 ] Signing RCM messages
[   0.0044 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key
[   0.0050 ] Assuming zero filled SBK key
[   0.0081 ] 
[   0.0081 ] Copying signature to RCM mesages
[   0.0088 ] tegrarcm_v2 --chip 0x18 0 --updatesig rcm_list_signed.xml
[   0.0099 ] 
[   0.0099 ] Parsing partition layout
[   0.0114 ] tegraparser_v2 --pt flash.xml.tmp
[   0.0140 ] 
[   0.0140 ] Creating list of images to be signed
[   0.0155 ] tegrahost_v2 --chip 0x18 0 --partitionlayout flash.xml.bin --list images_list.xml zerosbk
[   0.1024 ] 
[   0.1025 ] Generating signatures
[   0.1046 ] tegrasign_v2 --key None --list images_list.xml --pubkeyhash pub_key.key
[   0.1065 ] Assuming zero filled SBK key
[   0.3192 ] 
[   0.3192 ] Generating br-bct
[   0.3208 ] Updating dev and MSS params in BR BCT
[   0.3208 ] tegrabct_v2 --dev_param emmc.cfg --sdram P3310_A00_8GB_lpddr4_A02_l4t.cfg --brbct br_bct.cfg --chip 0x18 0
[   0.3420 ] 
[   0.3420 ] Updating bl info
[   0.3426 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x18 0 --updateblinfo flash.xml.bin --updatesig images_list_signed.xml
[   0.3438 ] 
[   0.3438 ] Updating smd info
[   0.3443 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x18 --updatesmdinfo flash.xml.bin
[   0.3450 ] 
[   0.3450 ] Updating Odmdata
[   0.3457 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x18 0 --updatefields Odmdata =0x7090000
[   0.3464 ] 
[   0.3464 ] Get Signed section of bct
[   0.3469 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x18 0 --listbct bct_list.xml
[   0.3475 ] 
[   0.3481 ] tegrasign_v2 --key None --list bct_list.xml --pubkeyhash pub_key.key
[   0.3486 ] Assuming zero filled SBK key
[   0.3488 ] 
[   0.3488 ] Updating BCT with signature
[   0.3494 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x18 0 --updatesig bct_list_signed.xml
[   0.3501 ] 
[   0.3501 ] Generating coldboot mb1-bct
[   0.3506 ] tegrabct_v2 --chip 0x18 0 --mb1bct mb1_cold_boot_bct.cfg --sdram P3310_A00_8GB_lpddr4_A02_l4t.cfg --misc tegra186-mb1-bct-misc-si-l4t.cfg --scr mobile_scr.cfg --pinmux tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg --pmc tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg --pmic tegra186-mb1-bct-pmic-quill-p3310-1000-c04.cfg --brcommand tegra186-mb1-bct-bootrom-quill-p3310-1000-c03.cfg --prod tegra186-mb1-bct-prod-quill-p3310-1000-c03.cfg
[   0.3512 ] MB1-BCT version: 0xf
[   0.3513 ] Packing sdram param for instance[0]
[   0.3690 ] Packing sdram param for instance[1]
[   0.3692 ] Packing sdram param for instance[2]
[   0.3694 ] Packing sdram param for instance[3]

[   0.3696 ] Parsing config file :tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg 
[   0.3700 ] Appending platform config data of size :- 3032

[   0.3703 ] Parsing config file :mobile_scr.cfg 
[   0.3705 ] Appending platform config data of size :- 12240

[   0.3709 ] Parsing config file :tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg 
[   0.3710 ] Appending platform config data of size :- 24
[   0.3710 ] 
[   0.3711 ] Parsing config file :tegra186-mb1-bct-pmic-quill-p3310-1000-c04.cfg 
[   0.3711 ] Appending platform config data of size :- 672
[   0.3711 ] 
[   0.3711 ] Parsing config file :tegra186-mb1-bct-bootrom-quill-p3310-1000-c03.cfg 
[   0.3711 ] Appending platform config data of size :- 64
[   0.3711 ] 
[   0.3711 ] Parsing config file :tegra186-mb1-bct-prod-quill-p3310-1000-c03.cfg 
[   0.3711 ] Appending platform config data of size :- 1628
[   0.3711 ] 
[   0.3711 ] Updating mb1-bct with firmware information
[   0.3716 ] tegrabct_v2 --chip 0x18 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo flash.xml.bin
[   0.3721 ] MB1-BCT version: 0xf
[   0.3724 ] 
[   0.3724 ] Updating mb1-bct with storage information
[   0.3729 ] tegrabct_v2 --chip 0x18 --mb1bct mb1_cold_boot_bct_MB1.bct --updatestorageinfo flash.xml.bin
[   0.3734 ] MB1-BCT version: 0xf
[   0.3737 ] 
[   0.3742 ] tegrahost_v2 --chip 0x18 --align mb1_cold_boot_bct_MB1.bct
[   0.3748 ] 
[   0.3753 ] tegrahost_v2 --appendsigheader mb1_cold_boot_bct_MB1.bct zerosbk
[   0.3759 ] 
[   0.3767 ] tegrasign_v2 --key None --list mb1_cold_boot_bct_MB1_sigheader.bct_list.xml --pubkeyhash pub_key.key
[   0.3773 ] Assuming zero filled SBK key
[   0.3783 ] 
[   0.3791 ] tegrahost_v2 --updatesigheader mb1_cold_boot_bct_MB1_sigheader.bct.encrypt mb1_cold_boot_bct_MB1_sigheader.bct.hash zerosbk
[   0.3798 ] 
[   0.3798 ] Generating recovery mb1-bct
[   0.3804 ] tegrabct_v2 --chip 0x18 0 --mb1bct mb1_bct.cfg --sdram P3310_A00_8GB_lpddr4_A02_l4t.cfg --misc tegra186-mb1-bct-misc-si-l4t.cfg --scr minimal_scr.cfg --pinmux tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg --pmc tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg --pmic tegra186-mb1-bct-pmic-quill-p3310-1000-c04.cfg --brcommand tegra186-mb1-bct-bootrom-quill-p3310-1000-c03.cfg --prod tegra186-mb1-bct-prod-quill-p3310-1000-c03.cfg
[   0.3809 ] MB1-BCT version: 0xf
[   0.3811 ] Packing sdram param for instance[0]
[   0.3988 ] Packing sdram param for instance[1]
[   0.3990 ] Packing sdram param for instance[2]
[   0.3992 ] Packing sdram param for instance[3]

[   0.3994 ] Parsing config file :tegra186-mb1-bct-pinmux-quill-p3310-1000-c03.cfg 
[   0.3998 ] Appending platform config data of size :- 3032

[   0.4000 ] Parsing config file :minimal_scr.cfg 
[   0.4002 ] Appending platform config data of size :- 12240

[   0.4010 ] Parsing config file :tegra186-mb1-bct-pad-quill-p3310-1000-c03.cfg 
[   0.4012 ] Appending platform config data of size :- 24
[   0.4013 ] 
[   0.4013 ] Parsing config file :tegra186-mb1-bct-pmic-quill-p3310-1000-c04.cfg 
[   0.4013 ] Appending platform config data of size :- 672
[   0.4013 ] 
[   0.4013 ] Parsing config file :tegra186-mb1-bct-bootrom-quill-p3310-1000-c03.cfg 
[   0.4013 ] Appending platform config data of size :- 64
[   0.4013 ] 
[   0.4013 ] Parsing config file :tegra186-mb1-bct-prod-quill-p3310-1000-c03.cfg 
[   0.4013 ] Appending platform config data of size :- 1628
[   0.4013 ] 
[   0.4013 ] Updating mb1-bct with firmware information
[   0.4019 ] tegrabct_v2 --chip 0x18 --mb1bct mb1_bct_MB1.bct --updatefwinfo flash.xml.bin
[   0.4024 ] MB1-BCT version: 0xf
[   0.4027 ] 
[   0.4027 ] Updating mb1-bct with storage information
[   0.4032 ] tegrabct_v2 --chip 0x18 --mb1bct mb1_bct_MB1.bct --updatestorageinfo flash.xml.bin
[   0.4037 ] MB1-BCT version: 0xf
[   0.4040 ] 
[   0.4045 ] tegrahost_v2 --chip 0x18 --align mb1_bct_MB1.bct
[   0.4051 ] 
[   0.4057 ] tegrahost_v2 --appendsigheader mb1_bct_MB1.bct zerosbk
[   0.4064 ] 
[   0.4071 ] tegrasign_v2 --key None --list mb1_bct_MB1_sigheader.bct_list.xml --pubkeyhash pub_key.key
[   0.4076 ] Assuming zero filled SBK key
[   0.4086 ] 
[   0.4094 ] tegrahost_v2 --updatesigheader mb1_bct_MB1_sigheader.bct.encrypt mb1_bct_MB1_sigheader.bct.hash zerosbk
[   0.4100 ] 
[   0.4101 ] Copying signatures
[   0.4107 ] tegrahost_v2 --chip 0x18 0 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
[   0.4572 ] 
[   0.4572 ] Boot Rom communication
[   0.4586 ] tegrarcm_v2 --chip 0x18 0 --rcm rcm_list_signed.xml
[   0.4597 ] BootRom is not running
[   5.6602 ] 
[   6.6625 ] tegrarcm_v2 --isapplet
[   6.6634 ] Applet version 01.00.0000
[   6.6658 ] 
[   6.6659 ] Sending BCTs
[   6.6670 ] tegrarcm_v2 --download bct_bootrom br_bct_BR.bct --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[   6.6682 ] Applet version 01.00.0000
[   6.7029 ] Sending bct_bootrom
[   6.7037 ] [................................................] 100%
[   6.7055 ] Sending bct_mb1
[   6.7060 ] [................................................] 100%
[   6.7219 ] 
[   6.7221 ] Generating blob
[   6.7254 ] tegrahost_v2 --chip 0x18 --align blob_nvtboot_recovery_cpu.bin
[   6.7284 ] 
[   6.7314 ] tegrahost_v2 --appendsigheader blob_nvtboot_recovery_cpu.bin zerosbk
[   6.7357 ] 
[   6.7393 ] tegrasign_v2 --key None --list blob_nvtboot_recovery_cpu_sigheader.bin_list.xml --pubkeyhash pub_key.key
[   6.7420 ] Assuming zero filled SBK key
[   6.7656 ] 
[   6.7686 ] tegrahost_v2 --updatesigheader blob_nvtboot_recovery_cpu_sigheader.bin.encrypt blob_nvtboot_recovery_cpu_sigheader.bin.hash zerosbk
[   6.7716 ] 
[   6.7738 ] tegrahost_v2 --chip 0x18 --align blob_nvtboot_recovery.bin
[   6.7787 ] 
[   6.7806 ] tegrahost_v2 --appendsigheader blob_nvtboot_recovery.bin zerosbk
[   6.7830 ] 
[   6.7856 ] tegrasign_v2 --key None --list blob_nvtboot_recovery_sigheader.bin_list.xml --pubkeyhash pub_key.key
[   6.7876 ] Assuming zero filled SBK key
[   6.7940 ] 
[   6.7968 ] tegrahost_v2 --updatesigheader blob_nvtboot_recovery_sigheader.bin.encrypt blob_nvtboot_recovery_sigheader.bin.hash zerosbk
[   6.7992 ] 
[   6.8014 ] tegrahost_v2 --chip 0x18 --align blob_preboot_d15_prod_cr.bin
[   6.8035 ] 
[   6.8055 ] tegrahost_v2 --appendsigheader blob_preboot_d15_prod_cr.bin zerosbk
[   6.8079 ] 
[   6.8104 ] tegrasign_v2 --key None --list blob_preboot_d15_prod_cr_sigheader.bin_list.xml --pubkeyhash pub_key.key
[   6.8124 ] Assuming zero filled SBK key
[   6.8171 ] 
[   6.8199 ] tegrahost_v2 --updatesigheader blob_preboot_d15_prod_cr_sigheader.bin.encrypt blob_preboot_d15_prod_cr_sigheader.bin.hash zerosbk
[   6.8223 ] 
[   6.8247 ] tegrahost_v2 --chip 0x18 --align blob_mce_mts_d15_prod_cr.bin
[   6.8266 ] 
[   6.8287 ] tegrahost_v2 --appendsigheader blob_mce_mts_d15_prod_cr.bin zerosbk
[   6.8384 ] 
[   6.8412 ] tegrasign_v2 --key None --list blob_mce_mts_d15_prod_cr_sigheader.bin_list.xml --pubkeyhash pub_key.key
[   6.8430 ] Assuming zero filled SBK key
[   6.9116 ] 
[   6.9126 ] tegrahost_v2 --updatesigheader blob_mce_mts_d15_prod_cr_sigheader.bin.encrypt blob_mce_mts_d15_prod_cr_sigheader.bin.hash zerosbk
[   6.9150 ] 
[   6.9157 ] tegrahost_v2 --chip 0x18 --align blob_bpmp.bin
[   6.9163 ] 
[   6.9169 ] tegrahost_v2 --appendsigheader blob_bpmp.bin zerosbk
[   6.9180 ] 
[   6.9187 ] tegrasign_v2 --key None --list blob_bpmp_sigheader.bin_list.xml --pubkeyhash pub_key.key
[   6.9192 ] Assuming zero filled SBK key
[   6.9290 ] 
[   6.9299 ] tegrahost_v2 --updatesigheader blob_bpmp_sigheader.bin.encrypt blob_bpmp_sigheader.bin.hash zerosbk
[   6.9309 ] 
[   6.9317 ] tegrahost_v2 --chip 0x18 --align blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2.dtb
[   6.9322 ] 
[   6.9328 ] tegrahost_v2 --appendsigheader blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2.dtb zerosbk
[   6.9341 ] 
[   6.9355 ] tegrasign_v2 --key None --list blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2_sigheader.dtb_list.xml --pubkeyhash pub_key.key
[   6.9360 ] Assuming zero filled SBK key
[   6.9473 ] 
[   6.9483 ] tegrahost_v2 --updatesigheader blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2_sigheader.dtb.encrypt blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2_sigheader.dtb.hash zerosbk
[   6.9494 ] 
[   6.9501 ] tegrahost_v2 --chip 0x18 --align blob_tos-trusty.img
[   6.9507 ] 
[   6.9514 ] tegrahost_v2 --appendsigheader blob_tos-trusty.img zerosbk
[   6.9524 ] 
[   6.9531 ] tegrasign_v2 --key None --list blob_tos-trusty_sigheader.img_list.xml --pubkeyhash pub_key.key
[   6.9536 ] Assuming zero filled SBK key
[   6.9603 ] 
[   6.9611 ] tegrahost_v2 --updatesigheader blob_tos-trusty_sigheader.img.encrypt blob_tos-trusty_sigheader.img.hash zerosbk
[   6.9621 ] 
[   6.9627 ] tegrahost_v2 --chip 0x18 --align blob_eks.img
[   6.9632 ] 
[   6.9638 ] tegrahost_v2 --appendsigheader blob_eks.img zerosbk
[   6.9644 ] 
[   6.9651 ] tegrasign_v2 --key None --list blob_eks_sigheader.img_list.xml --pubkeyhash pub_key.key
[   6.9658 ] Assuming zero filled SBK key
[   6.9659 ] 
[   6.9667 ] tegrahost_v2 --updatesigheader blob_eks_sigheader.img.encrypt blob_eks_sigheader.img.hash zerosbk
[   6.9674 ] 
[   6.9680 ] tegrahost_v2 --chip 0x18 --align blob_tegra186-tx2-cti-ASG016.dtb
[   6.9686 ] 
[   6.9692 ] tegrahost_v2 --appendsigheader blob_tegra186-tx2-cti-ASG016.dtb zerosbk
[   6.9700 ] 
[   6.9708 ] tegrasign_v2 --key None --list blob_tegra186-tx2-cti-ASG016_sigheader.dtb_list.xml --pubkeyhash pub_key.key
[   6.9714 ] Assuming zero filled SBK key
[   6.9758 ] 
[   6.9765 ] tegrahost_v2 --updatesigheader blob_tegra186-tx2-cti-ASG016_sigheader.dtb.encrypt blob_tegra186-tx2-cti-ASG016_sigheader.dtb.hash zerosbk
[   6.9773 ] 
[   6.9780 ] tegrahost_v2 --chip 0x18 --generateblob blob.xml blob.bin
[   6.9786 ] number of images in blob are 9
[   6.9789 ] blobsize is 4204120
[   6.9790 ] Added binary blob_nvtboot_recovery_cpu_sigheader.bin.encrypt of size 221312
[   6.9804 ] Added binary blob_nvtboot_recovery_sigheader.bin.encrypt of size 90016
[   6.9808 ] Added binary blob_preboot_d15_prod_cr_sigheader.bin.encrypt of size 63104
[   6.9812 ] Added binary blob_mce_mts_d15_prod_cr_sigheader.bin.encrypt of size 2082144
[   6.9816 ] Added binary blob_bpmp_sigheader.bin.encrypt of size 533904
[   6.9819 ] Added binary blob_tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2_sigheader.dtb.encrypt of size 605120
[   6.9825 ] Added binary blob_tos-trusty_sigheader.img.encrypt of size 366400
[   6.9829 ] Added binary blob_eks_sigheader.img.encrypt of size 1440
[   6.9832 ] Added binary blob_tegra186-tx2-cti-ASG016_sigheader.dtb.encrypt of size 240528
[   6.9841 ] 
[   6.9842 ] Sending bootloader and pre-requisite binaries
[   6.9849 ] tegrarcm_v2 --download blob blob.bin
[   6.9854 ] Applet version 01.00.0000
[   7.0022 ] Sending blob
[   7.0022 ] [................................................] 100%
[   7.4577 ] 
[   7.4606 ] tegrarcm_v2 --boot recovery
[   7.4633 ] Applet version 01.00.0000
[   7.4838 ] 
[   8.4880 ] tegrarcm_v2 --isapplet
[   8.7639 ] 
[   8.7705 ] tegradevflash_v2 --iscpubl
[   8.7729 ] Cannot Open USB
[   9.2896 ] 
[  10.2940 ] tegrarcm_v2 --isapplet
[  10.3139 ] 
[  10.3171 ] tegradevflash_v2 --iscpubl
[  10.3198 ] Bootloader version 01.00.0000
[  10.3387 ] Bootloader version 01.00.0000
[  10.3396 ] 
[  10.3397 ] Retrieving storage infomation
[  10.3427 ] tegrarcm_v2 --oem platformdetails storage storage_info.bin
[  10.3457 ] Applet is not running on device. Continue with Bootloader
[  10.3792 ] 
[  10.3823 ] tegradevflash_v2 --oem platformdetails storage storage_info.bin
[  10.3852 ] Bootloader version 01.00.0000
[  10.4027 ] Saved platform info in storage_info.bin
[  10.4067 ] 
[  10.4068 ] Flashing the device
[  10.4099 ] tegraparser_v2 --storageinfo storage_info.bin --generategpt --pt flash.xml.bin
[  10.4141 ] 
[  10.4171 ] tegradevflash_v2 --pt flash.xml.bin --create
[  10.4199 ] Bootloader version 01.00.0000
[  10.4247 ] Erasing sdmmc_boot: 3 ......... [Done]
[  10.4374 ] Writing partition secondary_gpt with gpt_secondary_0_3.bin
[  10.4393 ] [................................................] 100%

[  10.4502 ] Erasing sdmmc_user: 3 ......... [Done]
[  10.7208 ] Writing partition master_boot_record with mbr_1_3.bin
[  10.7225 ] [................................................] 100%
[  10.7262 ] Writing partition primary_gpt with gpt_primary_1_3.bin
[  10.7281 ] [................................................] 100%
[  10.7323 ] Writing partition secondary_gpt with gpt_secondary_1_3.bin
[  10.7444 ] [................................................] 100%

[  10.7553 ] Writing partition mb1 with mb1_prod.bin.encrypt
[  10.7569 ] [................................................] 100%
[  10.7640 ] Writing partition mb1_b with mb1_prod.bin.encrypt
[  10.7691 ] [................................................] 100%
[  10.7762 ] Writing partition dram-ecc-fw with dram-ecc_sigheader.bin.encrypt
[  10.7807 ] [................................................] 100%
[  10.7869 ] Writing partition badpage-fw with badpage_sigheader.bin.encrypt
[  10.7919 ] [................................................] 100%
[  10.7965 ] Writing partition badpage-fw_b with badpage_sigheader.bin.encrypt
[  10.8016 ] [................................................] 100%
[  10.8064 ] Writing partition spe-fw with spe_sigheader.bin.encrypt
[  10.8108 ] [................................................] 100%
[  10.8176 ] Writing partition spe-fw_b with spe_sigheader.bin.encrypt
[  10.8231 ] [................................................] 100%
[  10.8301 ] Writing partition mb2 with nvtboot_sigheader.bin.encrypt
[  10.8355 ] [................................................] 100%
[  10.8429 ] Writing partition mb2_b with nvtboot_sigheader.bin.encrypt
[  10.8492 ] [................................................] 100%
[  10.8567 ] Writing partition mts-preboot with preboot_d15_prod_cr_sigheader.bin.encrypt
[  10.8626 ] [................................................] 100%
[  10.8684 ] Writing partition mts-preboot_b with preboot_d15_prod_cr_sigheader.bin.encrypt
[  10.8743 ] [................................................] 100%
[  10.8801 ] Writing partition SMD with slot_metadata.bin
[  10.8852 ] [................................................] 100%
[  10.8906 ] Writing partition SMD_b with slot_metadata.bin
[  10.8925 ] [................................................] 100%
[  10.8970 ] Writing partition master_boot_record with mbr_1_3.bin
[  10.8992 ] [................................................] 100%
[  10.9031 ] Writing partition APP with system.img
[  10.9046 ] [................................................] 100%
[ 1072.6275 ] Writing partition mts-bootpack with mce_mts_d15_prod_cr_sigheader.bin.encrypt
[ 1072.6619 ] [................................................] 100%
[ 1072.7444 ] Writing partition mts-bootpack_b with mce_mts_d15_prod_cr_sigheader.bin.encrypt
[ 1072.7631 ] [................................................] 100%
[ 1072.8363 ] Writing partition cpu-bootloader with cboot_sigheader.bin.encrypt
[ 1072.8563 ] [................................................] 100%
[ 1072.8691 ] Writing partition cpu-bootloader_b with cboot_sigheader.bin.encrypt
[ 1072.8773 ] [................................................] 100%
[ 1072.8886 ] Writing partition bootloader-dtb with tegra186-tx2-cti-ASG016_sigheader.dtb.encrypt
[ 1072.8965 ] [................................................] 100%
[ 1072.9077 ] Writing partition bootloader-dtb_b with tegra186-tx2-cti-ASG016_sigheader.dtb.encrypt
[ 1072.9148 ] [................................................] 100%
[ 1072.9254 ] Writing partition secure-os with tos-trusty_sigheader.img.encrypt
[ 1072.9337 ] [................................................] 100%
[ 1072.9486 ] Writing partition secure-os_b with tos-trusty_sigheader.img.encrypt
[ 1072.9581 ] [................................................] 100%
[ 1072.9720 ] Writing partition eks with eks_sigheader.img.encrypt
[ 1072.9821 ] [................................................] 100%
[ 1072.9866 ] Writing partition adsp-fw with adsp-fw_sigheader.bin.encrypt
[ 1072.9912 ] [................................................] 100%
[ 1072.9989 ] Writing partition adsp-fw_b with adsp-fw_sigheader.bin.encrypt
[ 1073.0054 ] [................................................] 100%
[ 1073.0126 ] Writing partition bpmp-fw with bpmp_sigheader.bin.encrypt
[ 1073.0185 ] [................................................] 100%
[ 1073.0382 ] Writing partition bpmp-fw_b with bpmp_sigheader.bin.encrypt
[ 1073.0496 ] [................................................] 100%
[ 1073.0679 ] Writing partition bpmp-fw-dtb with tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2_sigheader.dtb.encrypt
[ 1073.0800 ] [................................................] 100%
[ 1073.1006 ] Writing partition bpmp-fw-dtb_b with tegra186-a02-bpmp-quill-p3310-1000-c04-00-te770d-ucm2_sigheader.dtb.encrypt
[ 1073.1146 ] [................................................] 100%
[ 1073.1339 ] Writing partition sce-fw with camera-rtcpu-sce_sigheader.img.encrypt
[ 1073.1458 ] [................................................] 100%
[ 1073.1537 ] Writing partition sce-fw_b with camera-rtcpu-sce_sigheader.img.encrypt
[ 1073.1599 ] [................................................] 100%
[ 1073.1674 ] Writing partition sc7 with warmboot_wbheader.bin.encrypt
[ 1073.1734 ] [................................................] 100%
[ 1073.1780 ] Writing partition sc7_b with warmboot_wbheader.bin.encrypt
[ 1073.1830 ] [................................................] 100%
[ 1073.1881 ] Writing partition BMP with bmp.blob
[ 1073.1925 ] [................................................] 100%
[ 1073.1988 ] Writing partition BMP_b with bmp.blob
[ 1073.2051 ] [................................................] 100%
[ 1073.2114 ] Writing partition kernel-bootctrl with kernel_bootctrl.bin
[ 1073.2174 ] [................................................] 100%
[ 1073.2225 ] Writing partition kernel-bootctrl_b with kernel_bootctrl.bin
[ 1073.2247 ] [................................................] 100%
[ 1073.2299 ] Writing partition kernel with boot_sigheader.img.encrypt
[ 1073.2320 ] [................................................] 100%
[ 1073.2507 ] Writing partition kernel_b with boot_sigheader.img.encrypt
[ 1073.2619 ] [................................................] 100%
[ 1073.2801 ] Writing partition kernel-dtb with tegra186-tx2-cti-ASG016_sigheader.dtb.encrypt
[ 1073.2924 ] [................................................] 100%
[ 1073.3023 ] Writing partition kernel-dtb_b with tegra186-tx2-cti-ASG016_sigheader.dtb.encrypt
[ 1073.3118 ] [................................................] 100%
[ 1073.3284 ] 
[ 1073.3324 ] tegradevflash_v2 --write BCT br_bct_BR.bct
[ 1073.3354 ] Bootloader version 01.00.0000
[ 1073.3384 ] Writing partition BCT with br_bct_BR.bct
[ 1073.3394 ] [................................................] 100%
[ 1073.3477 ] 
[ 1073.3660 ] tegradevflash_v2 --write MB1_BCT mb1_cold_boot_bct_MB1_sigheader.bct.encrypt
[ 1073.3694 ] Bootloader version 01.00.0000
[ 1073.3726 ] Writing partition MB1_BCT with mb1_cold_boot_bct_MB1_sigheader.bct.encrypt
[ 1073.3748 ] [................................................] 100%
[ 1073.3836 ] 
[ 1073.3867 ] tegradevflash_v2 --write MB1_BCT_b mb1_cold_boot_bct_MB1_sigheader.bct.encrypt
[ 1073.3896 ] Bootloader version 01.00.0000
[ 1073.3927 ] Writing partition MB1_BCT_b with mb1_cold_boot_bct_MB1_sigheader.bct.encrypt
[ 1073.3950 ] [................................................] 100%
[ 1073.4030 ] 
[ 1073.4031 ] Flashing completed

[ 1073.4033 ] Coldbooting the device
[ 1073.4064 ] tegradevflash_v2 --reboot coldboot
[ 1073.4094 ] Bootloader version 01.00.0000
[ 1073.4161 ] 
* The target t186ref has been flashed successfully. *
Reset the board to boot from internal eMMC.

I am super worried as I am not able to set back the TX2 to recovery mode. Please help me.

This is probably the issue. The clone is used only after boot has succeeded up to some point. However, if you have a custom carrier board, then the non-rootfs content would have to be updated for that carrier board. I am guessing that the content surrounding the clone is not correct for that carrier board.

However, this would not change the ability to reach recovery mode. The flash log says you did reach recovery mode, otherwise none of that would have been possible for logging. When you say “I am not able to set back the TX2 to recovery mode”, are you just saying flash fails to create a bootable Jetson? Not reaching recovery mode is far different than not being able to boot.

Btw, you can flash from any board, but the customized boot content in non-rootfs partitions will matter as soon as you actually try to boot.

1 Like

Hello,

@linuxdev So you mean this custom content is only update on the new board on fresh install?. I took a new jetson and flashed the cloned image directly, at this time I was able to set it properly in the recovery mode and then flash it, and the log says successful, as you said may be the non-rootfs partition is still not with customized configuration. So this messed up. How can I solve this?

Once this is done, I powered the device off and turned it on again after few seconds, and then that’s it, the boot is stuck at the above screen. Then, I tried to put the device in recovery mode by pressing recovery button while powering on the device, this doesn’t help at all. I don’t see it in the lsusb log. Even a non recovery state is not displayed in lsusb.

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse]
Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Do you have any suggestions to solve the issue I have?

The custom content from outside of the rootfs is only updated if you update your flash software. The clone will not preserve this content. If you can flash successfully and get boot to succeed with your flash to the custom carrier board device, then flashing again with the clone should do the job (you might need to specify the rootfs size if it is not default).

A flash puts in a lot of non-rootfs content. This is essentially from small images in other parts of the flash software which are picked based on arguments passed to flash.sh. Unless those images/content are updated for your custom carrier board prior to flash, then there will be no valid flash of that content for that custom carrier board. The flash will succeed, but the content will not boot. Mostly the changes are device tree.

If powering up with recovery held down does not show up on the host PC’s lsusb, then there is indeed an error which goes beyond software. One possibility is the micro-B USB cable just isn’t working (charger cables are notoriously bad for data, do you use the supplied micro-B USB of a dev kit?). Most such failures, when they are hardware and not due to cabling/hubs, are a problem of the carrier board, and not the module. Do you have another carrier board you can test with for recovery mode?

@linuxdev Thanks for the clear explanation. So, as per what you said, the non-rootfs content should also correspond to the same part as I have flashed the devices with the same contents on both devices.

The strange part is I used the same micro-B USB cable to use it in recovery mode, and it was flashed successfully, Later I used the same cable to put the device back to recovery but then as I explained no lsusb info found. So, if it is not the cable issue, then it should be the issue of carrier board as you said, that’s worrying. Yes i do have another one, I will try to give it a try, I was just worried that i will also mess it up and leave it without recovery mode. I will keep you posted.

It sounds weird the board cannot enter recovery mode anymore after you use cloned image.
The recovery mode is triggered by the hardware. The software installed on it should have no effect to recovery mode.

Hello @WayneWWW,
Yes, I tried with different USB cables and also different host machine, and we were unsuccessful to change it to recovery mode. I was successful 5/5 time to put a working board in recovery, but not the one’s I flashed with cloned image.

Do you have other TX2 modules or devkits to verify that this issue is really due to cloned image?

Yes, I flashed on 2 of them and they went to this condition and couldn’t set them to the recovery. But I tried it on the same device on which I cloned, and it works flawlessly. This is what bothering me.

@WayneWWW The rootfs and non rootfs files are same, as they are self contained inside the docker, and i was able to flash, clone, and re-flash the image successfully from the same docker time to time.

@WayneWWW @linuxdev
Update: I think I know the issue, the MD5SUM of the cloned image I have and the MD5SUM of the image we cloned on the Jetson’s are different, and this is caused as the scp may not be successful before, because we use different machines to flash the other Jetson, and upon checking the MD5SUM, we came to know that the image we flashed on Jetson is not complete.

What could be done in this case?. Do you think this would result in this behavior?, is there a way to recover it?. Please let me know.

Thank you,

Hi,

What is your method to put your device into recovery mode? Are you using nvidia devkits here? or other customized carrier board?

@WayneWWW
I am holding recovery button while powering on the device, this is the strategy I usually follow to place the device in recovery mode. I am using a customized carrier board.

Do you have nvidia devkit to verify it?

@WayneWWW Unfortunately, no!. I don’t have the devkit.

Ok. Then could you find a online storage and share your cloned image here?
We can clone it to our TX2 and see if we can still flash it or not.

@WayneWWW

I can share, but the problem arised as I wrongly flashed an incomplete cloned image, so I believe any incomplete cloned image might result in this behavior. I flashed the complete proper image with correct MD5SUM and the flashing works perfectly and the device is able to boot properly and I am able to set it up back in recovery mode.

So the culprit here is the incomplete cloned image, as few MBs are missing in the size. Do you know if we can recover from this somehow?

Hi sdikishor,

Actually, I focus more on why a incomplete cloned image would cause recovery mode failure… Not really sure what culprit might be.
Please note that we also tried to erase the whole emmc and then did the flash before and it could still work.

And I don’t quite get your latest comment here. Are there multiple TX2 modules for you to do this test? So you have one TX2 module that is totally not able to work now?

I flashed the complete proper image with correct MD5SUM and the flashing works perfectly and the device is able to boot properly and I am able to set it up back in recovery mode.