That was it! gpioget gpiochip3 10 worked. Thanks Robert!
On Friday, March 27, 2020 at 9:42:15 AM UTC-6, RobertCNelson wrote: > > On Fri, Mar 27, 2020 at 10:34 AM John Allwine <jo...@allwinedesigns.com > <javascript:>> wrote: > > > > I'm looking into using libgpiod to control the GPIO on the Beaglebone AI > in user space. I'm starting small and trying to use the included command > line tools gpioget and gpioset, but not having any success. > > > > The Beaglebone AI System Manual lists what looks like the gpio chip and > line under pinmux mode 14. P8.19 looks to be gpiochip4 line 10. Am I > reading that right? > > > > I have P8.19 configured in a device tree overlay to be an INPUT_PULLUP, > pinmuxed to mode 14. I have a button wired up to P8.19, which shorts it to > GND. I have verified that the button works using sysfs P8.19 GPIO number is > 106, also listed in the same table from the system manual): > > > > echo 106 > /sys/class/gpio/export > > cat /sys/class/gpio/gpio106/value > > > > The last command outputs 1 when the button is not depressed, 0 when it > is, as expected. I'm unable to use gpioget to see the same results: > > > > gpioget gpiochip4 10 > > > > When I run that, I always get back 0. Any thoughts? > > You can use gpioinfo to dump the whole pin list.. > > sudo gpioinfo > > But, 106 = 3*32 +10 - which should be gpiochip3 10, as long as the > gpio's are linear.. > > You can also run: > > sudo /opt/scripts/device/bone/show-pins.pl > > Which is nicely documented, only using the legacy method.. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- 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/27d5abc0-0292-40ae-8a2f-d4efd2437d35%40googlegroups.com.
