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

More documents

Recommendations

Info

Chapter 2 AUTOSAR communications. These are described in the following along with their symbols 4 to draw such a connection. The symbols are shown in figure 2.4. sender receiver client server Figure 2.4: Symbols for ports sender–receiver The sender distributes data to every receiver. Additionally, a mode manager can notify mode switches to the receivers. The direction of the communication is given through the arrow. Connections of the form 1 : N and N : 1 are possible. M : N connections are explicitly not allowed because of the complexity of the implementation. One sender port can send multiple data elements and multiple modes. The sender is in this case the provided port, the receiver is the required port. client–server The server provides an operation which can be invoked by the client. So the server is accessed via the provided port for this case, whereas the client is called via the required port. The client can send values and the server can return values. Here only connections of the form N : 1 are possible. One server port can provide multiple operations. An operation receives multiple values, does a calculation and then it can return multiple results. In both cases a required port, this is a receiver or a client, has to be connected. On the other hand a provided port, this means analogous a server or sender, can be left unconnected. The data elements and modes or the operations that are provided via a port are specified by the interface of this port. They may be used to create multiple ports with the same interface for one or different SWCs. Ports with the same or a compatible interface can be connected. Compatible means that the provided port at least provides the operations or data types as for the required port specified. The provided port can provide more data or operations, which is not used by the required port. 2.4.3 Software Components The SWCs are the applications which run on an AUTOSAR infrastructure. They interact only through ports with other components. Thus, they can be developed independent from the hardware or from other components. 4 To come back to the release discussion, the introduced symbols are specified in release 3.0. The older release 2.1 uses other symbols, but the newer are much easier to draw and the meaning is clearer 10
Atomic Software Components 2.4 Basic Concepts An atomic Software Components is a basic component, which provides an own behavior. The behavior is given with the later described internal behavior. An atomic Software Component can provide ports to allow communications with other components. Compositions Composition SWC1 SWC2 SWC3 Figure 2.5: Composition of SWCs Compositions are another form of a SWC which consists of other components. The components are aggregated to create a new component. Figure 2.5 shows such a composition of three SWCs. The ports from the components can be connected between each other or with ports of the composition. A connection between components inside the composition is called an assembly connector. A connection from a contained component to a port of the composition is called a delegation connector. A composition of components just provides the behavior that results by the connections of the contained components. It does not add an own implementation or own functionality. 2.4.4 Internal Behavior A component can not only provide ports, there also have to be some functionality behind it. This is done by specifying an internal behavior for an atomic Software Component. The internal behavior consists of several parts. Runnable Entities The functionality of an atomic Software Component is implemented in the form of runnable entities or in short runnables. Runnables are executed when a special event arises and they are implemented in form of a C or C ++ function. A runnable can access the ports of the SWC. The description for this is done with different points or accesses. DataSendPoint It describes an access to a sender port and a concrete data element of that port. The value, which is written to the port, is directly available. 11
Page 1: Evaluation Environment for AUTOSAR-
Page 5: Danksagung An dieser Stelle möchte
Page 8 and 9: Contents 4 Goals 29 4.1 Background
Page 10 and 11: Contents Abbreviations 105 Bibliogr
Page 12 and 13: Chapter 1 Introduction not allow to
Page 14 and 15: Chapter 2 AUTOSAR 2.1 Architecture
Page 16 and 17: Chapter 2 AUTOSAR the hardware depe
Page 18 and 19: Chapter 2 AUTOSAR Basic task Basic
Page 22 and 23: Chapter 2 AUTOSAR DataReceivePoint
Page 24 and 25: Chapter 2 AUTOSAR mode A mode depen
Page 26 and 27: Chapter 2 AUTOSAR not absolutely tr
Page 28 and 29: Chapter 2 AUTOSAR 1 types Int
Page 30 and 31: Chapter 2 AUTOSAR 1 swc root
Page 32 and 33: Chapter 2 AUTOSAR 1 TASK(Task1) { R
Page 34 and 35: Chapter 2 AUTOSAR 24
Page 36 and 37: Chapter 3 MEDC17 3.2 Basic Software
Page 38 and 39: Chapter 3 MEDC17 28
Page 40 and 41: Chapter 4 Goals Communication The c
Page 42 and 43: Chapter 4 Goals 4.1.3 Development o
Page 44 and 45: Chapter 4 Goals files for special p
Page 46 and 47: Chapter 5 Analysis and Design test
Page 48 and 49: Chapter 5 Analysis and Design 38 na
Page 50 and 51: Chapter 5 Analysis and Design confi
Page 52 and 53: Chapter 5 Analysis and Design group
Page 54 and 55: Chapter 5 Analysis and Design direc
Page 56 and 57: Chapter 5 Analysis and Design The s
Page 58 and 59: Chapter 5 Analysis and Design 48
Page 60 and 61: Chapter 6 Implementation of the Tes
Page 70 and 71:
Chapter 6 Implementation of the Tes
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Chapter 7 Test Cases These examples
Page 88 and 89:
Chapter 7 Test Cases • The AUTOSA
Page 90 and 91:
Chapter 7 Test Cases SWC1 run11 SWC
Page 92 and 93:
Chapter 7 Test Cases 1 #include #i
Page 94 and 95:
Chapter 7 Test Cases 1 #ifndef TEST
Page 96 and 97:
Chapter 7 Test Cases 7.3.2 Implemen
Page 98 and 99:
Chapter 7 Test Cases 1 FUNC(void, R
Page 100 and 101:
Chapter 7 Test Cases 7.9. The sourc
Page 102 and 103:
Chapter 8 Conclusion Since a templa
Page 104 and 105:
Appendix A Example /interfaces/CS
Page 106 and 107:
Appendix A Example /interfaces/SR
Page 108 and 109:
Appendix A Example 98
Page 110 and 111:
Appendix B Requirements of the Func
Page 112 and 113:
Page 114 and 115:
Page 117 and 118:
Bibliography [1] FlexRay Protocol S
show all

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

Create successful ePaper yourself

Delete template?

Save as template?