I’m working with the example from the SDK: SDK_2.9.0_MIMX8QM6xxxFF/…/rpmsg_lite_str_echo_rtos (on the M4 core 0) and I follow step by step what it says on the doc file:
Download the m4 file, do setenv fdt_file ‘fsl-imx8qm-mek-rpmsg.dtb’, save and boot.
Until that all went well, but when I try to load the imx_rpmsg_tty kernel module through “modprobe imx_rpmsg_tty” nothing happens (I’m logged in as root user). If I use lsmod I can see the module, but there’s no /dev/ttyRPMSG. I used insmod imx_rpmsg_tty.ko as well and I had the same result
On the M4 side the only thing I see is “RPMSG String Echo FreeRTOS RTOS API Demo…” and nothing else, so I believe the link between A53 and M4 is not established.
At this point I don’t know if it is a problem on the Linux side or on the M4 side so I’m really confused. Can you give me a hand with this because is a really important feature we need to implement.
Images from linux console
I am almost certain that the NXP MEK device tree won’t work for our boards.
You can use device tree overlays to add the corresponding RPMsg nodes. This answer to another post mentions a working configuration.
I’ll also make sure to try reproducing this and document accordingly.
I fixed the problem, following the guidance on this topic Apalis iMX8QM Rpmsg issue on BSP 5.0.
I’m using Torizon Core Builder to modify the device tree.