Removed RS Items. . ECU Extract still matches the existing ECU Configuration (as long as no Methodology consistency using the ECU configuration.  Specification of ECU Configuration Parameters (XML) . RS. Requirement Specification. DocumentCategory, TraceCategory. Specification of requirements .  Requirements on Communication. AUTOSAR SRS  Requirements on ECU Configuration. AUTOSAR RS ECU
|Published (Last):||11 April 2014|
|PDF File Size:||12.59 Mb|
|ePub File Size:||20.19 Mb|
|Price:||Free* [*Free Regsitration Required]|
This is done using object diagrams this is the M1 level of metamodeling with special semantics defined in section 3. ParameterValue All specialized parameter values that are derived from ParameterValue are described in the sections below. It would read those definitions and provide a generic interface to edit values for all parameters in the ECU Configuration Description.
Example of an object diagram for a foreign reference In the example in figure 3.
Or if a configuration parameter is defined at post-build time the configuration parameter has to be stored at a known memory location. This results in the following: Configuration of parameters can be done in any of these process-steps: The abstract class ContainerDef is used to gather the common features see figure 3.
ARElement itself inherits form Identifiable which autoxar two consequences: When CRC16 is selected, there will be increase in processing time but reduction in memory usage.
It contains values for those configuration parameters and containers defined in autoar Vendor Specific Module Definition that are fixed by the implementation of the module. This string nees to be one of the literals specified for this enumeration. Ecy is an Identifiable so it is mandatory to give each reference a name. If AUTOSAR were to continue with the approach sketched above, the configuration tools and generators of a specific module would need to read several different formats.
But since derived parameters do depend on other information there are certain restrictions applicable which reduce the degree of freedom what kind of configuration class a derived parameter might be. Configugation each BSW module, a generator reads the relevant parameters from the ECU Configuration Description and creates code that implements the specified configuration, as shown on the right autoear side of figures 2.
Furthermore, module vendors may define additional configuration parameters to allow for configuration of hardware and implementation-specific details of their implementation.
The additional attributes min, max and defaultValue can be specified as well.
This is done in the Vendor Specific Module Definition, cojfiguration section 2. However once the module is implemented the configuration class for each of the parameters is typically fixed in that implementation.
Specification of ECU Configuration
The implementation on the other hand fixes the configuration class for each parameter, and the corresponding value chosen must be specified.
ECU Configuration tools might consist of a single monolithic editor capable of manipulating all aspects of ECU Configuraation, it could be a core tool framework that takes plug-in components to configguration particular aspects of ECU Configuration, it might be a set of specialized tools each capable of configuring a particular type or subset of software modules or, probably more scu, software vendors could supply individual custom tools to configure only the code blocks that they supply similar to microprocessor vendors providing specialized debuggers for their own micros.
The metamodel of those references is shown in figure 3. The different tool chain models given in sections 2.
Specification of ECU Configuration
Container In example 3. Auotsar vendor of a BSW module would need to provide a tool. Typically, this is a vendor specific module configuration. The class FunctionNameDef does not introduce any additional attributes.
The module source file needs this header file to resolve the references and module configuration source file will need to cross check the declaration of data type against the definition.
Link Type Container Def In condiguration ECU Configuration Parameter Definition the potential containers are specified and the constraint is that in the actual ECU Configuration Description only one of those specified containers can actually be contained.
Link Type Float A template is defining the structure and possible content of an actual description. Dependencies between tools, configuartion well as the configuration work flow, might need to be expressed explicitly. How this symbolic name is accessed by the using module is up to the implementation of it13 and therefore out of scope of this specification.
The configuration of hardware objects is done in a subcontainer. Each tool would probably have an individual look and feel and this could increase the training and experience required to become proficient.
Link Type Boolean 1 aggregation Description Specifies if the number of instances of this container my be changed postBuild time. Example of parameter definitions using different types 3.