OSEK 实施语言 (OIL) v2.4.1：汽车电子系统生成

需积分: 5 199 浏览量更新于2024-06-27 收藏 1.23MB PDF 举报

"System Generation_OSEK_Implementation_Language(OIL)_V2.4.1" OSEK（Open Systems and the Corresponding Interfaces for Automotive Electronics）是汽车电子行业中一个旨在建立分布式控制单元开放式架构的联合项目。OIL（OSEK Implementation Language）是该项目的一个重要组成部分，用于描述具有多任务和通信能力的OSEK实时系统。OIL 2.4.1版本是这个语言的规范，发布于2003年1月23日，它替代了之前的所有版本，并且OSEK组织保留随时修改文档而不事先通知的权利。 ISO 17356是OSEK相关规范的国际标准化框架，包括以下几个部分： 1. OSEK Glossary：作为ISO 17356-1的一部分，它提供了术语的ISO风格介绍和词汇表，有助于理解和应用OSEK规范。 2. OSEK Binding Specification：基于OSEK Binding 1.4.1，ISO 17356-2涵盖了除了词汇表之外的绑定规格，确保不同组件间的兼容性。 3. OSEK OS：基于OSEK OS2.2.1，ISO 17356-3详细规定了OSEK操作系统的功能和接口，这是实现车辆控制的核心部分。 4. OSEK COM：基于OSEK COM3.0.2，ISO 17356-4定义了通信子系统，允许系统内的任务间通信和数据交换。 5. OSEK NM：基于OSEK NM2.5.2，ISO 17356-5涵盖了网络管理，负责管理和配置网络资源。 6. OSEK OIL：OIL 2.4.1是ISO 17356-6的基础，它是一种专为描述OSEK系统而设计的配置语言，用于系统生成和编译。 OIL 2.4.1规范详细阐述了如何用一种结构化的方式描述OSEK实时操作系统、通信系统、网络管理系统以及它们之间的交互。通过OIL，开发者可以定义任务、中断服务程序、定时器、事件、变量和资源，同时配置通信端口和消息，实现系统的定制化。此外，OIL还支持对软件组件的封装和重用，有利于软件的模块化和可移植性。在实际应用中，OIL文件通常与编译工具链一起使用，这些工具将OIL描述转换为特定微控制器平台的代码，以便在车辆电子系统中部署。OIL的使用有助于提高开发效率，确保软件质量，并促进不同供应商之间的互操作性。请注意，由于版权原因，本摘要并未包含OIL 2.4.1的完整内容。对于进一步的技术细节和具体语法，建议参考官方发布的文档或联系相关博主获取ISO 17356标准。

OSEK/VDX

OSEK Implementation Language

Specification 2.4.1

Implementation 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 = NO_DEFAULT;

param ÖA Generator-

specific

ERROR

ENUM WITH_AUTO [A, B, C]

param = AUTO;

param ÖA Generator-

specific

Generator-

specific

Table 2-1: Possible combinations of attributes with default values for ENUM

Example:

IMPLEMENTATION myOS {

TASK {

UINT32 [1..0xff] STACKSIZE = 16; // If STACKSIZE is missing,

// 16 is used as a default

};

2.3.9 Include mechanism

The include mechanism allows for separate definitions for some parts of OIL. The

implementation definition can be delivered with an OSEK implementation and used

(included) by the system designer.

The include statement has the same syntax as in ISO/ANSI-C:

#include <file>

#include "file"

• For each OIL tool there must be a way to specify search-paths for include files.

• #include <file> uses the search-path

• #include "file" uses the directory where the including file resides

Placement of include directives

The same rules apply as for ISO/ANSI-C, e.g. the include statement has to be on a separate

line and can appear anywhere in the description files.

OSEK/VDX OIL 2.4.1  by OSEK Page 11

OSEK/VDX

OSEK Implementation Language

Specification 2.4.1

3 OIL Object Definitions

3.1 Rules

The application configuration files must conform to some rules to be successfully processed.

These rules are:

• All objects are described using the OIL syntax.

• Each object must have a unique name. Each object may be divided into several parts.

• All object names must be accessible from the application.

• An attribute defines some object properties (for example, the task priority). Attributes that

take a single value may only be specified once per object. Attributes that take a list of

values must be specified as multiple statements.

• An object can have a set of references to other objects. Per object, there may be more than

one reference to the same type of object (e.g. more than one reference to different events,

see example in section 3.2.4.8).

• Unless stated otherwise, values must be defined for all standard attributes of all objects,

except for multiple attributes, which can be empty.

• If default values are required for standard attributes, they are specified in this document

and must not be changed.

• The

<name> non-terminal represents any ISO/ANSI-C identifier.

• The <number> non-terminal represents any integer constant. The range of integers is

determined by the target platform. Both decimal and hexadecimal integers are allowed, and

using the same notation as C. Decimal integers with leading zeroes are not allowed as they

might be misinterpreted as octal values.

• The

<string> non-terminal represents any 8-bit character sequence enclosed in double-

quotes ("), but not containing double-quotes.

• The description represents any 8-bit character sequence enclosed in double-quotes ("), but

not containing double-quotes.

• A reference defines a unidirectional link to another object (for example, the task X has to

be activated when the alarm Y expires).

• Implementation-specific additional parameters are only allowed for optional attributes. For

portability reasons, it is forbidden to define implementation-specific additional parameters

for standard attributes.

OSEK/VDX OIL 2.4.1  by OSEK Page 13

剩余63页未读，继续阅读

汽车电子助手

粉丝: 1w+
资源: 124

OSEK 实施语言 (OIL) v2.4.1：汽车电子系统生成

OSEK_System Generation_OSEK_Implementation_Language(OIL)_V2.5.0

System Generation_OSEK_Implementation_Language(OIL)_V2.2.0

OSEK_NM.rar_NM网络管理_osek_osek nm_osek nm_免费OSEK

osek implementation language

osek_vdx_networkmanagement_2.5.3.zip

osek标准_iso 17356-3-2005_part 3 osekvdx operating system (os)

OSEK操作系统在嵌入式系统设计中的作用是什么？并请简述OSEK网络管理的基本原理。

OSEK操作系统在嵌入式系统设计中承担哪些核心功能？OSEK网络管理（NM）的基本原理及其如何影响系统设计？

在OSEK/VDX标准中，如何通过OIL配置语言实现多任务并发执行单元的设置，并确保它们之间有效的通信？

OSEK操作系统在嵌入式系统设计中扮演着怎样的角色？请详细解释OSEK网络管理（NM）的基本原理及其实现策略。

最新资源