Release 4.

2 Overview and Revision History

AUTOSAR Release 4.2.2

Document Title Release 4.2 Overview and

Revision History
Document Owner AUTOSAR
Document Responsibility Release Management
Document Identification No 000
Document Classification Informal

Document Status Final

Part of AUTOSAR Release 4.2.2
Release Life Cycle Status R4.2 is in Evolution, R4.2 supersedes R4.1

Document Change History

Date Release Changed by Change Description
31.07.2015 4.2.2 Release Update according to revision 4.2.2
Management
31.10.2014 4.2.1 Release Initial release
Management

1 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Table of Contents

1 Introduction.......................................................................................................... 4
1.1 Scope of this document ................................................................................ 4
1.2 Content of chapters ...................................................................................... 4
2 Related documentation........................................................................................ 5

3 Summary of changes........................................................................................... 6
3.1 Release 4.2.1 ............................................................................................... 6
3.1.1 Introduced Concepts ............................................................................. 6
3.1.1.1 CAN Flexible Data Rate .................................................................... 6
3.1.1.2 Decentralized Configuration .............................................................. 6
3.1.1.3 Efficient COM for Large Data............................................................. 6
3.1.1.4 Efficient NV Data Handling via RTE .................................................. 6
3.1.1.5 Enhancement EcuM Fixed for Multi Core .......................................... 6
3.1.1.6 Ethernet Configuration and System Description for Manageable
Switched Systems............................................................................................ 6
3.1.1.7 Extension of E2E Protection .............................................................. 7
3.1.1.8 Global Time Synchronization ............................................................. 7
3.1.1.9 Integration of Non-AUTOSAR Systems ............................................. 7
3.1.1.10 Mechanisms and constraints to protect ASIL BSW against QM
BSW 7
3.1.1.11 Safety Extensions for Methodology and Templates ....................... 7
3.1.1.12 Secure Onboard Communication ................................................... 7
3.1.1.13 Sender Receiver Serialization ........................................................ 7
3.1.1.14 Support for post-build loadable and post-build selectable ECU
configuration .................................................................................................... 7
3.1.2 Impacts of Concepts ............................................................................. 7
3.2 Release 4.2.2 ............................................................................................. 12
3.2.1 Specifications ...................................................................................... 12
3.2.1.1 New Specifications .......................................................................... 12
3.2.1.2 Obsolete Specifications ................................................................... 12
3.2.1.3 Canceled ......................................................................................... 12
3.2.2 Concepts ............................................................................................. 12
3.2.3 Release Documentation ...................................................................... 12
4 Specification overview ....................................................................................... 14

5 Remarks to known technical deficiencies .......................................................... 22

6 Revision history ................................................................................................. 23

6.1 Release 4.2.1 ............................................................................................. 23
6.2 Release 4.2.2 ............................................................................................. 35
7 Appendix ........................................................................................................... 45
7.1 Definitions .................................................................................................. 45
7.1.1 Release number .................................................................................. 45
7.1.2 Revision number ................................................................................. 45
7.1.3 Release life cycle of a major release................................................... 46
2 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory
- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

7.1.4 Standard specifications and auxiliary material .................................... 46

7.1.5 History information in AUTOSAR ........................................................ 47

3 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

1 Introduction
1.1 Scope of this document
This document provides an overview of the complement of AUTOSAR specifications
comprising the initial Release 4.2 and its latest Revision 2.

1.2 Content of chapters

This document is structured as follows:

 Chapter 2 provides a list of documentation references.

 Chapter 3 provides a summary of changes that were implemented since the
preceding Release 4.1.
 Chapter 4 contains the overview of specifications comprising the Release 4.2
in its latest Revision 2. This chapter is structured according to the clusters
being in use in AUTOSAR Release 4.2.
 Chapter 5 contains remarks about known technical deficiencies.
 Chapter 6 contains the detailed revision history of all released specifications.
 Chapter 7.1 provides a set of definitions aimed to increase the understanding
of the content of this document and the Release 4.2.

4 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

2 Related documentation
1) Release Overview and Revision History
2) AUTOSAR Specifications in general
3) Change Documentation
4) Glossary

5 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

3 Summary of changes
This chapter contains a summary of changes which were implemented since the
previous Release 4.1.

3.1 Release 4.2.1

In AUTOSAR R4.2.1, several concepts were introduced, focusing on improvements
of two main areas:
1. Large data communication via Ethernet and CAN FD and
2. Safety and Security
The AUTOSAR Data Handling for Ethernet/CAN FD comprises the introduction of
Ethernet Switch capabilities paired with the ability to handle large blocks of data in
the COM stack domain, e.g. via serialized data communication.
The safety and security aims on improvements of the support of functional safety in
the AUTOSAR Meta Model, new E2E profiles for large data communication, and the
secure interaction of in-vehicle components.
Further improvements introduced in R4.2.1 are extended support of BSW distribution
according different safety levels, synchronized timing information across various bus
systems and loadable post-built configuration sets for BSW modules.

3.1.1 Introduced Concepts

The following concepts have been introduced.

3.1.1.1 CAN Flexible Data Rate

Support of CAN FD, allowing switching to a faster bit rate after the arbitration, higher
data rates than 1 Mbit/s and payloads longer than 8 bytes per frame.

3.1.1.2 Decentralized Configuration

This concept allows the configuration of the “Diagnostic Extract” – the demand of
diagnostic services and fault memory content – in the System Description.

3.1.1.3 Efficient COM for Large Data

Introduction of new functionality in the COM interaction layer to allow handling of
large blocks of data, e.g. for Ethernet communication.

3.1.1.4 Efficient NV Data Handling via RTE

An efficient mechanism for software components (SW-Cs) in order to handle non-
volatile (NV) data via RTE.

3.1.1.5 Enhancement EcuM Fixed for Multi Core

For ease of integration the fixed state machine of the ECU State Manager Fixed is
available also in case of a multicore configuration.

3.1.1.6 Ethernet Configuration and System Description for Manageable

Switched Systems
Mechanisms for configuring and controlling Ethernet switches, including modeling of
configuration parameters and a learning process for semi-static auto-configuration.

6 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

3.1.1.7 Extension of E2E Protection

Mechanism for a safe communication between SWCs, fully integrated within the
AUTOSAR methodology and which does not require any additional non-standard
code (like wrappers above RTE).

3.1.1.8 Global Time Synchronization

Mechanisms to distribute one or more master time bases across various busses and
bus systems.

3.1.1.9 Integration of Non-AUTOSAR Systems

Extension of AUTOSAR description means, process, and technology in such a way
that other — non-AUTOSAR — software systems can be integrated into an
AUTOSAR system during its development.

3.1.1.10 Mechanisms and constraints to protect ASIL BSW against QM BSW

AUTOSAR currently supports BSW distribution for multi core. This concept
introduces BSW distribution to be able to separate the BSW according to different
safety levels (e.g. QM requirements / ASIL requirements).

3.1.1.11 Safety Extensions for Methodology and Templates

Specification of extensions in AUTOSAR Methodology and Templates to realize and
document functional safety of AUTOSAR systems and the according usage of meta-
model.

3.1.1.12 Secure Onboard Communication

Standardization of security mechanisms to protect communication on in-vehicle
networks.

3.1.1.13 Sender Receiver Serialization

Introduction of a serialization mechanism to enable transferring large amounts of
data over an Ethernet network (sender/receiver communication), without mapping
complex data elements to several signals.

3.1.1.14 Support for post-build loadable and post-build selectable ECU

configuration
Support of the post-build loadable updates to previously generated post-build
selectable configuration sets for BSW modules.

3.1.2 Impacts of Concepts

The introduced concepts had impact on several specifications. The following table
provides a detailed overview.
Please note that some of the specifications are marked by special text formatting.
 Specifications in bold font are completely new specifications originating from
the particular concept.
 Specifications in italic font are affected indirectly as they provide artefacts for
the actually impacted specifications.

7 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Affected specifications
Concept Name Specification Long Name Classification
Specification of CAN Driver
Specification of CAN Interface
Specification of CAN Transport Layer
Specification of Communication
Specification of Diagnostic Communication Classification
Manager Standard
Specification of ECU Configuration Parameters
(XML)
CAN Flexible Data- Specification of I-PDU Multiplexer
rate Specification of PDU Router
System Template
Basic Software UML Model
Layered Software Architecture
Requirements on AUTOSAR Features
Requirements on CAN Auxiliary
Requirements on Communication
Requirements on I-PDU Multiplexer
Requirements on System Template
Diagnostic Extract Template
Software Component Template Standard
Specification of ECU Configuration Parameters
(XML)
Decentralized
Requirements on Diagnostic Extract
Configuration
Template
Auxiliary
Basic Software UML Model
Methodology
Requirements on Methodology
Specification of Large Data COM
Specification of RTE Software
Specification of ECU Configuration Parameters Standard
(XML)
System Template
Efficient COM for Basic Software UML Model
Large Data Layered Software Architecture
List of Basic Software Modules
Requirements on AUTOSAR Features Auxiliary
Requirements on Communication
Requirements on Runtime Environment
Requirements on System Template
Software Component Template
Efficient NV Data
Specification of RTE Software Standard
Handling via RTE
Specification of ECU Configuration Parameters
8 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory
- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

(XML)
Specification of NVRAM Manager
Basic Software UML Model
Requirements on Memory Services Auxiliary
Requirements on Runtime Environment
Specification of Basic Software Mode Manager
Specification of ECU Configuration Parameters
(XML)
Standard
Enhancement EcuM Specification of ECU State Manager
Fixed for Multi Core Specification of ECU State Manager with fixed
state machine
Basic Software UML Model
Auxiliary
Guide to Mode Management
Specification on Ethernet Switch Driver
Specification of ECU Configuration Parameters
(XML)
Specification of ECU State Manager
Specification of ECU State Manager with fixed Standard
Ethernet state machine
Configuration and Specification of Ethernet Interface
System Description Specification of TCP/IP Stack
for Manageable
System Template
Switched Systems
Basic Software UML Model
Layered Software Architecture
List of Basic Software Modules Auxiliary
Requirements on Ethernet Support in AUTOSAR
Requirements on System Template
Specification of Module E2E Transformer
Software Component Template
Specification of CRC Routines
Specification of ECU Configuration Parameters Standard
(XML)
Specification of SW-C End-to-End
Communication Protection Library
System Template
Extension of E2E Requirements on E2E Communication
Protection Protection
Basic Software UML Model
Layered Software Architecture
List of Basic Software Modules Auxiliary
Methodology
Requirements on AUTOSAR Features
Requirements on Libraries
Requirements on System Template

9 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Specification of Time Synchronization over

