AUTOSAR OS V4.0：多核标准与操作系统规范

5星 · 超过95%的资源需积分: 38 196 浏览量更新于2024-07-25 13 收藏 1.77MB PDF 举报

AUTOSAR OS V4.0 是一个针对多核系统的标准操作系统规格，它在第四代AUTOSAR平台中得到了扩展和完善。该文档详细阐述了操作系统的功能、设计和实施，特别是针对多核架构的支持。以下是一些关键知识点： 1. **多核支持**：从V5.0.0版本开始，AUTOSAR OS V4.0正式纳入了对多核系统的标准化描述。这包括对多核心操作系统架构的集成，旨在优化资源管理和任务调度，以充分利用现代硬件的并行处理能力。 2. **服务扩展**：在V4.0.0版本中，增加了操作系统的服务内容，如第12章所述，可能涉及新的功能和服务接口，以便于软件开发者构建更复杂和高效的系统。 3. **应用状态管理**：章节8和10.4的修订反映了对操作系统应用程序状态的更深入理解，允许其他应用动态地确定其活动状态，增强了系统的灵活性和响应性。 4. **配置调整**：从3.1.0版到V4.0，删除了"OsAppModeId"参数，表明对操作系统配置进行了简化或优化。同时，引入了可选的OsAlarm, OsTask等引用，可能是为了更好地整合不同类型的系统组件。 5. **澄清和文档细节**：在不同版本中，文档针对7.8.1和7.1.2.1等部分进行了澄清，明确了“do nothing”和OSEK声明的含义，以及对文档语言进行了一些小的修正，确保了规范的准确性和一致性。 6. **法律免责声明修订**：随着版本更新，文档中的法律免责声明也相应调整，以适应不断变化的法规和行业标准。 AUTOSAR OS V4.0是一个重要的里程碑，它为多核环境下的AUTOSAR系统提供了全面的基础，使得车辆电子控制单元（ECU）的设计和实现更加高效和可靠。这对于汽车行业来说，意味着更高效的硬件利用、更快的响应时间和更强的系统安全性。开发者可以利用这些规范来开发满足当前和未来汽车技术需求的高性能嵌入式操作系统。

Specification of Operating System

V5.0.0

R4.0 Rev 3

16 of 230 Document ID 034: AUTOSAR_SWS_OS

- AUTOSAR confidential -

12 13 14 152 3 4 5 6 7 8 9 10 110 1

High

LOW’s Inter-arrival time

LOW’s Deadline

LOW’s Response Time

High High

Low Low Low Low

18 19 20 21 22 23 24

Low

LOW’s Execution Time

Task HIGH and Task

OW activated

Task LOW terminates

Task LOW activated

again

Figure 2.1: Definition of Timing Terminology

Specification of Operating System

V5.0.0

R4.0 Rev 3

4 Constraints and assumptions

4.1 Existing Standards

This document makes the following assumptions about the referenced related

standards and norms:

 OSEK OS [15] provides a sufficiently flexible scheduling policy to schedule

AUTOSAR systems.

 OSEK OS [15] is a mature specification and implementations are used in millions

of ECUs worldwide.

 OSEK OS [15] does not provide sufficient support for isolating multi-source

software components at runtime.

 OSEK OS [15] does not provide sufficient runtime support for demonstrating the

absence of some classes of fault propagation in a safety-case.

 OSEKtime OS [16] and the HIS Protected OSEK [22] are immature specifications

that contain concepts necessary for AUTOSAR and satisfy specific application

domains. It is the purpose of this document to identify these needs and to

recommend the use of parts (or all) of these specifications as appropriate.

4.2 Terminology

The specification uses the following operators when requirements specify multiple

terms:

NOT : negation of a single term e.g. NOT Weekend

AND : conjunction of two terms e.g. Weekend AND Saturday

OR : disjunction of two terms e.g. Monday OR Tuesday

A requirement comprising multiple terms is evaluated left to right.

The precedence rules are:

Highest Precedence NOT

Lowest Precedence AND OR

The expression NOT X AND Y means (NOT X) AND (Y)

Where operators of the same precedence are used in the same sentence, commas

are used to disambiguate. The expression X AND Y, OR Z means (X AND Y) OR Z.

4.3 Interaction with the RTE

The configuration of an AUTOSAR system [4] maps the »runnables« of a »software

component« to (one or more) tasks that are scheduled by the operating system. All

runnables in a task share the same protection boundary. In AUTOSAR, a software

component must not include an interrupt handler. A software component is therefore

implemented as runnables executing within the body of a task, or set of tasks, only.

20 of 230 Document ID 034: AUTOSAR_SWS_OS

- AUTOSAR confidential -

剩余229页未读，继续阅读

zhycd168

粉丝: 11
资源: 1

AUTOSAR OS V4.0：多核标准与操作系统规范

兼容OSEK/VDX和AUTOSAR的操作系统源码Trampoline

AUTOSAR架构以及开发流程详细介绍（Vector公司制作-中文版）

Autosar OS详细讲解文档

LPC43xx设备操作模型：autosar_os v4.0详解

AUTOSAR中的OS_RTOS概念及应用

autosar_rs_safety下载

autosar_sws_timesyncovercan

autosar_tr_cimplementationrules

autosar_prs_secocprotocol

autosar_mod_ecuconfigurationparameters

最新资源