Hi, we are flashing our custom board using nano. But there is one module that always flash failed. Testing other module and flash is ok,
so we think its OEM issue. And we send this module back to them. But they can flash the module correctlly in their board.
Here is our flash log
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 7.3
###############################################################################
# Target Board Information:
# Name: uih_dtcb, Board Family: t210ref, SoC: Tegra 210,
# OpMode: production, Boot Authentication: ,
# Disk encryption: disabled ,
###############################################################################
./tegraflash.py --chip 0x21 --applet "/home/dl/Documents/chaofeng/dtcb/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.0099 ] Generating RCM messages
[ 0.0151 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/dl/Documents/chaofeng/dtcb/Linux_for_Tegra/bootloader/nvtboot_recovery.bin 0 0
[ 0.0186 ] RCM 0 is saved as rcm_0.rcm
[ 0.0202 ] RCM 1 is saved as rcm_1.rcm
[ 0.0203 ] List of rcm files are saved in rcm_list.xml
[ 0.0203 ]
[ 0.0204 ] Signing RCM messages
[ 0.0261 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0298 ] Assuming zero filled SBK key
[ 0.0506 ]
[ 0.0507 ] Copying signature to RCM mesages
[ 0.0571 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0629 ]
[ 0.0631 ] Boot Rom communication
[ 0.0686 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid
[ 0.0722 ] RCM version 0X210001
[ 0.1191 ] Bootrom returned error 4
[ 0.1522 ] Boot Rom communication failed
[ 0.1522 ]
Error: Return value 4
Command tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid
Reading board information failed.
Do you have any help about this?
thanks