Hi @cillex!
Thanks for your update!
We could run the RPMsg demo with the following modification on the device tree:
diff --git a/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi b/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi
index 0f62d9cea1f8..1a94c0885f4c 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-verdin.dtsi
@@ -160,6 +160,11 @@ reserved-memory {
#address-cells = <2>;
#size-cells = <2>;
ranges;
+ rtos_ipc_memory_region: ipc-memories@9c800000 {
+ compatible = "shared-dma-pool";
+ reg = <0x00 0x9c800000 0x00 0x00300000>;
+ no-map;
+ };
@rafael.tx found it here: k3-am62x-sk-common.dtsi « ti « dts « boot « arm64 « arch - linux-toradex.git - Linux kernel for Apalis, Colibri and Verdin modules
After applying this modification and running the RPMsg example, seems like the Cortex-M was up and running, but we got several problems reported by Journald.
So the investigation is still ongoing.
Best regards,