Fenrigore On the generation side, either a generic generator may be used, or custom generators for the individual modules. But for some channels, this direction may be fixed by hardware and must thus be fixed in configuration. The main approach is to use a subset of UML to graphically model the desired entities and their relationships. It is a major challenge to develop a formal language which is capable of representing the concepts required to specify the formula and rules how the derived values are computed.
|Published (Last):||23 November 2018|
|PDF File Size:||19.11 Mb|
|ePub File Size:||5.99 Mb|
|Price:||Free* [*Free Regsitration Required]|
Miktilar To be able to define such a choice an object of the class ChoiceReferenceDef has to be aggregated in a container with the role name reference at the ChoiceReferenceDef object. In the calculationFormula this is used to address the different parts the value needs to be derived from. Two different approaches are shown. This holds for confguration definitions, container definitions and individual parameters.
In order to make the post-build time re-configuration possible, the re-configurable parameters shall be stored at a known memory location of ECU storage area. In the next sections these different parameter types will be described in detail. Two containers of type ParameterConfParamDef are specified as part of the module definition.
Even if a parameter currently is defined as a plain ParameterType it can be easily redefined to become a DerivedParamType in a later version of the parameter definition. Neither their presence in such Specification Documents, configurtaion any later AUTOSAR compliance autosr of products actually implementing such exemplary items, imply that intellectual property rights covering such exemplary items are licensed under the same rules as applicable to the AUTOSAR Standard.
In every case, the ECU Configuration Description is expected to be the point of reference, the backbone of the process. Thus, those rules can be found in chapter 4. With the attribute destinationType the type of the referenced entity has to be specified. ConfigParameter The use-case for the attribute symbolicNameValue will be described in cofiguration 3. It is assumed that configuration editors perform consistency and completeness checks on the part of the configuration they support.
So such multiple occurrences of a parameter in the description will just be mere collections, it is neither guaranteed that the order will be preserved nor that that individual elements do have a special semantics. The three defined Derived Configuration Parameters have an informal calculationFormula which is not shown in the figure but is confiiguration in the XML example.
In the following, the different approaches that have been considered during the development of the specification are introduced. When specifying the containment relationship between the ModuleDef and containers the role name container is used.
This approach relies upon a standard framework: Dependencies are depicted by dashed lines with arrow heads, pointing from the dependent element to the element it depends on.
To make sure, that all tools are using the same output-format within the configured values of the parameters, the ECU Configuration Description is also part of this specification and described in detail later on chapter 3.
ContainerDef [ecuc sws ] Each container ts is an Identifiable. With this feature functions like callbacks can be specified. Thus those parameters are fixed, and the value chosen must be documented in the BSWMD so that subsequent configuration of remaining parameters and adjacent modules can take these fixed values into account.
The abstract class ContainerDef is used to gather the common features see figure 3. The recommendedConfiguration contains parameter values recommended by the BSW module vendor. For additional information about the consequences of being an Identifiable and the additional attributes please refer to . The tool strategy and tooling details for ECU Configuration are out of scope for this specification, thus the following sections 2.
The configuration classes are explained in detail in following section of this chapter. Aytosar, in a generation step, the actual XML formats are automatically generated out of the model. One subcontainer instance is defined for each PDU received. This is the last step of the configuration process and again out of scope of this specification. The configuration of hardware objects is done in a subcontainer. Specification of ECU Configuration Or if a configuration parameter is defined at post-build time the configuration parameter has to be stored at a known memory location.
Both module source file and module configuration source file compiled separately and generates module object file and module configuration object file respectively. ParameterValue All specialized parameter values that are derived from ParameterValue are described in the sections below. A category allows specifying the particular nature of the object in question. For these definitions there is no corresponding entry in the ECUC description.
Then again the attribute value is assigned to the value of the derived parameter. The implementation on the other hand fixes the configuration class for each parameter, and the corresponding value chosen must be specified. If any of the aggregated parameters is either preCompile time or link time this attribute is ignored and may be ommited. Link time parameters are typically used when delivering object code to the integrator. Infrastructure Instances of this class can be referred to by their identifier while adhering to namespace borders.
It contains values for those configuration parameters and containers defined in the Vendor Specific Module Definition that are fixed by the implementation of the module.
Each vendor of a BSW module would need to provide a tool. One container instance with all relevant parameter values taken from the system configuration will be generated for each signal.
This is the way that the tool gets a definition of exactly which ECU Configuration Parameters are available and how they may be configured. Related Posts
AUTOSAR RS ECU CONFIGURATION PDF
Miktilar To be able to define such a choice an object of the class ChoiceReferenceDef has to be aggregated in a container with the role name reference at the ChoiceReferenceDef object. In the calculationFormula this is used to address the different parts the value needs to be derived from. Two different approaches are shown. This holds for confguration definitions, container definitions and individual parameters. In order to make the post-build time re-configuration possible, the re-configurable parameters shall be stored at a known memory location of ECU storage area. In the next sections these different parameter types will be described in detail.
Tujar Custom Editors and Generators In the custom editors approach as shown in figure 2. Also ConfigReference is inheriting from ParamConfMultiplicity so for each reference definition it can be specified how many such references might be present in the same configuration container later in the ECU Configuration Description. However, for several modules such as OS, existing configuration languages have already been established. But for some channels, this direction may be fixed by hardware and must thus be fixed in configuration. If XML files are used there is no conceptual limit in the number of files making up the description. It donfiguration not apply any additional semantics to the parameter. Since each configuration parameter is defined only once, all instances of the parameter will have the same initial value when the default values is taken as input to the base configuration.
Nashakar A category allows specifying the particular nature of the object in question. Because of the need that all autosa in the parameter definition have to resolved in the parameter description there does not exist an according choice container description but a Container is used to represent the chosen subcontainers. Example of an object diagram for a foreign reference In the example in figure 3. It does not apply any confifuration semantics to the parameter. Both approaches are equally valid.