The AUTOSAR consortium was founded to manage the growing electronics complexity and improve cost-efficiency without any compromises with quality as well as reusability. It is expected that AUTOSAR, open and standardized automotive software architecture, is widespread in automotive industry worldwide. In general, automotive embedded software has been closely coupled with the hardware, and the boundary between application software and hardware related software is not clear. The AUTOSAR approach requires a more different approaching way to develop automotive embedded software than today. In AUTOSAR, the application software and infrastructural software are clearly separated through the concept of RTE (Run Time Environment), and the paradigm of design is shifted from coding to configuration. By introducing AUTOSAR, existing system need to be translated into AUTOSAR and, several migration concepts are necessary for the successful transition. ECU developments typically start with legacy software, and it is unavoidable to rearrange existing software according to the AUTOSAR concept. This paper shows how to construct AUTOSAR application software components and basic software modules for already developed ECU software.
[1]
Farzad Rajaei Salmasi,et al.
Design and Optimization of Parallel Hybrid Electric Vehicle (PHEV) Drivetrain based on Mechatronics Design Approach
,
2008
.
[2]
Devendra Rai,et al.
Model-Based Development of AUTOSAR-Compliant Applications: Exterior Lights Module Case Study
,
2008
.
[3]
Richard Thompson,et al.
Development of AUTOSAR Software Components within Model-Based Design
,
2008
.
[4]
Dae-Hyun Kum,et al.
Automotive Embedded System Software Development and Validation with AUTOSAR and Model-based Approach
,
2007
.
[5]
Kenji Nishikawa,et al.
TOYOTA Electronic Architecture and AUTOSAR Pilot
,
2007
.
[6]
Håkan Sivencrona,et al.
SWAP-design of an AUTOSAR open laboratory test bench
,
2008
.