Introduction to OpenAMP
summary
OpenAMP provides a concrete stack: libopenamp (rpmsg + remoteproc) on top of libmetal using virtio/remoteproc for shared‑memory messaging and lifecycle control. It ships working reference implementations for Linux userspace, Zephyr and bare‑metal on ARM (A53/R5 families) and powers Xilinx reference designs (remote start and FFT offload). Current limits: virtio is master/slave with no automatic slave recovery, kernel lacks zero‑copy rpmsg, and shared buffer sizes are fixed. Ongoing work targets code‑size reduction, unit tests, more virtio drivers and richer resource APIs.
AI-written summary · about
chapters (14)
- 0:00Introduction to OpenAMP
- 1:56Issues OpenAMP solves
- 4:10OpenAMP standardization
- 5:36OpenAMP libraries
- 7:07Message library overview
- 9:54Message library implementation
- 13:13Remoteproc lifecycle
- 15:28Resource table details
- 15:50Metal library purpose
- 18:09Service layer additions
- 18:54Recent OpenAMP changes
- 20:22Resource-limited support
- 21:07Testing improvements
- 23:02Q&A session
related talks
27mIntroduction to OpenAMP
31mOpenAMP Libmetal Shared Memory Cross OS Interface
22mEnhancing OpenAMP: Making Linux and Zephyr Work Better Together
39mSoftware Defined Hardware on Heterogeneous SoCs Using OpenAMP- 22mEnhancing OpenAMP: Making Linux and Zephyr Work Better Together
20mEnabling the Full Power of a Multiprocessor SoC
25mOpen Source Software Stack for Heterogenous embedded devices
34mZephyr and OpenAMP