AUTOAR4.2.2EcuC置容器20230717A

AUTOAR4.2.2EcuC置容器，In the configuration of an ECU there is information which needs to be shared between multiple BSW Modules. Since it can not be defined who owns this shared information the virtual module EcuC has been introduced to the AUTOSAR ECU Configuration Parameter Definition.

AUTOSAR_TPS_ECUConfiguration.pdf

• EcuC
  • In the configuration of an ECU there is information which needs to be shared between multiple BSW Modules. Since it can not be defined who owns this shared information the virtual module EcuC has been introduced to the AUTOSAR ECU Configuration Parameter Definition. Virtual module to collect ECU Configuration specific / global configuration information. Post-Build Variant Support true
  • EcucConfigSet(0..1)
    • This container contains the configuration parameters and sub containers of the global PduCollection
    • EcucPduCollection(0..1)
      • Collection of all Pdu objects flowing through the Com-Stack. In order to support the synchronization of Handle IDs (see section 3.4.1) two modules need to be able to refer to the same Pdu object2. Therefore a generic Pdu container has been defined which does not belong to any module but is defined in the EcuC module. Since the Pdu flowing through the COM-Stack does not belong to an individual module, the "virtual" module EcuC has been introduced in the ECU Configuration. This module is used to collect configuration information not associated with any specific standardized module. The EcucPduCollection may contain several "global" Pdu objects as shown in figure 3.9. Each Pdu may either represent a FrameTriggering (for Pdus not going through the Pdu Router: UserDefinedPdus, NmPdus and NPdus) or PduTriggering (for all other Pdus) belonging to the specific ECU from the AUTOSAR System Description[2] (ECU Extract). Therefore there is an optional reference to either FrameTriggering (SysTPduToFrameTriggeringRef) or PduTriggering (SysTPduToPduTriggeringRef) element in the System Template. Either SysTPduToFrameTriggeringRef or SysTPduToPduTriggeringRef shall be used.
      • PduIdTypeEnum
        • The PduIdType is used within the entire AUTOSAR Com Stack except for bus drivers. The size of this global type depends on the maximum number of PDUs used within one software module. If no software module deals with more PDUs that 256, this type can be set to uint8. If at least one software module handles more than 256 PDUs, this type must be set to uint16. See AUTOSAR_SWS_CommunicationStackTypes for more details.
        • UINT16
        • UINT8
      • PduLengthTypeEnum
        • The PduLengthType is used within the entire AUTOSAR Com Stack except for bus drivers. The size of this global type depends on the maximum length of PDUs to be sent by an ECU. If no segmentation is used the length depends on the maximum payload size of a frame of the underlying communication system (for FlexRay maximum size is 255 bytes, therefore uint8). If segmentation is used it depends on the maximum length of a segmented N-SDU (in general uint16 is used). See AUTOSAR_SWS_CommunicationStackTypes for more details
        • UINT16
        • UINT8
        • UINT32
      • MetaDataType(0..*)
        • Meta data serves to transport information through the AUTOSAR layers. It is transported by the PduInfoType structure via a separate pointer to a byte array alongside the length of and a pointer to the payload of the PDU. This container defines the content of the meta data.
        • MetaDataItem(1..*)
          • The content of meta data in a Pdu consists of an ordered list of meta data items. This container represents a meta data item that is contained in meta data of a Pdu [TPS_ECUC_06085] Ordering of MetaDataItems of an MetaDataType d The MetaDataItems of an MetaDataType shall be ordered according to their MetaDataItemLength. MetaDataItems with greater MetaDataItemLength going first. Rationale: This ensures that all MetaDataItems will be properly aligned without any padding between individual MetaDataItems. c() [TPS_ECUC_06086] Relevance of the order of MetaDataItems of an MetaDataType d The order of MetaDataItems of an MetaDataType defines the order and position of the meta data items in the meta data array of the respective Pdu. c()
          • MetaDataItemLength
            • EcucIntegerParamDef
          • MetaDataItemType
            • ADDRESS_EXTENSION_8
              • Address extension field (N_AE) of the mixed addressing modes with 11bit and 29bit CAN ID of ISO 15765-2. Size: 8 bits.
            • CAN_ID_32
              • CAN ID according to ISO 11898-2, either 29 bits or 11 bits. Encoding according to Can_IdType. Size: 32 bits.
            • ETHERNET_MAC_64
              • Ethernet MAC address. Size: 64 bits
            • LIN_NAD_8
              • LIN node address as used in the LIN transport protocol. Size: 8 bits.
            • PRIORITY_8
              • Priority field of SAE J1939 IDs, or Ethernet QoS parameter. Size: 8 bits.
            • SOCKET_CONNECTION_ID_16
              • SoAd socket connection ID. Size: 16 bits.
            • SOURCE_ADDRESS_16
              • Source address of CanTp, FrTp, or DoIP transport protocol messages, or of SAE J1939 messages. Size: 16 bits.
            • TARGET_ADDRESS_16
              • Target address of CanTp, FrTp, or DoIP transport protocol messages, or destination address of SAE J1939 messages. Size: 16 bits.
      • Pdu(0..*)
        • One Pdu flowing through the COM-Stack. This Pdu is used by all Com-Stack modules to agree on referencing the same Pdu.
        • DynamicLength(0..1)
          • This parameter defines whether the Pdu has dynamic length (true) or not (false). Please note that the usage of this attribute is restricted by [constr_3448].
          • EcucBooleanParamDef
        • J1939Requestable(0..1)
          • Pdu can be triggered by the J1939 request message
          • EcucBooleanParamDef
        • PduLength
          • Length of the Pdu in bytes. It should be noted that in former AUTOSAR releases (Rel 2.1, Rel 3.0, Rel 3.1, Rel 4.0 Rev. 1) this parameter was defined in bits
          • EcucIntegerParamDef
        • SysTPduToFrameTriggeringRef(0..1)
          • Reference to the FrameTriggering from the SystemTemplate which this Pdu belongs to. SysTPduToFrameTriggeringRef shall be used for UserDefinedPdus, NmPdus and NPdus which are not going through the Pdu Router. This reference shall not be used if SysTPduToPduTriggeringRef exists. dependency: SysTPduToFrameTriggeringRef shall be used for UserDefinedPdus, NmPdus and NPdus which are not going through the Pdu Router. This reference shall not be used if SysTPduToPduTriggeringRef exists.
          • Foreign reference to FRAME-TRIGGERING
        • SysTPduToPduTriggeringRef(0..1)
          • Reference to the PduTriggering from the SystemTemplate which this Pdu represents. SysTPduToPduTriggeringRef shall be used for all Pdus except UserDefinedPdus, NmPdus and NPdus which are not going through the Pdu Router. For these Pdus, SysTPduToFrameTriggeringRef shall be used. dependency: SysTPduToPduTriggeringRef shall be used for all Pdus except UserDefinedPdus, NmPdus and NPdus which are not going through the Pdu Router. This reference shall not be used if SysTPduToFrameTriggeringRef exists.
          • Foreign reference to PDU-TRIGGERING
  • EcucPartitionCollection(0..1)
    • Collection of Partitions defined for this ECU. In order to support memory-partitioning and multi-core the notion of a EcucPartition has been introduced into the EcuC virtual Module.
    • EcucPartition(0..*)
      • Definition of one Partition on this ECU. One Partition will be implemented using one Os-Application The design principle is that after the creation of a partition the software (SWC) is mapped to this partition. In the second step the BSW is configured and every member of a partition (BSW) defines a reference to the EcucPartition element. Another example is the interaction of a SWC with the ComM: A SWC running in a partition other than the BSW modules is requesting full communication at the ComM. If now the partition which the SWC is running in will be stopped due to an partition violation there is now an outstanding full communication request at the ComM which will prohibit a network to be sent to sleep. With the provided configuration means it is possible to implement counter measures for such use-cases.
      • EcucPartitionBswModuleExecution
        • Denotes that this partition will execute BSW Modules. BSW Modules can only be executed in such partitions
        • EcucBooleanParamDef
      • EcucPartitionQmBswModuleExecution
        • Denotes that this partition will execute QM BSW.
        • EcucBooleanParamDef
      • PartitionCanBeRestarted
        • Specifies the requirement whether the Partition can be restarted. If set to true all software executing in this partition shall be capable of handling a restart.
        • EcucBooleanParamDef
      • EcucPartitionBswModuleDistinguishedPartition(0..*)
        • This maps the abstract partition of the Bsw Module to a concrete Partition existing in the ECU.
        • Foreign reference to BSW-DISTINGUISHED-PARTITION
      • EcucPartitionSoftwareComponentInstanceRef(0..*)
        • References the SW Component instances from the Ecu Extract that shall be executed in this partition.
        • Instance reference to SW-COMPONENT-PROTOTYPE context: ROO T-SW-COMPOSITION-PROTOTYPE
  • EcucHardware(0..1)
    • Hardware definition of this Ecu. In order to allow the unique description and access to hardware resources the EcucHardware has been introduced One section of the EcucHardware is concerned with the definition of computation cores and the assignment of unique EcucCoreIds to these cores. Additionally it is possible to refer to the Ecu Resource Template HwElement which represents the core in hardware
    • EcucCoreDefinition(0..*)
      • Definition of one Core on this Ecu
      • EcucCoreId
        • EcucIntegerParamDef
      • EcucCoreHwRef(0..1)
        • Optional reference to the HwElement of HwCategory ProcessingUnit that represents this Core in the ECU Resource Template.
        • Foreign reference to HW-ELEMENT
  • EcucPostBuildVariants(0..1)
    • Collection of toplevel PostBuildSelectable variants. The PredefinedVariants linked inside this container will determine how many PostBuildSelectableVariants exist. If this container exist the name pattern for initialization of BSW modules will be <Mip>_Config_<PredefinedVariant.shortName>. If this container does not exist the name pattern for initialization of BSW modlues will be <Mip>_Config
    • EcucPostBuildVariantRef（1..*）
      • Reference to a PredefinedVariant that defines one toplevel postBuild configuration set (covering all post-build capable BSW modules). PredefinedVariants that are referenced here shall contain only PostBuildVariantCriterionValueSets [constr_3307] ShortNames of PredefinedVariants referenced by EcucPostBuildVariantRefs d All PredefinedVariants that are referenced by EcucPostBuildVariantRefs shall have different shortNames. c() PredefinedVariants may exist in different packages and thus have the same shortName. The generation of symbols in EcucPostBuildVariants requires these shortNames to be different.
      • Foreign reference to PREDEFINED-VARIANT
  • EcucUnitGroupAssignment(0..1)
    • Collection of UnitGroup references to support the generation of ASAM MCD file.
    • EcucUnitGroupRef(1..*)
      • Optional reference to the UnitGroup to support the generation of ASAM MCD file. These UnitGroups are selecting a set of units for a specific country.
      • Foreign reference to UNIT-GROUP
  • EcucVariationResolver(0..1)
    • Collection of PredefinedVariant elements containing definition of values for SwSystemconst which shall be applied when resolving the variability during ECU Configuration. In order to support the variant handling approach (see Generic Structure Template [7]) the already given values of system constants are specified in using the collection SwSystemconstantValueSet. In the EcuC the applicable SwSystemconstantValueSet elements are referenced indirectly via the PredefinedVariant collection.
    • PredefinedVariantRef（1..*）
      • Foreign reference to PREDEFINED-VARIANT