1、 g49g50g3g38g50g51g60g44g49g42g3g58g44g55g43g50g56g55g3g37g54g44g3g51g40g53g48g44g54g54g44g50g49g3g40g59g38g40g51g55g3g36g54g3g51g40g53g48g44g55g55g40g39g3g37g60g3g38g50g51g60g53g44g42g43g55g3g47g36g58applications Part 6: OSEK/VDX Implementation Language (OIL)ICS 43.040.15Road vehicles Open interfac
2、e for embedded automotive BRITISH STANDARDBS ISO 17356-6:2006BS ISO 17356-6:2006This British Standard was published under the authority of the Standards Policy and Strategy Committee on 3 February 2006 BSI 3 February 2006ISBN 0 580 47775 4The British Standards which implement international publicati
3、ons referred to in this document may be found in the BSI Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Search” facility of the BSI Electronic Catalogue or of British Standards Online.This publication does not purport to include all the necessar
4、y provisions of a contract. Users are responsible for its correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations.Summary of pagesThis document comprises a front cover, an inside front cover, the ISO title page, pages ii to v, a blank page, p
5、ages 1 to 49 and a back cover.The BSI copyright notice displayed in this document indicates when the document was last issued.Amendments issued since publicationAmd. No. Date CommentsA list of organizations represented on this committee can be obtained on request to its secretary.Cross-referencesenq
6、uiries on the interpretation, or proposals for change, and keep UK interests informed; monitor related international and European developments and promulgate them in the UK.National forewordThis British Standard reproduces verbatim ISO 17356-6:2006 and implements it as the UK national standard.The U
7、K participation in its preparation was entrusted to Technical Committee AUE/16, Electrical and electronic equipment, which has the responsibility to: aid enquirers to understand the text; present to the responsible international/European committee any Reference numberISO 17356-6:2006(E)INTERNATIONAL
8、 STANDARD ISO17356-6First edition2006-01-15Road vehicles Open interface for embedded automotive applications Part 6: OSEK/VDX Implementation Language (OIL) Vhicules routiers Interface ouverte pour applications automobiles embarques Partie 6: Language dexcution OSEK/VDX (OIL) BS ISO 17356-6:2006ii ii
9、iContents Page Foreword iv 0 Introduction . v 0.1 General remarks v 0.2 Motivation v 1 Scope . 1 2 Normative references . 1 3 Language Definition . 1 3.1 Preamble 1 3.2 General concept 2 4 ISO 17356-6 object definitions. 5 4.1 Rules 5 4.2 ISO 17356-6 objects, standard attributes and references 6 5 D
10、efinition of a particular implementation. 25 5.1 General. 25 5.2 Attribute types. 25 5.3 Reference Types . 27 5.4 Multiple values 27 5.5 Example . 27 6 Syntax and default definition. 29 6.1 ISO 17356-6 syntax . 29 6.2 Default definition of ISO 17356-6 objects and standard attributes 35 7 Description
11、 of the ISO 17356-6 objects 46 Annex A (informative) Generator hints 47 Bibliography . 48 Index 49 BS ISO 17356-6:2006iv Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International S
12、tandards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, als
13、o take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committe
14、es is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to the possi
15、bility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO 17356-6 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3, Electrical and electronic equipment. IS
16、O 17356 consists of the following parts, under the general title Road vehicles Open interface for embedded electronic equipment: Part 1: General structure and terms, definitions and abbreviated terms; Part 2: OSEK/VDX specifications for binding OS,COM and NM; Part 3: OSEK/VDX Operating System (OS);
17、Part 4: OSEK/VDX Communication (COM); Part 5: OSEK/VDX Network Management (NM); Part 6: OSEK/VDX Implementation Language (OIL). BS ISO 17356-6:2006v0 Introduction 0.1 General remarks This part of ISO 17356 refers to ISO 17356-2, ISO 17356-3 and ISO 17356-4. For a better understanding of this documen
18、t, the reader should be familiar with the contents of these other specifications. 0.2 Motivation To reach the goal of portable software, this part of ISO 17356 defines a way to describe the configuration of an application. This part of ISO 17356 only addresses a single central processing unit (CPU)
19、in an electronic control unit (ECU), not an ECU network. Figure 1 Example of development process for applications Figure 1 shows an example of a development process for applications. The ISO 17356-6 description may be handwritten or generated by a system configuration tool. There can be several ISO
20、17356-6 files, e.g.: files which contain CPU-specific configuration items (created by the supplier); and files which contain configuration items for the entire network (provided by the OEM). Sub-systems delivered in source code are compiled together with the application; others delivered as a librar
21、y are integrated by the linker. BS ISO 17356-6:2006blank1Road vehicles Open interface for embedded automotive applications Part 6: OSEK/VDX Implementation Language (OIL) 1 Scope This document describes the OSEK Implementation Language (OIL) concept for the description for ISO 17356 real-time systems
22、, capable of multitasking and communications, which can be used for motor vehicles. It is not a product description that relates to a specific implementation. General conventions, explanations of terms and abbreviations are compiled in a glossary, which is part of ISO 17356-1. 2 Normative references
23、 The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO 9899, Programming languages C ISO 17356-1, R
24、oad vehicles Open interface for embedded automotive applications Part 1: General structure and terms, definitions and abbreviated terms ISO 17356-2, Road vehicles Open interface for embedded automotive applications Part 2: OSEK/VDX specifications for binding OS, COM and NM ISO 17356-3, Road vehicles
25、 Open interface for embedded automotive applications Part 3: OSEK/VDX Operating System (OS) ISO 17356-4, Road vehicles Open interface for embedded automotive applications Part 4: OSEK/VDX Communication (COM) ISO 17356-5, Road vehicles Open interface for embedded automotive applications Part 5: OSEK/
26、VDX Network Management (NM) 3 Language Definition 3.1 Preamble The goal of this part of ISO 17356 is to provide a method to configure an application inside a particular CPU. This means for each CPU there is one ISO 17356-6 description. All system objects are described using ISO 17356-6 objects. BS I
27、SO 17356-6:20062 3.2 General concept The ISO 17356-6 description of the application is considered to be composed of a set of ISO 17356-6 objects. A CPU is a container for these objects. This part of ISO 17356 defines standard types for its objects. Each object is described by a set of attributes and
28、 references. This part of ISO 17356 defines explicitly all standard attributes for each ISO 17356-6 object. Each implementation can define additional implementation-specific attributes and references. It is possible only to add attributes to existing ISO 17356-6 objects. Creating new ISO 17356-6 obj
29、ects, or other changes to the grammar, are not allowed. All non-standard attributes (optional attributes) are considered to be fully implementation-specific and have no standard interpretation. Each implementation can limit the given set of values for attributes (e.g. restrict the possible value ran
30、ge for priorities). 3.2.1 ISO 17356-6 file structure The ISO 17356-6 description contains two parts one part for the definition of standard and implementation-specific features (implementation definition), and another for the definition of the structure of the application located on the particular C
31、PU (application definition). The ISO 17356-6 description consists of one main ISO 17356-6 file that can refer to included files (see 3.2.9). 3.2.2 Syntax The grammar rules for an ISO 17356-6 file are presented in the document using a notation similar to the Backus-Naur Form (BNF) 1, 2, see 6.1. All
32、keywords, attributes, object names, and other identifiers are case-sensitive. Comments in the BNF notation are written as C+-style comments. 3.2.3 ISO 17356-6 versions Two ISO 17356-6 sets of objects and standard attributes are defined: Full set of objects and standard attributes: ISO 17356-3 and fu
33、ll-featured ISO 17356-4, supporting the conformance classes BCC1, BCC2, ECC1, ECC2, CCCA, CCCB, CCC0, CCC1. Subset of objects and standard attributes: ISO 17356-3 with internal communication only, supporting the conformance classes BCC1, BCC2, ECC1, ECC2, CCCA, CCCB. Refer to ISO 17356-3 and ISO 173
34、56-4 for the features available with each of the abovementioned conformance classes. 3.2.4 Implementation definition For each ISO 17356-6 object, the implementation definition defines all attributes and their properties for a particular implementation. The implementation definition shall be present
35、in the ISO 17356-6 description and have to contain all standard attributes, which are listed in 4.2. The value range of those attributes may be restricted. Attribute definition is described in clause 5. Additional attributes and their properties can be defined for the objects for a particular implem
36、entation. Additional attributes are optional. BS ISO 17356-6:20063The include mechanism (see 3.2.1) can be used to define the implementation definition as a separate file. Thus, corresponding implementation definition files can be developed and delivered with particular implementations and then incl
37、uded with the application definition in users ISO 17356-6 files. An implementation of ISO 17356-6 shall support either all objects and standard attributes or a specific subset defined in 6.2.1. 3.2.5 Application definition The application definition comprises a set of objects and the values for thei
38、r attributes. Except for the ISO 17356-3, ISO 17356-4 and ISO 17356-5 objects, the application definition can contain more than one ISO 17356-6 object of a particular type. Each object is characterized by a set of attributes and their values. No attribute may appear that is not defined in the implem
39、entation definition. Attribute values shall comply with the attribute properties specified in the implementation definition. Attributes that take a single value shall only be specified once per object. Attributes that take a list of values shall be specified as multiple statements. Example for a mul
40、tiple statement: RESOURCE = RES1; RESOURCE = RES2; 3.2.6 Dependencies between attributes This part of ISO 17356 allows the expression of dependencies between attributes. To be more open to vendor-specific and standard extensions, the ISO 17356-6 syntax includes conditional attributes (parameters). T
41、his part of ISO 17356 allows infinite nesting of those dependencies. To express dependencies, ENUM and BOOLEAN attributes can be parameterized. If attributes in several sets of one conditional attribute have the same name, they shall have the same type. 3.2.7 Automatic attribute assignment Attribute
42、 values may be calculated by the generator. For these attributes, the keyword WITH_AUTO shall be used in the attributes definition in the implementation definition. In conjunction with WITH_AUTO, the attribute value AUTO is valid in the application definition and as a default value. 3.2.8 Default va
43、lues Default values are used by the generator in the case that an attribute is missing in the application definition. Default values are mandatory for optional attributes. Because the syntax of the implementation-specific part requires the definition of default values, a special default value NO_DEF
44、AULT is defined explicitly to suppress the default mechanism. In this case, the attribute shall be defined in the application part. Default values are forbidden for standard attributes except if explicitly stated otherwise in the specification. If a default value is allowed for a standard attribute,
45、 it is defined in 6.2. It is an error if a standard attribute that does not have a default value defined in the implementation definition is missing from the application definition. ISO 17356-6 grammar uses assignment in the implementation definition to specify default values. All possible combinati
46、ons of attributes with default values are shown in Table 1. The ISO 17356-6 syntax allows six combinations for the implementation-specific part and three combinations for the application part. BS ISO 17356-6:20064 Table 1 Possible combinations of attributes with default values for ENUM Implementatio
47、n part Application part param = A; param = AUTO; / nothing ENUM A, B, C param = B; param A ERROR param B ENUM A, B, C param = NO_DEFAULT; param A ERROR ERROR ENUM A, B, C param = AUTO; ERROR ERROR ERROR ENUM WITH_AUTO A, B, C param = B; param A generator-specific param B ENUM WITH_AUTO A, B, C param
48、 = NO_DEFAULT; param A generator-specific ERROR ENUM WITH_AUTO A, B, C param = AUTO; param A generator-specific generator-specific EXAMPLE IMPLEMENTATION myOS TASK UINT32 10xff STACKSIZE = 16; / If STACKSIZE is missing, / 16 is used as a default ; ; 3.2.9 Include mechanism 3.2.9.1 General The includ
49、e mechanism allows for separate definitions for some parts of this part of ISO 17356. The implementation definition can be delivered with an implementation and used (included) by the system designer. The include statement has the same syntax as in ISO 9899: #include , #include “file“. For each ISO 17356-6 tool there shall be a way to specify search-paths for include files. #include uses the search-path. #include “file“ uses the directory whe
