Capturing thoughts: - I'm thinking that there are conceptually two stages to this: (1) configuration (which is loaded by the OS at start-up, which is fine I think for most real applications) and (2) how you actually access the pins from whatever language/environment you are using. - Feeling pretty confident about being able to access via /dev/TTYO1-6 on serial based communication and maybe using a C library for direct GPIO (like digital on/off output/input) access. Wondering if SPI and I2C are serial enough to be able to access them this way. Research will tell.
On Thursday, March 9, 2017 at 5:17:59 AM UTC-7, woody stanford wrote: > > OK, I want to get to the bottom of this whole GPIO issue on the BBB, so > I'm opening up this thread as a "documenter" whereby which I can take notes > based on my research into how you consistently, stably and SOLIDLY > programatically access the GPIO pins on a BBB. I've already done a lot of > the footwork so I'm not entirely unknowledgeable, but I want to get to the > heart of this issue and solve the mental block people have with this. A > private hope. > > Either way, probably a good mess of processed links, articles and > information where you can start. > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/a7076297-08af-4d73-ae77-17c0f98c0bf6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
