Problem with RPMSG using modprobe imx_rpmsg_tty communication between the M4 core and A7 Core in IMX7D

Technical Support
, , ,
1

Hi, I am trying the freeRTOS example codes in my iMX7 processor. And I am running the str_echo_free_rtos in M4 core. But the problem is while trying RPmsg from the linux side. I am Following This

root@colibri-imx7-emmc:~# modprobe imx_rpmsg_tty

It returned nothing and I am can able to see the /dev/ttyRPMSG. not accessing the between the both cores.

root@colibri-imx7-emmc:~# uname -a

Linux colibri-imx7-emmc 4.1.44-2.7.4+gb1555bf #1 SMP Wed Oct 4 21:39:05 UTC 2017 armv7l GNU/Linux

From M4 side i am getting this on UARTB

RPMSG String Echo FreeRTOS RTOS API Demo...
RPMSG Init as Remote

Thanks & Regards

Nareshch.

2

Dear @Nareshch,

I did a test 2.8B6 image, rpmsg_str_echo_freertos_example demo is working. Could you try the same and let us know the feedback.

Why do you want to use 2.7.4 image?

I did set
fatload mmc 0:1 0x007f8000 rpmsg_str_echo_freertos_example.bin && bootaux 0x007f8000

root@colibri-imx7-emmc:~# uname -a
Linux colibri-imx7-emmc 4.9.166-2.8.6+gd899927728be #1 SMP Mon Apr 1 13:16:28 UTC 2019 armv7l GNU/Linux

If it is not working on a 2.8B6 image then could you share detailed step by steps instructions what you did on the standard release image to reproduce the issue on our side.

1 Like
3

Dear @Nareshch,

Also, I did a quick test with 2.7 image with the above changes the rpmsg_str_echo_freertos_example is working.

root@colibri-imx7-emmc:~# uname -a
Linux colibri-imx7-emmc 4.1.44-2.7.4+gb1555bf #1 SMP Wed Oct 4 21:39:05 UTC 2017 armv7l GNU/Linux

RPMSG String Echo FreeRTOS RTOS API Demo...
RPMSG Init as Remote
Name service handshake is done, M4 has setup a rpmsg channel [0 ---> 1024]
Get Message From Master Side : "Test" [len : 4]
Get New Line From Master Side
4

Dear @raja.tx
I didn’t set (fatload mmc 0:1 0x007f8000 rpmsg_str_echo_freertos_example.bin && bootaux 0x007f8000)
in My Device without seeting this in My Device RPMSG will work or Not.

5

HI @Nareshch

Is the problem solved now or not?