On Fri, Feb 17, 2017 at 2:07 AM, William Hermans <yyrk...@gmail.com> wrote:
> It's been my experience that if you're running 4.x kernel it's best not > to use config-pin at all. For simple GPIO it works ok most of the time. But > for more complex configurations it may not work all that well. There is at > least one GPIO( P9.27 I think ) that won't properly display it's high / low > value despite the pin being physically changed. This has been confirmed on > our hardware here. This, can be a game changer if you need to monitor the > pin states, and you need this pin. > Actually this seem to only happen on Beaglebone greens. I have not been able to duplicate this on any of our Beaglebone blacks. > > My buddy uses a simple yet long winded bash script to test our hardware, > and that works well for him. So it wouldn't be too much of a stretch to > imagine running a systemd service that calls a bash script that in turn > configures the pins via config-pin. > > Faster still would be to write your own device tree overlays, and load > them via uEnv.txt at boot. This has the benefit of loading the pins very > early ( in the initrd just a few seconds after boot ) > > Experimental versions of uboot can even load overlays the fastest, but > multiple overlay loading seems a bit glitched the last time I tested( a > couple months ago ). > > The last tow options here of course having nothing to do with config-pin / > universal IO. > > On Thu, Feb 16, 2017 at 9:00 PM, Drew Fustini <pdp7p...@gmail.com> wrote: > >> Anyone have a favorite way to run config-pin after a BeagleBone boots up? >> >> >> Background: >> this question came up in this thread on the Adafruit forum where a BBGW >> boots with 4.4 ti kernel and univ-all-00A0.dtbo: >> >> "Re: Green Wireless + DHT22 = not working?" >> https://forums.adafruit.com/viewtopic.php?f=49&t=111784#p559251 >> >> >> thanks, >> drew >> >> -- >> 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/ms >> gid/beagleboard/62afcae0-3fcb-441e-8292-1f39b9b2c8a7%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/62afcae0-3fcb-441e-8292-1f39b9b2c8a7%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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/CALHSORoRREZ1zvRO4MYt9_bQfHSsWW7cqF1sf8r5nrfcr5SNDw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
