Thanks for the suggestions. Here's what I get when I run show_pins.pl when I use the device tree overlay linked above <https://github.com/PocketNC/BeagleBoard-DeviceTrees/blob/pocketnc-ai-test/src/arm/am5729-beagleboneai-pocketnc-pro.dts#L56> : $ sudo /opt/scripts/device/bone/show-pins.pl | grep "P9.13" P9.13b 160 AB10 e fast rx up gpio6_12 P9.13a 204 C17 f fast rx Driver off
That seems right, but unfortunately I can't seem to properly read from it. When I take out the line that configures P9.13b from my device tree, it also does what would be expected so it seems like I'm configuring my device tree correctly. $ sudo /opt/scripts/device/bone/show-pins.pl | grep P9.13 P9.13b 160 AB10 f fast down Driver off P9.13a 204 C17 f fast rx Driver off Maybe Jason can chime in here. Why is P9.13b not blue in your spreadsheet? Does that mean it's not a usable pin? On Mon, May 11, 2020 at 11:27 PM Jon Morss <jonnym...@gmail.com> wrote: > According to the spreadsheet that Jason sent some time back, P9.13 does > not have the gpio value highlighted in blue but I am not sure what that > really means. However, it seems the pins with a gpio value in blue seem to > work fine, such as P9.12 (gpio5_0). > > https://docs.google.com/spreadsheets/d/1fE-AsDZvJ-bBwzNBj1_sPDrutvEvsmARqFwvbw_HkrE/edit?usp=sharing > > You could check the output of showpins to see what P9.13x is set to: > sudo /opt/scripts/device/bone/show-pins.pl |grep "P9.13" > P9.13b 160 AB10 e fast rx gpio6_12 > P9.13a 204 C17 e fast down > > With P9.12 set, it looks as such: > sudo /opt/scripts/device/bone/show-pins.pl |grep "P9.12" > P9.12 171 B14 e fast rx gpio5_0 > > Also, I do add this in the .dts file: > > cape_pins: cape_pins { > compatible = "gpio-leds"; > pinctrl-names = "default"; > gpios = <&gpio6 12 GPIO_ACTIVE_HIGH>, > <&gpio5 0 GPIO_ACTIVE_HIGH>; > pinctrl-0 = <&cape_pins_default>; > }; > > > Perhaps there is another trick to get P9.13b to work as a GPIO pin. > > Cheers, > > Jon > > > On Monday, May 11, 2020 at 3:25:59 PM UTC-7, John Allwine wrote: >> >> When I manually wire a pull up resistor, I still am not able to detect a >> high signal using the methods I listed, though I can verify with a >> multimeter that P9.13 is high. >> >> On Monday, May 11, 2020 at 3:17:36 PM UTC-6, John Allwine wrote: >>> >>> I'm trying to configure P9.13 on the Beaglebone AI as an input pull up, >>> but am not having any success. In the System Manual >>> <https://github.com/beagleboard/beaglebone-ai/wiki/System-Reference-Manual#p9.11-p9.13> >>> it lists P9.13a as not being bound to a GPIO port, but P9.13b is bound to >>> GPIO6_12. This is the device tree overlay I'm using >>> <https://github.com/PocketNC/BeagleBoard-DeviceTrees/blob/pocketnc-ai-test/src/arm/am5729-beagleboneai-pocketnc-pro.dts#L56> >>> with >>> line 56 showing how I'm attempting to configure P9.13b (and P9.13a the line >>> above it). Am I doing something wrong in my device tree overlay? I've had >>> success configuring many other pins, but P9.13 is giving me trouble for >>> some reason. >>> >>> I'm testing it a couple ways: >>> 1) with sysfs >>> echo 172 > /sys/class/gpio/export >>> cat /sys/class/gpio/gpio172/value >>> >>> 2) with libgpio >>> gpioget gpiochip5 12 >>> >>> Both return a value of 0, when I'd expect it to be 1 (I don't have >>> anything wired to it). Any idea what I'm doing wrong? >>> >> -- > 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/d808c9de-7abd-42bd-ab24-a697fb5f1913%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/d808c9de-7abd-42bd-ab24-a697fb5f1913%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/CAPEK9qZ4XLGMycRbbQEt9YnzRNGcEvy7oPz0p_CD04_dXe7poQ%40mail.gmail.com.