当前位置:首页 >> 交通运输 >>

AUTOSAR


Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1

Document Title
Document Owner Document Responsibility Document Identification No Document Classification Document Status Part of AUTOSAR Release Release Life Cycle Status

Release 4.2 Overview and Revision History
AUTOSAR Release Management 000 Standard Final 4.2.1 R4.2 is in Evolution, R4.2 supersedes R4.1

Document Change History
Date 31.10.2014 Release Changed by 4.2.1 Release Management Change Description Initial release

1 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1

Table of Contents
1 Introduction.......................................................................................................... 3 1.1 1.2 1.3 2 3 Scope of this document ................................................................................ 3 Content of chapters ...................................................................................... 3 History information in AUTOSAR ................................................................. 3

Related documentation........................................................................................ 4 Summary of changes........................................................................................... 5 3.1 Introduced Concepts .................................................................................... 5 3.1.1 CAN Flexible Data Rate ........................................................................ 5 3.1.2 Decentralized Configuration .................................................................. 5 3.1.3 Efficient COM for Large Data ................................................................ 5 3.1.4 Efficient NV Data Handling via RTE ...................................................... 5 3.1.5 Enhancement EcuM Fixed for Multi Core .............................................. 5 3.1.6 Ethernet Configuration and System Description for Manageable Switched Systems ............................................................................................... 5 3.1.7 Extension of E2E Protection.................................................................. 6 3.1.8 Global Time Synchronization ................................................................ 6 3.1.9 Integration of Non-AUTOSAR Systems ................................................ 6 3.1.10 Mechanisms and constraints to protect ASIL BSW against QM BSW ... 6 3.1.11 Safety Extensions for Methodology and Templates .............................. 6 3.1.12 Secure Onboard Communication .......................................................... 6 3.1.13 Sender Receiver Serialization ............................................................... 6 3.1.14 Support for post-build loadable and post-build selectable ECU configuration ........................................................................................................ 6 3.2 Impacts of Concepts..................................................................................... 6

4 5 6 7

Document overview ........................................................................................... 12 Remarks to known technical deficiencies .......................................................... 20 Revision history ................................................................................................. 21 Appendix ........................................................................................................... 34 7.1 Definitions .................................................................................................. 34 7.1.1 Release number .................................................................................. 34 7.1.2 Revision number ................................................................................. 34 7.1.3 Release life cycle of a major release................................................... 35 7.1.4 Standard specifications and auxiliary material .................................... 35 7.1.5 Release clusters.................................................................................. 36

2 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1

1 Introduction
1.1 Scope of this document
This document provides an overview of the complement of AUTOSAR documents comprising the initial Release 4.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 documents comprising the Release 4.2 in its latest Revision 0. 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 documents. ? Chapter 7.1 provides a set of definitions aimed to increase the understanding of the content of this document and the Release 4.2.

1.3 History information in AUTOSAR
The following diagram shows where which changes are documented.

3 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1

2 Related documentation
[1] [2] [3] [4] Release Overview and Revision History AUTOSAR Documents in general Backward Compatibility Statement Glossary Glossary

4 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1

3 Summary of changes
This chapter contains a summary of changes which were implemented since the previous Release 4.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 Introduced Concepts
The following concepts have been introduced. 3.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.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.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.4 Efficient NV Data Handling via RTE An efficient mechanism for software components (SW-Cs) in order to handle nonvolatile (NV) data via RTE. 3.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.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.

5 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 3.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.8 Global Time Synchronization Mechanisms to distribute one or more master time bases across various busses and bus systems. 3.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.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.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 metamodel. 3.1.12 Secure Onboard Communication Standardization of security mechanisms to protect communication on in-vehicle networks. 3.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.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.2 Impacts of Concepts
The introduced concepts had impact on several documents. The following table provides a detailed overview. Please note that some of the documents are marked by special text formatting. ? Documents in bold font are completely new documents originating from the particular concept. ? Documents in italic font are affected indirectly as they provide artefacts for the actually impacted specifications.

6 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1
Affected documents Concept Name Document Long Name Clasifiaction

CAN Flexible Datarate

Decentralized Configuration

Efficient COM for Large Data

Efficient NV Data Handling via RTE
7 of 36

Specification of CAN Driver Specification of CAN Interface Specification of CAN Transport Layer Specification of Communication Specification of Diagnostic Communication Manager Specification of ECU Configuration Parameters (XML) Specification of I-PDU Multiplexer Specification of PDU Router System Template Basic Software UML Model Layered Software Architecture Requirements on AUTOSAR Features Requirements on CAN Requirements on Communication Requirements on I-PDU Multiplexer Requirements on System Template Diagnostic Extract Template Software Component Template Specification of ECU Configuration Parameters (XML) Requirements on Diagnostic Extract Template Basic Software UML Model Methodology Requirements on Methodology Specification of Large Data COM Specification of RTE Software Specification of ECU Configuration Parameters (XML) System Template Basic Software UML Model Layered Software Architecture List of Basic Software Modules Requirements on AUTOSAR Features Requirements on Communication Requirements on Runtime Environment Requirements on System Template Software Component Template Specification of RTE Software Specification of ECU Configuration Parameters
- AUTOSAR confidential -

Classificatio n

Standard

Auxiliary

Standard

Auxiliary

Standard

Auxiliary

Standard

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 (XML) Specification of NVRAM Manager Basic Software UML Model Requirements on Memory Services Requirements on Runtime Environment Specification of Basic Software Mode Manager Specification of ECU Configuration Parameters (XML) Specification of ECU State Manager Specification of ECU State Manager with fixed state machine Basic Software UML Model 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 state machine Specification of Ethernet Interface Specification of TCP/IP Stack System Template Basic Software UML Model Layered Software Architecture List of Basic Software Modules 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 (XML) Specification of SW-C End-to-End Communication Protection Library System Template Requirements on E2E Communication Protection Basic Software UML Model Layered Software Architecture List of Basic Software Modules Methodology Requirements on AUTOSAR Features Requirements on Libraries Requirements on System Template

Auxiliary

Enhancement EcuM Fixed for Multi Core

Standard

Auxiliary

Standard

Ethernet Configuration and System Description for Manageable Switched Systems

Auxiliary

Standard

Extension of E2E Protection

Auxiliary

