Status of apalis-imx8_hmp_overlay.dts

[Florin]

What is the status of apalis-imx8_hmp_overlay.dts. Is it available? If not, how can I enable remoteproc support to upload M4 firmware from Linux?

Thanks,
Florin

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

The context provided does not specify the status of the apalis-imx8_hmp_overlay.dts. However, it mentions that Toradex provides a series of device tree overlays for Heterogeneous Multicore Processing, including the remoteproc framework, and that these overlays are pre-compiled into Torizon OS and BSP reference images. To enable remoteproc support, you would typically enable the related device tree overlay by replacing the appropriate *.dtbo in the overlays.txt file. You can check if it was correctly enabled using dmesg.

If the specific overlay for Apalis iMX8 is not available, you might need to check the Toradex device-tree-overlays.git repository for its source code or contact Toradex support for further assistance.

Please, also check if these links can help you solve your problem:

imx8mq load fimware to m4 from linux

RPMSG Character Device Driver in Torizon Core 6.2

Following on from this thread, I would like to implement an RPMSG communication from the M4 to the Linux userspace and back. /dev/rpmsg_cntrl0 … 3 are present On Linux side: I understand the approach in such a way that via the /dev/rpmsg_ctrlX and ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &ept) a new endpoint is created. this then appears e.g. as /dev/rpmsg0 if I use /dev/rpmsg_ctrl0 I should then be able to read and write to /dev/rpmsg0. When I call: fd = open("/dev/rpmsg_ctrl0", O_RDWR); I ge…

Device Tree Overlays (Linux) | Toradex Developer Center.

[alex.tx]

Please check this thread - Remoteproc for apalis-imx8