possible bug when loading rpmsg app on M4

[mhanuel26]

Hello,

I have found a case where this tool partially fail, it was reported while working on this.

When loading an application that uses rpmsg_lite for some reason the M4 code don't run correctly, opposed to what does when loading from start up. To reproduce I am loading example_rpmsg from here Good case
M4 debug output (after reboot with u-boot correctly set)

Hardware initialized                                                
Waiting for master to get ready...                                                                       
...Sending name service announcement to Linux...
Waiting for any messages from Linux...

Wrong case After loading it using sudo ./m4fwloader ./images/rpmsg_mcu_mpu_hello_world.bin 0x007F8000

Hardware initialized                                                
Waiting for master to get ready..........................

the code keeps in this loop.

   while(!rpmsg_lite_is_link_up(my_rpmsg))
    {
       PRINTF(".");
       vTaskDelay(300);
    }

Is this a bug? I would like to know how can I help debug the issue.

[Hadatko]

Hi @mhanuel26, to keep @MarekNovakNXP updated: Did you use kernel module and linux application after you loaded m4 app? (load and run m4 app, modprobe rpmsg kernel module/modules, run Linux application)

[mhanuel26]

Hi @Hadatko,

I will check again taking care of that. But notice that when reboot, M4 get's loaded first with output console of

Hardware initialized                                                
Waiting for master to get ready...                                                                       
...Sending name service announcement to Linux...
Waiting for any messages from Linux...

without any of those kernel modules since they cannot be compile to load by default, only loadable option <M>.

I will double check and report asap.