Hi @kayccc , as it stands carrier boards without eeproms should set the cvb eeprom read size to 0 as per Jetson AGX Orin Platform Adaptation and Bring-Up — Jetson Linux Developer Guide documentation otherwise MB1 halts and prevents booting.
My question would be the other way around, if the AGX Orin Devkit could be flashed and used with cvb_eeprom_read_size=0 and what would be the consequences, if any. What wouldn’t work on the Devkit?
Say we wanted to provide the same BSP image with cvb_eeprom_read_size=0 in the dtsi that someone would flash un-modified either on a Devkit or on a custom carrier board that has no eeprom, The custom dtb is later set trough the extlinux.conf file, if the carrier board is actually custom.
Is it safe to use this on the devkit? What would happen at most?