Driving Intelligence: The Software Shift Shaping Tomorrow’s Cars
summary
Built a homegrown stack for NEA that puts 40 ECUs down to 3 after starting with custom hardware, an in-house drive unit and inverter, and onboard software that helps NEA break 24 world records; now shifts to standardized toolchains—ISO 26262, AUTOSAR, ASPICE—with V‑model traceability, external audits, sub‑millisecond fault detection, redundancy and protected memory choices. Shows concrete migration pain: tooling gaps, retraining, test-case traceability and supplier wins supplying BMW and Porsche while using Bugatti as a showcase.
AI-written summary · about
chapters (9)
- 0:00Introduction and company background
- 3:56NEA project and early challenges
- 6:06New software development processes
- 7:29Functional safety standards
- 9:16AUTOSAR platform adoption
- 11:00Impact of functional safety
- 13:07V-model testing process
- 14:55SPICE process and traceability
- 17:25Future of automotive software
related talks
17mperspective on automotive software and Eclipse SDV
19mDriving Automotive with Open Source: From Compliance to Collaboration
39mSoftware development challenges in automotive projects
19mBoosting confidence in tiny AI deployment in embedded control systems
39mTransforming Car Development
18mSoftware is the New Fuel, AI the New Horsepower - Pioneering New Paths
22mSteering into Tomorrow: Embracing Software-Defined Vehicle in an Open-Source Appro...
06mEmbedded Executive LIVE