I’m currently trying to set up a little demo that uses rpmsg to communicate between the FreeRTOS and Linux CPUs. I could also run the echo server example, but I couldn’t get the linux example to compile (imx_rpmsg_tty.c « rpmsg « drivers - linux-toradex.git - Linux kernel for Apalis and Colibri modules). My SDK is somehow missing some headers (linux/delay.h, linux/tty_driver.h, linux/tty_flip.h, linux/virtio.h). I compiled it with
bitbake angstrom-lxde-image -c populate_sdk.
This led to some questions I tried to answer by looking into your yocto layers, but I was a bit confused.
First, where are the recipes for the demo applications? I searched in meta-toradex-demos, but couldn’t find them.
Are there any machine configurations or some documentation what the features of the different machines are? Are there more than this 3 images (angstrom-lxde-image, console-tdx-image, angstrom-qt-x11-image)?
Is there more documentation about what the different meta layers do?
Where did you do the linux kernel adaptions for the supported hardware? Is there a similar documentation how to do them as it has without yocto (Device Tree Customization)?