Evaluation Environment for AUTOSAR-Autocode in Motor Control ...

Chapter 1
Introduction
1.1 Motivation
The increasing complexity of embedded systems found the way into automotive development
some years ago. The number of electronic control units (ECU) has increased
to about 70 and they are connected by about 5 system buses per car [11]. However,
not every component comes from the same manufacture, instead the whole hardware
and software system of a car is composed from different suppliers.
The increasing complexity has to be handled together with the needs to be compatible
with other manufactures to keep the development effort down. To achieve
these goals there was still an attempt to standardize software done with OSEK/VDX
[13]. These first reached goals are now continued by the Automotive Open System
Architecture (AUTOSAR) [9].
However, the migration to such a standard has to be done and since there is a lot
of existing software, which should not be discarded, a way must be found, to do such
a migration in little steps.
1.2 Related Work
For embedded system, automatic code generators play a significant role. They provide
the creation of code from a configuration or a model and prevents errors from hand–
written code. However, it is required, that the code generators contain no errors and
produce correct code, which reflects the configuration.
For developing software for embedded devices the modeling tools ASCET[20] and
MATLAB/Simulink/Stateflow[21] exist. ASCET provides its own code generator to
create source code from the model. The software TargetLink[23] from dSPACE is
typically used to generate code from MATLAB/Simulink/Stateflow models.
The tool MTest[22, 17], which is also provided from dSPACE, is used to test the
models in different development phases. Other works deal with the testing of the code
generators itself[24, 26, 25]. However, these works assume that the semantic is defined
and the behavior of the generated code can be compared to that of the model. The
works also do not handle the aspect of integration of the generated code into another
enviroment.
Another tool for testing embedded software, which is also based on XML configurations,
is described in [18, 10]. However, it handles testing of source code and does
1