Pretty much sounds correct.  Did you create a file

/etc/modprobe.d/pruss-blacklist.conf

and the single line in this file is:

blacklist uio_pruss

Can you paste in your dts file change?  Here is what I have:
/* pruss: pick one: */

/*
 * /etc/modprobe.d/pruss-blacklist.conf
 *
 * blacklist uio_pruss
 */

#include "am33xx-pruss-rproc.dtsi"

/*
 * /etc/modprobe.d/pruss-blacklist.conf
 *
 * blacklist pruss
 * blacklist pruss_intc
 * blacklist pru-rproc
 */

/* #include "am33xx-pruss-uio.dtsi" */

The above is at this path on my board:

/opt/scripts/tools/dtb-rebuilder/src/arm/am335x-bonegreen.dts

So the only change is to unquote a single line in the file:  #include 
"am33xx-pruss-rproc.dtsi"

I git cloned the dtb-rebuilder into the same directory as the other utility 
scripts.
You ran make and then make install in the dtb-rebuilder directory?

I went through this process again on the latest IOT image and it worked:

https://debian.beagleboard.org/images/bone-debian-8.6-iot-armhf-2016-11-06-4gb.img.xz

On Thursday, November 17, 2016 at 11:56:00 PM UTC-5, Zach B wrote:
>
> So I finally got some time to work with the PRUs again. I still seem to be 
> having some issues with remoteproc. I got the c code for PRU0 to compile 
> and I moved it to /lib/firmware under the correct name. I also followed the 
> steps outlined in the e-linux exercise for enabling remote_proc as well as 
> the steps outlined in greg's PDF. I can't seem to get the remoteproc to 
> activate. Whenever I pole "/sys/bus/platform/devices" the only pru related 
> name I get out is "ocp:pruss@4a300000". The device not showing up also 
> means when I try to echo the enable command to bind I get a "No such 
> device" error.
>
> Any suggestions on how to get remote_proc activated and working? Also the 
> program flow as I understand is the pru code needs to be compiled and 
> placed in /lib/firmware under the correct name. Once the remote_proc is 
> activated once by doing a small device tree alteration I just have to call 
> modprobe pru_rpoc to turn it on. From there I can echo "4a334000.pru0" to 
> the bind folder and the code that was loaded onto the pru when remote_proc 
> was enabled will execute?
>
> Zach
>

-- 
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/00e28144-06ef-4800-9891-a2ddd153be06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to