Looks like this kind-of works now... dmesg doesn't show any errors, but a /dev entry for rpmsg_pru31 is only created if I manually cycle an rrmod -f pru_rproc, modprobe pru_rproc...
Is this because the pru's are booting before the /dev filesystem kernel modules are loaded? On Thursday, 18 May 2017 15:27:34 UTC+1, RobertCNelson wrote: > > On Thu, May 18, 2017 at 5:54 AM, Hugh Frater <[email protected] > <javascript:>> wrote: > > Despite googling the heck out of this simple problem, I can't find > > anything... > > > > Problem is: > > > > [ 34.358783] remoteproc1: 4a338000.pru1 is available > > [ 34.358802] remoteproc1: Note: remoteproc is still under development > and > > considered experimental. > > [ 34.358811] remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and > > backward compatibility isn't yet guaranteed. > > [ 34.359092] remoteproc1: Direct firmware load for am335x-pru1-fw > failed > > with error -2 > > [ 34.359113] remoteproc1: failed to load am335x-pru1-fw > > [ 34.371827] pru-rproc 4a338000.pru1: booting the PRU core manually > > [ 34.371857] remoteproc1: powering up 4a338000.pru1 > > [ 34.371968] remoteproc1: Direct firmware load for am335x-pru1-fw > failed > > with error -2 > > [ 34.371985] remoteproc1: request_firmware failed: -2 > > [ 34.377200] pru-rproc 4a338000.pru1: rproc_boot failed > > [ 34.493128] remoteproc1: releasing 4a338000.pru1 > > [ 34.493310] pru-rproc: probe of 4a338000.pru1 failed with error -2 > > > > The firmware file is present, it works - I just have to load it manually > > once I've booted with: > > > > sudo rmmod -f pru_rproc > > sudo modprobe pru_rproc > > > > Is there a known issue with enabling the PRU's at boot? > > Thanks for the bug, the firmware wasn't getting copied to the > initramfs, just pushed a fix, and should hit the apt repo shortly: > > > https://github.com/rcn-ee/repos/commit/2922f56ce8ab70771944f7eb99d7fd10f8a52b6a > > > [ 10.478212] ti-pruss 4a300000.pruss: creating PRU cores and other > child platform devices > [ 10.478410] irq: no irq domain found for > /ocp/pruss@4a300000/intc@4a320000 ! > [ 10.499594] irq: no irq domain found for > /ocp/pruss@4a300000/intc@4a320000 ! > [ 10.562246] remoteproc1: 4a338000.pru1 is available > [ 10.599505] pru-rproc 4a338000.pru1: booting the PRU core manually > [ 10.599538] remoteproc1: powering up 4a338000.pru1 > [ 10.599836] remoteproc1: Booting fw image am335x-pru1-fw, size 35392 > [ 10.599913] remoteproc1: remote processor 4a338000.pru1 is now up > [ 10.599951] pru-rproc 4a338000.pru1: PRU rproc node > /ocp/pruss@4a300000/pru1@4a338000 probed successfully > [ 10.602814] remoteproc2: 4a334000.pru0 is available > [ 10.604856] pru-rproc 4a334000.pru0: booting the PRU core manually > [ 10.604883] remoteproc2: powering up 4a334000.pru0 > [ 10.605156] remoteproc2: Booting fw image am335x-pru0-fw, size 36296 > [ 10.605225] remoteproc2: remote processor 4a334000.pru0 is now up > [ 10.605260] pru-rproc 4a334000.pru0: PRU rproc node > /ocp/pruss@4a300000/pru0@4a334000 probed successfully > > 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/39afa0bc-9140-4173-9f0e-fb253867ccfe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
