导图社区 AUTOAR4.2.2PDUR配置容器20230712A
AUTOAR4.2.2PDUR配置容器,介绍了PduRBswModules(0..*)、PduRGeneral、PduRRoutingTables的知识。
编辑于2023-08-18 16:43:20 安徽PDUR
PduRBswModules(0..*)
Each container describes a specific BSW module (upper/CDD/lower/IpduM) that the PDU Router shall interface to. The reason to have it as own configuration container instead of implication of the routing path is to be able to configure CDDs properly and to force module's to be used in a post-build situation even though no routing is made to/from this module (future configurations may include these modules).
PduRCancelReceive
Specifies if the Transport protocol module supports the CancelReceive API or not. Value true the API is supported.
EcucBooleanParamDef
PduRCancelTransmit
Specifies if the BSW module supports the CancelTransmit API or not. Value true the API is supported
EcucBooleanParamDef
PduRChangeParameterApi
This parameter, if set to true, enables the PduR_<Up>ChangeParameter Api for this Module.
EcucBooleanParamDef
PduRCommunicationInterface
Specifies if the BSW module supports the Communication Interface APIs or not. Value true the APIs are supported. A module can have both Communication Interface APIs and Transport Protocol APIs (e.g. the COM module).
EcucBooleanParamDef
PduRLowerModule
The PduRLowerModule will decide who will call the APIs and who will implement the APIs. For example, if the CanIf module is referenced then the PDU Router module will implement the PduR_CanIfRxIndication API. And the PDUR module will call the CanIf_Transmit API. Other APIs are of course also covered. An upper module can also be an lower module (e.g. the IpduM module).
EcucBooleanParamDef
PduRRetransmission
If set to true this means that the destination transport protocol module will use the retransmission feature. This parameter might be set to false if the retransmission feature is not used, even though the destination transport protocol is supporting it. This parameter is only valid for transport protocol modules and gateway operations. If transmission from a local upper layer module this module will handle the retransmission.
EcucBooleanParamDef
PduRTransportProtocol
The PDU Router module shall use the API parameters specified for transport protocol interface.
EcucBooleanParamDef
PduRTriggertransmit
Specifies if the BSW module supports the TriggerTransmit API or not. Value true means that the BSW module supports the TriggerTransmit interface which a lower layer module can call and also that it can call the TriggerTransmit interface of an upper layer module. Value false means that the BSW module does not support the TriggerTransmit interface which a lower layer module can call and also that it shall not call the TriggerTransmit interface of an upper layer module.
EcucBooleanParamDef
PduRTxConfirmation
Specifies if the BSW module supports the TxConfirmation API or not. Value true the API is supported.
EcucBooleanParamDef
PduRUpperModule
The PduRUpperModule will decide who will call the APIs and who will implement the APIs. For example, if the COM module is referenced then the PDU Router module will implement the PduR_Transmit API. And the PDUR module will call the Com_RxIndication API. Other APIs are of course also covered. An upper module can also be an lower module (e.g. the IpduM module)
EcucBooleanParamDef
PduRUseTag
This parameter, if set to true, enables the usage of the tag (<up>) in the following API calls: PduR_<Up>CancelReceive PduR_<Up>CancelTransmit PduR_<Up>ChangeParameter Example: If used by COM and the parameter is enabled the PduR_ComCancelTransmit is used. The background is that upper layer modules differ in usage of this tag (e.g. COM is using the tag, DCM is not).
EcucBooleanParamDef
PduRBswModuleRef
This is a reference to one BSW module's configuration (i.e. not the ECUC parameter definition template). Example, there could be several configurations of LinIf and this reference selects one of them.
Foreign reference to [ ECUC-MODULE-CONFIGURATION-VALUES ]
PduRGeneral
This container is a subcontainer of PduR and specifies the general configuration parameters of the PDU Router.
PduRDevErrorDetect
Switches the Default Error Tracer (Det) detection and notification ON or OFF. true: enabled (ON). false: disabled (OFF)
EcucBooleanParamDef
PduRMetaDataSupport(0..1)
Enable support for MetaData handling. The size of the MetaData is defined by the configuration parameter MetaDataLength of the global PDU definitions. This feature may be used for efficient CAN-CAN-routing, where the MetaData contains the CAN ID.
EcucBooleanParamDef
PduRVersionInfoApi
If true the PduR_GetVersionInfo API is available
EcucBooleanParamDef
PduRDemSupport[ETAS]
PduRInitFailed
EcucBooleanParamDef
PduRPduInstanceLost
EcucBooleanParamDef
PduRRoutingTables
Represents one table of routing paths. This routing table allows multiple configurations that can be used to create several routing tables in the same configuration. This is mainly used for post-build (e.g. post-build selectable) but can be used by pre-compile and link-time for variant handling
PduRDemEventParamenterRefs[ETAS]
PduRConfigurationId
Identification of the configuration of the PduR configuration. This identification can be read using the PduR API
EcucIntegerParamDef(0..65535)
PduRMaxRoutingPathCnt(0..1)
Maximum number of RoutingPaths in all RoutingTables. This parameter is needed only in case of post-build loadable implementation using static memory allocation
EcucIntegerParamDef(0..65535)
PduRMaxRoutingPathGroupCnt(0..1)
Maximum number of RoutingPathGroups. This parameter is needed only in case of post-build loadable implementation using static memory allocation.
EcucIntegerParamDef(0..65535)
PduRMaxRoutingTableCnt
Maximum number of RoutingTables. This parameter is needed only in case of post-build loadable implementation using static memory allocation.
EcucIntegerParamDef(0..65535)
PduRRoutingPathGroup(0..*)
This container groups routing path destinations. Destinations are used instead of routing paths since a routing path can be 1:n. It is desirable to be able to enable/disable a specific bus (i.e. a destination) rather than a routing path. Of course it is possible to create groups that covers specific routing paths as well. Enabling and disabling of routing path groups are made using the PduR API
PduRIsEnabledAtInit
If set to true this routing path group will be enabled after initializing the PDU Router module (i.e. enabled in the PduR_Init function).
EcucBooleanParamDef
PduRRoutingPathGroupId
Identification of the routing group. The identification will be used by the disable/enable API in the PDU Router module API.
EcucIntegerParamDef(0..65535)
PduRDestPduRef(1..*)
This reference selects one destination of the routing path.
Reference to [ PduRDestPdu ]
PduRRoutingTable(0..*)
Represents one container of routing paths.
PduRDestPdu(1..*)
This container is a subcontainer of PduRRoutingPath and specifies one destination for the PDU to be routed
PduRDestPduDataProvision(0..1)
Specifies how data are provided: direct (as part of the Transmit call) or via the TriggerTransmit callback function. Only required for non-TP gatewayed I-PDUs.
PDUR_DIRECT
The PDU Router module shall call the transmit function in the destination module and not buffer the I-PDU
PDUR_TRIGGERTRANSMIT
The PDU Router module shall call the transmit function in the destination module. The destination module will request the I-PDU using the triggerTransmit function. The IPDU is shall be buffered dependency: In case of PDUR_TRIGGERTRANSMIT the parameter PduRDestTxBufferRef is required.
PduRDestPduHandleId(0..1)
PDU identifier assigned by PDU Router. Used by communication interface and transport protocol modules for confirmation (PduR_<Lo>TxConfirmation) and for TriggerTransmit (PduR_<Lo>TriggerTransmit).
EcucIntegerParamDef(0..65535)
PduRTpThreshold(0..1)
This parameter is only relevant for TP routings. When configured, it enables on-the-fly routing and defines the number of bytes which must have been received before transmission on the destination bus may start. When omitted, direct TP routing is enforced. The PduRouter shall ensure that a buffer is allocated for this routing path which is at least as large as the threshold.
EcucIntegerParamDef(0..65535)
PduRTransmissionConfirmation(0..1)
This parameter is only for communication interfaces. Transport protocol modules will always call the TxConfirmation function. If set the destination communication interface module will call the TxConfirmation. However the TxConfirmation may be not called due to error. So the PduR shall not block until the TxConfirmation is called. One background for this parameter is for the PduR to know when all modules have confirmed a multicast operation.
EcucBooleanParamDef
PduRDestPduRef
Destination PDU reference; reference to unique PDU identifier which shall be used by the PDU Router instead of the source PDU ID when calling the related function of the destination module. Global PDU;EcuC AUTOSAR/EcucDefs/EcuC/EcucConfigSet/EcucPduCollection/Pdu (Proxy)
Reference to [ Pdu ]
PduRDestTxBufferRef(0..1)
Reference to a buffer that is allocated in the PduRTxBufferTable. This buffer is required for communication interface gatewaying, and for transport protocol gatewaying for single frame routing.
Reference to [ PduRTxBuffer ]
PduRDefaultValue(0..1)
Specifies the default value of the I-PDU. Only required for gateway operation and if at least one PDU specified by PduRDestPdu uses TriggerTransmit Data provision. Represented as an array of IntegerParamDef.
PduRDefaultValueElement(0..*)
Each value element is represented by the element and the position in an array
PduRDefaultValueElement
The default value consists of a number of elements. Each element is one byte long and the number of elements is specified by SduLength. The position of this parameter in the container is specified by the PduRElementBytePosition parameter.
EcucIntegerParamDef(0..255)
PduRDefaultValueElementBytePosition
EcucIntegerParamDef
PduRSrcPdu
This container is a subcontainer of PduRRoutingPath and specifies the source of the PDU to be routed.
PduRSourcePduHandleId
PDU identifier assigned by PDU Router.
EcucIntegerParamDef(0..65535)
PduRSrcPduUpTxConf(0..1)
When enabled, the TxConfirmation will be forwarded to the upper layer. Prerequisites: Lower layer and upper layer support TxConfirmation.
EcucBooleanParamDef
PduRSrcPduRef
Source PDU reference; reference to unique PDU identifier which shall be used for the requested PDU Router operation. AUTOSAR/EcucDefs/EcuC/EcucConfigSet/EcucPduCollection/Pdu (Proxy)
Reference to [ Pdu ]
PduRTpBufferTable(0..1)
This container will specify the needed buffers for gatewaying using TP. It is not connected to the specific routing path destination to allow a more efficient buffer handling
PduRTpBuffer(0..*)
Specifies a buffer used for gatwaying through TP
PduRTpBufferLength
Length of the TP buffer in number of bytes
EcucIntegerParamDef
PduRTxBufferTable(0..1)
This container contains the buffers used for gatewaying via communication interfaces and for single frames of transport protocols.
PduRTxBuffer(0..*)
Specifies a buffer used for gatewaying via communication interfaces or for single frames of transport protocols.
PduRPduMaxLength
Length of the Tx buffer in bytes. This parameter limits the size of buffered routed PDUs.
EcucIntegerParamDef
PduRTxBufferDepth