Enabling AD validation for the Software Defined Vehicle with a Structured Workflow
summary
Claim: virtual validation already runs productively to cut actual hardware tests by shifting integration left. The team builds a vECU virtual validation that runs Autosar middleware in containers, uses a Luxoft Autos demonstrator SDK and AWS automation to co-deploy to ARM targets and to cloud containers, enabling earlier Autosar integration tests and developer debug on a virtual target. The workflow preserves flashable binaries, replicates ECU behavior, and increases test coverage before any physical lab run.
AI-written summary · about
chapters (11)
- 0:00Enabling AD validation for the Software Defined Vehicle with a Structured Workflow
- 1:23Introduction to Virtual Validation in SDV Scope
- 1:45AD Digital Twin
- 2:43Virtual Validation
- 3:49Virtual Validation in Development Process
- 4:42vECU Virtual Validation
- 5:50Use case – AUSTOSAR Middleware Integration Test
- 6:04Technical Solution for earlier integration test
- 6:37ARALUX as early Middleware in Virtual Validation Phases
- 8:00Summary
- 8:55Virtual Validation reduces number of HW Tests
related talks
18mSoftware Defined Vehicle - from Hype to Reality
22mSteering into Tomorrow: Embracing Software-Defined Vehicle in an Open-Source Appro...
44mAutomation beyond Testing and Embedded System Validation
17mA Co-Simulation Middleware: Virtual Testing of Automotive Applications with Multiple Simulators
17mTowards Intelligent Automobile Cockpit via A New Container Architecture
17mKeynote: AGL SoDeV: Leading the Software Defined Vehicles Revolution
26mProduct-independent automation framework
19mThe role of software in validating silicon IP