Hi again,

I have some mature PRU firmware that I've been loading and starting by 
having a program 
<https://github.com/stepleton/cameo/blob/master/aphid/profile.py#L262> 
manipulate the files
  /sys/class/remoteproc/remoteproc[12]/(state|firmware)
well after the system has booted.

I'd like to speed that process up, so today I've finally copied my firmware 
files to /lib/firmware/am335x-pru0-fw and /lib/firmware/am335x-pru1-fw . 
Now, I did do
  sudo update-initramfs -uk `uname -r` ; sudo reboot
like you're supposed to. I can even do
  zcat /boot/initrd.img-4.19.50-ti-r20 | cpio -itv
and see my firmware files inside the file (albeit as 
/usr/lib/firmware/am335x-pru[01]-fw).

When the PocketBeagle boots, the firmware is listed correctly within 
/sys/class/remoteproc/remoteproc?/firmware files, it's just that the 
neighbouring "state" files show that both PRUs are "offline". I can echo 
"start" into those files and things work fine, but as I'm trying to 
accelerate the time from boot to a running system, it would be really nice 
if the firmware could start automatically on boot, as quickly as possible.

I'm using this firmware in concert with a new device tree overlay I've also 
been developing, which is the subject of another thread 
<https://groups.google.com/g/beagleboard/c/Ro2PioeoN-c/m/Cd2d0YRGBAAJ>. If 
you like, you can view it at

http://mg-1.uk:31132/pb-cameo-aphid.dts.txt

Perhaps something is missing in there? I based some of its design off of 
information in https://groups.google.com/g/beagleboard/c/lS8QlNV8JCc , 
which to be fair is now a healthy 3.5 years old...

Thanks for any help,
--Tom

-- 
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/e3580edd-15ab-46f7-aa7c-2d476692ca5cn%40googlegroups.com.

Reply via email to