Hi Bill, I just did something very similar. If you have a working communication channel between PRU and user space anyway (probably RPMsg), you could read the location from the PRU code using:
myvar = resourceTable.shared_mem.pa; and communicate that address to user space using RPMsg. If you're anyway writing a Linux kernel driver, you could also extract the address from the remoteproc driver and expose it, for example, through sysfs, but I don't have a working solution for that. Cheers, Kai Am Montag, 1. April 2019 00:44:27 UTC+2 schrieb Bill M: > > Greetings All, > > TLDR; what is the best way to access PRU remoteproc carveouts from > userspace? > > I have a (working) project for reading an 8-bit parallel interface camera > that I originally wrote using UIOPRUSS. I decided to take the plunge and > work through the remoteproc documentation to see if I could move to that. I > didn't want to use rpmsg, because I doubted it could handle the data > velocity (320 x 240 x 24bit color x 15 frames per second = 3,456,000, > roughly 3MB a second). I discovered carveouts in the resource table > headers, and thought this was excellent since it was much like how I was > already doing it with UIOPRUSS. It works and simplifies the code greatly, > but I have to use debugfs to get the carveout location to mmap to, which > seems less than ideal. What is the best way to expose the carveout to > userspace? Any suggestions appreciated. > > Thanks! > -- 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/f846fa81-9ed6-4c8f-8eff-816db8eb30aa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