8 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 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 Specification of Ethernet Interface Global Time Specification of FlexRay Interface Synchronization Specification of Synchronized Time-Base Manager System Template Basic Software UML Model Layered Software Architecture List of Basic Software Modules Requirements on AUTOSAR Features Requirements on Ethernet Support in AUTOSAR Requirements on Synchronized Time-Base Manager Integration of Franca IDL Software Component Descriptions) Integration of NonSpecification of ECU Configuration Parameters AUTOSAR Systems (XML Methodology Software Component Template Specification of RTE Software Specification of ECU Configuration Specification of ECU Configuration Parameters (XML) Specification of Memory Mapping Mechanisms and 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 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 (XML) Templates Standardization Template
9 of 36

Standard

Auxiliary

Standard Auxiliary

Standard

Auxiliary

Standard

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Requirements on Safety Extensions Methodology Requirements on AUTOSAR Features Requirements on Methodology Specification of Predefined Names in AUTOSAR Specification of Secure Onboard Communication Specification of ECU Configuration Parameters (XML) 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 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 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 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 loadable and post- Specification of ECU Configuration Parameters build selectable ECU (XML) configuration General Requirements on Basic Software Modules
10 of 36

Auxiliary

Standard

Auxiliary

Standard

Auxiliary

Standard

Auxiliary

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Glossary Layered Software Architecture Methodology Requirements on AUTOSAR Features Requirements on ECU Configuration

11 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1

4

Document overview

The published documents are divided up into the following clusters: ? Main Documents, ? Basic Software Architecture and Runtime Environment, ? Methodology and Templates, ? Application Interfaces and ? Other Documents These clusters are then further structured by subcategories to provide a better orientation to the specification users. The assignment of the documents to those clusters is shown below. Document Long Name

Classification

File Name

Cluster: Main Documents Glossary aux AUTOSAR_TR_Glossary List of known Issues aux AUTOSAR_TR_ListOfKnownIssues Main Requirements aux AUTOSAR_RS_Main Project Objectives aux AUTOSAR_RS_ProjectObjectives Release Overview and Revision std AUTOSAR_TR_ReleaseOverviewAndRevHistory History Requirements on AUTOSAR aux AUTOSAR_RS_Features Features Specification of Predefined aux AUTOSAR_TR_PredefinedNames Names in AUTOSAR Cluster: Basic Software Architecture and Runtime Environment Backward Compatibility aux AUTOSAR_TR_BWCStatement Statement Basic Software UML Model aux AUTOSAR_MOD_BSWUMLModel Complex Driver design and AUTOSAR_EXP_CDDDesignAndIntegrationGuideli aux integration guideline ne Description of the AUTOSAR aux AUTOSAR_EXP_ErrorDescription standard errors Example for a Serialization aux AUTOSAR_TR_SomeIpExample Protocol (SOME/IP) Explanation of Error Handling on aux AUTOSAR_EXP_ApplicationLevelErrorHandling Application Level Explanation of Interrupt Handling aux AUTOSAR_EXP_InterruptHandlingExplanation within AUTOSAR General Requirements on Basic aux AUTOSAR_SRS_BSWGeneral Software Modules General Requirements on SPAL aux AUTOSAR_SRS_SPALGeneral General Specification of Basic AUTOSAR_SWS_BSWGeneral std Software Modules General Specification on std AUTOSAR_ASWS_TransformerGeneral Transformers Guide to BSW Distribution aux AUTOSAR_EXP_BSWDistributionGuide Guide to Mode Management aux AUTOSAR_EXP_ModeManagementGuide Layered Software Architecture aux AUTOSAR_EXP_LayeredSoftwareArchitecture List of Basic Software Modules aux AUTOSAR_TR_BSWModuleList Modeling Guidelines of Basic aux AUTOSAR_TR_BSWUMLModelModelingGuide Software EA UML Model Overview of Functional Safety aux AUTOSAR_EXP_FunctionalSafetyMeasures
12 of 36 Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Document Long Name
Measures in AUTOSAR Requirements on ADC Driver Requirements on BSW Modules for SAE J1939 Requirements on CAN Requirements on Communication Requirements on Core Test Requirements on Crypto Service Manager Requirements on Debugging in AUTOSAR Requirements on Diagnostic Requirements on Diagnostic Log and Trace Requirements on DIO Driver Requirements on E2E Communication Protection Requirements on EEPROM Driver Requirements on Ethernet Support in AUTOSAR Requirements on Flash Driver Requirements on Flash Test Requirements on FlexRay Requirements on Free Running Timer Requirements on Function Inhibition Manager Requirements on Gateway Requirements on GPT Driver Requirements on I/O Hardware Abstraction Requirements on ICU Driver Requirements on I-PDU Multiplexer Requirements on Libraries Requirements on LIN Requirements on MCU Driver Requirements on Memory Hardware Abstraction Layer Requirements on Memory Services Requirements on Mode Management Requirements on Module XCP Requirements on Network Management Requirements on OCU Driver Requirements on Operating System Requirements on Port Driver Requirements on PWM Driver Requirements on RAM Test
13 of 36

Classification
aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux aux

File Name

AUTOSAR_SRS_ADCDriver AUTOSAR_SRS_SAEJ1939 AUTOSAR_SRS_CAN AUTOSAR_SRS_COM AUTOSAR_SRS_CoreTest AUTOSAR_SRS_CryptoServiceManager AUTOSAR_SRS_Debugging AUTOSAR_SRS_Diagnostic AUTOSAR_SRS_DiagnosticLogAndTrace AUTOSAR_SRS_DIODriver AUTOSAR_SRS_E2E AUTOSAR_SRS_EEPROMDriver AUTOSAR_SRS_Ethernet AUTOSAR_SRS_FlashDriver AUTOSAR_SRS_FlashTest AUTOSAR_SRS_FlexRay AUTOSAR_SRS_FreeRunningTimer AUTOSAR_SRS_FunctionInhibitionManager AUTOSAR_SRS_Gateway AUTOSAR_SRS_GPTDriver AUTOSAR_SRS_IOHWAbstraction AUTOSAR_SRS_ICUDriver AUTOSAR_SRS_IPDUMultiplexer AUTOSAR_SRS_Libraries AUTOSAR_SRS_LIN AUTOSAR_SRS_MCUDriver AUTOSAR_SRS_MemoryHWAbstractionLayer AUTOSAR_SRS_MemoryServices AUTOSAR_SRS_ModeManagement AUTOSAR_SRS_XCP AUTOSAR_SRS_NetworkManagement AUTOSAR_SRS_OCUDriver AUTOSAR_SRS_OS AUTOSAR_SRS_PortDriver AUTOSAR_SRS_PWMDriver AUTOSAR_SRS_RAMTest
Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Document Long Name
Requirements on Runtime Environment Requirements on Secure Onboard Communication Requirements on SPI Handler/Driver Requirements on Synchronized Time-Base Manager Requirements on Time Service Requirements on Transformer Requirements on TTCAN Requirements on Watchdog Driver Specification of Large Data COM Specification of RTE Software Specification of a Diagnostic Communication Manager for SAE J1939 Specification of a Request Manager for SAE J1939 Specification of a Transport Layer for SAE J1939 Specification of ADC Driver Specification of Basic Software Mode Manager Specification of Bit Handling Routines Specification of CAN Driver Specification of CAN Interface Specification of CAN Network Management Specification of CAN State Manager Specification of CAN Transceiver Driver Specification of CAN Transport Layer Specification of COM Based Transformer Specification of Communication Specification of Communication Manager Specification of Communication Stack Types Specification of Compiler Abstraction Specification of Core Test Specification of CRC Routines Specification of Crypto Abstraction Library Specification of Crypto Service Manager Specification of Debugging in
14 of 36

Classification
aux aux aux aux aux aux aux aux std std std std std std std std std std std std std std std std std std std std std std std std

File Name
AUTOSAR_SRS_RTE AUTOSAR_SRS_SecureOnboardCommunication AUTOSAR_SRS_SPIHandlerDriver AUTOSAR_SRS_SynchronizedTimeBaseManager AUTOSAR_SRS_TimeService AUTOSAR_SRS_Transformer AUTOSAR_SRS_TTCAN AUTOSAR_SRS_WatchdogDriver AUTOSAR_SWS_LargeDataCOM AUTOSAR_SWS_RTE AUTOSAR_SWS_SAEJ1939DiagnosticCommunicat ionManager AUTOSAR_SWS_SAEJ1939RequestManager AUTOSAR_SWS_SAEJ1939TransportLayer AUTOSAR_SWS_ADCDriver AUTOSAR_SWS_BSWModeManager AUTOSAR_SWS_BFXLibrary AUTOSAR_SWS_CANDriver AUTOSAR_SWS_CANInterface AUTOSAR_SWS_CANNetworkManagement AUTOSAR_SWS_CANStateManager AUTOSAR_SWS_CANTransceiverDriver AUTOSAR_SWS_CANTransportLayer AUTOSAR_SWS_COMBasedTransformer AUTOSAR_SWS_COM AUTOSAR_SWS_COMManager AUTOSAR_SWS_CommunicationStackTypes AUTOSAR_SWS_CompilerAbstraction AUTOSAR_SWS_CoreTest AUTOSAR_SWS_CRCLibrary AUTOSAR_SWS_CryptoAbstractionLibrary AUTOSAR_SWS_CryptoServiceManager AUTOSAR_SWS_Debugging
Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Document Long Name
AUTOSAR Specification of Default Error Tracer Specification of Diagnostic Communication Manager Specification of Diagnostic Event Manager Specification of Diagnostic Log and Trace Specification of Diagnostic over IP Specification of DIO Driver Specification of ECU State Manager Specification of ECU State Manager with fixed state machine Specification of EEPROM Abstraction Specification of EEPROM Driver Specification of Ethernet Driver Specification of Ethernet Interface Specification of Ethernet State Manager Specification of Ethernet Transceiver Driver Specification of Extended Fixed Point Routines Specification of Fixed Point Interpolation Routines Specification of Fixed Point Math Routines Specification of Flash Driver Specification of Flash EEPROM Emulation Specification of Flash Test Specification of FlexRay AUTOSAR Transport Layer Specification of FlexRay Driver Specification of FlexRay Interface Specification of FlexRay ISO Transport Layer Specification of FlexRay Network Management Specification of FlexRay State Manager Specification of FlexRay Transceiver Driver Specification of Floating Point Interpolation Routines Specification of Floating Point Math Routines
15 of 36

Classification
std std std std std std std std std std std std std std std std std std std std std std std std std std std std std

File Name

AUTOSAR_SWS_DefaultErrorTracer AUTOSAR_SWS_DiagnosticCommunicationManag er AUTOSAR_SWS_DiagnosticEventManager AUTOSAR_SWS_DiagnosticLogAndTrace AUTOSAR_SWS_DiagnosticOverIP AUTOSAR_SWS_DIODriver AUTOSAR_SWS_ECUStateManager AUTOSAR_SWS_ECUStateManagerFixed AUTOSAR_SWS_EEPROMAbstraction AUTOSAR_SWS_EEPROMDriver AUTOSAR_SWS_EthernetDriver AUTOSAR_SWS_EthernetInterface AUTOSAR_SWS_EthernetStateManager AUTOSAR_SWS_EthernetTransceiverDriver AUTOSAR_SWS_EFXLibrary AUTOSAR_SWS_IFXLibrary AUTOSAR_SWS_MFXLibrary AUTOSAR_SWS_FlashDriver AUTOSAR_SWS_FlashEEPROMEmulation AUTOSAR_SWS_FlashTest AUTOSAR_SWS_FlexRayARTransportLayer AUTOSAR_SWS_FlexRayDriver AUTOSAR_SWS_FlexRayInterface AUTOSAR_SWS_FlexRayISOTransportLayer AUTOSAR_SWS_FlexRayNetworkManagement AUTOSAR_SWS_FlexRayStateManager AUTOSAR_SWS_FlexRayTransceiverDriver AUTOSAR_SWS_IFLLibrary AUTOSAR_SWS_MFLLibrary
Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Document Long Name
Specification of Function Inhibition Manager Specification of GPT Driver Specification of I/O Hardware Abstraction Specification of ICU Driver Specification of I-PDU Multiplexer Specification of LIN Driver Specification of LIN Interface Specification of LIN Network Management Specification of LIN State Manager Specification of LIN Transceiver Driver Specification of MCU Driver Specification of Memory Abstraction Interface Specification of Memory Mapping Specification of Module E2E Transformer Specification of Module XCP Specification of Network Management for SAE J1939 Specification of Network Management Interface Specification of NVRAM Manager Specification of OCU Driver Specification of Operating System Specification of PDU Router Specification of Platform Types Specification of Port Driver Specification of PWM Driver Specification of RAM Test Specification of Secure Onboard Communication Specification of Service Discovery Specification of Socket Adaptor Specification of SOME/IP Transformer Specification of SPI Handler/Driver Specification of Standard Types Specification of SW-C End-toEnd Communication Protection Library Specification of Synchronized Time-Base Manager Specification of TCP/IP Stack Specification of Time Service
16 of 36

Classification
std std aux std std std std std std std std std std std std std std std std std std std std std std std std std std std std std std std std

File Name
AUTOSAR_SWS_FunctionInhibitionManager AUTOSAR_SWS_GPTDriver AUTOSAR_SWS_IOHardwareAbstraction AUTOSAR_SWS_ICUDriver AUTOSAR_SWS_IPDUMultiplexer AUTOSAR_SWS_LINDriver AUTOSAR_SWS_LINInterface AUTOSAR_SWS_LINNetworkManagement AUTOSAR_SWS_LINStateManager AUTOSAR_SWS_LINTransceiverDriver AUTOSAR_SWS_MCUDriver AUTOSAR_SWS_MemoryAbstractionInterface AUTOSAR_SWS_MemoryMapping AUTOSAR_SWS_E2ETransformer AUTOSAR_SWS_XCP AUTOSAR_SWS_SAEJ1939NetworkManagement AUTOSAR_SWS_NetworkManagementInterface AUTOSAR_SWS_NVRAMManager AUTOSAR_SWS_OCUDriver AUTOSAR_SWS_OS AUTOSAR_SWS_PDURouter AUTOSAR_SWS_PlatformTypes AUTOSAR_SWS_PortDriver AUTOSAR_SWS_PWMDriver AUTOSAR_SWS_RAMTest AUTOSAR_SWS_SecureOnboardCommunication AUTOSAR_SWS_ServiceDiscovery AUTOSAR_SWS_SocketAdaptor AUTOSAR_SWS_SOMEIPTransformer AUTOSAR_SWS_SPIHandlerDriver AUTOSAR_SWS_StandardTypes AUTOSAR_SWS_E2ELibrary AUTOSAR_SWS_SynchronizedTimeBaseManager AUTOSAR_SWS_TcpIp AUTOSAR_SWS_TimeService
Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Document Long Name

Classification

File Name
AUTOSAR_SWS_TimeSyncOverCAN AUTOSAR_SWS_TimeSyncOverEthernet AUTOSAR_SWS_TimeSyncOverFlexRay AUTOSAR_SWS_TTCANDriver AUTOSAR_SWS_TTCANInterface AUTOSAR_SWS_UDPNetworkManagement AUTOSAR_SWS_WatchdogDriver AUTOSAR_SWS_WatchdogInterface AUTOSAR_SWS_WatchdogManager AUTOSAR_SWS_EthernetSwitchDriver AUTOSAR_TR_SafetyConceptStatusReport AUTOSAR_EXP_UtilizationOfCryptoServices AUTOSAR_EXP_VFB AUTOSAR_RS_FeatureModelExchangeFormat AUTOSAR_TPS_FeatureModelExchangeFormat AUTOSAR_MOD_MiscSupport AUTOSAR_TPS_BSWModuleDescriptionTemplate AUTOSAR_MOD_GeneralBlueprints AUTOSAR_TR_AutosarModelConstraints AUTOSAR_TPS_DiagnosticExtractTemplate AUTOSAR_RS_MethodologyAndTemplatesGeneral AUTOSAR_TPS_GenericStructureTemplate AUTOSAR_TR_FrancaIntegration AUTOSAR_MMOD_MetaModel AUTOSAR_MMOD_XMLSchema AUTOSAR_TR_Methodology AUTOSAR_TR_XMLPersistenceRules AUTOSAR_TR_TimingAnalysis

Specification of Time std Synchronization over CAN Specification of Time std Synchronization over Ethernet Specification of Time std Synchronization over FlexRay Specification of TTCAN Driver std Specification of TTCAN Interface std Specification of UDP Network std Management Specification of Watchdog Driver std Specification of Watchdog std Interface Specification of Watchdog std Manager Specification on Ethernet Switch std Driver Technical Safety Concept Status aux Report Utilization of Crypto Services aux Virtual Functional Bus aux Cluster: Methodology and Templates AUTOSAR Feature Model aux Exchange Format Requirements AUTOSAR Feature Model std Exchange Format AUTOSAR Miscellaneous aux Support Files Basic Software Module std Description Template Collection of blueprints for aux AUTOSAR M1 models Collection of constraints on std AUTOSAR M1 models Diagnostic Extract Template std General Requirements on aux Methodology and Templates Generic Structure Template std Integration of Franca IDL Software Component aux Descriptions Meta Model aux Meta Model-generated XML std Schema Methodology aux Model Persistence Rules for XML std Recommended Methods and Practices for Timing Analysis and aux Design within the AUTOSAR Development Process Requirements on Basic Software aux Module Description Template Requirements on Diagnostic aux Extract Template
17 of 36

AUTOSAR_RS_BSWModuleDescriptionTemplate AUTOSAR_RS_DiagnosticExtractTemplate
Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Document Long Name
Requirements on ECU Configuration Requirements on ECU Resource Template Requirements on Interaction with Behavioral Models Requirements on Interoperability of AUTOSAR Tools Requirements on Methodology Requirements on Safety Extensions Requirements on Software Component Template Requirements on Standardization Template Requirements on System Template Requirements on Timing Extensions Software Component Template Specification of ECU Configuration Specification of ECU Configuration Parameters (XML) Specification of ECU Resource Template Specification of Interaction with Behavioral Models Specification of Interoperability of AUTOSAR Tools Specification of Timing Extensions Specifications of Safety Extensions Standardization Template Standardized M1 Models used for the Definition of AUTOSAR Supplementary material of the AUTOSAR XML Schema System Template Cluster: Application Interfaces Application Design Patterns Catalogue Application Interface Examples Application Interfaces User Guide Explanation of Application Interfaces of Occupant and Pedestrian Safety Systems Domain Explanation of Application Interfaces of the Body and Comfort Domain Explanation of Application Interfaces of the Chassis Domain
18 of 36

Classification
aux aux aux aux aux aux aux aux aux aux std std std std aux aux std std std std aux std aux aux aux

File Name
AUTOSAR_RS_ECUConfiguration AUTOSAR_RS_ECUResourceTemplate AUTOSAR_RS_InteractionWithBehavioralModels AUTOSAR_RS_InteroperabilityOfAutosarTools AUTOSAR_RS_Methodology AUTOSAR_RS_SafetyExtensions AUTOSAR_RS_SoftwareComponentTemplate AUTOSAR_RS_StandardizationTemplate AUTOSAR_RS_SystemTemplate AUTOSAR_RS_TimingExtensions AUTOSAR_TPS_SoftwareComponentTemplate AUTOSAR_TPS_ECUConfiguration AUTOSAR_MOD_ECUConfigurationParameters AUTOSAR_TPS_ECUResourceTemplate AUTOSAR_TR_InteractionWithBehavioralModels AUTOSAR_TR_InteroperabilityOfAutosarTools AUTOSAR_TPS_TimingExtensions AUTOSAR_TPS_SafetyExtensions AUTOSAR_TPS_StandardizationTemplate AUTOSAR_MOD_GeneralDefinitions AUTOSAR_TR_XMLSchemaSupplement AUTOSAR_TPS_SystemTemplate AUTOSAR_TR_AIDesignPatternsCatalogue AUTOSAR_MOD_AISpecificationExamples AUTOSAR_EXP_AIUserGuide

aux

AUTOSAR_EXP_AIOccupantAndPedestrianSafety

aux aux

AUTOSAR_EXP_AIBodyAndComfort AUTOSAR_EXP_AIChassis
Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Document Long Name

Classification

File Name

Explanation of Application Interfaces of the HMI, Multimedia aux AUTOSAR_EXP_AIHMIMultimediaAndTelematics 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 aux AUTOSAR_TR_SWCModelingGuide Guide Unique Names for Documentation, Measurement AUTOSAR_TR_AIMeasurementCalibrationDiagnosti and Calibration: Modeling and aux cs Naming Aspects including Automatic Generation XML Specification of Application std AUTOSAR_MOD_AISpecification Interfaces Application Interface Examples aux AUTOSAR_MOD_AISpecificationExamples Cluster: Other Documents There are currently no documents in this cluster

19 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1

5 Remarks to known technical deficiencies
The technical deficiencies per document 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 document: ? none There is a major change of one document which shall be pointed out here: ? Bigger parts of the specification of the SynchronizedTimeBaseManager (Document ID 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 (Document ID 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).

20 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1

6 Revision history
Revision 1 of Release 4.2.has been released on the 31th of October 2014. The following deliverables had major changes. More documents might have been changed, which are not listed here. Those documents have then only “minor corrections, clarifications or editorial changes; For details please refer to the BWCStatement [3] Specification Name
Application Design Patterns Catalogue

State
added

Document history entry
First Release of document. Patterns covered: o Sensor and Actuator Pattern o Arbitration of Several Set-point Requester Pattern Previously published as part of EXP_AIPowertrain. Sensors and Actuators Pattern adopted in the AI Domain Obsolete AI Table substituted by new official AI Tool for content development phase and arxml generation Enhanced collections arxml deliverables structure Added [TPS_FMDT_00064] Extended splitables for BSW Added Uses-Case descrpitions for BSW modules Editorial changes Update for TcpIp Initial Release Added SD Peer Identification Extended Error Handling Minor corrections and clarifications Changing Status->state; current, actual -> consolidate after Harmonization with Engine Chapter “Sensor/Actuator Design Pattern” moved to new document “AIDesignPatternsCatalogue” Integrate new interfaces / update existing interfaces for network representation of engine & transmission interfaces Alignment of post-build configuration to SWS_BSWGeneral Rephrasing of definition of runtime errors Incorporation of concept SupportForPBLAndPBSECUConfiguration Editorial changes Support variant rich Special Data

Application Interfaces User added Guide -

AUTOSAR Feature Model Exchange Format Basic Software Module Description Template

added added

Complex Driver design added and integration guideline Diagnostic Extract added Template Example for a Serialization added Protocol (SOME/IP) Explanation of Application added Interfaces of the Chassis Domain Explanation of Application added Interfaces of the Powertrain Engine Domain

-

General Requirements on Basic Software Modules

added

-

General Requirements on Methodology and Templates General Specification of Basic Software Modules

added

added

-

-

Update in error handling classification Update in initialization function requirements Updated due to SupportForPBLAndPBSECUConfiguration concept minor corrections / clarifications / editorial changes; For details please refer to the BWCStatement

21 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Specification Name
General Specification on Transformers Generic Structure Template Glossary

State
added added added

Document history entry
Initial Release Propagation of LifeCycleState Editorial changes Following terms changed: Data Variant Coding (3.65) OS-Application (3.168) Post-build time configuration (3.179) Incorporation of concept “Mechanisms and constraints to protect ASIL BSW against QM BSW” Minor clarifications Incorporation of Concept "EcuMFixedMC" Clarified LIN Schedule Table Switching Initial Release

Guide to BSW Distribution

added

-

Guide to Mode Management Integration of Franca IDL Software Component Descriptions Layered Software Architecture

added added

-

added

-

List of Basic Software Modules

added

Main Requirements Methodology

added added

-

Model Persistence Rules added for XML Overview of Functional added Safety Measures in AUTOSAR Recommended Methods added and Practices for Timing Analysis and Design within the AUTOSAR Development Process

Incorporated new 4.2 concepts for: Switch Configuration; Sender-Receiver-Serialization; CAN-FD; Large-DataCOM; E2E-Extension; Global Time Synchronization; Support for Post-build ECU-Configuration; SecureOnboard-Communication; ASIL/QM-Protection Introduction of new error classification Editorial changes Added COMBased-Transformer Added E2E-Transformer Added SOME/IP-Transformer Added Ethernet Switch Driver Added Large Data COM Added Secure Onboard Communication Added Global Time Synch Modules New requirement for Secure Onboard Communication New requirement for naming schemes and conventions Support for Safety Extensions added Support for Diagnostic Extract added Support for Rapid Prototyping added Support for Sender Receiver Serialization added Formal adaptations concerning traceability Initial Release

-

Release Overview and Revision History

added

-

Editorial changes only: improvements, corrections and additions. New chapter End-to-End Timing Analysis for Distributed Functions; Chapter Properties and Methods for Timing 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; added

22 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Specification Name
Requirements on AUTOSAR Features

State
added

Document history entry
Incorporation of features for new R4.2 concepts Added chapter “Standardization and Documentation” Added features for LinTP and DoIP Minor corrections Layout update. Tracing update. Added requirements for CAN FD support Removed requirements for transmit cancellation added support for Large Data COM added support for Sender/ Receiver Serialization updated to support CAN FD Support of WWH-OBD (Major change) Support of UDS service $38 (“RequestFileTransfer”), (Change) Added new requirements for runtime errors and transient errors (Change) Aging of events (Change) Initial Release

Requirements on Basic Software Module Description Template Requirements on CAN Requirements on Communication Requirements on Diagnostic

added

added added

added

Requirements on Diagnostic Extract Template Requirements on E2E Communication Protection Requirements on ECU Configuration

added

added added

-

Initial release Updated [RS_ECUC_00008]. Added [RS_ECUC_00085]. Added [RS_ECUC_00086]. Tracing update Layout update. Introduction of IPv6 for in-vehicle communication Support for Global Time Synchronization over Ethernet Support for Switch Control/Configuration, Semi-Static Auto-Configuration TcpIp generic upper layer support (CDD) Support of multi-frame TP fanout added New RS feature linked to GPT Predef Timer requirements added requirement for naming conventions [RS_IOAT_00003] minor editorial changes added Multiple PDU to Container Mapping extension of IpduMSelectorFieldLength Removed the section "5.1.7 Added polynomial to CRC Library Changed [SRS_Lin_01564] Schedule Table change request buffering Requirements linked to BSW features

Requirements on ECU Resource Template Requirements on Ethernet Support in AUTOSAR

added added

Requirements on Gateway Requirements on GPT Driver Requirements on Interoperability of AUTOSAR Tools Requirements on I-PDU Multiplexer Requirements on Libraries Requirements on LIN Requirements on Memory Hardware Abstraction Layer Requirements on Memory Services Requirements on Methodology

added added added

added added added added

added added

-

Requirements linked to BSW features Support for Safety Extensions added Support for Diagnostic Extract added

23 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Specification Name
Requirements on Mode Management Requirements on Module XCP Requirements on Operating System Requirements on Runtime Environment

State
added

Document history entry
Moved former SWS EcuM item describing the handling of sleep modes / shutdown targets to SRS level Removed Defensive Behavior Removing the limitation "Flash Programming for ECU development purposes" Editorial changes Incorporation of concept “Mechanisms and constraints to protect ASIL BSW against QM BSW” Added support for concepts: – 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] Initial release based on Concept "‘Safety extensions"’ Initial Release Added requirements for configuration of data transformation. Added requirement for naming conventions extend traceability to new document artefacts Concept "Global Time Synchronization" incorporated to replace (and by that improve) original functionality and to support new 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. Added requirements [RS_SYST_00049], [RS_SYST_00050], [RS_SYST_00051], [RS_SYST_00052], [RS_SYST_00053], [RS_SYST_00054], [RS_SYST_00055], [RS_SYST_00056] New RS_BRF_ feature linked to all requirements Initial Release Efficient NV data handling 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 Initial Release

added

added added

-

Requirements on Safety added Extensions Requirements on Secure added Onboard Communication Requirements on Software added Component Template Requirements on Standardization Template Requirements on Synchronized Time-Base Manager added added

-

Requirements on System Template

added

-

Requirements on Time Service Requirements on Transformer Software Component Template

added added added

-

Specification of Large Data COM

added

-

24 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Specification Name
Specification of RTE Software

State
added

Document history entry
Efficient NV data handling Introduction of data transformation Support for variable-size Arrays of arbitrary data types Various fixes and clarifications Optimizations Editorial changes Improved interaction with COM Harmonized with SWS BSW General Removed obsolete configuration elements Harmonized with SWS BSW General AdcGroupId is changed to pre-compile time value in all variants. New API and configuration containers to support EcuM Fixed for 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) Correct usage of const in function declarations Editoral changes Full CAN FD Support (incl. Trigger Transmit) Removed CanIf_CancelTxConfirmation Time-out and wake up event handling Small improvements and minor bug-fixes Full CAN FD Support Global Time Synchronization over CAN Removed CanIf_CancelTxConfirmation Small improvements Removed obsolete configuration parameters Partial Network Handling Improvements Const usage in APIs reworked API for ECU passive mode activation Baudrate change without reinitialisation, if possible Interface handling to CanIf module improved Interface handling to ComM module improved Revised the configuration of CAN Tranceiver. Minor corrections in wait state functionality. Clarification regarding the wakeup sources. Introduced support for CAN Flexible Data rate Minor corrections Clarifications Initial Release added support for Sender/ Receiver Serialization updated to support CAN FD minor corrections

