###############################################################################
./tegraflash.py --chip 0x18 --applet “/home/shi/AdscubeTx2/Linux_for_Tegra/bootloader/mb1_recovery_prod.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.0018 ] Generating RCM messages
[ 0.0026 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x18 0 --download rcm /home/shi/AdscubeTx2/Linux_for_Tegra/bootloader/mb1_recovery_prod.bin 0 0
[ 0.0032 ] RCM 0 is saved as rcm_0.rcm
[ 0.0036 ] RCM 1 is saved as rcm_1.rcm
[ 0.0036 ] List of rcm files are saved in rcm_list.xml
[ 0.0036 ]
[ 0.0036 ] Signing RCM messages
[ 0.0042 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0049 ] Assuming zero filled SBK key
[ 0.0073 ]
[ 0.0073 ] Copying signature to RCM mesages
[ 0.0080 ] tegrarcm_v2 --chip 0x18 0 --updatesig rcm_list_signed.xml
[ 0.0089 ]
[ 0.0089 ] Boot Rom communication
[ 0.0096 ] tegrarcm_v2 --chip 0x18 0 --rcm rcm_list_signed.xml --skipuid
[ 0.0103 ] RCM version 0X180001
[ 0.0112 ] Boot Rom communication completed
[ 1.0177 ]
[ 2.0220 ] tegrarcm_v2 --isapplet
[ 2.0249 ] Applet version 01.00.0000
[ 2.0440 ]
[ 2.0447 ] Retrieving EEPROM data
[ 2.0447 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/shi/AdscubeTx2/Linux_for_Tegra/bootloader/cvm.bin
[ 2.0453 ] Applet version 01.00.0000
[ 2.0870 ] Saved platform info in /home/shi/AdscubeTx2/Linux_for_Tegra/bootloader/cvm.bin
[ 2.1611 ]
Board ID(3636) version(301) sku(0001) revision(D.0)
not supported by U-Boot
FYI, that is a TX2. However, it does not distinguish between a recovery mode Jetson and the fully booted Jetson’s virtual devices (the network and mass storage visible on a fully booted Jetson has the same lsusb output).
Note in the “Linux_for_Tegra/” directory files of the name “*.conf”. Remove the “.conf” and those are targets for flash. Pick the right one for your board model, e.g., “jetson-tx2”.
Yes, I was just showing an example of how to find the right target. I did not make that clear. I don’t actually have a TX2 NX (just a TX2, or an Xavier NX), so I don’t actually have the .conf file saved on my system (I’m desperately low on disk space). So I was not sure of the exact file name, I only know the “algorithm” to find the right target name.
Incidentally, if you look at those “.conf” files, you’ll see many are symbolic links (go to “Linux_for_Tegra/” and run command “ls -l *.conf”). Those are common name aliases to files which are based on actual model specifications. Part of that specification is for the SoC (System on a Chip) in combination with the module circuit board, and the other part is the specification for the carrier board. Your TX2 NX has the same SoC as the TX2, but the module is quite different, and thus the configuration file. The carrier board itself is also different, and thus you definitely don’t want to use the plain TX2 configuration. Only the part which is for the SoC would be the same.