Specification of RTE Software (`RTE`)¶

属性	值
平台	CP
类别	SWS — 软件模块规范（Software Specification）
UID	084
规范版本	R25-11

本地文件¶

规范 PDF: F:\Work\Standards\01_Sources\CP_SWS_RTE_084\AUTOSAR_CP_SWS_RTE.pdf
ARXML 模型: F:\Work\Standards\01_Sources\CP_SWS_RTE_084\AUTOSAR_CP_SWS_RTE.arxml
纯文本全文: F:\Work\Standards\01_Sources\CP_SWS_RTE_084\zzgen\CP_SWS_RTE.complete.txt

文档简介¶

This document contains the software specification of the AUTOSAR Run-Time Environment (RTE) and the Basic Software Scheduler. Basically, the RTE together with the OS, AUTOSAR COM and other Basic Software Modules is the implementation of the Virtual Functional Bus concepts (VFB, ). The RTE implements the AUTOSAR Virtual Functional Bus interfaces and thereby realizes the communication between AUTOSAR software-components.

This document describes how these concepts are realized within the RTE. Furthermore, the Application Programming Interface (API) of the RTE and the interaction of the RTE with other basic software modules is specified.

The Basic Software Scheduler offers concepts and services to integrate Basic Software Modules Hence, the Basic Software Scheduler

embed Basic Software Module implementations into the AUTOSAR OS context
trigger main processing functions of the Basic Software Modules
apply data consistency mechanisms for the Basic Software Modules
to communicate modes between Basic Software Modules

模块依赖¶

The main documents that served as input for the specification of the RTE are the specification of the Virtual Functional Bus and the specification of the Software Component Template . Also of primary importance are the specifications of those Basic Software modules that closely interact with the RTE (or vice versa). These are especially the communication module and the operating system . The main input of an RTE generator is described (among others) in the ECU Configuration Description. Therefore, the corresponding specification is also important for the RTE specification. Furthermore, as the process of RTE generation is an important part of the overall AUTOSAR Methodology, the corresponding document is also considered.

The following list shows the specifications that are closely interdependent to the specification of the RTE:

Specification of the Virtual Functional Bus
Specification of the Software Component Template
Specification of AUTOSAR COM
Specification of AUTOSAR OS
Specification of ECU State Manager and Communication Manager
Specification of ECU Configuration
Specification of System Description / Generation
AUTOSAR Methodology
Specification of BSW Module Description Template
AUTOSAR Generic Structure Template

章节详细内容¶

1. Note on XML 示例¶

原文标题：Note on XML examples

This specification includes examples in XML based on the AUTOSAR metamodel available at the time of writing. These examples are included as illustrations of configurations and their expected outcome but should not be considered part of the specification.

2. 简介¶

原文标题：Introduction

This document contains the software specification of the AUTOSAR Run-Time Environment (RTE) and the Basic Software Scheduler. Basically, the RTE together with the OS, AUTOSAR COM and other Basic Software Modules is the implementation of the Virtual Functional Bus concepts (VFB, ). The RTE implements the AUTOSAR Virtual Functional Bus interfaces and thereby realizes the communication between AUTOSAR software-components.

This document describes how these concepts are realized within the RTE. Furthermore, the Application Programming Interface (API) of the RTE and the interaction of the RTE with other basic software modules is specified.

The Basic Software Scheduler offers concepts and services to integrate Basic Software Modules Hence, the Basic Software Scheduler

embed Basic Software Module implementations into the AUTOSAR OS context
trigger main processing functions of the Basic Software Modules
apply data consistency mechanisms for the Basic Software Modules
to communicate modes between Basic Software Modules

3. 范围¶

原文标题：Scope

This document is intended to be the main reference for developers of an RTE generator tool or of a concrete RTE implementation respectively. The document is also the reference for developers of AUTOSAR software-components and basic software modules that interact with the RTE, since it specifies the application programming interface of the RTE and therefore the mechanisms for accessing the RTE functionality. Furthermore, this specification should be read by the AUTOSAR working groups that are closely related to the RTE (see Section below), since it describes the interfaces of the RTE to these modules as well as the behavior / functionality the RTE expects from them.

This document is structured as follows. After this general introduction, Chapter gives a more detailed introduction of the concepts of the RTE. Chapter describes how an RTE is generated in the context of the overall AUTOSAR methodology. Chapter is the central part of this document. It specifies the RTE functionality in detail. The RTE API is described in Chapter .

4. Dependency to other AUTOSAR specifications¶

The main documents that served as input for the specification of the RTE are the specification of the Virtual Functional Bus and the specification of the Software Component Template . Also of primary importance are the specifications of those Basic Software modules that closely interact with the RTE (or vice versa). These are especially the communication module and the operating system . The main input of an RTE generator is described (among others) in the ECU Configuration Description. Therefore, the corresponding specification is also important for the RTE specification. Furthermore, as the process of RTE generation is an important part of the overall AUTOSAR Methodology, the corresponding document is also considered.

The following list shows the specifications that are closely interdependent to the specification of the RTE:

5. 缩略语¶

原文标题：Acronyms and Abbreviations

All abbreviations used throughout this document - except the ones listed here - can be found in the official AUTOSAR glossary .

6. Technical Terms¶

All technical terms used throughout this document - except the ones listed here - can be found in the official AUTOSAR glossary or the Software Component Template Specification .

Term	Description
application mode manager	An application mode manager is an AUTOSAR software-component that provides the service of switching modes. The modes of an application mode manager do not have to be standardized.
ASCR runnable	A Runnable Entity that is triggered by at least one AsynchronousServerCallReturnsEvent.
associated Local Software Cluster Communication Plug-In	The Local Software Cluster Communication Plug-In which is assigned to a Communication Graph, ExclusiveArea, mode machine instance or distributed shared mode queue and therefore handles all accesses via RTE APIs, SchM APIs or RTE internal code.
associated Cross Software Cluster Communication Plug-In	The Cross Software Cluster Communication Plug-In which is assigned to a Communication Graph, mode machine instance and therefore handles all accesses via RTE APIs or RTE internal code.

7. Document Conventions¶

Requirements in the SRS are referenced using where is the requirement id. For example, .

Requirements in the SWS are marked with as the first text in a paragraph. The scope of the requirement is marked with the half brackets.

Constraints on the input of the RTE are marked with .

Technical terms are typeset in monospace font, e.g. Warp Core.

AUTOSAR Meta Class Names and Attributes are typeset in monospace font, e.g. ApplicationSwComponentType. As a general rule, plural forms of AUTOSAR Meta Class Names and Attributes are created by adding "s" to the singular form, e.g. PortPrototypes. By this means the document resembles terminology used in the AUTOSAR XML Schema.

AUTOSAR ECU Configuration Parameters are typeset in monospace font, e.g. RteCodeVendorId. As a general rule, plural forms of ECU Configuration Parameters are created by adding "s" to the singular form, e.g. RteEventToTaskMappings. By this means the document resembles terminology used in the ARXML file of AUTOSAR ECU Configuration Parameter Definition.

API function calls are also marked with monospace font, like Rte_EjectWarpCore.

8. 需求追踪¶

原文标题：Requirements Tracing

The following table references the requirements specified in as well as and links to the fulfillment of these. Please note that if column "Satisfied by" is empty for a specific requirement this means that this requirement is not fulfilled by this document.

