Populated with notes from today:

• Is 1^st half of November still looking good for a demo? Still looking OK
• November demo:
• What to convey? OpenAMP has demos & docs. It’s easy to try on virtual platform or these 2 low-cost reference platforms. Building from upstream/soon-to-be-upstream, without need to install vendor SDKs.
• What should it include?
• Arnaud’s demo on ST platform based on Linux & Zephyr (with some extra patches on top of Zephyr to extend the sample).  If using upstream Linux (6.0?) & Zephyr, can demo rpmsg tty & rpmsg char.
• https://github.com/OpenAMP/openamp-system-reference/wiki/Samples-and-demos#Demos
• KV260 starter kit: Not sure if decoupling flow will be in upcoming release.  Can do with upstream kernel.
• Remoteproc & rpmsg patches (hopefully those get into next tree by Nov…)
• Upstream kernel
• FW can be pre-built binaries
• Lockstep mode, 2 FW for split-mode, print to UART
• Try for: System DT + Lopper plug-in to build RPU FW, Linux DT.  TBD if this is a separate demo, or integrated.
• KV260 with Zephyr (Felipe’s work)
• Xilinx QEMU
• Same as KV260 demo: Lockstep mode, 2 FW for split-mode, print to UART
• Hypervisorless demo with minimal Zephyr code, in the new OpenAMP structure
• What should the presentation include? See below
• What work needs to happen to support that? Continue that discussion over email (see Work Breakdown task categories below) & in next call.  Please give feedback on the task categories & what you would populate in those categories.
• Individual updates
• How do we look against original project goals?

Who is our target audience?

Spring demo: Hypervisor vendor/projects

Target audience	All	System architect	Embedded open source developer	RTOS / Operating system project	Semi vendor
How could they benefit from OpenAMP?	Minimizes development for IPC. Community-maintained project. Common architecture across semi vendors & OSes.	See all	Avoiding vendor kernel, SDK, FW. Able to use upstream.	Standardized way to connect in heterogeneous systems with other OSes. Option to re-use OpenAMP library (not RTOS-specific). Modular: Can use parts or all of the OpenAMP library (e.g. remoteproc, virtio w/o RPMsg).	Community-driven standard to connect your heterogeneous cores.
What is their alternative to OpenAMP?	Ad-hoc solutions. NXP RPMsg lite solution for systems with low memory for MCU-MCU communication.			Per-RTOS solution	Per-Semi solution

Webinar plan

• What is expected state of audience coming into the webinar?
• Audience will know about embedded AMP.
• Can point to elevator pitch slides in the invitation, so they may have read those.
• What is desired state of the audience after viewing the webinar?
• Will understand the benefits of OpenAMP & want to try out the demos for themselves.
• They will feel confident about the maturity of the project (compatibility w/ Zephyr & Linux upstreams)
• What are the sections of the webinar?
• Intro (Why OpenAMP slides) + what’s in today’s demo
• System DT Intro
• Roadmap, current status, near-future
• Demos (Order TBD), make sure to cover:
• RPMsg-focused on QEMU Xilinx & HW (live, pre-recorded?)
• Co-processor attachment on ST HW + RPMsg
• Virtio
• System DT
• CTA:
• Try it out, here’s where to find the stuff & how to give feedback
• Summary of takeaways/Conclusion
• You can get involved today & here’s how
• Repeat benefits from elevator pitch

Work breakdown

• Getting the webinar scheduled/advertised
• Slides
• Demo 1
• Demo 2
• Demo N
• Repositories
• Documentation
• Any other top level tasks to break down, or better way to categorize the tasks?

Thanks & regards,

Nathalie