/dev/ttyRPMSG30 is not created on Torizon OS 7.x for verdin-imx8mp

Technical Support
, ,
2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

Hello! Thank you for reaching out and providing a detailed explanation of your setup and the challenges you are facing with RPMsg device creation on Torizon OS 7.x for the Verdin iMX8M Plus.

You are correct—moving from Torizon OS 6.x to 7.x requires additional considerations for proper RPMsg (/dev/ttyRPMSG30) operation. The issue you described is a known change, and there are concrete steps you can follow to resolve it based on both community feedback and official guidance:

1. Device Tree Overlay Compatibility

The verdin-imx8mp_hmp_overlay.dts overlay is now officially supported on Torizon OS 7.x. Make sure you’re using the version provided with your current toradex_6.6-2.2.x-imx branch of device-tree-overlays, as you already do.
More info – List of overlays for peripherals and add-on products provided by Toradex

2. Required Kernel Arguments

For Torizon OS 7.x, in addition to clk-imx8mp.mcore_booted=1, there are required kernel arguments to prevent Linux from interrupting the M7 core’s operation.
This is described in detail here:
Community discussion – dev-ttyrpmsg30-not-created-in-torizon-os-7-on-verdin-imx8m-plus

Steps:

  1. Edit your tcbuild.yaml kernel arguments section to include:

    kernel:
  arguments:
    - clk-imx8mp.mcore_booted=1
    - m7bootsync=1
    - nohlt

    Note:

    • m7bootsync=1 ensures u-boot doesn’t interfere with M7 boot.
    • nohlt helps prevent power management from stopping the core, which can interfere with remoteproc.

  2. Double-check your device tree and overlays to ensure they do not conflict with remoteproc (you mentioned your custom overlay does not touch this, which is good).

3. Correct Device Tree Branch

You’re already using the recommended toradex_6.6-2.2.x-imx branch for both the Linux kernel and overlays, so there should not be any repository compatibility issue.
See this discussion for confirmation

4. Additional Guidelines

  • Make sure the FreeRTOS firmware for the M7 core is built for Torizon OS 7.x (RAM/firmware placement sometimes changes between OS versions).
  • Double-check that overlays are actually applied (by confirming with dmesg | grep -i overlay or inspecting /proc/cmdline).
  • If you start the M7 core from U-Boot, ensure no conflicting services in Linux attempt to also start it.

Summary

In short, to resolve missing /dev/ttyRPMSG30 on Torizon OS 7.x, add the specified kernel arguments in your tcbuild.yaml, ensure correct overlays, and confirm usage of the proper device tree branches. No further patches or hardware changes are required.

References for further reading:

If you follow these steps, RPMsg should work on Torizon OS 7.x as it did on 6.x.

Please let me know if you need further clarification or run into any issues with these changes!

Best regards,
Toradex AI Assistant.