Requirement	Description	Satisfied by
All Basic SW Modules shall perform a pre-processor check of the versions of all imported include files
All Basic SW Modules written in C language shall conform to the MISRA C 2025 Standard.
The Basic Software Module shall be able to initialize variables and hardware in a separate initialization function
The AUTOSAR Basic Software shall provide a microcontroller abstraction layer which provides a standardized interface to higher software layers
Unique Name of Basic Software Modules
Data types naming convention
Global variables naming convention
AUTOSAR Basic Software Modules shall not define global data in their header files, but in the C file
API naming convention
Shared code shall be reentrant
Error values naming convention
It shall be allowed to use macros instead of functions where source code is used and runtime is critical

9. RTE 概述¶

原文标题：RTE Overview

10. The RTE in the Context of AUTOSAR¶

The Run-Time Environment (RTE) is at the heart of the AUTOSAR ECU architecture. The RTE is the realization (for a particular ECU) of the interfaces of the AUTOSAR Virtual Function Bus (VFB). The RTE provides the infrastructure services that enable communication to occur between AUTOSAR software-components as well as acting as the means by which AUTOSAR software-components access basic software modules including the OS and communication service.

The RTE encompasses both the variable elements of the system infrastructure that arise from the different mappings of components to ECUs as well as standardized RTE services.

In principle the RTE can be logically divided into two sub-parts realizing:

the communication between software components
the scheduling of the software components

To fully describe the concept of the RTE, the Basic Software Scheduler has to be considered as well. The Basic Software Scheduler schedules the schedulable entities of the basic software modules. In some documents the schedulable entities are also called main processing functions.

11. AUTOSAR 概念¶

原文标题：AUTOSAR Concepts

This section introduces some important AUTOSAR concepts and how they are implemented within the context of the RTE.

12. AUTOSAR Software-components¶

In AUTOSAR, "application" software is conceptually located above the AUTOSAR RTE and consists of "AUTOSAR application software-components" that are ECU and location independent and "AUTOSAR sensor-actuator components" that are dependent on ECU hardware and thus not readily relocatable for reasons of performance/efficiency. This means that, subject to constraints imposed by the system designer, an AUTOSAR software-component can be deployed to any available ECU during system configuration. The RTE is then responsible for ensuring that components can communicate and that the system continues to function as expected wherever the components are deployed. Considering sensor/actuator software components, they may only directly address the local ECU abstraction. Therefore, access to remote ECU abstraction shall be done through an intermediate sensor/actuator software component which broadcasts the information on the remote ECU. Hence, moving the sensor/actuator software components on different ECUs, may then imply to also move connected devices (sensor/actuator) to the same ECU (provided that efficient access is needed).

13. 基础软件模块¶

原文标题：Basic Software Modules

As well as "AUTOSAR software-components" an AUTOSAR ECU includes basic software modules. Basic software modules can access the ECU abstraction layer as well as other basic software modules directly and are thus neither ECU nor location independent .

An "AUTOSAR software-component" cannot directly access basic software modules - all communication is via AUTOSAR interfaces and therefore under the control of the RTE. The requirement to not have direct access applies to all Basic Software Modules including the operating system and the communication service.

14. Communication¶

The communication interface of an AUTOSAR software-component consists of several ports (which are characterized by port-interfaces). An AUTOSAR software-component can communicate through its interfaces with other AUTOSAR software-components (whether that component is located on the same ECU or on a different ECU) or with basic software modules that have ports and runnables (i.e ServiceSwComponents, EcuAbstractionSwComponents and ComplexDeviceDriverSwComponents) and are located on the same ECU. This communication can only occur via the component's ports. A port can be categorized by either a sender-receiver or client-server port-interface. A sender-receiver interface provides a message passing facility whereas a client-server interface provides function invocation.

15. Communication Paradigms¶

The RTE provides different paradigms for the communication between software-component instances: sender-receiver (signal passing), client-server (function invocation), mode switch, and NvBlockSwComponentType interaction.

Each communication paradigm can be applied to intra-partition software-component distribution (which includes both intra-task and inter-task distribution, within the same Partition), inter-Partition software-component distribution, and inter-ECU software-component distribution. Intra-task communication occurs between runnable entities that are mapped to the same OS task whereas inter-task communication occurs between runnable entities mapped to different tasks of the same Partition and can therefore involve a context switch. Inter-Partition communication occurs between runnable entities in components mapped to different partitions of the same ECU and therefore involve a context switch and crossing a protection boundary (memory protection, timing protection, isolation on a core).

16. Communication Modes¶

The RTE supports two modes for sender-receiver communication:

Explicit - A component uses explicit RTE API calls to send and receive data elements .
Implicit - The RTE automatically reads a specified set of data elements before a runnable is invoked and automatically writes (a different) set of data elements after the runnable entity has terminated . The term "implicit" is used here since the runnable does not actively initiate the reception or transmission of data.

Implicit and explicit communication is considered in greater detail in Section .

17. Static Communication¶

Upstream requirements: ⌈ The RTE shall support static communication only. ⌋

Static communication includes only those communication connections where the source(s) and destination(s) of all communication is known at the point the RTE is generated. . This includes also connections which are subject to variability because the variant handling concept of AUTOSAR does only support the selection of connectors from a superset of possible connectors to define a particular variant. Dynamic reconfiguration of communication is not supported due to the run-time and code overhead which would therefore limit the range of devices for which the RTE is suitable.

18. Multiplicity¶

As well as point to point communication (i.e. "1:1") the RTE supports communication connections with multiple providers or requires:

When using sender-receiver communication, the RTE supports both "1:n" (single sender with multiple receivers) and "n:1" (multiple senders and a single receiver) communication with the restriction that multiple senders are not allowed for mode switch notifications, see metamodel restrictions .

The execution of the multiple senders or receivers is not coordinated by the RTE. This means that the actions of different software-components are independent - the RTE does not ensure that different senders transmit data simultaneously and does not ensure that all receivers read data or receive events simultaneously. * When using client-server communication, the RTE supports "n:1" (multiple clients and a single server) communication. The RTE does not support "1:n" (single client with multiple servers) client-server communication.

Irrespective of whether "1:1", "n:1" or "1:n" communication is used, the RTE is responsible for implementing the communication connections and therefore the AUTOSAR software-component is unaware of the configuration.

19. Concurrency¶

AUTOSAR software-components have no direct access to the OS and hence there are no "tasks" in an AUTOSAR application. Instead, concurrent activity within AUTOSAR is based around RunnableEntitys within components that are invoked by the RTE.

The AUTOSAR VFB specification defines a runnable entity as a "sequence of instructions that can be started by the Run-Time Environment". A component provides usually one or more runnable entities and each runnable entity has exactly one entry point. An entry point defines the symbol within the software-component's code that provides the implementation of a runnable entity.

The RTE is responsible for invoking runnable entities - AUTOSAR software-components are not able to (dynamically) create private threads of control. Hence, all activity within an AUTOSAR application is initiated by the triggering of runnable entities by the RTE as a result of RTEEvents.

An RTEEvent encompasses all possible situations that can trigger execution of a runnable entity by the RTE. The different classes of RTEEvent are defined in Section .

20. The RTE Generator¶

