EEPROM Use Case on FFC-4P SoM Pro Carrier Board

CalebBergquist

Hi all,

Please excuse my ignorance. I'm attempting to develop a SoM Pro carrier board and want to de-risk any problems of the design from my ignorance.

I noticed in the FFC-4P SoM pro carrier board, there is onboard EEPROM.

And I also noticed on the Som Pro module itself, there is also EEPROM with 32kb.

I chose not to put EEPROM on my som pro carrier board, reasoning that the Som itself has EEPROM, and not wanting to place parts on the board I wouldn't be using. My questions from this decision are:

Is there any mission critical requirement of a Som Pro carrier board needing carrier-board-level EEPROM for the SOM to function properly?
What is the function of the carrier board EEPROM vs the SoM pro EEPROM?

jakaskerl

CalebBergquist
The board EEPROM usually stores the calibration data (so product info, revision, camera calibration, IMU calibration, board configs). If you use our FW, it's very likely you will need it as well - especially if you want to make use of depth.

Thanks,
Jaka

CalebBergquist

Thank you for the info! We do intend to use it for depth.

So if the calibration data is usually stored on the carrier board level EEPROM,

Should I treat the Som Pro module side I2C0 0x50 EEPROM as reserved for revision detect and driver storage, and the 0x50-EEPROM as unwritable for calibration data?
Does the firmware explicitly look to store calibration data at a non-0x50 I2C0 EEPROM address?