Firstly:  Thank you very much for your quick reply! So much stuff to keep 
track of!
Zerothly: Your ADC article is simply Amazing! I wish i'd found it sooner!

I am indeed using mailboxes in my PRU code, compiled with ti-cgt-pru_2.1.2 
from code samples in the processor sdk pru-icss-4.0.2 package.

I will look at the package you references and gie it a whirl!

Am I correct in assuming that this is the way of the future ie: everyone 
will not fall-back to UIO and leave me and my code stranded?
To have everything started automatically at boot time I guess I will have 
to create another systemd service right?
 

On Friday, December 16, 2016 at 7:36:17 AM UTC-5, Greg wrote:
>
> You are very close!!!
>
> One thing to try right away is to:
>
> rmmod pru_rproc
>
> and then 
>
> modprobe pru_rproc
>
> I don't think you are removing pru_rproc before re-probing it.
> In my latest Debian image this works, and you don't need to do the bind in 
> addition to this.
> Of course the bind should work as well.
>
> Now, based on the dates you show, you may be using the old Remoteproc 
> framework which uses the mailboxes.
> Look in your code for the PRUs and see if you see the numbers like 58 or 
> 59.
> The new system flags should be like 18 or 19.
>
> If you have the old mailboxes you can convert your code easily enough.  In 
> fact, it will probably be simplified.
> Get the latest PRU Support package and look at the examples directory:
>
> https://git.ti.com/pru-software-support-package
>
> I'm pretty sure if you have the old mailboxes code you will get the 
> behavior you are observing.
>
> Regards,
> Greg
>

-- 
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/50a9cb6a-bdc4-4f80-91a7-92b35bdef818%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to