The RTE generator is one of a set of tools that create the realization of the AUTOSAR virtual function bus for an ECU based on information in the ECU Configuration Description. The RTE Generator is responsible for creating the AUTOSAR software-component API functions that link AUTOSAR software-components to the OS and manage communication between AUTOSAR software-components and between AUTOSAR software-components and basic software modules.

Additionally the RTE Generator creates both the Basic Software Scheduler and the Basic Software Scheduler API functions for each particular instance of a Basic Software Module.

The RTE generation process for SWCs has two main phases:

RTE Contract phase - a limited set of information about a component, principally the AUTOSAR interface definitions, is used to create an application header file for a component type. The application header file defines the "contract" between component and RTE.
RTE Generation phase - all relevant information about components, their deployment to ECUs and communication connections is used to generate the RTE and optionally the Ioc configuration . One RTE is generated for each ECU in the system.

21. 设计 Decisions¶

原文标题：Design Decisions

This section details decisions that affect both the general direction that has been taken as well as the actual content of this document.

The role of this document is to specify RTE behavior, not RTE implementation. Implementation details should not be considered to be part of the RTE software specification unless they are explicitly marked as RTE requirements.¶

An AUTOSAR system consists of multiple ECUs each of which contains an RTE that may have been generated by different RTE generators. Consequently, the specification of how RTEs from multiple vendors interoperate is considered to be within the scope of this document.¶

The RTE does not have sufficient information to be able to derive a mapping from runnable entity to OS task. The decision was therefore taken to require that the mapping be specified as part of the RTE input.¶

Support for CPP is provided by making the C RTE API available for CPP components rather than specifying a completely separate object-oriented API.¶

22. RTE Generation Process¶

This chapter describes the methodology of the RTE and Basic Software Scheduler generation. For a detailed description of the overall AUTOSAR methodology refer to methodology document .

Upstream requirements: ⌈ The RTE generator shall produce the same RTE API, RTE code, SchM API and SchM code when the input information is the same. ⌋

The RTE Generator gets involved in the AUTOSAR Methodology several times in different roles. Technically the RTE Generator can be implemented as one tool which is invoked with options to switch between the different roles. Or the RTE Generator could be a set of separate tools. In the following section the individual applications of the RTE Generator are described based on the roles that are take, not necessarily the actual tools.

The RTE Generator is used in different roles for the following phases:

RTE Contract Phase
Basic Software Scheduler Contract Phase
PreBuild Data Set Contract Phase
Basic Software Scheduler Generation Phase
RTE Generation Phase
PreBuild Data Set Generation Phase
PostBuild Data Set Generation Phase

23. RTE Generator for Software-Components¶

In Figure the overall AUTOSAR Methodology wrt. Application SW-Components and the RTE Generator is shown.

The whole vehicle functionality is described with means of CompositionSwComponents, SwComponentPrototypes and AtomicSwComponents . In the CompositionSwComponent descriptions the connections between the software-components' ports are also defined. Such a collection of software-components connected to each other, without the mapping on actual ECUs, is called the VFB view.

During the 'Configure System' step the needed software-components, the available ECUs and the System Constraints are resolved into a System Configuration Description. Now the SwComponentPrototypes and thus the associated AtomicSwComponents are mapped on the available ECUs.

Since in the VFB view the communication relationships between the AtomicSwComponents have been described and the mapping of each SwComponentPrototypes and AtomicSwComponents to a specific ECU has been fixed, the communication matrix can be generated. In the SwComponentType Description (using the format of the AUTOSAR Software Component Template ) the data that is exchanged through ports is defined in an abstract way.

24. RTE Generator for 基础软件 Scheduler¶

原文标题：RTE Generator for Basic Software Scheduler

In Figure the overall AUTOSAR Methodology wrt. Basis Software Scheduler and the RTE Generator interaction is shown.

The ECU Configuration phase is the start of the Basic Software Scheduler configuration where all the requirements of the different Basic Software Modules are collected. The Input information is provided in the Basic Software Module Descriptions of the individual Basic Software Modules.

The Basic Software Scheduler configuration is then generated into the Basic Software Scheduler code which is compiled and built into the Ecu executable.

25. Contract Phase¶

26. RTE Contract Phase¶

To be able to support the AUTOSAR software-component development with RTE-specific APIs the 'Component API' (application header file) is generated from the 'software-component Internal Behavior Description' (see Figure ) by the RTE Generator in the so called 'RTE Contract Phase' (see Figure ).

In the software-component Interface description - which is using the AUTOSAR Software Component Template - at least the AUTOSAR Interfaces of the particular software-component have to be described. This means the software-component Types with Ports and their Interfaces. In the software-component Internal Behavior description additionally the Runnable Entities and the RTE Events are defined. From this information the RTE Generator can generate specific APIs to access the Ports and send and receive data.

With the generated 'Component API' (application header file) the Software Component developer can provide the Software Component's source code without being concerned as to whether the communication will later be local or using some network(s).

27. 基础软件 Scheduler Contract Phase¶

原文标题：Basic Software Scheduler Contract Phase

To be able to support the Basic Software Module development with Basic Software Scheduler specific APIs the Module Interlink Header ( ) and Module Interlink Types Header ( ) containing the definitions and declaration for the Basic Software Scheduler API related to the single Basic Software Module instance is generated by the RTE Generator in the so called 'Basic Software Scheduler Contract Phase'.

The required input is

Basic Software Module Description and
Basic Software Module Internal Behavior and
Basic Software Module Implementation

Please note that in case of implemented PreCompileTime variability additionally the PreBuild Data Set Contract Phase is required to be able to compile the Basic Software Module.

28. PreBuild 数据 Set Contract Phase¶

原文标题：PreBuild Data Set Contract Phase

In the RTE PreBuild Data Set Contract Phase are the Condition Value Macros (see ) generated which are required to resolve the implemented pre-build variability of a particular software component or Basic Software Module.

The particular values are defined via PredefinedVariants. These PredefinedVariant elements containing definition of SwSystemconstValues for SwSystemconsts which shall be applied when resolving the variability during ECU Configuration.

The output of this phase is the RTE Configuration Header File . This file is required to compile a particular variant of a software component using PreCompileTime variability. The Condition Value Macros are used for the implementation of PreCompileTime variability with preprocessor statements and therefore are needed to run the C preprocessor resolving the implemented variability.

29. Edit ECU 配置 of the RTE¶

原文标题：Edit ECU Configuration of the RTE

During the configuration of an ECU the RTE also needs to be configured. This is divided into several steps which have to be performed iteratively: The configuration of the RTE and the configuration of other modules.

So first the 'RTE Configuration Editor' needs to collect all the information needed to establish an operational RTE. This gathering includes information on the software-component instances and their communication relationships, the Runnable Entities and the involved RTE-Events and so on. The main source for all this information is the 'ECU Configuration Values', which might provide references to further descriptions like the software-component description or the System Configuration description.

An additional input source is the Specification of Timing Extensions . This template can be used to specify the execution order of runnable entities (see section 'Execution order constraint'). An 'RTE Configuration Editor' can use the information to create and check the configuration of the Rte Event to Os task mapping (see section ).

30. Generation Phase¶

After the ECU has been entirely configured the generation of the actual RTE inclusive the Basic Software Scheduler part can be performed. Since all the relationships to and from the other Basic-SW modules have been already resolved during the ECU Configuration phase, the generation can be performed in parallel for all modules (see Figure ).

The Basic Software Scheduler is a part of the Rte and therefore not explicitly shown in figure .

