Autosar methodology

1. Agenda
1. System Configuration
2. Extraction of the ECU specific information
3. ECU Configuration
4. Generation of the module configuration
5. AUTOSAR Methodology Summary
6. K-SAR Editor Demo

2. • AUTOSAR Methodology Overview
ECU Extract of
System
Configuration
XML
XML
XML
System
Configuration
Input
Configure
System
System
Configuration
Description
Extract ECU
Specific Info
System Configuration Editor
[System Engineer]
Configure
ECU
XML
ECU
Configuration
Description
ECU Config Editor
[ECU Engineer]
Tooling Architecture
EXE
Generate
Executable
ECU
Executable
Build System
[ECU Engineer]
Work
Product
Tool or
activity

3. • 1. System Configuration
XML
System Configuration
Input
Work Product
Configure
System
XML
System Configuration
Description
Extract ECU
Specific Info
XML
ECU Extract of System
Configuration
Configure
ECU
XML
ECU Configuration
Description
Generate
Executable
EXE
ECU Executable
The configuration of the system has the goal to unify the description of the software components
and the description of the system inputs and hardware resources
I. The input of this activity is an instance of the System Template, which is named System
Configuration Input. System Configuration Input holds constraints, which concern the
communication matrix and the mapping of hardware and software
II. The second input for the activity Configure System is a collection of all available Software
component implementations
III. Activity Configure System involves mapping System elements to Software elements
IV. The output is The System Configuration Description references the communication matrix,
the topology and the top level composition
Tool or activity

4. • 1. System Configuration
XML
System Configuration
Input
Work Product
Configure
System
XML
System Configuration
Description
Extract ECU
Specific Info
XML
ECU Extract of System
Configuration
Configure
ECU
XML
ECU Configuration
Description
Generate
Executable
EXE
ECU Executable
Tool or activity
The System Configuration Description contains all relevant system-wide configuration, such as
I. ECUs present in the system
II. Communication systems interconnecting those ECUs and their configuration
III. Communication matrices (frames sent and received) for those communication systems
IV. Definition of Software Components with their ports and interfaces and connections
(defined in the SWC Description and referenced in the System Configuration Description)
V. Mapping of SWCs to ECUs
The ECU Extract of the System Configuration is a description in the same format as the System
Configuration Description, but with only those elements included that are relevant for the
configuration of one specific ECU.

5. • 2. Extraction of the ECU specific information
XML
System Configuration
Input(DBC)
Configure
System
XML
System Configuration
Description
Extract ECU
Specific Info
XML
ECU Extract of System
Configuration
Configure
ECU
XML
ECU Configuration
Description
Generate
Executable
EXE
ECU Executable
I. Extract ECU-Specific Information activity of the methodology demands on supporting tool
under the conceptual tool name AUTOSAR ECU Configuration Extractor(e.g. K-SAR)
II. Output is similar to the System Configuration Description, but it holds only the information
that is relevant for a Single ECU
Work Product Tool or activity

6. • 3. ECU Configuration
XML
System Configuration
Input(DBC)
Configure
System
XML
System Configuration
Description
Extract ECU
Specific Info
XML
ECU Extract of System
Configuration
Configure
ECU
XML
ECU Configuration
Description
Generate
Executable
EXE
ECU Executable
I. After the extraction of the ECU specific parts, the basic software modules have to be configured
for the ECU
II. The configuration information for the whole ECU is described in the ECU Configuration
Description
III. The Basic Software Module Description holds the information about the used implementation
for a basic software module
IV. Link between ECU configuration description and Basic Software Module Description of every
Basic Software module that will run of the ECU and the RTE
Work Product Tool or activity

7. • 4. Generation of the module configuration
I. The last step after the configuration of the ECU is the generation of the executable
II. This activity is done for each Basic Software module and configuration class
III. The activity Generate Module Configuration produces different outputs, dependent on the
configuration classes
IV. Different configuration classes are pre-compile time, link time and post-build time

8. • 5. AUTOSAR Methodology Summary
per ECU
ECU Configuration
Description
AUTOSAR
ECU
Configuration
Generator
SW-C
Implementation
RTE extract of
ECU configuration
OS extract of
ECU configuration
Basic SW
Module A extract
of ECU
configuration
Basic SW
Module A extract
of ECU
configuration
Basic SW
Module A extract
of ECU
configuration
List of
implementations
of SW
components
e.g. OIL
AUTOSAR
RTE
Generator
OS, COM, …
Generator
Other Basic
SW Generator
MCAL –
Generator
Decisions
(e.g. scheduling)
System
Configuration
Description
AUTOSAR
System
Configuration
Generator
Component
API
Generator
Generation step:
complex algorithm or engineering work
Information / Database (no files)
SW-
Component
Description
ECU
Resource
Description
(HW only)
System –
Constraint
Description
Component
API
e.g. app.h
ECU extract
of System
Configuration
ECU extract
of System
Configuration
Decisions
(e.g. mapping)
System

9. • 5. AUTOSAR Methodology Summary
per ECU
AUTOSAR
RTE
Generator
Generator for
OS, COM, ...
Other Basic
SW Generator
MCAL-
Generator
AUTOSAR RTE
Files
OS Files
Basic SW Files
MCAL Files
RTE.c
OS.c
*.c
MCAL.c
Software Componenten*.c Software Components
AUTOSAR
RTE
OS
Basic
Software
MCAL
Lib*.obj
Note: these steps resembles today’s development praxis

10. • Thank You