The problem is common to both boards, one with kernel a few months old, and another newer one:
Older: 4.4.12-ti-r31 Newer: 4.4.27-ti-r62 The older board I have used for many hours of experimentation with the Remoteproc/PRUs, and never had a problem. I never noticed the firmwares were not starting at boot! Looking at dmesg, these lines stand out: [ 4.746736] ti-pruss 4a300000.pruss: creating PRU cores and other child platform devices [ 4.747946] irq: no irq domain found for /ocp/pruss@4a300000/intc@4a320000 ! [ 4.748539] irq: no irq domain found for /ocp/pruss@4a300000/intc@4a320000 ! And then a bunch of lines indicating that the firmwares did not load and start, here are the lines for PRU0: [ 4.796962] remoteproc1: 4a334000.pru0 is available [ 4.796990] remoteproc1: Note: remoteproc is still under development and considered experimental. [ 4.796999] remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed. [ 4.797306] remoteproc1: Direct firmware load for am335x-pru0-fw failed with error -2 [ 4.797326] remoteproc1: failed to load am335x-pru0-fw [ 4.832461] pru-rproc 4a334000.pru0: booting the PRU core manually [ 4.832497] remoteproc1: powering up 4a334000.pru0 [ 4.832614] remoteproc1: Direct firmware load for am335x-pru0-fw failed with error -2 [ 4.832630] remoteproc1: request_firmware failed: -2 [ 4.837857] pru-rproc 4a334000.pru0: rproc_boot failed [ 4.959415] remoteproc1: releasing 4a334000.pru0 [ 4.959590] pru-rproc: probe of 4a334000.pru0 failed with error -2 There was a change a while back from "mailboxes" to system interrupts. Hmmmmm... But even after all of this, the PRUs can be started up using either modprobe pru_rproc, or commands to sysfs: echo "4a334000.pru0" > /sys/bus/platform/drivers/pru-rproc/bind echo "4a338000.pru1" > /sys/bus/platform/drivers/pru-rproc/bind So the above commands could be put in .profile or other start-up sequence, but still would like to root cause the kernel log messages. Regards, Greg -- 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/42ff3c96-7f72-4be4-8a52-9d5911a91886%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
