It's easiest to start off with the uboot overlay setup: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
And configure the pins as PRU pins: http://derekmolloy.ie/gpios-on-the-beaglebone-black-using-device-tree-overlays/ Best, Jaremy Jaremy Creechley creech...@gmail.com το ευαγγελιον On Mon, Sep 10, 2018 at 6:08 AM <mkresid...@gmail.com> wrote: > Hello PRU experts, > > Newcomers like myself struggle getting the PRUs enabled on PocketBeagle. > > (1) I've downloaded the image Debian 9.4 2018-06-17 4GB SD IoT > <http://debian.beagleboard.org/images/bone-debian-9.4-iot-armhf-2018-06-17-4gb.img.xz> > from > website (https://beagleboard.org/latest-images) > > Do we have steps of what to do from this clean installion point, that > would allow me to toggle a GPIO pin using a PRU? > > Many Thanks, > Brijen > > > > On Friday, March 30, 2018 at 9:24:25 PM UTC+1, Jaremy Creechley wrote: >> >> >> I'm working on creating a variant of a Buildroot image using the >> 4.9.82-ti-rt kernel (taken from @RCN's stretch/ sources) and modified to >> use u-boot overlays. The buildroot image works well on the Beaglebone Green >> (with the PRU's loading much quicker than the 4.4.x branch I'd used >> previously using TI's recently modified `/sys/class/remoteproc/` scheme). >> >> The image also boots the PocketBeagle and loads `g_ether` and boots fine. >> However, it does not load the PRU units and only loads `remoteproc0` [the >> omap timer (?)]. There are no `/sys/class/remoteproc/` entries for either >> of the PRU units. The kernel logs don't show anything, no errors, or >> anything regard the PRU units (aside from remoteproc0). >> >> Based on the serial output from the BBG, the U-Boot version correctly >> boots using U-Boot 2018.03. Also, the u-boot based cape manager loads on >> both the BBG and PB boards after some tweaking with the uEnv.txt file. >> Still I have not been able to get remoteproc to load the PRU units. >> >> Does anyone have any suggestions? Do I need to load another cape? I've >> tried setting the 4-9 PRU dtbo in `uEnv.txt` to no avail. >> >> I've been reading through the DTS and DTSI sources in the Linux kernel as >> well as the bb.org-overlays. It seems that the linux in-tree dtsi files for >> the PocketBeagle don't mention the PRUSS hardware units at all. This is in >> contrast to the BBB and BBG which both set the `status` field to "ok" for >> both PRU units. My suspicion based on that is that the PRUSS and remoteproc >> configurations aren't updated for the PB. The bb.org overlay's also do >> not mention the PB at all that I've found. However, it appears that several >> people have the PRU's loading and working on the PB's. Hence my confusion! >> >> Thanks, Jaremy >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/ci_v6wD_exU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/0f4ed650-b692-4e3f-836e-4df02c22d12f%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/0f4ed650-b692-4e3f-836e-4df02c22d12f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAMh_G9vs6thhChrD_i4fOPnhfUMvMtvENV2cYkVRUGJ1Zj9c6A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
