2025-01-21 02:04 AM
Hi,
Migrating to STs ecosystem v.5.1.0 from v.3 right now and having an issue with M4 where remoteproc is unable to attach to running M4 and consequently fails. From what I can see in the logs there is a timeout while waiting for the resources, in fact only m4_dma2 becomes available (see attached log dyndbg.txt).
I am following this guide How to assign an internal peripheral to an execution context - stm32mpu to configure DT files (see attached DT.txt). As you can see all corresponding soc peripherals have been disabled and all m4_ peripherals enabled, but for some reason only dma2 gets probed. What am I missing here?
Thanks!