31. 基础软件 Scheduler Generation Phase¶

原文标题：Basic Software Scheduler Generation Phase

Depending on the complexity of the ECU and the cooperation model of the different software vendors it might be required to integrate the Basic Software stand alone without software components.

Therefore the RTE Generator has to support the generation of the Basic Software Scheduler without software component related RTE fragments. The Basic Software Scheduler Generation Phase is only applicable for software builds which are not containing any kind of software components.

Upstream requirements: ⌈ In the Basic Software Scheduler Generation Phase the RTE Generator shall generate the Basic Software Scheduler without the RTE functionality. ⌋

In this case the RTE Generator generates the API for Basic Software Modules and the Basic Software Scheduling code only. When the input contains software component related information this information raises an error.

For instance:

Application Header Files are not generated for the software components contained in the ECU extract.
Mapped RTEEvents are not permitted and the runnable calls are not generated into the OS task bodies. Nevertheless all OS task bodies related to the Basic Software Scheduler configuration are generated.

32. RTE Generation Phase¶

The actual AUTOSAR software-components and Basic-SW modules code will be linked together with the RTE and Basic Software Scheduler code to build the entire ECU software.

Please note that in case of implemented PreCompileTime variability additionally the PreBuild Data Set Generation Phase is required (see section ) to be able to compile the ECU software. Further on in case of implemented post-build variability PostBuild Data Set Generation Phase is required (see section ) to be able to link the full ECU software.

The RTE Generator in the Generation Phase is also responsible to generate additional artifacts which contribute to the further build, deployment and calibration of the ECU's software.

Upstream requirements: , , ⌈ The RTE Generator in Generation Phase shall provide its Basic Software Module Description in order to capture the generated RTE's attributes. ⌋

Details about the Basic Software Module Description generation can can be found in section .

Upstream requirements: , ⌈ The RTE Generator in Generation Phase shall provide an MC-Support (Measurement and Calibration) description as part of the Basic Software Module Description. ⌋

其余 1105 章（内容从略，见纯文本全文）¶