CAN
Specification of Time Synchronization over
Ethernet
Specification of Time Synchronization over
FlexRay
Specification of CAN Interface
Specification of ECU Configuration Parameters
(XML)
Specification of Ethernet Driver
Global Time Specification of Ethernet Interface Standard
Synchronization Specification of FlexRay Interface
Specification of Synchronized Time-Base
Manager
System Template
Basic Software UML Model
Layered Software Architecture
List of Basic Software Modules
Requirements on AUTOSAR Features Auxiliary
Requirements on Ethernet Support in AUTOSAR
Requirements on Synchronized Time-Base
Manager
Integration of Franca IDL Software
Component Descriptions)
Integration of Non- Standard
Specification of ECU Configuration Parameters
AUTOSAR Systems
(XML
Methodology Auxiliary
Software Component Template
Specification of RTE Software
Specification of ECU Configuration
Specification of ECU Configuration Parameters Standard
(XML)
Mechanisms and Specification of Memory Mapping
constraints to protect Specification of Operating System
ASIL BSW against Basic Software UML Model
QM BSW Collection of blueprints for AUTOSAR M1 models
Glossary
Guide to BSW Distribution Auxiliary
Layered Software Architecture
Requirements on AUTOSAR Features
Requirements on Operating System
Specifications of Safety Extensions
Safety Extensions for
Specification of ECU Configuration Parameters
Methodology and Standard
(XML)
Templates
Standardization Template

10 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Requirements on Safety Extensions

Methodology
Requirements on AUTOSAR Features Auxiliary
Requirements on Methodology
Specification of Predefined Names in AUTOSAR
Specification of Secure Onboard
Communication
Specification of ECU Configuration Parameters
(XML) Standard
Specification of PDU Router
System Template
Requirements on Secure Onboard
Secure Onboard Communication
Communication Basic Software UML Model
Layered Software Architecture
List of Basic Software Modules Auxiliary
Main Requirements
Methodology
Requirements on AUTOSAR Features
Requirements on System Template
General Specification on Transformers
Specification of COM Based Transformer
Specification of SOME/IP Transformer
Software Component Template
Specification of RTE Software Standard
Specification of Communication
Specification of ECU Configuration Parameters
(XML)
System Template
Sender Receiver Requirements on Transformer
Serialization
Basic Software UML Model
Layered Software Architecture
List of Basic Software Modules
Methodology
Auxiliary
Requirements on AUTOSAR Features
Requirements on Communication
Requirements on Runtime Environment
Requirements on Software Component Template
Requirements on System Template
General Specification of Basic Software Modules
Support for post-build Specification of ECU Configuration
Standard
loadable and post- Specification of ECU Configuration Parameters
build selectable ECU (XML)
configuration General Requirements on Basic Software
Auxiliary
Modules
11 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory
- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Glossary
Layered Software Architecture
Methodology
Requirements on AUTOSAR Features
Requirements on ECU Configuration

3.2 Release 4.2.2

The AUTOSAR Release 4.2.2 focuses on bug fixing according to the objective of
revisions in the AUTOSAR release strategy.

3.2.1 Specifications
The following specifications change their life cycle status with this release.

3.2.1.1 New Specifications

The following specifications are added to this release:
 Supplementary material of general blueprints for AUTOSAR (UID 682, TR,
aux)
 Functional Safety analysis of an exemplary system using AUTOSAR (UID 641,
EXP, aux)

3.2.1.2 Obsolete Specifications

The following specifications are set to status “obsolete” in this release:
 Requirements on Debugging in AUTOSAR (UID 332, SRS, aux)
 Specification of Debugging in AUTOSAR (UID 315, SWS, std)
These specifications are scheduled for cancellation, i.e. removal from standard with
the next minor release.
In case of objections against the planned cancellation of any of the specifications
listed above, please submit your objections to AUTOSAR by an e-mail to
[email protected].

3.2.1.3 Canceled
The following specifications are set to status “canceled” in this release:
 Example for a Serialization Protocol (SOME/IP) (UID 637, TR, aux)
The content of this technical report will be merged into a new specification of a future
release.

3.2.2 Concepts
No concepts have been incorporated in this release.

3.2.3 Release Documentation

The following changes to the infrastructure are introduced in this release:
1) Change Documentation (UID 695, TR, inf):
provides a detailed and at the same time easy to use overview on all changes per
specification.
a) The straight forward approach highlights the changes per specification item
with a simple color code (removed part red and the added parts green).
12 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory
- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Furthermore changes are documented based on the AUTOSAR trace

hierarchies so the influence of requirement changes on specification items can
easily be identified.
b) The Change Documentation will be released shortly after the specifications.
2) AUTOSAR Specification Hashes (UID 759, TR, inf):
The integrity of all released AUTOSAR specifications can be checked via this list.
a) Due to the new approach the released specifications are not protected against
modifications via PDF attributes anymore. Instead the integrity of each
specification can be checked by its original hash value provided in this list.

13 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

4 Specification overview
The published specifications are divided up into the following clusters:
 Release Documentation,
 Main Specifications,
 Basic Software Architecture and Runtime Environment,
 Methodology and Templates and
 Application Interfaces.
These clusters are then further structured by subcategories to provide a better
orientation to the specification users. The assignment of the specifications to those
clusters is shown below.

Long Name Classi- File Name Life cycle

fication changes
Cluster: Release Documentation
Canceled in
R4.2.2 as it is
Backward Compatibility part of the
inf AUTOSAR_TR_BWCStatement
Statement Change
Documentation
now
AUTOSAR_TR_ChangeDocume New in R4.2.2
Change Documentation
inf ntation

Release Overview and Revision AUTOSAR_TR_ReleaseOvervie

inf
History wAndRevHistory
AUTOSAR_TR_SpecificationHas New in R4.2.2
AUTOSAR Specification Hashes inf
hes
Cluster: Main Specifications
Glossary aux AUTOSAR_TR_Glossary
Main Requirements aux AUTOSAR_RS_Main
AUTOSAR_RS_ProjectObjective
Project Objectives aux
s
Requirements on AUTOSAR
aux AUTOSAR_RS_Features
Features
AUTOSAR_TR_PredefinedName
Predefined Names in AUTOSAR aux
s
Cluster: Basic Software Architecture and Runtime Environment
AUTOSAR_MOD_BSWUMLMod
Basic Software UML Model aux
el
Complex Driver design and AUTOSAR_EXP_CDDDesignAn
aux
integration guideline dIntegrationGuideline
Description of the AUTOSAR AUTOSAR_EXP_ErrorDescriptio
aux
standard errors n
Example for a Serialization Canceled in
aux AUTOSAR_TR_SomeIpExample
Protocol (SOME/IP) R4.2.2
Explanation of Error Handling on AUTOSAR_EXP_ApplicationLev
aux
Application Level elErrorHandling
Explanation of Interrupt Handling AUTOSAR_EXP_InterruptHandli
aux
within AUTOSAR ngExplanation
AUTOSAR_EXP_SafetyUseCas New in R4.2.2
Safety Use Case Example Aux
e
General Requirements on Basic
aux AUTOSAR_SRS_BSWGeneral
Software Modules
General Requirements on SPAL aux AUTOSAR_SRS_SPALGeneral
14 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory
- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Long Name Classi- File Name Life cycle

fication changes
General Specification of Basic AUTOSAR_SWS_BSWGeneral
std
Software Modules
General Specification on AUTOSAR_ASWS_Transformer New in R4.2.1
std
Transformers General
AUTOSAR_EXP_BSWDistributio New in R4.2.1
Guide to BSW Distribution aux
nGuide
AUTOSAR_EXP_ModeManage
Guide to Mode Management aux
mentGuide
AUTOSAR_EXP_LayeredSoftwa
Layered Software Architecture aux
reArchitecture
List of Basic Software Modules aux AUTOSAR_TR_BSWModuleList
Modeling Guidelines of Basic AUTOSAR_TR_BSWUMLModel
aux
Software EA UML Model ModelingGuide
Overview of Functional Safety AUTOSAR_EXP_FunctionalSafe New in R4.2.1
aux
Measures in AUTOSAR tyMeasures
Requirements on ADC Driver aux AUTOSAR_SRS_ADCDriver
Requirements on BSW Modules
aux AUTOSAR_SRS_SAEJ1939
for SAE J1939
Requirements on CAN aux AUTOSAR_SRS_CAN
Requirements on Communication aux AUTOSAR_SRS_COM
Requirements on Core Test aux AUTOSAR_SRS_CoreTest
Requirements on Crypto Service AUTOSAR_SRS_CryptoService
aux
Manager Manager
Requirements on Debugging in Obsolete in
aux AUTOSAR_SRS_Debugging
AUTOSAR R4.2.2
Requirements on Diagnostic aux AUTOSAR_SRS_Diagnostic
Requirements on Diagnostic Log AUTOSAR_SRS_DiagnosticLog
aux
and Trace AndTrace
Requirements on DIO Driver aux AUTOSAR_SRS_DIODriver
Requirements on E2E New in R4.2.1
aux AUTOSAR_SRS_E2E
Communication Protection
Requirements on EEPROM AUTOSAR_SRS_EEPROMDrive
aux
Driver r
Requirements on Ethernet
aux AUTOSAR_SRS_Ethernet
Support in AUTOSAR
Requirements on Flash Driver aux AUTOSAR_SRS_FlashDriver
Requirements on Flash Test aux AUTOSAR_SRS_FlashTest
Requirements on FlexRay aux AUTOSAR_SRS_FlexRay
Requirements on Free Running AUTOSAR_SRS_FreeRunningTi
aux
Timer mer
Requirements on Function AUTOSAR_SRS_FunctionInhibiti
aux
Inhibition Manager onManager
Requirements on Gateway aux AUTOSAR_SRS_Gateway
Requirements on GPT Driver aux AUTOSAR_SRS_GPTDriver
Requirements on I/O Hardware AUTOSAR_SRS_IOHWAbstracti
aux
Abstraction on
Requirements on ICU Driver aux AUTOSAR_SRS_ICUDriver
Requirements on I-PDU AUTOSAR_SRS_IPDUMultiplex
aux
Multiplexer er
Requirements on Libraries aux AUTOSAR_SRS_Libraries
Requirements on LIN aux AUTOSAR_SRS_LIN
Requirements on MCU Driver aux AUTOSAR_SRS_MCUDriver
Requirements on Memory AUTOSAR_SRS_MemoryHWAb
aux
Hardware Abstraction Layer stractionLayer

15 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Long Name Classi- File Name Life cycle

fication changes
Requirements on Memory AUTOSAR_SRS_MemoryServic
aux
Services es
Requirements on Mode AUTOSAR_SRS_ModeManage
aux
Management ment
Requirements on Module XCP aux AUTOSAR_SRS_XCP
Requirements on Network AUTOSAR_SRS_NetworkManag
aux
Management ement
Requirements on OCU Driver aux AUTOSAR_SRS_OCUDriver
Requirements on Operating
aux AUTOSAR_SRS_OS
System
Requirements on Port Driver aux AUTOSAR_SRS_PortDriver
Requirements on PWM Driver aux AUTOSAR_SRS_PWMDriver
Requirements on RAM Test aux AUTOSAR_SRS_RAMTest
Requirements on Runtime
aux AUTOSAR_SRS_RTE
Environment
Requirements on Secure AUTOSAR_SRS_SecureOnboar New in R4.2.1
aux
Onboard Communication dCommunication
Requirements on SPI AUTOSAR_SRS_SPIHandlerDri
aux
Handler/Driver ver
Requirements on Synchronized AUTOSAR_SRS_SynchronizedT
aux
Time-Base Manager imeBaseManager
Requirements on Time Service aux AUTOSAR_SRS_TimeService
Requirements on Transformer aux AUTOSAR_SRS_Transformer New in R4.2.1
Requirements on TTCAN aux AUTOSAR_SRS_TTCAN
Requirements on Watchdog AUTOSAR_SRS_WatchdogDrive
aux
Driver r
Specification of Large Data AUTOSAR_SWS_LargeDataCO New in R4.2.1
std
COM M
Specification of RTE Software std AUTOSAR_SWS_RTE
Specification of a Diagnostic
AUTOSAR_SWS_SAEJ1939Dia
Communication Manager for std
gnosticCommunicationManager
SAE J1939
Specification of a Request AUTOSAR_SWS_SAEJ1939Req
std
Manager for SAE J1939 uestManager
Specification of a Transport AUTOSAR_SWS_SAEJ1939Tra
std
Layer for SAE J1939 nsportLayer
Specification of ADC Driver std AUTOSAR_SWS_ADCDriver
Specification of Basic Software AUTOSAR_SWS_BSWModeMa
std
Mode Manager nager
Specification of Bit Handling
std AUTOSAR_SWS_BFXLibrary
Routines
Specification of CAN Driver std AUTOSAR_SWS_CANDriver
Specification of CAN Interface std AUTOSAR_SWS_CANInterface
Specification of CAN Network AUTOSAR_SWS_CANNetworkM
std
Management anagement
Specification of CAN State AUTOSAR_SWS_CANStateMan
std
Manager ager
Specification of CAN Transceiver AUTOSAR_SWS_CANTransceiv
std
Driver erDriver
Specification of CAN Transport AUTOSAR_SWS_CANTransport
std
Layer Layer
Specification of COM Based AUTOSAR_SWS_COMBasedTr New in R4.2.1
std
Transformer ansformer
Specification of Communication std AUTOSAR_SWS_COM
Specification of Communication std AUTOSAR_SWS_COMManager
16 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory
- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Long Name Classi- File Name Life cycle

