OK status report, where I'm at is the dtc compiler I was talking about seems only to be buildable with a Debian-style installer, which is a deal-breaker for me because I use stock Angstrom.
Found another overlay compiler by Pantelis Antoniou, but this one doesn't appear to work either because of a missing *.h file on make (however it appears more promising because of its more traditional C structure). I think a little more work on that would be Also remember when compiling on MinGW that the make command is "mingw32-make" not "make". However it seems to partially build with that header file problem. (what are you compiling it on MinGW for...its just where I evaluate stuff before committing to a given library/program). Got some datasheets to look at. Interestingly enough, the datasheet for the Sitara presents their design a little differently as BBB which is interesting. I'll be back. 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/4ce36720-e324-473e-915a-046df47bd3b5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
