Tool/software:
Dear TI team,
I'm currently looking into different means of booting R5f cores on an AM64x.
Depending on the use case we'd like to boot the R5f cores early on (U-Boot), to get them up and running as quickly as possible, but we might also want to boot the R5f cores later when Linux is already running, especially during development.
Up until Processor SDK 10.00 I used to be able to remove the links in /lib/firmware to have the R5f cores come up as "offline". At that point I could modify the remoteproc 'firmware' and 'state' entries at /sys/class/remoteproc/remoteprocX/ to boot the R5f core. The only issue with that approach was that there would be no remoteproc entry for the second core in a cluster.
With Processor SDK 10.01 the remoteproc entries for the R5f cores are completely missing if Linux fails to find a firmware during boot.
- What is the "intended" behavior? Should I be able to boot the R5f cores at runtime? Or is this only supported during boot?
- Is there a known/intentional regression from 10.00 to 10.01?
Best Regards,
Dominic