Tried both those fixes Robert, no joy. Is it still acceptable practice to symlink am335x-pru1-fw to our .out file?
Google led me to this post: http://e2e.ti.com/support/processors/f/791/t/783113?Linux-AM3358-remoteproc-remoteproc0-Direct-firmware-load-for-tmp-PRU-LED1-out-failed-with-error-2 Where the OP had a fix which involved echo'ing the path of the PRU binary from /lib/firmware into /sys/class/remoteproc/remoteproc2/firmware. I've tried that also... Have things changed in the move to 4.14 and uBoot overlays or should the old ways still work? On Tuesday, 28 May 2019 16:33:54 UTC+1, RobertCNelson wrote: > > On Tue, May 28, 2019 at 10:27 AM Hugh Frater <[email protected] > <javascript:>> wrote: > > > > Does anyone know what the remoteproc error codes are? > > > > pru_rproc doesn't start the pru's at boot time, I assume this is the new > behaviour in 4.14 with the uBoot overlays. I've updated initramfs since > symlinking my binary to /lib/firmware/am335x-pru1-fw, that hasn't helped. > I've done an rmmod/modprobe cycle, that hasn't helped either. > > > > However, I would have expected it to start when I: > > > > debian@beaglebone:/lib/firmware$ sudo echo 'start' > > /sys/class/remoteproc/remoteproc2/state > > -bash: /sys/class/remoteproc/remoteproc2/state: Permission denied > > > > Looking at dmesg, I see: > > > > [22251.654264] remoteproc remoteproc2: powering up 4a338000.pru > > [22251.654353] remoteproc remoteproc2: Direct firmware load for > am335x-pru1-fw failed with error -2 > > [22251.654371] remoteproc remoteproc2: request_firmware failed: -2 > > [22251.665903] remoteproc remoteproc2: Boot failed: -2 > > > > The .out file is built with Ti v2.1.5 compiler under CCS - do I need to > update my pru-software-support-package? > > > > It would be handy if I could figure out what the -2 error code was. > > $ errno 2 > ENOENT 2 No such file or directory > > make sure am335x-pru1-fw is in /lib/firmware/ and the initramfs > > sudo update-initramfs -uk `uname -r` > > 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/166f926e-4671-43f0-9044-d7e03b9c76f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
