Zephyr and OpenAMP
summary
Zephyr runs on the Cortex‑R5 core while Embedded Linux runs on the Cortex‑A53 of a Zynq Ultrascale+ MPSoC and Zephyr is loaded from Linux using remoteproc and communicates via rpmsg (virtio + metal underneath). A Zephyr binary is placed in the rootfs, started by echoing to the remoteproc sysfs entry, and an echo test returns successfully; Vitis attaches for source‑level debugging. Common gotchas are missing resource table symbols, incorrect SRAM/DT mappings, and an unconnected mailbox; no throughput benchmarks are reported.
AI-written summary · about
chapters (9)
- 0:00Zephyr and OpenAMP intro
- 2:29Heterogeneous multiprocessor motivation
- 8:29OpenAMP framework overview
- 12:22OpenAMP in Zephyr RTOS
- 15:12Project specifics and hardware
- 18:03Development workflow and debugging
- 22:40OpenAMP issues and fixes
- 26:31Next steps and upstreaming
- 27:14Q&A
related talks
39mAsymmetric/Heterogeneous MultiProcessing (AMP/HMP): Mainline Linux and Zephyr in Unison
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
10mLightning Talk: Using Zephyr to Power the Sustainable Cloud
44mLinux and Zephyr “Talking” to Each Other in the Same SoC
05mZephyr
50mZephyr Project: An RTOS to Change the Face of IoT