Hi,
We have created our own custom carrier board for the Jetson Nano. We are using the production SOM 3448-0002 (b01). We are having trouble flashing the SOM while plugged into our carrier board.
On the host machine I see the following:
$ sudo ./flash.sh jetson-nano-emmc mmcblk0p1
[sudo] password for dev:
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 6.1
###############################################################################
# Target Board Information:
# Name: jetson-nano-emmc, Board Family: t210ref, SoC: Tegra 210,
# OpMode: production, Boot Authentication: ,
# Disk encryption: disabled ,
###############################################################################
./tegraflash.py --chip 0x21 --applet "/home/dev/projects/jetpack_manuf/jetpack-v1.0.1-j129-manuf/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.0041 ] Generating RCM messages
[ 0.0069 ] tegrarcm --listrcm rcm_list.xml --chip 0x21 0 --download rcm /home/dev/projects/jetpack_manuf/jetpack-v1.0.1-j129-manuf/bootloader/nvtboot_recovery.bin 0 0
[ 0.0086 ] RCM 0 is saved as rcm_0.rcm
[ 0.0099 ] RCM 1 is saved as rcm_1.rcm
[ 0.0100 ] List of rcm files are saved in rcm_list.xml
[ 0.0101 ]
[ 0.0101 ] Signing RCM messages
[ 0.0133 ] tegrasign --key None --list rcm_list.xml --pubkeyhash pub_key.key
[ 0.0154 ] Assuming zero filled SBK key
[ 0.0254 ]
[ 0.0255 ] Copying signature to RCM mesages
[ 0.0273 ] tegrarcm --chip 0x21 0 --updatesig rcm_list_signed.xml
[ 0.0295 ]
[ 0.0295 ] Boot Rom communication
[ 0.0325 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid
[ 0.0340 ] RCM version 0X210001
[ 0.7790 ] Boot Rom communication completed
[ 1.7862 ]
[ 1.7864 ] dump EEPROM info
[ 1.7904 ] tegrarcm --oem platformdetails eeprom /home/dev/projects/jetpack_manuf/jetpack-v1.0.1-j129-manuf/bootloader/cvm.bin
[ 1.7929 ] Applet version 00.01.0000
[ 2.4905 ] Saved platform info in /home/dev/projects/jetpack_manuf/jetpack-v1.0.1-j129-manuf/bootloader/cvm.bin
[ 2.5220 ]
[ 2.5258 ] tegrarcm --reboot recovery
[ 2.5283 ] Applet version 00.01.0000
[ 3.2313 ]
Parsing board information failed.
On the serial output of the device during flashing I see the following:
[0032.804] [L4T TegraBoot] (version ▒▒▒▒)
[0032.808] Processing in recovery mode
[0032.811] A02 Bootrom Patch rev = 1023
[0032.815] Power-up reason: pmc por
[0032.818] Established communication link with host
I analyzed the cvm.bin file that gets generated (by doing “hexdump cvm.bin”) and see that it is showing all 1’s in the file.
We probed the I2C2 interface during a Flash cycle and see no activity.
As another experiment we tried plugging the same SOM into a 4GB jetson nano devkit. All worked well. The cvm.bin file showed meaningful information and the flash process succeeded. We also probed the I2C2 interface on the dev kit during this flash command and saw activity.
I am wondering whether anyone has some suggestions for what might be different on our carrier board. It is almost as if the Flash process isn’t even trying I2C accesses during the flash sequence?
A bit more interesting information: We took a SOM straight from manufacturing and plugged it into our carrier board. This SOM booted right to a Linux shell. We aren’t sure what exactly is running on it but it seems to be some version of “TinyLinux”. From here, we could run an “i2cdump” command on our custom carrier board and successfully read the EEPROM.
So, it seems like the I2C2 interface is sane on our board, but for some reason isn’t accessed properly during a Flash sequence.
Any help would be much appreciated.