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

1 #define RTE E CS string to int overflow (42)
#define RTE E CS string to int underflow (43)
2.8 Example
#define Rte Call rport1 parse(array, sum) (Rte Call swc1 rport1 parse(array, sum))
FUNC(Std ReturnType, RTE CODE) Rte Call swc1 rport1 parse(CONSTP2VAR(String8, �
AUTOMATIC, RTE APPL DATA), CONSTP2VAR(Int16, AUTOMATIC, RTE APPL DATA));
/∗ Inline Write optimization; Rte Write pport1 intValue2 to direct access ∗/
extern VAR(Int16, RTE DATA) Rte RxBuf 1;
10 #define Rte Write pport1 intValue2(data) ( �
Rte WriteHook swc1 pport1 intValue2 Start(data), (Rte RxBuf 1 = data), �
Rte WriteHook swc1 pport1 intValue2 Return(data), RTE E OK )
/∗ Inline Write optimization; Rte Write pport1 intValue1 to direct access ∗/
extern VAR(Int16, RTE DATA) Rte RxBuf 0;
#define Rte Write pport1 intValue1(data) ( �
Rte WriteHook swc1 pport1 intValue1 Start(data), (Rte RxBuf 0 = data), �
Rte WriteHook swc1 pport1 intValue1 Return(data), RTE E OK )
FUNC(void, RTE APPL CODE) run11(void);
FUNC(void, RTE APPL CODE) run12(void);
Listing 2.5: Example header file for SWC1 (Rte swc1.h)
to implement a functional behavior for the Software Component, this functions have
to be implemented. Within these functions, the values of the ports can be accessed, if
it is configured for the SWC.
For an access to a sender port with a DataSendPoint, the API is specified within
AUTOSAR to be of the form Rte Write (data). Whereas is the name
of the port and is the name of the data element which is accessed. The value,
which is passed to the call with the parameter data, is written to the port.
As mentioned before, the both components are mapped to the same ECU and so
there is no need to use any inter–ECU communication mechanism. Instead the communication
can be done directly. It can be seen in the example that the API is
implemented with #define directives, which directly accesses the global variables
Rte RxBuf 1 and Rte RxBuf 2. The API for SWC2 is not shown here, but it has to
access the same variables to establish the communication.
To invoke an operation at the server, a function call is necessary. For the runnable
run12 is a SynchronousServerCallPoint specified. So the function does not return
until the operation on the server is finished and the return values are available. In
the special case mentioned above, the runnable, which implements the server, is not
mapped to a task and can be invoked concurrently. This runnable is then executed in
the context of the current task and therewith no other task has to be started.
For the SynchronousServerCallPoint, the API Rte Call rport1 parse( string , value)
is expected and created by the RTE generator. The operation parse takes one string
as argument and returns one integer value. This API is implemented using a #define
directive to a function. This function is implemented in the also generated file Rte.c.
21