I think I know exactly what is wrong. You need to activate the Remoteproc PRU framework. This is no longer active by default. Robert Nelson's script which is available via Github repository will fix the problem.
I have been working on detailed documentation of the entire process to activate the framework and set up the C compiler: https://github.com/Greg-R/pruadc1 More specifically, look at this PDF file: https://github.com/Greg-R/pruadc1/blob/master/doc/PRUADC1latex/PRUADC1.pdf Go to the chapter "Setting Up the Remoteproc PRU and Compiler on the Beaglebone Green". Now, the chapter is not completely finished. I am still seeing a problem with the configuration At boot, the PRU firmwares are not starting correctly. I don't understand why this is. However, you can do this: rmmod pru_rproc and then modprobe pru_rproc The firmwares will start running. More investigation, required, but at least there is some path to getting things working for now. I will do some more work on this later today. Regards, Greg On Tuesday, November 8, 2016 at 11:42:25 AM UTC-5, Zach B wrote: > > I have spent a solid 12 hours trying to get the PRU's on the beaglebone to > work. So far I seem to be completely stuck at the getting the device > overlay to work as well as enabling the remoteproc. I have tried to piece > together all of the information I have found on the internet but it is > either out of date or extremely fragmented. I can't seem to find a current > working example or I hit a wall when following along as said previously. > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/ce0bf666-a685-4e22-adc6-6bab07d7b73d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
