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

More documents

Recommendations

Info

Chapter 1 Introduction not allow to call a code generator before the test execution. 1.3 Outline This work starts with an introduction to AUTOSAR in chapter 2. There is an overview given and relevant mechanism and features for this work are described. Chapter 3 gives a short overview of MEDC17, which is the currently used platform of BOSCH for software development. Together with these preliminary explanations, the actual topic of this diploma thesis is described in detail in chapter 4. Afterwards the real work of this diploma thesis is explained. An evaluation environment is created and it is in principle divided by an test environment and test cases. The behavior and structure of the test environment is described in chapter 5. The implementation, which is used to achieve this behavior, is explained in chapter 6. The test cases itself together with some guidelines for creating tests are addressed in chapter 7. A conclusion of the work is given in chapter 8. 2
Chapter 2 AUTOSAR Automotive Open System Architecture (AUTOSAR) is a consortium of automotive manufactures including BOSCH, which tends to establish a standard 1 for automotive software engineering. The first discussions were done in 2002 and the partnership was signed in 2003. One idea behind AUTOSAR is “Cooperate on standards, compete on implementation”[8] and it is aimed to solve some principal goals: • decoupling of software from underlying hardware • development of software without dependency of the system structure • sharing of software between manufactures • relocating of software to a different Electronic Control Unit (ECU) in a vehicle • better tool support for the development process and even compatible tooling between the manufactures • replaceability of hardware components without much effort to customize the software This is achieved with the standardization of all major system functions and exchange formats. Additionally some parts of the hardware and the software are encapsulated to provide high reusability, scalability and flexibility. The standardization is done stepwise by publishing different releases. The first release with number 1.0 was published in 2005. Not every detail of AUTOSAR is of interest for this work and a complete description would go beyond the scope. The next sections give an overview of the architecture and the basic approach and it is based on [8]. The for this work significant parts are described in more detail in the following sections. This description is based on the AUTOSAR release 2.1, which is mainly used in this whole work. The newer release 3.0 is already published, but there doesn’t exist enough tools yet, which supports this release. 1 Currently AUTOSAR is just a de–facto standard 3
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 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 20 and 21: Chapter 2 AUTOSAR communications. T
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 62 and 63:
Chapter 6 Implementation of the Tes
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
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?