Connecting traditional AUTOSAR Adaptive applications
summary
Demo shows a working bridge between AUTOSAR Adaptive and containerized apps: EB corbos Adaptive core runs on an NXP S32G VM offering services via SOME/IP over IPv6 multicast, while a k3s Kubernetes cluster on Raspberry Pi and an NVIDIA Jetson runs a live object detector and accumulator. Connectivity uses a macvlan CNI to give pods a SECOND interface for Layer‑2 SOME/IP, vehicle speed is published, received, pushed to AWS Timestream and visualized in Grafana — the end‑to‑end demo works.
AI-written summary · about
chapters (7)
- 0:00Connecting traditional AUTOSAR Adaptive applications with containerized workloads via SOME/IP
- 0:22Motivation – Why using SOAFEE
- 1:42Container orchestrator - Demo
- 5:00SOME/IP – Scalable Service-Oriented Middleware over IP
- 7:00Connecting AUTOSAR Adaptive with containerized apps
- 9:04Connecting a pod to AUTOSAR Adaptive via SOME/IP
- 11:00Demo
related talks
01h 02mA perfect match: Dapr & Azure Container Apps
28mOpenAdx "Autonomous Driving Simulation" Testbed – hardware in the loop
40mCloud-Native Automotive Edge: AGL for Software-Defined Vehicles
34mKubernetes in Your 4x4 – Continuous Deployment Directly to the Car
40mLightweight and Easy to Integration Into Embedded System Using Linux Container.
37mHow to Extend AD/ADAS Sensors Accessibility to IVI Domain in the...
21mAPP4MC RaceCar: A Practical ADAS Demonstrator for Evaluating and Verifying Timing Behavior
32mAn Eclipse Automotive Stack for rapid-prototyping Software Defined Vehicles