Enhancing OpenAMP: Making Linux and Zephyr Work Better Together

on YouTube ↗22m

" summary

Real problem: shared memory appears at different physical addresses on application and DSP cores on NXP i.MX platforms, breaking OpenAMP. Implemented address translation in Zephyr via libmetal callbacks and an optional vendor table, added vendor-specific resource tables to declare firmware-ready signaling behavior, and added vendor handling in the IMX remoteproc callback in Linux. Changes land upstream, solve the ATM/ATLP integration issues, and restore reliable RPMsg/remoteproc startup and shared-memory comms without firmware hacks.

AI-written summary · about

" chapters (6)

1. 0:00Introduction and goals
2. 0:53Agenda and context
3. 1:29Limitations and case study
4. 6:24Enhancements and integration
5. 15:00Conclusion and summary
6. 16:34Questions and answers

" related talks

• 22mEnhancing OpenAMP: Making Linux and Zephyr Work Better TogetherIuliana Prodan · Zephyr Developer Summit 2025
• 29mIntroduction to OpenAMPWendy Liang · Linaro Connect Hong Kong 2018
• 31mOpenAMP Libmetal Shared Memory Cross OS InterfaceWendy Liang · Linaro Connect Bangkok 2019
• 27mIntroduction to OpenAMPEdward Mooring · Linaro Connect Bangkok 2019
• 39mAsymmetric/Heterogeneous MultiProcessing (AMP/HMP): Mainline Linux and Zephyr in UnisonMarcel Ziswiler · Embedded Linux Conference @ Open Source Summit North America 2022
• 34mZephyr and OpenAMPMohammed Billoo · Zephyr Developer Summit @ Embedded Open Source Summit 2024
• 20mEnabling the Full Power of a Multiprocessor SoCJeff Hancock · RISC-V Summit 2019
• 44mLinux and Zephyr “Talking” to Each Other in the Same SoCDiego Sueiro · Open Source Summit Europe & ELC + OpenIoT Summit Europe 2018