To end the thread:
My findings:
- In Torizon Core 6.2, the RPMSG_CHAR kernel module is present by default.
- However, in kernel version 5.15.77-6.2.0 there are no rpmsg0 / rpmsg1 nodes in imx8qm.dtsi or imx8-apalis-v1.1.dtsi
- so you can not activate them via a device tree overlay
- i have
added these nodes accordingly
edit the torizon core buildertcbuild.yaml
run the build command - the deploy directly back to the apalis module ran without errors but had no effect. Everything was unchanged there.
- so I searched for the corresponding newly created dtb and dto’s, found them, copied them to the module and lo and behold, I was able to achieve a small success.
Note: the M4_1 runs the NXP SDK rpmsg_lite_str_echo_rtos_imxcm4_m41 example
root@apalis-imx8-07201831:/var/rootdirs/home/torizon# dmesg | grep rpmsg
[ 0.084042] imx rpmsg driver is registered.
[ 1.410736] imx-rpmsg 90000000.rpmsg0: assigned reserved memory node vdevbuffer@90400000
[ 1.446797] virtio_rpmsg_bus virtio0: rpmsg host is online
[ 1.476781] virtio_rpmsg_bus virtio1: rpmsg host is online
[ 1.477272] imx-rpmsg 90100000.rpmsg1: assigned reserved memory node vdevbuffer@90400000
[ 1.478104] virtio_rpmsg_bus virtio2: rpmsg host is online
[ 1.478931] virtio_rpmsg_bus virtio3: rpmsg host is online
[ 1.478960] virtio_rpmsg_bus virtio3: creating channel rpmsg-virtual-tty-channel-1 addr 0x1f
[ 1.479414] virtio_rpmsg_bus virtio2: creating channel rpmsg-i2c-channel addr 0x1
[ 1.479583] i2c-rpmsg virtio2.rpmsg-i2c-channel.-1.1: new channel: 0x400 -> 0x1!
Now I’m looking for an example code for the M4 that fits the rpmsg_char kernel module
That’s a new thread then.
I now consider this problem solved.