Image Processing Reference
In-Depth Information
Application
software
System
software
Application layer
AUTOSAR RTE
Services layer
Complex
drivers
ECU abstraction layer
Microcontroller abstraction layer
Hardware
FIGURE .
AUTOSAR—system software layered architecture.
peripheral devices as well as memory mapped external devices. he task of this layer is to make higher
software layers independent of the microcontroller type.
ECU abstraction layer
: his layer interfaces with the sotware modules of the microcontroller abstrac-
tion layer and additionally contains drivers for external devices. he layer offers a standardized API
to access the peripheral devices of an ECU regardless of their location (i.e., whether the peripherals
are internal or external with respect to the ECU's microcontroller) and their connection (e.g., via port
pins, via a serial peripheral interface a.s.o.). The task of this layer is to make higher software layers
independent of the ECU's hardware layout.
Services layer
: his layer is mainly located on top of the ECU abstraction layer and provides operating
system services, vehicle network communication and management services, memory services (e.g.,
nonvolatile random access memory management), diagnostic services (e.g., error logger), and state
management services of the whole ECU. The task of this layer is the provision of basic services for
the application software and other system software modules.
Complex device drivers
: The concept of complex device drivers somehow intentionally violates the
AUTOSAR-layered architecture to provide the possibility to deploy legacy device drivers in an
AUTOSAR system software module stack. Additionally, the complex device driver module concept
has been introduced to facilitate the integration of highly application and ECU-dependent drivers
that require complex sensor evaluation and actuator control with direct access to the microcontroller
itself and complex microcontroller peripherals for performance reasons.
Runtime Environment
(
Rte
): he AUTOSAR Runtime Environment provides the interface between
application software components and the basic software modules as well as the infrastructure services
that enable communication between application software components.
Application layer
: Actually this layer is not part of the AUTOSAR system software modules layered
architecture, as this layer contains the AUTOSAR application software components described in
Section ...
In addition to this, mainly vertical structuring AUTOSAR further horizontally subdivides the
system software modules into different substacks. his subdivision is depicted in Figure ..
I/O substack
: The I/O substack comprises software modules that provide standardized access to
sensors, actuators, and ECU onboard peripherals (e.g., D/A or A/D converters, etc.).
Memory substack
: he memory substack comprises software modules that facilitate the standardized
access to internal and external nonvolatile memory for means of persistent data storage.
