导图社区 AUTOAR4.2.2Rte置容器20230717A
- 38
- 0
- 0
- 举报
AUTOAR4.2.2Rte置容器20230717A
AUTOAR4.2.2Rte置容器，Configuration of the Rte (Runtime Environment) module.
编辑于2023-08-18 16:43:51 安徽- AUTOSAR
- RTE
- 相似推荐
- 大纲
Rte
Configuration of the Rte (Runtime Environment) module
RteBswGeneral
General configuration parameters of the Bsw Scheduler section.
RteSchMVersionInfoApi
Enables the generation of the SchM_GetVersionInfo() API.
EcucBooleanParamDef
RteUseComShadowSignalApi
This parameter defines whether the ComShadowSignalAPIs ((Com_UpdateShadowSignal, Com_InvalidateShadowSignal, Com_ReceiveShadowSignal) are used or not. If this parameter is set to true the ShadowSignal APIs and Signal APIs (Com_SendSignal, Com_InvalidateSignal, Com_ReceiveSignal) are used. If this parameter is set to false only the Signal APIs (Com_SendSignal, Com_InvalidateSignal, Com_ReceiveSignal) are used.
EcucBooleanParamDef
RteBswModuleInstance(0..*)
Represents one instance of a Bsw-Module configured on one ECU
RteBswImplementationRef
Reference to the BswImplementation for which the Rte /SchM is configured.
Foreign reference to BSW-IMPLEMENTATION
RteBswModuleConfigurationRef(0..1)
Reference to the ECU Configuration Values provided for this BswImplementation.
Foreign reference to ECUC-MODULE-CONFIGURATION-VALUES
RteBswEventToTaskMapping(0..*)
Maps a BswModuleEntity onto an OsTask based on the activating BswEvent. A BswModuleEntity can be activated by more than one BswEvent and thus be mapped to more than one OsTask. In the case of a BswSchedulableEntity executed via a direct function call this RteBswEventToTaskMapping is still specified but no RteBswMappedToTaskRef element is included. The RteBswPositionInTask parameter is necessary to provide an ordering of events invoked by the same RTE API.
RteBswActivationOffset(0..1)
Activation offset in seconds.
EcucFloatParamDef
RteBswEventPredecessorSyncPointRef(0..1)
The RteBswEventPredecessorSyncPointRef is necessary to provide a cross core synchronization in case of BswEvents triggered by the same event source but mapped to tasks belonging to different partitions on different cores. The synchronization point must be reached by all referencing BswEvents before the execution in all related tasks is continued. In case of RteBswEventPredecessorSyncPointRef the BswModuleEntity activated by the mapped BswEvent is executed after the synchronization point is passed.
Reference to RteSyncPoint
RteBswEventRef
Foreign reference to BSW-EVENT
RteBswEventSuccessorSyncPointRef(0..1)
The RteBswEventSuccessorSyncPointRef is necessary to provide a cross core synchronization in case of BswEvents triggered by the same event source but mapped to tasks belonging to different partitions on different cores. The synchronization point must be reached by all referencing BswEvents before the execution in all related tasks is continued. In case of RteBswEventSuccessorSyncPointRef the BswModuleEntity activated by the mapped BswEvent is executed before the synchronization point is entered.
Reference to RteSyncPoint
RteBswImmediateRestart
When RteBswImmediateRestart is set to true the BswSchedulableEntitiy shall be immediately re-started after termination if it was activated by this BswEvent while it was already started. This parameter shall not be set to true when the mapped BswEvent refers to a BswSchedulableEntitiy which minimumStartInterval attribute is > 0
EcucBooleanParamDef
RteBswMappedToTaskRef(0..1)
Reference to the OsTask the BswSchedulableEntity activated by the RteBswEventRef is mapped to. If no reference to the OsTask is specified the BswSchedulableEntity activated by this BswEvent is executed in the context of the caller.
Reference to OsTask
RteBswPositionInTask(0..1)
Each BswSchedulableEntity activation mapped to an OsTask has a specific position within the task execution. For periodic activation this is the order of execution. For event driver activation this is the order of evaluation which actual BswSchedulableEntity has to be executed. In case of direct function calls this parameter is necessary to provide an ordering of events when several ExecutableEntities are invoked by the same RTE API.
EcucIntegerParamDef
RteBswUsedOsAlarmRef(0..1)
If an OsAlarm is used to activate the OsTask this BswEvent is mapped to it shall be referenced here.
Reference to OsAlarm
RteBswUsedOsEventRef(0..1)
If an OsEvent is used to activate the OsTask this BswEvent is mapped to it shall be referenced here
Reference to OsEvent
RteBswUsedOsSchTblExpiryPointRef(0..1)
If an OsScheduleTableExpiryPoint is used to activate the OsTask this BswEvent is mapped to it shall be referenced here
Reference to OsScheduleTableExpiryPoint
RteOsSchedulePoint(0..1)
Introduce a schedule point by explicitly calling Os Schedule service after the execution of the ExecutableEntity. The Rte generator is allowed to optimize several consecutive calls to Os schedule into one single call if the ExecutableEntity executions in between have been skipped. The absence of this parameter is interpreted as "NONE". It shall be considered an invalid configuration if the task is preemptable and the value of this parameter is not set to "NONE" or the parameter is absent.
CONDITIONAL
A Schedule Point shall be introduced at the end of the execution of this ExecutableEntity. The Schedule Point can be skipped if several Schedule Points would be called without any ExecutableEntity execution in between.
NONE
No Schedule Point shall be introduced at the end of the execution of this ExecutableEntity
UNCONDITIONAL
A Schedule Point shall always be introduced at the end of the execution of this ExecutableEntity
RteBswExclusiveAreaImpl(0..*)
Represents one ExclusiveArea of one BswImplementation. Used to specify the implementation means of this ExclusiveArea
RteBswExclusiveAreaOsResourceRef(0..1)
Optional reference to an OsResource in case RteExclusiveAreaImplMechanism is configured to OS_RESOURCE for this ExclusiveArea.
Reference to OsResource
RteBswExclusiveAreaOsSpinlockRef(0..1)
Optional reference to an OsSpinlock in case RteExclusiveAreaImplMechanism is configured to OS_SPINLOCK for this ExclusiveArea
Reference to OsSpinlock
RteBswExclusiveAreaRef
Reference to the ExclusiveArea for which the implementation mechanism shall be specified
Foreign reference to EXCLUSIVE-AREA
RteExclusiveAreaImplMechanism
To be used implementation mechanism for the specified ExclusiveArea.
ALL_INTERRUPT_BLOCKING
COOPERATIVE_RUNNABLE_PLACEMENT
OS_INTERRUPT_BLOCKING
OS_RESOURCE
OS_SPINLOCK
RteBswExternalTriggerConfig(0..*)
Defines the configuration of Inter Basic Software Module Entity Triggering
RteBswTriggerSourceQueueLength
Length of trigger queue on the trigger source side. The queue is implemented by the RTE. A value greater or equal to 1 requests an queued behavior. Setting the value of RteTriggerSourceQueueLength to 0 requests an none queued implementation of the trigger communication. If there is no RteBswTriggerSourceQueueLength configured for a Trigger Emitter the default value of 0 applies as well.
EcucIntegerParamDef
RteBswTriggerSourceRef
Reference to a Trigger instance in the role releasedTrigger of the related BSW Module instance. The referenced Trigger has to belong to the same BSW Module instance as the RteBswModuleInstance owning this parameter configures.
Foreign reference to TRIGGER
RteBswInternalTriggerConfig(0..*)
vDefines the configuration of internal Basic Software Module Entity Triggering
RteBswTriggerSourceQueueLength
Length of trigger queue on the trigger source side. The queue is implemented by the RTE. A value greater or equal to 1 requests an queued behavior. Setting the value of RteTriggerSourceQueueLength to 0 requests an none queued implementation of the trigger communication. If there is no RteBswTriggerSourceQueueLength configured for a Trigger Emitter the default value of 0 applies as well.
EcucIntegerParamDef
RteBswTriggerSourceRef
Reference to a BswInternalTriggeringPoint of the related BSW Module instance. The referenced BswInternalTriggeringPoint has to belong to the same BSW Module instance as the RteBswModuleInstance owning this parameter configures
Foreign reference to BSW-INTERNAL-TRIGGERING-POINT
RteBswRequiredClientServerConnection(0..*)
Defines the connection between one requiredClientServerEntry and one providedClientServerEntry of a BswModuleDescription. This container shall be provided on the client side of the connection.
RteBswProvidedClientServerEntryModInstRef
Reference to the RteBswModuleInstance configuration container which identifies the instance of the BSW Module. Used with the RteBswProvidedClientServerEntryRef to unambiguously identify the BswModuleClientServerEntry instance
Reference to RteBswModuleInstance
RteBswProvidedClientServerEntryRef
Reference the providedClientServerEntry for this connection.
Foreign reference to BSW-MODULE-CLIENT-SERVER-ENTRY
RteBswRequiredClientServerEntryRef
Reference the requiredClientServerEntry for this connection
Foreign reference to BSW-MODULE-CLIENT-SERVER-ENTRY
RteBswRequiredModeGroupConnection(0..*)
Defines the connection between one requiredModeGroup of this BSW Module instance and one providedModeGroup instance
RteBswProvidedModeGroupRef
References the providedModeGroupPrototype to which this requiredModeGroup shall be connected.
Foreign reference to MODE-DECLARATION-GROUP-PROTOTYPE
RteBswProvidedModeGrpModInstRef
Reference to the RteBswModuleInstance configuration container which identifies the instance of the BSW Module. Used with the RteBswProvidedModeGroupRef to unambiguously identify the ModeDeclarationGroupPrototype instance.
Reference to RteBswModuleInstance
RteBswRequiredModeGroupRef
References requiredModeGroupPrototype which shall be connected to the providedModeGroupPrototype.
Foreign reference to MODE-DECLARATION-GROUP-PROTOTYPE
RteModeDeclarationMappingSetRef(0..1)
This defines the effective ModeDeclarationMappingSet in the case that the provided ModeDeclarationGroupPrototype and the required ModeDeclarationGroupPrototype are not compatible
Foreign reference to MODE-DECLARATION-MAPPING-SET
RteBswRequiredSenderReceiverConnection(0..*)
Defines the connection between one requiredData and one providedData of a BswModuleDescription. This container shall be provided on the receiver side of the connection
RteBswProvidedDataModInstRef
Reference to the RteBswModuleInstance configuration container which identifies the instance of the BSW Module. Used with the RteBswProvidedVariableDataPrototypeRef to unambiguously identify the VariableDataPrototype instance.
Reference to RteBswModuleInstance
RteBswProvidedVariableDataPrototypeRef
Foreign reference to VARIABLE-DATA-PROTOTYPE
RteBswRequiredVariableDataPrototypeRef
Foreign reference to VARIABLE-DATA-PROTOTYPE
RteBswRequiredTriggerConnection(0..*)
Defines the connection between one requiredTrigger of this BSW Module instance and one releasedTrigger instance.
RteBswReleasedTriggerModInstRef
Reference to the RteBswModuleInstance configuration container which identifies the instance of the BSW Module. Used with the RteBswReleasedTriggerRef to unambiguously identify the Trigger instance.
Reference to RteBswModuleInstance
RteBswReleasedTriggerRef
References the releasedTrigger to which this requiredTrigger shall be connected.
Foreign reference to TRIGGER
RteBswRequiredTriggerRef
References one requiredTrigger which shall be connected to the releasedTrigger.
Foreign reference to TRIGGER
RteGeneration
This container holds the parameters for the configuration of the RTE Generation.
RteBypassSupport
General switch to enable and select the bypass support method.
COMPONENT_WRAPPER
NONE
RteCalibrationSupport
The RTE generator shall have the option to switch off support for calibration for generated RTE code. This option shall influence complete RTE code at once.
DOUBLE_POINTERED
INITIALIZED_RAM
NONE
SINGLE_POINTERED
RteCodeVendorId
Holds the vendor ID of the generated Rte code
EcucIntegerParamDef
RteDevErrorDetect
EcucBooleanParamDef
RteDevErrorDetectUninit
The Rte shall detect if it is started when its APIs are called, and the BSW Scheduler shall check if it is initialized when its APIs are called scope: local dependency: Shall only be used when RteDevErrorDetect equals true.
EcucBooleanParamDef
RteGenerationMode
COMPATIBILITY_MODE
VENDOR_MODE
RteInExclusiveAreaCheckEnabled
Enables the check for RTE_E_IN_EXCLUSIVE_AREA (for blocking APIs).
EcucBooleanParamDef
RteIocInteractionReturnValue
Defines whether the return value of RTE APIs is based on RTE-IOC interaction or RTE-COM interaction.
RTE_COM
RTE_IOC
RteMeasurementSupport
The RTE generator shall have the option to switch off support for measurement for generated RTE code. This option shall influence complete RTE code at once.
EcucBooleanParamDef
RteVfbTraceEnabled
The RTE generator shall globally enable VFB tracing when RteVfbTrace is set to "true".
EcucBooleanParamDef
RteOptimizationMode
Switch between the two available optimization modes of the RTE generator
MEMORY
RUNTIME
RteVfbTraceFunction(0..*)
The RTE generator shall enable VFB tracing for a given hook function when there is a #define in the RTE configuration header file for the hook function name and tracing is globally enabled. Example: #define Rte_WriteHook_i1_p1_a_Start This also applies to VFB trace functions with a RteVfbTraceClientPrefix, e.g. Rte_Dbg_WriteHook_I1_P1_a_Start.
EcucFunctionNameDef
RteToolChainSignificantCharacters(0..1)
If present, the RTE generator shall provide the list of C RTE identifiers whose name is not unique when only the first RteToolChainSignificantCharacters characters are considered
EcucIntegerParamDef
RteValueRangeCheckEnabled
If set to true the RTE generator shall enable the value range checking for the specified VariableDataPrototypes.
EcucBooleanParamDef
RteVfbTraceClientPrefix(0..*)
Defines an additional prefix for all VFB trace functions to be generated. With this approach it is possible to have debugging and DLT trace functions at the same time.
EcucLinkerSymbolDef
RteImplicitCommunication(0..*)
Configuration of the Implicit Communication behavior to be generated.
RteCoherentAccess
If set to true the referenced VariableAccess’es of this RteImplicitCommunication container are in one CoherencyGroup. Data values for Coherent Implicit Read Access’es are read before the first reading RunnbaleEntity starts and are stable during the execution of all the reading RunnableEntitys; except Coherent Implicit Write Access’es belongs to the same Coherency Group. Data values written by Coherent Implicit Write Access’es are available for readers not belonging to the Coherency Group after the last writing RunnableEntity has terminated. Please note that a Coherent Implicit Data Access can be defined for VariableAccess’es to same and different data element. Nevertheless all Coherent Implicit Data Access’es of one Coherency Group have to be executed in the same task.
EcucBooleanParamDef
RteImmediateBufferUpdate
If set to true the RTE will perform preemption area specific buffer update immediately before (for VariableAccess in the role dataReadAccess) resp. after (for VariableAccess in the role dataWriteAccess) Runnable execution.
EcucBooleanParamDef
RteSoftwareComponentInstanceRef(1..*)
Reference to a SwComponentPrototype. This denotes the instances of the VariableAccess belonging to the RteImplicitCommunication.
Instance reference to SW-COMPONENT-PROTOTYPE context: ROO T-SW-COMPOSITION-PROTOTYPE
RteVariableReadAccessRef(0..*)
Foreign reference to VARIABLE-ACCESS
RteVariableWriteAccessRef(0..*)
Reference to the VariableAccess in the dataWriteAccess role.
Foreign reference to VARIABLE-ACCESS
RteInitializationBehavior(1..*)
Specifies the initialization strategy for variables allocated by RTE with the purpose to implement VariableDataPrototypes. The container defines a set of RteSectionInitializationPolicys and one RteInitializationStrategy which is applicable for this set. In order to support different interactions with the start up code of the ECU the RTE supports different initialization strategies for variables implementing VariableDataPrototypes. Basically the initialization can be done either by start-up code or by the Rte_Start function. Further on it is possible to avoid any initialization for data which has to be reset safe or is explicitly initialized by other SW, e.g. the RAM Blocks might be initialized by NVRAM Manager.
RteInitializationStrategy
RTE_INITIALIZATION_STRATEGY_AT_DATA_DECLARATION
Variables shall be initialized at its declaration to the value defined by the related initValue attribute
RTE_INITIALIZATION_STRATEGY_AT_DATA_DECLARATION_AND_PARTITION_RESTART
Variables shall be initialized at its declaration to the value defined by the related initValue attribute and during execution of Rte_RestartPartition to the value defined by the related initValue attribute
RTE_INITIALIZATION_STRATEGY_AT_RTE_START_AND_PARTITION_RESTART
Variables shall be initialized during execution of Rte_Start and Rte_RestartPartition to the value defined by the related initValue attribute
RTE_INITIALIZATION_STRATEGY_NONE
Variables shall not be initialized at all.
RteSectionInitializationPolicy(1..*)
This parameter describes the SectionInitializationPolicys for which a particular RTE initialization strategy applies. The SectionInitializationPolicy describes the intended initialization of MemorySections. The following values are standardized in AUTOSAR Methodology: • NO-INIT: No initialization and no clearing is performed. Such data elements must not be read before one has written a value into it. • INIT: To be used for data that are initialized by every reset to the specified value (initValue). • POWER-ON-INIT: To be used for data that are initialized by "Power On" to the specified value (initValue). Note: there might be several resets between power on resets. • CLEARED: To be used for data that are initialized by every reset to zero. • POWER-ON-CLEARED: To be used for data that are initialized by "Power On" to zero. Note: there might be several resets between power on resets.
EcucStringParamDef
RteInitializationRunnableBatch(0..*)
This container corresponds to an Rte_Init_<shortName of this container> function invoking the mapped RunnableEntities.
RteOsInteraction(1..*)
Interaction of the Rte with the Os.
RteUsedOsActiviation(0..*)
Attributes used in the activation of OsTasks and Runnable Entities.
RteActivationOsAlarmRef（0..1)
Reference to OsAlarm
RteActivationOsSchTblRef(0..1)
Reference to OsScheduleTable
RteActivationOsTaskRef(0..1)
Reference to OsTask
RteExpectedActivationOffset
Activation offset in seconds. Important: This is a requirement from the Rte towards the Os/Mcu setup. The Rte Generator shall assume this activation offset to be fulfilled.
EcucFloatParamDef
RteExpectedTickDuration
The expected tick duration in seconds which shall be configured to drive the OsScheduleTables or OsAlarm. Important: This is a requirement from the Rte towards the Os/Mcu setup. The Rte Generator shall assume this tick duration to be fulfilled
EcucFloatParamDef
RteModeToScheduleTableMapping(0..*)
RteModeScheduleTableRef
Reference to the OsScheduleTable which shall be active in the specified RteModeSchblMapModeDeclarationRefs
Reference to OsScheduleTable
RteModeSchtblMapModeDeclarationRef(1..*)
Reference to the ModeDeclarations.
Foreign reference to MODE-DECLARATION
RteModeSchtblMapBsw(0..1)
Specifies an instance of a ModeDeclarationGroupPrototype of a Bsw-Module.
RteModeSchtblMapBswInstanceRef
Reference to RteBswModuleInstance
RteModeSchtblMapBswProvidedModeGroupRef
Foreign reference to MODE-DECLARATION-GROUP-PROTOTYPE
RteModeSchtblMapSwc(0..1)
Specifies an instance of a ModeDeclarationGroupPrototype of a SwComponentPrototype.
RteModeSchtblMapSwcInstanceRef
Reference to an instance specification of a SwComponentPrototype.
Reference to RteSwComponentInstance
RteModeSchtblMapSwcPortRef
Reference to the PPortPrototype of a SwComponentPrototype.
Foreign reference to ABSTRACT-PROVIDED-PORT-PROTOTYPE
RteSyncPoint(0..*)
The RteSyncPoint is necessary to provide an cross core synchronization in case of RteEvents triggered by the same event source but mapped to tasks belonging to different partitions on different cores. The synchronization point must be reached by all referencing RteEvents before the execution in all related tasks is continued. In case of Rte(Bsw)EventSuccessorSyncPointRef the ExecutableEntity activated by the mapped event is executed before the synchronization point is entered. In case of Rte(Bsw)EventPredecessorSyncPointRef the ExecutableEntity activated by the mapped event is executed after the synchronization point is passed.
RtePostBuildVariantConfiguration(0..1)
Specifies the PostbuildVariantSets for each of the PostBuild configurations of the RTE. The shortName of this container defines the name of the RtePostBuildVariant
RtePostBuildUsedPredefinedVariant(1..*)
Reference to the PredefinedVariant element which defines the values for PostBuildVariationCriterion elements
Foreign reference to PREDEFINED-VARIANT
RteSwComponentInstance(0..*)
Representation of one SwComponentPrototype located on the to be configured ECU. All subcontainer configuration aspects are in relation to this SwComponentPrototype. The RteSwComponentInstance can be associated with either a AtomicSwComponentType or ParameterSwComponentType.
RteSoftwareComponentInstanceRef(0..1)
Reference to a SwComponentPrototype.
Foreign reference to SW-COMPONENT-PROTOTYPE
RteEventToTaskMapping(0..*)
Maps an instance of a RunnableEntity onto one OsTask based on the activating RTEEvent. In the case of a RunnableEntity executed via a direct function call this RteEventToTaskMapping is still specified but no RteMappedToTask element is included. The RtePositionInTask parameter is necessary to provide an ordering of events invoked by the same RTE API.
RteActivationOffset(0..1)
Activation offset in seconds.
EcucFloatParamDef
RteEventPredecessorSyncPointRef(0..1)
The RteEventPredecessorSyncPointRef is necessary to provide a cross core synchronization in case of RteEvents triggered by the same event source but mapped to tasks belonging to different partitions on different cores. The synchronization point must be reached by all referencing RteEvents before the execution in all related tasks is continued. In case of RteEventPredecessorSyncPointRef the RunnableEntity activated by the mapped RteEvent is executed after the synchronization point is passed.
Reference to RteSyncPoint
RteEventRef
Reference to the description of the RTEEvent which is pointing to the RunnableEntity being mapped. This allows a fine grained mapping of RunnableEntites based on the activating RTEEvent.
Foreign reference to RTE-EVENT
RteEventSuccessorSyncPointRef(0..1)
The RteEventSuccessorSyncPointRef is necessary to provide a cross core synchronization in case of RteEvents triggered by the same event source but mapped to tasks belonging to different partitions on different cores. The synchronization point must be reached by all referencing RteEvents before the execution in all related tasks is continued. In case of RteEventSuccessorSyncPointRef the RunnableEntity activated by the mapped RteEvent is executed before the synchronization point is entered.
Reference to RteSyncPoint
RteImmediateRestart
When RteImmediateRestart is set to true the RunnableEntitiy shall be immediately re-started after termination if it was activated by this RTEEvent while it was already started. This parameter shall not be set to true when the mapped RTEEvent refers to a RunnableEntity which minimumStartInterval attribute is > 0.
EcucBooleanParamDef
RteMappedToTaskRef(0..1)
Reference to the OsTask the RunnableEntity activated by the RteEventRef is mapped to. If no reference to the OsTask is specified the RunnableEntity shall be executed via a direct function call. The fact that no reference to an OsTask is specified for a RunnableEntity does not necessarily imply that every RTE generator has to support the implementation of this RunnableEntity as a direct function call. The standard set of use cases for direct function calls that has to be supported by every RTE generator is explicitly stated as requirements in this document. For further optimization RTE vendors are free to support additional scenarios of direct function call implementations that are not explicitly required in this document.
Reference to OsTask
RteOsSchedulePoint(0..1)
Introduce a schedule point by explicitly calling Os Schedule service after the execution of the ExecutableEntity. The Rte generator is allowed to optimize several consecutive calls to Os schedule into one single call if the ExecutableEntity executions in between have been skipped. The absence of this parameter is interpreted as "NONE". It shall be considered an invalid configuration if the task is preemptable and the value of this parameter is not set to "NONE" or the parameter is absent.
CONDITIONAL
A Schedule Point shall be introduced at the end of the execution of this ExecutableEntity. The Schedule Point can be skipped if several Schedule Points would be called without any ExecutableEntity execution in between.
NONE
No Schedule Point shall be introduced at the end of the execution of this ExecutableEntity
UNCONDITIONAL
A Schedule Point shall always be introduced at the end of the execution of this ExecutableEntity
RtePositionInTask(0..1)
Each RunnableEntity mapped to an OsTask has a specific position within the task execution. For periodic activation this is the order of execution. For event driver activation this is the order of evaluation which actual RunnableEntity has to be executed. In case of direct function calls this parameter is necessary to provide an ordering of events when several ExecutableEntities are invoked by the same RTE API.
EcucIntegerParamDef
RteUsedInitFnc(0..1)
The RunnableEntity is executed during initialization in the context of the Rte_Init_<InitContainer> function.
Reference to RteInitializationRunnableBatch
RteUsedOsAlarmRef(0..1)
If an OsAlarm is used to activate the OsTask this RteEvent is mapped to it shall be referenced here.
Reference to OsAlarm
RteUsedOsEventRef(0..1)
If an OsEvent is used to activate the OsTask this RteEvent is mapped to it shall be referenced here.
Reference to OsEvent
RteUsedOsSchTblExpiryPointRef(0..1)
If an OsScheduleTableExpiryPoint is used to activate the OsTask this RteEvent is mapped to it shall be referenced here.
Reference to OsScheduleTableExpiryPoint
RteVirtuallyMappedToTaskRef(0..1)
Optional reference to an OsTask where the activation of this RteEvent shall be evaluated. The actual execution of the Runnable Entity shall happen in the OsTask referenced by RteMappedToTaskRef.
Reference to OsTask
RteExclusiveAreaImplementation(0..*)
Specifies the implementation to be used for the data consistency of this ExclusiveArea.
RteExclusiveAreaImplMechanism
To be used implementation mechanism for the specified ExclusiveArea
ALL_INTERRUPT_BLOCKING
COOPERATIVE_RUNNABLE_PLACEMENT
OS_INTERRUPT_BLOCKING
OS_RESOURCE
OS_SPINLOCK
RteExclusiveAreaOsResourceRef(0..1)
Optional reference to an OsResource in case RteExclusiveAreaImplMechanism is configured to OS_RESOURCE for this ExclusiveArea.
Reference to OsResource
RteExclusiveAreaRef
Foreign reference to EXCLUSIVE-AREA
RteExternalTriggerConfig(0..*)
Defines the configuration of External Trigger Event Communication for Software Components
RteSwcTriggerSourceRef
Reference to a Trigger instance in the pPortPrototype of the related component instance. The referenced Trigger instance has to belong to the same software component instance as the RteSwComponentInstance owning this parameter configures.
Instance reference to TRIGGER context: ABSTRACT-PROVIDED-PO RT-PROTOTYPE
RteTriggerSourceQueueLength
Length of trigger queue on the trigger source side. The queue is implemented by the RTE. A value greater or equal to 1 requests an queued behavior. Setting the value of RteTriggerSourceQueueLength to 0 requests an none queued implementation of the trigger communication. If there is no RteTriggerSourceQueueLength configured for a Trigger Emitter the default value of 0 applies as well.
EcucIntegerParamDef
RteInternalTriggerConfig(0..*)
Defines the configuration of Inter Runnable Triggering for Software Components
RteSwcTriggerSourceRef
Reference to an InternalTriggeringPoint of the related component instance. The referenced InternalTriggeringPoint has to belong to the same software component instance as the RteSwComponentInstance owning this parameter configures.
Foreign reference to INTERNAL-TRIGGERING-POINT
RteTriggerSourceQueueLength
Length of trigger queue on the trigger source side. The queue is implemented by the RTE. A value greater or equal to 1 requests an queued behavior. Setting the value of RteTriggerSourceQueueLength to 0 requests an none queued implementation of the trigger communication. If there is no RteTriggerSourceQueueLength configured for a Trigger Emitter the default value of 0 applies as well.
EcucIntegerParamDef
RteNvRamAllocation(0..*)
Specifies the relationship between the AtomicSwComponentType’s NVRAMMapping / NVRAM needs and the NvM module configuration [constr_9091] RteSwNvRamMappingRef and RteSwNvBlockDescriptorRef are excluding each other d If an RteSwNvBlockDescriptorRef is defined there shall be no RteSwNvRamMappingRef, RteNvmRomBlockLocationSymboland RteNvmRamBlockLocationSymbol defined. If an RteSwNvRamMappingRef is defined there shall be no RteSwNvBlockDescriptorRef defined. c()
RteNvmBlockRef
Reference to the used NvM block for storage of the NVRAMMapping information.
Symbolic name reference to NvMBlockDescriptor
RteNvmRamBlockLocationSymbol(0..1)
This is the name of the linker object name where the NVRam Block will be mirrored by the Nvm. This symbol will be resolved into the parameter "NvmRamBlockDataAddress" from the "NvmBlockDescriptor
EcucLinkerSymbolDef
RteNvmRomBlockLocationSymbol(0..1)
This is the name of the linker object name where the NVRom Block will be accessed by the Nvm. This symbol will be resolved into the parameter "NvmRomBlockDataAddress" from the "NvmBlockDescriptor"
EcucLinkerSymbolDef
RteSwNvBlockDescriptorRef(0..1)
Reference to the NvBlockDescriptor in case the RTE needs to call the NvM directly (e.g. for the supportDirtyFlag feature). XOR
Foreign reference to NV-BLOCK-DESCRIPTOR
RteSwNvRamMappingRef(0..1)
Reference to the SwSeriveDependency which is used to specify the NvBlockNeeds
Foreign reference to SWC-SERVICE-DEPENDENCY
RteSwComponentType(0..*)
Representation of one SwComponentType for the base of all configuration parameter which are affecting the whole type and not a specific instance
RteBypassSupportEnabled(0..1)
Individual switch to enable the bypass support for this software component type
EcucBooleanParamDef
RteComponentTypeRef
Reference to either AtomicSwComponentType or ParameterSwComponentType.
Foreign reference to SW-COMPONENT-TYPE
RteImplementationRef(0..1)
The Implementation which shall be assigned to the SwComponentType.
Foreign reference to SWC-IMPLEMENTATION
RteComponentTypeCalibration(0..1)
Specifies for each ParameterSwComponentType or AtomicSwComponentType whether calibration is enabled. If references to SwAddrMethod are provided in RteCalibrationSwAddrMethodRef only ParameterDataPrototypes with the referenced SwAddrMethod shall have software calibration support enabled.
RteCalibrationSupportEnabled
Enables calibration support for the specified ParameterSwComponentType or AtomicSwComponentType
EcucBooleanParamDef
RteCalibrationSwAddrMethodRef(0..*)
Reference to the SwAddrMethod for which software calibration support shall be enabled.
Foreign reference to SW-ADDR-METHOD