Specification of a Diagnostic Communication Manager for SAE J1939 Specification of a Request Manager for SAE J1939 Specification of a Transport Layer for SAE J1939 Specification of ADC Driver Specification of Basic Software Mode Manager

added

added added

added added

-

Specification of Bit Handling Routines Specification of CAN Driver

added added

Specification of CAN Interface

added

Specification of CAN Network Management

added

Specification of CAN State added Manager

Specification of CAN Transceiver Driver Specification of CAN Transport Layer Specification of COM Based Transformer Specification of Communication

added

added

added added

-

25 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Specification Name
Specification of Communication Manager

State
added

Document history entry
Release of PNC related FULL_COM request already upon leaving PNC_REQUESTED Several clarifications Minor corrections MetaData information is added in PduInfoType

Specification of Communication Stack Types Specification of Compiler Abstraction

added

added

-

Specification of Core Test added Specification of Diagnostic Communication Manager added -

Specification of CRC Routines Specification of Crypto Service Manager

added

added

Specification of Debugging added in AUTOSAR Specification of Default added Error Tracer

Specification of Diagnostic Event Manager

added

Specification of Diagnostic Log and Trace Specification of Diagnostic over IP

added added

-

The compiler symbol definitions are not allowed to contain any 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 CORTST_E_CORE_FAILURE extended production error formalization, including healing. Correction of CorTst_GetCurrentStatus prototype Introduction of a new CRC-32 with the polynomial 0xF4ACFB13 Editorial changes Obsolete configuration elements removed Error fixing and consistency improvements Editorial changes Removed Post Buid information Other small modifications Extended & renamed DevelopmentErrorTracer to DefaultErrorTracer by adding routines New Routines Det_ReportRountineError and Det_ReportTransientFault New configuration paramaters Det_ReportRountineErrorCallout and Det_ReportTransientFaultCallout Update to ISO 14229-1:2013 (Order of NRCs, SID 0x19 and 0x28 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. Support of ISO 27145 (WWH-OBD / Euro VI)[1] Update to support ISO 14229-1:2013[2] Introduction of event dependencies Refined DTC/Event suppression Changed requirements: SWS_Dlt_00515, SWS_Dlt_00516, SWS_Dlt_00332, SWS_Dlt_0028 Harmonization of identical APIs within BSW Handling UUDT messages within DoIP Harmonization of callback functions and configuration parameter names Editorial changes

26 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Specification Name
Specification of DIO Driver

State
added

Document history entry
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. Improved description of Post-build variants Improved Post-build loadable approach Introduction of Uri References Minor corrections / clarifications / editorial changes; For details please refer to the BWCStatement Layout update Added switch configuration Defined initialization order for InitListZero/InitListOne Definition of the name pattern of c-init-data struct corrected Type conflicts solved Editorial changes Incorporation of MultiCore concept Defined initialization order for InitListZero/InitListOne Definition of the name pattern of c-init-data struct corrected Editorial changes Requirements linked to BSW features, general and module specific requirements Added pass/fail criteria and additional attributes for extended production errors Removed redundant SWS IDs with respect to NULL_PTR check for Eep_Init() Change from Synchronous to Asynchronous API gPTP Timestamp Support Enhanced Production Errors Changed Access to Statistic Frame Handling Registers Change from Synchronous to Asynchronous API gPTP Timestamp Support Ethernet Switch Support Ethernet Wakeup Support Change from Synchronous to Asynchronous API Additional callback functions added Existing behavior of functions changes Editorial changes Change from Synchronous to Asynchronous API Ethernet Wakeup Support

Specification of ECU Configuration

added

-

Specification of ECU added Resource Template Specification of ECU State added Manager

-

Specification of ECU State added Manager with fixed state machine

Specification of EEPROM Abstraction Specification of EEPROM Driver

added added

Specification of Ethernet Driver

added

-

Specification of Ethernet Interface

added

Specification of Ethernet State Manager

added

Specification of Ethernet Transceiver Driver

added

27 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Specification Name
Specification of Extended Fixed Point Routines

State
added

Document history entry
Added: 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. Added: IFX RecordLayout Blueprint reference in section 3.1 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 Minor corrections and clarifications Requirements linked to features and BSW requirements. Requirement for blank checking added Requirements linked to features, general and module specific requirements 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 Clarification regarding NULL pointer handling Removed obsolete ECU configuration elements Removed obsolete configuration parameters Improved description of extended production errors Support for GlobalTimeSynchronization added Minor corrections

Specification of Fixed Point Interpolation Routines

added

-

Specification of Fixed Point Math Routines Specification of Flash Driver Specification of Flash EEPROM Emulation Specification of Flash Test

added added added

-

added

Specification of FlexRay AUTOSAR Transport Layer Specification of FlexRay Driver Specification of FlexRay Interface

added

-

added added

28 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Specification Name
Specification of FlexRay ISO Transport Layer

State
added

Document history entry
Added FRTP_TIME_CS in table 2, FRTP_TIMEOUT_BR and 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). Correction of Partial Networking aggregation algorithm Harmonize description of identical API’s Const usage consistent in specifications Changed development error checking of FrSM_Init pointer parameter. Editorial changes Reworked development and production errors according to the new SWS_BSWGeneral Supports multiple branch ids per transceiver Supports new busy wait time service Added: IFL RecordLayout Blueprint reference in section 3.1 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 Added: 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. Simplification of FiM configuration Support of "Monitored Components" Postbuild configuration clean up Editorial changes Init pointer check harmonized with BSW_General, redundant SWS_GPT_00294, SWS_GPT_00340 items removed Added new error code GPT_E_INIT_FAILED 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 added requirement for naming conventions [RS_IOAT_00003] minor editorial changes

