How to read/write EEPROM on carrier board from host ,via usb

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

Hi Sir,
Since we have EEPROM on our customized carrier board, we believe that we might need to clone the content of the EEPROM of NV carrier board to ours:

  1. A corrupted EEPROM will make the device fail to boot ?

  2. What data inside EEPROM is mandatory for kernel to boot successfully？

  3. Is there any tool or script to read/write EEPROM(chkbdinfor ? ) in recovery mode ?

Please advise . Thanks.

Jimmy

3

Hi jimmy_ma,

What’s the Jetpack version in use?

Do you mean the EEPROM on the carrier board(CVB) or the one in the module(CVM)?

If you are talking about the EEPROM on the carrier board, it is optional and your board should boot w/o EEPROM connected.

Please share the full flash log for further check.

4

Hi Kevin,
I am using r36.4.3

  1. I mean the EEPROM on the carrier board

  2. Is it easier to do without EEPROM ?
    But it seems that the flashing process will check EEPROM data, like BOARDSKU

  3. Please check the attached log.

Thanks

Jimmy
flash_log.txt (20.4 KB)

5

Flashing process will check the EEPROM of CVM for BoardID, SKU, FAB…etc.

Yes, you can remove the EEPROM on carrier board and refer to the following instruction to update MB2 BCT.
Jetson AGX Orin Platform Adaptation and Bring-Up — NVIDIA Jetson Linux Developer Guide

6

The following command can dump the data in EEPROM data when your board is in force recovery state.

$ ./tegraflash.py --chip "0x23" --applet "/home/KT/NVIDIA/Linux_for_Tegra/bootloader/mb1_t234_prod.bin" --skipuid --cfg readinfo_t234_min_prod.xml --dev_params tegra234-br-bct-diag-boot.dts --device_config tegra234-mb1-bct-device-p3701-0000.dts --misc_config tegra234-mb1-bct-misc-p3701-0000.dts --bins "mb2_applet applet_t234.bin" --minratchet_config tegra234-mb1-bct-ratchet-p3701-0000.dts --cmd "readfuses fuse_t234.bin fuse_t234.xml
7

Hi Kevin,
Thank for the reply.

  1. How to specify CVB or CVM, for dumping the EERPOM data?
  2. Then, how to write a EEPROM image into it , in force recovery state?

Thanks again.

Jimmy

8

Sorry that I’m still not clear about your use case.
Actually, the EEPROM on CVB is not needed for your custom carrier board.
The EEPROM on CVM stores the information of the module like its ID/SKU/FAB..etc.

9

Hi Kevin,
So, the flash process is checking the EEPROM on CVM (like 3701), not carrier board (like 3737) ?

Got it & thanks.

Jimmy

10

Yes, the EEPROM on CVB is optional and you can just remove it.