fication changes
Manager
Specification of Communication AUTOSAR_SWS_Communicatio
std
Stack Types nStackTypes
Specification of Compiler AUTOSAR_SWS_CompilerAbstr
std
Abstraction action
Specification of Core Test std AUTOSAR_SWS_CoreTest
Specification of CRC Routines std AUTOSAR_SWS_CRCLibrary
Specification of Crypto AUTOSAR_SWS_CryptoAbstract
std
Abstraction Library ionLibrary
Specification of Crypto Service AUTOSAR_SWS_CryptoService
std
Manager Manager
Specification of Debugging in Obsolete in
std AUTOSAR_SWS_Debugging
AUTOSAR R4.2.2
Specification of Default Error AUTOSAR_SWS_DefaultErrorTr
std
Tracer acer
Specification of Diagnostic AUTOSAR_SWS_DiagnosticCo
std
Communication Manager mmunicationManager
Specification of Diagnostic Event AUTOSAR_SWS_DiagnosticEve
std
Manager ntManager
Specification of Diagnostic Log AUTOSAR_SWS_DiagnosticLog
std
and Trace AndTrace
Specification of Diagnostic over AUTOSAR_SWS_DiagnosticOve
std
IP rIP
Specification of DIO Driver std AUTOSAR_SWS_DIODriver
Specification of ECU State AUTOSAR_SWS_ECUStateMan
std
Manager ager
Specification of ECU State
AUTOSAR_SWS_ECUStateMan
Manager with fixed state std
agerFixed
machine
Specification of EEPROM AUTOSAR_SWS_EEPROMAbst
std
Abstraction raction
AUTOSAR_SWS_EEPROMDriv
Specification of EEPROM Driver std
er
Specification of Ethernet Driver std AUTOSAR_SWS_EthernetDriver
Specification of Ethernet AUTOSAR_SWS_EthernetInterfa
std
Interface ce
Specification of Ethernet State AUTOSAR_SWS_EthernetState
std
Manager Manager
Specification of Ethernet AUTOSAR_SWS_EthernetTrans
std
Transceiver Driver ceiverDriver
Specification of Extended Fixed
std AUTOSAR_SWS_EFXLibrary
Point Routines
Specification of Fixed Point
std AUTOSAR_SWS_IFXLibrary
Interpolation Routines
Specification of Fixed Point Math
std AUTOSAR_SWS_MFXLibrary
Routines
Specification of Flash Driver std AUTOSAR_SWS_FlashDriver
Specification of Flash EEPROM AUTOSAR_SWS_FlashEEPRO
std
Emulation MEmulation
Specification of Flash Test std AUTOSAR_SWS_FlashTest
Specification of FlexRay AUTOSAR_SWS_FlexRayARTra
std
AUTOSAR Transport Layer nsportLayer
Specification of FlexRay Driver std AUTOSAR_SWS_FlexRayDriver
Specification of FlexRay AUTOSAR_SWS_FlexRayInterfa
std
Interface ce
Specification of FlexRay ISO std AUTOSAR_SWS_FlexRayISOTr
17 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory
- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Long Name Classi- File Name Life cycle

fication changes
Transport Layer ansportLayer
Specification of FlexRay Network AUTOSAR_SWS_FlexRayNetwo
std
Management rkManagement
Specification of FlexRay State AUTOSAR_SWS_FlexRayState
std
Manager Manager
Specification of FlexRay AUTOSAR_SWS_FlexRayTrans
std
Transceiver Driver ceiverDriver
Specification of Floating Point
std AUTOSAR_SWS_IFLLibrary
Interpolation Routines
Specification of Floating Point
std AUTOSAR_SWS_MFLLibrary
Math Routines
Specification of Function AUTOSAR_SWS_FunctionInhibit
std
Inhibition Manager ionManager
Specification of GPT Driver std AUTOSAR_SWS_GPTDriver
Specification of I/O Hardware AUTOSAR_SWS_IOHardwareAb
aux
Abstraction straction
Specification of ICU Driver std AUTOSAR_SWS_ICUDriver
AUTOSAR_SWS_IPDUMultiplex
Specification of I-PDU Multiplexer std
er
Specification of LIN Driver std AUTOSAR_SWS_LINDriver
Specification of LIN Interface std AUTOSAR_SWS_LINInterface
Specification of LIN Network AUTOSAR_SWS_LINNetworkMa
std
Management nagement
Specification of LIN State AUTOSAR_SWS_LINStateMana
std
Manager ger
Specification of LIN Transceiver AUTOSAR_SWS_LINTransceive
std
Driver rDriver
Specification of MCU Driver std AUTOSAR_SWS_MCUDriver
Specification of Memory AUTOSAR_SWS_MemoryAbstra
std
Abstraction Interface ctionInterface
AUTOSAR_SWS_MemoryMappi
Specification of Memory Mapping std
ng
Specification of Module E2E AUTOSAR_SWS_E2ETransform New in R4.2.1
std
Transformer er
Specification of Module XCP std AUTOSAR_SWS_XCP
Specification of Network AUTOSAR_SWS_SAEJ1939Net
std
Management for SAE J1939 workManagement
Specification of Network AUTOSAR_SWS_NetworkMana
std
Management Interface gementInterface
Specification of NVRAM AUTOSAR_SWS_NVRAMMana
std
Manager ger
Specification of OCU Driver std AUTOSAR_SWS_OCUDriver
Specification of Operating
std AUTOSAR_SWS_OS
System
Specification of PDU Router std AUTOSAR_SWS_PDURouter
Specification of Platform Types std AUTOSAR_SWS_PlatformTypes
Specification of Port Driver std AUTOSAR_SWS_PortDriver
Specification of PWM Driver std AUTOSAR_SWS_PWMDriver
Specification of RAM Test std AUTOSAR_SWS_RAMTest
Specification of Secure Onboard AUTOSAR_SWS_SecureOnboar New in R4.2.1
std
Communication dCommunication
Specification of Service AUTOSAR_SWS_ServiceDiscov
std
Discovery ery
Specification of Socket Adaptor std AUTOSAR_SWS_SocketAdaptor
Specification of SOME/IP std AUTOSAR_SWS_SOMEIPTrans New in R4.2.1
18 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory
- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Long Name Classi- File Name Life cycle

fication changes
Transformer former
Specification of SPI AUTOSAR_SWS_SPIHandlerDri
std
Handler/Driver ver
AUTOSAR_SWS_StandardType
Specification of Standard Types std
s
Specification of SW-C End-to-
End Communication Protection std AUTOSAR_SWS_E2ELibrary
Library
Specification of Synchronized AUTOSAR_SWS_Synchronized
std
Time-Base Manager TimeBaseManager
Specification of TCP/IP Stack std AUTOSAR_SWS_TcpIp
Specification of Time Service std AUTOSAR_SWS_TimeService
Specification of Time AUTOSAR_SWS_TimeSyncOver New in R4.2.1
std
Synchronization over CAN CAN
Specification of Time AUTOSAR_SWS_TimeSyncOver New in R4.2.1
std
Synchronization over Ethernet Ethernet
Specification of Time AUTOSAR_SWS_TimeSyncOver New in R4.2.1
std
Synchronization over FlexRay FlexRay
Specification of TTCAN Driver std AUTOSAR_SWS_TTCANDriver
AUTOSAR_SWS_TTCANInterfa
Specification of TTCAN Interface std
ce
Specification of UDP Network AUTOSAR_SWS_UDPNetworkM
std
Management anagement
AUTOSAR_SWS_WatchdogDriv
Specification of Watchdog Driver std
er
Specification of Watchdog AUTOSAR_SWS_WatchdogInter
std
Interface face
Specification of Watchdog AUTOSAR_SWS_WatchdogMan
std
Manager ager
Specification on Ethernet Switch AUTOSAR_SWS_EthernetSwitc New in R4.2.1
std
Driver hDriver
Technical Safety Concept Status AUTOSAR_TR_SafetyConceptSt
aux
Report atusReport
AUTOSAR_EXP_UtilizationOfCr
Utilization of Crypto Services aux
yptoServices
Virtual Functional Bus aux AUTOSAR_EXP_VFB
Cluster: Methodology and Templates
AUTOSAR Feature Model AUTOSAR_RS_FeatureModelEx
aux
Exchange Format Requirements changeFormat
AUTOSAR Feature Model AUTOSAR_TPS_FeatureModelE
std
Exchange Format xchangeFormat
AUTOSAR Miscellaneous
aux AUTOSAR_MOD_MiscSupport
Support Files
Basic Software Module AUTOSAR_TPS_BSWModuleDe
std
Description Template scriptionTemplate
Collection of blueprints for AUTOSAR_MOD_GeneralBluepr
aux
AUTOSAR M1 models ints
Collection of constraints on AUTOSAR_TR_AutosarModelCo
std
AUTOSAR M1 models nstraints
AUTOSAR_TPS_DiagnosticExtr New in R4.2.1
Diagnostic Extract Template std
actTemplate
General Requirements on AUTOSAR_RS_MethodologyAnd
aux
Methodology and Templates TemplatesGeneral
AUTOSAR_TPS_GenericStructu
Generic Structure Template std
reTemplate
Integration of Franca IDL aux AUTOSAR_TR_FrancaIntegratio New in R4.2.1
19 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory
- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Long Name Classi- File Name Life cycle

fication changes
Software Component n
Descriptions
Meta Model aux AUTOSAR_MMOD_MetaModel
Meta Model-generated XML
std AUTOSAR_MMOD_XMLSchema
Schema
Methodology aux AUTOSAR_TR_Methodology
AUTOSAR_TR_XMLPersistence
Model Persistence Rules for XML std
Rules
Recommended Methods and
Practices for Timing Analysis and
aux AUTOSAR_TR_TimingAnalysis
Design within the AUTOSAR
Development Process
Requirements on Basic Software AUTOSAR_RS_BSWModuleDes
aux
Module Description Template criptionTemplate
Requirements on Diagnostic AUTOSAR_RS_DiagnosticExtrac New in R4.2.1
aux
Extract Template tTemplate
Requirements on ECU AUTOSAR_RS_ECUConfiguratio
aux
Configuration n
Requirements on ECU Resource AUTOSAR_RS_ECUResourceT
aux
Template emplate
Requirements on Interaction with AUTOSAR_RS_InteractionWithB
aux
Behavioral Models ehavioralModels
Requirements on Interoperability AUTOSAR_RS_InteroperabilityO
aux
of AUTOSAR Tools fAutosarTools
Requirements on Methodology aux AUTOSAR_RS_Methodology
Requirements on Safety AUTOSAR_RS_SafetyExtension New in R4.2.1
aux
Extensions s
Requirements on Software AUTOSAR_RS_SoftwareCompo
aux
Component Template nentTemplate
Requirements on Standardization AUTOSAR_RS_Standardization
aux
Template Template
Requirements on System
aux AUTOSAR_RS_SystemTemplate
Template
Requirements on Timing AUTOSAR_RS_TimingExtension
aux
Extensions s
AUTOSAR_TPS_SoftwareComp
Software Component Template std
onentTemplate
Specification of ECU AUTOSAR_TPS_ECUConfigurati
std
Configuration on
Specification of ECU AUTOSAR_MOD_ECUConfigura
std
Configuration Parameters (XML) tionParameters
Specification of ECU Resource AUTOSAR_TPS_ECUResource
std
Template Template
Interaction with Behavioral AUTOSAR_TR_InteractionWithB
aux
Models ehavioralModels
Interoperability of AUTOSAR AUTOSAR_TR_InteroperabilityO
aux
Tools fAutosarTools
Specification of Timing AUTOSAR_TPS_TimingExtensio
std
Extensions ns
Specifications of Safety AUTOSAR_TPS_SafetyExtensio New in R4.2.1
std
Extensions ns
AUTOSAR_TPS_Standardization
Standardization Template std
Template
Standardized M1 Models used AUTOSAR_MOD_GeneralDefinit
std
for the Definition of AUTOSAR ions
Supplementary material of aux AUTOSAR_TR_GeneralBlueprint New in R4.2.2
20 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory
- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Long Name Classi- File Name Life cycle

