On 6/24/2016 12:20 PM, Andrew Szymkowiak wrote: > I've got a project going on a Beaglebone Black, where I need the I2C2 pins > (P9-19 and 20) to be timer inputs. So I've commented out the i2c2 entries in > the device tree, and have most things working. But I can't seem to get to > eMMC1 > with this configuration. My theory is that the cape-manager is confused by > not > being able to do the I2C scan for the eeproms on the capes (there are none in > my > setup), so does not continue on to handling the virtual capes. Does anyone > know > how I might get beyond this? (I am using an old, 3.8 kernel, as had different > difficulties trying to get my H/W setup going w/ a 4.1 kernel).
If you can live with the pins being I2C during boot, you can setup a device tree that has the pinmux control for the I2C pins exported to user-space via pinmux-helper, with the default pinmux set to I2C. Then when the system boots, the pins will be in I2C mode, cape-manager will do it's thing, and once everything is up and running you can change the pinmux to turn the pins into timer inputs. -- 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/fb0ebc7a-cc13-ff28-3c30-2e5f907e2f01%40steinkuehler.net. For more options, visit https://groups.google.com/d/optout.
