I currently have all the modules loaded as indicated by the various labs :
root@localhost:~# lsmod
Module Size Used by
rpmsg_pru 3986 0
usb_f_ecm 7925 1
g_ether 3482 0
usb_f_rndis 17792 2 g_ether
u_ether 9321 3 usb_f_ecm,g_ether,usb_f_rndis
libcomposite 39088 3 usb_f_ecm,g_ether,usb_f_rndis
virtio_rpmsg_bus 10643 1 rpmsg_pru
pruss_remoteproc 13127 2
remoteproc 24927 1 pruss_remoteproc
virtio_ring 9675 2 virtio_rpmsg_bus,remoteproc
virtio 4624 2 virtio_rpmsg_bus,remoteproc
omap_serial_rs485 15232 0
I have entries in the PRU (from the devicetree) at:
root@localhost:/sys/firmware/devicetree/base/ocp/pruss@4a300000# ls
#address-cells interrupts phandle ranges ti,hwmods
#size-cells linux,phandle pru@4a334000 reg
compatible name pru@4a338000 reg-names
I could not find an entry for "R31" or any other specific registers as mentioned in the lab (5 & 6).
I'm working in kernel space, for a driver that needs to access the PRU. How do I access the registers and manipulate the PRU via the pruss_remoteproc from within a kernel space driver? I'm not familiar with the remoteproc driver.
I'm using a Beaglebone with a 4.1.13-ti-rt-r77 kernel.
Thanks for any help you can render...
B
