RPMsg framework Help

[c spengler]

I am trying to get the drivers working for the RPMsg framework. I tried the things in the ST wiki and found that there were no entries in the menuconfig for the RPMsge framework in your yocto kit. I was able to make a bbappend that insinuated a request to build the driver. It turns on CONFIG_RPMSG_CHAR, CONFIG_RPMSG_QCOM_GLINK_RPM, and changes the driver to be built in instead of a module. This allows me to load a firmware into the M4, that works fine. But, it does not create the ttyRPMSGx tty. When I use mknod to create the driver against major device 5 minor 3 it will make the driver entry in /dev but when I try to cat/echo something from or to it fails with a “No such device or address”. I also saw in the ST example there were one or two additional changes in there device tree that are not in your supplied device tree for mcusram and an alias for cm_rproc. Not sure if I should add them.

What I am looking for is a guide to getting the RPMesg framework/tty working under your yocto kit or some idea as to where to go next.

[Eshtaartha Basu]

Hello c spengler,

To help you better, we would need more information about your software build environment. Please provide the version numbers for the following:

1. Which SDK from Octavo Systems are you using?
2. CubeIDE version?
3. CubeFW version?
4. OpenSTLinux Developer Package version?
5. Cube Programmer version?

If you have put together a custom yocto project:
6. U-Boot version?
7. TF-A version?
8. Kernel Version?

[c spengler]

I am using your kit:

meta-octavo-osd32mp1 latest (breakout and red board)

The dunfell  repo distribution is refs/tags/openstlinux-5.10-dunfell-mp1-21-03-31

kernel is 5.10

I am not using Cube in the linux side as far as I know. I am not using an open st linux developer package, I am using the st layers as populated by the above repo command.

ST_OSTL_COMPATIBILTY_VERSION_st-openstlinux = “3.0” Is what the openstlinux layer version indicates.

No cube programmer.

This configuration can pass firmware to the M4 and run it.

 

 

[Eshtaartha Basu]

We carefully reviewed the remoteproc initialization log which was shared previously.

The line “[00000.000][INFO ]Cortex-M4 boot successful with STM32Cube FW version: v1.6.0” indicates that M4 firmware was built using STM32CubeMP1 Firmware v1.6.0. “OSD32MP1-BRK OpenSTLinux | Version: 3.0.1” official image is not compatible with “STM32CubeMP1 Firmware v1.6.0”

Please rebuild the M4 firmware using STM32CubeMP1 Firmware v1.4.0 and try again.
(STM32CubeMP1 FW v1.4.0 – https://github.com/STMicroelectronics/STM32CubeMP1/tree/1.4.0)

We also re-validated the operation of RPMSG framework using “OpenAMP_TTY_echo” project:
STM32CubeMP1-1.4.0/Projects/STM32MP157C-DK2/Applications/OpenAMP/OpenAMP_TTY_echo

Validation screenshot attached.

 

• This reply was modified 2 months, 1 week ago by Eshtaartha Basu.

Attachments:

1. 

   OSD32MP1-BRK-OpenStLinux-v3-0-1-ttyRPMSG-2024-08-26-12-24-12.png
   

[Author]

Posts