Hi all,
Please let us know your agenda topic requests for this week's sync.
* Tanmay: Update on upstreaming
* Nathalie: PMU ROM & KV260 updates
* Other individual updates
* 12/1 or not 12/1? Is much progress expected by 12/1 call if US folks are the ones with tasks in flight & US Thanksgiving is end of this week?
* Continue with weekly sync, or change to every 2 weeks?
* Objectives to complete before next meeting?
Reminder to please respond to the poll for which weeks would be best candidates for a virtual sprint in ~Q1CY22:
https://doodle.com/poll/n4wb9698y8748c76?utm_source=poll&utm_medium=link
And of action items from last week:
* @Tomas Evensen<mailto:tomase@xilinx.com>: Add to slide 7: Want to showcase proprietary RTOSes
* @Tomas Evensen<mailto:tomase@xilinx.com>: Send Nathalie the latest slides after update
* Nathalie: Update to new WR logo in the slides
* Nathalie: PDF-ize & post & share the sharing link
* Nathalie: Post the PPT template and presentation & share the sharing link to members
* Nathalie: Poll this group for what week might be best to have a virtual sprint in the new year.
Thanks & regards,
Nathalie
Hi all,
During this week's call, Arnaud suggested it could be helpful to have a virtual sprint sometime in the new year. The proposed duration is 1 week when participants could spend most of their time that week to work on this project & attend a daily sync up discussion.
Please let us know what weeks are most likely feasible for you in this poll:
https://doodle.com/poll/n4wb9698y8748c76?utm_source=poll&utm_medium=link
Thanks & regards,
Nathalie
Hi all,
Notes from last call:
https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref…
Initial agenda:
* Arnaud: SDK to use upstream versions.
* Tomas, Bill: Update from presentation at HPP call
* Individual updates
* What to work on before next Wednesday's call?
Please let us know if you have additional agenda topics.
Thanks & regards,
Nathalie
Etsam/All,
Setup Zephyr as normal.
I used the zephyr-sdk-0.13.1 for toolchain and qemu etc.
I used a local python3 venv and pip3 to get west and cmake
Right now you have to run west twice; once to build and once to run
qemu. Don't use -p with west on the second one (optional and OK on first)
$ west build -b mps2_an521 zephyr/samples/subsys/ipc/openamp
$ west build -b mps2_an521 zephyr/samples/subsys/ipc/openamp -t run
The sample does not use remoteproc just rpmsg.
The mps2_an521 board is a dual cortex-M33 platform.
It has QEMU and real HW support but I will not use the HW as it is
expensive.
An RFC PR to fix the need for 2 west invocations is here:
https://github.com/zephyrproject-rtos/zephyr/pull/40240
Thanks go to Arnaud for the pointer to this sample.
Thanks,
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Dan/all,
Looking closer, I am not sure the comments I saw on the Linaro project
are relevant. The Linaro Stratos project is about making virtio work on
multiple hypervisors including Xen. When I saw the comments below I
therefore assumed they were about virtio. Looking more closely the
developer seems to be using Xen native APIs and not virtio.
Here are the Zephyr PR he mentions in the text body:
https://github.com/zephyrproject-rtos/zephyr/pull/36691https://github.com/zephyrproject-rtos/zephyr/pull/39960
His comments on Stratos project issue:
*********************************************
Currently I am working on Xen support in Zephyr (main goal now is to
start Zephyr as Dom0 and create 1 Zephyr guest).
During development I am trying to upstream some features to Zephyr
mainline. Currently I have 1 merged pull-request and 1 is now on review.
Merged PR contains:
Some of Xen public headers, which were placed in Zephyr tree
(include/xen/public/);
Hypercall interface to Xen for arm64 (arch/arm64/core/xen);
PV console driver for DomUs. It is implemented as UART driver, but works
with console ring-buffer instead of real hardware. Such solution was
made because Zephyr has lot of good features for UART drivers (UART
logging backend, shell backend, console with symbol processing stuff
etc.). Also this driver can set up consoleio hooks for printk and
stdout. It allows to receive boot logs ASAP after start with debug
version of hypervisor (very helpful for boot debug).
PR, that is on review contains:
Support for Xen Enlighten page.
Support for pre-defined event-channels (PV console, XenBus).
UART PV console driver improvement - now it is interrupt driven through
the console event channel.
Dom0 console driver. It is also UART-like, but works with consoleio
hypercalls for input and output (which are always available only for
Dom0), instead of console ring-buffer.
Also some other features are now under development: grant tables, XenBus
and starting Zephyr as Domain-0. They are present on my github, but
currently are not ready for review or upstream.
Current status for these features:
Grant tables: taken from Unikraft, ported to Zephyr code base and
tested. Works, but currently is not finished yet. Planned to push it as
next PR to Zephyr repo.
XenBus: also taken from Unikraft, cleaned-up and ported to Zephyr.
Tested: able to list directories, write and read from files in Xenstore.
Driver registration on bus was not tested due to lack of any backend
drivers, but Zephyr uses fully static configuration, so this should not
be a problem.
Zephyr Domain-0: currently I am working on this PoC and successfully
started simple sample (samples/subsys/shell/shell_module) with Dom0
console driver on R-Car Gen3 hardware. It looks a little bit hacky due
to static configuration in Zephyr (it does not use device tree in
runtime, so we need to know Dom0 and GIC location on compile time to
build and link with right addresses), but I think it is OK for PoC.
Lot of problems during development are caused by the licensing - Zephyr
is licensed under Apache-2.0, so I can not use GPL-2.0 code in there.
Also when I am trying to use MIT code from Xen (public headers) or
Unikraft (Xenbus and grant table drivers) it causes long Zephyr TSC
negotiation to take MIT code inside the Zephyr tree. So It may take some
time to add suitable Xen support in Zephyr upstream.
But I will continue PoC development and share some of the updates here.
Please, contact me if you need any other details.
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Hi all,
Please let us know if you have any additional agenda topics for this week.
* Individual updates
* Arnaud: SDK to use upstream versions.
* What to work on before next Wednesday's call?
Notes from last week's call: https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref…
Thanks & regards,
Nathalie
Hi Nathalie,
Please add following to agenda:
KV260 BSP Yocto flow status.
Thanks,
Tanmay Shah
tanmay.shah(a)xilinx.com<mailto:tanmay.shah@xilinx.com>
From: Openamp-system-reference <openamp-system-reference-bounces(a)lists.openampproject.org> on behalf of Nathalie Chan King Choy via Openamp-system-reference <openamp-system-reference(a)lists.openampproject.org>
Reply-To: Nathalie Chan King Choy <nathalie(a)xilinx.com>
Date: Monday, November 1, 2021 at 10:32 AM
To: "openamp-system-reference(a)lists.openampproject.org" <openamp-system-reference(a)lists.openampproject.org>
Subject: [OA-syst-ref] Calling for agenda items: 11/3 OpenAMP System Reference weekly
Happy Monday!
Please let us know if you have any additional agenda topics for this week. Here is what I have so far:
* Individual updates
* Nathalie: KV260 ordering, PMU ROM ELF updates
* What to work on before next Wednesday’s call?
Notes from last week’s call at https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref…
Thanks & regards,
Nathalie
Happy Monday!
Please let us know if you have any additional agenda topics for this week. Here is what I have so far:
* Individual updates
* Nathalie: KV260 ordering, PMU ROM ELF updates
* What to work on before next Wednesday's call?
Notes from last week's call at https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Ref…
Thanks & regards,
Nathalie