Monitoring M7 firmware run from u-boot

[mirkoardinghi1]

Hi, I run a M7 firmware from u-boot with the commands:

fatload mmc 1:1 0x48000000 rpmsg_lite_str_echo_rtos.bin;cp.b 0x48000000 0x7e0000 20000
bootaux 0x7e0000

and it works but when I check the status from /sys/class/remoteproc/remoteproc0/state I have "attached" but the M7 is running

Instead when I run M7 from linux the state is "running" as I expected

echo stop > /sys/class/remoteproc/remoteproc0/state
echo rpmsg_lite_str_echo_rtos_imxcm7.elf > /sys/class/remoteproc/remoteproc0/firmware
echo start > /sys/class/remoteproc/remoteproc0/state

Why? I'm using yocto kirkstone with kernel 5.15.71, and I have an imx8mplus.

[AldoG]

Hello,

this is because how the Cortex-M was lunched is different, in case for attached as shown in the remoteproc code:

If the remote processor has been started by an external entity we have no idea of what image it is running. As such simply display a generic string.

Best regards/Saludos,
Aldo.