Removed RS Items. . ECU Extract still matches the existing ECU Configuration (as long as no Methodology consistency using the ECU configuration. [3] Specification of ECU Configuration Parameters (XML) . RS. Requirement Specification. DocumentCategory, TraceCategory. Specification of requirements . [3] Requirements on Communication. AUTOSAR SRS [4] Requirements on ECU Configuration. AUTOSAR RS ECU

Author: Mugrel Akinom
Country: Finland
Language: English (Spanish)
Genre: Personal Growth
Published (Last): 2 October 2015
Pages: 460
PDF File Size: 11.88 Mb
ePub File Size: 7.67 Mb
ISBN: 978-5-99667-963-3
Downloads: 72537
Price: Free* [*Free Regsitration Required]
Uploader: Kicage

Documents Flashcards Grammar checker. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including rrs and microfilm, without permission in writing from the publisher. Neither their presence in such Specification Documents, nor any later AUTOSAR compliance certification of products vonfiguration 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.

The tool strategy and tooling details for the ECU Configuration are out of scope of this specification. Nevertheless tools need the knowledge about ECU Configuration Parameters and their constraints such as configuration class, value range, multiplicities etc.

This description is the input for the tools and has to be standardized. The description of configuration parameters is called ECU Configuration Parameter Definition and described in detail in this specification chapter 3.

To make sure, that all tools are donfiguration 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. The ECU Configuration Description may be on one confifuration the input format for other configuration tools within a tool-chain of several configuration editors and on the other hand it is the basis of generators. The configured parameters are generated into ECU executables.

This is the last step of the configuration process and again out of scope of this specification. Configuratoin abbreviations are mentioned that are specifically used in this specification: In this document, the activities Configure ECU and Generate Executable will be defined in more detail than rd in [8]. To understand this chapter, the reader should be familiar with [8]. The flow of work products is depicted by solid lines with arrow configurtaion, pointing in the direction of the work flow.

Dependencies are depicted by dashed lines with arrow heads, pointing from the dependent element to the element it depends on.

Compositions are depicted by a solid line with a solid diamond on the end of the aggregating element.

Specification of ECU Configuration

The specifics of these module implementation are defined in the BSW Module Descriptions not shown in figure 1. Since the following chapters assume familiarity with the contents of these two work products, they are shortly introduced in the following sections.

Details on the System Configuration Description can be found in [7]. BSW module implementations must support configuration of these standardized parameters. The definitions may be adapted to the implementation following the rules defined in chapter 4.

Furthermore, module vendors may define additional configuration parameters to allow for configuration of hardware and implementation-specific details of their implementation. The Vendor Specific Module Definition contains definitions for both the standardized parameters as adapted by the implementer and for the additional vendor-specific parameters.

It references the Standardized Module Definition that it refines. 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.

There may be several reasons to fix values of configuration parameters of a module: 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. First, the hardware defines the number of instances that can be configured. For example, the DIO driver for a specific microcontroller has a fixed number of DIO ports and channels that can be configured.

Each port and each channel is represented by one Container see chapter 3. Second, within the configuration of each hardware instance, some parameters that are changeable in the general case are fixed by hardware for certain instances. But for some channels, this direction may be fixed by hardware and must thus be fixed in configuration. This part of the BSW module description is not relevant for the methodology and is thus not further described at this point.


Some informative background why this single work product is needed will help the understanding of the following section.

In order to generate a working executable that runs on the ECU, much more configuration information must be provided.

This approach has the advantage that the different formats can be tailored to the problem at hand, and they can be extended and adapted ceu. This is best illustrated using some examples: 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.

The different configuration formats would potentially contain redundant information. Xonfiguration cases make it extremely difficult to obtain consistency within the overall configuration. Each module generator may then extract the subset of configuration data it needs from that single format.

The configuration of the different modules is done in configuratikn sections of the overall description. This generation is a semi-automatic process: The BSWMD defines all configuration parameters, and their structuring in containers, relevant for this specific implementation of euc module.

This is done in the Vendor Specific Module Definition, see section 2. The rules that must be followed when building the base ECU Configuration Description can only be defined once the meta model is introduced in chapter 3.

Thus, those rules can be found in chapter 4.

Specification of ECU Configuration

Those editors may operate with user interaction, semi automatically or automatically, depending on module and implementation. The tool strategy and tooling details for ECU Configuration are out of scope for this specification, thus the following sections 2. It is assumed that configuration editors perform consistency and completeness checks on the part of the configuration they support.

In the following, the different approaches that have been considered during the development of es specification are introduced. Other approaches might be consistent with this specification, but have not been considered explicitly. Tool suppliers have a high degree of freedom in the approach their tools may take to ECU Configuration. ECU Configuration tools might consist of a single monolithic editor capable of manipulating all aspects of ECU Configuration, it could be augosar core tool framework that takes plug-in components to manipulate particular autosaar 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 likely, software vendors could supply individual custom tools to configure only the code aurosar that they supply similar to microprocessor vendors providing specialized debuggers for their own micros.

Common to the different tool approaches is that each configuration editor must be capable of reading a possibly incomplete ECU Configuration Description and writing back its modified configuration results in the same format. In every case, the ECU Configuration Description is expected to be the point of reference, the backbone of the process.

The sections below look at some possible tool forms and identify some of their strengths and weaknesses. Custom Editors and Generators In the custom editors approach as shown in figure 2. These tools can be optimized to the particular task of configuring one BSW module and would likely be quite powerful. The complex dependencies between the BSW autksar configuration and other configuration items in the ECU Configuration Description could be expressed and supported in the tool.

Each vendor of a BSW module would need to provide a tool. Each tool would probably have an configurationn look and feel and this could increase the training and experience required to become proficient.

It would read those definitions and provide a generic interface to edit values for all parameters in the ECU Configuration Description. It would only be able to resolve the relatively simple dependencies explicitly defined in the Configuration Parameter Definitions.


Only a limited number of editors would be required, atosar only one, and the look and aurosar is less likely to vary greatly configurwtion generic tools. Training and tooling costs are therefore likely to be lower.

On the generation side, either a generic generator may be used, or custom generators for the individual modules. Framework Tools The tool framework as shown in figure 2. The heart of the tool would be a framework that provides certain core services such as importing and exporting data from standard file formats, maintaining standard internal data structures and providing an HMI to the user.

This ensures that the ECU Configuration Description is read, interpreted and written in a defined way. It provides a low initial tooling and training investment. The power of the approach would be the ability to add plug-in modules that extend the core functionality. These would allow very sophisticated features, potentially dedicated to one BSW module, to be added by individual suppliers.

Additionally, it would be possible to add generic plug-ins that addressed a specific aspect of configuration across all BSW modules. This approach relies upon a standard framework: The configuration deals with, for example, detailed scheduling information or the configuration data for the needed BSW modules. ECU Configuration is thus likely to be an iterative process. This iteration will initially be between editors and then, when a plausible ECU Configuration is achieved, code generation may highlight additional changes that require further iteration.

Sequential Application of tools Figure 2. Iteration cycles must be implemented by repeated activation of different configuration tools for specific aspects of the BSW. Dependencies between tools, as well as the configuration work flow, might need to be expressed explicitly. Configuration tools are required only to support a single standardized interface, the ECU Configuration Description Template, but there is no overall picture of the state of configuration for a particular ECU because each tool specializes only on a particular subset of the configuration.

The different tool chain models given in sections 2.

Generation is the process of applying the tailored ECU Configuration Description to the software modules. This can be performed in different ways, and is dependent on the configuration classes chosen for the different modules see chapter 2. For 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 hand side of figures 2.

In this generation step, the abstract parameters of the ECU Configuration Description are translated to hardware and implementation-specific data structures that fit to the implementation of the corresponding software module.

This specification does not specify the generator tools in detail. It is assumed however that generators perform error, consistency and completeness checks on the part of the configuration they require for generation. Configuration of parameters can be done in any of these process-steps: Or if a configuration parameter is defined at post-build time the configuration parameter has to be stored at a known memory location. The configuration class of a parameter is typically not fixed in the standardized parameter definition since several variants are possible.

However once the module is implemented the configuration class for each of the parameters is typically fixed in that implementation. Choosing the right configuration class from the available variants is depending on the type of application and the design decision of the module implementer.

Different configuration classes can be cohfiguration within one module. For example, for post-build time configurable BSW implementations only a subset of the parameters might be configurable post-build time.

Some parameters might be configured as pre-compile time or link time. The configuration classes are explained in detail in following section of this chapter.