On Fri, Mar 4, 2016 at 10:20 AM, Delbert Martin <[email protected]> wrote:
> I'm having some issues with PRU documentation and information gathering, or
> maybe I'm just reading a lot of stuff wrong.
>
> Help me figure out where I am wrong.
>
> PRU(s) are little embedded processors in the AM335x core.
>
> bone_capemgr allows you to change pinmux functions of the core, to allow
> plug in capes to be detected and set up. and firmware loaded into the
> kernel.
>
> there seems to be a handful of kernel modules relating to the PRUs,
>
> pruss ( pru sub system driver / Allows kernel to interact with PRU? )
> pru_rproc ( PRU Remoteproc system )
> rpmsg_pru ( remote proc message system w/ PRU ) ( this may also be used to
> pass buffers between PRU and kernel ?)
> uio ( UIO allows the IO to be assigned to Device files ?)
> uio_pdrv_genirq ( guessing a UIO/PRU IRQ generator )
>
> Based on what I have read from various Google Searches, the PRUs must be
> enabled, possibly by an Overlay?
> are there any overlays that allow you to just enable the PRU, SANS IO pins,
> just to see if it will run code?
>
> FROM: http://mythopoeic.org/bbb-pru-minimal/
> echo BB-BONE-PRU-01 >/sys/devices/bone_capemgr.9/slots
> which I found is based on the older 3.8 kernels and bone_capemgr has moved
> to /sys/devices/platform/bone_capemgr
>
> from the new https://github.com/beagleboard/bb.org-overlays/
> it gives me a plethora of options in /lib/firmware which all appear to be
> Device Tree Overlays
> based on names I cannot find one like BB-BONE-PRU-01 the closest I can find
> is uio-pruss-enable-00A0

uio-pruss-enable-00A0 is specific to the "4.1.x-bone" kernel's (uio)

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Mainline_.284.1.x_lts.29

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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to