Download GU0102 TSK51x/TSK52x RTOS
Transcript
3 The OSEK/VDX Implementation Language (OIL) Summary 3.1 This chapter describes how you can configure your application with a file written in OIL (Osek Implementation Language) language (which needs to be added to the project as a project member). The chapter ends with a working example of an OIL file. Why an OIL Language Purpose of the OIL language The OSEK/VDX Implementation Language (OIL) language is used to configure the RTOS library. An OIL configuration file contains the definition of the application. The usage of OIL to configure OSEK/VDX systems enhances the portability of RTOS applications among different target processors. Hand-coded or generated Depending on the OSEK/VDX implementation you must either write the OIL file manually or you can use a graphical user interface which helps you create the OIL file. 3.2 What are the OIL System Objects? Every version of OIL language defines syntactically and semantically a set of OIL system objects. These objects are defined in the OSEK standard. One of the system objects is CPU. This serves as a container for all other objects. Objects are defined by their attributes. Refer to http://www.osek-vdx.org/mirror/oil25.pdf for detailed information. 3.2.1 Standard and Non-Standard Attributes Every OIL system object has attributes that can hold values. According to the OIL standard, each object has at least a minimum mandatory set of attributes, called the standard attributes. Besides the standard attributes, an OSEK/VDX implementation may define additional attributes (non-standard attributes) for any OIL system object. To configure a system for an specific OSEK/VDX implementation you need to instantiate and/or define OIL objects and assign values to their attributes. 3-1