I’m making a limited use BBB cape, that uses I2C from P9_19/20 and UART from P9_24/26, should I bother putting the EEPROM on there for id? The SRM still says yes, but I think the new style is uboot overlays?
In this case, I know the BBB will always have this cape, and no others, attached. (Software later in the boot process can handle with the case when it’s not really attached).
I know there has been some discussion but the SRM conflicts with that and I can’t remember the conclusion.
I mean, it’s easy enough to put on there but my impression is that it is essentially not used anymore by uboot or the kernel.
I'm making a limited use BBB cape, that uses I2C from P9_19/20 and UART from
P9_24/26, should I bother putting the EEPROM on there for id? The SRM still
says yes, but I think the new style is uboot overlays?
In this case, I know the BBB will always have this cape, and no others,
attached. (Software later in the boot process can handle with the case when
it's not really attached).
I know there has been some discussion but the SRM conflicts with that and I
can't remember the conclusion.
I mean, it's easy enough to put on there but my impression is that it is
essentially not used anymore by uboot or the kernel.
It's really up to you at this point. If you have an eeprom installed,
we will read it in U-Boot and load the proper overlay.
Note: just because U-Boot used those pins as i2c, your overlay could
switch them to can/spi/gpio/etc.
You can see this today with our default images, where P9.19/P9.20
default to i2c, but the other modes are now available in user space
thru config-pin once the kernel takes over:
