On Tue, May 28, 2019 at 10:41 AM Hugh Frater <[email protected]> wrote:
>
> 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?

Take a look at Mark's writeup:

https://markayoder.github.io/PRUCookbook/

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/CAOCHtYjwv84aZKjpKNLF93BStwJVRFhf2zEhmHbe8gJRZ_757w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to