Okay, so based on a discussion on element14 and out of my own curiosity, I am attempting to set a header pin to PWM but I am not having much luck. Looking again at the am5729-beagleboneai-roboticscape.dts as an example, I set P8_23 (gpio22) as follows:
* DRA7XX_CORE_IOPAD(0x3794, PIN_OUTPUT | MUX_MODE10) /* AC8: P8.23: mmc3_dat4.ehrpwm3A - PWM3A */* And then rebuild the .dtb *cd /opt/source/dtb-4.19-ti/ * *make src/arm/am5729-beagleboneai.dtb * *sudo make install * *sudo reboot * If I run the analogInOut.js Cloud9 example, the LED does not turn on. I have to set the pin back to GPIO Mode14 for it to work. Nothing seems to get populated in '/sys/class/pwm' so I suspect I am missing something. Is there an easier way to set this? Cheers, Jon On Thu, Oct 24, 2019 at 10:15 PM jonnymo <[email protected]> wrote: > Huzzah! Using 76 did the trick. There is now light on P9.15 > I guess I missed that the AM57x did not have a gpio0. > > > Thanks a bunch. > > Jon > > On Thu, Oct 24, 2019 at 10:05 AM Jason Kridner <[email protected]> > wrote: > >> On Thu, Oct 24, 2019 at 12:39 PM jonnymo <[email protected]> wrote: >> >>> Oh, duh! I should have caught that missing lib. >>> Okay, so the output of show-pins shows P.15 but it neither shows as up >>> or down. Is this correct? >>> >>> *debian@beaglebone:~$ sudo /opt/scripts/device/bone/show-pins.pl >>> <http://show-pins.pl> | grep "P9.15"* >>> *P9.15 69 AG4 e fast gpio3_12* >>> >>> >>> Also, is the '69' value the gpio number that is used to enable this? >>> Such as : >>> >>> *debian@beaglebone:~$ sudo echo 69 > /sys/class/gpio/export * >>> *debian@beaglebone:~$ sudo echo out > /sys/class/gpio/gpio69/direction * >>> *debian@beaglebone:~$ sudo echo 1 > /sys/class/gpio/gpio69/value* >>> >>> >>> Since this is gpio3_12 I was thinking it was '108' considering the >>> 32x3+12 calculation as with the BB Black. >>> Neither 69 or 108 seems to work though. >>> >> >> There’s no gpio0 on AM57x, so it is 2*32 +12 = 76. >> >> >>> Also, are the failed messages from the version output something to be >>> concerned about? >>> >>> *[ 1.582238] remoteproc remoteproc4: Direct firmware load for >>> dra7-ipu1-fw.xem4 failed with error -2* >>> *[ 1.582247] remoteproc remoteproc4: powering up 58820000.ipu* >>> *[ 1.582322] remoteproc remoteproc4: Direct firmware load for >>> dra7-ipu1-fw.xem4 failed with error -2* >>> *[ 1.582330] remoteproc remoteproc4: request_firmware failed: -2* >>> *[ 1.588375] remoteproc remoteproc5: Direct firmware load for >>> dra7-ipu2-fw.xem4 failed with error -2* >>> *[ 1.588383] remoteproc remoteproc5: powering up 55020000.ipu* >>> *[ 1.588455] remoteproc remoteproc5: Direct firmware load for >>> dra7-ipu2-fw.xem4 failed with error -2* >>> *[ 1.588463] remoteproc remoteproc5: request_firmware failed: -2* >>> *[ 1.594532] remoteproc remoteproc6: Direct firmware load for >>> dra7-dsp1-fw.xe66 failed with error -2* >>> *[ 1.594542] remoteproc remoteproc6: powering up 40800000.dsp* >>> *[ 1.594630] remoteproc remoteproc6: Direct firmware load for >>> dra7-dsp1-fw.xe66 failed with error -2* >>> *[ 1.594639] remoteproc remoteproc6: request_firmware failed: -2* >>> *[ 1.600688] remoteproc remoteproc7: Direct firmware load for >>> dra7-dsp2-fw.xe66 failed with error -2* >>> *[ 1.600697] remoteproc remoteproc7: powering up 41000000.dsp* >>> *[ 1.600770] remoteproc remoteproc7: Direct firmware load for >>> dra7-dsp2-fw.xe66 failed with error -2* >>> *[ 1.600777] remoteproc remoteproc7: request_firmware failed: -2* >>> *dmesg | grep pru* >>> >>> >>> >>> Thanks, >>> >>> Jon >>> >>> On Thu, Oct 24, 2019 at 8:24 AM Robert Nelson <[email protected]> >>> wrote: >>> >>>> On Thu, Oct 24, 2019 at 10:12 AM Jon Morss <[email protected]> wrote: >>>> > >>>> > Hi, >>>> > >>>> > I've been trying to configure a header gpio pin such as P9_15 as an >>>> output port on the BBAI but I am having no luck. This pin is used with the >>>> Cloud9 Python and JS examples but it is not working so I have tried to >>>> enable it manually. >>>> > >>>> > I've added the following in the am5729-beagleboneai.dts file and run >>>> make and make install and a reboot: >>>> > >>>> > cape_pins: cape_pins { >>>> > compatible = "gpio-leds"; >>>> > pinctrl-names = "default"; >>>> > gpios = <&gpio3 12 GPIO_ACTIVE_HIGH>; >>>> > pinctrl-0 = <&cape_pins_default>; >>>> > }; >>>> > >>>> > >>>> > >>>> > DRA7XX_CORE_IOPAD(0x3514, PIN_OUTPUT | MUX_MODE14) /* AG4: P9.15: >>>> vin1a_d8.gpio3_12 - MDIR2A */ >>>> >>>> ^ looks correct.. >>>> >>>> >>>> > The config-pins tools shows >>>> > >>>> > debian@beaglebone:~$ sudo config-pin -q p9.15 >>>> > [sudo] password for debian: >>>> > P9_15 pinmux file not found! >>>> > Pin has no cape: P9_15 >>>> >>>> Don't use config-pin the bbai.. >>>> >>>> > The show-pins tools shows: >>>> > >>>> > debian@beaglebone:~$ sudo /opt/scripts/device/bone/show-pins.pl >>>> > Can't locate Inline/Files.pm in @INC (you may need to install the >>>> Inline::Files module) (@INC contains: /etc/perl >>>> /usr/local/lib/arm-linux-gnueabihf/perl/5.24.1 /usr/local/share/perl/5.24.1 >>>> /usr/lib/arm-linux-gnueabihf/perl5/5.24 /usr/share/perl5 >>>> /usr/lib/arm-linux-gnueabihf/perl/5.24 /usr/share/perl/5.24 >>>> /usr/local/lib/site_perl /usr/lib/arm-linux-gnueabihf/perl-base) at >>>> /opt/scripts/device/bone/show-pins.pl line 11. >>>> > BEGIN failed--compilation aborted at /opt/scripts/device/bone/ >>>> show-pins.pl line 11. >>>> >>>> sudo apt install libinline-files-perl >>>> >>>> >>>> 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 [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYiApGknihWCTdh5B0Fz75pOTkqoA4Ka%2BN0OUxCH8V5iWw%40mail.gmail.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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/CAG99bkpE-gX9PjaOwqXJ6K0wZMsikQaVWNNGiOFv3Bi1i11fuA%40mail.gmail.com >>> <https://groups.google.com/d/msgid/beagleboard/CAG99bkpE-gX9PjaOwqXJ6K0wZMsikQaVWNNGiOFv3Bi1i11fuA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> https://beagleboard.org/about - a 501c3 non-profit educating around open >> hardware computing >> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPkGupqvGg%2BapMXHDWQ1sgBOSR9woOt2R7Y81WSxeW7%3D4w%40mail.gmail.com >> <https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPkGupqvGg%2BapMXHDWQ1sgBOSR9woOt2R7Y81WSxeW7%3D4w%40mail.gmail.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAG99bkpg847d-n3om-eQVUn03rhMOCY8v7vWbLxX%2BzETXWy0Ug%40mail.gmail.com.
