OK, how are these "overlays" set up technically? In my reading, what seems to be operative, is that these overlays are "compiled" with the magical:
dtc compiler (Reference: DTC And Compiling Custom Overlays heading in https://vadl.github.io/beagleboneblack/2016/07/29/setting-up-bbb-gpio ) Now GCC being the only way to actually compile something aside (I will not be budged in this opinion), we have to build this "compiler" so we can process our configuration files such that it performs the required operation to the BBB. I'm assuming we just set up out overlays in the correct fashion and then commit them to the OS with the dtc compiler. I'll document my research into this process here. I need to load it to my BBB, make/build it and then figure out the configuration such that when I'm finished I have a nice constellation of GPIO, UART and I2C pins just the way I want them, and report here. 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/90bbf1b4-f5fc-4226-9424-0fbf548a244c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