Specification of FlexRay Network Management Specification of FlexRay State Manager Specification of FlexRay Transceiver Driver added -

added

added

Specification of Floating Point Interpolation Routines

added

Specification of Floating Point Math Routines added -

-

Specification of Function Inhibition Manager

added

Specification of GPT Driver

added

-

Specification of ICU Driver

added

-

-

Specification of Interoperability of AUTOSAR Tools

added

-

29 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Specification Name
Specification of I-PDU Multiplexer Specification of LIN Driver Specification of LIN Interface

State
added added added

Document history entry
Added Multiple PDU to Container Mapping Extension of IpduMSelectorFieldLength Replaced SWS_Lin_00064 with SWS_Lin_00268 Changed the description of return value E_NOT_OK for LinIf_Wakeup Changed the parameter LinIfFrameRef.upperMultiplicity from '*' to '1' Revised the typo in SWS_LinIf_00614 Editorial changes Added SWS_LinNm_00172 for LinNm_ConfigType, LINNM170 for 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. Removed NULL pointer check requirement ( moved to BSW General Corrections in ECU parameter configuration Supports Time service for transceiver state change waits Removed requirements for NULL pointer checking as redundant with BSW General. Specified pass/fail criteria for extended production errors Requirements linked to features, general and module specific requirements Support partitioning of BSW for safety systems Remove obsolete memory sections in Recommendation A Clarifications about the handling of SIZE and ALIGNMENT editorial changes Initial release Editorial corrections. Minor corrections. Changed the multiplicity of XcpEventChannelTriggeredDaqListRef. Remove limitation "Flash Programming for ECU development purposes". Enhanced description of extended production error J1939NM_E_ADDRESS_LOST Fixed usage of ‘const’ in NM APIs Harmonized with SWS BSW General Corrections on the requirement tracing Clarification at use of callback versus callout Editorial changes

Specification of LIN Network Management

added

-

Specification of LIN State Manager Specification of LIN Transceiver Driver Specification of MCU Driver Specification of Memory Abstraction Interface Specification of Memory Mapping

added

-

added added

added added

Specification of Module E2E Transformer Specification of Module XCP

added added

Specification of Network Management for SAE J1939 Specification of Network Management Interface

added

-

added

30 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Specification Name
Specification of NVRAM Manager

State
added

Document history entry
Detailed pass/fail conditions for production errors Added the NvM_ValidateAll functionality Updated return values for Init and SingleBlock callbacks Other small clarifications Set the postBuildVariantValue and postBuildVariantMultiplicity to 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. Add support for AsilQmProtection Minor updates/clarification of descriptions Editorial changes Support multi-frame TP fanout CAN-FD and SecOC Concept incorporation Improved Cancel Transmission handling in case of gatewaying Editorial changes removed SWS_Platform_00063 as the influence of Postbuild time configuration parameters on header files is already specified in SWS_BswGeneral Complete list of Module Abbreviation for each AUTOSAR document Include additional keywords Updated trace reference for code file structure requirement Added Pass/Fail Criterias for Extended Production Errors Initial Release Fixed Service Migration support at client side Support for more efficient SoAd interface Optimized StopSubscribe/Subscribe load Introduction of IPv6 for in-vehicle communication Support for Service Migration of Service Discovery Clients (SpecificRoutingGroup Handling) SoAd_RequestIpAddrAssignment API extension Clarifications and corrections of requirements and sequence charts Initial Release Added SWS_Spi_00383, SWS_Spi_00384, SWS_Spi_00385, SWS_Spi_00386 and ECUC_Spi_00243 New configuration parameter SpiUserCallbackHeaderFile SPI hardware error is applicable for sync and async transmits Editorial changes Introduction of E2E profiles 4, 5, 6 Introduction of E2E state machine Introduction of init functions and status mapping fucntions for profiles 1, 2 Overview of wrapper, by means of several new diagrams.

Specification of OCU Driver

added

Specification of Operating System Specification of PDU Router added -

added

Specification of Platform Types

added

-

Specification of Predefined added Names in AUTOSAR Specification of PWM Driver Specification of RAM Test Specification of Secure Onboard Communication Specification of Service Discovery Specification of Socket Adaptor added added added added

-

added

Specification of SOME/IP Transformer Specification of SPI Handler/Driver

added added

-

-

Specification of SW-C End-to-End Communication Protection Library

added

31 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Specification Name
Specification of Synchronized Time-Base Manager

State
added

Document history entry
Concept "Global Time Synchronization" incorporated to replace (and by that improve) original functionality and to support new 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. Introduction of IPv6 for in-vehicle communication Support for Switch Control/Configuration, Semi-Static Auto-Configuration TcpIp generic upper layer support (CDD) Clarifications and corrections of requirements and sequence charts Initial Release Initial Release

Specification of TCP/IP Stack

added

-

Specification of Time Synchronization over CAN Specification of Time Synchronization over Ethernet Specification of Time Synchronization over FlexRay Specification of Timing Extensions

added added

-

added

-

Initial Release

added

-

Specification of TTCAN Driver Specification of TTCAN Interface Specification of UDP Network Management

added added

added

Specification of Watchdog Driver Specification of Watchdog Manager Specification on Ethernet Switch Driver Specifications of Safety Extensions Standardization Template

added

-

added

added added added

Added the capability in Execution Order 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 Updated disclaimer Editorial changes Improved extended production error description Updated disclaimer Editorial changes Harmonization of API description Revised Partial Networking Requirements Extended Production Errors Editorial Changes Adapt specification of extended production errors. WDG_E_INIT_FAILED added (error code is referenced by SWS_BSWGeneral) Introduced of the modeling of system services Reformulated some requirements to constraints Minor corrections Initial Release Initial specification based on Concept "‘Safety Extensions"’ introduction of Blueprint Policy include safety extension relevant items extension of acceptanace test items

32 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Specification Name
SW-C and System Modeling Guide

State
added

Document history entry
Generic CompuMethods reuse mechanism enhanced through new modeling rules Extended naming rules and recommendations for Long Names standardization Extended description of blueprint mechanism applied to Application Interfaces Domain 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 P/L-List now also available as .arxml as part of MOD_AISpecification

System Template

added

-

Unique Names for Documentation, Measurement and Calibration: Modeling and Naming Aspects including Automatic Generation Virtual Functional Bus

added

-

added

-

Introduction of PRPortPrototype

33 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1

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 nonbackward-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 documents) of a given Release, 2) As depicted in every document, precisely identify a given document (with its unique name and three-digit version ID) as being part of the Release Item 1) addresses the fact that the set of documents 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 documents 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 document a unique identifier is provided upon which Revision a) a document was either 1 st time added to/removed from a Release or b) a document was modified as being part of one and the same Release, as long the latter is valid and therefore subject to Standard Maintenance.