fication changes
general blueprints for AUTOSAR sSupplement
Supplementary material of the AUTOSAR_TR_XMLSchemaSup
aux
AUTOSAR XML Schema plement
AUTOSAR_TPS_SystemTemplat
System Template std
e
Cluster: Application Interfaces
Application Design Patterns AUTOSAR_TR_AIDesignPattern New in R4.2.1
aux
Catalogue sCatalogue
AUTOSAR_MOD_AISpecificatio
Application Interface Examples aux
nExamples
Application Interfaces User
aux AUTOSAR_EXP_AIUserGuide
Guide
Explanation of Application
Interfaces of Occupant and AUTOSAR_EXP_AIOccupantAn
aux
Pedestrian Safety Systems dPedestrianSafety
Domain
Explanation of Application
AUTOSAR_EXP_AIBodyAndCo
Interfaces of the Body and aux
mfort
Comfort Domain
Explanation of Application
aux AUTOSAR_EXP_AIChassis
Interfaces of the Chassis Domain
Explanation of Application
AUTOSAR_EXP_AIHMIMultimed
Interfaces of the HMI, Multimedia aux
iaAndTelematics
and Telematics Domain
Explanation of Application
Interfaces of the Powertrain aux AUTOSAR_EXP_AIPowertrain
Engine Domain
Requirements on SW-C and
aux AUTOSAR_RS_SWCModeling
System Modeling
SW-C and System Modeling AUTOSAR_TR_SWCModelingG
aux
Guide uide
Unique Names for
Documentation, Measurement
AUTOSAR_TR_AIMeasurement
and Calibration: Modeling and aux
CalibrationDiagnostics
Naming Aspects including
Automatic Generation
XML Specification of Application AUTOSAR_MOD_AISpecificatio
std
Interfaces n
AUTOSAR_MOD_AISpecificatio
Application Interface Examples aux
nExamples

21 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

5 Remarks to known technical deficiencies

The technical deficiencies per specification are – if applicable – mentioned inside the
respective specification in a chapter called “Known Limitations” which is located after
the table of contents.
There are the following technical deficiencies to be mentioned which are not related
to a specific specification:
 none

There is a major change of one specification which shall be pointed out here:
 Bigger parts of the specification of the SynchronizedTimeBaseManager
(UID 421) have become obsolete
The concept "Global Time Synchronization" was initiated to improve the
functionality of the SynchronizedTimeBaseManager significantly. It has been
incorporated for R4.2.1, therefore bigger parts of the specification of the
SynchronizedTimeBaseManager (UID 421) have become obsolete. This
module was not in broad use up to now, so AUTOSAR has opted for the
backward incompatible change and removed the obsolete parts (instead of
labeling them).

22 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

6 Revision history
6.1 Release 4.2.1
Revision 1 of Release 4.2.has been released on the 31th of October 2014. The
following deliverables had major changes.

Name Specification history entry

Application Design - First Release of document. Patterns covered:
Patterns Catalogue o Sensor and Actuator Pattern
o Arbitration of Several Set-point Requester
Pattern
- Previously published as part of
EXP_AIPowertrain.
Application Interfaces User - Sensors and Actuators Pattern adopted in the AI Domain
Guide - Obsolete AI Table substituted by new official AI Tool for content
development phase and arxml generation
- Enhanced collections arxml deliverables structure
AUTOSAR Feature Model - Added [TPS_FMDT_00064]
Exchange Format
Basic Software Module - Extended splitables for BSW
Description Template - Added Uses-Case descrpitions for BSW modules
- Editorial changes
Complex Driver design - Update for TcpIp
and integration guideline
Diagnostic Extract - Initial Release
Template
Example for a Serialization - Added SD Peer Identification
Protocol (SOME/IP) - Extended Error Handling
- Minor corrections and clarifications
Explanation of Application - Changing Status->state; current, actual -> consolidate after
Interfaces of the Chassis Harmonization with Engine
Domain
Explanation of Application - Chapter “Sensor/Actuator Design Pattern” moved to new document
Interfaces of the “AIDesignPatternsCatalogue”
Powertrain Engine Domain Integrate new interfaces / update existing interfaces for network
representation of engine & transmission interfaces
General Requirements on - Alignment of post-build configuration to SWS_BSWGeneral
Basic Software Modules - Rephrasing of definition of runtime errors
- Incorporation of concept SupportForPBLAndPBSECUConfiguration
- Editorial changes
General Requirements on - Support variant rich Special Data
Methodology and
Templates
General Specification of - Update in error handling classification
Basic Software Modules - Update in initialization function requirements
Updated due to SupportForPBLAndPBSECUConfiguration concept
- minor corrections / clarifications / editorial changes; For details
please refer to the BWCStatement
General Specification on - Initial Release
Transformers
Generic Structure - Propagation of LifeCycleState
Template Editorial changes
Glossary - Following terms changed:
Data Variant Coding (3.65)
OS-Application (3.168)
Post-build time configuration (3.179)

23 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

Guide to BSW Distribution - Incorporation of concept “Mechanisms and constraints to protect
ASIL BSW against QM BSW”
Minor clarifications
Guide to Mode - Incorporation of Concept "EcuMFixedMC"
Management Clarified LIN Schedule Table Switching
Integration of Franca IDL - Initial Release
Software Component
Descriptions
Layered Software - Incorporated new 4.2 concepts for: Switch Configuration; Sender-
Architecture Receiver-Serialization; CAN-FD; Large-Data-COM; E2E-Extension;
Global Time Synchronization; Support for Post-build ECU-
Configuration; Secure-Onboard-Communication; ASIL/QM-
Protection
Introduction of new error classification
Editorial changes
List of Basic Software - Added COMBased-Transformer
Modules - Added E2E-Transformer
- Added SOME/IP-Transformer
- Added Ethernet Switch Driver
- Added Large Data COM
- Added Secure Onboard Communication
- Added Global Time Synch Modules
Main Requirements - New requirement for Secure Onboard Communication
- New requirement for naming schemes and conventions
Methodology - Support for Safety Extensions added
- Support for Diagnostic Extract added
- Support for Rapid Prototyping added
- Support for Sender Receiver Serialization
added
Model Persistence Rules - Formal adaptations concerning traceability
for XML
Overview of Functional - Initial Release
Safety Measures in
AUTOSAR
Recommended Methods - Editorial changes only: improvements, corrections and additions.
and Practices for Timing - New chapter End-to-End Timing Analysis for
Analysis and Design within Distributed Functions;
the AUTOSAR - Chapter Properties and Methods for Timing
Development Process Analysis: additional information and restructuring;
Added further use-cases;
Added examples, see figures 1.2, 3.1 and 4.1;
Added index at the end of the document;
Release Overview and - added
Revision History
Requirements on - Incorporation of features for new R4.2 concepts
AUTOSAR Features Added chapter “Standardization and Documentation”
- Added features for LinTP and DoIP
- Minor corrections
Requirements on Basic - Layout update.
Software Module - Tracing update.
Description Template
Requirements on CAN - Added requirements for CAN FD support
Removed requirements for transmit cancellation
Requirements on - added support for Large Data COM
Communication - added support for Sender/ Receiver Serialization
- updated to support CAN FD

24 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

Requirements on - Support of WWH-OBD (Major change)
Diagnostic - Support of UDS service $38 (“RequestFileTransfer”), (Change)
- Added new requirements for runtime errors and transient errors
(Change)
- Aging of events (Change)
Requirements on - Initial Release
Diagnostic Extract
Template
Requirements on E2E - Initial release
Communication Protection
Requirements on ECU - Updated [RS_ECUC_00008].
Configuration - Added [RS_ECUC_00085].
- Added [RS_ECUC_00086].
- Tracing update
Requirements on ECU - Layout update.
Resource Template
Requirements on Ethernet - Introduction of IPv6 for in-vehicle communication
Support in AUTOSAR - Support for Global Time Synchronization over Ethernet
- Support for Switch Control/Configuration, Semi-Static Auto-
Configuration
- TcpIp generic upper layer support (CDD)
Requirements on Gateway - Support of multi-frame TP fanout added
Requirements on GPT - New RS feature linked to GPT Predef Timer requirements
Driver
Requirements on - added requirement for naming conventions
Interoperability of [RS_IOAT_00003]
AUTOSAR Tools - minor editorial changes
Requirements on I-PDU - added Multiple PDU to Container Mapping
Multiplexer extension of IpduMSelectorFieldLength
Requirements on Libraries - Removed the section "5.1.7
- Added polynomial to CRC Library
Requirements on LIN - Changed [SRS_Lin_01564] Schedule Table change request
buffering
Requirements on Memory - Requirements linked to BSW features
Hardware Abstraction
Layer
Requirements on Memory - Requirements linked to BSW features
Services
Requirements on - Support for Safety Extensions added
Methodology - Support for Diagnostic Extract added
Requirements on Mode - Moved former SWS EcuM item describing the handling of sleep
Management modes / shutdown targets to SRS level
- Removed Defensive Behavior
Requirements on Module - Removing the limitation "Flash Programming for ECU development
XCP purposes"
- Editorial changes
Requirements on - Incorporation of concept “Mechanisms and constraints to protect
Operating System ASIL BSW against QM BSW”

25 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

Requirements on Runtime - Added support for concepts:
Environment – NVDataHandlingRTE: [SRS_Rte_00245]
– EfficientCOMforLargeData:
[SRS_Rte_00246]
- SenderReceiverSerialization:
[SRS_Rte_00247], [SRS_Rte_00248],
[SRS_Rte_00249], [SRS_Rte_00250],
[SRS_Rte_00251]
- Added requirement: [SRS_Rte_00252]
Requirements on Safety - Initial release based on Concept "‘Safety extensions"’
Extensions
Requirements on Secure - Initial Release
Onboard Communication
Requirements on Software - Added requirements for configuration of data
Component Template transformation.
- Added requirement for naming conventions
Requirements on - extend traceability to new document artefacts
Standardization Template
Requirements on - Concept "Global Time Synchronization" incorporated to replace
Synchronized Time-Base (and by that improve) original functionality and to support new
Manager functionality, e.g.:
support of CAN and Ethernet
support for gateways to enable time domains spanning several
busses
Due to deficiencies R4.0/1 content has been removed (e.g.
customer API + polling of time-base providers). Exception: API to
synchronize OS schedule tables.
Requirements on System - Added requirements [RS_SYST_00049],
Template [RS_SYST_00050], [RS_SYST_00051],
[RS_SYST_00052], [RS_SYST_00053],
[RS_SYST_00054], [RS_SYST_00055],
[RS_SYST_00056]
Requirements on Time - New RS_BRF_ feature linked to all requirements
Service
Requirements on - Initial Release
Transformer
Software Component - Efficient NV data handling
Template - Introduction of data transformation
- Support for variable-size Arrays of arbitrary
data types
- Support for ASIL/QM development
- Minor corrections / clarifications / editorial
changes; For details please refer to the
BWCStatement
Specification of Large - Initial Release
Data COM
Specification of RTE - Efficient NV data handling
Software - Introduction of data transformation
- Support for variable-size Arrays of arbitrary
data types
- Various fixes and clarifications
Specification of a - Optimizations
Diagnostic Communication - Editorial changes
Manager for SAE J1939
Specification of a Request - Improved interaction with COM
Manager for SAE J1939 Harmonized with SWS BSW General

