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

5.2 Components of the Environment
run OSEK–OS 5.0 for PC This type executes the binary file for the PC–Port.
The binary is executed for a specific time. During this time the binary can make some
outputs to the standard output. If there is an output, that starts with the string
“ERROR”, this type is adopted as “failed”. Otherwise it is finished correctly. As a
variable this type requires a period of time that specifies how long the binary shall be
executed.
copy to Mx17 PST Since a complete built of MEDC17 has a size about 650MB,
it is not workable to copy it for every test. So the sources of the test are copied
to the MEDC17 directory, to integrate the test. So just one checkout is used for the
whole environment. The names of the copied files are stored in the MEDC17 directory
to delete the files before files of another test are copied to MEDC17. The test type
requires also some variables. These are the location of the PST and the names of the
subdirectories, in which the files shall be copied.
compile Mx17 PST The compilation of MEDC17 is not integrated in the environment.
It has to be performed with other build tools, which have to be started
manually.
run on control unit Here again, the flashing of the compiled MEDC17 to the control
unit and the debugging of the control unit, have to be done by the user. This
is done with the graphical debugger Universal Debug Engine, which is the debugger
used at BOSCH.
With this description it is clear that the test type “code review” does not need a
Perl script, because everything, which can be done automatically is done by an test
type that is executed before. So a test type, which is performed by the user, does not
have a Perl file.
5.2.6 Variables
To keep the test types configurable for a test template, variables are introduced. The
types e.g. need the name of the ECU in the configuration files, for which the RTE shall
be created, or a period of time for which a compiled binary shall be executed. Such
variables are defined by the test type and can be used in the Perl files. The variables,
which are required by the different test types, are already mentioned in the previous
section. Typically the variables are set by the test templates, but a test type can also
provide a “default value”, which is used, if no other is specified. A variable without
a “default value” has to be set from a test template that uses this test type. A test
type additionally sets a description for the variable. The description should explain
the purpose of the variable.
5.2.7 Test Template
A test template consists of a number with four digits and a name. The template is
unique identified by the number. The number is also used to sort the templates and
41