Thoughts I want to capture (for later discussion): - working theory: I want to be able to access my communication pins (my SPI, I2C, and UART serial) stuff through TTYO1 thru 6 so I can use streams (a la fopen() in C ) so I have some /dev/ abstraction insulating me from a lot of platform and cross-compilation issues.
- I really need to learn python so I can talk more intelligently on how these ideas relate to python. - apparently there are three accepted ways of configuring these pins: overlays, the uEnv.txt file (Q: are the overlay names loaded there just the .dts filenames minus the 00A0.dts suffix...kinda looks like) and the config-pin utility. Still have questions in my mind as to how they all work together to configure the board. 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/3d36f5fc-3485-41e4-b704-f5eab00943e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