26 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

Specification of a - Removed obsolete configuration elements
Transport Layer for SAE Harmonized with SWS BSW General
J1939
Specification of ADC - AdcGroupId is changed to pre-compile time value in all variants.
Driver
Specification of Basic - New API and configuration containers to support EcuM Fixed for
Software Mode Manager Multi Core
- Addition of new container for defining mode values:
BswMCompuScaleModeValue
- New Action BswMFrSMAllSlots for invoking
- FrSM_AllSlots
- New requirements for: Action list execution (SWS_BswM_00223)
and Deadline Monitoring (SWS_BswM_00224,00225)
Specification of Bit - Correct usage of const in function declarations
Handling Routines - Editoral changes
Specification of CAN - Full CAN FD Support (incl. Trigger Transmit)
Driver - Removed CanIf_CancelTxConfirmation
- Time-out and wake up event handling
- Small improvements and minor bug-fixes
Specification of CAN - Full CAN FD Support
Interface - Global Time Synchronization over CAN
- Removed CanIf_CancelTxConfirmation
- Small improvements
Specification of CAN - Removed obsolete configuration parameters
Network Management - Partial Network Handling Improvements
- Const usage in APIs reworked
Specification of CAN State - API for ECU passive mode activation
Manager - Baudrate change without reinitialisation, if possible
- Interface handling to CanIf module improved
- Interface handling to ComM module improved
Specification of CAN - Revised the configuration of CAN Tranceiver.
Transceiver Driver - Minor corrections in wait state functionality.
- Clarification regarding the wakeup sources.
Specification of CAN - Introduced support for CAN Flexible Data rate
Transport Layer - Minor corrections
- Clarifications
Specification of COM - Initial Release
Based Transformer
Specification of - added support for Sender/ Receiver Serialization
Communication - updated to support CAN FD
- minor corrections
Specification of - Release of PNC related FULL_COM request already upon leaving
Communication Manager PNC_REQUESTED
- Several clarifications
- Minor corrections
Specification of - MetaData information is added in PduInfoType
Communication Stack
Types
Specification of Compiler - The compiler symbol definitions are not allowed to contain any
Abstraction value behind the symbol
- Rework the document structure in order to follow TMPS_SRS_SWS
and replace hardcoded diagrams with artifacts
- Remove all MISRA/ C/ C++ related statements and references
- Correct the unresolved references that point in SRS_BSWGeneral

27 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

Specification of Core Test - CORTST_E_CORE_FAILURE extended production error
formalization, including healing.
- Correction of CorTst_GetCurrentStatus prototype
Specification of CRC - Introduction of a new CRC-32 with the polynomial 0xF4ACFB13
Routines - Editorial changes
Specification of Crypto - Obsolete configuration elements removed
Service Manager - Error fixing and consistency improvements
- Editorial changes
Specification of Debugging - Removed Post Buid information
in AUTOSAR - Other small modifications
Specification of Default - Extended & renamed DevelopmentErrorTracer to
Error Tracer DefaultErrorTracer by adding routines
- New Routines Det_ReportRountineError and
Det_ReportTransientFault
- New configuration paramaters
- Det_ReportRountineErrorCallout and
Det_ReportTransientFaultCallout
Specification of Diagnostic - Update to ISO 14229-1:2013 (Order of NRCs, SID 0x19 and 0x28
Communication Manager extended subfunctions, SID 0x38)
- Specify security mechanisms (security Lock time, static seed).
- Refine service ReadDataByPeriodicIdentifier (0x2A) and provide
UUDT transfer.
- Reorganize the configuration parameters for the routines.
Specification of Diagnostic - Support of ISO 27145 (WWH-OBD / Euro VI)[1]
Event Manager - Update to support ISO 14229-1:2013[2]
- Introduction of event dependencies
- Refined DTC/Event suppression
Specification of Diagnostic - Changed requirements: SWS_Dlt_00515, SWS_Dlt_00516,
Log and Trace SWS_Dlt_00332, SWS_Dlt_0028
Specification of Diagnostic - Harmonization of identical APIs within BSW
over IP - Handling UUDT messages within DoIP
Harmonization of callback functions and configuration parameter
names
- Editorial changes
Specification of DIO Driver - DIO: ReadChannelGroup / WriteChannelGroup pointer parameters.
Provided support for Link time only.
- The generation of link-time parameters aggregated by a
postBuildChangeable container may not be possible. Reference to
SWS_BSW_00380 is removed.
Specification of ECU - Improved description of Post-build variants
Configuration - Improved Post-build loadable approach
- Introduction of Uri References
- Minor corrections / clarifications / editorial
changes; For details please refer to the
BWCStatement
Specification of ECU - Layout update
Resource Template
Specification of ECU State - Added switch configuration
Manager - Defined initialization order for InitListZero/InitListOne
- Definition of the name pattern of c-init-data struct corrected
- Type conflicts solved
- Editorial changes
Specification of ECU State - Incorporation of MultiCore concept
Manager with fixed state - Defined initialization order for InitListZero/InitListOne
machine - Definition of the name pattern of c-init-data struct corrected
- Editorial changes

28 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

Specification of EEPROM - Requirements linked to BSW features, general and module specific
Abstraction requirements
Specification of EEPROM - Added pass/fail criteria and additional attributes for extended
Driver production errors
- Removed redundant SWS IDs with respect to NULL_PTR check for
Eep_Init()
Specification of Ethernet - Change from Synchronous to Asynchronous API
Driver gPTP Timestamp Support
- Enhanced Production Errors
- Changed Access to Statistic Frame Handling Registers
Specification of Ethernet - Change from Synchronous to Asynchronous API
Interface gPTP Timestamp Support
- Ethernet Switch Support
- Ethernet Wakeup Support
Specification of Ethernet - Change from Synchronous to Asynchronous API
State Manager Additional callback functions added
- Existing behavior of functions changes
- Editorial changes
Specification of Ethernet - Change from Synchronous to Asynchronous API
Transceiver Driver Ethernet Wakeup Support
Specification of Extended - Added:
Fixed Point Routines New Variants for SWS_Efx_00412 (0xE2 - 0xE9)
Note has been added for SWS_Efx_00053, SWS_Efx_00072 &
Section 8.5.3.1.
A statement has been added to clarify the formula used for
Hypotenuse function just below the section 8.5.9
A statement has been added to provide more clarity on the formula
mentioned in SWS_Efx_00451

Modified:
Updated usage of const in a consistent manner in EFX document.
(SWS_Efx_00050, SWS_Efx_00067, SWS_Efx_00085,
SWS_Efx_00519, SWS_Efx_00107, SWS_Efx_00122,
SWS_Efx_00146, SWS_Efx_00172, SWS_Efx_00205,
SWS_Efx_00379 & SWS_Efx_00404)
Formula for TeQ_<size> has been corrected in section 8.5.3.1 and
font has been updated for SWS_Efx_00071
Condition check included for SWS_Efx_00053, SWS_Efx_00072 &
Section 8.5.3.1 and corrected for SWS_Efx_00054,
SWS_Efx_00073 & SWS_Efx_00504. Formula updated for
SWS_Efx_00073.
Specification of Fixed - Added:
Point Interpolation IFX RecordLayout Blueprint reference in section 3.1
Routines Modified:
The usage of const is corrected in function parameters for
SWS_Ifx_00004, SWS_Ifx_00014, SWS_Ifx_00015,
SWS_Ifx_00017, SWS_Ifx_00020, SWS_Ifx_00022,
SWS_Ifx_00025, SWS_Ifx_00027, SWS_Ifx_00030,
SWS_Ifx_00032, SWS_Ifx_00205 & SWS_Ifx_00209.
Serial numbers in Section 3.2
Specification of Fixed - Minor corrections and clarifications
Point Math Routines
Specification of Flash - Requirements linked to features and BSW requirements.
Driver
Specification of Flash - Requirement for blank checking added
EEPROM Emulation - Requirements linked to features, general and module specific
requirements

29 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

Specification of Flash Test - Formal text modifications in: SWS_FlsTst_00138,
SWS_FlsTst_00140, SWS_FlsTst_00142, SWS_FlsTst_00143,
SWS_FlsTst_00071, SWS_FlsTst_00115, SWS_FlsTst_00116,
SWS_FlsTst_00117, ECUC_FlsTst_00160, Figure 7/8/9/10
ECUC_FlsTst_00086: configuration
- FlsTstConfigurationOfOptApiServices added
Specification of FlexRay - Clarification regarding NULL pointer handling
AUTOSAR Transport - Removed obsolete ECU configuration elements
Layer
Specification of FlexRay - Removed obsolete configuration parameters
Driver - Improved description of extended production errors
Specification of FlexRay - Support for GlobalTimeSynchronization added
Interface - Minor corrections
Specification of FlexRay - Added FRTP_TIME_CS in table 2, FRTP_TIMEOUT_BR and
ISO Transport Layer FRTP_TIMEOUT_CS in table3.
- Updated for “Use cases for NULL_PTR in CopyRxData and
CopyTxData should be allowed”.
- Updated SWS_FrTp_01132, SWS_FrTp_01140,
SWS_FrTp_01146, SWS_FrTp_01148, SWS_FrTp_01150 for
FRTP_E_PARAM_POINTER.
- Added FRTP_E_INIT_FAILED in the SWS_FrTp_01132 (table).
Specification of FlexRay - Correction of Partial Networking aggregation algorithm
Network Management - Harmonize description of identical API’s
- Const usage consistent in specifications
Specification of FlexRay - Changed development error checking of FrSM_Init pointer
State Manager parameter.
- Editorial changes
Specification of FlexRay - Reworked development and production errors according to the new
Transceiver Driver SWS_BSWGeneral
- Supports multiple branch ids per transceiver
- Supports new busy wait time service
Specification of Floating - Added:
Point Interpolation IFL RecordLayout Blueprint reference in section 3.1
Routines - Modified:
The usage of const is updated in function parameters for
SWS_Ifl_00010, SWS_Ifl_00021 & SWS_Ifl_00025
- IFL Blueprint modified for the schema version
Serial numbers in Section 3.2
Specification of Floating - Added:
Point Math Routines New Functions are added to convert values between Float and
Integer. (SWS_Mfl_00837, SWS_Mfl_838, SWS_Mfl_840,
SWS_Mfl_841 & SWS_Mfl_842)
- Modified:
BSWUML Model was updated for "Mfl_FloatToIntCvrt_f32" &
"Mfl_IntToFloatCvrt" functions. (SWS_Mfl_00836 & SWS_Mfl_839)
Updated usage of const in a consistent manner.
Specification of Function - Simplification of FiM configuration
Inhibition Manager - Support of "Monitored Components"
- Postbuild configuration clean up
- Editorial changes
Specification of GPT - Init pointer check harmonized with BSW_General, redundant
Driver SWS_GPT_00294, SWS_GPT_00340 items removed
- Added new error code GPT_E_INIT_FAILED

30 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

