After i2cset test, nano can't boot in eMMC boot evironment


Hey… why your log shows you are flashing -k LNX ? You should use the full flash command.

Sorry for about that. I mistakenly add -k LNX temporarily.
But I used to run " sudo ./ jetson-nano-emmc mmcblk0p1" all the time.

And “Overriding board information” seems work for me.

Sort out the situation, I did the following steps.

Step 1: uncompress Tegra210_Linux_R32.3.1_aarch64.tbz2

Step 2: uncompress Tegra_Linux_Sample-Root-Filesystem_R32.3.1_aarch64.tbz2

Step 3: run “sudo ./”

Step 4: add BCFFILE to [p3448-0000.conf.common]


BCT="–bct ";

Step 5: add some BOARDINFO to [p3448-0000-emmc.conf]


+BOARDSKU=“0002” ;

source “${LDK_DIR}/p3448-0000.conf.common”;
T21BINARGS="–bins "EBT cboot.bin; "
CMDLINE_ADD=“console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 sdhci_tegra.en_boot_part_access=1”;


Step 6: set Nano to RCM

Step 7: use command “sudo ./ jetson-nano-emmc mmcblk0p1” to flash

Then , entire flash succeeded and confirmed that start up Linux Kernel.

20200703_rel32.3.1_override_UART.txt (27.7 KB)
20200703_rel32.3.1_override_FLASHLOG.txt (22.9 KB)

From the conclusion, in my environment,
・No need to use nvtboot_20190711.tar.gz.
・Need to define BCFFILE.
・Need to override BOARDINFO in Step 5.

There is no way to override eeprom value on host.

Not sure if you notice or not, the source of override BOARDINFO is after i2cset test, nano can't boot - #35 by WayneWWW.

In my understanding,
the board information in EEPROM cannot use due to CRC error,
I think it is necessary to override on the host side.

Thank you for your support.


1 Like

Yes, after system boots up, please use i2cset to modify eeprom to correct checksum value.