Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
RPMsg Issues in Torizon OS 7.x
Based on the available information, there have been known issues with RPMsg functionality in Torizon OS 7.x that align with what you’re experiencing.
Known Issues and Resolution
There was a regression in Torizon OS 7.x where the /dev/ttyRPMSG30 device was not being created properly (1). This issue was identified and resolved by the Toradex team - there was a small error in the device tree overlay due to changes in the driver in the new kernel version (1).
The overlay has been adjusted and the fix is available in the device tree overlays repository (1). This suggests that the issue you’re experiencing may be related to this known regression rather than requiring the pd_ignore_unused patch mentioned in the NXP community post.
Recommended Troubleshooting Steps
1. Verify Device Tree Overlay Configuration
Ensure you’re using the correct HMP overlay for your module (2):
- For Verdin iMX8M Plus:
verdin-imx8mp_hmp_overlay.dts - For Verdin iMX8M Mini:
verdin-imx8mm_hmp_overlay.dts
2. Check RPMsg Driver Registration
Verify the RPMsg driver is properly registered (2):
# dmesg | grep -i rpmsg
[ 0.045742] imx rpmsg driver is registered.
3. Load the RPMsg TTY Module
After confirming proper driver registration (2):
# sudo modprobe imx_rpmsg_tty
4. Verify Device Creation
Check if the RPMsg devices are created (2):
# ls /dev/ | grep -i rpmsg
rpmsg_ctrl0
ttyRPMSG30
MCUXpresso SDK Considerations
When using updated MCUXpresso SDK versions, ensure you’re following the proper compilation process (3). The memory buffer reservations and resource table configurations must match between the Cortex-M firmware and the Linux device tree overlay (2).
The key memory addresses for RPMsg communication are defined in the MCUXpresso SDK and must align with the device tree overlay configuration (2).
Alternative Communication Methods
If RPMsg continues to cause issues, consider using shared memory communication as an alternative approach (4). This method doesn’t rely on RPMsg drivers and provides direct memory access between cores.
Given your deadline concerns, I’d recommend first updating to the corrected device tree overlay and testing with the standard RPMsg examples before implementing the NXP workaround patch.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.