Failed Flashing t210ref

I have trouble flashing the Jetson Nano B01 board after doing FC Rec. Below shows the errors I faced, hope to hear from you soon. Thanks.

After reading through some forums, I had tried changing my micro-usb wires and installing the libxml2-utils library using:
$sudo apt-get install libxml2-utils


(base) sumitrra@sumitrra-N56VZ:~/Linux_for_Tegra$ sudo ./flash.sh p3448-0000-max-spi external
###############################################################################

L4T BSP Information:

R32 , REVISION: 4.4

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

Target Board Information:

Name: p3448-0000-max-spi, Board Family: t210ref, SoC: Tegra 210,

OpMode: production, Boot Authentication: ,

###############################################################################
./tegraflash.py --chip 0x21 --applet “/home/sumitrra/Linux_for_Tegra/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.0023 ] Generating RCM messages
[ 0.0037 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/sumitrra/Linux_for_Tegra/bootloader/nvtboot_recovery.bin 0 0
[ 0.0055 ] RCM 0 is saved as rcm_0.rcm
[ 0.0069 ] RCM 1 is saved as rcm_1.rcm
[ 0.0069 ] List of rcm files are saved in rcm_list.xml
[ 0.0069 ]
[ 0.0070 ] Signing RCM messages
[ 0.0081 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0090 ] Assuming zero filled SBK key
[ 0.0171 ]
[ 0.0172 ] Copying signature to RCM mesages
[ 0.0189 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0209 ]
[ 0.0210 ] Boot Rom communication
[ 0.0223 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid
[ 0.0237 ] RCM version 0X210001
[ 0.1261 ] Boot Rom communication completed
[ 1.1331 ]
[ 1.1334 ] dump EEPROM info
[ 1.1358 ] tegrarcm --oem platformdetails eeprom /home/sumitrra/Linux_for_Tegra/bootloader/cvm.bin
[ 1.1375 ] Applet version 00.01.0000
[ 1.2153 ] Saved platform info in /home/sumitrra/Linux_for_Tegra/bootloader/cvm.bin
[ 1.2920 ]
Board ID(3448) version(401)
Using UUID 555c02c0-9178-44ed-90c8-8870f32fb19d for mounting root partition.
copying bctfile(/home/sumitrra/Linux_for_Tegra/bootloader/t210ref/BCT/P3448_A00_lpddr4_204Mhz_P987.cfg)… done.
copying bootloader(/home/sumitrra/Linux_for_Tegra/bootloader/t210ref/cboot.bin)… done.
copying initrd(/home/sumitrra/Linux_for_Tegra/bootloader/l4t_initrd.img)… done.
populating kernel to rootfs… done.
populating initrd to rootfs… done.
populating /home/sumitrra/Linux_for_Tegra/kernel/dtb/tegra210-p3448-0002-p3449-0000-b00.dtb to rootfs… done.
Making Boot image… done.
Existing sosfile(/home/sumitrra/Linux_for_Tegra/bootloader/nvtboot_recovery.bin) reused.
copying tegraboot(/home/sumitrra/Linux_for_Tegra/bootloader/t210ref/nvtboot.bin)… done.
copying cpu_bootloader(/home/sumitrra/Linux_for_Tegra/bootloader/t210ref/cboot.bin)… done.
copying bpffile(/home/sumitrra/Linux_for_Tegra/bootloader/t210ref/sc7entry-firmware.bin)… done.
Existing badpagefile(/home/sumitrra/Linux_for_Tegra/bootloader/badpage.bin) reused.
copying wb0boot(/home/sumitrra/Linux_for_Tegra/bootloader/t210ref/warmboot.bin)… done.
Existing tosfile(/home/sumitrra/Linux_for_Tegra/bootloader/tos-mon-only.img) reused.
Existing eksfile(/home/sumitrra/Linux_for_Tegra/bootloader/eks.img) reused.
copying dtbfile(/home/sumitrra/Linux_for_Tegra/kernel/dtb/tegra210-p3448-0002-p3449-0000-b00.dtb)… done.
Copying nv_boot_control.conf to rootfs
sed: can’t read /home/sumitrra/Linux_for_Tegra/rootfs/etc/nv_boot_control.conf: Not a directory
sed: can’t read /home/sumitrra/Linux_for_Tegra/rootfs/etc/nv_boot_control.conf: Not a directory
sed: can’t read /home/sumitrra/Linux_for_Tegra/rootfs/etc/nv_boot_control.conf: Not a directory
sed: can’t read /home/sumitrra/Linux_for_Tegra/rootfs/etc/nv_boot_control.conf: Not a directory
sed: can’t read /home/sumitrra/Linux_for_Tegra/rootfs/etc/nv_boot_control.conf: Not a directory
sed: can’t read /home/sumitrra/Linux_for_Tegra/rootfs/etc/nv_boot_control.conf: Not a directory
sed: can’t read /home/sumitrra/Linux_for_Tegra/rootfs/etc/nv_boot_control.conf: Not a directory
sed: can’t read /home/sumitrra/Linux_for_Tegra/rootfs/etc/nv_boot_control.conf: Not a directory
Skip generating system.img
Existing tbcfile(/home/sumitrra/Linux_for_Tegra/bootloader/nvtboot_cpu.bin) reused.
copying tbcdtbfile(/home/sumitrra/Linux_for_Tegra/kernel/dtb/tegra210-p3448-0002-p3449-0000-b00.dtb)… done.
copying cfgfile(/home/sumitrra/Linux_for_Tegra/bootloader/t210ref/cfg/flash_l4t_t210_max-spi_p3448.xml) to flash.xml… done.
copying flasher(/home/sumitrra/Linux_for_Tegra/bootloader/t210ref/cboot.bin)… done.
Existing flashapp(/home/sumitrra/Linux_for_Tegra/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
saving flash command in /home/sumitrra/Linux_for_Tegra/bootloader/flashcmd.txt
saving Windows flash command to /home/sumitrra/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.0012 ] tegrasign --key None --getmode mode.txt
[ 0.0025 ] Assuming zero filled SBK key
[ 0.0027 ]
[ 0.0029 ] Generating RCM messages
[ 0.0042 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm nvtboot_recovery.bin 0 0
[ 0.0054 ] RCM 0 is saved as rcm_0.rcm
[ 0.0065 ] RCM 1 is saved as rcm_1.rcm
[ 0.0065 ] List of rcm files are saved in rcm_list.xml
[ 0.0065 ]
[ 0.0066 ] Signing RCM messages
[ 0.0078 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0089 ] Assuming zero filled SBK key
[ 0.0197 ]
[ 0.0199 ] Copying signature to RCM mesages
[ 0.0217 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0249 ]
[ 0.0250 ] Parsing partition layout
[ 0.0265 ] tegraparser --pt flash.xml.tmp
[ 0.0281 ]
[ 0.0282 ] Creating list of images to be signed
[ 0.0297 ] tegrahost --chip 0x21 0 --partitionlayout flash.xml.bin --list images_list.xml
[ 0.0371 ]
[ 0.0371 ] Generating signatures
[ 0.0387 ] tegrasign --key None --list images_list.xml --pubkeyhash pub_key.key
[ 0.0405 ] Assuming zero filled SBK key
[ 0.1182 ]
[ 0.1184 ] Generating br-bct
[ 0.1203 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.cfg --chip 0x21 0
[ 0.1217 ] Copying Sdram info from 2 to 3 set
[ 0.1252 ]
[ 0.1253 ] Updating boot device parameters
[ 0.1268 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatedevparam flash.xml.bin
[ 0.1286 ] Warning: No sdram params
[ 0.1291 ]
[ 0.1291 ] Updating bl info
[ 0.1307 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updateblinfo flash.xml.bin --updatesig images_list_signed.xml
[ 0.1335 ]
[ 0.1336 ] Updating secondary storage information into bct
[ 0.1350 ] tegraparser --pt flash.xml.bin --chip 0x21 0 --updatecustinfo P3448_A00_lpddr4_204Mhz_P987.bct
[ 0.1367 ]
[ 0.1368 ] Updating Odmdata
[ 0.1381 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatefields Odmdata =0x94000
[ 0.1394 ] Warning: No sdram params
[ 0.1398 ]
[ 0.1398 ] Get Signed section of bct
[ 0.1416 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --listbct bct_list.xml
[ 0.1432 ]
[ 0.1432 ] Signing BCT
[ 0.1461 ] tegrasign --key None --list bct_list.xml --pubkeyhash pub_key.key
[ 0.1475 ] Assuming zero filled SBK key
[ 0.1487 ]
[ 0.1488 ] Updating BCT with signature
[ 0.1500 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatesig bct_list_signed.xml
[ 0.1518 ]
[ 0.1518 ] Copying signatures
[ 0.1533 ] tegrahost --chip 0x21 0 --partitionlayout flash.xml.bin --updatesig images_list_signed.xml
[ 0.1610 ]
[ 0.1611 ] Updating BFS information on BCT
[ 0.1626 ] tegrabct --bct P3448_A00_lpddr4_204Mhz_P987.bct --chip 0x21 0 --updatebfsinfo flash.xml.bin
[ 0.1643 ]
[ 0.1644 ] Boot Rom communication
[ 0.1659 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml
[ 0.1672 ] BootRom is not running
[ 0.2388 ]
[ 0.2390 ] Sending BCTs
[ 0.2415 ] tegrarcm --download bct P3448_A00_lpddr4_204Mhz_P987.bct
[ 0.2436 ] Applet version 00.01.0000
[ 0.3212 ] Sending bct
[ 0.3214 ] […] 100%
[ 0.4983 ]
[ 0.4984 ] Sending bootloader and pre-requisite binaries
[ 0.5008 ] tegrarcm --download ebt cboot.bin 0 0 --download rp1 tegra210-p3448-0002-p3449-0000-b00.dtb 0
[ 0.5029 ] Applet version 00.01.0000
[ 0.5771 ] Sending ebt
[ 0.5775 ] […] 100%
[ 0.6822 ] Sending rp1
[ 0.6853 ] […] 100%
[ 0.7418 ]
[ 0.7442 ] tegrarcm --boot recovery
[ 0.7454 ] Applet version 00.01.0000
[ 0.8179 ]
[ 0.8180 ] Retrieving storage infomation
[ 0.8204 ] tegrarcm --oem platformdetails storage storage_info.bin
[ 0.8223 ] Applet is not running on device. Continue with Bootloader
[ 639.7939 ]
[ 639.7964 ] tegradevflash --oem platformdetails storage storage_info.bin
[ 639.7984 ] Cboot version 00.01.0000
[ 639.8293 ] Saved platform info in storage_info.bin
[ 639.8302 ]
[ 639.8303 ] Flashing the device
[ 639.8316 ] tegradevflash --pt flash.xml.bin --storageinfo storage_info.bin --create
[ 639.8327 ] Cboot version 00.01.0000
[ 639.8767 ] Writing partition GPT with gpt.bin
[ 639.8774 ] […] 100%
[ 639.8839 ] Writing partition PT with flash.xml.bin
[ 639.9246 ] […] 100%
[ 639.9288 ] Writing partition NVC with nvtboot.bin.encrypt
[ 639.9632 ] […] 100%
[ 639.9800 ] Writing partition NVC_R with nvtboot.bin.encrypt
[ 640.0259 ] […] 100%
[ 640.0477 ] Writing partition TBC with nvtboot_cpu.bin.encrypt
[ 640.0977 ] […] 100%
[ 640.1166 ] Writing partition RP1 with tegra210-p3448-0002-p3449-0000-b00.dtb.encrypt
[ 640.1650 ] […] 100%
[ 640.1882 ] Writing partition EBT with cboot.bin.encrypt
[ 640.2387 ] […] 100%
[ 640.2702 ] Writing partition WB0 with warmboot.bin.encrypt
[ 640.3234 ] […] 100%
[ 640.3402 ] Writing partition BPF with sc7entry-firmware.bin.encrypt
[ 640.3887 ] […] 100%
[ 640.4058 ] Writing partition TOS with tos-mon-only.img.encrypt
[ 640.4545 ] […] 100%
[ 640.4731 ] Writing partition DTB with tegra210-p3448-0002-p3449-0000-b00.dtb.encrypt
[ 640.5226 ] […] 100%
[ 640.5466 ] Writing partition LNX with boot.img.encrypt
[ 640.5971 ] 00000004: Filesize is bigger than partition size
[ 640.6296 ]
Error: Return value 4
Command tegradevflash --pt flash.xml.bin --storageinfo storage_info.bin --create
Failed flashing t210ref.


Who told you to flash your board with this command?

base) sumitrra@sumitrra-N56VZ:~/Linux_for_Tegra$ sudo ./flash.sh p3448-0000-max-spi external

Dear Wayne,

Thanks for your reply, I was having trouble with the internal system, and I was advised to conduct a factory reset on the B01 board. Based on the online source, I was given a link to follow to conduct the reset onto the board. Are you able to advice me on my following steps after I had conduct on the factory reset through Pin 9 and 10, really hope to hear from you soon. Many thanks!

Hi,

Is this emmc module or sdcard module?

Actually, my point is, if you are really new users to all this and you totally don’t know how to use the tool, how about you just reflash your board with sdkmanger?

The purpose of sdkmanager is for newbie to reflash sdkamanger.

Hi Wayne,

The emmc module itself. Currently I have trouble booting the jetson nano module itself, it doesn’t show anything on the display monitor, only a blank screen. Truly sorry for the mistake I have made. Previously, I have got it up running, but factory reset was recommended when the error was not mitigated~

Hi,

Is there any issue to reflash your board with sdkmanager? Do you understand what sdkmanager is trying to do?

Hi,

Are you able to send me a link or a direction for me to follow, cause I fear I might misunderstood the instruction. Thanks.

There is no “factory reset” in jetson but only “recovery mode”. You have to set your board into recovery mode so that sdkmanager or flash.sh is able to flash your jetson.

After flash, if it is done without problem, then your jetson would be able to boot.

Thanks Wayne,

Will give it a go, and get back to you asap when it works. Thanks.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.