Specification of ICU Driver - IcuChannelId: postBuildVariantValue set to false
SWS IDs with respect to NULL_PTR check for Icu_Init() removed
ICU_E_PARAM_POINTER and ICU_E_INIT_FAILED added to
Error classification
- ICU_E_PARAM_CONFIG and ICU_E_PARAM_BUFFER_PTR
removed from Error classification
Specification of - added requirement for naming conventions
Interoperability of [RS_IOAT_00003]
AUTOSAR Tools minor editorial changes
Specification of I-PDU - Added Multiple PDU to Container Mapping
Multiplexer Extension of IpduMSelectorFieldLength
Specification of LIN Driver - Replaced SWS_Lin_00064 with SWS_Lin_00268
Specification of LIN - Changed the description of return value E_NOT_OK for
Interface LinIf_Wakeup
Changed the parameter LinIfFrameRef.upperMultiplicity from '*' to
'1'
Revised the typo in SWS_LinIf_00614
Editorial changes
Specification of LIN - Added SWS_LinNm_00172 for LinNm_ConfigType, LINNM170 for
Network Management LinNm_MainFunction, ECUC_LinNm_00027 for LinNmTimeoutTime
and ECUC_LinNm_00028 for LinNmMainFunctionPeriod.
Updated SWS_LinNm_00029 and SWS_LinNm_00054 for LinNm
initialization ConfigPtr.
Updated “Figure 7-1”, “Figure 7-2” and “9.2 LinNm_PassiveStartUp”
to enter the Lin channel into sleep mode once the
LinNmTimeoutTime elapsed in passive startup.
Updated the requirements for const usage in function parameters.
Specification of LIN State - Removed NULL pointer check requirement ( moved to BSW
Manager General
- Corrections in ECU parameter configuration
Specification of LIN - Supports Time service for transceiver state change waits
Transceiver Driver
Specification of MCU - Removed requirements for NULL pointer checking as redundant
Driver with BSW General.
- Specified pass/fail criteria for extended production errors
Specification of Memory - Requirements linked to features, general and module specific
Abstraction Interface requirements
Specification of Memory - Support partitioning of BSW for safety systems
Mapping - Remove obsolete memory sections in
Recommendation A
- Clarifications about the handling of SIZE and
ALIGNMENT
- editorial changes
Specification of Module - Initial release
E2E Transformer
Specification of Module - Editorial corrections.
XCP - Minor corrections.
- Changed the multiplicity of XcpEventChannelTriggeredDaqListRef.
Remove limitation "Flash Programming for ECU development
purposes".
Specification of Network - Enhanced description of extended production error
Management for SAE J1939NM_E_ADDRESS_LOST
J1939 - Fixed usage of ‘const’ in NM APIs
- Harmonized with SWS BSW General

31 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

Specification of Network - Corrections on the requirement tracing
Management Interface - Clarification at use of callback versus callout
- Editorial changes
Specification of NVRAM - Detailed pass/fail conditions for production errors
Manager - Added the NvM_ValidateAll functionality
Updated return values for Init and SingleBlock callbacks
- Other small clarifications
Specification of OCU - Set the postBuildVariantValue and postBuildVariantMultiplicity to
Driver false and also
set the valueConfigClass and the multiplicityConfigClass for all
variants to preCompile.
- Removal of automatically supported BSW requirement. Reference
to SWS_BSW_00380 is removed.
Specification of Operating - Add support for AsilQmProtection
System - Minor updates/clarification of descriptions
- Editorial changes
Specification of PDU - Support multi-frame TP fanout
Router CAN-FD and SecOC Concept incorporation
Improved Cancel Transmission handling in case of gatewaying
- Editorial changes
Specification of Platform - removed SWS_Platform_00063 as the influence of Post-build time
Types configuration parameters on header files is already specified in
SWS_BswGeneral
Specification of Predefined - Complete list of Module Abbreviation for each
Names in AUTOSAR AUTOSAR document
- Include additional keywords
Specification of PWM - Updated trace reference for code file structure requirement
Driver
Specification of RAM Test - Added Pass/Fail Criterias for Extended Production Errors
Specification of Secure - Initial Release
Onboard Communication
Specification of Service - Fixed Service Migration support at client side
Discovery - Support for more efficient SoAd interface
- Optimized StopSubscribe/Subscribe load
Specification of Socket - Introduction of IPv6 for in-vehicle communication
Adaptor - Support for Service Migration of Service Discovery Clients
(SpecificRoutingGroup Handling)
- SoAd_RequestIpAddrAssignment API extension
Clarifications and corrections of requirements and sequence charts
Specification of SOME/IP - Initial Release
Transformer
Specification of SPI - Added SWS_Spi_00383, SWS_Spi_00384, SWS_Spi_00385,
Handler/Driver SWS_Spi_00386 and ECUC_Spi_00243
- New configuration parameter
- SpiUserCallbackHeaderFile
- SPI hardware error is applicable for sync and async transmits
- Editorial changes
Specification of SW-C - Introduction of E2E profiles 4, 5, 6
End-to-End - Introduction of E2E state machine
Communication Protection - Introduction of init functions and status mapping fucntions for
Library profiles 1, 2
- Overview of wrapper, by means of several new diagrams.

32 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

Specification of - Concept "Global Time Synchronization" incorporated to replace
Synchronized Time-Base (and by that improve) original functionality and to support new
Manager functionality, e.g.:
support of CAN and Ethernet
support for gateways to enable time domains spanning several
busses
Due to deficiencies R4.0/1 content has been removed (e.g.
customer API + polling of time-base providers). Exception: API to
synchronize OS schedule tables.
Specification of TCP/IP - Introduction of IPv6 for in-vehicle communication
Stack - Support for Switch Control/Configuration, Semi-Static Auto-
Configuration
- TcpIp generic upper layer support (CDD)
- Clarifications and corrections of requirements and sequence charts
Specification of Time - Initial Release
Synchronization over CAN
Specification of Time - Initial Release
Synchronization over
Ethernet
Specification of Time - Initial Release
Synchronization over
FlexRay
Specification of Timing - Added the capability in Execution Order
Extensions - Constraint to reference RTE and BSW Events
- Added description about how to specify time
sets
- Minor corrections / clarifications / editorial
changes; For details please refer to the
BWCStatement
Specification of TTCAN - Updated disclaimer
Driver - Editorial changes
Specification of TTCAN - Improved extended production error description
Interface - Updated disclaimer
- Editorial changes
Specification of UDP - Harmonization of API description
Network Management - Revised Partial Networking Requirements
- Extended Production Errors
- Editorial Changes
Specification of Watchdog - Adapt specification of extended production errors.
Driver - WDG_E_INIT_FAILED added (error code is referenced by
SWS_BSWGeneral)
Specification of Watchdog - Introduced of the modeling of system services
Manager - Reformulated some requirements to constraints
- Minor corrections
Specification on Ethernet - Initial Release
Switch Driver
Specifications of Safety - Initial specification based on Concept "‘Safety
Extensions Extensions"’
Standardization Template - introduction of Blueprint Policy
- include safety extension relevant items
- extension of acceptanace test items

33 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

SW-C and System - Generic CompuMethods reuse mechanism
Modeling Guide - enhanced through new modeling rules
- Extended naming rules and recommendations for Long Names
standardization
- Extended description of blueprint mechanism applied to Application
Interfaces Domain
System Template - Introduction of data transformation
- Introduction of SecuredIPdu
- Introduction of Switch Configuration
- Introduction of Global Time Synchronization
- Improved support for CanFD
- Minor corrections / clarifications / editorial
changes; For details please refer to the
BWCStatement
Unique Names for - P/L-List now also available as .arxml as part of
Documentation, MOD_AISpecification
Measurement and
Calibration: Modeling and
Naming Aspects including
Automatic Generation
Virtual Functional Bus - Introduction of PRPortPrototype

More specifications might have been changed, which are not listed here. Those
specifications have then only “minor corrections, clarifications or editorial changes;
for details please refer to the Change Documentation [3].

34 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

6.2 Release 4.2.2

Revision 2 of Release 4.2.has been released on the 31th of July 2015. The following
specifications had major changes.

Name Specification history entry

- reconsideration of signal definitions and tailored
pattern for smart actuators and actuators with no
Application Design
feedback loop
Patterns Catalogue
- specification items added
- minor changes
Application Interfaces User - Updated explanation of the COMPU_METHOD reusage
Guide - Updated the Linear Conversion Example
AUTOSAR Specification - Initial Release
Hashes
Change Documentation - Initial Release
Complex Driver design - Update for Default Error Tracer
and integration guideline - Re-entrancy of interfaces
Explanation of Application - Chapter “Timing and Accuracy Requirements to Torque
Interfaces of the Signals” and related figure removed and moved into description of
Powertrain Engine Domain related Interfaces in AI-Tool
- Introduce new requirement SRS_BSW_00403
General Requirements on - Introduce new requirement SRS_BSW_00351
Basic Software Modules - Modified requirement SRS_BSW_00406 and SRS_BSW_00450
- Debugging support marked as obsolete
- Debugging support marked as obsolete
General Specification of
- minor corrections / clarifications / editorial changes; For details
Basic Software Modules
please refer to the ChangeDocumentation
- Transformation of intra-ECU communication
- Transformation of external-trigger events
General Specification on
- Autonomous error responses of transformers
Transformers
- Minor corrections / clarifications / editorial changes;
For details please refer to the ChangeDocumentation
- Update View Approach
Generic Structure
- Combinations of status values
Template
- Update Inline Text Model Element
- Following terms changed:
- ECU Abstraction Layer (3.74)
Glossary - Standardized AUTOSAR Interface (3.224)
- Following terms removed:
- Software Module
Guide to Mode - Description of wakeup handling on multiple cores
Management - Description of inter-partition mode communication
Interaction with Behavioral - Long name of document changed
Models
List of Basic Software - Adopted name for "DefaultErrorTracer"
Modules
Overview of Functional - New Chapter: „Hardware Diagnostics“ covers Core Test and RAM
Safety Measures in Test.
AUTOSAR - Minor corrections / clarifications / editorial changes.
Predefined Names in - Include abbreviations for Acceptance Tests
AUTOSAR

35 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

- Section 6.3: introduced basic timing tasks like
“Collect Timing Requirement” or “Create Timing
Recommended Methods Model”. Adapted introduction of chapter 6
and Practices for Timing accordingly.
Analysis and Design within - Clarified relation of the timing properties described
the AUTOSAR in section 6.4 to AUTOSAR TIMEX.
Development Process - improved glossary and index
- New figures for improved overview of use-cases
(figures 3.2 and 4.2)
Release Overview and - Update according to revision 4.2.2
Revision History
Requirements on - Debugging features marked as obsolete
AUTOSAR Features - Added missing memory stack features
Requirements on Basic - Set Debugging support to obsolete
Software Module [RS_BSWMD_00061].
Description Template
Requirements on - Marked the document as obsolete
Debugging in AUTOSAR
- Clarification of bootloader interaction
Requirements on
- Interfaces for DCM communication via PDU router
Diagnostic
- Rework of document structure
Requirements on Function - Fim considers EventAvailbilty/ EventSuppression
Inhibition Manager
Requirements on - added use case section that was part of the
Interoperability of TR_IOAT
AUTOSAR Tools
Requirements on Memory - Requirements linked to BSW features
Hardware Abstraction
Layer
Requirements on Memory - Requirements linked to BSW features
Services
Requirements on Mode - Clarified post-build configurability of some requirements
Management
Requirements on RAM - Update of the document for Diverse corrections
Test - Editorial changes
Requirements on Runtime - Added requirement: [SRS_Rte_00253]
Environment
Safety Use Case Example - Initial Release
- Fixed TriggerTransmit for dynamic length PDUs
Specification of Large
- Added PreCompile configuration class for all symbolicNameValue
Data COM
parameters
Specification of a - Clarifications
Diagnostic Communication - DM01 handling on multiple networks
Manager for SAE J1939 - DM19 updated negative response code
- Fixed names and signatures of service ports
Specification of a Request
- Support for explicit broadcast of ACKM
Manager for SAE J1939
- Introduction of further error classes
Specification of a - Fixed retry behavior
Transport Layer for SAE - Clarified effect of MetaData on SA/DA/Protocol
J1939 - Introduction of further error classes
Specification of ADC - DET changed from ‘Development Error Tracer’ to ‘Default Error
Driver Tracer’.

36 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

- Improved specification of service interfaces
- Additional functional requirements for BswMPduGroupSwitch action
- Added BswMNmIfCarWakeUpIndication as a new
Specification of Basic
BswMModeRequestSource
Software Mode Manager
- Deprecated some spec. elements (marked with “obsolete”), editorial
changes, increased requirement traceability and minor changes to
configuration containers/parameters
- Updated SWS_Bfx_00017 for the return type of Bfx_GetBit function
from 1 and 0 to TRUE and FALSE
- Updated chapter 8.1 for the definition of bit addressing and updated
the examples of Bfx_SetBit, Bfx_ClrBit, Bfx_GetBit, Bfx_SetBits,
Specification of Bit
Bfx_CopyBit, Bfx_PutBits, Bfx_PutBit
Handling Routines
- Updated SWS_Bfx_00017 for the return type of Bfx_GetBit function
from 1 and 0 to TRUE and FALSE without changing the formula
- Updated SWS_Bfx_00011 and SWS_Bfx_00022 for the review
comments provided for the examples
- CanHwObjectCount parameter multiplicity is changed to 1
Error Classification has changed
Specification of CAN - Improved 8.4.2 Enabling/Disabling wakeup notification
Driver - DET has been renamed from "Development Error Tracer" to
"Default Error Tracer
- Small improvements and minor bug-fixes
- Clarified wakeup, buffering, transmit, and variants
Specification of CAN
- Removed deprecated APIs
Interface
- Editorial changes
- Clarification NM message transmission start
Specification of CAN
- Clarification of configuration dependencies
Network Management
- Clarification NM timers while communication is disabled
- Development Error Tracer replaced with Default Error Tracer
Specification of CAN State
- Bus-off recovery time dependencies specified more precisely
Manager
- Optional interface to check and to change baudrate removed
Specification of CAN - Clarification regarding wake-up flag indication
Transceiver Driver - Editorial changes
- File structure correction
Specification of CAN
- FC_OVFL clarification
Transport Layer
- DET Renaming and Extension Incorporation
Specification of COM - Exclude support for external trigger
Based Transformer communication [SWS_ComXf_00032]
Specification of - Chapter added to explain partial network usecase
Communication Manager - Minor corrections
Specification of Compiler - Cleanup the requirements traceability
Abstraction - Clarify the list of compiler symbols
- Correction of CorTst_Init prototype
- Added CorTst_ConfigType and CorTst_ResultType
Specification of Core Test
- Debugging support marked as obsolete
- Minor corrections
Specification of CRC - Corrected the magic check for the CRC32 and CRC32P4
Routines
- Changed return type from Csm_ReturnType to Std_Types in all API
Specification of Crypto functions
Service Manager - Added detailed description of RTE interfaces
- Error fixing and consistency improvements
Specification of Debugging - Marked the specification as obsolete
in AUTOSAR
Specification of Default - Harmonized Traceability
Error Tracer - Ensured consistent usage of development errors in all modules

37 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

- Specify the NRCs to be sent by the Dcm in case of Dem interfaces
return negative values.
Specification of Diagnostic - Clarify Routine operation prototypes
Communication Manager - Debugging support marked as obsolete
- Minor corrections / clarifications / editorial changes; For details
please refer to the ChangeDocumentation
- New APIs Dem_GetEventFreezeFrameDataEx and
Dem_GetEventExtendedDataRecordEx with
buffersize as parameter and corrected return value
defintions.
- Providing OBD FreezFrame for UDS service 0x19
Specification of Diagnostic
0x05
Event Manager
- ISO 14229-1:2013[1] NRC handling for service
0x14
- Refined service interfaces for DataElements
- minor corrections / clarifications / editorial changes;
For details please refer to the ChangeDocumentation
Specification of Diagnostic - Minor corrections
Log and Trace
Specification of Diagnostic - DET Renaming and Extension Incorporation
over IP Support for parallel diagnostic sessions
- DET Renaming and Extension Incorporation
Specification of DIO Driver
- Changed DioChannelId, DioPortId precomplile configuration
- Reworked slave core poll sequence
Specification of ECU State - Reviewed multicore shutdown synchronization
Manager - Reclassified error types
- Editorial changes
- Adaptations related to renaming of DET
Specification of ECU State table for "EcuM_SleepModeType" added
Manager with fixed state missing modules in Table2 "Driver Initialization Details" added
machine - Requirement regarding "state of wakeup sources belonging to
previous sleep modes" added
- Error classification reworked
Specification of EEPROM - Debug support marked as obsolete
Abstraction Parameter ranges corrected
- Job result clarified if requested block can’t be found
Specification of EEPROM - DET renaming and adaptation
Driver - Chapter 7 adaptation for error classification
- Eth_ControllerInit functionality merged into Eth_Init API
Specification of Ethernet
- Development Error Tracer renamed to Default Error Tracer
Driver
- IRQ handler API removed
Specification of Ethernet - EthIf_TransceiverInit and EthIf_ControllerInit removed
Interface - Development Error Tracer renamed to Default Error Tracer
- Harmonize Sequence diagrams, Network State Machine and
Functional Description
- Debugging support marked as obsolete
Specification of Ethernet
Report to DET if TcpIp state is not accepted
State Manager
- Adaptations related to renaming of DET,
- Error Handling: tables for Runtime Errors and Transient Faults
added
Specification of Ethernet - EthTrcv_TransceiverInit functionality merged into EthTrcv_Init API
Transceiver Driver - Development Error Tracer renamed to Default Error Tracer

38 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

- Modified:
- Updated the requirement ID for SWS_Efx_00033 as per the
convention
- Updated requirement ID SWS_Efx_00436 (UML) for
Specification of Extended
OutTypeMn as per the standard convention
Fixed Point Routines
- Updated SWS_Efx_00001 for naming convention under
Section 5.1, File Structure
- Updated SWS_Efx_00365 to correct the data type of input
parameters
- Added:
- Added a new statement in Section 8.5 below the formula to
provide more clarity to the users
Specification of Fixed - Modified:
Point Interpolation - Updated the "Requirements traceability" section
Routines - Updated Record layouts for distributed interpolation
routines in SWS_Ifx_00185
- Updated SWS_Ifx_00001 for naming convetion under
Section 5.1, File Structure
- Modified
Specification of Fixed - Updated SWS_Mfx_00017 for shift value of Function ID
Point Math Routines 0x200 to 0x205 from 64 to 63
- Updated SWS_Mfx_00001 under Section 5.1 File Structure.
- Debugging support marked as obsolete
Specification of Flash - Error classification reworked
Driver - Reference to DEM removed
- Description for configuration parameter FlsUseInterrupts clarified
- Behaviour during FEE_BUSY_INTERNAL reworked
Specification of Flash - Error classification reworked
EEPROM Emulation - Debugging support marked as obsolete
- Job result clarified if requested block can’t be found
- Debugging support marked as obsolete
- ECUC_FlsTst_00119 set to obsolete;
- ECUC_FlsTst_00161 created;
- ECUC_FlsTst_00151 modified (pre-compile only);
- SWS_FlsTst_00023, SWS_FlsTst_00026,
- SWS_FlsTst_00133 removed;
- SWS_FlsTst_00007: Error code 0x05 modified
- SWS_FlsTst_00168 created: Extended production error table with
pass/fail criteria;
- SWS_FlsTst_00161 modified;
- SWS_FlsTst_00167 created;
Specification of Flash Test
- Renaming from Development Error Tracer to Default Error Tracer;
changes in abbreviations, chapter 3.1, SWS_FlsTst_00011;
- Template changes; chapters runtime errors and transient faults
added;
- Formal text modifications in: SWS_FlsTst_00138,
SWS_FlsTst_00140, SWS_FlsTst_00142, SWS_FlsTst_00143,
SWS_FlsTst_00071, SWS_FlsTst_00115, SWS_FlsTst_00116,
SWS_FlsTst_00117, ECUC_FlsTst_00160, Figure 7/8/9/10
- ECUC_FlsTst_00086: configuration
- FlsTstConfigurationOfOptApiServices added

Specification of FlexRay - Changed attribute Ecuc.postBuildVariantValue to false for

AUTOSAR Transport FrArTpSduRxId and FrArTpSduTxId
Layer
Specification of FlexRay - Changed development errors to default errors
Driver

39 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

- Updated the SWS requirements for DET renaming.
Specification of FlexRay
- Updated the SWS requirement SWS_FrTp_01047 and added a
ISO Transport Layer
note for the Tx Pdu processing.
- Clarification on FrNmPassiveModeEnabled
- Clarification on FrNmNumberOfClusters
Specification of FlexRay
- Clarity on scheduling of MainFunction
Network Management
- Debugging support marked as obsolete
- Minor corrections
- Revised development error handling.
Specification of FlexRay - Debugging support marked as obsolete
State Manager - Minor corrections / clarifications / editorial changes; for details
please refer to the ChangeDocumentation
- Redesigned extended production error chapter, updated to default
error tracer
Specification of FlexRay - Added a (dummy) configuration parameter to the initialization
Transceiver Driver interface
- Debugging support marked as obsolete
- Removed chapter(s) on change documentation
- Modified:
Specification of Floating - Updated Record layouts definitions for SWS_Ifx_00170
Point Interpolation - Updated SWS_Ifl_00001 for naming convention under
Routines Section 5.1, File Structure
- Updated valid range for float32 in Table 1 of Section 8.1
- Modified:
- BSWUML Model for "Mfl_HystCenterHalfDelta_f32_u8",
"Mfl_HystLeftRight_f32_u8", "Mfl_HystDeltaRight_f32_u8"
& "Mfl_HystLeftDelta_f32_u8" functions were updated in the
Word Document.
- Statement has been updated for Mfl_DT1Typ1Calc and
Mfl_DT1Typ2Calc to clearly mention the data type for the
Time Equivalent parameter.
- Description field has been updated/rectified for Tv_C and
Tnrec_C parameters in Mfl_ParamPID_Type.
- Updated naming convention for TeQ_f32 Parameter.
- Corrected the description for TeQ_<Size> in section 8.5.4.1
and statement in section 8.5.4.4.
- Naming convention followed for Tnrec Parameter in
Mfl_PISetParam function.
Specification of Floating
- Statement has been updated to correct naming convention
Point Math Routines
for TeQ_f32.
- Updated SWS_Mfl_00001 for naming convention under
Section 5.1, File Structure
- BSWUML Model for "Mfl_ArrayAverage_f32_f32" function
was updated to include pointer to constant to avoid MISRA
violation/warning. (SWS_Mfl_00192)
- Valid range for float32 has been updated in Section 8.2 and
removed float64 data type from Section 8.1, 8.2 and
Section 2
- Deleted:
- Removed the requirements SWS_Mfl_00240,
SWS_Mfl_00245, SWS_Mfl_00250 & SWS_Mfl_00255
- Removed redundant requirements SWS_Mfl_00034,
SWS_Mfl_00046 & SWS_Mfl_00302, which were cov-ered
as part of section 8.5.4.4.

40 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

- Fim considers EventAvailbilty/ EventSuppression
Specification of Function - Modified Initialization Sequence
Inhibition Manager - minor corrections / clarifications / editorial changes; For details
please refer to the ChangeDocumentation
- Det renaming and extension incorporation
Specification of GPT
- Debugging support marked as obsolete
Driver
- Remove duplicated requirements in traceability
Specification of I/O - Updated IoHwAb_Init function protoptype
Hardware Abstraction
- Editorial changes
- DET renamed from "Development Error Tracer" to "Default Error
Specification of ICU Driver Tracer".
- All references to obsolete SWS_Icu_00048 removed from the
document
- Chapter 6 "Requirements traceability" clean up
- Reference to DET are named as “Default” Error Tracer instead of
Specification of LIN Driver “Development” Error Tracer
- Dependency on Module DET listed in Chapter 5 is linked to
SWS_Lin_00048 instead of SWS_Lin_00052
- Removed PostBuildTime from the configuration class of optional
Specification of LIN interfaces
Interface - Changed to call the <User_TriggerTransmit> with the buffer length
- Changed to Default Error Tracer from Development Error Tracer
- Updated the SWS requirements for DET renaming.
- Updated the SWS for LinNmComUserDataSupport.
Specification of LIN
- Removed SWS requirement SWS_LinNm_00040.
Network Management
- Removed SWS numbers LINNM170, LINNM171 and updated with
SWS_LinNm_00173, SWS_LinNm_00174.
- Modified header file structure
Specification of LIN State
- Debugging support marked as obsolete
Manager
- Editorial changes
Specification of LIN - Development Error Tracer replaced with Default Error Tracer
Transceiver Driver - Standardized the initialization function
- Minor change regarding DET renaming and extension Incorporation
Specification of MCU
- Clarifications regarding configuration class of symbolicNameValue
Driver
parameters
- Block result MEMIF_BLOCK_INCONSISTENT extended to blocks
Specification of Memory
which can’t be foundError classification reworked
Abstraction Interface
- Links to requirements added
- Support core scope specific memory allocation
Specification of Memory
- Clean up requirement tracing
Mapping
- editorial changes
Specification of Module - Various minor fixes
E2E Transformer
- Debugging support marked as obsolete
Specification of Module - Editorial corrections.
XCP - Modifications in some parameters multiplicity of XcpDaqlist
container.
Specification of Network - Support for networks without address claiming
Management for SAE - Fixed state notifications to BswM
J1939 - Introduction of further error classes
- "‘Coordination algorithm"’ and "‘Coordinated
shutdown"’ redefined
Specification of Network
- Make the CarWakeup feature available
Management Interface
- Debugging support marked as obsolete
- Editorial changes

41 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

- Clarified behavior related to restoring default data for blocks and for
handling of MEMIF_BLOCK_INVALID job result
Specification of NVRAM - Added additional information related to the block states in chapter
Manager 7.2.2.14 and related subchapters
- Updated NvM_Init and NvM_ValidateAll function prototypes
- Debugging support marked as obsolete
- DET has been renamed.
- SWS_Ocu_00041 and SWS_Ocu_00042 requirements are
Specification of OCU removed.
Driver - OCU_E_PARAM_CONFIG is removed.
- Added OCU_E_INIT_FAILED
- Invalid requirement IDs: Updated SWS_Ocu_156, SWS_Ocu_169
- Allow calls to ControlIdle from all cores
Specification of Operating
- Minor updates/clarification of descriptions
System
- Editorial changes
- Added support of TriggerTransmit for dynamic length PDUs
- Clarification on output parameter 'availableDataPtr' of
PduR_<User:LoTp>CopyTxData
- Clarification for releasing of buffer on return of E_NOT_OK from
<DstLoTp_Transmit> API
Specification of PDU - Clarified behavior for disabled TxPduId of upper layer
Router - Clarified Routing PDUs between local modules
- Cleanup of references to former SoAd API
- DET Renaming and Extension Incorporation
- LdCom asupper module
- Clarification for releasing of buffer on return of
- E_NOT_OK from <DstLoTp_Transmit> API
- Float types shall follow the appropriate binary interchange format of
Specification of Platform
IEEE 754-2008.
Types
- Editorial changes
- Rephrased SWS_Port_00077, SWS_Port_00087,
SWS_Port_00087, SWS_Port_00223
Specification of Port Driver - Editorial changes on Chapter 7
- Remove SWS_Port_0105
- Replace PORT_E_PARAM_CONFIG by PORT_E_INIT_FAILED
Specification of PWM - Removed requirements with respect to NULL_PTR check
Driver - DET has been renamed
- Updated Pass/Fail Criterias for Extended Production Errors
- Debugging support marked as obsolete
Specification of RAM Test
- Diverse corrections
- Editorial changes
- Debugging support marked as obsolete
Specification of RTE
- Minor corrections / clarifications / editorial changes;
Software
- For details please refer to the ChangeDocumentation
- Debugging support marked as obsolete
Specification of Service
- Clarifications
Discovery
- Minor bugfixes
Specification of Socket - Clarifications and corrections of requirements
Adaptor - Editorial changes
- Size of length fields is configurable
- External trigger events are communciated as
fire-and-forget methods
Specification of SOME/IP
- Autonomous error reactions of SOME/IP
Transformer
transformer
- Minor corrections / clarifications / editorial changes;
For details please refer to the ChangeDocumentation

42 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

- Cleanup of requirements chapter
Specification of SPI
- Debugging support marked as obsolete
Handler/Driver
- Editorial changes
Specification of Standard - Harmonized Traceability
Types
- Introduced new E2E state machine profile status
E2E_P_NONEWDATA. Adapted figures, API tables and mapping
functions. This solves an issue with deterministic startup of the state
Specification of SW-C machine.
End-to-End - Updated Figure 7-7, added behavior in case ReceivedCounter is
Communication Protection out of range.
Library - Assigned new specification ID SWS_E2E_00478 to duplicate
specification SWS_E2E_00324 (specification of profile 4).
- Fixed figure 7-6 “Calculate CRC over Data ID and Data”, which was
already fixed in R4.1.2 but falsely included as of R4.1.1.
- Config parameter argument added to StbM_Init
Specification of - StbM_TimeStampRawType changed uint32
Synchronized Time-Base - StbM_BusSetGlobalTime allow NULL as userDataPtr
Manager - 'const' added to input arguments passed by pointer
- Debugging support marked as obsolete
- Support for transmission of fragmented IPv4/IPv6 frames
Specification of TCP/IP
- Clarifications and corrections of requirements
Stack
- Editorial changes
Specification of Time - CanTSyn_SetTransmissionMode changed to return "void"
Synchronization over CAN - minor corrections / clarifications / editorial changes
- <Bus>TSyn_SetTransmissionMode changed to return "void"
Specification of Time
- Call of StbM_BusSetGlobalTime() added - sequence diagrams
Synchronization over
corrected
Ethernet
- 'const' added to input arguments passed by pointer
- Error code FRTSYN_E_INVALID_PDU_SDU_ID replaced by
Specification of Time
FRTSYN_E_INVALID_PDUID
Synchronization over
- FlexRay communication state handling simplified
FlexRay
(FrIf_GetPOCStatus replaced by FrIf_GetState)
Specification of Timing - Minor corrections and editorial changes
Extensions - Added appendices C and D
Specification of TTCAN - Fixed error section
Driver
Specification of TTCAN - Fixed error section
Interface - Editorial changes
- Revised Error Classification
Specification of UDP
- Added support for Car Wakeup
Network Management
- Bug fixes and editorial changes
- Debugging support marked as obsolete
Specification of Watchdog
- minor corrections / clarifications / editorial changes; For details
Driver
please refer to the ChangeDocumentation
Specification of Watchdog - Minor fixes
Interface
- Debugging support marked as obsolete
Specification of Watchdog
- Several minor fixes.
Manager
- Fixed handling of development errors.
- introduction of LifeCycleState for constraint and
Standardization Template specification items
- editorial changes
Supplementary material of - Initial Release
general blueprints for
AUTOSAR

43 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Name Specification history entry

- System Level description introduced in the
CompositionSWComponents domain.
SW-C and System
- IDENTICAL CompuMethods modeling rules aligned to ASAM
Modeling Guide
representation.
- Complete traceability towards Modeling Requirements Document
Virtual Functional Bus - Reference to Application Interfaces

More specifications might have been changed, which are not listed here. Those
specifications have then only “minor corrections, clarifications or editorial changes;
for details please refer to the Change Documentation [3]

44 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

7 Appendix
7.1 Definitions
As far as not explained in this chapter, a collection of AUTOSAR definitions is
provided in 1).