Cluster Generation Phase
基础软件模块描述 generation
Bsw 模块描述
Bsw Internal 行为
Bsw Implementation
Com and Large 数据 Path in Com usage
Com user generation
Large 数据 Path in Com user generation
PreBuild 数据 Set Generation Phase
PostBuild 数据 Set Generation Phase
RTE 配置 interaction with other BSW 模块
RTE 功能性规范
Architectural 概念
范围
RTE and 数据类型
RTE and AUTOSAR Software-Components
Hierarchical 结构 of Software-Components
Ports, 接口 and Connections
Internal 行为
Implementation
Instantiation
范围 and background
概念 of instantiation
Single instantiation
多 instantiation
Reentrant 代码
Unambiguous object identification
多 instantiation and Per-instance 存储
RTE and AUTOSAR 服务
RTE and ECU 抽象
RTE and Complex Device 驱动
基础软件 Scheduler and 基础软件模块
a 基础软件模块的描述
基础软件接口
基础软件 Internal 行为
基础软件 Implementation
基础软件模块的多 Instances
AUTOSAR 服务 / ECU 抽象 / Complex Device Drivers
RunnableEntity / BswModuleEntity 映射
Synchronized ModeDeclarationGroupPrototype
Synchronized Trigger
RTE and 基础软件 Scheduler Implementation Aspects
范围
OS
OS Objects
基础软件 Schedulable Entities
Runnable Entities
RTE Events
BswEvents
映射 of Runnable Entities and 基础软件 Schedulable Entities to tasks (informative)
Scenario for 映射 of RunnableEntitys to tasks
Scenario 1
Scenario 2
Scenario 3
Scenario 4
Scenario 5
Scenario 6
Scenario 7
Scenario 8
Scenario 9
Monitoring of runnable execution time
TimingEvent activated runnables
同步 of TimingEvent activated runnables
BackgroundEvent activated Runnable Entities and BasicSoftware Schedulable Entities
InitEvent activated Runnable Entities
OsTaskExecutionEvent activated Runnable Entities
Activation and Start of ExecutableEntitys
Activation by direct 功能 call
Activation Offset for RunnableEntitys and BswSchedulableEntitys
Provide activating RTE event
Cyclic execution of ExecutableEntitys
Interrupt decoupling and 通知
基础通知 principles
Interrupts
Decoupling interrupts on RTE level
RTE and interrupt categories
RTE and 基础软件 Scheduler and BswExecutionContext
Interrupt decoupling for COM
数据 Consistency
通用
Communication Patterns
概念
Mechanisms to guarantee 数据 consistency
Exclusive Areas
Assignment of 数据 consistency mechanisms
InterRunnableVariables
InterRunnableVariables with implicit 行为
InterRunnableVariables with explicit 行为
Runnable Entities and 基础软件 Schedulable Entities的多 trigger
Implementation of Parameter and 数据 Elements
通用
Compatibility rules
Implementation of an 接口 element
初始化 of VariableDataPrototypes
初始化 of optional Elements
ApplicationDataType
ImplementationDataType
Initial value calculation
Measurement and Calibration
通用
定义 of Calibration Parameters
Online and offline calibration
Measurement
What can be measured
RTE 支持 for Measurement
Calibration
Calibration parameters
Separation of calibration parameters
支持 for offline calibration
支持 for online calibration：数据 emulation
数据 emulation without SW 支持 (direct access)
数据 emulation with SW 支持
Single pointered method
Double pointered method
InitRam parameter method
Arrangement of a ParameterElementGroup for pointered methods
Further 定义 for pointered methods
Calibration parameter access
Calibration parameter allocation
Calibration parameters in NVRAM
多 calibration parameters instances
Generation of McSupportData
Export of the McSupportData
Usage of the FlatMap
Common attributes of McDataInstance
Export of Measurement information
Sender-Receiver communication
Client-Server communication
InterRunnableVariable
PerInstanceMemory
Nv RAM Block
Non Volatile 数据 communication
Export Calibration information
ParameterDataPrototypes of ParameterSwComponentType
Shared ParameterDataPrototypes
Instance specific ParameterDataPrototypes
Default values for RAM Block
Export of the Calibration Method
描述 of ParameterElementGroup
McSupport 描述 of the InitRam parameter method
McSupport 描述 of the Single pointered method
McSupport 描述 of the Double pointered method
Export of Variant 处理
Access to NVRAM 数据
通用
Usage of the NvBlockSwComponentType
接口 of the NvBlockSwComponentType
Access to the NVRAM 数据
Access to the Bulk NvData
NVM 接口
数据 Consistency
Communication Paradigms
Sender-Receiver
简介
Receive Modes
Applicability
Representation in the 软件组件模板
多数据 Elements
Initial Values
多 Receivers and Senders
Implicit and Explicit 数据 Reception and Transmission
Implicit
Explicit
数据 access的概念
Transmission Acknowledgement
Communication Time-out
数据 Element Invalidation
数据 Element Invalidation in case of Inter-ECU communication
数据 Element Invalidation in case of Intra-ECU communication
Filters
缓冲
Last-is-Best-Semantics for '数据' Reception
Queueing for 'event' Reception
Queueing of 模式 switches
Operation
Inter-ECU 映射
Primitive 数据类型
Composite 数据类型
Atomicity
Fan-out
Fan-in
Sequence diagrams of Sender Receiver communication
"Never received status" for 数据 Element
"Update flag" for 数据 Element
Dynamic 数据类型
Inter-ECU communication through TP
Inter-ECU communication of arrays of bytes
COM
Large 数据 Path in COM
处理 of acknowledgment events
Meta 数据 for application
Client-Server
简介
Multiplicity
多 Clients Single Server
多 operations
Single Client 多 Server
Call Serialization
(Bsw)OperationInvokedEvents mapped to a task/ISR2
(Bsw)OperationInvokedEvents not mapped to a task/ISR2
Communication Time-out
Port-Defined argument values
缓冲
Inter-ECU and Inter-Partition Response to Request 映射
Client Identifier
SequenceCounter
Inter-ECU Response Channel Fan-Out
Parameter Serialization
Operation
Inter-ECU 映射
Atomicity
Fault 检测 and reporting
Asynchronous Client Server communication
Synchronous Client Server communication
SWC internal communication
Inter Runnable Variables
Inter-Partition communication
Inter 分区数据 communication using IOC
Inter 分区数据 communication using 基础软件 Scheduler
Accessing Com and Det in multicore/multipartition 配置
Accessing NvM in multicore/multipartition configurations
Signaling and 控制 flow 支持 for inter 分区 communication
Trusted Functions
存储 Protection and Pointer 类型 Parameters in RTE API
PortInterface Element 映射 and 数据 Conversion
PortInterface Element 映射
网络 Representation
网络 Representation with no 数据 transformation
网络 Representation with 数据 transformation
数据 Conversion
Range Checks during Runtime
Range checks at sender's side
Range checks at receiver's side
Communication 数据的Cyclic 处理
简介
Cyclic Reception of Communication 数据
传输 and Value 错误处理
错误 Reporting to Dem
传输 and Value 错误 Counters 处理
Value Bitfield 错误处理
Modes
模式 User
模式管理器
Refinement of the semantics of ModeDeclarations and ModeDeclarationGroups
Order of actions taken by the RTE / 基础软件 Scheduler upon interception of a 模式 switch 通知
Assignment of 模式 machine instances to RTE and 基础软件 Scheduler
模式 machine instances的初始化
模式 switches的通知
模式 switch acknowledgment
映射 of ModeDeclarations
Distributed Shared 模式 Queues
External and Internal Trigger
External Trigger Event Communication
简介
Trigger Sink
Trigger Source
Multiplicity
多 Trigger
多 Trigger Sinks Single Trigger Source
多 Trigger Sources Single Trigger Sink
Synchronized Trigger
Inter Runnable Triggering
Multiplicity
Inter 基础软件模块 Entity Triggering
Inter ECU Trigger Communication
Queuing of Triggers
Activation of triggered ExecutableEntities
初始化 and Finalization
初始化 and Finalization of the RTE
the 基础软件 Scheduler的初始化
初始化 of the RTE
Finalization of the RTE
Finalization of the 基础软件 Scheduler
初始化 and Finalization of AUTOSAR Software-Components
Variant 处理支持
概述
Choosing a Variant and Binding Variability
通用 impact of Binding Times on RTE generation
Choosing a particular variant
SystemDesignTime
CodeGenerationTime
PreCompileTime
LinkTime
PostBuild
Variability affecting the RTE generation
软件 Composition
Variant existence of SwComponentPrototypes
Variant existence of SwConnectors
COM related Variant existence
Variant existence of PortPrototypes
Atomic 软件组件 and its Internal 行为
RTE API which is subject to variability
Conditional API options
Runnable Entity's and RTEEvents
Conditional 存储 Allocation
NvBlockComponent and its Internal 行为
Parameter 组件
数据类型
Constants
基础软件模块 and its Internal 行为
基础软件接口
Flat Instance descriptor
Variability affecting the 基础软件 Scheduler generation
基础软件 Scheduler API which is subject to variability
基础软件 Entities
API 行为
Variability affecting SWC implementation
Development 错误
DET Report Identifiers
DET 错误 Identifiers
DET 错误 Classification
Bypass 支持
Bypass 描述
组件 wrapper method
Direct buffer access method
Extended buffer access method
Global Enable
RPT Preparation
Level 1 - Post-Build Hooking
Explicit Sender-Receiver and IRV APIs
Interaction With 数据 Conversion
Implicit Sender-Receiver and IRV
模式 APIs
Client-Server APIs
IN Parameters
OUT Parameters
IN-OUT Parameters
Level 2 - Non Post-Build Hooking
RP Enabler Flag
Level 3 - Extended Non Post-Build Hooking
Level 2 and 3 - Non Post-Build Hooking and Implicit Communication
Export
服务 Based Prototyping
Rapid Prototyping Scenarios
服务 Functions
RP Stim Enabler
集成
服务 Point IDs
Conditional RunnableEntity Invocation
Interaction with RTE-Managed buffers
Export
数据 Transformation
Execution of 转换器
转换器 for inter-ECU communication
转换器 for intra-ECU communication
转换器 Chains
Buffer 处理
接口 to 转换器
错误处理
转换器代码 Forwarding
转换器 Transaction 处理
转换器协议 Header Peeking
COM Based 转换器
RTE Reference
范围
Programming Languages
Generator Principles
Default operating 模式
Vendor 模式
Build 支持
软件组件 Namespace
Generator external 配置 switches
Unconnected R-Port check
Missing input 配置 check
Missing 初始化 values
API Principles
RTE Namespace
Direct API
Indirect API
Accessing Port 句柄
VariableAccess in the dataReadAccess and dataWriteAccess roles
Per Instance 存储
API 映射
"RTE Contract" Phase
"RTE Generation" Phase
功能 Elision
API Naming Conventions
API Parameters
Return Values
Return References
错误处理
Success Feedback
Unconnected Ports
数据 Elements
Explicit Communication
Implicit Communication
模式 Switch Ports
Client-Server
External Triggers
Non-identical port 接口
Return 类型 Std_ReturnType
RTE 模块
RTE Header 文件
Lifecycle Header 文件
Application Header 文件
文件 Name
范围
文件 Contents
Instance 句柄
Runnable Entity Prototype
Initial Values
PerInstanceMemory
RTE-Component 接口
Application 错误
RTE 类型 Header 文件
文件 Contents
Classification of Implementation 数据类型
Primitive Implementation 数据类型
Array Implementation 数据类型
结构 Implementation 数据类型
Union Implementation 数据类型
Implementation 数据类型 redefinition
Pointer Implementation 数据类型
ImplementationDataTypes with VariationPoints
Naming of 数据类型
C/CPP
RTE 数据句柄类型 Header 文件
文件 Name
文件 Contents
Application 类型 Header 文件
文件 Name
范围
文件 Contents
RTE Modes
Enumeration 数据类型
Range 数据类型
Implementation 数据类型 symbols
Macros for accessing Availability Information in Structs for optional Members
VFB 追踪 Header 文件
C/CPP
文件 Contents
RTE 配置 Header 文件
C/CPP
文件 Contents
Condition Value Macros
Generated RTE
Header 文件 Usage
C/CPP
文件 Contents
组件数据 Structures
Generated API
回调
Task bodies
Lifecycle API
Reentrancy
RTE Post Build Variant Sets
示例 1：文件 Contents Rte_PBcfg.h
示例 2：文件 Contents Rte_PBcfg.h
示例：文件 Contents Rte_PBcfg.c
RTE NvM Extern Buffer Declaration 文件
RTE 数据 Structures
Instance 句柄
组件数据结构
数据句柄 Section
数据 Element without Status
数据 Element with Status
数据 Element with Extended Status
Usage
Per-instance 存储句柄 Section
Inter Runnable Variable 句柄 Section
Exclusive-area API Section
Port API Section
Calibration Parameter 句柄 Section
Inter Runnable Variable API Section
Inter Runnable Triggering API Section
Instance Id Section
RAM Block 数据 Updated 句柄 Section
Vendor Specific Section
API 数据类型
Std_ReturnType
Infrastructure 错误
Application 错误
Predefined 错误 Codes
No 错误
RTE_E_OK
Standard Application 错误 Values
RTE_E_INVALID
RTE_E_RAM_UNCHANGED
Immediate Infrastructure 错误 Codes
RTE_E_COM_STOPPED
RTE_E_TIMEOUT
RTE_E_LIMIT
RTE_E_NO_DATA
RTE_E_TRANSMIT_ACK
RTE_E_NEVER_RECEIVED
RTE_E_UNCONNECTED
RTE_E_IN_EXCLUSIVE_AREA
RTE_E_SEG_FAULT
RTE_E_OUT_OF_RANGE
RTE_E_SERIALIZATION_ERROR, RTE_E_HARD_TRANSFORMER_ERROR
RTE_E_SERIALIZATION_LIMIT, RTE_E_TRANSFORMER_LIMIT
RTE_E_SOFT_TRANSFORMER_ERROR
RTE_E_COM_BUSY
Overlayed 错误
RTE_E_LOST_DATA
RTE_E_MAX_AGE_EXCEEDED
Rte_Instance
RTE Modes
Enumeration 数据类型
Range 数据类型
数据类型 with bitfield conversions
Communication 错误 Info DataType
API Reference
Rte_Ports
Rte_NPorts
Rte_Port
Rte_Write
Rte_Send
Rte_Switch
Rte_Invalidate
Rte_Feedback
Rte_SwitchAck
Rte_Read
Rte_DRead
Rte_Receive
Rte_Call
Rte_Result
Rte_Pim
Rte_CData
Rte_Prm
Rte_IRead
Rte_IReadRef
Rte_IWrite
Rte_IWriteRef
Rte_IInvalidate
Rte_IStatus
Rte_IrvIRead
Rte_IrvIReadRef
Rte_IrvIWrite
Rte_IrvIWriteRef
Rte_IrvRead
Rte_IrvWrite
Rte_Enter
Rte_Exit
Rte_Mode
Enhanced Rte_Mode
Rte_Trigger
Rte_IrTrigger
Rte_IFeedback
Rte_IsUpdated
Rte_PBCon
Rte_IsAvailable
Rte_SetAvailable
Rte_SetMetaDataItem
Rte_GetMetaDataItem
Rte_GetMetaDataLength
Rte_IsOutOfRange
Rte_IsInvalidValue
Rte_ComDataMainFunction
Runnable Entity Reference
Signature
Entry Point Prototype
Role Parameters
Return Value
Triggering Events
TimingEvent
BackgroundEvent
SwcModeSwitchEvent
AsynchronousServerCallReturnsEvent
DataReceiveErrorEvent
OperationInvokedEvent
DataReceivedEvent
DataSendCompletedEvent
ModeSwitchedAckEvent
SwcModeManagerErrorEvent
ExternalTriggerOccurredEvent
InternalTriggerOccurredEvent
DataWriteCompletedEvent
InitEvent
TransformerErrorEvent
OsTaskExecutionEvent
Reentrancy
RTE Lifecycle API Reference
Rte_Start
Signature
Existence
描述
Return Value
Notes
Rte_Stop
Signature
Existence
描述
Return Value
Notes
Rte_Init
Signature
Existence
描述
Return Value
Notes
Rte_StartTiming
Signature
Existence
描述
Return Value
Notes
RTE Call-backs Reference
RTE-COM Message Naming Conventions
Communication 服务 Call-backs
Call-backs for communication over AUTOSAR COM
Rte_COMCbk
Rte_COMCbkTAck
Rte_COMCbkTErr
Rte_COMCbkInv
Rte_COMCbkRxTOut
Rte_COMCbkTxTOut
Rte_COMCbkTxPrep_
Call-backs for communication over AUTOSAR Large 数据 Path in COM
Rte_COMCbkRxIndication
Rte_COMCbkStartOfReception
Rte_COMCbkCopyRxData
Rte_COMCbkTpRxIndication
Rte_COMCbkCopyTxData
Rte_COMCbkTpTxConfirmation
Rte_COMCbkTriggerTransmit
Rte_COMCbkTxConfirmation
NVM 服务 Call-backs
Rte_SetMirror
Rte_GetMirror
Rte_NvMNotifyJobFinished
Rte_NvMNotifyInitBlock
Expected 接口
Expected 接口 from Com
Expected 接口 from Os
Expected 接口 for 数据 Transformation
Expected 接口 from NvM
VFB 追踪 Reference
Principle of Operation
支持 for 多 clients
支持 for 多 Instantiation
Contribution to the 基础软件模块描述 and the client's 配置
Trace Events
RTE API Trace Events
RTE API Start
RTE API Return
BSW Scheduler API Trace Events
BSW Scheduler API Start
BSW Scheduler API Return
模式 Switch Trace Events
RTE 模式 Switch Request Terminate API
BSW Scheduler 模式 Switch Request Terminate API
COM Trace Events
Signal Transmission
Signal Reception
Signal Invalidation
Signal Group Invalidation
COM Callback
OS Trace Events
Task Activate
Task Dispatch
Task Termination
Set OS Event
Wait OS Event
Received OS Event
Runnable Entity Trace Events
Runnable Entity Invocation
Runnable Entity Termination
BSW Schedulable Entities Trace Events
BSW Schedulable Entity Invocation
BSW Schedulable Entity Termination
RPT Trace Events
Transmission
Reception
配置
Interaction with Object-code Software-Components
基础软件 Scheduler Reference
范围
API Principles
基础软件 Scheduler Namespace
BSW Scheduler Name Prefix and Section Name Prefix
BSW Scheduler API options
基础软件 Scheduler 模块
模块 Interlink 类型 Header
文件 Name
范围
文件 Contents
基础软件 Scheduler Modes
模块 Interlink Header
文件 Name
范围
文件 Contents
Entry Point Prototype
基础软件 Scheduler - 基础软件模块接口
Provide activating Bsw event
RunnableEntity mapped to BswModuleEntity
Condition Value Macros
API 数据类型
Predefined 错误 Codes for Std_ReturnType
SCHM_E_OK
SCHM_E_LIMIT
SCHM_E_NO_DATA
SCHM_E_TRANSMIT_ACK
SCHM_E_IN_EXCLUSIVE_AREA
SCHM_E_TIMEOUT
SCHM_E_LOST_DATA
基础软件 Modes
Enumeration 数据类型
Range 数据类型
数据类型 with bitfield conversions
API Reference
SchM_Enter
SchM_Exit
SchM_Call
SchM_Result
SchM_Send
SchM_Receive
SchM_Switch
SchM_Mode
Enhanced SchM_Mode
SchM_SwitchAck
SchM_Trigger
SchM_ActMainFunction
SchM_CData
SchM_Pim
Bsw 模块 Entity Reference
Signature
Entry Point Prototype
Reentrancy
Provide activating Bsw event
基础软件 Scheduler Lifecycle API Reference
SchM_Init
SchM_Start
SchM_StartTiming
SchM_Deinit
RTE Implementation Plug-Ins Reference
简介
RTE Implementation Plug-Ins in the AUTOSAR 架构
多 RTE Implementation Plug-Ins 处理 one Communication Graph
接口 between RTE Implementation Plug-Ins and RTE
文件结构
RTE Global Buffer Declaration 文件
RIPS Buffer Declaration Files
RTE Implementation Plug-In Header 文件
RIPS SWC-BSW-Instance Header 文件
RTE Implementation Plug-In Implementation 文件
RTE Header 文件
Application Header 文件
模块 Interlink Header
RTE 数据句柄类型 Header 文件
API principles
API name pattern
基础需求 on RTE Implementation Plug-In 服务
基础需求 on RTE Implementation
Macro API implementations
API 数据类型
API Reference
Implicit buffer value access
Rte_Rips_IRead
Rte_Rips_IWrite
Implicit buffer address access
Rte_Rips_IRBufferRef
Rte_Rips_IWBufferRef
Implicit communication buffer Fill Flush Routines
Rte_Rips_FillFlushRoutine
Explicit access protection
Rte_Rips_StartRead
Rte_Rips_StopRead
Rte_Rips_StartWrite
Rte_Rips_StopWrite
Explicit 数据 access 服务
Rte_Rips_Read
Rte_Rips_Write
Rte_Rips_DRead
ExclusiveArea protection
Rte_Rips_Enter
Rte_Rips_Exit
模式 queue protection functions
Rte_Rips_EnterModeQueue
Rte_Rips_ExitModeQueue
Cross cluster 模式 communication functions
Rte_Rips_Switch
Rte_Rips_DequeueModeSwitch
Distributed Shared 模式 Queue 调度同步 functions
Rte_Rips_DsmqSwitch
Rte_Rips_DsmqTransitionStart
Rte_Rips_DsmqTransitionSync
Rte_Rips_DsmqTransitionEnd
Server 功能 Invocations
Rte_Rips_Invoke
Rte_Rips_ReturnResult
Rte_Rips_InvocationHandler
Signal 通知 for 转换器
Rte_Rips_NotifyRxAck
Rte_Rips_NotifyRxTOut
Rte_Rips_NotifyTxAck
Rte_Rips_NotifyTxErr
Rte_Rips_NotifyTxTOut
Rte_Rips_NotifyRxIndication
Rte_Rips_NotifyTriggerTransmit
Rte_Rips_NotifyTxConfirmation
Rte_Rips_NotifyCopyRxData
Rte_Rips_NotifyCopyTxData
Rte_Rips_NotifyStartOfReception
Rte_Rips_NotifyTpRxIndication
Rte_Rips_NotifyTpTxConfirmation
Cross cluster trigger communication functions
Rte_Rips_Trigger
数据 and Event 通知
Rte_Rips_Feedback
Rte_Rips_DataIsUpdated
Rte_Rips_DataIsUpdated_EventActivation
External Parameter Access
Rte_Rips_Prm
RTE Implementation Plug-In Lifecycle API
Rte_Rips_SchM_Init
Rte_Rips_Rte_Start
Rte_Rips_Rte_Stop
Rte_Rips_SchM_Deinit
RTE Implementation Plug-Ins 功能性规范
Specializations of AtomicSwComponentTypes
Interaction with VFB 追踪
校验 Strategy for RTE Implementation Plug-Ins
Graduated 校验 Strategy
校验 Implication w.r.t. Exclusive Areas
校验 Implication w.r.t. Event To Task 映射
校验 Implication w.r.t. communication multiplicity
数据 Communication
Enable RTE Implementation Plug-In 支持 for communication graphs
Details on RIPS FlatInstanceDescriptors for 数据 Communication Graphs
数据 Communication Graphs involving NvBlockSwComponents
处理 of Communication Status and Conversion with RTE Implementation Plug-Ins
Instantiation of global copy
Explicit Communication and RTE Implementation Plug-Ins
Global copy provided by RTE
Simple 示例 about non-queued read and write
Simple 示例 about queued read and write
Global copy provided by RTE Implementation Plug-In
Implicit Communication and RTE Implementation Plug-Ins
Fill Flush Routines
Simple 示例 about implicit w/o 组件数据结构
object 代码软件组件 with conversion的示例
Inter Runnable Variables and RTE Implementation Plug-Ins
RTE Implementation Plug-Ins and NvBlockSwComponents
示例 about source 代码软件组件 with complex call tree and NV 数据
Exclusive Areas
Exclusive Areas and RTE Implementation Plug-Ins
Enable RTE Implementation Plug-In 支持 for ExclusiveAreas
Exclusive Areas in Role canEnter
Exclusive Areas in Role runsInside
Modes
Modes and Local 软件 Cluster Communication Plug-In
Modes and Cross 软件 Cluster Communication Plug-In
Enable RTE Implementation Plug-In 支持 for 模式 machine instances
Cross 软件 Cluster Communication Plug-In 支持 for 模式 communication
Rte_Rips_Switch indication
Rte_Rips_DequeueModeSwitch indication
Enable RTE Implementation Plug-In 支持 for distributed shared 模式 queues
RTE Implementation Plug-In 支持 for distributed shared 模式 queues
DSMQ transition OsTask activation
Rte_Rips_DsmqSwitch indication
Rte_Rips_DsmqTransitionStart indication
Rte_Rips_DsmqTransitionSync indication
Rte_Rips_DsmqTransitionEnd indication
Parameters
Enable RTE Implementation Plug-In 支持 for Parameter Communication Graphs
Instantiation of parameter
软件组件 Implementation
检测 of source 代码 vs. object 代码软件 components
软件 sharing and RTE Implementation Plug-Ins
Client Server Communication
Enable RTE Implementation Plug-In 支持 for client server Communication
Trigger Communication
Enable RTE Implementation Plug-In 支持 for triggers
Trigger and Cross 软件 Cluster Communication Plug-In
Rte_Rips_Trigger indication
Transformers
DataTransformation for 数据 Communication Graphs的处理
处理 of Client Server Communication Graphs and Trigger Communication Graphs
Measurement
Measurement on 数据 Communication Graphs
Measurement on Parameter Communication Graphs
Inter-Partition communication
Bypass 支持
组件 wrapper method
Direct buffer access method
Extended buffer access method
Activation of RTEEvents and BswEvents
RTE ECU 配置
RTE 模块配置
RTE 配置 Version Information
RTE Generation Parameters
RTE PreBuild 配置
RTE PostBuild 配置
软件组件 instances的处理
RTE Event to task/ISR 映射
Evaluation and execution order
Direct and trusted 功能 call
调度 Points
Timeprotection 支持
Os Interaction
Background activation
Constraints
Rte Os Interaction
Activation using Os features
Modes and 调度 Tables
Exclusive Area implementation
NVRam Allocation
SWC Trigger queuing
SWC 模式 Machine Instance 配置
软件组件类型的处理
Selection of Software-Component Implementation
组件类型 Calibration
Implicit communication 配置
Exclusive access optimization
Communication infrastructure
配置 of the BSW Scheduler
BSW Scheduler 通用配置
BSW 模块 Instance 配置
BSW ExclusiveArea 配置
BswEvent to task 映射
BswEvent to ISR2 映射
BSW Trigger 配置
BSW Trigger connection
BSW Trigger queuing
BSW ModeDeclarationGroup 配置
BSW Client Server 配置
BSW Sender Receiver 配置
BSW 模式 Machine Instance 配置
同步 Points的配置
初始化的配置
配置 of Task Chains
distributed shared 模式 queues的配置
配置 of RTE Implementation Plug-Ins
通用配置定义 for Uri References
通用配置 of RTE Implementation Plug-Ins utilization
配置 of Fill-Flush-Routines of RTE Implementation Plug-Ins
配置 of invocation handlers of RTE Implementation Plug-Ins
配置 of Com User
Com User 模块 Cnf的配置
Com 回调的配置
附录
Metamodel Restrictions
Restrictions concerning WaitPoint
Restrictions concerning RTEEvent
Restrictions concerning queued implementation policy
Restrictions concerning ServerCallPoint
软件 components的Restriction concerning 多 instantiation
Restrictions concerning runnable entity
Restrictions concerning runnables with dependencies on modes
Restriction concerning SwcInternalBehavior
Restrictions concerning Initial Value
Restriction concerning PerInstanceMemory
Restrictions concerning unconnected r-port
Restrictions concerning unconnected requiredData, requiredModeGroup, requiredTrigger and requiredClientServerEntry
Restrictions regarding communication of 模式 switch 通知
Restrictions regarding Measurement and Calibration
Restriction concerning ExclusiveAreaImplMechanism
Restrictions concerning AtomicSwComponentTypes
Restriction concerning the enableUpdate attribute of NonqueuedReceiverComSpecs
Restrictions concerning the large and dynamic 数据类型
Restriction concerning REFERENCE 类型
Restriction concerning ModeDeclarationGroup categories and value attributes
Restrictions concerning C/S 接口
Restrictions concerning S/R Features
External 需求
MISRA C Compliance
Referenced Meta Classes
Referenced ECUC 配置 Parameters
Com
ComMainFunctionTx
ComMainFunctionRx
ComGroupSignal
ComIPdu
ComSignal
ComUserModule
ComUserUriDefSet
ComUserModuleCnf
ComUserSignal
ComSignalGroup
ComUserSignalGroup
ComUserIPdu
ComUserCallback
EcuC
EcucPartition
EcucPdu
EcucPduDedicatedPartition
NvM
NvMBlockDescriptor
NvMInitBlockCallback
NvMSingleBlockCallback
NvMTargetBlockReference
Os
OsAlarm
OsApplication
OsAlarmCallback
OsCounter
OsEvent
OsScheduleTable
OsScheduleTableExpiryPoint
OsTask
OsIsr
OsApplicationTrustedFunction
Xfrm
XfrmImplementationMapping
示例
ModeDeclarationGroupMapping
Stability need for received 数据
CompuMethod with bitfield texttable conversion
结构类型 with self-reference
多 calibration parameters instances
PayloadAsArray for variable-size array
PayloadAsPointerToArray for variable-size array
Change history of AUTOSAR traceable items
Traceable item history of this document according to AUTOSAR Release R4.0.2
Deleted SWS Items
Changed SWS Items
Added SWS Items
Traceable item history of this document according to AUTOSAR Release R4.0.3
Deleted SWS Items
Changed SWS Items
Added SWS Items
Traceable item history of this document according to AUTOSAR Release R4.1.1
Renamed SWS Items
Added constraints
Deleted SWS Items
Changed SWS Items
Added SWS Items
Traceable item history of this document according to AUTOSAR Release R4.1.2
Added 规范 Items in 4.1.2
Changed 规范 Items in 4.1.2
Deleted 规范 Items in 4.1.2
Added Constraints in 4.1.2
Changed Constraints in 4.1.2
Deleted Constraints in 4.1.2
Traceable item history of this document according to AUTOSAR Release R4.1.3
Added 规范 Items in 4.1.3
Changed 规范 Items in 4.1.3
Deleted 规范 Items in 4.1.3
Added Constraints in 4.1.3
Changed Constraints in 4.1.3
Deleted Constraints in 4.1.3
Traceable item history of this document according to AUTOSAR Release R4.2.1
Added 规范 Items in 4.2.1
Changed 规范 Items in 4.2.1
Deleted 规范 Items in 4.2.1
Added Constraints in 4.2.1
Changed Constraints in 4.2.1
Deleted Constraints in 4.2.1
Traceable item history of this document according to AUTOSAR Release R4.2.2
Added 规范 Items in 4.2.2
Changed 规范 Items in 4.2.2
Deleted 规范 Items in 4.2.2
Added Constraints in 4.2.2
Changed Constraints in 4.2.2
Deleted Constraints in 4.2.2
Traceable item history of this document according to AUTOSAR Release R4.3.0
Added 规范 Items in 4.3.0
Changed 规范 Items in 4.3.0
Deleted 规范 Items in 4.3.0
Renamed Constraints in 4.3.0
Added Constraints in 4.3.0
Changed Constraints in 4.3.0
Deleted Constraints in 4.3.0
Traceable item history of this document according to AUTOSAR Release R4.3.1
Added 规范 Items in 4.3.1
Changed 规范 Items in 4.3.1
Deleted 规范 Items in 4.3.1
Added Constraints in 4.3.1
Changed Constraints in 4.3.1
Deleted Constraints in 4.3.1
Traceable item history of this document according to AUTOSAR Release R4.4.0
Added 规范 Items in 4.4.0
Changed 规范 Items in 4.4.0
Deleted 规范 Items in 4.4.0
Added Constraints in 4.4.0
Changed Constraints in 4.4.0
Deleted Constraints in 4.4.0
Traceable item history of this document according to AUTOSAR Release R19-11
Added 规范 Items in 19-11
Changed 规范 Items in 19-11
Deleted 规范 Items in 19-11
Traceable item history of this document according to AUTOSAR Release R20-11
Added 规范 Items in R20-11
Changed 规范 Items in R20-11
Deleted 规范 Items in R20-11
Traceable item history of this document according to AUTOSAR Release R21-11
Added 规范 Items in R21-11
Changed 规范 Items in R21-11
Deleted 规范 Items in R21-11
Traceable item history of this document according to AUTOSAR Release R22-11
Added 规范 Items in R22-11
Changed 规范 Items in R22-11
Deleted 规范 Items in R22-11
Traceable item history of this document according to AUTOSAR Release R23-11
Added 规范 Items in R23-11
Changed 规范 Items in R23-11
Deleted 规范 Items in R23-11
Added Constraints in R23-11
Changed Constraints in R23-11
Deleted Constraints in R23-11
Traceable item history of this document according to AUTOSAR Release R24-11
Added 规范 Items in R24-11
Changed 规范 Items in R24-11
Deleted 规范 Items in R24-11
Added Constraints in R24-11
Changed Constraints in R24-11
Deleted Constraints in R24-11
Traceable item history of this document according to AUTOSAR Release R25-11
Added 规范 Items in R25-11
Changed 规范 Items in R25-11
Deleted 规范 Items in R25-11
Added Constraints in R25-11
Changed Constraints in R25-11
Deleted Constraints in R25-11

Specification of RTE Software (RTE)¶