2023-06-25 09:02 AM
Hello,
Searched around but couldn't find a similar issue.Please point me to one if one exist. I have a custom board with the stm32mp157c mounted. Board works fine, trying to communication between the m4 and a7 processor using the rpmsg devices. I have the example compiled but when I run it either of the rpmsg0 or 1 devices are present under /dev. If I take a precompiled example of the tty echo it runs fine.
Log from my build
[40144.602678] remoteproc remoteproc0: powering up m4
[40144.612280] remoteproc remoteproc0: Booting fw image OpenAMP_TTY_echo_CM4.elf, size 2367104
[40144.623913] mlahb:m4@10000000#vdev0buffer: assigned reserved memory node vdev0buffer@10042000
[40144.631840] virtio_rpmsg_bus virtio0: rpmsg host is online
[40144.631970] virtio_rpmsg_bus virtio0: creating channel rpmsg-tty addr 0x400
[40144.644298] mlahb:m4@10000000#vdev0buffer: registered virtio0 (type 7)
[40144.650201] remoteproc remoteproc0: remote processor m4 is now up
[40144.656732] virtio_rpmsg_bus virtio0: creating channel rpmsg-tty addr 0x401
Log from the precompiled
[40713.026976] remoteproc remoteproc0: powering up m4
[40713.031634] remoteproc remoteproc0: Booting fw image OpenAMP_TTY_echo.elf, size 217172
[40713.039020] mlahb:m4@10000000#vdev0buffer: assigned reserved memory node vdev0buffer@10042000
[40713.047833] virtio_rpmsg_bus virtio0: creating channel rpmsg-tty-channel addr 0x0
[40713.057806] virtio_rpmsg_bus virtio0: rpmsg host is online
[40713.063787] mlahb:m4@10000000#vdev0buffer: registered virtio0 (type 7)
[40713.070024] rpmsg_tty virtio0.rpmsg-tty-channel.-1.0: new channel: 0x400 -> 0x0 : ttyRPMSG0
[40713.077714] virtio_rpmsg_bus virtio0: creating channel rpmsg-tty-channel addr 0x1
[40713.086064] remoteproc remoteproc0: remote processor m4 is now up
[40713.098384] rpmsg_tty virtio0.rpmsg-tty-channel.-1.1: new channel: 0x401 -> 0x1 : ttyRPMSG1
The example source code is not modified. I am simply trying to first get it to run before making the changes that are needed for my use case.
Not sure where to start digging.
Thanks
2023-06-27 04:51 AM
Hello @mantwih ,
A typical issue that can explain this is a bad alignment between your OSTL version (At the moment I write this message we are at OSTL 4.1) and the CubeFWPackage you use (At the moment I write this message, we are at STM32VCube_FW_MP1_1.6.0).
Can you first double check the version of both your A7 soft and your M4 soft ?
Kind regards,
Erwan.