I’m trying to incorporate my Jetson nano (P3448) from board (P3541) [though I’m not using the development board] into a kubernetes cluster based on the turingpi motherboard. I’ve managed to get two Jetson TX2 NX boards up and running, but with the nano I’m stuck. I tried reformatting by download the image and flashing the SD card. That worked up to the point I tried to update it when running, and after that got a consistent error. Various online posts suggested using the nvidia SDK manager - flashing that way got stuck at 99%. One of the posts here suggested I might be using the wrong board configuration, so I repeatedly tried the base board, the development board and the 2G development board. Same result.
A post with a very similar title to this one, closed several years ago, suggested directly using the flash.sh function in the SDK tools directory. I tried that, with pretty much every variation on the theme. The results, every time, is the same:
/nvidia/nvidia_sdk/JetPack_4.6.3_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra$ sudo ./flash.sh $‘jetson-nano-qspi’ mmcblk0p1
###############################################################################
L4T BSP Information:
R32 , REVISION: 7.3
###############################################################################
Target Board Information:
Name: jetson-nano-qspi, Board Family: t210ref, SoC: Tegra 210,
OpMode: production, Boot Authentication: ,
Disk encryption: disabled ,
###############################################################################
./tegraflash.py --chip 0x21 --applet “/home/ubuntu/nvidia/nvidia_sdk/JetPack_4.6.3_Linux_JETSON_NANO_TARGETS/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.0007 ] Generating RCM messages
[ 0.0024 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/ubuntu/nvidia/nvidia_sdk/JetPack_4.6.3_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra/bootloader/nvtboot_recovery.bin 0 0
[ 0.0028 ] RCM 0 is saved as rcm_0.rcm
[ 0.0032 ] RCM 1 is saved as rcm_1.rcm
[ 0.0032 ] List of rcm files are saved in rcm_list.xml
[ 0.0032 ]
[ 0.0032 ] Signing RCM messages
[ 0.0047 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0051 ] Assuming zero filled SBK key
[ 0.0104 ]
[ 0.0104 ] Copying signature to RCM mesages
[ 0.0119 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0127 ]
[ 0.0127 ] Boot Rom communication
[ 0.0143 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid
[ 0.0148 ] RCM version 0X210001
According to the prior post, this process should take maybe 10 minutes, longer on a slow host (which this is not). Nothing else happened after 2 hours. Bad board?