after i2cset test, nano can't boot

i wan’t change mac address, and modify the i2c by command:
i2cset -f -y 2 0x50 0xac 0x3f

now the jetson nano can’t boot, how can fix it?

  1. Does reflash the device help?
  2. Try to write it back from uboot.

Please refer to eeprom layout from download center. Also, could you share the boot log?
It is not common that modify mac addr would cause system not boot.

hi, WayneWWW,
the device can’t enter uboot, External Media

i test anathor new jetson nano and works well.

it seems device halt after poweron (Not yet run the uboot).

How should I debug next? thank you.


Does reflash the board help?

Also, do you see other bootloader log? There is not only u-boot but also c-boot and nvtboot log prior to u-boot.

hi, WayneWWW,

how to reflash the board, Where is the relevant documentation?

it seems the c-boot or nvboot run error, but serial console only show 24 ~ 40 bytes(Every time the content is different).

boot 1st log:
00 F8 BF FE E7 5F 54 BC 91 62 84 A1 20 CB EA 8E 0B 7F 94 FF B5 7E 00 00

boot 2st log:
00 F7 FE 7F F7 FF FF FF F7 FD FB 89 67 4A BD 8C ED 7E 7A 7D F3 D9 BD F7 DB FF 3D E1 00 00

and how can i check c-boot or nvboot status? thank you very much.

hi, WayneWWW,
i’m using the sdkmanager reflash, and inform the result later.


All document is on Jetson Download Center | NVIDIA Developer.

I would suggest you to reflash the sdcard using sdkmanager.(Linux host required)

hi, WayneWWW,
the device failed several times by sdkmanager reflash(anathor device works well),
i upload the log:

you can see the line 2403:

2019-06-14 18:53:08.773 - info: command sudo ./ jetson-nano-qspi-sd mmcblk0p1 finished with error
2019-06-14 18:53:08.773 - info: cmd finished failure SDKM_END_CODE_FAILURE_30eed489-ee33-46b4-982a-87f0e19b606b
2019-06-14 18:53:08.774 - error: command terminated with error
2019-06-14 18:53:08.774 - error: install 'Flash Jetson Nano' failure, command < cd '/home/wyt/nvidia/nvidia_sdk/JetPack_4.2_Linux_P3448' ;

and i run the commands:
cd nvidia_sdk/JetPack_4.2_Linux_P3448/Linux_for_Tegra/
./ jetson-nano-qspi-sd mmcblk0p1

the console show:

External Media

i find the error code at
External Media

can you help do the test command: i2cset -f -y 2 0x50 0xac 0x3f

the e2prom dump to ~/nvidia/nvidia_sdk/JetPack_4.2_Linux_P3448/Linux_for_Tegra/bootloader/cvm.bin


External Media

can i modify the e2prom register in recovery mode? (like linux command i2cset -f -y 2 0x50 0xac 0xC2)


it seems the cboot or nvboot do eeprom checksum, so sdkmanager or boot failed, can i modify the e2prom register in recovery mode?



Can you check by passing board details in flashing and see if flash happens?


FAB=B00 BOARDID=2180 BOARDSKU=400 BOARDREV=E.0 sudo ./ mmcblk0p1

Also comment out these lines in flash script.

    if [ "${SKIP_EEPROM_CHECK}" = "" ]; then

            boardid=`./chkbdinfo -i cvm.bin`;

            boardversion=`./chkbdinfo -f cvm.bin`;

            boardsku=`./chkbdinfo -k cvm.bin`;

            boardrevision=`./chkbdinfo -r cvm.bin`;

            chkerr "Parsing board information failed.";



thanks for your reply, the command also failed, i upload the log here:


hello, can give some tips? thanks.

Could you also share the log of device from UART log?

hi, WayneWWW,

External Media

it’s the log, i looks the cboot or nvboot failed. maybe the eeprom checksum failed,

so, how to modify the eeprom to original value, or skip the eeprom checksum?

thank you~



Is the log from #16 the log during flash?

it’s boot log, about 20~20 hex byte. i think it’s cboot or nvboot output.

What should I do next? thanks.

Please dump the UART log during the flash process.