"Parsing board information failed" during flash

Hello! I think the EEPROM on one of my Jetson TX2NX’s has died because when I am trying to flash it, I receive this error. When I’m trying to flash other TX2NX’s everything works fine. I would like to know, what does this EEPROM part exactly do and how do I test the EEPROM via userspace or something? Can I force the flash script to ignore EEPROM during flash?

[   2.3320 ] Retrieving EEPROM data
[   2.3324 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/matiss/TX2NX/nvidia_sdk/Linux_for_Tegra/bootloader/cvm.bin
[   2.3367 ] Applet version 01.00.0000
[   2.6144 ] Saved platform info in /home/matiss/TX2NX/nvidia_sdk/Linux_for_Tegra/bootloader/cvm.bin
[   2.7609 ] 
Parsing board information failed.

Is that TX2-NX module still able to boot up? I mean boot into linux.

Yeah, boots up fine.

Please use i2cdump to dump the i2c bus with address 0x50.

I don’t have a TX2-NX now to check which bus is for the module eeprom, you can just scan each bus.

Here’s the dump on i2c-7

I will probe file /dev/i2c-7, address 0x50, mode byte
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 01 00 0d 00 34 0e 01 00 03 48 00 00 00 00 00 00    ?.?.4??.?H......
10: 00 01 00 00 36 39 39 2d 31 33 36 33 36 2d 30 30    .?..699-13636-00
20: 30 31 2d 33 30 30 20 48 2e 30 00 00 00 00 00 00    01-300 H.0......
30: 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
40: ff ff ff ff 44 34 3b 2d b0 48 31 34 32 30 35 32    ....D4;-?H142052
50: 31 30 31 34 36 32 36 00 00 00 00 00 00 00 00 00    1014626.........
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 4e 56 43 42 1c 00 4d 31 00 00    ......NVCB?.M1..
a0: ff ff ff ff ff ff ff ff ff ff ff ff 44 34 3b 2d    ............D4;-
b0: b0 48 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ?H..............
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 af    ...............?

Then looks like the eeprom is still here.

Please go back to flash.sh, dump the uart log when flash.sh gives out error.

I have disabled the UART logs from bootloader as I have a device connected to that UART, so that won’t be an option at the moment.
However, here’s a dump of the EEPROM from different module:

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 01 00 0d 00 34 0e 01 00 03 48 00 00 00 00 00 00    ?.?.4??.?H......
10: 00 01 00 00 36 39 39 2d 31 33 36 33 36 2d 30 30    .?..699-13636-00
20: 30 31 2d 33 30 30 20 48 2e 30 00 00 00 00 00 00    01-300 H.0......
30: 00 00 ff ff ff 34 ff ff ff ff ff ff ff ff ff ff    .....4..........
40: ff ff ff ff ed 33 3b 2d b0 48 31 34 32 30 35 32    ....?3;-?H142052
50: 31 30 31 33 39 39 39 00 00 00 00 00 00 00 00 00    1013999.........
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
90: 00 00 00 00 00 00 4e 56 43 42 1c 00 4d 31 00 00    ......NVCB?.M1..
a0: ff ff ff ff ff ff ff ff ff ff ff ff ed 33 3b 2d    ............?3;-
b0: b0 48 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ?H..............
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0f    ...............?

It is pointless to compare the eeprom between different modules directly.

If you cannot dump flash log, then I cannot help you.

But could you explain - what does exactly .flash.sh do with the EEPROM? I checked in flash.py that there’s this:

chkerr "Reading board information failed.";
	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.";
	fi;

You can try to enable that. Maybe it would pass.

Make it easier to understand, flash script needs eeprom info to know which board is in use.

Okay, right now I tried and it seems commenting it out, the flash works fine? Basically I only have to be sure that I am using correct board as the flash argument. I suppose the SKIP_EEPROM_CHECK is not implemented as an argument yet.

If you skip the eeprom, then you need to give boardid,boardversion,boardsku and boardrevision manually.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.