AUTOSAR (AUTomotive Open System ARchitecture) is an open and standardized automotive software architecture, jointly developed by automobile manufacturers, suppliers, and tool developers. MathWorks is an AUTOSAR Premium Member and actively participates in the development of the standard with focus on how to use Model-Based Design with an AUTOSAR development process.

The AUTOSAR standard provides two platforms to support the current and the next generation of automotive ECUs. The first is the Classic platform, used for traditional applications such as powertrain, chassis, and body and interior electronics. The second is the Adaptive platform, used for compute-intensive applications such as highly automated driving, Car-to-X, software updates over the air, or vehicles as part of the Internet of Things. The Foundation AUTOSAR standard enforces interoperability between the AUTOSAR platforms.

Simulink^® natively supports AUTOSAR. AUTOSAR Blockset lets engineers map Simulink models to either AUTOSAR Classic or Adaptive specifications. And you can also generate production C and C++ AUTOSAR code using Embedded Coder^®. Simulink, AUTOSAR Blockset, and Embedded Coder support round-trip integration with AUTOSAR architectures as illustrated below.

Key products for developing AUTOSAR applications:

• Simulink and Stateflow^® for software design
• AUTOSAR Blockset to design and simulate AUTOSAR Classic and Adaptive ECU software
  
• Embedded Coder for generating production code and ARXML, and for SIL/PIL verification
• Polyspace Code Prover for verifying code of AUTOSAR Software Components 
  
• Third-party tools for AUTOSAR authoring: Vector Informatik DaVinci Developer, KPIT Cummins K-SAR, Mentor Graphics Volcano Vehicle System Architect, ETAS ISOLAR-A

User presentations, technical articles, and videos:

• John Deere: Vertical AUTOSAR System Development at John Deere (18:34) (PDF)
  
• Fiat Chrysler Automobile: Leveraging Model-Based Design, Automatic Code Generation, and AUTOSAR to Architect and Implement an Engine Control Application for Series Production
  
• LG Chem: Developing AUTOSAR-Compliant Software for a Hybrid Vehicle Battery Management System with Model-Based Design
• BMW: Model-Based Software Development: And OEM's Perspective (PDF)
• Autoliv: Development of Integrated Vehicle Safety Applications Through Model-Based Design (19:47)
• VALEO E.E.S.: Automatic Code Generation of AUTOSAR Software Components for Mass Production Application of Engine Management Systems: Process and Benefits (26:03)
• KPIT: KPIT Establishes an End-to-End Process for AUTOSAR-Compliant Software Development with Model-Based Design
• AUTOSAR: Model-Based Development Approach: AUTOSAR + Functional Safety + Aspice (27:08)
• Magneti Marelli: Development of a Semi-active Suspension System Using Model-Based Design with AUTOSAR and Compliant with the A-SPICE Standard

MathWorks presentations, videos, and documentation:

• Simulink Advance Support for AUTOSAR: Compositions, BSW Services Simulation and Code Generation (32:44)
• AUTOSAR Support from Simulink and Embedded Coder (2:33)
• From Simulink to AUTOSAR Production Code (5:16)
• AUTOSAR Code Generation for Multiple Runnable Entities (2:46)
• AUTOSAR Client-Server SIL Simulation (5:38)
• Simulation of AUTOSAR Software Components (6:01)
• Simulink to AUTOSAR Code Made Easy (32:32)
• Development of AUTOSAR Software Components Within Model-Based Design
• Generating Code for AUTOSAR Software Components Using Embedded Coder
• Model AUTOSAR Variants in Simulink (4:53)
• Model AUTOSAR ECU Power-Up and Power-Down Behavior in Simulink (7:20)
• AUTOSAR Queued Sender-Receiver Communication (4:24)
• AUTOSAR Compositions in Simulink : Top-Down Workflow (4:49)
• AUTOSAR ECU Software Simulation in Simulink (10:52)
• Comprehensive Workflow for AUTOSAR Classic and Adaptive Using Model-Based Design (35:20)