Sorry for the deleted post I forgot a piece of information... So I'm not exactly sure what modifications I made that fixed my problem because I made a few and somewhere it resolved my issue. I ended up modifying the files listed below. I don't think I had to modify all of them but I figured I would enable the pru_rproc for all variations of device trees that load for future use (whether this is good or bad idk). Uncomment '#include "am33xx-pruss-rproc.dtsi"' in the following files as desired
/opt/source/dtb-4.4-ti/src/arm/am335x-boneblack-overlay.dts /opt/source/dtb-4.4-ti/src/arm/am335x-boneblack-audio.dts /opt/source/dtb-4.4-ti/src/arm/am335x-boneblack-hdmi-overlay.dts /opt/source/dtb-4.4-ti/src/arm/am335x-boneblack-emmc-overlay.dts be sure to run "make" followed by "make install" after making the above modifications. I then modified my uEnv.txt file as follows: Change ##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled: #dtb=am335x-boneblack-overlay.dtb to ##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled: dtb=am335x-boneblack-overlay.dtb this should enable the device tree file "cape-universala-00A0.dts" on boot. The "cape-universala-00A0.dts" has all of the pins pinmuxed and configured for all modes, so it should blow everything wide open for use with config-pin. it worked for all of the pins I wanted to configure. The universal capes can be found (at least for me) at /opt/source/beaglebone-universal-io/ or you can check them out on this github link: https://github.com/cdsteinkuehler/beaglebone-universal-io Doing those 2 things seems to have allowed me to configure any pin I want and starts the pru_rproc on boot ensuring all of the required devices are there to start and stop the PRUs. I ended up not having to mess around with any custom device trees. Hopefully that information helps someone else struggling with the same thing I was. On Sunday, November 20, 2016 at 7:25:06 PM UTC-5, William Hermans wrote: > > On Sun, Nov 20, 2016 at 4:31 PM, Zach B <zbro...@gmail.com <javascript:>> > wrote: > >> Thanks for the information Greg. >> >> Robert & everyone, >> I was digging into that link you sent about which universal overlay gets >> loaded at boot. I have tried modifying my uEnv.txt file to enable different >> overlays but i cant' seem to get config-pin to work for P9_31 and P9_29. It >> responds that config-pin isn't set up for those pins but when I run >> config-pin overlay cape-univversala >> >> it seems to load just fine but when I call either: >> config-pin-q P9_31 >> config-pin P9_31 pruout >> >> it says that it is unable to access the "state" of that pin or set the >> "pinmux". What's the right way to enable config-pin on all of the pins so >> that I can set the PRU pins I need to "pruout"? >> >> Zach >> > > Most likely this is because the universal IO overlay you're loading does > not have those pins muxed. I have run into this myself when working with a > custom cape( physical hardware ). So, I have to create a custom overlay > based on more than one universal IO overlay. Then once I gleaned how the > structure for each pin had to be in the overlay, I modified the overlay > further to only define the exact mux for each pin. That is, removing all > the extra mux modes I did not need. > > So, in short, you're going to have to create your own overlay file based > on multiple universal IO overlays, if you want to use config-pin to mux the > pins. If you just want to use config-pin to load an overlay, then your > overlay does not *have* to be based on a universal IO overlay. > > -- 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/41cefc20-ff0c-49ba-a780-8d25bf4216da%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
