On 6/3/2016 3:28 PM, William Hermans wrote: > william@beaglebone:~$ ls /dev | grep i2c > i2c-0 > i2c-2 > > So I would imagine i2c-2 was meant instead of i2c-1. > > But if i2c-0 is used for EEPROM also, what is i2c-2 used for ?
I2C2 is used for cape EEPROMs (so the cape manager can auto-detect capes and load the appropriate overlays). It may also be used for I2C expansion depending on the cape(s) installed. It is possible (although a bit tricky) to keep the boot-time cape manager functionality and switch the I2C2 pins to GPIO at runtime by migrating the pinmux control out of the I2C device-tree entry and into something like my Universal Cape overlay, then setting the default mode of the mux to I2C. That way the pins are I2C at startup, then can be switched to GPIO (or any other supported function) at run-time. -- Charles Steinkuehler [email protected] -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/8c5312e7-21b9-81bb-d5f5-b3dfd7394a4f%40steinkuehler.net. For more options, visit https://groups.google.com/d/optout.
