AUTOSAR Classic PlatformThe Production-Proven Standard for In-Vehicle ECUs
The AUTOSAR Idea
AUTOSAR (Automotive Open System Architecture) is a standardization initiative of leading automotive manufacturers and suppliers that was founded in 2003.
With the rising number of complex functions, the development of in-vehicle electronics is becoming increasingly broader in scope and more complicated. The idea behind AUTOSAR is to avoid continually re-developing the same or similar software components. The worldwide development partnership has set the goal of establishing an open standard for the system architecture in the automotive industry.
Reduced development effort and improved quality are important reasons for introducing a uniform and producer independent system platform. Hardware and software are decoupled from one another to assure such results. The AUTOSAR concept is based on modular components with defined interfaces.
AUTOSAR Adaptive Platform
The AUTOSAR development partnership has added a new standard to its portfolio which is based on POSIX operating systems: the AUTOSAR Adaptive Platform. The primary motivations for the new platform are autonomous driving, Vehicle-to-X (V2X) applications and the growing external networking of vehicles (Connectivity).
The previous standard will continue to be offered under the name AUTOSAR Classic Platform.
Basic elements of the AUTOSAR architecture are, among others, formally defined software components (SWC) with clearly specified interfaces to the basic software (BSW) that in turn provide fundamental standard services, such as bus communication, memory management, IO-access, system and diagnostic services. Another basic element is the runtime environment RTE that connects the SWCs with the BSW.
The Virtual Functional Bus (VFB) specified by AUTOSAR delivers the conceptual foundation for the communication of SWCs with each other and the use of BSW services. The development of the SWCs is based on the VFB. In this manner, the SWCs are independent of the ECU hardware. This makes them easier to reuse and integrate into different projects on different platforms. The VFB is implemented in a specific vehicle by using a specifically configured RTE together with a suitably configured BSW for each ECU.
During system design, the architecture of the functional software is determined. This is done by defining SWCs and their distribution over the ECUs. Network communication is also determined in this step. The result is the system description – an AUTOSAR XML file from which one generates a specific ECU extract of system description for every ECU.
During ECU development, the SWCs are designed and implemented and the BSW and RTE are configured. The developer determines the necessary amount of basic software for his project by configuration. In this manner, he can optimize the entire ECU software. The result of the configuration is an ECU Configuration Description (AUTOSAR XML file) that is tuned to the ECU Extract of System Description.
Based on the ECU Configuration Description, code generators generate and/or adapt the BSW for the ECU software. The RTE is also created in an ECU-specific manner.
This method defined in AUTOSAR significantly simplifies the integration of application software into an ECU. Manual software adjustment becomes unnecessary.
- E/E complexity is growing fast
- Quantity of software is exploding
- Many different hardware platforms are used
- Development processes and data formats are not harmonized
The main objectives of AUTOSAR:
- Improve software quality and reduce costs by re-use
- Re-use of functions across carlines and across OEM boundaries
- Re-use of development methods and tools
- Re-use of basic software
The Vector Academy provides an E-Learning module for AUTOSAR free of charge. It is intended for all persons who wish to acquire an overview of the goals of AUTOSAR. Along with the fundamental AUTOSAR concepts, it also discusses methodology and typical migration scenarios.
Essential Know How for Your Development
++++ A new edition is being prepared and is expected to be available again in May 2022 ++++
The clearly structured AUTOSAR Poster in DIN A1 format gives you important technical details on the AUTOSAR Classic R19-11 (4.5) method. Among other things, the poster illustrates the following topics:
- AUTOSAR system design
- Layer model
- Mode management, multi-core and safety
- Secure variant coding (certificate handling)
++++ A new edition is being prepared and is expected to be available again in April 2022 ++++
To support a common understanding of the AUTOSAR software modules, we have compiled all important terms from the AUTOSAR specifications R19-11 (4.5), 4.4, 4.3, 4.2, 4.1 and 4.0 in German and English in this AUTOSAR Glossary.
- Part 1: Introduction into AUTOSAR
- Part 2: Description of AUTOSAR work products and activities
- Part 3: Description of AUTOSAR Basic Software Modules (BSW)
Qualification Program Vector Certified Embedded Professional
Extensive software skills are one of the most important qualifications for the successful implementation of projects today. Whether supplier or engineering partner - the competence of employees represents an important competitive advantage. That is why Vector offers unique certification programs for embedded software engineers. Engineers are being trained as experts in Vector's basic software and the corresponding software tools. The Vector degree enables qualified and efficient support in demanding AUTOSAR Classic projects. Through close contact with the Vector experts, further knowledge transfer is assured.
More Know How
AUTOSAR Workshop | 1-5 days
Do you want to know more about the basics of AUTOSAR and the AUTOSAR basic software and tools? Vector offers a 1-5-day modular AUTOSAR workshop. This deals with AUTOSAR 4 and AUTOSAR 3 alternately. According to the booked module...
- You get to know the AUTOSAR methodology
- You gain insights in all major subject areas of the ECU development
- You get to know the specifics of some vehicle manufacturers
- MICROSAR safe is presented - the Vector solution for safety-related ECUs according to ISO 26262.