[email protected] schrieb am Mittwoch, 14. April 2021 um 17:58:31 UTC+2:
> So I looked over the libpruio page and it looks great. My head's spinning > a bit between remoteproc, uio, and libpruio options but I'd like to try > libpruio. > I don't want to break remoteproc if I set up to use libpruio. Will that > happen? > libpruio will never run under rproc, since rproc isn't powerful enough (same issue with maschinekit). Only uio_pruss driver will meet its needs. > Also, I'm running Buster (version.sh) at the bottom of this post > The instructions refer to Jessie. Are the Debian packages referred to > compatible with Buster? Here's what I am referring to. > > The easy way to benefit from *libpruio* is to install the Debian > packages. They're not in mainline, yet. > RobertCNelson started to add the packages in mainline years ago. Ask him why he never finished. For kernel 4.19 you'll have to add a symlink, since a sysfs path changed. (Compiling from source may be a good option.) Start your project by a working example. Then add features step by step. You cannot test your PRU mainloop before you got hardware IO running. 1. install libpruio 2. get pruss_toggle example running 3. add a second output 4. learn to read ADC values in RB mode (first from ARM side, then from PRU) 5. learn to exchange data between ARM and PRU 6. finally put all together in your PRU mainloop (perhaps test on ARM before) Regards -- 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/7f8b9988-b6bf-4ae5-885b-818f1be0664bn%40googlegroups.com.