7.1.1 Release number

AUTOSAR applies a two-digit numbering scheme Rx.y to identify Releases. Its

primary purpose is to identify a Release as a major (upgrade, can contain non-
backward-compatible extensions) or as minor (update, backward compatible
extensions) Release. Referring to previous Releases (e.g. R2.0), incrementing the
first digit “x” does identify a Release as major, whereas incrementing “y” will mark a
Release as only minor by nature.

7.1.2 Revision number

The Revision Number was first time introduced with Release 2.1 and extends the
Release Numbering scheme as explained in section 7.1.1. Combined with the
Release Number, the Revision Number shall:

1) Precisely identify the actual content (set of specifications) of a given

Release,
2) As depicted in every specification, precisely identify a given specification
(with its unique name and three-digit version ID) as being part of the
Release

Item 1) addresses the fact that the set of specifications comprising a Release (in the
meaning of a baseline) is rarely established once at a certain point in time
(“Big Bang”), but rather evolves and/or varies over a certain timeframe. The
maximum duration, which is limited by the timeframe, a Release is declared as “valid”
by the AUTOSAR Partnership (see section 7.1.3).

Hence with Item 1), a major prerequisite will be put in place to enable the Standard
Maintenance as planned by the AUTOSAR Partnership. In general, the primary
objective is to avoid the provision of an additional – previously not planned – Release
in case only one or a few specifications were to be modified as part of the Standard
Maintenance. Conversely, without the application of a Revision Number, if the
AUTOSAR partnership wants to avoid the provision of (an) additional intermediate
Release(s), one would have to defer the introduction of any changes until the next
planned Release – even in case of changes urgently needed by the applicants of the
AUTOSAR Standard.

