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

2.8 Example
the RTE and should clarify how components can be implemented and how the API
can be used.
2.8.1 Configuration of the Example
The example is based on a system with two SWCs, which are shown in figure 2.8. This
section just contains an extract of the configuration and some parts of the source code
for SWC1. To whole configuration of the system can be found in appendix A. The
configuration of the ECU is not shown.
SWC1
run11 run12
SWC2
run21 run22
Virtual Functional Bus
Figure 2.8: Visualization of the example
Task1
Task2
Every SWC uses two ports and has two runnables, which are shown as boxes inside
of the components. The lines to the ports show an access to this ports. The runnable
run11 is triggered by a timing event which occurs every 100ms. Runnable run12 is
triggered by another timing event which occurs every 50ms. The two runnables of
SWC1 are mapped to the same task Task1. In more detail the events triggering a
runnable are mapped to a task, but here every runnable is just triggered by one event
and so they only run in the context of one Task. The runnable run22 of SWC2 is
also triggered by an timing event every 50ms and runs in the context of Task2. The
other runnable run21 is triggered by the invocation of a server call at the server port.
This runnable is not mapped to a task, but is has the option set, that it can be
invoked concurrently. This is one special case, where an event must not be mapped
to a task. Instead a direct call to the runnable should be performed to provide a
better performance. Both SWCs are mapped to the same ECU. All this information
is reflected by the configuration files.
Listing 2.1 shows the definition of the data elements which are used for this example.
The first is the integer type Int16 with a specified range of valid values. The second
type is a string type, which has a length of 8 characters and the symbol String8. To
reference a type, the names of the packages have to be used as path. This means for
the integer type, that it can be referenced by the path /types/Int16.
The description of the interface of the sender–receiver port used in the example is
shown in listing 2.2. The interface SR Int16 consists of two data elements intValue1
and intValue2, which are both of type Int16, and it provides a not queued communication.
Here it is shown, how the reference to the data types are used multiple times.
The package names specified in the listings are arbitrary. There is no need to call
17