<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>openamp on toorun.dev</title><link>https://toorun.dev/tags/openamp/</link><description>Recent content in openamp on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 04 Oct 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/openamp/index.xml" rel="self" type="application/rss+xml"/><item><title>RPMsg Between Linux and an MCU: One-Way Messaging, Telemetry, and Request-Response</title><link>https://toorun.dev/posts/rpmsg-linux-mcu-communication-practical-guide/</link><pubDate>Sun, 04 Oct 2026 10:00:00 +0000</pubDate><guid>https://toorun.dev/posts/rpmsg-linux-mcu-communication-practical-guide/</guid><description>RPMsg Between Linux and an MCU: One-Way Messaging, Telemetry, and Request-Response A common embedded design pairs a Linux-capable application processor with an MCU. Linux handles networking, storage, and the user interface; the MCU handles precise sampling, motor control, or other time-sensitive work. RPMsg (Remote Processor Messaging) provides a message channel between the two processors on supported systems.
This guide shows three useful communication patterns:
Linux sends commands to the MCU without expecting a reply.</description></item></channel></rss>