Item 2) is complementary to Item 1) in that for every specification a unique identifier

is provided upon which Revision a) a specification was either 1st time added
to/removed from a Release or b) a specification was modified as being part of one

45 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

and the same Release, as long the latter is valid and therefore subject to Standard
Maintenance.

Hence with item 2), the combination of Release and Revision Number in a
specification can be interpreted either as a) “specification was (1st time) added to the
Release x.y Rev n” or b) as “specification was modified as part of Release x.y
Rev m”, with m > n.

Conversely, the Revision number will only change for specifications subject to
addition or modification of a valid Release (baseline). After their 1 st time addition to
the Release (baseline), it will not change for specifications which are not modified.

In the light of the above provided background, as an additional remark, the Revision
Number will only be applied for each specification’s Release version, i.e. it will not be
applied to working versions.

7.1.3 Release life cycle of a major release

Each major release goes through four consecutive steps within its lifecycle:

1. Development: Between start of life cycle and the initial release (e.g. R4.0.1)
2. Evolution: Following the initial release with zero, one or several minor releases
and/or revisions (e.g. R4.0.2, R4.1.1)
3. Maintenance: No new contents is added to a major release but only
maintenance of the existing content with zero, one or several revisions (e.g.
R3.2.2) is provided
4. Issue Notice: No more revisions but zero, one or several issue notices, i.e.
updates of the list of known issues until end of life cycle.

7.1.4 Standard specifications and auxiliary material

Standard Specifications are documents, models or formats which comprise the main
result of the AUTOSAR Partnership. It includes the standardized results which have
to be fulfilled to achieve AUTOSAR conformance.

In Release 4.2, Standard Specifications are stored at the following URL:

https://svn.autosar.org/repos/work/26_Products/10_CP_R4/02_Releases/R4.2/01_St
andard

Auxiliary Material is a supporting document, model or format meant to further explain

and/or improve the usability of standard specifications of the AUTOSAR partnership.
Auxiliary material is recommended to read and/or use for a better understanding or
harmonized usage of the AUTOSAR standard but is not mandatory to follow for
AUTOSAR conformance.

In Release 4.2, Auxiliary Material is stored at the following URL:

https://svn.autosar.org/repos/work/26_Products/10_CP_R4/02_Releases/R4.2/02_A
uxiliary

46 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -
Release 4.2 Overview and Revision History
AUTOSAR Release 4.2.2

Contents of auxiliary documents remain of auxiliary nature even if they are

referenced from standard documents.

7.1.5 History information in AUTOSAR

The following diagram shows where which changes are documented.

47 of 47 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -