Required Device Tree modifications for RPMSG on Colibri iMX7D 1GB

[ompie]

Hi @hfranco.tx,

@hfranco.tx

No luck from my side on the RPMsg yet. I’ve also searched the supported NXP zephyr examples, but they don’t support RPMsg yet, unfortunately. For now, while we still didn’t figure out how to work with RPMSG and mainline, the best approach I believe would be to downgrade the BSP 5 (not TorizoCore) to use the RPMSG with the downstream kernel. Of course, this is also a problem, because you want to use TorizonCore and TorizonCore uses the mainline kernel but that would be a possibility.

That’s a pity. I didn’t expect to be the first one to use RPMSG with TorizonCore 5.x. !
If there is no guaranteed solution in the (very) near future (I’m already very late with the delivery of the project), then the best way to go is BSP 5. I don’t know exactly what this implies yet but if this guarantees that RPMSG will work, then it is the way to go.
Any pointers to articles on the Toradex web site for all that step necessary will be welcome…

@hfranco.tx

This is a possibility, to use the M4 without any OS, however, I believe going with FreeRTOS or another RTOS will guarantee that your tasks are being executed properly and also make the development more scalable. Have you checked if it’s possible to configure your FreeRTOS to overcome this issue?

I did not dive into FreeRTOS configuration yet concerning the issue. But I believe it is linked to the fact that if I give a notification, FreeRTOS has to do some context switching to prepare the notified task for execution. And this all takes place during my interrupt.
Going bare metal is not a problem for me. Most of the projects I do are bare metal. So I have my ideas of how to get this work.

Best regards,
Jeroen