SNIP_CLASSIC_FR_SECTION_7_6_Configuration_description

7.6 Configuration description [SWS_Fr_00080] Upstream requirements: SRS_BSW_00003, SRS_BSW_00334, SRS_BSW_00374, SRS_BSW_ 00379 ⌈The Fr module shall provide an XML file that contains the data, which is required for the SW identification and configuration parameters. This file shall describe vendor specific configuration parameters if applicable.⌋ [SWS_Fr_00480] Upstream requirements: SRS_Fr_05058 ⌈A driver MCG reads the ECU configuration parameters of the Fr and the FrIf modules. While cluster related configuration parameters are contained in the FrIf module’s configuration, CC related configuration parameters are contained in the Fr module’s configuration. The Fr module’s specific configuration tool shall read both ECU module configurations to derive the configuration parameters for all FlexRay CCs mapped to the Fr module.⌋ [SWS_Fr_00481] ⌈All frame transmission/reception related configuration parameters are located only in the FrIf module description (within configuration containers ’FrIfLPdu’ and ’FrIfFrameTriggering’). The Fr must be able to handle all transmission/reception requests of all related LPdus. The LPdus within the FrIf configuration contain both an LPduIdx which is passed to the Fr API as well as a link to a frame triggering that holds the link of the LPdu to the FlexRay network (assignment to Slot, channel, cycle). The CC configuration parameters related to frame transmission and reception shall be derived from the communication matrix the CC is mapped to within the FrIf.⌋ [SWS_Fr_00482] ⌈For optimization purposes the Fr MCG shall read the FrIf job list for detecting the points in time certain actions on the Fr will be synchronously invoked by the FrIf (see [6] for the FrIf configuration parameters).⌋ [SWS_Fr_00483] ⌈Based on those invocation times the Fr MCG might decide certain resource alignment optimizations for transmission and reception (share buffers among different LPdus).⌋ [SWS_Fr_00003] ⌈If the FrIf job list contains dedicated buffer reconfiguration entries that allow for optimization, then the Fr module’s MCG may decide to share one buffer for several LPdus within the static segment.⌋ [SWS_Fr_00624] ⌈If an LPdu is dynamically reconfigurable (’FrIfReconfigurable’ set to true) the MCG shall decide to assign a single exclusive hardware message buffer to those LPdus.⌋ [SWS_Fr_00484] ⌈The Fr MCG shall have knowledge about the capabilities of the CC and the corresponding driver, therefore this tool is called driver dependent.⌋ [SWS_Fr_00485] ⌈If an Fr MCG is unable to map all required communication operations to the available resources, then it has to report that conflict1.⌋ [SWS_Fr_00486] ⌈The number of supported FlexRay CCs is defined at configuration time.⌋ [SWS_Fr_00487] ⌈The MCG shall ensure the consistency of the generated configuration.⌋ [SWS_Fr_00027] Upstream requirements: SRS_BSW_00345, SRS_BSW_00404 ⌈The Fr module shall support the pre-compile-time and post-build-time configuration classes.⌋ An assignment of those configuration classes to configuration parameters can be found in Chapter 10. Hint: The description of the software configuration itself is not part of this specification but very implementation specific. 1This can result from either from running out of resources (e.g. buffers) or the mapping of the configuration to the particular device is not supported (e.g. configuration features supported in [1], but the device is compliant to [2]). A detailed description of all Fr related configuration parameters is specified in Chapter 10 of this document. Additionally the configuration parameters of the FrIf (see chapter 10 of [6]) shall be evaluated for Fr module configuration.