Post by Piyush Itankar

https://lnkd.in/gcc6qQSx The second part of Automotive Verification and Validation (V&V) series, shifting the focus from the application layer to the crucial role of the infrastructure part and the software integrator. The discussion clarifies the division of labor between vehicle manufacturers (OEMs like BMW, Audi, and Daimler), who typically develop the core application software, and embedded suppliers (like Bosch), who design the underlying infrastructure stack and handle final integration. We tightly scope the conversation around M-class and R-class microcontroller-based Electronic Control Units (ECUs)—such as those running body control modules, automatic wipers, and braking systems—while intentionally setting aside infotainment-heavy A-class processors. Viewers will get a detailed look into the AUTOSAR ecosystem, exploring how requirements flow through software compositions, components, runnables, and runtime environments (RTE). The episode also features an in-depth technical analysis of why the CAN protocol remains the industry's bread and butter over protocols like SPI or I2C, how Automotive Ethernet is shaping the future of vehicular networks, and the rigorous demands of functional safety engineering (ASIL) including memory partitioning and end-to-end data protection. 00:00 - Recap: Application Layer V&V (MIL, SIL, HIL) 02:00 - Defining the Scope: M & R Class Microcontrollers vs. A-Class CPUs 04:05 - Safety Criticality in Standard ECUs (Body Control & Anti-Pinch Systems) 05:52 - AUTOSAR Application Architecture: Components, Runnables, and Interfaces 12:45 - Basic Software (BSW) Architecture & The Role of the Integrator 21:30 - Managing Technical Specifications via ARXML and Database Files 24:30 - Deep Dive: Why Automotive Relies on CAN over I2C or SPI 28:40 - The Future of In-Vehicle Networks: Automotive Ethernet and CAN Coexistence 32:45 - Functional Safety Requirements: Unpacking ASIL Standards 38:40 - Safety Mechanics: Watchdogs, Memory Partitioning, and E2E Protection