Apr 08, 2024 ‐ 15:00 UTC

Host:

• Philipp Ahmann

Participants:

• Nicole Pappler
• Guy Lunardi
• Alfred Strauch
• Steven Carbno
• Thomas Mittelstädt

** Regrets:**

• Kate Stewart

Attended Recently

• Andreas Bartelt
• Stewart Hildebrand
• Kate Stewart
• Olivier Charrier
• Walt Miner

Topics & Notes:

Check past action items

• Last meeting minutes: https://github.com/elisa-tech/wg-systems/wiki/Mar-18,-2024-%E2%80%90-16:00-UTC
• AI-Philipp-Thomas: Need to schedule a follow-up with ZAL (Aerospace research centre in Hamburg, Germany)
  • ZAL considers domain separation on single HW platform.
  • ZAL representative will visit embedded world and take a look at the demonstrator at Collabora booth and also meet Kate at Zephyr booth.
  • They are also having similar architectures considered for Aerospace as considered for Automotive.

Embedded World Demonstrator

• The demonstrator will arrive this evening at embedded world.
• Documentation was sufficient as training for the demo at the embedded world.
• If questions come up at Collabora, Thomas will be contacted via mattermost.
• Material prepared where the draft version can be found here: https://drive.google.com/drive/folders/1mzBNq6HSvdSHadTR0mk3mUT9a83_Xifj

Review past TSC meeting minutes

• 03-Apr-2024

Lund WS agenda

• Agenda link

Next steps to System BOM

• Start initial brainstorming (really just initial parts) in a gdoc before putting the result in GitHub repo.
  • DRAFT - ELISA SBOM Generation
• Should consider HBOM as part of the System as well.
• Start taking actions after the HBOM presentation April 22nd.

AoB

• No meeting next week (due to OSS NA and EOSS). Next meeting April 22nd.
• Alignment on HBOM presentation to be done via mail (if needed).
• Workshop participation is also possible virtually (for some parts at least).
• Regarding Systems WG CI and qemu setup Sudip was busy and want to have progress by the Lund WS timing.
• Hardware discussion for the future. What are standard requirements for the future
  • Power domain separation is a feature
  • Watchdog need to be provided
  • We expect microcontroller typically with a lockstep.
  • You can also create external elements, meaning if you do not have a microcontroller on chip you can have it as external microcontroller
  • This is still part of the system.
  • We also would like to have System MMUv3
  • Other more ELISA specific things not related to Safety:
    • Good open drivers for graphics are important. NDA and licenses do not work on OSS.
    • Community version of the board needs to be available for low cost.
    • Have one hardware example to best show what is needed to reproduce and develop use cases.
    • Find a second hardware to reproduce the 1st hardware.
  • Do we need a closer talk to hardware manufacturer?
    • In discussion with SoC provider they differ in preferred RTOS and Hypervisor.
    • Discussions with HW providers make sense and are taking place
    • SoC provider do not judge themselves as SW-Companies (SW is enablement not a product) --> this is changing.
    • Some issues also for HW provider by obligations to companies providing IP for them.
    • We may need to talk to more hardware providers to see, if we find a good chipset.
  • We have many hypervisors and no real standardization for the various chipsets.
    • Today Linux systems work well and out of the box also with new chipsets.
    • 20 years back Linux support for hardware was much worse. It feels a bit that we are in the state for hypervisors where Linux was many years back for compatibility.
    • Landscape is seen competitive and hypervisor is still seen as a differentiating technology and nothing consolidated.