Hi,
One of our customer is using our customized BSP based on nvidia jetson nano stock BSP, and trying to flash the emmc module from a host (Ubuntu 18.04 and 20.04 LTS) using a USB cable.
He is getting below issue while flashing:
$ sudo ./flash.sh jetson-nano-emmc mmcblk0p1
[sudo] kato password
###############################################################################
L4T BSP Information:
R32 , REVISION: 3.1
###############################################################################
Target Board Information:
Name: jetson-nano-emmc, Board Family: t210ref, SoC: Tegra 210,
OpMode: production, Boot Authentication: ,
###############################################################################
./tegraflash.py --chip 0x21 --applet “/home/kk/SSSSSSS/XXXXX-XXXX/xxxxx Nano BSP XX . 020201016/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.0030 ] Generating RCM messages
[ 0.0054 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/kk/SSSSSSS/XXXXX-XXXX/xxxxx Nano BSP XX . 020201016/Linux_for_Tegra/bootloader/nvtboot_recovery.bin 0 0
[ 0.0063 ] RCM 0 is saved as rcm_0.rcm
[ 0.0085 ] RCM 1 is saved as rcm_1.rcm
[ 0.0085 ] List of rcm files are saved in rcm_list.xml
[ 0.0085 ]
[ 0.0085 ] Signing RCM messages
[ 0.0105 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0115 ] Assuming zero filled SBK key
[ 0.0201 ]
[ 0.0201 ] Copying signature to RCM mesages
[ 0.0211 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0225 ]
[ 0.0225 ] Boot Rom communication
[ 0.0234 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid
[ 0.0243 ] RCM version 0X210001
[ 0.0680 ] Boot Rom communication completed
[ 1.0747 ]
[ 1.0748 ] dump EEPROM info
[ 1.0766 ] tegrarcm --oem platformdetails eeprom /home/kk/SSSSSSS/XXXXX-XXXX/xxxxx Nano BSP XX . XXXXXXXX/Linux_for_Tegra/bootloader/cvm.bin
[ 1.0779 ] Applet version 00.01.0000
[ 1.0932 ] Saved platform info in /home/kkk/SSSSSSS/XXXXX-XXXX/xxxxx Nano BSP XX . XXXXXXXX/Linux_for_Tegra/bootloader/cvm.bin
[ 1.1700 ]
Board ID(3448) version(400)
./flash.sh: line 321: Nano: command not found
./flash.sh: line 367: Nano: command not found
./flash.sh: 行 367: Nano:
./flash.sh: 行 321: Nano:
./flash.sh: 行 367: Nano:
./flash.sh: 行 321: Nano:
./flash.sh: 行 321: Nano:
./flash.sh: 行 321: Nano:
./flash.sh: 行 321: Nano:
./flash.sh: 行 344: Nano:
./flash.sh: 行 353: Nano:
./flash.sh: 行 353: Nano:
./flash.sh: 行 353: Nano:
./flash.sh: 行 353: Nano:
./flash.sh: 行 353: Nano:
./flash.sh: 行 353: Nano:
./flash.sh: 行 353: Nano:
./flash.sh: 行 344: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 341: Nano:
./flash.sh: 行 353: Nano:
./flash.sh: 行 344: Nano:
./flash.sh: 450 line: [: too many arguments
copying bootloader(bootloader/t210ref/cboot.bin)…
cp: ‘020201016/Linux_for_Tegra/bootloader/cboot.bin’ is not directpry
failed.
Please help to resolve this issue