34 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 Hence with item 2), the combination of Release and Revision Number in a document can be interpreted either as a) “document was (1st time) added to the Release x.y Rev n” or b) as “document was modified as part of Release x.y Rev m”, with m > n. Conversely, the Revision number will only change for documents subject to addition or modification of a valid Release (baseline). After their 1st time addition to the Release (baseline), it will not change for documents 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 document’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/22_Releases/42_Release4.2/01_Standard 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/22_Releases/42_Release4.2/02_Auxiliary Contents of auxiliary documents remain of auxiliary nature even if they are referenced from standard documents.

35 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -

Release 4.2 Overview and Revision History AUTOSAR Release 4.2.1 7.1.5 Release clusters Main documents “Main Documents” are general AUTOSAR documents facilita ting a global view on requirements, concepts and terms. Basic software architecture and runtime environment Documents belonging to this Release cluster provide descriptions, requirements and specifications of the AUTOSAR Software Architecture and the Runtime Environment. Methodology and templates Documents belonging to this Release cluster provide requirements, specifications, templates and guidelines on the AUTOSAR methodology and tool chain. Application interfaces Documents belonging to this Release cluster provide specifications of interfaces between applications and related explanatory material. Other documents This cluster contains documents which do not belong to any of the previous Release clusters.

36 of 36

