SNIP_ADAPTIVE_CAN_FIGURE_Figure_5_17_ADAPTIVEPLATFORMTIMINGEXTENSIONS

Figure 5.17: Trace showing various occurrences of the timing description events E1 and E2, as well as the value of the variable DE3. Based on the several functions provided by the occurrence expression language, the interpreter requires the following information from the system: • the value of a referenced AutosarOperationArgumentInstance at time t. • the value of a referenced AutosarVariableInstance at time t. • the occurrences of a referenced TimingDescriptionEvent at time t and before. There are different ways to gather the required information: • Model analysis and simulation: In a deterministic system environment, occurrences of TimingDescriptionEvents can be determined offline, for example the point in time a frame will be transmitted in the static segment of a FlexRay network. • T arget trace: The required information can be gathered from a running system by recording the points in time a TimingDescriptionEvent has occurred. If the interpreter has the required information as input, the different functions provided by the occurrence expression language can be interpreted as follows: • TIMEX_value(t, <reference to an AutosarVariableInstance>) returns the variable value at time t. • TIMEX_value(t, <reference to an AutosarOperationArgumentInstance>) returns the operation argument value at time t. • TIMEX_occurs(t, <reference to a TimingDescriptionEvent>) returns TRUE (or 1) if the referenced event has occurred at time t, else it returns FALSE (or 0).