Following the instructions from that Apr 17 2017 discussion resulted in the
cape manager disabled and no I2C addresses reserved for the capes.
I have not made the changes on recent OS releases, and there have been a
lot of changes in the cape manager, so perhaps best to have Robert comment.
@Graham
Thank you very much for your response. I went back to the (BBB without
reserved I2C
addresses)[https://groups.google.com/forum/?utm_medium=email_source=footer#!searchin/beagleboard/BBB$20without$20reserved$20i2c$20addresses%7Csort:date/beagleboard/NG8cDWuv2Y0/XGzZ3SJIBQAJ]
and
Detailed discussion on Apr 17 2017.
--- Graham
==
On Wed, Oct 31, 2018 at 10:15 AM Graham Haddock
wrote:
> I think there is a detailed discussion as to what is supposed to be inside
> the cape EEPROMs in the
> "BeagleBone Black System Reference Manual"
>
> It looks like there is a live Wiki
I think there is a detailed discussion as to what is supposed to be inside
the cape EEPROMs in the
"BeagleBone Black System Reference Manual"
It looks like there is a live Wiki version at
https://github.com/beagleboard/beaglebone-black/wiki/System-Reference-Manual
But since that address has
@Graham I do have a cape with EEPROM at address 0x57 but the EEPROM is
wiped with nothing on it so I guess that is why the board doesn't populate
that address by default. How can I fix that?
On Tuesday, October 30, 2018 at 11:14:50 PM UTC-4, gra...@flex-radio.com
wrote:
>
> Those addresses at
Those addresses at 0x54-0x57 are reserved by the kernel driver.
Unless you have some capes with those EEPROMS populated, there is nothing
actually there.
--- Graham
==
On Tuesday, October 30, 2018 at 7:01:27 PM UTC-5, MG wrote:
>
> The BeagleBoneBlack comes with an "internal" EEPROM connected