Document ID 000: AUTOSAR_Release4.2_Overview_RevHistory

- AUTOSAR confidential -


赞助商链接
相关文章:
AUTOSAR技术分析报告
AUTOSAR技术分析报告_计算机软件及应用_IT/计算机_专业资料。AUTOSAR 技术分析报告(科银京成:王瑜、余鹏、曾英哲、鲁阳、杨宝泽) 1. AUTOSAR 简介 汽车电子领域的...
AUTOSAR技术概述
AUTOSAR技术概述_高等教育_教育专区。AUTOSAR 技术概述摘要: 对由应用软件组件(SW-Cs)、虚拟功能总线/运行时环境(VFB/RTE)和电控单元(ECU)基础软件(BSW)栈构成 ...
AutoSAR技术概述
AUTOSAR 技术概述前言 为了各个功能实现“模块性”、“可量测性”、“可移植性”和“复用性”,AUTOSAR 为车辆系统提供了 如右上图所示得基于不同层面的标准接口...
AUTOSAR解决方案
AUTOSAR解决方案_电子/电路_工程科技_专业资料。AUTOSAR 解决方案 为了降低 ECU 软件开发的复杂度,AUTOSAR 联盟提出了一套经过实践验证的软件 架构, 并以此作为开发...
AUTOSAR事件机制
AUTOSAR事件机制_计算机软件及应用_IT/计算机_专业资料。AUTOSAR 事件机制 作者:邓孔宏 1.1 事件 事件是由操作系统管理的对象。事件机制只提供给拓展的任务,它开始...
AUTOSAR资料From官网
The AUTOSAR standard will serve as a platform upon which future vehicle applications will be implemented and will also serve to minimize the current ...
什么是AUTOSAR
什么是 AUTOSAR 近年来, 汽车工业的飞速发展, 越来越多的车上的原有的机械控制装置正在被电子控制装置 所取代,例如用于控制发动机,自动变速箱、防抱死系统、电子...
AUTOSAR CAN诊断_图文
AUTOSAR CAN 诊断实现 2010-09-26 19:42:36 来源:与非网 关键字: AUTOSAR CAN 诊断 嵌入式软体 AUTOSAR 是由全球汽车 OEM 和供应商共同推出的一种汽车电子...
AUTOSAR(AUTomotive Open Systems Architecture)是由全...
AUTOSAR(AUTomotive Open Systems Architecture)是由全球汽车OEM和供应商共同推出的一种汽车电子嵌入式软_信息与通信_工程科技_专业资料。本文在深入研究AUTOSAR V3.1...
现代汽车电子技术结课论文
现代汽车电子技术课程论文 浅谈 AUTOSAR 及其应用发展 姓学班学 名: 院: 级: 号: 指导教师: 浅谈 autosar 及应用 前言: AUTOSAR(汽车开放系统架构) ,汽车开放...
更多相关标签: