Required Device Tree modifications for RPMSG on Colibri iMX7D 1GB

[ompie]

Hi @hfranco.tx,

Thanks for looking at my post!

@hfranco.tx

The demo you’re trying to run

@ompie

modprobe imx_rpmsg_tty

is not available for the mainline kernel. This implementation comes from NXP (downstream kernel) and they’re not included (or they weren’t accepted) on the mainline kernel.

Instead, the mainline kernel supports a different sample from OpenAMP

I admit I’m a bit confused. I’ve seen several other posts on the forum concerning RPMSG and Torizon (this one and this one for instance) and I did not see any mention of Torizon not supporting RPMSG or using OpenAMP. Although re-reading the post again, I could understand that recompilation is necessary (here so it is probably me that did not read correctly).

@hfranco.tx

So, in order to test this feature, one possibility is to compile OpenAMP demos yourself and enable them on the linux kernel side as well (this will also require TorizonCore to be recompiled with Yocto or, if it’s possible, enable this feature as kernel modules and add them with TorizonCore Builder).

Wow ! I was very glad not having to dive into Yocto when I started working on the Colibri (this is my first Toradex project) because of the already steep learning curve (between pin assignments, device trees, docker and containers plus getting the M4 up and running…).

Is there a way to add the necessary kernel module via Torizon Builder ? If so, can you guide me through this ?

I’m also not sure whether the mentioned modprobe imx_rpmsg_tty is the right module or command to use.
All I’m trying to do is make rpmsg working. So perhaps mentioning modprobe triggered an incorrect understanding on your side (I hope so ).

Best regards,

Jeroen