Ok thanks Robert, Yes, well, some rationale at least from my side as input. After I've checked my options to go for PRU, I found there's both remoteproc and uio. At first glance, I did not like the remoteproc implementation as it appears to be more of an interrupt based approach. I think this is more towards userspace program on the main processor that does not do that much harm, but for the PRU being the opportunity to do hard real time stuff (although not really interrupt based but polling-wise) a somewhat weird concept choice. I've seen an idea to let PRU1 handle the interrupts, and use PRU2 to interact with PRU1 for the real realtime stuff which does sound like a compromise. So my "instinct" for what it's worth was to steer clear of remoteproc and use uio. It fitted my application better as well to have shared memory both accessible to PRU and userspace. As far as I could tell a couple of weeks ago this is not possible with remoteproc. I might be wrong though, but this is how I came to the conclusion to go for uio.
Regards, Maarten On Tuesday, July 19, 2016 at 7:05:33 PM UTC+2, RobertCNelson wrote: > > Hi Joseph, > > On Tue, Jul 19, 2016 at 11:52 AM, Joseph Heller <[email protected] > <javascript:>> wrote: > >> Finally, that worked William (&John &Robert)! I did a small check with an >> LED and am able to with it on/off now via the PRU and uio. >> >> For your consideration, I wonder how you feel like to document this more >> structurally so others can benefit from it? I was offset by some older >> posts on the forum. Next thing I just though about is to make more use of >> the .deb functionality instead of relying on script or instructions. For >> instance uio "conflicts" with remoteproc in reality, but both reside on the >> same sd-card image. Otherwise, I also understood the PRU's are not that >> much used, so maybe it;s not worth the effort to invest in this. >> >> Anyway, thanks again for the help, I'd be glad to inform/post the end >> result of my project somewhere once my time-critical part of c code as >> transferred to the PRU. >> > > So i'm hoping, this will only be short term. I believe everyone at ti, > now has a crystal clear idea of what users want from the pruss interface. > So hopefully this uio/remoteproc will get fixed.. A couple notes on the > script, normally the dtb-rebuilder repo can be found here: > > /opt/source/dtb-4.4-ti/ > > It's just for a few releases, that didn't get cloned properly. > > 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/9ada81cc-b65b-430e-bb6a-291580a892a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
