I've been testing my apps/capes with a couple of the SanCloud BBE devices to see how they work and did run into a little problem. I contacted SanCloud and they confirmed that P8-10 on the BBE is a "no connect". This is documented on their web site (see pin mapping section of https://www.sancloud.co.uk/?page_id=254 ) but I completely missed it.
In any case, cape-universal and such still shows the pin as configurable and config-pin and such can be used to set the pin as gpio out and such. Is still appears in /sys/class/gpio/. Etc... It just doesn't work as it's a no-connect. The question is: should the device tree or whatever remove that pin on the BBE? For me, it was confusing as, from the OS level, it looks like it should work and it looks like I can configure it and use it, but then it didn't work. However, on the flip side, my C++ code would have crashed (poor programming on my side) if the stuff in /sys wasn't there as I kind of assumed on the BBB's that it's there. I can definitely update my code (working on that), but the question does remain: should the devices that cannot work exist in the tree? -- 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/5306bb34-c70a-430f-8d73-634adae403d6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
