> Hello Misc, This is probably a discussion for tech@; anyway:
> I'm trying to get a BeagleBone Black talking onewire and i2c via GPIO to > several off-board ICs through gpioow(4) and gpioiic(4) respectively. As a warning, let me say that tinkering with hardware like this isn't very high on the list of things we support in OpenBSD as it often conflicts with the security goals we have. > I've got the following in /etc/rc.securelevel: > > # Set GPIO pin directions for USR LEDs and give them names > gpioctl gpio1 21 set out USR0 > gpioctl gpio1 22 set out USR1 > gpioctl gpio1 23 set out USR2 > gpioctl gpio1 24 set out USR3 > > # Attach a onewire(4) bus on a gpioow(4) device using 1 GPIO pin > gpioctl gpio1 attach gpioow 29 0x1 > > # Attach a i2c(4) bus on a gpioiic(4) device using 2 GPIO pins > gpioctl gpio2 attach gpioiic 2 0x3 I'm not at all sure how well gpioow(4) and gpioiic(4) work. There are several reasons why it might not: * The omgpio(4) driver or hardware might not support all the pin configurations/states that are required to implement gpioow(4)/gpioiic(4). * The timing accuracy of the raw bit banging that these drivers do isn't good enough. * Your i2c devices live on an address not probed by i2c_scan(). * Your i2c devices are not recognized by i2c_scan(). If you want to get this to work, you'll probably have to start debugging i2c_scan() and onewire_search() to see where things are going wrong. An alternative could be to use the i2c controllers provided by omap to hook up your devices. In that case you'll want to modify the device tree you're using and add your devices to the tree such that they are automatically discovered.
