About the behavior when using Carrier Board without EEPROM

Hi, community.

I’m using the Verdin SoM(imx8mp Quad 4GB with wifi/BT) and Verdin Development board(carrier board). Currently Toradex reference image for yocto project is working in these boards.
However, there’s one thing that bothers me.

No matter what a carrier board does not have a EEPROM, does U-boot work well ?
(provided that, use the same reference image)

U-Boot 2020.04-5.3.0-devel+git.2e5818d88ee0 (Jan 01 1970 - 00:00:00 +0000)

CPU: i.MX8MP[8] rev1.1 1600 MHz (running at 1200 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 44C
Reset cause: POR
DRAM: 4 GiB
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC… OK
In: serial
Out: serial
Err: serial
Model: Toradex Verdin iMX8M Plus Quad 4GB Wi-Fi / BT IT V1.0B, Serial# 06849095
Carrier: ??

Best regards, Takeo.

Hi again Takeo san,

Let me double check but I’m 99% sure that the important values related to the device tree and other boot related variables are always stored on the module’s eMMC, not in the CB’s so it should be fine without it.

I will update the question with the HQ information. Please wait a little longer.

Alvaro.

Hi alvaro-san,

Thank you for support again.
Please let me know if you get an answer from HQ.
I wish the same reference image could be used as it is.

Best regards, Takeo.

Hi Takeo san, I have an update in the usage of the EEPROM in Verdin Carrier Board.

This EEPROM memory in CBs helps for auto-detection to load proper device trees/overlays, however, you should also be able to statically define this without further issue (or not define it at all). Definitely, it is not needed for any critical functionality and you can simply not have this in your carrier board.

Kind regards,
Alvaro.