You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rpmsg_multi_services does not work on Zephyr. I am using the upstream sources practically unmodified, but added some logging via UART. My board is the Odyssey SOM (STM32MP157C) and I am using the "linux-stm32mp" v5.10 kernel from the meta-st-stm32mp layer. The SOM required some additional patches from meta-st-odyssey and the device tree is also significantly extended for our product. I consulted the original ST device trees (eg. stm32mp157c-dk2-m4-examples.dts) to make sure that everything should be set up correctly for rpmsg. I added this to my device tree - but I guess it doesn't actually do anything:
&m4_rproc {
m4_system_resources {
status = "okay";
};
};
For the kernel, I enabled the following options, according to meta-openamp:
However, a rpmsg_ctrl.ko is not built, apparently because my kernel is too old (or new). But I probed rpmsg_tty, rpmsg_client_sample and rpmsg_char.
I installed rpmsg-utils, but it's not clear what to do with them. The upstream repository meantions udev rules, but these are not included in your Yocto port.
After starting the remote M4 firmware, I see the following in the kernel log:
The rpmsg_multi_services does not work on Zephyr. I am using the upstream sources practically unmodified, but added some logging via UART. My board is the Odyssey SOM (STM32MP157C) and I am using the "linux-stm32mp" v5.10 kernel from the meta-st-stm32mp layer. The SOM required some additional patches from meta-st-odyssey and the device tree is also significantly extended for our product. I consulted the original ST device trees (eg.
stm32mp157c-dk2-m4-examples.dts
) to make sure that everything should be set up correctly for rpmsg. I added this to my device tree - but I guess it doesn't actually do anything:For the kernel, I enabled the following options, according to meta-openamp:
However, a rpmsg_ctrl.ko is not built, apparently because my kernel is too old (or new). But I probed rpmsg_tty, rpmsg_client_sample and rpmsg_char.
I installed rpmsg-utils, but it's not clear what to do with them. The upstream repository meantions udev rules, but these are not included in your Yocto port.
After starting the remote M4 firmware, I see the following in the kernel log:
However, the app itself crashes, as is shown in my Zephyr debug log:
Unfortunately, the coredump cannot be analyzed.
Do you have any clue what's going on here and what I might have missed?
The text was updated successfully, but these errors were encountered: