There are error occurs for flashing the emmc

ubuntu@ubuntu:~/nano/R32.4.4/Linux_for_TegraOK$ sudo ./flash.sh jetson-nano-emmc mmcblk0p1
[sudo] password for ubuntu:
###############################################################################

L4T BSP Information:

R32 , REVISION: 4.4

###############################################################################

Target Board Information:

Name: jetson-nano-emmc, Board Family: t210ref, SoC: Tegra 210,

OpMode: production, Boot Authentication: ,

###############################################################################
./tegraflash.py --chip 0x21 --applet “/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/nvtboot_recovery.bin” --skipuid --cmd “dump eeprom boardinfo cvm.bin”
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.0017 ] Generating RCM messages
[ 0.0025 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/nvtboot_recovery.bin 0 0
[ 0.0032 ] RCM 0 is saved as rcm_0.rcm
[ 0.0035 ] RCM 1 is saved as rcm_1.rcm
[ 0.0035 ] List of rcm files are saved in rcm_list.xml
[ 0.0035 ]
[ 0.0036 ] Signing RCM messages
[ 0.0043 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0049 ] Assuming zero filled SBK key
[ 0.0092 ]
[ 0.0093 ] Copying signature to RCM mesages
[ 0.0100 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0110 ]
[ 0.0110 ] Boot Rom communication
[ 0.0117 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid
[ 0.0124 ] RCM version 0X210001
[ 0.0499 ] Boot Rom communication completed
[ 1.0571 ]
[ 1.0572 ] dump EEPROM info
[ 1.0591 ] tegrarcm --oem platformdetails eeprom /home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/cvm.bin
[ 1.0606 ] Applet version 00.01.0000
[ 1.0710 ] Saved platform info in /home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/cvm.bin
[ 1.3240 ]
Board ID(3448) version(400)
copying bctfile(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/t210ref/BCT/P3448_A00_lpddr4_204Mhz_P987.cfg)… done.
copying bootloader(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/t210ref/cboot.bin)… done.
copying initrd(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/l4t_initrd.img)… done.
populating kernel to rootfs… done.
populating initrd to rootfs… done.
populating /home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/kernel/dtb/tegra210-p3448-0002-p3449-0000-b00.dtb to rootfs… done.
Making Boot image… done.
Existing sosfile(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/nvtboot_recovery.bin) reused.
copying tegraboot(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/t210ref/nvtboot.bin)… done.
copying cpu_bootloader(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/t210ref/cboot.bin)… done.
copying bpffile(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/t210ref/sc7entry-firmware.bin)… done.
Existing badpagefile(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/badpage.bin) reused.
copying wb0boot(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/t210ref/warmboot.bin)… done.
Existing tosfile(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/tos-mon-only.img) reused.
Existing eksfile(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/eks.img) reused.
copying dtbfile(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/kernel/dtb/tegra210-p3448-0002-p3449-0000-b00.dtb)… done.
Copying nv_boot_control.conf to rootfs
Making system.img…
populating rootfs from /home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/rootfs … done.
populating /boot/extlinux/extlinux.conf … Sync’ing system.img … done.
Converting RAW image to Sparse image… done.
system.img built successfully.
Existing tbcfile(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/nvtboot_cpu.bin) reused.
copying tbcdtbfile(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/kernel/dtb/tegra210-p3448-0002-p3449-0000-b00.dtb)… done.
copying cfgfile(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/t210ref/cfg/flash_l4t_t210_emmc_p3448.xml) to flash.xml… done.
copying flasher(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/t210ref/cboot.bin)… done.
Existing flashapp(/home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/tegraflash.py) reused.
./tegraflash.py --bl cboot.bin --bct P3448_A00_lpddr4_204Mhz_P987.cfg --odmdata 0x94000 --bldtb tegra210-p3448-0002-p3449-0000-b00.dtb --applet nvtboot_recovery.bin --cmd “flash; reboot” --cfg flash.xml --chip 0x21 --bins “EBT cboot.bin; DTB tegra210-p3448-0002-p3449-0000-b00.dtb”
saving flash command in /home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/bootloader/flashcmd.txt
saving Windows flash command to /home/ubuntu/nano/R32.4.4/Linux_for_TegraOK/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.0276 ] tegrasign --key None --getmode mode.txt
[ 0.0285 ] Assuming zero filled SBK key
[ 0.0295 ]
[ 0.0297 ] Generating RCM messages
[ 0.0735 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm nvtboot_recovery.bin 0 0
[ 0.0764 ] RCM 0 is saved as rcm_0.rcm
[ 0.0909 ] RCM 1 is saved as rcm_1.rcm
[ 0.0909 ] List of rcm files are saved in rcm_list.xml
[ 0.0909 ]
[ 0.0910 ] Signing RCM messages
[ 0.0944 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0973 ] Assuming zero filled SBK key
[ 0.1164 ]
[ 0.1165 ] Copying signature to RCM mesages
[ 0.1197 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.1241 ]
[ 0.1242 ] Parsing partition layout
[ 0.2064 ] tegraparser --pt flash.xml.tmp
[ 0.2399 ]
[ 0.2401 ] Creating list of images to be signed
[ 0.2804 ] tegrahost --chip 0x21 0 --partitionlayout flash.xml.bin --list images_list.xml
[ 0.3320 ]
[ 0.3320 ] Generating signatures
[ 0.3330 ] tegrasign --key None --list images_list.xml --pubkeyhash pub_key.key
[ 0.3338 ] Assuming zero filled SBK key
[ 0.4126 ]
[ 0.4127 ] Generating br-bct
[ 0.4408 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.cfg --chip 0x21 0
[ 0.4416 ] Copying Sdram info from 2 to 3 set
[ 0.4652 ]
[ 0.4653 ] Updating boot device parameters
[ 0.4662 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatedevparam flash.xml.bin
[ 0.4669 ] Warning: No sdram params
[ 0.4671 ]
[ 0.4671 ] Updating bl info
[ 0.4678 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updateblinfo flash.xml.bin --updatesig images_list_signed.xml
[ 0.4690 ]
[ 0.4690 ] Updating secondary storage information into bct
[ 0.4698 ] tegraparser --pt flash.xml.bin --chip 0x21 0 --updatecustinfo P3448_A00_lpddr4_204Mhz_P987.bct
[ 0.4706 ]
[ 0.4707 ] Updating Odmdata
[ 0.4714 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatefields Odmdata =0x94000
[ 0.4720 ] Warning: No sdram params
[ 0.4722 ]
[ 0.4722 ] Get Signed section of bct
[ 0.4729 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --listbct bct_list.xml
[ 0.4737 ]
[ 0.4737 ] Signing BCT
[ 0.4750 ] tegrasign --key None --list bct_list.xml --pubkeyhash pub_key.key
[ 0.4757 ] Assuming zero filled SBK key
[ 0.4762 ]
[ 0.4762 ] Updating BCT with signature
[ 0.4770 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatesig bct_list_signed.xml
[ 0.4779 ]
[ 0.4780 ] Copying signatures
[ 0.4793 ] tegrahost --chip 0x21 0 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
[ 0.4872 ]
[ 0.4873 ] Updating BFS information on BCT
[ 0.4882 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatebfsinfo flash.xml.bin
[ 0.4888 ] BFS:
[ 0.4899 ] 0: [PT ] flash.xml.bin (size=4339/131072)
[ 0.4910 ] 1: [TBC] nvtboot_cpu.bin.encrypt (size=65760/196608)
[ 0.4915 ] 2: [RP1] tegra210-p3448-0002-p3449-0000-b00.dtb.encrypt (size=242400/1048576)
[ 0.4920 ] 3: [EBT] cboot.bin.encrypt (size=483888/655360)
[ 0.4923 ] 4: [WB0] warmboot.bin.encrypt (size=3952/131072)
[ 0.4926 ] 5: [BPF] sc7entry-firmware.bin.encrypt (size=3376/262144)
[ 0.4929 ] BFS0: 131072 @ 2560 SUM 96e7f5e9 over 2883584 bytes
[ 0.4933 ] BFS:
[ 0.4933 ] 0: [PT-1] flash.xml.bin (size=4339/131072)
[ 0.4936 ] 1: [TBC-1] nvtboot_cpu.bin.encrypt (size=65760/196608)
[ 0.4940 ] 2: [RP1-1] tegra210-p3448-0002-p3449-0000-b00.dtb.encrypt (size=242400/1048576)
[ 0.4944 ] 3: [EBT-1] cboot.bin.encrypt (size=483888/655360)
[ 0.4949 ] 4: [WB0-1] warmboot.bin.encrypt (size=3952/131072)
[ 0.4954 ] 5: [BPF-1] sc7entry-firmware.bin.encrypt (size=3376/262144)
[ 0.4962 ] 8: [VER_b] emmc_bootblob_ver.txt (size=102/32768)
[ 0.5119 ] 9: [VER] emmc_bootblob_ver.txt (size=102/32768)
[ 0.5123 ] BFS1: 131072 @ 8704 SUM 96e7f5e9 over 2981888 bytes
[ 0.5128 ] KFS:
[ 0.5387 ] 0: [DTB] tegra210-p3448-0002-p3449-0000-b00.dtb.encrypt (size=242400/1048576)
[ 0.5392 ] 1: [TOS] tos-mon-only.img.encrypt (size=54208/6291456)
[ 0.5394 ] 2: [EKS] eks.img (size=1028/81920)
[ 0.5909 ] 3: [LNX] boot.img.encrypt (size=485376/67092480)
[ 0.5927 ] KFS0: 1048576 @ 29376546 SUM 81ce28e1 over 7907328 bytes
[ 0.6063 ] KFS:
[ 0.6514 ] 0: [DTB-1] tegra210-p3448-0002-p3449-0000-b00.dtb.encrypt (size=242400/1048576)
[ 0.6521 ] 1: [TOS-1] tos-mon-only.img.encrypt (size=54208/6291456)
[ 0.6526 ] 2: [EKS-1] eks.img (size=1028/81920)
[ 0.6530 ] 3: [LNX-1] boot.img.encrypt (size=485376/67092480)
[ 0.6534 ] KFS1: 1048576 @ 29522082 SUM 81ce28e1 over 7907328 bytes
[ 0.6564 ]
[ 0.6564 ] Boot Rom communication
[ 0.6573 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml
[ 0.6579 ] BootRom is not running
[ 0.6966 ]
[ 0.6967 ] Sending BCTs
[ 0.6976 ] tegrarcm --download bct P3448_A00_lpddr4_204Mhz_P987.bct
[ 0.6984 ] Applet version 00.01.0000
[ 0.7105 ] Sending bct
[ 0.7106 ] […] 100%
[ 0.8050 ]
[ 0.8098 ] tegrahost --chip 0x21 --align cboot.bin
[ 0.8133 ]
[ 0.8166 ] tegrahost --magicid EBT --appendsigheader cboot.bin cboot.bin_blheader
[ 0.8238 ]
[ 0.8279 ] tegrasign --key None --list cboot.bin_list.xml
[ 0.8310 ] Assuming zero filled SBK key
[ 0.8543 ]
[ 0.8557 ] tegrahost --updatesigheader cboot.bin_blheader.encrypt cboot.bin_blheader.hash zerosbk
[ 0.8576 ]
[ 0.8590 ] tegrahost --chip 0x21 --align tegra210-p3448-0002-p3449-0000-b00.dtb
[ 0.8598 ]
[ 0.8607 ] tegrahost --magicid DTB --appendsigheader tegra210-p3448-0002-p3449-0000-b00.dtb tegra210-p3448-0002-p3449-0000-b00.dtb_blheader
[ 0.8623 ]
[ 0.8633 ] tegrasign --key None --list tegra210-p3448-0002-p3449-0000-b00.dtb_list.xml
[ 0.8641 ] Assuming zero filled SBK key
[ 0.8700 ]
[ 0.8710 ] tegrahost --updatesigheader tegra210-p3448-0002-p3449-0000-b00.dtb_blheader.encrypt tegra210-p3448-0002-p3449-0000-b00.dtb_blheader.hash zerosbk
[ 0.8720 ]
[ 0.8724 ] Sending bootloader and pre-requisite binaries
[ 0.8732 ] tegrarcm --download ebt cboot.bin.encrypt 0 0 --download rp1 tegra210-p3448-0002-p3449-0000-b00.dtb.encrypt 0
[ 0.8740 ] Applet version 00.01.0000
[ 0.8866 ] Sending ebt
[ 0.9536 ]
Error: Return value 1
Command tegrarcm --download ebt cboot.bin.encrypt 0 0 --download rp1 tegra210-p3448-0002-p3449-0000-b00.dtb.encrypt 0

hello tpwang2000,

could you please have a try with the latest NVIDIA JetPack SDK release?
we’re able to flash Nano eMMC with r32.5 successfully.
for example,

$ sudo ./flash.sh jetson-nano-emmc mmcblk0p1
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 5.0
###############################################################################
# Target Board Information:
# Name: jetson-nano-emmc, Board Family: t210ref, SoC: Tegra 210, 
# OpMode: production, Boot Authentication: NS, 
# Disk encryption: disabled ,
###############################################################################
...

Board ID(3448) version(400) 
...

[ 169.2553 ] [................................................] 100%
[ 169.6604 ] 
[ 169.6605 ] Flashing completed

[ 169.6607 ] Coldbooting the device
[ 169.6633 ] tegradevflash --reboot coldboot
[ 169.6655 ] Cboot version 00.01.0000
[ 169.6681 ] 
*** The target t210ref has been flashed successfully. ***
Reset the board to boot from internal eMMC.

I have already flash the module before, but now there is a function that is not working normally. I want to reflash the module.
Others modules can be flashed successfully. I use re32.4.4.4

hello tpwang2000,

may I know what’s the modification you had done, is it possible to share error logs for reference?
besides, can this platform boot-up again with default JetPack release image?
thanks

You need log for starting ? I’ll grab the log,
By the way, the module starts very slowly, the temperature is very high, and it is abnormal

I still have another module that can’t get into recovery mode,then How to reflash it?

hello tpwang2000,

we’ll need error logs for reference,
please refer to Jetson Nano - Serial Console - JetsonHacks to setup UART serial console.

you’ll need to enter forced-recovery mode for image flashing.
please also check Preparing a Jetson Developer Kit for Use session for ways to enters Force Recovery Mode.
thanks