AUTOSAR — LLMpedia

AUTOSAR
Name	AUTOSAR
Developer	AUTOSAR Development Partnership
Released	2003
Latest release	Adaptive Platform, Classic Platform
Operating system	Real-time operating systems
Programming language	C, C++
License	Consortium specifications

Contents

AUTOSAR AUTOSAR is an open and standardized automotive software architecture developed to enable interoperability between automotive suppliers and manufacturers; it provides a layered framework for control units, middleware, and application software to support modular development, reuse, and scalability across models from companies such as Bosch (company), Continental AG, Daimler AG, BMW, and Volkswagen Group. The initiative coordinates technical specifications used by stakeholders like Audi, Ford Motor Company, General Motors, Toyota Motor Corporation, and Renault to harmonize electronic control unit (ECU) software development for vehicles deployed in markets overseen by regulators including the European Commission, the Federal Motor Carrier Safety Administration, and the National Highway Traffic Safety Administration.

Overview

AUTOSAR defines interfaces, service layers, and software component models used in ECUs produced by suppliers such as NXP Semiconductors, Infineon Technologies, Renesas Electronics, Texas Instruments, and STMicroelectronics. The platform supports classical real-time applications and dynamic computing services for advanced driver assistance systems (ADAS) from vendors like Bosch (company), ZF Friedrichshafen AG, Magneti Marelli, Aptiv, and Valeo. Stakeholders include OEMs such as Subaru Corporation, Mazda Motor Corporation, Hyundai Motor Company, Kia Corporation, and Tata Motors. AUTOSAR specifications interact with middleware and standards like Time-Triggered Protocol, CAN bus, LIN (Local Interconnect Network), and Ethernet (computer networking), and are relevant for development flows used by toolmakers such as ETAS, Vector Informatik, dSPACE, Mentor Graphics, and PREEvision.

The development partnership began in 2003 with founding members including BMW, Bosch (company), Continental AG, Daimler AG, Ford Motor Company, General Motors, and Volkswagen Group. Subsequent working groups drew participants from Renault, PSA Peugeot Citroën, Toyota Motor Corporation, Nissan Motor Corporation, Mazda Motor Corporation, and suppliers like Denso Corporation. Over time, the partnership coordinated with standards bodies such as ISO, IEC, SAE International, IEEE, and ETSI to align automotive software specifications with safety norms like ISO 26262 and cybersecurity frameworks like UNECE WP.29. The initiative evolved into two major product lines with contributions from research organizations including Fraunhofer Society, VTT Technical Research Centre of Finland, and universities like RWTH Aachen University and Karlsruhe Institute of Technology.

AUTOSAR’s layered architecture separates application software components from basic software and runtime environments, enabling integration across ECUs built by Magna International, Lear Corporation, Aisin Seiki, Marelli, and Delphi Technologies. Layers include an application layer analogous to practices used by Intel Corporation and ARM Ltd. in embedded systems, a runtime environment (RTE) similar in role to middleware deployed by Microsoft Corporation in other domains, and a basic software layer comprising services, ECU abstraction, and microcontroller abstraction with chip vendors like NXP Semiconductors and Infineon Technologies influencing implementation. The architecture supports communication stacks for protocols designed by Bosch (company) and standards groups such as Society of Automotive Engineers and integrates with simulation platforms from Ansys, Siemens PLM Software, and MathWorks.

AUTOSAR specifications define interfaces, exchange formats, and configuration descriptions used alongside standards like ISO 26262, ISO/SAE 21434, IEEE 802.3, IEEE 1588, and SAE J1939. The Classic Platform and Adaptive Platform reference models align with requirements from regulators and industry consortia including UNECE, CENELEC, and ETSI. Documents cover automatic code generation practices employed by Vector Informatik, modelling languages favored by Object Management Group, and data exchange approaches used in tools from IBM and Accenture. Specification governance involves corporate members such as Hitachi Automotive Systems, Mitsubishi Electric, Tenneco, and Hella GmbH & Co. KGaA.

Implementations of specifications are provided by software vendors and toolchains from Vector Informatik, ETAS, Elektrobit, Green Hills Software, and Wind River Systems. Development workflows incorporate model-based design tools from MathWorks, simulation and verification from dSPACE, static analysis by Coverity (Synopsys), and continuous integration solutions used by GitLab and Jenkins adopted by teams at BMW and Mercedes-Benz. Microcontroller support is available from Renesas Electronics, Infineon Technologies, NXP Semiconductors, and development boards used by researchers at Stanford University and Massachusetts Institute of Technology. Ecosystem tooling includes diagnostic and calibration tools provided by ETAS, Vector Informatik, and hardware-in-the-loop systems by National Instruments.

OEMs including Tesla, Inc., Volvo Cars, Jaguar Land Rover, Škoda Auto, and Ferrari N.V. have integrated AUTOSAR-based systems to varying degrees, affecting supply chains of Bosch (company), Continental AG, Aptiv, and Denso Corporation. The architecture influenced software strategies in emerging mobility companies like Uber Technologies, Waymo LLC, Cruise LLC, and in partnerships with technology firms such as Google, Apple Inc., Amazon (company), and Microsoft Corporation for cloud-connected vehicle services. Standardization reduced integration costs for suppliers like Faurecia and Magneti Marelli and reshaped procurement and certification practices overseen by agencies such as the European Union and United States Department of Transportation.

Safety compliance relies on harmonization with functional safety standards like ISO 26262 and cybersecurity regulations such as UNECE WP.29 and ISO/SAE 21434; stakeholders involved in security assessments include TÜV SÜD, TÜV Rheinland, DEKRA and testing labs affiliated with European Telecommunications Standards Institute. Security toolchains leverage static analysis from Coverity and fuzzing infrastructures influenced by work at Google and Microsoft Research while threat modeling draws on practices from MITRE and OWASP Foundation. Safety-critical deployments require certification processes involving organizations like SAE International, ISO, and national approval bodies used by manufacturers such as Toyota Motor Corporation and Honda Motor Co., Ltd..

Category:Automotive software