I don't mean to start a fight here. You are all providing helpful information. I think I will proceed on one of the following paths.
1. Dig in and understand the GPIO registers. I have seen those in the libpruio docs, but just haven't groked them yet. 2. Failing that, I can use libpruio to read the button during the *customSleep()* function, where it will both call a *break* right there as well as set an *abort* flag to notify any subsequent tests that they should also not execute. 3. And lastly, really dive into the device tree more long-term per Seth's info, because I think that would be useful knowledge for future projects. Thanks, Don -- Don Pancoe, P.E. Industrial Designer, Electrical Engineer DonPancoe.com <http://donpancoe.com/> On Fri, Mar 5, 2021 at 3:48 AM TJF <jeli.freih...@gmail.com> wrote: > > Dennis Bieber schrieb am Donnerstag, 4. März 2021 um 23:41:22 UTC+1: > >> libpruio >> does not seem to support such -- cf: >> https://groups.google.com/g/beagleboard/c/3wphAPs9Uws (which is the >> underlying C level, I doubt the Python interface adds any features) >> > Nonsens! Use > > io.IntcInit > > to configure the interrupt table (IRQ[0-4,6,7]). And mask your event in > the GPIO registers > > LEVELDETECT[0,1] > RISINGDETECT > FALLINGDETECT > > If need be also set the GPIO registers > > DEBOUNCENABLE > DEBOUNCINGTIME > > and then catch (and reset) the new IRQ in a thread. But this isn't worth > the effort! > > As mentioned above, the while loop should get placed in a custom sleep > function. And since the app does nothing in that sleep function, the > abortPIN can get polled fast enough (20 to 100 Hz). > > Dennis Bieber schrieb am Donnerstag, 4. März 2021 um 23:41:22 UTC+1: > >> Non Sequitur: "TJF" is, as I recall, the author of that libpruio package, >> and pushes it as the only solution for everything related to Beaglebone >> GPIO. >> > Nonsens! You can find hundreds of threads here without any pushing. Since > the OP already implemented libpruio for the eCAP feature, why shouldn't he > use further features? > > > -- > 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/bd3d4e00-58e8-4e6d-86df-004e5305b0a2n%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/bd3d4e00-58e8-4e6d-86df-004e5305b0a2n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAP3tSUPDKm2gnhiTH0d5PuutpRBa1TaHhjMQNBJ5-q83GJ6V4A%40mail.gmail.com.
