Dealing with automotive software complexity with virtual prototyping - Part 2: An AUTOSAR use case
Victor Reyes, Synopsys Inc.
embedded.com (May 25, 2014)
In 2003, OEM manufacturers and Tier 1 automotive suppliers founded the AUTOSAR3 consortium to address the technical and business challenges they all faced with the increase in software development and test costs. The premise of that conversation is the principle that guides the AUTOSAR alliance today: Cooperate on standards, compete on implementation. The net goal of the consortium is to drive the change in software development, moving from proprietary solutions to standardized, productized and predictable software products.
AUTOSAR focuses on three main areas: software architecture, methodology and application interfaces. In this document we will only discuss on the software architecture part.
The goal of the AUTOSAR software architecture [3] is to provide a clear separation from the application (differentiation) and the infrastructure (commodity) domain.
To read the full article, click here
Related Semiconductor IP
- 1.8V/3.3V I/O library with ODIO and 5V HPD in TSMC 16nm
- 1.8V/3.3V I/O Library with ODIO and 5V HPD in TSMC 12nm
- 1.8V to 5V GPIO, 1.8V to 5V Analog in TSMC 180nm BCD
- 1.8V/3.3V GPIO Library with HDMI, Aanlog & LVDS Cells in TSMC 22nm
- Specialed 20V Analog I/O in TSMC 55nm
Related White Papers
- Transaction Level Model of IEEE 1394 Serial Bus Link Layer Controller IP Core and its Use in the Software Driver Development
- PRODUCT HOW-TO: Use ARM DBX hardware extensions to accelerate Java in space-constrained embedded apps
- USB Host IP-Core Hardware and Software Concurrent Development
- For smoother embedded systems development, design-out the hardware