Hello, I know I am blowing up your feed here. I found out you are right. CircuitPython must work. >>> https://circuitpython.org/blinka
Seth P.S. Nice! On Monday, March 1, 2021 at 6:47:56 PM UTC-6 donp...@gmail.com wrote: > You prompted me to recheck how I'm accessing the two peripherals I did get > to install, the UART and the I2C. I'm only sending messages out over the > UART using pyserial, although I do also use minicom to bi-directionally > communicate with the board under test from the BBB Ubuntu command line. For > the I2C I'm using the Adafruit char LCD library, which relies on busio from > Circuit Python. Still an Adafruit product, but not technically the BBB_IO > library, I guess. > > If anyone can give tips on how to do a button-based interrupt (abort) > without BBB_IO, I'm all ears. I guess I could just start programming the > BBB in C. I already program embedded microcontrollers in that language, so > why not SBC? > > > -- > Don Pancoe, P.E. > Industrial Designer, Electrical Engineer > DonPancoe.com <http://donpancoe.com/> > > On Mon, Mar 1, 2021 at 4:27 PM set_ <fun...@gmail.com> wrote: > >> Hello, >> >> I literally am havin' the same issue as you right now w/ a GPS module >> working w/ BB-UART2-00A0.dtbo and a grove connector. This is my error: >> >> *py_setup_uart(UART2): set_pin_mode() failed for pin=P9_22Traceback (most >> recent call last):* >> * File "FirstGPS.py", line 5, in <module>* >> * UART.setup("UART2")* >> *ValueError: Set pin mode failed for uart channel.* >> >> I think things are changing at some point in some way at some level. >> Vague...yes. I can set up my source w/out the .dtbo and use config-pin to >> set my uart2 pins to have my source 'work.' >> >> Anyway, I will be following along to see how far you get b/c right now, I >> am a little stumped as to why what has worked no longer is viable. >> >> Seth >> >> On Monday, March 1, 2021 at 12:27:01 PM UTC-6 donp...@gmail.com wrote: >> >>> Hello all, >>> >>> I have a BBB Python application (PCBA test fixture) where I am using >>> libpruio, specifically for access to the eCAP pins. Libpruio requires that >>> the universal cape be disabled, but when I needed a UART and I2C, I was >>> able to add those back in using the existing dtbo files from /lib/firmware >>> (shown below) in my uEnv.txt. >>> >>> uboot_overlay_addr0=/lib/firmware/BB-I2C1-00A0.dtbo >>> uboot_overlay_addr1=/lib/firmware/BB-UART4-00A0.dtbo >>> uboot_overlay_addr2=/lib/firmware/DP-GPIO-PCBATest-00A0.dtbo (I talk >>> about this below) >>> >>> >>> Now I want to add an "abort" button to the test fixture since the >>> technicians have reported it takes a lot of time to reset if the board >>> under test locks up. I expect that wiring a pushbutton to a GPIO with an >>> interrupt is the way to handle this, and I've been thinking that there are >>> two ways to get there. >>> >>> 1. Include another dtbo file to add a single GPIO that I can then >>> access with Adafruit_BBIO (this is where my efforts have focused so >>> far), or >>> 2. Figure out how to work with the hardware-based IRQ of the PRU >>> with libpruio (which I've been avoiding because it looks even more scary) >>> >>> I've tried to make a custom dtbo by following an example from Derek >>> Molloy (github.com/derekmolloy/boneDeviceTree) and while it compiled >>> and booted OK, I still get the following error when I run a simple test >>> program. The same error as when I tried running the program before I >>> created the dtbo. >>> >>> kapsul@beaglebone:~/pyDev$ sudo python3 abortTest.py >>> Traceback (most recent call last): >>> File "abortTest.py", line 6, in <module> >>> GPIO.setup("P9_12", GPIO.IN) >>> ValueError: Set gpio mode failed, missing file or invalid permissions. >>> >>> >>> Further, when I do the following (with or without the dtbo), I get the >>> following... >>> >>> kapsul@beaglebone:~/pyDev$ config-pin -q p9.12 >>> P9_12 pinmux file not found! >>> Cannot read pinmux file: /sys/devices/platform/ocp/ocp*P9_12_pinmux/state >>> >>> >>> Any input would be appreciated, whether it is correcting me on path 1 or >>> steering me towards path 2. I will happily provide any additional info, but >>> I didn't want to start uploading stuff until I know what, exactly, will be >>> helpful. >>> >>> Thanks, >>> -- >>> Don Pancoe, P.E. >>> Industrial Designer, Electrical Engineer >>> DonPancoe.com <http://donpancoe.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...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/58e45b18-f019-49e7-92ce-95015cbc0e63n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beagleboard/58e45b18-f019-49e7-92ce-95015cbc0e63n%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/a48cac86-7e7c-4bd8-8a0e-a14cb700f97dn%40googlegroups.com.
