Thank you Pierrick, your valuable job did the trick. What I missed was that PRUs need to be explicity started and stopped. I assumed that they just should have been automatically started by kernel.
So: sudo sh -c "echo 'start' > /sys/class/remoteproc/remoteproc1/state" [ 91.626880] remoteproc remoteproc1: powering up 4a334000.pru0 [ 91.636173] remoteproc remoteproc1: Booting fw image am335x-pru0-fw, size 32772 [ 91.636250] remoteproc remoteproc1: remote processor 4a334000.pru0 is now up sudo sh -c "echo 'stop' > /sys/class/remoteproc/remoteproc1/state" [ 100.781202] ti-pruss 4a300000.pruss: unconfigured system_events = 0xffffffffffffffff host_intr = 0x00000001 [ 100.781230] remoteproc remoteproc1: stopped remote processor 4a334000.pru0 This solve the question but I'm not able to confirm that pin toggle example is working because I still need to set pinmux. I think also that your work about data acquisition will be very helpful to me because I have to solve similar problem. Thank you again. Filippo Il giorno sabato 26 maggio 2018 18:03:09 UTC+2, pierric...@gadz.org ha scritto: > > Hi Filippo > How are you trying to toggles the PRUs? I do not have a BBB with me this > weekend but I’ll have a look at it on Monday. > > BTW, I have struggled with PRU too so I’ve wrote this memo: hhttps:// > github.com/PierrickRauby/PRU-RPMsg-Setup-BeagleBoneBlack , hope it can > help you > > Thanks > Pierrick -- 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/90cd87f1-edb4-45fa-869a-e4cb4b8ead13%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
