Specification of Diagnostic Communication

Manager
AUTOSAR CP R24-11

Specification of Diagnostic
Document Title Communication Manager
Document Owner AUTOSAR
Document Responsibility AUTOSAR
Document Identification No 18

Document Status published

Part of AUTOSAR Standard Classic Platform
Part of Standard Release R24-11

Document Change History

Date Release Changed by Description
• DCM Context Data for IdsM event

• Improvement of various Requirements

AUTOSAR related to Authentification Service 0x29
2024-11-27 R24-11 Release • Remove protocol type and related APIs
Management
• Minor corrections / clarifications /
editorial changes; For details please
refer to the ChangeDocumentation
• Fixed StartOfReception

• Added Authentication TransmitCertificate

• Introduced Secure Variant Coding

AUTOSAR
Release • Reworked the structure of elements in
2023-11-23 R23-11
Management SecurityEvents to enable usage in
multiple platforms

• minor corrections / clarifications /

editorial changes; For details please
refer to the ChangeDocumentation
5

1 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
• Diagnostic Extract shall be completed to
describe multi-dimensional arrays and
arrays with complex data types

AUTOSAR • Update RoE to match latest ISO 14229-1

2022-11-24 R22-11 Release • Handling of
Management Dem_GetNumberOfFreezeFrameRecords

• minor corrections / clarifications /

editorial changes; For details please
refer to the ChangeDocumentation
• Incorporation of Concept 670 Classic
Platform Flexibility

• Separated SAE J2012_4 DTCs and

UDS DTCs
AUTOSAR
2021-11-25 R21-11 Release • OBD on UDS shall be supported
Management
• Removed the Mirror Memory following
ISO 14229-1:2020

• Support subfunctions 1A and 56 for UDS

services 0x19
• Incorporation of Concept 671 Intrusion
Detection System Manager

• Added
AUTOSAR DcmDspExternalSRDataElementClass
2020-11-30 R20-11 Release
Management • Updated the Error Classification chapter

• minor corrections / clarifications /

editorial changes; For details please
refer to the ChangeDocumentation
5

2 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
• Incorporation of Concept NVData
Handling Enhancements

• Incorporation of PeriodicDID Scheduler

Type2

AUTOSAR • Renaming of the SRS_Diagnostics to

2019-11-28 R19-11 Release RS_Diagnostics
Management
• minor corrections / clarifications /
editorial changes; For details please
refer to the ChangeDocumentation

• Changed Document Status from Final to

published
• Incorporation of Concept 636 Security
Extensions

• Rework of SenderReceiver interface

support for DIDs: Atomic
SenderReceiver interfaces added.

• Rework of SenderReceiver interface

AUTOSAR support for controlling DIDs via service
2018-10-31 4.4.0 Release InputOutputControlByIdentifier (0x2F)
Management
• Support added for input signals for the
RequestRoutineResults (0x03)
subfunction of the RoutineControl (0x31)
service

• minor corrections / clarifications /

editorial changes; For details please
refer to the ChangeDocumentation
• Cleanup SRS_Diagnostic requirement
traceability

• Fix Dcm/Dem interactions inconsistencies

AUTOSAR
2017-12-08 4.3.1 Release • Add constraints requirements for
Management parameter configuration

• minor corrections / clarifications /

editorial changes; For details please
refer to the ChangeDocumentation
5

3 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
• Redesign interfaces between Dem and
Dcm

• Rework Security Access management

AUTOSAR • Add management for parallel support for
2016-11-30 4.3.0 Release OBD and UDS protocols
Management
• Clarify usage of Diagnosis scaling

• minor corrections / clarifications /

editorial changes; For details please
refer to the BWCStatement
• Specify the NRCs to be sent by the Dcm
in case of Dem interfaces return
negative values.
AUTOSAR • Clarify Routine operation prototypes
2015-07-31 4.2.2 Release
Management • Debugging support marked as obsolete

• Minor corrections / clarifications /

editorial changes; For details please
refer to the Change Documentation
• Update to ISO 14229-1:2013 (Order of
NRCs, SID 0x19 and 0x28 extended
subfunctions, SID 0x38)

• Specify security mechanisms (security

AUTOSAR Lock time, static seed).
2014-10-31 4.2.1 Release
Management • Refine service
ReadDataByPeriodicIdentifier (0x2A)
and provide UUDT transfer.

• Reorganize the configuration parameters

for the routines.
• Added functional description for
DIDRange usage
AUTOSAR
Release • Added support for bootloader interaction
2014-03-31 4.1.3
Management • Revised the header file structure

• Editorial changes
5

4 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
• Created API tables for service interfaces

• Provided synchronous and

asynchronous APIs for DataServices
callouts
AUTOSAR
• Harmonization for the length parameter
2013-10-31 4.1.2 Release
interpretation all over RDBI, WDBI and
Management
RC services to be in bytes

• Editorial changes

• Removed chapter(s) on change

documentation
• Added Response on Event support

AUTOSAR • Rework configuration for S/R

2013-03-15 4.1.1
Administration communication

• Rework OBD Service $06 management

• Change interaction with BswM module
for mode management

• Change of callout configuration

AUTOSAR
2011-12-22 4.0.3 management for services and
Administration
sub-services processing

• Synchronous and asynchronous

clarification
• ComM_DCM_InactiveDiagnostic and
ComM_DCM_ActiveDiagnostic has
been defined as mandatory interfaces.

• DcmDslPeriodicTxConfirmationPduId
multiplicity changed and creation of
DcmDslPeriodicConnection parameter in
order to link the confirmation Id with
AUTOSAR TxPdu Id for PeriodicTransmission.
2009-12-18 4.0.1
Administration
• Dem_GetDTCOfOBDFreezeFrame,
Dlt_ConditionCheckRead added as
optional interfaces

• DspInternal_<DiagnosticService> Api
moved to mandatory internal interface to
support the ECU Supplier diagnosis.

• Rework of ReadData operation

5

5 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
• Add support of following UDS services :
ReadMemoryByAdress,
WriteMemoryByAdress,
RequestDownload, RequestUpload,
TransferData, RequestTransferExit,
CommunicationControl,
ResponseOnEvent.

• Add of bootloader interaction

AUTOSAR
2009-12-04 3.1.4
Administration • Add of BswM interaction

• Add of IoHwAb interaction

• Add of DLT interaction

• Add of Signal based approach on RTE

interfaces

• Legal nvocation revised

• Introduction of OBD support

• generation of artefacts from the models

according to the AUTOSAR process

AUTOSAR • Identification of requirements and

2008-08-13 3.1.1
Administration correct formulation of specification items
as requirements

• General cleanup

• Legal nvocation revised

• Rework of the interfaces with RTE
(remove of Central Diagnostic SWC
concept)
AUTOSAR
2007-12-21 3.0.1 • Correction of issues identified on R2.1
Administration
• Document meta information extended

• Small layout adaptations made

AUTOSAR • "Advice for users" revised
2007-01-24 2.1.15
Administration • "Revision Information" added
5

6 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
• Corrections in configuration chapter

• Rework on interface between DCM and

DEM according to changes in DEM SWS
AUTOSAR
2.1.14
Administration • Corrections in Sequence diagram

• Addition of header files inclusions

• Legal disclaimer revised

AUTOSAR
2006-11-28 2.1 • Layout Adaptations
Administration
• Document structure adapted to common
Release 2.0 SWS Template

AUTOSAR • Major changes in chapter 10

2006-05-16 2.0
Administration

• Structure of document changed partly

• Other changes see chapter 11

AUTOSAR
2005-05-31 1.0 • Initial release
Administration

7 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Disclaimer

This work (specification and/or software implementation) and the material contained in
it, as released by AUTOSAR, is for the purpose of information only. AUTOSAR and the
companies that have contributed to it shall not be liable for any use of the work.
The material contained in this work is protected by copyright and other types of intel-
lectual property rights. The commercial exploitation of the material contained in this
work requires a license to such intellectual property rights.
This work may be utilized or reproduced without any modification, in any form or by
any means, for informational purposes only. For any other purpose, no part of the work
may be utilized or reproduced, in any form or by any means, without permission in
writing from the publisher.
The work has been developed for automotive applications only. It has neither been
developed, nor tested for non-automotive applications.
The word AUTOSAR and the AUTOSAR logo are registered trademarks.

8 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Contents
1 Introduction and functional overview 24

2 Acronyms and Abbreviations 27

2.1 Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 29
3 Related documentation 30
3.1 Input documents & related standards and norms . . . . . . . . . . . . 30
3.2 Related specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4 Constraints and assumptions 32
4.1 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.2 Applicability to car domains . . . . . . . . . . . . . . . . . . . . . . . . 34
4.3 Applicability to emission-related environments (OBD) . . . . . . . . . . 34
5 Dependencies to other modules 35

6 Requirements Tracing 37

7 Functional specification 42
7.1 General design elements . . . . . . . . . . . . . . . . . . . . . . . . . . 42
7.1.1 Submodules within the Dcm module . . . . . . . . . . . . . . 42
7.1.2 Negative Response Code (NRC) . . . . . . . . . . . . . . . . 43
7.1.3 Non-volatile information . . . . . . . . . . . . . . . . . . . . . 44
7.1.4 Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
7.1.4.1 Atomic types overview . . . . . . . . . . . . . . . . . 44
7.1.4.2 Data array types overview . . . . . . . . . . . . . . . 45
7.1.4.3 Nested Data types overview . . . . . . . . . . . . . . 45
7.1.4.4 Data types constraints . . . . . . . . . . . . . . . . . 50
7.1.4.5 Dcm_OpStatusType . . . . . . . . . . . . . . . . . . 51
7.1.4.6 Dcm_Cemr_{DID}Type . . . . . . . . . . . . . . . . . 52
7.2 Diagnostic Session Layer (DSL) . . . . . . . . . . . . . . . . . . . . . . 52
7.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.2.2 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
7.2.3 Interaction with other modules . . . . . . . . . . . . . . . . . 53
7.2.4 Functional description . . . . . . . . . . . . . . . . . . . . . . 53
7.2.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . 53
7.2.4.2 Forward requests from the PduR module to the DSD
submodule . . . . . . . . . . . . . . . . . . . . . . . 54
7.2.4.2.1 Dcm_StartOfReception . . . . . . . . . . . . . 55
7.2.4.2.2 Dcm_CopyRxData . . . . . . . . . . . . . . . . 57
7.2.4.2.3 Dcm_TpRxIndication . . . . . . . . . . . . . . 58
7.2.4.3 Concurrent TesterPresent (”keep alive logic”) 58
7.2.4.3.1 Dcm_CopyTxData . . . . . . . . . . . . . . . . 58
7.2.4.3.2 Dcm_TpTxConfirmation . . . . . . . . . . . . . 59

9 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.2.4.4 Forward responses from the DSD submodule to the

PduR module . . . . . . . . . . . . . . . . . . . . . . 59
7.2.4.5 Generic Connection Handling . . . . . . . . . . . . . 61
7.2.4.6 Guarantee timing to tester by sending busy responses 62
7.2.4.7 Support of periodic transmission . . . . . . . . . . . 63
7.2.4.8 Support of segmented response (paged-buffer) . . . 63
7.2.4.9 Support of ResponsePending response triggered by
the Application . . . . . . . . . . . . . . . . . . . . . 64
7.2.4.10 Manage security level . . . . . . . . . . . . . . . . . 64
7.2.4.10.1 Initialization sequence . . . . . . . . . . . . . . 65
7.2.4.10.2 AttemptCounter update . . . . . . . . . . . . . 67
7.2.4.11 Manage session state . . . . . . . . . . . . . . . . . 67
7.2.4.12 Manage authentication state . . . . . . . . . . . . . . 68
7.2.4.13 Non-default sessions . . . . . . . . . . . . . . . . . . 71
7.2.4.14 Allow to modify timings . . . . . . . . . . . . . . . . . 72
7.2.4.14.1 Different service tables . . . . . . . . . . . . . 72
7.2.4.14.2 Prioritization of protocol . . . . . . . . . . . . . 73
7.2.4.14.3 Preemption of protocol . . . . . . . . . . . . . 73
7.2.4.14.4 Parallel diagnostic protocol processing . . . . 75
7.2.4.15 Manage resources . . . . . . . . . . . . . . . . . . . 78
7.2.4.16 Communication Mode Handling . . . . . . . . . . . . 78
7.2.4.16.1 No Communication . . . . . . . . . . . . . . . 79
7.2.4.16.2 Silent Communication . . . . . . . . . . . . . . 79
7.2.4.16.3 Full Communication . . . . . . . . . . . . . . . 80
7.2.4.16.4 Diagnostic Activation State . . . . . . . . . . . 81
7.3 Diagnostic Service Dispatcher (DSD) . . . . . . . . . . . . . . . . . . . 82
7.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7.3.2 Use cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7.3.2.1 Receive a request message and transmit a positive
response message . . . . . . . . . . . . . . . . . . . 83
7.3.2.2 Receive a request message and suppress a positive
response . . . . . . . . . . . . . . . . . . . . . . . . 83
7.3.2.3 Receive a request message and suppress a negative
response . . . . . . . . . . . . . . . . . . . . . . . . 83
7.3.2.4 Receive a request message and transmit a negative
response message . . . . . . . . . . . . . . . . . . . 84
7.3.2.5 Send a positive response message without corre-
sponding request . . . . . . . . . . . . . . . . . . . . 84
7.3.2.6 Segmented Responses (paged-buffer) . . . . . . . . 85
7.3.3 Interaction of the DSD with other modules . . . . . . . . . . . 85
7.3.3.1 Interaction of the DSD with the DSL main functionality 85
7.3.3.2 Interaction of the DSD with the DSP . . . . . . . . . . 86
7.3.4 Functional Description of the DSD . . . . . . . . . . . . . . . 86
7.3.4.1 Support checking the diagnostic service identifier
and adapting the diagnostic message . . . . . . . . 86
7.3.4.2 Handling of "suppressPosRspMsgIndicationBit" . . . 88

10 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.3.4.3 Verification functionality . . . . . . . . . . . . . . . . 89

7.3.4.3.1 Verification of the diagnostic service access
rights . . . . . . . . . . . . . . . . . . . . . . . 89
7.3.4.3.2 Verification of the Diagnostic Session . . . . . 92
7.3.4.3.3 Verification of the Service Security Access levels 93
7.3.4.3.4 Verification of the Service mode dependencies 93
7.3.4.4 Check format and subfunction support . . . . . . . . 94
7.3.4.4.1 Verification of the Manufacturer Application en-
vironment/permission . . . . . . . . . . . . . . 94
7.3.4.4.2 Verification of the Supplier Application environ-
ment/permission . . . . . . . . . . . . . . . . . 95
7.3.4.5 Distribution of diagnostic message to DSP submodule 96
7.3.4.6 Assemble positive or negative response . . . . . . . 96
7.3.4.6.1 Positive Response . . . . . . . . . . . . . . . . 96
7.3.4.6.2 Negative Response . . . . . . . . . . . . . . . 97
7.3.4.6.3 Suppression of response . . . . . . . . . . . . 97
7.3.4.7 Initiate transmission . . . . . . . . . . . . . . . . . . 97
7.4 Diagnostic Service Processing (DSP) . . . . . . . . . . . . . . . . . . . 99
7.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.4.1.1 Check format and subfunction support . . . . . . . . 99
7.4.1.2 Assemble response . . . . . . . . . . . . . . . . . . 100
7.4.1.3 Negative Response Codes handling . . . . . . . . . 100
7.4.1.4 Diagnostic mode declaration groups . . . . . . . . . 100
7.4.1.5 Environmental condition dependent execution . . . . 102
7.4.1.6 Sender/Receiver Communication . . . . . . . . . . . 106
7.4.1.7 Passing SwDataDefProps properties from DEXT file
to the Dcm Service SW-C . . . . . . . . . . . . . . . . 106
7.4.1.7.1 DcmDspDiagnosticDataElementRef
workflow . . . . . . . . . . . . . . . . . . . . . 107
7.4.1.7.2 DcmDspAlternativeDataType.DcmAp-
plicationDataType workflow . . . . . . . . 108
7.4.1.8 Asynchronous call behavior . . . . . . . . . . . . . . 108
7.4.2 UDS Services . . . . . . . . . . . . . . . . . . . . . . . . . . 109
7.4.2.1 General behavior using DEM interfaces . . . . . . . 110
7.4.2.2 Service 0x10 - Diagnostic Session Control . . . . . . 111
7.4.2.3 Service 0x11 - ECUReset . . . . . . . . . . . . . . . 112
7.4.2.4 Service 0x14 - Clear Diagnostic Information . . . . . 113
7.4.2.5 Service 0x19 - Read DTC Information . . . . . . . . . 115
7.4.2.5.1 Subfunctions 0x01, 0x07 and 0x12 . . . . . . 116
7.4.2.5.2 Subfunctions 0x02, 0x0A, 0x13, 0x15 and 0x17 117
7.4.2.5.3 Subfunction 0x08 . . . . . . . . . . . . . . . . 120
7.4.2.5.4 Subfunction 0x09 . . . . . . . . . . . . . . . . 121
7.4.2.5.5 Subfunctions 0x06/0x19 . . . . . . . . . . . . . 123
7.4.2.5.6 Subfunction 0x03 . . . . . . . . . . . . . . . . 125
7.4.2.5.7 Subfunctions 0x04 and 0x18 . . . . . . . . . . 125
7.4.2.5.8 Subfunction 0x05 . . . . . . . . . . . . . . . . 127

11 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.2.5.9 Subfunctions 0x0B, 0x0C, 0x0D and 0x0E . . 128

7.4.2.5.10 Subfunction 0x14 . . . . . . . . . . . . . . . . 129
7.4.2.5.11 Subfunction 0x1A . . . . . . . . . . . . . . . . 131
7.4.2.5.12 Subfunction 0x42 . . . . . . . . . . . . . . . . 132
7.4.2.5.13 Subfunction 0x55 . . . . . . . . . . . . . . . . 133
7.4.2.5.14 Subfunction 0x56 . . . . . . . . . . . . . . . . 134
7.4.2.6 Service 0x22 - ReadDataByIdentifier . . . . . . . . . 135
7.4.2.6.1 UDS DID . . . . . . . . . . . . . . . . . . . . . 139
7.4.2.6.2 OBD DID . . . . . . . . . . . . . . . . . . . . . 140
7.4.2.7 Service 0x24 - ReadScalingDataByIdentifier . . . . . 142
7.4.2.8 Service 0x27 - SecurityAccess . . . . . . . . . . . . 143
7.4.2.9 Service 0x28 - CommunicationControl . . . . . . . . 146
7.4.2.10 Service 0x29 - Authentication . . . . . . . . . . . . . 149
7.4.2.10.1 De-authentication . . . . . . . . . . . . . . . . 151
7.4.2.10.2 Verify Certificates . . . . . . . . . . . . . . . . 152
7.4.2.10.3 Proof of ownership client . . . . . . . . . . . . 158
7.4.2.10.4 Definition and verification of roles . . . . . . . 160
7.4.2.10.5 Definition and verification of white lists . . . . . 162
7.4.2.10.6 AuthenticationConfiguration . . . . . . . . . . 166
7.4.2.10.7 TransmitCertificate . . . . . . . . . . . . . . . . 166
7.4.2.11 Service 0x2A - ReadDataByPeriodicIdentifier . . . . 167
7.4.2.11.1 Scheduler PeriodicTransmission . . . . . . . . 170
7.4.2.12 Service 0x2C - DynamicallyDefineDataIdentifier . . . 179
7.4.2.13 Service 0x2E - WriteDataByIdentifier . . . . . . . . . 181
7.4.2.14 Service 0x2F - InputOutputControlByIdentifier . . . . 185
7.4.2.15 Service 0x31 - RoutineControl . . . . . . . . . . . . . 198
7.4.2.15.1 Handling of OBD RID . . . . . . . . . . . . . . 206
7.4.2.16 Service 0x3E - Tester Present . . . . . . . . . . . . . 207
7.4.2.17 Service 0x3D - WriteMemoryByAddress . . . . . . . 208
7.4.2.18 Service 0x23 - ReadMemoryByAddress . . . . . . . 209
7.4.2.19 Service 0x34 - RequestDownload . . . . . . . . . . . 211
7.4.2.20 Service 0x35 - RequestUpload . . . . . . . . . . . . 213
7.4.2.21 Service 0x36 - TransferData . . . . . . . . . . . . . . 214
7.4.2.22 Service 0x37 - RequestTransferExit . . . . . . . . . . 216
7.4.2.23 Service 0x38 - RequestFileTransfer . . . . . . . . . . 218
7.4.2.24 Service 0x85 - ControlDTCSetting . . . . . . . . . . 220
7.4.2.25 Service 0x86 - ResponseOnEvent (RoE) . . . . . . . 222
7.4.2.26 Service 0x87 - LinkControl . . . . . . . . . . . . . . . 224
7.4.3 OBD Services . . . . . . . . . . . . . . . . . . . . . . . . . . 224
7.4.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . 224
7.4.3.2 General behavior . . . . . . . . . . . . . . . . . . . . 225
7.4.3.3 Service $01 - Request Current Powertrain Diagnos-
tic Data . . . . . . . . . . . . . . . . . . . . . . . . . 226
7.4.3.4 Service $02 - Request Power Train FreezeFrame Data 229
7.4.3.4.1 Service $02 - PID$02 . . . . . . . . . . . . . . 229
7.4.3.4.2 Service $02 - availability PID . . . . . . . . . . 230

12 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.3.4.3 Service $02 - other PIDs . . . . . . . . . . . . 230

7.4.3.5 Service $03 $07 $0A - Obtaining DTCs . . . . . . . 231
7.4.3.6 Service $04 - Clear/reset emission-related diagnos-
tic information . . . . . . . . . . . . . . . . . . . . . . 233
7.4.3.7 Service $06 - Request On-Board Monitoring Test-
results for Specific Monitored Systems . . . . . . . . 234
7.4.3.7.1 General requirements . . . . . . . . . . . . . . 234
7.4.3.7.2 Test results obtained via Dem interaction . . . 234
7.4.3.8 Service $08 - Request Control of On-Board System,
Test or Component . . . . . . . . . . . . . . . . . . . 235
7.4.3.9 Service $09 - Request Vehicle Information . . . . . . 236
7.4.4 Interaction usecases . . . . . . . . . . . . . . . . . . . . . . . 238
7.4.4.1 Jump to Bootloader . . . . . . . . . . . . . . . . . . . 238
7.4.4.2 Jump due to ECUReset . . . . . . . . . . . . . . . . 241
7.4.4.3 Jump from Bootloader / ECUReset . . . . . . . . . . 242
7.4.4.4 Flags management . . . . . . . . . . . . . . . . . . . 243
7.4.4.4.1 Jump to Bootloader . . . . . . . . . . . . . . . 243
7.4.4.4.2 Jump from Bootloader . . . . . . . . . . . . . . 243
7.5 Error notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
7.6 Synchronous and Asynchronous implementation . . . . . . . . . . . . 244
7.7 DID configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
7.7.1 Individual DID . . . . . . . . . . . . . . . . . . . . . . . . . . 245
7.7.2 DID ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
7.8 Secure Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
7.9 Startup behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
7.10 Error Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
7.10.1 Development Errors . . . . . . . . . . . . . . . . . . . . . . . 254
7.10.2 Runtime Errors . . . . . . . . . . . . . . . . . . . . . . . . . . 254
7.10.3 Production Errors . . . . . . . . . . . . . . . . . . . . . . . . 255
7.10.4 Extended Production Errors . . . . . . . . . . . . . . . . . . . 255
7.11 Security Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
8 API specification 273
8.1 Imported types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
8.2 Type definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
8.2.1 Dcm_StatusType . . . . . . . . . . . . . . . . . . . . . . . . . 274
8.2.2 Dcm_CommunicationModeType . . . . . . . . . . . . . . . . 274
8.2.3 Dcm_ConfigType . . . . . . . . . . . . . . . . . . . . . . . . . 275
8.2.4 Dcm_ReturnReadMemoryType . . . . . . . . . . . . . . . . . 276
8.2.5 Dcm_ReturnWriteMemoryType . . . . . . . . . . . . . . . . . 276
8.2.6 Dcm_EcuStartModeType . . . . . . . . . . . . . . . . . . . . 277
8.2.7 Dcm_ProgConditionsType . . . . . . . . . . . . . . . . . . . 277
8.2.8 Dcm_MsgItemType . . . . . . . . . . . . . . . . . . . . . . . 278
8.2.9 Dcm_MsgType . . . . . . . . . . . . . . . . . . . . . . . . . . 278
8.2.10 Dcm_MsgLenType . . . . . . . . . . . . . . . . . . . . . . . . 279
8.2.11 Dcm_MsgAddInfoType . . . . . . . . . . . . . . . . . . . . . 279

13 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.2.12 Dcm_IdContextType . . . . . . . . . . . . . . . . . . . . . . . 280

8.2.13 Dcm_MsgContextType . . . . . . . . . . . . . . . . . . . . . 280
8.2.14 Dcm_ExtendedOpStatusType . . . . . . . . . . . . . . . . . 281
8.3 Function definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
8.3.1 Functions provided for other BSW components . . . . . . . . 282
8.3.1.1 Dcm_Init . . . . . . . . . . . . . . . . . . . . . . . . . 282
8.3.1.2 Dcm_GetVersionInfo . . . . . . . . . . . . . . . . . . 283
8.3.1.3 Dcm_DemTriggerOnDTCStatus . . . . . . . . . . . . 283
8.3.1.4 Dcm_GetVin . . . . . . . . . . . . . . . . . . . . . . 284
8.3.1.5 Dcm_BndMWriteBlockFinish . . . . . . . . . . . . . 284
8.3.2 Functions provided to BSW modules and to SW-Cs . . . . . 285
8.3.2.1 Dcm_SetDeauthenticatedRole . . . . . . . . . . . . 285
8.3.2.2 Dcm_GetSecurityLevel . . . . . . . . . . . . . . . . . 286
8.3.2.3 Dcm_GetSesCtrlType . . . . . . . . . . . . . . . . . 286
8.3.2.4 Dcm_ResetToDefaultSession . . . . . . . . . . . . . 287
8.3.2.5 Dcm_ SetActiveDiagnostic . . . . . . . . . . . . . . . 287
8.4 Callback notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
8.4.1 Dcm_StartOfReception . . . . . . . . . . . . . . . . . . . . . 289
8.4.2 Dcm_CopyRxData . . . . . . . . . . . . . . . . . . . . . . . . 290
8.4.3 Dcm_TpRxIndication . . . . . . . . . . . . . . . . . . . . . . 290
8.4.4 Dcm_CopyTxData . . . . . . . . . . . . . . . . . . . . . . . . 291
8.4.5 Dcm_TpTxConfirmation . . . . . . . . . . . . . . . . . . . . . 292
8.4.6 Dcm_TxConfirmation . . . . . . . . . . . . . . . . . . . . . . 293
8.4.7 Dcm_ComM_NoComModeEntered . . . . . . . . . . . . . . 293
8.4.8 Dcm_ComM_SilentComModeEntered . . . . . . . . . . . . . 294
8.4.9 Dcm_ComM_FullComModeEntered . . . . . . . . . . . . . . 294
8.4.10 Dcm_CsmAsyncJobFinished . . . . . . . . . . . . . . . . . . 295
8.4.11 Dcm_KeyMAsyncCertificateVerifyFinished . . . . . . . . . . 295
8.5 Callout Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
8.5.1 Dcm_ReadMemory . . . . . . . . . . . . . . . . . . . . . . . 296
8.5.2 Dcm_WriteMemory . . . . . . . . . . . . . . . . . . . . . . . 297
8.5.3 Dcm_SetProgConditions . . . . . . . . . . . . . . . . . . . . 298
8.5.4 Dcm_GetProgConditions . . . . . . . . . . . . . . . . . . . . 299
8.5.5 Dcm_ProcessRequestAddFile . . . . . . . . . . . . . . . . . 300
8.5.6 Dcm_ProcessRequestDeleteFile . . . . . . . . . . . . . . . . 301
8.5.7 Dcm_ProcessRequestReplaceFile . . . . . . . . . . . . . . . 302
8.5.8 Dcm_ProcessRequestReadFile . . . . . . . . . . . . . . . . 303
8.5.9 Dcm_ProcessRequestReadDir . . . . . . . . . . . . . . . . . 304
8.5.10 Dcm_WriteFile . . . . . . . . . . . . . . . . . . . . . . . . . . 305
8.5.11 Dcm_ReadFileOrDir . . . . . . . . . . . . . . . . . . . . . . . 305
8.5.12 UploadDownloadServices . . . . . . . . . . . . . . . . . . . . 306
8.5.12.1 ProcessRequestDownload . . . . . . . . . . . . . . . 306
8.5.12.2 ProcessRequestTransferExit . . . . . . . . . . . . . 307
8.5.12.3 ProcessRequestUpload . . . . . . . . . . . . . . . . 308
8.5.12.4 ProcessTransferDataRead . . . . . . . . . . . . . . . 309
8.5.12.5 ProcessTransferDataWrite . . . . . . . . . . . . . . . 310

14 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.6 Scheduled functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

8.6.1 Dcm_MainFunction . . . . . . . . . . . . . . . . . . . . . . . 311
8.7 Expected interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
8.7.1 Mandatory interfaces . . . . . . . . . . . . . . . . . . . . . . 312
8.7.2 Optional interfaces . . . . . . . . . . . . . . . . . . . . . . . . 312
8.7.3 Configurable interfaces . . . . . . . . . . . . . . . . . . . . . 316
8.7.3.1 SecurityAccess . . . . . . . . . . . . . . . . . . . . . 316
8.7.3.1.1 GetSeed . . . . . . . . . . . . . . . . . . . . . 316
8.7.3.1.2 CompareKey . . . . . . . . . . . . . . . . . . . 317
8.7.3.1.3 GetSecurityAttemptCounter . . . . . . . . . . 318
8.7.3.1.4 SetSecurityAttemptCounter . . . . . . . . . . . 319
8.7.3.2 DataServices . . . . . . . . . . . . . . . . . . . . . . 319
8.7.3.2.1 ReadData . . . . . . . . . . . . . . . . . . . . 319
8.7.3.2.2 WriteData . . . . . . . . . . . . . . . . . . . . 322
8.7.3.2.3 ReadDataLength . . . . . . . . . . . . . . . . . 326
8.7.3.2.4 ConditionCheckRead . . . . . . . . . . . . . . 329
8.7.3.2.5 GetScalingInformation . . . . . . . . . . . . . 330
8.7.3.2.6 ReturnControlToECU . . . . . . . . . . . . . . 333
8.7.3.2.7 ResetToDefault . . . . . . . . . . . . . . . . . 334
8.7.3.2.7.1 Synchronous interface . . . . . . . . . . 334
8.7.3.2.7.2 Asynchronous interface . . . . . . . . . 336
8.7.3.2.8 FreezeCurrentState . . . . . . . . . . . . . . . 338
8.7.3.2.8.1 Synchronous interface . . . . . . . . . . 338
8.7.3.2.8.2 Asynchronous interface . . . . . . . . . 340
8.7.3.2.9 ShortTermAdjustment . . . . . . . . . . . . . . 342
8.7.3.2.9.1 Synchronous interface . . . . . . . . . . 342
8.7.3.2.9.2 Asynchronous interface . . . . . . . . . 344
8.7.3.3 DataServices_DIDRange . . . . . . . . . . . . . . . 346
8.7.3.3.1 IsDidAvailable . . . . . . . . . . . . . . . . . . 347
8.7.3.3.2 ReadDidData . . . . . . . . . . . . . . . . . . . 348
8.7.3.3.3 WriteDidData . . . . . . . . . . . . . . . . . . . 348
8.7.3.3.4 ReadDidRangeDataLength . . . . . . . . . . . 349
8.7.3.4 InfoTypesServices . . . . . . . . . . . . . . . . . . . 350
8.7.3.4.1 GetInfotypeValueData . . . . . . . . . . . . . . 350
8.7.3.5 RoutineServices . . . . . . . . . . . . . . . . . . . . 350
8.7.3.5.1 Xxx_Start Operation . . . . . . . . . . . . . . . 350
8.7.3.5.2 Xxx_StartConfirmation Operation . . . . . . . 352
8.7.3.5.3 Xxx_Stop Operation . . . . . . . . . . . . . . . 353
8.7.3.5.4 Xxx_StopConfirmation Operation . . . . . . . 355
8.7.3.5.5 Xxx_RequestResults Operation . . . . . . . . 355
8.7.3.5.6 Xxx_RequestResultsConfirmation Operation . 357
8.7.3.6 RequestControlServices . . . . . . . . . . . . . . . . 358
8.7.3.6.1 RequestControl callout . . . . . . . . . . . . . 358
8.7.3.7 ServiceRequestNotification . . . . . . . . . . . . . . 358
8.7.3.7.1 Indication . . . . . . . . . . . . . . . . . . . . . 359
8.7.3.7.2 Confirmation . . . . . . . . . . . . . . . . . . . 360

15 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.7.3.8 ClearDTCCheckFnc . . . . . . . . . . . . . . . . . . 360

8.8 Dcm as Service-Component . . . . . . . . . . . . . . . . . . . . . . . . 361
8.8.1 Implementation Data Types . . . . . . . . . . . . . . . . . . . 361
8.8.1.1 Dcm_OpStatusType . . . . . . . . . . . . . . . . . . 361
8.8.1.2 Dcm_ConfirmationStatusType . . . . . . . . . . . . . 362
8.8.1.3 Dcm_SecLevelType . . . . . . . . . . . . . . . . . . 362
8.8.1.4 Dcm_SesCtrlType . . . . . . . . . . . . . . . . . . . 363
8.8.1.5 Dcm_ProtocolType . . . . . . . . . . . . . . . . . . . 363
8.8.1.6 Dcm_NegativeResponseCodeType . . . . . . . . . . 365
8.8.1.7 Dcm_DataElementType_{Data}Type . . . . . . . . . 367
8.8.1.8 Dcm_DataElement_{Data}StructuredType . . . . . . 368
8.8.1.9 Dcm_DataElementType_{Data}ArrayType . . . . . . 369
8.8.1.10 Dcm_DataElementType_{Data}PrimitiveType . . . . 370
8.8.1.11 Dcm_DataArrayTypeUint8_{Data}Type . . . . . . . . 371
8.8.1.12 {DID}_Struct_DataType . . . . . . . . . . . . . . . . 371
8.8.1.13 Dcm_RangeArray_{Range}Type . . . . . . . . . . . 372
8.8.1.14 Dcm_InfoTypeServicesArray_{VehInfoData}Type . . 373
8.8.1.15 Dcm_RequestControlServicesInArray_{Tid}Type . . 373
8.8.1.16 Dcm_RequestControlServicesOutArray_{Tid}Type . 374
8.8.1.17 Dcm_ScalingInfoArray_{Data}Type . . . . . . . . . . 374
8.8.1.18 Dcm_RequestDataOut_{Routine}_{Signal}PrimitivType375
8.8.1.19 Dcm_RequestDataIn_{Routine}_{Signal}PrimitiveType 376
8.8.1.20 Dcm_RequestDataOut_{Routine}_{Signal}Type . . . 377
8.8.1.21 Dcm_RequestDataOut_{Routine}_{Signal}StructuredType377
8.8.1.22 Dcm_RequestDataIn_{Routine}_{Signal}Type . . . . 378
8.8.1.23 Dcm_RequestDataIn_{Routine}_{Signal}StructuredType378
8.8.1.24 Dcm_RequestDataOut_{Routine}_{Signal}ArrayType 379
8.8.1.25 Dcm_RequestDataIn_{Routine}_{Signal}ArrayType . 380
8.8.1.26 Dcm_RequestFlexibleOutArrayData_{Routine}_
{Signal}Type . . . . . . . . . . . . . . . . . . . . . . . 381
8.8.1.27 Dcm_RequestFlexibleInArrayData_{Routine}_{Sig-
nal}Type . . . . . . . . . . . . . . . . . . . . . . . . . 381
8.8.1.28 Dcm_StartDataIn_{Routine}_{Signal}PrimitivType . . 382
8.8.1.29 Dcm_StartDataIn_{Routine}_{Signal}Type . . . . . . 382
8.8.1.30 Dcm_StartDataIn_{Routine}_{Signal}StructuredType 383
8.8.1.31 Dcm_StartDataIn_{Routine}_{Signal}ArrayType . . . 384
8.8.1.32 Dcm_StartDataOut_{Routine}_{Signal}PrimitivType . 385
8.8.1.33 Dcm_StartDataOut_{Routine}_{Signal}Type . . . . . 385
8.8.1.34 Dcm_StartDataOut_{Routine}_{Signal}StructuredType 386
8.8.1.35 Dcm_StartDataOut_{Routine}_{Signal}ArrayType . . 387
8.8.1.36 Dcm_StartFlexibleInArrayData_{Routine}_{Sig-
nal}Type . . . . . . . . . . . . . . . . . . . . . . . . . 388
8.8.1.37 Dcm_StartFlexibleOutArrayData_{Routine}_{Sig-
nal}Type . . . . . . . . . . . . . . . . . . . . . . . . . 388
8.8.1.38 Dcm_StopDataIn_{Routine}_{Signal}PrimitivType . . 389
8.8.1.39 Dcm_StopDataIn_{Routine}_{Signal}Type . . . . . . 389

16 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.40 Dcm_StopDataIn_{Routine}_{Signal}StructuredType 390

8.8.1.41 Dcm_StopDataIn_{Routine}_{Signal}ArrayType . . . 391
8.8.1.42 Dcm_StopDataOut_{Routine}_{Signal}PrimitivType . 392
8.8.1.43 Dcm_StopDataOut_{Routine}_{Signal}Type . . . . . 392
8.8.1.44 Dcm_StopDataOut_{Routine}_{Signal}StructuredType 393
8.8.1.45 Dcm_StopDataOut_{Routine}_{Signal}ArrayType . . 394
8.8.1.46 Dcm_StopFlexibleInArrayData_{Routine}_{Sig-
nal}Type . . . . . . . . . . . . . . . . . . . . . . . . . 395
8.8.1.47 Dcm_StopFlexibleOutArrayData_{Routine}_{Sig-
nal}Type . . . . . . . . . . . . . . . . . . . . . . . . . 395
8.8.1.48 Dcm_KeyArray_{SecurityLevel}Type . . . . . . . . . 396
8.8.1.49 Dcm_SeedArray_{SecurityLevel}Type . . . . . . . . 396
8.8.1.50 Dcm_SecurityAccessDataRecordArray_{Secu-
rityLevel}Type . . . . . . . . . . . . . . . . . . . . . . 397
8.8.1.51 Dcm_RequestDataArrayType . . . . . . . . . . . . . 397
8.8.1.52 Dcm_ControlMask_{DID}Type . . . . . . . . . . . . . 398
8.8.1.53 Dcm_inputOutputControlParameterType . . . . . . . 398
8.8.1.54 Dcm_IOOperationRequest_{DID}Type . . . . . . . . 399
8.8.1.55 Dcm_IOOperationResponseType . . . . . . . . . . . 399
8.8.1.56 Dcm_DidSupportedType . . . . . . . . . . . . . . . . 400
8.8.1.57 Dcm_FileAndDirNameType . . . . . . . . . . . . . . 400
8.8.1.58 Dcm_ResponseDataArrayType . . . . . . . . . . . . 401
8.8.1.59 Dcm_AuthenticationRoleType . . . . . . . . . . . . . 401
8.8.1.60 Dcm_ControlMask_{Data}ArrayType . . . . . . . . . 402
8.8.1.61 Dcm_ControlMask_{Data}PrimitiveType . . . . . . . 402
8.8.1.62 Dcm_Cemr_{DID}Type . . . . . . . . . . . . . . . . . 403
8.8.2 Sender-Receiver-Interfaces . . . . . . . . . . . . . . . . . . . 403
8.8.2.1 DataServices_{DID} . . . . . . . . . . . . . . . . . . 404
8.8.2.2 DataServices_{Data} . . . . . . . . . . . . . . . . . . 404
8.8.2.3 IOControlRequest_{DID} . . . . . . . . . . . . . . . . 405
8.8.2.4 IOControlResponse_{DID} . . . . . . . . . . . . . . . 405
8.8.3 Client-Server-Interfaces . . . . . . . . . . . . . . . . . . . . . 406
8.8.3.1 SecurityAccess_{SecurityLevel} . . . . . . . . . . . . 406
8.8.3.2 DataServices_{Data} . . . . . . . . . . . . . . . . . . 409
8.8.3.2.1 ReadData . . . . . . . . . . . . . . . . . . . . 430
8.8.3.2.2 WriteData . . . . . . . . . . . . . . . . . . . . 430
8.8.3.2.3 ReadDataLength . . . . . . . . . . . . . . . . . 430
8.8.3.2.4 ConditionCheckRead . . . . . . . . . . . . . . 431
8.8.3.2.5 GetScalingInformation . . . . . . . . . . . . . 431
8.8.3.2.6 ReturnControlToEcu . . . . . . . . . . . . . . . 431
8.8.3.2.7 ResetToDefault . . . . . . . . . . . . . . . . . 431
8.8.3.2.8 FreezeCurrentState . . . . . . . . . . . . . . . 431
8.8.3.2.9 ShortTermAdjustment . . . . . . . . . . . . . . 431
8.8.3.3 DataServices_DIDRange_{Range} . . . . . . . . . . 431
8.8.3.4 InfotypeServices_{VehInfoData} . . . . . . . . . . . . 434
8.8.3.5 RoutineServices_{RoutineName} . . . . . . . . . . . 435

17 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.3.6 RequestControlServices_{Tid} . . . . . . . . . . . . 450

8.8.3.7 ServiceRequestNotification . . . . . . . . . . . . . . 450
8.8.3.8 UploadDownloadServices . . . . . . . . . . . . . . . 453
8.8.3.9 DCMServices . . . . . . . . . . . . . . . . . . . . . . 466
8.8.3.10 Authentication . . . . . . . . . . . . . . . . . . . . . . 468
8.8.4 NvDataInterface . . . . . . . . . . . . . . . . . . . . . . . . . 468
8.8.4.1 DataServices_{DID} . . . . . . . . . . . . . . . . . . 468
8.8.5 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
8.8.5.1 DataServices_DIDRange_{Range} . . . . . . . . . . 470
8.8.5.2 DataServices_{DID} . . . . . . . . . . . . . . . . . . 471
8.8.5.3 DataServices_{Data} . . . . . . . . . . . . . . . . . . 472
8.8.5.4 IOControlRequest_{DID} . . . . . . . . . . . . . . . . 474
8.8.5.5 IOControlResponse_{DID} . . . . . . . . . . . . . . . 474
8.8.5.6 DCMServices . . . . . . . . . . . . . . . . . . . . . . 474
8.8.5.7 InfotypeServices_{VehInfoData} . . . . . . . . . . . . 475
8.8.5.8 RequestControlServices_{Tid} . . . . . . . . . . . . 475
8.8.5.9 ServiceRequestManufacturerNotification_{Name} . . 476
8.8.5.10 ServiceRequestSupplierNotification_{Name} . . . . . 476
8.8.5.11 RoutineServices_{RoutineName} . . . . . . . . . . . 476
8.8.5.12 SecurityAccess_{SecurityLevel} . . . . . . . . . . . . 477
8.8.5.13 Dcm_DiagnosticSessionControlModeSwitchInterface 477
8.8.5.14 Dcm_EcuResetModeSwitchInterface . . . . . . . . . 477
8.8.5.15 Dcm_ModeRapidPowerShutDownModeSwitchInter-
face . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
8.8.5.16 Dcm_CommunicationControlModeSwitchInterface_
{ComMChannelName} . . . . . . . . . . . . . . . . . 478
8.8.5.17 Dcm_ControlDTCSettingModeSwitchInterface . . . . 478
8.8.5.18 Dcm_SecurityAccessModeSwitchInterface . . . . . . 479
8.8.5.19 Dcm_UploadDownloadServices . . . . . . . . . . . . 479
8.8.5.20 Dcm_Authentication_{Connection} . . . . . . . . . . 479
8.8.5.21 Dcm_AuthenticationStateMSI . . . . . . . . . . . . . 480
8.8.6 ModeDeclarationGroups . . . . . . . . . . . . . . . . . . . . 480
8.8.6.1 DcmDiagnosticSessionControl . . . . . . . . . . . . 480
8.8.6.2 DcmEcuReset . . . . . . . . . . . . . . . . . . . . . 481
8.8.6.3 DcmModeRapidPowerShutDown . . . . . . . . . . . 481
8.8.6.4 DcmCommunicationControl . . . . . . . . . . . . . . 482
8.8.6.5 DcmControlDTCSetting . . . . . . . . . . . . . . . . 482
8.8.6.6 DcmSecurityAccess . . . . . . . . . . . . . . . . . . 483
8.8.6.7 DcmAuthenticationState . . . . . . . . . . . . . . . . 483
8.8.7 Mode-Switch-Interfaces . . . . . . . . . . . . . . . . . . . . . 484
8.8.7.1 Dcm_DiagnosticSessionControlModeSwitchInterface 484
8.8.7.2 Dcm_EcuResetModeSwitchInterface . . . . . . . . . 484
8.8.7.3 Dcm_ModeRapidPowerShutDownModeSwitchInter-
face . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
8.8.7.4 Dcm_CommunicationControlModeSwitchInterface . 485
8.8.7.5 Dcm_ControlDTCSettingModeSwitchInterface . . . . 485

18 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.7.6 Dcm_SecurityAccessModeSwitchInterface . . . . . . 485

8.8.7.7 Dcm_AuthenticationStateModeSwitchInterface . . . 486
8.9 External diagnostic service processing . . . . . . . . . . . . . . . . . . 486
8.9.1 <Module>_<DiagnosticService> . . . . . . . . . . . . . . . . 486
8.9.2 <Module>_<DiagnosticService>_<SubService> . . . . . . . 487
8.10 Internal interfaces (not normative) . . . . . . . . . . . . . . . . . . . . . 488
8.10.1 DslInternal_SetSecurityLevel . . . . . . . . . . . . . . . . . . 488
8.10.2 DslInternal_SetSesCtrlType . . . . . . . . . . . . . . . . . . . 488
8.10.3 DspInternal_DcmConfirmation . . . . . . . . . . . . . . . . . 488
8.10.4 DslInternal_ResponseOnOneEvent . . . . . . . . . . . . . . 488
8.10.5 DslInternal_ResponseOnOneDataByPeriodicId . . . . . . . . 489
8.10.6 DsdInternal_StartPagedProcessing . . . . . . . . . . . . . . 489
8.10.7 DspInternal_CancelPagedBufferProcessing . . . . . . . . . . 489
8.10.8 DsdInternal_ProcessPage . . . . . . . . . . . . . . . . . . . 489
9 Sequence diagrams 490
9.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
9.2 DSL (Diagnostic Session Layer) . . . . . . . . . . . . . . . . . . . . . . 491
9.2.1 Process Busy behavior . . . . . . . . . . . . . . . . . . . . . 491
9.2.2 Update Diagnostic Session Control when timeout occurs . . 492
9.2.3 Process single response of ReadDataByPeriodicIdentifier . . 493
9.2.4 Process single event-triggered response of ResponseOnEvent494
9.2.5 Process concurrent requests . . . . . . . . . . . . . . . . . . 495
9.2.6 Interface to ComManager . . . . . . . . . . . . . . . . . . . . 497
9.2.6.1 Handling in Default Session . . . . . . . . . . . . . . 497
9.2.6.2 Handling in Non-Default Session . . . . . . . . . . . 498
9.2.6.3 Session transitions . . . . . . . . . . . . . . . . . . . 498
9.2.6.4 Communication States . . . . . . . . . . . . . . . . . 499
9.2.7 Receive request message and transmit negative response
message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
9.2.8 Process Service Request with paged-buffer . . . . . . . . . . 502
9.2.9 Process copy data in reception . . . . . . . . . . . . . . . . . 504
9.2.10 Process copy data in transmission . . . . . . . . . . . . . . . 505
9.3 DSP (Diagnostic Service Processing) . . . . . . . . . . . . . . . . . . . 505
9.3.1 Interface DSP - DEM (service 0x19, 0x14, 0x85) . . . . . . . 505
9.3.2 Interface special services . . . . . . . . . . . . . . . . . . . . 505
9.3.2.1 Process Diagnostic Session Control . . . . . . . . . 505
9.3.2.2 Process Tester Present . . . . . . . . . . . . . . . . 506
9.3.2.3 Process Security Access . . . . . . . . . . . . . . . . 507
9.3.2.4 Process ResponseOnEvent OnDtcChange . . . . . 508
9.3.2.5 Process ResponseOnEvent OnChangeOfDataIden-
tifier . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
9.3.2.6 Process Jump to Bootloader . . . . . . . . . . . . . . 510
9.3.2.7 Process IOControlRequest handling . . . . . . . . . 511
10 Configuration specification 514
10.1 How to read this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . 514

19 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2 Containers and configuration parameters . . . . . . . . . . . . . . . . . 514

10.2.1 Dcm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
10.2.2 DcmConfigSet . . . . . . . . . . . . . . . . . . . . . . . . . . 516
10.2.2.1 DcmPageBufferCfg . . . . . . . . . . . . . . . . . . . 516
10.2.2.2 DcmProcessingConditions . . . . . . . . . . . . . . . 517
10.2.3 DcmDsd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
10.2.3.1 DcmDsd . . . . . . . . . . . . . . . . . . . . . . . . . 520
10.2.3.2 DcmDsdService . . . . . . . . . . . . . . . . . . . . 522
10.2.3.3 DcmDsdServiceRequestManufacturerNotification . . 526
10.2.3.4 DcmDsdServiceRequestSupplierNotification . . . . . 527
10.2.3.5 DcmDsdServiceTable . . . . . . . . . . . . . . . . . 527
10.2.3.6 DcmDsdSubService . . . . . . . . . . . . . . . . . . 528
10.2.4 DcmDsl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
10.2.4.1 DcmDsl . . . . . . . . . . . . . . . . . . . . . . . . . 533
10.2.4.2 DcmDslBuffer . . . . . . . . . . . . . . . . . . . . . . 534
10.2.4.3 DcmDslDiagResp . . . . . . . . . . . . . . . . . . . . 535
10.2.4.4 DcmDslProtocol . . . . . . . . . . . . . . . . . . . . 537
10.2.4.5 DcmDslProtocolRow . . . . . . . . . . . . . . . . . . 539
10.2.4.6 DcmDslConnection . . . . . . . . . . . . . . . . . . . 547
10.2.4.7 DcmDslMainConnection . . . . . . . . . . . . . . . . 548
10.2.4.8 DcmDslProtocolRx . . . . . . . . . . . . . . . . . . . 551
10.2.4.9 DcmDslProtocolTx . . . . . . . . . . . . . . . . . . . 553
10.2.4.10 DcmDslPeriodicTransmission . . . . . . . . . . . . . 554
10.2.4.11 DcmDslPeriodicConnection . . . . . . . . . . . . . . 555
10.2.5 DcmDsp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
10.2.5.1 DcmDspReadDTCInformation . . . . . . . . . . . . . 563
10.2.5.2 DcmDspReadDTCInformationUserDefinedFault-
Memory . . . . . . . . . . . . . . . . . . . . . . . . . 564
10.2.5.3 DcmDspAuthentication . . . . . . . . . . . . . . . . . 565
10.2.5.3.1 DcmDspAuthenticationTransmitCertificate . . . 570
10.2.5.4 DcmDspAuthenticationRow . . . . . . . . . . . . . . 572
10.2.5.5 DcmDspAuthenticationConnection . . . . . . . . . . 573
10.2.5.6 Communication Control . . . . . . . . . . . . . . . . 581
10.2.5.6.1 DcmDspComControl . . . . . . . . . . . . . . 581
10.2.5.6.2 DcmDspComControlAllChannel . . . . . . . . 582
10.2.5.6.3 DcmDspComControlSetting . . . . . . . . . . 584
10.2.5.6.4 DcmDspComControlSpecificChannel . . . . . 585
10.2.5.6.5 DcmDspComControlSubNode . . . . . . . . . 586
10.2.5.7 DcmDspCommonAuthorization . . . . . . . . . . . . 588
10.2.5.8 DIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
10.2.5.8.1 DcmDspDid . . . . . . . . . . . . . . . . . . . 591
10.2.5.8.2 DcmDspDidInfo . . . . . . . . . . . . . . . . . 597
10.2.5.8.3 DcmDspDidRead . . . . . . . . . . . . . . . . 599
10.2.5.8.4 DcmDspDidSignal . . . . . . . . . . . . . . . . 602
10.2.5.8.5 DcmDspDidSignalCompositePool . . . . . . . 603
10.2.5.8.6 DcmDspDidSupportInfo . . . . . . . . . . . . . 604

20 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.8.7 DcmDspDidRange . . . . . . . . . . . . . . . . 605

10.2.5.8.8 DcmDspDidWrite . . . . . . . . . . . . . . . . 611
10.2.5.9 DcmDspControlDTCSetting . . . . . . . . . . . . . . 614
10.2.5.10 Data elements . . . . . . . . . . . . . . . . . . . . . 616
10.2.5.10.1DcmDspData . . . . . . . . . . . . . . . . . . . 616
10.2.5.10.2DcmDspDiagnosisScaling . . . . . . . . . . . 631
10.2.5.10.3DcmDspArgumentScaling . . . . . . . . . . . . 632
10.2.5.10.4DcmDspAlternativeArgumentData . . . . . . . 634
10.2.5.10.5DcmDspTextTableMapping . . . . . . . . . . . 634
10.2.5.10.6DcmDspAlternativeDataInterface . . . . . . . . 636
10.2.5.10.7DcmDspAlternativeDataType . . . . . . . . . . 638
10.2.5.10.8DcmDspAlternativeDiagnosticDataElement . . 639
10.2.5.10.9DcmDataElementInstance . . . . . . . . . . . 640
10.2.5.10.10
DcmDspExternalSRDataElementClass . . . . 641
10.2.5.10.11
DcmDspPidService01ExternalSRDataElementClass642
10.2.5.10.12
DcmSubElementInDataElementInstance . . . 642
10.2.5.10.13
DcmSubElementInImplDataElementInstance . 643
10.2.5.10.14
DcmDspDidDataSupportInfo . . . . . . . . . . 644
10.2.5.10.15
DcmDspDataInfo . . . . . . . . . . . . . . . . 646
10.2.5.11 DcmDspDidControl . . . . . . . . . . . . . . . . . . . 647
10.2.5.12 DcmDspDidControlEnableMask . . . . . . . . . . . . 652
10.2.5.13 Ecu Reset . . . . . . . . . . . . . . . . . . . . . . . . 653
10.2.5.13.1DcmDspEcuReset . . . . . . . . . . . . . . . . 653
10.2.5.13.2DcmDspEcuResetRow . . . . . . . . . . . . . 654
10.2.5.14 Memory . . . . . . . . . . . . . . . . . . . . . . . . . 656
10.2.5.14.1DcmDspMemory . . . . . . . . . . . . . . . . . 656
10.2.5.14.2DcmDspMemoryTransfer . . . . . . . . . . . . 656
10.2.5.14.3DcmDspAddressAndLengthFormatIdentifier . 657
10.2.5.14.4DcmDspMemoryIdInfo . . . . . . . . . . . . . 659
10.2.5.14.5DcmDspMemoryTransferIdInfo . . . . . . . . . 661
10.2.5.14.6DcmDspReadMemoryRangeByLabelInfo . . . 662
10.2.5.14.7DcmDspReadMemoryRangeInfo . . . . . . . . 665
10.2.5.14.8DcmDspWriteMemoryRangeByLabelInfo . . . 668
10.2.5.14.9DcmDspWriteMemoryRangeInfo . . . . . . . . 673
10.2.5.15 PIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
10.2.5.15.1DcmDspPid . . . . . . . . . . . . . . . . . . . 677
10.2.5.15.2DcmDspPidSupportInfo . . . . . . . . . . . . . 682
10.2.5.15.3DcmDspPidData . . . . . . . . . . . . . . . . . 684
10.2.5.15.4DcmDspPidService01 . . . . . . . . . . . . . . 685
10.2.5.15.5DcmDspPidService02 . . . . . . . . . . . . . . 688
10.2.5.15.6DcmDspPidDataSupportInfo . . . . . . . . . . 689
10.2.5.16 DcmDspRequestControl . . . . . . . . . . . . . . . . 691
10.2.5.17 DcmDspRequestFileTransfer . . . . . . . . . . . . . 693
10.2.5.18 Response on Event . . . . . . . . . . . . . . . . . . . 696
10.2.5.18.1DcmDspRoe . . . . . . . . . . . . . . . . . . . 696
10.2.5.19 Routines . . . . . . . . . . . . . . . . . . . . . . . . . 701

21 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.19.1DcmDspRoutine . . . . . . . . . . . . . . . . . 701
10.2.5.19.2DcmDspRequestRoutineResults . . . . . . . . 705
10.2.5.19.3DcmDspRequestRoutineResultsIn . . . . . . . 709
10.2.5.19.4DcmDspRequestRoutineResultsInSignal . . . 710
10.2.5.19.5DcmDspRequestRoutineResultsInSignalCompositePool714
10.2.5.19.6DcmDspRequestRoutineResultsOut . . . . . . 714
10.2.5.19.7DcmDspRequestRoutineResultsOutSignal . . 715
10.2.5.19.8DcmDspRequestRoutineResultsOutSignalCompositePool718
10.2.5.19.9DcmDspStartRoutine . . . . . . . . . . . . . . 719
10.2.5.19.10
DcmDspStartRoutineIn . . . . . . . . . . . . . 723
10.2.5.19.11
DcmDspStartRoutineInSignal . . . . . . . . . 726
10.2.5.19.12
DcmDspStartRoutineInSignalCompositePool . 729
10.2.5.19.13
DcmDspStartRoutineOut . . . . . . . . . . . . 730
10.2.5.19.14
DcmDspStartRoutineOutSignal . . . . . . . . 732
10.2.5.19.15
DcmDspStopRoutine . . . . . . . . . . . . . . 735
10.2.5.19.16
DcmDspStopRoutineIn . . . . . . . . . . . . . 740
10.2.5.19.17
DcmDspStartRoutineOutSignalCompositePool 741
10.2.5.19.18
DcmDspStopRoutineInSignal . . . . . . . . . . 742
10.2.5.19.19
DcmDspStopRoutineInSignalCompositePool . 746
10.2.5.19.20
DcmDspStopRoutineOut . . . . . . . . . . . . 746
10.2.5.19.21
DcmDspStopRoutineOutSignal . . . . . . . . . 748
10.2.5.19.22
DcmDspStopRoutineOutSignalCompositePool 751
10.2.5.20 Session Security and Modes . . . . . . . . . . . . . 752
10.2.5.20.1DcmDspSecurity . . . . . . . . . . . . . . . . . 752
10.2.5.20.2DcmDspSecurityRow . . . . . . . . . . . . . . 755
10.2.5.20.3DcmDspSession . . . . . . . . . . . . . . . . . 762
10.2.5.20.4DcmDspSessionRow . . . . . . . . . . . . . . 763
10.2.5.20.5DcmModeCondition . . . . . . . . . . . . . . . 766
10.2.5.20.6DcmSwcDataElementValue . . . . . . . . . . . 769
10.2.5.20.7DcmSwcDataElementPrimitive . . . . . . . . . 770
10.2.5.20.8DcmSwcDataElementArray . . . . . . . . . . . 771
10.2.5.20.9DcmSwcDataElementArrayElement . . . . . . 771
10.2.5.20.10
DcmModeRule . . . . . . . . . . . . . . . . . . 772
10.2.5.21 DcmDspVehInfo . . . . . . . . . . . . . . . . . . . . 776
10.2.5.22 DcmDspVehInfoData . . . . . . . . . . . . . . . . . . 778
10.2.5.23 DcmDspPeriodicTransmission . . . . . . . . . . . . . 780
10.2.5.24 DcmDspClearDTC . . . . . . . . . . . . . . . . . . . 786
10.2.6 DcmGeneral . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
10.2.6.1 DcmSecurityEventRefs . . . . . . . . . . . . . . . . 794
10.2.6.2 DcmSecureCoding . . . . . . . . . . . . . . . . . . . 811
10.3 Protocol Configuration Example . . . . . . . . . . . . . . . . . . . . . . 814
10.4 Published Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
A Change history of AUTOSAR traceable items 816
A.1 Traceable item history of this document according to AUTOSAR Re-
lease R24-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816

22 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

A.1.1 Added Specification Items in R24-11 . . . . . . . . . . . . . . 816

A.1.2 Changed Specification Items in R24-11 . . . . . . . . . . . . 819
A.1.3 Deleted Specification Items in R24-11 . . . . . . . . . . . . . 821
A.1.4 Added Constraints in R24-11 . . . . . . . . . . . . . . . . . . 822
A.1.5 Changed Constraints in R24-11 . . . . . . . . . . . . . . . . 822
A.1.6 Deleted Constraints in R24-11 . . . . . . . . . . . . . . . . . 823
A.2 Traceable item history of this document according to AUTOSAR Re-
lease R23-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
A.2.1 Added Specification Items in R23-11 . . . . . . . . . . . . . . 823
A.2.2 Changed Specification Items in R23-11 . . . . . . . . . . . . 825
A.2.3 Deleted Specification Items in R23-11 . . . . . . . . . . . . . 833
A.2.4 Added Constraints in R23-11 . . . . . . . . . . . . . . . . . . 833
A.2.5 Changed Constraints in R23-11 . . . . . . . . . . . . . . . . 834
A.2.6 Deleted Constraints in R23-11 . . . . . . . . . . . . . . . . . 834
A.3 Not applicable requirements . . . . . . . . . . . . . . . . . . . . . . . . 835

23 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

1 Introduction and functional overview

The Dcm SWS describes the functionality, the API, and the configuration of the
AUTOSAR Basic Software module Dcm (Diagnostic Communication Manager). The
Dcm module provides a common API for diagnostic services. The functionality of the
Dcm module is used by external diagnostic tools during the development, manufactur-
ing or service.

Offboard Onboard

AUTOSAR Application

DCM*
Manufacturing
Microcontroller (µC)

Development

Diagnostic
Tool
Service
*DCM: Diagnostic Communication Manager

Figure 1.1: Overview of the communication between the external diagnostic tools and
the onboard AUTOSAR Application

The Dcm module ensures diagnostic data flow and manages the diagnostic states, es-
pecially diagnostic sessions and security states. Furthermore, the Dcm module checks
if the diagnostic service request is supported and if the service may be executed in
the current session according to the diagnostic states.The Dcm module provides the
OSI-Layers 5 to 7 of Table 1: Diagnostic protocols and OSI-Layer.
OSI-
Protocols
Layer
UDS- Legislated
Protocol OBD -
7 - ISO14229- - - - - ISO15031-5
1 [1] - SAE [2] - SAE
J1979-2 J1979
SAE SAE
ISO 14229- J1979DA, J1979DA,
6 - - -
1:2013 [1] SAE SAE
J2012DA J2012DA
ISO14229-2
5 ISO15765-3 - - - -
[3]
4 ISO15765-2 ISO 15765-4 - - ISO 13400-2 ISO 15765-4
ISO14229-2
3 ISO15765-2 ISO 15765-4 - - ISO 13400-2
[3]
CAN- ISO14229-2
2 ISO 15765-4 LIN-Protocol FlexRay ISO 13400-3
Protocol [3]
CAN- ISO14229-2
1 ISO 15765-4 LIN-Protocol FlexRay ISO 13400-3
Protocol [3]

24 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

OSI-
Protocols
Layer

Table 1.1: Diagnostic protocols and OSI-Layers

At OSI-level 7, the Dcm module provides an extensive set of ISO14229-1 [1] services.
In addition, the Dcm module provides mechanisms to support the OBD services $01 -
$0A defined in documents [4, SAE J1979] and [2, ISO 15031-5]. With these services,
Autosar OBD functionality is capable of meeting all light duty OBD regulations worldwide
(California OBDII, EOBD, Japan OBD, and all others). At OSI-level 5, the Dcm module
handles the network-independent sections of the following specifications:
• ISO15765-3 [5]: Implementation of unified diagnostic services (UDS on CAN)
• ISO15765-4 [6]: Requirements for emission-related systems, Chapter 5 ”Session
Layer”
In the AUTOSAR Architecture the Diagnostic Communication Manager is located in the
Communication Services (Service Layer).

Figure 1.2: Position of the Dcm module in AUTOSAR Architecture

The Dcm module is network-independent. All network-specific functionality (the

specifics of networks like CAN, LIN, FlexRay or MOST) is handled outside of the Dcm
module. The PDU Router (PduR) module provides a network-independent interface
to the Dcm module. The Dcm module receives a diagnostic message from the PduR
module. The Dcm module processes and checks internally the diagnostic message.
As part of processing the requested diagnostic service, the Dcm will interact with other
BSW modules or with SW-Components (through the RTE) to obtain requested data or
to execute requested commands. This processing is very service-specific. Typically,

25 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

the Dcm will assemble the gathered information and send a message back through the
PduR module.

26 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

2 Acronyms and Abbreviations

The glossary below includes acronyms and abbreviations relevant to the Dcm module
that are not included in the [7, AUTOSAR Glossary].
Abbreviation / Acronym: Description:
AddressAndLengthFormat Defines the number of bytes used for the memoryAddress and
Identifier memorySize parameter in the request messages.
Application Layer The Application Layer is placed above the RTE. Within the Appli-
cation Layer the AUTOSAR Software-Components are placed.
Atomic Sender/Receiver inter- An atomic sender-receiver interface can be used to group DID
face data elements into one record data element prototype. All data
elements can be read or write having a single read or write oper-
ation.
Channel A link at which a data transfer can take place. If there is more
than one Channel, there is normally some kind of ID assigned to
the Channel.
Concurrent TesterPresent A UDS service TesterPresent with set suppressPosRspMsgIndi-
cationBit (3E 80) which is received with functional addressing. It
is also known as keep-alive logic..
Diagnostic Channel A link at which a data transfer between a diagnostic tool and
an ECU can take place. Example: An ECU is connected via
CAN and the diagnostic channel has an assigned CAN-ID. Diag-
nostic channels connected to other bus-systems such as MOST,
FlexRay, LIN, etc. are also possible.
External Diagnostic Tool A device which is NOT permanently connected to the vehicle
communication network. This External Diagnostic Tool can be
connected to the vehicle for various purposes, as e.g. for:
• development
• manufacturing
• service (in a garage)
Example External Diagnostic Tools are:
• a diagnostic tester
• an OBD scan tool
The External Diagnostic Tool is to be connected by a mechanic
to gather information from ”inside” the car.
Freeze Frame A set of the vehicle/system operation conditions at a specific time.
Functional Addressing The diagnostic communication model where a group or all nodes
of a specific communication network receive a message from one
sending node (1-n communication). This model is also referred
to as ’broadcast’ or ’multicast’. OBD communication will always
be done in the Functional Addressing mode.

27 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Abbreviation / Acronym: Description:

Internal Diagnostic Tool A device/ECU which is connected to the vehicle communication
network. The Internal Diagnostic Tool can be used for:
• advanced event tracking
• advanced analysis
• for service
The behavior of the Internal Diagnostic Tool can be the same as
of an External Diagnostic Tool. The notion of ”Internal Diagnos-
tic Tool” does not imply that it is included in each ECU as an
AUTOSAR Software-Component.
Physical Addressing The diagnostic communication model where a node of a specific
communication network receives a message from one sending
node (1-1 communication). This model is also referred to as ’uni-
cast’.
UDS Service this refers to a UDS Service as defined in ISO14229-1 [1].
OBD Scan tool See definition External Diagnostic Tool.
OBD Service This refers to an OBD Service as defined in ISO15031-5 [2].
OBD UDS DTC separation The feature will report a different 3 byte DTC number for SAE
J1979-2 based UDS communication than for none J1979-2 UDS
communication.
periodic transmission rate Time interval value that defines the time between two calls of a
periodic data identifier transmission. The value is configuration
specific and there are separate values for fast, medium and slow
periodic data transmission. The configured value is always an
integer multiple of the Dcm main task time.

Terms: Description:
API Application Programming Interface
CAN Controller Area Network
CEMR ControlEnableMaskRecord
Dcm Diagnostic Communication Manager
Dem Diagnostic Event Manager
Det Default Error Tracer
DID Data Identifier
DSD Diagnostic Service Dispatcher (submodule of the Dcm module)
DSL Diagnostic Session Layer (submodule of the Dcm module)
DSP Diagnostic Service Processing (submodule of the Dcm module)
DTC Diagnostic Trouble Codes
ID Identifier
LIN Local Interconnect Network
MCU Micro-Controller Unit
MOST Media Orientated System Transport
NRC Negative Response Code
OBD On-Board Diagnosis
OSI Open Systems Interconnection
PDID Periodic Data Identifier, periodically send by the Dcm after a re-
quest of ReadDataByPeriodicIndentifer
PDU Protocol Data Unit
PID Parameter Identifier
RCRRP Response correctly received - response pending
RID Routine Identifier
ROE ResponseOnEvent

28 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Terms: Description:
RTE Runtime Environment
SAP Service Access Point
SDU Service Data Unit
SID Service Identifier
SW-C Software-Component
TP Transport Protocol
UDS Unified Diagnostic Services
Xxx_ Placeholder for an API provider
SPRMIB suppressPosRspMsgIndicationBit

2.1 Typographical Conventions

This document uses the following typographical conventions:
• see configuration parameter myConfigurationParameter: this is a reference to a
configuration parameter which can be found in Chapter 10.
• myFunction(): this is a function provided or required by the module as defined in
Chapter 8

29 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

3 Related documentation

3.1 Input documents & related standards and norms

[1] ISO 14229-1(2013) – Unified diagnostic services (UDS) – Part 1: Application layer
(Release 2013-03)
https://www.iso.org
[2] ISO 15031-5 – Road vehicles – Communication between vehicle and external
equipment for emission-related diagnostic – Part 5: Emission-related diagnostic
services.
https://www.iso.org
[3] ISO 14229-2(2021) – Unified diagnostic services (UDS) - Part 2: Session layer
services (Release 2021-10)
https://www.iso.org
[4] SAE J1979 – E/E Diagnostic Test Modes
[5] ISO 15765-3 – Diagnostics on controller area network (CAN) – Part 3: Implemen-
tation of unified diagnostic services (UDS on CAN) (Release 2004 10-06)
[6] ISO 15765-4 – Diagnostics on controller area network (CAN) – Part 4: Require-
ments for emission-related systems (Release 2005 01-04)
[7] Glossary
AUTOSAR_FO_TR_Glossary
[8] General Specification of Basic Software Modules
AUTOSAR_CP_SWS_BSWGeneral
[9] ISO 14229-1(2020) – Unified diagnostic services (UDS) – Part 1: Application layer
(Release 2020-02)
https://www.iso.org
[10] Requirements on Diagnostics
AUTOSAR_FO_RS_Diagnostics
[11] Requirements on Intrusion Detection System
AUTOSAR_FO_RS_IntrusionDetectionSystem
[12] General Requirements on Basic Software Modules
AUTOSAR_CP_RS_BSWGeneral
[13] ISO 17356-3: Road vehicles – Open interface for embedded automotive applica-
tions – Part 3: OSEK/VDX Operating System (OS)
[14] Specification of PDU Router
AUTOSAR_CP_SWS_PDURouter
[15] ISO 15765-2 – Road vehicles – Diagnostics on Controller Area Networks (CAN)
– Part2: Network layer services

30 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[16] ISO 15031-6 – Road vehicles – Communication between vehicle and external
equipment for emission-related diagnostic – Part 6: Diagnostic trouble code defi-
nitions
https://www.iso.org
[17] Specification of Crypto Service Manager
AUTOSAR_CP_SWS_CryptoServiceManager
[18] Specification of Key Manager
AUTOSAR_CP_SWS_KeyManager
[19] Specification of I/O Hardware Abstraction
AUTOSAR_CP_SWS_IOHardwareAbstraction
[20] Specification of Diagnostic Event Manager
AUTOSAR_CP_SWS_DiagnosticEventManager

3.2 Related specification

AUTOSAR provides a General Specification on Basic Software modules [8, SWS BSW
General] , which is also valid for Diagnostic Communication Manager.
Thus, the specification SWS BSW General shall be considered as additional and re-
quired specification for Diagnostic Communication Manager.

31 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4 Constraints and assumptions

4.1 Limitations
The following limitations apply when using the Dcm module:
• The Dcm module does not provide any diagnostic multi-channel capabilities. This
means that parallel requests of a tester addressed to different independent func-
tionalities cannot be processed by a single Dcm module. Furthermore, the con-
cept currently implemented does not take more than one instance of a Dcm mod-
ule residing in one ECU into account. As the legislator requires that emission-
related service requests according to ISO 15031-5 [2] shall be processed prior to
any enhanced diagnostic requests, the Dcm module provides a protocol switching
mechanism based on protocol prioritization.
• UDS Service AccessTimingParameter (0x83) is not supported by the ISO stan-
dards in CAN and LIN. Also it is not planned to support this service with FlexRay.
Therefore no support for this service is planned.
• Subfunction onTimerInterrupt of Service ResponseOnEvent is not supported in
the current release.
• UDS Service SecuredDataTransmission (0x84) is not supported in the current
release.
• The Dcm SWS does not cover any SAE J1939 related diagnostic requirements.
• Due to DEM limitation, the diagnostic service $19 05 is limited to the OBD leg-
islative freeze frame.
• Management of IOControl service without InputOutputControlParameter in re-
quest and response is not supported
• The length of controlState parameter in IOControl request and response has to be
of same size (due to the one configuration parameter DcmDspDataByteSize)
• Same layout of a DID which is used in RDBI, WDBI or IOCBI services
• The user optional parameter DTCSettingControlOptionRecord in the Con-
trolDTCSetting request is only supported if it corresponds to a groupOfAllDTCs
(0xFFFFFF) value. In other cases it has to be managed in a vendor specific
implementation.
• Only the ControlDTCSetting sub-functions 0x01 and 0x02 are supported.
• The handling of infrastructure errors reported by the RTE during DCM/DEM <-
> SW-C interactions is missing from the SWS and might have to be taken into
account by implementers if they need it.
• The Dcm does not support DLT for ROE
• The ROE ServiceToRespondTo does not support PageBuffering

32 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• DID range feature cannot be applied for services DynamicallyDefineDataIdenti-

fier, ReadDataByPeriodicIdentifier and InputOutputControlById
• AUTOSAR Dcm is not intended to be used in the bootloader
• PeriodicTransmission is not possible on FlexRay, as ISO 14229-4 demands
header information (address information (source and target address) and FPL
(Frame Payload length)). This information can’t be filled with the specified con-
cept of IF interface.
• The specification of the transformer for intra ecu communication between the Dcm
module and the NvBlockSoftwareComponentType is not standardized in the cur-
rent AUTOSAR release. For this scenario custom transformers implemented by
a complex driver can be used. To elaborate on this the responsible stakeholder
(usually the OEM) needs to specify the custom transformer from a behavioral
point of view in a separate document (this might include definition of byte-ordering
or alignment). If there is the necessity to define transformer specific attributes in
the model this can be done using special data groups in UserDefinedTransforma-
tionDescription and UserDefinedTransformationISignalProps. For the configura-
tion of this scenario, a DataPrototypeMapping shall exist for the affected Sender-
ReceiverInterfaces of the Dcm module and the NvBlockSoftwareComponentType
which refers to a DataTransformation in the role firstToSecondDataTransforma-
tion. This DataTransformation shall reference exactly one TransformationTech-
nology in the role transformerChain with the transformerClass attribute set to "se-
rializer" and may compose a UserDefinedTransformationDescription in the role
transformationDescription.
• For UDS service 0x29, the Dcm supports only the sub-functions for PKI. Authen-
tication via challenge response is not supported.
• For UDS service 0x29, secure diagnostic communication with Diffie-Hellmann
key exchange is not supported.
• For UDS service 0x29 the Dcm does not support NRC ’Certificate verification failed
- Invalid Content’.
• The Dcm supports only selected subset of functionality according to ISO 14229-
1:2020 [9]. Unless explicitly stated the Dcm follows the ISO 14229-1:2013 [1].
• Autosar PduR architecture allows the use of streaming protocols. As diagnostic
protocols do not use streaming protocols, the Dcm does not support it either and
therefore the Dcm_StartOfReception with TpSduLength equal to zero is not
supported.
• The Dcm has a different order of NRCs for UDS service 0x36. The ISO14229-1
[1] defined NRC order for that service would require further APIs that would make
the overall service processing more complicated. Details can be found in chapter
7.4.2.21.
• The Dcm does not support the behavior described in the ISO 14229-1:2020 [9]
chapter 10.4.that after a powerup a single false access attempt in the previous

33 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

power cycle already starts the security delay time. ([SWS_Dcm_01355] is fol-
lowed instead.) .

4.2 Applicability to car domains

The Dcm module can be used for all car domains.

4.3 Applicability to emission-related environments (OBD)

This Dcm SWS is intended to fulfill the emission related requirements given by legisla-
tor. However, the supplier of the emission related system is responsible to fulfill the
OBD requirements. Certain requirements cannot be fulfilled by the Dcm module by itself,
but need to be considered at the level of the entire ECU or system. Example: During
the integration of the Dcm module within the system, the timing requirements (50ms
response time) must be fulfilled.
For WWH-OBD only the FunctionalGroupIdentifier 0x33 is currently supported.

34 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

5 Dependencies to other modules

The AUTOSAR Diagnostic Communication Manager (DCM) has interfaces and depen-
dencies to the following Basic Software modules and SW-Cs:

          


         

InfotypeServices ServiceRequestNotification

SecurityAccess RoutineServices
«abswRequires» «abswRequires»

«abswRequires»
DataServices «abswRequires»
«abswRequires»

«abswRequires» RequestManufacturerNotification
DataServices_DIDRange SecurityAccess ServiceRequestSupplierNotification
DataServicesPIDRPort InfotypeServices RoutineServices RequestControlServices

Dcm «abswRequires»
DataServices_DIDRange
RequestControlServices

Dem
«realize» «optional»
Dem_DcmReadDataOfOBDFreezeFrame «realize»
Dcm_MainFunction

«realize»
Dcm_Init NvM

«realize»
«optional» NvM_WriteBlock

«optional»
IoHwAb
«realize»
IoHwAb_Dcm
«realize» «mandatory»

BswM
«realize» «optional»
BswM_Dcm_ApplicationUpdated

Dcm_ComM ComM_Types
ComM_Dcm
«realize» «optional»
BswM_Dcm_CommunicationMode_CurrentState
«optional»
«mandatory» «realize» «realize»
«optional»

KeyM Csm PduR ComM

Figure 5.1: Interaction of the Dcm with other modules

• Diagnostic Event Manager (DEM): The DEM module provides function to retrieve
all information related to fault memory such that the Dcm module is able to re-
spond to tester requests by reading data from the fault memory.
• Protocol Data Unit Router (PduR module): The PduR module provides functions
to transmit and receive diagnostic data. Proper operation of the Dcm module
presumes that the PduR interface supports all service primitives defined for the
Service Access Point (SAP) between diagnostic application layer and underlying
transport layer (see ISO14229-1 [1], chapter 5 Application layer services).

35 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• Communication Manager (ComM): The ComM module provides functions such

that the Dcm module can indicate the states ”active” and ”inactive” for diagnostic
communication. The Dcm module provides functionality to handle the commu-
nication requirements ”Full-/ Silent-/ No-Communication”. Additionally, the Dcm
module provides the functionality to enable and disable Diagnostic Communica-
tion if requested by the ComM module.
• SW-C and RTE: The Dcm module has the capability to analyze the received di-
agnostic request data stream and handles all functionalities related to diagnostic
communication such as protocol handling and timing. Based on the analysis of
the request data stream the Dcm module assembles the response data stream
and delegates routines or IO-Control executions to SW-Cs .If any of the data el-
ements or functional states cannot be provided by the Dcm module itself the Dcm
requests data or functional states from SW-Cs via port-interfaces or from other
BSW modules through direct function-calls.
• BswM: The Dcm notifies the BswM that the application was updated if the initial-
ization of the Dcm is the consequence of a jump from the bootloader . The Dcm
also indicates to the BswM a communication mode change.
• Crypto Service Manager (Csm): The crypto service module provides a wide
range of cryptographic algorithms. The Csm is used for authentication calcu-
lation.
• Key Manager (KeyM): The key manager module provides support for certificate
handling and APIs to realize authenticated diagnostics via certificates.

36 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

6 Requirements Tracing
The following tables reference the requirements specified in [10], [11] as well as [12]
and links to the fulfillment of these. Please note that if column “Satisfied by” is empty for
a specific requirement this means that this requirement is not fulfilled by this document.
Requirement Description Satisfied by
[RS_Diag_04003] Network independent design [SWS_Dcm_00030]
[RS_Diag_04005] Manage Security Access level [SWS_Dcm_00020] [SWS_Dcm_00033]
handling [SWS_Dcm_00252] [SWS_Dcm_00338]
[SWS_Dcm_01397] [SWS_Dcm_01535]
[SWS_Dcm_CONSTR_06083]
[RS_Diag_04006] Manage session handling [SWS_Dcm_00022] [SWS_Dcm_00250]
[SWS_Dcm_00339] [SWS_Dcm_01373]
[SWS_Dcm_01374] [SWS_Dcm_01375]
[SWS_Dcm_01376] [SWS_Dcm_01377]
[SWS_Dcm_01378] [SWS_Dcm_01535]
[RS_Diag_04011] Provide diagnostic state information [SWS_Dcm_00338] [SWS_Dcm_00339]
to applications [SWS_Dcm_01321] [SWS_Dcm_01322]
[RS_Diag_04015] Timing handling according to [SWS_Dcm_00027] [SWS_Dcm_00030]
ISO14229-2 [SWS_Dcm_00143] [SWS_Dcm_01679]
[RS_Diag_04016] Support "Busy handling" by sending a [SWS_Dcm_00024]
negative response 0x78
[RS_Diag_04020] Suppress responses to diagnostic [SWS_Dcm_00001] [SWS_Dcm_00200]
tool requests
[RS_Diag_04021] Handling of different diagnostic [SWS_Dcm_00015] [SWS_Dcm_00079]
sessions in parallel [SWS_Dcm_00460] [SWS_Dcm_00575]
[SWS_Dcm_00576] [SWS_Dcm_00727]
[SWS_Dcm_01046] [SWS_Dcm_01602]
[SWS_Dcm_01603] [SWS_Dcm_01604]
[SWS_Dcm_01605]
[RS_Diag_04033] Support the upload/download [SWS_Dcm_00496] [SWS_Dcm_00499]
services for reading/writing data in an [SWS_Dcm_00502] [SWS_Dcm_00503]
ECU in an extended and [SWS_Dcm_00504] [SWS_Dcm_00505]
manufacturer specific diagnostic [SWS_Dcm_01417] [SWS_Dcm_01418]
session [SWS_Dcm_01419] [SWS_Dcm_01420]
[SWS_Dcm_01421] [SWS_Dcm_01422]
[SWS_Dcm_01591] [SWS_Dcm_01592]
[SWS_Dcm_01593] [SWS_Dcm_01594]
[SWS_Dcm_01595] [SWS_Dcm_01596]
[SWS_Dcm_01598]
[RS_Diag_04058] Ability to access different event [SWS_Dcm_00004] [SWS_Dcm_00005]
memories [SWS_Dcm_00077] [SWS_Dcm_00279]
[SWS_Dcm_00293] [SWS_Dcm_00295]
[SWS_Dcm_00378] [SWS_Dcm_00388]
[SWS_Dcm_00389] [SWS_Dcm_00393]
[SWS_Dcm_00465] [SWS_Dcm_01263]
[RS_Diag_04067] Provide the diagnostic status [SWS_Dcm_00293] [SWS_Dcm_00378]
information according to ISO 14229-1
[RS_Diag_04098] Interact with standard bootloader [SWS_Dcm_00532] [SWS_Dcm_00535]
[SWS_Dcm_00536] [SWS_Dcm_00592]
[SWS_Dcm_00654] [SWS_Dcm_00767]
[SWS_Dcm_01163] [SWS_Dcm_01177]
[SWS_Dcm_01423] [SWS_Dcm_01424]
[SWS_Dcm_01425] [SWS_Dcm_CONSTR_06080]
5

37 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Requirement Description Satisfied by
[RS_Diag_04115] The optional parameter DTCSetting [SWS_Dcm_00406] [SWS_Dcm_01063]
ControlOptionRecord as part of UDS
service ControlDTCSetting shall be
limited to GroupOfDTC
[RS_Diag_04119] Handle the execution of diagnostic [SWS_Dcm_00628] [SWS_Dcm_00858]
services according to the assigned [SWS_Dcm_00859] [SWS_Dcm_01435]
diagnostic session
[RS_Diag_04147] Communication with the transport [SWS_Dcm_00642] [SWS_Dcm_01186]
layers to receive and send diagnostic
data
[RS_Diag_04153] Support generic connections [SWS_Dcm_00849] [SWS_Dcm_01347]
[SWS_Dcm_01348]
[RS_Diag_04159] Control of DTC storage [SWS_Dcm_00249] [SWS_Dcm_01399]
[RS_Diag_04160] ResponseOnEvent according to ISO [SWS_Dcm_00135] [SWS_Dcm_00894]
14229-1 [SWS_Dcm_01410] [SWS_Dcm_01625]
[SWS_Dcm_01626] [SWS_Dcm_01627]
[SWS_Dcm_01628] [SWS_Dcm_01629]
[SWS_Dcm_01630] [SWS_Dcm_01631]
[SWS_Dcm_01632]
[RS_Diag_04162] Parallel fault memory access [SWS_Dcm_01369] [SWS_Dcm_01370]
[SWS_Dcm_01371] [SWS_Dcm_01372]
[RS_Diag_04163] Parallel OBD and UDS processing [SWS_Dcm_01367]
[RS_Diag_04180] Process all UDS Services related to [SWS_Dcm_01623]
diagnostic fault memory of ISO
14229-1 internally
[RS_Diag_04196] UDS Service handling for all [SWS_Dcm_01622] [SWS_Dcm_01671]
diagnostic services defined in ISO [SWS_Dcm_01672] [SWS_Dcm_01673]
14229-2
[RS_Diag_04203] Common checks on all supported [SWS_Dcm_01622]
UDS Services Requests
[RS_Diag_04205] Support of SnapshotRecords [SWS_Dcm_01623] [SWS_Dcm_01624]
[RS_Diag_04209] Pseudo parallel client interaction [SWS_Dcm_01674] [SWS_Dcm_01675]
according to ISO [SWS_Dcm_01676] [SWS_Dcm_01677]
[SWS_Dcm_01678]
[RS_Diag_04215] Support of UDS service ReadDataBy [SWS_Dcm_00721] [SWS_Dcm_00722]
PeriodicIdentifier (0x2A) [SWS_Dcm_00820] [SWS_Dcm_00843]
[SWS_Dcm_01096] [SWS_Dcm_01097]
[SWS_Dcm_01098] [SWS_Dcm_01099]
[SWS_Dcm_01101] [SWS_Dcm_01103]
[SWS_Dcm_01104] [SWS_Dcm_01105]
[SWS_Dcm_01106] [SWS_Dcm_01111]
[SWS_Dcm_01112] [SWS_Dcm_01115]
[SWS_Dcm_01117] [SWS_Dcm_01118]
[SWS_Dcm_01568] [SWS_Dcm_01569]
[SWS_Dcm_01570] [SWS_Dcm_01571]
[SWS_Dcm_01572] [SWS_Dcm_01573]
[SWS_Dcm_01574] [SWS_Dcm_01575]
[SWS_Dcm_01576] [SWS_Dcm_01577]
[SWS_Dcm_01578] [SWS_Dcm_01613]
5

38 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Requirement Description Satisfied by
[RS_Diag_04218] Support of UDS service 0x2F Input [SWS_Dcm_00256] [SWS_Dcm_00396]
OutputControlByIDentifier [SWS_Dcm_00397] [SWS_Dcm_00398]
[SWS_Dcm_00399] [SWS_Dcm_00563]
[SWS_Dcm_00564] [SWS_Dcm_00565]
[SWS_Dcm_00579] [SWS_Dcm_00580]
[SWS_Dcm_00581] [SWS_Dcm_00640]
[SWS_Dcm_00680] [SWS_Dcm_00682]
[SWS_Dcm_01273] [SWS_Dcm_01274]
[SWS_Dcm_01275] [SWS_Dcm_01277]
[SWS_Dcm_01313] [SWS_Dcm_01434]
[SWS_Dcm_01436] [SWS_Dcm_01437]
[SWS_Dcm_01438] [SWS_Dcm_01439]
[SWS_Dcm_01440] [SWS_Dcm_01441]
[SWS_Dcm_01554] [SWS_Dcm_01600]
[SWS_Dcm_91057] [SWS_Dcm_91058]
[SWS_Dcm_91059] [SWS_Dcm_91060]
[SWS_Dcm_91061] [SWS_Dcm_CONSTR_06084]
[SWS_Dcm_CONSTR_06085]
[SWS_Dcm_CONSTR_06086]
[RS_Diag_04224] Support the UDS service 0x31 [SWS_Dcm_01442] [SWS_Dcm_01443]
(RoutineControl) according to ISO [SWS_Dcm_01580] [SWS_Dcm_01581]
14229-1
[RS_Diag_04230] Support of UDS service 0x29 [SWS_Dcm_01459] [SWS_Dcm_01460]
(Authentication) [SWS_Dcm_01461] [SWS_Dcm_01463]
[SWS_Dcm_01464] [SWS_Dcm_01465]
[SWS_Dcm_01466] [SWS_Dcm_01467]
[SWS_Dcm_01468] [SWS_Dcm_01469]
[SWS_Dcm_01477] [SWS_Dcm_01478]
[SWS_Dcm_01479] [SWS_Dcm_01480]
[SWS_Dcm_01481] [SWS_Dcm_01482]
[SWS_Dcm_01483] [SWS_Dcm_01484]
[SWS_Dcm_01485] [SWS_Dcm_01486]
[SWS_Dcm_01487] [SWS_Dcm_01488]
[SWS_Dcm_01489] [SWS_Dcm_01493]
[SWS_Dcm_01503] [SWS_Dcm_01504]
[SWS_Dcm_01506] [SWS_Dcm_01507]
[SWS_Dcm_01508] [SWS_Dcm_01509]
[SWS_Dcm_01510] [SWS_Dcm_01511]
[SWS_Dcm_01512] [SWS_Dcm_01513]
[SWS_Dcm_01515] [SWS_Dcm_01518]
[SWS_Dcm_01528] [SWS_Dcm_01529]
[SWS_Dcm_01530] [SWS_Dcm_01532]
[SWS_Dcm_01533] [SWS_Dcm_01534]
[SWS_Dcm_01535] [SWS_Dcm_01536]
[SWS_Dcm_01537] [SWS_Dcm_01538]
[SWS_Dcm_01542] [SWS_Dcm_01544]
[SWS_Dcm_01551] [SWS_Dcm_01558]
[SWS_Dcm_01559] [SWS_Dcm_01560]
[SWS_Dcm_01561] [SWS_Dcm_01565]
[SWS_Dcm_01579] [SWS_Dcm_01588]
[SWS_Dcm_CONSTR_06094]
[SWS_Dcm_CONSTR_06096]
[RS_Diag_04232] Access rights in client certificates [SWS_Dcm_01516] [SWS_Dcm_CONSTR_06087]
[SWS_Dcm_CONSTR_06089]
5

39 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Requirement Description Satisfied by
[RS_Diag_04233] Access granularity of diagnostic [SWS_Dcm_01496] [SWS_Dcm_01514]
services [SWS_Dcm_01522] [SWS_Dcm_01523]
[SWS_Dcm_01524] [SWS_Dcm_01525]
[SWS_Dcm_01526] [SWS_Dcm_01527]
[SWS_Dcm_01539] [SWS_Dcm_01540]
[SWS_Dcm_01541] [SWS_Dcm_01545]
[SWS_Dcm_01546] [SWS_Dcm_01547]
[SWS_Dcm_01548] [SWS_Dcm_01549]
[SWS_Dcm_01552] [SWS_Dcm_01553]
[SWS_Dcm_01555] [SWS_Dcm_01556]
[SWS_Dcm_01557] [SWS_Dcm_01562]
[SWS_Dcm_CONSTR_06088]
[RS_Diag_04234] Binary compatibility of white list for [SWS_Dcm_01521] [SWS_Dcm_01522]
individual access [SWS_Dcm_01523] [SWS_Dcm_01524]
[SWS_Dcm_01525] [SWS_Dcm_01526]
[SWS_Dcm_01527]
[RS_Diag_04235] Client certificate validity [SWS_Dcm_01470] [SWS_Dcm_01471]
[SWS_Dcm_01472] [SWS_Dcm_01473]
[SWS_Dcm_01474] [SWS_Dcm_01475]
[SWS_Dcm_01476]
[RS_Diag_04243] Update of constant parameters [SWS_Dcm_01582] [SWS_Dcm_01583]
through diagnostics [SWS_Dcm_01584] [SWS_Dcm_01585]
[SWS_Dcm_01586] [SWS_Dcm_01587]
[SWS_Dcm_91088]
[RS_Diag_04248] Support of session control service [SWS_Dcm_00311]
[RS_Diag_04249] Support of session layer service [SWS_Dcm_00024] [SWS_Dcm_00027]
[SWS_Dcm_00111] [SWS_Dcm_00114]
[SWS_Dcm_00115] [SWS_Dcm_00117]
[SWS_Dcm_00143] [SWS_Dcm_00654]
[SWS_Dcm_00703] [SWS_Dcm_00837]
[SWS_Dcm_00839] [SWS_Dcm_01073]
[SWS_Dcm_01425] [SWS_Dcm_01666]
[SWS_Dcm_01667] [SWS_Dcm_01668]
[SWS_Dcm_01669] [SWS_Dcm_01670]
[SWS_Dcm_01679]
[RS_Diag_04250] Support subfunction 0x1A and 0x56 [SWS_Dcm_01607] [SWS_Dcm_01608]
of UDS service 0x19 [SWS_Dcm_01609] [SWS_Dcm_01610]
[SWS_Dcm_01611] [SWS_Dcm_01612]
[SWS_Dcm_01640]
[RS_Diag_04253] Support separated DTCs for UDS [SWS_Dcm_01618] [SWS_Dcm_01619]
and OBD based on J1979-2
[RS_Diag_04254] Independent CP Software Cluster [SWS_Dcm_91090] [SWS_Dcm_91091]
development [SWS_Dcm_91092] [SWS_Dcm_91093]
[SWS_Dcm_91094] [SWS_Dcm_91095]
[SWS_Dcm_91098] [SWS_Dcm_91099]
[SWS_Dcm_91100] [SWS_Dcm_91101]
[SWS_Dcm_91102] [SWS_Dcm_91103]
[SWS_Dcm_91104] [SWS_Dcm_91105]
[SWS_Dcm_91106] [SWS_Dcm_91107]
[RS_Diag_04271] Support of Transmit Certificate [SWS_Dcm_01682] [SWS_Dcm_01683]
[RS_Diag_04272] Support of secure data coding [SWS_Dcm_01684] [SWS_Dcm_01685]
[SWS_Dcm_01686] [SWS_Dcm_01687]
[SWS_Dcm_01688] [SWS_Dcm_01689]
[SWS_Dcm_01690] [SWS_Dcm_01691]
[SWS_Dcm_01692] [SWS_Dcm_01693]
[SWS_Dcm_01694] [SWS_Dcm_01695]
5

40 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Requirement Description Satisfied by
[RS_Ids_00810] Basic SW security events [SWS_Dcm_01589] [SWS_Dcm_01590]
[SWS_Dcm_01702] [SWS_Dcm_01703]
[SWS_Dcm_01704] [SWS_Dcm_01705]
[SWS_Dcm_01706] [SWS_Dcm_01707]
[SWS_Dcm_01708] [SWS_Dcm_01709]
[SWS_Dcm_01710] [SWS_Dcm_01711]
[SWS_Dcm_01712] [SWS_Dcm_01713]
[SWS_Dcm_01714] [SWS_Dcm_01715]
[SWS_Dcm_01716] [SWS_Dcm_01717]
[SWS_Dcm_01718] [SWS_Dcm_01719]
[SWS_Dcm_01720] [SWS_Dcm_01721]
[SWS_Dcm_01722] [SWS_Dcm_01723]
[SWS_Dcm_01724] [SWS_Dcm_01725]
[SWS_Dcm_01726] [SWS_Dcm_01727]
[SWS_Dcm_01728] [SWS_Dcm_01729]
[SWS_Dcm_01730] [SWS_Dcm_01731]
[SWS_Dcm_01732] [SWS_Dcm_01733]
[SWS_Dcm_01734] [SWS_Dcm_01735]
[SWS_Dcm_01736] [SWS_Dcm_01737]
[SWS_Dcm_01738] [SWS_Dcm_01739]
[SWS_Dcm_01740] [SWS_Dcm_01741]
[SWS_Dcm_01742] [SWS_Dcm_01743]
[SWS_Dcm_01744] [SWS_Dcm_01745]
[SWS_Dcm_01746] [SWS_Dcm_01747]
[SWS_Dcm_01748] [SWS_Dcm_01749]
[SWS_Dcm_01750] [SWS_Dcm_01751]
[SWS_Dcm_01752] [SWS_Dcm_01753]
[SRS_BSW_00003] All software modules shall provide [SWS_Dcm_00065]
version and identification information
[SRS_BSW_00101] The Basic Software Module shall be [SWS_Dcm_00033] [SWS_Dcm_00034]
able to initialize variables and [SWS_Dcm_00035] [SWS_Dcm_00037]
hardware in a separate initialization
function
[SRS_BSW_00337] Classification of development errors [SWS_Dcm_00040]
[SRS_BSW_00369] All AUTOSAR Basic Software [SWS_Dcm_00044]
Modules shall not return specific
development error codes via the API
[SRS_BSW_00373] The main processing function of each [SWS_Dcm_00053]
AUTOSAR Basic Software Module
shall be named according the defined
convention
[SRS_BSW_00407] Each BSW module shall provide a [SWS_Dcm_00065]
function to read out the version
information of a dedicated module
implementation
[SRS_BSW_00424] BSW module main processing [SWS_Dcm_00053]
functions shall not be allowed to enter
a wait state
[SRS_BSW_00438] Configuration data shall be defined in [SWS_Dcm_00037]
a structure
[SRS_BSW_00452] Classification of runtime errors [SWS_Dcm_01416]
[SRS_BSW_00482] Get version information function shall [SWS_Dcm_00065]
follow a naming rule

Table 6.1: Requirements Tracing

41 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7 Functional specification

7.1 General design elements

7.1.1 Submodules within the Dcm module

To define the functionality of the Dcm module, The Dcm SWS models the Dcm module
as consisting of the following submodules:
• Diagnostic Session Layer (DSL) submodule: The DSL submodule ensures data
flow concerning diagnostic requests and responses, supervises and guarantees
diagnostic protocol timing and manages diagnostic states (especially diagnostic
session and security).
• Diagnostic Service Dispatcher (DSD) submodule: The DSD submodule pro-
cesses a stream of diagnostic data. The submodule:
– Receives a new diagnostic request over a network and forwards it to a data
processor.
– Transmits a diagnostic response over a network when triggered by the data
processor (e.g. by the DSP submodule).
• Diagnostic Service Processing (DSP) submodule: The DSP submodule handles
the actual diagnostic service (respectively subservice) requests.
The next graphic gives an overview of the interfaces between the submodules DSP,
DSD, and DSL within the Dcm module.

42 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DEM Interface DEM DspInternal_CancelPagedBufferProcessing()

Xxx_ReadData() DsdInternal_ProcessPage()
Xxx_WriteData() DspInternal_DcmUpdatePage()
Xxx_ReadDataLength() DsdInternal_StartPagedProcessing()
Xxx_ConditionCheckRead()
Xxx_GetScalingInformation()
DSD
Service Interpreter calls
Xxx_ReturnControlToECU()
Xxx_ResetToDefault() DSP DspInternal_DcmConfirmation()
Xxx_FreezeCurrentState() <Module>_<DiagnosticService>_<SubService>-
Xxx_ShortTermAdjustement()
<Module>_<DiagnosticService>()-
Xxx_GetInfoTypeValue()
Xxx_IsDidAvailable()
Xxx_WriteDidData()
Xxx_ReadDidData()

Data Confirmation functionality

Data Indication functionality
Xxx_Start()

Transmit functionality
Xxx_Stop()
Xxx_RequestResults() External
Xxx_RequestControl()
Xxx_GetSeed() module
Xxx_CompareKey()
Xxx_Indication()
Xxx_Confirmation()
PDU Router
Dcm_StartOfReception ()
Dcm_CopyRxData ()
Dcm_CopyTxData()
Dcm_RxIndication()
DslInternal_GetSesCtrlType() Dcm_TxConfirmation()
PduR_DcmTransmit()
DslInternal_SetSecurityLevel()

DSL PduR_DcmCancelTransmitResqest()
PduR_DcmCancelReceiveResqest()
Dcm_ResetToDefaultSession()
Dcm_GetSecurityLevel() COM Manager
Dcm_GetSesCtrlTypel() *1 | see page
*2 | before

Dcm_Init()

Figure 7.1: Possible interaction between the submodules in the DCM

Note: The implementation of these submodules and the interfaces between them is
not mandatory. They are introduced only to improve the readability of the specification.

7.1.2 Negative Response Code (NRC)

The standards defining the UDS Services and OBD Services define the negative re-
sponse codes (NRCs). The Dcm SWS uses these NRCs in the interfaces between the
Dcm and other BSW modules and the SW-Cs. These NRCs are defined in the data
type Dcm_NegativeResponseCodeType.

[SWS_Dcm_01075] dThe order of the transmitted NRC shall be compliant with the one
described in ISO14229-1 [1].c

43 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.1.3 Non-volatile information

Several features of the Dcm require non-volatile information to be initialized. AUTOSAR

does not describe how this information is accessed or if the information is already avail-
able when the Dcm is initialized. Therefore the access for the non-volatile information
is implementation specific and has to be ensured during integration.

[SWS_Dcm_00870] dThe Dcm shall check if the NvM is read out correctly. If the non-
volatile information could not read out correct the Dcm shall start a default reaction.
The default reaction is described in the chapter were the usage of the non-volatile data
is described.c

[SWS_Dcm_01048] dIf the Dcm cancels a service with NvM access, it shall call
NvM_CancelJobs().c

The service is cancelled either by reaching the maximum number of RCRRP NRCs or
by protocol preemption.

7.1.4 Types

[SWS_Dcm_00969] dThe Dcm shall treat non-integer data types (e.g. uint8[n]) either
like integer data types of the matching size or leave their contents uninterpreted in case
DcmDspDataEndianness is configured to OPAQUE.c

[SWS_Dcm_00970] dThe Dcm module shall interpret opaque data as uint8[n] and shall
always map it to an n-bytes sized signal. For opaque data endianness, DcmDsp-
DataEndianness has to be configured to OPAQUE.c

[SWS_Dcm_00971] dThe Dcm shall extend the endianness conversion defined in [13],
to signed data types.c

In [13] (Chapter 2.4) the endianness conversion is defined for unsigned data types.
The associated configurations can be found in the configuration DcmDspData.

7.1.4.1 Atomic types overview

Figure 7.2: Atomic types overview

44 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.1.4.2 Data array types overview

Figure 7.3: Data array types overview

7.1.4.3 Nested Data types overview

The data types used for DIDs and Diagnostic Routines may be defined in a nested way.
A DID or Routine Argument may consist of several elements, e.g. an array where each
array element is a structure, and that structure consists of several data elements typed
by primitives, arrays, or further structures.
In the configuration this represented by a dedicated pattern:
• the root data element defines a pool of nested elements (e.g. DcmDspDidSig-
nalCompositePool in DcmDspDid)
• the root data element has an anchor object (e.g. DcmDspDidSignal), this an-
chor object may represent primitive or array data, in this case there is no refer-
ence to a pool element defined (e.g. DcmDspDidSignalCompositeRef).
• if the anchor object represents a structure, then it defines one or more references
to pool elements (e.g. DcmDspDidSignalCompositeRef). This defines that
the referenced pool elements build the content of that structure.
A pool element may itself be a nested definition. This allows for an arbitrary nesting of
structured elements.

45 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp: DcmDspData:
EcucParamConfContainerDef +subContainerEcucParamConfContainerDef

lo w e rM ultiplicity = 0 lo w e rM ultiplicity = 0
+parameter
u p p e rMultiplicity = 1 u p p e rM ultiplicity = *
DcmDspDataByteSize:
EcucIntegerParamDef +destination

lo w e rM ultiplicity = 0
u p p e rMultiplicity = 1
m in = 0
max = 65535 A
+subContainer
+parameter
DcmDspDid:
EcucParamConfContainerDef DcmDspDidDataRef:
EcucReferenceDef
u p p e rM ultiplicity = *
lo w e rM ultiplicity = 0 +reference lo w e rM ultiplicity = 0
DcmDspDidSignal: EcucParamConfContainerDef u p p e rMultiplicity = 1
+subContainer
lo w e rM ultiplicity = 0
u p p e rM ultiplicity = * +parameter
DcmDspDidByteOffset:
EcucIntegerParamDef

+subContainer lo w e rM ultiplicity = 1
u p p e rMultiplicity = 1
+reference m in = 0
max = 65535
DcmDspDidSignalCompositeRef:
EcucReferenceDef

lo w e rM ultiplicity = 0
u p p e rM ultiplicity = *

+destination

DcmDspDidSignalCompositePool:
+subContainer
EcucParamConfContainerDef

lo w e rM ultiplicity = 0
u p p e rM ultiplicity = *

Figure 7.4: Nested data for DcmDspDid

[SWS_Dcm_01633] dIf a DcmDspDidSignal contains at least one DcmDspDidSig-

nalCompositeRef, then that DcmDspDidSignal shall only define the following pa-
rameters:
• DcmDspDidByteOffset
• DcmDspDataByteSize.
c

Specifically this means that DcmDspDidSignal shall not define any DcmDspDid-
DataRef, as this would give details about specific data type information of primitive or
array data types. If the DcmDspDidSignal contains a DcmDspDidSignalCompos-
iteRef then this DcmDspDidSignal is a nested data type.

[SWS_Dcm_01634] dThe nested data type occupies a consecutive number of bytes (

DcmDspDataByteSize) starting at the position DcmDspDidByteOffset.c

[SWS_Dcm_01635] dAll of the data types that are defined in the scope of the nested
data type shall be placed inside the area defined by DcmDspDataByteSize and
DcmDspDidByteOffset.c

46 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01636] dThe DcmDspDidByteOffset values of nested data elements

shall be given to the absolute starting position of the DID (NOT relative to the respective
composite structure).c

[SWS_Dcm_01637] dEach DcmDspDidSignalCompositePool shall only be refer-

enced up to once by a DcmDspDidSignalCompositeRef. Each DcmDspDidSig-
nalCompositePool element is specifically defined to be at a dedicated position in
the DID and can only occur once in the definition of the DcmDspDid.c

[SWS_Dcm_01638] dA DcmDspDidSignalCompositeRef shall only refer to DcmD-

spDidSignalCompositePool elements which are defined in the scope of the same
DcmDspDid as the owner of the DcmDspDidSignalCompositeRef.c

The specification above has been defined on the basis of the DcmDspDid. The same
pattern for the definition of nested data types has been applied to further parts of the
configuration. The following list gives the respective correspondence between the con-
figuration items used above and the further configuration items used for the definition
of nested data types.

[SWS_Dcm_01639] dThe nesting of data types does not only apply to DcmDspDid,
but is also supported for the following definitions:
• DcmDspDid corresponds to
– DcmDspStartRoutineIn
– DcmDspStartRoutineOut
– DcmDspStopRoutineIn
– DcmDspStopRoutineOut
– DcmDspRequestRoutineResultsIn
– DcmDspRequestRoutineResultsOut
• DcmDspDidSignal corresponds to
– DcmDspStartRoutineInSignal
– DcmDspStartRoutineOutSignal
– DcmDspStopRoutineInSignal
– DcmDspStopRoutineOutSignal
– DcmDspRequestRoutineResultsInSignal
– DcmDspRequestRoutineResultsOutSignal
• DcmDspDidSignalCompositePool corresponds to

47 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

– DcmDspStartRoutineInSignalCompositePool
– DcmDspStartRoutineOutSignalCompositePool
– DcmDspStopRoutineInSignalCompositePool
– DcmDspStopRoutineOutSignalCompositePool
– DcmDspRequestRoutineResultsInSignalCompositePool
– DcmDspRequestRoutineResultsOutSignalCompositePool
• DcmDspDidSignalCompositeRef corresponds to
– DcmDspStartRoutineInSignalCompositeSignalRef
– DcmDspStartRoutineOutSignalCompositeSignalRef
– DcmDspStopRoutineInSignalCompositeSignalRef
– DcmDspStopRoutineOutSignalCompositeSignalRef
– DcmDspRequestRoutineResultsInSignalCompositeSignalRef
– DcmDspRequestRoutineResultsOutSignalCompositeSignalRef
c

The example nested data type in figure 7.5 is defined as A which consists of X and Y
defined as primitive types.
0 1 2 3 4 5 6 7 8

A
X Y

Figure 7.5: Nested data type for DcmDspStartRoutineIn

A starts at position 2 of the DcmDspStartRoutineIn and has a size of 4 byte. The

nested leaf elements X and Y are defined within the range of the structure A and do
not overlap. In this example there is even a gap left between X and Y.

48 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspStartRoutineIn: DcmDspRoutineParameterSize_Signal_A:
EcucContainerValue EcucNumericalParamValue

value = 4

DcmDspRoutineSignalPos_Signal_A:
EcucNumericalParamValue

value = 2

DcmDspStartRoutineInSignal_Signal_A: DcmDspStartRoutineInSignalCompositeSignalRef_Y:
EcucContainerValue EcucReferenceValue

DcmDspStartRoutineInSignalCompositeSignalRef_X:
EcucReferenceValue

DcmDspStartRoutineInSignalContainedPool_Y:
EcucContainerValue

DcmDspStartRoutineInSignalContainedPool_X:
EcucContainerValue

DcmDspStartRoutineInSignal_Signal_X: DcmDspStartRoutineInSignal_Signal_Y:
EcucContainerValue EcucContainerValue

DcmDspRoutineSignalPos_Signal_X:
DcmDspRoutineSignalPos_Signal_Y:
EcucNumericalParamValue
EcucNumericalParamValue
value = 2
value = 4

DcmDspRoutineParameterSize_Signal_X: DcmDspRoutineParameterSize_Signal_Y:
EcucNumericalParamValue
EcucNumericalParamValue
value = 1 value = 2

DcmDspRoutineSignalType_Signal_X: DcmDspRoutineSignalType_Signal_Y:
EcucTextualParamValue EcucTextualParamValue
value = UINT8 value = UINT16

Figure 7.6: Example configuration of nested data for DcmDspStartRoutineIn

In figure 7.6 an example configuration is shown for a nested data type of figure 7.5.
The container DcmDspStartRoutineIn holds the definition of the root element
DcmDspStartRoutineInSignal_Signal_A as well as the two pool elements DcmDsp-
StartRoutineInSignalContainedPool_X and DcmDspStartRoutineInSignalContained-
Pool_Y.
The root element DcmDspStartRoutineInSignal_Signal_A defines its absolute start
position as 2 (DcmDspRoutineSignalPos_Signal_A) and its size in byte as
4 (DcmDspRoutineParameterSize_Signal_A). The root element DcmDspStartRou-
tineInSignal_Signal_A also defines that there are two nested elements part of that
root element using the references DcmDspStartRoutineInSignalContainedPool_X and
DcmDspStartRoutineInSignalContainedPool_Y. These references point to pool ele-
ments defined in the scope of the same DcmDspStartRoutineIn.

49 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

The referenced pool elements define each their absolute position (DcmDspRoutineS-
ignalPos_Signal_X ) as well as their size (DcmDspRoutineParameterSize_Signal_X )
and primitive type (DcmDspRoutineSignalType_Signal_X ).

7.1.4.4 Data types constraints

[SWS_Dcm_CONSTR_06002] Existence of size parameter dDcmDspDataByte-

Size shall be present if DcmDspDataType is set to: UINT8_N, SINT8_N, UINT16_N,
SINT16_N, UINT32_N, SINT32_N, FLOAT_N or UINT8_DYN.c

Note: DcmDspDataByteSize is not required for primitive datatypes

[SWS_Dcm_CONSTR_06035] Restrictions on size parameter for 16 Bit arrays d

DcmDspDataByteSize shall be a multiple of 2 if the value is greater than 2 and
DcmDspDataType is UINT16_N or SINT16_N.c

[SWS_Dcm_CONSTR_06036] Restrictions on size parameter for 32 Bit arrays d

DcmDspDataByteSize shall be a multiple of 4 if the value is greater than 4 and
DcmDspDataType is UINT32_N or SINT32_N.c

[SWS_Dcm_CONSTR_06008] Define the usage of DcmDspRoutineParameter-

Size parameter dDcmDspRoutineParameterSize is only required if DcmDspRou-
tineSignalType is set to SINT8_N, SINT16_N, SINT32_N, UINT8_N, UINT16_N,
UINT32_N, FLOAT_N or VARIABLE_LENGTH.c

[SWS_Dcm_CONSTR_06011] Only last parameters in RID may have a variable

length dDcmDspRoutineSignalType with VARIABLE_LENGTH is only valid for the last
signal.c

[SWS_Dcm_CONSTR_06012] Existence of size parameter dDcmDspPid-

DataByteSize shall be present if DcmDspPidDataType is set to: UINT8_N,
SINT8_N, UINT16_N, SINT16_N, UINT32_N or SINT32_N.c

Note: DcmDspPidDataByteSize is not required for primitive datatypes

[SWS_Dcm_CONSTR_06040] Restrictions on size parameter for 16 Bit arrays d

DcmDspPidDataByteSize shall be a multiple of 2 if the value is greater than 2 and
DcmDspPIDDataType is UINT16_N or SINT16_N.c

50 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_CONSTR_06041] Restrictions on size parameter for 32 Bit arrays d

DcmDspPidDataByteSize shall be a multiple of 4 if the value is greater than 4 and
DcmDspPIDDataType is UINT32_N or SINT32_N.c

UINT8 shall be used as (implementation) data type for bit lengths between 1 and 8

[SWS_Dcm_CONSTR_06026] Usage of variable data length in case of S/R com-

munication, NvRam access or ECU signal access dIn case DcmDspDataUse-
Port is set to {USE_DATA_SENDER_RECEIVER, USE_DATA_SENDER_RECEIVER_-
AS_SERVICE, USE_ECU_SIGNAL}, the usage of variable data length shall be not al-
lowed.c

[SWS_Dcm_CONSTR_06031] dThe DcmDspData.SHORT-NAME and DcmDspPid-

Data.SHORT-NAME shall be distinct.c

Note: Variable data length is only possible with UINT8 arrays with DcmDspDataType
set to UINT8_DYN.

7.1.4.5 Dcm_OpStatusType

For the operation using the Dcm_OpStatusType, the Dcm shall work as follow :

[SWS_Dcm_00527] dAt first call of an operation using the Dcm_OpStatusType, the

Dcm call the operation with OpStatus = DCM_INITIALc

[SWS_Dcm_00528] dIf the value DCM_E_FORCE_RCRRP is returned from an oper-

ation using Dcm_OpStatusType, the Dcm shall invoke the transmit request for RCR-RP
(NRC 0x78 transmission) and the Dcm shall not realize further invocation of the opera-
tion till RCR-RP is transmitted.c

[SWS_Dcm_00529] dAfter transmit confirmation of a RCR-RP transmitted on the con-

text of [SWS_Dcm_00528], the Dcm calls, from Dcm_MainFunction (due to call con-
text), the operation again with OpStatus = DCM_FORCE_RCRRP_OK.c

[SWS_Dcm_00530] dIf a DCM_E_PENDING value is returned from an operation using

the Dcm_OpStatusType, the Dcm call the operation on each Dcm_MainFunction call
with OpStatus = DCM_PENDING as long as DCM_E_PENDING is returned.c

51 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.1.4.6 Dcm_Cemr_{DID}Type

For ease of use in SWC, the Dcm generates a symbolic name to access the CEMR bit
according to Dcm_Cemr_{DID}Type (see [SWS_Dcm_91087]) for each data element
used in a DID with IO control. The SWC can work only with the generated symbolic
value of the bitfield text table to mask out a certain bit. This helps to avoid confusion,
while the first RID bit on the network controls the first parameter of the DID but that Bit
is the most significant Bit in the MSB. The symbolic name also helps if the size of the
RID is changing. In that case the bitmask changes as well, but the symbolic value is
always updated.

7.2 Diagnostic Session Layer (DSL)

7.2.1 Introduction

[SWS_Dcm_00030]
Upstream requirements: RS_Diag_04003, RS_Diag_04015

dAll functional areas of the DSL submodule shall be in conformance with the specifica-
tions ISO14229-1 [1], ISO14229-2 [3] and the network-independent part of ISO15765-3
[5].c

There is no network-dependent functional area in the DSL submodule. Within the con-
figuration, some parameters can be set dependent on the network.

7.2.2 Use cases

The DSL submodule provides the following functionalities:

• Session handling (as required by ISO14229-1 [1] and ISO 15765-3 [5])
• Application layer timing handling (as required by ISO14229-1 [1] and ISO 15765-
3 [5])
• Specific response behavior (as required by ISO14229-1 [1] and ISO 15765-3 [5])
• Authentication state handling per diagnostic connection (as required by ISO
14229-1:2018)
– Provide authentication state per connection
– Manage authentication state transitions

52 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.2.3 Interaction with other modules

The DSL has the following interaction with other modules:

• PduR module
– PduR module provides data of incoming diagnostic requests.
– The DSL submodule triggers output of diagnostic responses.
• DSD submodule
– The DSL submodule informs the DSD submodule about incoming requests
and provides the data.
– The DSD submodule triggers output of diagnostic responses.
• SW-Cs / DSP submodule. The DSL submodule provides access to security and
session state.
• ComM module
– The DSL submodule guarantees the communication behavior required by
the ComM module

7.2.4 Functional description

7.2.4.1 Overview

The DSL submodule provides the following functionality:

Request Handling
• Forward requests from the PduR module to the DSD submodule.
• Concurrent TesterPresent (”keep alive logic”).
Response Handling
• Forward responses from the DSD submodule to the PduR module.
• Guarantee response timing to tester.
• Support of periodic transmission.
• Support of ResponseOnEvent (ROE) transmission.
• Support of segmented response.
• Support of ResponsePending response triggered by the application.
Security Level Handling
• Manage security level.

53 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Authentication
• Manage authentication state per diagnostic connection
Session State Handling
• Manage session state.
• Keep track of active non-default sessions.
• Allows modifying timings.
Diagnostic Protocol Handling
• Handling of different diagnostic protocols.
• Manage resources.
Communication Mode Handling
• Handling of communication requirements (Full- / Silent- / No Communication).
• Indicating of active / inactive diagnostic.
• Enabling / disabling all kinds of diagnostic transmissions.

7.2.4.2 Forward requests from the PduR module to the DSD submodule

The PduR module indicates the Dcm module whenever a reception of new diagnostic
request content is started on a DcmDslProtocolRxPduId, which is assigned to the
Dcm module. This is done by calling Dcm_StartOfReception, which inform the Dcm
module of the data size to be received and provides the data of the first frame or single
frame, and allows the Dcm to reject the reception if the data size overflows its buffer
size, or if the requested service is not available. The further call to Dcm_CopyRxData
request the Dcm module to copy the data from the provided buffer to the Dcm buffer.
If the reception of a diagnostic request is finished (when Dcm_StartOfReception
succeeded) the PduR module will call Dcm_TpRxIndication to give a receive indi-
cation to the Dcm module. The Dcm shall be able to use generic connections, where
the addressing information is provided to Dcm by Dcm_StartOfReception via the
MetaData of the DcmRxPdu. This addressing information must be stored and used for
the response and for detection of requests from the same tester. see section 7.2.4.5
Generic Connection Handling for further details.

[SWS_Dcm_00111]
Upstream requirements: RS_Diag_04249

dThe DSL submodule shall forward received data to the DSD submodule only after a call
of Dcm_TpRxIndication with parameter Result = E_OK (see [SWS_Dcm_00093]).c

54 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00241] dAs soon as a request message is received (after a call of Dcm_-

TpRxIndication with parameter Result = E_OK (see [SWS_Dcm_00093]) and until
a call to Dcm_TpTxConfirmation (see [SWS_Dcm_00351]) for the associated Tx-
DcmPduId), the DSL submodule shall block the corresponding DcmPduId. During the
processing of this request, no other request of the same DcmDslConnection (e.g.
an enhanced session can be ended by a OBD session) can be received, until the corre-
sponding response message is sent and the DcmPduId is released again (except for
Concurrent TesterPresent requests).c

More descriptions of the APIs (prototype, input/output parameter) can be found in the
interface description of PduR module [14].
It is allowed to have different DcmPduIds for different diagnostic communication appli-
cations. For example:
• OBD DcmDslProtocolRxPduId: for reception of OBD requests,
• OBD DcmTxPduId: for transmission of OBD responses,
• UDS phys DcmDslProtocolRxPduId: for reception of UDS physically addressed
requests,
• UDS func DcmDslProtocolRxPduId: for reception of UDS functionally ad-
dressed requests,
• UDS DcmTxPduId: for transmission of UDS responses.
Address type (physical/functional addressing) is configured per DcmDslProtocol-
RxPduId. A configuration per DcmDslProtocolRxPduId is possible because there
will always be different DcmDslProtocolRxPduId values for functional and physi-
cal receptions, independent of the addressing format of the Transport Layer (extended
addressing, normal addressing).

7.2.4.2.1 Dcm_StartOfReception

[SWS_Dcm_00444] dIf the requested size is large than the buffer available in the
DCM, the function Dcm_StartOfReception shall return BUFREQ_E_OVFL (see
[SWS_Dcm_00094]).c

[SWS_Dcm_00642]
Upstream requirements: RS_Diag_04147

dWhen the API Dcm_StartOfReception is invoked with TpSduLength equal to 0,

the value BUFREQ_E_NOT_OK shall be returned.c

55 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01671] Message reception according to ISO 14229-2

Upstream requirements: RS_Diag_04196

dThe Dcm shall receive and handle diagnostic messages according to the session layer
services of ISO14229-2 [3].c

[SWS_Dcm_01672] Mapping of T_DataSOM.ind

Upstream requirements: RS_Diag_04196

dThe Dcm shall map a call of Dcm_StartOfReception to the T_DataSOM.ind from

ISO14229-2 [3].c

[SWS_Dcm_01673] Mapping of T_Data.ind

Upstream requirements: RS_Diag_04196

dThe Dcm shall map a call of Dcm_TpRxIndicationto T_Data.ind from ISO14229-2

[3].c

[SWS_Dcm_01674] Multi client handling

Upstream requirements: RS_Diag_04209

dThe Dcm shall handle requests from multiple clients according to ISO14229-1 [1] An-
nex J.c

”Figure J.2 - Multiple client handling flow” of ISO14229-1 [1] gives a comprehensive
overview of parallel client request handling. A major aspect is the support of additional
protocol resources. The Dcm follows this flow chart and provides protocol resources per
configured DcmDslProtocolRow. In default session this allows the Dcm to process
requests in parallel.

[SWS_Dcm_01675] Protocol resource availability

Upstream requirements: RS_Diag_04209

dThe Dcm shall assign additional protocol resource to each configured DcmDslPro-
tocolRow with a own DcmDslBuffer.c

The configuration parameter DcmDslDiagRespOnSecondDeclinedRequest de-

fines the behavior of the decision box ”Is NRC 0x21 handling supported?” of ”Figure
J.2 - Multiple client handling flow” of ISO14229-1 [1].

[SWS_Dcm_01676] Decline a second request with NRC 0x21

Upstream requirements: RS_Diag_04209

dIf the Dcm is rejecting a second received request according to ISO14229-1 [1] Annex
J and DcmDslDiagRespOnSecondDeclinedRequest is set to TRUE, the Dcm shall
return a NRC 0x21 as response for the rejected second received request.c

56 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01677] Ignoring a second request

Upstream requirements: RS_Diag_04209

dIf the Dcm is rejecting a second received request according to ISO14229-1 [1] Annex J
and DcmDslDiagRespOnSecondDeclinedRequest is set to FALSE, the Dcm shall
ignore the new request. .c

ISO14229-1 [1] Annex J misses a definition of the server in case a second diagnostic
request is received from the same connection, while the server is still processing a
request on that connection. The Dcm fills this gap by not accepting further diagnostic
requests for processing. In that case no response is send, even no NRC 0x21.

[SWS_Dcm_01678] Mulitple requests on the same connection

Upstream requirements: RS_Diag_04209

dIf the Dcm receives a further diagnostic request for processing and the Dcm is still
processing an ongoing request on the same connection, the Dcm shall decline the new
received request.c

7.2.4.2.2 Dcm_CopyRxData

[SWS_Dcm_00443] dIf Dcm_StartOfReception returns BUFREQ_OK, the further

call to Dcm_CopyRxData shall copy the data from the buffer provided in info parame-
ter) to the Dcm buffer and update the bufferSizePtr parameter with remaining free place
in Dcm receive buffer after completion of this call.c

[SWS_Dcm_00996] dWhen the API Dcm_CopyRxData is invoked with SduLength

from info equal to 0, the value BUFREQ_OK shall be returned and bufferSizePtr shall
be filled with the remaining size of the Rx buffer.c

Note: The size of the Rx buffer is based on the buffer length, which is returned in the
parameter RxBufferSizePtr of API Dcm_StartOfReception.

[SWS_Dcm_00342] dAfter starting to copy the received data (see

[SWS_Dcm_00443]), the Dcm module shall not access the receive buffer until it
is notified by the service Dcm_TpRxIndication about the successful completion or
unsuccessful termination of the reception.c

Note: Dcm_TpRxIndication is only expected when Dcm_StartOfReception suc-

ceeded

57 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.2.4.2.3 Dcm_TpRxIndication

[SWS_Dcm_00344] dIf Dcm_TpRxIndication is called with parameter Result dif-

ferent from E_OK, then the Dcm module shall not evaluate the buffer assigned to the
I-PDU, which is referenced in parameter DcmRxPduId.c

Rationale for [SWS_Dcm_00344]: It is undefined which part of the buffer contains valid
data in this case

7.2.4.3 Concurrent TesterPresent (”keep alive logic”)

The Concurrent TesterPresent is defined by ISO14229-1 [1] and also called ”by-
pass logic” or ”keep alive logic”. The purpose is to keep the non-default session active
and reset the S3 timer defined by ISO14229-2 [3]. Concurrent TesterPresent
are only received by functional addressing and are processed independent from any
activity on a physical request and service processing.

[SWS_Dcm_01666] Concurrent tester present support

Upstream requirements: RS_Diag_04249

dThe Dcm shall handle and process the Concurrent TesterPresent according to
ISO14229-1 [1].c

In addition to ISO14229-1 [1] the Dcm limits the processing for received Concurrent
TesterPresent messages to the connection from where the request to enter a non-
default session was received. This avoids that a tester that did not request the non-
default session can influence the protocol and timing behavior of another tester.

[SWS_Dcm_01667] Concurrent tester present from different connections

Upstream requirements: RS_Diag_04249

dThe Dcm shall only process and handle Concurrent TesterPresent messages
received on the same DcmDslConnection that requested the Dcm to enter the non-
default session.c

7.2.4.3.1 Dcm_CopyTxData

If the copied data is smaller than the length requested to transmit within the service
PduR_DcmTransmit() the Dcm module will be requested by the service Dcm_CopyTx-
Data to provide another data when the current copied data have been transmitted.

58 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00346] dIf the function Dcm_CopyTxData is called and the Dcm module
successfully copied the data in the buffer provided in info parameter, then the function
shall return BUFREQ_OK.c

[SWS_Dcm_00350] dCaveats of Dcm_CopyTxData:

• The value of parameter availableDataPtr of function Dcm_CopyTxData shall not
exceed the number of Bytes still to be sent.
• If this service returns BUFREQ_E_NOT_OK the transmit requests issued by
calling the service PduR_DcmTransmit() is still not finished. A final confirma-
tion (indicating an error with call of service Dcm_TpTxConfirmation) is re-
quired to finish this service and to be able to start another transmission (call
to PduR_DcmTransmit()). So it is up to the transport protocol to confirm the abort
of transmission.
c

7.2.4.3.2 Dcm_TpTxConfirmation

[SWS_Dcm_00352] dIf the function Dcm_TpTxConfirmation is called, then the Dcm

module shall unlock the transmit buffer.c

[SWS_Dcm_00353] dIf the function Dcm_TpTxConfirmation is called, then the Dcm

module shall stop error handling (Page buffer timeout, P2ServerMax/P2*ServerMax
timeout ).c

For transmission via FlexRay the following restriction has to be considered: Since the
FlexRay Specification does not mandate the existence of a transmit interrupt, the exact
meaning of this confirmation (i.e. "transfer into the FlexRay controller’s send buffer" OR
"transmission onto the FlexRay network") depends on the capabilities of the FlexRay
communication controller and the configuration of the FlexRay Interface.

7.2.4.4 Forward responses from the DSD submodule to the PduR module

[SWS_Dcm_00114]
Upstream requirements: RS_Diag_04249

dThe DSD submodule shall request the DSL submodule for transmission of responses.c

59 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00115]
Upstream requirements: RS_Diag_04249

dWhen the diagnostic response of a DcmDslMainConnection is ready, the DSL sub-

module shall trigger the transmission of the diagnostic response to the PduR mod-
ule by calling PduR_DcmTransmit() using the corresponding DcmDslProtocolTxP-
duRef parameter as PduId.c

[SWS_Dcm_01072] dIn case of PeriodicTransmission, the Dcm shall provide in the

call to PduR_DcmTransmit() the full payload data and expect no call to Dcm_CopyTx-
Data.c

[SWS_Dcm_01073]
Upstream requirements: RS_Diag_04249

dIn case of PeriodicTransmission, the Dcm will be called for periodic transmission with
Dcm_TxConfirmation to indicate the transmission result.c

Responses are sent with the DcmTxPduId, which is linked in the Dcm module configura-
tion to the DcmDslProtocolRxPduId, i.e. the ID the request was received with (see
configuration parameter DcmDslProtocolTx) Within PduR_DcmTransmit() only the
length information and, for generic connections, the addressing information, is given to
the PduR module. After the Dcm module has called successfully PduR_DcmTransmit(),
the PduR module will call Dcm_CopyTxData to request the Dcm module to provide the
data to be transmitted and will call Dcm_TpTxConfirmation after the complete PDU
has successfully been transmitted or an error occurred. see section 7.2.4.5 "Generic
Connection Handling for further details on address information handling within generic
connections".

[SWS_Dcm_00117]
Upstream requirements: RS_Diag_04249

dIf the DSL submodule receives a confirmation after the complete Dcm PDU has suc-
cessfully been transmitted or an error occurred by a call of Dcm_TpTxConfirmation,
then the DSL submodule shall forward this confirmation to the DSD submodule.c

[SWS_Dcm_00118] dIn case of a failed transmission (failed PduR_DcmTransmit() re-

quest) or error confirmation (Dcm_TpTxConfirmation with error), the DSD submod-
ule shall not repeat the diagnostic response transmission.c

Note: Dcm_TpTxConfirmation is only expected when PduR_DcmTransmit suc-

ceeded.

[SWS_Dcm_01166] dIf the Multiplicity of DcmDslProtocolTx is set to "0" the Dcm

shall process the received diagnostic request without sending a response.c

60 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

More descriptions of the APIs (prototype, input/output parameter) can be found in the
interface description of the PduR module [14].

7.2.4.5 Generic Connection Handling

The Dcm shall be able to handle generic connections, identified by DcmPdus with Meta-
DataItems of type SOURCE_ADDRESS_16 and TARGET_ADDRESS_16. These con-
nections carry the actual tester address at run time. Generic connections are sup-
ported for diagnostics over IP and FlexRay diagnostics, and CAN diagnostics using
normal fixed or mixed 29 bit addressing formats according to ISO15765-2 [15]. De-
pending on the actual layout of the CAN IDs, generic connections could also be used
for extended or normal and mixed 11 bit addressing formats. The Dcm is not aware of
the actual addressing format used by CanTp. Several connections may reference the
same DcmPdus.

[SWS_Dcm_CONSTR_06044] dGeneric connections shall be consistent. This means

that the MetaDataItems and the PduLength of all referenced PDUs of a DcmDslCon-
nection (DcmDslProtocolRxPduRef, DcmDslProtocolTxPduRef, DcmDslPe-
riodicTxPduRef)are identical.c

[SWS_Dcm_00848] dThe source address of diagnostic requests received via

a generic connection must be stored. It is provided in the MetaDataItem
SOURCE_ADDRESS_16 provided via Dcm_StartOfReception.c

[SWS_Dcm_00849] Target address for generic connection transmission

Upstream requirements: RS_Diag_04153

dIf the Dcm is about to send a response, response on event, or periodic message for a
generic connection request, the Dcm shall set TARGET_ADDRESS_16 to the value of
the stored source address in the MetaDataPtr in the PduR_DcmTransmit().c

[SWS_Dcm_01429] dThe source address of diagnostic requests received via a

generic connection shall be provided in the parameter TesterSourceAddress
to the application [SWS_Dcm_01341], [SWS_Dcm_01342], [SWS_Dcm_00694],
[SWS_Dcm_00698]).c

[SWS_Dcm_01347]
Upstream requirements: RS_Diag_04153

dThe target address of diagnostic requests received via a generic connec-

tion can be provided in the MetaDataItem TARGET_ADDRESS_16 received via
Dcm_StartOfReception(). In this case, the Dcm shall ignore physical requests where
the target address is not equal to the configured ECU address DcmDspProtocolE-
cuAddr.c

61 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01348]
Upstream requirements: RS_Diag_04153

dThe source address of the response transmitted via generic connections can be read
from the configuration parameter DcmDspProtocolEcuAddr. It shall be provided to
PduR_DcmTransmit() in the MetaDataItem SOURCE_ADDRESS_16, if that is config-
ured for the transmit PDU.c

Note: If different source addresses are required for certain transmitted di-
agnostic messages of the same DcmDslProtocolRow, the MetaDataItem
SOURCE_ADDRESS_16 can be omitted from the PDUs, and the address can then
be configured in the lower layers. The same is possible for physical requests, where
the TARGET_ADDRESS_16 can be omitted from the PDUs.

7.2.4.6 Guarantee timing to tester by sending busy responses

[SWS_Dcm_00024]
Upstream requirements: RS_Diag_04016, RS_Diag_04249

dIf the Application (or the DSP submodule) is able to perform a requested diagnos-
tic task, but needs additional time to finish the task and prepare the response, then
the DSL submodule shall send a negative response with NRC 0x78 (Response pend-
ing) when reaching the response time (DcmDspSessionP2ServerMax - DcmTim-
StrP2ServerAdjust respectively DcmDspSessionP2StarServerMax - DcmTim-
StrP2StarServerAdjust).c

Rationale for [SWS_Dcm_00024]: The DSL submodule guarantees the response tim-
ing to tester.

[SWS_Dcm_00119] dThe DSL submodule shall send negative responses as required

in [SWS_Dcm_00024] from a separate buffer.c

Rationale for [SWS_Dcm_00119]: This is needed in order to avoid overwriting the on-
going processing of requests, e.g. the application already prepared response contents
in the diagnostic buffer. The number of negative responses with NRC 0x78 (response
pending) for one diagnostic request can be limited by the configuration parameter
DcmDslDiagRespMaxNumRespPend to avoid endless NRC 0x78 transmission in case
of an application deadlock.

[SWS_Dcm_01567] dThe maximum number of negative responses with NRC 0x78 can
be configured using the optional configuration parameter DcmDslDiagRespMaxNum-
RespPend (see ECUC_Dcm_00693). If this parameter is not configured, the default
amount of negative responses with NRC 0x78 is infinite.c

62 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.2.4.7 Support of periodic transmission

The UDS service ReadDataByPeriodicIdentifier (0x2A) allows the tester to request the
periodic transmission of data record values from the ECU identified by one or more
periodicDataIdentifiers.

[SWS_Dcm_00122] dThe Dcm module shall send responses for periodic transmissions
using a separate protocol and a separate buffer of configurable size.c

The DcmDslPeriodicTransmissionConRef configuration parameter allows linking

the protocol used to receive the periodic transmission request / transmit the periodic
transmission response to the protocol used for the transmission of the periodic trans-
mission messages. Note that multiple DcmTxPduIds can be assigned to the periodic
transmission protocol. The Dcm module respects several restrictions according to the
communication mode:

[SWS_Dcm_00123] dPeriodic transmission communication shall only take place in Full

Communication Mode.c

Periodic transmission events can occur when not in Full Communication Mode. So the
following requirement exists:

[SWS_Dcm_00125] dThe Dcm module shall discard periodic transmission events be-
side Full Communication Mode and shall not queue it for transmission.c

[SWS_Dcm_00126] dPeriodic transmission events shall not activate the Full Commu-
nication Mode.c

7.2.4.8 Support of segmented response (paged-buffer)

[SWS_Dcm_00028] dIf enabled (DcmPagedBufferEnabled=TRUE), the Dcm mod-

ule shall provide a mechanism to send responses larger than the configured and allo-
cated diagnostic buffer.c

[SWS_Dcm_CONSTR_06055] Dependency for DcmDslProtocolMaximumRe-

sponseSize dDcmDslProtocolMaximumResponseSize shall be only present if
DcmPagedBufferEnabled is set to TRUE.c

63 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01058] dIf DcmPagedBufferEnabled == TRUE and the generated Re-

sponse for a Request is longer than DcmDslProtocolMaximumResponseSize, the
Dcm shall respond with NRC 0x14 (DCM_E_RESPONSETOOLONG).c

[SWS_Dcm_01059] dIf DcmPagedBufferEnabled == FALSE and the generated Re-

sponse for a Request is longer than Dcm_MsgContextType structure element resMax-
DataLen, the Dcm shall respond with NRC 0x14 (DCM_E_RESPONSETOOLONG) .c

With paged-buffer handling the ECU is not forced to provide a buffer, which is as large
as the maximum length of response. Please note:
• paged-buffer handling is for transmit only - no support for reception.
• paged-buffer handling is not available for the Application (DCM-internal use only).

[SWS_Dcm_01186]
Upstream requirements: RS_Diag_04147

dThe Dcm shall provide the correct amount of Data requested by the TP or return
BUFREQ_E_BUSY in case the requested amount of data is not available.c

Note: In case the requested amount of data is not available, the Dcm should fill up the
paged buffer immediately.

7.2.4.9 Support of ResponsePending response triggered by the Application

In some cases, e.g. in case of routine execution, the Application needs to request an
immediate NRC 0x78 (Response pending), which shall be sent immediately and not
just before reaching the response time (P2ServerMax respectively P2*ServerMax).
When the Dcm module calls an operation and gets an error status
DCM_E_FORCE_RCRRP, the DSL submodule will trigger the transmission of a
negative response with NRC 0x78 (Response pending). This response needs to be
sent from a separate buffer, in order to avoid overwriting the ongoing processing of the
request.

7.2.4.10 Manage security level

[SWS_Dcm_00020]
Upstream requirements: RS_Diag_04005

dThe DSL submodule shall save the level of the current active security level.c

64 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

For accessing this level, the DSL submodule provides interfaces to:
• get the current active security level: Dcm_GetSecurityLevel
• set a new security level: DslInternal_SetSecurityLevel()

[SWS_Dcm_00033]
Upstream requirements: SRS_BSW_00101, RS_Diag_04005

dDuring Dcm initialization the security level is set to the value 0x00
(DCM_SEC_LEV_LOCKED).c

[SWS_Dcm_00139] dThe DSL shall reset the security level to the value 0x00 (i.e. the
security is enabled) under one of the following conditions: - if a transition from any
diagnostic session other than the defaultSession to another session other than the de-
faultSession (including the currently active diagnostic session) is performed or - if a
transition from any diagnostic session other than the defaultSession to the defaultSes-
sion (DslInternal_SetSecurityLevel()) (initiated by UDS Service DiagnosticSessionCon-
trol (0x10) or S3Server timeout) is performed.c

Only one security level can be active at a time.

[SWS_Dcm_01329] dOn every security level change the Dcm shall update the Mod-
eDeclarationGroup DcmSecurityAccess with the new security level.c

[SWS_Dcm_CONSTR_06083] Dependency on DcmDspSecurityAttemptCoun-

terEnabled
Upstream requirements: RS_Diag_04005

dIf DcmDspSecurityNumAttDelay is not configured, the DcmDspSecurityAt-

temptCounterEnabled on the same DcmDspSecurityRow shall be set to FALSE.c

[SWS_Dcm_CONSTR_06101] dDcmDspSecurityResetAttemptCounterOnTimeout
shall be present only if the DcmDspSecurityAttemptCounterEnabled for
DcmDspSecurityRow is set to TRUE.c

7.2.4.10.1 Initialization sequence

[SWS_Dcm_01154] dAt initialization, for each DcmDspSecurityRow entry for which

the DcmDspSecurityAttemptCounterEnabled configuration parameter is set to
TRUE, the corresponding Xxx_GetSecurityAttemptCounter shall be called in or-
der to get the value of the AttemptCounter for each of these DcmDspSecurityRow
entries.c

65 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01156] dIf Xxx_GetSecurityAttemptCounter has returned

E_NOT_OK the attempt counter shall be set to the value configured in DcmD-
spSecurityNumAttDelay of the according SecurityLevel.c

[SWS_Dcm_01351] dIf any Xxx_GetSecurityAttemptCounter opera-

tion returns a DCM_E_PENDING value, the Dcm shall interrupt calling the
Xxx_GetSecurityAttemptCounter() in order to resume this chain of calls within
the next Dcm_MainFunction() cycle.c

Note: this may be the case when these values are stored within some specific non-
volatile memory.

[SWS_Dcm_CONSTR_06076] Dependency for DcmDspSecurityGetAttempt-

CounterFnc dDcmDspSecurityGetAttemptCounterFnc shall be present only if
DcmDspSecurityUsePort is set to USE_ASYNCH_FNC and DcmDspSecurityAt-
temptCounterEnabled is set to TRUE.c

[SWS_Dcm_01352] dIf the delay after the first call of the Dcm_MainFunction() which
is configured in DcmDspSecurityMaxAttemptCounterReadoutTime has been
reached and all the Xxx_GetSecurityAttemptCounter have not been called
yet (i.e. one operation has returned a DCM_E_PENDING status in the previous
Dcm_MainFunction() cycle), the pending operation shall be cancelled by a call with
the OpStatus set to DCM_CANCEL.c

[SWS_Dcm_01353] dIn the conditions of [SWS_Dcm_01352], the AttemptCounters of

remaining security levels (which have not been obtained via the calls to their Xxx_Get-
SecurityAttemptCounter) shall be initialized with the value configured in DcmD-
spSecurityNumAttDelay of the according SecurityLevel.c

[SWS_Dcm_01354] dWhile not all Xxx_GetSecurityAttemptCounter operations

have returned a final status and the operation chain has not been cancelled, the con-
ditionsNotCorrect (0x22) NRC shall be returned to any SecurityAccess (0x27) request-
Seed subfunction request.c

[SWS_Dcm_01355] dOnce all the AttemptCounter values have been successfully or

unsuccessfully retrieved (all the Xxx_GetSecurityAttemptCounter() operations have
been executed and have returned a final, non-PENDING error value or the opera-
tion chain has been cancelled), if at least one of the restored AttemptCounter val-
ues is greater than or equal to the DcmDspSecurityNumAttDelay configured for
its corresponding DcmDspSecurityRow, the Dcm shall start the SecurityDelayTimer
with the higher value of DcmDspSecurityDelayTimeOnBoot / DcmDspSecurity-
DelayTime of the according DcmDspSecurityRow.c

66 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01356] dA timer (DcmDspSecurityDelayTime, DcmDspSecurity-

MaxAttemptCounterReadoutTime) which is configured with 0 shall be considered
to have timed out instantaneously when it is started, i.e. shall have no delay effect.c

[SWS_Dcm_CONSTR_06074] Dependency for DcmDspSecurityMaxAttempt-

CounterReadoutTime dDcmDspSecurityMaxAttemptCounterReadoutTime
shall be a multiple and at minimum equal to DcmTaskTime.c

7.2.4.10.2 AttemptCounter update

[SWS_Dcm_01357] dA successful sendKey subfunction request shall reset that secu-

rity level’s specific AttemptCounter.c

[SWS_Dcm_01599] dIf DcmDspSecurityResetAttemptCounterOnTimeout is set to

TRUE and SecurityDelayTimer expires, the Dcm shall reset that security level’s spe-
cific AttemptCounter.c

[SWS_Dcm_01155] dThe Dcm shall call Xxx_SetSecurityAttemptCounter() (in case

the configuration parameter DcmDspSecurityAttemptCounterEnabled for the ac-
cording DcmDspSecurityRow is set to TRUE) when the Dcm has changed the attempt
counter to inform the application about the counter change.c

[SWS_Dcm_CONSTR_06078] Dependency for DcmDspSecuritySetAttempt-

CounterFnc dDcmDspSecuritySetAttemptCounterFnc shall be present only if
DcmDspSecurityUsePort is set to USE_ASYNCH_FNC and the DcmDspSecurity-
AttemptCounterEnabled set to TRUE.c

7.2.4.11 Manage session state

[SWS_Dcm_00022]
Upstream requirements: RS_Diag_04006

dThe DSL submodule shall save the state of the current active session.c

For accessing this variable, the DSL submodule provides interfaces to:
• get the current active session: Dcm_GetSesCtrlType
• set a new session: DslInternal_SetSesCtrlType()

67 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00034]
Upstream requirements: SRS_BSW_00101

dDuring Dcm initialization, the session state is set to the value 0x01 ("DefaultSession").c

[SWS_Dcm_01062] dThe call to Dcm_ResetToDefaultSession allows the appli-

cation to reset the current session to Default session and invokes the mode switch
of the ModeDeclarationGroupPrototype DcmDiagnosticSessionControl by calling
SchM_Switch_<bsnp>_DcmDiagnosticSessionControl(RTE_MODE_DcmDiagnostic
SessionControl_DCM_DEFAULT_SESSION).c

Example: Automatic termination of an extended diagnostic session upon exceeding of

a speed limit.

7.2.4.12 Manage authentication state

The Dcm provides means for authenticated diagnostics. The DSL sub-module provides
an authentication state per diagnostic connection. It initializes this state upon startup
and takes care about fallback into non-authenticated states if the connection is idle for
some time.

[SWS_Dcm_01477] Authentication state per connection

Upstream requirements: RS_Diag_04230

dThe Dcm shall provide an authentication state per configured DcmDslConnection.c

[SWS_Dcm_01478] Mode declaration group per connection

Upstream requirements: RS_Diag_04230

dThe Dcm shall provide the authentication state of each connection via the ModeDec-
larationGroupPrototype DcmAuthenticationState_<ConnectionName>.c

The Dcm maintains an authentication state and mirrors this state to the mode dec-
laration group DcmAuthentication_<ConnectionName>. This mode declaration group
is intended to be changed only by the Dcm, however applications changing this state
have no influence on the Dcm authentication state.

[SWS_Dcm_01479] Authentication states

Upstream requirements: RS_Diag_04230

dThe Dcm shall support per connection the two authentication states:c

• deauthenticated
• authenticated

68 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Upon startup, the Dcm is in deauthenticated state or restores the persisted state. A
transition to authenticated state can only be done after the client successfully exe-
cuted the authentication sequence. In some use cases as in production, a frequent
power-on/power off sequence is performed. To keep the achieved authentication state
over the power off, there is a dedicated mode rule requesting the Dcm to persist the
authenticated state.

[SWS_Dcm_01480] Initialization of authentication state

Upstream requirements: RS_Diag_04230

dIf DcmDspAuthenticationPersistStateModeRuleRef is not configured or the

mode rule referenced by DcmDspAuthenticationPersistStateModeRuleRef is
evaluated to false, the Dcm shall initialize within Dcm_Init all authentication states to
deauthenticated state.c

[SWS_Dcm_01481] Initialization of persisted authentication states

Upstream requirements: RS_Diag_04230

dIf the mode rule referenced by DcmDspAuthenticationPersistState-

ModeRuleRef is evaluated to true, the Dcm shall initialize the persisted authentication
state including role and white list on each connection.c

Transitions between authenticated states are controlled by both DSL and DSP sub-
modules. The DSL sub-module is in charge for fallback of authenticated state into
deauthenticated state. The DSP sub-module is in charge for transition changes trig-
gered from a client by diagnostic services.

Figure 7.7: Authenticated state transitions without persistent states

[SWS_Dcm_01482] Fallback to deauthenticated state on idle connection

Upstream requirements: RS_Diag_04230

dThe Dcm shall make a transition from authenticated into deauthenticated state for a
configured connection if the following conditions apply:

69 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• The Dcm was in default session when the last diagnostic response was sent on
that connection and
• DcmDspAuthenticationDefaultSessionTimeOut is configured and no di-
agnostic request was received on that connection for DcmDspAuthentica-
tionDefaultSessionTimeOut seconds after the last Dcm_TpTxConfirma-
tion on that connection.
c

[SWS_Dcm_01483] Fallback to deauthenticated session on S3server timeout

Upstream requirements: RS_Diag_04230

dIf the Dcm is in a non-default session and a S3server timeout occurs, the Dcm shall
perform a transition from authenticated into deauthenticated state on the authentication
state assigned to that connection which was in a non-default session.c

[SWS_Dcm_01484] Clearing persisted authentication state

Upstream requirements: RS_Diag_04230

dIf the authentication state of a connection performs a transition to deauthenticated

state, the Dcm shall clear all persisted authentication information on that connection.c

[SWS_Dcm_01485] Reaction of fallback into deauthenticated state

Upstream requirements: RS_Diag_04230

dUpon a transition from authenticated into deauthenticated state, the Dcm shall dis-
card the current role, white list and use the configured deauthentication role from
DcmDspAuthenticationDeauthenticatedRoleRef.c

In some use cases, it is desirable that the application set the role instead of using
a diagnostic service with its potentially time-consuming certificate parsing. The Dcm
provides the API Dcm_SetDeauthenticatedRole to overwrite the configured deau-
thentication role. The overwritten role is only valid in deauthenticated state will not be
persisted and is overwritten by a role provided by certificates via service 0x29.

[SWS_Dcm_01486] Default authentication role set from SWC

Upstream requirements: RS_Diag_04230

dIf a connection is in deauthenticated state and the API Dcm_SetDeauthenticate-

dRole is called, the Dcm shall use the provided deauthenticatedRole as new role per
deauthenticated state for this connection.c

70 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01487] Setting deauthenticated role by SWC only in deauthenticated

state
Upstream requirements: RS_Diag_04230

dThe Dcm shall process a call of Dcm_SetDeauthenticatedRole only if the con-

nection is in deauthenticated state.c

[SWS_Dcm_01488] Lifetime of deauthenticated role by SWC

Upstream requirements: RS_Diag_04230

dA deauthenticated role set by Dcm_SetDeauthenticatedRole is discarded when

that connection performs a transition to authenticated state.c

[SWS_Dcm_01489] No persistency for deauthenticated roles by SWC

Upstream requirements: RS_Diag_04230

dIf the authentication state is not persisted, at startup the Dcm shall always be in the
deauthenticated state and use the default role configured in DcmDspAuthentica-
tionDeauthenticatedRoleRef.c

7.2.4.13 Non-default sessions

The Dcm supports the ISO14229-1 [1] defined sessions. There are two kind of ses-
sions, the default session and the non-default sessions. In a non-default session the
S3 timer is used to detect inactive testers and if the timer elapses the default session
is entered.

[SWS_Dcm_01668] S3Server session timer support

Upstream requirements: RS_Diag_04249

dThe Dcm shall support the S3Server and start and stop this timer according to
ISO14229-2 [3].c

[SWS_Dcm_01669] Sessions and connections

Upstream requirements: RS_Diag_04249

dThe Dcm shall start or stop the S3Server according to ISO14229-2 [3] but only for the
client on the DcmDslConnection that requested the non-default session.c

[SWS_Dcm_01670] Change to default session upon S3Server elapses

Upstream requirements: RS_Diag_04249

dIf the S3Server elapses, the Dcm shall switch back to default session.c

71 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.2.4.14 Allow to modify timings

[SWS_Dcm_00027]
Upstream requirements: RS_Diag_04015, RS_Diag_04249

dThe Dcm module shall handle the following protocol timing parameters in compli-
ance with ISO14229-2 [3]: P2ServerMin, P2ServerMax, P2*ServerMin, P2*ServerMax,
S3Serverc

[SWS_Dcm_00143]
Upstream requirements: RS_Diag_04015, RS_Diag_04249

dP2min / P2*min shall be set to defined values: P2min = 0ms, P2*min = 0ms.c

[SWS_Dcm_01679] Default S3 timeout value

Upstream requirements: RS_Diag_04015, RS_Diag_04249

dIf the parameter DcmS3ServerTimeoutOverwrite is not configured, Dcm shall take

the value of 5000ms as the S3Server timeout.c

[SWS_Dcm_01680] Overwritten S3 timeout value dIf the parameter

DcmS3ServerTimeoutOverwrite is configured, the Dcm shall take the configured
value as the S3Server timeout.c

These protocol timing parameters have influence on the session layer timing (no influ-
ence on Transport Layer timing). Some of these timing parameters can be modified
while protocol is active with the following means:
• UDS Service DiagnosticSessionControl (0x10)
• UDS Service AccessTimingParameter (0x83)
The DSL submodule provides the following functionalities to modify the timing parame-
ters:
• Provide the active timing parameters,
• Set the new timing parameters. Activation of new timing values is only allowed
after sending the response.

7.2.4.14.1 Different service tables

For the different protocols a different set of allowed diagnostic services is valid (e.g.
the UDS commands for the enhanced diagnosis, the OBD mode services for the OBD
protocol). It is possible to create different service tables and link them to the diagnostic
protocol.

72 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00035]
Upstream requirements: SRS_BSW_00101

dWith every protocol initialization, the DSL submodule sets a link to the corresponding
service table (see configuration parameter DcmDslProtocolSIDTable).c

The DSD submodule uses this link for further processing of diagnostic requests.

7.2.4.14.2 Prioritization of protocol

The configuration parameter DcmDslProtocolPriority makes it possible to give

each protocol its own relative priority. Possible use case: There are ECUs, commu-
nicating with a vehicle-internal diagnostic tester (running on enhanced diagnosis) and
a vehicle-external OBD-II/WWH-OBD tester. The OBD-II/WWH-OBD communication
must have a higher priority than the enhanced diagnosis.

[SWS_Dcm_00015]
Upstream requirements: RS_Diag_04021

dA protocol with higher priority is allowed to preempt the already running protocol.c

Differentiation of diagnostic protocols is possible, because of different DcmDslProto-

colRxPduId values (configured per protocol, see configuration parameter DcmDsl-
ProtocolRxPduRef) referenced in the protocol configuration.

7.2.4.14.3 Preemption of protocol

[SWS_Dcm_00079]
Upstream requirements: RS_Diag_04021

dIf a protocol is preempted and this protocol has a running pending response trans-
mission, the Dcm shall call PduR_DcmCancelTransmit () for this transmission with the
following parameters: PduId: the id of the Pdu to be canceledc

[SWS_Dcm_00460]
Upstream requirements: RS_Diag_04021

dWhen PduR_DcmCancelTransmit() returns E_NOT_OK, the Dcm module shall stop

the current protocol.c

73 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01046]
Upstream requirements: RS_Diag_04021

dIf a running diagnostic request is preempted by a higher priority request, the Dcm shall
cancel all external pending operations on the preempted protocol with Dcm_OpStatus
set to DCM_CANCEL.c

[SWS_Dcm_01047] dIn case an operation to the Dem is pending and the new request
also requires an interaction with the Dem, the Dcm shall accept the new request and
call the corresponding Dem API with the parameters from the new request.c

[SWS_Dcm_00575]
Upstream requirements: RS_Diag_04021

dIf the Dcm is preempting a protocol with a pending reception, the Dcm module shall
call cancel that reception with PduR_DcmCancelReceive().c

[SWS_Dcm_00576]
Upstream requirements: RS_Diag_04021

dIf PduR_DcmCancelReceive () returns E_NOT_OK, the Dcm shall stop the current
protocol.c

[SWS_Dcm_00727]
Upstream requirements: RS_Diag_04021

dIf a diagnostic request cannot be processed due to a higher priority protocol and
DcmDslDiagRespOnSecondDeclinedRequest is set to True, the Dcm shall send
NRC 0x21 (BusyRepeatRequest) for the not processed request.c

[SWS_Dcm_01605]
Upstream requirements: RS_Diag_04021

dIf a diagnostic cannot be processed due to a higher priority protocol and DcmDslDia-
gRespOnSecondDeclinedRequest is set to False, the Dcm shall ignore the request.
In this case no response message at all is generated.c

[SWS_Dcm_00729] dIn case of multiple clients with different PduIDs which are re-
questing the same protocol, as all the connections of the same protocol are having the
same priority, a second request (with the different RxPduId) will not be processed. If the
configuration parameter DcmDslDiagRespOnSecondDeclinedRequest is TRUE, a
negative response with NRC 0x21 (BusyRepeatRequest) shall be issued for the second
request. If the configuration parameter is FALSE, no response shall be issued.c

Note:

74 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• A multitude of RxPduIDs may be configured per DcmDslProtocol

• These RxPduIDs may be themselves connected to different Testers via the PduR
configuration
• This means that many Testers may be configured for the same Protocol
• And this represents a non-UDS extension/use case. In order to have a UDS-
compliant flow, there should be one DcmDslProtocol instance per Tester.

[SWS_Dcm_01050] dIn case of diagnostic parallel requests, with same / lower pri-
ority than the active request then the ComM APIs (ComM_DCM_ActiveDiagnostic,
ComM_DCM_InactiveDiagnostic) shall not be called.c

7.2.4.14.4 Parallel diagnostic protocol processing

Multiple testers are a common scenario in today’s vehicles. In order to reduce the in-
terference between concurrent tester requests to a minimum the Dcm supports parallel
diagnostic service processing. This behavior is according to recommended practice
of ISO 14229-1 Appendix J. There are certain restrictions, that in non-default session
only diagnostic communication from one tester is allowed. In default session and for
OBD-II communication it is possible to process diagnostic requests in parallel. Parallel
OBD and UDS communication is particularly important if vehicles are equipped with
so called ’OBD dongles’ or with electronical logging devices. These devices are in-
stalled by the vehicle owner and do diagnostic communication over standardized OBD
services. The presence of such devices shall interfere as little as possible with vehi-
cle internal UDS communication. Therefore, whenever it is possible, the Dcm supports
parallel processing.

[SWS_Dcm_01602] Processing of parallel requests in default session

Upstream requirements: RS_Diag_04021

dIf the Dcm receives a request and no further protocol with a higher priority is currently
in a non-default session, the Dcm shall accept the new incoming request and process
it.c

[SWS_Dcm_01603] No parallel processing in non-default session

Upstream requirements: RS_Diag_04021

dIf the Dcm receives a request and a further protocol with a higher priority is currently
in a non-default session, the Dcm shall decline the new received request according to
[SWS_Dcm_00727].c

Some Dcm interfaces provide access to different diagnostic services, e.g. interface
RoutineService for subfunctions Start, Stop and Request Result of a RoutineControl

75 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

(0x31) or the interface DataServices for the Read and Write operations. On these
interfaces only a single client shall access to the data at any point in time.

[SWS_Dcm_01604] Delay parallel processing on the same application interface

change
Upstream requirements: RS_Diag_04021

dIf the Dcm receives a request and the service processing of this request requires a
call to the same application interface that is currently processing another request, the
Dcm shall delay the call to the interface until the running operation on that application
interface has finished.c

If the Dcm delays the service processing due to [SWS_Dcm_01604] the standard timing
behavior with P2 and NRC 0x78 apply. From an outside perspective, the delayed call
to the application looks like that the application itself is taking more time for execution.

[SWS_Dcm_01367]
Upstream requirements: RS_Diag_04163

dThe Dcm shall process incoming OBD-II requests in parallel to a running UDS request.
In this case the protocol priority check according to [SWS_Dcm_00015] is skipped and
no protocol pre-emption is done.c

With the container DcmDslProtocolRow, the Dcm configuration supports multiple pro-
tocols. Each protocol has a configured DcmDemClientRef defining the Dem client in-
teracting with the Dem. This client Id allows the Dem to distinguish between concurrent
calls of the Dcm of the same function or set of functions to process a certain request.

[SWS_Dcm_01369]
Upstream requirements: RS_Diag_04162

dWhile processing a diagnostic request received from a given protocol, the Dcm shall
determine the DcmDemClientRef of the DcmDslProtocolRow of the processed pro-
tocol. The Dcm shall use this value in all Dem API calls that have a ClientId as parame-
ter.c

[SWS_Dcm_01370] Serialization of multiple calls to the same interface

Upstream requirements: RS_Diag_04162

dThe Dcm shall internally serialize all asynchronous C/S interface or C function calls
to the same port interface or C function during parallel diagnostic services processing
and return a pending to the re-entrant caller.c

76 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01371]
Upstream requirements: RS_Diag_04162

dIf the Dcm receives a request on a higher priority protocol than the currently processed
request and a diagnostic service in a non-default session is currently processed, the
Dcm shall cancel the running diagnostic request, make a transition into default session
and process the new received request.c

Integrators will assign OBD protocols the highest priority to meet the legislated response
and timing requirements. Therefore, all definitions of ’higher priority protocols’ apply to
the use case where OBD is used.

[SWS_Dcm_01372]
Upstream requirements: RS_Diag_04162

dIf the Dcm processes a request from a high priority protocol in default session and
the Dcm is receiving a diagnostic request to change in a non-default session, the Dcm
shall delay the session change request until the high priority protocol service is finished
according to [SWS_Dcm_01371] and make a transition into the requested non-default
session.c

[SWS_Dcm_CONSTR_06102] Limitation to one single OBD protocol dThe Dcm shall

support only one DcmDslProtocolRow with a configured DcmDslProtocolType set
to DCM_OBD_ON_<XYZ>.c

[SWS_Dcm_CONSTR_06103] OBD procotol shall have highest priority dThe

Dcm shall support a DcmDslProtocolRow with DcmDslProtocolType set to
DCM_OBD_ON_<XYZ> as the highest priority.c

[SWS_Dcm_CONSTR_06000] Harmonize the naming between interfaces

and modes dThe shortname of DcmDspSessionRow shall match names of
Dcm_SesCtrlType and of the mode declarations of DcmDiagnosticSessionControl. The
"DCM_" prefix is mandatory for all shortnames.c

[SWS_Dcm_CONSTR_06001] Provide standardized names for ISO standardized

diagnostic sessions dThe following values of DcmDspSessionLevel which repre-
sent ISO defined diagnostic sessions shall be used for the shortname of DcmDspSes-
sionRow:
1 DCM_DEFAULT_SESSION
2 DCM_PROGRAMMING_SESSION
3 DCM_EXTENDED_DIAGNOSTIC_SESSION
4 DCM_SAFETY_SYSTEM_DIAGNOSTIC_SESSION
c

77 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.2.4.15 Manage resources

Due to limited resources, the following points should be considered as hints for the
design:
• It is allowed to use and allocate only one diagnostic buffer in the Dcm module.
This buffer is then used for processing the diagnostic requests and responses.
• Output of NRC 0x78 (Response pending) responses is done with a separate
buffer.
• paged-buffer handling (see [SWS_Dcm_00028]).

7.2.4.16 Communication Mode Handling

Communication Mode Handling is an interface between Dcm and ComM. The ComM
informs the Dcm about the current communication state of a channel. The Dcm is calling
the ComM about active Diagnostic which shall prevent an Ecu shutdown/sleep.
The status ActiveDiagnostic shows if diagnostic requests shall keep the ECU awake
(ActiveDiagnostic ==’DCM_COMM_ACTIVE’) or if diagnostic requests shall not pre-
vent an Ecu shutdown/sleep (ActiveDiagnostic ==’DCM_COMM_NOT_ACTIVE’). Ap-
plication can change the status ActiveDiagnostic regarding to system conditions.

[SWS_Dcm_CONSTR_06027] dThe application will inform the Dcm by calling

Xxx_SetActiveDiagnostic() about the ActiveDiagnostic status.c

[SWS_Dcm_01069] dAfter Dcm_Init, the Dcm shall set ActiveDiagnostic to

’DCM_COMM_ACTIVE’.c

[SWS_Dcm_01070] dIf Xxx_SetActiveDiagnostic() is called with ’false’ the Dcm set

ActiveDiagnostic to ’DCM_COMM_NOT_ACTIVE’.c

[SWS_Dcm_01071] dIf Xxx_SetActiveDiagnostic() is called with ’true’ the Dcm set Ac-
tiveDiagnostic to ’DCM_COMM_ACTIVE’.c

[SWS_Dcm_01142] dThe Dcm shall wait the Full Communication mode indication from
the ComM (call to Dcm_ComM_FullComModeEntered) before initiating the trans-
mission of the diagnostic answer. The time to wait should be no longer than the
P2ServerMax calculated from the moment the request was received.c

[SWS_Dcm_01143] dIf the Dcm fails to confirm a response pending transmission

(DCM_E_FORCE_RCRRP) due to [SWS_Dcm_01142], the Dcm shall trigger the Det
error DCM_E_FORCE_RCRRP_IN_SILENT_COMM.c

78 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Note : On the reception side a silent communication mode can lead to the lost of the
request in case of segmented transmission.

7.2.4.16.1 No Communication

The ComM module will indicate the No Communication Mode to the Dcm module by
calling Dcm_ComM_NoComModeEntered. In response, the Dcm will immediately dis-
able all transmissions (see the definition of Dcm_ComM_NoComModeEntered for de-
tails).

[SWS_Dcm_00148] dDcm_ComM_NoComModeEntered shall disable all kinds of trans-

missions (receive and transmit) of communication. This means that the message re-
ception and also the message transmission shall be off.c

[SWS_Dcm_00149] dDcm_ComM_NoComModeEntered shall disable the Respon-

seOnEvent transmissions.c

[SWS_Dcm_00150] dDcm_ComM_NoComModeEntered shall disable the periodicId

transmissions (ReadDataByPeriodicIdentifier).c

[SWS_Dcm_00151] dDcm_ComM_NoComModeEntered shall disable normal trans-

missions.c

[SWS_Dcm_00152] dAfter Dcm_ComM_NoComModeEntered has been called, the

Dcm module shall not call the function PduR_DcmTransmit().c

[SWS_Dcm_01324] dIn case Dcm_ComM_NoComModeEntered is called with a Net-

workId for a ComM channel not referenced within the Dcm (see configuration parame-
ter DcmDslProtocolComMChannelRef), the Dcm shall return without performing any
further action.c

7.2.4.16.2 Silent Communication

The ComM module will indicate the Silent Communication Mode to the Dcm module by
calling Dcm_ComM_SilentComModeEntered. In response, the Dcm will immediately
disable all transmissions (see the definition of Dcm_ComM_SilentComModeEntered
for details).

[SWS_Dcm_00153] dDcm_ComM_SilentComModeEntered shall disable all trans-

mission. This means that the message transmission shall be off.c

79 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00154] dDcm_ComM_SilentComModeEntered shall disable the Re-

sponseOnEvent transmissions.c

[SWS_Dcm_00155] dDcm_ComM_SilentComModeEntered shall disable the period-

icId transmissions (ReadDataByPeriodicIdentifier) shall be disabled.c

[SWS_Dcm_00156] dDcm_ComM_SilentComModeEntered shall disable the normal

transmissions.c

[SWS_Dcm_01325] dIn case Dcm_ComM_SilentComModeEntered is called with a

NetworkId for a ComM channel not referenced within the Dcm (see configuration pa-
rameter DcmDslProtocolComMChannelRef), the Dcm shall return without perform-
ing any further action.c

7.2.4.16.3 Full Communication

The ComM module will indicate the Full Communication Mode to the Dcm module by
calling Dcm_ComM_FullComModeEntered. In response, the Dcm will enable all trans-
missions (see the definition of Dcm_ComM_FullComModeEntered for details).

[SWS_Dcm_00157] dDcm_ComM_FullComModeEntered shall enable all kind of

communication. This means that the message reception and also the message trans-
mission shall be on.c

[SWS_Dcm_00159] dDcm_ComM_FullComModeEntered shall enable the Respon-

seOnEvent transmissions.c

[SWS_Dcm_00160] dDcm_ComM_FullComModeEntered shall enable the periodicId

transmissions (ReadDataByPeriodicIdentifier).c

[SWS_Dcm_00161] dDcm_ComM_FullComModeEntered shall enable the normal

transmissions.c

[SWS_Dcm_00162] dAfter Dcm_ComM_FullComModeEntered has been called, the

Dcm shall handle the functions DslInternal_ResponseOnOneDataByPeriodicId() or
DslInternal_ResponseOnOneEvent() without restrictions.c

[SWS_Dcm_01326] dIn case Dcm_ComM_FullComModeEntered is called with a Net-

workId for a ComM channel not referenced within the Dcm (see configuration parame-
ter DcmDslProtocolComMChannelRef), the Dcm shall return without performing any
further action.c

80 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.2.4.16.4 Diagnostic Activation State

The Dcm notifies the ComM module about the internal diagnostic state for all networks.
There are two options for the diagnostic state on a network. In ’active’ diagnostic state,
the Dcm is processing one or more diagnostic requests from this network or the Dcm is
in a non-default session. In ’inactive’ diagnostic state, the Dcm is in default session and
is not processing a diagnostic request on that network.
When a network has no communication in progress, the Dcm will set the diagnostic ac-
tivation state to ’inactive’. When there is a diagnostic communication on a network the
Dcm sets the diagnostic state to ’active’. In any non-default session, the diagnostic state
remains in state ’active’. The communication state can also be controlled by the API
Xxx_SetActiveDiagnostic according to [SWS_Dcm_01070] and [SWS_Dcm_01071].

[SWS_Dcm_01373]
Upstream requirements: RS_Diag_04006

dThe Dcm shall go into ’active’ diagnostic state on a network, if a diagnostic request
is received on a network or the diagnostic session is changed to any non-default ses-
sion.c

[SWS_Dcm_01374]
Upstream requirements: RS_Diag_04006

dThe Dcm shall go into ’inactive’ diagnostic state on a network when the current di-
agnostic request processing is finished and the Dcm is not processing a diagnostic
request of another protocol on this network and if the Dcm is in default session.c

[SWS_Dcm_01375]
Upstream requirements: RS_Diag_04006

dThe Dcm shall go into ’inactive’ diagnostic state on all networks if a S3Server timeout
occurs and the Dcm makes a transition into default session.c

[SWS_Dcm_01376]
Upstream requirements: RS_Diag_04006

dIf ActiveDiagnostic is ’DCM_COMM_ACTIVE’ and the Dcm is doing a transi-

tion into ’active’ diagnostic state of a diagnostic protocol, the Dcm shall call
ComM_DCM_ActiveDiagnostic(NetworkId), with the networkId associated to the re-
ceived Pdu (see DcmDslProtocolComMChannelRef), with every request, to inform
the ComM module about the need to stay in Full Communication Mode.c

81 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01377]
Upstream requirements: RS_Diag_04006

dUpon a diagnostic state transition into ’inactive’, the Dcm shall notify the
ComM module about an inactive diagnostic state on a network by calling
ComM_DCM_InactiveDiagnostic(NetworkId), with the networkId associated to the re-
ceived Pdu (see DcmDslProtocolComMChannelRef).c

[SWS_Dcm_01378]
Upstream requirements: RS_Diag_04006

dThe definition of a finished diagnostic request according to [SWS_Dcm_01374], shall

be as follows:
• the Dcm has sent a positive or negative response unequal to NRC 0x78 by re-
ceiving the Dcm_TpTxConfirmation connected to the response given by the
DSL submodule
• the Dcm has processed the service with SPRMIB=true and the positive response
was suppressed
• in case of functional addressing, the Dcm has processed the service and the
negative response was suppressed.
c

7.3 Diagnostic Service Dispatcher (DSD)

7.3.1 Introduction

The DSD submodule is responsible to check the validity of an incoming diagnostic re-
quest (Verification of Diagnostic Session/Security Access levels/Application permis-
sion) and keeps track of the progress of a service request execution.

[SWS_Dcm_00178] dThe DSD submodule shall only process valid requests and shall
reject invalid ones.c

7.3.2 Use cases

The following use cases are relevant and are described in detail in the following:
• Receive a request message and transmit a positive response message
• Receive a request message and suppress a positive response

82 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• Receive a request message and suppress a negative response

• Receive a request message and transmit a negative response message
• Send a positive response message without corresponding request
• Segmented Responses

7.3.2.1 Receive a request message and transmit a positive response message

This is the standard use case of normal communication ("ping-pong"). The server
receives a diagnostic request message. The DSD submodule ensures the validity of
the request message. In this use case, the request is valid and the response will be
positive. The request will be forwarded to the appropriate data processor in the DSP
submodule. When the data processor has finished all actions of data processing, it
triggers the transmission of the response message by the DSD submodule.
If the data processor processes the service immediately as part of the request indica-
tion function, the data processor can trigger the transmission inside this indication func-
tion ("synchronous"). If the processing takes a longer time (e. g. waiting on EEPROM
driver), the data processor defers some processing ("asynchronous"). The response
pending mechanism is covered by the DSL submodule. The data processor triggers
the transmission explicitly, but from within the data processor’s context.
As soon as a request message is received, the corresponding DcmPduId is blocked by
the DSL submodule (see [SWS_Dcm_00241]). During the processing of this request,
no other request of the same protocol type (e.g. an enhanced session can be ended
by a OBD session) can be received, until the corresponding response message is sent
and the DcmPduId is released again.

7.3.2.2 Receive a request message and suppress a positive response

This is a sub-use-case of the previous one. Within the UDS protocol it is possible
to suppress the positive response by setting a special bit in the request message
(see [SWS_Dcm_00200]). This special suppression handling is completely performed
within the DSD submodule.

7.3.2.3 Receive a request message and suppress a negative response

In case of functional addressing the DSD submodule shall suppress the negative re-
sponse for NRC 0x11, 0x12, 0x31, 0x7E and 0x7F (see [SWS_Dcm_00001]).

83 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.3.2.4 Receive a request message and transmit a negative response message

There are a many different reasons why a request message is rejected and a negative
response is to be sent. If a diagnostic request is not valid or if a request may not be
executed in the current session, the DSD submodule will reject the processing and a
negative response will be returned.
But there are even many reasons to reject the execution of a well-formed request mes-
sage, e.g. if the ECU or system state does not allow the execution. In this case, the
DSP submodule will trigger a negative response including an NRC supplying additional
information why this request was rejected.
In case of a request composed of several parameters (e.g. a UDS Service Read-
DataByIdentifier (0x22) request with more than one identifier to read), each parameter
is treated separately. And each of these parameters can return an error. This kind of
request returns a positive response if at least one of the parameters was processed
successfully.

[SWS_Dcm_00827] dThe DSD sub-module shall check the received diagnostic request
in the order given by ISO14229-1 [1]. If one of the computations failed the Dcm shall
stop the execution of the NRC check sequence then stop or do not start the execution of
the received diagnostic request and finally transmit the NRC for which the computation
failed.c

7.3.2.5 Send a positive response message without corresponding request

There are two services within the UDS protocol, where multiple responses are sent for
only one request. In general, one service is used to enable (and disable) an event- or
time-triggered transmission of another service, which again is sent by the ECU without
a corresponding request (see ISO14229-1 [1]). These services are:
• UDS Service ReadDataByPeriodicIdentifier (0x2A). This service allows the client
to request the periodic transmission of data record values from the server identi-
fied by one or more periodicDataIdentifiers.
Type 2 = UUDT message on a separate DcmTxPduId.
• ResponseOnEvent (0x86). This service requests a server to start or stop trans-
mission of responses on a specified event.
Type 1 = USDT messages on the DcmTxPduId already used for normal diagnos-
tic responses,
Type 2 = USDT messages on separate DcmTxPduId.
For Type 1, the outgoing messages must be synchronized with "normal outgoing
messages", which have a higher priority.

84 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

This handling is especially controlled by the DSL submodule. However, the DSD sub-
module also provides the possibility to generate a response without a corresponding
request.

7.3.2.6 Segmented Responses (paged-buffer)

Within the diagnostic protocol, some services allow to exchange a significant amount
of data, e.g. UDS Service ReadDTCInformation (0x19) and UDS Service TransferData
(0x36).
In the conventional approach, the ECU internal buffer must be large enough to keep
the longest data message which is to be exchanged (worst-case) and the complete
buffer is filled before the transmission is started.
RAM memory in an ECU often is a critical resource, especially in smaller micros. In
a more memory-saving approach, the buffer is filled only partly, transmitted partly and
then refilled partly - and so on. This paging mechanism requires only a significantly re-
duced amount of memory, but demands a well-defined reaction time for buffer refilling.
The user can decide whether to use the "linear buffer" or paged-buffer for diagnostics.

7.3.3 Interaction of the DSD with other modules

The DSD submodule is called by the DSL submodule when receiving a diagnostic mes-
sage and performs the following operations:
• delegates processing of request to the DSP submodule or external modules out-
side the Dcm
• keeps track of request processing (Return the status on <Module>_<Diagnos-
ticService>() and <Module>_<DiagnosticService>_<SubService>() APIs call or
"Service Interpreter calls")
• transmits the response of the Application to the DSL submodule (Transmit func-
tionality)

7.3.3.1 Interaction of the DSD with the DSL main functionality

Direction Explanation
Bidirectional Exchange of the Diagnostic Messages (receive/transmit).
DSD submodule to DSL Obtain latest diagnostic session and latest security level.
submodule
DSL submodule to DSD Confirmation of transmission of Diagnostic Message.
submodule

Table 7.1: Interaction between the DSD submodule and the DSL submodule

85 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.3.3.2 Interaction of the DSD with the DSP

Direction Explanation
DSD submodule to DSP - Delegate processing of request.
submodule - Confirmation of transmission of Diagnostic Message.
DSP submodule to DSD - Signal that processing is finished.
submodule

Table 7.2: Interaction of the DSD with the DSP

7.3.4 Functional Description of the DSD

7.3.4.1 Support checking the diagnostic service identifier and adapting the di-
agnostic message

The DSD submodule shall be triggered by the DSL submodule if a new diagnostic mes-
sage is recognized. The DSD submodule will start processing by analyzing the diag-
nostic service identifier contained in the received diagnostic message.

[SWS_Dcm_00084] dIf configured (configuration parameter DcmRespondAllRe-

quest=FALSE), if the Dcm module receives a diagnostic request that contains a ser-
vice ID that is in the range from 0x40 to 0x7F or in the range from 0xC0 to 0xFF, the
Dcm shall not respond to such a request.c

This range corresponds to the diagnostic response identifier.

[SWS_Dcm_00192] dThe DSD submodule shall analyze the (incoming) diagnostic

message for the diagnostic service identifier (based on first byte of the diagnostic
message) and shall check the supported services with the newly received diagnos-
tic service identifier.c

[SWS_Dcm_00193] dDuring this check, the DSD submodule shall search the newly
received diagnostic service identifier in the "Service Identifier Table".c

For performance reasons it might be necessary that the support check is done with a
"lookup table" functionality. In this "Service Identifier Table" all supported Service IDs
of the ECU are predefined.

[SWS_Dcm_00195] dThe DSL submodule shall provide the current "Service Identifier
Table"c

Rationale for [SWS_Dcm_00195]: The "Service Identifier Table" and the information
about the supported services will be generated out of the configuration. More than one

86 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Service Identifier Table can be configured for selection. At one time only one Service
Identifier Table can be active.

[SWS_Dcm_00196] dFor the check, the DSD submodule shall scan the active "Ser-
vice Identifier Table" for a newly received diagnostic service identifier. If this service
identifier is supported and if the configuration parameter DcmDsdSidTabFnc (see
ECUC_Dcm_00777) is not empty, the DSD submodule shall call the configured service
interface (<Module>_<DiagnosticService>). If the configuration parameter is empty,
the Dcm shall call the internally implemented service interface.c

The diagnostic service identifier is not supported when it is not included in the "Service
Identifier Table".

[SWS_Dcm_00197] dIf the newly received diagnostic service identifier is not sup-
ported, the DSD submodule shall transmit a negative response with NRC 0x11 (Service
not supported) to the DSL submodule.c

[SWS_Dcm_00198] dThe DSD submodule shall store the newly received diagnostic
service identifier for later use.c

For example: WriteDataByIdentifier (for writing VIN number):

1. A new diagnostic message is received by the DSL submodule. (Diagnostic Mes-
sage WriteDataByIdentifier = 0x2E, 0xF1, 0x90, 0x57, 0x30, 0x4C, 0x30, 0x30,
0x30, 0x30, 0x34, 0x33, 0x4D, 0x42, 0x35, 0x34, 0x31, 0x33, 0x32, 0x36)
2. The DSL submodule indicates a new diagnostic message with the "Data Indica-
tion" functionality to the DSD submodule. In the diagnostic message buffer the
diagnostic message is stored (buffer = 0x2E,0xF1,0x90,..).
3. The DSD submodule executes a check of the supported services with the de-
termined service identifier (first byte of buffer 0x2E) on the incoming diagnostic
message.
4. The incoming diagnostic message is stored in the Dcm variable
Dcm_MsgContextType.

[SWS_Dcm_CONSTR_06047] dId of the Service identifier configured in DcmDsd-

SidTabServiceId shall be unique within one DcmDsdServiceTable.c

[SWS_Dcm_00732] dFor the first call of <Module>_<DiagnosticService> the opStatus

shall be set to DCM_INITIAL.c

87 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00733] dThe Dcm shall not accept further requests (on same or lower
priority) while <Module>_<DiagnosticService>() returns DCM_E_PENDING. Dcm-
internal timeout handling (based on RCR-RP limitation) may lead to a cancellation
of the external diagnostic service processing.c

[SWS_Dcm_00735] dIn case of cancellation the API <Module>_<DiagnosticService>

is called again with the parameter opStatus set to DCM_CANCEL.c

7.3.4.2 Handling of "suppressPosRspMsgIndicationBit"

The "suppressPosRspMsgIndicationBit" is part of the subfunction parameter structure

(Bit 7 based on second byte of the diagnostic message, see ISO14229-1 [1] Section
6.5: Server response implementation rules).

[SWS_Dcm_00200]
Upstream requirements: RS_Diag_04020

dIf the "suppressPosRspMsgIndicationBit" is TRUE, the DSD submodule shall NOT

send a positive response message.c

[SWS_Dcm_00201] dThe DSD submodule shall remove the "suppressPosRspMsgIndi-

cationBit" (by masking the Bit) from the diagnostic message.c

[SWS_Dcm_00202] dThe Dcm module shall transport the information on a suppres-

sion of a positive response being active (between the layers) via the parameter
Dcm_MsgContextType.c

[SWS_Dcm_00203] dIn case of responsePending the Dcm module shall clear the "sup-
pressPosRspMsgIndicationBit."c

Rationale for [SWS_Dcm_00203]: In the described case the final response (negative/-
positive) is required.

[SWS_Dcm_00204] dThe Dcm module shall only perform the "suppressPosRspMs-

gIndicationBit" handling when the configuration parameter DcmDsdSidTabSubfun-
cAvail is set for the newly received service identifierc

Note: The "suppressPosRspMsgIndicationBit" handling needs to be considered inde-

pendent of the processing order in the request (like for RoutineControl service).
Rationale for [SWS_Dcm_00204]: The "suppressPosRspMsgIndicationBit" is only
available if a service has a subfunction.

88 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.3.4.3 Verification functionality

Prior of execution of a received diagnostic service, the DSD performs a set of verifica-
tions. The DSD will only accept a service, if all verifications are successfully passed.

[SWS_Dcm_01535] DSD verifications prior of service execution

Upstream requirements: RS_Diag_04230, RS_Diag_04005, RS_Diag_04006

dThe Dcm shall only accept a diagnostic request, if the following verifications have
been passed in the following order:c

1. Verification of Manufacturer permission (Call of the manufacturer interface indi-

cation operation)
2. Verification of the SID
3. Verification of the service access control on the current authentication state
4. Verification of the Diagnostic Session
5. Verification of the Service Security Access levels
6. Verification of the Supplier permission (Call of the Supplier interface indication
operation)
7. Verification of the Mode rules for service IDs.

[SWS_Dcm_01474]
Upstream requirements: RS_Diag_04235

dIn case the DSD generates a NRC, the Dcm shall only call XXX_Confirmation.c

This means that the Dcm will not call DspInternal_DcmConfirmation().

7.3.4.3.1 Verification of the diagnostic service access rights

The UDS service Authentication (0x29) is used to change the authentication state of a
diagnostic connection and to provide the access rights. Depending on the reached role
and provided white list a dynamic set of diagnostic services is available for the tester
on that connection. The DSD submodule verifies on service ID (SID) and sub-function
(SF) level, if a service can be executed or not.

[SWS_Dcm_01536] Authentication on UDS services only

Upstream requirements: RS_Diag_04230

dThe Dcm shall only verify the authentication for UDS services. A UDS service has a
service ID within the range of 0x10 and 0xFF.c

89 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

OBD services are explicitly excluded from authentication checks. By legislation the
OBD services need to be always available, independent from active authentication
state. If WWH-OBD is used the system engineer must ensure that these services are
always accessible.

[SWS_Dcm_01537] Verifying access rights

Upstream requirements: RS_Diag_04230

dThe Dcm shall only verify and check the configured access rights of a diagnostic
service, if the container DcmDspAuthentication is configured.c

If no DcmDspAuthentication is configured, the Dcm will process all diagnostic services

as if the current connection would grant access to execute the current processed ser-
vice. Checking the access rights for diagnostic services is done at different levels of
the service structure. The use of diagnostic service access rights introduces means to
allow or to refuse a diagnostic service due to current roles and authentication states.
Some services shall always be allowed to be executed, like the service 0x29 (Authen-
tication) to set the current tester access rights. This service and other OEM or sup-
plier specific services should have granted access independent from the authentication
state. To realize this, the Dcm uses a default role that is used in all deauthenticated
states. In that state, all role based verifications are done as in authenticated state. The
active role is provided by the configuration.

[SWS_Dcm_01538] Access rights for services in deauthenticated state

Upstream requirements: RS_Diag_04230

dIf the current connection is in deauthenticated state, the Dcm shall use the role con-
figured by DcmDspAuthenticationDeauthenticatedRoleRef as current role for
all role based access verification checks.c

[SWS_Dcm_01539] Definition of allowed service execution

Upstream requirements: RS_Diag_04233

dThe Dcm shall allow the service execution, if a role verification was successful or the
service is allowed by the white list.c

[SWS_Dcm_01540] Diagnostic service execution rights verification

Upstream requirements: RS_Diag_04233

dThe Dcm shall check if a service execution is permitted in the current authentication
check or not. The Dcm shall perform the following checks in the given order below. If
a check grants access to a service, the remaining checks are skipped:
1. Checks on service ID level
2. Checks on service ID and sub-function level

90 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

3. Checks for services with one or multiple DIDs

4. Check on dynamically defined DIDs
5. Checks on service 0x31 per sub-function
6. Checks on service 0x19 parameter MemorySelection
7. Checks on service 0x14 parameter MemorySelection
c

[SWS_Dcm_01541] Service ID authentication check for UDS service requests

Upstream requirements: RS_Diag_04233

dUpon processing a diagnostic service, the Dcm shall grant access to the diagnostic
service if:
1. for that service a service role is configured via DcmDsdServiceRoleRef and
the verification according to [SWS_Dcm_01522] was successful or
2. the active white list on that connection has one entry for a SID (1-byte element)
which matches that service.
c

[SWS_Dcm_01542] Service with sub-function authentication check for UDS ser-

vice requests
Upstream requirements: RS_Diag_04230

dUpon processing a diagnostic service with sub-function, the Dcm shall grant access
to the diagnostic service if:
1. for that service and subfunction a subservice service role is config-
ured via DcmDsdSubServiceRoleRef and the verification according to
[SWS_Dcm_01522] was successful or
2. the active white list on that connection has one entry for a SID with sub-function
(2-byte element) that matches that service and sub-function.
c

[SWS_Dcm_01562] White list verification for services with 3 and 4 bytes

Upstream requirements: RS_Diag_04233

dFor 3 and 4 bytes white list for services entries, the Dcm shall verify on the full length
of the configured white list service element. The service is granted access if the first
bytes of the received request match the entire white list entry.c

91 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Verification of byte 3 and 4 within the Dsd is beyond the scope of a typical Dsd opera-
tion. It provides means to extend the capabilities of white list service verifications and
gives means to adapt to legacy authentication solutions.

[SWS_Dcm_01544] Response behavior of services without access rights

Upstream requirements: RS_Diag_04230

dIf the service execution verification fails due to a failed check in scope of
[SWS_Dcm_01540], the Dcm shall send a NRC 0x34 authenticationRequired and stop
the service processing.c

7.3.4.3.2 Verification of the Diagnostic Session

The UDS Service DiagnosticSessionControl (0x10) is used to enable different diagnos-

tic sessions in the ECU (e.g. Default session, Extended session). A diagnostic session
enables a specific set of diagnostic services and/or functionality in the ECU. It further-
more enables a protocol-depending data set of timing parameters applicable to the
started session.
On receiving a service request, the DSD module will obtain the current Diagnostic
Session with Dcm_GetSesCtrlType and will verify whether the execution of the re-
quested service (NOT the UDS Service DiagnosticSessionControl (0x10)) and sub-
service is allowed in the current diagnostic session or not.
Note that the handling of the UDS Service DiagnosticSessionControl (0x10) itself is not
part of the DSD submodule.

[SWS_Dcm_00211] dIf the newly received diagnostic service is not allowed in the cur-
rent Diagnostic Session (according to the configuration parameter DcmDsdSidTab-
SessionLevelRef), the DSD submodule shall transmit a negative response with NRC
0x7F (serviceNotSupportedInActiveSession) to the DSL submodule.c

[SWS_Dcm_00616] dIf the newly received diagnostic service is allowed in the current
Diagnostic Session ( see [SWS_Dcm_00211]), but the requested subservice is not
allowed in the current Diagnostic Session (according to the configuration parameter
DcmDsdSubServiceSessionLevelRef), the DSD submodule shall transmit a neg-
ative response with NRC 0x7E (subFunctionNotSupportedInActiveSession) to the DSL
submodule.c

92 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.3.4.3.3 Verification of the Service Security Access levels

The purpose of the Security Access level handling is to provide a possibility to access
data and/or diagnostic services, which have restricted access for security, emissions, or
safety reasons. The DSD submodule shall perform this handling with the UDS Service
SecurityAccess (0x27). The DSD submodule will perform a verification whether the
execution of the requested service (NOT the UDS Service SecurityAccess (0x27)) is
allowed in the current Security level by asking for the current security level, using the
DSL function Dcm_GetSecurityLevel.
The management of the security level is not part of the DSD submodule.
Note: For some use cases (e.g. UDS Service ReadDataByIdentifier (0x22), where
some DataIdentifier can be secure) it will be necessary for the Application to call also
the function Dcm_GetSecurityLevel.

[SWS_Dcm_00217] dIf the newly received diagnostic service is not allowed in the
current Security level (according to the configuration parameter DcmDsdSidTabSe-
curityLevelRef), the DSD submodule shall transmit a negative response with NRC
0x33 (Security access denied) to the DSL submodule.c

[SWS_Dcm_00617] dIf the newly received diagnostic service is allowed in the current
Security level ( see [SWS_Dcm_00217]), but the requested subservice is not allowed in
the current Security level (according to the configuration parameter DcmDsdSubSer-
viceSecurityLevelRef), the DSD submodule shall transmit a negative response
with NRC 0x33 (Security access denied) to the DSL submodule.c

7.3.4.3.4 Verification of the Service mode dependencies

[SWS_Dcm_00773] dIf the newly received diagnostic service is not allowed in the
current mode condition (according to the configuration parameter DcmDsdSidTab-
ModeRuleRef), the DSD submodule shall transmit the calculated negative response
of the referenced DcmModeRule to the DSL submodule.c

[SWS_Dcm_00774] dIf the newly received diagnostic service is allowed in the cur-
rent mode condition [SWS_Dcm_00773], but the requested subservice is not allowed
in the current mode condition (according to the configuration parameter DcmDsdSub-
ServiceModeRuleRef), the DSD submodule shall transmit the calculated negative
response of the referenced DcmModeRule to the DSL submodule.c

93 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.3.4.4 Check format and subfunction support

The DSD submodule checks whether a specific subfunction is supported before exe-
cuting the requested command.

[SWS_Dcm_00273] General sub-function supported NRC check dThe DSD shall

send the negative response NRC 0x12 (sub-functionNotSupported ), if for the pro-
cessed service no configured DcmDsdSubService exists with the DcmDsdSubSer-
viceId of the processed service. This NRC check shall not be done for UDS Service
0x31 (RoutineControl).c

The DSD submodule will check for the minimum message length before executing the
requested command.

[SWS_Dcm_00696] dThe DSD submodule shall trigger a negative response with NRC
0x13 (Incorrect message length or invalid format), if the length of the request is inferior
to the minimum length of the request.c

[SWS_Dcm_01411] dIf DcmDsdSubService is configured for a DcmDsdService,

the Dcm shall support the sub-function configured in DcmDsdSubServiceId with
SPRMIB set to 0 or 1.c

7.3.4.4.1 Verification of the Manufacturer Application environment/permission

The purpose of this functionality is that, just after receiving the diagnostic request, the
Manufacturer Application is requested to check permission/environment.
E.g. in after-run ECU state, it might be not allowed to process OBD requests.

[SWS_Dcm_00218] dIf container DcmDsdServiceRequestManufacturerNoti-

fication exists, the DSD submodule shall call the operation Xxx_Indication on
all configured ServiceRequestIndication ports (see configuration parameter DcmDsd-
ServiceRequestManufacturerNotification).c

[SWS_Dcm_00462] dIf at least a single Xxx_Indication function called according

to [SWS_Dcm_00218] returns E_REQUEST_NOT_ACCEPTED, the DSD submodule
shall give no response.c

[SWS_Dcm_01172] dIn case of [SWS_Dcm_00462], the DSD shall only call

Xxx_Confirmation but not DspInternal_DcmConfirmation.c

94 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00463] dIf at least a single Xxx_Indication function called accord-

ing to [SWS_Dcm_00218] has returned E_NOT_OK and no function has returned
E_REQUEST_NOT_ACCEPTED, the DSD submodule shall trigger a negative re-
sponse with NRC from the ErrorCode parameter.c

[SWS_Dcm_01321]
Upstream requirements: RS_Diag_04011

dIf more than one Xxx_Indication function called, according to

[SWS_Dcm_00218], has returned E_NOT_OK and no function has returned
E_REQUEST_NOT_ACCEPTED, the DSD submodule shall trigger a negative re-
sponse using the ErrorCode parameter from the first Xxx_Indication returning
E_NOT_OK.c

7.3.4.4.2 Verification of the Supplier Application environment/permission

The purpose of this functionality is that, right before processing the diagnostic mes-
sage, the Supplier Application is requested to check permission/environment.
E.g. in after-run ECU state, it might be not allowed to process OBD requests.

[SWS_Dcm_00516] dIf container DcmDsdServiceRequestSupplierNotifica-

tion exists, the DSD submodule shall call the operation Xxx_Indication on all
configured ServiceRequestIndication ports (see configuration parameter DcmDsdSer-
viceRequestSupplierNotification).c

[SWS_Dcm_00517] dIf at least a single Xxx_Indication function called according

to [SWS_Dcm_00516] returns E_REQUEST_NOT_ACCEPTED, the DSD submodule
shall give no response.c

[SWS_Dcm_00518] dIf at least a single Xxx_Indication function called accord-

ing to [SWS_Dcm_00516] has returned E_NOT_OK and no function has returned
E_REQUEST_NOT_ACCEPTED, the DSD submodule shall trigger a negative re-
sponse with NRC from the ErrorCode parameter.c

[SWS_Dcm_01322]
Upstream requirements: RS_Diag_04011

dIf more than one Xxx_Indication function called, according to

[SWS_Dcm_00516], has returned E_NOT_OK and no function has returned
E_REQUEST_NOT_ACCEPTED, the DSD submodule shall trigger a negative re-
sponse using the ErrorCode parameter from the first Xxx_Indication returning
E_NOT_OK.c

95 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.3.4.5 Distribution of diagnostic message to DSP submodule

[SWS_Dcm_00221] dThe DSD submodule shall search for the executable functionality
of the DSP submodule for newly received diagnostic service identifier and shall call the
corresponding DSP service interpreter.c

7.3.4.6 Assemble positive or negative response

[SWS_Dcm_00222] dWhen the DSP submodule has finished the execution of the re-
quested Diagnostic Service the DSD submodule shall assemble the response.c

The execution of the DSP service interpreter can have the results:
• positive Result or
• negative Result.
Following possible Responses can be assembled:
• positive Response,
• negative Response, or
• no Response (in the case of suppression of responses).

7.3.4.6.1 Positive Response

[SWS_Dcm_00223] dThe DSD submodule shall add the response service identi-
fier and the response data stream (returned by the Application) in the parameter
"Dcm_MsgContextType".c

[SWS_Dcm_00224] dThe DSD submodule shall therefore transfer the

Dcm_MsgContextType into a (response) buffer and shall add the service identi-
fier at the first byte of the buffer.c

[SWS_Dcm_00225] dThe DSD submodule shall execute the "Initiate transmission"

functionality in the next execution step.c

96 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.3.4.6.2 Negative Response

The DSP submodule can trigger the transmission of a negative response with a specific
NRC to the DSD submodule. For the allowed NRC of the executed Service ID please
refer to the specification of the service in ISO14229-1 [1] (Response code parame-
ter definition Table 18 of ISO 14229-1:2020) and ISO15031-5 [2]. The DSP and the
Application have to take care of the correct use of NRC of the executed Service ID.

[SWS_Dcm_00228] dThe DSD submodule shall handle all NRCs supported from the
Application and defined in Dcm_NegativeResponseCodeType.c

7.3.4.6.3 Suppression of response

[SWS_Dcm_00231] dIn the case that the "suppressPosRspMsgIndicationBit" is in-

dicated in the functionality "Handling of suppressPosRspMsgIndicationBit" (stored in
the Variable Dcm_MsgContextType (Element: Dcm_MsgAddInfo)), the DSD submod-
ule shall activate the suppression of Positive Responses.c

[SWS_Dcm_00001]
Upstream requirements: RS_Diag_04020

dIn the case of a Negative Result of the execution and active Functional Address-
ing the DSD submodule shall activate the suppression of the following Negative Re-
sponses:
• NRC 0x11 (Service not supported),
• NRC 0x12 (SubFunction not supported),
• NRC 0x31 (Request out of range),
• NRC 0x7E (Subfunction not supported in active session),
• NRC 0x7F (Service not supported in active session)
c

7.3.4.7 Initiate transmission

[SWS_Dcm_00232] dThe DSD submodule shall forward the diagnostic (response)

message (positive or negative response) to the DSL submodule.c

97 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00237] dThe DSL submodule shall forward the diagnostic (response)

message (positive or negative response) further to the PduR module by executing a
DSL transmit functionality.c

The DSL submodule will receive a confirmation by the PduR module upon forwarding
the data.

[SWS_Dcm_00235] dThe DSL submodule shall forward the received confirmation from
the PduR module to the DSD submodule.c

[SWS_Dcm_00236] dThe DSD submodule shall forward the confirmation via the inter-
nal function DspInternal_DcmConfirmation() to the DSP submodule.c

[SWS_Dcm_00238] dIn the case that no diagnostic (response) message shall be sent
(Suppression of Responses) the DSL submodule shall not transmit any response.c

In this case no Data Confirmation is sent from the DSL submodule to the
DSD submodule but the DSD submodule will still call internal function DspInter-
nal_DcmConfirmation().

[SWS_Dcm_00240] dIn case the request has been fully processed by the Dcm, The
DSD submodule shall finish the processing of one Diagnostic Message of the Diagnos-
tic Service Dispatcher by calling DspInternal_DcmConfirmation().c

Rationale for [SWS_Dcm_00240]: The DSP submodule is waiting for the execution of
the DspInternal_DcmConfirmation() functionality. So it has to be sent, also when no
Data Confirmation is provided. Altogether this means that in any of the following cases:
• Positive Response,
• Negative Response,
• Suppressed Positive Response, and
• Suppressed Negative Response
The DSD submodule will finish by calling DspInternal_DcmConfirmation() (refer to
8.10.3 DspInternal_DcmConfirmation).

[SWS_Dcm_00741] dThe DSD submodule shall call the operation Xxx_Confirmation()

on all ports using the ServiceRequestNotification interface (see configuration param-
eter DcmDsdServiceRequestManufacturerNotification and DcmDsdSer-
viceRequestSupplierNotification)c

98 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00742] dThe call of Xxx_Confirmation() shall be done right after the call
of DspInternal_DcmConfirmation()c

[SWS_Dcm_00677] dIf the operation Indication() returns value

E_REQUEST_NOT_ACCEPTED, the Dcm module shall not send any diagnostic
response and shall end the current diagnostic request management.c

[SWS_Dcm_00678] dIf the operation Indication() returns value E_NOT_OK, the Dcm
module shall send a negative response with NRC value equal to ErrorCode parameter
value.c

7.4 Diagnostic Service Processing (DSP)

7.4.1 General

When receiving a function call from the DSD submodule requiring the DSP submodule
to process a diagnostic service request, the DSP always carries out following basic
process steps:
• analyze the received request message,
• check format and whether the addressed subfunction is supported,
• acquire data or execute the required function call on the DEM, SW-Cs or other
BSW modules
• assemble the response
The following sections are some general clarifications.

7.4.1.1 Check format and subfunction support

The DSP submodule will check for appropriate message length and structure before
executing the requested command.

[SWS_Dcm_00272] dThe DSP submodule shall trigger a negative response with NRC
0x13 (Incorrect message length or invalid format), when the analysis of the request
message results in formatting or length failure.c

Note: It is up to the implementation in which detail the format check might be executed
and depends on the level of detail the diagnostic data description provides at compile
time.

99 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.1.2 Assemble response

[SWS_Dcm_00039] dThe DSP submodule shall assemble the response message ex-
cluding response service identifier and determine the response message length.c

[SWS_Dcm_00038] dIf the paged-buffer mechanism is used, the DSP submodule shall
determine the overall response length before any data is passed to the DSD submodule
or the DSL submodule respectively.c

Requirement [SWS_Dcm_00038] is needed because of segmented diagnostic data

transmission on CAN using ISO15765-2 [15], which requires the provision of the over-
all length of the complete data stream in the very first CAN frame of the respective
data transmission (please refer to Section 7.2.4.8 for details about the paged-buffer
mechanism).

7.4.1.3 Negative Response Codes handling

[SWS_Dcm_00271] dUnless another particular NRC is specified,the DSP submodule

shall trigger a negative response with NRC 0x10 (generalReject), when the API calls
made to execute the service do not return OK.c

[SWS_Dcm_01414] Accepted range of Dcm_NegativeResponseCodeType for

negative responses dIf the Dcm calls an external application by any of the APIs hav-
ing the out parameter Dcm_NegativeResponseCodeType ErrorCode, the Dcm shall
accept only values in the range 0x01-0xFF in case the return value is E_NOT_OK.c

[SWS_Dcm_01415] Behavior on application returning unexpected return code dIf

the Dcm calls an API with the out parameter Dcm_NegativeResponseCodeType Er-
rorCode and the application sets this parameter to DCM_POS_RESP and E_NOT_OK
is returned, the Dcm shall report the runtime error DCM_E_INVALID_VALUE.c

[SWS_Dcm_00275] dThe DSP submodule shall trigger a negative response with NRC
0x31 (Request out of range), when the analysis of the request message results in other
unsupported message parameters.c

7.4.1.4 Diagnostic mode declaration groups

The Dcm shall act as a mode manager for the diagnostic modes:
• 1. DcmDiagnosticSessionControl (service 0x10)

100 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• 2. DcmEcuReset (partly service 0x11)

• 3. DcmSecurityAccess (service 0x27)
• 4. DcmModeRapidPowerShutDown (partly service 0x11)
• 5. DcmCommunicationControl_<symbolic name of ComMChannelId>. (service
0x28)
• 6. DcmControlDTCSetting (service 0x85)
• 7. DcmResponseOnEvent_<RoeEventID> (service 0x86)
• 8. DcmAuthenticationState_<Symbolic Name of DcmDslMainConnection>
Note: The RTE/SchM will prefix the names with "MODE_", wherefore the names do
not include the MODE keyword.

[SWS_Dcm_01327] dThe Dcm shall define the ModeDeclarationGroupPrototype

DcmSecurityAccess as provided-ModeGroup based on the following ModeDeclara-
tionGroup:
1 ModeDeclarationGroup DcmSecurityAccess {
2 {
3 DCM_SEC_LEV_LOCKED
4 DCM_SEC_LEV_1
5 ...
6 DCM_SEC_LEV_63
7 }
8 initialMode = DCM_SEC_LEV_LOCKED
9 };

[SWS_Dcm_01328] d
1 ModeSwitchInterface SchM_Switch_<bsnp>_DcmSecurityAccess {
2 isService = true;
3 SecLevel currentMode;
4 };

[SWS_Dcm_00806] dThe Dcm shall define the ModeDeclarationGroupPrototype

DcmDiagnosticSessionControl as provided-ModeGroup based on the ModeDeclara-
tionGroup DcmDiagnosticSessionControl.c

[SWS_Dcm_00777] dThe Dcm shall define the ModeDeclarationGroupPrototype

DcmEcuReset as provided-ModeGroup in its Basic Software Module instance based
on the ModeDeclarationGroup DcmEcuReset.c

101 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00807] dThe Dcm shall define the ModeDeclarationGroupPrototype Dcm-

ModeRapidPowerShutDown as provided-ModeGroup in its Basic Software Module in-
stance based on the ModeDeclarationGroup DcmModeRapidPowerShutDown.c

[SWS_Dcm_00780] dThe Dcm shall define for each network which is consid-
ered in the CommunicationControl service a separate ModeDeclarationGroupProto-
type DcmCommunicationControl_<symbolic name of ComMChannelId> as provided-
ModeGroup in its Basic Software Module instance based on the ModeDeclara-
tionGroup DcmCommunicationControl.c

[SWS_Dcm_00781] dThe Dcm shall define the ModeDeclarationGroupPrototype Dcm-

ControlDTCSetting as provided-ModeGroup in its Basic Software Module instance
based on the ModeDeclarationGroup DcmControlDTCSetting.c

[SWS_Dcm_00933] dThe Dcm shall define for each RoeEvent a separate ModeDec-
larationGroupPrototype DcmResponseOnEvent_<Symbolic name of RoeEventId> as
provided-ModeGroup in its Basic Software Module instance based on the ModeDecla-
rationGroup DcmResponseOnEvent.c

The Dcm provides a state machine for each RoeEvent. The state for a RoeEvent is
needed by SWC to activate event reporting or report the Roe status to a Did. Therefore
the Dcm provides for each state of each RoeEvent a ModeDeclarationGroupPrototype
which reports the current state of the state machine as mode.

[SWS_Dcm_00934] dThe ModeDeclarationGroupPrototype shall represent the current

state of the ROE state machine for this RoeEvent.c

7.4.1.5 Environmental condition dependent execution

The execution of a diagnostic service or the acceptance of certificates can be re-

stricted to a mode condition. This enables the Dcm to formalize environmental
checks. For diagnostic service processing, a further check (see [SWS_Dcm_00773]
and [SWS_Dcm_00774]) can be configured to the Dcm. This is like session and secu-
rity checks. The referenced mode rule is arbitrating on to several mode declarations of
a mode declaration groups in which the request can be processed. Otherwise a con-
figurable NRC (see [SWS_Dcm_00812]) is responded. The same mode rule checks
can be applied on certificate validation. Certificates can be restricted to certain vehicle
properties, such as VIN or a certain version number. Only if all the conditions are valid,
the certificate is accepted by the Dcm.

102 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00808] dThe DcmModeRule shall evaluate all referenced DcmModeCon-

ditions and/or nested DcmModeRules either by a logical AND in case DcmLogical-
Operator is set to DCM_AND or by a logical OR in case the DcmLogicalOperator
is set to DCM_OR. In case only a single DcmModeCondition or DcmModeRule is ref-
erenced the DcmLogicalOperator shall not be present and therefore not be used.c

[SWS_Dcm_CONSTR_06028] dDcmModeCondition shall either have a DcmB-

swModeRef or a DcmSwcModeRef or a DcmSwcSRDataElementRef as external ref-
erence.c

[SWS_Dcm_00810] dThe DcmSwcModeRef and DcmBswModeRef of DcmModeCon-

ditions shall evaluate if the referenced Mode-Declaration is set in case of DcmCondi-
tionType is set to DCM_EQUALS or is not set in case of DcmConditionType is set
to DCM_EQUALS_NOT.c

[SWS_Dcm_01119] Mode condition evaluation dFor each mode condition, the Dcm
shall compare a compare value with a S/R data element. The compare value is pro-
vided by DcmSwcSRDataElementValueRef or DcmModeConditionConnectionCertifi-
cateCompareElementRef and the S/R Element is by DcmSwcSRDataElementRef. The
mode condition is evaluated to true if the S/R data element value is:
• equal to the compare value in case of DcmConditionType is set to
DCM_EQUALS
• unequal to the compare value in case of DcmConditionType is set to
DCM_EQUALS_NOT
• greater than the compare value in case of DcmConditionType is set to
DCM_GREATER_THAN
• greater or equal than the compare value in case of DcmConditionType is set
to DCM_GREATER_OR_EQUAL
• less than the compare value in case of DcmConditionType is set to
DCM_LESS_THAN
• less or equal than the compare value in case of DcmConditionType is set to
DCM_LESS_OR_EQUAL.
c

[SWS_Dcm_CONSTR_06029] dThe values DCM_GREATER_THAN,

DCM_GREATER_OR_EQUAL, DCM_LESS_OR_EQUAL and DCM_LESS_THAN
shall not used with a Mode reference (DcmBswModeRef or DcmSwcModeRef) .c

103 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Note: The current mode of the referenced ModeDeclarationGroupPrototypes could

be read by either the API SchM_Mode (in case of DcmBswModeRef) or by the API
Rte_Mode (in case of DcmSwcModeRef).

[SWS_Dcm_00811] dIn case multiple DcmModeConditions are referenced within a

DcmModeRule they shall be evaluated in order of the index attributes of the EcucRef-
erenceValues for DcmArgumentRef.c

Note: This implies the priority of NRCs

[SWS_Dcm_00782] dIf a DcmModeRule is not referenced from the DcmDspAuthen-

ticationConnection, the Dcm shall use the optional parameter DcmModeRuleN-
rcValue as NegativeResponseCode in case the mode rule is evaluated to false.c

Mode rules for DcmDspAuthenticationConnection are not part of the NRC eval-
uation.

[SWS_Dcm_00812] dIn case a nested DcmModeRule contains also a DcmModeRu-

leNrcValue parameter, this NRC shall be used prior the higher-level NRC.c

[SWS_Dcm_00813] dIn case DcmLogicalOperator is set to DCM_AND, the first

failed DcmModeRule with an explicit configured NRC (DcmModeRuleNrcValue) shall
be used to define the NRC for the response message.c

[SWS_Dcm_00814] dIn case DcmLogicalOperator is set to DCM_OR, the last

failed DcmModeRule with an explicit configured NRC (DcmModeRuleNrcValue) shall
be used to define the NRC for the response message.c

Note: The difference in the AND and OR logical operation is to allow an optimized
implementation.

[SWS_Dcm_00815] dIn case the complete evaluation result in no specific NRC the NRC
0x22 (ConditionsNotCorrect) shall be used.c

[SWS_Dcm_00942] dThe Dcm shall create for commonly used ModeDeclara-

tionGroupPrototype of each DcmSwcModeRef of DcmModeConditions a required
mode switch port referencing this ModeDeclarationGroupPrototype. The name pattern
of this port prototype shall be DcmModeUser_<ModeDeclarationGroupPrototype>" in
case the ModeDeclarationGroupPrototype shortname is unique. Otherwise the name
pattern is implementation specific, except the required prefix "DcmModeUser_".c

104 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Note: ModeDeclarationGroupPrototypes are not necessarily unique, wherefore the ex-

ception is required to avoid name clashes in the Dcm Service-SWC.
Examples on using mode dependent request execution:
General assumptions:
1. DcmModeRule1 consists of DcmModeCondition1, DcmModeRule2 and Dcm-
ModeRule3
2. DcmModeRule1 defines NRC 0x22
3. DcmModeRule2 and DcmModeRule3 do not have any sub-rules
4. DcmModeRule2 defines NRC 0x72
5. DcmModeRule3 does not define a NRC value
Example 1:
1) DcmModeRule1 uses an OR combination (DcmModeCondition1 OR Dcm-
ModeRule2 OR DcmModeRule3)
a) DcmModeCondition1 is failing
–> NRC 0x22 is returned
b) DcmModeRule2 is failing
–> NRC 0x72 is returned
c) DcmModeRule3 is failing
–> NRC 0x22 is returned
d) DcmModeCondition1, DcmModeRule2 and DcmModeRule3 are failing
–> NRC 0x72 is returned
e) DcmModeCondition1 and DcmModeRule3 are failing
–> NRC 0x22 is returned

Example 2:
1) DcmModeRule1 uses an AND combination (DcmModeCondition1 AND Dcm-
ModeRule2 AND DcmModeRule3)
a) DcmModeCondition1 is failing
–> NRC 0x22 is returned
b) DcmModeRule2 is failing
–> NRC 0x72 is returned
c) DcmModeRule3 is failing
–> NRC 0x22 is returned
d) DcmModeCondition1, DcmModeRule2 and DcmModeRule3 are failing
–> NRC 0x22 is returned
e) DcmModeCondition1 and DcmModeRule3 are failing
–> NRC 0x22 is returned
e) DcmModeRule2 and DcmModeRule3 are failing
–> NRC 0x72 is returned

105 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_CONSTR_06089] Only one compare element

Upstream requirements: RS_Diag_04232

dIn one DcmModeCondition only one of the elements DcmSwcSRDataElementRef

or DcmModeConditionCertificateCompareElementRef shall be configured.c

[SWS_Dcm_CONSTR_06090] Use of certificate compare elements dThe DcmMod-

eConditionCertificateCompareElementRef is only allowed, if the parent Dcm-
ModeRule is referenced from a DcmDspAuthenticationConnection.c

7.4.1.6 Sender/Receiver Communication

[SWS_Dcm_00964] dIf DcmDspDiagnosisScaling is present, the Dcm shall de-

rive the CompuMethod from the DcmDspDiagnosisScaling container and add it
to the DataType in their respective port interface for S/R port of DataServices_Data
[SWS_Dcm_01035].c

7.4.1.7 Passing SwDataDefProps properties from DEXT file to the Dcm Service
SW-C

UseCase: Pass the SwDataDefProps details like CompuMethod, DataContraints and

Units to the Dcm Service SW-C and make them there available per DID DataElement /
per RoutineControl signal. Two alternative work flows are available.

106 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.1.7.1 DcmDspDiagnosticDataElementRef workflow

Figure 7.8: DcmDspDiagnosticDataElementRef Workflow

The feature of the DcmDspDiagnosticDataElementRef workflow is the use of a

EcucForeignReference inside the generated EcuC values. While importing the DEXT
information, a dedicated EcuC parameter is generated, which holds a EcucForeign-
Reference named DcmDspDiagnosticDataElementRef to a DiagnosticDataEle-
ment in the DEXT file. This EcucForeignReference enables the access to all Sw-
DataDefProps (BaseType, CompuMethod, DataConstr, etc.) of the corresponding Di-
agnosticDataElement. The container DcmDspAlternativeDiagnosticDataEle-
ment aggregates this EcucForeignReference. In the process step of generating the
corresponding Service SWC all needed content will be copied directly based on the
EcucForeignReference from DEXT to the Service SW-C. In this work flow the existence
of the DEXT file while the generation of the Service SW-C is required.

[SWS_Dcm_CONSTR_06053] dThe aggregation of DcmDspTextTableMapping at

DcmDspAlternativeDataType is only valid if the category of the CompuMethod
of the DataType referenced by DcmDspAlternativeDataType.DcmApplicationDataType
has category set to TEXTTABLE or SCALE_LINEAR_AND_TEXTTABLE.c

107 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.1.7.2 DcmDspAlternativeDataType.DcmApplicationDataType workflow

Figure 7.9: DcmDspAlternativeDataType.DcmApplicationDataType Workflow

The feature of the DcmDspAlternativeDataType.DcmApplicationDataType

workflow is that while importing the DEXT information beside the EcuC values also a
SW-C fragment is generated. In this SW-C fragment all needed SwDataDefProps are di-
rectly copied from the DEXT file. Inside the generated EcuC values the EcuC parame-
ter DcmDspAlternativeDataType.DcmApplicationDataType refers to the SWC
fragment and enables the access to all SwDataDefProps (BaseType, CompuMethod,
DataConstr, etc.). In the process step of generating the corresponding Service SW-C,
all needed content will be included based on the reference from DcmDspAlterna-
tiveDataType.DcmApplicationDataType to the SW-C fragment. In this work flow
the existence of the DEXT file while the generation of the Service SW-C is not required.

7.4.1.8 Asynchronous call behavior

[SWS_Dcm_01412] dIf a Dem function returns DEM_PENDING, the Dcm shall call this
function again at a later point in time as long as DEM_PENDING is returned.c

[SWS_Dcm_00120] dIf the number of negative responses for a requested diagnostic

tasks (see [SWS_Dcm_00024]) reaches the value defined in the configuration param-
eter DcmDslDiagRespMaxNumRespPend, the Dcm module shall stop processing the
active diagnostic request, inform the application or BSW (if this diagnostic task implies
the call to a SW-C interface or a BSW interface) by setting OpStatus parameter, of

108 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

active port interface, to DCM_CANCEL, report the runtime error DCM_E_INTERFACE_-

TIMEOUT and shall send a negative response with NRC 0x10 (General reject).c

[SWS_Dcm_01184] dThe Dcm_SetProgConditions API shall be called again in

the next Dcm main function cycle if previous return status was E_PENDING.c

[SWS_Dcm_00760] dThe return of DCM_E_PENDING shall do a re-triggering (e.g. in

the next MainFunction cycle).c

[SWS_Dcm_01413] dThe return values of interfaces called with an OpStatus equal

to DCM_CANCEL shall be ignored.c

7.4.2 UDS Services

[SWS_Dcm_01622] Diagnostic Request Validation

Upstream requirements: RS_Diag_04196, RS_Diag_04203

dThe Dcm shall execute the diagnostic request validation, negative response code (
NRC) determination and processing according to ISO 14229-1 [1].c

[SWS_Dcm_00442] dThe Dcm module shall implement the services of UDS according
to [SWS_Dcm_01641].c

[SWS_Dcm_01641] Support of UDS Services d

SID Service Subfunction Supported
0x10 DiagnosticSessionControl Supported
0x11 ECUReset Supported
0x14 ClearDiagnosticInformation Supported
0x19 ReadDTCInformation Supported
0x22 ReadDataByIdentifier Supported
0x23 ReadMemoryByAddress Supported (callout)
0x24 ReadScalingDataByIdentifier Supported
0x27 SecurityAccess Supported
0x28 CommunicationControl Supported
0x29 Authentication Supported
0x2A ReadDataByPeriodicIdentifier Supported
0x2C DynamicallyDefineDataIdentifie Supported
0x2E WriteDataByIdentifier Supported
0x2F InputOutputControlByIdentifier Supported
0x31 RoutineControl Supported
0x34 RequestDownload Supported (callout)
0x35 RequestUpload Supported (callout)
0x36 TransferData Supported
0x37 RequestTransferExit Supported

109 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

SID Service Subfunction Supported

0x38 RequestFileTransfer Supported (callout)
0x3D WriteMemoryByAddress Supported (callout)
0x3E TesterPresent Supported
0x83 AccessTimingParameter NRC
"ServiceNotSupported"
0x84 SecuredDataTransmission NRC
"ServiceNotSupported"
0x85 ControlDTCSetting On, off Supported
0x86 ResponseOnEvent Supported
0x87 LinkControl User optional

7.4.2.1 General behavior using DEM interfaces

Fault memory related diagnostic services are by default processed directly within the
Dcm. The Dcm uses the Dem module to clear, query, and read diagnostic fault codes,
status, and related data. The option to process such a diagnostic via the callout of the
DSD sub-module, e.g. DcmDsdSubServiceFnc for service 0x19, is considered an
exceptional use case.
This chapter describes general rules, and how the Dcm interacts with the Dem to fulfill
the task to process the fault memory related UDS services.
The UDS defined DTC status availability mask is managed by the Dem module and
therefore not configured in the Dcm. When this mask is required the Dcm uses the
Dem_GetDTCStatusAvailabilityMask API to read this information.
The UDS defined severity DTC severity availability mask is also managed
by the Dem and therefore not configured by the Dcm. The Dcm uses
Dem_GetDTCStatusAvailabilityMask to retrieve this mask information.
To ensure consistent event related data during the reading sequence, the Dcm module
will lock the update of event related data during the read operation. The Dem provides
Dem_DisableDTCRecordUpdate and Dem_EnableDTCRecordUpdate to temporarily
stop updating the event memory. In particular, this happens during the use of the
following Dem APIs.
• Dem_SelectExtendedDataRecord()
• Dem_GetSizeOfExtendedDataRecordSelection()
• Dem_GetNextExtendedDataRecord()
• Dem_SelectFreezeFrameData()
• Dem_GetSizeOfFreezeFrameSelection() and
• Dem_GetNextFreezeFrameData()

110 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Potentially time consuming API calls in the Dem are designed asynchronous so that the
call can return and the caller can call again at a later time to retrieve the requested
data. These APIs have DEM_PENDING as a possible return value. If this return value
is detected, the Dcm will call again with the same parameters. The time of the next call
is implementation specific, but mostly this will occur in the next Dcm_MainFunction.
Repeated occurring DEM_PENDING as the return value from the Dem can result in
ResponsePending NRC 0x78 sent by the Dcm.

7.4.2.2 Service 0x10 - Diagnostic Session Control

UDS Service 0x10 allows an external tester to enable different diagnostic sessions in
the server. A diagnostic session enables a specific set of diagnostic services and/or
functionality in the server. The service request contains the parameter:
• diagnosticSessionType

[SWS_Dcm_00250]
Upstream requirements: RS_Diag_04006

dThe Dcm module shall implement the UDS Service 0x10 according to ISO 14229-
1:2020 [9]c

[SWS_Dcm_00307] dWhen responding to UDS Service 0x10, if the requested sub-

function value is not configured in the ECU (configuration parameter DcmDspSes-
sionLevel), the DSP submodule shall trigger a negative response with NRC 0x12
(SubFunction not supported).c

If the requested subfunction value is configured, the following steps are processed
even if the requested session type is equal to the already running session type (see
ISO14229-1 [1] Section 9.2).

[SWS_Dcm_00311]
Upstream requirements: RS_Diag_04248

dThe send confirmation function shall set the new diagnostic session type
with DslInternal_SetSesCtrlType() and shall set the new timing parameters
(P2ServerMax, P2ServerMax*) (see configuration parameters DcmDspSes-
sionP2ServerMax and DcmDspSessionP2StarServerMax) and do the mode switch
of the ModeDeclarationGroupPrototype DcmDiagnosticSessionControl by calling
SchM_Switch_<bsnp>_DcmDiagnosticSessionControl() with the new diagnostic
session type (see [SWS_Dcm_91019]).c

111 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00085] dThe DSP submodule shall manage internally a read ac-

cess for the dataIdentifier 0xF186 (ActiveDiagnosticSessionDataIdentifier) defined in
ISO14229-1 [1].c

7.4.2.3 Service 0x11 - ECUReset

UDS Service ECUReset (0x11) allows an external tester to request a server reset. The
service request contains parameter:
• resetType

[SWS_Dcm_00260] dThe Dcm module shall implement the UDS Service ECUReset
(0x11).c

[SWS_Dcm_00373] dOn reception of a request for UDS Service 0x11 with the sub
functions other than enableRapidPowerShutDown (0x04) or disableRapidPowerShut-
Down (0x05), the Dcm module shall trigger the mode switch of ModeDeclarationGroup-
Prototype DcmEcuReset equal to the received resetType. After the mode switch is
requested the Dcm shall trigger the start of the positive response message transmis-
sion. Sub function hardReset (0x01) to HARD Sub function keyOffOnReset (0x02) to
KEYONOFF Sub function softReset (0x03) to SOFTc

Note: By this mode switch the Dcm informs the BswM to carry out necessary actions
for the handling of this individual reset type. These actions can be configured within
the BswM action list corresponding to the requested reset type. Here the integrator can
also define if an ECU reset will finally be performed or not.

[SWS_Dcm_00594] dOn the transmit confirmation (call to Dcm_TpTxConfirmation)

of the positive response for the subfunctions other than enableRapidPowerShutDown
(0x04) or disableRapidPowerShutDown (0x05), the Dcm module shall trigger the mode
switch of ModeDeclarationGroupPrototype DcmEcuReset to the mode EXECUTE (via
SchM_Switch_<bsnp>_DcmEcuReset(RTE_MODE_DcmEcuReset_EXECUTE)).c()c

Note: By this mode switch the Dcm requests the BswM to perform the final processing
on the reset type according to the configured action list.

[SWS_Dcm_00818] dOn reception of a request for UDS Service 0x11 with the
sub functions enableRapidPowerShutdown (0x04) or disableRapidPowerShutdown
(0x05), the Dcm module shall trigger the mode switch of ModeDeclarationGroupPro-
totype DcmRapidPowerShutDown: Sub function enableRapidPowerShutDown (0x04)
to ENABLE_RAPIDPOWERSHUTDOWN, Sub function disableRapidPowerShutDown
(0x05) to DISABLE_RAPIDPOWERSHUTDOWNc

112 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Note: If EnableRapidPowerShutdown is enabled, the ECU should shorten its power-

down time.

[SWS_Dcm_00589] dIn case the parameter DcmDspPowerDownTime is present, the

Dcm shall set the powerDownTime in positive response to sub-service enableRapid-
PowerShutDown with value set in DcmDspPowerDownTime.c

[SWS_Dcm_00834] dAfter sending the positive response of EcuReset (call of

Dcm_TpTxConfirmation) the Dcm shall ignore all further requests during reset-
processing.c

[SWS_Dcm_CONSTR_06080] DcmDspEcuResetRow container configuration

Upstream requirements: RS_Diag_04098

dOne container DcmDspEcuResetRow shall be configured for each DcmDsdSubSer-

vice (DcmDspEcuResetId matching to the DcmDsdSubServiceId) configured for
the UDS service ECUReset (0x11) which does not have the corresponding DcmDsd-
SubServiceFnc parameter configured.c

7.4.2.4 Service 0x14 - Clear Diagnostic Information

UDS Service ClearDiagnosticInformation (0x14) requests an ECU to clear the error

memory. The service request contains the parameter:
• groupOfDTC.

[SWS_Dcm_00247] dThe Dcm module shall implement UDS Service 0x14.c

[SWS_Dcm_01263]
Upstream requirements: RS_Diag_04058

dUpon reception of a UDS Service ClearDiagnosticInformation (0x14) request with pa-

rameter groupOfDTC, the Dcm module shall call the API Dem_SelectDTC() with the
following parameter values:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
• DTC: groupOfDTC from the service request
• DTCFormat: DEM_DTC_FORMAT_UDS
• DTCOrigin: DEM_DTC_ORIGIN_PRIMARY_MEMORY
c

113 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01400] dAfter call of Dem_SelectDTC() the Dcm shall call

Dem_GetDTCSelectionResultForClearDTC() with the following parameter value:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef.
c

[SWS_Dcm_01265] dIn case Dem_GetDTCSelectionResultForClearDTC() returns

DEM_WRONG_DTC, the Dcm shall send a NRC 0x31 (RequestOutOfRange).c

[SWS_Dcm_01268] dIn case Dem_GetDTCSelectionResultForClearDTC() returns

E_OK, the Dcm module shall check if application allows to clear the DTC (according
to the configuration parameter DcmDspClearDTCCheckFnc). If not, the Dcm module
shall send a negative response with NRC set to value from the parameter "ErrorCode".c

[SWS_Dcm_01269] dIn case application allows to clear the DTC, the Dcm module
shall check if the DTC can be cleared in the current mode condition (according to the
configuration parameter DcmDspClearDTCModeRuleRef). If not, the Dcm module
shall send the calculated negative response code of the referenced DcmModeRule.c

[SWS_Dcm_00005]
Upstream requirements: RS_Diag_04058

dIf the condition checks are successfully done, the Dcm module shall call
Dem_ClearDTC with the following parameter values:
• ClientId = Client Id for this Dcm instance (see DcmDemClientRef)
c

[SWS_Dcm_00705] dIn case Dem_ClearDTC() returns E_OK, the Dcm module shall
send a positive response.c

[SWS_Dcm_00707] dIn case Dem_ClearDTC() returns DEM_CLEAR_FAILED, the

Dcm shall send a negative response 0x22 (conditionsNotCorrect).c

[SWS_Dcm_00708] dIn case Dem_ClearDTC() returns DEM_WRONG_DTC, the Dcm

shall send a negative response 0x31 (requestOutOfRange).c

[SWS_Dcm_00966] dIn case Dem_ClearDTC() returns DEM_CLEAR_BUSY, the Dcm

shall send a negative response 0x22 (conditionsNotCorrect).c

[SWS_Dcm_01060] dIn case Dem_ClearDTC() returns

DEM_CLEAR_MEMORY_ERROR, the Dcm shall trigger a negative response
with NRC 0x72 (generalProgrammingFailure).c

114 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01408] dIn case Dem_ClearDTC() returns DEM_WRONG_DTCORIGIN,

the Dcm shall trigger a negative response 0x31 (requestOutOfRange).c

7.4.2.5 Service 0x19 - Read DTC Information

Service 0x19 allows a client to read the status of server resident Diagnostic Trouble
Code (DTC) information.

[SWS_Dcm_00248] dThe Dcm module shall implement the UDS Service 0x19.c

To setup the retrieval of specific data from the Dem module, the Dcm will
call different filter APIs (Dem_SetDTCFilter(), Dem_SetFreezeFrameRecordFilter(),
Dem_SelectFreezeFrameData() and Dem_SelectExtendedDataRecord()).

[SWS_Dcm_01043] dIn case E_NOT_OK is returned by Dem_SetDTCFilter(), the Dcm

module shall send a negative response with NRC 0x31 (requestOutOfRange).c

[SWS_Dcm_01334] dFor all sub-functions addressing user defined fault memory,

before calling the appropriate Dem API, the Dcm shall add the value 0x0100 to
the received selection request parameter MemorySelection in order to match the
Dem_DTCOriginType.c

The Dcm service processor for UDS service ReadDTCInformation (0x19) can be used
in configurations where SAE J1979-2 is supported, so that reported DTC values of
SAE J1979-2 services have different DTC values than used for UDS DTCs.
Some manufacturers don’t want to fully change to SAE J1979-2 support with UDS and
will only support the J1979-2 functionality on the limited UDS subset defined by J1979-
2, wherefore the feature OBD UDS DTC separation was added.

[SWS_Dcm_01618] Use of separated OBD and UDS DTCs

Upstream requirements: RS_Diag_04253

dIf DcmDspReadDTCInformationSupportedObdUdsDtcSeparation is set to

True, the Dcm service processor for all diagnostic requests according to SAE J1979-
2 shall use the Dem API Dem_SelectDTC with the parameter DTCFormat set to
DEM_DTC_FORMAT_OBD_3BYTE to query and process DTC related information.c

115 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01619]
Upstream requirements: RS_Diag_04253

dIf DcmDspReadDTCInformationSupportedObdUdsDtcSeparation is set to

False, the Dcm service processor for all diagnostic requests according to SAE J1979-
2 shall use the Dem API Dem_SelectDTC with the parameter DTCFormat set to
DEM_DTC_FORMAT_UDS to query and process DTC related information.c

[SWS_Dcm_01343] dFor services with FunctionalGroupIdentifier as parameter in the

request, the Dcm shall only process request messages with FunctionalGroupIdentifier
equal to 0x33.c

[SWS_Dcm_01344] dFor services with FunctionalGroupIdentifier as parameter in the

request and FunctionalGroupIdentifier unequal to 0x33, the Dcm shall return NRC 0x31
(RequestOutOfRange).c

7.4.2.5.1 Subfunctions 0x01, 0x07 and 0x12

UDS Service 0x19 with subfunctions 0x01 or 0x12 requests the ECU to report the
number of DTCs matching tester-defined criteria. The service request contains the
parameter:
• DTCStatusMask
UDS Service 0x19 with subfunction 0x07 requests the ECU to report the num-
ber of DTCs matching tester-defined criteria. The service request contains the
parameters:
• DTCSeverityMask
• DTCStatusMask

[SWS_Dcm_00376] dWhen sending a positive response to UDS Service 0x19 with

subfunction 0x01, 0x07 or 0x12, the Dcm module shall use the data in the response
message according to [SWS_Dcm_01642]c

[SWS_Dcm_01642] Subfunction 0x01, 0x07 and 0x12 response values d

Parameter name Value
DTCStatusAvailabilityMask DTCStatusAvailabilityMask
DTCFormatIdentifier Value returned by Dem_GetTranslationType()
DTCCount Value calculated according to [SWS_Dcm_00293]

116 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00293]
Upstream requirements: RS_Diag_04058, RS_Diag_04067

dWhen responding to UDS Service 0x19 with subfunction 0x01, 0x07 or 0x12, the Dcm
module shall calculate the number of DTCs using Dem_GetNumberOfFilteredDTC()
after having set the DEM-filter with Dem_SetDTCFilter() using the parameter values
according to [SWS_Dcm_01643].c

[SWS_Dcm_01643] Dem_SetDTCFilter() parameters values for subfunctions

0x01, 0x07 and 0x12 d
reportNumberOfDTC reportNumberOfDTC reportNumberOf
ByStatusMask BySeverity- EmissionsRelated
MaskRecord OBDDTCByStatus-
Mask
0x01 0x07 0x12
ClientId Client Id for this Dcm Client Id for this Dcm Client Id for this Dcm
instance (see instance (see instance (see
DcmDemClientRef) DcmDemClientRef) DcmDemClientRef)
DTCStatusMask DTCStatusMask from DTCStatusMask from DTCStatusMask from
request request request
DTCFormat DEM_DTC_ DEM_DTC_ DEM_DTC_
FORMAT_UDS FORMAT_UDS FORMAT_UDS
DTCOrigin PRIMARY_MEMORY PRIMARY_MEMORY DEM_DTC_ORIGIN_
OBD_RELEVANT_
MEMORY
FilterWithSeverity FALSE TRUE FALSE
DTCSeverityMask Not relevant DTCSeverityMask Not relevant
from request
FilterForFaultDetec- FALSE FALSE FALSE
tionCounter

7.4.2.5.2 Subfunctions 0x02, 0x0A, 0x13, 0x15 and 0x17

UDS Service 0x19 with subfunctions 0x02 or 0x13 requests the DTCs (and their associ-
ated status) that match certain conditions. The service request contains the parameter:
• DTCStatusMask
UDS Service 0x19 with subfunction 0x0A requests all supported DTCs and their associ-
ated status. UDS Service 0x19 with subfunction 0x15 requests all DTCs with permanent
status.

[SWS_Dcm_00377] dWhen sending a positive response to UDS Service 0x19 with

subfunction 0x02, 0x0A, 0x13, 0x15 or 0x17, the Dcm module shall use the data in the
response message according to [SWS_Dcm_01644].c

117 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01644] Subfunction 0x02, 0x0A, 0x13, 0x15 and 0x17 response val-
ues d
Parameter name Value
DTCStatusAvailabilityMask DTCStatusAvailabilityMask
DTCAndStatusRecord As defined in [SWS_Dcm_00008] and
[SWS_Dcm_00378]
MemorySelection (subservice 0x17 From request
only)

[SWS_Dcm_01545] Read user defined memory by status mask authentication

check
Upstream requirements: RS_Diag_04233

dOn reception of the UDS Service ReadDTCInformation (0x19) with sub-function re-
portUserDefMemoryDTCByStatusMask (0x17), the Dcm shall check if the access to
the selected user defined memory in parameter MemorySelection is authenticated and
read the DTC information only if:
• a DcmDspReadDTCInformationUserDefinedFaultMemoryRoleRef is
configured with DcmDspReadDTCInformationUserDefinedFaultMem-
oryId matching the MemorySelection and the verification according to
[SWS_Dcm_01479] was successful or
• the active white list on that connection has an entry for that requested user de-
fined memory selection one entry.
c

According to [SWS_Dcm_01545] the authentication checks are only executed if

DcmDspAuthentication is configured. In case of a failed authentication the NRC han-
dling is according to [SWS_Dcm_01544] and [SWS_Dcm_01551] applies.

[SWS_Dcm_00008] dOn reception of a UDS Service 0x19 request with subfunction

0x02 and 0x13 and if the result of the bitwise AND operation between the DTCSta-
tusMask received within the request message and the DTCStatusAvailabilityMask re-
ported by the DEM is equal to 0, the Dcm module shall answer positively with 0 DTC.c

[SWS_Dcm_00378]
Upstream requirements: RS_Diag_04058, RS_Diag_04067

dWhen responding to UDS Service 0x19 with subfunctions 0x02, 0x0A, 0x13, 0x15 or
0x17, the Dcm module shall obtain the records with DTCs (and their associated status)
by repeatedly calling Dem_GetNextFilteredDTC() after having configured the filter with
Dem_SetDTCFilter() using the parameter values according to [SWS_Dcm_01645].c

118 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01645] Dem_SetDTCFilter() parameters values for subfunctions

0x02, 0x0A, 0x13, 0x15 and0x17 d
reportDTC report report report report
ByStatus Supported Emissions DTCWith UserDef
Mask DTCs Related Permanent Memory
OBDDTC Status DTCBy
ByStatus StatusMask
Mask
0x02 0x0A 0x13 0x15 0x17
ClientId Client Id for Client Id for Client Id for Client Id for Client Id for
this Dcm this Dcm this Dcm this Dcm this Dcm
instance (see instance (see instance (see instance (see instance (see
DcmDem- DcmDem- DcmDem- DcmDem- DcmDem-
ClientRef) ClientRef) ClientRef) ClientRef) ClientRef)
DTCStatus DTCStatus 0x00 DTCStatus 0x00 DTCStatus
Mask Mask from Mask from Mask from
request request request
DTCFormat DEM_DTC_ DEM_DTC_ DEM_DTC_ DEM_DTC_ DEM_DTC_
FOR- FOR- FOR- FOR- FOR-
MAT_UDS MAT_UDS MAT_UDS MAT_UDS MAT_UDS
DTCOrigin PRIMARY_ PRIMARY_ DEM_DTC_ PERMA Memory
MEMORY MEMORY ORIGIN_ NENT_ Selection from
OBD_ MEMORY request +
RELEVANT_ 0x0100
MEMORY
FilterWith NO NO NO NO NO
Severity
DTCSeverity Not relevant Not relevant Not relevant Not relevant Not relevant
Mask
FilterForFault NO NO NO NO NO
Detection
Counter

Note:
• The Dcm module can get an indication of the number of records that will be found
using Dem_GetNextFilteredDTC() by using Dem_GetNumberOfFilteredDTC().
This allows the implementation to calculate the total size of the response before
cycling through the DTCs.
• The value 0x00 used as DTCStatusMask for the subfunctions 0x0A and 0x15
disables the status byte filtering in Dem_SetDTCFilter().

[SWS_Dcm_00828] dIn case of paged buffer support is disabled, the Dcm module shall
not insert zero-padded DTCs to the response of UDS Service 0x19 with subfunctions
0x02, 0x0A, 0x13, 0x15 or 0x17.c

119 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

When using paged buffer mechanism, in some case, it’s possible that the number of
DTC matching the filter change between the calculation of the total size, needed for
the first page transmission, and the sending of the further pages. For this reason, the
following requirement apply :

[SWS_Dcm_00587] dIn case of paged buffer support is enabled, The Dcm shall limit
the response size to the size calculated when sending the first page. If more DTCs
match the filter after this sending, the additional DTCs shall not be considered.c

[SWS_Dcm_00588] dIn case of paged buffer support is enabled,The Dcm shall pad
the response with the size calculated when sending the first page. If less DTC match
the filter after this sending, the missing DTCs shall be padded with 0 value as defined
in 15031-6 [16].c

[SWS_Dcm_01229] dIf Dem_GetNextFilteredDTC() returns

DEM_NO_SUCH_ELEMENT and at least one matching element could be retrieved
before, the Dcm shall send a positive response including these data elements.c

[SWS_Dcm_01230] dIf Dem_GetNextFilteredDTC() returns

DEM_NO_SUCH_ELEMENT and at no matching element could be retrieved be-
fore, the Dcm shall send a positive response only for service and subservice and
additional parameters required within a positive response.c

7.4.2.5.3 Subfunction 0x08

UDS Service 0x19 with subfunction 0x08 requests the DTCs and the associated status
that match a tester-defined severity mask record. The service request contains the
following parameters:
• DTCSeverityMask
• DTCStatusMask

[SWS_Dcm_00379] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x08, the Dcm module shall use the data in the response message according
to [SWS_Dcm_01646].c

[SWS_Dcm_01646] Subfunction 0x08 response values d

Parameter name Value
DTCStatusAvailabilityMask DTCStatusAvailabilityMask
DTCAndSeverityRecord As defined in [SWS_Dcm_00380]

120 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00380] dWhen responding to UDS Service 0x19 with subfunction

0x08, the Dcm module shall obtain the DTCAndSeverityRecords by repeatedly call-
ing Dem_GetNextFilteredDTCAndSeverity() after having configured the filter with
Dem_SetDTCFilter() using the parameter values according to [SWS_Dcm_01647].c

[SWS_Dcm_01647] Dem_SetDTCFilter() parameters values for Subfunction 0x08

d
reportDTCBySeverityMaskRecord
ClientId Client Id for this Dcm instance (see DcmDemClientRef)
DTCStatusMask DTCStatusMask from request
DTCFormat DEM_DTC_FORMAT_UDS
DTCOrigin PRIMARY_MEMORY
FilterWithSeverity TRUE
DTCSeverityMask DTCSeverityMask from request
FilterForFaultDetectionCounter FALSE

Note: The Dcm module can get an indication of the number of records
that will be found using Dem_GetNextFilteredDTCAndSeverity() by using
Dem_GetNumberOfFilteredDTC().

7.4.2.5.4 Subfunction 0x09

UDS Service 0x19 with subfunction 0x09 requests the severity information of a DTC.
The service request contains the parameter:
• DTCMaskRecord

[SWS_Dcm_00381] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x09, the Dcm module shall use the data in the response message according
to [SWS_Dcm_01648].c

[SWS_Dcm_01648] Subfunction 0x09 response values d

Parameter name Value
DTCStatusAvailabilityMask DTCStatusAvailabilityMask
DTCAndSeverityRecord DTCSeverityMask: see [SWS_Dcm_01402]
DTCFunctionalUnit: see [SWS_Dcm_01403]
DTC: the given DTC of the request
statusOfDTC : see [SWS_Dcm_01404]

121 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01402] dTo select the DTC, the Dcm module shall call the API
Dem_SelectDTC() with the following parameter values:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
• DTC: DTC from the service request
• DTCFormat: DEM_DTC_FORMAT_UDS
• DTCOrigin: DEM_DTC_ORIGIN_PRIMARY_MEMORY
c

[SWS_Dcm_01403] dTo retrieve the DTCSeverityMask of the selected DTC, the Dcm
shall call Dem_GetSeverityOfDTC() with the following parameter value:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
c

[SWS_Dcm_01404] dTo retrieve the DTCFunctionalUnit of the selected DTC, the Dcm
shall call Dem_GetFunctionalUnitOfDTC() with the following parameter value:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
c

[SWS_Dcm_01405] dTo retrieve the statusOfDTC of the selected DTC, the Dcm shall
call Dem_GetStatusOfDTC() with the following parameter value:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
c

[SWS_Dcm_01226] dIf Dem_GetFunctionalUnitOfDTC() returns DEM_WRONG_DTC

or DEM_WRONG_DTCORIGIN, the Dcm shall send a NRC 0x31 (requestOut-
OfRange).c

[SWS_Dcm_01240] dIf Dem_GetSeverityOfDTC() returns DEM_WRONG_DTC, the

Dcm shall send a NRC 0x31 (requestOutOfRange)c

[SWS_Dcm_01406] dIf Dem_GetStatusOfDTC() returns DEM_WRONG_DTC or

DEM_WRONG_DTCORIGIN, the Dcm shall send a NRC 0x31 (requestOutOfRange).c

122 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.2.5.5 Subfunctions 0x06/0x19

The UDS Service 0x19 with subfunction 0x06 or 0x19 requests a specific Extended
Data Records for a specific DTC. The service request contains the parameters:
• DTCMaskRecord
• DTCExtendedDataRecordNumber

[SWS_Dcm_01547] Read user defined memory extended data record authentica-

tion check
Upstream requirements: RS_Diag_04233

dOn reception of the UDS Service ReadDTCInformation (0x19) with sub-function re-
portUserDefMemoryDTCExtDataRecordByDTCNumber (0x19), the Dcm shall check
if the access to the selected user defined memory in parameter MemorySelection is
authenticated and read the DTC information only if:
• a DcmDspReadDTCInformationUserDefinedFaultMemoryRoleRef is
configured with DcmDspReadDTCInformationUserDefinedFaultMem-
oryId matching the MemorySelection and the verification according to
[SWS_Dcm_01522] was successful or
• the active white list on that connection has an entry for that requested user de-
fined memory selection.
c

According to [SWS_Dcm_01537] the authentication checks are only executed if

DcmDspAuthentication is configured. In case of a failed authentication the NRC han-
dling is according to [SWS_Dcm_01485] and [SWS_Dcm_01544] applies.

[SWS_Dcm_00386] dUpon reception of UDS Service 0x019 with subfunction 0x06 or

0x19, the Dcm shall retrieve from the Dem the stored extended data records for the
requested DTC and origin.c

[SWS_Dcm_00295]
Upstream requirements: RS_Diag_04058

dWhen responding to UDS Service 0x19 with subfunction 0x06 or 0x19, the Dcm module
shall calculate the statusOfDTC by first calling Dem_SelectDTC() with the parameters
values set according to [SWS_Dcm_01649] and then Dem_GetStatusOfDTC() with
ClientId = Client Id for this Dcm instance (see DcmDemClientRef).c

[SWS_Dcm_01649] Dem_SelectDTC() parameters values for subfunctions 0x06

and 0x19 d

123 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

reportDTCExtendedData reportUserDefMemoryDTC
RecordByDTCNumber ExtDataRecord
ByDTCNumber
0x06 0x19
ClientId Client Id for this Dcm instance Client Id for this Dcm instance
(see DcmDemClientRef) (see DcmDemClientRef)
DTC DTCMaskRecord from DTCMaskRecord from
request request
DTCOrigin PRIMARY_MEMORY MemorySelection from
request + 0x0100

[SWS_Dcm_00841] dIf Dem_GetNextExtendedDataRecord() returns E_OK and Buf-

Size 0 (empty buffer), the Dcm module shall omit the DTCExtendedDataRecordNumber
for the related record in the response of service 0x19 0x06/0x19.c

[SWS_Dcm_00382] dWhen responding to UDS Service 0x19 with subfunction 0x06

or 0x19, the Dcm module shall calculate the DTCExtendedDataRecord by first call-
ing Dem_SelectExtendedDataRecord() with the parameter values set according to
[SWS_Dcm_01650] and then call Dem_GetNextExtendedDataRecord() repeatedly un-
til DEM_NO_SUCH_ELEMENT is returned.c

[SWS_Dcm_01650] Dem_SelectExtendedDataRecord() parameters values for

subfunctions 0x06 and 0x19 d
report reportUserDefMemory
DTCExtendedDataRecord DTCExtDataRecord
ByDTCNumber ByDTCNumber
0x06 0x19
ClientId Client Id for this Dcm instance Client Id for this Dcm instance
(see DcmDemClientRef) (see DcmDemClientRef)
DTC DTCMaskRecord from DTCMaskRecord from
request request
DTCOrigin PRIMARY_MEMORY Memory Selection from
request + 0x0100
ExtendedDataNumber DTCExtendedData DTCExtendedData
RecordNumber from request RecordNumber from request

The Dcm module shall obtain the size of the extended data record by using
Dem_GetSizeOfExtendedDataRecordSelection().

124 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.2.5.6 Subfunction 0x03

UDS Service 0x19 with subfunction 0x03 allows an external tester to request all stored
snapshot records for all DTCs in an ECU.

[SWS_Dcm_01640] Support of UDS Service 0x19 with subfunction 0x03

Upstream requirements: RS_Diag_04250

dThe Dcm shall support UDS Service 0x19 with subfunction 0x03 according to ISO
14229-1:2020 [9].c

When using paged buffer mechanism, in some case, it’s possible that the number of
DTC matching the filter change between the calculation of the total size, needed for
the first page transmission, and the sending of the further pages. For this reason, the
requirement [SWS_Dcm_00587] and [SWS_Dcm_00588] define the behavior in these
situations.

7.4.2.5.7 Subfunctions 0x04 and 0x18

Using UDS Service 0x19 with subfunction 0x04 or 0x18, an external tester can request
snapshot record data for one or all snapshot records of a specific DTC.
To process the UDS Service 0x19 04 or 0x19 18, the Dcm supports the option to process
the entire service BSW internally while interacting with the Dem and the option to leave
the service processing to an external service processor.

[SWS_Dcm_01623] Use of internal service processor to read snapshot records

Upstream requirements: RS_Diag_04180, RS_Diag_04205

dIf a DcmDsdService for service 0x19 with a DcmDsdSubService for subfunction

0x04 or 0x18 is configured and DcmDsdSubServiceFnc is not configured for that
service, the Dcm shall process the diagnostic request according to ISO 14229-1 [1].c

[SWS_Dcm_01624] Use of external service processor to read snapshot records

Upstream requirements: RS_Diag_04205

dIf a DcmDsdService for service 0x19 with a DcmDsdSubService for subfunction

0x04 or 0x18 is configured and DcmDsdSubServiceFnc is configured for that service,
the Dcm shall leave the processing of the diagnostic request to the external service
processor provided in DcmDsdSubServiceFnc.c

125 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Figure 7.10: Request DTC Snapshot Record by Snapshot Record Number

[SWS_Dcm_01546] Read user defined memory snapshot record authentication

check
Upstream requirements: RS_Diag_04233

dOn reception of the UDS Service ReadDTCInformation (0x19) with sub-function re-
portUserDefMemoryDTCSnapshotRecordByDTCNumber (0x18), the Dcm shall check
if the access to the selected user defined memory in parameter MemorySelection is
authenticated and read the DTC information only if:
• a DcmDspReadDTCInformationUserDefinedFaultMemoryRoleRef is
configured with DcmDspReadDTCInformationUserDefinedFaultMem-
oryId matching the MemorySelection and the verification according to
[SWS_Dcm_01522] was successful or
• the active white list on that connection has an entry for that requested user de-
fined memory selection.
c

According to [SWS_Dcm_01546] the authentication checks are only executed if

DcmDspAuthentication is configured. In case of a failed authentication the NRC han-
dling is according to [SWS_Dcm_01485] and [SWS_Dcm_01551] applies.

126 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.2.5.8 Subfunction 0x05

UDS Service 0x19 with subfunction 0x05 allows an external tester to request Freeze-
Frame information for a specific FreezeFrame record number. The service request
contains parameter:
• DTCStoredDataRecordNumber
Due to Dem limitation, the diagnostic service $19 05 is limited to the OBD legislative
freeze frame.

[SWS_Dcm_00632] dOn reception of service 0x19 with subfunction 0x05, if the record
number of the diagnostic request is different from 0x00, the Dcm module shall send a
negative response with NRC 0x31 (request out of range).c

[SWS_Dcm_00574] dWhen sending a positive response to UDS Service 0x19 with

subfunction 0x05 and DTCStoredDataRecordNumber is 0x00, the Dcm module shall
use the data in the response message according to [SWS_Dcm_01651].c

[SWS_Dcm_01651] Subfunction 0x05 response values d

Parameter name Value
DTCStoredDataRecordNumber DTCStoredDataRecordNumber from request (0x00)
DTCAndStatusRecord DTC according to [SWS_Dcm_01193], statusOfDTC
according to [SWS_Dcm_00389]
DTCStoredDataRecordNumberOfIden- As defined in [SWS_Dcm_00388]
tifiers / DTCStoredDataRecord

[SWS_Dcm_00388]
Upstream requirements: RS_Diag_04058

dWhen responding to UDS Service 0x19 with subfunction 0x05 and DTCStored-
DataRecordNumber is 0x00, the Dcm shall compose the OBD Freezeframe by looping
all DcmDspPid and collecting all DcmDspPidData which are configured for service
0x02 by calling Dem_DcmReadDataOfOBDFreezeFrame() for the Data Element. The
Dcm shall compose the DidId by adding 0xF400 to the Pid, and calculate padding and
supported informations.c

[SWS_Dcm_01193] dWhen responding to UDS Service 0x19 with subfunc-

tion 0x05 and DTCStoredDataRecordNumber is 0x00, the Dcm shall call
Dem_DcmGetDTCOfOBDFreezeFrame() with FrameNumber 0x00 and DTCFormat
DEM_DTC_FORMAT_UDS to retrieve the DTC of the provided FreezeFrame.c

127 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00389]
Upstream requirements: RS_Diag_04058

dWhen responding to UDS Service 0x19 with subfunction 0x05 and DTCStored-
DataRecordNumber is 0x00, the Dcm module shall obtain the status of the DTC by
first calling Dem_SelectDTC() with the following parameters:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
• DTC: DTC as defined in [SWS_Dcm_00388]
• DTCOrigin: DEM_DTC_ORIGIN_PRIMARY_MEMORY
and then Dem_GetStatusOfDTC() with the following parameter:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
c

7.4.2.5.9 Subfunctions 0x0B, 0x0C, 0x0D and 0x0E

An external test tool can request the first occurred or most recent failed or confirmed
DTC and associated status, by sending the UDS Service request 0x19 including one of
the following sub-functions 0x0B, 0x0C, 0x0D, 0x0E

[SWS_Dcm_00392] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x0B, 0x0C, 0x0D or 0x0E, the Dcm module shall use the data in the response
message according to [SWS_Dcm_01652].c

[SWS_Dcm_01652] Subfunctions 0x0B, 0x0C, 0x0D and 0x0E response values d

Parameter name Value
DTCStatusAvailabilityMask DTCStatusAvailabilityMask
DTCAndStatusRecord The DTC is obtained according to [SWS_Dcm_00466], the
StatusOfDtc is obtained according to [SWS_Dcm_00393]

[SWS_Dcm_00393]
Upstream requirements: RS_Diag_04058

dFor the purpose of responding to UDS Service 0x19 with subfunctions 0x0B,
0x0C, 0x0D or 0x0E, the Dcm module shall obtain the StatusOfDtc by calling
Dem_GetStatusOfDTC() with the following parameter values:
• ClientId :Client Id for this Dcm instance (see DcmDemClientRef
• DTC: the DTC value as defined in [SWS_Dcm_00466]

128 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• DTCOrigin: DEM_DTC_ORIGIN_PRIMARY_MEMORY
c

[SWS_Dcm_00466] dFor the purpose of responding to UDS Service 0x19 with

subfunctions 0x0B, 0x0C, 0x0D or 0x0E, the Dcm shall obtain the DTC with
Dem_GetDTCByOccurrenceTime() using the parameter values according to Table
[SWS_Dcm_01653].c

[SWS_Dcm_01653] Dem_GetDTCByOccurrenceTime() parameters values for

subfunctions 0x0B, 0x0C, 0x0D and 0x0E d
reportFirstTest reportFirst reportMost reportMost
FailedDTC ConfirmedDTC RecentTest Recent
FailedDTC ConfirmedDTC
0x0B 0x0C 0x0D 0x0E
ClientId Client Id for this Client Id for this Client Id for this Client Id for this
Dcm instance Dcm instance Dcm instance Dcm instance
(see DcmDem- (see DcmDem- (see DcmDem- (see DcmDem-
ClientRef) ClientRef) ClientRef) ClientRef)
DTCRequest DEM_FIRST_ DEM_FIRST_ DEM_MOST_ DEM_MOST_
FAILED_DTC DET_ RECENT_ REC_DET_
CONFIRMED_ FAILED_DTC CONFIRMED_
DTC DTC

[SWS_Dcm_00766] dIf the Dcm received DEM_NO_SUCH_ELEMENT by calling

Dem_GetDTCByOccurrenceTime it shall reply with a positive response and empty DT-
CAndStatusRecord.c

7.4.2.5.10 Subfunction 0x14

An external test tool may request an ECU to report the FaultDetectionCounter for all
DTCs with a "Prefailed" status, by sending a UDS Service request 0x19 with subfunction
0x14.

[SWS_Dcm_00464] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x14, the Dcm module shall use the data in the response message according
to [SWS_Dcm_01654].c

[SWS_Dcm_01654] Subfunction 0x14 response values d

Parameter name Value
DTC The DTC is obtained according from the call to
Dem_GetNextFilteredDTCAndFDC()

129 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Parameter name Value

DTCFaultDetectionCounter The DTCFaultDetectionCounter is obtained according
from the call to Dem_GetNextFilteredDTCAndFDC()

[SWS_Dcm_00465]
Upstream requirements: RS_Diag_04058

dWhen responding to UDS Service 0x19 with subfunctions 0x14, the Dcm module
shall obtain the DTCFaultCounter of every DTCs with status "prefailed" by repeat-
edly calling Dem_GetNextFilteredDTCAndFDC() after having configured the filter with
Dem_SetDTCFilter() using the parameter values according to [SWS_Dcm_01655].c

[SWS_Dcm_01655] Dem_GetNextFilteredDTCAndFDC() parameters values for

subfunctions 0x14 d
Parameter name Value
ClientId Client Id for this Dcm instance (see DcmDemClientRef)
DTCStatusMask 0x00
DTCFormat DEM_DTC_FORMAT_UDS
DTCOrigin PRIMARY_MEMORY
FilterWithSeverity FALSE
DTCSeverityMask Not relevant
FilterForFaultDetectionCounter TRUE

[SWS_Dcm_00681] dThe Dcm module shall obtain the number of records

that will be found using Dem_GetNextFilteredDTCAndFDC() by using
Dem_GetNumberOfFilteredDTC().c

[SWS_Dcm_00519] dThe calls to Dem_SetDTCFilter() with parameter FilterForFault-

DetectionCounter set to YES shall be done in the context of the Dcm_MainFunctionc

This allows the implementation to calculate the total size of the response before cycling
through the DTCs.
When using paged buffer mechanism, in some case, it’s possible that the number of
DTC matching the filter change between the calculation of the total size, needed for
the first page transmission, and the sending of the further pages. For this reason, the
requirement [SWS_Dcm_00587] and [SWS_Dcm_00588] shall be considered for the
implementation of this subservice.

130 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01232] dIf Dem_GetNextFilteredDTCAndFDC() returns

DEM_NO_SUCH_ELEMENT and at least one matching element could be retrieved
before, the Dcm shall send a positive response including these data elements.c

[SWS_Dcm_01233] dIf Dem_GetNextFilteredDTCAndFDC() returns

DEM_NO_SUCH_ELEMENT and no matching element could be retrieved before, the
Dcm shall send a positive response only for service and subservice.c

7.4.2.5.11 Subfunction 0x1A

UDS Service 0x19 with subfunction 0x1A request the Dcm to retrieve all DTCs that sup-
port an extended data record.

[SWS_Dcm_01607] Support of UDS Service 0x19 with subfunction 0x1A

Upstream requirements: RS_Diag_04250

dThe Dcm shall support UDS Service 0x19 with subfunction 0x1A according to ISO
14229-1:2020 [9].c

To retrieve the DTCs that support an extended data record, the Dem provides the API
Dem_SetDTCFilterByExtendedDataRecordNumber that allows to set a filter for an ex-
tended data record. Subsequent calls to Dem_GetNextFilteredDTC provide the re-
quested data.
The positive response consists of an enumeration of DTC number and DTC status. The
Dcm does not define any specific order in which the DTCs are reported in the positive
response message.

[SWS_Dcm_01608] Positive response of UDS Service 0x19 with subfunction 0x1A

Upstream requirements: RS_Diag_04250

dIf one or more extended data record is/are supported for the requested DTCExt-
DataRecordNumber, the Dcm shall send a positive response including all DTCs and
the DTC status.c

[SWS_Dcm_01609] Negative response of UDS Service 0x19 with subfunction

0x1A
Upstream requirements: RS_Diag_04250

dIf no extended data record is supported for the requested DTCExtDataRecordNum-

ber, the Dcm shall send a negative response with NRC 0x31 (RequestOutOfRange).c

131 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.2.5.12 Subfunction 0x42

UDS Service 0x19 with subfunction 0x42 requests WWH OBD DTCs matching a DTC
status mask a severity mask record. The service request contains the following pa-
rameters:
• FunctionalGroupIdentifier
• DTCSeverityMask
• DTCStatusMask

[SWS_Dcm_01129] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x42, the Dcm module shall use the data in the response message according
to [SWS_Dcm_01656].c

[SWS_Dcm_01656] Subfunction 0x42 response values d

Parameter name Value
FunctionalGroupIdentifier 0x33
DTCStatusAvailabilityMask Dem_GetDTCStatusAvailabilityMask
DTCSeverityAvailabilityMask Dem_GetDTCSeverityAvailabilityMask
DTCFormatIdentifier Dem_GetTranslationType (limited to values 0x04 and
0x02)
DTCAndSeverityRecord As defined in [SWS_Dcm_01130]

[SWS_Dcm_01130] dWhen responding to UDS Service 0x19 with subfunction

0x42, the Dcm module shall obtain the DTCAndSeverityRecords by repeatedly call-
ing Dem_GetNextFilteredDTCAndSeverity() after having configured the filter with
Dem_SetDTCFilter() using the parameter values according to [SWS_Dcm_01657].c

[SWS_Dcm_01657] Dem_GetNextFilteredDTCAndSeverity() parameters values

for subfunctions 0x42 d
Parameter name Value
ClientId Client Id for this Dcm instance (see DcmDemClientRef)
DTCStatusMask DTCStatusMask from request
DTCFormat DEM_DTC_FORMAT_UDS
DTCOrigin DEM_DTC_ORIGIN_OBD_RELEVANT_MEMORY
FilterWithSeverity TRUE
DTCSeverityMask DTCSeverityMask from request
FilterForFaultDetectionCounter FALSE

132 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01131] dThe return values of Dem_GetNextFilteredDTCAndSeverity

shall be filled according to [SWS_Dcm_01658].c

[SWS_Dcm_01658] Dem_GetNextFilteredDTCAndSeverity return values d

Parameter name Value
DTCSeverity DTCSeverity
DTCHighByte (MSB) DTC (high byte)
DTCMiddleByte DTC (middle byte)
DTCLowByte DTC (low byte)
statusOfDTC DTCStatus

Note: The Dcm module can get an indication of the number of records
that will be found using Dem_GetNextFilteredDTCAndSeverity() by using
Dem_GetNumberOfFilteredDTC().

7.4.2.5.13 Subfunction 0x55

With UDS Service 0x19 with sub-function 0x55 a client can retrieve a list of OBD
DTCs with the "permanent DTC" status. The service request contains the following
parameter:
• FunctionalGroupIdentifier

[SWS_Dcm_01345] dWhen sending a positive response to UDS Service 0x19 with sub-
function 0x55, the Dcm module shall use the following data in the response message
according to [SWS_Dcm_01659].c

[SWS_Dcm_01659] Subfunction 0x55 response values d

Parameter name Value
FunctionalGroupIdentifier 0x33
DTCStatusAvailabilityMask Dem_GetDTCStatusAvailabilityMask
DTCFormatIdentifier Dem_GetTranslationType (limited to values 0x04 and
0x02)
DTCAndStatusRecord As returned by Dem_GetNextFilteredDTC()

Note : When responding to UDS Service 0x19 with sub-function 0x55, the
Dcm module could obtain the DTCAndStatusRecords by repeatedly calling
Dem_GetNextFilteredDTC() after having configured the filter with Dem_SetDTCFilter()
using the parameter values according to [SWS_Dcm_01660].

133 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01660] Dem_SetDTCFilter() parameters values for subfunction 0x55

d
Parameter name Value
ClientId See DcmDemClientRef
DTCStatusMask 0x00
DTCFormat DEM_DTC_FORMAT_UDS
DTCOrigin DEM_DTC_ORIGIN_PERMANENT_MEMORY
FilterWithSeverity FALSE
DTCSeverityMask Not relevant
FilterForFaultDetectionCounter FALSE

The Dcm module can get an indication of the number of records that will be found using
Dem_GetNextFilteredDTC() by using Dem_GetNumberOfFilteredDTC().

[SWS_Dcm_01346] dWhen responding to UDS Service 0x19 with sub-function

0x55 and Dem_GetTranslationType returns a Dem_DTCTranslationFormatType
different to 0x02 (DEM_DTC_TRANSLATION_SAEJ1939_73) or 0x04
(DEM_DTC_TRANSLATION_J2012DA_FORMAT_04), the Dcm module shall re-
turn NRC 0x10 (generalReject).c

7.4.2.5.14 Subfunction 0x56

UDS Service 0x19 with subfunction 0x56 request the Dcm to retrieve all DTCs that are
assigned to an DTC readiness group identifier.

[SWS_Dcm_01610] Support of UDS Service 0x19 with subfunction 0x56

Upstream requirements: RS_Diag_04250

dThe Dcm shall support UDS Service 0x19 with subfunction 0x56 according to ISO
14229-1:2020 [9].c

To retrieve the DTCs that are assigned to an DTC readiness group, the Dem provides
the API Dem_SetDTCFilterByReadinessGroup that allows to set a filter for a readiness
group. Subsequent calls to Dem_GetNextFilteredDTC provide the requested data.
The positive response consists of an enumeration of DTC number and DTC status. The
Dcm does not define any specific order in which the DTCs are reported in the positive
response message.

134 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01611] Positive response of UDS Service 0x19 with subfunction 0x56

Upstream requirements: RS_Diag_04250

dIf one or more DTCs support the requested DTC readiness group identifier, the Dcm
shall send a positive response including all DTCs and the DTC status.c

[SWS_Dcm_01612] Negative response of UDS Service 0x19 with subfunction 0x56

Upstream requirements: RS_Diag_04250

dIf no DTC supports the requested DTC readiness group, the Dcm shall send a negative
response with NRC 0x31 (requestOutOfRange).c

7.4.2.6 Service 0x22 - ReadDataByIdentifier

[SWS_Dcm_00253] dThe Dcm module shall implement the UDS Service ReadDataByI-
dentifier (0x22)c

[SWS_Dcm_01335] dOn reception of the UDS Service ReadDataByIdentifier (0x22), if

the number of requested DID exceeds the configured maximum number of data identi-
fiers (refer to configuration parameter DcmDspMaxDidToRead), the Dcm module shall
send NRC 0x13 (Incorrect message length or invalid format)c

With UDS Service 0x22, the tester can request the value of one or more DIDs.

[SWS_Dcm_01548] Read UDS DID authentication check

Upstream requirements: RS_Diag_04233

dOn reception of the UDS Service ReadDataByIdentifier (0x22), the Dcm shall check
if the access to all requested DIDs outside the range 0xF200-0xF8FF is authenticated
and read the data identifiers only if:
• for that read DID a role is configured via DcmDspDidReadRoleRef and the ver-
ification according to [SWS_Dcm_01522] was successful or
• the active white list on that connection has for each requested DID one entry with
read access that matches that DID.
c

[SWS_Dcm_01549] Read Dynamically defined DID authentication check

Upstream requirements: RS_Diag_04233

dOn reception of the UDS Service ReadDataByIdentifier (0x22), the Dcm shall check
for all requested DIDs inside the range 0xF200-0xF3FF if the content is based of DIDs
or parts of DIDs that are authenticated and read the data identifiers only if:

135 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• for those read DIDs a role is configured via DcmDspDidReadRoleRef and the
verification according to [SWS_Dcm_01522] was successful or
• the active white list on that connection has for each requested DID one entry with
read access that matches those DIDs.
c

According to [SWS_Dcm_01537] the authentication checks are only executed if

DcmDspAuthentication is configured. In case of a failed authentication the NRC han-
dling is according to [SWS_Dcm_01544] and [SWS_Dcm_01551] applies.

[SWS_Dcm_00438] dOn reception of the UDS Service ReadDataByIdentifier (0x22)

, for every requested DID the Dcm module shall check if the DID is supported (see
configuration parameter DcmDspDid and DcmDspDidRange) If none of the requested
DIDs is supported, the Dcm module shall send NRC 0x31 (Request out of range).c

[SWS_Dcm_00651] dOn reception of the UDS Service ReadDataByIdentifier (0x22)

with DID in the range 0xF200 to 0xF3FF, the Dcm module shall check if the DID can be
dynamically defined (the DcmDspDidInfo it references has the DcmDspDidDynami-
callyDefined set to true). If yes, if this DID has not been dynamically defined yet by
calls to the DynamicallyDefineDataIdentifier (0x2C) service, i.e. it has no data sources
defined, the Dcm module shall send NRC 0x31 (Requestout of range)c

[SWS_Dcm_00652] dOn reception of the UDS Service ReadDataByIdentifier (0x22)

with DID in the range 0xF200 to 0xF3FF, if verification has been successfully done (see
[SWS_Dcm_00651]) and the dynamic DID has been defined with a DID source (see
[SWS_Dcm_00646]), the Dcm module shall use the configuration of this DID source to
read the data.c

[SWS_Dcm_00864] dOn reception of the UDS Service ReadDataByIdentifier (0x22)

with DID in the range 0xF200 to 0xF3FF, if verification has been successfully done
(see [SWS_Dcm_00651]) and the dynamic DID has been defined with a DID source
(see [SWS_Dcm_00646]), the Dcm module shall do the session, security and mode
dependencies checks for all source DIDs in case the configuration parameter DcmD-
spDDDIDcheckPerSourceDID is set to TRUE.c

[SWS_Dcm_00865] dIn case the configuration parameter DcmDspDDDIDcheckPer-

SourceDID is set to FALSE, there is no session, security or mode dependencies check
for the source DIDs.c

Note: In case there is a need to validate the session or security dependencies always,
the DDDID should be cleared by any security and session transitions.

136 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00653] dOn reception of the UDS Service ReadDataByIdentifier (0x22)

with DID in the range 0xF200 to 0xF3FF, if verification has been successfully done (see
[SWS_Dcm_00651]) and the dynamic DID has been defined with a memory address
(see [SWS_Dcm_00646]), the Dcm module shall use the callout Dcm_ReadMemory to
read the data.c

[SWS_Dcm_00561] dIf a DID is set as unused (DcmDspDidUsed set to FALSE), the

Dcm shall consider the DID as not supported (according to [SWS_Dcm_00438])c

[SWS_Dcm_00433] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID the Dcm module shall check if the DID has a Read access con-
figured (see configuration parameter DcmDspDidRead in DcmDspDidInfo). If none
of the DID has a Read access, the Dcm module shall send NRC 0x31 (Request out of
range).c

[SWS_Dcm_00434] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID the Dcm module shall check if the DID can be read in the
current session (see configuration parameter DcmDspDidReadSessionRef). If none
of the DID can be renden in the current session, the Dcm module shall send a NRC
0x31 (RequestOutOfRange).c

[SWS_Dcm_00435] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID the Dcm module shall check if the DID can be read in the cur-
rent security level (see configuration parameter DcmDspDidReadSecurityLevel-
Ref). If not, the Dcm module shall send NRC 0x33 (Security access denied).c

[SWS_Dcm_00819] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID the Dcm module shall check if the DID can be read in the
current mode condition (according to the configuration parameter DcmDspDidRead-
ModeRuleRef). If not, the Dcm module shall send the calculated negative response of
the referenced DcmModeRule.c

[SWS_Dcm_00439] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID outside the OBD range (F400-F8FF), the Dcm module shall
request the application if the DID can be read by calling the configured func-
tion (if parameter DcmDspDataUsePort set to USE_DATA_SYNCH_FNC or USE_-
DATA_ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ERROR or USE_DATA_SYNCH_-
FNC_PROXY or USE_DATA_ASYNCH_FNC_PROXY; see configuration parameter DcmD-
spDataConditionCheckReadFnc) on each data of the DID or call the associated
ConditionCheckRead operation (if parameter DcmDspDataUsePort set to USE_-
DATA_SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_CLIENT_SERVER_ERROR). If not (one function returns E_NOT_OK) ,

137 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

the Dcm module shall send a negative response with NRC set to value from the pa-
rameter "ErrorCode" of DcmDspDataConditionCheckReadFnc function or Condi-
tionCheckRead operation.c

Note: This requirement exceeds the standard ConditionCheck behavior as described

by ISO 14229-1 ”NRC handling for ReadDataByIdentifier service” , because it is not
restricted to use NRC 0x22 in a negative response.

[SWS_Dcm_00440] dIf the requested DID references other DID using DcmDsp-
DidRef, the Dcm module shall process the verification and the reading of every ref-
erenced DID and concatenate the response data without any gaps based on the se-
quence in the configuration.c

[SWS_Dcm_CONSTR_06023] DcmDspDidRef shall not reference the same DID

reference twice dDcmDspDid container shall not include the same DcmDspDidRef
parameters more than once.c

[SWS_Dcm_CONSTR_06057] Dependency for DcmDspDataEcuSignal dDcmDsp-

DataEcuSignal shall be only present if DcmDspDataUsePort is set to USE_ECU_-
SIGNAL.c

[SWS_Dcm_CONSTR_06058] Dependency for DcmDspDataEndianness dIn case

DcmDspDataEndianness is not configured, the DcmDspDataDefaultEndianness
shall be used instead.c

[SWS_Dcm_CONSTR_06061] Dependency for DcmDspDataReadDataLengthFnc

dDcmDspDataReadDataLengthFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR or
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY
c

[SWS_Dcm_CONSTR_06062] Dependency for DcmDspDataReadFnc dDcmDsp-

DataReadFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR or

138 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY or

• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY
c

[SWS_Dcm_01385] dIf the DID dataRecord has bytes, not defined by any data ele-
ment, the Dcm shall fill these bytes with the value 0x00.c

[SWS_Dcm_01431] dIf the configuration parameter DcmDspDidSize is configured,

the Dcm shall enforce the DID data to have the configured size.c

[SWS_Dcm_01587] Atomic BndM read operation

Upstream requirements: RS_Diag_04243

dAfter all verification (see [SWS_Dcm_00433], [SWS_Dcm_00434],

[SWS_Dcm_00435], [SWS_Dcm_00436]) the Dcm module shall get for every re-
quested DID with DcmDspDidUsePort set to USE_ATOMIC_BNDM and outside
the OBD range (F400-F8FF) the data values by reading the data from the associated
BlockId from the BndM (DcmDspDidBndMBlockIdRef) using the block specific
reading function BndM_GetBlockPtr_<BlockId.Shortname>.c

7.4.2.6.1 UDS DID

[SWS_Dcm_00578] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID outside the OBD range (F400-F8FF), after all verifica-
tion (see [SWS_Dcm_00433], [SWS_Dcm_00434] and [SWS_Dcm_00435]), If the
data is configured as a "ECU signal" of the IoHwAb (parameter DcmDspDataUse-
Port), the Dcm shall call the Api IoHwAb_Dcm_Read<EcuSignalName >() (param-
eter DcmDspDataReadEcuSignal) to get the Data. In this case, the requirements
[SWS_Dcm_00439], [SWS_Dcm_00436] and [SWS_Dcm_00437] shall not apply.c

[SWS_Dcm_00436] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID outside the OBD range (F400-F8FF), the Dcm module
shall for each signal (DcmDspDidSignal) with a dynamic data length (DcmD-
spDataType is set to UINT8_DYN): call either the configured function DcmDsp-
DataReadDataLengthFnc (if parameter DcmDspDataUsePort set to USE_DATA_-
SYNCH_FNC or USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ERROR or
USE_DATA_SYNCH_FNC_PROXY or USE_DATA_ASYNCH_FNC_PROXY) or the associ-
ated ReadDataLength operation (if parameter DcmDspDataUsePort set to USE_-
DATA_SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_CLIENT_SERVER_ERROR) to get the data length in byte.c

139 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00437] dAfter all verification (see [SWS_Dcm_00433],

[SWS_Dcm_00434], [SWS_Dcm_00435] and [SWS_Dcm_00436]) the Dcm mod-
ule shall get for every requested DID outside the OBD range (F400-F8FF), all the data
values by calling all the configured function (if parameter DcmDspDataUsePort set
to USE_DATA_SYNCH_FNC or USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_-
FNC_ERROR or USE_DATA_SYNCH_FNC_PROXY or USE_DATA_ASYNCH_FNC_PROXY;
see configuration parameter DcmDspDataReadFnc) or call all the associated
ReadData operations (if parameter DcmDspDataUsePort set to USE_DATA_-
SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_CLIENT_SERVER_ERROR) or read all the associated SenderReceiver
interfaces (if parameter DcmDspDataUsePort set to USE_DATA_SENDER_RECEIVER
or to USE_DATA_SENDER_RECEIVER_AS_SERVICE).c

[SWS_Dcm_01432] dAfter all verification (see [SWS_Dcm_00433],

[SWS_Dcm_00434], [SWS_Dcm_00435] and [SWS_Dcm_00436]) the Dcm module
shall get for every requested DID with DcmDspDidUsePort set to USE_ATOMIC_-
SENDER_RECEIVER_INTERFACE, USE_ATOMIC_SENDER_RECEIVER_INTER-
FACE_AS_SERVICE or USE_ATOMIC_NV_DATA_INTERFACE and outside the OBD
range (F400-F8FF) the data values by reading the associated sender-receiver or
NvDataInterface DataServices_{DID}.c

[SWS_Dcm_00638] dTo serialize the required AUTOSAR data types (signed- and un-
signed integer) into the response message of ReadDataByIdentifier responses, the
target endianness configured in DcmDspDataEndianness shall be considered for
DcmDspData elements having DcmDspDataUsePort set to USE_DATA_SENDER_-
RECEIVER, USE_DATA_SENDER_RECEIVER_AS_SERVICE, USE_ECU_SIGNAL.c

[SWS_Dcm_CONSTR_06070] Dependency for DcmDspDataEndianness dIn case

DcmDspDataEndianness is not present, the DcmDspDataDefaultEndianness
shall be used instead.c

7.4.2.6.2 OBD DID

[SWS_Dcm_00481] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID inside the OBD range (F400-F4FF), the Dcm module
shall get the DID value as defined for OBD Service $01 (see [SWS_Dcm_00407],
[SWS_Dcm_00408], [SWS_Dcm_00621], [SWS_Dcm_00622], [SWS_Dcm_00623],
[SWS_Dcm_00944] and [SWS_Dcm_00718] ), if DcmDspEnableObdMirror is set
to true.c

140 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00482] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID inside the OBD Monitor range (F600-F6FF), the Dcm mod-
ule shall get the DID value as defined for OBD Service $06 (see [SWS_Dcm_00957],
[SWS_Dcm_00958], and [SWS_Dcm_00956])c

[SWS_Dcm_00483] dOn reception of the UDS Service ReadDataByIdentifier (0x22),

for every requested DID inside the OBD InfoType range (F800-F8FF), the Dcm module
shall get the DID value as defined for OBD Service $09 (see [SWS_Dcm_00422] and
[SWS_Dcm_00423] without including the number of data items within the response, if
DcmDspEnableObdMirror is set to true.c

[SWS_Dcm_01195] dIf DcmDspEnableObdMirror is set to true, an explicitly config-

ured DID inside the OBD range (F400-F4FF) and the OBD InfoType range (F800-F8FF)
shall use the UDS interface.c

[SWS_Dcm_01197] dIf DcmDspEnableObdMirror is set to FALSE, all requests

within the OBD DID range shall use the UDS interface.c

If DcmDspEnableObdMirror is set to FALSE ([SWS_Dcm_01197]) or the DID is ex-

plicitly configured inside the OBD PID range (F400-F4FF) ([SWS_Dcm_01195]), the
access to the OBD data shall be given in the following way:

[SWS_Dcm_01379] dOn reception of an UDS Service ReadDataByIdentifier (0x22)

request with only ”availability OBDDataIdentifier” as parameter, the Dcm shall respond
with the corresponding supported (=configured) DIDs in the OBD range (F400-F4FF).c

[SWS_Dcm_01380] dOn reception of an UDS Service ReadDataByIdentifier (0x22) re-

quest with only OBDDataIdentifier that are not ”availability OBDDataIdentifier”, the
Dcm shall obtain the current value of these OBDDataIdentifier by invoking the con-
figured Xxx_ReadData() functions for every data of the OBDDataIdentifier and shall
return these values as response to Service 0x22.c

[SWS_Dcm_01382] dIf an OBDDataIdentifier contains support information (presence

of DcmDspDidDataSupportInfo container), the Dcm shall add the support informa-
tion in the diagnostic response.c

[SWS_Dcm_01383] dIf an OBDDataIdentifier contains support information (presence

of DcmDspDidDataSupportInfo container), the Dcm shall calculate the support in-
formation value according to the available data for this DID: for every DcmDspData
container existing for this DID, the associated support information bits, referenced in
DcmDspDidDataSupportInfo, shall be set to one.c

141 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01384] dWhen responding to UDS Service ReadDataByIdentifier (0x22)

with OBDDataIdentifier, the Dcm shall put fill-bytes between DcmDspData in the OBD-
DataIdentifier whenever content bytes are missing, in order to fit to the DID size (see
configuration parameter DcmDspDidSize).c

[SWS_Dcm_01386] dTo serialize the required AUTOSAR data types (signed and
unsigned integer) into the response message of ReadDataByIdentifier (0x22) OBD-
DataIdentifier responses the target endianness configured in DcmDspDataEndian-
ness shall be considered for DcmDspData elements having DcmDspDataUsePort
set to {USE_DATA_SENDER_RECEIVER, USE_DATA_SENDER_RECEIVER_AS_SER-
VICE, USE_ECU_SIGNAL}. In case DcmDspDataEndianness is not present, the
DcmDspDataDefaultEndianness shall be used instead.c

If DcmDspEnableObdMirror is set to FALSE or the DID is explicitly configured inside

the OBD InfoType range (F800-F8FF), the access to the OBD data shall be given in the
following way:

[SWS_Dcm_01387] dOn reception of an UDS Service ReadDataByIdentifier (0x22)

request with one or more ”availability OBDInfoTypeDataIdentifier” as parameter, the
Dcm module shall respond with the corresponding supported (=configured) DIDs in the
OBD range (F800-F8FF).c

[SWS_Dcm_01389] dOn reception of an UDS Service ReadDataByIdentifier (0x22)

request with an OBDInfoTypeDataIdentifier that is not an ”availability OBDInfoType-
DataIdentifier”, the Dcm module shall obtain the value of this OBDInfoTypeDataIdenti-
fier by invoking all the configured Xxx_ReadData() function for every data of this OBD-
InfoTypeDataIdentifier and shall return the value as response to Service 0x22.c

7.4.2.7 Service 0x24 - ReadScalingDataByIdentifier

[SWS_Dcm_00258] dThe Dcm module shall implement the UDS Service ReadScaling-
DataByIdentifier (0x24)c

To obtain scaling information, the tester can invoke UDS Service 0x24 with the 2-byte
DID as parameter. The configuration of the Dcm contains for each configured DID:
• The 2-byte DID (see configuration parameter DcmDspDidIdentifier)
• For every data of the DID :
• The function GetScalingInformation (see configuration parameters DcmDsp-
DataGetScalingInfoFnc and DcmDspDataUsePort)

142 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• The length of the ScalingInfo returned by the GetScalingInformation function (see

configuration parameter DcmDspDataScalingInfoSize)

[SWS_Dcm_00394] dOn reception of a request for UDS Service ReadScalingByIden-

tifier, the Dcm module shall call every function Xxx_GetScalingInformation() configured
for everay data of the DID received in the request and return the data received in the
responsec

[SWS_Dcm_01601] dIn the context of [SWS_Dcm_00490], the Dcm shall place the
received scaling information for every data of a DcmDspDid in the same order as
specified by DcmDspDidByteOffset.c

[SWS_Dcm_CONSTR_06060] Dependency for DcmDspDataGetScalingInfoFnc

dDcmDspDataGetScalingInfoFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR or
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY
c

7.4.2.8 Service 0x27 - SecurityAccess

[SWS_Dcm_00252]
Upstream requirements: RS_Diag_04005

dThe Dcm module shall implement the UDS Service SecurityAccess (0x27)c

The purpose of this service is to provide a means to access data and/or diagnostic
services, which have restricted access for security, emissions, or safety reasons.

[SWS_Dcm_00321] dIf the request length is correct, the DSP submodule shall check
if the requested subfunction value (access type) is configured in the ECU (see con-
figuration parameter DcmDspSecurityLevel). If the requested subfunction value is
not configured, the DSP submodule shall trigger a negative response with NRC 0x12
(SubFunction not supported).c

143 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00323] dIf the requested subfunction value is configured and a service

with subfunction type "requestSeed "(= odd value) has been received and if the re-
quested access type is already active (see Dcm_GetSecurityLevel), the DSP sub-
module shall set the seed content to 0x00.c

[SWS_Dcm_00324] dIn the other case than the one described in [SWS_Dcm_00323]
(access type is not active or "send key" request), if DcmDspSecurityUsePort is
set to USE_ASYNCH_CLIENT_SERVER, the DSP submodule shall call the configured
operation Xxx_GetSeed() (in case "request seed" is received) or Xxx_CompareKey()
(in case "send key" is received).c

[SWS_Dcm_00862] dOn reception of the UDS Service SecurityAccess (0x27) with sub-
function type "requestSeed" and if the requested access type is not already active, the
Dcm module shall request a seed by calling the configured Xxx_GetSeed() function (if
the configuration parameter DcmDspSecurityUsePort is set to USE_ASYNCH_FNC,
refer to configuration parameter DcmDspSecurityGetSeedFnc).c

Note : If the static seed mechanism is used, the processing needs to be done by the
application implementing the Xxx_GetSeed() and Xxx_CompareKey() functions.

[SWS_Dcm_CONSTR_06077] Dependency for DcmDspSecurityGetSeedFnc d

DcmDspSecurityGetSeedFnc shall be present only if DcmDspSecurityUsePort
is set to USE_ASYNCH_FNC.c

[SWS_Dcm_00863] dOn reception of the UDS Service SecurityAccess (0x27) with

subfunction type "sendKey", if the requested access type is not already active and
if the "request seed" for the related access type was executed successfully, the
Dcm module shall request the result of a key comparison by calling the configured
Xxx_CompareKey() function (if the configuration parameter DcmDspSecurityUse-
Port is set to USE_ASYNCH_FNC, refer to configuration parameter DcmDspSecuri-
tyCompareKeyFnc).c

[SWS_Dcm_CONSTR_06075] Dependency for DcmDspSecurityCompareKeyFnc

dDcmDspSecurityCompareKeyFnc shall be configured only if DcmDspSecuri-
tyUsePort is set to USE_ASYNCH_FNC.c

The following list gives as an example, which errors can be detected by the security
access service and stored in the error code information:
• RequestSequenceError (NRC 0x24), when invalid access type is send at "send
key",
• RequiredTimeDelayNotExpired (NRC 0x37), when time delay is active (see con-
figuration parameter DcmDspSecurityDelayTime),

144 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• ExceededNumberOfAttempts (NRC 0x36), when number of attempts to get secu-

rity access reaches or exceeds the configured limit (see configuration parameter
DcmDspSecurityNumAttDelay), and
• InvalidKey (NRC 0x35), when invalid key is send at "send key".

[SWS_Dcm_00325] dIf the operation CompareKey() returns E_OK, the DSP submod-
ule shall set the new access type with DslInternal_SetSecurityLevel()(see the conver-
sion formula given in ECUC_Dcm_00754 DcmDspSecurityLevel).c

[SWS_Dcm_01397]
Upstream requirements: RS_Diag_04005

dIf Xxx_CompareKey() returns value DCM_E_COMPARE_KEY_FAILED and DcmD-

spSecurityNumAttDelay is configured, the Dcm shall increment the attempt counter
of the security level for which the sendKey subfunction request failed.c

[SWS_Dcm_00660] dIf Xxx_CompareKey() returns value

DCM_E_COMPARE_KEY_FAILED and if the number of failed attempts to enter
the requested security level (AttemptCounter) is less than the value configured for
the DcmDspSecurityNumAttDelay parameter of the requested security level, the
Dcm module shall send a negative response with NRC 0x35 (InvalidKey) and shall not
change the Dcm internal security level. Note: if DcmDspSecurityNumAttDelay
parameter is not configured, the number of failed attempts to enter the requested
security level (AttemptCounter) is not considered.c

[SWS_Dcm_01349] dIf Xxx_CompareKey() returns value

DCM_E_COMPARE_KEY_FAILED and if the number of failed attempts to enter
the requested security level (AttemptCounter) is greater or equal than the value con-
figured for the DcmDspSecurityNumAttDelay parameter of the requested security
level, the Dcm module shall start the SecurityDelayTimer with the value configured in
DcmDspSecurityDelayTime for the SecurityLevel which was requested in the failed
request, send a negative response with NRC 0x36 (exceededNumberOfAttempts) and
shall not change the Dcm internal security level.c

[SWS_Dcm_01150] dIf Xxx_CompareKey() returns value E_NOT_OK, the Dcm mod-

ule shall send a negative response with NRC code equal to the ErrorCode parameter
value and shall not increment the attempt counter or change the Dcm internal security
level.c

[SWS_Dcm_01350] dWhile the SecurityDelayTimer of SecurityLevel is not yet

elapsed, the Dcm module shall send a negative response with NRC 0x37 (required-
TimeDelayNotExpired) on a SecurityAccess (0x27) requestSeed subfunction request
for that Security Level.c

145 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00659] dIf Xxx_GetSeed() returns value E_NOT_OK, the Dcm module

shall send a negative response with NRC code equal to the ErrorCode parameter
value.c

7.4.2.9 Service 0x28 - CommunicationControl

[SWS_Dcm_00511] dThe Dcm module shall implement the CommunicationControl

(service 0x28) of the Unified Diagnostic Services.c

[SWS_Dcm_00512] dOn invocation of the sent confirmation function of the UDS Ser-
vice CommunicationControl (0x28) from DSD with the subnet parameter of the request
equal to 0x00, the Dcm shall do for each NetworkHandle (see DcmDspAllComMChan-
nelRef) which is configured in DcmDspComControlAllChannel:
1. trigger the mode switch Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype to the mode corresponding the communicationType and con-
trolType parameter from the CommunicationControl request.
2. call the Api BswM_Dcm_CommunicationMode_CurrentState with the parameters
NetworkHandleType and Dcm_CommunicationModeType corresponding to the
communicationType and controlType parameter from the CommunicationControl
request (see Dcm_CommunicationModeType definition).
c

[SWS_Dcm_00785] dOn invocation of the sent confirmation function of the UDS Ser-
vice CommunicationControl (0x28) from DSD with the subnet parameter of the request
equal to 0x0F(CommunicationControl on the network which request is received on),
the Dcm shall do for the NetworkHandle (see DcmDslProtocolComMChannelRef) of
the current received DcmDslProtocolRxPduRef:
1. trigger the mode switch Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype to the mode corresponding to the communicationType and
controlType parameter from the CommunicationControl request.
2. call the Api BswM_Dcm_CommunicationMode_CurrentState with the parameters
NetworkHandleType and Dcm_CommunicationModeType corresponding to the
communicationType and controlType parameter from the CommunicationControl
request (see Dcm_CommunicationModeType definition)
c

[SWS_Dcm_00786] dOn invocation of the sent confirmation function of the UDS Ser-
vice CommunicationControl (0x28) from DSD with the subnet parameter of the request
between 0x01 and 0x0E, the Dcm shall check if the received subnet parameter (see

146 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspSubnetNumber) is supported. In case it is not supported a NegativeResponse

code 0x31 shall be sent. In case it is supported the Dcm shall do for the correspond-
ing NetworkHandle (see DcmDspSpecificComMChannelRef) of the received subnet
parameter (see DcmDspSubnetNumber):
1. trigger the mode switch Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype to the mode corresponding the communicationType and con-
trolType parameter from the CommunicationControl request.
2. call the Api BswM_Dcm_CommunicationMode_CurrentState the parameters Net-
workHandleType and with Dcm_CommunicationModeType corresponding the
communicationType and controlType parameter from the CommunicationControl
request (see Dcm_CommunicationModeType definition)
c

For some use-cases the Dcm may re-enable the CommunicationControl due to external
changed mode conditions:

[SWS_Dcm_00753] dIn case that the referenced ModeRule (see ECUC_Dcm_00943)

is not fulfilled anymore for a NetworkHandle which is currently in a state other than
DCM_ENABLE_RX_TX_NORM_NM, the Dcm shall:
1. switch the mode group Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype toDCM_ENABLE_RX_TX_NORM_NM
2. call BswM_Dcm_CommunicationMode_CurrentState with the parameters Net-
workHandleType set to the corresponding NetworkHandle of the network and
RequestedCommunicationMode set to DCM_ENABLE_RX_TX_NORM_NM
c

[SWS_Dcm_00860] dFor a NetworkHandle which is currently in a state other than

DCM_ENABLE_RX_TX_NORM_NM if the Dcm is transitioning to default session or
upon any diagnostic session change where the new session does not support UDS
Service CommunicationControl anymore, the Dcm shall:
1. switch the mode group Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype to DCM_ENABLE_RX_TX_NORM_NM
2. call BswM_Dcm_CommunicationMode_CurrentState with the parameters Net-
workHandleType set to the corresponding NetworkHandle of the network and
RequestedCommunicationMode set to DCM_ENABLE_RX_TX_NORM_NM
c

147 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Note: the NetworkHandles to be considered are all ComM channels which are refer-
enced from either DcmDspSpecificComMChannelRef, DcmDspAllComMChannel-
Ref or DcmDspComControlSubNodeComMChannelRef.

[SWS_Dcm_01077] dIf a CommunicationControl Request with the sub-function "en-

ableRxAndDisableTxWithEnhancedAddressInformation" is received, the Dcm shall
check the "nodeIdentification-Number" listed as DcmDspComControlSubNodeId and
for the referenced network (see DcmDspComControlSubNodeComMChannelRef ), it
shall do the followings:
1. trigger the mode switch Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype to the mode corresponding the communicationType and con-
trolType parameter from the CommunicationControl request.
2. call the Api BswM_Dcm_CommunicationMode_CurrentState with the parameters
NetworkHandleType and Dcm_CommunicationModeType corresponding to the
communicationType and controlType parameter from the CommunicationControl
request (see Dcm_CommunicationModeType definition).
The analogue controlType enableRxAndDisableTx shall be used with the the following
existing Dcm_CommunicationModeType values:
• DCM_ENABLE_RX_DISABLE_TX_NORM
• DCM_ENABLE_RX_DISABLE_TX_NM
• DCM_ENABLE_RX_DISABLE_TX_NORM_NM.
c

[SWS_Dcm_01078] dThe Dcm shall trigger a negative response with NRC 0x31
(RequestOutOfRange), if a CommunicationControl Request with the sub-function
"enableRxAndDisableTxWithEnhancedAddressInformation" and a "nodeIdentification-
Number" which is not listed as DcmDspComControlSubNodeId is received.c

[SWS_Dcm_01079] dIf a CommunicationControl Request with the sub-function "en-

ableRxAndTxWithEnhancedAddressInformation" is received, the Dcm shall check the
"nodeIdentification-Number" listed as DcmDspComControlSubNodeId and for the
referenced network (see DcmDspComControlSubNodeComMChannelRef ) it shall
do the followings:
1. trigger the mode switch Dcm_CommunicationControl_<Network> ModeDeclara-
tionGroupPrototype to the mode corresponding the communicationType and con-
trolType parameter from the CommunicationControl request.
2. call the Api BswM_Dcm_CommunicationMode_CurrentState with the parameters
NetworkHandleType and Dcm_CommunicationModeType corresponding to the
communicationType and controlType parameter from the CommunicationControl
request (see Dcm_CommunicationModeType definition).

148 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

The analogue controlType enableRxAndTx shall be used with this the following existing
Dcm_CommunicationType values :
• DCM_ENABLE_RX_TX_NORM
• DCM_ENABLE_RX_TX_NM
• DCM_ENABLE_RX_TX_NORM_NM.
c

[SWS_Dcm_01080] dThe Dcm shall trigger a negative response with NRC 0x31 (Re-
questOutOfRange), if a CommunicationControl Request with the sub-function "en-
ableRxAndTxWithEnhancedAddressInformation" and a "nodeIdentification-Number"
which is not listed as DcmDspComControlSubNodeId is received.c

[SWS_Dcm_01081] dIf DcmDspComControlSubNodeUsed is set to FALSE the sub-

system (DcmDspComControlSubNode) is not available in this configuration.c

[SWS_Dcm_01082] dIf DcmDspComControlSubNodeUsed is set to TRUE the sub-

system (DcmDspComControlSubNode) is available in this configuration.c

Note : Condition checks (i.e. NRC 22 checks) on CommunicationType and NetworkType

as well as check of CommunicationType support (i.e. NRC 0x31 check for Communi-
cationType) are not directly supported by the Dcm. Supplier/manufacturer notifications
can be used.

7.4.2.10 Service 0x29 - Authentication

The UDS service Authentication (0x29) is used to provide dynamic means to control
the access to diagnostic services. Execution of certain diagnostic services might have
impact on safety, emissions or the vehicle. Controlling the access to diagnostic ser-
vices via certificates provide means to control the access to diagnostic services after
production. The access to these resources can be limited in time or bound to certain
vehicles or ECUs only. AUTOSAR Dcm provides an out of the box solution for authen-
ticated diagnostics with a given semantics of the UDS service Authentication. Even
ISO14229-1 [9] leaves more freedom, the Dcm will use only the functionality specified
in this chapter. Further interpretations, certificate types or certificate content are out of
scope of the AUTOSAR Dcm module.

[SWS_Dcm_01559] Support of UDS service authentication

Upstream requirements: RS_Diag_04230

dThe Dcm shall implement the UDS service Authentication (0x29) for sub-functions:
• deAuthenticate

149 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• verifyCertificateUnidirectional
• verifyCertificateBidirectional
• proofOfOwnership
• authenticationConfiguration
c

Note: AUTOSAR Dcm only implements the authentication via PKI certificated ex-
change. Authentication with challenge-response (ACR) is out of scope of AUTOSAR.
If it is required it needs a full custom implementation using existing Dcm callouts for
custom service processing.

[SWS_Dcm_01551] NRC Handling for UDS service authentication

Upstream requirements: RS_Diag_04230

dThe Dcm shall follow the NRC handling as defined for ISO 14229-1:2018 for UDS
service authentication. This includes the NRC codes as well as the order of individual
NRC checks.c

[SWS_Dcm_CONSTR_06091] Authentication configuration dThe presence of a

DcmDsdService with DcmDsdSidTabServiceId set to 0x29, requires a configured con-
tainer DcmDspAuthentication on DcmDsp.c

[SWS_Dcm_CONSTR_06092] Authentication per connection dThe presence of

a DcmDsdService with DcmDsdSidTabServiceId set to 0x29, requires a configured
DcmDspAuthenticationConnection per configured connection DcmDslConnection.c

[SWS_Dcm_CONSTR_06093] One authentication configuration per connection

dEach DcmDspAuthenticationConnection shall refer a different DcmDslMainConnec-
tion by the reference in DcmDspAuthenticationConnectionMainConnectionRef.c

The Dcm is using the Csm and KeyM for certificate management. Parsing the certifi-
cate is a potential time-consuming operation and needs to be executed asynchronous.
There are opinions that security shall not reveal any cause of failed authentication and
thus have no dedicated NRCs for different certificate failures. To respect this use case
the Dcm provides a general security NRC handling.

150 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01560] Use of generic NRC for invalid certificate or content

Upstream requirements: RS_Diag_04230

dIf the mode referenced by DcmDspAuthenticationGeneralNRCModeRuleRef evalu-

ates to true, the Dcm shall send the NRC code given in DcmDspAuthenticationGener-
alNRC instead of the specific NRC codes in all situation where a Certificate verification
failed - NRC is returned.c

[SWS_Dcm_CONSTR_06094] Generic NRC configuration requirements

Upstream requirements: RS_Diag_04230

dIf DcmDspAuthenticationGeneralNRCModeRuleRef is configured the parameter

DcmDspAuthenticationGeneralNRC shall also be configured.c

7.4.2.10.1 De-authentication

The de-authenticate sub-function shall be always available if service 0x29 is used. This
service set the authentication state to deauthenticated for the diagnostic connection the
request was received on.

[SWS_Dcm_CONSTR_06095] dThe presence of a DcmDsdService with DcmDsd-

SidTabServiceId set to 0x29, requires a DcmDsdSubService on this DcmDsdService
with DcmDsdSubServiceId set to deAuthenticate.c

[SWS_Dcm_01561] Deauthentication by diagnostic service request

Upstream requirements: RS_Diag_04230

dOn reception of an Authentication (0x29) service with sub-function equal to de-

authenticate, the Dcm shall set the authentication state to deauthenticated on the con-
nection the Dcm has received that request.c

[SWS_Dcm_01565]
Upstream requirements: RS_Diag_04230

dOn reception of an Authentication (0x29) service with sub-function equal to de-

Authenticate, the Dcm shall reply with a positive response having the authentication-
ReturnParameter set to DeAuthentication successful.c

151 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.2.10.2 Verify Certificates

[SWS_Dcm_01459] Supported communicationConfiguration

Upstream requirements: RS_Diag_04230

dOn reception of an Authentication (0x29) service with sub-function equal to verifyC-

ertificateUnidirectional or verifyCertificateBidirectional, the Dcm shall reply with an NRC
0x31 (requestOutOfRange) if the communicationConfiguration (COCO) parameter has
a value different than 0x00.c

The support of a COCO with constant value of 0x00 implies that no session key is
supported by the Dcm. Upon receiving an authentication request with sub-function ver-
ifyCertificateUniDirectional and the communicationConfiguration (COCO) set to 0x00,
the Dcm starts to verify the certificate. This service is implemented on BSW level by in-
tention, to reduce the possible dialects of service 0x29 to what is natively supported by
AUTOSAR. The Csm [17] and KeyM [18] modules allow to use different cryptographic
methods. It is part of the Dcm strategy to explicitly require that certificates and all kind
of access to information inside are handled by the Csm and its configuration. This
allows to map different kind of certificates with different levels of security to the Dcm,
thus abstracting the certificate complexity from Dcm.

[SWS_Dcm_01460] Verify verifyCertificateUnidirectional message length check

Upstream requirements: RS_Diag_04230

dOn reception of an Authentication (0x29) service with sub-function equal to verifyCer-

tificateUnidirectional, the Dcm shall verify that the message length fits to the size given
in the parameters lengthOfCertificateClient and return a NRC 0x13 if the size does not
match.c

[SWS_Dcm_01461] Verify verifyCertificateBidirectional message length check

Upstream requirements: RS_Diag_04230

dOn reception of an Authentication (0x29) service with sub-function equal to verifyCer-

tificateBidirectional, the Dcm shall verify that the message length fits to the size given
in the parameters lengthOfCertificateClient and lengthOfChallengeClient and return a
NRC 0x13 if the size does not match. The Dcm uses the lengthOfCertificateClient as
offset to calculate the position of lengthOfChallengeClient.c

[SWS_Dcm_01462] Required configuration for bidirectional authentication dIf

the sub-function verifyCertificateBidirectional is configured in the DsdServiceSubFunc-
tion for 0x29, the configuration parameters DcmDspAuthenticationECUCertifi-
cateRef and DcmDspAuthenticationECUCertificateKeyElementRef are re-
quired.c

152 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01579] Mandatory certificate data

Upstream requirements: RS_Diag_04230

dOn reception of an Authentication (0x29) service with sub-function equal to verifyC-

ertificateUnidirectional or verifyCertificateBidirectionaland a lengthOfCertificateClient
equal to zero, the Dcm shall respond with NRC 0x13 (incorrectMessageLengthOrIn-
validFormat)..c

Store certificate in Csm

[SWS_Dcm_01463] Certificate validation

Upstream requirements: RS_Diag_04230

dOn reception of an Authentication (0x29) service with sub-function equal to verifyCer-

tificateUnidirectional or verifyCertificateBidirectional, the Dcm shall use the KeyM API
KeyM_SetCertificate to store the client certificate from the service request within the
KeyM module. The following parameter values shall be used:
• CertificateId = DcmDspAuthenticationConnectionCertificateRef ->
KeyMCertificate.KeyMCertificateId
• certificateDataPtr.certData = Pointer to certificateClient from Request
• certificateDataPtr.certDataLength = lengthOfCertificateClient from Request
c

Diagnostic certificate configuration is a task that is mainly executed in the Csm and
KeyM modules. The Dcm provides an abstraction from these modules and only keeps
symbolic references to containers that keep the information. Please take attention
while configuring the Csm and KeyM ’in spirit of Dcm certificates’.

[SWS_Dcm_01464] Invalid certificate size failure

Upstream requirements: RS_Diag_04230

dIf the API KeyM_SetCertificate returns KEYM_E_SIZE_MISMATCH, the Dcm shall

return the NRC 0x13 (incorrectMessageLengthOrInvalidFormat).c

[SWS_Dcm_01465] Behavior on busy crypto operation

Upstream requirements: RS_Diag_04230

dIf any of the Csm or KeyM APIs called by the Dcm is returning CRYPTO_E_BUSY or
KEYM_E_BUSY, the Dcm shall return the NRC 0x21 (busyRepeat).c

153 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01466] Csm APIs returning failure code behavior

Upstream requirements: RS_Diag_04230

dThroughout this chapter the Csm or KeyM are used to process the authentication
requests. These APIs have return values for failures. Unless there is no dedicated
requirement for a given return value and if the return value is different to E_OK, the
Dcm shall return a NRC 0x10 ’GeneralReject’.c

The cryptographic operations have potential long execution times and are called asyn-
chronously.

[SWS_Dcm_01467] Asynchronous certificate operation handling

Upstream requirements: RS_Diag_04230

dFor all asynchronous Csm or KeyM operations, the Dcm shall wait until the call-
back has been called, indicating a successful job termination. If the result (e.g.
KeyM_CertificateStatusType) is E_OK, the Dcm shall continue to process the 0x29 re-
quest, if the result is different to E_OK, the Dcm shall skip the further processing and
return a negative response with NRC ’GeneralReject’.c

Parse and Verify certificate in Csm

[SWS_Dcm_01468] Verifying client certificate

Upstream requirements: RS_Diag_04230

dAfter the Dcm has set the certificate according to [SWS_Dcm_01463], the Dcm shall
verify the certificate by calling KeyM_VerifyCertificate with the following parameters:
• CertificateId = DcmDspAuthenticationConnectionCertificateRef ->
KeyMMCertificate.KeyMCertificateId
c

[SWS_Dcm_01469] Behavior on failed certificate verification

Upstream requirements: RS_Diag_04230

dAfter the Dcm has verified a certificate and KeyM_CertificateStatusType is set to

KEYM_E_CERTIFICATE_SIGNATURE_FAIL, the Dcm shall send a negative response
with NRC set to ’Certificate verification failed - Invalid Signature’.c

[SWS_Dcm_01470] Check certificate chain of trust

Upstream requirements: RS_Diag_04235

dIf the operation started in [SWS_Dcm_01468] returns a result of

KEYM_E_CERTIFICATE_INVALID_CHAIN_OF_TRUST, the Dcm shall refuse the
client certificate and return a negative response with NRC ’Certificate verification failed
- Invalid Chain of Trust’.c

154 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01471] Check certificate type

Upstream requirements: RS_Diag_04235

dIf the operation started in [SWS_Dcm_01468] returns a result of

KEYM_E_CERTIFICATE_INVALID_TYPE, the Dcm shall refuse the client certifi-
cate and return a negative response with NRC ’Certificate verification failed - Invalid
Type’.c

[SWS_Dcm_01472] Check certificate format

Upstream requirements: RS_Diag_04235

dIf the operation started in [SWS_Dcm_01468] returns a result of

KEYM_E_CERTIFICATE_INVALID_FORMAT, the Dcm shall refuse the client cer-
tificate and return a negative response with NRC ’Certificate verification failed - Invalid
Format’.c

[SWS_Dcm_01473] Check certificate content

Upstream requirements: RS_Diag_04235

dIf the operation started in [SWS_Dcm_01468] returns a result of

KEYM_E_CERTIFICATE_INVALID_CONTENT, the Dcm shall refuse the client
certificate and return a negative response with NRC ’Certificate verification failed -
Invalid Content’.c

Note: While most of the KeyM return values can be mapped 1:1 on UDS NRC values, this
does not apply for KEYM_E_CERTIFICATE_INVALID_CONTENT. An invalid content
from KeyM indicates that a key element verification has failed. A failed key element
verification means that the certificate itself is valid, but the KeyM refuses the certificate
as the data does not fit to the server’s required value. In UDS this is expressed by
’Certificate verification failed - Invalid Scope’. As result invalid content from KeyM will
trigger the NRC invalid scope.

[SWS_Dcm_01475] Check certificate validity

Upstream requirements: RS_Diag_04235

dIf the operation started in [SWS_Dcm_01468] returns a result of

KEYM_E_CERTIFICATE_REVOKED, the Dcm shall refuse the client certificate
and return a negative response with NRC ’Certificate verification failed - Invalid
Certificate (revoked)’.c

[SWS_Dcm_01476] Check certificate valid until

Upstream requirements: RS_Diag_04235

dIf the operation started in [SWS_Dcm_01468] returns a result of

KEYM_E_CERTIFICATE_VALIDITY_PERIOD_FAIL, the Dcm shall refuse the client
certificate and return a negative response with NRC ’Certificate verification failed -
Invalid Time Period’.c

155 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Providing the server challenge

The Dcm uses the Csm to create a server challenge by returning a random value.

[SWS_Dcm_01588] Length of server challenge

Upstream requirements: RS_Diag_04230

dThe Dcm shall create a server challenge with the length configured in DcmDspAu-
thenticationEcuChallengeLength.c

[SWS_Dcm_01493] Creating the server challenge

Upstream requirements: RS_Diag_04230

dAfter successfully validating the client certificate in [SWS_Dcm_01463], the Dcm shall
create a server challenge by using the Csm in the following sequence:
1) Call of Csm_RandomGenerate with parameters
a. jobId : DcmDspAuthenticationRandomJobRef -> CsmJobId
2) Wait until the asynchronous job has terminated according to [SWS_Dcm_01467].
c

The API Csm_RandomGenerate requires an initialised random generator. The initial-

ization of the random generator is a task of the system (integrator).

[SWS_Dcm_01621] dIf calculation of server challenge fails i.e Csm_RandomGenerate

returns CRYPTO_E_ENTROPY_EXHAUSTED, the Dcm shall send NRC 0x59 (Chal-
lenge calculation failed).c

[SWS_Dcm_01503] Sending positive response on verifyCertificateUniDirectional

Upstream requirements: RS_Diag_04230

dIf the Dcm has successfully calculated server challenge the Dcm shall send a positive
response for the verifyCertificateUniDirectional request with the following parameter
values:
authenticationReturnParameter : ’Certificate verified, Ownership verification neces-
sary’
lengtfOfChallengeServer: length of the challenge generated in [SWS_Dcm_01493]
challengeServer: challenge generated in [SWS_Dcm_01493]
lengthOfEphemeralPublicKeyServer: 0x0000
c

Processing a diagnostic request verifyCertificateBidirectional will furthermore require

the Dcm to send a server certificate and signing the client challenge. Therefore, the
following steps are done additionally for verifyCertificateBidirectional.

156 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01504] Signing client challenge

Upstream requirements: RS_Diag_04230

dOn reception of an Authentication (0x29) service with sub-function equal to veri-

fyCertificateBidirectional, the Dcm shall sign the received client challenge by calling
Csm_SignatureGenerate with the following parameter values:
jobId: DcmDspAuthenticationClientChallengeSignJobRef -> CsmJobId
mode: CRYPTO_OPERATIONMODE_SINGLECALL
dataPtr: Pointer to challengeClient in request
dataLength: lengthOfChallengeClient from request
resultPtr: Dcm sided buffer to store the proofOfOwnershipServer
resultLengthPtr: Response data for lengthOfProofOfOwnershipServer
c

[SWS_Dcm_CONSTR_06096] Require asynchronous client challenge signing

Upstream requirements: RS_Diag_04230

dDcmDspAuthenticationClientChallengeSignJobRef shall be only accepted

if the referenced CsmJob itself:
• has a CsmProcessingMode set to CRYPTO_PROCESSING_ASYNC
• references a CsmPrimitive with an aggregated CsmSignatureGenerate.
c

[SWS_Dcm_01506] Providing the server certificate

Upstream requirements: RS_Diag_04230

dOn reception of an Authentication (0x29) service with sub-function equal to verifyCer-

tificateBidirectional, the Dcm shall provide the server certificate in the response. The
Dcm shall call KeyM_GetCertificate with the following parameters:
certId: DcmDspAuthenticationECUCertificateRef/KeyMCertificateId
certificateDataPtr: Dcm implementation specific
c

[SWS_Dcm_01507] Server certificate size check

Upstream requirements: RS_Diag_04230

dIf the API KeyM_GetCertificate returns KEYM_E_KEY_CERT_SIZE_MISMATCH

(0x04), the Dcm shall return NRC 0x10 (generalReject).c

[SWS_Dcm_01508] Sending positive response on verifyCertificateBidirectional

Upstream requirements: RS_Diag_04230

dIf the Dcm has successfully calculated client challenge, the server challenge and the
server certificate, the Dcm shall send a positive response for the verifyCertificateBidi-
rectional request with the following parameter values:

157 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

authenticationReturnParameter: ’Certificate verified, Ownership verification neces-

sary’
lengtfOfChallengeServer: length of the challenge generated in [SWS_Dcm_01493]
challengeServer: challenge generated in [SWS_Dcm_01493]
lengthOfCertificateServer: length of the certificated provided in [SWS_Dcm_01506]
certificateServer: certificated provided in [SWS_Dcm_01506]
lengthOfProofOfOwnershipServer: length of proof-of-ownership server created in
[SWS_Dcm_01504]
proofOfOwnershipServer: proof-of-ownership server created in [SWS_Dcm_01504]
lengthOfEphemeralPublicKeyServer: 0x0000
c

7.4.2.10.3 Proof of ownership client

[SWS_Dcm_01509] Sequence check

Upstream requirements: RS_Diag_04230

dOn reception of an Authentication (0x29) service with sub-function equal to proofO-

fOwnership and if on this connection the most recent processed verifyCertificateUni-
directional or verifyCertificateBidirectional service failed or no such sub-function was
processed yet, the Dcm shall send the negative response ’requestSequenceError’. The
connection shall remain in de-authenticated state.c

[SWS_Dcm_01510] Proof of ownership message length check

Upstream requirements: RS_Diag_04230

dOn reception of an Authentication (0x29) service with sub-function equal to proofO-

fOwnership, the Dcm shall verify that the message length fits to the size given in the
parameters lengthOfProofOfOwnershipClient and lengthOfEphemeralPublicKeyClient
and return a NRC 0x13 if the size does not match.c

[SWS_Dcm_01511] Client proof of ownership verification

Upstream requirements: RS_Diag_04230

dOn reception of an Authentication (0x29) service with sub-function equal to proofO-

fOwnership, the Dcm shall verify the client’s proof of ownership data provided in the
request by calling Csm_SignatureVerify with the following in-parameters:
jobId: DcmDspAuthenticationVerifyProofOfOwnerShipClientJobRef ->
CsmJob.CsmJobId
mode: set to CRYPTO_OPERATIONMODE_SINGLECALL
dataPtr: challenge generated [SWS_Dcm_01493]
dataLength: length of the challenge generated in [SWS_Dcm_01493]
signaturePtr: proofOfOwnerShipClient from request

158 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

signatureLength: lengthOfProofOfOwnerShipClient from request

c

[SWS_Dcm_CONSTR_06098] Require asynchronous signature verification d

DcmDspAuthenticationVerifyProofOfOwnerShipClientJobRef is only valid
if the referenced CsmJob itself:
• has a CsmProcessingMode set to CRYPTO_PROCESSING_ASYNC
• references a CsmPrimitive with an aggregated CsmSignatureVerify.
c

[SWS_Dcm_01512] Failed ownership verification

Upstream requirements: RS_Diag_04230

dIf the result of Csm_SignatureVerify from [SWS_Dcm_01511] is

Crypto_VerifyResultType equal to CRYPTO_E_VER_NOT_OK, the Dcm shall send a
negative response with NRC ’Ownership verification failed’.c

[SWS_Dcm_01513] SessionKey support

Upstream requirements: RS_Diag_04230

dUpon sending a positive response for an authentication request with sub-function

equal to proofOfOwnership, the Dcm shall:
• set all bytes of lengthOfSessionKeyInfo to 0x00
• omit the sessionKeyInfo
c

Set current role

[SWS_Dcm_01514] Update the current role

Upstream requirements: RS_Diag_04233

dIf the proof of ownership verification in [SWS_Dcm_01511] was successful and re-
sulted in CRYPTO_E_VER_OK, the Dcm shall use the value read from the certificate
extension DcmDspAuthenticationRoleElementRef as new role for the current
authenticated state.c

[SWS_Dcm_01515] Role size check

Upstream requirements: RS_Diag_04230

dIf the size of the read role information in [SWS_Dcm_01514] is different than the size
in DcmDspAuthenticationRoleSize, the Dcm shall send a negative response with
NRC ’Certificate verification failed - Invalid Content’.c

159 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Set white list

[SWS_Dcm_01516] Update the current whitelist

Upstream requirements: RS_Diag_04232

dIf the proof of ownership verification in [SWS_Dcm_01511] was successful and re-
sulted in CRYPTO_E_VER_OK, the Dcm shall use the white list read from the certifi-
cate according to [SWS_Dcm_01517] as new white list for the current authenticated
state.c

[SWS_Dcm_01517] White list access dTo read the white list from a certificate,
the Dcm shall read all child elements from the referenced DcmDspAuthentica-
tionWhiteListServicesElementRef, DcmDspAuthenticationWhiteList-
DIDElementRef, DcmDspAuthenticationWhiteListRIDElementRef and
DcmDspAuthenticationWhiteListMemorySelectionElementRef certificate
data.c

[SWS_Dcm_01518] White list size check

Upstream requirements: RS_Diag_04230

dIf the size of the read white list information in [SWS_Dcm_01516] is larger
than the size in DcmDspAuthenticationWhiteListServicesMaxSize or
DcmDspAuthenticationWhiteListDIDMaxSize or DcmDspAuthentication-
WhiteListRIDMaxSize or DcmDspAuthenticationWhiteListMaxSize , the
Dcm shall send a negative response with NRC ’Certificate verification failed - Invalid
Content’ (0x25).c

[SWS_Dcm_CONSTR_06087] Required size for white lists

Upstream requirements: RS_Diag_04232

dIf any of the optional DcmDspAuthenticationWhiteListMemorySelec-

tionElementRef are configured, the corresponding DcmDspAuthentication-
WhiteListMemorySelectionMaxSize shall be configured for that white list.c

7.4.2.10.4 Definition and verification of roles

The roles transmitted inside the certificates are used to assign a tester on one con-
nection one or more roles. A single role itself is presented by a certain bit within the
bitfield representation of the role. Within the Dcm there is static role assignment to each
diagnostic service. A service can be executed if at least one role (bit) assigned to a
service matches a role (bit) in the certificate.

160 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_CONSTR_06088] Supported role sizes

Upstream requirements: RS_Diag_04233

dThe parameter DcmDspAuthenticationRoleSize defines the size in bytes used

in both, certificates and ECU internal static role configuration. All role parameters (e.g.
DcmDspServiceRole) shall have values that would fit in the amount of bytes given by
DcmDspAuthenticationRoleSize.c

[SWS_Dcm_01521] Integer interpretation of roles in certificates

Upstream requirements: RS_Diag_04234

dThe Dcm shall interpret all configured role integer values in the little endian format.c

[SWS_Dcm_01522] Role verification

Upstream requirements: RS_Diag_04233, RS_Diag_04234

dUpon each role verification, the Dcm shall make a bitwise ’and’ operation on the value
provided by the role in the certificate for that connection and the role value assigned
to the service. The value that is assigned to the service is calculated by setting all the
bits referred by each DcmDspAuthenticationRow. If the result is greater than 0, the
Dcm shall treat the service as allowed to be executed.c

[SWS_Dcm_01523] Failed role verification

Upstream requirements: RS_Diag_04233, RS_Diag_04234

dUpon each role verification, the Dcm shall make a bitwise ’and’ operation on the role
provided in the certificate for that connection and the role assigned to the service. If
the result is equal to 0, the Dcm shall stop the processing of that service and send a
negative response ’authenticationRequired’.c

An example of roles in certificates and services with assigned certificates is given in

Figure 7.11. The provided certificate uses 1 byte for roles, with 5 role definitions in.
The certificate will grant the tester rights for the roles ’AfterSales’ and ’ExtendedUser’.
With that certificate, the tester can execute the services that have the corresponding
permissions to be executed in that roles. In that example, the service 0x28 and 0x11
01 are both allowed to be executed. The routine with identifier 0x5678 is only allowed
to be executed in role ’production’, the Dcm will deny the execution with NRC ’authenti-
cationRequired’.

161 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Figure 7.11: Example for roles

7.4.2.10.5 Definition and verification of white lists

Besides the use of roles, the certificates can get extended with optional white lists
for service execution. This allows the issuer of the certificate to extend the range of
allowed services without updating the access lists in the ECU.
The white list is build out of the following elements:
• List of allowed services, 1-4 byte each
• List of allowed data identifiers (DID) and access information, 3 byte each
• List of allowed routine identifiers (RID) and access information, 3 byte each
• List of allowed user defined fault memories, 1 byte each
Parsing and access to the different elements of the white lists is done by
invoking KeyM_CertElementGetFirst and KeyM_CertElementGetNext according to
[SWS_Dcm_01517].

[SWS_Dcm_01524] White list for services definition

Upstream requirements: RS_Diag_04233, RS_Diag_04234

dThe white list for services is a set of values, each consisting of up to 4 bytes. Each
value itself contains the first bytes of a diagnostic service that is allowed be executed.c

Example:
In the following example, a white list section within a certificate is shown. It contains 5
additional services that can be executed:

1 ...
2 SEQUENCE (1 elem)
3 SEQUENCE (2 elem)

162 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4 OBJECT IDENTIFIER 3.9.3.345.3.1.3453.24.3.9.355.73

5 SET (6 elem)
6 OCTET STRING (1 byte) 85
7 OCTET STRING (2 byte) 1101
8 OCTET STRING (3 byte) 22123A
9 OCTET STRING (3 byte) 2E123A
10 OCTET STRING (4 byte) 310113F4
11 SEQUENCE (3 elem) ....

This will allow the Dcm to execute:

• Service 0x85 (with any sub-subfunction and DTCSettingControlOptionRecord

byte)
• Service 0x11 01
• Read and WriteDataByIdentifier for DID 0x123A
• Routine Start for RID 0x13F4
Checks for white lists for services are all done at DSD level. The Dcm checks if the first
bytes of a received diagnostic request match the values allowed by the white list. If a
white list entry exists where all bytes are matching the first bytes of the request, the
service is granted access.
For all other white lists, the Dcm performs the checks at DSP level in the corresponding
service processors.
Please note that it is possible to allow a DID execution in two places in the white list: 1)
as 3 byte service and 2) as DID in the DID list. The difference is that the service checks
only the first 3 bytes of the PDU and will not detect the DID being used in multiple DID or
dynamically defined DID requests, while the DID list element is verified in all services
requesting the DID.

[SWS_Dcm_01525] White list definition for DIDs

Upstream requirements: RS_Diag_04233, RS_Diag_04234

dThe white list for DIDs defines the set of data identifiers that are allowed to be read,
written and controlled. Each entry shall contain in the first two bytes the DID number
and in the third byte the following access definitions:
• Bit 0: Read access
• Bit1: Write access
• Bit2: Control access (by InputOutputControlByIdentifier)
A bit value of 0 means that the operation is forbidden, a bit value of 1 means that the
operation is allowed. All not used bits (3-7) shall be set to zero.
DID numbers are always in big endian format (MSB first).c

163 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Example:

DID access record Grants access to

0x1A90 0x01 All read data by identifier operations for DID 0x1A90
0x314F 0x05 All read data by identifier and IOcontrol operations for DID
0x314F

DID read operations are performed from various UDS services. Dcm checks on each
DID read the access to that DID.

[SWS_Dcm_01526] White list definition for RIDs

Upstream requirements: RS_Diag_04233, RS_Diag_04234

dThe white list for RIDs defines the set of routine identifiers that have access to the
sub-functions startRoutine, stopRoutine and requestRoutineResult. Each entry shall
contain in the first two bytes the RID number and in the third byte the following access
definitions:
• Bit 0: Access to sub-function ’startRoutine’
• Bit1: Access to sub-function ’stopRoutine’
• Bit2: Access to sub-function ’requestRoutineResult’
A bit value of 0 means that the sub-function is forbidden, a bit value of 1 means that
the sub-function is allowed. All not used bits (3-7) shall be set to zero.
RID numbers are always in big endian format (MSB first).c

Example:

RID access record Grants access to

0x0240 0x01 StartRoutine is allowed for RID 0x0240
0x028A 0x07 All routine sub-functions are allowed for RID 0x28A

[SWS_Dcm_01527] White list definition for MemorySelection

Upstream requirements: RS_Diag_04233, RS_Diag_04234

dThe white list memory selection is used for the UDS service 0x19 with sub-functions
0x17, 0x18 and 0x19. The value in the white list defines the accepted parameter values
for MemorySelection in the UDS request.c

Transition into authenticated session

164 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01528] Transition into authenticated state

Upstream requirements: RS_Diag_04230

dIf the proof of ownership verification in [SWS_Dcm_01511] was successful and re-
sulted in CRYPTO_E_VER_OK and after the role and white list setting was done, the
Dcm shall set the DcmAuthenticationState_<ConnectionName> on that connection into
DCM_AUTHENTICATED.c

[SWS_Dcm_01529] Successful ownership verification

Upstream requirements: RS_Diag_04230

dIf the result of Csm_SignatureVerify from [SWS_Dcm_01511] is

Crypto_VerifyResultType equal to CRYPTO_E_VER_OK, the Dcm shall send a
positive response with authenticationReturnParameter set to ’Ownership verified,
Authentication complete’ and providing a size of 0 for lengthOfSessionKeyInfo and no
sessionKeyInfo.c

[SWS_Dcm_01530] Persisting authentication state

Upstream requirements: RS_Diag_04230

dIf the result of Csm_SignatureVerify from [SWS_Dcm_01511] is

Crypto_VerifyResultType equal to CRYPTO_E_VER_OK and the mode rule ref-
erenced by DcmDspAuthenticationPersistStateModeRuleRef is evaluated
to true, the Dcm shall persist the authentication state, role and white list on that
connection.c

[SWS_Dcm_01531] Activation of role and white list dThe Dcm shall consider the
role and white list for access control only, if the Dcm is in authenticated state.c

[SWS_Dcm_01532] Re-entering authenticated state

Upstream requirements: RS_Diag_04230

dIf the Dcm is already in authenticated state while a transition to authentication stated
is requested according to [SWS_Dcm_01529], the Dcm shall overwrite the roles and
white list and use only the role and white last from the last received certificate.c

165 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.2.10.6 AuthenticationConfiguration

[SWS_Dcm_01533] Providing the authentication configuration

Upstream requirements: RS_Diag_04230

dIf DcmDspAuthentication is configured and an Authentication (0x29) service with

sub-function equal to authenticationConfiguration is received, the Dcm shall send a pos-
itive response with authenticationReturnParameter set to ’AuthenticationConfiguration
APCE’.c

7.4.2.10.7 TransmitCertificate

The subfunction transmitCertificate (0x4) offers a mechanism to transmit general-

purpose certificates to the ECU. The Dcm does not directly interpret such certificates
but allows the application to use them. In general, the semantics is out of the scope of
the Dcm. Typical examples are:
• Secure coding certificates - authenticates data written by WDBDI
• SecOC certificates
• TLS ECU certficates
• Enhanced diagnostic rights certificates
More than one of these certificates can be supported by the Dcm. The key to identifying
the certificate type is the certificateEvaluationId parameter from the UDS request mes-
sage. A DcmDspAuthenticationTransmitCertificate provides the configura-
tion information on how the certificates are processed and which application callback
is used to inform about successful certificate transmission.

[SWS_Dcm_01681] Support of subfunction transmitCertificate dThe Dcm shall

support the subfunction transmitCertificate of the UDS service Authentication accord-
ing to ISO 14229-1:2020 [9].c

[SWS_Dcm_01682] Verify certificateEvaluationId

Upstream requirements: RS_Diag_04271

dIf the UDS service Authentication (0x29) service with sub-function equal to trans-
mitCertificate is received and the certificateEvaluationId has no configured DcmDspAu-
thenticationTransmitCertificateEvaluationId in any DcmDspAuthenti-
cationTransmitCertificate containers, the Dcm shall return a NRC 0x31 (re-
questOutOfRange).c

166 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

The Dcm uses the KeyM for all certificate management operations. This document does
only mention the KeyM and a configuration reference to a KeyMCertificate. For details
on how the KeyM module is used please read the KeyM SWS document. Be aware that
cryptographic operations have potentially long execution times and are called asyn-
chronously.

[SWS_Dcm_01683] Certificate storage parsing and verification

Upstream requirements: RS_Diag_04271

dThe Dcm shall store, parse, and verify a certificate in the KeyM module, using the
KeyM destination DcmDspAuthenticationTransmitCertificateRef for the re-
ceived certificateEvaluationId.c

After the certificate was processed successfully according to [SWS_Dcm_01683] the

certificate is correctly stored in the server and the application is informed by KeyM
about the existence of a new certificate.

7.4.2.11 Service 0x2A - ReadDataByPeriodicIdentifier

[SWS_Dcm_01613]
Upstream requirements: RS_Diag_04215

dThe Dcm shall support the UDS service ReadDataByPeriodicIdentfier (0x2A) with all
transmissionMode types according to ISO 14229-1:2020 [9].c

[SWS_Dcm_01552] Read Periodic DID authentication check for statically defined

DIDs
Upstream requirements: RS_Diag_04233

dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), the Dcm shall
check if the access to all static defined requested DIDs is authenticated and read the
data identifiers periodically only if:
• a DID read role is configured via DcmDspDidReadRoleRef for that DID and the
verification according to [SWS_Dcm_01522] was successful or
• the active white list on that connection has for each requested DID one entry with
read access that matches that DID.
c

167 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01553] Read Periodic DID authentication check for dynamically de-

fined DIDs
Upstream requirements: RS_Diag_04233

dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), the Dcm shall
check if the access to all dynamically defined requested DIDs if the content is based of
DIDs or parts of DIDs is authenticated and read the data identifiers periodically only if:
• a DID read role is configured via DcmDspDidReadRoleRef for that DID and the
verification according to [SWS_Dcm_01522] was successful or
• the active white list on that connection has for each requested DID one entry with
read access that matches that DID.
c

According to [SWS_Dcm_01537] the authentication checks are only executed if

DcmDspAuthentication is configured. In case of a failed authentication the NRC han-
dling is according to [SWS_Dcm_01544] and [SWS_Dcm_01551] applies.

[SWS_Dcm_00721] Session check for ReadDataByPeriodicIdentifier DID

Upstream requirements: RS_Diag_04215

dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), for every re-
quested periodicDIDs, the Dcm module shall check if the periodicDID can be read in
the current session (see configuration parameter DcmDspDidReadSessionRef). If
none of the periodicDID can be read in the current session, the Dcm module shall send
a NRC 0x31 (RequestOutOfRange).c

[SWS_Dcm_00722] Security level check for ReadDataByPeriodicIdentifier DID

Upstream requirements: RS_Diag_04215

dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), for every re-
quested periodicDIDs, the Dcm module shall check if the periodicDID can be read
in the current security level (see configuration parameter DcmDspDidReadSecu-
rityLevelRef). If not, the Dcm module shall send NRC 0x33 (Security access de-
nied).c

Note: To evaluate the session and security assignements the Dcm evaluates the con-
figuration that is used for ReadDataByIdentifier, e.g. DcmDspDidReadSessionRef or
DcmDspDidReadSecurityLevelRef.

[SWS_Dcm_00820] Mode condition check for ReadDataByPeriodicIdentifier DID

Upstream requirements: RS_Diag_04215

dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), for every

requested periodicDIDs, the Dcm module shall check if the periodicDID can be

168 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

read in the current mode condition (see configuration parameter DcmDspDidRead-

ModeRuleRef). If not, the Dcm module shall send the calculated negative response
code of the reference DcmModeRulec

[SWS_Dcm_01097] Checks for DDDIDs in ReadDataByPeriodicIdentifier

Upstream requirements: RS_Diag_04215

dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), if verifi-

cation has been successfully done ([SWS_Dcm_00721], [SWS_Dcm_00722] and
[SWS_Dcm_00820]), and if the request contains one or more dynamically defined
DID(s), the Dcm module shall do the session, security and mode dependencies checks
for all source data in case the configuration parameter DcmDspDDDIDcheckPer-
SourceDID is set to TRUE.c

[SWS_Dcm_01098] Condition check for ReadDataByPeriodicIdentifier DID

Upstream requirements: RS_Diag_04215

dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), for every re-
quested periodicDIDs, the Dcm module shall invoke the ConditionCheckRead operation
(or the respective C-Function) if configured. In case of a negative result, the returned
ErrorCode shall be used as final negative response code.c

[SWS_Dcm_01099] Support of dynamic length DIDs

Upstream requirements: RS_Diag_04215

dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A), for every re-
quested periodicDIDs, with a configured dynamic length the Dcm module shall invoke
the ReadDataLength operation (or the respective C-Function) to retrieve the length of
the periodicDID. This length is valid for each ReadData operation till the periodicDID is
removed from the scheduler or updated via a new request. This length shall further be
used to check against the UUDT size.c

[SWS_Dcm_00843] Ensuring maxim number of periodic DIDs

Upstream requirements: RS_Diag_04215

dOn reception of the UDS Service ReadDataByPeriodicIdentifier (0x2A),the Dcm mod-

ule shall check if the periodicDataIdentifiers requested in a single request do not
exceed the configured DcmDspMaxPeriodicDidToRead (maximum length check).
Otherwise (in case the number of elements is exceeded) the Dcm module shall send a
NRC 0x13 (Incorrect message length or invalid format).c

[SWS_Dcm_01096] Behavior on unused DIDs

Upstream requirements: RS_Diag_04215

dIf DcmDspDidUsed is set to FALSE, the Dcm shall consider the DID as not sup-
ported.c

169 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.2.11.1 Scheduler PeriodicTransmission

Note: The periodic response message layout is according to ISO 14229-1:2020 [9]. It
contains the periodic data identifier and the data. The service ID and A_PCI byte is
not part of the periodic response message.

[SWS_Dcm_01101]
Upstream requirements: RS_Diag_04215

dThe Dcm shall send all periodic scheduled response by using the configured DcmD-
slPeriodicConnections.c

ISO 14229-1:2020 [9] defines two distinct scheduler types for ReadDataByPeriodicI-
dentifier. Depending on the scheduler type, the Dcm has different transmission strate-
gies. The used scheduler type of the server is selected by setting DcmDspPeriodic-
TransmissionSchedulerType to one of the two types.

[SWS_Dcm_01568] Support of periodic transmission type 1

Upstream requirements: RS_Diag_04215

dIf DcmDspPeriodicTransmissionSchedulerType is set to SCHED-

ULER_TYPE1 and the Dcm is set up to send PDIDs, the Dcm shall trigger the
transmission of all scheduled PDIDs each time the configured periodic transmission
rate elapses.c

[SWS_Dcm_01569] Transmission of one PDID per available connection

Upstream requirements: RS_Diag_04215

dIf PDID transmission is triggered according to [SWS_Dcm_01568], Dcm shall transmit

one PDID per available periodic connection starting with the first PDID in the list of
scheduled PDIDs.c

[SWS_Dcm_01570] Continue in next main function if more PDIDs than available

connections
Upstream requirements: RS_Diag_04215

dIf PDID transmission is triggered according to [SWS_Dcm_01568] and more PDIDs

are to transmit than the number of available periodic connections, the Dcm shall con-
tinue the transmission in the next Dcm main function call. Each time the available
periodic connections shall be used.c

[SWS_Dcm_01571] Overlapping triggers and transmissions

Upstream requirements: RS_Diag_04215

dIf PDID transmission is triggered according to [SWS_Dcm_01568] or

[SWS_Dcm_01572] and the next periodic transmission rate trigger occurs before

170 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

the Dcm has finished sending the scheduled PDIDs according to [SWS_Dcm_01570],
the Dcm shall continue to transmit PDIDs according to [SWS_Dcm_01570] and
schedule the PDIDs of the new trigger after the last previous PDID has been
transmitted.c

[SWS_Dcm_01572] Support of periodic transmission type 2

Upstream requirements: RS_Diag_04215

dIf DcmDspPeriodicTransmissionSchedulerType is set to SCHED-

ULER_TYPE2 the Dcm is set up to send PDIDs and the periodic transmission
rate for a scheduler elapses, the Dcm shall trigger the transmission of the next
scheduled PDIDs on all available periodic connections.c

[SWS_Dcm_01573] PDID transmission sequence for scheduler type 2

Upstream requirements: RS_Diag_04215

dFor scheduler type 2 transmission of PDIDs within a single elapse of the scheduler,
the Dcm shall start to transmit the first configured PDID and continue to transmit con-
secutively all other configured PDIDs. If the last PDID is transmitted, the Dcm restarts
the sequence with the first configured PDID. If a PDID is sent more than once within
a single elapse of the scheduler then the PDIDs contents shall be reloaded with the
applicable DID / Memory data for every re-transmission.c

[SWS_Dcm_01574] Continue in next periodic rate scheduler if more PDIDs than

available connections
Upstream requirements: RS_Diag_04215

dIf a scheduler type 2 PDID transmission is active according to [SWS_Dcm_01572]

and the number of scheduled PDIDs is larger than the number of available periodic
connections, the Dcm shall continue to send the next scheduled PDIDs the next time
the periodic transmission rate scheduler elapses.c

The following example gives an overview about scheduler type 1 and type 2. They use
PDIDs starting at 0xF201 and having all PDID data set to zero. The PDIDs are send
on CAN 2.0, using the CAN-IDs 0x6A0, 0x6A1.
Example 1: Scheduler Type 1
1 SchedulerRate: 1000ms
2

3 PeriodicRate: 4000ms
4
5 NumPeriodicAddr: 1
6
7 NumPDID 2
8

9 1017.02 6A0 01 00 00 00 00 00 00 00
10
11 2016.97 6A0 02 00 00 00 00 00 00 00

171 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

12
13
14
15 5016.87 6A0 01 00 00 00 00 00 00 00
16
17 6016.78 6A0 02 00 00 00 00 00 00 00
18
19
20
21 9016.67 6A0 01 00 00 00 00 00 00 00
22

23 10016.63 6A0 02 00 00 00 00 00 00 00
24
25
26
27 13016.52 6A0 01 00 00 00 00 00 00 00
28

29 14016.46 6A0 02 00 00 00 00 00 00 00

Example 2: Scheduler Type 2

1 SchedulerRate: 1000ms
2
3 PeriodicRate: 4000ms
4

5 NumPeriodicAddr: 1
6
7 NumPDID 2
8
9 945.01 6A0 01 00 00 00 00 00 00 00
10

11 4944.78 6A0 02 00 00 00 00 00 00 00
12
13 8944.66 6A0 01 00 00 00 00 00 00 00
14
15 12944.49 6A0 02 00 00 00 00 00 00 00
16

17 16944.33 6A0 01 00 00 00 00 00 00 00
18
19 20944.28 6A0 02 00 00 00 00 00 00 00
20
21 24944.01 6A0 01 00 00 00 00 00 00 00

Example 3: Aliasing with Scheduler Type 1

1 SchedulerRate: 1000ms
2
3 PeriodicRate: 4000ms
4
5 NumPeriodicAddr: 1
6

7 NumPDID 5
8
9
10 529.89 6A0 01 00 00 00 00 00 00 00
11

172 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

12 1529.70 6A0 02 00 00 00 00 00 00 00
13
14 2529.59 6A0 03 00 00 00 00 00 00 00
15
16 3529.35 6A0 04 00 00 00 00 00 00 00
17

18
19
20 4529.16 6A0 05 00 00 00 00 00 00 00 <-- Alias (should start over at
01)
21

22 5529.02 6A0 01 00 00 00 00 00 00 00
23
24 6529.15 6A0 02 00 00 00 00 00 00 00
25
26 7529.03 6A0 03 00 00 00 00 00 00 00
27

28
29
30 8528.92 6A0 04 00 00 00 00 00 00 00 <-- Alias (should start over at
01)
31
32 9528.82 6A0 05 00 00 00 00 00 00 00
33
34 10528.46 6A0 01 00 00 00 00 00 00 00
35
36 11528.60 6A0 02 00 00 00 00 00 00 00
37
38

39
40 12528.47 6A0 03 00 00 00 00 00 00 00 <-- Alias (should start over at
01)
41
42 13528.36 6A0 04 00 00 00 00 00 00 00
43
44 14528.27 6A0 05 00 00 00 00 00 00 00

Example 4: Scheduler Type 2

1 SchedulerRate: 1000ms
2
3 PeriodicRate: 4000ms
4

5 NumPeriodicAddr: 1
6
7 NumPDID 5
8
9

10 592.03 6A0 01 00 00 00 00 00 00 00
11
12 4591.56 6A0 02 00 00 00 00 00 00 00
13
14 8591.13 6A0 03 00 00 00 00 00 00 00
15

16 12590.69 6A0 04 00 00 00 00 00 00 00
17

173 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

18 16590.26 6A0 05 00 00 00 00 00 00 00
19
20 20589.78 6A0 01 00 00 00 00 00 00 00
21
22 24589.23 6A0 02 00 00 00 00 00 00 00
23

24 28588.90 6A0 03 00 00 00 00 00 00 00
25
26 32588.45 6A0 04 00 00 00 00 00 00 00
27
28 36588.05 6A0 05 00 00 00 00 00 00 00

Example 5: Scheduler 1 with Multiple Periodic Addresses

1 SchedulerRate: 1000ms
2
3 PeriodicRate: 4000ms
4
5 NumPeriodicAddr: 2
6

7 NumPDID 5
8
9
10
11 778.69 6A0 01 00 00 00 00 00 00 00
12
13 778.73 6A1 02 00 00 00 00 00 00 00
14
15
16
17 1778.56 6A0 03 00 00 00 00 00 00 00
18
19 1778.61 6A1 04 00 00 00 00 00 00 00
20
21
22
23 2778.44 6A0 05 00 00 00 00 00 00 00
24
25
26
27 4778.24 6A0 01 00 00 00 00 00 00 00
28
29 4778.27 6A1 02 00 00 00 00 00 00 00
30
31
32
33 5778.08 6A0 03 00 00 00 00 00 00 00
34

35 5778.12 6A1 04 00 00 00 00 00 00 00
36
37
38
39 6778.12 6A0 05 00 00 00 00 00 00 00
40

41
42 8777.90 6A0 01 00 00 00 00 00 00 00

174 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

43
44 8777.93 6A1 02 00 00 00 00 00 00 00
45
46
47
48 9777.70 6A0 03 00 00 00 00 00 00 00
49
50 9777.73 6A1 04 00 00 00 00 00 00 00
51
52
53

54 10777.57 6A0 05 00 00 00 00 00 00 00

Example 6: Scheduler 2 with Multiple Periodic Addresses

1 SchedulerRate: 1000ms
2
3 PeriodicRate: 4000ms
4
5 NumPeriodicAddr: 2
6
7 NumPDID 5
8
9
10

11
12 764.64 6A0 01 00 00 00 00 00 00 00
13
14 764.69 6A1 02 00 00 00 00 00 00 00
15
16

17
18 4762.79 6A0 03 00 00 00 00 00 00 00
19
20 4762.82 6A1 04 00 00 00 00 00 00 00
21
22

23
24 8762.35 6A0 05 00 00 00 00 00 00 00
25
26 8762.36 6A1 01 00 00 00 00 00 00 00
27
28

29
30 12762.01 6A0 02 00 00 00 00 00 00 00
31
32 12762.04 6A1 03 00 00 00 00 00 00 00

Example 7: Scheduler 2 with 2 Periodic Addresses and 1 PDID

1 SchedulerRate: 1000ms
2
3 PeriodicRate: 1000ms
4
5 NumPeriodicAddr: 2
6

175 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7 NumPDID 1
8
9
10
11 7.19 6A0 01 00 00 00 00 00 00 00
12

13 77.21 6A1 01 00 00 00 00 00 00 00
14
15
16
17 1077.61 6A0 01 00 00 00 00 00 00 00
18
19 1077.68 6A1 01 00 00 00 00 00 00 00
20
21
22
23 2078.29 6A0 01 00 00 00 00 00 00 00
24
25 2078.40 6A1 01 00 00 00 00 00 00 00
26
27
28
29 3078.26 6A0 01 00 00 00 00 00 00 00
30
31 3078.33 6A1 01 00 00 00 00 00 00 00
32
33
34
35 4079.13 6A0 01 00 00 00 00 00 00 00
36
37 4079.19 6A1 01 00 00 00 00 00 00 00
38
39
40

41 5079.17 6A0 01 00 00 00 00 00 00 00
42
43 5079.24 6A1 01 00 00 00 00 00 00 00
44
45
46

47 6079.75 6A0 01 00 00 00 00 00 00 00
48
49 6079.82 6A1 01 00 00 00 00 00 00 00
50
51
52

53 7080.77 6A0 01 00 00 00 00 00 00 00
54
55 7080.91 6A1 01 00 00 00 00 00 00 00
56
57
58

59 8080.90 6A0 01 00 00 00 00 00 00 00
60
61 8080.97 6A1 01 00 00 00 00 00 00 00
62

176 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

63
64
65 9081.09 6A0 01 00 00 00 00 00 00 00
66
67 9081.15 6A1 01 00 00 00 00 00 00 00

[SWS_Dcm_01103] Require previous confirmation before next transmission

Upstream requirements: RS_Diag_04215

dThe Dcm shall trigger a transmission DcmDslPeriodicTxPduRef only after the

DcmDslPeriodicTxConfirmationPduId transmit confirmation for the previously
transmitted periodic response is received.c

[SWS_Dcm_01104] Transmission error behavior

Upstream requirements: RS_Diag_04215

dIn case of a PDID transmission error, the Dcm shall use always the same order of
periodicDIDs per client. Transmission errors shall not influence this order, the Dcm
shall continue to retry the transmission and start the next PDID only after the PDID
was transmitted successfully.c

[SWS_Dcm_01105] No negative response for periodic DID after positive re-

sponse
Upstream requirements: RS_Diag_04215

dAfter periodicDIDs are started and a positive response was sent, the Dcm shall start
to send the periodic DID.c

[SWS_Dcm_01106] Sending periodic DIDs without further condition checks

Upstream requirements: RS_Diag_04215

dEach time the counter of a periodicDataIdentifiers elapses, the Dcm shall retrieve the
DID data without validating further conditions (i.e. session, security, mode dependen-
cies, ConditionCheckRead and ReadDataLength).c

Note: The rate for a specific transmissionMode is defined as the time between any
two consecutive response messages with the same periodicDataIdentifier, when only
a single periodicDID is scheduled. If multiple periodicDIDs are scheduled concurrently,
the effective period between the same periodicDataIdentifier will vary based upon the
following design parameters:
• The main function recurrence DcmTaskTime
• The number of available periodic connections
• The number of periodicDIDs that can be scheduled concurrently (see configura-
tion parameter DcmDspMaxPeriodicDidScheduler).

177 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01575] Connection limitation for fast transmission

Upstream requirements: RS_Diag_04215

dIf DcmDspPeriodicTransmissionMaxPeriodicFastTransmissions is config-

ured, the Dcm shall limit the number of used periodic connections for transmission-
Mode ’sendAtFastRate’ to DcmDspPeriodicTransmissionMaxPeriodicFast-
Transmissions connections.c

[SWS_Dcm_01576] Connection limitation for medium transmission

Upstream requirements: RS_Diag_04215

dIf DcmDspPeriodicTransmissionMaxPeriodicMediumTransmissions
is configured, the Dcm shall limit the number of used periodic connections for
transmissionMode ’sendAtMediumRate’ to DcmDspPeriodicTransmissionMax-
PeriodicMediumTransmissions connections.c

[SWS_Dcm_01577] Connection limitation for slow transmission

Upstream requirements: RS_Diag_04215

dIf DcmDspPeriodicTransmissionMaxPeriodicSlowTransmissions is config-

ured, the Dcm shall limit the number of used periodic connections for transmission-
Mode ’sendAtSlowRate’ to DcmDspPeriodicTransmissionMaxPeriodicSlow-
Transmissions connections.c

[SWS_Dcm_01578] Connection order for limited transmissions

Upstream requirements: RS_Diag_04215

dIf any of the transmission connection limitations according to [SWS_Dcm_01575],

[SWS_Dcm_01576] or [SWS_Dcm_01577] is configured, the Dcm shall select the
DcmDslPeriodicConnection in the order of definition. That means that the first
transmitted periodic DID shall take the first configured connections and so forth.c

[SWS_Dcm_01111] Periodic DDDID transmission and session change

Upstream requirements: RS_Diag_04215

dIf DcmDspDDDIDcheckPerSourceDID is set to TRUE upon a session change, the

Dcm shall stop any scheduled periodic DDDID, that contains source data not supported
in the current session.c

[SWS_Dcm_01112] Periodic DDDID transmission and security level change

Upstream requirements: RS_Diag_04215

dIf DcmDspDDDIDcheckPerSourceDID is set to TRUE, upon any security level

change, the Dcm shall stop any scheduled periodic DDDID that contains source data
not supported in the current security level.c

178 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01115] Cancel pending read operations

Upstream requirements: RS_Diag_04215

dUpon stopping the periodical read of a data identifier while a pending asynchronous
ReadData operation is still in progress, the Dcm shall cancel the pending read operation
by calling ReadData with OpStatus=DCM_CANCEL.c

[SWS_Dcm_01117] Stop cancels pending transmissions

Upstream requirements: RS_Diag_04215

dUpon stopping the periodical read of a data identifier, the Dcm shall cancel pending
transmissions of that DID.c

[SWS_Dcm_01118] Finalizing initiated transmissions upon stop

Upstream requirements: RS_Diag_04215

dUpon stopping the periodical read of a data identifier the Dcm shall finalize already
initiated transmissions of that DID.c

7.4.2.12 Service 0x2C - DynamicallyDefineDataIdentifier

[SWS_Dcm_00259] dThe DSP submodule shall implement the DynamicallyDefine-

DataIdentifier (service 0x2C, diagnostic data access) of the Unified Diagnostic Ser-
vices.c

The DynamicallyDefineDataIdentifier service is implemented internally in Dcm module.

[SWS_Dcm_00866] dIf DcmDDDIDStorage configuration parameter is set to FALSE,

the Dcm shall initialize all DDDIDs as not present at power-up Dcm_Init).c

[SWS_Dcm_00867] dIf DcmDDDIDStorage configuration parameter is set to TRUE,

the Dcm shall restore the DDDID definition from NvM at power-up Dcm_Init).c

[SWS_Dcm_00868] dIf DcmDDDIDStorage configuration parameter is set to

TRUE, the Dcm shall trigger the storage of the DDDID definition to NvRam (via
NvM_SetRamBlockStatus).c

[SWS_Dcm_00646] dOn reception of service DynamicallyDefineDataIdentifier with

subservice defineByIdentifier or defineByMemoryAddress, the Dcm module shall con-
figure this new DID with associated information receive from the diagnostic request:
Memory address and memory length or DID source, position and size.c

179 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00861] dOn reception of the UDS Service DynamicallyDefineDataIden-

tifier (0x2C), the Dcm module shall check if the DDDID will not exceed the config-
ured parameter value DcmDspDDDIDMaxElements. Otherwise (in case the number
of elements will be exceeded) the Dcm module shall send a NRC 0x31 (RequestOut-
OfRange).c

[SWS_Dcm_00854] dOn reception of the UDS Service DynamicallyDefineDataIdenti-

fier (0x2C) with subservice defineByMemoryAddress, the Dcm shall check if the re-
quested AddressAndLengthFormatIdentifier is supported (refer to configura-
tion parameter DcmDspSupportedAddressAndLengthFormatIdentifier), Oth-
erwise the NRC 0x31 (requestOutOfRange) shall be responded. In case the container
AddressAndLengthFormatIdentifier is not present, the Dcm shall accept all
possible AddressAndLengthFormatIdentifiers.c

[SWS_Dcm_00647] dOn reception of service DynamicallyDefineDataIdentifier with

subservice clearDynamicallyDefinedDataIdentifier, the Dcm module shall remove the
configuration of this DID.c

[SWS_Dcm_00723] dOn reception of the UDS Service DynamicallyDefineDataIdenti-

fier (0x2C),the Dcm module shall check if the DDDID can be defined in the current
session (see configuration parameter DcmDspDidReadSessionRef). If not, the Dcm
module shall send a NRC 0x31 (RequestOutOfRange).c

[SWS_Dcm_00724] dOn reception of the UDS Service DynamicallyDefineDataIdenti-

fier (0x2C), the Dcm module shall check if the DDDID can be defined in the current
security level (see configuration parameter DcmDspDidReadSecurityLevelRef). If
not, the Dcm module shall send NRC 0x33 (Security access denied).c

[SWS_Dcm_00725] dOn reception of the UDS Service DynamicallyDefineDataIdenti-

fier (0x2C), the Dcm module shall check if the requested Source-DIDs are supported in
the current session (see configuration parameter of referenced DID DcmDspDidRead-
SessionRef)). If not, the Dcm module shall send a NRC 0x31 (RequestOutOfRange).c

[SWS_Dcm_00726] dOn reception of the UDS Service DynamicallyDefineDataIden-

tifier (0x2C), the Dcm module shall check if the requested Source-DID or the mem-
oryRange are supported in the current security level (see configuration parameter
of referenced DID DcmDspDidReadSecurityLevelRef or memoryRange DcmD-
spReadMemoryRangeSecurityLevelRef). If not, the Dcm module shall send a NRC 0x33
(Security access denied).c

[SWS_Dcm_00821] dOn reception of the UDS Service DynamicallyDefineDataIden-

tifier (0x2C), the Dcm module shall check if the requested Source-DID or the mem-
oryRange are supported in the current mode condition (see configuration parameter

180 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

of referenced DID DcmDspDidReadModeRuleRef or memoryRange DcmDspRead-

MemoryRangeModeRuleRef). If not, the Dcm module shall send the calculated nega-
tive response code of the referenced DcmModeRule.c

In case of memory address(es), on reception of ReadDataByIdentifier or Read-

DataByPeriodicIdentifier request for a dynamically defined DID, the Dcm will use the
callout Dcm_ReadMemory for all contained memory addresses to access the data.

[SWS_Dcm_01051] dOn reception of the UDS Service DynamicallyDefineDataIdenti-

fier (0x2C), if the request message contains different MemoryIdValue compare to the
configured values in DcmDspMemoryIdInfo container, the Dcm shall send a NRC 0x31
(RequestOutOfRange).c

In case of DID source(s), on reception of ReadDataByIdentifier or ReadDataByPeriod-

icIdentifier request for a dynamically defined DID, the Dcm will use the configuration of
the contained DIDs to read the data.

7.4.2.13 Service 0x2E - WriteDataByIdentifier

[SWS_Dcm_00255] dThe Dcm module shall implement the UDS Service WriteDataByI-
dentifier (0x2E) of the Unified Diagnostic Services.c

When using Service 0x2E, the request of the tester contains a 2-byte DID and a
dataRecord with the data to be written. The configuration of the Dcm contains a list
of supported DIDs and defines for each configured DID:
• The 2-byte DID (see configuration parameter DcmDspDidIdentifier)
• For every data of the DID:
– The function WriteData to be used for this data (see configuration parame-
ters DcmDspDataWriteFnc and DcmDspDataUsePort)

[SWS_Dcm_01496] Write UDS DID authentication check

Upstream requirements: RS_Diag_04233

dOn reception of the UDS Service WriteDataByIdentifier (0x2E), the Dcm shall check
if the write access to the requested DID is authenticated and write the data identifier
only if:
• for that write DID a role is configured via DcmDspDidWriteRoleRef and the
verification according to [SWS_Dcm_01522] was successful or
• the active white list on that connection has for the requested DID one entry with
write access that matches that DID.

181 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

According to [SWS_Dcm_01537] the authentication checks are only executed if

DcmDspAuthentication is configured. In case of a failed authentication the NRC han-
dling is according to [SWS_Dcm_01544] and [SWS_Dcm_01551] applies.

[SWS_Dcm_00467] dOn reception of the UDS Service WriteDataByIdentifier (0x2E),

the Dcm module shall check if the DID is supported (see configuration parameter
DcmDspDid and DcmDspDidRange) If not, the Dcm module shall send NRC 0x31 (Re-
quest out of range) .c

[SWS_Dcm_00562] dIf a DID is set as unused (DcmDspDidUsed set to FALSE), the

Dcm shall consider the DID as not supported (according to [SWS_Dcm_00467])c

[SWS_Dcm_00468] dOn reception of the UDS Service WriteDataByIdentifier (0x2E),

the Dcm module shall check if the DID has a Write access configured (see configuration
parameter DcmDspDidWrite in DcmDspDidInfo). If not, the Dcm module shall send
NRC 0x31 (Request out of range).c

[SWS_Dcm_00469] dOn reception of the UDS Service WriteDataByIdentifier (0x2E),

the Dcm module shall check if the DID can be written in the current session (see con-
figuration parameter DcmDspDidWriteSessionRef). If not, the Dcm module shall
send a NRC 0x31 (Request Out of Range).c

[SWS_Dcm_00470] dOn reception of the UDS Service WriteDataByIdentifier (0x2E),

the Dcm module shall check if the DID can be written in the current security level
(see configuration parameter DcmDspDidWriteSecurityLevelRef). If not, the
Dcm module shall send NRC 0x33 (Security access denied).c

[SWS_Dcm_00822] dOn reception of the UDS Service WriteDataByIdentifier (0x2E),

the Dcm module shall check if the DID can be written in the current mode condition (see
configuration parameter DcmDspDidWriteModeRuleRef). If not, the Dcm module
shall send the calculated negative response code of the referenced DcmModeRule.c

[SWS_Dcm_00473] dOn reception of the UDS Service WriteDataByIdentifier (0x2E),

if all signals (DcmDspDidSignal) of the DID have fixed length (DcmDspDataType
is different than UINT8_DYN), the Dcm module shall check if the received data length
corresponds to the DID data length (addition of all DcmDspDataByteSize).c

[SWS_Dcm_00395] dAfter all verifications (see [SWS_Dcm_00467],

[SWS_Dcm_00468], [SWS_Dcm_00469], [SWS_Dcm_00470], [SWS_Dcm_00473]
) the Dcm module shall write all the signals (DcmDspDidSignal) of the DID by

182 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

either calling the configured function DcmDspDataWriteFnc (if parameter DcmD-

spDataUsePort is set to USE_DATA_SYNCH_FNC or USE_DATA_ASYNCH_FNC
or USE_DATA_ASYNCH_FNC_ERROR or USE_DATA_SYNCH_FNC_PROXY or USE_-
DATA_ASYNCH_FNC_PROXY) or the associated WriteData operations (if parameter
DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)
or the associated SenderReceiver interfaces (if parameter DcmDspDataUsePort is
set to USE_DATA_SENDER_RECEIVER or to USE_DATA_SENDER_RECEIVER_AS_-
SERVICE) with the following parameter values:
Data: the dataRecord form the request
DataLength: the number of bytes in the dataRecord (get from the configuration if the
data has fixed length (DcmDspDataType is different than UINT8_DYN) or from the
diagnostic request length if the data has dynamic length (DcmDspDataType is set to
UINT8_DYN)).c

[SWS_Dcm_01433] dAfter all verifications (see [SWS_Dcm_00467],

[SWS_Dcm_00468], [SWS_Dcm_00469], [SWS_Dcm_00470], [SWS_Dcm_00473] )
for DID’s with DcmDspDidUsePort is set to USE_ATOMIC_SENDER_RECEIVER_-
INTERFACE, USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE or
USE_ATOMIC_NV_DATA_INTERFACE, the Dcm module shall write the data by writing
the associated sender-receiver or NvDataInterface DataServices_{DID}.c

[SWS_Dcm_CONSTR_06039] Signals with variable datalength dOnly the last sig-

nal (DcmDspDidSignal) of a DID can have variable datalength (DcmDspDataType
is set to UINT8_DYN).c

In other case the Dcm won’t be able to split the data from the request.

[SWS_Dcm_00639] dTo serialize the request message of UDS Service WriteDataByI-

dentifier request into the required AUTOSAR data types (signed- and unsigned inte-
ger), the target endianness configured in DcmDspDataEndianness shall be consid-
ered for DcmDspData elements having DcmDspDataUsePort set to USE_DATA_-
SENDER_RECEIVER, USE_DATA_SENDER_RECEIVER_AS_SERVICE. In case DcmD-
spDataEndianness is not present, the DcmDspDataDefaultEndianness shall be
used instead.c

[SWS_Dcm_CONSTR_06018] dDcmDspData elements used in service 0x2E shall not

have DcmDspDataUsePorts set to USE_ECU_SIGNAL.c

[SWS_Dcm_CONSTR_06073] Dependency for DcmDspDataWriteFnc dDcmDsp-

DataWriteFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or

183 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR or

• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY
c

Note: The invocation of functions BndM_WriteStart and BndM_WriteFinalize are not

part of Dcm Specification. The functions are called via project specific implementation
(e.g. CDD).

[SWS_Dcm_01582] Atomic BndM write operation

Upstream requirements: RS_Diag_04243

dAfter all verifications (see [SWS_Dcm_00467], [SWS_Dcm_00468],

[SWS_Dcm_00469], [SWS_Dcm_00470], [SWS_Dcm_00473]) for DIDs with
DcmDspDidUsePort is set to USE_ATOMIC_BNDM, the Dcm module shall
write the data by writing the data to the associated BlockId from the BndM
(DcmDspDidBndMBlockIdRef) using the block specific writing function
BndM_WriteBlock_<BlockId.Shortname>.c

[SWS_Dcm_01583] Not allowed atomic BndM write operation

Upstream requirements: RS_Diag_04243

dIf the Dcm calls BndM_WriteBlock_’BlockId.Shortname’ according to

[SWS_Dcm_01582] and BndM_WriteBlock_’BlockId.Shortname’ returns E_NOT_OK,
the Dcm shall return a negative response 0x24 (requestSequenceError).c

Note: The BndM needs to be set into writing mode as a precondition. This is either
done by the coding sub-module in Dcm or by a CDD.

[SWS_Dcm_01584] Positive response on atomic BndM write operation

Upstream requirements: RS_Diag_04243

dIf the Dcm has triggered an atomic BndM write operation according to
[SWS_Dcm_01582], the Dcm shall return a positive response if the write operation
of the BndM has called Dcm_BndMWriteBlockFinish with the parameter result set to
E_OK.c

[SWS_Dcm_01585] Negative response on atomic BndM write operation

Upstream requirements: RS_Diag_04243

dIf the Dcm has triggered an atomic BndM write operation according to
[SWS_Dcm_01582], the Dcm shall return a negative response 0x72 (generalProgram-
mingFailure) if the write operation of the BndM has called Dcm_BndMWriteBlockFinish
with the parameter result set to E_NOT_OK.c

184 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Note: The Dcm needs to ensure that [SWS_Dcm_00024] requirement is respected

while waiting on the job finish callback as specified in [SWS_Dcm_01584] and
[SWS_Dcm_01585].

[SWS_Dcm_01586]
Upstream requirements: RS_Diag_04243

dIf the Dcm is reading or writing a DID with DcmDspDidUsePort set to

USE_ATOMIC_BNDM, the Dcm shall transform the dataRecord into the corresponding
BndM type. The DID data element structure needs to be compatible to the referenced
ImplementationDataType of the BndMBlockDescriptor. For each DID data element a
corresponding sub-element shall exist in the ImplementationDataType with the same
shortname and the basetypes shall be compatible.c

[SWS_Dcm_CONSTR_06099] Consistency of BndM Block configuration dIf a

DcmDspDid has DcmDspDidUsePort set to USE_ATOMIC_BNDM, the parameter
DcmDspDidBndMBlockIdRef shall be present.c

7.4.2.14 Service 0x2F - InputOutputControlByIdentifier

[SWS_Dcm_00256]
Upstream requirements: RS_Diag_04218

dThe Dcm module shall implement the UDS Service InputOutputControlByIdentifier

(0x2F).c

When using Service 0x2F, the request of the tester contains a 2-byte DID.
The configuration of the Dcm contains a list of supported DID’s. For each DID, the Dcm
configuration specifies:
• The 2-bytes DID (see configuration parameter DcmDspDidIdentifier)
• For every data of the DID :
– The function Xxx_ReturnControlToECU() for this data (see configuration pa-
rameters DcmDspDataReturnControlToEcuFnc and DcmDspDataUse-
Port)
– The function Xxx_ResetToDefault() for this data (see configuration parame-
ters DcmDspDataResetToDefaultFnc and DcmDspDataUsePort)
– The function Xxx_FreezeCurrentState() for this DID (see configuration pa-
rameters DcmDspDataFreezeCurrentStateFnc and DcmDspDataUse-
Port)

185 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

– The function Xxx_ShortTermAdjustment() for this DID (see configura-

tion parameters DcmDspDataShortTermAdjustmentFnc and DcmDsp-
DataUsePort)
– The sizes of the control record used in the function
Xxx_ShortTermAdjustment() (see configuration parameter and DcmD-
spDataByteSize)

[SWS_Dcm_00579]
Upstream requirements: RS_Diag_04218

dThe Dcm shall support InputOutputControlParameter definitions according to

[SWS_Dcm_01661].c

[SWS_Dcm_01661] InputOutputControlParameter definitions d

Hex Description
00 returnControlToECU
01 resetToDefault
02 freezeCurrentState
03 shortTermAdjustment

[SWS_Dcm_01554] IOControl DID authentication check

Upstream requirements: RS_Diag_04218

dOn reception of the UDS Service InputOutputControlByIdentifier (0x2F), the Dcm shall
check if the control access to the requested DID is authenticated and control the IO only
if:
• for that IO control a role is configured via DcmDspDidControlRoleRef and the
verification according to [SWS_Dcm_01522] was successful or
• the active white list on that connection has for the requested DID one entry with
control access that matches that DID.
c

According to [SWS_Dcm_01522] the authentication checks are only executed if

DcmDspAuthentication is configured. In case of a failed authentication the NRC
handling is according to [SWS_Dcm_01544] and [SWS_Dcm_01551] applies.

186 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00563]
Upstream requirements: RS_Diag_04218

dOn reception of the UDS Service InputOutputControlByIdentifier (0x2F), the Dcm mod-
ule shall check if the DID is supported (see configuration parameter DcmDspDid) If
not, the Dcm module shall send NRC 0x31 (Request out of range).c

[SWS_Dcm_00564]
Upstream requirements: RS_Diag_04218

dIf a DID is set as unused (DcmDspDidUsed set to FALSE), the Dcm shall consider the
DID as not supported (according to [SWS_Dcm_00563])c

[SWS_Dcm_00565]
Upstream requirements: RS_Diag_04218

dOn reception of the UDS Service InputOutputControlByIdentifier (0x2F), the Dcm mod-
ule shall check if the DID has a Control access configured (see configuration parame-
ter DcmDspDidControl in DcmDspDidInfo). If not, the Dcm module shall send NRC
0x31 (Request out of range).c

[SWS_Dcm_00566] dOn reception of the UDS Service InputOutputControlByIdentifier

(0x2F), the Dcm module shall check if the DID can be control in the current session (see
configuration parameter DcmDspDidControlSessionRef). If not, the Dcm module
shall send a NRC 0x31 (Request Out of Range).c

[SWS_Dcm_00567] dOn reception of the UDS Service InputOutputControlByIdentifier

(0x2F), the Dcm module shall check if the DID can be control in the current security
level (see configuration parameter DcmDspDidControlSecurityLevelRef). If not,
the Dcm module shall send NRC 0x33 (Security access denied).c

[SWS_Dcm_00823] dOn reception of the UDS Service InputOutputControlByIdentifier

(0x2F), the Dcm module shall check if the DID can be control in the current mode
condition (see configuration parameter DcmDspDidControlModeRuleRef). If not,
the Dcm module shall send the calculated negative response code of the referenced
DcmModeRule.c

[SWS_Dcm_01600] CEMR on SR interface for DIDs with no CEMR in the UDS re-
quest
Upstream requirements: RS_Diag_04218

dIf the IOC DID has no CEMR in the UDS request message, the Dcm shall use a Dcm_-
Cemr_Type that has a bit for each DcmDspData of the DID on the interface IOCon-
trolRequest that has each bit set to 1.c

187 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00580]
Upstream requirements: RS_Diag_04218

dOn reception of a request for UDS Service InputOutputControlByIdentifier (0x2F)

, if all verifications have been successfully done (see [SWS_Dcm_00563],
[SWS_Dcm_00565], [SWS_Dcm_00566], [SWS_Dcm_00567] ) and if the data is con-
figured as a "ECU signal" of the IoHwAb (parameter DcmDspDataUsePort), the Dcm
shall call the Api IoHwAb_Dcm_<symbolic name of ECU signal (parameter DcmD-
spDataEcuSignal)>() with InputOutputControlParameter for the ’action’ parameter
and in case of InputOutputControlParameter is set to ’shortTermAdjustment’ the signal
value for the "signal" parameter. In this case the requirements [SWS_Dcm_00396],
[SWS_Dcm_00397], [SWS_Dcm_00398] and [SWS_Dcm_00399] doesn’t apply.c

[SWS_Dcm_00581]
Upstream requirements: RS_Diag_04218

dIn case of more than one supported I/O signal per DataIdentifier and the configuration
parameter DcmDspDidControlMask is set to DCM_CONTROLMASK_INTERNAL, the
Dcm shall internally consider the parameter controlEnableMaskRecord and control only
the included signals in the request message.c

[SWS_Dcm_CONSTR_06051] dThe configuration parameter DcmDspDidControl-

MaskSize shall be only present if DcmDspDidControlMask is equal to DCM_CON-
TROLMASK_EXTERNAL or DCM_CONTROLMASK_INTERNAL.c

[SWS_Dcm_01273]
Upstream requirements: RS_Diag_04218

dIf the configuration parameter DcmDspDidControlMask is set to DCM_CONTROL-

MASK_EXTERNAL or DCM_CONTROLMASK_INTERNAL, or the DcmDspDid element
used in service 0x2F is configured to have an atomic S/R interface, the Dcm shall
reject requests without included control enable mask record with the NRC 0x13 (incor-
rectMessageLengthOrInvalidFormat).c

[SWS_Dcm_01274]
Upstream requirements: RS_Diag_04218

dIf the configuration parameter DcmDspDidControlMask is set to

DCM_CONTROLMASK_NO, the Dcm shall reject request with included control
enable mask record with the NRC 0x13 (incorrectMessageLengthOrInvalidFormat).c

188 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_CONSTR_06084] Sender-receiver communication for IOControls is

limited to atomic S/R interfaces
Upstream requirements: RS_Diag_04218

dIf a DID has a configured DcmDspDidUsePort = USE_DATA_ELEMENT_SPE-

CIFIC_INTERFACES, the possible values of DcmDspDataUsePort are limited to non
S/R interfaces.c

[SWS_Dcm_CONSTR_06085] Atomic S/R for IOControls are limited to non-NV

interfaces
Upstream requirements: RS_Diag_04218

dIf a DID has a configured DcmDspDidControl, the possible values of DcmDsp-

DidUsePort are limited to atomic S/R interface and USE_DATA_ELEMENT_SPE-
CIFIC_INTERFACES.c

[SWS_Dcm_CONSTR_06086] Signals for DIDs with Atomic S/R are not shared
with other DIDs
Upstream requirements: RS_Diag_04218

dIf a DcmDspDid is configured to have an atomic S/R interface, all DcmDspDataEle-

ments referenced by this DID shall be referenced only from this DID.
c

[SWS_Dcm_CONSTR_06050] dIf a DcmDspDid is used in service 0x2F and is con-

figured to have an atomic S/R interface, the DcmDspDidControlMask shall be set to
DCM_CONTROLMASK_EXTERNAL and the parameter DcmDspDidControlMaskSize
shall be present with a value greater than zero.c

[SWS_Dcm_00680] Mapping of internal ControlEnableMaskRecord to DID data

elements
Upstream requirements: RS_Diag_04218

dIf DcmDspDidControlMask is set to DCM_CONTROLMASK_INTERNAL,the Con-

trolEnableMaskRecord shall be mapped to the DID data elements by applying the
following mapping :
• The most significant bit of the first byte of the ControlEnableMask shall corre-
spond to the first DID data element
• The second most significant bit of the first byte of the ControlEnableMask shall
correspond to the second DID data element and continuing on in this fashion
utilizing as many ControlEnableMask bytes as necessary to map all DID data
elements.
c

189 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

The controlEnableMaskRecord is only present, if the DataIdentifer supports more than

one signal.
The Dcm supports atomic S/R interfaces activated by the configuration DcmD-
spDidUsePort set to USE_ATOMIC_SENDER_RECEIVER_INTERFACE or USE_-
ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE. In the text and require-
ments of this chapter the term ’atomic S/R interface’ for IO control means that the
IO controlled DID is configured to one of the two choices.
The service use case TPS_SWCT_01654 and the constr_1679 limits the S/R inter-
faces used for IOControl to explicit S/R communication. In implicit communication is
not supported by the Dcm.

[SWS_Dcm_01434] IOControl General execution sequence

Upstream requirements: RS_Diag_04218

dOn reception of a request for UDS Service InputOutputControlByIdentifier (0x2F)

the Dcm shall first execute the service verifications according to [SWS_Dcm_00563],
[SWS_Dcm_00565], [SWS_Dcm_00566], [SWS_Dcm_00567] and on successful
passing the verifications start the configured service processing.c

[SWS_Dcm_00396]
Upstream requirements: RS_Diag_04218

dOn reception of a request for UDS Service InputOutputControlByIdentifier (0x2F)

with inputOutputControlParameter equal to returnControlToEcu, the Dcm mod-
ule shall invoke all impacted configured function of the controlEnableMaskRecord
(if parameter DcmDspDataUsePort set to USE_DATA_SYNCH_FNC or USE_-
DATA_ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ERROR or USE_DATA_SYNCH_-
FNC_PROXY or USE_DATA_ASYNCH_FNC_PROXY; see configuration parameter DcmD-
spDataReturnControlToEcuFnc). Alternatively call all the associated Return-
ControlToECU operations (if parameter DcmDspDataUsePort set to USE_DATA_-
SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER or USE_DATA_-
ASYNCH_CLIENT_SERVER_ERROR) for every data of the DID received in the request.c

[SWS_Dcm_00397]
Upstream requirements: RS_Diag_04218

dOn reception of a request for UDS Service InputOutputControlByIdentifier (0x2F) with

inputOutputControlParameter equal to resetToDefault, the Dcm module shall
invoke all impacted configured function of the controlEnableMaskRecord (if parame-
ter DcmDspDataUsePort set to USE_DATA_SYNCH_FNC or USE_DATA_ASYNCH_FNC

190 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

or USE_DATA_ASYNCH_FNC_ERROR or USE_DATA_SYNCH_FNC_PROXY or USE_-

DATA_ASYNCH_FNC_PROXY; see configuration parameter DcmDspDataResetToDe-
faultFnc). Alternatively call all the associated ResetToDefault operations (if pa-
rameter DcmDspDataUsePort set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)
for every data of the DID received in the request.c

[SWS_Dcm_00398]
Upstream requirements: RS_Diag_04218

dOn reception of a request for UDS Service InputOutputControlByIdentifier (0x2F)

with inputOutputControlParameter equal to freezeCurrentState, the Dcm mod-
ule shall invoke all impacted configured function of the controlEnableMaskRecord
(if parameter DcmDspDataUsePort set to USE_DATA_SYNCH_FNC or USE_-
DATA_ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ERROR or USE_DATA_SYNCH_-
FNC_PROXY or USE_DATA_ASYNCH_FNC_PROXY; see configuration parameter DcmD-
spDataFreezeCurrentStateFnc). Alternatively call all the associated Freeze-
CurrentState operations (if parameter DcmDspDataUsePort set to USE_DATA_-
SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER or USE_DATA_-
ASYNCH_CLIENT_SERVER_ERROR) for every data of the DID received in the request.c

[SWS_Dcm_00399]
Upstream requirements: RS_Diag_04218

dOn reception of a request for UDS Service InputOutputControlByIdentifier (0x2F) with

inputOutputControlParameter equal to shortTermAdjustment, the Dcm mod-
ule shall invoke all impacted configured function of the controlEnableMaskRecord
(if parameter DcmDspDataUsePort set to USE_DATA_SYNCH_FNC or USE_DATA_-
ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ERROR or USE_DATA_SYNCH_FNC_-
PROXY or USE_DATA_ASYNCH_FNC_PROXY; see configuration parameter DcmDsp-
DataShortTermAdjustmentFnc). Alternatively call all the associated ShortTer-
mAdjustment operations (if parameter DcmDspDataUsePort set to USE_DATA_
SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER or USE_
DATA_ASYNCH_CLIENT_SERVER_ERROR) for every data of the DID received in
the request.c

[SWS_Dcm_00858] Cancel active IO controls on session change

Upstream requirements: RS_Diag_04119

dOn any session transition, the Dcm shall stop all active IO controls according to
[SWS_Dcm_01435] which are not supported by the new session.c

191 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00628] Cancel active IO controls in default sessions

Upstream requirements: RS_Diag_04119

dOn a session transition to default session, the Dcm shall stop all active IO controls
according to [SWS_Dcm_01435].c

[SWS_Dcm_00859] Cancel active IO controls on security level change

Upstream requirements: RS_Diag_04119

dOn any security level change, the Dcm shall stop all active IO controls according to
[SWS_Dcm_01435] which are not support by the new security level anymore.c

[SWS_Dcm_01435] Dcm cancel IO control sequence

Upstream requirements: RS_Diag_04119

dIf the Dcm needs to cancel an active IO control due to [SWS_Dcm_00858],

[SWS_Dcm_00628] or [SWS_Dcm_00859], the Dcm shall do the following:
• For controlled data elements with DcmDspDataUsePort set to USE_ECU_SIG-
NAL: call to IoHwAb_Dcm_<symbolic ECU signal name>() with ’action’ parameter
set to ReturnControlToECU.
• For controlled data elements with DcmDspDataUsePort set to USE_DATA_-
ASYNCH_CLIENT_SERVER or USE_DATA_SYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_CLIENT_SERVER_ERROR: call the C/S interface operation Re-
turnControlToECU.
• For controlled data elements with DcmDspDataUsePort set to USE_DATA_-
SYNCH_FNC or USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_FNC_ERROR
or USE_DATA_SYNCH_FNC_PROXY or USE_DATA_ASYNCH_FNC_PROXY: call the
configured function Xxx_ReturnControlToECU (see parameter DcmDspDataRe-
turnControlToEcuFnc)
• For controlled DIDs with is configured atomic S/R interfaces: update the data
element IOOperationRequest with inputOutputControlParameter = 0x00, the
controlEnableMask = 0xFFFFFFFF1 and data element underControl = 0x00.
c

[SWS_Dcm_00640]
Upstream requirements: RS_Diag_04218

dTo serialize the required AUTOSAR data types (signed- and unsigned integer) from
the request message (in case of inputOutputControlParameter is set to ’short-
TermAdjustment’) / into the response message of UDS Service InputOutputControlByI-
dentifier responses, the target endianness configured in DcmDspDataEndianness
shall be considered for DcmDspData elements having DcmDspDataUsePort set to

1
The size of the mask depends on the parameter DcmDspDidControlMaskSize

192 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

USE_ECU_SIGNAL. In case DcmDspDataEndianness is not present, the DcmDsp-

DataDefaultEndianness shall be used instead.c

[SWS_Dcm_00682]
Upstream requirements: RS_Diag_04218

dThe controlState in the ControlStatusRecord for positive response message of

IoControl service shall be retrieved using the associated ReadData operation/func-
tion/SenderReceiver after application processing on the IO control request is positively
finalized.c

Beside the Client/Server interface, the Dcm provides the SenderReceiver interface IO-
ControlRequest_DID. The underControl data element of this interface is calculated by
the Dcm with one state bit for each data element identical to the CEMR. Applications
can directly derive the active control enable status without the need to maintain inter-
nal states.
The bit-mask underControl contains the accumulated status about which data elements
of this particular I/O is currently under diagnostic control. The normal operation state
could be derived if the value of underControl is set to 0x00 (which is the initial value).
Each set bit indicates a data element which is under diagnostic control via FreezeCur-
rentState, ’ResetToDefault’ or ’ShortTermAdjustment’.

[SWS_Dcm_01436] Calculation of the underControl data element

Upstream requirements: RS_Diag_04218

dThe Dcm shall calculate the underControl data element of the S/R interface IOCon-
trolRequest_{DID}. The underControl is a bitfield of the same size than the CEMR of
the controlled DID. Each bit represents the same data element as in the CEMR. A value
of 0 indicates, that the corresponding data element is currently not controlled by the
Dcm, a value of 1 indicates that it is controlled. The initial value is 0, each control
request for a data element with inputOutputControlParameter equal to Reset-
ToDefault, FreezeCurrentState or ShortTermAdjustment will set the corresponding bit
value to 1, and each control request with inputOutputControlParameter set to
ReturnControlToECU will set the bit value to 0.c

With each I/O Control request a command IOOperationRequest is provided to the

application to update the input or the respective output. IOOperationRequest con-
tains the inputOutputControlParameter, the controlEnableMask and in case
of ShortTermAdjustment the controlState.
To identify that previous operation has finished (e.g Write IOControlRequest_{DID}),
the user can use the update flag mechanism from the RTE.
The application needs to update their output values and finalizes the request with the
response message IOOperationRequest to the Dcm. The possible values are:

193 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• 0x00 positive response (similar to E_OK)

• 0x10 generalReject
• 0x21 busyRepeatRequest
• 0x22 conditionsNotCorrect
• 0x26 FailurePreventsExecutionOfRequestedAction
• 0x31 requestOutOfRange
• 0x78 ResponsePending (similar to E_PENDING)
Based on the write trigger of the SW-C to IOControlResponse_{DID}.IOOpera-
tionResponse, the Dcm will:
1. wait for final processing (0x78)
2. send a positive response message (0x00)
3. send a negative response message (all other values, except 0xFF)

Figure 7.12: IO-Control with Sender/Receiver interfaces

[SWS_Dcm_01437] inputOutputControlParameter idle state

Upstream requirements: RS_Diag_04218

dThe inputOutputControlParameter of data element of IOOperationRequest

from S/R interface IOControlRequest_{DID} shall have an initial value of 0xFF.
This value indicates the application, that the Dcm is currently not processing an UDS
service to control this DID.c

194 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01438] inputOutputControlParameter after processing an UDS

InputOutputControlByIdentifier (0x2F) service
Upstream requirements: RS_Diag_04218

dIf the Dcm is processing an InputOutputControlByIdentifier request with inputOut-

putControlParameter equal to ResetToDefault, FreezeCurrentState or ShortTer-
mAdjustment, the Dcm shall set the inputOutputControlParameter of data ele-
ment of IOOperationRequest from S/R interface IOControlRequest_{DID} to
the idle state 0xFF after the application has set the IOControlResponse_{DID}.
IOOperationResponse to 0x00 and before processing other InputOutputControlByI-
dentifier requests.c

Upon the Dcm writes IOOperationRequest of IOControlRequest_{DID} the

SWC processes the IO control request. The SWC informs the Dcm about the cur-
rent processing state by updating IOControlResponse_{DID}.IOOperationRe-
sponse.

[SWS_Dcm_01439] Positive response based on IOOperationResponse

Upstream requirements: RS_Diag_04218

dIf the Dcm is processing an InputOutputControlByIdentifier request, it shall reply with

a positive response, if the applications set IOControlResponse_{DID}.IOOpera-
tionResponse to 0x00.c

[SWS_Dcm_01440] Negative response based on IOOperationResponse

Upstream requirements: RS_Diag_04218

dIf the Dcm is processing an InputOutputControlByIdentifier request, it shall reply with

a negative response with the NRC IOControlResponse_{DID}.IOOperationRe-
sponse, if the applications set IOControlResponse_{DID}.IOOperationRe-
sponse a value different to 0x00 and 0x78.c

[SWS_Dcm_01441] RCRRP based on IOOperationResponse

Upstream requirements: RS_Diag_04218

dIf the Dcm is processing an InputOutputControlByIdentifier request and the IOCon-

trolResponse_{DID}.IOOperationResponse has a value of 0x78, the Dcm shall
wait until the IOControlResponse_{DID}.IOOperationResponse gets a value
different to 0x78 and send RCRRP according to [SWS_Dcm_00024].c

Note: The use of the RTE functionality ”IsUpdated” is a possible mechanism for the
Dcm to detect a write from SW-C to the S/R data element.

195 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01275] Common action for all inputOutputControlParameter op-

erations with atomic S/R
Upstream requirements: RS_Diag_04218

dIf the Dcm is processing an InputOutputControlByIdentifier request for a DID config-

ured atomic S/R interface, the Dcm module shall update in the IOControlRequest_-
{DID} the data element IOOperationRequest with
1. controlEnableMask = controlEnableMaskRecord of the request message
2. inputOutputControlParameter = inputOutputControlParameter from the re-
quest message
c

The value 0xFF of the inputOutputControlParameter of the command IOOp-

erationRequest is the ’idle’ state. The values 0x00 (ReturnControlToECU), 0x01
(ResetToDefault), 0x02 (FreezeCurrentState) or 0x03 (ShortTermAdjustment) start the
request processing and include the control option inputOutputControlParame-
ter, controlEnableMask and controlState (for ShortTermAdjustment only).

[SWS_Dcm_01277] Additional action for InputOutputControl operations for

ShortTermAdjustment with atomic S/R
Upstream requirements: RS_Diag_04218

dIf the Dcm is processing an InputOutputControlByIdentifier request with inputOut-

putControlParameter equal to ShortTermAdjustment for a DID with configured
atomic S/R interface, in addition to [SWS_Dcm_01275] the Dcm module shall update
in the IOControlRequest_{DID} the data element controlState with content of
the controlState from the request message.c

Note: The controlState is a separate data elment that it can be optionally pro-
cessed by a data transformer to transform the byte stream into a composite type (see
Figure 7.12: IO-Control with Sender/Receiver interfaces).
An example of the Dcm S/R interaction is given in Figure 9.22, Figure 9.23 and Figure
9.24. For ReturnControlToECU the data from the request is provided to the application,
the Dcm will continue to finalize the request after writing the data into the S/R ports. All
other sub-functions will wait for the application providing the response 0x00 or an NRC
code.

[SWS_Dcm_CONSTR_06048] Composite sub elements accessible only by read

dComposite sub elements can only be referred from Read DID i.e. Write and Control
DID are not supported.c

196 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_CONSTR_06030] dThe ReturnControlToEcu functionnality is existing

if at least one of the following parameters are activated : DcmDspDidFreeze-
CurrentState in ECUC_Dcm_00624 : or DcmDspDidResetToDefault in
ECUC_Dcm_00623 : or DcmDspDidShortTermAdjustment in ECUC_Dcm_00625
: .c

[SWS_Dcm_CONSTR_06059] Dependency for DcmDspDataFreezeCur-

rentStateFnc dDcmDspDataFreezeCurrentStateFnc shall be only present
if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR or
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY
c

[SWS_Dcm_CONSTR_06063] Dependency for DcmDspDataResetToDefaultFnc

dDcmDspDataResetToDefaultFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR or
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY
c

[SWS_Dcm_CONSTR_06064] Dependency for DcmDspDidControlMaskSize d

DcmDspDidControlMaskSize shall be only present if DcmDspDidControlMask is
equal to DCM_CONTROLMASK_EXTERNAL or DCM_CONTROLMASK_INTERNAL.c

[SWS_Dcm_CONSTR_06081] Dependency for DcmDspDidControlMaskBitPo-

sition dThe value configured for DcmDspDidControlMaskBitPosition shall be
lower than DcmDspDidControlMaskSize * 8.c

[SWS_Dcm_CONSTR_06065] Dependency for DcmDspDataReturnControlToE-

cuFnc dDcmDspDataReturnControlToEcuFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or

197 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR or

• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY
c

[SWS_Dcm_CONSTR_06066] Dependency for DcmDspDataShortTermAdjust-

mentFnc dDcmDspDataShortTermAdjustmentFnc shall be only present if:
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_ERROR or
• DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY or
• DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY
c

[SWS_Dcm_CONSTR_06082] Dependency for DcmDspDidControlMaskSize

dDcmDspDidControlMaskSize larger than 4 shall be only allowed if DcmD-
spDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER, USE_DATA_-
ASYNCH_CLIENT_SERVER_ERROR or USE_DATA_SYNCH_CLIENT_SERVER. Note:
ControlEnableMask larger than 32 bits is a very rare use case. Therefore the Dcm
supports only C/S interfaces to solve this use case.c

7.4.2.15 Service 0x31 - RoutineControl

[SWS_Dcm_00257] dThe Dcm module shall implement the UDS Service RoutineCon-
trol (0x31) for subFunctions startRoutine, stopRoutine and requestsRoutineResults.c

A tester can use UDS Service 0x31 to start, stop or obtain the results of a routine
identified by a 2-byte routineIdentifier. The Dcm module configuration contains a list
of the routineIdentifiers (see configuration parameter DcmDspRoutineIdentifier)
supported by the DCM. For each routineIdentifier, the Dcm configuration specifies:
• The function Xxx_Start() associated with this routineIdentifier (see configuration
parameters DcmDspStartRoutineFnc, DcmDspRoutineUsePort and DcmD-
spRoutineFncSignature)
• List of signal available in the request and in the response (see configuration pa-
rameters DcmDspStartRoutineIn and DcmDspStartRoutineOut)

198 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• The function Xxx_Stop() associated with this routineIdentifier (see configuration

parameters DcmDspStopRoutineFnc, DcmDspRoutineUsePort and DcmD-
spRoutineFncSignature)
• List of signal available in the request and in the response (see configuration pa-
rameters DcmDspStopRoutineIn and DcmDspStopRoutineOut)
• The function Xxx_RequestResults() associated with this routineIdentifier
(see configuration parameters DcmDspRequestRoutineResultsFnc, DcmD-
spRoutineUsePort and DcmDspRoutineFncSignature)
• List of signal available in the request and in the response (see configuration
parameters DcmDspRequestRoutineResultsIn and DcmDspRequestRou-
tineResultsOut)

[SWS_Dcm_01442]
Upstream requirements: RS_Diag_04224

dIf DcmDspRoutineUsePort is set to true, the Dcm shall call the corresponding oper-
ation of the C/S interfaces RoutineServices_RoutineName to process this routine.c

A routine handler processes the diagnostic routine control request. The Dcm passes the
routineControlOption as input parameters to the routine handler. The routine processes
the request and writes the result to the output parameters of the routine handler call.
In case of shared Rx and Tx buffer, there are two cases where writing to the output
parameters of the routine control can cause overwriting of the input parameters:
• a routine control uses arrays as output parameters (call by reference)
• a routine control writes to output parameters and returns DCM_E_PENDING. It
is called again with DcmOpstatus set to DCM_PENDING. The input parameters
are derived from the Rx buffer that was overwritten by the previous write to the
output parameters
For efficient memory consumption it is controllable, if the Dcm applies further strategies
to separate input and output parameters in those situations.

[SWS_Dcm_01580] Input and output consistency during C/S based routine han-
dling
Upstream requirements: RS_Diag_04224

dIf DcmDspRoutineUsePort is set to TRUE and the ClientServerOpera-

tion.diagArgIntegrity of that operation is also set to TRUE, the Dcm shall ensure that
the routine handler in the C/S interfaces RoutineServices_RoutineName writing to the
output parameters will not overwrite the input parameters.c

199 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01581] "Routine argument integrity for C/S calls

Upstream requirements: RS_Diag_04224

dIf DcmDspRoutineUsePort is set to true and DcmDspRoutineInterfaceAr-

gumentIntegrity is configured, the Dcm shall create the corresponding oper-
ation of the C/S interface RoutineServices_RoutineName with ClientServerOpera-
tion.diagArgIntegrity set to DcmDspRoutineInterfaceArgumentIntegrity.c

[SWS_Dcm_CONSTR_06097] Availability of DcmDspRoutineInterfaceArgu-

mentIntegrity dDcmDspRoutineInterfaceArgumentIntegrity shall only be
available if the corresponding DcmDspRoutine has DcmDspRoutineUsePort is set
to true.c

[SWS_Dcm_01443]
Upstream requirements: RS_Diag_04224

dIf DcmDspRoutineUsePort is set to false, the Dcm shall use the configured callout
functions for routine operations.c

[SWS_Dcm_00568] dOn reception of the UDS Service RoutineControl (0x31), the Dcm
module shall check if the Routine is supported (see configuration parameter DcmD-
spRoutine) If not, the Dcm module shall send NRC 0x31 (Request out of range).c

[SWS_Dcm_00569] dIf a Routine is set as unused (DcmDspRoutineUsed set

to FALSE), the Dcm shall consider the Routine as not supported (according to
[SWS_Dcm_00568])c

[SWS_Dcm_01555] StartRoutine authentication check

Upstream requirements: RS_Diag_04233

dOn reception of the UDS Service RoutineControl (0x31) with sub-function startRou-
tine, the Dcm shall check if the access to the requested routine identifier is authenti-
cated and process the routine only if:
• for this start routine service a role is configured via DcmDspStartRoutineRol-
eRef and the verification according to [SWS_Dcm_01522] was successful or
• the active white list on that connection has one RID entry with sub-function ac-
cess set to startRoutine that matches that service and sub-function.
c

200 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01556] StopRoutine authentication check

Upstream requirements: RS_Diag_04233

dOn reception of the UDS Service RoutineControl (0x31) with sub-function stopRou-
tine, the Dcm shall check if the access to the requested routine identifier is authenti-
cated and process the routine only if:
• for this stop routine service a role is configured via DcmDspStopRoutineRol-
eRef and the verification according to [SWS_Dcm_01522] was successful or
• the active white list on that connection has one RID entry with sub-function ac-
cess set to stopRoutine that matches that service and sub-function.
c

[SWS_Dcm_01557] RequestRoutineResult authentication check

Upstream requirements: RS_Diag_04233

dOn reception of the UDS Service RoutineControl (0x31) with sub-function reque-
stRoutineResult, the Dcm shall check if the access to the requested routine identifier
is authenticated and process the routine only if:
• for this request routine results service a role is configured via DcmD-
spRequestRoutineResultsRoleRef and the verification according to
[SWS_Dcm_01522] was successful or
• the active white list on that connection has one RID entry with sub-function ac-
cess set to requestRoutineResults that matches that service and sub-function.
c

According to [SWS_Dcm_01537] the authentication checks are only executed if

DcmDspAuthentication is configured. In case of a failed authentication the NRC
handling is according to [SWS_Dcm_01544] and [SWS_Dcm_01551] applies.
The service RoutineControl (0x31) is of exotic nature and has both, a sub-function and
an identifier. UDS defines a different behavior for this service. Permission checks for
session and security are done on identifier level rather than on sub-function level.

[SWS_Dcm_CONSTR_06100] Same session and security settings for same rou-

tine identifier dAll DcmDspCommonAuthorization that are referenced via DcmD-
spStartRoutineCommonAuthorizationRef, DcmDspStopRoutineCommonAu-
thorizationRef or DcmDspRequestRoutineResultsCommonAuthorization-
Ref from a the same DcmDspRoutine, shall have the same (identical) set of ref-
erenced DcmDspCommonAuthorizationSecurityLevelRef and DcmDspCommo-
nAuthorizationSessionRef.c

201 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00570] dOn reception of the UDS Service RoutineControl (0x31), the Dcm
module shall check if the Routine can be executed in the current session (see con-
figuration parameters DcmDspStartRoutineCommonAuthorizationRef, DcmD-
spStopRoutineCommonAuthorizationRef and DcmDspRequestRoutineRe-
sultsCommonAuthorizationRef). If not, the Dcm module shall send a NRC 0x31
(Request Out of Range).c

[SWS_Dcm_00571] dOn reception of the UDS Service RoutineControl (0x31), the

Dcm module shall check if the Routine can be executed in the current secu-
rity level (see configuration parameter DcmDspStartRoutineCommonAuthoriza-
tionRef, DcmDspStopRoutineCommonAuthorizationRef and DcmDspReque-
stRoutineResultsCommonAuthorizationRef). If not, the Dcm module shall send
NRC 0x33 (Security access denied).c

[SWS_Dcm_00869] dOn reception of the UDS Service RoutineControl (0x31), the

Dcm module shall check if the SubFunction to the corresponding Routine is supported
(see existence of configuration container DcmDspStopRoutine for SubFunction 0x02;
DcmDspRequestRoutineResults for SubFunction 0x03). If not, the Dcm module
shall send NRC 0x12 (SubFunction not supported).c

[SWS_Dcm_01169] dOn reception of the UDS Service RoutineControl (0x31) with Sub-
Function startRoutine, the Dcm module shall check if the Routine can be executed in
the current mode condition (see configuration parameter DcmDspStartRoutineCom-
monAuthorizationRef). If not, the Dcm module shall send the calculated negative
response code of the referenced DcmModeRule.c

[SWS_Dcm_01170] dOn reception of the UDS Service RoutineControl (0x31) with Sub-
Function stopRoutine, the Dcm module shall check if the Routine can be executed in
the current mode condition (see configuration parameter DcmDspStopRoutineCom-
monAuthorizationRef). If not, the Dcm module shall send the calculated negative
response code of the referenced DcmModeRule.c

[SWS_Dcm_01171] dOn reception of the UDS Service RoutineControl (0x31) with Sub-
Function requestRoutineResults, the Dcm module shall check if the Routine can be
executed in the current mode condition (see configuration parameter DcmDspReque-
stRoutineResultsCommonAuthorizationRef). If not, the Dcm module shall send
the calculated negative response code of the referenced DcmModeRule.c

Routines have different input and output parameters depending on the routine con-
figuration (e.g. DcmDspStartRoutineIn for input parameter for the routine start
service). The signature of the called routine operations Xxx_Start, Xxx_Stop and
Xxx_RequestResults is depending on this configuration. The defined parameters for
input and output routine data are optional, and marked in brackets ’[]’ in the definition
in [SWS_Dcm_01203], [SWS_Dcm_01204] and [SWS_Dcm_91013].

202 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01360] dFor each configured routine input signal in DcmDspStartRou-

tineInSignal, DcmDspStopRoutineInSignal or DcmDspRequestRoutineRe-
sultsInSignal with a signal type unequal to VARIABLE_LENGTH, the optional pa-
rameter ’DcmDspRoutineSignalType dataIn_n’ shall be provided in the corresponding
operations in [SWS_Dcm_01203], [SWS_Dcm_01204] or [SWS_Dcm_91013].c

[SWS_Dcm_01361] dFor a configured routine input signal in DcmDspStartRou-

tineInSignal, DcmDspStopRoutineInSignal or DcmDspRequestRoutineRe-
sultsInSignal with a signal type equal to VARIABLE_LENGTH the optional pa-
rameter const ’uint8 * dataInVar’ shall be provided in the corresponding operations in
[SWS_Dcm_01203] [SWS_Dcm_01204] or [SWS_Dcm_91013].c

[SWS_Dcm_01362] dFor each configured routine output signal in DcmDsp-

StartRoutineOutSignal, DcmDspStopRoutineOutSignal or DcmDspReque-
stRoutineResultsOutSignal with a signal type unequal to VARIABLE_LENGTH
the optional parameter ’DcmDspRoutineSignalType dataOut_n’ shall be provided
in the corresponding operations in [SWS_Dcm_01203], [SWS_Dcm_01204] or
[SWS_Dcm_91013].c

[SWS_Dcm_01363] dFor a configured routine output signal in DcmDspStartRouti-

neOutSignal, DcmDspStopRoutineOutSignal or DcmDspRequestRoutineRe-
sultsOutSignal with a signal type equal to VARIABLE_LENGTH the optional pa-
rameter const ’uint8 * dataOutVar’ shall be provided in the corresponding operations in
[SWS_Dcm_01203], [SWS_Dcm_01204] or [SWS_Dcm_91013].c

[SWS_Dcm_01364] dThe optional in/out parameter currentDataLength in

[SWS_Dcm_01203], [SWS_Dcm_01204] or [SWS_Dcm_91013] is always present if
at least one of the routine input signal data or routine output signal data have a signal
with routine type ’VARIABLE_LENGTH’.c

Note: The ’currentDataLength’ parameter as in/out parameter contains the data length
in bytes of the ’dataInVar’ while calling the operation and it returns the length in bytes
of the ’dataOutVar’. As ’dataInVar’ and ’dataOutVar’ are optional, ’currentDataLength’
is only present if at least one of this optional parameter is used.

[SWS_Dcm_00590] dWhen receiving a request for UDS Service RoutineControl

(0x31) if all verifications have been successfully done (see [SWS_Dcm_00568],
[SWS_Dcm_00570], [SWS_Dcm_00571]), the Dcm module shall split the routineCon-
trolOptionRecord received according of the list of input signal configured for this routine
( see configuration parameters DcmDspStartRoutineIn, DcmDspStopRoutineIn,
DcmDspRequestRoutineResultsIn)c

[SWS_Dcm_01614] DRAFT dWhen receiving a request for UDS Service RoutineCon-

trol (0x31) if all verifications have been successfully done (see [SWS_Dcm_00568],

203 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00570], [SWS_Dcm_00571]) and DcmDspRoutineFncSignature is

set to ROUTINE_FNC_PROXY the Dcm module shall pass the routineControlOption-
Record to the called function and send back the resulting routineStatusRecord via the
dataInOut parameter where the currentDataLength denotes the size of the passed rou-
tineControlOptionRecord and returned routineStatusRecord.c

[SWS_Dcm_00400] dWhen receiving a request for UDS Service RoutineControl (0x31)

with subfunction startRoutine, if all verifications have been successfully done (see
[SWS_Dcm_00568], [SWS_Dcm_00570], [SWS_Dcm_00571]), the Dcm module shall
call the configured Xxx_Start() function passing the dataIn, calculated from routineCon-
trolOptionRecord (see [SWS_Dcm_00590]), and the dataOut reference according of
the list of output signal configured for this routine ( see configuration parameter DcmD-
spStartRoutineOut).c

[SWS_Dcm_00401] dUpon completing [SWS_Dcm_00400], when Xxx_Start() returns

E_OK, the Dcm module shall reply with a positive response with the data returned
by Xxx_Start() in the dataOut as routineStatusRecord (dataOut are merged according
to the list of output signal configured for this routine ( see configuration parameter
DcmDspStartRoutineOut)).c

[SWS_Dcm_01615] DRAFT dWhen receiving a request for UDS Service RoutineCon-

trol (0x31) with subfunction startRoutine, if all verifications have been successfully
done (see [SWS_Dcm_00568], [SWS_Dcm_00570], [SWS_Dcm_00571]) and DcmD-
spRoutineFncSignature is set to ROUTINE_FNC_PROXY, the Dcm module shall call
the configured Xxx_Start() function passing the routineControlOptionRecord via (see
[SWS_Dcm_01614]) and if Xxx_Start() returned E_OK reply the returned routineSta-
tusRecord with a positive response.c

[SWS_Dcm_00402] dWhen receiving a request for UDS Service RoutineControl (0x31)

with subfunction stopRoutine, if all verifications have been successfully done (see
[SWS_Dcm_00568], [SWS_Dcm_00570], [SWS_Dcm_00571]), the Dcm module shall
call the configured Xxx_Stop() function passing the dataIn, calculated from routineCon-
trolOptionRecord (see [SWS_Dcm_00590]), and the dataOut reference according of
the list of output signal configured for this routine ( see configuration parameter DcmD-
spStopRoutineOut).c

[SWS_Dcm_00403] dUpon completing [SWS_Dcm_00402], when Xxx_Stop() returns

E_OK, the Dcm module shall reply with a positive response with the data returned
by Xxx_Stop()in the dataOut as routineStatusRecord (dataOut are merged according
to the list of output signal configured for this routine ( see configuration parameter
DcmDspStopRoutineOut)).c

[SWS_Dcm_01616] DRAFT dWhen receiving a request for UDS Service RoutineCon-

trol (0x31) with subfunction stopRoutine, if all verifications have been successfully

204 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

done (see [SWS_Dcm_00568], [SWS_Dcm_00570], [SWS_Dcm_00571]) and DcmD-

spRoutineFncSignature is set to ROUTINE_FNC_PROXY, the Dcm module shall call
the configured Xxx_Stop() function passing the routineControlOptionRecord via (see
[SWS_Dcm_01614]) and if Xxx_Stop() returned E_OK reply the returned routineSta-
tusRecord with a positive response.c

[SWS_Dcm_00404] dWhen receiving a request for UDS Service RoutineControl (0x31)

with subfunction requestRoutineResults, if all verifications have been successfully done
(see [SWS_Dcm_00568], [SWS_Dcm_00570], [SWS_Dcm_00571]), the Dcm module
shall call the configured Xxx_RequestResults() function passing the dataIn, calculated
from routineControlOptionRecord (see [SWS_Dcm_00590])and provide the dataOut
reference according of the list of output signal configured for this routine ( see configu-
ration parameter DcmDspRequestRoutineResultsOut).c

[SWS_Dcm_00405] dUpon completing [SWS_Dcm_00404], when

Xxx_RequestResults() returns E_OK, the Dcm module shall reply with a positive
response with the data returned by Xxx_RequestResults()in the dataOut as routineS-
tatusRecord (dataOut are merged according to the list of output signal configured for
this routine ( see configuration parameter DcmDspRequestRoutineResultsOut)).c

[SWS_Dcm_01617] DRAFT dWhen receiving a request for UDS Service RoutineCon-

trol (0x31) with subfunction requestRoutineResults, if all verifications have been suc-
cessfully done (see [SWS_Dcm_00568], [SWS_Dcm_00570], [SWS_Dcm_00571])
and DcmDspRoutineFncSignature is set to ROUTINE_FNC_PROXY, the Dcm mod-
ule shall call the configured Xxx_RequestResults() function passing the routineCon-
trolOptionRecord via (see [SWS_Dcm_01614]) and if Xxx_RequestResults() returned
E_OK, reply the returned routineStatusRecord with a positive response.c

[SWS_Dcm_00641] dTo serialize the required AUTOSAR data types (signed- and un-
signed integer) from the request message / into the response message of UDS Service
RoutineControl, the target endianness configured in DcmDspRoutineSignalEndi-
anness shall be considered for DcmDspRoutine signals having DcmDspRoutineS-
ignalType set to fixed length (DcmDspRoutineSignalType set to other value than
VARIABLE_LENGTH).c

[SWS_Dcm_CONSTR_06072] Dependency for DcmDspRoutineSignalEndian-

ness dIn case DcmDspRoutineSignalEndianness is not present, the DcmDsp-
DataDefaultEndianness shall be used instead.c

[SWS_Dcm_01139] dThe Dcm shall follow the NRC handling for RoutineControlService
according to ISO 14229-1 [1].c

[SWS_Dcm_01140] dOn reception of the UDS Service RoutineControl (0x31), the Dcm
module shall check the overall length of the request. If length of the request is wrong,

205 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

the Dcm module shall send NRC 0x13 (Incorrect message length or invalid format) to
the tester.c

[SWS_Dcm_01141] dThe Dcm shall call the appropriate routine functions of the SWC
after having performed the total length check and the Mode rules, security level
and session checks (DcmDspStartRoutineCommonAuthorizationRef, DcmD-
spStopRoutineCommonAuthorizationRef and DcmDspRequestRoutineRe-
sultsCommonAuthorizationRef).c

Note: Subsequent checks have to be performed by the SWC.

7.4.2.15.1 Handling of OBD RID

[SWS_Dcm_00701] dOn reception of the UDS Service RoutineControl (0x31), for every
requested RID inside the OBD range (E000-E0FF) and usage of UDS interface, the Dcm
module shall use the routineInfo byte value from DcmDspRoutineInfoByte in the
response to the tester.c

[SWS_Dcm_01330] dIf DcmDspEnableObdMirror is set to true, an explicitly config-

ured RID inside the OBD range (E000-E0FF) shall use the UDS interface.c

[SWS_Dcm_01331] dIf DcmDspEnableObdMirror is set to false, all requests within

the OBD RID range shall use the UDS interface.c

[SWS_Dcm_01332] dOn reception of the UDS Service RoutineControl (0x31), for every
requested RID inside the OBD range (E000-E0FF), the Dcm module shall handle the
RID as defined for OBD Service $08 (see [SWS_Dcm_00418], [SWS_Dcm_00947],
[SWS_Dcm_00419], [SWS_Dcm_00420], [SWS_Dcm_00948], [SWS_Dcm_01192]) if
DcmDspEnableObdMirror is set to true and RID not explicitly configured.c

[SWS_Dcm_01333] dOn reception of the UDS Service RoutineControl (0x31), for every
requested RID inside the OBD range (E000-E0FF) and usage of OBD interface, the Dcm
shall use the routineInfo byte value from DcmDspRequestControlInfoByte in the
response to the tester.c

If DcmDspEnableObdMirror is set to FALSE or the RID is explicitly configured inside

the OBD TestId range (E000-E0FF), the access to the OBD data shall be given in the
following way:

206 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01390] dOn reception of an UDS Service RoutineControl (0x31) request

with one or more ”availability OBDTestIds” as parameter, the Dcm module shall respond
with the corresponding supported (=configured) RIDs.c

[SWS_Dcm_01392] dOn reception of an UDS Service RoutineControl (0x31) request

with a OBDTestIds that is not an ”availability OBDTestIds”, the Dcm module shall invoke
the configured Xxx_Start() function.c

[SWS_Dcm_01393] dAs specified in [4, SAE J1979], unused data bytes shall be filled
with $00.c

[SWS_Dcm_CONSTR_06071] Dependency for DcmDspStartRoutineFnc, DcmD-

spStopRoutineFnc, DcmDspRequestRoutineResultsFnc, DcmDspStartRou-
tineConfirmationFnc, DcmDspStopRoutineConfirmationFnc dThe following
configuration parameters shall only be present if DcmDspRoutineUsePort is set to
FALSE.
• DcmDspStartRoutineFnc
• DcmDspStopRoutineFnc
• DcmDspRequestRoutineResultsFnc
• DcmDspStartRoutineConfirmationFnc
• DcmDspStopRoutineConfirmationFnc
c

7.4.2.16 Service 0x3E - Tester Present

[SWS_Dcm_00251] dThe Dcm module shall implement the Tester Present (service
0x3E, diagnostic communication and security) of the Unified Diagnostic Services for
the subfunction values 0x00 and 0x80.c

[SWS_Dcm_01558] Skipping authentication check for tester present

Upstream requirements: RS_Diag_04230

dThe Dcm shall process the UDS service 0x3E (TesterPresent) independently from the
current authentication state.c

This service is used to keep one or multiple servers in a diagnostic session being
different than the defaultSession.

207 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.2.17 Service 0x3D - WriteMemoryByAddress

[SWS_Dcm_00488] dThe Dcm module shall implement the WriteMemoryByAddress

(service 0x3D) of the Unified Diagnostic Services.c

This service is used to write data using a physical memory address.

[SWS_Dcm_00855] dOn reception of the UDS Service WriteMemoryByAddress

(0x3D), the Dcm shall check if the requested AddressAndLengthFormatIdenti-
fier is supported (refer to configuration parameter DcmDspSupportedAddressAn-
dLengthFormatIdentifier), Otherwise the NRC 0x31 (requestOutOfRange) shall
be responded. In case the container AddressAndLengthFormatIdentifier is not
present, the Dcm shall accept all possible AddressAndLengthFormatIdentifiers.c

[SWS_Dcm_00489] dOn reception of the UDS Service WriteMemoryByAddress

(0x3D), the Dcm shall check if the complete memory range to write to (from ’mem-
oryAddress’ parameter to ’memoryAddress + memorySize -1’) is inside the allowed
memory ranges (check of DcmDspWriteMemoryRangeLow and DcmDspWriteMem-
oryRangeHigh parameters for each DcmDspWriteMemoryRangeInfo container
or DcmDspWriteMemoryRangeByLabelLow and DcmDspWriteMemoryRangeBy-
LabelHigh parameters for each DcmDspWriteMemoryRangeByLabelInfo con-
tainer). If not, the Dcm module shall send NRC 0x31 (Request out of range).c

[SWS_Dcm_00490] dOn reception of the UDS Service WriteMemoryByAddress

(0x3D), the Dcm shall check if the complete memory range (from ’memoryAddress’
parameter to ’memoryAddress + memorySize -1’) can be written in the current secu-
rity level (see DcmDspWriteMemoryRangeSecurityLevelRef). If security level is not
correct, the Dcm module shall send NRC 0x33 (securityAccessDenied).c

[SWS_Dcm_00825] dOn reception of the UDS Service WriteMemoryByAddress

(0x3D), the Dcm shall check if the complete memory range (from ’memoryAddress’
parameter to ’memoryAddress + memorySize -1’) can be written in the current mode
condition (see DcmDspWriteMemoryRangeModeRuleRef). If mode condition is not
correct, the Dcm module shall send the calculated negative response code of the refer-
enced dcmModeRule.c

[SWS_Dcm_00491] dOn reception of the UDS Service WriteMemoryByAddress

(0x3D), and after verification of the validity of the request (see [SWS_Dcm_00489]
and [SWS_Dcm_00490]) the Dcm module shall call the callout Dcm_WriteMemory.c

208 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01052] dOn reception of the UDS Service WriteMemoryByAddress

(0x3D), if the request message contains different MemoryIdValue compare to the con-
figured values in DcmDspMemoryIdInfo container, the Dcm shall send a NRC 0x31
(RequestOutOfRange).c

[SWS_Dcm_01056] dThe configured ranges of memory address (DcmDspReadMemo-

ryRangeHigh and DcmDspReadMemoryRangeLow or DcmDspReadMemoryRange-
ByLabelHigh and DcmDspReadMemoryRangeByLabelLow) shall not overlap each
other.c

[SWS_Dcm_01358] dOn reception of the UDS Service WriteMemoryByAddress

(0x3D), the Dcm shall check if the complete memory range (from ’memoryAddress’
parameter to ’memoryAddress + memorySize -1’) can be written in the current session
(see DcmDspWriteMemoryRangeSessionLevelRef). If the session is not correct, the
Dcm module shall send NRC 0x31 (RequestOutOfRange).c

[SWS_Dcm_00643] dIf the operation Dcm_WriteMemory returns

DCM_WRITE_FAILED, the Dcm module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.c

[SWS_Dcm_00837]
Upstream requirements: RS_Diag_04249

dIf the call to Dcm_WriteMemory returns DCM_WRITE_FORCE_RCRRP, the Dcm

shall invoke the transmit request for RCR-RP (NRC 0x78 transmission) and the Dcm
shall not realize further invocation of the operation till RCR-RP is transmitted.c

[SWS_Dcm_00838] dAfter transmit confirmation of a RCR-RP transmitted on the con-

text of [SWS_Dcm_00837], the Dcm calls, from Dcm_MainFunction (due to call con-
text), Dcm_WriteMemory again with OpStatus = DCM_FORCE_RCRRP_OK.c

7.4.2.18 Service 0x23 - ReadMemoryByAddress

This service is used to read data using a physical memory address.

[SWS_Dcm_00492] dThe Dcm module shall implement the ReadMemoryByAddress

(service 0x23) of the Unified Diagnostic Services.c

[SWS_Dcm_00853] dOn reception of the UDS Service ReadMemoryByAddress

(0x23), the Dcm shall check if the requested AddressAndLengthFormatIdenti-
fier is supported (refer to configuration parameter DcmDspSupportedAddressAn-
dLengthFormatIdentifier), Otherwise the NRC 0x31 (requestOutOfRange) shall

209 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

be responded. In case the container DcmDspAddressAndLengthFormatIdenti-

fier is not present, the Dcm shall accept all possible AddressAndLengthFormatIden-
tifiers. ).c

[SWS_Dcm_00493] dOn reception of the UDS Service ReadMemoryByAddress

(0x23), the Dcm shall check if the complete memory range to read from (from
’memoryAddress’ parameter to ’memoryAddress + memorySize -1’) is inside the al-
lowed memory ranges (check of DcmDspReadMemoryRangeLow and DcmDspRead-
MemoryRangeHigh parameters for each DcmDspReadMemoryRangeInfo container
or DcmDspReadMemoryRangeByLabelLow and DcmDspReadMemoryRangeByLa-
belHigh parameters for each DcmDspReadMemoryRangeByLabelInfo container).
If not, the Dcm module shall send NRC 0x31 (Request out of range).c

[SWS_Dcm_00494] dOn reception of the UDS Service ReadMemoryByAddress

(0x23), the Dcm shall check if the complete memory range (from ’memoryAddress’
parameter to ’memoryAddress + memorySize -1’) can be readen in the current secu-
rity level (see DcmDspReadMemoryRangeSecurityLevelRef). If security level is not
correct, the Dcm module shall send NRC 0x33 (securityAccessDenied).c

[SWS_Dcm_00826] dOn reception of the UDS Service ReadMemoryByAddress

(0x23), the Dcm shall check if the complete memory range (from ’memoryAddress’
parameter to ’memoryAddress + memorySize -1’) can be readen in the current mode
condition (see DcmDspReadMemoryRangeModeRuleRef). If mode condition is not
correct, the Dcm module shall send calclulated negative response code of the refer-
enced DcmModeRule.c

[SWS_Dcm_00495] dOn reception of the UDS Service ReadMemoryByAddress

(0x23), and after verification of the validity of the request (see [SWS_Dcm_00493]
and [SWS_Dcm_00494]) the Dcm module shall call the callout Dcm_ReadMemory.c

[SWS_Dcm_01053] dOn reception of the UDS Service ReadMemoryByAddress

(0x23), if the request message contains different MemoryIdValue compare to the con-
figured values in DcmDspMemoryIdInfo container, the Dcm shall send a NRC 0x31
(RequestOutOfRange).c

[SWS_Dcm_01158] dThe configured ranges of memory address (DcmDspReadMemo-

ryRangeHigh and DcmDspReadMemoryRangeLow or DcmDspReadMemoryRange-
ByLabelHigh and DcmDspReadMemoryRangeByLabelLow) shall not overlap each
other.c

[SWS_Dcm_01359] dOn reception of the UDS Service ReadMemoryByAddress

(0x23), the Dcm shall check if the complete memory range (from ’memoryAddress’
parameter to ’memoryAddress + memorySize -1’) can be read in the current session

210 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

(see DcmDspReadMemoryRangeSessionLevelRef). If the session is not correct, the

Dcm module shall send NRC 0x31 (RequestOutOfRange).c

[SWS_Dcm_00644] dIf the operation Dcm_ReadMemory returns

DCM_READ_FAILED, the Dcm module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.c

[SWS_Dcm_00839]
Upstream requirements: RS_Diag_04249

dIf the call to Dcm_ReadMemory returns DCM_READ_FORCE_RCRRP, the Dcm shall

invoke the transmit request for RCR-RP (NRC 0x78 transmission) and the Dcm shall
not realize further invocation of the operation till RCR-RP is transmitted.c

[SWS_Dcm_00840] dAfter transmit confirmation of a RCR-RP transmitted on the con-

text of [SWS_Dcm_00839], the Dcm calls, from Dcm_MainFunction (due to call con-
text), Dcm_ReadMemory again with OpStatus = DCM_FORCE_RCRRP_OK.c

7.4.2.19 Service 0x34 - RequestDownload

This service is used to request the start of a download process.

[SWS_Dcm_00496]
Upstream requirements: RS_Diag_04033

dThe Dcm module shall implement the RequestDownload (service 0x34) of the Unified
Diagnostic Services.c

[SWS_Dcm_00856] dOn reception of the UDS ServiceRequestDownload (0x34), the

Dcm shall check if the requested AddressAndLengthFormatIdentifier is sup-
ported (refer to configuration parameter DcmDspSupportedAddressAndLength-
FormatIdentifier), Otherwise the NRC 0x31 (requestOutOfRange) shall be re-
sponded. In case the container AddressAndLengthFormatIdentifier is not
present, the Dcm shall accept all possible AddressAndLengthFormatIdentifiers.c

[SWS_Dcm_01057] dOn reception of the UDS ServiceRequestDownload (0x34), if the

request message contains different MemoryIdValue compare to the configured values
in DcmDspMemoryIdInfo container, the Dcm shall send a NRC 0x31 (RequestOut-
OfRange).c

[SWS_Dcm_01132] dNRC described in [SWS_Dcm_01662] shall be the responsibility

of the callout function.c

211 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01662] NRC managed by callout function for service 0x34 d

NRC Use Case
0x31 requestOutOfRange The specified dataFormatIdentifier is not valid.
0x70 uploadDownload- An attempt to download to a server’s memory cannot be
NotAccepted accomplished due to some fault conditions.
Note: this NRC will be handled by the callout only if mode rule is
not used for this case

Note: the callout function can, if needed, return also other NRC but the ones above
won’t be treated by the Dcm module.

[SWS_Dcm_01591] Processing request download without RTE

Upstream requirements: RS_Diag_04033

dIf DcmDspMemoryTransferUsePort is set to FALSE, the Dcm shall call Dcm_Pro-

cessRequestDownload to process the request.c

[SWS_Dcm_00757] dIf the operation Dcm_ProcessRequestDownload returns

value E_NOT_OK, the Dcm module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.c

[SWS_Dcm_01417]
Upstream requirements: RS_Diag_04033

dUpon calling Dcm_ProcessRequestDownload, the Dcm shall write the maximum

possible buffer size into the BlockLength parameter.c

[SWS_Dcm_01418]
Upstream requirements: RS_Diag_04033

dIf the function call Dcm_ProcessRequestDownload returns a requested buffer

length larger than the supported buffer length of the current protocol connection, the
Dcm shall report the Det error DCM_E_INTERFACE_BUFFER_OVERFLOW .c

For definition of DCM_E_INTERFACE_BUFFER_OVERFLOW see [SWS_Dcm_00040].

[SWS_Dcm_01419]
Upstream requirements: RS_Diag_04033

dIf the function call Dcm_ProcessRequestDownload returns a requested buffer

length smaller or equal than the supported buffer length of the current protocol con-
nection, the Dcm shall return the BlockLength value within the maxNumberOfBlock-
Length parameter of the positive response.c

212 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.2.20 Service 0x35 - RequestUpload

This service is used to request the start of a upload process.

[SWS_Dcm_00499]
Upstream requirements: RS_Diag_04033

dThe Dcm module shall implement the RequestUpload (service 0x35) of the Unified
Diagnostic Services.c

[SWS_Dcm_00857] dOn reception of the UDS RequestUpload (0x35), the Dcm shall
check if the requested AddressAndLengthFormatIdentifier is supported (refer
to configuration parameter DcmDspSupportedAddressAndLengthFormatIden-
tifier), Otherwise the NRC 0x31 (requestOutOfRange) shall be responded. In case
the container AddressAndLengthFormatIdentifier is not present, the Dcm shall
accept all possible AddressAndLengthFormatIdentifiers.c

[SWS_Dcm_01055] dOn reception of the UDS RequestUpload (0x35), if the request

message contains different MemoryIdValue compare to the configured values in DcmD-
spMemoryIdInfo container, the Dcm shall send a NRC 0x31 (RequestOutOfRange).c

[SWS_Dcm_01133] dNRC described in [SWS_Dcm_01663] shall be the responsibility

of the callout function.c

[SWS_Dcm_01663] NRC managed by callout function for service 0x35 d

NRC Use Case
0x31 - requestOut- The specified dataFormatIdentifier is not valid.
OfRange
0x70 - uploadDownload- An attempt to download to a server’s memory cannot be
NotAccepted accomplished due to some fault conditions.
Note: this NRC will be handled by the callout only if mode rule is
not used for this case

Note: the callout function can, if needed, return also other NRC but the ones above
won’t be treated by the Dcm module.

[SWS_Dcm_01592] Processing request upload without RTE

Upstream requirements: RS_Diag_04033

dIf DcmDspMemoryTransferUsePort is set to FALSE, the Dcm shall call Dcm_Pro-

cessRequestUpload to process the request.c

213 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00758] dIf the operation Dcm_ProcessRequestUpload returns value

E_NOT_OK, the Dcm module shall send a negative response with NRC code equal to
the parameter ErrorCode parameter value.c

[SWS_Dcm_01420]
Upstream requirements: RS_Diag_04033

dUpon calling Dcm_ProcessRequestUpload, the Dcm shall write the maximum pos-
sible buffer size into the BlockLength parameter.c

[SWS_Dcm_01421]
Upstream requirements: RS_Diag_04033

dIf the function call Dcm_ProcessRequestUpload returns a requested buffer length

larger than the supported buffer length of the current protocol connection, the Dcm shall
report the Det error DCM_E_INTERFACE_BUFFER_OVERFLOW .c

For definition of DCM_E_INTERFACE_BUFFER_OVERFLOW see [SWS_Dcm_01416].

[SWS_Dcm_01422]
Upstream requirements: RS_Diag_04033

dIf the function call Dcm_ProcessRequestUpload returns a requested buffer length

smaller or equal than the supported buffer length of the current protocol connection,
the Dcm shall return the BlockLength value within the maxNumberOfBlockLength
parameter of the positive response.c

7.4.2.21 Service 0x36 - TransferData

This service is used to transfer data during a download or upload process.

[SWS_Dcm_00502]
Upstream requirements: RS_Diag_04033

dThe Dcm module shall implement the TransferData (service 0x36) of the Unified Diag-
nostic Services.c

To execute the transfer data request, it is mandatory to have a previous received Re-
questDownload or RequestUpload according to ISO14229-1 [1]. The Dcm will follow
this requirements and track internally if such a request was received before the Trans-
ferData request. This is relevant to check if a NRC 0x24 sequence error has occurred
and to reset the block sequence counter.

214 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01620] Request sequence error check dThe Dcm shall implement the
requestSequenceErrorCheck (NRC 0x24) for RequestDownload, RequestUpload and
RequestFileTransfer operations according to ISO14229-1 [1].c

The Dcm does not track if the data transfer is completed by the memory size parameter.
The NRC 0x24 check for this has to be done in the application. This is a deviation to
ISO14229-1 [1] where the NRC 0x24 check is done on only one place.

[SWS_Dcm_00645] Block sequence counter check dThe Dcm shall realize the block
sequence counter error verification according to ISO14229-1 [1] before the Read or
Write Data calls are realized and return the NRC 0x73 if the block sequence counter of
the request is wrong.c

[SWS_Dcm_00503] Processing transfer data write without RTE

Upstream requirements: RS_Diag_04033

dOn reception of the UDS Service TransferData (0x36), if a download process is running
(RequestDownload service has been previously received), the request format is correct
and DcmDspMemoryTransferUsePort is set to FALSE, the Dcm module shall call the
callout Dcm_ProcessTransferDataWrite.c

[SWS_Dcm_00504] Processing transfer data read without RTE

Upstream requirements: RS_Diag_04033

dOn reception of the UDS Service TransferData (0x36), if an upload process is running
(RequestUpload service has been previously received),the request format is correct
and DcmDspMemoryTransferUsePort is set to FALSE, the Dcm module shall call
the callout Dcm_ProcessTransferDataRead.c

[SWS_Dcm_01444] dOn reception of the UDS Service TransferData (0x36), if a file

download is running (RequestFileTransfer service has been previously received with
0x01 (AddFile) or 0x03 (ReplaceFile)) and the request format is correct, the Dcm mod-
ule shall call the callout Dcm_WriteFile().c

[SWS_Dcm_01445] dOn reception of the UDS Service TransferData (0x36), if a file

or directory information upload is running (RequestFileTransfer service has been pre-
viously received with 0x04 (ReadFile) or 0x05 (ReadDir)) and the request format is
correct, the Dcm module shall call the callout Dcm_ReadFileOrDir().c

[SWS_Dcm_01173] dNRCs described in [SWS_Dcm_01665] shall be the responsibil-

ity of the callout function.c

[SWS_Dcm_01665] NRC managed by callout function for service 0x36 d

215 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

NRC Use Case

0x24 - requestSequenceError only for the following conditions:
If the RequestDownload or RequestUpload service
is active, but the server has already received all
data as determined by the memorySize parameter
in the active RequestDownload or RequestUpload
service
0x31 - requestOutOfRange Only for the following conditions:
The transferRequestParameterRecord contains
additional control parameters (e.g. additional
address information) and this control information is
invalid. The transferRequestParameterRecord is
not consistent with the server’s memory alignment
constraints
0x71 - transferDataSuspended The data transfer operation was halted due to
some fault.
0x72 - generalProgrammingFailure If the server detects an error when finalizing the
data transfer between the client and server (e.g.,
via an integrity check).
0x92 - voltageTooHigh The voltage measured is higher than the maximum
acceptable voltage for downloading data.
0x93 - voltageTooLow The voltage measured is under the minimum
acceptable voltage for downloading data.

Note: the callout function can, if needed, return also other NRCs but the ones above
won’t be treated by the Dcm module.

7.4.2.22 Service 0x37 - RequestTransferExit

This service is used to terminate a download or upload process.

[SWS_Dcm_00505]
Upstream requirements: RS_Diag_04033

dThe Dcm module shall implement the RequestTransferExit (service 0x37) of the Uni-
fied Diagnostic Services.c

[SWS_Dcm_01134] dNRC described in [SWS_Dcm_01664] shall be the responsibility

of the callout function.c

[SWS_Dcm_01664] NRC managed by callout function for service 0x37 d

NRC Use Case
0x24 - requestSequenceError The programming process is not completed when a
request for this service is received.

216 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

NRC Use Case

0x72 - generalProgrammingFailure If the server detects an error when finalizing the
data transfer between the client and server (e.g.,
via an integrity check).

Note: the callout function can, if needed, return also other NRC but the ones above
won’t be treated by the Dcm module.

[SWS_Dcm_01593] Processing transfer exit without RTE

Upstream requirements: RS_Diag_04033

dIf DcmDspMemoryTransferUsePort is set to FALSE, the Dcm shall call Dcm_Pro-

cessRequestTransferExit to process the request.c

[SWS_Dcm_00759] dIf the operation Dcm_ProcessRequestTransferExit returns

value E_NOT_OK, the Dcm module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.c

[SWS_Dcm_01594] Usage of API for RequestTransferExit processing

Upstream requirements: RS_Diag_04033

dIf DcmDspMemoryTransferUsePort is set to false, the Dcm shall use the API
Dcm_ProcessRequestTransferExit to process the RequestTransferExit request.c

[SWS_Dcm_01595] Usage of C/S interface for RequestTransferExit processing

Upstream requirements: RS_Diag_04033

dIf DcmDspMemoryTransferUsePort is set to true, the Dcm shall use the operation
ProcessRequestTransferExit of the C/S interface UploadDownloadServices to pro-
cess the RequestTransferExit request.c

[SWS_Dcm_01596] Mapping of transferRequestParameter

Upstream requirements: RS_Diag_04033

dFor Dcm_ProcessRequestTransferExit and operation ProcessRequestTransfer-

Exit of the C/S interface UploadDownloadServices the Dcm shall use:
• the size in bytes of the transferRequestParameterRecord from the request in the
parameter transferRequestParameterRecordSize
• the transferRequestParameterRecord data of the request in the parameter trans-
ferRequestParameterRecord
c

217 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01597] dFor Dcm_ProcessRequestTransferExit and operation Pro-

cessRequestTransferExit of the C/S interface UploadDownloadServices the Dcm
shall use the size of the implementation data type Dcm_RequestDataArrayType as
in-value for the in/out parameter transferResponseParameterRecordSize.c

[SWS_Dcm_01598] Mapping of transferResponseParameter to the positive re-

sponse
Upstream requirements: RS_Diag_04033

dFor Dcm_ProcessRequestTransferExit and operation ProcessRequestTransfer-

Exit of the C/S interface UploadDownloadServices the Dcm shall use transfer-
ResponseParameterRecordSize bytes of the transferResponseParameterRecord as
transferResponseParameterRecord of the positive response.c

7.4.2.23 Service 0x38 - RequestFileTransfer

[SWS_Dcm_01083] dThe Dcm module shall implement the RequestFileTransfer (ser-

vice 0x38) of the Unified Diagnostic Services.c

This service is used to request the start of a file transfer process according to ISO-
14229-1.

[SWS_Dcm_01446] dIf the DcmRequestFileTransferUsePort is set to TRUE the

Dcm shall use C/S calls of the interface RequestFileTransfer for all RequestFileTransfer
related callouts.c

[SWS_Dcm_01447] dIf the DcmRequestFileTransferUsePort is set to FALSE the

Dcm shall use C function calls for all RequestFileTransfer related callouts.c

[SWS_Dcm_01448] dIf the fileSizeParameterLength parameter in the RequestFile-

Transfer request is present and outside the closed interval [0x01..0x08], the Dcm shall
send a negative response with NRC 0x31 (RequestOutOfRange).c

[SWS_Dcm_01449] dIf the modeOfOperation parameter in the RequestFileTransfer

request is not supported (0x00 or greater than 0x05), the Dcm shall send a negative
response with NRC 0x31 (RequestOutOfRange).c

[SWS_Dcm_01450] dThe Dcm shall process RequestFileTransfer according to [6] and,

in case of modeOfOperation equal to 0x01 (AddFile) call XXX_ProcessRequestAddFile
after the full length check.c

218 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01451] dThe Dcm shall process RequestFileTransfer accord-

ing to [6] and, in case of modeOfOperation equal to 0x02 (DeleteFile) call
XXX_ProcessRequestDeleteFile after the full length check.c

[SWS_Dcm_01452] dThe Dcm shall process RequestFileTransfer accord-

ing to [6] and, in case of modeOfOperation equal to 0x03 (ReplaceFile) call
XXX_ProcessRequestReplaceFile after the full length check.c

[SWS_Dcm_01453] dThe Dcm shall process RequestFileTransfer accord-

ing to [6] and, in case of modeOfOperation equal to 0x04 (ReadFile) call
XXX_ProcessRequestReadFile after the full length check.c

[SWS_Dcm_01454] dThe Dcm shall process RequestFileTransfer accord-

ing to [6] and, in case of modeOfOperation equal to 0x05 (ReadDir) call
XXX_ProcessRequestReadDir after the full length check.c

[SWS_Dcm_01088] dIf any of the file transfer operations XXX_ProcessRequest<yyy>

returns value E_NOT_OK, the Dcm module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.c

[SWS_Dcm_01455] dThe Dcm shall use the value configured in DcmRequestFile-

TransferFileSizeOrDirInfoParameterLength as value sent in fileSizeOrDirIn-
foParameterLength in the response.c

[SWS_Dcm_01090] dThe Dcm shall use the value configured in DcmRequestFile-

TransferFileSizeOrDirInfoParameterLength as number of bytes sent in file-
SizeUncompressedOrDirInfoLength and fileSizeCompressed in the response.c

[SWS_Dcm_01456] dThe Dcm shall use the value configured in DcmRequestFile-

TransferLengthFormatIdentifier as value sent in lengthFormatIdentifier in the
response.c

[SWS_Dcm_01091] dThe Dcm shall use the value configured in DcmRequestFile-

TransferLengthFormatIdentifier as number of bytes sent in maxNumberOf-
BlockLength in the response.c

[SWS_Dcm_01457] dIf the maxNumberOfBlockLength does not fit into the requested
lengthFormatIdentifier number of bytes, the Dcm shall send NRC 0x10 (generalReject).c

[SWS_Dcm_01458] dIf the fileSizeUncompressedOrDirInfoLength or fileSizeCom-

pressed do not fit into the requested fileSizeOrDirInfoParameterLength number of
bytes, the Dcm shall send NRC 0x10 (generalReject).c

219 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.2.24 Service 0x85 - ControlDTCSetting

An external test tool can request an ECU to either disable or enable DTC storage in the
ECUs error memory by sending a UDS Service 0x85 request with sub-function 0x01
("ON") or 0x02 ("OFF").

[SWS_Dcm_00249]
Upstream requirements: RS_Diag_04159

dThe Dcm module shall implement UDS Service ControlDTCSetting (0x85) to enable or
disable the storage of DTCs in the ECUs error memory.c

[SWS_Dcm_01399]
Upstream requirements: RS_Diag_04159

dIf the Dcm receives a ControlDTCSetting (0x85) service with DTCSettingControlOp-

tionRecord != 0xFFFFFF, the Dcm shall send a NRC 0x31 (RequestOutOfRange).c

[SWS_Dcm_01063]
Upstream requirements: RS_Diag_04115

dOn reception of UDS Service 0x85 with subfunction 0x01 (DTCSettingType "ON"), the
Dcm shall call Dem_EnableDTCSetting() with ClientId = Client Id for this Dcm instance
(see DcmDemClientRef).c

[SWS_Dcm_00783] dIn case of Dem_EnableDTCSetting returns

E_OK (see [SWS_Dcm_01063]), the Dcm shall invoke a mode
switch of the ModeDeclarationGroupPrototype DcmControlDTC-
Setting by calling SchM_Switch_<bsnp>_DcmControlDTCSetting
(RTE_MODE_DcmControlDTCSetting_ENABLEDTCSETTING).c

[SWS_Dcm_00406]
Upstream requirements: RS_Diag_04115

dOn reception of UDS Service 0x85 with subfunction 0x02 (DTCSettingType "OFF"), the
Dcm shall call Dem_DisableDTCSetting() with ClientId = Client Id for this Dcm instance
(see DcmDemClientRef).c

[SWS_Dcm_00784] dIn case of Dem_DisableDTCSetting returns

E_OK (see [SWS_Dcm_00406] ), the Dcm shall invoke a mode
switch of the ModeDeclarationGroupPrototype DcmControlDTC-
Setting by calling SchM_Switch_<bsnp>_DcmControlDTCSetting
(RTE_MODE_DcmControlDTCSetting_DISABLEDTCSETTING).c

220 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00751] dIn case the DTCSetting is disabled and a transitions to de-

fault session or upon any diagnostic session change where the new session does
not support UDS Service ControlDTCsetting anymore, the Dcm module shall call
Dem_EnableDTCSetting() with the following parameters
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
and switch the mode DcmControlDTCSetting to DCM_ENABLEDTCSETTING.c

For some use-cases the Dcm may re-enable the controlDTCsetting due to external
changed mode conditions:

[SWS_Dcm_00752] dIn case the DTCSetting is disabled and at least one ref-
erenced arbitrary ModeDeclarationGroupPrototypes (see configuration parameter
DcmDspControlDTCSettingReEnableModeRuleRef) for service ControlDTCSet-
ting (0x85) with DTCSettingType "OFF" (0x02) are not fulfilled anymore, the Dcm mod-
ule shall call Dem_EnableDTCSetting() with the following parameters:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
and switch the mode DcmControlDTCSetting to DCM_ENABLEDTCSETTINGc

Note: If at least one ModeDeclarationGroupPrototypes is configured (see configuration

parameter DcmDspControlDTCSettingReEnableModeRuleRef) for service Con-
trolDTCSetting (0x85) with DTCSettingType "OFF" (0x02), it is recommended to acti-
vate the condition check for the according sub-function 0x02(see configuration param-
eter DcmDsdSubServiceModeRuleRef).
Note: This active observation of the referenced mode declaration groups can either be
achieved by polling the mode condition in each MainFunction cycle or by attaching to
the change notification of mode declaration group (SchM will trigger a BSWEntitiy in
Dcm on changes of this mode declaration group).

[SWS_Dcm_00829] dIf the configuration parameter DcmSupportDTCSettingCon-

trolOptionRecord is set to true and the length of DTCSettingControlOptionRecord
in the request is different from 3 bytes, the Dcm shall return NRC 0x13 (Incorrect mes-
sage length or invalid format).c

[SWS_Dcm_00852] dIf the configuration parameter DcmSupportDTCSettingCon-

trolOptionRecord is set to false and the request contains any data after the sub-
function, the Dcm shall return NRC 0x13 (Incorrect message length or invalid format).c

[SWS_Dcm_01564] dIf the configuration parameter DcmSupportDTCSettingCon-

trolOptionRecord is set to false and the request contains any data after the sub-
function, the Dcm shall return NRC 0x13 (Incorrect message length or invalid format).c

221 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.2.25 Service 0x86 - ResponseOnEvent (RoE)

With the UDS Service ResponseOnEvent (0x86), a tester requests the server to start
or stop transmission of responses initiated by a specified server event.

[SWS_Dcm_01625] Support of ResponseOnEvent

Upstream requirements: RS_Diag_04160

dThe Dcm shall support the UDS service ResponseOnEvent (0x86) and all subfunc-
tions of this service according to ISO 14229-1:2020 [9].c

[SWS_Dcm_01626] Not supported storageState bit

Upstream requirements: RS_Diag_04160

dIf DcmDspRoeStoreEventSupport is set to false and a RoE request is received

with the storeEvent bit set to 1, the Dcm shall send a NRC 0x31 (requestOutOfRange).c

[SWS_Dcm_00894] Support of eventWindowTime

Upstream requirements: RS_Diag_04160

dThe Dcm shall support a eventWindowTime set to infiniteTimeToResponse and pow-

erWindowTime according to ISO 14229-1:2020 [9].c

[SWS_Dcm_01627] DTC status changed trigger

Upstream requirements: RS_Diag_04160

dThe Dcm shall use calls to Dcm_DemTriggerOnDTCStatus() as trigger for changes of

a DTC status.c

The Dcm leaves it open who is calling the Dcm_DemTriggerOnDTCStatus(). How-

ever, the Dcm API is designed to be compatible to the Dem module. If the Dem
is used, it is recommended to map one Dem DTC status trigger notification to
Dcm_DemTriggerOnDTCStatus().

[SWS_Dcm_01410] No onDTCStatusChangedEvents during ClearDiagnosticIn-

formation
Upstream requirements: RS_Diag_04160

dWhile the Dcm is processing a ClearDiagnosticInformation request, the Dcm shall ig-
nore the callback Dcm_DemTriggerOnDTCStatus.c

222 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00135] Discard serviceToRespondToMessage on transmission er-

rors
Upstream requirements: RS_Diag_04160

dThe Dcm shall discard all serviceToRespondTo messages that could not be send due
to transmission errors.c

There is not queuing for failed RoE responses for later transmission.

[SWS_Dcm_01534] Authentication check for service to respond to

Upstream requirements: RS_Diag_04230

dOn transmission of the service to respond to, the Dcm shall perform the service au-
thentication checks and send a positive response only for services that have granted
access to that connection.c

[SWS_Dcm_01628] ResponseOnEvent scheduler rate

Upstream requirements: RS_Diag_04160

dThe Dcm shall implement the RoE scheduler according to ISO 14229-1:2020 [9]
and map the configured scheduler rate DcmDspRoeSchedulerRate to ResponseOn-
EventSchedulerRate from ISO 14229-1:2020 [9].c

[SWS_Dcm_01629] Maximum number of changed DIDs per scheduler

Upstream requirements: RS_Diag_04160

dThe Dcm shall provide the maximum number of changed DIDs per RoE scheduler
by mapping DcmDspRoeMaxNumChangeOfDataIdentfierEvents to MaxNum-
ChangeOfDataIdentfierEvents from ISO 14229-1:2020 [9].c

[SWS_Dcm_CONSTR_06104] dDcmDspRoeMaxNumChangeOfDataIdent-
fierEvents shall be configured, if the Dcm is configured to support service
ResponseOnEvent with subfunction onChangeOfDataIdentifier.c

[SWS_Dcm_01630] Maximum number of comparison of value DIDs per scheduler

Upstream requirements: RS_Diag_04160

dThe Dcm shall provide the maximum number of comparison of DIDs per RoE
scheduler by mapping DcmDspRoeMaxNumChangeOfDataIdentfierEvents to
MaxNumComparisonOfValueEvents from ISO 14229-1:2020 [9].c

[SWS_Dcm_CONSTR_06105] dDcmDspRoeMaxNumChangeOfDataIdent-
fierEvents shall be configured, if the Dcm is configured to support service
ResponseOnEvent with subfunction onComparisonOfValues.c

223 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01631] Maximum supported DID length

Upstream requirements: RS_Diag_04160

dThe Dcm shall provide the maximum length of a DID as input for a ResponseOn-
Event event by mapping DcmDspRoeMaxSupportedDIDLength to MaxSupported-
DIDLength from ISO 14229-1:2020 [9].c

[SWS_Dcm_CONSTR_06106] dDcmDspRoeMaxSupportedDIDLength shall be

configured, if the Dcm is configured to support service ResponseOnEvent with sub-
function onChangeOfDataIdentifier or onComparisonOfValues.c

[SWS_Dcm_01632] Maximum number of changed DTCs per scheduler

Upstream requirements: RS_Diag_04160

dThe Dcm shall provide the maximum number of DTC status change events by map-
ping DcmDspRoeMaxNumOfStoredDTCStatusChangedEvents to MaxNumberOfS-
toredDTCStatusChangedEvents from ISO 14229-1:2020 [9].c

[SWS_Dcm_CONSTR_06107] dDcmDspRoeMaxNumOfStoredDTCSta-
tusChangedEvents shall be configured, if the Dcm is configured to support the
service ResponseOnEvent with subfunction onDTCStatusChange.c

7.4.2.26 Service 0x87 - LinkControl

This service is used to gain bus bandwidth for diagnostic purposes.

The Service LinkControl (0x87) is user optional. There are different project specific
use cases which are not handled in the default Dcm. One use case is to switch the
bandwidth in application an other use case performs an OEM bootloader jump.
Therefore the service LinkControl needs to be implemented project specific as external
service (refer to Chapter 8.8 Dcm as Service-Component).

7.4.3 OBD Services

7.4.3.1 Overview

The following table defines the OBD Services supported by the DCM.
Relevant OBD Ser- Support in the DCM
vice Identifier
$01 Supported
$02 Supported
$03 Supported
$04 Supported

224 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Relevant OBD Ser- Support in the DCM

vice Identifier
$06 Supported
$07 Supported
$08 Supported
$09 Supported
$0A Supported

Table 7.3: Support for OBD services in the DCM

7.4.3.2 General behavior

In many cases, the Dcm protocol allows the bundling of several requests (for example
several "PIDs") and the corresponding bundling of the responses. The descriptions of
the behavior for the individual services do not explicitly consider this. As the Dcm needs
to comply with OBD standard (as is defined through various requirements below), the
Dcm might need to repeat the steps defined below to parse a request and assemble a
valid response.
In a vehicle there can be 3 different types of OBD ECUs:
• Master ECU (one per vehicle)
• Primary ECU (several per vehicle)
• Dependent / Secondary ECUs (several per vehicle)
From the Basic Software point of view Dependent / Secondary ECUs doesn’t need any
specific OBD functionality. In Dependent / Secondary ECUs OBD-relevant information
will not be stored in the Basic Software (e.g. no direct communication with the scan
tool). The respective OBD functionality might be handled in Dependent / Secondary
ECUs by a SWC.
The following OBD requirements are only valid for Master and Primary ECUs. If neces-
sary the OBD requirements differentiate between Master and Primary Requirement.
The following table gives an overview about which OBD functionality must be supported
in a Master ECU, Primary ECU or Dependent / Secondary ECU:
Functionality Master ECU Primary ECU Dependent /
Secondary ECU
OBD Scantool Yes Yes No
Communication

Table 7.4: Overview about OBD functionality in different OBD ECUs

225 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00077]
Upstream requirements: RS_Diag_04058

dWhen calling the DEM module for OBD services, the Dcm module shall use the follow-
ing values for the parameter DTCOrigin:
Service $0A uses DEM_DTC_ORIGIN_PERMANENT_MEMORY
All other services use DEM_DTC_ORIGIN_OBD_RELEVANT_MEMORYc

SAE-J1979 [4] states that the external test equipment shall not request OBD Service
$01/$06/$09 with a mixture of "availability identifiers" and "data containing identifiers".
Therefore the AUTOSAR standard does not define the Dcm behavior in this situation.

7.4.3.3 Service $01 - Request Current Powertrain Diagnostic Data

[SWS_Dcm_00243] dThe Dcm module shall implement the OBD service $01 (Request
Current Powertrain diagnostic Data) in compliance to all provisions of the OBD stan-
dard.c

Using Service $01, an external test tool can request an emission-related ECU to return
PID-values or to return the supported PIDs. OBD reserves certain PIDs for the special
purpose of obtaining the list of available PIDs in a certain range. These PIDs are called
"availability PIDs" and are $00, $20, $40, $60, $80, $A0, $C0 an $E0.
The Dcm collects the PID information from 1 to n SW-Cs. This applies in particular
for PIDs which contain several data values for potentially different sources. Example:
PID$83 reports Nox Sensor Data for sensor 1 and sensor 2 in one composed PID
which might come from different SW-C.
The Dcm configuration defines the PIDs that are available on the ECU. The Dcm con-
figuration defines for each such PID:
• The PID Identifier (see configuration parameter DcmDspPidIdentifier)
• Indication of the PID is used or not (for postbuild configuration) (see configuration
parameter DcmDspPidUsed)
• The size of the PID (see configuration parameter DcmDspPidSize)
• The supported information for this PID (see configuration parameter DcmDsp-
PidSupportInfo)
• List of data (DcmDspPidData) for the PID with the following configuration for
every data
– The length of the data associated with the PID (see configuration parameter
DcmDspPidDataByteSize)

226 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

– The position of the data in the PID (see configuration parameter DcmDsp-
PidByteOffset)
– The reference to the supported information container (see configuration pa-
rameter DcmDspPidDataSupportInfo)
– The Xxx_ReadData() function that the Dcm must call to obtain the current
value of the data or the name of the port that the Dcm uses to obtain the
current value through the RTE from a SW-C (see configuration parameters
DcmDspPidDataReadFnc and DcmDspPidDataUsePort)

[SWS_Dcm_00407] dOn reception of an OBD Service $01 request with only "avail-
ability PIDs" as parameter, the Dcm shall respond with the corresponding supported
(=configured) PIDs encoded according to the OBD standard.c

To obtain the value for a PID, the Dcm uses the configured Xxx_ReadData() functions
for every data of the PID. To provide OBD Service $01, the Dcm relies on external
functions that allow it to obtain the value of the PIDs. There is one such function per
data of every PID that is needed by the DCM.
When using a Xxx_ReadData() function, the Dcm provides a buffer of the correct length,
which is filled by the function with the data PID value.

[SWS_Dcm_00408] dOn reception of an OBD Service $01 request with only PIDs that
are not "availability PIDs", the Dcm shall obtain the current value of these PIDs by
invoking the configured Xxx_ReadData() functions for every data of the PID and shall
return these values as response to Service $01.c

The entity providing the actual implementation of the Xxx_ReadData() function for a
specific signal of a PID might be a SW-C or another basic software module. The origin
of the function is not known to the Dcm but is part of the Dcm configuration. Some
PIDs are provided by the DEM. These PIDs are also explicitly configured in the Dcm
configuration and it is the responsibility of a correct Dcm configuration to make the
Xxx_ReadData() function point to the correct function provided by the DEM.

[SWS_Dcm_CONSTR_06069] Dependency for DcmDspPidDataReadFnc dDcmD-

spPidDataReadFnc shall be only present if DcmDspPidDataUsePort is set to
USE_DATA_SYNCH_FNC.c

For certain PIDs, the Dem provides the function to obtain the PID value. Which PIDs
come from the Dem are part of the Dcm configuration.
Note: For PIDs where Dem provides the function, DcmDspPidDataUsePort for that
PID should be set to USE_DATA_SYNCH_FNC and DcmDspPidDataReadFnc shall
point to the function Dem_DcmReadDataOfPID<NN> where <NN> represents the Id
of the PID.

227 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

The data byte A of the PIDs contain the support status of the subsequent data bytes.
Since not all data values might be available due to the particular vehicle configuration
(e.g. there is only a Nox-sensor 1 available in the vehicle in the example above), the
PID response contains in this data byte A the information about the support status of
the following data values. Note, that the PIDs always contain the same number of bytes
- even if not all values are really available.

[SWS_Dcm_00621] dIf a PID contains support information (presence of DcmDsp-

PidDataSupportInfo container) the Dcm shall add the support information in the
diagnostic response.c

[SWS_Dcm_00622] dIf a PID contains support information (presence of DcmDspPid-

DataSupportInfo container) the Dcm shall calculate the support information value
according to the available data for this PID: for every DcmDspPidData container ex-
isting for this PID, the associated support information bits, referenced in DcmDspPid-
DataSupportInfo, shall be set to onec

The response to the OBD-tester needs to be composed out of the available data values.
Data bytes that are not provided by an SW-C need to be replaced with fill-byte to obtain
a complete PID contents.

[SWS_Dcm_00623] dWhen responding to OBD Service $01, the Dcm shall put fill-bytes
between DcmDspPidData in the PID whenever content bytes are missing in order to
fit to the PID size (see configuration parameter DcmDspPidSize).c

[SWS_Dcm_00944] dThe Dcm shall set the fill bytes to 0x00.c

Note: If other fill-bytes than 0x00 are needed by legistlation, the application has to
provide the value of the fill-byte.

[SWS_Dcm_00718] dTo serialize the required AUTOSAR data types (signed- and
unsigned integer) into the response message of OBD Service $01 responses
the target endianness configured in DcmDspPidDataEndianness shall be con-
sidered for DcmDspPidData elements having DcmDspPidDataUsePort set to
USE_DATA_SENDER_RECEIVER or USE_DATA_SENDER_RECEIVER_AS_SERVICE.
In case DcmDspPidDataEndianness is not present, the DcmDspDataDefault-
Endianness shall be used instead.c

[SWS_Dcm_CONSTR_06068] Dependency for DcmDspPidDataEndianness dIn

case DcmDspPidDataEndianness is not present, the DcmDspDataDefaultEndi-
anness shall be used instead.c

228 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.3.4 Service $02 - Request Power Train FreezeFrame Data

[SWS_Dcm_00244] dThe Dcm shall implement OBD Service $02 (Request Power Train
FreezeFrame Data) in compliance to all provisions of the OBD standard.c

For OBD-relevant FreezeFrames AUTOSAR only supports frame 0, which is the mini-
mum required by legislation.

[SWS_Dcm_00409] dThe Dcm shall ignore all requests regarding record-numbers that
are not 0c

[SWS_Dcm_00972] dOn reception of an OBD Service $02 request with a mixure of

"availability PIDs" and not "availability PIDs", this request shall be ignored by the
Dcm.c

[SWS_Dcm_00973] dWhen responding to OBD Service $02, the Dcm shall put fill-bytes
between DcmDspPidData in the PID whenever content bytes are missing in order to
fit to the PID size (see configuration parameter DcmDspPidSize).c

[SWS_Dcm_00974] dThe Dcm shall set the fill bytes to 0x00.c

Note: If other fill-bytes than 0x00 are needed by legislation, the application has to
provide the value of the fill-byte.
The following sections define how specific PIDs are handled by the Dcm.

7.4.3.4.1 Service $02 - PID$02

An external tester can request the DTC that caused a FreezeFrame to be stored by
using the Service $02 with the PID value $02.

[SWS_Dcm_00279]
Upstream requirements: RS_Diag_04058

dOn reception of a request for Service $02 with PID $02, the Dcm shall call
Dem_DcmGetDTCOfOBDFreezeFrame() with FrameNumber set to 0x00 to get the
DTC number.c

The Dem module returns the corresponding DTC. Note that this 2-byte DTC is packed
into the 4-byte data returned by the call to Dem_DcmGetDTCOfOBDFreezeFrame ().
see Dem specification on how this is done.

229 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01061] dIf Dem_DcmGetDTCOfOBDFreezeFrame returns E_NOT_OK,

the Dcm shall answer positively with $0000 (indicates no stored freeze frame data).c

7.4.3.4.2 Service $02 - availability PID

Using Service $02, an external tester may request the supported PIDs for a specific
freeze-frame by using the "availability PIDs".

[SWS_Dcm_00284] dOn reception of a service $02 request with an "availability PID",

the Dcm shall respond with the corresponding supported (=configured) PIDs encoded
according to the OBD standard.c

7.4.3.4.3 Service $02 - other PIDs

Using Service $02, an external tester may request the values of specific PIDs in specific
FreezeFrames.

[SWS_Dcm_00286] dOn reception of a service $02 request with a

PID that is not an "availability PID" and is not $02, the Dcm shall call
Dem_DcmReadDataOfOBDFreezeFrame() for every data of the PID with the
following parameter values:
• PID = the PID received in the OBD request
• DestBuffer = a buffer in which the callee can write the value of the PID
• BufSize = the size of the DestBuffer, this must be at least equal to the size needed
to store the value of the PID as configured in the DCM
• DataElementIndexOfPid = implicit index (from 0 to n) of the DataElement calcu-
lated by Dcm according to the order of the DataElement positions in the PID (see
parameter DcmDspPidByteOffset)
c

Note that is not necessary for the Dcm module to lock or unlock the record updates of
the Dem module.

[SWS_Dcm_00287] dUpon the completion of [SWS_Dcm_00286], the Dcm shall gen-

erate a response message including the respective PID, FreezeFrame Number and
the associated data record for the requested FreezeFrame number.c

230 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01252] dIf Dem_DcmReadDataOfOBDFreezeFrame() returns

E_NOT_OK and a single PID is requested, the Dcm shall not provide any answer.c

[SWS_Dcm_01253] dIf Dem_DcmReadDataOfOBDFreezeFrame() returns

E_NOT_OK and all PIDs from the requested multiple PID(s) are not supported,
the Dcm shall not provide any answer.c

[SWS_Dcm_01254] dIf Dem_DcmReadDataOfOBDFreezeFrame() returns

E_NOT_OK and at least one PID from the requested multiple PID(s) is sup-
ported, the Dcm shall send a positive response including the data of the supported
PID(s).c

7.4.3.5 Service $03 $07 $0A - Obtaining DTCs

[SWS_Dcm_00245] dThe Dcm module shall implement OBD Service $03 (Request
emission-related diagnostic trouble codes) in compliance to all provisions of the OBD
standard.c

[SWS_Dcm_00410] dThe Dcm module shall implement OBD Service $07 (Request
Emission-Related Diagnostic Trouble Codes Detected during Current or Last Com-
pleted Driving Cycle) in compliance to all provisions of the OBD standard.c

[SWS_Dcm_00411] dThe Dcm module shall implement OBD Service $0A (Request
Emission-Related Diagnostic Trouble Codes with Permanent Status) in compliance to
all provisions of the OBD standard.c

An external test tool can request an emission-related ECU to report all stored, pending
or permanent emission-related DTCs by sending the request $03, $07, $0A respec-
tively.

[SWS_Dcm_00289] dWhen receiving a request for OBD Service $03, the Dcm module
shall obtain from the DEM all DTCs in primary memory and with a "confirmed" status
using the functions Dem_SetDTCFilter() and Dem_GetNextFilteredDTC().c

Note: The Dcm module can get an indication of the number of records that will be
found using Dem_GetNextFilteredDTC() by using Dem_GetNumberOfFilteredDTC().
This allows the implementation to calculate the total size of the response before cycling
through the DTCs.

231 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00412] dWhen receiving a request for OBD Service $07, the Dcm module
shall obtain from the DEM module all DTCs in primary memory with a "pending" status
using the functions Dem_SetDTCFilter() and Dem_GetNextFilteredDTC().c

Note: The Dcm module can get an indication of the number of records that will be
found using Dem_GetNextFilteredDTC() by using Dem_GetNumberOfFilteredDTC().
This allows the implementation to calculate the total size of the response before cycling
through the DTCs.

[SWS_Dcm_00330] dWhen receiving a request for OBD Service $0A, the Dcm module
shall obtain from the DEM all DTCs stored in permanent memory using the functions
Dem_SetDTCFilter() and Dem_GetNextFilteredDTC().c

Note: The Dcm module can get an indication of the number of records that will be
found using Dem_GetNextFilteredDTC() by using Dem_GetNumberOfFilteredDTC().
This allows the implementation to calculate the total size of the response before cycling
through the DTCs.
The following table illustrates the parameters the Dcm module must use when calling
Dem_SetDTCFilter() in response to a request for OBD Service $03, $07 or $0A.
Parameters to Dem_SetDTCFilter
OBD Service $03 $07 $0A
ClientId Client Id for this Dcm Client Id for this Dcm Client Id for this Dcm
instance (see instance (see instance (see
DcmDemClientRef) DcmDemClientRef) DcmDemClientRef)
DTCStatusMask 0x08 (confirmed bit 0x04(pending bit set) 0x00
set)
DTCFormat DEM_DTC_ DEM_DTC_ DEM_DTC_
FORMAT_OBD FORMAT_OBD FORMAT_OBD
DTCOrigin DEM_DTC_ORIGIN_ DEM_DTC_ORIGIN_ DEM_DTC_ORIGIN_
OBD_RELEVANT_ OBD_RELEVANT_ PERMANENT
MEMORY MEMORY
FilterWithSeverity FALSE FALSE FALSE
DTCSeverityMask Not relevant Not relevant Not relevant
FilterForFaultDetec- FALSE FALSE FALSE
tionCounter

Table 7.5: Dem_SetDTCFilter Parameters

When using paged buffer mechanism, in some case, it’s possible that the number of
DTC matching the filter change between the calculation of the total size, needed for
the first page transmission, and the sending of the further pages. For this reason, the
requirement [SWS_Dcm_00587] and [SWS_Dcm_00588] shall be considered for the
implementation of this service.

232 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01227] dDem_GetNextFilteredDTC returns DEM_NO_SUCH_ELEMENT

and at least one matching element could be retrieved before, the Dcm shall send a
positive response including these data elements and the number of DTCs.c

[SWS_Dcm_01228] dIf Dem_GetNextFilteredDTC returns

DEM_NO_SUCH_ELEMENT and no matching element could be retrieved before, the
Dcm shall send a positive response with the number of DTCs set to 0x00.c

7.4.3.6 Service $04 - Clear/reset emission-related diagnostic information

[SWS_Dcm_00246] dThe Dcm module shall implement OBD Service $04 (Clear/re-
set emission-related diagnostic information) in compliance to all provisions of the OBD
standard.c

An external test tool can request an emission-related ECU to clear the error memory
by sending the request $04.

[SWS_Dcm_00004]
Upstream requirements: RS_Diag_04058

dWhen receiving a request for OBD Service $04, the Dcm module shall call the interface
Dem_SelectDTC with the following parameter values:
• ClientId: Client Id for this Dcm instance (see DcmDemClientRef)
• DTC = DEM_DTC_GROUP_ALL_DTCS
• DTCFormat = DEM_DTC_FORMAT_OBD
• DTCOrigin = DEM_DTC_ORIGIN_OBD_RELEVANT_MEMORY
c

[SWS_Dcm_00413] dIn case Dem_ClearDTC() returns E_OK, the Dcm module shall
send a positive response.c

[SWS_Dcm_00703]
Upstream requirements: RS_Diag_04249

dIn case Dem_ClearDTC() returns DEM_PENDING, the Dcm shall invoke

Dem_ClearDTC() on next Dcm_MainFunction call again. It is up to the Dcm to send
NRC 78 (ResponsePending) to respect the response behaviourc

233 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00704] dIn case Dem_ClearDTC() returns DEM_CLEAR_FAILED, the

Dcm shall send a negative response 0x22 (conditionsNotCorrect).c

[SWS_Dcm_00967] dIn case Dem_ClearDTC() returns DEM_CLEAR_BUSY, the Dcm

shall send a negative response 0x22 (ConditionsNotCorrect).c

[SWS_Dcm_01067] dIn case Dem_ClearDTC() returns

DEM_CLEAR_MEMORY_ERROR, the Dcm module shall send a negative response
0x22 (ConditionNotCorrect).c

7.4.3.7 Service $06 - Request On-Board Monitoring Test-results for Specific

Monitored Systems

7.4.3.7.1 General requirements

[SWS_Dcm_00414] dThe Dcm module shall implement OBD Service $06 (Request On-
Board Monitoring Test-results for Specific Monitored Systems) in compliance to all pro-
visions of the OBD standard.c

Using Service $06, an external test tool can request an emission-related ECU to return
the DTR’s associated with the OBDMID or to return the supported OBDMIDs. OBD
reserves certain OBDMIDs for the special purpose of obtaining the list of supported
OBDMIDs in a certain range. These OBDMIDs are called "availability OBDMIDs" and
are $00, $20, $40, $60, $80, $A0, $C0 an $E0.
A tester request for supported OBDMIDs may contain up to six (6) "availability OBD-
MIDs".

[SWS_Dcm_00956] dOn reception of an OBD Service $06 request with multiple non-
availability OBDMIDs, the Dcm module shall ignore the request.c

7.4.3.7.2 Test results obtained via Dem interaction

The maintenance of the DTRs lies within the responsibility of the DEM. SW-Cs report-
ing DTRs use dedicated interfaces offered by the DEM. Upon requests from the tester
the Dcm retrieves the information from the DEM using dedicated DEM interfaces. There
is no direct interaction between the Dcm and SW-Cs.

234 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00957] dOn reception of an OBD Service $06 request with only "avail-
ability OBDMID(s)" as parameter(s), the Dcm module shall obtain the supported OB-
DMIDs by calling the Dem interface Dem_DcmGetAvailableOBDMIDs()for each "avail-
ability OBDMID ($00, $20, ...)" contained within the request and concatenate the re-
sults within the response message according to ISO-15031-5 [2].c

[SWS_Dcm_00958] dOn reception of an OBD Service $06 request with an OBDMID

that is not an "availability OBDMID", the Dcm module shall call the DEM interface
Dem_DcmGetNumTIDsOfOBDMID() to obtain the TIDs available for the requested OB-
DMID and then recurrently call the interface Dem_DcmGetDTRData() for the number
of reported TIDs to obtain the associated DTR data.c

7.4.3.8 Service $08 - Request Control of On-Board System, Test or Component

[SWS_Dcm_00417] dThe Dcm module shall implement OBD Service $08 (Request
Control of On-Board System, Test or Component) in compliance to all provisions of
the OBD standard.c

Using Service $08, an external test tool can control an on-board system, test or com-
ponent using a TID. OBD reserves certain TIDs for the special purpose of obtaining the
list of supported TIDs in a certain range. These TIDs are called "availability TIDs" and
are $00, $20, $40, $60, $80, $A0, $C0 an $E0.
The Dcm module’s configuration defines the TIDs that are available on the ECU for
the purpose of OBD Service $08. The configuration defines for each such TID (see
configuration parameter DcmDspRequestControlTestId):
• the name of the port the Dcm uses to access the RequestControlServices inter-
face (see configuration parameter DcmDspRequestControl)
• the number of bytes this function takes as input (see configuration parameter
DcmDspRequestControlInBufferSize)
• the number of bytes this function writes as output (see configuration parameter
DcmDspRequestControlOutBufferSize)
To provide OBD Service $08, the Dcm relies on external functions configured per TID.

[SWS_Dcm_00418] dOn reception of an OBD Service $08 request with one or more
"availability TIDs" as parameter, the Dcm module shall respond with the corresponding
supported (=configured) TIDs.c

[SWS_Dcm_00947] dOn reception of an OBD Service $08 request "availability TIDs"

together with other TIDs as parameter, the Dcm module shall ignore the request.c

235 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00419] dOn reception of an OBD Service $08 request with a TID that is not
an "availability TID", the Dcm module shall invoke the configured Xxx_RequestControl()
function with the following parameters values: InBuffer: data contained in the OBD
request (the size of which must correspond to the size configured in the Dcm module’s
configuration) OutBuffer: space in which the RequestControl function can store its
result (the size of the buffer is taken from the Dcm module’s configuration)c

[SWS_Dcm_00420] dAfter the execution of [SWS_Dcm_00419], the Dcm module shall

respond to the service request using the data stored by the RequestControl function in
the OutBuffer.c

[SWS_Dcm_00948] dAs specified in [4, SAE J1979], unused data bytes shall be filled
with $00.c

[SWS_Dcm_01192] dIf Xxx_RequestControl() doesn’t return E_OK, the Dcm shall re-
turn NRC 0x22.c

7.4.3.9 Service $09 - Request Vehicle Information

[SWS_Dcm_00421] dThe Dcm module shall implement OBD Service $09 (Request Ve-
hicle Information) in compliance to all provisions of the OBD standard.c

Using Service $09, an external test tool can request vehicle information or can obtain
lists of supported vehicle information. OBD reserves certain InfoTypes for the special
purpose of obtaining the list of supported InfoTypes in a certain range. These Infotypes
are called "availability InfoTypes" and are $00, $20, $40, $60, $80, $A0, $C0 an $E0.
The Dcm module’s configuration defines the InfoTypes and associated data that are
available on one or several SW-C. The configuration defines for each such InfoType:
• The value of InfoType (see configuration parameter DcmDspVehInfoInfoType)
• For every data of the InfoType:
– The position of this data in the InfoType (see configuration parameter DcmD-
spVehInfoDataOrder)
– the size of the value of the InfoType data (see configuration parameter
DcmDspVehInfoDataSize)
– the function that the Dcm module must call to obtain the value for this Info-
Type data OR the port-name through which the Dcm module can obtain the
value for this InfoType data (see configuration parameter DcmDspVehInfo-
DataReadFnc and DcmDspVehInfoDataUsePort).

236 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

To provide OBD Service $09, the Dcm relies on external functions that allow it to obtain
the value of an InfoType data. There is one such function per InfoType data that is
needed by the DCM.
When invoking a Xxx_GetInfotypeValueData() function, the Dcm module provides a
buffer of the correct size in which the value of the InfoType data can be stored. The
entity providing the actual implementation of the Xxx_GetInfotypeValueData() function
for a specific InfoType data might be a SW-C or another basic software module. The
origin of the function is part of the Dcm module’s configuration.
Certain InfoTypes needed by the Dcm to provide Service $09 are provided by the DEM.
This is handled in the Dcm configuration.

[SWS_Dcm_00422] dOn reception of an OBD Service $09 request with one or more
"availability InfoTypes" as parameter, the Dcm module shall respond with the corre-
sponding supported (=configured) InfoTypes.c

[SWS_Dcm_00423] dOn reception of an OBD Service $09 request for an InfoType that
is not an "availability InfoType", the Dcm module shall obtain the value of this InfoType
by invoking all the configured Xxx_GetInfotypeValueData() function for every data of
this InfoType and shall return the value as response to Service $09c

[SWS_Dcm_00684] dIn case DcmDspVehInfoNODIProvResp is set to FALSE, in

addition to collect the available InfoType value contributions from the individual SW-C,
the Dcm shall compute the data byte NofDataItems in the diagnostic response, which
defines the number of DataItems included in one InfoType.c

Note: The Calculation of the Calibration Identification (CAL-ID) and Calibration Verifi-
cation Number (CVN) is not a BSW Task and will not handled within the DCM.

[SWS_Dcm_01167] dIn case DcmDspVehInfoNODIProvResp is set to TRUE, the

Dcm shall take over the value returned by the provider and report it as NofDataItems in
the diagnostic response.c

[SWS_Dcm_CONSTR_06045] dIn case the responsibility is on provider side (DcmD-

spVehInfoNODIProvResp is set to TRUE), only one DcmDspVehInfoData con-
tainer shall be allowed.c

[SWS_Dcm_CONSTR_06046] dIn case DcmDspVehInfoDataUsePort

is set to FALSE and DcmDspVehInfoDataReadFnc is set to either
Dem_DcmGetInfoTypeValue08 or Dem_DcmGetInfoTypeValue0B then DcmD-
spVehInfoNODIProvResp shall be set to TRUE.c

237 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Note : The integrator has to make sure that the buffer determined by the DcmDspVe-
hInfoDataSize is sufficiently sized to receive the data returned by the provider of
the data.

[SWS_Dcm_01191] dIf Xxx_GetInfoTypeValueData() doesn’t return E_OK or

E_PENDING, the Dcm shall return NRC 0x22.c

7.4.4 Interaction usecases

The Dcm shall be able to manage a jump to the bootloader / jump due to ECUReset
request. Due to the diversity of possibility to realize this jump, this will be done using
callout call.

7.4.4.1 Jump to Bootloader

4 different use cases have been identified for the jump to the bootloader, if all precon-
ditions are fulfilled and assuming the ’suppressPosRspMsgIndicationBit ’ flag is set to
’false’:
1. The application immediately sends a final positive response and then jumps to
the bootloader
2. The application first sends a NRC 0x78 response, then the final positive response
and afterwards jumps to the bootloader
3. The application immediately jumps to the bootloader and the bootloader sends
the final positive response
4. The application first sends a NRC 0x78 response, then jumps to the bootloader
and the bootloader sends the final positive response
Note: In case the ’suppressPosRspMsgIndicationBit’ flag is set to ’true’, use case ’1’
and use case ’3’ will not issue a positive response.

[SWS_Dcm_00532]
Upstream requirements: RS_Diag_04098

dOn reception of service DiagnosticSessionControl if the provided session is

used to jump to OEM bootloader (parameter DcmDspSessionForBoot set to
DCM_OEM_BOOT or DCM_OEM_BOOT_RESPAPP) the Dcm shall prepare the jump
to the OEM bootloader (see [SWS_Dcm_00535]) by triggering the mode switch of Mod-
eDeclarationGroupPrototype DcmEcuReset to JUMPTOBOOTLOADER.c

Note: By this mode switch the Dcm informs the BswM to prepare the jump to the boot-
loader.

238 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00592]
Upstream requirements: RS_Diag_04098

dOn reception of service DiagnosticSessionControl if the provided session is used

to jump to System Supplier bootloader (parameter DcmDspSessionForBoot set to
DCM_SYS_BOOT or DCM_SYS_BOOT_RESPAPP) the Dcm shall prepare the jump
to the System Supplier bootloader (see [SWS_Dcm_00535]) by triggering the mode
switch of ModeDeclarationGroupPrototype DcmEcuReset to JUMPTOSYSSUPPLIER-
BOOTLOADERc

Note: By this mode switch the Dcm informs the BswM to prepare the jump to the boot-
loader.

[SWS_Dcm_01164] dIn case the service DiagnosticSessionControl implies an ECU

reset, the Dcm shall ignore all further requests while that reset is being processed.c

[SWS_Dcm_00654]
Upstream requirements: RS_Diag_04098, RS_Diag_04249

dIn case the ModeDeclarationGroupPrototype DcmEcuReset is switched to mode

JUMPTOBOOTLOADER or JUMPTOSYSSUPPLIERBOOTLOADER and the configu-
ration parameter DcmSendRespPendOnRestart is set to TRUE, the Dcm shall trigger
transmission of NRC 0x78 - RCR-RP.c

Note: This final transmission of NRC 0x78 before switching to Bootloader shall reload
the P2* timeout in the client.

[SWS_Dcm_01175] dIn case the ModeDeclarationGroupPrototype DcmEcuReset can

not be switched JUMPTOBOOTLOADER or JUMPTOSYSSUPPLIERBOOTLOADER,
the Dcm shall answer negatively to the request with NRC 0x22 (Conditions not correct).c

[SWS_Dcm_00535]
Upstream requirements: RS_Diag_04098

dIf the jump to bootloader is requested (see [SWS_Dcm_00532], [SWS_Dcm_00592],

the configuration parameter DcmSendRespPendOnRestart is set to TRUE (see
[SWS_Dcm_00654]) and the configuration parameter DcmDspSessionForBoot is
set to DCM_OEM_BOOT or DCM_SYS_BOOT, the Dcm shall call Dcm_SetProgCon-
ditions after a successful transmission of NRC 0x78 (Response pending).c

This will allow to store all relevant information prior to jumping to the bootloader.
Note: It is up to the software integrator to decide where to store that data. Usually it
will be stored in non-volatile memory like e.g. data flash. It is also acceptable to "store"
this data in a RAM section which is not initialized out of reset.

239 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01163]
Upstream requirements: RS_Diag_04098

dIn the context of a request to jump to the bootloader (see [SWS_Dcm_00532]

and [SWS_Dcm_00592]), after Dcm_SetProgConditions returns E_OK according
to [SWS_Dcm_00535], the Dcm shall trigger the mode switch of the ModeDeclara-
tionGroupPrototype DcmEcuReset to EXECUTE.c

[SWS_Dcm_01177]
Upstream requirements: RS_Diag_04098

dIf the jump to bootloader is requested (see [SWS_Dcm_00532], [SWS_Dcm_00592],

the configuration parameter DcmSendRespPendOnRestart is set to TRUE (see
[SWS_Dcm_00654]), and the configuration parameter DcmDspSessionForBoot is
set to DCM_OEM_BOOT_RESPAPP or DCM_SYS_BOOT_RESPAPP, the Dcm shall
initiate the final response after a successful transmission of NRC 0x78 (Response pend-
ing).c

[SWS_Dcm_00995] dIf the NRC 0x78 (Response Pending) response in

[SWS_Dcm_00535] is not sent successfully the Dcm shall cancel the current
request.c

[SWS_Dcm_00997] dIf the NRC 0x78 (Response Pending) response in

[SWS_Dcm_00535] is not sent successfully no jump to the bootloader shall be
performedc

Note: If the NRC 0x78 (Response Pending) response has not been sent correctly the
Dcm will stay in the application and wait for the next request from the Client.

[SWS_Dcm_01178] dIn case the ModeDeclarationGroupPrototype DcmEcuReset

is switched to mode JUMPTOBOOTLOADER or JUMPTOSYSSUPPLIERBOOT-
LOADER, the configuration parameter DcmSendRespPendOnRestart is set to
FALSE and the configuration parameter DcmDspSessionForBoot is set to
DCM_OEM_BOOT_RESPAPP or DCM_SYS_BOOT_RESPAPP , the Dcm shall initi-
ate the final responsec

[SWS_Dcm_01179] dIn case the final response has been successfully sent according
to [SWS_Dcm_01177] or [SWS_Dcm_01178], the Dcm shall call Dcm_SetProgCon-
ditionsc

[SWS_Dcm_01180] dIf Dcm_SetProgConditions returns E_OK according to

[SWS_Dcm_01179], the Dcm shall trigger the mode switch of the ModeDeclara-
tionGroupPrototype DcmEcuReset to EXECUTE.c

240 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01181] dIf Dcm_SetProgConditions returns E_NOT_OK according to

[SWS_Dcm_01179], the Dcm shall not request any reset, shall not perform the jump to
bootloader, and shall not switch the ModeDeclarationGroupPrototype DcmEcuReset to
EXECUTE.c

[SWS_Dcm_00720] dIn case the ModeDeclarationGroupPrototype DcmEcuRe-

set is switched to mode JUMPTOBOOTLOADER or JUMPTOSYSSUPPLIER-
BOOTLOADER, the configuration parameter DcmSendRespPendOnRestart is set
to FALSE and the configuration parameter DcmDspSessionForBoot it set to
DCM_OEM_BOOT or DCM_SYS_BOOT, the Dcm shall call Dcm_SetProgCondi-
tions immediately. (see [SWS_Dcm_00532] and [SWS_Dcm_00592])c

[SWS_Dcm_00719] dIf Dcm_SetProgConditions returns E_OK according to

[SWS_Dcm_00720], the Dcm shall shall trigger the mode switch of the ModeDecla-
rationGroupPrototype DcmEcuReset to EXECUTE without sending a NRC 0x78 (Re-
sponse pending).c

In case of [SWS_Dcm_00719], the exact response handling depends on the state of

the ’suppressPosRspMsgIndicationBit’ (TRUE or FALSE) in the request message.

[SWS_Dcm_00715] dIf the jump to bootloader is requested (see [SWS_Dcm_00532]

and [SWS_Dcm_00592]) and if the call to Dcm_SetProgConditions returns
E_NOT_OK (see [SWS_Dcm_00535] and [SWS_Dcm_00720]), no further action shall
be taken by the Dcm and negative response NRC 0x22 (Conditions not correct) shall be
returned.c

7.4.4.2 Jump due to ECUReset

On reception of an ECUReset Service 0x11 request, if the configuration parameter

DcmResponseToEcuReset is set to AFTER_RESET, the Dcm will set the Respon-
seRequired flag by calling Dcm_SetProgConditions.

[SWS_Dcm_01423] Answer to ECUReset request

Upstream requirements: RS_Diag_04098

dOn reception of an ECUReset Service 0x11 request, if DcmResponseToEcuReset

is set to AFTER_RESET, the Dcm shall answer to EcuReset service after the reset.c

[SWS_Dcm_01424] Answer to ECUReset request

Upstream requirements: RS_Diag_04098

dOn reception of an ECUReset Service 0x11 request, if DcmResponseToEcuReset

is set to BEFORE_RESET, the Dcm shall answer to EcuReset service before the reset.c

241 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01425] Answer to ECUReset request

Upstream requirements: RS_Diag_04098, RS_Diag_04249

dIf the Dcm intiates a reset and DcmSendRespPendOnRestart is set to TRUE, the
Dcm shall trigger transmission of NRC 0x78 (Response pending) before the reset.c

7.4.4.3 Jump from Bootloader / ECUReset

[SWS_Dcm_00536]
Upstream requirements: RS_Diag_04098

dAt Dcm initialization, the Dcm shall call Dcm_GetProgConditions to know if the
initialization is the consequence of a jump from the bootloader / ECUReset.c

Note: It is the responsibility of the software integrator to ensure that the data contained
in Dcm_ProgConditionsType is valid when Dcm_Init is called. E.g. if this data is
stored in non-volatile memory, it may take some time to make it available after an ECU
reset. This has to be taken into account when designing the ECU’s startup process.

[SWS_Dcm_00537] dIf the initialization of the Dcm is the consequence of a jump

from the bootloader / ECUReset (see [SWS_Dcm_00536], the Dcm shall call
ComM_DCM_ActiveDiagnostic(NetworkId) to request the ComManager for the full
communication mode.c

[SWS_Dcm_00767]
Upstream requirements: RS_Diag_04098

dWhen the ComM reports full communication to the Dcm, the Dcm shall send the Re-
sponse to the Service Id passed in the Dcm_ProgConditionsType.c

[SWS_Dcm_00768] dIf the initialization of the Dcm is the consequence of a jump

from the bootloader (see [SWS_Dcm_00536] and the application is updated by an
FLASH download (Dcm_ProgConditionsType.ApplUpdated == True), the Dcm shall call
BswM_Dcm_ApplicationUpdated() to notify the BswM that the application was up-
dated.c

242 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.4.4.4 Flags management

7.4.4.4.1 Jump to Bootloader

[SWS_Dcm_01182] dOn reception of a UDS Service 0x10 request (Diagnostic Session

Control) with subfunction 0x02 (Start Programming Session), the Dcm shall set the Re-
programmingRequest flag and, if indicated for this service, the ResponseRequired
flag by calling Dcm_SetProgConditions.c

[SWS_Dcm_01183] dDepending on configuration parameter DcmDspSessionFor-

Boot, either the application shall send the positive response (if suppressPosRspMs-
gIndicationBit = FALSE) or after an ECU reset, when the bootloader is started, it shall
send a response and clear the ResponseRequired flag. In either case, the bootloader
shall clear the ReprogrammingRequest flag.c

[SWS_Dcm_01185] dIn case that, during jump to Bootloader, the Dcm_SetProg-

Conditions API returns E_NOT_OK, a DET error shall be reported DCM_E_SET_-
PROG_CONDITIONS_FAIL and normal functionality shall resume.c

7.4.4.4.2 Jump from Bootloader

After successful reprograming of the application software, the bootloader will update
the ApplUpdated flag and the ResponseRequired flags.
After an ECU reset, when the newly programmed application is started for the first time,
the Dcm will read the ApplUpdated and ResponseRequired flag by calling Dcm_Get-
ProgConditions. During this function call the ApplUpdated and ResponseRequired
flags are cleared by the integration code.

7.5 Error notification

The Default Error Tracer module is just help for BSW development and integration. It
must not be contained inside the production code. The API is defined, but the function-
ality can be chosen and implemented according to the development needs (e.g. errors
count, send error information via a serial interface to an external logger, and so on).

243 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.6 Synchronous and Asynchronous implementation

The Dcm can access data using an R-Port requiring either a synchronous or an asyn-
chronous ClientServertInterface DataServices_{Data}. In the Dcm SWS, the param-
eter DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR.
In case of USE_DATA_SYNCH_CLIENT_SERVER, the interface shall be compatible
with the Dem interface "DataServices_<Data>" (no OpStatus parameter). The pa-
rameter OpStatus and return parameter DCM_E_PENDING shall only be available
in case of USE_DATA_ASYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_-
SERVER_ERROR.
Note: a Dcm implementation using AsynchronousServerCallPoint or Syn-
chronousServerCallPoint when calling service processors is completely an im-
plementation decision. This only indicates that the operation uses the status of
the operation to allow an asynchronous processing by the SW-C (initiating a re-
quest, checking if a request is still pending, or canceling a pending request, see
[SWS_Dcm_00686]).
There is no correlation to the operation signature (i.e. existence of OpStatus parameter
and DCM_E_PENDING return code) that demands AsynchronousServerCallPoint or
SynchronousServerCallPoint usage.

[SWS_Dcm_01187] dIf an asynchronous interface is used, the Dcm shall consider the
Output data (OUT) only valid after the last call to the interface that returns E_OK.c

[SWS_Dcm_01188] dIf an asynchronous interface is used, the Dcm shall consider the
OUT-parameter ErrorCode only valid after the last call to the interface that returns
E_NOT_OKc

Note : The "last call" to the interface is the call that returns with a value that indicates
that processing has finished, i.e. E_OK or E_NOT_OK.
Note : INOUT parameter are a combination of the requirements above, i.e. on each
call of the interface the parameters shall have a valid in-value, and the Dcm considers
the out-value valid only after the last call of the interface.

[SWS_Dcm_01189] dIf an asynchronous interface is used, the Dcm shall provide the
values originating from the request for the Input data (IN) on every call to the interface.c

Note: Requirements [SWS_Dcm_01187], [SWS_Dcm_01188] and

[SWS_Dcm_01189] do not apply for functions where a deviant behaviour is ex-
plicitly specified.

244 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.7 DID configuration

The configuration of the Dcm contains a list of supported DIDs which can be configured
in two ways:
• The individual DID configuration,which required one connection (either via a port
or a c-function) per configured data element of the respective DID to access to
the data (reading, writing and controlling). The interface DataServices should be
used for each DID in this case.
• The DID range configuration, used to handle a set of DIDs sharing the same
behavior uniformly in one SW-C with only one port-connection. The interface
DataServices_DIDRange_{Range} should be used in this case. Using this con-
figuration allows an interface optimization.The following parameters shall be con-
figured in order to use the DIDRange optimization: DcmDspDidRangeIdenti-
fierLowerLimit and DcmDspDidRangeIdentifierUpperLimit which de-
limited the range of the DIDs. DcmDspDidRangeMaxDataLength and DcmD-
spDidRangeHasGaps.

[SWS_Dcm_01174] dIf DcmVinRef is configured then the VIN shall be fetched once
by the Dcm during startup by calling Dcm_GetVin.c

7.7.1 Individual DID

The individual DID can be configured in DcmDspDid. A unique DID identifier is config-
ured on 2 bytes in DcmDspDidIdentifier. In case the DID refers to other DIDs, the
link between them can be configured in DcmDspDidRef2 . Each DID allows to access
to signal data values (by reading and/or writing). The signal reference (to DcmDsp-
Data) and the position of the data in the diagnostic answer (for reading) or request (for
writing) can be configured in DcmDspDidSignal.
The configuration of the data belonging to the DID can be provided in the container
DcmDspData (ECUC_Dcm_00869). This container collects the following information:
• The Data endianness of the data belonging to the DID (ECUC_Dcm_00986:
DcmDspDataEndianness)
• The length and the type of the data (ECUC_Dcm_00605: DcmDspDataByte-
Size, ECUC_Dcm_00985 : DcmDspDataType)
• The interface to be used to access to the data (ECUC_Dcm_00713: DcmDsp-
DataUsePort)
• The interfaces to the application in order to :

2
Overview of DcmDspDid container is described in chapter 10.2.5.8.1

245 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

– Check if the DID can be accessed in the current conditions. This

can be achieved by checking for each DataElement if the conditions
to read the data are satisfied (ECUC_Dcm_00677: DcmDspDataCon-
ditionCheckReadFnc and ECUC_Dcm_00955: DcmDspDataCondi-
tionCheckReadFncUsed)
– Request to freeze the current state of an IOControl (ECUC_Dcm_00674:
DcmDspDataFreezeCurrentStateFnc)
– Get the scaling information of the DID. This can be achieved by getting the
scaling information for each DataElement (ECUC_Dcm_00676: DcmDsp-
DataGetScalingInfoFnc)
– Request the data length of a DataElement (ECUC_Dcm_00671: DcmDsp-
DataReadDataLengthFnc)
– Read a certain ECU signal (ECUC_Dcm_00824: DcmDspDataReadE-
cuSignal).
– Access in reading or writing to the data (ECUC_Dcm_00669 : DcmDsp-
DataReadFnc, ECUC_Dcm_00670: DcmDspDataWriteFnc)
– Request to reset an IOControl to default value (ECUC_Dcm_00673 : DcmD-
spDataResetToDefaultFnc)
– Request to return control to ECU of an IOControl (ECUC_Dcm_00672 :
DcmDspDataReturnControlToEcuFnc)
– Request to adjust the IO signal (ECUC_Dcm_00675 : DcmDspDataShort-
TermAdjustmentFnc)
It is also possible to configure an alternative diagnosis representation via
ECUC_Dcm_00993: DcmDspDiagnosisScaling.
The following example shows how to configure the containers DcmDspDid and DcmD-
spData for an individual DID 0xF080. This configuration allows access to a byte
of data via synchronous C APIs WriteDID_F080 (for writing) and ReadDID_F080 (for
reading).
• DcmDspDidIdentifier=0xF080
• DcmDspDidByteOffset=0
• DcmDspDidDataRef=DcmDspData_F080
• DcmDspDataByteSize=8
• DcmDspDataType=UINT8_N
• DcmDspDataUsePort=USE_DATA_SYNCH_FNC
• DcmDspDataWriteFnc=WriteDID_F080
• DcmDspDataReadFnc=ReadDID_F080

246 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

7.7.2 DID ranges

DID ranges are in general the same as the ’normal’ DID read and write function, except
that the DID is also passed as a parameter. This allows to treat the DID range in a
switch/case in the read or the write function.
The ranges can be applied for reading (ReadDataByIdentifier 0x22) and writing (Write-
DataByIdentifier 0x2E) DIDs.
The ranges can be configured in ECUC_Dcm_00937 : DcmDspDidRange. Each con-
figured range is by default accessible by service 0x22 and 0x2E. In case the range
should be limited to reading or writing, the referenced DcmDspDidInfo container
should be defined accordingly.
It is also possible to define gaps within the range (DcmDspDidRangeHasGaps). By
activating this feature, the Dcm invokes each time a DID is requested within the config-
ured range, the operation IsDidAvailable has to check the current availability. And as
the DIDs of the specified range can have different length, the length of the longest DID
has to be configured (DcmDspDidRangeMaxDataLength) in order to reserve enough
buffer passed to the respective function.
In general, the range functionality can also be used for a single DID if you specifically
want to pass the DID as a parameter. Then lower DID and upper DID should be the
same.
ReadDidRangeDataLength operation allows to request the application to return the
data length of a DID Range.

[SWS_Dcm_CONSTR_06020] Definition of allowed DID access dAny defined range

shall only reference via DcmDspDidRangeInfoRef. The sub-containers DcmDsp-
DidControl and DcmDspDidDefineinDcmDspDidInfo shall not be used] .c

[SWS_Dcm_CONSTR_06021] DID ranges cannot be mapped on DDDIDs, be-

cause service 0x2C DDDID does not support the range feature. Practi-
cally DcmDspDidRangeIdentifierLowerLimit and DcmDspDidRangeIdenti-
fierUpperLimit should not include DIDs of the range 0xF200 till 0xF3FF. dAny
defined range shall only reference DcmDspDidInfo via DcmDspDidRangeInfoRef,
having set DcmDspDidDynamicallyDefined == False.c

7.8 Secure Coding

Secure coding or secure variant coding offers the functionality to update, change, or re-
place parameters in the server in a secure way. Secure variant coding is an AUTOSAR
standardized functionality that allows manufacturers to control which data can be writ-
ten into the ECU. Only signed data is accepted and can be written into the server. In

247 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

typical environments, the data is signed by the manufacturer’s backend. The manufac-
turer can control which data can be written.
From a high level this sequence consists of:
• Bringing in a certificate that authenticates the content that shall be written
• Writing the parameter data
• Provide a signature of the data that matches the certificate public key
• Update the data in the server.

Figure 7.13: Secure Coding Sequence

The secure coding sequence is always started by transmitting a certificate using the
UDS service Authentication with the sub-function transmitCertificate.

[SWS_Dcm_01684] Starting the secure coding sequence

Upstream requirements: RS_Diag_04272

dUpon receiving a certificate via the UDS service transmitCertificate with a certifica-
teEvaluationId mapped to a DcmDspAuthenticationTransmitCertificate with
DcmDspAuthenticationTransmitCertificateFunction that is set to = SE-
CURE_CODING, the Dcm shall (re-)start the secure coding mechanism and use this
certificate to validate the secure coding data.c

Special attention needs to be given to the mechanism to buffer the coding data until
it is protected. The secure coding procedure can contain multiple consecutively sent

248 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

WriteDataByIdentifier requests. The written data can only be applied and forwarded to
the application of the signature calculated over all the data is valid. In the meantime, the
data is buffered. There are various approaches for resource-efficient buffer handling.
AUTOSAR does not have the goal of providing solutions for all possible strategies.
Rather two strategies are taken into consideration:
1. Buffer all coding data within the Dcm prior to persisting. This approach works fine
for smaller write data but scales less well for larger coding data.
2. This strategy is an outlook to use the BndM module. It might be part of future
AUTOSAR releases. The BndM allows direct a/b partition NV memory access
and does not require a further RAM buffer.
The Dcm derives the used strategy directly from the configured used port interfaces
DcmDspDataUsePort for the DID data elements. In the current version only strat-
egy 1) is supported which means that all configured port interfaces are valid with the
exception of [SWS_Dcm_CONSTR_06108].

[SWS_Dcm_CONSTR_06108] Not supported port interfaces for secure coding

dA DcmDspDid that is referenced by DcmSecureCodingDataIdentifier shall
not have a DcmDspData with DcmDspDataUsePort set to USE_ECU_SIGNAL or
USE_BLOCK_ID.c

The data that is stored during the secure coding process is a sequential chain of stored
data identifiers as shown in Figure 7.13. For each data identifier, the 2-byte data iden-
tifier number followed by the data record of the data identifier is stored. This is sequen-
tially repeated for each secure data identifier. The signature validation is run over the
entire buffer.

Figure 7.14: Dcm Secure Coding Buffer Layout

The data identifier number in the signature check ensures that the written data matches
the intended write operation of the manufacturer and avoids misuse to a data record
as data of a different DID. The signature validation over the entire buffer only allows
one explicit order of DIDs in which the data has to be written. Even if the order might
be irrelevant for coding data for some users, the order needs to be kept.

249 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01685] Write Secure Coding DID for started secure coding sequence
Upstream requirements: RS_Diag_04272

dIf the Dcm receives a write data by identifier request for a data identifier referenced
by DcmSecureCodingDataIdentifier and the secure coding sequence has been
started according to [SWS_Dcm_01684], the Dcm shall sequentially store the data in
the buffer defined by DcmSecureCodingDataBufferSize and store the 2 byte DID
number followed by the data in it.c

[SWS_Dcm_CONSTR_06109] Static length of secure coding DIDs dA DcmDspDid

that is referenced by DcmSecureCodingDataIdentifier shall have a static length.
This means that the DcmDspData of that DID shall not have any DcmDspDataType
set to UINT8_DYN.c

With [SWS_Dcm_01685] the Dcm stores the data in a temporary local buffer that is
not visible to the outside. Applications have therefore no access to the data at this
point. This also implies that the configured callouts in DcmDspDataUsePort are not
yet invoked.
Apart from this local data storage, the Dcm processes a secure coding DID diagnostic
request in the same way as any other diagnostic request. In particular, all service
validation checks are executed.

[SWS_Dcm_01686] Write Secure Coding DID without a started secure coding

sequence
Upstream requirements: RS_Diag_04272

dIf the Dcm receives a write data by identifier request for a data identifier referenced by
DcmSecureCodingDataIdentifier and the secure coding sequence has not been
started according to [SWS_Dcm_01684], the Dcm shall return an NRC 0x22 (condition-
sNotCorrect) as a response to the write data by identifier request.c

[SWS_Dcm_01687] Write Secure Coding DID buffer overflow

Upstream requirements: RS_Diag_04272

dIf the Dcm is storing secured coding DID data within the buffer provided by Dcm-
SecureCodingDataBufferSize and the data of the DID written to it exceeds the
configured size, the Dcm shall send an NRC 0x22 (conditionsNotCorrect) and stop the
secure coding sequence.c

The secure coding sequence is finalized by a dedicated routine control service. It is

responsible for verifying the authenticity of the written data and triggers the final data
write operations.

250 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01688] Secure Coding validation trigger on inactive secure coding

sequence
Upstream requirements: RS_Diag_04272

dIf the Dcm receives the routine control service referred by DcmSecureCodingVali-
dationRoutine and the secure coding sequence has not been started according to
[SWS_Dcm_01684], the Dcm shall return an NRC 0x22 (conditionsNotCorrect).c

[SWS_Dcm_01689] Secure Coding validation trigger without written data

Upstream requirements: RS_Diag_04272

dIf the Dcm receives the routine control service referred by DcmSecureCodingVali-
dationRoutine and no secure data according to [SWS_Dcm_01685] has been writ-
ten so far, the Dcm shall return an NRC 0x22 (conditionsNotCorrect).c

[SWS_Dcm_CONSTR_06110] Secure Coding validation routine input parameter

dA DcmDspRoutine that is referenced by DcmSecureCodingValidationRoutine
shall only have a single configured DcmDspStartRoutineInSignal with DcmD-
spRoutineSignalType set to UINT8_N.c

[SWS_Dcm_CONSTR_06111] Secure Coding validation routine output parameter

dA DcmDspRoutine that is referenced by DcmSecureCodingValidationRoutine
shall only have a single configured DcmDspStartRoutineOutSignal with DcmD-
spRoutineSignalType set to UINT8.c

A secure coding validation routine control service is processed entirely Dcm internal
without calling an SWC via C/S calls or a CDD via a C-Function.

[SWS_Dcm_CONSTR_06112] Secure Coding validation routine is synchronous

dA DcmDspRoutine that is referenced by DcmSecureCodingValidationRou-
tine shall not have a configured DcmDspStopRoutine and DcmDspRequestRou-
tineResults.c

[SWS_Dcm_01690] Dcm internal processing of secure coding validation routine

Upstream requirements: RS_Diag_04272

dIf the Dcm receives the routine control service referred by DcmSecureCodingVali-
dationRoutine, the Dcm shall process the routine control inside the Dcm and does
neither create nor call the external C-Function interface [SWS_Dcm_01203].c

[SWS_Dcm_01691] Authentication of secure coding data

Upstream requirements: RS_Diag_04272

dIf the Dcm receives the routine control service referred by DcmSecureCodingVal-
idationRoutine it shall verify if the signature matches the authentication provided

251 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

by the secure coding certificate by using the crypto job configured by DcmSecure-
CodingAuthenticationJobRef with a signature obtained by the one and only rou-
tine control request parameter and the secure coding data buffer as data to verify.c

[SWS_Dcm_CONSTR_06113] Require asynchronous signature verification d

DcmSecureCodingAuthenticationJobRef is only valid if the referenced CsmJob
itself:
• has a CsmProcessingMode set to CRYPTO_PROCESSING_ASYNC
• references a CsmPrimitive with an aggregated CsmSignatureVerify.
c

The crypto job from [SWS_Dcm_01691] securely authenticates the data that has been
written into the secure data buffer. This is done by verifying this data with the signature
that is provided by the client as a request parameter of the secure coding authentication
routine control service with the public key of the certificate. The certificate’s public key
is mandatory input data for the verification. In the AUTOSAR architecture, the crypto
job directly accesses the public key of the certificate. The integrator of the Csm and
KeyM modules links the public key to the crypto job.
A successful authentication of the secure data ensures from a security point of view,
that the client is authenticated to write exactly that data to the corresponding data iden-
tifiers. After this successful authentication, the Dcm will call the same configured write
APIs as it would do for write operations without the secure coding procedure. It can be
seen as a delay of the write operations to the point that all write data is authenticated.
For the application, it is a write operation and it does not need to distinguish between
a normal or secured coding write operation.

[SWS_Dcm_01692] Successful authenticated secure coding data

Upstream requirements: RS_Diag_04272

dIf the secure coding data has been successfully validated according to
[SWS_Dcm_01691], the Dcm shall call the configured write operations for all secured
coding data identifiers in the secure data buffer.c

The secure coding sequence can consist of more than one written data identifier. From
the Dcm side, there is no transaction system in place or any kind of rollback if a write
operation fails. In case of a failed write operation, the secure coding sequence is
canceled and a failure indication is sent as a parameter in the positive response of the
secure coding validation routine control service. It is the application’s responsibility to
design a sufficient stable mechanism to deal with this situation.

252 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01693] Successfully completed secure coding procedure

Upstream requirements: RS_Diag_04272

dIf all the called write operations from [SWS_Dcm_01691] have been completed
successfully, the Dcm shall set the positive response routine parameter DcmDsp-
StartRoutineOutSignal of the DcmSecureCodingValidationRoutine to the
value of 0x00 to indicate a successful completion of the secure coding procedure and
send a positive response for the DcmSecureCodingValidationRoutine.c

[SWS_Dcm_01694] Failed secure coding write

Upstream requirements: RS_Diag_04272

dIf a called write operation from [SWS_Dcm_01691] has failed, the Dcm shall cancel
all pending other secure coding write operations and set the positive response routine
parameter DcmDspStartRoutineOutSignal of the DcmSecureCodingValida-
tionRoutine to the value of 0x01 to indicate a failed secure coding write operation
and send a positive response for the DcmSecureCodingValidationRoutine.c

[SWS_Dcm_01695] Wrong signature for secure coding data

Upstream requirements: RS_Diag_04272

dIf the crypto job to authenticate the secure data has failed, the Dcm shall set the
positive response routine parameter DcmDspStartRoutineOutSignal of the Dcm-
SecureCodingValidationRoutine to the value of 0x02 to indicate a signature
validation failure and send a positive response for the DcmSecureCodingValida-
tionRoutine.c

[SWS_Dcm_01696] Behavior on too long signature validation dIf the execution time
of the routine control behind the DcmSecureCodingValidationRoutine exceeds
the maximum number of allowed response times due to [SWS_Dcm_00120], the Dcm
shall report the Runtime Error DCM_E_INTERFACE_TIMEOUT.c

7.9 Startup behavior

[SWS_Dcm_00334] dDcm_Init shall initialize all Dcm global variables with the values
of the configurationc

7.10 Error Classification

This section describes how the Dcm module has to treat the several error classes that
may happen during the life cycle of the Dcm module.

253 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Diagnostic-Communication-Errors are handled directly in the ISO-Protocols by NRCs.

[SWS_Dcm_00044]
Upstream requirements: SRS_BSW_00369

dThe error values shall be the unique for all error types. The Dcm shall use only the
values given in this chapter.c

Section ”Error Handling” of the document ”General Specification of Basic Software

Modules” describes the error handling of the Basic Software in detail. Above all, it
constitutes a classification scheme consisting of five error types which may occur in
BSW modules.
Based on this foundation, the following section specifies particular errors arranged in
the respective subsections below.

7.10.1 Development Errors

The errors and exceptions described in [SWS_Dcm_00040] shall be detectable by the

Dcm module depending on its build version (development/production mode).

[SWS_Dcm_00040] Definiton of development errors in module Dcm

Upstream requirements: SRS_BSW_00337

d
Type of error Related error code Error value
The Dcm is getting called with an invalid input DCM_E_INVALID_VALUE 0x02
parameter value or the Dcm has called an function
and this function returns an invalid out parameter
or return value.
Interface return-value is out of range DCM_E_INTERFACE_RETURN_VALUE 0x02
Internal:Dcm not initialized DCM_E_UNINIT 0x05
Dcm API function with invalid input parameter DCM_E_PARAM 0x06
Dcm API service invoked with NULL POINTER as DCM_E_PARAM_POINTER 0x07
parameter
Dcm initialisation failed DCM_E_INIT_FAILED 0x08
Storing the ProgConditions failed DCM_E_SET_PROG_CONDITIONS_FAIL 0x09

7.10.2 Runtime Errors

The errors and exceptions described in [SWS_Dcm_01416] shall be detectable by the

Dcm module depending on its build version (development/production mode).

254 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01416] Definiton of runtime errors in module Dcm

Upstream requirements: SRS_BSW_00452

d
Type of error Related error code Error value
Interface: Timeout occurred during interaction with DCM_E_INTERFACE_TIMEOUT 0x01
another module (e.g. maximum number of
response pending is reached, refer to
[SWS_Dcm_00120])
Interface: Boundary check of buffers provided by DCM_E_INTERFACE_BUFFER_OVERFLOW 0x03
the Dcm failed during interaction with another
module (application, Dem,PduR, etc.)

7.10.3 Production Errors

There are no production errors.

7.10.4 Extended Production Errors

There are no extended production errors.

7.11 Security Events

[SWS_Dcm_01589]
Upstream requirements: RS_Ids_00810

dIf security event reporting has been enabled for the Dcm module ( DcmEnableSecu-
rityEventReporting = true) the respective security events shall be reported to the
IdsM via the interfaces defined in AUTOSAR_SWS_BSWGeneral.c

[SWS_Dcm_01590] Security events for Dcm

Status: DRAFT
Upstream requirements: RS_Ids_00810

d
Name Description ID
SEV_UDS_SECURITY_ACCESS_NEEDED Tester has sent a diagnostic request without meeting the 100
server’s security level requirements for that service. NRC
0x33 (securityAccessDenied) was returned.
5

255 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Name Description ID
SEV_UDS_AUTHENTICATION_NEEDED A diagnostic request was received while the required 101
authentication to execute this service is not given. NRC
0x34 (authenticationRequired) was returned.
SEV_UDS_SECURITY_ACCESS_ Successful unlocked the ECU (via Security Access SID 102
SUCCESSFUL 0x27)
SEV_UDS_SECURITY_ACCESS_FAILED Unlocking of the ECU (via Security Access SID 0x27) failed 103
SEV_UDS_AUTHENTICATION_SUCCESSFUL Succesfully authenticated (via Authentication SID 0x29) 104
SEV_UDS_AUTHENTICATION_FAILED Authentication (via Authentication SID 0x29) failed 105
SEV_UDS_WRITE_DATA_SUCCESSFUL Diagnostic data identifier has been written by SID 0x2E 106
WriteDataByIdentifier
SEV_UDS_WRITE_DATA_FAILED Change of Diagnostic data identifier has been requested 107
by SID 0x2E WriteDataByIdentifier, but failed
SEV_UDS_WRITE_MEMORY_SUCCESSFUL Data has been written into memory by SID 0x3D Write 108
MemoryByAddress
SEV_UDS_WRITE_MEMORY_FAILED Writting of Data into memory has been requested by SID 109
0x3D WriteMemoryByAddress, but failed
SEV_UDS_REQUEST_UP_DOWNLOAD_ An upload / download sequence has been requested 110
SUCCESSFUL successfully with SID 0x34 or SID 0x35
SEV_UDS_REQUEST_UP_DOWNLOAD_ An upload / download sequence has been requested with 111
FAILED SID 0x34 or SID 0x35, but failed
SEV_UDS_REQUEST_FILE_TRANSFER_ A file transfer sequence has been requested successfully 112
SUCCESSFUL with SID 0x38.
SEV_UDS_REQUEST_FILE_TRANSFER_ A file transfer sequence has been requested with SID 113
FAILED 0x38, but failed
SEV_UDS_COMMUNICATION_CONTROL_ The control of a communication has been requested by 114
SUCCESSFUL service SID 0x28 CommunicationControl successfully.
SEV_UDS_COMMUNICATION_CONTROL_ The control of a communication has been requested by 115
FAILED service SID 0x28 CommunicationControl, but failed.
SEV_UDS_CLEAR_DTC_SUCCESSFUL DTC information has been cleared by SID 0x14 Clear 116
DiagnosticInformation.
SEV_UDS_CLEAR_DTC_FAILED Clearing DTC information has been requested by SID 0x14 117
ClearDiagnosticInformation, but failed.
SEV_UDS_CONTROL_DTC_SETTING_ The control of a DTC setting has been requested by 118
SUCCESSFUL service SID 0x85 ControlDTCSetting successfully.
SEV_UDS_CONTROL_DTC_SETTING_FAILED Control of DTC setting has been requested by service SID 119
0x85 ControlDTCSetting, but failed.
SEV_UDS_ECU_RESET_SUCCESSFUL ECU has been reset by SID 0x11 ECUReset. 120
SEV_UDS_ECU_RESET_FAILED ECU Reset has been requested by SID 0x11 ECUReset, 121
but failed.
SEV_UDS_ROUTINE_CONTROL_ The control of a routine has been requested by service SID 122
SUCCESSFUL 0x31 RoutineControl successfully.
SEV_UDS_ROUTINE_CONTROL_FAILED The control of a routine has been requested by service SID 123
0x31 RoutineControl, but failed.
SEV_UDS_IO_CONTROL_SUCCESSFUL IOControl operation has been requested by service SID 124
0x2F InputOutputControlByIdentifier successfully.
SEV_UDS_IO_CONTROL_FAILED IOControl operation has been requested by service SID 125
0x2F InputOutputControlByIdentifier, but failed.

256 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01702] Reporting security access denied to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service request is not allowed in the current security level, which
results in a negative response with NRC 0x33 (securityAccessDenied), the Dcm shall
report a security event SEV_UDS_SECURITY_ACCESS_NEEDED to IdsM (see [11]
and table [SWS_Dcm_01703]) with the context data given in [SWS_Dcm_01703].c

[SWS_Dcm_01703] Security event context data definition: SEV_UDS_SECU-

RITY_ACCESS_NEEDED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_SECURITY_ACCESS_NEEDED
ID 100
Description Tester has sent a diagnostic request without meeting the server’s security level requirements
for that service. NRC 0x33 (securityAccessDenied) was returned.
Context Data Version 1
Context Data Data Type Allowed Values
SID uint8
Subfunction uint8 255: is filled in case the service is without Subfunction
DataIdentifier uint16 65535: is filled in case the service is without DID
RoutineIdentifier uint16 65535: is filled in case the service is without RID
ClientSourceAddress uint16

[SWS_Dcm_01704] Reporting authentication required to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service request is not having the required authentication which
results in a negative response with NRC 0x34 (authenticationRequired), the Dcm shall
report a security event SEV_UDS_AUTHENTICATION_NEEDED to IdsM (see [11] and
table [SWS_Dcm_01705]) with the context data given in [SWS_Dcm_01705].c

257 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01705] Security event context data definition: SEV_UDS_AUTHEN-

TICATION_NEEDED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_AUTHENTICATION_NEEDED
ID 101
Description A diagnostic request was received while the required authentication to execute this service
is not given. NRC 0x34 (authenticationRequired) was returned.
Context Data Version 1
Context Data Data Type Allowed Values
SID uint8
Subfunction uint8 255: is filled in case the service is without Subfunction
DataIdentifier uint16 65535: is filled in case the service is without DID
RoutineIdentifier uint16 65535: is filled in case the service is without RID
ClientSourceAddress uint16

[SWS_Dcm_01706] Reporting successful security access to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service SecurityAccess with subfunction CompareKey is re-

ceived, which successfully unlocks the requested security access type, the Dcm shall
report a security event SEV_UDS_SECURITY_ACCESS_SUCCESSFUL to IdsM (see
[11] and table [SWS_Dcm_01707]) with the context data given in [SWS_Dcm_01707].c

[SWS_Dcm_01707] Security event context data definition: SEV_UDS_SECU-

RITY_ACCESS_SUCCESSFUL
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_SECURITY_ACCESS_SUCCESSFUL
ID 102
Description Successful unlocked the ECU (via Security Access SID 0x27)
Context Data Version 1
Context Data Data Type Allowed Values
Subfunction uint8
ClientSourceAddress uint16

258 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01708] Reporting failed security access to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service SecurityAccess is received, which re-

sults in a negative response,the Dcm shall report a security event
SEV_UDS_SECURITY_ACCESS_FAILED to IdsM (see [11] and table
[SWS_Dcm_01709]) with the context data given in [SWS_Dcm_01709].c

[SWS_Dcm_01709] Security event context data definition: SEV_UDS_SECU-

RITY_ACCESS_FAILED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_SECURITY_ACCESS_FAILED
ID 103
Description Unlocking of the ECU (via Security Access SID 0x27) failed
Context Data Version 1
Context Data Data Type Allowed Values
Subfunction uint8
ClientSourceAddress uint16
NegativeResponseCode uint8

[SWS_Dcm_01710] Reporting successful authentication to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service Authentication with subfunction proofOfOwnership is

received, which is successful, the Dcm shall report a security event
SEV_UDS_AUTHENTICATION_SUCCESSFUL to IdsM (see [11] and table
[SWS_Dcm_01711]) with the context data given in [SWS_Dcm_01711].c

[SWS_Dcm_01711] Security event context data definition: SEV_UDS_AUTHEN-

TICATION_SUCCESSFUL
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_AUTHENTICATION_SUCCESSFUL
ID 104
Description Succesfully authenticated (via Authentication SID 0x29)
Context Data Version 1
Context Data Data Type Allowed Values
Subfunction uint8
5

259 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
SEV Name SEV_UDS_AUTHENTICATION_SUCCESSFUL
ClientSourceAddress uint16

[SWS_Dcm_01712] Reporting failed authentication to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service Authentication is received, which results in a negative re-
sponse, the Dcm shall report a security event SEV_UDS_AUTHENTICATION_FAILED
to IdsM (see [11] and table [SWS_Dcm_01713]) with the context data given in
[SWS_Dcm_01713].c

[SWS_Dcm_01713] Security event context data definition: SEV_UDS_AUTHEN-

TICATION_FAILED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_AUTHENTICATION_FAILED
ID 105
Description Authentication (via Authentication SID 0x29) failed
Context Data Version 1
Context Data Data Type Allowed Values
Subfunction uint8
ClientSourceAddress uint16
NegativeResponseCode uint8

[SWS_Dcm_01714] Reporting successful writing of data to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service WriteDataByIdentifier is received, which

results in a positive response, the Dcm shall report a security event
SEV_UDS_WRITE_DATA_SUCCESSFUL to IdsM (see [11] and table
[SWS_Dcm_01715]) with the context data given in [SWS_Dcm_01715].c

260 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01715] Security event context data definition: SEV_UDS_WRITE_

DATA_SUCCESSFUL
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_WRITE_DATA_SUCCESSFUL
ID 106
Description Diagnostic data identifier has been written by SID 0x2E WriteDataByIdentifier
Context Data Version 1
Context Data Data Type Allowed Values
DID uint16
ClientSourceAddress uint16

[SWS_Dcm_01716] Reporting writing of data failed to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service WriteDataByIdentifier is received, which results in a nega-

tive response, the Dcm shall report a security event SEV_UDS_WRITE_DATA_FAILED
to IdsM (see [11] and table [SWS_Dcm_01717]) with the context data given in
[SWS_Dcm_01717].c

[SWS_Dcm_01717] Security event context data definition: SEV_UDS_WRITE_

DATA_FAILED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_WRITE_DATA_FAILED
ID 107
Description Change of Diagnostic data identifier has been requested by SID 0x2E WriteDataByIdentifier,
but failed
Context Data Version 1
Context Data Data Type Allowed Values
DID uint16
ClientSourceAddress uint16
NegativeResponseCode uint8

[SWS_Dcm_01718] Reporting successful up download to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service RequestDownload or RequestUpload is received,

which results in a positive response, the Dcm shall report a security event

261 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

SEV_UDS_REQUEST_UP_DOWNLOAD_SUCCESSFUL to IdsM (see [11] and table

[SWS_Dcm_01719]) with the context data given in [SWS_Dcm_01719].c

[SWS_Dcm_01719] Security event context data definition: SEV_UDS_REQUEST_

UP_DOWNLOAD_SUCCESSFUL
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_REQUEST_UP_DOWNLOAD_SUCCESSFUL
ID 110
Description An upload / download sequence has been requested successfully with SID 0x34 or SID 0x35
Context Data Version 1
Context Data Data Type Allowed Values
SID uint8
MemoryAddress uint32
MemorySize uint32
ClientSourceAddress uint16

[SWS_Dcm_01720] Reporting up download failed to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service RequestDownload or RequestUpload is received,

which results in a negative response, the Dcm shall report a security event
SEV_UDS_REQUEST_UP_DOWNLOAD_FAILED to IdsM (see [11] and table
[SWS_Dcm_01719]) with the context data given in [SWS_Dcm_01719].c

[SWS_Dcm_01721] Security event context data definition: SEV_UDS_REQUEST_

UP_DOWNLOAD_FAILED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_REQUEST_UP_DOWNLOAD_FAILED
ID 111
Description An upload / download sequence has been requested with SID 0x34 or SID 0x35, but failed
Context Data Version 1
Context Data Data Type Allowed Values
SID uint8
MemoryAddress uint32
MemorySize uint32
ClientSourceAddress uint16
NegativeResponseCode uint8

262 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01722] Reporting successful file transfer to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service RequestFileTransfer is received, which re-

sults in a positive response, the Dcm shall report a security event
SEV_UDS_REQUEST_FILE_TRANSFER_SUCCESSFUL to IdsM (see [11] and
table [SWS_Dcm_01723]) with the context data given in [SWS_Dcm_01723].c

[SWS_Dcm_01723] Security event context data definition: SEV_UDS_REQUEST_

FILE_TRANSFER_SUCCESSFUL
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_REQUEST_FILE_TRANSFER_SUCCESSFUL
ID 112
Description A file transfer sequence has been requested successfully with SID 0x38.
Context Data Version 1
Context Data Data Type Allowed Values
ModeOfOperation uint8 AddFile (0x01)
DeleteFile (0x02)
ReplaceFile (0x03)
ReadFile (0x04)
ReadDir (0x05)
ResumeFile (0x06)
FilePathAndName uint8 [50] Each byte of this parameter is encoded in ASCII format.
ClientSourceAddress uint16

[SWS_Dcm_01724] Reporting file transfer failed to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service RequestFileTransfer is received, which re-

sults in a negative response, the Dcm shall report a security event
SEV_UDS_REQUEST_FILE_TRANSFER_FAILED to IdsM (see [11] and table
[SWS_Dcm_01725]) with the context data given in [SWS_Dcm_01725].c

263 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01725] Security event context data definition: SEV_UDS_REQUEST_

FILE_TRANSFER_FAILED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_REQUEST_FILE_TRANSFER_FAILED
ID 113
Description A file transfer sequence has been requested with SID 0x38, but failed
Context Data Version 1
Context Data Data Type Allowed Values
ModeOfOperation uint8 AddFile (0x01)
DeleteFile (0x02)
ReplaceFile (0x03)
ReadFile (0x04)
ReadDir (0x05)
ResumeFile (0x06)
FilePathAndName uint8 [50] Each byte of this parameter is encoded in ASCII format.
ClientSourceAddress uint16
NegativeResponseCode uint8

[SWS_Dcm_01726] Reporting successful communication control to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service CommunicationControl is received, which

results in a positive response, the Dcm shall report a security event
SEV_UDS_COMMUNICATION_CONTROL_SUCCESSFUL to IdsM (see [11] and
table [SWS_Dcm_01727]) with the context data given in [SWS_Dcm_01727].c

[SWS_Dcm_01727] Security event context data definition: SEV_UDS_COMMUNI-

CATION_CONTROL_SUCCESSFUL
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_COMMUNICATION_CONTROL_SUCCESSFUL
ID 114
Description The control of a communication has been requested by service SID 0x28 Communication
Control successfully.
Context Data Version 1
Context Data Data Type Allowed Values
Subfunction uint8
ClientSourceAddress uint16

264 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01728] Reporting communication control failed to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service CommunicationControl is received, which

results in a negative response, the Dcm shall report a security event
SEV_UDS_COMMUNICATION_CONTROL_FAILED to IdsM (see [11] and table
[SWS_Dcm_01729]) with the context data given in [SWS_Dcm_01729].c

[SWS_Dcm_01729] Security event context data definition: SEV_UDS_COMMUNI-

CATION_CONTROL_FAILED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_COMMUNICATION_CONTROL_FAILED
ID 115
Description The control of a communication has been requested by service SID 0x28 Communication
Control, but failed.
Context Data Version 1
Context Data Data Type Allowed Values
Subfunction uint8
ClientSourceAddress uint16
NegativeResponseCode uint8

[SWS_Dcm_01730] Reporting successful clearing of dtc to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service ClearDiagnosticInformation is received,

which results in a positive response, the Dcm shall report a security
event SEV_UDS_CLEAR_DTC_SUCCESSFUL to IdsM (see [11] and table
[SWS_Dcm_01731]) with the context data given in [SWS_Dcm_01731].c

[SWS_Dcm_01731] Security event context data definition: SEV_UDS_CLEAR_

DTC_SUCCESSFUL
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_CLEAR_DTC_SUCCESSFUL
ID 116
Description DTC information has been cleared by SID 0x14 ClearDiagnosticInformation.
Context Data Version 1
Context Data Data Type Allowed Values
5

265 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
SEV Name SEV_UDS_CLEAR_DTC_SUCCESSFUL
GroupOfDTC uint8 [3] given in the format: HighByte, MiddleByte, LowByte
MemorySelection uint16 0x0001: PrimaryMemory
0x01XX: XX is the address of the UserDefinedMemory
ClientSourceAddress uint16

[SWS_Dcm_01732] Reporting clearing of dtc failed to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service ClearDiagnosticInformation is received, which results in

a negative response, the Dcm shall report a security event
SEV_UDS_CLEAR_DTC_FAILED to IdsM (see [11] and table [SWS_Dcm_01733])
with the context data given in [SWS_Dcm_01733].c

[SWS_Dcm_01733] Security event context data definition: SEV_UDS_CLEAR_

DTC_FAILED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_CLEAR_DTC_FAILED
ID 117
Description Clearing DTC information has been requested by SID 0x14 ClearDiagnosticInformation, but
failed.
Context Data Version 1
Context Data Data Type Allowed Values
GroupOfDTC uint8 [3] given in the format: HighByte, MiddleByte, LowByte
MemorySelection uint16 0x0001: PrimaryMemory
0x01XX: XX is the address of the UserDefinedMemory
ClientSourceAddress uint16
NegativeResponseCode uint8

[SWS_Dcm_01734] Reporting successful control of dtc to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service ControlDTCSetting is received, which re-

sults in a positive response, the Dcm shall report a security event
SEV_UDS_CONTROL_DTC_SETTING_SUCCESSFUL to IdsM (see [11] and
table [SWS_Dcm_01735]) with the context data given in [SWS_Dcm_01735].c

266 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01735] Security event context data definition: SEV_UDS_CON-

TROL_DTC_SETTING_SUCCESSFUL
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_CONTROL_DTC_SETTING_SUCCESSFUL
ID 118
Description The control of a DTC setting has been requested by service SID 0x85 ControlDTCSetting
successfully.
Context Data Version 1
Context Data Data Type Allowed Values
Subfunction uint8
ClientSourceAddress uint16

[SWS_Dcm_01736] Reporting control of dtc failed to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service ControlDTCSetting is received, which re-

sults in a negative response, the Dcm shall report a security event
SEV_UDS_CONTROL_DTC_SETTING_FAILED to IdsM (see [11] and table
[SWS_Dcm_01737]) with the context data given in [SWS_Dcm_01737].c

[SWS_Dcm_01737] Security event context data definition: SEV_UDS_CON-

TROL_DTC_SETTING_FAILED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_CONTROL_DTC_SETTING_FAILED
ID 119
Description Control of DTC setting has been requested by service SID 0x85 ControlDTCSetting, but
failed.
Context Data Version 1
Context Data Data Type Allowed Values
Subfunction uint8
ClientSourceAddress uint16
NegativeResponseCode uint8

[SWS_Dcm_01738] Reporting successful reset of ECU to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service ECUReset is received, which re-

sults in a positive response, the Dcm shall report a security event

267 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

SEV_UDS_ECU_RESET_SUCCESSFUL to IdsM (see [11] and table

[SWS_Dcm_01739]) with the context data given in [SWS_Dcm_01739].c

[SWS_Dcm_01739] Security event context data definition: SEV_UDS_ECU_RE-

SET_SUCCESSFUL
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_ECU_RESET_SUCCESSFUL
ID 120
Description ECU has been reset by SID 0x11 ECUReset.
Context Data Version 1
Context Data Data Type Allowed Values
Subfunction uint8
ClientSourceAddress uint16

[SWS_Dcm_01740] Reporting reset of ECU failed to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service ECUReset is received, which results in a negative

response, the Dcm shall report a security event SEV_UDS_ECU_RESET_FAILED
to IdsM (see [11] and table [SWS_Dcm_01741]) with the context data given in
[SWS_Dcm_01741].c

[SWS_Dcm_01741] Security event context data definition: SEV_UDS_ECU_RE-

SET_FAILED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_ECU_RESET_FAILED
ID 121
Description ECU Reset has been requested by SID 0x11 ECUReset, but failed.
Context Data Version 1
Context Data Data Type Allowed Values
Subfunction uint8
ClientSourceAddress uint16
NegativeResponseCode uint8

268 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01742] Reporting successful routine control to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service RoutineControl is received, which re-

sults in a positive response, the Dcm shall report a security event
SEV_UDS_ROUTINE_CONTROL_SUCCESSFUL to IdsM (see [11] and table
[SWS_Dcm_01743]) with the context data given in [SWS_Dcm_01743].c

[SWS_Dcm_01743] Security event context data definition: SEV_UDS_ROUTINE_

CONTROL_SUCCESSFUL
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_ROUTINE_CONTROL_SUCCESSFUL
ID 122
Description The control of a routine has been requested by service SID 0x31 RoutineControl
successfully.
Context Data Version 1
Context Data Data Type Allowed Values
RID uint16
Subfunction uint8
ClientSourceAddress uint16

[SWS_Dcm_01744] Reporting routine control failed to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service RoutineControl is received, which re-

sults in a negative response, the Dcm shall report a security event
SEV_UDS_ROUTINE_CONTROL_FAILED to IdsM (see [11] and table
[SWS_Dcm_01745]) with the context data given in [SWS_Dcm_01745].c

[SWS_Dcm_01745] Security event context data definition: SEV_UDS_ROUTINE_

CONTROL_FAILED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_ROUTINE_CONTROL_FAILED
ID 123
Description The control of a routine has been requested by service SID 0x31 RoutineControl, but failed.
Context Data Version 1
Context Data Data Type Allowed Values
5

269 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
SEV Name SEV_UDS_ROUTINE_CONTROL_FAILED
RID uint16
Subfunction uint8
ClientSourceAddress uint16
NegativeResponseCode uint8

[SWS_Dcm_01746] Reporting successful IO control to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service IOControl is received, which re-

sults in a positive response, the Dcm shall report a security event
SEV_UDS_IO_CONTROL_SUCCESSFUL to IdsM (see [11] and table
[SWS_Dcm_01747]) with the context data given in [SWS_Dcm_01747].c

[SWS_Dcm_01747] Security event context data definition: SEV_UDS_IO_CON-

TROL_SUCCESSFUL
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_IO_CONTROL_SUCCESSFUL
ID 124
Description IOControl operation has been requested by service SID 0x2F InputOutputControlBy
Identifier successfully.
Context Data Version 1
Context Data Data Type Allowed Values
DID uint16
inputOutputControlParameter uint8
ClientSourceAddress uint16

[SWS_Dcm_01748] Reporting IO control failed to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service IOControl is received, which results in a negative re-
sponse, the Dcm shall report a security event SEV_UDS_IO_CONTROL_FAILED
to IdsM (see [11] and table [SWS_Dcm_01749]) with the context data given in
[SWS_Dcm_01749].c

270 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01749] Security event context data definition: SEV_UDS_IO_CON-

TROL_FAILED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_IO_CONTROL_FAILED
ID 125
Description IOControl operation has been requested by service SID 0x2F InputOutputControlBy
Identifier, but failed.
Context Data Version 1
Context Data Data Type Allowed Values
DID uint16
inputOutputControlParameter uint8
ClientSourceAddress uint16
NegativeResponseCode uint8

[SWS_Dcm_01750] Reporting successful Memory Write operation to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service WriteMemoryByAddress is received, which

results in a positive response, the Dcm shall report a security event
SEV_UDS_WRITE_MEMORY_SUCCESSFUL to IdsM (see [11] and table
[SWS_Dcm_01751]) with the context data given in [SWS_Dcm_01751].c

[SWS_Dcm_01751] Security event context data definition: SEV_UDS_WRITE_

MEMORY_SUCCESSFUL
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_WRITE_MEMORY_SUCCESSFUL
ID 108
Description Data has been written into memory by SID 0x3D WriteMemoryByAddress
Context Data Version 1
Context Data Data Type Allowed Values
MemoryAddress uint32
MemorySize uint32
ClientSourceAddress uint16

271 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01752] Reporting Write Memory failed to IdsM

Upstream requirements: RS_Ids_00810

dIn case a diagnostic service WriteMemoryByAddress is received,

which results in a negative response, the Dcm shall report a security
event SEV_UDS_WRITE_MEMORY_FAILED to IdsM (see [11] and table
[SWS_Dcm_01753]) with the context data given in [SWS_Dcm_01753].c

[SWS_Dcm_01753] Security event context data definition: SEV_UDS_WRITE_

MEMORY_FAILED
Status: DRAFT
Upstream requirements: RS_Ids_00810

d
SEV Name SEV_UDS_WRITE_MEMORY_FAILED
ID 109
Description Writting of Data into memory has been requested by SID 0x3D WriteMemoryByAddress, but
failed
Context Data Version 1
Context Data Data Type Allowed Values
MemoryAddress uint32
MemorySize uint32
ClientSourceAddress uint16
NegativeResponseCode uint8

272 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8 API specification
This section defines:
• The syntax and semantics of the functions that are provided and required from
other BSW modules. These take the form of "C"-APIs.
• The syntax and semantics of a subset of those functions which are used by
software-components through the RTE. These take the form of descriptions using
the concepts of the Software-Component Template.

8.1 Imported types

In this chapter all types included from the following files are listed.

[SWS_Dcm_00333] Definition of imported datatypes of module Dcm d

Module Header File Imported Type
BndM bndm.h BndM_BlockIdType
bndm.h BndM_ResultType
bndm_externals.h BndM_Block{BlockId.Shortname}Type

Comtype ComStack_Types.h BufReq_ReturnType

ComStack_Types.h NetworkHandleType
ComStack_Types.h PduIdType
ComStack_Types.h PduInfoType
ComStack_Types.h PduLengthType
ComStack_Types.h RetryInfoType
ComStack_Types.h TpDataStateType
Csm Rte_Csm_Type.h Crypto_ResultType

Dem Dem.h Dem_DTCRequestType

Dem.h Dem_DTCSeverityType
Dem.h Dem_DTCTranslationFormatType
Rte_Dem_Type.h Dem_DTCFormatType
Rte_Dem_Type.h Dem_DTCOriginType
Rte_Dem_Type.h Dem_UdsStatusByteType
IdsM IdsM_Types.h IdsM_SecurityEventIdType
KeyM Rte_KeyM_Type.h KeyM_CertificateIdType
Rte_KeyM_Type.h KeyM_CertificateStatusType
NvM Rte_NvM_Type.h NvM_BlockIdType
Std Std_Types.h Std_ReturnType
Std_Types.h Std_VersionInfoType

273 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.2 Type definitions

The Dcm module shall ensure that implementation-specific types are not "visible" out-
side of Dcm. Otherwise, the complete architecture would be corrupted.
This section lists the types which are defined by the Dcm SWS.

8.2.1 Dcm_StatusType

[SWS_Dcm_00976] Definition of datatype Dcm_StatusType d

Name Dcm_StatusType
Kind Type
Derived from uint8
Range DCM_E_OK 0x00 This value is representing a
successful operation.
DCM_E_ROE_NOT_ 0x06 ResponseOnOneEvent request is
ACCEPTED not accepted by DCM
DCM_E_PERIODICID_ 0x07 Periodic transmission request is
NOT_ACCEPTED not accepted by DCM
Description Base item type to transport status information.
Available via Dcm.h

8.2.2 Dcm_CommunicationModeType

[SWS_Dcm_00981] Definition of datatype Dcm_CommunicationModeType d

Name Dcm_CommunicationModeType
Kind Type
Derived from uint8
Range DCM_ENABLE_RX_TX_ 0x00 Enable the Rx and Tx for normal
NORM communication
DCM_ENABLE_RX_ 0x01 Enable the Rx and disable the Tx
DISABLE_TX_NORM for normal communication
DCM_DISABLE_RX_ 0x02 Disable the Rx and enable the Tx
ENABLE_TX_NORM for normal communication
DCM_DISABLE_RX_TX_ 0x03 Disable Rx and Tx for normal
NORMAL communication
DCM_ENABLE_RX_TX_ 0x04 Enable the Rx and Tx for network
NM management communication
5

274 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
DCM_ENABLE_RX_ 0x05 Enable Rx and disable the Tx for
DISABLE_TX_NM network management
communication
DCM_DISABLE_RX_ 0x06 Disable the Rx and enable the Tx
ENABLE_TX_NM for network management
communication
DCM_DISABLE_RX_TX_ 0x07 Disable Rx and Tx for network
NM management communication
DCM_ENABLE_RX_TX_ 0x08 Enable Rx and Tx for normal and
NORM_NM network management
communication
DCM_ENABLE_RX_ 0x09 Enable the Rx and disable the Tx
DISABLE_TX_NORM_NM for normal and network
management communication
DCM_DISABLE_RX_ 0x0A Disable the Rx and enable the Tx
ENABLE_TX_NORM_NM for normal and network
management communication
DCM_DISABLE_RX_TX_ 0x0B Disable Rx and Tx for normal and
NORM_NM network management
communication
Description –
Available via Dcm.h

8.2.3 Dcm_ConfigType

[SWS_Dcm_00982] Definition of datatype Dcm_ConfigType d

Name Dcm_ConfigType
Kind Structure
Elements Implementation specific
Type –
Comment –
Description This type defines a data structure for the post build parameters of the DCM . At initialization the
DCM gets a pointer to a structure of this type to get access to its configuration data, which is
necessary for initialization.
Available via Dcm.h

275 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.2.4 Dcm_ReturnReadMemoryType

[SWS_Dcm_00985] Definition of datatype Dcm_ReturnReadMemoryType d

Name Dcm_ReturnReadMemoryType
Kind Type
Derived from uint8
Range DCM_READ_OK 0x00 Reading has been done
DCM_READ_PENDING 0x01 Reading is pending, another call
is request to finalize the reading
DCM_READ_FAILED 0x02 Reading has failed
DCM_READ_FORCE_ 0x03 Reading is pending, the
RCRRP Response pending transmission
starts immediately
Description Return values of Callout Dcm_ReadMemory
Available via Dcm.h

8.2.5 Dcm_ReturnWriteMemoryType

[SWS_Dcm_00986] Definition of datatype Dcm_ReturnWriteMemoryType d

Name Dcm_ReturnWriteMemoryType
Kind Type
Derived from uint8
Range DCM_WRITE_OK 0x00 Writing has been done
DCM_WRITE_PENDING 0x01 Writing is pending, another called
is requested
DCM_WRITE_FAILED 0x02 The writing has failed
DCM_WRITE_FORCE_ 0x03 Writing is pending, the Response
RCRRP pending transmission starts
immediately
Description Return type of callout Dcm_WriteMemory
Available via Dcm.h

276 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.2.6 Dcm_EcuStartModeType

[SWS_Dcm_00987] Definition of datatype Dcm_EcuStartModeType d

Name Dcm_EcuStartModeType
Kind Type
Derived from uint8
Range DCM_COLD_START 0x00 The ECU starts normally
DCM_WARM_START 0x01 The ECU starts from a bootloader
jump
Description Allows the DCM to know if a diagnostic response shall be sent in the case of a jump from
bootloader
Available via Dcm.h

8.2.7 Dcm_ProgConditionsType

[SWS_Dcm_00988] Definition of datatype Dcm_ProgConditionsType d

Name Dcm_ProgConditionsType
Kind Structure
ConnectionId
Elements Type uint16
Comment Unique id of the connection on which the request has been received
TesterAddress
Type uint16
Comment Source address of the received request if meta data is enabled,
otherwise the value as configured in DcmDslProtocolRxTesterSource
Addr
Sid
Type uint8
Comment Service identifier of the received request
SubFncId
Type uint8
Comment Identifier of the received subfonction
ReprogrammingRequest
Type boolean
Comment Set to true in order to request reprogramming of the ECU.
ApplUpdated
Type boolean
Comment Indicate whether the application has been updated or not.
ResponseRequired
Type boolean
5

277 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Comment Set to true in case the flashloader or application shall send a response.
Description Used in Dcm_SetProgConditions() to allow the integrator to store relevant information prior to
jumping to bootloader / jump due to ECUReset request.
Available via Dcm.h

8.2.8 Dcm_MsgItemType

[SWS_Dcm_00989] Definition of datatype Dcm_MsgItemType d

Name Dcm_MsgItemType
Kind Type
Derived from uint8
Description Base type for diagnostic message item
Available via Dcm.h

8.2.9 Dcm_MsgType

[SWS_Dcm_00990] Definition of datatype Dcm_MsgType d

Name Dcm_MsgType
Kind Pointer
Type Dcm_MsgItemType*
Description Base type for diagnostic message (request, positive or negative response)
Available via Dcm.h

278 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.2.10 Dcm_MsgLenType

[SWS_Dcm_00991] Definition of datatype Dcm_MsgLenType d

Name Dcm_MsgLenType
Kind Type
Derived from uint32
Description Length of diagnostic message (request, positive or negative response). The maximum length is
dependent of the underlying transport protocol/media.
Available via Dcm.h

8.2.11 Dcm_MsgAddInfoType

Please note that the following table describes a struct type definition - including its
struct items "elements".

[SWS_Dcm_00992] Definition of datatype Dcm_MsgAddInfoType d

Name Dcm_MsgAddInfoType
Kind Structure
Elements reqType
Type bit
Comment (Pos LSB+0)
0 = physical request
1 = functional request
suppressPosResponse
Type bit
Comment Position LSB+1
0 = no (do not suppress)
1 = yes (no positive response will be sent)
Description Additional information on message request.
Datastructure: Bitfield
Available via Dcm.h

279 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.2.12 Dcm_IdContextType

[SWS_Dcm_00993] Definition of datatype Dcm_IdContextType d

Name Dcm_IdContextType
Kind Type
Derived from uint8
Description This message context identifier can be used to determine the relation between request and
response confirmation.
Available via Dcm.h

8.2.13 Dcm_MsgContextType

Please note that the following table describes a struct type definition - including its
struct items "elements".

[SWS_Dcm_00994] Definition of datatype Dcm_MsgContextType d

Name Dcm_MsgContextType
Kind Structure
reqData
Elements
Type Dcm_MsgType
Comment Request data, starting directly after service identifier (which is not part
of this data)
reqDataLen
Type Dcm_MsgLenType
Comment Request data length (excluding service identifier)
resData
Type Dcm_MsgType
Comment Positive response data, starting directly after service identifier (which is
not part of this data).
resDataLen
Type Dcm_MsgLenType
Comment Positive response data length (excluding service identifier)
msgAddInfo
Type Dcm_MsgAddInfoType
Comment Additional information about service request and response (see: Dcm_
MsgAddInfo)
resMaxDataLen
Type Dcm_MsgLenType
5

280 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Comment The maximal length of a response is restricted by the size of the buffer.
The buffer size can depend on the diagnostic protocol identifier which
is assigned to this message, e. g. an OBD protocol id can obtain other
properties than the enhanced diagnostic protocol id. The resMaxData
Len is a property of the diagnostic protocol assigned by the DSL. The
value does not change during communication. It cannot be
implemented as a constant, because it can differ between different
diagnostic protocols.
idContext
Type Dcm_IdContextType
Comment This message context identifier can be used to determine the relation
between request and response confirmation. This identifier can be
stored within the application at request time, so that the response can
be assigned to the original request. Background: Within the
confirmation, the message context is no more valid, all message data
is lost. You need an additional information to determine the request to
which this confirmation belongs.
dcmRxPduId:
Type PduIdType
Comment Pdu identifier on which the request was received. The PduId of the
request can have consequences for message processing. E. g. an
OBD request will be received on the OBD PduId and will be processed
slightly different than an enhanced diagnostic request received on the
physical
Description This data structure contains all information which is necessary to process a diagnostic message
from request to response and response confirmation.
Available via Dcm.h

8.2.14 Dcm_ExtendedOpStatusType

[SWS_Dcm_91015] Definition of datatype Dcm_ExtendedOpStatusType d

Name Dcm_ExtendedOpStatusType
Kind Type
Derived from uint8
Range DCM_INITIAL 0x00 Indicates the initial call to the
operation
DCM_PENDING 0x01 Indicates that a pending return
has been done on the previous
call of the operation
DCM_CANCEL 0x02 Indicates that the Dcm requests to
cancel the pending operation
DCM_FORCE_RCRRP_OK 0x03 Confirm a response pending
transmission Variation
DCM_POS_RESPONSE_ 0x04 Indicates that a positive response
SENT has been sent successfully
DCM_POS_RESPONSE_ 0x05 Indicates that a positive response
FAILED has not been sent successfully
5

281 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
DCM_NEG_RESPONSE_ 0x06 Indicates that a negative response
SENT has been sent successfully
DCM_NEG_RESPONSE_ 0x07 Indicates that a negative response
FAILED has not been sent successfully
Description –
Available via Dcm.h

8.3 Function definitions

This section defines the functions provided for other modules.

8.3.1 Functions provided for other BSW components

8.3.1.1 Dcm_Init

[SWS_Dcm_00037] Definition of API function Dcm_Init

Upstream requirements: SRS_BSW_00438, SRS_BSW_00101

d
Service Name Dcm_Init
Syntax void Dcm_Init (
const Dcm_ConfigType* ConfigPtr
)
Service ID [hex] 0x01
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) ConfigPtr Pointer to configuration set in Variant Post-Build.
Parameters (inout) None
Parameters (out) None
Return value None
Description Service for basic initialization of DCM module.
Available via Dcm.h

The call of this service is mandatory before using the Dcm module for further process-
ing.

282 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.3.1.2 Dcm_GetVersionInfo

[SWS_Dcm_00065] Definition of API function Dcm_GetVersionInfo

Upstream requirements: SRS_BSW_00407, SRS_BSW_00482, SRS_BSW_00003

d
Service Name Dcm_GetVersionInfo
Syntax void Dcm_GetVersionInfo (
Std_VersionInfoType* versionInfo
)
Service ID [hex] 0x24
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) versionInfo Pointer to where to store the version information of this module.
Return value None
Description Returns the version information of this module
Available via Dcm.h

8.3.1.3 Dcm_DemTriggerOnDTCStatus

[SWS_Dcm_00614] Definition of API function Dcm_DemTriggerOnDTCStatus d

Service Name Dcm_DemTriggerOnDTCStatus
Syntax Std_ReturnType Dcm_DemTriggerOnDTCStatus (
uint32 DTC,
Dem_UdsStatusByteType DTCStatusOld,
Dem_UdsStatusByteType DTCStatusNew
)
Service ID [hex] 0x2B
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) DTC This is the DTC the change trigger is assigned to.
DTCStatusOld DTC status before change
DTCStatusNew DTC status after change
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: this value is always returned.
Description Triggers on changes of the UDS status byte. Allows to trigger on ROE Event for subservice On
DTCStatusChanged.
Available via Dcm_Dem.h

283 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.3.1.4 Dcm_GetVin

[SWS_Dcm_00950] Definition of API function Dcm_GetVin d

Service Name Dcm_GetVin
Syntax Std_ReturnType Dcm_GetVin (
uint8* Data
)
Service ID [hex] 0x07
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) Data Pointer to where to store the VIN
Return value Std_ReturnType E_OK: The Data pointer has been filled with valid VIN
E_NOT_OK: The default VIN will be used in the DoIP
Description Function to get the VIN (as defined in SAE J1979-DA)
Available via Dcm.h

Note: After fetching the VIN, the Dcm can offer the data to all users without worrying
that the data is unavailable if a user asks for it. This is necessary because the VIN
could not be fetched synchronously for all settings of DcmDspDidDataUsePort.
Note: The invocation of functions BndM_WriteStart and BndM_WriteFinalize are not
part of Dcm Specification. The functions are called via project specific CDD implemen-
tation.

8.3.1.5 Dcm_BndMWriteBlockFinish

[SWS_Dcm_91088] Definition of API function Dcm_BndMWriteBlockFinish

Upstream requirements: RS_Diag_04243

d
Service Name Dcm_BndMWriteBlockFinish
Syntax void Dcm_BndMWriteBlockFinish (
BndM_BlockIdType BlockId,
BndM_ResultType result
)
Service ID [hex] 0x7a
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) BlockId –
result –
5

284 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Parameters (inout) None
Parameters (out) None
Return value None
Description Called by BndM to indicate that a block write operation has finished.
Available via Dcm.h

8.3.2 Functions provided to BSW modules and to SW-Cs

The functions defined in this section can also be used by SW-Cs through the RTE.

8.3.2.1 Dcm_SetDeauthenticatedRole

[SWS_Dcm_91069] Definition of API function Dcm_SetDeauthenticatedRole d

Service Name Dcm_SetDeauthenticatedRole
Syntax Std_ReturnType Dcm_SetDeauthenticatedRole (
uint16 connectionId,
const Dcm_AuthenticationRoleType* deauthenticatedRole
)
Service ID [hex] 0x79
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) connectionId Unique connection identifier identifiying the connection for which
a deauthenticated roles is set.
deauthenticatedRole New deauthenticated role that is assigned to that connection
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: this value is always returned.
Description Sets a new role used in deauthenticated state for that connection. The set role is valid until the
connection switches into authenticated state or the ECU is reset.
Available via Dcm.h

285 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.3.2.2 Dcm_GetSecurityLevel

[SWS_Dcm_00338] Definition of API function Dcm_GetSecurityLevel

Upstream requirements: RS_Diag_04005, RS_Diag_04011

d
Service Name Dcm_GetSecurityLevel
Syntax Std_ReturnType Dcm_GetSecurityLevel (
Dcm_SecLevelType* SecLevel
)
Service ID [hex] 0x0d
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) SecLevel Active Security Level value Conversion formula to calculate
SecurityLevel out of tester requested SecurityAccessType
parameter: SecurityLevel = (SecurityAccessType + 1) / 2 Content
of SecurityAccessType is according to "securityAccessType"
parameter of SecurityAccess request (see [11])
Return value Std_ReturnType E_OK: this value is always returned.
Description This function provides the active security level value.
Available via Dcm.h

8.3.2.3 Dcm_GetSesCtrlType

[SWS_Dcm_00339] Definition of API function Dcm_GetSesCtrlType

Upstream requirements: RS_Diag_04006, RS_Diag_04011

d
Service Name Dcm_GetSesCtrlType
Syntax Std_ReturnType Dcm_GetSesCtrlType (
Dcm_SesCtrlType* SesCtrlType
)
Service ID [hex] 0x06
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) SesCtrlType Active Session Control Type value Content is according to
"diagnosticSessionType" parameter of DiagnosticSessionControl
request (see [11])
Return value Std_ReturnType E_OK: this value is always returned.
5

286 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Description This function provides the active session control type value.
Available via Dcm.h

8.3.2.4 Dcm_ResetToDefaultSession

[SWS_Dcm_00520] Definition of API function Dcm_ResetToDefaultSession d

Service Name Dcm_ResetToDefaultSession
Syntax Std_ReturnType Dcm_ResetToDefaultSession (
void
)
Service ID [hex] 0x2a
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: this value is always returned.
Description The call to this function allows the application to reset the current session to Default session.
Example: Automatic termination of an extended diagnostic session upon exceeding of a speed
limit.
Available via Dcm.h

8.3.2.5 Dcm_ SetActiveDiagnostic

[SWS_Dcm_01068] Definition of API function Dcm_SetActiveDiagnostic d

Service Name Dcm_SetActiveDiagnostic
Syntax Std_ReturnType Dcm_SetActiveDiagnostic (
boolean active
)
Service ID [hex] 0x56
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) active If false Dcm shall not call ComM_DCM_ActiveDiagnostic(). If true
Dcm will call ComM_DCM_ActiveDiagnostic().
Parameters (inout) None
Parameters (out) None
5

287 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Return value Std_ReturnType E_OK: this value is always returned.
Description Allows to activate and deactivate the call of ComM_DCM_ActiveDiagnostic() function.
Available via Dcm.h

8.4 Callback notifications

This section defines the functions provided for lower layer BSW modules.
class DCMCallbacks

«module»
Dcm

«realize» «realize»

«interface» «interface»
Dcm_PduR Dcm_ComM

Dcm_CopyRxData() Dcm_ComMNoComModeEntered()
Dcm_CopyTxData() Dcm_ComMSilentComModeEntered()
Dcm_RxIndication() Dcm_ComMFullComModeEntered()
Dcm_TxConfirmation()
Dcm_StartOfReception()

«optional»

«module»
«module»
__PduR
ComM

Figure 8.1: Overview of the callbacks provided by the DCM

288 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.4.1 Dcm_StartOfReception

[SWS_Dcm_00094] Definition of callback function Dcm_StartOfReception d

Service Name Dcm_StartOfReception
Syntax BufReq_ReturnType Dcm_StartOfReception (
PduIdType id,
const PduInfoType* info,
PduLengthType TpSduLength,
PduLengthType* bufferSizePtr
)
Service ID [hex] 0x46
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) id Identification of the I-PDU.
info Pointer to a PduInfoType structure containing the payload data
(without protocol information) and payload length of the first
frame or single frame of a transport protocol I-PDU reception, and
the MetaData related to this PDU. If neither first/single frame data
nor MetaData are available, this parameter is set to NULL_PTR.
TpSduLength Total length of the N-SDU to be received.
Parameters (inout) None
Parameters (out) bufferSizePtr Available receive buffer in the receiving module. This parameter
will be used to compute the Block Size (BS) in the transport
protocol module.
Return value BufReq_ReturnType BUFREQ_OK: Connection has been accepted. bufferSizePtr
indicates the available receive buffer; reception is continued. If no
buffer of the requested size is available, a receive buffer size of 0
shall be indicated by bufferSizePtr.
BUFREQ_E_NOT_OK: Connection has been rejected; reception is
aborted. bufferSizePtr remains unchanged.
BUFREQ_E_OVFL: No buffer of the required length can be
provided; reception is aborted. bufferSizePtr remains unchanged.
Description This function is called at the start of receiving an N-SDU. The N-SDU might be fragmented into
multiple N-PDUs (FF with one or more following CFs) or might consist of a single N-PDU (SF).
If the service is successful and BUFREQ_OK is returned, the service provides the currently
available maximum buffer size. This function might be called in interrupt context.
Available via Dcm.h

By the function Dcm_StartOfReception the receiver (e.g. DCM) is also informed

implicitly about a first frame reception or a single frame reception. If the function Dcm_-
StartOfReception returns a return value not equal to BUFREQ_OK, the values of
the out parameters are not specified and should not be evaluated by the caller.

289 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.4.2 Dcm_CopyRxData

[SWS_Dcm_00556] Definition of API function Dcm_CopyRxData d

Service Name Dcm_CopyRxData
Syntax BufReq_ReturnType Dcm_CopyRxData (
PduIdType id,
const PduInfoType* info,
PduLengthType* bufferSizePtr
)
Service ID [hex] 0x44
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) id Identification of the received I-PDU.
info Provides the source buffer (SduDataPtr) and the number of bytes
to be copied (SduLength). An SduLength of 0 can be used to
query the current amount of available buffer in the upper layer
module. In this case, the SduDataPtr may be a NULL_PTR.
Parameters (inout) None
Parameters (out) bufferSizePtr Available receive buffer after data has been copied.
Return value BufReq_ReturnType BUFREQ_OK: Data copied successfully
BUFREQ_E_NOT_OK: Data was not copied because an error
occurred.
Description This function is called to provide the received data of an I-PDU segment (N-PDU) to the upper
layer. Each call to this function provides the next part of the I-PDU data. The size of the
remaining buffer is written to the position indicated by bufferSizePtr. This function might be
called in interrupt context.
Available via Dcm.h

8.4.3 Dcm_TpRxIndication

[SWS_Dcm_00093] Definition of API function Dcm_TpRxIndication d

Service Name Dcm_TpRxIndication
Syntax void Dcm_TpRxIndication (
PduIdType id,
Std_ReturnType result
)
Service ID [hex] 0x45
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) id Identification of the received I-PDU.
result Result of the reception.
Parameters (inout) None
Parameters (out) None
Return value None
5

290 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Description Called after an I-PDU has been received via the TP API, the result indicates whether the
transmission was successful or not. This function might be called in interrupt context.
Available via Dcm.h

8.4.4 Dcm_CopyTxData

[SWS_Dcm_00092] Definition of API function Dcm_CopyTxData d

Service Name Dcm_CopyTxData
Syntax BufReq_ReturnType Dcm_CopyTxData (
PduIdType id,
const PduInfoType* info,
const RetryInfoType* retry,
PduLengthType* availableDataPtr
)
Service ID [hex] 0x43
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) id Identification of the transmitted I-PDU.
info Provides the destination buffer (SduDataPtr) and the number of
bytes to be copied (SduLength). If not enough transmit data is
available, no data is copied by the upper layer module and
BUFREQ_E_BUSY is returned. The lower layer module may
retry the call. An SduLength of 0 can be used to indicate state
changes in the retry parameter or to query the current amount of
available data in the upper layer module. In this case, the Sdu
DataPtr may be a NULL_PTR.
retry This parameter is used to acknowledge transmitted data or to
retransmit data after transmission problems.
If the retry parameter is a NULL_PTR, it indicates that the
transmit data can be removed from the buffer immediately after it
has been copied. Otherwise, the retry parameter must point to a
valid RetryInfoType element.
If TpDataState indicates TP_CONFPENDING, the previously
copied data must remain in the TP buffer to be available for error
recovery. TP_DATACONF indicates that all data that has been
copied before this call is confirmed and can be removed from the
TP buffer. Data copied by this API call is excluded and will be
confirmed later. TP_DATARETRY indicates that this API call shall
copy previously copied data in order to recover from an error. In
this case TxTpDataCnt specifies the offset in bytes from the
current data copy position.
Parameters (inout) None
Parameters (out) availableDataPtr Indicates the remaining number of bytes that are available in the
upper layer module’s Tx buffer. availableDataPtr can be used by
TP modules that support dynamic payload lengths (e.g. FrIsoTp)
to determine the size of the following CFs.
5

291 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Return value BufReq_ReturnType BUFREQ_OK: Data has been copied to the transmit buffer
completely as requested.
BUFREQ_E_BUSY: Request could not be fulfilled, because the
required amount of Tx data is not available. The lower layer
module may retry this call later on. No data has been copied.
BUFREQ_E_NOT_OK: Data has not been copied. Request failed.
Description This function is called to acquire the transmit data of an I-PDU segment (N-PDU). Each call to
this function provides the next part of the I-PDU data unless retry->TpDataState is TP_
DATARETRY. In this case the function restarts to copy the data beginning at the offset from the
current position indicated by retry->TxTpDataCnt. The size of the remaining data is written to
the position indicated by availableDataPtr. This function might be called in interrupt context.
Available via Dcm.h

8.4.5 Dcm_TpTxConfirmation

[SWS_Dcm_00351] Definition of API function Dcm_TpTxConfirmation d

Service Name Dcm_TpTxConfirmation
Syntax void Dcm_TpTxConfirmation (
PduIdType id,
Std_ReturnType result
)
Service ID [hex] 0x48
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) id Identification of the transmitted I-PDU.
result Result of the transmission of the I-PDU.
Parameters (inout) None
Parameters (out) None
Return value None
Description This function is called after the I-PDU has been transmitted on its network, the result indicates
whether the transmission was successful or not. This function might be called in interrupt
context.
Available via Dcm.h

292 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.4.6 Dcm_TxConfirmation

[SWS_Dcm_01092] Definition of API function Dcm_TxConfirmation d

Service Name Dcm_TxConfirmation
Syntax void Dcm_TxConfirmation (
PduIdType TxPduId,
Std_ReturnType result
)
Service ID [hex] 0x40
Sync/Async Synchronous
Reentrancy Reentrant for different PduIds. Non reentrant for the same PduId.
Parameters (in) TxPduId ID of the PDU that has been transmitted.
result E_OK: The PDU was transmitted. E_NOT_OK: Transmission of
the PDU failed.
Parameters (inout) None
Parameters (out) None
Return value None
Description The lower layer communication interface module confirms the transmission of a PDU, or the
failure to transmit a PDU. This function might be called in interrupt context.
Available via Dcm.h

8.4.7 Dcm_ComM_NoComModeEntered

[SWS_Dcm_00356] Definition of callback function Dcm_ComM_NoComModeEn-

tered d
Service Name Dcm_ComM_NoComModeEntered
Syntax void Dcm_ComM_NoComModeEntered (
uint8 NetworkId
)
Service ID [hex] 0x21
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) NetworkId Identifier of the network concerned by the mode change
Parameters (inout) None
Parameters (out) None
Return value None
Description This call informs the Dcm module about a ComM mode change to COMM_NO_
COMMUNICATION.
Available via Dcm_ComM.h

293 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.4.8 Dcm_ComM_SilentComModeEntered

[SWS_Dcm_00358] Definition of callback function Dcm_ComM_SilentComMode

Entered d
Service Name Dcm_ComM_SilentComModeEntered
Syntax void Dcm_ComM_SilentComModeEntered (
uint8 NetworkId
)
Service ID [hex] 0x22
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) NetworkId Identifier of the network concerned by the mode change
Parameters (inout) None
Parameters (out) None
Return value None
Description This call informs the Dcm module about a ComM mode change to COMM_SILENT_
COMMUNICATION.
Available via Dcm_ComM.h

8.4.9 Dcm_ComM_FullComModeEntered

[SWS_Dcm_00360] Definition of callback function Dcm_ComM_FullComMode

Entered d
Service Name Dcm_ComM_FullComModeEntered
Syntax void Dcm_ComM_FullComModeEntered (
uint8 NetworkId
)
Service ID [hex] 0x23
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) NetworkId Identifier of the network concerned by the mode change
Parameters (inout) None
Parameters (out) None
Return value None
Description This call informs the Dcm module about a ComM mode change to COMM_FULL_
COMMUNICATION.
Available via Dcm_ComM.h

294 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.4.10 Dcm_CsmAsyncJobFinished

[SWS_Dcm_91076] Definition of configurable interface Dcm_CsmAsyncJobFin-

ished d
Service Name Dcm_CsmAsyncJobFinished
Syntax void Dcm_CsmAsyncJobFinished (
uint32 jobId,
Crypto_ResultType result
)
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) jobId JobId provided by the Csm, indicating the job that has finished.
result Return value of the asynchronous job
Parameters (inout) None
Parameters (out) None
Return value None
Description Can be called from Csm upon finishing an asynchronous job processing. The integrator will
configure this name as callback function within the Csm ECUC configuration for asynchronous
jobs. Only one such callback is available, the Dcm detects the job that has finished by
evaluating the job parameter. API availability: This API will be available only if ({ecuc(Dcm/Dcm
Dsp/DcmDspAuthentication/DcmDspAuthenticationConnection} != null).
Available via

8.4.11 Dcm_KeyMAsyncCertificateVerifyFinished

[SWS_Dcm_91077] Definition of configurable interface Dcm_KeyMAsyncCertifi-

cateVerifyFinished d
Service Name Dcm_KeyMAsyncCertificateVerifyFinished
Syntax Std_ReturnType Dcm_KeyMAsyncCertificateVerifyFinished (
KeyM_CertificateIdType CertID,
KeyM_CertificateStatusType Result
)
Sync/Async Synchronous
Reentrancy Reentrant
Parameters (in) CertID Certificate identifier that has finished the verification
Result Return value of the asynchronous job
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: this value is always returned
5

295 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Description Can be called from Key upon finishing an asynchronous certificate verification. The integrator
will configure this name as callback function within the KeyM ECUC configuration for
asynchronous jobs. Only one such callback is available, the Dcm detects the certificate that has
finished by evaluating the certId parameter. API availability: This API will be available only if
({ecuc(Dcm/DcmDsp/DcmDspAuthentication/DcmDspAuthenticationConnection} != null).
Available via

8.5 Callout Definitions

Callouts are pieces of code that have to be added to the Dcm during ECU integra-
tion. The content of most callouts is hand-written code, for some callouts the Dcm
configuration tool shall generate a default implementation that is manually edited by
the integrator. Conceptually, these callouts belong to the ECU Firmware.
Since callouts are no services of the Dcm they do not have an assigned Service ID.
Note: The Autosar architecture doesn’t provide the possibility to access the ECU mem-
ory using a physical address. This realized using BlockId which identified a memory
block.
According to that, the Dcm is not able to fully support the implementation of ISO14229-
1 [1]services which request a physical memory access. Therefore, the Dcm define
callout to realize this kind of memory access. This callout implementation could be
simply realized by defining a mapping between the BlockId and the physical memory
address.

8.5.1 Dcm_ReadMemory

[SWS_Dcm_00539] Definition of configurable interface Dcm_ReadMemory d

Service Name Dcm_ReadMemory
Syntax Dcm_ReturnReadMemoryType Dcm_ReadMemory (
Dcm_OpStatusType OpStatus,
uint8 MemoryIdentifier,
uint32 MemoryAddress,
uint32 MemorySize,
uint8* MemoryData,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x7c
Sync/Async Asynchronous
Reentrancy Non Reentrant
5

296 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK
MemoryIdentifier Identifier of the Memory Block (e.g. used if memory section
distinguishing is needed) Note: If it’s not used this parameter
shall be set to 0.
MemoryAddress Starting address of server memory from which data is to be
retrieved.
MemorySize Number of bytes in the MemoryData
Parameters (inout) None
Parameters (out) MemoryData Data read (Points to the diagnostic buffer in DCM)
ErrorCode If the operation Dcm_ReadMemory returns value DCM_READ_
FAILED, the Dcm module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Dcm_ReturnRead DCM_READ_OK: read was successful
MemoryType DCM_READ_FAILED: read was not successful
DCM_READ_PENDING: read is not yet finished
DCM_READ_FORCE_RCRRP: reading is pending, the Response
pending transmission starts immediately
Description The Dcm_ReadMemory callout is used to request memory data identified by the parameter
memoryAddress and memorySize from the UDS request message. This service is needed for
the implementation of UDS services:
• ReadMemoryByAddress
• RequestUpload
• ReadDataByIdentifier (in case of Dynamical DID defined by memory address)
• TransferData
Available via Dcm_Externals.h

8.5.2 Dcm_WriteMemory

[SWS_Dcm_00540] Definition of configurable interface Dcm_WriteMemory d

Service Name Dcm_WriteMemory
Syntax Dcm_ReturnWriteMemoryType Dcm_WriteMemory (
Dcm_OpStatusType OpStatus,
uint8 MemoryIdentifier,
uint32 MemoryAddress,
uint32 MemorySize,
const uint8* MemoryData,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x27
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK
MemoryIdentifier Identifier of the Memory Block (e.g. used by WriteDataByIdentifier
service). Note: If it’s not used this parameter shall be set to 0.
5

297 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
MemoryAddress Starting address of server memory in which data is to be copied.
Note: If it’s not used (e.g. if the data is compressed) this
parameter shall be set to 0.
MemorySize Number of bytes in MemoryData
MemoryData Data to write (Points to the diagnostic buffer in DCM)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Dcm_WriteMemory returns value DCM_WRITE_
FAILED, the Dcm module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Dcm_ReturnWrite DCM_WRITE_OK: write was successful
MemoryType DCM_WRITE_FAILED: write was not successful
DCM_WRITE_PENDING: write is not yet finished
DCM_WRITE_FORCE_RCRRP: writing is pending, the Response
pending transmission starts immediately
Description The Dcm_WriteMemory callout is used to write memory data identified by the parameter
memoryAddress and memorySize. This service is needed for the implementation of UDS
services :
• WriteMemoryByAddress
• RequestDownload
• TransferData
Available via Dcm_Externals.h

Note : The callout implementation shall take care of the following points :
• When writing data in NVRAM, take care to keep the consistency with data in the
mirror RAM
• When writing data in memory, take care that a SW-C won’t overwrite the data.
Maybe the SW-C should be informed of this writing

8.5.3 Dcm_SetProgConditions

[SWS_Dcm_00543] Definition of configurable interface Dcm_SetProgConditions

d
Service Name Dcm_SetProgConditions
Syntax Std_ReturnType Dcm_SetProgConditions (
Dcm_OpStatusType OpStatus,
const Dcm_ProgConditionsType* ProgConditions
)
Service ID [hex] 0x61
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_
FORCE_RCRRP_OK
ProgConditions Conditions on which the jump to bootloader has been requested
5

298 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Conditions have correctly been set
E_NOT_OK: Conditions cannot be set
DCM_E_PENDING: Conditions set is in progress, a further call to
this API is needed to end the setting
DCM_E_FORCE_RCRRP: Application requests the transmission of
a response Response Pending (NRC 0x78)
Description The Dcm_SetProgConditions callout allows the integrator to store relevant information prior to
jumping to bootloader / jump due to ECUReset request. The context parameter are defined in
Dcm_ProgConditionsType.
Available via Dcm_Externals.h

Note: In case the SecurityAccess AttemptCounter needs to be shared between appli-

cation and bootloader in addition to the ProgConditionStructure the current value can
be retrieved via the API Xxx_GetSecurityAttemptCounter (see chapter 7.4.4 In-
teraction)

8.5.4 Dcm_GetProgConditions

[SWS_Dcm_00544] Definition of configurable interface Dcm_GetProgConditions

d
Service Name Dcm_GetProgConditions
Syntax Dcm_EcuStartModeType Dcm_GetProgConditions (
Dcm_ProgConditionsType * ProgConditions
)
Service ID [hex] 0x62
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) ProgConditions Conditions on which the jump from the bootloader has been
requested
Return value Dcm_EcuStartModeType –
Description The Dcm_GetProgConditions callout is called upon Dcm initialization and allows to determine if
a response ($50 or $51) has to be sent. The context parameters are defined in Dcm_Prog
ConditionsType.
Available via Dcm_Externals.h

299 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.5.5 Dcm_ProcessRequestAddFile

[SWS_Dcm_91078] Definition of configurable interface Dcm_ProcessRequest

AddFile d
Service Name Dcm_ProcessRequestAddFile
Syntax Std_ReturnType Dcm_ProcessRequestAddFile (
Dcm_OpStatusType OpStatus,
uint16 filePathAndNameLength,
const uint8* filePathAndName,
uint8 dataFormatIdentifier,
uint64 fileSizeUncompressed,
uint64 fileSizeCompressed,
uint64* maxNumberOfBlockLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x72
Sync/Async Asynchronous
Reentrancy Non Reentrant

Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
filePathAndNameLength Defines the length in bytes for the parameter filePathAndName.
filePathAndName Defines the file system location of the server where the file which
shall be added, deleted, replaced or read from depending on the
parameter modeOfOperation parameter. In addition this
parameter includes the file name of the file which shall be added,
deleted, replaced or read as part of the file path.
dataFormatIdentifier This data-parameter is a one byte value with each nibble
encoded separately. The high nibble specifies the "compression
Method", and the low nibble specifies the "encryptingMethod".
The value 0x00 specifies that neither compressionMethod nor
encryptingMethod is used. Values other than 0x00 are vehicle
manufacturer specific.
fileSizeUncompressed Defines the size of the uncompressed file to be download in
bytes.
fileSizeCompressed Defines the size of the compressed file to be downloaded in
bytes.
Parameters (inout) None
Parameters (out) maxNumberOfBlock Max number of bytes to be included in each TransferData request
Length excluding the SID and the blockSequenceCounter.
ErrorCode If the operation Dcm_ProcessRequestAddFile returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission of a
response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function to start a RequestFileTransfer process with mode
OfOperation equal to 0x01 (AddFile).
Available via Dcm_Externals.h

300 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.5.6 Dcm_ProcessRequestDeleteFile

[SWS_Dcm_91079] Definition of configurable interface Dcm_ProcessRequest

DeleteFile d
Service Name Dcm_ProcessRequestDeleteFile
Syntax Std_ReturnType Dcm_ProcessRequestDeleteFile (
Dcm_OpStatusType OpStatus,
uint16 filePathAndNameLength,
const uint8* filePathAndName,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x73
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
filePathAndNameLength Defines the length in bytes for the parameter filePathAndName.
filePathAndName Defines the file system location of the server where the file which
shall be added, deleted, replaced or read from depending on the
parameter modeOfOperation parameter. In addition this
parameter includes the file name of the file which shall be added,
deleted, replaced or read as part of the file path.
Parameters (inout) None
Parameters (out) ErrorCode If the operation Dcm_ProcessRequestDeleteFile returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission of a
response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function to start a RequestFileTransfer process with mode
OfOperation equal to 0x02 (DeleteFile).
Available via Dcm_Externals.h

301 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.5.7 Dcm_ProcessRequestReplaceFile

[SWS_Dcm_91080] Definition of configurable interface Dcm_ProcessRequestRe-

placeFile d
Service Name Dcm_ProcessRequestReplaceFile
Syntax Std_ReturnType Dcm_ProcessRequestReplaceFile (
Dcm_OpStatusType OpStatus,
uint16 filePathAndNameLength,
const uint8* filePathAndName,
uint8 dataFormatIdentifier,
uint64 fileSizeUncompressed,
uint64 fileSizeCompressed,
uint64* maxNumberOfBlockLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x74
Sync/Async Asynchronous
Reentrancy Non Reentrant

Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
filePathAndNameLength Defines the length in bytes for the parameter filePathAndName.
filePathAndName Defines the file system location of the server where the file which
shall be added, deleted, replaced or read from depending on the
parameter modeOfOperation parameter. In addition this
parameter includes the file name of the file which shall be added,
deleted, replaced or read as part of the file path.
dataFormatIdentifier This data-parameter is a one byte value with each nibble
encoded separately. The high nibble specifies the "compression
Method", and the low nibble specifies the "encryptingMethod".
The value 0x00 specifies that neither compressionMethod nor
encryptingMethod is used. Values other than 0x00 are vehicle
manufacturer specific.
fileSizeUncompressed Defines the size of the uncompressed file to be download in
bytes.
fileSizeCompressed Defines the size of the compressed file to be downloaded in
bytes.
Parameters (inout) None
Parameters (out) maxNumberOfBlock Max number of bytes to be included in each TransferData request
Length excluding the SID and the blockSequenceCounter.
ErrorCode If the operation Dcm_ProcessRequestReplaceFile returns value
E_NOT_OK, the DCM module shall send a negative response
with NRC code equal to the parameter ErrorCode parameter
value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission of a
response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function to start a RequestFileTransfer process with mode
OfOperation equal to 0x03 (ReplaceFile).
Available via Dcm_Externals.h

302 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.5.8 Dcm_ProcessRequestReadFile

[SWS_Dcm_91081] Definition of configurable interface Dcm_ProcessRequest

ReadFile d
Service Name Dcm_ProcessRequestReadFile
Syntax Std_ReturnType Dcm_ProcessRequestReadFile (
Dcm_OpStatusType OpStatus,
uint16 filePathAndNameLength,
const uint8* filePathAndName,
uint8 dataFormatIdentifier,
uint64 fileSizeUncompressed,
uint64 fileSizeCompressed,
uint64* maxNumberOfBlockLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x75
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
filePathAndNameLength Defines the length in bytes for the parameter filePathAndName.
filePathAndName Defines the file system location of the server where the file which
shall be added, deleted, replaced or read from depending on the
parameter modeOfOperation parameter. In addition this
parameter includes the file name of the file which shall be added,
deleted, replaced or read as part of the file path.
dataFormatIdentifier This data-parameter is a one byte value with each nibble
encoded separately. The high nibble specifies the "compression
Method", and the low nibble specifies the "encryptingMethod".
The value 0x00 specifies that neither compressionMethod nor
encryptingMethod is used. Values other than 0x00 are vehicle
manufacturer specific.
Parameters (inout) None
Parameters (out) fileSizeUncompressed Defines the size of the uncompressed file to be uploaded in bytes.
fileSizeCompressed Defines the size of the compressed file to be uploaded in bytes.
maxNumberOfBlock Max number of bytes to be included in each TransferData
Length response excluding the SID and the blockSequenceCounter.
ErrorCode If the operation Dcm_ProcessRequestReadFile returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission of a
response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function to start a RequestFileTransfer process with mode
OfOperation equal to 0x04 (ReadFile).
Available via Dcm_Externals.h

303 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.5.9 Dcm_ProcessRequestReadDir

[SWS_Dcm_91082] Definition of configurable interface Dcm_ProcessRequest

ReadDir d
Service Name Dcm_ProcessRequestReadDir
Syntax Std_ReturnType Dcm_ProcessRequestReadDir (
Dcm_OpStatusType OpStatus,
uint16 filePathAndNameLength,
const uint8* filePathAndName,
uint64* dirInfoLength,
uint64* maxNumberOfBlockLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x76
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
filePathAndNameLength Defines the length in bytes for the parameter filePathAndName.
filePathAndName Defines the file system location of the server where the file which
shall be added, deleted, replaced or read from depending on the
parameter modeOfOperation parameter. In addition this
parameter includes the file name of the file which shall be added,
deleted, replaced or read as part of the file path.
Parameters (inout) None
Parameters (out) dirInfoLength Defines the size of directory information to be uploaded in bytes.
maxNumberOfBlock Max number of bytes to be included in each TransferData request
Length excluding the SID and the blockSequenceCounter.
ErrorCode If the operation Dcm_ProcessRequestReadDir returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission of a
response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function to start a RequestFileTransfer process with mode
OfOperation equal to 0x05 (ReadDir).
Available via Dcm_Externals.h

304 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.5.10 Dcm_WriteFile

[SWS_Dcm_91083] Definition of configurable interface Dcm_WriteFile d

Service Name Dcm_WriteFile
Syntax Std_ReturnType Dcm_WriteFile (
Dcm_OpStatusType OpStatus,
uint64 DataLength,
uint8* Data,
Dcm_NegativeResponseCodeType* ErrorCode
)
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
DataLength Defines the length in bytes for the parameter Data. The value will
not exceed, but might be less, compared to the value of max
NumberOfBlockLength return in Dcm_ProcessRequestFile
Transfer.
Data Pointer to the data to be written.
Parameters (inout) None
Parameters (out) ErrorCode If the operation Dcm_WriteFile returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission of a
response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function when data is received using UDS service Transfer
Data if there’s an ongoing RequestFileTransfer process started with 0x01 (AddFile) or 0x03
(ReplaceFile).
Available via Dcm_Externals.h

8.5.11 Dcm_ReadFileOrDir

[SWS_Dcm_91085] Definition of configurable interface Dcm_ReadFileOrDir d

Service Name Dcm_ReadFileOrDir
Syntax Std_ReturnType Dcm_ReadFileOrDir (
Dcm_OpStatusType OpStatus,
uint64* DataLength,
uint8* Data,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x78
Sync/Async Asynchronous
5

305 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL: All In-parameters are valid. DCM_PENDING: All
In-parameters are set to 0x00. DCM_CANCEL: All In-parameters
are set to 0x00. DCM_FORCE_RCRRP_OK: All In-parameters
are set to 0x00.
Data Pointer to the data to be written.
Parameters (inout) DataLength As in, the parameter defines the maximum block length to be
used, i.e. the value of maxNumberOfBlockLength sent to the
client in the response of RequestFileTransfer.
As out, the parameter defines the actual length in bytes for the
parameter Data. The value shall not exceed, but might be less,
the value provided as in parameter.
Parameters (out) ErrorCode If the operation Dcm_ReadFileOrDir returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application request the transmission of a
response Response Pending (NRC 0x78)
Description Callout function. DCM shall call this function when data shall be sent as a response to UDS
service TransferData if there’s an ongoing RequestFileTransfer process started with 0x04
(ReadFile) or 0x05 (ReadDir).
Available via Dcm_Externals.h

8.5.12 UploadDownloadServices

From the point of view of the DCM, the operations has the following signatures:

8.5.12.1 ProcessRequestDownload

[SWS_Dcm_00754] Definition of configurable interface Dcm_ProcessRequest

Download d
Service Name Dcm_ProcessRequestDownload
Syntax Std_ReturnType Dcm_ProcessRequestDownload (
Dcm_OpStatusType OpStatus,
uint8 DataFormatIdentifier,
uint8 MemoryIdentifier,
uint32 MemoryAddress,
uint32 MemorySize,
uint32* BlockLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x30
Sync/Async Asynchronous
5

306 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL
DataFormatIdentifier Bit 7 - 4: Compression Method
• 0x0: not compressed
• 0x1..F: vehicle-manufacturer-specific
Bit 3 - 0: Encrypting method
• 0x0: not encrypted
• 0x1..F: vehicle-manufacturer-specific
MemoryIdentifier Identifier of the Memory Block, if the parameter is not used it shall
be set to 0.
MemoryAddress Starting address of server memory to which data is to be written
MemorySize Uncompressed memory size in bytes
Parameters (inout) BlockLength Max. Number of bytes for one Dcm_WriteMemory
Parameters (out) ErrorCode If the operation Dcm_ProcessRequestDownload returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
Description Callout function. DCM shall call this callout function to start a download process. This service is
needed for the implementation of UDS service RequestDownload.
Available via Dcm_Externals.h

8.5.12.2 ProcessRequestTransferExit

[SWS_Dcm_00755] Definition of configurable interface Dcm_ProcessRequest

TransferExit d
Service Name Dcm_ProcessRequestTransferExit
Syntax Std_ReturnType Dcm_ProcessRequestTransferExit (
Dcm_OpStatusType OpStatus,
const uint8* transferRequestParameterRecord,
uint32 transferRequestParameterRecordSize,
uint8* transferResponseParameterRecord,
uint32* transferResponseParameterRecordSize,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x32
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL
transferRequest Pointer to vehicle manufacturer specific transferRequest
ParameterRecord ParameterRecord
5

307 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
transferRequest Length of ParameterRecord in bytes
ParameterRecordSize
Parameters (inout) transferResponse When the function is called this parameter contains the maximum
ParameterRecordSize number of data bytes that can be written to the buffer. The
function returns the actual number of written data bytes in
transferResponseParameterRecord.
Parameters (out) transferResponse Pointer to vehicle manufacturer specific transferResponse
ParameterRecord ParameterRecord
ErrorCode see below
Return value Std_ReturnType E_OK: Transfer was successful
E_NOT_OK: Transfer was not successful or the response buffer is
too small
DCM_E_PENDING: Transfer is not yet finished
Description Callout function. DCM shall call this callout function to terminate a download or upload process.
This callout is needed for the implementation of UDS service RequestTransferExit.
Available via Dcm_Externals.h

8.5.12.3 ProcessRequestUpload

[SWS_Dcm_00756] Definition of configurable interface Dcm_ProcessRequestUp-

load d
Service Name Dcm_ProcessRequestUpload
Syntax Std_ReturnType Dcm_ProcessRequestUpload (
Dcm_OpStatusType OpStatus,
uint8 DataFormatIdentifier,
uint8 MemoryIdentifier,
uint32 MemoryAddress,
uint32 MemorySize,
uint32* BlockLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x31
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK
DataFormatIdentifier Bit 7 - 4: Compression Method
• 0x0: not compressed
• 0x1..F: vehicle-manufacturer-specific
Bit 3 - 0: Encrypting method
• 0x0: not encrypted
• 0x1..F: vehicle-manufacturer-specific
MemoryIdentifier Identifier of the Memory Block, if the parameter is not used it shall
be set to 0.
5

308 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
MemoryAddress Starting address of server memory from which data are to be
copied
MemorySize Uncompressed memory size in bytes
Parameters (inout) BlockLength Max. Number of bytes for one Dcm_ReadMemory
Parameters (out) ErrorCode If the operation Dcm_ProcessRequestUpload returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
Description Callout function. DCM shall call this callout function to start an upload process. This service is
needed for the implementation of UDS service RequestUpload.
Available via Dcm_Externals.h

8.5.12.4 ProcessTransferDataRead

[SWS_Dcm_91070] Definition of configurable interface Dcm_ProcessTransfer

DataRead d
Service Name Dcm_ProcessTransferDataRead
Syntax Dcm_ReturnReadMemoryType Dcm_ProcessTransferDataRead (
Dcm_OpStatusType OpStatus,
uint8 MemoryIdentifier,
uint32 MemoryAddress,
uint32 MemorySize,
Dcm_RequestDataArrayType MemoryData,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x26
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK
MemoryIdentifier Identifier of the Memory Block (e.g. used if memory section
distinguishing is needed) Note: If it’s not used this parameter
shall be set to 0.
MemoryAddress Starting address of server memory from which data is to be
retrieved.
MemorySize Number of bytes in the MemoryData
Parameters (inout) None
Parameters (out) MemoryData Data read (Points to the diagnostic buffer in DCM)
ErrorCode If the operation Dcm_ReadMemory returns value DCM_READ_
FAILED, the Dcm module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
5

309 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Return value Dcm_ReturnRead DCM_READ_OK: read was successful
MemoryType DCM_READ_FAILED: read was not successful
DCM_READ_PENDING: read is not yet finished
DCM_READ_FORCE_RCRRP: reading is pending, the Response
pending transmission starts immediately
Description The ProcessTransferDataRead callout is used to request memory data identified by the
parameter memoryAddress and memorySize from the UDS request message. This service is
needed for the implementation of UDS services:
• ReadMemoryByAddress
• RequestUpload
• ReadDataByIdentifier (in case of Dynamical DID defined by memory address)
• TransferData
Available via Dcm_Externals.h

8.5.12.5 ProcessTransferDataWrite

[SWS_Dcm_91071] Definition of configurable interface Dcm_ProcessTransfer

DataWrite d
Service Name Dcm_ProcessTransferDataWrite
Syntax Dcm_ReturnWriteMemoryType Dcm_ProcessTransferDataWrite (
Dcm_OpStatusType OpStatus,
uint8 MemoryIdentifier,
uint32 MemoryAddress,
uint32 MemorySize,
const Dcm_RequestDataArrayType MemoryData,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x7b
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK
MemoryIdentifier Identifier of the Memory Block (e.g. used by WriteDataByIdentifier
service). Note: If it’s not used this parameter shall be set to 0.
MemoryAddress Starting address of server memory in which data is to be copied.
Note: If it’s not used (e.g. if the data is compressed) this
parameter shall be set to 0.
MemorySize Number of bytes in MemoryData
MemoryData Data to write (Points to the diagnostic buffer in DCM)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Dcm_WriteMemory returns value DCM_WRITE_
FAILED, the Dcm module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
5

310 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Return value Dcm_ReturnWrite DCM_WRITE_OK: write was successful
MemoryType DCM_WRITE_FAILED: write was not successful
DCM_WRITE_PENDING: write is not yet finished
DCM_WRITE_FORCE_RCRRP: writing is pending, the Response
pending transmission starts immediately
Description The ProcessTransferDataWrite callout is used to write memory data identified by the parameter
memoryAddress and memorySize. This service is needed for the implementation of UDS
services :
• WriteMemoryByAddress
• RequestDownload
• TransferData
Available via Dcm_Externals.h

8.6 Scheduled functions

These functions are directly called by Basic Software Scheduler. The following func-
tions shall have no return value and no parameter. All functions shall be non reentrant.

8.6.1 Dcm_MainFunction

[SWS_Dcm_00053] Definition of scheduled function Dcm_MainFunction

Upstream requirements: SRS_BSW_00424, SRS_BSW_00373

d
Service Name Dcm_MainFunction
Syntax void Dcm_MainFunction (
void
)
Service ID [hex] 0x25
Description This service is used for processing the tasks of the main loop.
Available via SchM_Dcm.h

8.7 Expected interfaces

In this chapter all interfaces required from other modules are listed.

311 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.7.1 Mandatory interfaces

This section defines all interfaces, which are required to fulfill the core functionality of
the module.

[SWS_Dcm_91001] Definition of mandatory interfaces required by module Dcm

d
API Function Header File Description
ComM_DCM_ActiveDiagnostic ComM_Dcm.h Indication of active diagnostic by the DCM.
ComM_DCM_InactiveDiagnostic ComM_Dcm.h Indication of inactive diagnostic by the DCM.
PduR_DcmTransmit PduR_Dcm.h Requests transmission of a PDU.

8.7.2 Optional interfaces

This section defines all interfaces, which are required to fulfill an optional functionality
of the module.

[SWS_Dcm_91002] Definition of optional interfaces requested by module Dcm d

API Function Header File Description
BndM_GetBlockPtr_<Block BndM_Externals.h –
Id.Shortname>
BndM_WriteBlock_<Block BndM_Externals.h Will persist the data in flash, that it can later directly
Id.Shortname> accessed via BndM_GetBlockPtr API. The writing
take a while and is finished after the successful
callback xxx_BndMWriteBlockFinish
BndM_WriteCancel BndM.h Cancels the writing
BndM_WriteFinalize BndM.h Will trigger the finalization of writing phase. The
finish of asynchronous processing will trigger the
callback xxx_BndMWriteFinalizeFinish including the
result of this operation.
BndM_WriteStart BndM.h Will trigger the start of writing phase. The finish of
asynchronous processing will trigger the callback
xxx_BndMWriteStartFinish including the result of
this operation
BswM_Dcm_ApplicationUpdated BswM_Dcm.h This function is called by the DCM in order to report
an updated application.
BswM_Dcm_CommunicationMode BswM_Dcm.h Function called by DCM to inform the BswM about
_CurrentState the current state of the communication mode.
Dem_ClearDTC Dem.h Clears single DTCs, as well as groups of DTCs.
5

312 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
API Function Header File Description
Dem_DcmGetAvailableOBDMIDs Dem_Dcm.h Reports the value of a requested
"availability-OBDMID" to the DCM upon a Service
$06 request. Derived from that the tester displays
the supported tests a mechanic can select from. API
is needed in OBD-relevant ECUs only.
API Availability: This API will be available only if
({ecuc(Dem/DemGeneral.DemOBDSupport)} !=
DEM_OBD_NO_OBD_SUPPORT)
Dem_DcmGetDTCOfOBDFreeze Dem_Dcm.h Gets DTC by freeze frame record number. API is
Frame needed in OBD-relevant ECUs only.
API Availability: This API will be available only if
({ecuc(Dem/DemGeneral.DemOBDSupport)} !=
DEM_OBD_NO_OBD_SUPPORT)
Dem_DcmGetDTRData Dem_Dcm.h Reports a DTR data along with TID-value, UaSID,
test result with lower and upper limit. API is needed
in OBD-relevant ECUs only.
API Availability: This API will be available only if
({ecuc(Dem/DemGeneral.DemOBDSupport)} !=
DEM_OBD_NO_OBD_SUPPORT)
Dem_DcmGetNumTIDsOfOBDMID Dem_Dcm.h Gets the number of TIDs per (functional) OBDMID.
This can be used by the DCM to iteratively request
for OBD/TID result data within a loop from
0....numberOfTIDs-1 API is needed in OBD-relevant
ECUs only.
API Availability: This API will be available only if
({ecuc(Dem/DemGeneral.DemOBDSupport)} !=
DEM_OBD_NO_OBD_SUPPORT)
Dem_DcmReadDataOfOBDFreeze Dem_Dcm.h Gets data element per PID and index of the most
Frame important freeze frame being selected for the output
of service $02. The function stores the data in the
provided DestBuffer. API is needed in OBD-relevant
ECUs only.
API Availability: This API will be available only if
({ecuc(Dem/DemGeneral.DemOBDSupport)} !=
DEM_OBD_NO_OBD_SUPPORT)
Dem_DisableDTCRecordUpdate Dem.h Disables the event memory update of a specific
DTC (only one at one time).
Dem_DisableDTCSetting Dem.h Disables the DTC setting for all DTCs assigned to
the DemEventMemorySet of the addressed client.
Dem_EnableDTCRecordUpdate Dem.h Enables the event memory update of the DTC
disabled by Dem_DisableDTCRecordUpdate()
before.
Note: As the call to Dem_EnableDTCRecordUpdate
is the last action in the sequence of disabling/
enabling a DTC, the caller is not interested in the
return value. Therefore E_OK should be returned
even if the DTC is enabled asynchronously.
Dem_EnableDTCSetting Dem.h (Re)-Enables the DTC setting for all DTCs assigned
to the DemEventMemorySet of the addressed client.
Dem_GetDTCByOccurrenceTime Dem.h Gets the DTC by occurrence time. There is no
explicit parameter for the DTC-origin as the origin
always is DEM_DTC_ORIGIN_PRIMARY_
MEMORY.
Dem_GetDTCSeverityAvailabilityMask Dem.h Gets the DTC Severity availability mask.
5

313 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
API Function Header File Description
Dem_GetDTCStatusAvailabilityMask Dem.h Gets the DTC Status availability mask of the
selected fault memory.
Dem_GetFunctionalUnitOfDTC Dem.h Gets the functional unit of the requested DTC.
Dem_GetNextExtendedDataRecord Dem.h Gets extended data record for the DTC selected by
Dem_SelectExtendedDataRecord. The function
stores the data in the provided DestBuffer.
Dem_GetNextFilteredDTC Dem.h Gets the next filtered DTC matching the filter
criteria. For UDS services, the interface has an
asynchronous behavior, because a large number of
DTCs has to be processed.
Dem_GetNextFilteredDTCAndFDC Dem.h Gets the next filtered DTC and its associated Fault
Detection Counter (FDC) matching the filter criteria.
The interface has an asynchronous behavior,
because a large number of DTCs has to be
processed and the FDC might be received
asynchronously from a SW-C, too.
Dem_GetNextFilteredDTCAndSeverity Dem.h Gets the next filtered DTC and its associated
Severity matching the filter criteria. The interface
has an asynchronous behavior, because a large
number of DTCs has to be processed.
Dem_GetNextFilteredRecord Dem.h Gets the next freeze frame record number and its
associated DTC stored in the event memory. The
interface has an asynchronous behavior, because
NvRAM access might be required.
Dem_GetNextFreezeFrameData Dem.h Gets freeze frame data by the DTC selected by
Dem_SelectFreezeFrameData. The function stores
the data in the provided DestBuffer.
Dem_GetNumberOfFilteredDTC Dem.h Gets the number of a filtered DTC.
Dem_GetNumberOfFreezeFrame Dem.h This function returns the number of all freeze frame
Records records currently stored in the primary event
memory
Dem_GetSeverityOfDTC Dem.h Gets the severity of the requested DTC. For large
configurations and DTC-calibration, the interface
behavior can be asynchronous (splitting the
DTC-search into segments).
Dem_GetSizeOfExtendedDataRecord Dem.h Gets the size of Extended Data Record by DTC
Selection selected by the call of Dem_SelectExtendedData
Record.
Dem_GetSizeOfFreezeFrameSelection Dem.h Gets the size of freeze frame data by DTC selected
by the call of Dem_SelectFreezeFrameData.
Dem_GetStatusOfDTC Dem.h Gets the status of a DTC. For large configurations
and DTC-calibration, the interface behavior can be
asynchronous (splitting the DTC-search into
segments). The DTCs of OBD Events Suppression
shall be reported as Dem_WRONG_DTC.
Dem_GetTranslationType Dem.h Gets the supported DTC formats of the ECU.The
supported formats are configured via DemTypeOf
DTCSupported.
5

314 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
API Function Header File Description
Dem_SetDTCFilter Dem.h Sets the DTC Filter.
The server shall perform a bit-wise logical AND-ing
operation between the parameter DTCStatusMask
and the current UDS status in the server. In addition
to the DTCStatusAvailabilityMask, the server shall
return all DTCs for which the result of the AND-ing
operation is non-zero [i.e. (statusOfDTC &
DTCStatusMask) != 0]. The server shall process
only the DTC Status bits that it is supporting. OBD
Events Suppression shall be ignored for this
computation. If no DTCs within the server match the
masking criteria specified in the client’s request, no
DTC or status information shall be provided
following the DTCStatusAvailabilityMask byte in the
positive response message
(((statusOfDTC & DTCStatusMask) != 0) &&
((severity & DTCSeverityMask) != 0)) == TRUE
Dem_SetFreezeFrameRecordFilter Dem.h Sets a freeze frame record filter.
Det_ReportError Det.h Service to report development errors.
IdsM_SetSecurityEvent (obsolete) IdsM.h This API is the application interface to report
security events to the IdsM.
Tags: atp.Status=obsolete
IdsM_SetSecurityEventWithContext IdsM.h This API is the application interface to report
Data (obsolete) security events with context data to the IdsM.
Tags: atp.Status=obsolete
IoHwAb_Dcm_<EcuSignalName> IoHwAb_Dcm.h This function provides control access to a certain
ECU Signal to the DCM module (<EcuSignalname>
is the symbolic name of an ECU Signal). The ECU
signal can be locked and unlocked by this function.
Locking ’freezes’ the ECU signal to the current
value, the configured default value or a value given
by the parameter ’signal’.
IoHwAb_Dcm_Read<EcuSignal IoHwAb_Dcm.h This function provides read access to a certain ECU
Name> Signal to the DCM module (<EcuSignalname> is the
symbolic name of an ECU Signal).
NvM_ReadBlock NvM.h Service to copy the data of the NV block to its
corresponding RAM block.
NvM_SetRamBlockStatus NvM.h Service for setting the RAM block status of a
permanent RAM block or the status of the explicit
synchronization of a NVRAM block.
NvM_WriteBlock NvM.h Service to copy the data of the RAM block to its
corresponding NV block.
PduR_DcmCancelReceive PduR_Dcm.h Requests cancellation of an ongoing reception of a
PDU in a lower layer transport protocol module.
PduR_DcmCancelTransmit PduR_Dcm.h Requests cancellation of an ongoing transmission of
a PDU in a lower layer communication module.
SchM_ActMainFunction_Dcm <none> Invokes the SchM_ActMainFunction function to
trigger the activation of a corresponding main
processing function.

Dem_DcmReadDataOfOBDFreezeFrame is only required when OBD Service $02 is

configured (see configuration parameter DcmDsdSidTabServiceId).

315 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.7.3 Configurable interfaces

This section defines the interfaces where the Dcm configuration defines the actual func-
tions that the Dcm will use. Depending on the configuration, an implementation of these
functions could be provided by other BSW-modules (typically the DEM) or by software-
components (through the RTE).

8.7.3.1 SecurityAccess

From the point of view of the DCM, the operation has the following signature:

8.7.3.1.1 GetSeed

If DcmDspSecurityADRSize is present:

[SWS_Dcm_01151] Definition of configurable interface Xxx_GetSeed d

Service Name Xxx_GetSeed
Syntax Std_ReturnType Xxx_GetSeed (
const uint8* SecurityAccessDataRecord,
Dcm_OpStatusType OpStatus,
uint8* Seed,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x8b
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) SecurityAccessData This data record contains additional data to calculate the seed
Record value; the size of this parameter is DcmDspSecurityADRSize
which is at least "1".
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) Seed Pointer for provided seed
ErrorCode If the operation Xxx_GetSeed returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description Request to application for asynchronous provision of seed value
Available via Dcm_Externals.h

If DcmDspSecurityADRSize is not present:

316 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_91003] Definition of configurable interface Xxx_GetSeed d

Service Name Xxx_GetSeed
Syntax Std_ReturnType Xxx_GetSeed (
Dcm_OpStatusType OpStatus,
uint8* Seed,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x8a
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) Seed Pointer for provided seed
ErrorCode If the operation Xxx_GetSeed returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description Request to application for asynchronous provision of seed value
Available via Dcm_Externals.h

8.7.3.1.2 CompareKey

[SWS_Dcm_91004] Definition of configurable interface Xxx_CompareKey d

Service Name Xxx_CompareKey
Syntax Std_ReturnType Xxx_CompareKey (
const uint8* Key,
Dcm_OpStatusType OpStatus,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x47
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) Key Key, which needs to be compared
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) ErrorCode NRC to be sent if E_NOT_OK is returned
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
DCM_E_COMPARE_KEY_FAILED: Key did not match.
5

317 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Description Request to application for asynchronous comparing key (DcmDspSecurityUsePort = USE_
ASYNCH_CLIENT_SERVER)
Available via Dcm_Externals.h

8.7.3.1.3 GetSecurityAttemptCounter

[SWS_Dcm_01152] Definition of configurable interface Xxx_GetSecurityAttempt

Counter d
Service Name Xxx_GetSecurityAttemptCounter
Syntax Std_ReturnType Xxx_GetSecurityAttemptCounter (
Dcm_OpStatusType OpStatus,
uint8* AttemptCounter
)
Service ID [hex] 0x59
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL
Parameters (inout) None
Parameters (out) AttemptCounter The attempt counter for this security level
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description Read the attempt counter for a specific security level from the application
Available via Dcm_Externals.h

Note: In case the Security Access AttemptCounter needs to be shared between ap-
plication and bootloader, the application needs to consider this in the API-call Xxx_-
GetSecurityAttemptCounter (see chapter 7.4.4 Interaction). Further this has also
impact on the security delay timer which needs to be considered.

318 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.7.3.1.4 SetSecurityAttemptCounter

[SWS_Dcm_01153] Definition of configurable interface Xxx_SetSecurityAttempt

Counter d
Service Name Xxx_SetSecurityAttemptCounter
Syntax Std_ReturnType Xxx_SetSecurityAttemptCounter (
Dcm_OpStatusType OpStatus,
uint8 AttemptCounter
)
Service ID [hex] 0x5a
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL
AttemptCounter The attempt counter for this security level
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description Set the attempt counter for a specific security level in the application
Available via Dcm_Externals.h

8.7.3.2 DataServices

From the point of view of the DCM, the operations have the following signatures:
Note : The OpStatus parameter exist only for asynchronous operations (if DcmD-
spDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or USE_DATA_-
ASYNCH_CLIENT_SERVER_ERROR or USE_DATA_ASYNCH_FNC or USE_DATA_-
ASYNCH_FNC_ERROR or USE_DATA_ASYNCH_FNC_PROXY). In case of synchronous
operations (DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or
USE_DATA_SYNCH_FNC or USE_DATA_ASYNCH_FNC_PROXY), the OpStatus parame-
ter does not exist.

8.7.3.2.1 ReadData

If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-

DATA_SYNCH_FNC, the following definition is used:

319 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00793] Definition of configurable interface Xxx_ReadData d

Service Name Xxx_ReadData
Syntax Std_ReturnType Xxx_ReadData (
uint8* Data
)
Service ID [hex] 0x34
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) Data Buffer where the requested data shall be copied to
Return value Std_ReturnType E_OK: this value is always returned.
Description This function requests to the application a data value of a DID/PID if DcmDspDataUsePort is
set to USE_DATA_SYNCH_CLIENT_SERVER.
Available via Dcm_Externals.h

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or

USE_DATA_ASYNCH_FNC, the following definition is used:

[SWS_Dcm_91006] Definition of configurable interface Xxx_ReadData d

Service Name Xxx_ReadData
Syntax Std_ReturnType Xxx_ReadData (
Dcm_OpStatusType OpStatus,
uint8* Data
)
Service ID [hex] 0x3b
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) Data Buffer where the requested data shall be copied to
Return value Std_ReturnType E_OK: Request was successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application a data value of a DID/PID if DcmDspDataUsePort is
set to USE_DATA_ASYNCH_CLIENT_SERVER.
Available via Dcm_Externals.h

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER_ERROR or

USE_DATA_ASYNCH_FNC_ERROR, the following definition is used:

320 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_91005] Definition of configurable interface Xxx_ReadData d

Service Name Xxx_ReadData
Syntax Std_ReturnType Xxx_ReadData (
Dcm_OpStatusType OpStatus,
uint8* Data,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x58
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) Data Buffer where the requested data shall be copied to
ErrorCode If the operation Xxx_ReadData returns value E_NOT_OK, the
Dcm module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application a data value of a DID/PID if DcmDspDataUsePort is
set to USE_DATA_ASYNCH_CLIENT_SERVER.
Available via Dcm_Externals.h

If DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY, the following defi-

nition is used:

[SWS_Dcm_91090] Definition of configurable interface Xxx_ReadData

Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_ReadData (draft)
Syntax Std_ReturnType Xxx_ReadData (
uint8* Data,
uint16 DataLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x68
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) DataLength Length in byte of the data to be read
Parameters (inout) None
Parameters (out) Data Buffer where the requested data shall be copied to
ErrorCode If the operation Xxx_ReadData returns value E_NOT_OK, the
Dcm module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
5

321 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application a data value of a DID/PID if DcmDspDataUsePort is
set to USE_DATA_SYNCH_FNC_PROXY.
Tags: atp.Status=draft
Available via Dcm_Externals.h

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY, the following def-

inition is used:

[SWS_Dcm_91091] Definition of configurable interface Xxx_ReadData

Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_ReadData (draft)
Syntax Std_ReturnType Xxx_ReadData (
Dcm_OpStatusType OpStatus,
uint8* Data,
uint16 DataLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x7d
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
DataLength Length in byte of the data to be read
Parameters (inout) None
Parameters (out) Data Buffer where the requested data shall be copied to
ErrorCode If the operation Xxx_ReadData returns value E_NOT_OK, the
Dcm module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application a data value of a DID/PID if DcmDspDataUsePort is
set to USE_DATA_ASYNCH_FNC_PROXY..
Tags: atp.Status=draft
Available via Dcm_Externals.h

8.7.3.2.2 WriteData

If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-

DATA_SYNCH_FNC, the following definition is used:

322 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

If DcmDspDataType is NOT set to UINT8_DYN, the following definition is used:

[SWS_Dcm_00794] Definition of configurable interface Xxx_WriteData d

Service Name Xxx_WriteData
Syntax Std_ReturnType Xxx_WriteData (
const uint8* Data,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x51
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) Data Buffer containing the data to be written
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_WriteData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests the application to write a data value of a DID.
Available via Dcm_Externals.h

If DcmDspDataType is set to UINT8_DYN, the following definition is used:

[SWS_Dcm_91007] Definition of configurable interface Xxx_WriteData d

Service Name Xxx_WriteData
Syntax Std_ReturnType Xxx_WriteData (
const uint8* Data,
uint16 DataLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x52
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) Data Buffer containing the data to be written
DataLength Length in byte of the data to be written
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_WriteData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests the application to write a data value of a DID.
Available via Dcm_Externals.h

323 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or

USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR
USE_DATA_ASYNCH_FNC_ERROR, the following definition is used:
If DcmDspDataType is NOT set to UINT8_DYN, the following definition is used:

[SWS_Dcm_91008] Definition of configurable interface Xxx_WriteData d

Service Name Xxx_WriteData
Syntax Std_ReturnType Xxx_WriteData (
const uint8* Data,
Dcm_OpStatusType OpStatus,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x35
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) Data Buffer containing the data to be written
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_WriteData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests the application to write a data value of a DID.
Available via Dcm_Externals.h

If DcmDspDataType is set to UINT8_DYN, the following definition is used:

[SWS_Dcm_91009] Definition of configurable interface Xxx_WriteData d

Service Name Xxx_WriteData
Syntax Std_ReturnType Xxx_WriteData (
const uint8* Data,
uint16 DataLength,
Dcm_OpStatusType OpStatus,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x3e
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) Data Buffer containing the data to be written
DataLength Length in byte of the data to be written
OpStatus Status of the current operation
Parameters (inout) None
5

324 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Parameters (out) ErrorCode If the operation Xxx_WriteData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests the application to write a data value of a DID.
Available via Dcm_Externals.h

If DcmDspDataType is set to USE_DATA_SYNCH_FNC_PROXY, the following definition

is used:

[SWS_Dcm_91095] Definition of configurable interface Xxx_WriteData

Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_WriteData (draft)
Syntax Std_ReturnType Xxx_WriteData (
const uint8* Data,
uint16 DataLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x85
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) Data Buffer containing the data to be written
DataLength Length in byte of the data to be written
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_WriteData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests the application to write a data value of a DID if DcmDspDataUsePort is
set to USE_DATA_SYNCH_FNC_PROXY.
Tags: atp.Status=draft
Available via Dcm_Externals.h

If DcmDspDataType is set to USE_DATA_ASYNCH_FNC_PROXY, the following defini-

tion is used:

325 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_91092] Definition of configurable interface Xxx_WriteData

Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_WriteData (draft)
Syntax Std_ReturnType Xxx_WriteData (
const uint8* Data,
uint16 DataLength,
Dcm_OpStatusType OpStatus,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x91
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) Data Buffer containing the data to be written
DataLength Length in byte of the data to be written
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_WriteData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests the application to write a data value of a DID if DcmDspDataUsePort is
set to USE_DATA_ASYNCH_FNC_PROXY.
Tags: atp.Status=draft
Available via Dcm_Externals.h

8.7.3.2.3 ReadDataLength

If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-

DATA_SYNCH_FNC or USE_DATA_SYNCH_FNC_PROXY, the following definition is used:

[SWS_Dcm_00796] Definition of configurable interface Xxx_ReadDataLength d

Service Name Xxx_ReadDataLength
Syntax Std_ReturnType Xxx_ReadDataLength (
uint16* DataLength
)
Service ID [hex] 0x86
Sync/Async Synchronous
Reentrancy Non Reentrant
5

326 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Parameters (in) None
Parameters (inout) None
Parameters (out) DataLength Length in byte of the data to be read
Return value Std_ReturnType E_OK: this value is always returned.
Description This function requests the application to return the data length in byte of a Data.
Available via Dcm_Externals.h

Please note that the function definition according [SWS_Dcm_00796] will become ob-
solete and gets replaced by [SWS_Dcm_91096]

[SWS_Dcm_91096] Definition of configurable interface Xxx_ReadDataLength

Status: DRAFT
d
Service Name Xxx_ReadDataLength (draft)
Syntax Std_ReturnType Xxx_ReadDataLength (
uint16* DataLength
)
Service ID [hex] 0x36
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) DataLength Length in byte of the data to be read
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests the application to return the data length in byte of a Data.
Tags: atp.Status=draft
Available via Dcm_Externals.h

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or USE_-

DATA_ASYNCH_CLIENT_SERVER_ERROR or USE_DATA_ASYNCH_FNC or USE_-
DATA_ASYNCH_FNC_ERROR or USE_DATA_ASYNCH_FNC_PROXY, the following defi-
nition is used:

327 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_91010] Definition of configurable interface Xxx_ReadDataLength d

Service Name Xxx_ReadDataLength
Syntax Std_ReturnType Xxx_ReadDataLength (
Dcm_OpStatusType OpStatus,
uint16* DataLength
)
Service ID [hex] 0x4c
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) DataLength Length in byte of the data to be read
Return value Std_ReturnType E_OK: this value is always returned.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests the application to return the data length in byte of a Data.
Available via Dcm_Externals.h

Please note that the function definition according [SWS_Dcm_91010] will become ob-
solete and gets replaced by [SWS_Dcm_91097]

[SWS_Dcm_91097] Definition of configurable interface Xxx_ReadDataLength

Status: DRAFT
d
Service Name Xxx_ReadDataLength (draft)
Syntax Std_ReturnType Xxx_ReadDataLength (
Dcm_OpStatusType OpStatus,
uint16* DataLength
)
Service ID [hex] 0x8c
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) DataLength Length in byte of the data to be read
Return value Std_ReturnType E_OK: this value is always returned.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests the application to return the data length in byte of a Data.
Tags: atp.Status=draft
Available via Dcm_Externals.h

328 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.7.3.2.4 ConditionCheckRead

If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-

DATA_SYNCH_FNC or USE_DATA_SYNCH_FNC_PROXY, the following definition is used:

[SWS_Dcm_00797] Definition of configurable interface Xxx_ConditionCheck

Read d
Service Name Xxx_ConditionCheckRead
Syntax Std_ReturnType Xxx_ConditionCheckRead (
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x49
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ConditionCheckRead returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application if the conditions to read the Data are correct.
Available via Dcm_Externals.h

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or USE_-

DATA_ASYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR USE_DATA_-
ASYNCH_FNC_ERROR or USE_DATA_ASYNCH_FNC_PROXY, the following definition is
used:

[SWS_Dcm_91011] Definition of configurable interface Xxx_ConditionCheck

Read d
Service Name Xxx_ConditionCheckRead
Syntax Std_ReturnType Xxx_ConditionCheckRead (
Dcm_OpStatusType OpStatus,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x37
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ConditionCheckRead returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
5

329 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application if the conditions to read the Data are correct.
Available via Dcm_Externals.h

8.7.3.2.5 GetScalingInformation

This function requests to the application for the scaling information of a Data (scaling-
Byte and scalingByteExtension).
If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-
DATA_SYNCH_FNC, the following definition is used:

[SWS_Dcm_00798] Definition of configurable interface Xxx_GetScalingInforma-

tion d
Service Name Xxx_GetScalingInformation
Syntax Std_ReturnType Xxx_GetScalingInformation (
uint8* ScalingInfo,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x4b
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) None
Parameters (inout) None
Parameters (out) ScalingInfo Scaling information (scalingByte and scalingByteExtension)
ErrorCode If the operation Xxx_GetScalingInformation returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application for the scaling information of a Data.
Available via Dcm_Externals.h

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or

USE_DATA_ASYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR
USE_DATA_ASYNCH_FNC_ERROR, the following definition is used:

330 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_91012] Definition of configurable interface Xxx_GetScalingInforma-

tion d
Service Name Xxx_GetScalingInformation
Syntax Std_ReturnType Xxx_GetScalingInformation (
Dcm_OpStatusType OpStatus,
uint8* ScalingInfo,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x38
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) ScalingInfo Scaling information (scalingByte and scalingByteExtension)
ErrorCode If the operation Xxx_GetScalingInformation returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application for the scaling information of a Data.
Available via Dcm_Externals.h

If DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY, the following defi-

nition is used:

[SWS_Dcm_91093] Definition of configurable interface Xxx_GetScalingInforma-

tion
Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_GetScalingInformation (draft)
Syntax Std_ReturnType Xxx_GetScalingInformation (
uint8* ScalingInfo,
uint8 ScalingInfoLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x90
Sync/Async Synchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}== (USE_DATA_
SYNCH_FNC_PROXY) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspData
InfoRef->DcmDspDataScalingInfoSize)} != NULL)
Parameters (in) ScalingInfoLength Length in byte of the scaling information to be read
Parameters (inout) None
5

331 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Parameters (out) ScalingInfo Scaling information (scalingByte and scalingByteExtension)
ErrorCode If the operation Xxx_GetScalingInformation returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application for the scaling information of a Data.
Tags: atp.Status=draft
Available via Dcm_Externals.h

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY, the following def-

inition is used:

[SWS_Dcm_91094] Definition of configurable interface Xxx_GetScalingInforma-

tion
Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_GetScalingInformation (draft)
Syntax Std_ReturnType Xxx_GetScalingInformation (
Dcm_OpStatusType OpStatus,
uint8* ScalingInfo,
uint8 ScalingInfoLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x8f
Sync/Async Asynchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}== (USE_DATA_
ASYNCH_FNC_PROXY) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspData
InfoRef->DcmDspDataScalingInfoSize)} != NULL)
Parameters (in) OpStatus Status of the current operation
ScalingInfoLength Length in byte of the scaling information to be read
Parameters (inout) None
Parameters (out) ScalingInfo Scaling information (scalingByte and scalingByteExtension)
ErrorCode If the operation Xxx_GetScalingInformation returns value E_
NOT_OK, the DCM module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application for the scaling information of a Data.
Tags: atp.Status=draft
Available via Dcm_Externals.h

332 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.7.3.2.6 ReturnControlToECU

If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or

USE_DATA_SYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER or USE_DATA_-
ASYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR or USE_DATA_-
ASYNCH_FNC_ERROR, the following definition is used:

[SWS_Dcm_01285] Definition of configurable interface Xxx_ReturnControlTo

ECU d
Service Name Xxx_ReturnControlToECU
Syntax Std_ReturnType Xxx_ReturnControlToECU (
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask],
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x4f
Sync/Async Synchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}== (USE_DATA_
SYNCH_FNC || USE_DATA_ASYNCH_FNC || USE_DATA_ASYNCH_FNC_ERROR|| USE_
DATA_SYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER || USE_DATA_
ASYNCH_CLIENT_SERVER_ERROR) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid
Info/DcmDspDidControl/DcmDspDidFreeze CurrentState)} == TRUE) || ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidResetToDefault)} == TRUE) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE))

Parameters (in) controlMask –

Type Dcm_ControlMask_{DID}Type
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref-> DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)}
<= 0x04)
controlMask –
Type uint8*
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_SYNCH_CLIENT_SERVER || USE_
DATA_ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_
CLIENT_SERVER_ERROR)) && ({ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/Dcm
DspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/Dcm
DspDidControl/DcmDspDidControlMaskSize)} => 0x05)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ReturnControlToECU returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application to return control to ECU of an IOControl.
Available via Dcm_Externals.h

333 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Note: Square brackets [] indicate that an argument is optional.

If DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY or USE_DATA_-
ASYNCH_FNC_PROXY, the following definition is used:

[SWS_Dcm_91098] Definition of configurable interface Xxx_ReturnControlTo

ECU
Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_ReturnControlToECU (draft)
Syntax Std_ReturnType Xxx_ReturnControlToECU (
uint8* controlMask,
uint8 controlMaskLength,
Dcm_NegativeResponseCodeType ErrorCode
)
Service ID [hex] 0x8e
Sync/Async Synchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}== (USE_DATA_
SYNCH_FNC_PROXY || USE_DATA_ASYNCH_FNC_PROXY) ) && ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDid/DcmDspDidInfoRef -> DcmDspDidInfo/DcmDspDidControl)} !=
NULL)
Parameters (in) controlMask Control enable mask
controlMaskLength Control enable mask length in byte
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ReturnControlToECU returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application to return control to ECU of an IOControl.
Tags: atp.Status=draft
Available via Dcm_Externals.h

8.7.3.2.7 ResetToDefault

8.7.3.2.7.1 Synchronous interface

If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-

DATA_SYNCH_FNC, the following definition is used:

334 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01286] Definition of configurable interface Xxx_ResetToDefault d

Service Name Xxx_ResetToDefault
Syntax Std_ReturnType Xxx_ResetToDefault (
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask],
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x4d
Sync/Async Synchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
SYNCH_FNC|| USE_DATA_SYNCH_CLIENT_SERVER)) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidResetToDefault)} == TRUE)

Parameters (in) controlMask –

Type Dcm_ControlMask_{DID}Type
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref-> DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)}
<= 0x04)
controlMask –
Type uint8*
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == USE_DATA_SYNCH_CLIENT_SERVER) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref -> DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)}
=> 0x05)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ResetToDefault returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application to reset an IOControl to default value.
Available via Dcm_Externals.h

Note: Square brackets [] indicate that an argument is optional.

If DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY, the following defi-
nition is used:

335 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_91099] Definition of configurable interface Xxx_ResetToDefault

Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_ResetToDefault (draft)
Syntax Std_ReturnType Xxx_ResetToDefault (
uint8* controlMask,
uint8 controlMaskLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x8d
Sync/Async Synchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}== USE_DATA_
SYNCH_FNC_PROXY) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidResetToDefault)} == TRUE)
Parameters (in) controlMask Control enable mask
controlMaskLength Control enable mask length in byte
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ResetToDefault returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application to reset an IOControl to default value.
Tags: atp.Status=draft
Available via Dcm_Externals.h

8.7.3.2.7.2 Asynchronous interface

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or USE_-

DATA_ASYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR or USE_-
DATA_ASYNCH_FNC_ERROR, the following definition is used:

[SWS_Dcm_01314] Definition of configurable interface Xxx_ResetToDefault d

Service Name Xxx_ResetToDefault
Syntax Std_ReturnType Xxx_ResetToDefault (
Dcm_OpStatusType OpStatus,
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask],
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x3c
Sync/Async Asynchronous
5

336 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_FNC || USE_DATA_ASYNCH_FNC_ERROR|| USE_DATA_ASYNCH_CLIENT_
SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR|| )) && ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidResetToDefault)} == TRUE)

Parameters (in) OpStatus Status of the current operation

controlMask –
Type Dcm_ControlMask_{DID}Type
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref -> DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)}
<= 0x04)
controlMask –
Type uint8*
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_ASYNCH_CLIENT_SERVER || USE_
DATA_ASYNCH_CLIENT_SERVER_ERROR)) && ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef -> Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} ==
DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/
DcmDspDidControl/DcmDspDidControlMaskSize)} => 0x05)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ResetToDefault returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application to reset an IOControl to default value.
Available via Dcm_Externals.h

Note: Square brackets [] indicate that an argument is optional.

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY, the following def-
inition is used:

337 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_91100] Definition of configurable interface Xxx_ResetToDefault

Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_ResetToDefault (draft)
Syntax Std_ReturnType Xxx_ResetToDefault (
Dcm_OpStatusType OpStatus,
uint8* controlMask,
uint8 controlMaskLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x7f
Sync/Async Asynchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}== USE_DATA_
ASYNCH_FNC_PROXY) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidResetToDefault)} == TRUE)
Parameters (in) OpStatus Status of the current operation
controlMask Control enable mask
controlMaskLength Control enable mask length in byte
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ResetToDefault returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application to reset an IOControl to default value.
Tags: atp.Status=draft
Available via Dcm_Externals.h

8.7.3.2.8 FreezeCurrentState

8.7.3.2.8.1 Synchronous interface

If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-

DATA_SYNCH_FNC, the following definition is used:

338 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01290] Definition of configurable interface Xxx_FreezeCurrentState

d
Service Name Xxx_FreezeCurrentState
Syntax Std_ReturnType Xxx_FreezeCurrentState (
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask],
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x4a
Sync/Async Synchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_FNC|| USE_DATA_SYNCH_CLIENT_SERVER)&& ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreezeCurrentState)} == TRUE)

Parameters (in) controlMask –

Type Dcm_ControlMask_{DID}Type
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref -> DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)}
<= 0x04)
controlMask –
Type uint8*
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == USE_DATA_ SYNCH_CLIENT_SERVER) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref -> DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)}
=> 0x05)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_FreezeCurrentState returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application to freeze the current state of an IOControl.
Available via Dcm_Externals.h

Note: Square brackets [] indicate that an argument is optional.

If DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY, the following defi-
nition is used:

339 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_91101] Definition of configurable interface Xxx_FreezeCurrentState

Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_FreezeCurrentState (draft)
Syntax Std_ReturnType Xxx_FreezeCurrentState (
uint8* controlMask,
uint8 controlMaskLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x77
Sync/Async Synchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}== USE_DATA_
SYNCH_FNC_PROXY) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidFreezeCurrentState)} == TRUE)
Parameters (in) controlMask Control enable mask
controlMaskLength Control enable mask length in byte
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_FreezeCurrentState returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application to freeze the current state of an IOControl.
Tags: atp.Status=draft
Available via Dcm_Externals.h

8.7.3.2.8.2 Asynchronous interface

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or USE_-

DATA_ASYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR or USE_-
DATA_ASYNCH_FNC_ERROR, the following definition is used:

[SWS_Dcm_01315] Definition of configurable interface Xxx_FreezeCurrentState

d
Service Name Xxx_FreezeCurrentState
Syntax Std_ReturnType Xxx_FreezeCurrentState (
Dcm_OpStatusType OpStatus,
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask],
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x84
5

340 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Sync/Async Asynchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_FNC || USE_DATA_ASYNCH_FNC_ERROR|| USE_DATA_ASYNCH_CLIENT_
SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR))&& ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreezeCurrentState)} == TRUE)

Parameters (in) OpStatus Status of the current operation

controlMask –
Type Dcm_ControlMask_{DID}Type
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref -> DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)}
<= 0x04)
controlMask –
Type uint8*
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_ASYNCH_CLIENT_SERVER || USE_
DATA_ASYNCH_CLIENT_SERVER_ERROR)) && ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef -> Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} ==
DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/
DcmDspDidControl/DcmDspDidControlMaskSize)} => 0x05)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_FreezeCurrentState returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application to freeze the current state of an IOControl.
Available via Dcm_Externals.h

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY, the following def-

inition is used:

341 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_91102] Definition of configurable interface Xxx_FreezeCurrentState

Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_FreezeCurrentState (draft)
Syntax Std_ReturnType Xxx_FreezeCurrentState (
Dcm_OpStatusType OpStatus,
uint8* controlMask,
uint8 controlMaskLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x88
Sync/Async Asynchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}== USE_DATA_
ASYNCH_FNC_PROXY) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidFreezeCurrentState)} == TRUE)
Parameters (in) OpStatus Status of the current operation
controlMask Control enable mask
controlMaskLength Control enable mask length in byte
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_FreezeCurrentState returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application to freeze the current state of an IOControl.
Tags: atp.Status=draft
Available via Dcm_Externals.h

8.7.3.2.9 ShortTermAdjustment

8.7.3.2.9.1 Synchronous interface

If DcmDspDataUsePort is set to USE_DATA_SYNCH_CLIENT_SERVER or USE_-

DATA_SYNCH_FNC, the following definition is used:

342 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00802] Definition of configurable interface Xxx_ShortTermAdjust-

ment d
Service Name Xxx_ShortTermAdjustment
Syntax Std_ReturnType Xxx_ShortTermAdjustment (
const uint8* ControlStateInfo,
[uint16 DataLength],
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask],
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x50
Sync/Async Synchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_FNC|| USE_DATA_SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShortTermAdjustment)} == TRUE)

Parameters (in) ControlStateInfo ControlState information contained in the ControlOptionRecord

parameter of the InputOutputControlByIdentifier diagnostic
request
DataLength Length in byte of the data to be written
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
Type} == UINT8_DYN
controlMask –
Type Dcm_ControlMask_{DID}Type
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref -> DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)}
<= 0x04)
controlMask –
Type uint8*
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == USE_DATA_ SYNCH_CLIENT_SERVER) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref -> DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)}
>= 0x05)
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ShortTermAdjustment returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application to adjust the IO signal.
Available via Dcm_Externals.h

Note: Square brackets [] indicate that an argument is optional.

If DcmDspDataUsePort is set to USE_DATA_SYNCH_FNC_PROXY, the following defi-
nition is used:

343 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_91103] Definition of configurable interface Xxx_ShortTermAdjust-

ment
Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_ShortTermAdjustment (draft)
Syntax Std_ReturnType Xxx_ShortTermAdjustment (
const uint8* ControlStateInfo,
uint16 DataLength,
uint8* controlMask,
uint8 controlMaskLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x87
Sync/Async Synchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}== USE_DATA_
SYNCH_FNC_PROXY) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidShortTermAdjustment)} == TRUE)
Parameters (in) ControlStateInfo ControlState information contained in the ControlOptionRecord
parameter of the InputOutputControlByIdentifier diagnostic
request
DataLength ControlState information length in byte
controlMask Control enable mask
controlMaskLength Control enable mask length in byte
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ShortTermAdjustment returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function requests to the application to adjust the IO signal.
Tags: atp.Status=draft
Available via Dcm_Externals.h

8.7.3.2.9.2 Asynchronous interface

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or USE_-

DATA_ASYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR or USE_-
DATA_ASYNCH_FNC_ERROR, the following definition is used:

344 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01316] Definition of configurable interface Xxx_ShortTermAdjust-

ment d
Service Name Xxx_ShortTermAdjustment
Syntax Std_ReturnType Xxx_ShortTermAdjustment (
const uint8* ControlStateInfo,
[uint16 DataLength],
Dcm_OpStatusType OpStatus,
[Dcm_ControlMask_{DID}Type controlMask],
[uint8* controlMask],
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x55
Sync/Async Asynchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_FNC || USE_DATA_ASYNCH_FNC_ERROR|| USE_DATA_ASYNCH_CLIENT_
SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR))&& ({ecuc(Dcm/DcmConfigSet/
DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShortTermAdjustment)} == TRUE)
ControlStateInfo ControlState information contained in the ControlOptionRecord
Parameters (in)
parameter of the InputOutputControlByIdentifier diagnostic
request
DataLength Length in byte of the data to be written
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
Type} == UINT8_DYN
OpStatus Status of the current operation
controlMask –
Type Dcm_ControlMask_{DID}Type
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref -> DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)}
<= 0x04)
controlMask –
Type uint8*
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == (USE_DATA_ASYNCH_CLIENT_SERVER || USE_
DATA_ASYNCH_CLIENT_SERVER_ERROR)) && ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef -> Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} ==
DCM_CONTROLMASK_EXTERNAL)&& ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/
DcmDspDidControl/DcmDspDidControlMaskSize)} >= 0x05)
Parameters (inout) None
Parameters (out) ErrorCode NRC to be sent in the negative response in case of failure (E_
NOT_OK)
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application to adjust the IO signal.
Available via Dcm_Externals.h

345 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

If DcmDspDataUsePort is set to USE_DATA_ASYNCH_FNC_PROXY, the following def-

inition is used:

[SWS_Dcm_91104] Definition of configurable interface Xxx_ShortTermAdjust-

ment
Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_ShortTermAdjustment (draft)
Syntax Std_ReturnType Xxx_ShortTermAdjustment (
const uint8* ControlStateInfo,
uint16 DataLength,
Dcm_OpStatusType OpStatus,
uint8* controlMask,
uint8 controlMaskLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x83
Sync/Async Synchronous
Reentrancy Non Reentrant
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}== USE_DATA_
ASYNCH_FNC_PROXY) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidShortTermAdjustment)} == TRUE)

Parameters (in) ControlStateInfo ControlState information contained in the ControlOptionRecord

parameter of the InputOutputControlByIdentifier diagnostic
request
DataLength ControlState information length in byte
OpStatus Status of the current operation
controlMask Control enable mask
controlMaskLength Control enable mask length in byte
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ShortTermAdjustment returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application to adjust the IO signal.
Tags: atp.Status=draft
Available via Dcm_Externals.h

8.7.3.3 DataServices_DIDRange

From the point of view of the DCM, the operations have the following signatures:

346 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Note : The OpStatus parameter should only be used for asynchronous operations
(if DcmDspDataUsePort is set to USE_DATA_ASYNCH_CLIENT_SERVER or USE_-
DATA_ASYNCH_FNC or USE_DATA_ASYNCH_CLIENT_SERVER_ERROR USE_DATA_-
ASYNCH_FNC_ERROR). In case of synchronous operations (DcmDspDataUsePort is
set to USE_DATA_SYNCH_CLIENT_SERVER or USE_DATA_SYNCH_FNC), the OpSta-
tus parameter should not be used.

8.7.3.3.1 IsDidAvailable

[SWS_Dcm_00803] Definition of configurable interface Xxx_IsDidAvailable d

Service Name Xxx_IsDidAvailable
Syntax Std_ReturnType Xxx_IsDidAvailable (
uint16 DID,
Dcm_OpStatusType OpStatus,
Dcm_DidSupportedType* supported
)
Service ID [hex] 0x53
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) DID DID value
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) supported Indicate if the DID is available within the range. Returning DCM_
DID_SUPPORTED means it is supported within the range,
Returning DCM_DID_NOT_SUPPORTED means it is not
supported within the range
Return value Std_ReturnType E_OK: This value is returned when the Did is finally available.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests if a specific DID is available within the range or not.
Available via Dcm_Externals.h

347 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.7.3.3.2 ReadDidData

[SWS_Dcm_00804] Definition of configurable interface Xxx_ReadDidData d

Service Name Xxx_ReadDidData
Syntax Std_ReturnType Xxx_ReadDidData (
uint16 DID,
uint8* Data,
Dcm_OpStatusType OpStatus,
uint16 DataLength,
Dcm_NegativeResponseCodeType ErrorCode
)
Service ID [hex] 0x89
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) DID Data ID value
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) Data Buffer where the requested data shall be copied to
DataLength Length of the data to be read
ErrorCode If the operation Xxx_ReadDidData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests to the application a data value of a DID
Available via Dcm_Externals.h

8.7.3.3.3 WriteDidData

[SWS_Dcm_00805] Definition of configurable interface Xxx_WriteDidData d

Service Name Xxx_WriteDidData
Syntax Std_ReturnType Xxx_WriteDidData (
uint16 DID,
const uint8* Data,
Dcm_OpStatusType OpStatus,
uint16 DataLength,
Dcm_NegativeResponseCodeType ErrorCode
)
Service ID [hex] 0x41
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) DID Data ID value
5

348 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Data Buffer containing the data to be written
OpStatus Status of the current operation
DataLength Length of the data to be written
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_WriteDidData returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests the application to write a data value of a DID.
Available via Dcm_Externals.h

8.7.3.3.4 ReadDidRangeDataLength

ReadDidRangeDataLength requests the application to return the data length of a DID

range. This interface is used for UDS Service ReadDataByIdentifier.

[SWS_Dcm_01271] Definition of configurable interface Xxx_ReadDidRangeData

Length d
Service Name Xxx_ReadDidRangeDataLength
Syntax Std_ReturnType Xxx_ReadDidRangeDataLength (
uint16 DID,
Dcm_OpStatusType OpStatus,
uint16* DataLength
)
Service ID [hex] 0x5e
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) DID Data ID value
OpStatus Status of the current operation
Parameters (inout) None
Parameters (out) DataLength Length of the data to be written/read
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description This function requests the application to return the data length of a DID Range.
Available via Dcm_Externals.h

349 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.7.3.4 InfoTypesServices

8.7.3.4.1 GetInfotypeValueData

[SWS_Dcm_91014] Definition of configurable interface Xxx_GetInfotypeValue

Data d
Service Name Xxx_GetInfotypeValueData
Syntax Std_ReturnType Xxx_GetInfotypeValueData (
Dcm_OpStatusType OpStatus,
uint8* DataValueBuffer,
uint8* DataValueBufferSize
)
Service ID [hex] 0x60
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) DataValueBufferSize When the function is called this parameter contains the maximum
number of data bytes that can be written to the buffer. The callee
fills in the number of written data bytes in DataValueBuffer.
Parameters (out) DataValueBuffer Buffer containing the Infotype information
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
Description The function provides the data related to the requested Infotype.
Available via Dcm_Externals.h

8.7.3.5 RoutineServices

The operations mentioned in the following sub-chapters are only general examples,
because the number of In and OUT parameters can be variable from 0 to an arbitrary
number.It is therefore not possible to list all variations of operation prototypes.

8.7.3.5.1 Xxx_Start Operation

If DcmDspRoutineFncSignature is set to ROUTINE_FNC_NORMAL, the following

definition is used:

350 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_01203] Definition of configurable interface Xxx_Start d

Service Name Xxx_Start
Syntax Std_ReturnType Xxx_Start (
[DcmDspRoutineSignalType dataIn_1, ...
DcmDspRoutineSignalType dataIn_n],
[const uint8* dataInVar],
Dcm_OpStatusType OpStatus,
[DcmDspRoutineSignalType dataOut_1, ...
DcmDspRoutineSignalType dataOut_n],
[uint8* dataOutVar],
[uint16* currentDataLength],
Dcm_NegativeResponseCodeType ErrorCode
)
Service ID [hex] 0x5b
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) dataIn_1 Fixed-length input data provided in the routine control request
... ...
dataIn_n Fixed-length input data provided in the routine control request
dataInVar Variable-length input data provided in the routine control request
OpStatus Status of the current operation
Parameters (inout) currentDataLength If variable length routine input data is used, this parameter
contains the length in bytes of the dataInVar array. If variable
length routine output data is used, this parameter contains the
length in bytes of the dataOutVar parameter.

Parameters (out) dataOut_1 Fixed-length output data to provide in the routine control response
... ...
dataOut_n Fixed-length output data to provide in the routine control response
dataOutVar Variable-length output data to provide in the routine control
response
ErrorCode If the operation Xxx_Start returns value E_NOT_OK, the Dcm
module shall send a negative response with NRC code equal to
the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
DCM_E_FORCE_RCRRP: application requests the transmission of
a response Pending (NRC 0x78)
Description This function requests to the application to start the execution of a routine.
Available via Dcm_Externals.h

Note: Square brackets [] indicate that an argument is optional.

If DcmDspRoutineFncSignature is set to ROUTINE_FNC_PROXY, the following def-
inition is used:

351 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_91105] Definition of configurable interface Xxx_Start

Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_Start (draft)
Syntax Std_ReturnType Xxx_Start (
Dcm_OpStatusType OpStatus,
uint8* dataInOut,
uint16* currentDataLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x80
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) dataInOut Input and output data in the routine control request / response
currentDataLength This parameter contains the length in bytes of the dataInOut
array. It include fixed length and variable length data.
Parameters (out) ErrorCode If the operation Xxx_Start returns value E_NOT_OK, the Dcm
module shall send a negative response with NRC code equal to
the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish.
DCM_E_FORCE_RCRRP: application requests the transmission
of a response Pending (NRC 0x78)
Description This function requests to the application to start the execution of a routine.
Tags: atp.Status=draft
Available via Dcm_Externals.h

8.7.3.5.2 Xxx_StartConfirmation Operation

If DcmDspRoutineFncSignature is set to ROUTINE_FNC_NORMAL or ROUTINE_-

FNC_PROXY, the following definition is used:

[SWS_Dcm_91016] Definition of configurable interface Xxx_StartConfirmation d

Service Name Xxx_StartConfirmation
Syntax Std_ReturnType Xxx_StartConfirmation (
Dcm_ConfirmationStatusType ConfirmationStatus
)
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) ConfirmationStatus Confirmation status of a StartRoutine request
5

352 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function indicates the transmission of a response to a StartRoutine request
Available via Dcm_Externals.h

Note: Square brackets [] indicate that an argument is optional.

8.7.3.5.3 Xxx_Stop Operation

If DcmDspRoutineFncSignature is set to ROUTINE_FNC_NORMAL, the following

definition is used:

[SWS_Dcm_01204] Definition of configurable interface Xxx_Stop d

Service Name Xxx_Stop
Syntax Std_ReturnType Xxx_Stop (
[DcmDspRoutineSignalType dataIn_1, ...
DcmDspRoutineSignalType dataIn_n],
[const uint8* dataInVar],
Dcm_OpStatusType OpStatus,
[DcmDspRoutineSignalType dataOut_1, ...
DcmDspRoutineSignalType dataOut_n],
[uint8* dataOutVar],
[uint16* currentDataLength],
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x5c
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) dataIn_1 Fixed-length input data provided in the routine control request
... ...
dataIn_n Fixed-length input data provided in the routine control request
dataInVar Variable-length input data provided in the routine control request
OpStatus Status of the current operation
Parameters (inout) currentDataLength If variable length routine input data is used, this parameter
contains the length in bytes of the dataInVar array. If variable
length routine output data is used, this parameter contains the
length in bytes of the dataOutVar parameter.
Parameters (out) dataOut_1 Fixed-length output data to provide in the routine control response
... ...
dataOut_n Fixed-length output data to provide in the routine control response
dataOutVar Variable-length output data to provide in the routine control
response
5

353 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
ErrorCode If the operation Xxx_Stop returns value E_NOT_OK, the Dcm
module shall send a negative response with NRC code equal to
the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish
DCM_E_FORCE_RCRRP: application requests the transmission of
a response Pending (NRC 0x78)
Description This function requests to the application to stop the execution of a routine
Available via Dcm_Externals.h

Note: Square brackets [] indicate that an argument is optional.

If DcmDspRoutineFncSignature is set to ROUTINE_FNC_PROXY, the following def-
inition is used:

[SWS_Dcm_91106] Definition of configurable interface Xxx_Stop

Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_Stop (draft)
Syntax Std_ReturnType Xxx_Stop (
Dcm_OpStatusType OpStatus,
uint8* dataInOut,
uint16* currentDataLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x81
Sync/Async Asynchronous
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) dataInOut Input and output data in the routine control request / response
currentDataLength This parameter contains the length in bytes of the dataInOut
array. It include fixed length and variable length data.
Parameters (out) ErrorCode If the operation Xxx_Stop returns value E_NOT_OK, the Dcm
module shall send a negative response with NRC code equal to
the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish
DCM_E_FORCE_RCRRP: application requests the transmission
of a response Pending (NRC 0x78)
Description This function requests to the application to stop the execution of a routine
Tags: atp.Status=draft
Available via Dcm_Externals.h

354 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.7.3.5.4 Xxx_StopConfirmation Operation

If DcmDspRoutineFncSignature is set to ROUTINE_FNC_NORMAL or ROUTINE_-

FNC_PROXY, the following definition is used:

[SWS_Dcm_91017] Definition of configurable interface Xxx_StopConfirmation d

Service Name Xxx_StopConfirmation
Syntax Std_ReturnType Xxx_StopConfirmation (
Dcm_ConfirmationStatusType ConfirmationStatus
)
Service ID [hex] 0x69
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) ConfirmationStatus Dcm_ConfirmationStatus Confirmation status of a StopRoutine
request
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function indicates the transmission of a response to a StopRoutine request
Available via Dcm_Externals.h

Note: Square brackets [] indicate that an argument is optional.

8.7.3.5.5 Xxx_RequestResults Operation

If DcmDspRoutineFncSignature is set to ROUTINE_FNC_NORMAL, the following

definition is used:

[SWS_Dcm_91013] Definition of configurable interface Xxx_RequestResults d

Service Name Xxx_RequestResults
Syntax Std_ReturnType Xxx_RequestResults (
[DcmDspRoutineSignalType* dataIn_1, ...
DcmDspRoutineSignalType* dataIn_n],
[const uint8* dataInVar],
Dcm_OpStatusType OpStatus,
[DcmDspRoutineSignalType* dataOut_1, ...
DcmDspRoutineSignalType* dataOut_n],
[uint8* dataOutVar],
[uint16* currentDataLength],
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x71
Sync/Async Synchronous
5

355 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Reentrancy Non Reentrant
Parameters (in) dataIn_1 Fixed-length input data provided in the routine control request
... ...
dataIn_n Fixed-length input data provided in the routine control request
dataInVar Variable-length input data provided in the routine control request
OpStatus Move to be mentioned after dataInVar.
Parameters (inout) currentDataLength If variable length routine input data is used, this parameter
contains the length in bytes of the dataInVar array. If variable
length routine output data is used, this parameter contains the
length in bytes of the dataOutVar parameter.

Parameters (out) dataOut_1 Fixed-length Output data to provide in the routine control
response
... ...
dataOut_n Fixed-length Output data to provide in the routine control
response
dataOutVar Variable-length Output data to provide in the routine control
response
ErrorCode If the operation Xxx_RequestResults returns value E_NOT_OK,
the Dcm module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish
DCM_E_FORCE_RCRRP: application requests the transmission of
a response Pending (NRC 0x78)
Description This function requests to the application the result of a routine execution
Available via Dcm_Externals.h

Note: Square brackets [] indicate that an argument is optional.

If DcmDspRoutineFncSignature is set to ROUTINE_FNC_PROXY, the following def-
inition is used:

[SWS_Dcm_91107] Definition of configurable interface Xxx_RequestResults

Status: DRAFT
Upstream requirements: RS_Diag_04254

d
Service Name Xxx_RequestResults (draft)
Syntax Std_ReturnType Xxx_RequestResults (
Dcm_OpStatusType OpStatus,
uint8* dataInOut,
uint16* currentDataLength,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x82
Sync/Async Asynchronous
5

356 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Reentrancy Non Reentrant
Parameters (in) OpStatus Status of the current operation
Parameters (inout) dataInOut Input and output data in the routine control request / response If
variable length routine input data is used, this parameter contains
the length in bytes of the dataInVar array. If variable length
routine output data is used, this parameter contains the length in
bytes of the dataOutVar parameter.
currentDataLength This parameter contains the length in bytes of the dataInOut
array. It include fixed length and variable length data.
Parameters (out) ErrorCode If the operation Xxx_RequestResults returns value E_NOT_OK,
the Dcm module shall send a negative response with N
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
DCM_E_PENDING: Request is not yet finished. Further call(s)
required to finish
DCM_E_FORCE_RCRRP: application requests the transmission
of a response Pending (NRC 0x78)
Description This function requests to the application the result of a routine execution
Tags: atp.Status=draft
Available via Dcm_Externals.h

8.7.3.5.6 Xxx_RequestResultsConfirmation Operation

If DcmDspRoutineFncSignature is set to ROUTINE_FNC_NORMAL or ROUTINE_-

FNC_PROXY, the following definition is used:

[SWS_Dcm_91018] Definition of configurable interface Xxx_RequestResultsCon-

firmation d
Service Name Xxx_RequestResultsConfirmation
Syntax Std_ReturnType Xxx_RequestResultsConfirmation (
Dcm_ConfirmationStatusType ConfirmationStatus
)
Service ID [hex] 0x70
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) ConfirmationStatus Confirmation status of a RequestRoutineResults request
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function indicates the transmission of a response to a RequestRoutineResults request
Available via Dcm_Externals.h

Note: Square brackets [] indicate that an argument is optional.

357 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.7.3.6 RequestControlServices

From the point of view of the DCM, the operation has the following signature:

8.7.3.6.1 RequestControl callout

[SWS_Dcm_01338] Definition of configurable interface Xxx_RequestControl d

Service Name Xxx_RequestControl
Syntax Std_ReturnType Xxx_RequestControl (
uint8* OutBuffer,
const uint8* InBuffer
)
Service ID [hex] 0x63
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) None
Parameters (inout) OutBuffer Output buffer in which the RequestControl function can store its
result
InBuffer Input buffer containing the data of the OBD Service 0x08 request
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description Invokes a TID-specific function taking a configured number of bytes as input and returing a
fixed number of bytes as output. This is typically used to implement OBD Service $08
Available via Dcm_Externals.h

8.7.3.7 ServiceRequestNotification

From the point of view of the DCM, the operations has the following signatures:

358 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.7.3.7.1 Indication

[SWS_Dcm_01341] Definition of configurable interface Xxx_Indication d

Service Name Xxx_Indication
Syntax Std_ReturnType Xxx_Indication (
uint8 SID,
const uint8* RequestData,
uint32 DataSize,
uint8 ReqType,
uint16 ConnectionId,
Dcm_NegativeResponseCodeType* ErrorCode,
Dcm_ProtocolType ProtocolType,
uint16 TesterSourceAddress
)
Service ID [hex] 0x65
Sync/Async Synchronous
Reentrancy Non Reentrant

Parameters (in) SID –

RequestData Complete request data (diagnostic buffer), except the service ID
DataSize Number of valid bytes in the RequestData parameter
ReqType Addressing type of the request(0=physical request,1=functional
request)
ConnectionId Unique connection identifier
ProtocolType Type of the protocol to be indicated
TesterSourceAddress source address of the tester
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_Indication re- turns value E_NOT_OK, the
Dcm module shall send a negative response with NRC code
equal to the parameter ErrorCode parameter value
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
E_REQUEST_NOT_ACCEPTED : Request not accepted
Description This function indicates to the application that a service is about to be executed and allows the
application to reject the execution of the service request
Available via Dcm_Externals.h

359 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.7.3.7.2 Confirmation

[SWS_Dcm_01342] Definition of configurable interface Xxx_Confirmation d

Service Name Xxx_Confirmation
Syntax Std_ReturnType Xxx_Confirmation (
uint8 SID,
uint8 ReqType,
uint16 ConnectionId,
Dcm_ConfirmationStatusType ConfirmationStatus,
Dcm_ProtocolType ProtocolType,
uint16 TesterSourceAddress
)
Service ID [hex] 0x66
Sync/Async Synchronous
Reentrancy Non Reentrant

Parameters (in) SID Value of service identifier

ReqType Addressing type of the request(0=physical request,1=functional
request)
ConnectionId Unique connection identifier
ConfirmationStatus Confirmation of a successful transmission or a transmission error
of a diagnostic service.
ProtocolType Type of Dcm Protocol
TesterSourceAddress source address of the tester
Parameters (inout) None
Parameters (out) None
Return value Std_ReturnType E_OK: Request was successful.
E_NOT_OK: Request was not successful.
Description This function confirms to the application the successful transmission or a transmission error of
a diagnostic service.
Available via Dcm_Externals.h

8.7.3.8 ClearDTCCheckFnc

From the point of view of the Dcm, the operation has the following signature:

[SWS_Dcm_01270] Definition of configurable interface Xxx_ClearDTCCheckFnc

d
Service Name Xxx_ClearDTCCheckFnc
Syntax Std_ReturnType Xxx_ClearDTCCheckFnc (
uint32 GoDTC,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x5f
5

360 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) GoDTC requested groupOfDTC
Parameters (inout) None
Parameters (out) ErrorCode If the operation Xxx_ClearDTCCheckFnc returns value E_NOT_
OK, the DCM module shall send a negative response with NRC
code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: application allows to clear the requested groupOfDTC
E_NOT_OK: application does not allow to clear the requested
groupOfDTC. Dcm shall send a negative response with the NRC
returned in the ErrorCode
Description Callout function for condition check, manufacturer / supplier specific checks on the groupOf
DTC, which is requested to clear.
Available via Dcm_Externals.h

8.8 Dcm as Service-Component

8.8.1 Implementation Data Types

8.8.1.1 Dcm_OpStatusType

[SWS_Dcm_00984] Definition of ImplementationDataType Dcm_OpStatusType d

Name Dcm_OpStatusType
Kind Type
Derived from uint8
Range DCM_INITIAL 0x00 Indicates the initial call to the
operation
DCM_PENDING 0x01 Indicates that a pending return
has been done on the previous
call of the operation
DCM_CANCEL 0x02 Indicates that the DCM requests
to cancel the pending operation
DCM_FORCE_RCRRP_OK 0x03 Confirm a response pending
transmission
Description –
Variation –
Available via Rte_Dcm_Type.h

361 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.2 Dcm_ConfirmationStatusType

[SWS_Dcm_00983] Definition of ImplementationDataType Dcm_Confirmation

StatusType d
Name Dcm_ConfirmationStatusType
Kind Type
Derived from uint8
Range DCM_RES_POS_OK 0x00 –
DCM_RES_POS_NOT_OK 0x01 –
DCM_RES_NEG_OK 0x02 –
DCM_RES_NEG_NOT_OK 0x03 –
Description –
Variation –
Available via Rte_Dcm_Type.h

8.8.1.3 Dcm_SecLevelType

[SWS_Dcm_00977] Definition of ImplementationDataType Dcm_SecLevelType d

Name Dcm_SecLevelType
Kind Type
Derived from uint8
Range DCM_SEC_LEV_LOCKED 0x00 –
configuration dependent 0x01...0x3F –
Reserved by Document 0x40...0xFF –
Description Security Level type definition
Variation –
Available via Rte_Dcm_Type.h

362 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.4 Dcm_SesCtrlType

[SWS_Dcm_00978] Definition of ImplementationDataType Dcm_SesCtrlType d

Name Dcm_SesCtrlType
Kind Type
Derived from uint8
Range DCM_DEFAULT_SESSION 0x01 –
DCM_PROGRAMMING_ 0x02 –
SESSION
DCM_EXTENDED_ 0x03 –
DIAGNOSTIC_SESSION
DCM_SAFETY_SYSTEM_ 0x04 –
DIAGNOSTIC_SESSION
configuration dependent 0x40...0x7E (according to "diagnosticSession
Type" parameter of Diagnostic
SessionControl request)
Description Session type definition. 0, 127 and all values above 127 are reserved by ISO.
Variation –
Available via Rte_Dcm_Type.h

8.8.1.5 Dcm_ProtocolType

[SWS_Dcm_00979] Definition of ImplementationDataType Dcm_ProtocolType d

Name Dcm_ProtocolType
Kind Type
Derived from uint8
Range DCM_OBD_ON_CAN 0x00 OBD on CAN (ISO15765-4;
ISO15031-5)
DCM_OBD_ON_FLEXRAY 0x01 (OBD on Flexray (Manufacturer
specific; ISO15031-5))
DCM_OBD_ON_IP 0x02 (OBD on Internet Protocol
(Manufacturer specific;
ISO15031-5))
DCM_UDS_ON_CAN 0x03 UDS on CAN (ISO15765-3;
ISO14229-1)
DCM_UDS_ON_FLEXRAY 0x04 UDS on FlexRay (Manufacturer
specific; ISO14229-1)
DCM_UDS_ON_IP 0x05 (UDS on Internet Protocol
(Manufacturer specific;
ISO14229-1))
DCM_ROE_ON_CAN 0x06 Response On Event on CAN
DCM_ROE_ON_FLEXRAY 0x07 Response On Event on FlexRay
5

363 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
DCM_ROE_ON_IP 0x08 (Response on Event on Internet
Protocol)
DCM_PERIODICTRANS_ 0x09 Periodic Transmission on CAN
ON_CAN
DCM_PERIODICTRANS_ 0x0A Periodic Transmission on FlexRay
ON_FLEXRAY
DCM_PERIODICTRANS_ 0x0B (Periodic Transmission on Internet
ON_IP Protocol)
DCM_NO_ACTIVE_ 0x0C No protocol has been started
PROTOCOL
DCM_UDS_ON_LIN 0x0D UDS on LIN (ISO14229-1;
ISO14229-7)
Reserved for further 0x0E..0xEF –
AUTOSAR implementation
DCM_SUPPLIER_1 0xF0 Reserved for SW supplier
specific.
DCM_SUPPLIER_2 0xF1 Reserved for SW supplier
specific.
DCM_SUPPLIER_3 0xF2 Reserved for SW supplier
specific.
DCM_SUPPLIER_4 0xF3 Reserved for SW supplier
specific.
DCM_SUPPLIER_5 0xF4 Reserved for SW supplier
specific.
DCM_SUPPLIER_6 0xF5 Reserved for SW supplier
specific.
DCM_SUPPLIER_7 0xF6 Reserved for SW supplier
specific.
DCM_SUPPLIER_8 0xF7 Reserved for SW supplier
specific.
DCM_SUPPLIER_9 0xF8 Reserved for SW supplier
specific.
DCM_SUPPLIER_10 0xF9 Reserved for SW supplier
specific.
DCM_SUPPLIER_11 0xFA Reserved for SW supplier
specific.
DCM_SUPPLIER_12 0xFB Reserved for SW supplier
specific.
DCM_SUPPLIER_13 0xFC Reserved for SW supplier
specific.
DCM_SUPPLIER_14 0xFD Reserved for SW supplier
specific.
DCM_SUPPLIER_15 0xFE Reserved for SW supplier
specific.
Description Protocol type definition
Variation –
Available via Rte_Dcm_Type.h

364 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.6 Dcm_NegativeResponseCodeType

[SWS_Dcm_00980] Definition of ImplementationDataType Dcm_NegativeRe-

sponseCodeType d
Name Dcm_NegativeResponseCodeType
Kind Type
Derived from uint8
DCM_POS_RESP 0x00 PR
Range 0x01..0x0F
range of values 0x01..0x0F ISOSAERESRVD
reserved by ISO 14229
DCM_E_ 0x10 GR
GENERALREJECT
DCM_E_ 0x11 SNS
SERVICENOTSUPPORTED
DCM_E_SUBFUNCTION- 0x12 SFNS
NOTSUPPORTED
DCM_E_INCORRECTMES- 0x13 IMLOIF
SAGELENGTHORINVALID-
FORMAT
DCM_E_ 0x14 RTL
RESPONSETOOLONG
range of values 0x15..0x20 0x15..0x20 ISOSAERESRVD
reserved by ISO 14229
DCM_E_ 0x21 BRR
BUSYREPEATREQUEST
DCM_E_CONDITIONSNOT- 0x22 CNC
CORRECT
value 0x23 reserved by ISO 0x23 ISOSAERESRVD
14229
DCM_E_REQUESTSE- 0x24 RSE
QUENCEERROR
DCM_E_ 0x25 NRFSC
NORESPONSEFROMSUB-
NETCOMPONENT
DCM_E_FAILUREPRE- 0x26 FPEORA
VENTSEXECUTIONOFRE-
QUESTEDACTION
range of values 0x27..0x30 0x27..0x30 ISOSAERESRVD
reserved by ISO 14229
DCM_E_ 0x31 ROOR
REQUESTOUTOFRANGE
value 0x32 reserved by ISO 0x32 ISOSAERESRVD
14229
DCM_E_SECURITYAC- 0x33 SAD
CESSDENIED
value 0x34 reserved by ISO 0x34 ISOSAERESRVD
14229
DCM_E_INVALIDKEY 0x35 IK
DCM_E_EXCEEDNUM- 0x36 ENOA
BEROFATTEMPTS
5

365 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
DCM_E_REQUIRED- 0x37 RTDNE
TIMEDELAYNOTEXPIRED
range of values 0x38..0x4F 0x38..0x4F RBEDLSD
reserved by ISO 15764
range of values 0x50..0x6F 0x50..0x6F ISOSAERESRVD
reserved by ISO 14229
DCM_E_UPLOADDOWN- 0x70 UDNA
LOADNOTACCEPTED
DCM_E_TRANSFERDATA- 0x71 TDS
SUSPENDED
DCM_E_GENERALPRO- 0x72 GPF
GRAMMINGFAILURE
DCM_E_WRONGBLOCK- 0x73 WBSC
SEQUENCECOUNTER
range of values 0x74..0x77 0x74..0x77 ISOSAERESRVD
reserved by ISO 14229
range of values 0x79..0x7D 0x79..0x7D ISOSAERESRVD
reserved by ISO 14229
DCM_E_SUBFUNCTION- 0x7E SFNSIAS
NOTSUPPORTEDINAC-
TIVESESSION
DCM_E_ 0x7F SNSIAS
SERVICENOTSUPPORTE-
DINACTIVESESSION
value 0x80 reserved by ISO 0x80 ISOSAERESRVD
14229
DCM_E_RPMTOOHIGH 0x81 RPMTH
DCM_E_RPMTOOLOW 0x82 RPMTL
DCM_E_ 0x83 EIR
ENGINEISRUNNING
DCM_E_ 0x84 EINR
ENGINEISNOTRUNNING
DCM_E_ENGINERUN- 0x85 ERTTL
TIMETOOLOW
DCM_E_ 0x86 TEMPTH
TEMPERATURETOOHIGH
DCM_E_ 0x87 TEMPTL
TEMPERATURETOOLOW
DCM_E_ 0x88 VSTH
VEHICLESPEEDTOOHIGH
DCM_E_ 0x89 VSTL
VEHICLESPEEDTOOLOW
DCM_E_THROTTLE_ 0x8A TPTH
PEDALTOOHIGH
DCM_E_THROTTLE_ 0x8B TPTL
PEDALTOOLOW
DCM_E_TRANSMISSION- 0x8C TRNIN
RANGENOTINNEUTRAL
DCM_E_TRANSMISSION- 0x8D TRNIG
RANGENOTINGEAR
value 0x8E reserved by ISO 0x8E ISOSAERESRVD
14229
DCM_E_BRAKESWITCH_ 0x8F BSNC
NOTCLOSED
DCM_E_SHIFTERLEVER- 0x90 SLNIP
NOTINPARK
5

366 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
DCM_E_TORQUECON- 0x91 TCCL
VERTERCLUTCHLOCKED
DCM_E_ 0x92 VTH
VOLTAGETOOHIGH
DCM_E_ 0x93 VTL
VOLTAGETOOLOW
range of values 0x94..0xEF 0x94..0xEF RFSCNC
reserved by ISO 14229
DCM_E_VMSCNC_0 0xF0 VMSCNC
DCM_E_VMSCNC_1 0xF1 VMSCNC1
DCM_E_VMSCNC_2 0xF2 VMSCNC2
DCM_E_VMSCNC_3 0xF3 VMSCNC3
DCM_E_VMSCNC_4 0xF4 VMSCNC4
DCM_E_VMSCNC_5 0xF5 VMSCNC5
DCM_E_VMSCNC_6 0xF6 VMSCNC6
DCM_E_VMSCNC_7 0xF7 VMSCNC7
DCM_E_VMSCNC_8 0xF8 VMSCNC8
DCM_E_VMSCNC_9 0xF9 VMSCNC9
DCM_E_VMSCNC_A 0xFA VMSCNCA
DCM_E_VMSCNC_B 0xFB VMSCNCB
DCM_E_VMSCNC_C 0xFC VMSCNCC
DCM_E_VMSCNC_D 0xFD VMSCNCD
DCM_E_VMSCNC_E 0xFE VMSCNCE
value 0xFF reserved by ISO 0xFF ISOSAERESRVD
14229
Description This Table of available Negative Response Codes represents the allowed Response Codes an
AUTOSAR SW Component shall return after a function call. For the allowed NRC of the executed
Service ID please refer to the specification of the service in ISO14229-1 (UDS) and ISO15031-5
(OBD/CARB) (Response code parameter definition Table 18 of ISO 14229-1:2020).
Variation –
Available via Rte_Dcm_Type.h

8.8.1.7 Dcm_DataElementType_{Data}Type

[SWS_Dcm_91051] Definition of ImplementationDataType Dcm_DataEle-

ment_{Data}Type d
Name Dcm_DataElement_{Data}Type
Kind Type
Derived from Basetype Variation
5

367 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Dcm_DataElement_{Data} (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDsp
_ArrayType DataType)} == ([S|U]INT[8|16|32]|FLOAT)_N) || ({ecuc(Dcm/?Dcm
ConfigSet/?DcmDsp/?DcmDspPid/?DcmDspPidData/?DcmDsp
PidService01.?DcmDspPidDataType)} ==
([S|U]INT[8|16|32]|FLOAT)_N))
Dcm_DataElement_{Data} (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDsp
_PrimitiveType DataType)} == (BOOLEAN|[S|U]INT[8|16|32]|FLOAT)) ||
({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspPid/?DcmDspPid
Data/?DcmDspPidService01.?DcmDspPidDataType)} ==
(BOOLEAN|[S|U]INT[8|16|32]|FLOAT)))
Dcm_DataElement_{Data} DcmDspDidSignal with at least one DcmDspDidSignalComposite
_StructuredType Ref.
Description Common description for S/R and C/S data elements.
Variation (({Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort == USE_DATA_ELEMENT_
SPECIFIC_INTERFACES}) && ( ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspData
UsePort)} == USE_DATA_SENDER_RECEIVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Pid/DcmDspPidData/DcmDspPidService01/DcmDspPidDataUsePort)} == USE_DATA_SENDER_
RECEIVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPid
Service01/DcmDspPidDataUsePort)} == USE_DATA_SENDER_RECEIVER_AS_SERVICE) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataUsePort)} == USE_DATA_
SENDER_RECEIVER_AS_SERVICE) ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataUsePort)} == USE_DATA_SYNCH_CLIENT_SERVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspData.DcmDspDataUsePort)} == USE_DATA_ASYNCH_CLIENT_SERVER) || ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_ASYNCH_CLIENT_
SERVER_ERROR) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDsp
PidService01.DcmDspPidDataUsePort)} == USE_DATA_SYNCH_CLIENT_SERVER) ))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME)})
Available via Rte_Dcm_Type.h

8.8.1.8 Dcm_DataElement_{Data}StructuredType

[SWS_Dcm_91118] Definition of ImplementationDataType Dcm_DataEle-

ment_{Data}_StructuredType d
Name Dcm_DataElement_{Data}_StructuredType
Kind Structure
Elements structureMember
Type Dcm_DataElement_{Data}Type
Comment –
Description –
Variation DcmDspDidSignal.DcmDspDidSignalCompositeRef.DcmDspDidSignalCompositePool
Available via Rte_Dcm_Type.h

368 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.9 Dcm_DataElementType_{Data}ArrayType

[SWS_Dcm_91063] Definition of ImplementationDataType Dcm_DataEle-

ment_{Data}_ArrayType d
Name Dcm_DataElement_{Data}_ArrayType
Kind Array

Element type Type Variation

float32 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == FLOAT_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?Dcm
DspPid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidData
Type)} == FLOAT_N))
sint16 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == SINT16_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?Dcm
DspPid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidData
Type)} == SINT16_N))
sint32 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == SINT32_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?Dcm
DspPid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidData
Type)} == SINT32_N))
sint8 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == SINT8_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Pid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidDataType)}
== SINT8_N))
uint16 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == UINT16_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?Dcm
DspPid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidData
Type)} == UINT16_N))
uint32 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == UINT32_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?Dcm
DspPid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidData
Type)} == UINT32_N))
uint8 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDspData
Type)} == UINT8_N) || ({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDsp
Pid/?DcmDspPidData/?DcmDspPidService01.?DcmDspPidDataType)}
== UINT8_N))
Size –
Description –
Variation ((({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType)} ==
([S|U]INT[8|16|32]|FLOAT)_N) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data/DcmDspPidService01.DcmDspPidDataType)} == ([S|U]INT[8|16|32]|FLOAT)_N)) && ({Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort == USE_DATA_ELEMENT_SPECIFIC_
INTERFACES}) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataUsePort)} ==
USE_DATA_SENDER_RECEIVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDsp
PidData/DcmDspPidService01/DcmDspPidDataUsePort)} == USE_DATA_SENDER_RECEIVER)
|| ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/Dcm
DspPidDataUsePort)} == USE_DATA_SENDER_RECEIVER_AS_SERVICE) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspData/DcmDspDataUsePort)} == USE_DATA_SENDER_RECEIVER_
AS_SERVICE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} ==
USE_DATA_SYNCH_CLIENT_SERVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Data.DcmDspDataUsePort)} == USE_DATA_ASYNCH_CLIENT_SERVER) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_ASYNCH_CLIENT_
SERVER_ERROR) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDsp
PidService01.DcmDspPidDataUsePort)} == USE_DATA_SYNCH_CLIENT_SERVER)))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME)})
5

369 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Available via Rte_Dcm_Type.h

8.8.1.10 Dcm_DataElementType_{Data}PrimitiveType

[SWS_Dcm_91062] Definition of ImplementationDataType Dcm_DataEle-

ment_{Data}_PrimitiveType d
Name Dcm_DataElement_{Data}_PrimitiveType
Kind Type
Basetype Variation
Derived from
boolean (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDsp
DataType)} == BOOLEAN) || ({ecuc(Dcm/?DcmConfigSet/?Dcm
Dsp/?DcmDspPid/?DcmDspPidData/?DcmDspPid
Service01.?DcmDspPidDataType)} == BOOLEAN))
float32 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDsp
DataType)} == FLOAT) || ({ecuc(Dcm/?DcmConfigSet/?Dcm
Dsp/?DcmDspPid/?DcmDspPidData/?DcmDspPid
Service01.?DcmDspPidDataType)} == FLOAT))
sint16 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDsp
DataType)} == SINT16) || ({ecuc(Dcm/?DcmConfigSet/?Dcm
Dsp/?DcmDspPid/?DcmDspPidData/?DcmDspPid
Service01.?DcmDspPidDataType)} == SINT16))
sint32 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDsp
DataType)} == SINT32) || ({ecuc(Dcm/?DcmConfigSet/?Dcm
Dsp/?DcmDspPid/?DcmDspPidData/?DcmDspPid
Service01.?DcmDspPidDataType)} == SINT32))
sint8 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDsp
DataType)} == SINT8) || ({ecuc(Dcm/?DcmConfigSet/?Dcm
Dsp/?DcmDspPid/?DcmDspPidData/?DcmDspPid
Service01.?DcmDspPidDataType)} == SINT8))
uint16 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDsp
DataType)} == UINT16) || ({ecuc(Dcm/?DcmConfigSet/?Dcm
Dsp/?DcmDspPid/?DcmDspPidData/?DcmDspPid
Service01.?DcmDspPidDataType)} == UINT16))
uint32 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDsp
DataType)} == UINT32) || ({ecuc(Dcm/?DcmConfigSet/?Dcm
Dsp/?DcmDspPid/?DcmDspPidData/?DcmDspPid
Service01.?DcmDspPidDataType)} == UINT32))
uint8 (({ecuc(Dcm/?DcmConfigSet/?DcmDsp/?DcmDspData.?DcmDsp
DataType)} == UINT8) || ({ecuc(Dcm/?DcmConfigSet/?Dcm
Dsp/?DcmDspPid/?DcmDspPidData/?DcmDspPid
Service01.?DcmDspPidDataType)} == UINT8))
Description –
5

370 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation ((({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType)} ==
(BOOLEAN|[S|U]INT[8|16|32]|FLOAT)) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/Dcm
DspPidData/DcmDspPidService01.DcmDspPidDataType)} ==
(BOOLEAN|[S|U]INT[8|16|32]|FLOAT))) && ({Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidUsePort == USE_DATA_ELEMENT_SPECIFIC_INTERFACES}) && (({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspData/DcmDspDataUsePort)} == USE_DATA_SENDER_RECEIVER) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDsp
PidDataUsePort)} == USE_DATA_SENDER_RECEIVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspPid/DcmDspPidData/DcmDspPidService01/DcmDspPidDataUsePort)} == USE_DATA_
SENDER_RECEIVER_AS_SERVICE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/Dcm
DspDataUsePort)} == USE_DATA_SENDER_RECEIVER_AS_SERVICE) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_SYNCH_CLIENT_
SERVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_
DATA_ASYNCH_CLIENT_SERVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.Dcm
DspDataUsePort)} == USE_DATA_ASYNCH_CLIENT_SERVER_ERROR) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01.DcmDspPidDataUse
Port)} == USE_DATA_SYNCH_CLIENT_SERVER)))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME)})
Available via Rte_Dcm_Type.h

8.8.1.11 Dcm_DataArrayTypeUint8_{Data}Type

[SWS_Dcm_01121] Definition of ImplementationDataType Dcm_DataArrayType

Uint8_{Data}Type d
Name Dcm_DataArrayTypeUint8_{Data}Type
Kind Array Element type uint8
Size (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataByteSize)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.DcmDspPidDataByteSize)})) Elements
Description –
Variation (( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_DATA_
ELEMENT_SPECIFIC_INTERFACES) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Data.DcmDspDataType)} == UINT8_N) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.Dcm
DspDataType)} == UINT8_DYN) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data/DcmDspPidService01.DcmDspPidDataType)} == UINT8_N))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME)})
Available via Rte_Dcm_Type.h

8.8.1.12 {DID}_Struct_DataType

This data type has a different modeling as other data types. The
{DID}_Struct_DataType datatype is modeled as prosa text only. At the time this
specification was created there are no means to visualize this datatype with existing

371 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

AUTOSAR tooling as table as all the other data types. Still AUTOSAR allows modeling
such data types. Simply that they cannot be shown here as table.

[SWS_Dcm_91056] Definition of ImplementationDataType {DID}_Struct_Data

Type d
Name {DID}_Struct_DataType
Kind Structure
Description The elements of this structure data type is a composition of all DcmDspDataElement of the Dcm
DspDid. Example: A DID with the 3 data elements uint32 data1, sint8 data2 and sint16 data 3,
has a structure definition of struct { uint32 data1, sint8 data2, sint16 data 3}.
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == ((USE_ATOMIC_
SENDER_RECEIVER_INTERFACE|| USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_
SERVICE) || USE_ATOMIC_NV_DATA_INTERFACE))
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})
Available via Rte_Dcm_Type.h

8.8.1.13 Dcm_RangeArray_{Range}Type

[SWS_Dcm_01012] Definition of ImplementationDataType Dcm_RangeAr-

ray_{Range}Type d
Name Dcm_RangeArray_{Range}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRangeMaxDataLength)} Elements
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.DcmDspDidRangeUsePort)} == TRUE
Range = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.SHORT-NAME)}
Available via Rte_Dcm_Type.h

372 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.14 Dcm_InfoTypeServicesArray_{VehInfoData}Type

[SWS_Dcm_01013] Definition of ImplementationDataType Dcm_InfoTypeSer-

vicesArray_{VehInfoData}Type d
Name Dcm_InfoTypeServicesArray_{VehInfoData}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfoData.DcmDspVehInfoData
Size)} Elements
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfoData/DcmDspVehInfoData
UsePort)} == TRUE
VehInfoData = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfo
Data.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.15 Dcm_RequestControlServicesInArray_{Tid}Type

[SWS_Dcm_01014] Definition of ImplementationDataType Dcm_RequestControl

ServicesInArray_{Tid}Type d
Name Dcm_RequestControlServicesInArray_{Tid}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl.DcmDspRequestControlInBuffer
Size)} Elements
Description –
Variation Tid = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl.SHORT-NAME)}
Available via Rte_Dcm_Type.h

373 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.16 Dcm_RequestControlServicesOutArray_{Tid}Type

[SWS_Dcm_01015] Definition of ImplementationDataType Dcm_RequestControl

ServicesOutArray_{Tid}Type d
Name Dcm_RequestControlServicesOutArray_{Tid}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl.DcmDspRequestControlOutBuffer
Size)} Elements
Description –
Variation Tid = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.17 Dcm_ScalingInfoArray_{Data}Type

[SWS_Dcm_01017] Definition of ImplementationDataType Dcm_ScalingInfoAr-

ray_{Data}Type d
Name Dcm_ScalingInfoArray_{Data}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDataInfo.DcmDspDataScalingInfoSize)} Elements
Description –
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
ASYNCH_CLIENT_SERVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
UsePort)} == USE_DATA_SYNCH_CLIENT_SERVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspData.DcmDspDataUsePort)} == USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData->DcmDspDataInfoRef.DcmDspDataScalingInfo
Size)} != NULL)
Data = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}
Available via Rte_Dcm_Type.h

374 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.18 Dcm_RequestDataOut_{Routine}_{Signal}PrimitivType

[SWS_Dcm_01018] Definition of ImplementationDataType Dcm_RequestData

Out_{Routine}_{Signal}PrimitivType d
Name Dcm_RequestDataOut_{Routine}_{Signal}PrimitivType
Kind Type

Derived from Basetype Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/Dcm
DspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == FLOAT
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/Dcm
DspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == SINT16
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/Dcm
DspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == SINT32
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/Dcm
DspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == SINT8
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/Dcm
DspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == UINT16
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/Dcm
DspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == UINT32
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/Dcm
DspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == UINT8
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == [U|S]INT[8|16|32]|FLOAT) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/
DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

375 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.19 Dcm_RequestDataIn_{Routine}_{Signal}PrimitiveType

[SWS_Dcm_91054] Definition of ImplementationDataType Dcm_RequestData

In_{Routine}_{Signal}PrimitiveType d
Name Dcm_RequestDataIn_{Routine}_{Signal}PrimitiveType
Kind Type

Derived from Basetype Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/Dcm
DspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== FLOAT
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/Dcm
DspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== SINT16
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/Dcm
DspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== SINT32
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/Dcm
DspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== SINT8
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/Dcm
DspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== UINT16
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/Dcm
DspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== UINT32
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/Dcm
DspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== UINT8
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== [U|S]INT[8|16|32]|FLOAT) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

376 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.20 Dcm_RequestDataOut_{Routine}_{Signal}Type

[SWS_Dcm_91040] Definition of ImplementationDataType Dcm_RequestData

Out_{Routine}_{Signal}Type d
Name Dcm_RequestDataOut_{Routine}_{Signal}Type
Kind Type
Derived from Basetype Variation
Dcm_RequestDataOut_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
Routine}_{Signal}Primitiv RequestRoutineResults/DcmDspRequestRoutineResultsOut/Dcm
Type DspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == ([U|S]INT[8|16|32]|FLOAT))
Dcm_RequestDataOut_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
Routine}_{Signal}ArrayType RequestRoutineResults/DcmDspRequestRoutineResultsOut/Dcm
DspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == ([U|S]INT[8|16|32]|FLOAT)_N)
Dcm_RequestDataOut_{ DcmDspRequestRoutineResultsOutSignal with at least one Dcm
Routine}_{Signal}Structured DspRequestRoutineResultsOutSignalCompositeSignalRef.
Type
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.21 Dcm_RequestDataOut_{Routine}_{Signal}StructuredType

[SWS_Dcm_91119] Definition of ImplementationDataType Dcm_RequestData

Out_{Routine}_{Signal}StructuredType d
Name Dcm_RequestDataOut_{Routine}_{Signal}StructuredType
Kind Structure
Elements structureMember
Type Dcm_RequestDataOut_{Routine}_{Signal}Type
Comment –
Description –
Variation DcmDspRoutine.DcmDspRequestRoutineResults.DcmDspRequestRoutineResultsOut.DcmDsp
RequestRoutineResultsOutSignalCompositePool
Available via Rte_Dcm_Type.h

377 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.22 Dcm_RequestDataIn_{Routine}_{Signal}Type

[SWS_Dcm_91052] Definition of ImplementationDataType Dcm_RequestData

In_{Routine}_{Signal}Type d
Name Dcm_RequestDataIn_{Routine}_{Signal}Type
Kind Type
Derived from Basetype Variation
Dcm_RequestDataIn_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
Routine}_{Signal}Primitive RequestRoutineResults/DcmDspRequestRoutineResultsIn/Dcm
Type DspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== ([U|S]INT[8|16|32|FLOAT)])
Dcm_RequestDataIn_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
Routine}_{Signal}ArrayType RequestRoutineResults/DcmDspRequestRoutineResultsIn/Dcm
DspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== ([U|S]INT[8|16|32]|FLOAT)_N)
Dcm_RequestDataIn_{ DcmDspRequestRoutineResultsInSignal with at least one Dcm
Routine}_{Signal}Structured DspRequestRoutineResultsInSignalCompositeSignalRef.
Type
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.23 Dcm_RequestDataIn_{Routine}_{Signal}StructuredType

[SWS_Dcm_91120] Definition of ImplementationDataType Dcm_RequestData

In_{Routine}_{Signal}StructuredType d
Name Dcm_RequestDataIn_{Routine}_{Signal}StructuredType
Kind Structure
Elements StructureMember
Type Dcm_RequestDataIn_{Routine}_{Signal}Type
Comment –
Description –
Variation DcmDspRoutine.DcmDspRequestRoutineResults.DcmDspRequestRoutineResultsIn.DcmDsp
RequestRoutineResultsInSignalCompositePool
Available via Rte_Dcm_Type.h

378 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.24 Dcm_RequestDataOut_{Routine}_{Signal}ArrayType

[SWS_Dcm_91041] Definition of ImplementationDataType Dcm_RequestData

Out_{Routine}_{Signal}ArrayType d
Name Dcm_RequestDataOut_{Routine}_{Signal}ArrayType
Kind Array

Element type Type Variation

float32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == FLOAT_N)
sint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == SINT16_N)
sint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == SINT32_N)
sint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == SINT8_N)
uint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == UINT16_N)
uint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == UINT32_N)
uint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.DcmDspRoutineSignalType)} == UINT8_N)
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutineParameter
Size)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == ([U|S]INT[8|16|32]|FLOAT)_N) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/
DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

379 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.25 Dcm_RequestDataIn_{Routine}_{Signal}ArrayType

[SWS_Dcm_91055] Definition of ImplementationDataType Dcm_RequestData

In_{Routine}_{Signal}ArrayType d
Name Dcm_RequestDataIn_{Routine}_{Signal}ArrayType
Kind Array

Element type Type Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == FLOAT_N
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == SINT16_N
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == SINT32_N
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == SINT8_N
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == UINT16_N
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == UINT32_N
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequest
RoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == UINT8_N
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDspRoutineParameter
Size)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== ([U|S]INT[8|16|32]|FLOAT)_N) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/Dcm
DspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

380 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.26 Dcm_RequestFlexibleOutArrayData_{Routine}_{Signal}Type

[SWS_Dcm_01019] Definition of ImplementationDataType Dcm_RequestFlexible

OutArrayData_{Routine}_{Signal}Type d
Name Dcm_RequestFlexibleOutArrayData_{Routine}_{Signal}Type
Kind Array Element type uint8
Size {(ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutineParameter
Size} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutineSignal
Type)} == VARIABLE_LENGTH)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.27 Dcm_RequestFlexibleInArrayData_{Routine}_{Signal}Type

[SWS_Dcm_91053] Definition of ImplementationDataType Dcm_RequestFlexible

InArrayData_{Routine}_{Signal}Type d
Name Dcm_RequestFlexibleInArrayData_{Routine}_{Signal}Type
Kind Array Element type uint8
Size {(ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDspRoutineParameter
Size} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/DcmDsp
RequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.DcmDspRoutineSignalType)}
== VARIABLE_LENGTH)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/
DcmDspRequestRoutineResultsIn/DcmDspRequestRoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

381 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.28 Dcm_StartDataIn_{Routine}_{Signal}PrimitivType

[SWS_Dcm_01020] Definition of ImplementationDataType Dcm_StartData

In_{Routine}_{Signal}PrimitivType d
Name Dcm_StartDataIn_{Routine}_{Signal}PrimitivType
Kind Type

Derived from Basetype Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.DcmDspRoutineSignalType)} == FLOAT
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.DcmDspRoutineSignalType)} == SINT16
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.DcmDspRoutineSignalType)} == SINT32
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.DcmDspRoutineSignalType)} == SINT8
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.DcmDspRoutineSignalType)} == UINT16
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.DcmDspRoutineSignalType)} == UINT32
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.DcmDspRoutineSignalType)} == UINT8
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
In/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} == [U|S]INT[8|16|32]|FLOAT) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.29 Dcm_StartDataIn_{Routine}_{Signal}Type

[SWS_Dcm_91042] Definition of ImplementationDataType Dcm_StartData

In_{Routine}_{Signal}Type d
Name Dcm_StartDataIn_{Routine}_{Signal}Type
Kind Type
Derived from Basetype Variation
5

382 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Dcm_StartDataIn_{Routine} ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
_{Signal}PrimitivType StartRoutine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT))
Dcm_StartDataIn_{Routine} ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
_{Signal}ArrayType StartRoutine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT)_N)
Dcm_StartDataIn_{Routine} DcmDspStartRoutineInSignal with at least one DcmDspStart
_{Signal}StructuredType RoutineInSignalCompositeSignalRef.
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.30 Dcm_StartDataIn_{Routine}_{Signal}StructuredType

[SWS_Dcm_91121] Definition of ImplementationDataType Dcm_StartData

In_{Routine}_{Signal}StructuredType d
Name Dcm_StartDataIn_{Routine}_{Signal}StructuredType
Kind Structure
Elements structureMember
Type Dcm_StartDataIn_{Routine}_{Signal}Type
Comment –
Description –
Variation DcmDspRoutine.DcmDspStartRoutine.DcmDspStartRoutineIn.DcmDspStartRoutineInSignal
CompositePool
Available via Rte_Dcm_Type.h

383 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.31 Dcm_StartDataIn_{Routine}_{Signal}ArrayType

[SWS_Dcm_91043] Definition of ImplementationDataType Dcm_StartData

In_{Routine}_{Signal}ArrayType d
Name Dcm_StartDataIn_{Routine}_{Signal}ArrayType
Kind Array

Element type Type Variation

float32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == FLOAT_N
sint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == SINT16_N)
sint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == SINT32_N)
sint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == SINT8_N)
uint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == UINT16_N)
uint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == UINT32_N)
uint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDsp
RoutineSignalType)} == UINT8_N)
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
In/DcmDspStartRoutineInSignal.DcmDspRoutineParameterSize)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
In/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT)_N)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

384 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.32 Dcm_StartDataOut_{Routine}_{Signal}PrimitivType

[SWS_Dcm_01021] Definition of ImplementationDataType Dcm_StartData

Out_{Routine}_{Signal}PrimitivType d
Name Dcm_StartDataOut_{Routine}_{Signal}PrimitivType
Kind Type

Derived from Basetype Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.DcmDspRoutineSignalType)} == FLOAT
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.DcmDspRoutineSignalType)} == SINT16
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.DcmDspRoutineSignalType)} == SINT32
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.DcmDspRoutineSignalType)} == SINT8
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.DcmDspRoutineSignalType)} == UINT16
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.DcmDspRoutineSignalType)} == UINT32
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StartRoutine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.DcmDspRoutineSignalType)} == UINT8
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
Out/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} == [U|S]INT[8|16|32]|FLOAT) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.33 Dcm_StartDataOut_{Routine}_{Signal}Type

[SWS_Dcm_91044] Definition of ImplementationDataType Dcm_StartData

Out_{Routine}_{Signal}Type d
Name Dcm_StartDataOut_{Routine}_{Signal}Type
Kind Type
Derived from Basetype Variation
5

385 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Dcm_StartDataOut_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
Routine}_{Signal}Primitiv StartRoutine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Type Signal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT))
Dcm_StartDataOut_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
Routine}_{Signal}ArrayType StartRoutine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT)_N)
Dcm_StartDataOut_{ DcmDspStartRoutineOutSignal with at least one DcmDspStart
Routine}_{Signal}Structured RoutineOutSignalCompositeSignalRef.
Type
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.34 Dcm_StartDataOut_{Routine}_{Signal}StructuredType

[SWS_Dcm_91122] Definition of ImplementationDataType Dcm_StartData

Out_{Routine}_{Signal}StructuredType d
Name Dcm_StartDataOut_{Routine}_{Signal}StructuredType
Kind Structure
Elements structureMember
Type Dcm_StartDataOut_{Routine}_{Signal}Type
Comment –
Description –
Variation DcmDspRoutine.DcmDspStartRoutine.DcmDspStartRoutineOut.DcmDspStartRoutineOutSignal
CompositePool
Available via Rte_Dcm_Type.h

386 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.35 Dcm_StartDataOut_{Routine}_{Signal}ArrayType

[SWS_Dcm_91045] Definition of ImplementationDataType Dcm_StartData

Out_{Routine}_{Signal}ArrayType d
Name Dcm_StartDataOut_{Routine}_{Signal}ArrayType
Kind Array

Element type Type Variation

float32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == FLOAT_N
sint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == SINT16_N)
sint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == SINT32_N)
sint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == SINT8_N)
uint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == UINT16_N)
uint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == UINT32_N)
uint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.Dcm
DspRoutineSignalType)} == UINT8_N)
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
Out/DcmDspStartRoutineOutSignal.DcmDspRoutineParameterSize)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
Out/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT)_
N) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

387 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.36 Dcm_StartFlexibleInArrayData_{Routine}_{Signal}Type

[SWS_Dcm_01022] Definition of ImplementationDataType Dcm_StartFlexibleIn

ArrayData_{Routine}_{Signal}Type d
Name Dcm_StartFlexibleInArrayData_{Routine}_{Signal}Type
Kind Array Element type uint8
Size {(ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
In/DcmDspStartRoutineInSignal.DcmDspRoutineParameterSize} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
In/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.37 Dcm_StartFlexibleOutArrayData_{Routine}_{Signal}Type

[SWS_Dcm_01023] Definition of ImplementationDataType Dcm_StartFlexibleOut

ArrayData_{Routine}_{Signal}Type d
Name Dcm_StartFlexibleOutArrayData_{Routine}_{Signal}Type
Kind Array Element type uint8
Size {(ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
Out/DcmDspStartRoutineOutSignal.DcmDspRoutineParameterSize} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStartRoutine
Out/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

388 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.38 Dcm_StopDataIn_{Routine}_{Signal}PrimitivType

[SWS_Dcm_01024] Definition of ImplementationDataType Dcm_StopData

In_{Routine}_{Signal}PrimitivType d
Name Dcm_StopDataIn_{Routine}_{Signal}PrimitivType
Kind Type

Derived from Basetype Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineIn/DcmDspStopRoutineIn
Signal.DcmDspRoutineSignalType)} == FLOAT
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineIn/DcmDspStopRoutineIn
Signal.DcmDspRoutineSignalType)} == SINT16
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineIn/DcmDspStopRoutineIn
Signal.DcmDspRoutineSignalType)} == SINT32
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineIn/DcmDspStopRoutineIn
Signal.DcmDspRoutineSignalType)} == SINT8
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineIn/DcmDspStopRoutineIn
Signal.DcmDspRoutineSignalType)} == UINT16
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineIn/DcmDspStopRoutineIn
Signal.DcmDspRoutineSignalType)} == UINT32
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineIn/DcmDspStopRoutineIn
Signal.DcmDspRoutineSignalType)} == UINT8
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
In/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.39 Dcm_StopDataIn_{Routine}_{Signal}Type

[SWS_Dcm_91046] Definition of ImplementationDataType Dcm_StopData

In_{Routine}_{Signal}Type d
Name Dcm_StopDataIn_{Routine}_{Signal}Type
Kind Type
Derived from Basetype Variation
5

389 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Dcm_StopDataIn_{Routine} ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
_{Signal}PrimitivType StopRoutine/DcmDspStopRoutineIn/DcmDspStopRoutineIn
Signal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT))
Dcm_StopDataIn_{Routine} ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
_{Signal}ArrayType StopRoutine/DcmDspStopRoutineIn/DcmDspStopRoutineIn
Signal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT)_N)
Dcm_StopDataIn_{Routine} DcmDspStopRoutineInSignal with at least one DcmDspStop
_{Signal}StructuredType RoutineInSignalCompositeSignalRef.
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.40 Dcm_StopDataIn_{Routine}_{Signal}StructuredType

[SWS_Dcm_91123] Definition of ImplementationDataType Dcm_StopData

In_{Routine}_{Signal}StructuredType d
Name Dcm_StopDataIn_{Routine}_{Signal}StructuredType
Kind Structure
Elements structureMember
Type Dcm_StopDataIn_{Routine}_{Signal}Type
Comment –
Description –
Variation DcmDspRoutine.DcmDspStopRoutine.DcmDspStopRoutineIn.DcmDspStopRoutineInSignal
CompositePool
Available via Rte_Dcm_Type.h

390 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.41 Dcm_StopDataIn_{Routine}_{Signal}ArrayType

[SWS_Dcm_91047] Definition of ImplementationDataType Dcm_StopData

In_{Routine}_{Signal}ArrayType d
Name Dcm_StopDataIn_{Routine}_{Signal}ArrayType
Kind Array

Element type Type Variation

float32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == FLOAT_N
sint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == SINT16_N)
sint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == SINT32_N)
sint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == SINT8_N)
uint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == UINT16_N)
uint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == UINT32_N)
uint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDsp
RoutineSignalType)} == UINT8_N)
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
In/DcmDspStopRoutineInSignal.DcmDspRoutineParameterSize)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
In/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT)_N)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

391 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.42 Dcm_StopDataOut_{Routine}_{Signal}PrimitivType

[SWS_Dcm_01025] Definition of ImplementationDataType Dcm_StopData

Out_{Routine}_{Signal}PrimitivType d
Name Dcm_StopDataOut_{Routine}_{Signal}PrimitivType
Kind Type

Derived from Basetype Variation

float32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.DcmDspRoutineSignalType)} == FLOAT
sint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.DcmDspRoutineSignalType)} == SINT16
sint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.DcmDspRoutineSignalType)} == SINT32
sint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.DcmDspRoutineSignalType)} == SINT8
uint16 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.DcmDspRoutineSignalType)} == UINT16
uint32 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.DcmDspRoutineSignalType)} == UINT32
uint8 {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
StopRoutine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.DcmDspRoutineSignalType)} == UINT8
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
Out/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} == [U|S]INT[8|16|32]|FLOAT) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.43 Dcm_StopDataOut_{Routine}_{Signal}Type

[SWS_Dcm_91048] Definition of ImplementationDataType Dcm_StopData

Out_{Routine}_{Signal}Type d
Name Dcm_StopDataOut_{Routine}_{Signal}Type
Kind Type
Derived from Basetype Variation
5

392 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Dcm_StopDataOut_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
Routine}_{Signal}Primitiv StopRoutine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Type Signal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT))
Dcm_StopDataOut_{ ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
Routine}_{Signal}ArrayType StopRoutine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.DcmDspRoutineSignalType)} ==
([U|S]INT[8|16|32]|FLOAT)_N)
Dcm_StopDataOut_{ DcmDspStopRoutineOutSignal with at least one DcmDspStop
Routine}_{Signal}Structured RoutineOutSignalCompositeSignalRef.
Type
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.44 Dcm_StopDataOut_{Routine}_{Signal}StructuredType

[SWS_Dcm_91124] Definition of ImplementationDataType Dcm_StopData

Out_{Routine}_{Signal}StructuredType d
Name Dcm_StopDataOut_{Routine}_{Signal}StructuredType
Kind Structure
Elements structureMember
Type Dcm_StopDataOut_{Routine}_{Signal}Type
Comment –
Description –
Variation DcmDspRoutine.DcmDspStopRoutine.DcmDspStopRoutineOut.DcmDspStopRoutineOutSignal
CompositePool
Available via Rte_Dcm_Type.h

393 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.45 Dcm_StopDataOut_{Routine}_{Signal}ArrayType

[SWS_Dcm_91049] Definition of ImplementationDataType Dcm_StopData

Out_{Routine}_{Signal}ArrayType d
Name Dcm_StopDataOut_{Routine}_{Signal}ArrayType
Kind Array

Element type Type Variation

float32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == FLOAT_N
sint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == SINT16_N)
sint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == SINT32_N)
sint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == SINT8_N)
uint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == UINT16_N)
uint32 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == UINT32_N)
uint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.Dcm
DspRoutineSignalType)} == UINT8_N)
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
Out/DcmDspStopRoutineOutSignal.DcmDspRoutineParameterSize)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
Out/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} == ([U|S]INT[8|16|32]|FLOAT)_
N) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

394 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.46 Dcm_StopFlexibleInArrayData_{Routine}_{Signal}Type

[SWS_Dcm_01026] Definition of ImplementationDataType Dcm_StopFlexibleIn

ArrayData_{Routine}_{Signal}Type d
Name Dcm_StopFlexibleInArrayData_{Routine}_{Signal}Type
Kind Array Element type uint8
Size {(ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
In/DcmDspStopRoutineInSignal.DcmDspRoutineParameterSize} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
In/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.47 Dcm_StopFlexibleOutArrayData_{Routine}_{Signal}Type

[SWS_Dcm_01027] Definition of ImplementationDataType Dcm_StopFlexibleOut

ArrayData_{Routine}_{Signal}Type d
Name Dcm_StopFlexibleOutArrayData_{Routine}_{Signal}Type
Kind Array Element type uint8
Size {(ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
Out/DcmDspStopRoutineOutSignal.DcmDspRoutineParameterSize} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStopRoutine
Out/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
&& ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRoutineUsePort)} == TRUE)
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Available via Rte_Dcm_Type.h

395 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.48 Dcm_KeyArray_{SecurityLevel}Type

[SWS_Dcm_01028] Definition of ImplementationDataType Dcm_KeyAr-

ray_{SecurityLevel}Type d
Name Dcm_KeyArray_{SecurityLevel}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurityKey
Size)} Elements
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurityUse
Port)} == USE_ASYNCH_CLIENT_SERVER
SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurity
Row.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.49 Dcm_SeedArray_{SecurityLevel}Type

[SWS_Dcm_01029] Definition of ImplementationDataType Dcm_SeedAr-

ray_{SecurityLevel}Type d
Name Dcm_SeedArray_{SecurityLevel}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecuritySeed
Size)} Elements
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurityUse
Port)} == USE_ASYNCH_CLIENT_SERVER
SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurity
Row.SHORT-NAME)}
Available via Rte_Dcm_Type.h

396 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.50 Dcm_SecurityAccessDataRecordArray_{SecurityLevel}Type

[SWS_Dcm_01159] Definition of ImplementationDataType Dcm_SecurityAccess

DataRecordArray_{SecurityLevel}Type d
Name Dcm_SecurityAccessDataRecordArray_{SecurityLevel}Type
Kind Array Element type uint8
Size {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp/DcmDspSecurity/DcmDspSecurityRow/DcmDsp
SecurityADRSize)} Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurityUse
Port)} == USE_ASYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Security/DcmDspSecurityRow.DcmDspSecurityADRSize)} != NULL)
SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurity
Row.SHORT-NAME)}
Available via Rte_Dcm_Type.h

8.8.1.51 Dcm_RequestDataArrayType

[SWS_Dcm_01165] Definition of ImplementationDataType Dcm_RequestDataAr-

rayType d
Name Dcm_RequestDataArrayType
Kind Array Element type uint8
Size (MAX({ecuc(Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocol
RxBufferID->DcmDslBuffer.DcmDslBufferSize)}) -1) Elements
Description –
Variation –
Available via Rte_Dcm_Type.h

397 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.52 Dcm_ControlMask_{DID}Type

[SWS_Dcm_01320] Definition of ImplementationDataType Dcm_Control

Mask_{DID}Type d
Name Dcm_ControlMask_{DID}Type
Kind Type
Derived from Basetype Variation
Dcm_ControlMask_{Data} (( ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
ArrayType InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
MaskSize)} >= 0x05)
&& (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataUsePort)} == (USE_DATA_ SYNCH_CLIENT_SERVER ||
USE_DATA_ASYNCH_CLIENT_SERVER || USE_DATA_
ASYNCH_CLIENT_SERVER_ERROR)))
Dcm_ControlMask_{Data} ({ecuc(Dcm/DcmConfigSet/ DcmDsp/DcmDspDid/ DcmDspDid
_PrimitiveType InfoRef->DcmDspDidInfo/ DcmDspDidControl/ DcmDspDidControl
MaskSize)} <= 0x04)
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
SYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_
CLIENT_SERVER_ERROR)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlEnableMask)} == NULL)
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})
Available via Rte_Dcm_Type.h

8.8.1.53 Dcm_inputOutputControlParameterType

[SWS_Dcm_01305] Definition of ImplementationDataType Dcm_InputOutputCon-

trolParameterType d
Name Dcm_InputOutputControlParameterType
Kind Type
Derived from uint8
Range DCM_RETURN_ 0x00 returnControlToECU
CONTROL_TO_ECU
DCM_RESET_TO_ 0x01 resetToDefault
DEFAULT
DCM_FREEZE_ 0x02 freezeCurrentState
CURRENT_STATE
DCM_SHORT_TERM_ 0x03 shortTermAdjustment
ADJUSTMENT
DCM_IDLE 0xff Idle state, no request in
processing (initial value)
Description –
5

398 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation –
Available via Rte_Dcm_Type.h

8.8.1.54 Dcm_IOOperationRequest_{DID}Type

[SWS_Dcm_01306] Definition of ImplementationDataType Dcm_IOOperationRe-

quest_{DID}Type d
Name Dcm_IOOperationRequest_{DID}Type
Kind Structure
Elements inputOutputControlParameter
Type Dcm_InputOutputControlParameterType
Comment –
controlEnableMask
Type Dcm_Cemr_{DID}Type
Comment –
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE )) ||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/Dcm
DspDidUsePort)} == (USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE ))&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/DcmDsp
DidControl)} != NULL)
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})
Available via Rte_Dcm_Type.h

8.8.1.55 Dcm_IOOperationResponseType

[SWS_Dcm_01307] Definition of ImplementationDataType Dcm_IOOperationRe-

sponseType d
Name Dcm_IOOperationResponseType
Kind Type
Derived from uint8
Range DCM_POSITIVE_ 0x00 positive response (similar to E_
RESPONSE OK)
DCM_GENERAL_REJECT 0x10 NRC generalReject
DCM_BUSY_REPEAT_ 0x21 NRC busyRepeatRequest
REQUEST
5

399 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
DCM_CONDITIONS_NOT_ 0x22 NRC conditionsNotCorrect
CORRECT
DCM_FAILURE_ 0x26 NRC FailurePreventsExecutionOf
PREVENTS_EXECUTION RequestedAction
DCM_REQUEST_OUT_ 0x31 NRC requestOutOfRange
OF_RANGE
DCM_RESPONSE_ 0x78 ResponsePending (similar to E_
PENDING PENDING)
Description –
Variation –
Available via Rte_Dcm_Type.h

8.8.1.56 Dcm_DidSupportedType

[SWS_Dcm_01138] Definition of ImplementationDataType Dcm_DidSupported

Type d
Name Dcm_DidSupportedType
Kind Type
Derived from uint8
Range DCM_DID_SUPPORTED 0x00 –
DCM_DID_NOT_ 0x01 –
SUPPORTED
Description –
Variation –
Available via Rte_Dcm_Type.h

8.8.1.57 Dcm_FileAndDirNameType

[SWS_Dcm_91066] Definition of ImplementationDataType Dcm_FileAndDirName

Type d
Name Dcm_FileAndDirNameType
Kind Array Element type uint8
Size ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer.DcmRequestFileTransferMax
FileAndDirName)}) Elements
Description –
5

400 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransferUse
Port)} == TRUE)
Available via Rte_Dcm_Type.h

8.8.1.58 Dcm_ResponseDataArrayType

[SWS_Dcm_91064] Definition of ImplementationDataType Dcm_ResponseData

ArrayType d
Name Dcm_ResponseDataArrayType
Kind Array Element type uint8
Size (MAX({ecuc(Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDslProtocol
TxBufferRef->DcmDslBuffer.DcmDslBufferSize)}) -1) Elements
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransferUse
Port)} == TRUE)
Available via Rte_Dcm_Type.h

8.8.1.59 Dcm_AuthenticationRoleType

[SWS_Dcm_91068] Definition of ImplementationDataType Dcm_Authentication

RoleType d
Name Dcm_AuthenticationRoleType
Kind Array Element type uint8
Size ({ecuc(Dcm/DcmDsp/DcmDspAuthentication.DcmDspAuthenticationRoleSize)}) Elements
Description –
Variation –
Available via Rte_Dcm_Type.h

401 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.60 Dcm_ControlMask_{Data}ArrayType

[SWS_Dcm_91050] Definition of ImplementationDataType Dcm_Control

Mask_{Data}ArrayType d
Name Dcm_ControlMask_{Data}ArrayType
Kind Array Element type uint8
Size ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidControlMaskSize)}) Elements
Description The current DcmDspData is referenced by the DcmDspDID.
Variation (( ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidControlMaskSize)} >= 0x05) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspData.DcmDspDataUsePort)} == (USE_DATA_ SYNCH_CLIENT_SERVER || USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
Available via Rte_Dcm_Type.h

8.8.1.61 Dcm_ControlMask_{Data}PrimitiveType

[SWS_Dcm_91089] Definition of ImplementationDataType Dcm_Control

Mask_{Data}_PrimitiveType d
Name Dcm_ControlMask_{Data}_PrimitiveType
Kind Type
Derived from Basetype Variation
uint16 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
MaskSize)} == 0x02)
uint32 (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
MaskSize)}== 0x03)||{ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Did/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/
DcmDspDidControlMaskSize)}== 0x04))
uint8 ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
MaskSize)} == 0x01)
Description The current DcmDspData is referenced by the DcmDspDID.
Variation ( ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
SYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_
CLIENT_SERVER_ERROR)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlEnableMask)} == NULL) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidControlMaskSize)} <= 0x04))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
Available via Rte_Dcm_Type.h

402 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.1.62 Dcm_Cemr_{DID}Type

[SWS_Dcm_91087] Definition of ImplementationDataType Dcm_Cemr_{DID}Type

d
Name Dcm_Cemr_{DID}Type
Kind Bitfield
Derived from Dcm_ControlMask_{DID}Type
Elements Variable bit
Kind bit
Name ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidControl. DcmDspDidControlEnable
Mask.SHORT-NAME)}
Mask 2ˆ (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDsp
DidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)} * 8 - 1) - {ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDid
Control/DcmDspDidControlEnableMask/DcmDspDidControlMaskBitPosition)})
Descrip- Bitmask of data element in control enable mask record.
tion
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidControl/DcmDspDidControlEnableMask)} !=
NULL)
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}
Available via Rte_Dcm_Type.h

The Dcm_Cemr_Type data type defines a bitfield text table with a single mask entry
for each valid bit in the control enable mask record. A value of 0 in the DcmDspDid-
ControlMaskBitPosition represents the most significant bit in the most significant
byte of the control enable mask. Therefore it is mapped to Bit 7 (0x80) of the first byte
of the control enable mask. In a two byte CEMR the bit position 0 would map to 0x8000,
the bit position 1 would map to 0x4000, ... . Also this is a unusual representation it
helps to keep the bits stable if the size of the CEMR is changed. The definition of the
bits is directly defined by DcmDspDidControlEnableMask.

8.8.2 Sender-Receiver-Interfaces

Using the concepts of the SW-C template, the interface is defined as follows if Sender-
Receiver interface is used (DcmDspDataUsePort set to
USE_DATA_SENDER_RECEIVER ||USE_DATA_SENDER_RECEIVER_AS_SERVICE):

403 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.2.1 DataServices_{DID}

[SWS_Dcm_91057] Definition of SenderReceiverInterface DataServices_{DID}

Upstream requirements: RS_Diag_04218

d
Name DataServices_{DID}
Comment –
IsService ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_ATOMIC_
SENDER_RECEIVER_INTERFACE_AS_SERVICE)
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/Dcm
DspDidUsePort)} == (USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE))
DID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}
Data Elements data
Type {DID}_Struct_DataType
Variation DID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}

8.8.2.2 DataServices_{Data}

[SWS_Dcm_00687] Definition of SenderReceiverInterface DataServices_{Data} d

Name DataServices_{Data}
Comment –
IsService (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataUsePort)} == USE_DATA_
SENDER_RECEIVER_AS_SERVICE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/Dcm
DspPidData/DcmDspPidService01/DcmDspPidDataUsePort)} == USE_DATA_SENDER_
RECEIVER_AS_SERVICE))
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_DATA_
ELEMENT_SPECIFIC_INTERFACES)&&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/
DcmDspDataUsePort)} == (USE_DATA_SENDER_RECEIVER ||USE_DATA_SENDER_
RECEIVER_AS_SERVICE))) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data/DcmDspPidService01/DcmDspPidDataUsePort)} ==(USE_DATA_SENDER_RECEIVER
||USE_DATA_SENDER_RECEIVER_AS_SERVICE))
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME})
Data Elements data
Type Dcm_DataElement_{Data}Type
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data.SHORT-NAME)})

404 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.2.3 IOControlRequest_{DID}

[SWS_Dcm_01308] Definition of SenderReceiverInterface IOControlRe-

quest_{DID} d
Name IOControlRequest_{DID}
Comment Attention: controlState is only valid in case of IOOperationRequest is set to shortTerm
Adjustment.
The DCM provides a byte stream which could be transformed via transformer into an complex
type.
IsService true
Variation ((({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE ) ||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/Dcm
DspDidUsePort)} == USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_
SERVICE))&&({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDsp
DidInfo/ DcmDspDidControl)}!= NULL)) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/
DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)}== DCM_
CONTROLMASK_EXTERNAL)))
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})

Data Elements underControl

Type Dcm_Cemr_{DID}Type
Variation –
IOOperationRequest
Type Dcm_IOOperationRequest_{DID}Type
Variation DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})
controlState
Type {DID}_Struct_DataType
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidShortTermAdjustment)} == True)
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})

8.8.2.4 IOControlResponse_{DID}

[SWS_Dcm_01309] Definition of SenderReceiverInterface IOControlRe-

sponse_{DID} d
Name IOControlResponse_{DID}
Comment –
IsService true
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} ==(USE_ATOMIC_
SENDER_RECEIVER_INTERFACE || USE_ATOMIC_SENDER_RECEIVER_INTERFACE_
AS_SERVICE))) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/Dcm
DspDidControl)} != NULL))
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})
Data Elements IOOperationResponse
5

405 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type Dcm_IOOperationResponseType
Variation –

8.8.3 Client-Server-Interfaces

8.8.3.1 SecurityAccess_{SecurityLevel}

Provides functions required for the UDS Service SecurityAccess (see

[SWS_Dcm_00323],[SWS_Dcm_00862] and [SWS_Dcm_00863]).
Using the concepts of the SW-C template, the interface is defined as fol-
lows if ClientServer interface is used (DcmDspSecurityUsePort set to or
USE_ASYNCH_CLIENT_SERVER):

[SWS_Dcm_00685] Definition of ClientServerInterface SecurityAccess_{Security

Level} d
Name SecurityAccess_{SecurityLevel}
Comment –
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurity
UsePort)} == USE_ASYNCH_CLIENT_SERVER
SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurity
Row.SHORT-NAME)}
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.
11 DCM_E_COMPARE_ Key did not match.
KEY_FAILED

Operation CompareKey
Comment –
Mapped to API Xxx_CompareKey
Variation –
Parameters Key
Type Dcm_KeyArray_{SecurityLevel}Type
Direction IN
Comment Key, which needs to be compared
Variation SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDsp
SecurityRow.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
5

406 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment return Error Code
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_COMPARE_KEY_FAILED

Operation GetSecurityAttemptCounter
Comment Restore the attempt counter from the application
Mapped to API Xxx_GetSecurityAttemptCounter
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurity
AttemptCounterEnabled)} == TRUE
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
AttemptCounter
Type uint8
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation GetSeed
Comment –
Mapped to API Xxx_GetSeed
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurity
ADRSize)} == NULL)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
Seed
Type Dcm_SeedArray_{SecurityLevel}Type
Direction OUT
Comment Pointer for provided seed
Variation SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDsp
SecurityRow.SHORT-NAME)}
ErrorCode
5

407 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation GetSeed
Comment –
Mapped to API Xxx_GetSeed
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurity
ADRSize)} != NULL)
SecurityAccessDataRecord
Parameters
Type Dcm_SecurityAccessDataRecordArray_{SecurityLevel}Type
Direction IN
Comment –
Variation SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDsp
SecurityRow.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
Seed
Type Dcm_SeedArray_{SecurityLevel}Type
Direction OUT
Comment Pointer for provided seed
Variation SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDsp
SecurityRow.SHORT-NAME)}
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation SetSecurityAttemptCounter
Comment Store the attempt counter in the application
Mapped to API Xxx_SetSecurityAttemptCounter
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurity
AttemptCounterEnabled)} == TRUE
Parameters OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
5

408 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation –
AttemptCounter
Type uint8
Direction IN
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

8.8.3.2 DataServices_{Data}

Using the concepts of the SW-C template, the interface is defined as fol-
lows if ClientServer interface is used (DcmDspDataUsePort set to USE_-
DATA_SYNCH_CLIENT_SERVER or USE_DATA_ASYNCH_CLIENT_SERVER or
USE_DATA_ASYNCH_CLIENT_SERVER_ERROR):

[SWS_Dcm_00686] Definition of ClientServerInterface DataServices_{Data} d

Name DataServices_{Data}
Comment –
IsService true
Variation ((( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_DATA_
ELEMENT_SPECIFIC_INTERFACES)) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Data.DcmDspDataUsePort)} == USE_DATA_SYNCH_CLIENT_SERVER) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} ==USE_DATA_ASYNCH_CLIENT_
SERVER) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)}
==USE_DATA_ASYNCH_CLIENT_SERVER_ERROR) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspPid/DcmDspPidData/DcmDspPidService01.DcmDspPidDataUsePort)} ==USE_DATA_
SYNCH_CLIENT_SERVER) )
Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME)})
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.

Operation ConditionCheckRead
Comment –
Mapped to API Xxx_ConditionCheckRead
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidRead)} != NULL) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataConditionCheckReadFnc
Used)} == TRUE)
5

409 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ConditionCheckRead
Comment –
Mapped to API Xxx_ConditionCheckRead
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidRead)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspData
ConditionCheckReadFncUsed)} == TRUE)
Parameters ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation FreezeCurrentState
Comment –
Mapped to API Xxx_FreezeCurrentState
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreeze
CurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} != DCM_
CONTROLMASK_EXTERNAL)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
5

410 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation FreezeCurrentState
Comment –
Mapped to API Xxx_FreezeCurrentState
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreeze
CurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)} <= 0x04)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation FreezeCurrentState
Comment –
Mapped to API Xxx_FreezeCurrentState
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreeze
CurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)} >= 0x05)

Parameters OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
5

411 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation FreezeCurrentState
Comment –
Mapped to API Xxx_FreezeCurrentState
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidFreezeCurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} != DCM_CONTROLMASK_EXTERNAL)
Parameters ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation FreezeCurrentState
Comment –
Mapped to API Xxx_FreezeCurrentState
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidFreezeCurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask
Size)} <= 0x04)
controlMask
Parameters
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

412 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Operation FreezeCurrentState
Comment –
Mapped to API Xxx_FreezeCurrentState
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidFreezeCurrentState)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask
Size)} >= 0x05)
controlMask
Parameters
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation GetScalingInformation
Comment –
Mapped to API Xxx_GetScalingInformation
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDspDataInfoRef->DcmDspDataScaling
InfoSize)} != NULL)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ScalingInfo
Type Dcm_ScalingInfoArray_{Data}Type
Direction OUT
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

413 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Operation GetScalingInformation
Comment –
Mapped to API Xxx_GetScalingInformation
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/DcmDsp
DataInfoRef->DcmDspDataScalingInfoSize)} != NULL)
ScalingInfo
Parameters
Type Dcm_ScalingInfoArray_{Data}Type
Direction OUT
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ReadData
Comment The server is not allowed to return E_NOT_OK, but shall always provide a valid data value (e.g.
a default/replacement value in an error-case) to Dcm/Dem nevertheless the signature of the
operation includes E_NOT_OK to ensure compatibility between server runnable and RTE Call
API, since the RTE may return negative Std_Return values in certain cases (e.g. partition of
server stopped)
Mapped to API Xxx_ReadData
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
ASYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/Dcm
DspDidRead)} != NULL)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
Data
Type Dcm_DataElement_{Data}Type
Direction OUT
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data.SHORT-NAME)})
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ReadData
Comment The server is not allowed to return E_NOT_OK, but shall always provide a valid data value (e.g.
a default/replacement value in an error-case) to Dcm/Dem nevertheless the signature of the
operation includes E_NOT_OK to ensure compatibility between server runnable and RTE Call
API, since the RTE may return negative Std_Return values in certain cases (e.g. partition of
server stopped)
5

414 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Mapped to API Xxx_ReadData
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
ASYNCH_CLIENT_SERVER_ERROR) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid
Info/DcmDspDidRead)} != NULL)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
Data
Type Dcm_DataElement_{Data}Type
Direction OUT
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ReadData
Comment The server is not allowed to return E_NOT_OK, but shall always provide a valid data value (e.g.
a default/replacement value in an error-case) to Dcm/Dem nevertheless the signature of the
operation includes E_NOT_OK to ensure compatibility between server runnable and RTE Call
API, since the RTE may return negative Std_Return values in certain cases (e.g. partition of
server stopped)
Mapped to API Xxx_ReadData
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/Dcm
DspDidRead)} != NULL) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/
DcmDspPidService01.DcmDspPidDataUsePort)} == USE_DATA_SYNCH_CLIENT_SERVER))
Parameters Data
Type Dcm_DataElement_{Data}Type
Direction OUT
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPid
Data.SHORT-NAME)})
Possible Errors E_OK
E_NOT_OK

Operation ReadDataLength
Comment –
Mapped to API Xxx_ReadDataLength
5

415 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidRead)} != NULL) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType} == UINT8_DYN)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataLength
Type uint16
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ReadDataLength
Comment –
Mapped to API Xxx_ReadDataLength
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidRead)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType}
== UINT8_DYN)
Parameters DataLength
Type uint16
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ResetToDefault
Comment –
Mapped to API Xxx_ResetToDefault
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidResetTo
Default)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} != DCM_
CONTROLMASK_EXTERNAL)

Parameters OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
5

416 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ResetToDefault
Comment –
Mapped to API Xxx_ResetToDefault
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidResetTo
Default)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)} <= 0x04)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ResetToDefault
Comment –
Mapped to API Xxx_ResetToDefault
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidResetTo
Default)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)} >= 0x05)

Parameters OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
controlMask
5

417 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ResetToDefault
Comment –
Mapped to API Xxx_ResetToDefault
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidResetToDefault)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} != DCM_CONTROLMASK_EXTERNAL)
Parameters ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ResetToDefault
Comment –
Mapped to API Xxx_ResetToDefault
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidResetToDefault)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask
Size)} <= 0x04)
controlMask
Parameters
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

418 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Operation ResetToDefault
Comment –
Mapped to API Xxx_ResetToDefault
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidResetToDefault)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask
Size)} >= 0x05)
controlMask
Parameters
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ReturnControlToECU
Comment –
Mapped to API Xxx_ReturnControlToECU
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
SYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER || USE_DATA_
ASYNCH_CLIENT_SERVER_ERROR)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid
Info/DcmDspDidControl/DcmDspDidFreezeCurrentState)} == TRUE) || ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidResetToDefault)} == TRUE) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} != DCM_
CONTROLMASK_EXTERNAL)
Parameters ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ReturnControlToECU
Comment –
Mapped to API Xxx_ReturnControlToECU
5

419 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreeze
CurrentState)} == TRUE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidResetToDefault)} == TRUE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/
DcmDspDidControlMask)} == DCM_CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/Dcm
DspDidControlMaskSize)} <= 0x04)
controlMask
Parameters
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ReturnControlToECU
Comment –
Mapped to API Xxx_ReturnControlToECU
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidFreeze
CurrentState)} == TRUE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDid
Control/DcmDspDidResetToDefault)} == TRUE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDidInfo/DcmDspDidControl/DcmDspDidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/
DcmDspDidControlMask)} == DCM_CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/Dcm
DspDidControlMaskSize)} >= 0x05)
controlMask
Parameters
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ShortTermAdjustment
Comment –
Mapped to API Xxx_ShortTermAdjustment
5

420 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataType} != UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} != DCM_
CONTROLMASK_EXTERNAL)
ControlStateInfo
Parameters
Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ShortTermAdjustment
Comment –
Mapped to API Xxx_ShortTermAdjustment
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataType} != UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)} <= 0x04)
ControlStateInfo
Parameters
Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
5

421 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ShortTermAdjustment
Comment –
Mapped to API Xxx_ShortTermAdjustment
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataType} != UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)} >= 0x05)
ControlStateInfo
Parameters Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ShortTermAdjustment
Comment –
Mapped to API Xxx_ShortTermAdjustment
5

422 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataType} == UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} != DCM_
CONTROLMASK_EXTERNAL)
ControlStateInfo
Parameters Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ShortTermAdjustment
Comment –
Mapped to API Xxx_ShortTermAdjustment
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataType} == UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)} <= 0x04)

Parameters ControlStateInfo
Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
5

423 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ShortTermAdjustment
Comment –
Mapped to API Xxx_ShortTermAdjustment
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidControl/DcmDspDidShort
TermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDsp
DataType} == UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask)} == DCM_
CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMaskSize)} >= 0x05)
ControlStateInfo
Parameters
Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
5

424 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ShortTermAdjustment
Comment –
Mapped to API Xxx_ShortTermAdjustment
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspData.DcmDspDataType} != UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} != DCM_CONTROLMASK_EXTERNAL)
ControlStateInfo
Parameters
Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ShortTermAdjustment
Comment –
Mapped to API Xxx_ShortTermAdjustment
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspData.DcmDspDataType} != UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask
Size)} <= 0x04)

Parameters ControlStateInfo
Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
controlMask
Type Dcm_ControlMask_{DID}Type
5

425 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ShortTermAdjustment
Comment –
Mapped to API Xxx_ShortTermAdjustment
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspData.DcmDspDataType} == UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} != DCM_CONTROLMASK_EXTERNAL)
ControlStateInfo
Parameters
Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ShortTermAdjustment
Comment –
Mapped to API Xxx_ShortTermAdjustment
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspData.DcmDspDataType} == UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask
Size)} <= 0x04)
Parameters ControlStateInfo
Type Dcm_DataArrayTypeUint8_{Data}Type
5

426 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ShortTermAdjustment
Comment –
Mapped to API Xxx_ShortTermAdjustment
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidControl/DcmDspDidShortTermAdjustment)} == TRUE) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspData.DcmDspDataType} == UINT8_DYN) && ({ecuc(Dcm/DcmConfigSet/Dcm
Dsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControl
Mask)} == DCM_CONTROLMASK_EXTERNAL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl/DcmDspDidControlMask
Size)} >= 0x05)
ControlStateInfo
Parameters
Type Dcm_DataArrayTypeUint8_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
Variation –
controlMask
Type Dcm_ControlMask_{DID}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
5

427 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation WriteData
Comment –
Mapped to API Xxx_WriteData
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidWrite)} != NULL) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType} != UINT8_DYN)
Data
Parameters
Type Dcm_DataElement_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation WriteData
Comment –
Mapped to API Xxx_WriteData
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == (USE_DATA_
ASYNCH_CLIENT_SERVER || USE_DATA_ASYNCH_CLIENT_SERVER_ERROR)) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDspDidWrite)} != NULL) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType} == UINT8_DYN)
Data
Parameters
Type Dcm_DataElement_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
Comment –
Variation –
5

428 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation WriteData
Comment –
Mapped to API Xxx_WriteData
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidWrite)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType}
!= UINT8_DYN)
Data
Parameters
Type Dcm_DataElement_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation WriteData
Comment –
Mapped to API Xxx_WriteData
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataUsePort)} == USE_DATA_
SYNCH_CLIENT_SERVER) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidInfo/DcmDsp
DidWrite)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.DcmDspDataType}
== UINT8_DYN)

Parameters Data
Type Dcm_DataElement_{Data}Type
Direction IN
Comment –
Variation Data = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)})
DataLength
Type uint16
Direction IN
5

429 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

One DataServices interface will be generated for each Data of each DID/PID, with
following possible operations:

8.8.3.2.1 ReadData

ReadData allows requesting to the application a data value of a DID/PID. A ReadData

interface is defined for every data of each DID/PID with read access when the data
element is configured to use a C/S interface. If the length is variable, the operation
ReadDataLength has to provide the current valid data length of this Data.
This interface is used for UDS Service ReadDataByIdentifier and for UDS Service Read-
DataByPeriodicIdentifier (0x2A) and for UDS Service InputOutputControlByIdentifier
(0x2F).
The ReadData interface can be defined as synchronous or asynchronous according to
configuration parameter DcmDspDataUsePort. The synchronous mechanism of the
ReadData interface is compatible to the related DEM interface to allow the provider to
use the same interface for both Dcm and DEM.

8.8.3.2.2 WriteData

WriteData requests the application to write a data value of a DID. The Data specific type
is an array of uint8 which represent either the fix length of this Data or the maximum
possible length of this Data. A WriteData interface is defined for every data of each
DID with write access. This interface is used for the UDS Service WriteDataByIdentifier
(0x2E).

8.8.3.2.3 ReadDataLength

ReadDataLength requests the application to return the data length of a Data. A Read-
DataLength interface is defined for every data of each DID with variable data length.

430 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

This interface is used for UDS Service ReadDataByIdentifier and for UDS Service Read-
DataByPeriodicIdentifier (0x2A).

8.8.3.2.4 ConditionCheckRead

ConditionCheckRead requests to the application if the conditions (System state,...) to

read the Data are correct. This operation is called for all requested DIDs before re-
questing the data of each DID. A ConditionCheckRead interface is defined for every
data of each DID with read access.

8.8.3.2.5 GetScalingInformation

Request to the application for the scaling information of a Data (see

[SWS_Dcm_00394]).

8.8.3.2.6 ReturnControlToEcu

Request to the application to return control to ECU of an IOControl (see

[SWS_Dcm_00396]).

8.8.3.2.7 ResetToDefault

Request to the application to reset an IOControl to default value (see

[SWS_Dcm_00397]).

8.8.3.2.8 FreezeCurrentState

Request to the application to freeze the current state of an IOControl (see

[SWS_Dcm_00398]).

8.8.3.2.9 ShortTermAdjustment

Request to the application to adjust the IO signal (see [SWS_Dcm_00399]).

8.8.3.3 DataServices_DIDRange_{Range}

The following interface defines an operation needed to get the DID range. Using the
concepts of the SW-C template, the interface is defined as follows:

431 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00769] Definition of ClientServerInterface DataServices_

DIDRange_{Range} d
Name DataServices_DIDRange_{Range}
Comment –
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.DcmDspDidRangeUsePort)} == TRUE
Range = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.SHORT-NAME)})
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.

Operation IsDidAvailable
Comment –
Mapped to API Xxx_IsDidAvailable
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.DcmDspDidRangeHasGaps)} == TRUE
DID
Parameters
Type uint16
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
supported
Type Dcm_DidSupportedType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
DCM_E_PENDING

Operation ReadDidData
Comment –
Mapped to API Xxx_ReadDidData
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange/DcmDspDidRangeInfoRef->DcmDsp
DidRead)} != NULL)

Parameters DID
Type uint16
Direction IN
Comment –
Variation –
Data
Type Dcm_RangeArray_{Range}Type
Direction OUT
Comment –
5

432 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation Range = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid
Range.SHORT-NAME)})
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataLength
Type uint16
Direction OUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ReadDidRangeDataLength
Comment –
Mapped to API Xxx_ReadDidRangeDataLength
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange/DcmDspDidRangeInfoRef->DcmDsp
DidRead)} != NULL)
DID
Parameters
Type uint16
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataLength
Type uint16
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation WriteDidData
Comment –
Mapped to API Xxx_WriteDidData
5

433 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange/DcmDspDidRangeInfoRef->DcmDsp
DidWrite)} != NULL)
DID
Parameters Type uint16
Direction IN
Comment –
Variation –
Data
Type Dcm_RangeArray_{Range}Type
Direction IN
Comment –
Variation Range = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid
Range.SHORT-NAME)})
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataLength
Type uint16
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

8.8.3.4 InfotypeServices_{VehInfoData}

The following interface defines an operation needed to get data from one or several
SW-C in order to supply OBD Service $09 (see [SWS_Dcm_00423]).
Using the concepts of the SW-C template, the interface is defined as follows:

[SWS_Dcm_00688] Definition of ClientServerInterface InfotypeServices_{Veh

InfoData} d

434 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Name InfotypeServices_{VehInfoData}
Comment –
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfoData/DcmDspVehInfo
DataUsePort)}==TRUE
VehInfoData = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfo
Data.SHORT-NAME)}
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.

Operation GetInfotypeValueData
Comment –
Mapped to API Xxx_GetInfotypeValueData
Variation –
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataValueBuffer
Type Dcm_InfoTypeServicesArray_{VehInfoData}Type
Direction OUT
Comment –
Variation VehInfoData = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDsp
VehInfoData.SHORT-NAME)}
DataValueBufferSize
Type uint8
Direction INOUT
Comment When the function is called this parameter contains the maximum number of
data bytes that can be written to the buffer. The function returns the actual
number of written data bytes in DataValueBuffer
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

8.8.3.5 RoutineServices_{RoutineName}

The following interface defines operations needed for the UDS Service Rou-
tineControl (0x31) (see [SWS_Dcm_00400], [SWS_Dcm_00401], [SWS_Dcm_00402],
[SWS_Dcm_00403], [SWS_Dcm_00404], [SWS_Dcm_00405]).
Using the concepts of the SW-C template, the interface is defined as follows:

435 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00690] Definition of ClientServerInterface RoutineServices_{Routine

Name} d
Name RoutineServices_{RoutineName}
Comment –
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.DcmDspRoutineUsePort)} == TRUE
RoutineName = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.
12 DCM_E_FORCE_RCRRP application request the transmission of a response
Response Pending (NRC 0x78)

Operation RequestResults
Comment –
Mapped to API Xxx_RequestResults
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/Dcm
DspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutine
SignalType)} != VARIABLE_LENGTH) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine/DcmDspRequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH)
DataIn_{Signal}
Parameters
Type Dcm_RequestDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_RequestDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
5

436 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation RequestResults
Comment –
Mapped to API Xxx_RequestResults
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/Dcm
DspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutine
SignalType)} == VARIABLE_LENGTH) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine/DcmDspRequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH)
DataIn_{Signal}
Parameters
Type Dcm_RequestDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_RequestDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutine
Results/DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResults
OutSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataOut_{Signal}
Type Dcm_RequestFlexibleOutArrayData_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutine
Results/DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResults
OutSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
currentDataLength
Type uint16
5

437 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Direction OUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors –

Operation RequestResults
Comment –
Mapped to API Xxx_RequestResults
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/Dcm
DspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutine
SignalType)} != VARIABLE_LENGTH) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine/DcmDspRequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
DataIn_{Signal}
Parameters
Type Dcm_RequestDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataIn_{Signal}
Type Dcm_RequestFlexibleInArrayData_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_RequestDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
ErrorCode
5

438 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors –

Operation RequestResults
Comment –
Mapped to API Xxx_RequestResults
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/Dcm
DspRequestRoutineResultsOut/DcmDspRequestRoutineResultsOutSignal.DcmDspRoutine
SignalType)} == VARIABLE_LENGTH) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine/DcmDspRequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
DataIn_{Signal}
Parameters Type Dcm_RequestDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsIn/DcmDspRequest
RoutineResultsInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataIn_{Signal}
Type Dcm_StartFlexibleInArrayData_{Routine}_{Signal}Type
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_RequestDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutine
Results/DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResults
OutSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataOut_{Signal}
Type Dcm_RequestFlexibleOutArrayData_{Routine}_{Signal}Type
Direction OUT
Comment –
5

439 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutine
Results/DcmDspRequestRoutineResultsOut/DcmDspRequestRoutineResults
OutSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDsp
RequestRoutineResults/DcmDspRequestRoutineResultsOut/DcmDspRequest
RoutineResultsOutSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
currentDataLength
Type uint16
Direction OUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation RequestResultsConfirmation
Comment This operation indicates the transmission of a response to a RequestResultsRoutine request
Mapped to API Xxx_RequestResultsConfirmation
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspRequestRoutineResults/Dcm
DspRequestRoutineResultsConfirmationEnabled)}==TRUE)
Parameters ConfirmationStatus
Type Dcm_ConfirmationStatusType
Direction IN
Comment Confirmation status of a RequestResultsRoutinerequest
Variation –
Possible Errors E_OK
E_NOT_OK

Operation Start
Comment –
Mapped to API Xxx_Start
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH)
&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} != VARIABLE_
LENGTH)
Parameters DataIn_{Signal}
Type Dcm_StartDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
5

440 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StartDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation Start
Comment –
Mapped to API Xxx_Start
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH)
&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} == VARIABLE_
LENGTH)
DataIn_{Signal}
Parameters
Type Dcm_StartDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
5

441 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
DataOut_{Signal}
Type Dcm_StartDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)
DataOut_{Signal}
Type Dcm_StartFlexibleOutArrayData_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation –
currentDataLength
Type uint16
Direction OUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation Start
Comment –
Mapped to API Xxx_Start
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} == VARIABLE_
LENGTH) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} != VARIABLE_
LENGTH)

Parameters DataIn_{Signal}
Type Dcm_StartDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataIn_{Signal}
Type Dcm_StartFlexibleInArrayData_{Routine}_{Signal}Type
Direction IN
Comment –
5

442 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StartDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
currentDataLength
Type uint16
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation Start
Comment –
Mapped to API Xxx_Start
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineIn/DcmDspStartRoutineInSignal.DcmDspRoutineSignalType)} == VARIABLE_
LENGTH) &&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineOut/DcmDspStartRoutineOutSignal.DcmDspRoutineSignalType)} == VARIABLE_
LENGTH)

Parameters DataIn_{Signal}
Type Dcm_StartDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/
DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDspRoutineSignal
Type)} != VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataIn_{Signal}
5

443 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type Dcm_StartFlexibleInArrayData_{Routine}_{Signal}Type
Direction IN
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/
DcmDspStartRoutineIn/DcmDspStartRoutineInSignal.DcmDspRoutineSignal
Type)} == VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineIn/DcmDspStartRoutineIn
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StartDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/
DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.DcmDspRoutine
SignalType)} != VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataOut_{Signal}
Type Dcm_StartFlexibleOutArrayData_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/
DcmDspStartRoutineOut/DcmDspStartRoutineOutSignal.DcmDspRoutine
SignalType)} == VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStart
Routine/DcmDspStartRoutineOut/DcmDspStartRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
currentDataLength
Type uint16
Direction INOUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

444 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Operation StartConfirmation
Comment This operation indicates the transmission of a response to a StartRoutine request
Mapped to API Xxx_StartConfirmation
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStartRoutine/DcmDspStart
RoutineConfirmationEnabled)}==TRUE
Parameters ConfirmationStatus
Type Dcm_ConfirmationStatusType
Direction IN
Comment Confirmation status of a StartRoutine request
Variation –
Possible Errors E_OK
E_NOT_OK

Operation Stop
Comment –
Mapped to API Xxx_Stop
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH)
&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} != VARIABLE_
LENGTH)
DataIn_{Signal}
Parameters
Type Dcm_StopDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StopDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
5

445 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation Stop
Comment –
Mapped to API Xxx_Stop
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} != VARIABLE_LENGTH)
&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} == VARIABLE_
LENGTH)
DataIn_{Signal}
Parameters Type Dcm_StopDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StopDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataOut_{Signal}
Type Dcm_StopFlexibleOutArrayData_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation –
currentDataLength
Type uint16
Direction OUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
5

446 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation Stop
Comment –
Mapped to API Xxx_Stop
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} != VARIABLE_
LENGTH)
DataIn_{Signal}
Parameters Type Dcm_StopDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataIn_{Signal}
Type Dcm_StopFlexibleInArrayData_{Routine}_{Signal}Type
Direction IN
Comment –
Variation –
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StopDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
currentDataLength
Type uint16
Direction IN
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
5

447 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation Stop
Comment –
Mapped to API Xxx_Stop
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineIn/DcmDspStopRoutineInSignal.DcmDspRoutineSignalType)} == VARIABLE_LENGTH)
&&
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineOut/DcmDspStopRoutineOutSignal.DcmDspRoutineSignalType)} == VARIABLE_
LENGTH)
DataIn_{Signal}
Parameters
Type Dcm_StopDataIn_{Routine}_{Signal}Type
Direction IN
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/
DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDspRoutineSignal
Type)} != VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataIn_{Signal}
Type Dcm_StopFlexibleInArrayData_{Routine}_{Signal}Type
Direction IN
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/
DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.DcmDspRoutineSignal
Type)} == VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineIn/DcmDspStopRoutineInSignal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
OpStatus
Type Dcm_OpStatusType
Direction IN
Comment –
Variation –
DataOut_{Signal}
Type Dcm_StopDataOut_{Routine}_{Signal}Type
Direction OUT
Comment –
5

448 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/
DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.DcmDspRoutine
SignalType)} != VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
DataOut_{Signal}
Type Dcm_StopFlexibleOutArrayData_{Routine}_{Signal}Type
Direction OUT
Comment –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/
DcmDspStopRoutineOut/DcmDspStopRoutineOutSignal.DcmDspRoutine
SignalType)} == VARIABLE_LENGTH
Signal = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStop
Routine/DcmDspStopRoutineOut/DcmDspStopRoutineOut
Signal.SHORT-NAME)}
Routine = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Routine.SHORT-NAME)}
currentDataLength
Type uint16
Direction INOUT
Comment –
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation StopConfirmation
Comment This operation indicates the transmission of a response to a StopRoutine request
Mapped to API Xxx_StopConfirmation
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine/DcmDspStopRoutine/DcmDspStop
RoutineConfirmationEnabled)}==TRUE)
Parameters ConfirmationStatus
Type Dcm_ConfirmationStatusType
Direction IN
Comment Confirmation status of a StopRoutine request
Variation –
Possible Errors E_OK
E_NOT_OK

From the point of view of the DCM, the operations have the following signatures:

449 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.3.6 RequestControlServices_{Tid}

The following interface allows the Dcm to provide OBD Service $08 (see
[SWS_Dcm_00419]).
Using the concepts of the SW-C template, the interface is defined as follows:

[SWS_Dcm_00691] Definition of ClientServerInterface RequestControlSer-

vices_{Tid} d
Name RequestControlServices_{Tid}
Comment –
IsService true
Variation Tid = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl.SHORT-NAME)}
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed

Operation RequestControl
Comment –
Mapped to API Xxx_RequestControl
Variation –
OutBuffer
Parameters
Type Dcm_RequestControlServicesOutArray_{Tid}Type
Direction OUT
Comment –
Variation Tid = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequest
Control.SHORT-NAME)}
InBuffer
Type Dcm_RequestControlServicesInArray_{Tid}Type
Direction IN
Comment –
Variation Tid = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequest
Control.SHORT-NAME)}
Possible Errors E_OK
E_NOT_OK

8.8.3.7 ServiceRequestNotification

The following interface indicates to the Application that a service is about to be ex-
ecuted and allows the Application to reject the execution of the service request (see
[SWS_Dcm_00218], [SWS_Dcm_00462], [SWS_Dcm_00463]).
Using the concepts of the SW-C template, the interface is defined as follows:

450 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_00694] Definition of ClientServerInterface ServiceRequestNotifica-

tion d
Name ServiceRequestNotification
Comment –
IsService true
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceRequestManufacturerNotification)} !=
NULL)||({ecuc(Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceRequestSupplierNotification)} !=
NULL)
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
8 E_REQUEST_NOT_ no response will be sent
ACCEPTED

Operation Confirmation
Comment –
Mapped to API Xxx_Confirmation
Variation –
SID
Parameters Type uint8
Direction IN
Comment Value of service identifier
Variation –
ReqType
Type uint8
Direction IN
Comment Addressing type of the request(0=physical request, 1=functional request)
Variation –
ConnectionId
Type uint16
Direction IN
Comment Unique connection identifier
Variation –
ConfirmationStatus
Type Dcm_ConfirmationStatusType
Direction IN
Comment Confirmation of a successful transmission or a transmission error of a
diagnostic service.
Variation –
ProtocolType
Type Dcm_ProtocolType
Direction IN
Comment –
Variation –
TesterSourceAddress
Type uint16
Direction IN
Comment –
Variation –
5

451 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Possible Errors E_OK
E_NOT_OK

Operation Indication
Comment –
Mapped to API Xxx_Indication
Variation –
SID
Type uint8
Parameters
Direction IN
Comment Value of service identifier
Variation –
RequestData
Type Dcm_RequestDataArrayType
Direction IN
Comment This parameter contains the complete request data (diagnostic buffer), except
the service ID
Variation –
DataSize
Type uint32
Direction IN
Comment This parameter defines how many bytes in the RequestData parameter are
valid
Variation –
ReqType
Type uint8
Direction IN
Comment Addressing type of the request(0=physical request, 1=functional request
Variation –
ConnectionId
Type uint16
Direction IN
Comment Unique connection identifier
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment –
Variation –
ProtocolType
Type Dcm_ProtocolType
Direction IN
Comment –
Variation –
TesterSourceAddress
Type uint16
Direction IN
5

452 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK
E_REQUEST_NOT_ACCEPTED

8.8.3.8 UploadDownloadServices

[SWS_Dcm_91065] Definition of ClientServerInterface UploadDownloadServices

d
Name UploadDownloadServices
Comment –
IsService true
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspMemoryTransfer.DcmDspMemoryTransferUse
Port)} == TRUE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/Dcm
RequestFileTransferUsePort)} == TRUE)
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed
10 DCM_E_PENDING Request is not yet finished. Further call(s) required
to finish.
12 DCM_E_FORCE_RCRRP application request the transmission of a response
Response Pending (NRC 0x78)

Operation ProcessRequestAddFile
Comment Callout function.
DCM shall call this function to start a RequestFileTransfer process with modeOfOperation equal
to 0x01 (AddFile).
Mapped to API Dcm_ProcessRequestAddFile
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransferUse
Port)} == TRUE)

Parameters OpStatus
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
filePathAndNameLength
Type uint16
Direction IN
Comment Defines the length in bytes for the parameter filePathAndName.
5

453 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation –
filePathAndName
Type const Dcm_FileAndDirNameType
Direction IN
Comment Defines the file system location of the server where the file which shall be
added, deleted, replaced or read from depending on the parameter modeOf
Operation parameter. In addition this parameter includes the file name of the
file which shall be added, deleted, replaced or read as part of the file path.
Variation –
dataFormatIdentifier
Type uint8
Direction IN
Comment This data-parameter is a one byte value with each nibble encoded separately.
The high nibble specifies the "compressionMethod", and the low nibble
specifies the "encryptingMethod". The value 0x00 specifies that neither
compressionMethod nor encryptingMethod is used. Values other than 0x00
are vehicle manufacturer specific.
Variation –
fileSizeUncompressed
Type uint64
Direction IN
Comment Defines the size of the uncompressed file to be download in bytes.
Variation –
fileSizeCompressed
Type uint64
Direction IN
Comment Defines the size of the compressed file to be downloaded in bytes.
Variation –
maxNumberOfBlockLength
Type uint64
Direction OUT
Comment Max number of bytes to be included in each TransferData request excluding
the SID and the blockSequenceCounter.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ProcessRequestAddFile returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

454 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Operation ProcessRequestDeleteFile
Comment Callout function.
DCM shall call this function to start a RequestFileTransfer process with modeOfOperation equal
to 0x02 (DeleteFile).
Mapped to API Dcm_ProcessRequestDeleteFile
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransferUse
Port)} == TRUE)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
filePathAndNameLength
Type uint16
Direction IN
Comment Defines the length in bytes for the parameter filePathAndName.
Variation –
filePathAndName
Type const Dcm_FileAndDirNameType
Direction IN
Comment Defines the file system location of the server where the file which shall be
added, deleted, replaced or read from depending on the parameter modeOf
Operation parameter. In addition this parameter includes the file name of the
file which shall be added, deleted, replaced or read as part of the file path.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ProcessRequestDeleteFile returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation ProcessRequestDownload
Comment Callout function.
DCM shall call this callout function to start a download process.
This service is needed for the implementation of UDS service RequestDownload.
Mapped to API Dcm_ProcessRequestDownload
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspMemoryTransfer.DcmDspMemoryTransferUse
Port)}
Parameters OpStatus
Type Dcm_OpStatusType
Direction IN
5

455 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Comment DCM_INITIAL
DCM_PENDING
DCM_CANCEL
Variation –
DataFormatIdentifier
Type uint8
Direction IN
Comment Bit 7 - 4: Compression Method
• 0x0: not compressed
• 0x1..F: vehicle-manufacturer-specific
Bit 3 - 0: Encrypting method
• 0x0: not encrypted
• 0x1..F: vehicle-manufacturer-specific
Variation –
MemoryIdentifier
Type uint8
Direction IN
Comment Identifier of the Memory Block, if the parameter is not used it shall be set to 0.
Variation –
MemoryAddress
Type uint32
Direction IN
Comment Starting address of server memory to which data is to be written
Variation –
MemorySize
Type uint32
Direction IN
Comment Uncompressed memory size in bytes
Variation –
BlockLength
Type uint32
Direction INOUT
Comment Max. Number of bytes for one Dcm_WriteMemory
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ProcessRequestDownload returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

456 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Operation ProcessRequestReadDir
Comment Callout function.
DCM shall call this function to start a RequestFileTransfer process with modeOfOperation equal
to 0x05 (ReadDir).
Mapped to API Dcm_ProcessRequestReadDir
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransferUse
Port)} == TRUE)
OpStatus
Parameters Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
filePathAndNameLength
Type uint16
Direction IN
Comment Defines the length in bytes for the parameter filePathAndName.
Variation –
filePathAndName
Type const Dcm_FileAndDirNameType
Direction IN
Comment Defines the file system location of the server where the file which shall be
added, deleted, replaced or read from depending on the parameter modeOf
Operation parameter. In addition this parameter includes the file name of the
file which shall be added, deleted, replaced or read as part of the file path.
Variation –
dirInfoLength
Type uint64
Direction OUT
Comment Defines the size of directory information to be uploaded in bytes.
Variation –
maxNumberOfBlockLength
Type uint64
Direction OUT
Comment Max number of bytes to be included in each TransferData request excluding
the SID and the blockSequenceCounter.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ProcessRequestReadDir returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

457 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Operation ProcessRequestReadFile
Comment Callout function.
DCM shall call this function to start a RequestFileTransfer process with modeOfOperation equal
to 0x04 (ReadFile).
Mapped to API Dcm_ProcessRequestReadFile
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransferUse
Port)} == TRUE)
OpStatus
Parameters Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
filePathAndNameLength
Type uint16
Direction IN
Comment Defines the length in bytes for the parameter filePathAndName.
Variation –
filePathAndName
Type const Dcm_FileAndDirNameType
Direction IN
Comment Defines the file system location of the server where the file which shall be
added, deleted, replaced or read from depending on the parameter modeOf
Operation parameter. In addition this parameter includes the file name of the
file which shall be added, deleted, replaced or read as part of the file path.
Variation –
dataFormatIdentifier
Type uint8
Direction IN
Comment This data-parameter is a one byte value with each nibble encoded separately.
The high nibble specifies the "compressionMethod", and the low nibble
specifies the "encryptingMethod". The value 0x00 specifies that neither
compressionMethod nor encryptingMethod is used. Values other than 0x00
are vehicle manufacturer specific.
Variation –
fileSizeUncompressed
Type uint64
Direction OUT
Comment Defines the size of the uncompressed file to be uploaded in bytes.
Variation –
fileSizeCompressed
Type uint64
Direction OUT
Comment Defines the size of the compressed file to be uploaded in bytes.
Variation –
maxNumberOfBlockLength
Type uint64
Direction OUT
5

458 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Comment Max number of bytes to be included in each TransferData response excluding
the SID and the blockSequenceCounter.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ProcessRequestReadFile returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation ProcessRequestReplaceFile
Comment Callout function.
DCM shall call this function to start a RequestFileTransfer process with modeOfOperation equal
to 0x03 (ReplaceFile).
Mapped to API Dcm_ProcessRequestReplaceFile
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransferUse
Port)} == TRUE)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
filePathAndNameLength
Type uint16
Direction IN
Comment Defines the length in bytes for the parameter filePathAndName.
Variation –
filePathAndName
Type const Dcm_FileAndDirNameType
Direction IN
Comment Defines the file system location of the server where the file which shall be
added, deleted, replaced or read from depending on the parameter modeOf
Operation parameter. In addition this parameter includes the file name of the
file which shall be added, deleted, replaced or read as part of the file path.
Variation –
dataFormatIdentifier
Type uint8
Direction IN
Comment This data-parameter is a one byte value with each nibble encoded separately.
The high nibble specifies the "compressionMethod", and the low nibble
specifies the "encryptingMethod". The value 0x00 specifies that neither
compressionMethod nor encryptingMethod is used. Values other than 0x00
are vehicle manufacturer specific.
5

459 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation –
fileSizeUncompressed
Type uint64
Direction IN
Comment Defines the size of the uncompressed file to be download in bytes.
Variation –
fileSizeCompressed
Type uint64
Direction IN
Comment Defines the size of the compressed file to be downloaded in bytes.
Variation –
maxNumberOfBlockLength
Type uint64
Direction OUT
Comment Max number of bytes to be included in each TransferData request excluding
the SID and the blockSequenceCounter.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ProcessRequestReplaceFile returns value E_NOT_OK,
the DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation ProcessRequestTransferExit
Comment Callout function.
DCM shall call this callout function to terminate a download or upload process.
This callout is needed for the implementation of UDS service RequestTransferExit.
Mapped to API Dcm_ProcessRequestTransferExit
Variation –
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL
DCM_PENDING
DCM_CANCEL
Variation –
transferRequestParameterRecord
Type Dcm_RequestDataArrayType
Direction IN
Comment Vehicle manufacturer specific transferRequestParameterRecord
Variation –
transferRequestParameterRecordSize
5

460 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type uint32
Direction IN
Comment Length of transferRequestParameterRecord in bytes
Variation –
transferResponseParameterRecord
Type Dcm_RequestDataArrayType
Direction OUT
Comment Vehicle manufacturer specific transferResponseParameterRecord
Variation –
transferResponseParameterRecordSize
Type uint32
Direction INOUT
Comment When the function is called this parameter contains the maximum number of
data bytes that can be written to the buffer. The function returns the actual
number of written data bytes in transferResponseParameterRecord.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment see below
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

Operation ProcessRequestUpload
Comment Callout function.
DCM shall call this callout function to start an upload process.
This service is needed for the implementation of UDS service RequestUpload.
Mapped to API Dcm_ProcessRequestUpload
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspMemoryTransfer.DcmDspMemoryTransferUse
Port)}

Parameters OpStatus
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL
DCM_PENDING
DCM_CANCEL
DCM_FORCE_RCRRP_OK
Variation –
DataFormatIdentifier
Type uint8
Direction IN
5

461 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Comment Bit 7 - 4: Compression Method

• 0x0: not compressed

• 0x1..F: vehicle-manufacturer-specific

Bit 3 - 0: Encrypting method

• 0x0: not encrypted

• 0x1..F: vehicle-manufacturer-specific
Variation –
MemoryIdentifier
Type uint8
Direction IN
Comment Identifier of the Memory Block, if the parameter is not used it shall be set to 0.
Variation –
MemoryAddress
Type uint32
Direction IN
Comment Starting address of server memory from which data are to be copied
Variation –
MemorySize
Type uint32
Direction IN
Comment Uncompressed memory size in bytes
Variation –
BlockLength
Type uint32
Direction INOUT
Comment Max. Number of bytes for one Dcm_ReadMemory
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ProcessRequestUpload returns value E_NOT_OK, the
DCM module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING

462 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Operation ProcessTransferDataRead
Comment The ProcessTransferDataRead callout is used to request memory data identified by the
parameter memoryAddress and memorySize from the UDS request message.
This service is needed for the implementation of UDS services:
• ReadMemoryByAddress
• RequestUpload
• ReadDataByIdentifier (in case of Dynamical DID defined by memory address)
• TransferData
Mapped to API Dcm_ProcessTransferDataRead
Variation –
OpStatus
Parameters Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL
DCM_PENDING
DCM_CANCEL
DCM_FORCE_RCRRP_OK
Variation –
MemoryIdentifier
Type uint8
Direction IN
Comment Identifier of the Memory Block (e.g. used if memory section distinguishing is
needed)
Note: If it’s not used this parameter shall be set to 0.
Variation –
MemoryAddress
Type uint32
Direction IN
Comment Starting address of server memory from which data is to be retrieved.
Variation –
MemorySize
Type uint32
Direction IN
Comment Number of bytes in the MemoryData
Variation –
MemoryData
Type Dcm_RequestDataArrayType
Direction OUT
Comment Data read (Points to the diagnostic buffer in DCM)
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ReadMemory returns value DCM_READ_FAILED, the
Dcm module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
5

463 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation ProcessTransferDataWrite
Comment The ProcessTransferDataWrite callout is used to write memory data identified by the parameter
memoryAddress and memorySize. This service is needed for the implementation of UDS
services :
• WriteMemoryByAddress
• RequestDownload
• TransferData
Mapped to API Dcm_ProcessTransferDataWrite
Variation –
OpStatus
Parameters Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL
DCM_PENDING
DCM_CANCEL
DCM_FORCE_RCRRP_OK
Variation –
MemoryIdentifier
Type uint8
Direction IN
Comment Identifier of the Memory Block (e.g. used by WriteDataByIdentifier service).
Note: If it’s not used this parameter shall be set to 0.
Variation –
MemoryAddress
Type uint32
Direction IN
Comment Starting address of server memory in which data is to be copied.
Note: If it’s not used (e.g. if the data is compressed) this parameter shall be set
to 0.
Variation –
MemorySize
Type uint32
Direction IN
Comment Number of bytes in MemoryData
Variation –
MemoryData
Type Dcm_RequestDataArrayType
Direction IN
Comment Data to write (Points to the diagnostic buffer in DCM)
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
5

464 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Comment If the operation Dcm_WriteMemory returns value DCM_WRITE_FAILED, the
Dcm module shall send a negative response with NRC code equal to the
parameter ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

Operation ReadFileOrDir
Comment Callout function.
DCM shall call this function when data shall be sent as a response to UDS service TransferData
if there’s an ongoing RequestFileTransfer process started with 0x04 (ReadFile) or 0x05 (Read
Dir).
Mapped to API Dcm_ReadFileOrDir
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransferUse
Port)} == TRUE)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
DataLength
Type uint64
Direction INOUT
Comment As in, the parameter defines the maximum block length to be used, i.e. the
value of maxNumberOfBlockLength sent to the client in the response of
RequestFileTransfer.
As out, the parameter defines the actual length in bytes for the parameter
Data. The value shall not exceed, but might be less, the value provided as in
parameter.
Variation –
Data
Type Dcm_ResponseDataArrayType
Direction IN
Comment Pointer to the data to be written.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_ReadFileOrDir returns value E_NOT_OK, the DCM
module shall send a negative response with NRC code equal to the parameter
ErrorCode parameter value.
Variation –
Possible Errors E_OK
E_NOT_OK
DCM_E_PENDING
DCM_E_FORCE_RCRRP

465 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Operation WriteFile
Comment Callout function.
DCM shall call this function when data is received using UDS service TransferData if there’s an
ongoing RequestFileTransfer process started with 0x01 (AddFile) or 0x03 (ReplaceFile).
Mapped to API Dcm_WriteFile
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFileTransferUse
Port)} == TRUE)
OpStatus
Parameters
Type Dcm_OpStatusType
Direction IN
Comment DCM_INITIAL: All In-parameters are valid.
DCM_PENDING: All In-parameters are set to 0x00.
DCM_CANCEL: All In-parameters are set to 0x00.
DCM_FORCE_RCRRP_OK: All In-parameters are set to 0x00.
Variation –
DataLength
Type uint64
Direction IN
Comment Defines the length in bytes for the parameter Data. The value will not exceed,
but might be less, compared to the value of maxNumberOfBlockLength return
in Dcm_ProcessRequestFileTransfer.
Variation –
Data
Type Dcm_RequestDataArrayType
Direction IN
Comment Pointer to the data to be written.
Variation –
ErrorCode
Type Dcm_NegativeResponseCodeType
Direction OUT
Comment If the operation Dcm_WriteFile returns value E_NOT_OK, the DCM module
shall send a negative response with NRC code equal to the parameter Error
Code parameter value.
Variation –
Possible Errors –

8.8.3.9 DCMServices

[SWS_Dcm_00698] Definition of ClientServerInterface DCMServices d

Name DCMServices
Comment –
IsService true
5

466 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation –
Possible Errors 0 E_OK Operation successful
1 E_NOT_OK Operation failed

Operation GetSecurityLevel
Comment –
Mapped to API Dcm_GetSecurityLevel
Variation –
Parameters SecLevel
Type Dcm_SecLevelType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation GetSesCtrlType
Comment –
Mapped to API Dcm_GetSesCtrlType
Variation –
Parameters SesCtrlType
Type Dcm_SesCtrlType
Direction OUT
Comment –
Variation –
Possible Errors E_OK
E_NOT_OK

Operation ResetToDefaultSession
Comment –
Mapped to API Dcm_ResetToDefaultSession
Variation –
Possible Errors E_OK
E_NOT_OK

Operation SetActiveDiagnostic
Comment Allows to activate and deactivate the call of ComM_DCM_ActiveDiagnostic() function.
Mapped to API Dcm_SetActiveDiagnostic
Variation –
Parameters active
Type boolean
Direction IN
Comment If false Dcm shall not call ComM_DCM_ActiveDiagnostic(). If true Dcm will call
ComM_DCM_ActiveDiagnostic().
Variation –
Possible Errors E_OK

467 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.3.10 Authentication

[SWS_Dcm_91072] Definition of ClientServerInterface Authentication d

Name Authentication
Comment –
IsService true
Variation –
Possible Errors 0 E_OK Operation successful

Operation SetDeauthenticatedRole
Comment Sets a new role used in deauthenticated state for that connection. The set role is valid until the
connection switches into authenticated state or the ECU is reset.
Mapped to API Dcm_SetDeauthenticatedRole
Variation –
Parameters deauthenticatedRole
Type Dcm_AuthenticationRoleType
Direction IN
Comment New deauthenticated role that is assigned to that connection.
Variation –
Possible Errors E_OK

8.8.4 NvDataInterface

8.8.4.1 DataServices_{DID}

[SWS_Dcm_91061] Definition of SenderReceiverInterface DataServices_{DID}

Upstream requirements: RS_Diag_04218

d
Name DataServices_{DID}
Comment –
IsService false
Variation ( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_ATOMIC_
NV_DATA_INTERFACE)
DID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}
Data Elements data
Type {DID}_Struct_DataType
Variation DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})

468 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.5 Ports

This section formally specifies the corresponding AUTOSAR Service using the con-
cepts of the Software-Component-Template. The following definition can be generated
completely out of the configuration of the Dcm, which defines the exact ports that are
present and their names.
Naming of the port : The prefix of the port name is fixed and defined herafter (e.g.
DataServices_). The name behind the prefix corresponds to the name of the associ-
ated container in the ECU configuration and can be freely defined during the configu-
ration step. e.g. : for a DcmDspData container called Speed the port name would be
DataServices_Speed
1 ServiceSwComponentType Dcm {
2
3 //the presence and name of this port is configuration-independent
4 ProvidePort DCMServices DCMServices;
5
6 //see configuration parameter DcmDspSecurityRow
7 RequirePort SecurityAccess_\{SecurityLevel\} SecurityAccess_\{
SecurityLevel\};
8 ...
9
10
11 //see configuration parameter DcmDspData
12 RequirePort DataServices_\{Data\} DataServices_\{Data\};
13 ProvidePort DataServices_\{Data\} DataServices_\{Data\}; // Only if
the data can be written and DcmDspDataUsePort is set to
USE_DATA_SENDER_RECEIVER or to USE_DATA_SENDER_RECEIVER_AS_SERVICE
14 ...
15
16
17 //see configuration parameter DcmDspVehInfoData
18 RequirePort InfotypeServices_{VehInfoData}
19 InfotypeServices_{VehInfoData}
20 ...
21
22
23 //see configuration parameter DcmDspRoutine
24 RequirePort RoutineServices_{RoutineName}
25 RoutineServices_{RoutineName};
26 ...
27
28 //see configuration parameter DcmDspRequestControl
29 RequirePort RequestControlServices_\{Tid\}
30 RequestControlServices_\{Tid\};
31 ...
32

33
34 //see configuration parameter
DcmDsdServiceRequestManufacturerNotication
35 RequirePort ServiceRequestNotification
36 ServiceRequestManufacturerNotification_{Name};
37 ...
38

469 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

39 //see configuration parameter DcmDsdServiceRequestSupplierNotication

40 RequirePort ServiceRequestNotification
41 ServiceRequestSupplierNotification_\_SWC>;
42 ...
43
44 //Note: When service 0x19 subfunctions 0x14 is used (call to //
Dem_GetNextFilteredDTCAndFDC), the following is defined:
45 //Non-DEM-internal calculated fault detection counters are typically
46 //requested from SW-Cs through the RTE. To indicate an equivalent call-
tree //for these runables, a work-around is used: The Dcm main
function //specifies a trigger to the DEM interface GeneralEvtInfo
(operation //GetFaultDetectionCounter), which triggers the
according ehavior (refer to //RunnableEntity
GetFaultDetectionCounter, chapter "Service Interface //
DiagnosticInfo & General" in DEM SWS)."
47 RequirePort Dem/CallbackGetFaultDetectCounter CBFaultDetectCtrDummy
48 (The client-server interface can be used from the DEM.)
49
50 RunnableEntity MainFunction
51 symbol \ARApiRef{Dcm_MainFunction}"
52 canbeInvokedConcurrently = FALSE
53 SSCP = port CBFaultDetectCtrDummy, GetFaultDetectionCounter
54
55 Connector from CBFaultDetectCtrDummy to Dem/GeneralEvtInfo
56 }

8.8.5.1 DataServices_DIDRange_{Range}

[SWS_Dcm_01034] Definition of Port DataServices_DIDRange_{Range} required

by module Dcm d
Name DataServices_DIDRange_{Range}
Kind RequiredPort Interface DataServices_DIDRange_{Range}
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.DcmDspDidRangeUsePort)} == TRUE
Range = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDidRange.SHORT-NAME)})

470 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.5.2 DataServices_{DID}

[SWS_Dcm_91058] Definition of Port DataServices_{DID} provided by module

Dcm
Upstream requirements: RS_Diag_04218

d
Name DataServices_{DID}
Kind ProvidedPort Interface DataServices_{DID}, DataServices_{DID}
Description –
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE ) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidUsePort)} == (USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE ) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_NV_
DATA_INTERFACE)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->
DcmDspDidInfo/DcmDspDidWrite)} != NULL) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Did/DcmDspDidInfoRef-> DcmDspDidInfo/DcmDspDidRead)} == NULL) || ({ecuc(Dcm/DcmConfig
Set/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/DcmDspDidControl)} !=NULL))
DID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}

[SWS_Dcm_91060] Definition of Port DataServices_{DID} provided/required by

module Dcm
Upstream requirements: RS_Diag_04218

d
Name DataServices_{DID}
Kind Provided Interface DataServices_{DID}, DataServices_{DID}
RequiredPort
Description –
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE ) ||({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidUsePort)} == (USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE ) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_NV_
DATA_INTERFACE)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidWrite)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidRead)} != NULL))
DID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}

471 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[SWS_Dcm_91059] Definition of Port DataServices_{DID} required by module

Dcm
Upstream requirements: RS_Diag_04218

d
Name DataServices_{DID}
Kind RequiredPort Interface DataServices_{DID}, DataServices_{DID}
Description –
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE ) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDsp
DidUsePort)} == (USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE ) ||
({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_NV_
DATA_INTERFACE)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfo
Ref->DcmDspDidInfo/DcmDspDidWrite)} == NULL) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/Dcm
DspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidRead)} != NULL) || ({ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef->DcmDspDidInfo/DcmDspDidControl)}
!=NULL))
DID = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)}

8.8.5.3 DataServices_{Data}

[SWS_Dcm_01035] Definition of Port DataServices_{Data} required by module

Dcm d
Name DataServices_{Data}
Kind RequiredPort Interface DataServices_{Data}, DataServices_{Data}
Description –
Variation ( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspPid/DcmDspPidData/DcmDspPidService01/Dcm
DspPidDataUsePort)} ==(USE_DATA_SYNCH_CLIENT_SERVER ||USE_DATA_SENDER_
RECEIVER ||USE_DATA_SENDER_RECEIVER_AS_SERVICE))
Data = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)} || {ecuc(Dcm/Dcm
ConfigSet/DcmDsp/DcmDspPid/DcmDspPidData.SHORT-NAME)}

[SWS_Dcm_01310] Definition of Port DataServices_{Data} required by module

Dcm d
Name DataServices_{Data}
Kind RequiredPort Interface DataServices_{Data}, DataServices_{Data}
Description –
5

472 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation ((( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_DATA_
ELEMENT_SPECIFIC_INTERFACES)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/
DcmDspDataUsePort)} == (USE_DATA_SENDER_RECEIVER ||USE_DATA_SENDER_
RECEIVER_AS_SERVICE))) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef-> DcmDspDidInfo/DcmDspDidWrite)} == NULL) && (({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/DcmDspDidRead)} != NULL)))
Data = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}

[SWS_Dcm_01031] Definition of Port DataServices_{Data} provided by module

Dcm d
Name DataServices_{Data}
Kind ProvidedPort Interface DataServices_{Data}, DataServices_{Data}
Description –
Variation ((( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_DATA_
ELEMENT_SPECIFIC_INTERFACES)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/
DcmDspDataUsePort)} == (USE_DATA_SENDER_RECEIVER ||USE_DATA_SENDER_
RECEIVER_AS_SERVICE))) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef-> DcmDspDidInfo/DcmDspDidWrite)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/DcmDspDidRead)} == NULL)
Data = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}

[SWS_Dcm_01311] Definition of Port DataServices_{Data} provided/required by

module Dcm d
Name DataServices_{Data}
Kind Provided Interface DataServices_{Data}
RequiredPort
Description –
Variation ((( {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == USE_DATA_
ELEMENT_SPECIFIC_INTERFACES)) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData/
DcmDspDataUsePort)} == (USE_DATA_SENDER_RECEIVER ||USE_DATA_SENDER_
RECEIVER_AS_SERVICE))) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDid
InfoRef-> DcmDspDidInfo/DcmDspDidWrite)} != NULL) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/
DcmDspDid/DcmDspDidInfoRef-> DcmDspDidInfo/DcmDspDidRead)} != NULL)
Data = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspData.SHORT-NAME)}

473 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.5.4 IOControlRequest_{DID}

[SWS_Dcm_01312] Definition of Port IOControlRequest_{DID} provided/required

by module Dcm d
Name IOControlRequest_{DID}
Kind Provided Interface IOControlRequest_{DID}
RequiredPort
Description –
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE || USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_
SERVICE))) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDsp
DidInfo/DcmDspDidControl)} != NULL)
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})

8.8.5.5 IOControlResponse_{DID}

[SWS_Dcm_01313] Definition of Port IOControlResponse_{DID} required by

module Dcm
Upstream requirements: RS_Diag_04218

d
Name IOControlResponse_{DID}
Kind RequiredPort Interface IOControlResponse_{DID}
Description –
Variation (({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidUsePort)} == (USE_ATOMIC_
SENDER_RECEIVER_INTERFACE || USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_
SERVICE))) && ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid/DcmDspDidInfoRef-> DcmDsp
DidInfo/DcmDspDidControl)} != NULL)
DID = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspDid.SHORT-NAME)})

8.8.5.6 DCMServices

[SWS_Dcm_01030] Definition of Port DCMServices provided by module Dcm d

Name DCMServices
Kind ProvidedPort Interface DCMServices
Description –
5

474 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Variation –

8.8.5.7 InfotypeServices_{VehInfoData}

[SWS_Dcm_01037] Definition of Port InfotypeServices_{VehInfoData} required

by module Dcm d
Name InfotypeServices_{VehInfoData}
Kind RequiredPort Interface InfotypeServices_{VehInfoData}
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfoData/DcmDspVehInfoData
UsePort)}==TRUE
VehInfoData = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspVehInfo/DcmDspVehInfo
Data.SHORT-NAME)}

8.8.5.8 RequestControlServices_{Tid}

[SWS_Dcm_01038] Definition of Port RequestControlServices_{Tid} required by

module Dcm d
Name RequestControlServices_{Tid}
Kind RequiredPort Interface RequestControlServices_{Tid}
Description –
Variation Tid = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestControl.SHORT-NAME)}

475 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.5.9 ServiceRequestManufacturerNotification_{Name}

[SWS_Dcm_01039] Definition of Port ServiceRequestManufacturerNotifica-

tion_{Name} required by module Dcm d
Name ServiceRequestManufacturerNotification_{Name}
Kind RequiredPort Interface ServiceRequestNotification
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceRequestManufacturerNotification)} != NULL)
Name = {ecuc(Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceRequestManufacturer
Notification.SHORT-NAME)}

8.8.5.10 ServiceRequestSupplierNotification_{Name}

[SWS_Dcm_01042] Definition of Port ServiceRequestSupplierNotifica-

tion_{Name} required by module Dcm d
Name ServiceRequestSupplierNotification_{Name}
Kind RequiredPort Interface ServiceRequestNotification
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceRequestSupplierNotification)} != NULL)
Name = {ecuc(Dcm/DcmConfigSet/DcmDsd/DcmDsdServiceRequestSupplier
Notification.SHORT-NAME)}

8.8.5.11 RoutineServices_{RoutineName}

[SWS_Dcm_01040] Definition of Port RoutineServices_{RoutineName} required

by module Dcm d
Name RoutineServices_{RoutineName}
Kind RequiredPort Interface RoutineServices_{RoutineName}
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.DcmDspRoutineUsePort)} == TRUE
RoutineName = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRoutine.SHORT-NAME)}

476 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.5.12 SecurityAccess_{SecurityLevel}

[SWS_Dcm_01041] Definition of Port SecurityAccess_{SecurityLevel} required

by module Dcm d
Name SecurityAccess_{SecurityLevel}
Kind RequiredPort Interface SecurityAccess_{SecurityLevel}
Description –
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.DcmDspSecurityUse
Port)} == USE_ASYNCH_CLIENT_SERVER
SecurityLevel = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurity
Row.SHORT-NAME)}

8.8.5.13 Dcm_DiagnosticSessionControlModeSwitchInterface

[SWS_Dcm_91033] Definition of Port DiagnosticSessionControlModeSwitchIn-

terface provided by module Dcm d
Name DiagnosticSessionControlModeSwitchInterface
Kind ProvidedPort Interface Dcm_DiagnosticSessionControlModeSwitchInterface
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about the current Diagnostic Session
Variation –

8.8.5.14 Dcm_EcuResetModeSwitchInterface

[SWS_Dcm_91034] Definition of Port EcuResetModeSwitchInterface provided by

module Dcm d
Name EcuResetModeSwitchInterface
Kind ProvidedPort Interface Dcm_EcuResetModeSwitchInterface
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about an upcoming ECU Reset and
its type
Variation –

477 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.5.15 Dcm_ModeRapidPowerShutDownModeSwitchInterface

[SWS_Dcm_91035] Definition of Port ModeRapidPowerShutDownModeSwitchIn-

terface provided by module Dcm d
Name ModeRapidPowerShutDownModeSwitchInterface
Kind ProvidedPort Interface Dcm_ModeRapidPowerShutDownModeSwitchInterface
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about the rapid power shut down
mode
Variation –

8.8.5.16 Dcm_CommunicationControlModeSwitchInterface_{ComMChannel-
Name}

[SWS_Dcm_91036] Definition of Port CommunicationControlModeSwitchInter-

face_{ComMChannelName} provided by module Dcm d
Name CommunicationControlModeSwitchInterface_{ComMChannelName}
Kind ProvidedPort Interface CommunicationControlModeSwitchInterface_{ComM
ChannelName}
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about the communication control of
the indicated ComM channel
Variation ComMChannelName = {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspCom
ControlAllChannel/DcmDspAllComMChannelRef->ComMChannel.SHORT-NAME)} or {ecuc(Dcm/
DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspComControlSpecificChannel/DcmDsp
SpecificComMChannelRef->ComMChannel.SHORT-NAME)}

8.8.5.17 Dcm_ControlDTCSettingModeSwitchInterface

[SWS_Dcm_91037] Definition of Port ControlDTCSettingModeSwitchInterface

provided by module Dcm d
Name ControlDTCSettingModeSwitchInterface
Kind ProvidedPort Interface Dcm_ControlDTCSettingModeSwitchInterface
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about the DTC Setting mode
Variation –

478 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.5.18 Dcm_SecurityAccessModeSwitchInterface

[SWS_Dcm_91039] Definition of Port SecurityAccessModeSwitchInterface pro-

vided by module Dcm d
Name SecurityAccessModeSwitchInterface
Kind ProvidedPort Interface Dcm_SecurityAccessModeSwitchInterface
Description A ModeSwitchInterface PPortPrototype used to notify SW-Cs about the current Security Level
Variation –

8.8.5.19 Dcm_UploadDownloadServices

[SWS_Dcm_91084] Definition of Port UploadDownloadServices required by mod-

ule Dcm d
Name UploadDownloadServices
Kind RequiredPort Interface UploadDownloadServices
Description –
Variation ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspMemoryTransfer.DcmDspMemoryTransferUsePort)}
== TRUE) || ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspRequestFileTransfer/DcmRequestFile
TransferUsePort)} == TRUE)

8.8.5.20 Dcm_Authentication_{Connection}

[SWS_Dcm_91073] Definition of Port Authentication_{Connection} provided by

module Dcm d
Name Authentication_{Connection}
Kind ProvidedPort Interface Authentication
Description –
Port Defined Type uint16
Argument Value(s)
Value {ecuc(Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/
DcmDslConnection/DcmDslMainConnection.DcmDslProtocolRxConnectionId
)}
Variation Connection = { Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDsl
Connection/DcmDslMainConnection.Short-Name)}

479 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.5.21 Dcm_AuthenticationStateMSI

[SWS_Dcm_91075] Definition of Port AuthenticationStateModeSwitchInter-

face_{Connection} provided by module Dcm d
Name AuthenticationStateModeSwitchInterface_{Connection}
Kind ProvidedPort Interface Dcm_AuthenticationStateModeSwitchInterface_{
Connection}
Description –
Variation Connection = Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDsl
Connection/DcmDslMainConnection.Short-Name

8.8.6 ModeDeclarationGroups

8.8.6.1 DcmDiagnosticSessionControl

[SWS_Dcm_91019] Definition of ModeDeclarationGroup DcmDiagnosticSession

Control d
Name DcmDiagnosticSessionControl
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_DEFAULT_SESSION
On transition value 255
Modes DCM_DEFAULT_SESSION 0
DCM_PROGRAMMING_SESSION 1
DCM_EXTENDED_DIAGNOSTIC_SESSION 2
DCM_SAFETY_SYSTEM_DIAGNOSTIC_SESSION 3
Description ModeDeclarationGroup representing the different diagnostic sessions
Further modes to be added: {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSession/
DcmDspSessionRow.SHORT-NAME)}

Note: According [SWS_Dcm_CONSTR_06001] there are standardized mode dec-

laration which are part of the standardized AUTOSAR interface. Note: Refer
[ecuc_sws_2108] defining the symbolic name prefix

480 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.6.2 DcmEcuReset

[SWS_Dcm_91021] Definition of ModeDeclarationGroup DcmEcuReset d

Name DcmEcuReset
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_NONE
On transition value 255
Modes DCM_NONE 0
DCM_HARD 1
DCM_KEYONOFF 2
DCM_SOFT 3
DCM_JUMPTOBOOTLOADER 4
DCM_JUMPTOSYSSUPPLIERBOOTLOADER 5
DCM_EXECUTE 6
Description ModeDeclarationGroup representing the different ECU reset types

8.8.6.3 DcmModeRapidPowerShutDown

[SWS_Dcm_91023] Definition of ModeDeclarationGroup DcmModeRapidPower

ShutDown d
Name DcmModeRapidPowerShutDown
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_ENABLE_RAPIDPOWERSHUTDOWN
On transition value 255
Modes DCM_ENABLE_RAPIDPOWERSHUTDOWN 0
DCM_DISABLE_RAPIDPOWERSHUTDOWN 1
Description ModeDeclarationGroup representing the enable/disable state of rapid power
shutdown

481 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.6.4 DcmCommunicationControl

[SWS_Dcm_91025] Definition of ModeDeclarationGroup DcmCommunication

Control d
Name DcmCommunicationControl
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_ENABLE_RX_TX_NORM_NM
On transition value 255
DCM_ENABLE_RX_TX_NORM 0
Modes
DCM_ENABLE_RX_DISABLE_TX_NORM 1
DCM_DISABLE_RX_ENABLE_TX_NORM 2
DCM_DISABLE_RX_TX_NORMAL 3
DCM_ENABLE_RX_TX_NM 4
DCM_ENABLE_RX_DISABLE_TX_NM 5
DCM_DISABLE_RX_ENABLE_TX_NM 6
DCM_DISABLE_RX_TX_NM 7
DCM_ENABLE_RX_TX_NORM_NM 8
DCM_ENABLE_RX_DISABLE_TX_NORM_NM 9
DCM_DISABLE_RX_ENABLE_TX_NORM_NM 10
DCM_DISABLE_RX_TX_NORM_NM 11
Description ModeDeclarationGroup representing the different communication control states

8.8.6.5 DcmControlDTCSetting

[SWS_Dcm_91027] Definition of ModeDeclarationGroup DcmControlDTCSetting

d
Name DcmControlDTCSetting
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_ENABLEDTCSETTING
On transition value 255
Modes DCM_ENABLEDTCSETTING 0
DCM_DISABLEDTCSETTING 1
Description ModeDeclarationGroup representing the enable/disable state for DTC storage

482 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.6.6 DcmSecurityAccess

[SWS_Dcm_91031] Definition of ModeDeclarationGroup DcmSecurityAccess d

Name DcmSecurityAccess
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_SEC_LEV_LOCKED
On transition value 255
Modes DCM_SEC_LEV_LOCKED 0
Description ModeDeclarationGroup representing the different diagnostic security levels
Further modes to be added: {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDsp
Security/DcmDspSecurityRow.SHORT-NAME)}

8.8.6.7 DcmAuthenticationState

[SWS_Dcm_91067] Definition of ModeDeclarationGroup DcmAuthentication

State_{Connection} d
Name DcmAuthenticationState_{Connection}
Kind ModeDeclarationGroup
Category EXPLICIT_ORDER
Initial mode DCM_DEAUTHENTICATED
On transition value 255
Modes DCM_DEAUTHENTICATED 0
DCM_AUTHENTICATED 1
Description Representing the authentication state of a diagnostic connection.

483 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.7 Mode-Switch-Interfaces

8.8.7.1 Dcm_DiagnosticSessionControlModeSwitchInterface

[SWS_Dcm_91020] Definition of ModeSwitchInterface Dcm_DiagnosticSession

ControlModeSwitchInterface d
Name Dcm_DiagnosticSessionControlModeSwitchInterface
Comment A SW-C that wants to get informed about the current Diagnostic Session requires the Mode
SwitchInterface Dcm_DiagnosticSessionControlModeSwitchInterface
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSession/DcmDspSessionRow.SHORT-NAME)}
ModeGroup diagnosticSession DcmDiagnosticSessionControl

8.8.7.2 Dcm_EcuResetModeSwitchInterface

[SWS_Dcm_91022] Definition of ModeSwitchInterface Dcm_EcuResetMode

SwitchInterface d
Name Dcm_EcuResetModeSwitchInterface
Comment A SW-C that wants to get informed about an upcoming ECU Reset requires the ModeSwitch
Interface Dcm_EcuResetModeSwitchInterface
IsService true
Variation –
ModeGroup ecuReset DcmEcuReset

8.8.7.3 Dcm_ModeRapidPowerShutDownModeSwitchInterface

[SWS_Dcm_91024] Definition of ModeSwitchInterface Dcm_ModeRapidPower

ShutDownModeSwitchInterface d
Name Dcm_ModeRapidPowerShutDownModeSwitchInterface
Comment A SW-C that wants to get informed about the rapid power shut down mode requires the Mode
SwitchInterface Dcm_ModeRapidPowerShutDownModeSwitchInterface
IsService true
Variation –
ModeGroup modeRapidPowerShutDown DcmModeRapidPowerShutDown

484 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

8.8.7.4 Dcm_CommunicationControlModeSwitchInterface

[SWS_Dcm_91026] Definition of ModeSwitchInterface CommunicationControl

ModeSwitchInterface_{ComMChannelName} d
Name CommunicationControlModeSwitchInterface_{ComMChannelName}
Comment A SW-C that wants to get informed about the communication control of a ComM channel
requires the ModeSwitchInterface Dcm_CommunicationControlModeSwitchInterface
IsService true
Variation ComMChannelName = ({ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspCom
ControlAllChannel/DcmDspAllComMChannelRef->ComMChannel.SHORT-NAME)} ||
{ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspComControl/DcmDspComControlSpecificChannel/
DcmDspSpecificComMChannelRef->
ModeGroup communicationControl DcmCommunicationControl

8.8.7.5 Dcm_ControlDTCSettingModeSwitchInterface

[SWS_Dcm_91028] Definition of ModeSwitchInterface Dcm_ControlDTCSetting

ModeSwitchInterface d
Name Dcm_ControlDTCSettingModeSwitchInterface
Comment A SW-C that wants to get informed about the DTC Setting mode requires the ModeSwitch
Interface Dcm_ControlDTCSettingModeSwitchInterface
IsService true
Variation –
ModeGroup controlDTCSetting DcmControlDTCSetting

8.8.7.6 Dcm_SecurityAccessModeSwitchInterface

[SWS_Dcm_91032] Definition of ModeSwitchInterface Dcm_SecurityAccess

ModeSwitchInterface d
Name Dcm_SecurityAccessModeSwitchInterface
Comment A SW-C that wants to get informed about the current Security Level requires the ModeSwitch
Interface Dcm_SecurityAccessModeSwitchInterface
IsService true
Variation {ecuc(Dcm/DcmConfigSet/DcmDsp/DcmDspSecurity/DcmDspSecurityRow.SHORT-NAME)}
5

485 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
ModeGroup securityAccess DcmSecurityAccess

8.8.7.7 Dcm_AuthenticationStateModeSwitchInterface

[SWS_Dcm_91074] Definition of ModeSwitchInterface Dcm_AuthenticationState

ModeSwitchInterface_{Connection} d
Name Dcm_AuthenticationStateModeSwitchInterface_{Connection}
Comment –
IsService true
Variation Connection = Dcm/DcmConfigSet/DcmDsl/DcmDslProtocol/DcmDslProtocolRow/DcmDsl
Connection/DcmDslMainConnection.Short-Name
ModeGroup authenticationState DcmAuthenticationState

8.9 External diagnostic service processing

The following chapter applies only to external processed diagnostic services.

8.9.1 <Module>_<DiagnosticService>

[SWS_Dcm_00763] Definition of configurable interface <Module>_<Diagnostic

Service> d
Service Name <Module>_<DiagnosticService>
Syntax Std_ReturnType <Module>_<DiagnosticService> (
Dcm_ExtendedOpStatusType OpStatus,
Dcm_MsgContextType* pMsgContext,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x7e
Sync/Async Asynchronous
Reentrancy Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK DCM_POS_RESPONSE_SENT DCM_POS_
RESPONSE_FAILED DCM_NEG_RESPONSE_SENT DCM_
NEG_RESPONSE_FAILED
5

486 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Parameters (inout) pMsgContext Message-related information for one diagnostic protocol identifier.
The pointers in pMsgContext shall point behind the SID.
Parameters (out) ErrorCode If the operation <Module>_<DiagnosticService> returns value E_
NOT_OK, the Dcm module shall send a negative response with
NRC code equal to the parameter ErrorCode parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application requests the transmission of
a response Response Pending (NRC 0x78)
Description Callout function. The Dcm shall call this callout function as soon as valid message is received
on relevant DcmDslProtocolRxPduId on SID level. The usecase of multiple diagnostic protocols
will be possible by using different arguments and the function shall be programmed in a way
that it is reentrant. Caller is responsible for the lifetime of the argument pMsgContext. The
name of the callout is defined within parameter DcmDsdSidTabFnc
Available via Dcm_Externals.h

8.9.2 <Module>_<DiagnosticService>_<SubService>

[SWS_Dcm_00764] Definition of configurable interface <Module>_<Diagnostic

Service>_<SubService> d
Service Name <Module>_<DiagnosticService>_<SubService>
Syntax Std_ReturnType <Module>_<DiagnosticService>_<SubService> (
Dcm_ExtendedOpStatusType OpStatus,
Dcm_MsgContextType* pMsgContext,
Dcm_NegativeResponseCodeType* ErrorCode
)
Service ID [hex] 0x33
Sync/Async Asynchronous
Reentrancy Reentrant
Parameters (in) OpStatus DCM_INITIAL DCM_PENDING DCM_CANCEL DCM_FORCE_
RCRRP_OK DCM_POS_RESPONSE_SENT DCM_POS_
RESPONSE_FAILED DCM_NEG_RESPONSE_SENT DCM_
NEG_RESPONSE_FAILED
Parameters (inout) pMsgContext Message-related information for one diagnostic protocol identifier.
The pointers in pMsgContext shall point behind the SID.
Parameters (out) ErrorCode If the operation <Module>_<DiagnosticService>_<SubService>
returns value E_NOT_OK, the Dcm module shall send a negative
response with NRC code equal to the parameter ErrorCode
parameter value.
Return value Std_ReturnType E_OK: Request was successful
E_NOT_OK: Request was not successful
DCM_E_PENDING: Request is not yet finished
DCM_E_FORCE_RCRRP: Application requests the transmission of
a response Response Pending (NRC 0x78)
5

487 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Description Callout function. If a DcmDsdSubServiceFnc is configured for the received subservice, the Dcm
shall call this callout function as soon as this subservice is requested. The usecase of multiple
diagnostic protocols will be possible by using different arguments and the function shall be
programmed in a way that it is reentrant. Caller is responsible for the lifetime of the argument p
MsgContext. The name of the callout is defined within parameter DcmDsdSubServiceFnc.
Available via Dcm_Externals.h

8.10 Internal interfaces (not normative)

The following interfaces are used in the Dcm SWS in order to improve the understand-
ing of the Dcm module behavior. An implementation is not required to use these inter-
faces.

8.10.1 DslInternal_SetSecurityLevel

1 void
2 DslInternal_SetSecurityLevel(Dcm_SecLevelType SecurityLevel)

This function sets a new security level value in the Dcm module. NOTE: for the definition
of the parameter, refer to Dcm_GetSecurityLevel.
8.10.2 DslInternal_SetSesCtrlType

1 void
2 DslInternal_SetSesCtrlType(Dcm_SesCtrlType SesCtrlType)

This function sets a new session control type value in the Dcm module. NOTE: for the
definition of the parameter, refer to the Dcm_GetSesCtrlType.
8.10.3 DspInternal_DcmConfirmation

1 void
2 DspInternal_DcmConfirmation(Dcm_IdContextType idContext,
3 uint16 ConnectionId
4 Dcm_ConfirmationStatusType status)

This function confirms the successful transmission or a transmission error of a diag-

nostic service. This is the right time to perform any application state transitions.
This API is also called if the response to a diagnostic service is suppressed.
8.10.4 DslInternal_ResponseOnOneEvent

1 Dcm_StatusType
2 DslInternal_ResponseOnOneEvent(const Dcm_MsgType MsgPtr,
3 Dcm_MsgLenType MsgLen,

488 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4 uint16 ConnectionId)

This API executes the processing of one event, requested internally in the DCM.
8.10.5 DslInternal_ResponseOnOneDataByPeriodicId

1 Dcm_StatusType
2 DslInternal_ResponseOnOneDataByPeriodicId(uint8 PeriodicId)

This API provides the processing of one periodic ID event, requested internally in the
DCM. The frequency of calling this function depends on the rate given in the original
ReadDataByPeriodicID request (parameter transmissionMode).
8.10.6 DsdInternal_StartPagedProcessing

1 void
2 DsdInternal_StartPagedProcessing(const Dcm_MsgContextType* pMsgContext)

With this API, the DSP submodule gives the complete response length to the Dcm mod-
ule and starts paged-buffer handling. This API starts no transmission!
8.10.7 DspInternal_CancelPagedBufferProcessing

1 void
2 DspInternal_CancelPagedBufferProcessing()

Dcm informs DSP, that processing of paged-buffer was cancelled due to errors. Upon
this call, DSP is not allowed to process further on paged-buffer handling.
8.10.8 DsdInternal_ProcessPage

1 void
2 DsdInternal_ProcessPage(Dcm_MsgLenType FilledPageLen)

DSP requests transmission of filled page.

489 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9 Sequence diagrams

9.1 Overview
For clarification, the following sequence diagrams don’t represent the full communica-
tion mechanism between the Dcm module and the PduR module. This is to keep the
sequence diagrams simple. Before the Dcm_TpRxIndication call, the PduR mod-
ule will ask the Dcm module for a buffer by calling Dcm_StartOfReception and
Dcm_CopyRxData. This exchange is not shown on the next sequence diagrams. Af-
ter a PduR_DcmTransmit() request from the Dcm module to the PduR module, data
exchanges with Dcm_CopyTxData service, are not shown in the sequence diagrams.
The function Xxx_StartProtocol() shall be called with the very first diagnostic request.

490 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.2 DSL (Diagnostic Session Layer)

9.2.1 Process Busy behavior

«module» «module» «module» External Module «module»

PduR Dsl Dsd Dsp


Dcm_TpRxIndication(PduIdType,
Std_ReturnType)

  <Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Data_Indication_functionality() Dcm_NegativeResponseCodeType**)

Data_Indication_functionality()

Dcm_TpRxIndication()

alt response?

[negative response: RC=0x78]

PduR_DcmTransmit(Std_ReturnType, PduIdType,
const PduInfoType*): Std_ReturnType

 
PduR_DcmTransmit()

PduR_DcmTransmit(Std_ReturnType, PduIdType,
const PduInfoType*): Std_ReturnType

PduR_DcmTransmit()

[positive response]
Dcm_TpTxConfirmation(PduIdType,
NotifResultType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.1: Process Busy Behavior

Internally, the DSL submodule calculates the time to response the tester. In the
case that the external module processing the request doesn’t close the request
by returning E_OK or E_NOT_OK to <Module>_<DiagnosticService>() or <Mod-
ule>_<DiagnosticService>_<SubService>() APIs call (in case of normal response han-
dling) or DsdInternal_ProcessPage() (in case of paged-buffer handling) during the
P2ServerMax and/or P2*ServerMax, the DSL submodule sends a negative response
(requestCorectlyReceived-ResponsePending) independently.

491 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.2.2 Update Diagnostic Session Control when timeout occurs

«module» «module» «module» External Module «module»

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,
   
  
Std_ReturnType)
 

Data_Indication_functionality() <Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

Data_Indication_functionality()

Dcm_TpRxIndication()

Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()


Data_Confimation_functionality()

Dcm_TpTxConfirmation()

Figure 9.2: Update Diagnostic Session Control when timeout occurs

The DSL submodule resets session control value to default, if in a non-default ses-
sion S3server timeout occurs. S3server timeout timer will be started with every data
confirmation from the PduR module.

492 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.2.3 Process single response of ReadDataByPeriodicIdentifier

«module» «module» «module» «module» Dcm User

PduR Dsl Dsd Dsp

ref

  Receive a request message ... - synchronous
  
     
       

ref
Receive a request message ... - asynchronous


                !  "
#!    #      !  $ %

&   DslInternal_ResponseOnOneDataByPeriodicId(uint8)

 
Data_Indication_functionality()

ReadDataByIdentifier service interpreter()

ReadData(Did specific type):

Std_ReturnType

DspInternal_DcmReadDataByIdentifier()



Data_Indication_functionality()

DslInternal_ResponseOnOneDataByPeriodicId()

Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.3: Process single response of ReadDataByPeriodicIdentifier

The DSP submodule requests sampling and transmission of Periodic Identifier data,
when an event to Periodic Identifier occurs (i. e. a given time period is over). The DSP
submodule initiates the sending of one periodic identifier calling the function Respon-
seOnOneDataByPeriodicId() provided by the DSL submodule.
Within this function the DSL submodule simulates a "ReadDataByIdentifier" request
for the given PeriodicId. The High byte of the DataIdentifier shall be set to 0xF2 as
specified in [19]) and the low byte is set to value of the PeriodicId.
The ReadData interfaces of the corresponding Datas of the DID are called to get the
DID value. The Dcm module is not able to receive for the same periodic identifier

493 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

another event request from the DSP submodule, unless the confirmation of the current
transmission is received.

9.2.4 Process single event-triggered response of ResponseOnEvent

«module» «module» «module» «module» Dcm User

PduR Dsl Dsd Dsp

ref
Receive a request message ... - synchronous


  
      
        
 ref
Receive a request message ... - asynchronous

                !      

    "  #    #      
     !   

  DslInternal_ResponseOnOneEvent(const Dcm_MsgType, Dcm_MsgLenType, uint16)


Data_Indication_functionality()

ReadDataByIdentifier service interpreter()

ReadData(Did specific type):

Std_ReturnType

  DspInternal_DcmReadDataByIdentifier()

Data_Indication_functionality()

DslInternal_ResponseOnOneEvent()

Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

Data_Confirmation_functionality()
DspInternal_DcmConfirmation(Dcm_IdContextType, PduIdType,
Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.4: Process single event-triggered response of ResponseOnEvent

This sequence diagram shows an example for ResponseOnEvent. ResponseOnEvent

is setup and started for onDTCStatusChange. Event changes are reported to the Dcm
which will trigger a serviceToRespondTo.

494 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.2.5 Process concurrent requests

«module» «module» «module» External Module «module» Dcm User

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,

 Std_ReturnType)

Data_Indication_functionality() <Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)



 Dcm_TpRxIndication(PduIdType,
Std_ReturnType)
Data_Indication_functionality()

Stop_Protocol_functionality()

Stop_Protocol_functionality()
Data_Indication_functionality()

PduR_DcmCancelTransmitRequest()

 PduR_DcmTransmit(Std_ReturnType,

  PduIdType, const PduInfoType*):
Std_ReturnType

PduR_DcmTransmit()

Dcm_TpRxIndication()

<Module>_<DiagnosticService>()

Data_Indication_functionality()

Dcm_TpRxIndication()

  Dcm_TpRxIndication(PduIdType,
Std_ReturnType)

 
 Data_Indication_functionality()
 !

Figure 9.5: Process concurrent requests

On reception of OBD request in parallel to processing of a normal diagnostic request

(e.g enhanced diagnostic protocol, customer diagnostic protocol), running diagnostic
request will be preempted. This is due to the configured higher priority of OBD protocol
(see configuration parameter DcmDslProtocolPriority).
The following is processed on reception of 1st OBD request:
• The Application is informed of the protocol stop (done with Xxx_StopProtocol())
and resets to a stable state (e.g. switch of digital Ios,..).

495 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

• Lower Layer is requested to cancel ongoing transmission on the same N-PDU

(done with PduR_DcmCancelTransmitRequest()).
• If the Dcm is not able to switch fast enough from non OBD to OBD protocol, the DSL
submodule responses with a negative response "BusyRepeatRequest" (NRC
0x21) to OBD tester. It is in the responsibility of the system designer to ensure
that the legislative timings are satisfied.
As long as the external module processing the request is not fin-
ished (finish is indicated by returning E_OK or E_NOT_OK to <Mod-
ule>_<DiagnosticService>()/<Module>_<DiagnosticService>_<SubService>() API
call) or no timeout occurs, the DSL submodule responses with negative response
"BusyRepeatRequest".
With receiving E_OK or E_NOT_OK from the external module to <Mod-
ule>_<DiagnosticService>()/<Module>_<DiagnosticService>_<SubService>() API
call, the DSL submodule will not transmit a response to old request. There will also
not given any negative response to inform first tester about preemption of diagnostic
request.
If the external module processing the request never returns E_OK or E_NOT_OK
to <Module>_<DiagnosticService>()/<Module>_<DiagnosticService>_<SubService>()
API call, the DSL submodule runs into timeout and switches directly to further process-
ing of preempting protocol.

496 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.2.6 Interface to ComManager

9.2.6.1 Handling in Default Session

«module» «module» «module» External Module «module»

PduR Dcm ComM Dsp

Dcm_TpRxIndication(PduIdType,

 Std_ReturnType)

ComM_DCM_ActiveDiagnostic(NetworkHandleType)

ComM_DCM_ActiveDiagnostic()

<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType, Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

Dcm_TpRxIndication()

  Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

DspInternal_DcmConfirmation(Dcm_IdContextType, PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

ComM_DCM_InactiveDiagnostic(NetworkHandleType)

ComM_DCM_InactiveDiagnostic()

Dcm_TpTxConfirmation()

Figure 9.6: Handling in Default Session

497 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.2.6.2 Handling in Non-Default Session

«module» «module» «module» External Module «module»

PduR Dcm ComM Dsp

Dcm_TpRxIndication(PduIdType,

 Std_ReturnType)

<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

Dcm_TpRxIndication()

 
Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

DspInternal_DcmConfirmation(Dcm_IdContextType, PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Dcm_TpTxConfirmation()

Figure 9.7: Handling in Non-Default Session

9.2.6.3 Session transitions

«module» «module»
Dsl ComM

  Session transition: Default to

 Non-Default()

ComM_DCM_ActiveDiagnostic(NetworkHandleType)

ComM_DCM_ActiveDiagnostic()

Session transition: Non-

default to Default()

  ComM_DCM_InactiveDiagnostic(NetworkHandleType)


ComM_DCM_InactiveDiagnostic()

Figure 9.8: Session transitions

498 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.2.6.4 Communication States

«module» «module»
ComM Dcm

   Dcm_ComM_NoComModeEntered(uint8)

Disable Transmission of ROE

and PeriodicID()

Disable normal Transmission

(receive and transmit)
Dcm_ComMNoComModeEntered() (PduR_DcmTransmit)

 
  Dcm_ComM_SilentComModeEntered(uint8)

Disable Transmission of ROE

and PeriodicID()

Disable normal transmission

(transmit) (PduR_DcmTransmit)
Dcm_ComMSilentComModeEntered()

   Dcm_ComM_FullComModeEntered(uint8)

Enable Transmission of ROE

and PeriodicID()

Enable normal Transmission

(PduR_DcmTransmit)
Dcm_ComMFullComModeEntered()

Figure 9.9: Communication States Overview

DSD (Diagnostic Service Dispatcher) Receive a request message and transmit a posi-
tive response message - synchronous transmission

499 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

«module» «module» «module» External Module «module»

PduR Dsl Dsd Dsp

 Dcm_TpRxIndication(PduIdType,
Std_ReturnType)

Data_Indication_functionality()
<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

 

Data_Indication_functionality()

Dcm_TpRxIndication()

Dcm_TpTxConfirmation(PduIdType,
NotifResultType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.10: synchronous transmission

Receive a request message and transmit a positive response message - asynchronous

transmission
«module» «module» «module» External Module «module»
PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,

 Std_ReturnType)

Data_Indication_functionality()
<Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

Data_Indication_functionality()

Dcm_TpRxIndication()

Dcm_TpTxConfirmation(PduIdType,

 
NotifResultType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.11: asynchronous transmission

500 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Receive a request message and suppress a positive response

«module» «module» «module» External Module «module»
PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,

 Std_ReturnType)

Data_Indication_functionality() <Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType,
Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

 
Data_Indication_functionality()

Dcm_TpRxIndication()

Figure 9.12: Mechanism of receiving a message and suppressing a positive response

9.2.7 Receive request message and transmit negative response message

«module» «module» «module» External Module «module»

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,

 Std_ReturnType)

Data_Indication_functionality() <Module>_<DiagnosticService>(Std_ReturnType,
Dcm_ExtendedOpStatusType, Dcm_MsgContextType**,
Dcm_NegativeResponseCodeType**)

 
<Module>_<DiagnosticService>()

Data_Indication_functionality()

Dcm_RxIndication()

Dcm_TpTxConfirmation(PduIdType,
NotifResultType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.13: Mechanism of receiving a request message and transmitting a negative

response message

501 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.2.8 Process Service Request with paged-buffer

«module» «module» «module» «module»

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,


Std_ReturnType)
Data_Indication_functionality()
service interpreter call()

  DsdInternal_StartPagedProcessing(const
Dcm_MsgContextType*)

DspInternal_DcmUpdatePage(Dcm_MsgType, Dcm_MsgLenType)

DspInternal_DcmUpdatePage()

DspInternal_StartPagedProcessing()

service interpreter call()

DsdInternal_ProcessPage(Dcm_MsgLenType)
   PduR_DcmTransmit(Std_ReturnType,
  Transmit_functionality()
PduIdType, const PduInfoType*):
Std_ReturnType

Dcm_CopyTxData(BufReq_ReturnType, PduIdType,
PduInfoType*, RetryInfoType*, PduLengthType*)

Dcm_CopyTxData=BUFREQ_E_BUSY()

loop transmit
Dcm_CopyTxData(BufReq_ReturnType, PduIdType,
PduInfoType*, RetryInfoType*, PduLengthType*)
Data_Confirmation_functionality()
DspInternal_DcmUpdatePage(Dcm_MsgType,
Dcm_MsgLenType)

DsdInternal_ProcessPage(Dcm_MsgLenType)

Transmit_functionality()

Dcm_CopyTxData(BufReq_ReturnType, PduIdType,
PduInfoType*, RetryInfoType*, PduLengthType*)

Dcm_CopyTxData=BUFREQ_OK()

Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

Data_Confirmation_functionality()
   DspInternal_DcmConfirmation(Dcm_IdContextType,
  PduIdType, Dcm_ConfirmationStatusType)

Figure 9.14: Process Service Request with paged-buffer

The following flow is processed in case no error occurs on the Application side:

502 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Start of process:
4) DsdInternal_StartPagedProcessing(): With this API, the DSP submodule gives the
complete response length to the Dcm module and starts paged-buffer handling. This
API starts no transmission!
5) UpdatePage(): The Dcm module requests data to be transmitted.
6) DsdInternal_ProcessPage(): With this API, the DSP submodule requests transmis-
sion of the current page.
8) PduR_DcmTransmit(): The Dcm module requests transmission to the lower layers.
9) Dcm_CopyTxData: The buffer is filled and the Dcm module shall return
"BUFREQ_OK"(10).

Start of the loop:

11) Dcm_CopyTxData: The PduR module requests the buffer but the buffer is not
filled by the DSP submodule.
12 + 13) UpdatePage: The Dcm module requests the DSP submodule to fill the next
page.
14) By returning "BUFREQ_E_BUSY", the Dcm module indicates that the buffer has to
be filled by the DSP submodule.
15) DsdInternal_ProcessPage(): With this API, the DSP submodule requests transmis-
sion of the current page.
17) Then, on the next call of Dcm_CopyTxData the buffer is filled and the Dcm module
shall return "BUFREQ_OK" (18).

LOOP: The flow 10 to 18 is repeated as long data can be sent.

End of the loop:
n-2 -> n) Dcm_TpTxConfirmation When all data is send, the PduR module indicates
the sending with a confirmation, which is given to the DSP submodule.
The APIs 4, 5 and 6 are needed only for paged-buffer transmission.
Page buffer timeout handling:

The Dcm module reacts in the following described way, when the DSP submodule starts
paged-buffer handling, but is not able to process further on filling the response data.
E.g. there are problems to access data from an EEPROM device. When providing
the Pagebuffer to the DSP submodule (13: UpdatePage()), and getting a negative Tx
confirmation from underlying Transport Layers, the following error handling is carried
out in the Dcm module:
• The Dcm module stops further processing of paged-buffer (item 15),
• The Dcm module requests the DSP submodule (14: DspInter-
nal_CancelPagedBufferProcessing()) to stop further processing of PagedBuffer.

503 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

«module» «module» «module» «module»

PduR Dsl Dsd Dsp

Dcm_TpRxIndication

 (PduIdType, Std_ReturnType)
Data_Indication_functionality()

DspInternal_Dcm<DiagnosticService>(Dcm_MsgContextType)

  DsdInternal_StartPagedProcessing(const Dcm_MsgContextType*)

DspInternal_DcmUpdatePage(Dcm_MsgType, Dcm_MsgLenType)

DspInternal_DcmUpdatePage()

DsdInternal_StartPagedProcessing()

DspInternal_Dcm<DiagnosticServices>()

DsdInternal_ProcessPage(Dcm_MsgLenType)
PduR_DcmTransmit(Std_ReturnType,
  Transmit_functionality()
 PduIdType, const PduInfoType*):
Std_ReturnType

Dcm_CopyTxData(BufReq_ReturnType, PduIdType,
PduInfoType*, RetryInfoType*, PduLengthType*)

Dcm_CopyTxData=BUFREQ_OK()

loop transmit
Dcm_CopyTxData(BufReq_ReturnType, PduIdType,
PduInfoType*, RetryInfoType*, PduLengthType*)
Data_Confirmation_functionality() DspInternal_DcmUpdatePage(Dcm_MsgType,
Dcm_MsgLenType)

Dcm_CopyTxData=BUFREQ_E_BUSY()

DspInternal_DcmCancelPagedBufferProcessing()

 

 

Data_Failed_Functionality()

Dcm_CopyTxData(BufReq_ReturnType, PduIdType,
PduInfoType*, RetryInfoType*, PduLengthType*)

Dcm_CopyTxData=BUFREQ_E_NOT_OK()

   Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)


Data_Confirmation_functionality() DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

Figure 9.15: Process Service Request when paged-buffer Timeout occurs

9.2.9 Process copy data in reception

Please refer to Figure 9 "CanTp I-PDU reception" in [14, SWS PduR].

504 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.2.10 Process copy data in transmission

Please refer to Figure 14 "CanTp I-PDU transmission" in [14, SWS PduR].

9.3 DSP (Diagnostic Service Processing)

9.3.1 Interface DSP - DEM (service 0x19, 0x14, 0x85)

Please refer to Section 9 in [20, SWS Dem].

9.3.2 Interface special services

9.3.2.1 Process Diagnostic Session Control

«module» «module» «module» «module»

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,
Std_ReturnType)

Data_Indication_functionality()

DiagnosticSessionControl service
interpreter()

Data_Indication_functionality()

Dcm_TpRxIndication()

Dcm_TpTxConfirmation(PduIdType,
Std_ReturnType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType,
PduIdType, Dcm_ConfirmationStatusType)

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

Figure 9.16: Process Diagnostic Session Control

Above sequence diagram shows processing of Diagnostic Session Control request

from a tester. Note that the new diagnostic session and timing parameters only apply
after the transmission confirmation of the server positive response

505 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.3.2.2 Process Tester Present

«module» «module» «module» «module»

PduR Dsl Dsd Dsp

 Dcm_TpRxIndication(PduIdType,
  Std_ReturnType)
  
  Data_Indication_functionality()

TesterPresent service
interpreter()

TesterPresent service
interpreter()

Data_Indication_functionality()

Dcm_TpRxIndication()

Dcm_TpRxIndication(PduIdType,


  Std_ReturnType)
 
  Data_Indication_functionality()

TesterPresent service
interpreter()

TesterPresent service
interpreter()

Data_Indication_functionality()

Dcm_TpRxIndication()

Figure 9.17: Process Tester Present

Above sequence diagram shows processing of TesterPresent commands, which are

not of type functional addressed with subfunction 0x80. These TesterPresent com-
mands are interpreted in the DSL submodule (more details can be found in Section
7.2.4.3 Concurrent TesterPresent keep alive logic").
All the other TesterPresent commands are processed in the following way: On a com-
mand TesterPresent the DSD submodule calls the DSP submodule with the function
TesterPresent(). The sequence chart also shows the case when an error occurs and a
negative response is sent.

506 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.3.2.3 Process Security Access

«module» «module» «module» «module» Dcm User

PduR Dsl Dsd Dsp

  Dcm_TpRxIndication(PduIdType,

Std_ReturnType)

Data_Indication_functionality()

SecurityAccess service
interpreter()

GetSeed(Std_ReturnType, uint8*, Dcm_OpStatusType, uint8*,

Dcm_NegativeResponseCodeType*)

GetSeed()

  Dcm_TpRxIndication(PduIdType,

Std_ReturnType)

Data_Indication_functionality()
SecurityAccess service
interpreter()

CompareKey(Std_ReturnType,
uint8*, Dcm_OpStatusType)

Dcm_CompareKey()

Dcm_SetSecurityLevel(Dcm_SecLevelType)

Dcm_SetSecurityLevel()

Figure 9.18: Process Security Access

To get the security access, the DSD submodule has to call the DSP submodule to get
the seed value from the application. If no error is detected, the seed value is sent in
the positive response.
In a second step, the DSP submodule gets the key calculated by the tester and requests
the application to compare this key with the internal calculated key. If no error occurs,
the new access type is set in the DSL submodule and a positive response is sent.

507 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.3.2.4 Process ResponseOnEvent OnDtcChange

«module» «module» «module» «module» Dcm User

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,
Std_ReturnType)
Data_Indication_functionality()

ResponseOnEvent service
interpreter()

  
ResponseOnEvent service
 
Data_Indication_functionality() interpreter()
Dcm_TpRxIndication()
Configure Event()

    

Dcm_TpRxIndication(PduIdType,    
Std_ReturnType)

Data_Indication_functionality()
ResponseOnEvent service
interpreter()
 
 
 
ResponseOnEvent service
Data_Indication_functionality() interpreter()
Internal activation of DTC
Dcm_TpRxIndication() status supervision()

Dcm_DemTriggerOnDTCStatus()

Check DTC and

Status()

alt If DTC and Status fit to ROE configuration

DslInternal_ResponseOnOneEvent(MsgPtr,MsgLen,DcmRxPduId)
[TRUE]

Data_Indication_functionality()

ReadDTCInformation
service interpreter()

Dcm_DemTriggerOnDTCStatus()

[FALSE]

Dcm_TpRxIndication(PduIdType,
Std_ReturnType)

Data_Indication_functionality() ResponseOnEvent service

interpreter()

 
 

 
Data_Indication_functionality() ResponseOnEvent service
Dcm_TpRxIndication() interpreter()

Internal deactivation of
DTC status supervision()

Figure 9.19: Process ResponseOnEvent OnDtcChange

Above sequence diagram shows processing of ResponseOnEvent service for sub-

service OnDtcChange.
After configuration and activation of the event by the service ResponseOnEvent, the
Dcm checks the status of the configured DTC on every call to interface Dcm_DemTrig-
gerOnDTCStatus in order to identify if the event shall be trigger. This interface is

508 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

called by DEM for any DTC status change and independing of the activation/unactiva-
tion of ResponseOnEvent.

9.3.2.5 Process ResponseOnEvent OnChangeOfDataIdentifier

«module» «module» «module» «module» Dcm User

PduR Dsl Dsd Dsp

Dcm_TpRxIndication(PduIdType,
Std_ReturnType)
Data_Indication_functionality()
ResponseOnEvent service
interpreter()


     
 
ResponseOnEvent service
Data_Indication_functionality() interpreter()
Dcm_TpRxIndication()

     Configure Event()

  
Dcm_TpRxIndication(PduIdType,
Std_ReturnType)
Data_Indication_functionality()
ResponseOnEvent service
interpreter()
  

 
ResponseOnEvent service
interpreter()
Data_Indication_functionality()
Dcm_TpRxIndication()
              
         

DslInternal_ResponseOnOneEvent(MsgPtr, MsgLen, DcmRxPduId)

Data_Indication_functionality()
DspInternal_DcmReadDataByIdentifier(pMsgContext)

Xxx_ReadData()

Dcm_TpRxIndication(PduIdType,     

Std_ReturnType)
Data_Indication_functionality() ResponseOnEvent service
interpreter()

 

Data_Indication_functionality() ResponseOnEvent service
interpreter()
 
Dcm_TpRxIndication()

Figure 9.20: Process ResponseOnEvent OnChangeOfDataIdentifier

Above sequence diagram shows processing of ResponseOnEvent service for subser-

vice OnChangeOfDataIdentifier. After configuration and activation of the event by the
service ResponseOnEvent, Dcm compares values of all configured DID’s every time
ResponseOnEventSchedulerRate ellapses and triggers the event if the conditions are
met. On occurrence of this Event, Dcm will execute the service configured in service-
ToRespondToRecord.

509 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.3.2.6 Process Jump to Bootloader

«module» «module» «module» «module» «module»

PduR Dsl Dsd Dsp Dcm_Callouts

Dcm_TpRxIndication(PduIdType,
Std_ReturnType)

Data_Indication_functionality()

DiagnosticSessionControl service
interpreter()

DiagnosticSessionControl service
interpreter()

Data_Indication_functionality()

Dcm_TpRxIndication()

alt if Reset allowed

[TRUE]

Dcm_TpTxConfirmation(PduIdType, Std_ReturnType)

Data_Confirmation_functionality()

DspInternal_DcmConfirmation(Dcm_IdContextType, PduIdType,
Dcm_ConfirmationStatusType)

Dcm_SetProgConditions()

Dcm_SetProgConditions()

DspInternal_DcmConfirmation()

Data_Confirmation_functionality()

Dcm_TpTxConfirmation()

[FALSE]

Figure 9.21: Process Jump to Bootloader

Above sequence diagram shows processing of a jump to bootloader on reception of

DiagnosticSessionControl. On reception of DiagnosticSessionControl, the Dcm checks
if the requested session is configured to trigger a jump to bootloader. In positive case,
the Dcm start the jump to bootloader process:
• Transmission of NRC 0x78 (ResponsePending)
• On confirmation of transmission of NRC 0x78, the Dcm calls the callout DcmSet-
ProgConditions to store all information needed for the bootloader

510 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

9.3.2.7 Process IOControlRequest handling

«module» «module» «module»

Dcm Rte SWC
Tester
(from Dcm) (from Rte)
2F D001 00 80

Write IOControlRequest_{DID}

   
  
  
 
 !    $  %  !  
 

Write IOControlRequest_{DID}.IOOperationRequest

     
     
 !! "#

alt pos Response

[Read DataServices_{DID}]:

[data=0x1234]:

[positive response]:1 00 1234

[Read IOControlRequest_{DID}]:

[underControl]:

[isUpdatedWriteIOControlRequest_{DID}().IOOper...]:

[status]:

alt check IsUpdated

[Read IOControlRequest_{DID}().IOOperationRequest]:
Process
IOControlRequest
&    
 !! "#

[Write IOControlResponse_{DID}({Ack | Nack})]:

[Write DataServices_{DID}(data = 0x1234)]:

Figure 9.22: Process IOControlRequest handling with returnControlToECU as inputOut-

putControlParameter

511 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

«module» «module» «module»

Dcm Rte SWC
Tester

(from Dcm) (from Rte)

2F D001 03 1234 80
[Read IOControlResponse.IOOperationResponse]:
Write IOControlRequest_{DID}

   
  
 
 
 
& "#
 
&  ! ' 
(&  !  ) * +   # #  , ' -

Write IOControlRequest_{DID}.IOOperationRequest

&   ./ ' 

# #  , ' 
! "# $%

[Read IOControlRequest_{DID}]:
[underControl]:

[isUpdatedWriteIOControlRequest_{DID}().IOOper...]:
[status]:

alt Check IsUpdated

[TRUE] [Read IOControlRequest_{DID}().IOOperationRequest]:

[IOOperationRequest.inputOutputControlParameter]:

alt InputOutputControlParameter
[ResetToDefault (01)]

[freezeCurrentState (02)]

[shortTermAdjustment (03)]
[Read IOControlRequest_{DID}]:
[controlState = 0x1234]:

alt OperationStatus
[Pending]
[Write IOControlResponse_{DID}({Pending 0x78})]:

! "# $%

[Done]
[Write IOControlResponse_{DID}({Ack=0x00 | Nack})]:

[Write DataServices_{DID}(data=0x1234)]:

0120340 453673208 53 3096 :;<0===

Figure 9.23: Process IOControlRequest handling with shortTermAdjustment as in-

putOutputControlParameter part 1

512 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

«module» «module» «module»

Dcm Rte SWC
Tester
(from Dcm) (from Rte)

       

[IsUpdated IOControlResponse]:
[status]:

alt Check IsUpdated

[TRUE]
[Read IOControlResponse_{DID}]:

[IOOperationResponse]:

alt IOOpertionResponse

[Pending (0x78)]

7F 2F 78 (optional,
depending on timing)

[Done (0x00 | Nack)]

[Update underControl]:
underControl = 0x80 |
underControl

[Write IOControlRequest_{DID}.underControl]:

[Read DataServices_{DID}]:

[data = 0x1234]:

6F D001 03 1234

Figure 9.24: Process IOControlRequest handling with shortTermAdjustment as in-

putOutputControlParameter part 2

513 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10 Configuration specification
In general, this chapter defines configuration parameters and their clustering into con-
tainers. In order to support the specification Chapter 10.1 describes fundamentals.
It also specifies a template (table) you shall use for the parameter specification. We
intend to leave Chapter 10.1 in the specification to guarantee comprehension.
Chapter 10.2 specifies the structure (containers) and the parameters of the module
<MODULE_ABBREVIATION>.
Chapter 10.4 specifies published information of the module <MOD-
ULE_ABBREVIATION>.

10.1 How to read this chapter

For details refer to the chapter 10.1 "Introduction to configuration specification" in
SWS_BSWGeneral [8].

10.2 Containers and configuration parameters

The following chapters summarize all configuration parameters. The detailed meanings
of the parameters describe Chapter 7 and Chapter 8.

514 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

AUTOSARParameterDefinition:
EcucDefinitionCollection

+module

Dcm: EcucModuleDef

upperMultiplicity = 1
lowerMultiplicity = 0

+container +container

DcmConfigSet: EcucParamConfContainerDef DcmGeneral:

EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDsd:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDsl:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmPageBufferCfg:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDsp:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmProcessingConditions:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.1: Configuration overview

10.2.1 Dcm

[ECUC_Dcm_01082] Definition of EcucModuleDef Dcm d

Module Name Dcm
Description Configuration of the Dcm (Diagnostic Communications Manager) module.
Post-Build Variant Support true
Supported Config Variants VARIANT-LINK-TIME, VARIANT-POST-BUILD, VARIANT-PRE-COMPILE

515 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmConfigSet 1 This container contains the configuration parameters and sub
containers of the DCM module supporting multiple configuration
sets.
DcmGeneral 1 Contains general configuration parameters valid for the entire
Dcm module.

10.2.2 DcmConfigSet

[ECUC_Dcm_00819] Definition of EcucParamConfContainerDef DcmConfigSet d

Container Name DcmConfigSet
Parent Container Dcm
Description This container contains the configuration parameters and sub containers of the DCM
module supporting multiple configuration sets.
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDsd 1 These parameters configure the Diagnostic Service Dispatcher
submodule.
DcmDsl 1 These parameters configure the Diagnostic Session Layer
submodule.
DcmDsp 0..1 These parameters apply to Diagnostic Service Processing.
There will always be one set of these parameters per Dcm.
Please note: Although the multiplicity is set to 0..1. It can be
expected that this container exists in any valid DCM
configuration.
DcmPageBufferCfg 1 This container contains the configuration (parameters) for Page
Buffer handling
DcmProcessingConditions 0..1 This container contains the configuration for mode arbitration
functionality of the Dcm

10.2.2.1 DcmPageBufferCfg

[ECUC_Dcm_00775] Definition of EcucParamConfContainerDef DcmPageBuffer

Cfg d

516 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmPageBufferCfg

Parent Container DcmConfigSet
Description This container contains the configuration (parameters) for Page Buffer handling
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmPagedBufferEnabled 1 [ECUC_Dcm_00776]

No Included Containers

[ECUC_Dcm_00776] Definition of EcucBooleanParamDef DcmPagedBufferEn-

abled d
Parameter Name DcmPagedBufferEnabled
Parent Container DcmPageBufferCfg
Description Allow to enable or disable the Paged buffer mechanism. true = Paged buffer handling
enabled false = Paged Buffer handling disabled
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

DcmPageBufferCfg: DcmPagedBufferEnabled:
EcucParamConfContainerDef EcucBooleanParamDef
+parameter
lowerMultiplicity = 1 upperMultiplicity = 1
upperMultiplicity = 1 lowerMultiplicity = 1

Figure 10.2: DcmPageBufferCfg configuration overview

10.2.2.2 DcmProcessingConditions

[ECUC_Dcm_00932] Definition of EcucParamConfContainerDef DcmProcessing

Conditions d

517 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmProcessingConditions

Parent Container DcmConfigSet
Description This container contains the configuration for mode arbitration functionality of the Dcm
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmModeCondition 1..* This container contains the configuration of a mode condition or
an environmental conditions which can be used as argument in
DcmModeRules.
One DcmModeCondition shall contain either one DcmSwcMode
Ref or one DcmBswModeRef or one DcmSwcSRDataElement
Ref.
Please note that the Dcm acts as well as mode manager.
Therefore the references DcmSwcModeRef or one DcmBsw
ModeRef. might point to provided ModeDeclarationGroup
Prototypes of the Dcm itself as well as to provided Mode
DeclarationGroupPrototypes of other Bsw Modules or software
components.
In case of a configured DcmSwcModeRef or DcmBswModeRef
only the DcmConditionType DCM_EQUALS or DCM_EQUALS_
NOT are applicable.
In case of DcmSwcSRDataElementRef all literals of Dcm
ConditionType are possible.
DcmModeRule 1..* This container contains the configuration of a mode rule which
represents a logical expression with DcmModeConditions or
other DcmModeRules as arguments.
All arguments are processed with the operator defined by Dcm
LogicalOperator, for instance: Argument_A AND Argument_B
AND Argument_C

518 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmProcessingConditions:
EcucParamConfContainerDef +subContainer DcmLogicalOperator:
DcmModeRule: EcucEnumerationParamDef
lowerMultiplicity = 0 EcucParamConfContainerDef +parameter
upperMultiplicity = 1 lowerMultiplicity = 0
lowerMultiplicity = 1 upperMultiplicity = 1
upperMultiplicity = *

+destination +literal

DCM_OR:
EcucEnumerationLiteralDef
+literal

+reference DCM_AND:
+parameter EcucEnumerationLiteralDef

DcmArgumentRef: DcmModeRuleNrcValue:
+subContainer EcucChoiceReferenceDef EcucIntegerParamDef

DcmModeCondition: upperMultiplicity = * lowerMultiplicity = 0

EcucParamConfContainerDef +destination lowerMultiplicity = 1 upperMultiplicity = 1
requiresIndex = true min = 1
lowerMultiplicity = 1 max = 255
upperMultiplicity = *

DCM_EQUALS:
EcucEnumerationLiteralDef
+literal

DCM_GREATER_THAN:
EcucEnumerationLiteralDef
+literal

DCM_EQUALS_NOT:
EcucEnumerationLiteralDef
+literal

DCM_LESS_THAN:
EcucEnumerationLiteralDef
+literal

DCM_LESS_OR_EQUAL:
EcucEnumerationLiteralDef
+literal

DCM_GREATER_OR_EQUAL: +literal
EcucEnumerationLiteralDef DcmConditionType: EcucEnumerationParamDef

lowerMultiplicity = 1
upperMultiplicity = 1

+parameter

DcmModeConditionCertificateCompareElementRef: KeyMCertificateElement:
+reference EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 65535
requiresSymbolicNameValue = true
(from KeyM)

Figure 10.3: DcmDspProcessingConditions1 configuration overview

DcmModeCondition: DcmSwcSRDataElementRef:
EcucParamConfContainerDef EcucChoiceReferenceDef DcmDspPidService01ExternalSRDataElementClass:
+destination
+reference EcucChoiceContainerDef
lowerMultiplicity = 1 upperMultiplicity = 1
upperMultiplicity = * lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspPidService01:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+destination

DcmDspExternalSRDataElementClass: DcmDspData:
EcucChoiceContainerDef +subContainer EcucParamConfContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = *

+subContainer
DcmSwcDataElementPrimitive:
DcmSwcDataElementValue: EcucParamConfContainerDef +parameter DcmSwcDataElementPrimitiveValue:
+choice
EcucChoiceContainerDef EcucIntegerParamDef
lowerMultiplicity = 0
upperMultiplicity = 1

DcmSwcDataElementArray:
+choice EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer DcmSwcDataElementArrayElementIndex:
EcucIntegerParamDef
+parameter
DcmSwcDataElementArrayElement:
EcucParamConfContainerDef

lowerMultiplicity = 0 +parameter
upperMultiplicity = * DcmSwcDataElementArrayElementValue:
EcucIntegerParamDef

+reference

DcmBswModeRef: EcucInstanceReferenceDef

lowerMultiplicity = 0
upperMultiplicity = 1
destinationType = MODE-DECLARATION
destinationContext = MODE-DECLARATION-GROUP-PROTOTYPE

+reference

DcmSwcModeRef: EcucInstanceReferenceDef

lowerMultiplicity = 0
upperMultiplicity = 1
destinationType = MODE-DECLARATION
destinationContext = ROOT-SW-COMPOSITION-PROTOTYPE SW-COMPONENT-PROTOTYPE P-PORT-PROTOTYPE MODE-DECLARATION-GROUP-PROTOTYPE

Figure 10.4: DcmDspProcessingConditions2 configuration overview

519 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.3 DcmDsd

10.2.3.1 DcmDsd

[ECUC_Dcm_00688] Definition of EcucParamConfContainerDef DcmDsd d

Container Name DcmDsd
Parent Container DcmConfigSet
Description These parameters configure the Diagnostic Service Dispatcher submodule.
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDsdServiceRequest 0..* The name of this container is used to define the name of the
ManufacturerNotification R-Port through which the DCM accesses the interface Service
RequestNotification. The R-Port is named ServiceRequest
ManufacturerNotification_{Name} where {Name} is the name of
the container DcmDsdServiceRequestManufacturerNotification.
The lowerMultiplicity is 0: If container DcmDsdServiceRequest
ManufacturerNotification does not exist the Indication API is not
available.
DcmDsdServiceRequestSupplier 0..* The name of this container is used to define the name of the
Notification R-Port through which the DCM accesses the interface Service
RequestNotification. The R-Port is named ServiceRequest
SupplierNotification_<SWC> where <SWC> is the name of the
container DcmDsdServiceRequestSupplierNotification.
The lowerMultiplicity is 0: If the container DcmDsdRequest
SupplierNotification does not exist the Indication API is not
available.
DcmDsdServiceTable 1..256 This container contains the configuration (DSD parameters) for a
Service Identifier Table.
Note: It is allowed to add OBD services to a DcmDsdService
Table related to a UDS Protocol. But it is not allowed to add UDS
services to a DcmDsdServiceTable related to an OBD Protocol.

520 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsd:
EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1
DcmDspAuthenticationRow:
EcucParamConfContainerDef
+subContainer
lowerMultiplicity = 0
DcmDsdSidTabId:
DcmDsdServiceTable: upperMultiplicity = 31
EcucIntegerParamDef
EcucParamConfContainerDef +parameter
max = 255 +destination
upperMultiplicity = 256
min = 0
lowerMultiplicity = 1
upperMultiplicity = 1
lowerMultiplicity = 1

DcmDsdServiceRoleRef:
DcmDsdServiceUsed: EcucReferenceDef
EcucBooleanParamDef
lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 32
lowerMultiplicity = 1
defaultValue = true

+parameter +reference

DcmDsdSidTabServiceId: DcmDsdSidTabSubfuncAvail: DcmDsdSidTabFnc:

EcucIntegerParamDef EcucBooleanParamDef EcucFunctionNameDef

max = 255 upperMultiplicity = 1 lowerMultiplicity = 0

min = 0 lowerMultiplicity = 1 upperMultiplicity = 1
upperMultiplicity = 1
lowerMultiplicity = 1 +parameter +parameter

+parameter

+subContainer

DcmDsdService: EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 1

+reference +reference +reference

DcmDsdSidTabSessionLevelRef: DcmDsdSidTabSecurityLevelRef: DcmDsdSidTabModeRuleRef:

EcucReferenceDef EcucReferenceDef EcucReferenceDef

lowerMultiplicity = 0 lowerMultiplicity = 0 lowerMultiplicity = 0

upperMultiplicity = * upperMultiplicity = * upperMultiplicity = 1

+destination +destination +destination

DcmDspSessionRow: DcmDspSecurityRow: DcmModeRule:

EcucParamConfContainerDef EcucParamConfContainerDef EcucParamConfContainerDef
upperMultiplicity = 31 upperMultiplicity = 31 lowerMultiplicity = 1
lowerMultiplicity = 0 lowerMultiplicity = 0 upperMultiplicity = *

+parameter +parameter

DcmDspSessionLevel: DcmDspSecurityLevel:
EcucIntegerParamDef EcucIntegerParamDef

max = 126 max = 63

min = 1 min = 1
lowerMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1
symbolicNameValue = true symbolicNameValue = true

Figure 10.5: DcmDsd configuration overview

521 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Dcm: EcucModuleDef DcmDsd: DcmDsdServiceRequestManufacturerNotification:

EcucParamConfContainerDef +subContainer EcucParamConfContainerDef
upperMultiplicity = 1
lowerMultiplicity = 0 lowerMultiplicity = 1 requiresIndex = true
upperMultiplicity = 1 upperMultiplicity = *
lowerMultiplicity = 0

+container DcmDsdServiceRequestSupplierNotification:
+subContainer EcucParamConfContainerDef
DcmConfigSet: EcucParamConfContainerDef +subContainer
requiresIndex = true
upperMultiplicity = *
lowerMultiplicity = 0

Figure 10.6: DcmDsdIndication configuration overview

10.2.3.2 DcmDsdService

[ECUC_Dcm_00689] Definition of EcucParamConfContainerDef DcmDsdService

d
Container Name DcmDsdService
Parent Container DcmDsdServiceTable
Description This container contains the configuration (DSD parameters) for a Service.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDsdServiceUsed 1 [ECUC_Dcm_01044]
DcmDsdSidTabFnc 0..1 [ECUC_Dcm_00777]
DcmDsdSidTabServiceId 1 [ECUC_Dcm_00735]
DcmDsdSidTabSubfuncAvail 1 [ECUC_Dcm_00737]
DcmDsdServiceRoleRef 0..32 [ECUC_Dcm_01139]
DcmDsdSidTabModeRuleRef 0..1 [ECUC_Dcm_00918]
DcmDsdSidTabSecurityLevelRef 0..* [ECUC_Dcm_00733]
DcmDsdSidTabSessionLevelRef 0..* [ECUC_Dcm_00734]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDsdSubService 0..* This container contains the configuration (DSD parameters) for a
subservice of a service. Only those services may have
subservices, which have the DcmDsdSidTabSubfuncAvail
configured as TRUE.

522 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01044] Definition of EcucBooleanParamDef DcmDsdServiceUsed d

Parameter Name DcmDsdServiceUsed
Parent Container DcmDsdService
Description Allows to activate or deactivate the usage of a Service. This parameter can be used for
multi-purpose ECUs.
true - service is available
false - service is not available
Multiplicity 1
Type EcucBooleanParamDef
Default value true
Post-Build Variant Value true
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

[ECUC_Dcm_00777] Definition of EcucFunctionNameDef DcmDsdSidTabFnc d

Parameter Name DcmDsdSidTabFnc
Parent Container DcmDsdService
Description Callback function of the ECU Supplier specific component for the particular service.
The function’s prototype is as described for <Module>_<DiagnosticService>. If this
parameter is not configured, the service is handled Dcm-internally.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

523 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00735] Definition of EcucIntegerParamDef DcmDsdSidTabService

Id d
Parameter Name DcmDsdSidTabServiceId
Parent Container DcmDsdService
Description Identifier of the service.
The possible service identifiers are defined in ISO 14229-1 and ISO 15031-5.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00737] Definition of EcucBooleanParamDef DcmDsdSidTabSub-

funcAvail d
Parameter Name DcmDsdSidTabSubfuncAvail
Parent Container DcmDsdService
Description Information about whether the service has subfunctions or not. This parameter is used
for the handling of the "suppressPosRspMsgIndicationBit" as defined in ISO 14229-1,
which can be used as a reference for the configuration.
true - service has subfunctions, suppressPosRspMsgIndicationBit is available
false - service has no subfunctions, suppressPosRspMsgIndicationBit is not available
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01139] Definition of EcucReferenceDef DcmDsdServiceRoleRef d

Parameter Name DcmDsdServiceRoleRef
Parent Container DcmDsdService
Description Reference to DcmDspAuthenticationRow that defines a role in that the service is
allowed to be executed.
Multiplicity 0..32
5

524 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type Reference to DcmDspAuthenticationRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00918] Definition of EcucReferenceDef DcmDsdSidTabModeRule

Ref d
Parameter Name DcmDsdSidTabModeRuleRef
Parent Container DcmDsdService
Description Reference to a DcmDspModeRule which controls the execution of the service. If there
is no reference configured, no mode rule check shall be performed.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00733] Definition of EcucReferenceDef DcmDsdSidTabSecurity

LevelRef d
Parameter Name DcmDsdSidTabSecurityLevelRef
Parent Container DcmDsdService
Description Reference to a Security Level in which the service is allowed to be executed. Multiple
references are allowed for a service.
Please refer to ISO 14229-1, ISO 15031-5 and chapter "Verification of the Service
Security Access levels."
If there is no reference configured, no service security verification shall be performed.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
5

525 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00734] Definition of EcucReferenceDef DcmDsdSidTabSession

LevelRef d
Parameter Name DcmDsdSidTabSessionLevelRef
Parent Container DcmDsdService
Description Reference to a Session Level in which the service is allowed to be executed. Multiple
references are allowed for a service.
Please refer to ISO 14229-1, ISO 15031-5 and chapter "Verification of the Diagnostic
Session".
If there is no reference configured, no diagnostic session verification shall be
performed.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

10.2.3.3 DcmDsdServiceRequestManufacturerNotification

[ECUC_Dcm_00681] Definition of EcucParamConfContainerDef DcmDsdService

RequestManufacturerNotification d

526 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDsdServiceRequestManufacturerNotification

Parent Container DcmDsd
Description The name of this container is used to define the name of the R-Port through which the
DCM accesses the interface ServiceRequestNotification. The R-Port is named Service
RequestManufacturerNotification_{Name} where {Name} is the name of the container
DcmDsdServiceRequestManufacturerNotification.
The lowerMultiplicity is 0: If container DcmDsdServiceRequestManufacturerNotification
does not exist the Indication API is not available.
Attributes: requiresIndex=true
Configuration Parameters

No Included Parameters

No Included Containers

10.2.3.4 DcmDsdServiceRequestSupplierNotification

[ECUC_Dcm_00816] Definition of EcucParamConfContainerDef DcmDsdService

RequestSupplierNotification d
Container Name DcmDsdServiceRequestSupplierNotification
Parent Container DcmDsd
Description The name of this container is used to define the name of the R-Port through which the
DCM accesses the interface ServiceRequestNotification. The R-Port is named Service
RequestSupplierNotification_<SWC> where <SWC> is the name of the container Dcm
DsdServiceRequestSupplierNotification.
The lowerMultiplicity is 0: If the container DcmDsdRequestSupplierNotification does
not exist the Indication API is not available.
Attributes: requiresIndex=true
Configuration Parameters

No Included Parameters

No Included Containers

10.2.3.5 DcmDsdServiceTable

[ECUC_Dcm_00732] Definition of EcucParamConfContainerDef DcmDsdService

Table d

527 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDsdServiceTable

Parent Container DcmDsd
Description This container contains the configuration (DSD parameters) for a Service Identifier
Table.
Note: It is allowed to add OBD services to a DcmDsdServiceTable related to a UDS
Protocol. But it is not allowed to add UDS services to a DcmDsdServiceTable related to
an OBD Protocol.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDsdSidTabId 1 [ECUC_Dcm_00736]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDsdService 1..* This container contains the configuration (DSD parameters) for a
Service.

[ECUC_Dcm_00736] Definition of EcucIntegerParamDef DcmDsdSidTabId d

Parameter Name DcmDsdSidTabId
Parent Container DcmDsdServiceTable
Description Due to using possibly more service tables, the unique DcmDsdSidTabId can be used to
identify them.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

Note : The Dcm internal interaction with the DSP is implementation specific and there-
fore not explicitly configured.

10.2.3.6 DcmDsdSubService

[ECUC_Dcm_00802] Definition of EcucParamConfContainerDef DcmDsdSubSer-

vice d

528 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDsdSubService

Parent Container DcmDsdService
Description This container contains the configuration (DSD parameters) for a subservice of a
service. Only those services may have subservices, which have the DcmDsdSidTab
SubfuncAvail configured as TRUE.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDsdSubServiceFnc 0..1 [ECUC_Dcm_00942]
DcmDsdSubServiceId 1 [ECUC_Dcm_00803]
DcmDsdSubServiceUsed 1 [ECUC_Dcm_01047]
DcmDsdSubServiceModeRuleRef 0..1 [ECUC_Dcm_00924]
DcmDsdSubServiceRoleRef 0..32 [ECUC_Dcm_01140]
DcmDsdSubServiceSecurityLevelRef 0..* [ECUC_Dcm_00812]
DcmDsdSubServiceSessionLevelRef 0..* [ECUC_Dcm_00804]

No Included Containers

[ECUC_Dcm_00942] Definition of EcucFunctionNameDef DcmDsdSubService

Fnc d
Parameter Name DcmDsdSubServiceFnc
Parent Container DcmDsdSubService
Description Callback function of the ECU Supplier specific component for the particular service.
The function’s prototype is as described for <Module>_<DiagnosticService>_<Sub
Service>.
If this parameter is not configured, the subservice is handled Dcm-internally.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

529 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00803] Definition of EcucIntegerParamDef DcmDsdSubServiceId d

Parameter Name DcmDsdSubServiceId
Parent Container DcmDsdSubService
Description Identifier of the subservice.
The possible subservice identifiers are defined in ISO 14229-1 and ISO 15031-5.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 127
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01047] Definition of EcucBooleanParamDef DcmDsdSubService

Used d
Parameter Name DcmDsdSubServiceUsed
Parent Container DcmDsdSubService
Description Allows to activate or deactivate the usage of a Subservice. This parameter can be used
for multi-purpose ECUs.
true - subservice is available false - subservice is not available.
Multiplicity 1
Type EcucBooleanParamDef
Default value true
Post-Build Variant Value true
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

[ECUC_Dcm_00924] Definition of EcucReferenceDef DcmDsdSubServiceMode

RuleRef d
Parameter Name DcmDsdSubServiceModeRuleRef
Parent Container DcmDsdSubService
Description Reference to a DcmDspModeRule which controls the execution of the subservice.
If there is no reference configured, no mode rule check shall be performed.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
5

530 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01140] Definition of EcucReferenceDef DcmDsdSubServiceRole

Ref d
Parameter Name DcmDsdSubServiceRoleRef
Parent Container DcmDsdSubService
Description Reference to DcmDspAuthenticationRow that defines a role in that the service with this
subfunction is allowed to be executed.
Multiplicity 0..32
Type Reference to DcmDspAuthenticationRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00812] Definition of EcucReferenceDef DcmDsdSubServiceSecu-

rityLevelRef d
Parameter Name DcmDsdSubServiceSecurityLevelRef
Parent Container DcmDsdSubService
Description Reference to a Security Level in which the subservice is allowed to be executed.
Multiple references are allowed for a subservice.
Please refer to ISO 14229-1, ISO 15031-5 and chapter "Verification of the Service
Security Access levels."
If there is no reference configured, no subservice security verification shall be
performed.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
5

531 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00804] Definition of EcucReferenceDef DcmDsdSubServiceSes-

sionLevelRef d
Parameter Name DcmDsdSubServiceSessionLevelRef
Parent Container DcmDsdSubService
Description Reference to a Session Level in which the subservice is allowed to be executed.
Multiple references are allowed for a subservice.
Please refer to ISO 14229-1, ISO 15031-5 and chapter "Verification of the Diagnostic
Session".
If there is no reference configured, no diagnostic session verification shall be
performed.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

532 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsdServiceTable:
EcucParamConfContainerDef

upperMultiplicity = 256
lowerMultiplicity = 1

DcmDsdSubServiceRoleRef: DcmDspAuthenticationRow:
EcucReferenceDef +destination EcucParamConfContainerDef
+subContainer
lowerMultiplicity = 0 lowerMultiplicity = 0
DcmDsdService: upperMultiplicity = 32 upperMultiplicity = 31
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 1
+reference

DcmDsdSubServiceId: DcmDsdSubServiceFnc: DcmDsdSubServiceUsed:

EcucIntegerParamDef EcucFunctionNameDef EcucBooleanParamDef

min = 0 lowerMultiplicity = 0 upperMultiplicity = 1

max = 127 upperMultiplicity = 1 lowerMultiplicity = 1
lowerMultiplicity = 1 defaultValue = true
upperMultiplicity = 1

+parameter +parameter +parameter

+subContainer

DcmDsdSubService: EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

+reference +reference +reference

DcmDsdSubServiceSessionLevelRef: DcmDsdSubServiceSecurityLevelRef: DcmDsdSubServiceModeRuleRef:

EcucReferenceDef EcucReferenceDef EcucReferenceDef

lowerMultiplicity = 0 lowerMultiplicity = 0 lowerMultiplicity = 0

upperMultiplicity = * upperMultiplicity = * upperMultiplicity = 1

+destination +destination +destination

DcmDspSessionRow: DcmDspSecurityRow: DcmModeRule:

EcucParamConfContainerDef EcucParamConfContainerDef EcucParamConfContainerDef

upperMultiplicity = 31 upperMultiplicity = 31 lowerMultiplicity = 1

lowerMultiplicity = 0 lowerMultiplicity = 0 upperMultiplicity = *

+parameter +parameter

DcmDspSessionLevel: DcmDspSecurityLevel:
EcucIntegerParamDef EcucIntegerParamDef

max = 126 max = 63

min = 1 min = 1
lowerMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1
symbolicNameValue = true symbolicNameValue = true

Figure 10.7: DcmDsdSubService configuration overview

10.2.4 DcmDsl

10.2.4.1 DcmDsl

[ECUC_Dcm_00690] Definition of EcucParamConfContainerDef DcmDsl d

Container Name DcmDsl
Parent Container DcmConfigSet
Description These parameters configure the Diagnostic Session Layer submodule.
Configuration Parameters

No Included Parameters

533 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDslBuffer 1..256 This container contains the configuration of a diagnostic buffer.
DcmDslDiagResp 1 This container contains the configuration of the automatic
requestCorrectlyReceivedResponsePending response
management in the Dcm.
DcmDslProtocol 1 This container contains the configurations of the diagnostic
protocols used in Dcm.

Dcm: EcucModuleDef DcmDsl:

upperMultiplicity = 1 EcucParamConfContainerDef
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1

DcmDslProtocol: DcmDslBuffer:
EcucParamConfContainerDef EcucParamConfContainerDef
+subContainer +subContainer
upperMultiplicity = 1 upperMultiplicity = 256
lowerMultiplicity = 1 lowerMultiplicity = 1

DcmDslDiagResp:
EcucParamConfContainerDef
+subContainer
upperMultiplicity = 1
lowerMultiplicity = 1

Figure 10.8: DcmDsl configuration overview

10.2.4.2 DcmDslBuffer

[ECUC_Dcm_00739] Definition of EcucParamConfContainerDef DcmDslBuffer d

Container Name DcmDslBuffer
Parent Container DcmDsl
Description This container contains the configuration of a diagnostic buffer.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDslBufferSize 1 [ECUC_Dcm_00738]

No Included Containers

534 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00738] Definition of EcucIntegerParamDef DcmDslBufferSize d

Parameter Name DcmDslBufferSize
Parent Container DcmDslBuffer
Description Size of the diagnostic buffer in bytes.
For a linear buffer the size shall be as large as the longest diagnostic message (request
or response).
For a paged buffer the size has impacts on the application performance.
Multiplicity 1
Type EcucIntegerParamDef
Range 8 .. 4294967294
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

Dcm: EcucModuleDef

upperMultiplicity = 1
lowerMultiplicity = 0

DcmDsl: DcmDslBuffer: DcmDslBufferSize:

EcucParamConfContainerDef EcucParamConfContainerDef EcucIntegerParamDef
+subContainer +parameter
lowerMultiplicity = 1 upperMultiplicity = 256 max = 4294967294
upperMultiplicity = 1 lowerMultiplicity = 1 min = 8
lowerMultiplicity = 1
upperMultiplicity = 1

Figure 10.9: DcmDslBuffer configuration overview

10.2.4.3 DcmDslDiagResp

[ECUC_Dcm_00691] Definition of EcucParamConfContainerDef DcmDslDiag

Resp d
Container Name DcmDslDiagResp
Parent Container DcmDsl
Description This container contains the configuration of the automatic requestCorrectlyReceived
ResponsePending response management in the Dcm.
Configuration Parameters

535 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDslDiagRespMaxNumRespPend 0..1 [ECUC_Dcm_00693]
DcmDslDiagRespOnSecondDeclinedRequest 1 [ECUC_Dcm_00914]

No Included Containers

[ECUC_Dcm_00693] Definition of EcucIntegerParamDef DcmDslDiagRespMax

NumRespPend d
Parameter Name DcmDslDiagRespMaxNumRespPend
Parent Container DcmDslDiagResp
Description Maximum number of negative responses with response code 0x78 (requestCorrectly
ReceivedResponsePending) allowed for a request. If Dcm reaches this limit, an
automatic 0x10 (generalReject) final response will be trasmitted and the service
processing will be cancelled. Value 0x00 means that no NRC 0x78 response will be
transmitted.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00914] Definition of EcucBooleanParamDef DcmDslDiagRespOn

SecondDeclinedRequest d
Parameter Name DcmDslDiagRespOnSecondDeclinedRequest
Parent Container DcmDslDiagResp
Description Defines the reaction upon a second request (ClientB) that can not be processed (e.g.
due to priority assessment).
TRUE: when the second request (Client B) can not be processed, it shall be answered
with NRC21 BusyRepeatRequest.
FALSE: when the second request (Client B) can not be processed, it shall not be
responded.
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
5

536 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

10.2.4.4 DcmDslProtocol

[ECUC_Dcm_00694] Definition of EcucParamConfContainerDef DcmDslProtocol

d
Container Name DcmDslProtocol
Parent Container DcmDsl
Description This container contains the configurations of the diagnostic protocols used in Dcm.
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDslProtocolRow 1..* This container contains the configuration of one particular
diagnostic protocol used in Dcm.

537 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Dcm: EcucModuleDef DcmDslProtocol:

EcucParamConfContainerDef
upperMultiplicity = 1
DcmDsl:
lowerMultiplicity = 0 +subContainer upperMultiplicity = 1
EcucParamConfContainerDef
lowerMultiplicity = 1
lowerMultiplicity = 1
upperMultiplicity = 1 DcmDslConnection:
+container
+subContainer EcucChoiceContainerDef
DcmConfigSet: lowerMultiplicity = 1
EcucParamConfContainerDef upperMultiplicity = *

+subContainer
DcmTimStrP2StarServerAdjust: DcmDspProtocolEcuAddr: DcmDslProtocolMaximumResponseSize:
EcucFloatParamDef EcucIntegerParamDef EcucIntegerParamDef

min = 0 min = 0 max = 65535

lowerMultiplicity = 1 max = 65535 min = 1
upperMultiplicity = 1 lowerMultiplicity = 0 lowerMultiplicity = 0
max = 5 upperMultiplicity = 1 upperMultiplicity = 1
defaultValue = 4095 DcmDslProtocolPriority:
+parameter +parameter +parameter EcucIntegerParamDef

DcmTimStrP2ServerAdjust: max = 255

DcmDslProtocolType: DcmDslProtocolRowUsed: EcucFloatParamDef min = 0
EcucEnumerationParamDef EcucBooleanParamDef lowerMultiplicity = 1
min = 0 upperMultiplicity = 1
lowerMultiplicity = 1 upperMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 lowerMultiplicity = 1 upperMultiplicity = 1
symbolicNameValue = true defaultValue = true +parameter
max = 1

+parameter +parameter +subContainer

+parameter

DcmDslProtocolRow: EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 1

+parameter

DcmDslProtocolTransType: +reference +reference

EcucEnumerationParamDef
DcmDslProtocolSIDTable: DcmDslProtocolRxBufferRef:
lowerMultiplicity = 0
EcucReferenceDef EcucReferenceDef
upperMultiplicity = 1
lowerMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1
+literal +literal

TYPE1: TYPE2: +destination

EcucEnumerationLiteralDef EcucEnumerationLiteralDef
+subContainer DcmDslBuffer:
EcucParamConfContainerDef

+reference upperMultiplicity = 256

+parameter lowerMultiplicity = 1
DcmDemClientRef:
DcmSendRespPendOnRestart: EcucReferenceDef +destination +reference
EcucBooleanParamDef
lowerMultiplicity = 1
upperMultiplicity = 1 DcmDslProtocolTxBufferRef:
upperMultiplicity = 1
lowerMultiplicity = 1 EcucReferenceDef
defaultValue = true lowerMultiplicity = 1
upperMultiplicity = 1
+destination +destination

DemClient:
EcucParamConfContainerDef DcmDsdServiceTable:
EcucParamConfContainerDef
lowerMultiplicity = 1
upperMultiplicity = 255 upperMultiplicity = 256
lowerMultiplicity = 1

+parameter

DcmDsdSidTabId:
EcucIntegerParamDef

max = 255
min = 0
upperMultiplicity = 1
lowerMultiplicity = 1

Figure 10.10: DcmDslProtocol configuration overview

538 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.4.5 DcmDslProtocolRow

[ECUC_Dcm_00695] Definition of EcucParamConfContainerDef DcmDslProtocol

Row d
Container Name DcmDslProtocolRow
Parent Container DcmDslProtocol
Description This container contains the configuration of one particular diagnostic protocol used in
Dcm.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDslProtocolMaximumResponseSize 0..1 [ECUC_Dcm_01020]
DcmDslProtocolPriority 1 [ECUC_Dcm_00699]
DcmDslProtocolRowUsed 1 [ECUC_Dcm_01043]
DcmDslProtocolTransType 0..1 [ECUC_Dcm_00700]
DcmDslProtocolType 1 [ECUC_Dcm_01110]
DcmDspProtocolEcuAddr 0..1 [ECUC_Dcm_01081]
DcmSendRespPendOnRestart 1 [ECUC_Dcm_01114]
DcmTimStrP2ServerAdjust 1 [ECUC_Dcm_00729]
DcmTimStrP2StarServerAdjust 1 [ECUC_Dcm_00728]
DcmDemClientRef 1 [ECUC_Dcm_01083]
DcmDslProtocolRxBufferRef 1 [ECUC_Dcm_00701]
DcmDslProtocolSIDTable 1 [ECUC_Dcm_00702]
DcmDslProtocolTxBufferRef 1 [ECUC_Dcm_00704]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDslConnection 1..* This container contains the configuration of a communication
channel for one particular protocol.
Note that it is allowed to communicate with multiple testers,
therefore multiple connections may be configured for a protocol.

[ECUC_Dcm_01020] Definition of EcucIntegerParamDef DcmDslProtocolMaxi-

mumResponseSize d
Parameter Name DcmDslProtocolMaximumResponseSize
Parent Container DcmDslProtocolRow
Description This parameter is mandatory and defines the maximum length of the response
message in case DcmPagedBufferEnabled == TRUE
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 65535
5

539 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Default value 4095
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00699] Definition of EcucIntegerParamDef DcmDslProtocolPriority

d
Parameter Name DcmDslProtocolPriority
Parent Container DcmDslProtocolRow
Description Protocol priority used during protocol preemption. A higher priority protocol may
preempt a lower priority protocol. Lower numeric values represent higher protocol
priority:
0 - Highest protocol priority
255 - Lowest protocol priority
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01043] Definition of EcucBooleanParamDef DcmDslProtocolRow

Used d
Parameter Name DcmDslProtocolRowUsed
Parent Container DcmDslProtocolRow
Description Allows to activate or deactivate the usage of a Protocol. This parameter can be used
for multi-purpose ECUs.
true - protocol is available
false - protocol is not available.
Multiplicity 1
Type EcucBooleanParamDef
5

540 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Default value true
Post-Build Variant Value true
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

[ECUC_Dcm_00700] Definition of EcucEnumerationParamDef DcmDslProtocol

TransType d
Parameter Name DcmDslProtocolTransType
Parent Container DcmDslProtocolRow
Description This parameter is used only if the protocol is of type DCM_ROE_ON_xxx. It selects the
transmission type of the protocol.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range TYPE1 Messages on the DcmTxPduId already used for
normal diagnostic responses. The outgoing
messages must be synchronized with ’normal
outgoing messages’, which have a higher priority.
TYPE2 Messages on a separate DcmTxPduId.
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01110] Definition of EcucEnumerationParamDef DcmDslProtocol

Type d
Parameter Name DcmDslProtocolType
Parent Container DcmDslProtocolRow
Description The diagnostic protocol type for the DCM DSL protocol that is being configured.
Implementation Type: Dcm_ProtocolType
Multiplicity 1
Type EcucEnumerationParamDef (Symbolic Name generated for this parameter)
Range DCM_OBD_ON_CAN OBD on CAN (ISO15765-4; ISO15031-5)
DCM_OBD_ON_FLEXRAY –
DCM_OBD_ON_IP –
DCM_PERIODICTRANS_ON_ –
CAN
5

541 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
DCM_PERIODICTRANS_ON_ –
FLEXRAY
DCM_PERIODICTRANS_ON_IP –
DCM_ROE_ON_CAN –
DCM_ROE_ON_FLEXRAY –
DCM_ROE_ON_IP –
DCM_SUPPLIER_1 Reserved for SW supplier specific
DCM_SUPPLIER_10 Reserved for SW supplier specific
DCM_SUPPLIER_11 Reserved for SW supplier specific
DCM_SUPPLIER_12 Reserved for SW supplier specific
DCM_SUPPLIER_13 Reserved for SW supplier specific
DCM_SUPPLIER_14 Reserved for SW supplier specific
DCM_SUPPLIER_15 Reserved for SW supplier specific
DCM_SUPPLIER_2 Reserved for SW supplier specific
DCM_SUPPLIER_3 Reserved for SW supplier specific
DCM_SUPPLIER_4 Reserved for SW supplier specific
DCM_SUPPLIER_5 Reserved for SW supplier specific
DCM_SUPPLIER_6 Reserved for SW supplier specific
DCM_SUPPLIER_7 Reserved for SW supplier specific
DCM_SUPPLIER_8 Reserved for SW supplier specific
DCM_SUPPLIER_9 Reserved for SW supplier specific
DCM_UDS_ON_CAN UDS on CAN (ISO15765-3; ISO14229-1)
DCM_UDS_ON_FLEXRAY UDS on FlexRay (Manufacturer specific;
ISO14229-1)
DCM_UDS_ON_IP –
DCM_UDS_ON_LIN –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01081] Definition of EcucIntegerParamDef DcmDspProtocolEcu

Addr d
Parameter Name DcmDspProtocolEcuAddr
Parent Container DcmDslProtocolRow
Description Ecu source address used for diagnostic communication. This parameter is required for
Generic Connections.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Value false
5

542 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01114] Definition of EcucBooleanParamDef DcmSendRespPendOn

Restart d
Parameter Name DcmSendRespPendOnRestart
Parent Container DcmDslProtocolRow
Description If set to TRUE, the Dcm will send a NRC 0x78 before a transition to bootloader or
performing an ECU reset. If set to False, no 0x78 is send in this case.
Multiplicity 1
Type EcucBooleanParamDef
Default value true
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00729] Definition of EcucFloatParamDef DcmTimStrP2ServerAd-

just d
Parameter Name DcmTimStrP2ServerAdjust
Parent Container DcmDslProtocolRow
Description This parameter is used to guarantee that the diagnostic response is available on the
bus before reaching P2 by adjusting the current DcmDspSessionP2ServerMax.
This parameter mainly represents the software architecture dependent communication
delay between the time the transmission is initiated by DCM and the time when the
message is actually transmitted to the bus.
The parameter value is defined in seconds and must be a multiple of DcmTaskTime.
Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 1]
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

543 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00728] Definition of EcucFloatParamDef DcmTimStrP2StarServer

Adjust d
Parameter Name DcmTimStrP2StarServerAdjust
Parent Container DcmDslProtocolRow
Description This parameter is used to guarantee that the diagnostic response is available on the
bus before reaching P2Star by adjusting the current DcmDspSessionP2StarServerMax.
This parameter mainly represents the software architecture dependent communication
delay between the time the transmission is initiated by DCM and the time when the
message is actually transmitted to the bus.
The parameter value is defined in seconds and must be a multiple of DcmTaskTime.
Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 5]
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01083] Definition of EcucReferenceDef DcmDemClientRef d

Parameter Name DcmDemClientRef
Parent Container DcmDslProtocolRow
Description Reference to DemClient in Dem configuration. Used by the Dem to distinguish different
client calls.
Multiplicity 1
Type Reference to DemClient
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

544 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00701] Definition of EcucReferenceDef DcmDslProtocolRxBuffer

Ref d
Parameter Name DcmDslProtocolRxBufferRef
Parent Container DcmDslProtocolRow
Description Reference to a configured diagnostic buffer that is used for diagnostic request
reception for the protocol.
Multiplicity 1
Type Reference to DcmDslBuffer
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00702] Definition of EcucReferenceDef DcmDslProtocolSIDTable d

Parameter Name DcmDslProtocolSIDTable
Parent Container DcmDslProtocolRow
Description Reference to a service table that is used for diagnostic request processing for this
protocol.
Multiplicity 1
Type Reference to DcmDsdServiceTable
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00704] Definition of EcucReferenceDef DcmDslProtocolTxBuffer

Ref d
Parameter Name DcmDslProtocolTxBufferRef
Parent Container DcmDslProtocolRow
Description Reference to a configured diagnostic buffer that is used for diagnostic response
transmission for the protocol.
Multiplicity 1
Type Reference to DcmDslBuffer
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
5

545 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Scope / Dependency scope: ECU

DcmDslProtocolType:
+literal DCM_OBD_ON_CAN:
EcucEnumerationParamDef
EcucEnumerationLiteralDef
lowerMultiplicity = 1
upperMultiplicity = 1
+literal DCM_UDS_ON_CAN:
symbolicNameValue = true
EcucEnumerationLiteralDef

+literal DCM_UDS_ON_FLEXRAY:
EcucEnumerationLiteralDef

+literal DCM_ROE_ON_CAN:
EcucEnumerationLiteralDef

+literal DCM_ROE_ON_FLEXRAY:
EcucEnumerationLiteralDef

+literal DCM_PERIODICTRANS_ON_CAN:
EcucEnumerationLiteralDef

+literal DCM_PERIODICTRANS_ON_FLEXRAY:
EcucEnumerationLiteralDef

+literal DCM_OBD_ON_FLEXRAY:
EcucEnumerationLiteralDef

+literal DCM_ROE_ON_IP:
EcucEnumerationLiteralDef

+literal DCM_OBD_ON_IP:
EcucEnumerationLiteralDef

+literal DCM_PERIODICTRANS_ON_IP:
EcucEnumerationLiteralDef

+literal DCM_UDS_ON_IP:
EcucEnumerationLiteralDef

+literal DCM_UDS_ON_LIN:
EcucEnumerationLiteralDef

DCM_SUPPLIER_1:
+literal EcucEnumerationLiteralDef
DCM_SUPPLIER_2:
+literal EcucEnumerationLiteralDef
DCM_SUPPLIER_3:
+literal EcucEnumerationLiteralDef

DCM_SUPPLIER_4:
+literal EcucEnumerationLiteralDef
DCM_SUPPLIER_5:
+literal EcucEnumerationLiteralDef DCM_SUPPLIER_6:
+literal EcucEnumerationLiteralDef

DCM_SUPPLIER_7:
+literal EcucEnumerationLiteralDef
DCM_SUPPLIER_8:
+literal EcucEnumerationLiteralDef DCM_SUPPLIER_9:
+literal EcucEnumerationLiteralDef

DCM_SUPPLIER_10:
+literal EcucEnumerationLiteralDef
DCM_SUPPLIER_11:
+literal EcucEnumerationLiteralDef DCM_SUPPLIER_12:
+literal EcucEnumerationLiteralDef

DCM_SUPPLIER_13:
+literal EcucEnumerationLiteralDef
DCM_SUPPLIER_14:
+literal EcucEnumerationLiteralDef DCM_SUPPLIER_15:
EcucEnumerationLiteralDef
+literal

Figure 10.11: DcmDslProtocolType configuration overview

546 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.4.6 DcmDslConnection

[ECUC_Dcm_00705] Definition of EcucChoiceContainerDef DcmDslConnection

d
Choice Container Name DcmDslConnection
Parent Container DcmDslProtocolRow
Description This container contains the configuration of a communication channel for one particular
protocol.
Note that it is allowed to communicate with multiple testers, therefore multiple
connections may be configured for a protocol.

No Included Parameters

Container Choices
Container Name Multiplicity Scope / Dependency
DcmDslMainConnection 0..1 This container contains the configuration for a main connection
of a diagnostic protocol. Additionally it may contain references to
ROE and Periodic connections if the protocol type or protocol
transmission type needs them.
DcmDslPeriodicTransmission 0..1 This container contains the configuration of a periodic
transmission connection.

Dcm: EcucModuleDef

upperMultiplicity = 1
lowerMultiplicity = 0

DcmDsl:
EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

+subContainer

DcmDslProtocol:
EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 1

+subContainer

DcmDslProtocolRow:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 1

+subContainer

DcmDslConnection: EcucChoiceContainerDef

lowerMultiplicity = 1
upperMultiplicity = *

+choice +choice

DcmDslMainConnection: DcmDslPeriodicTransmission:
EcucParamConfContainerDef EcucParamConfContainerDef

upperMultiplicity = 1 lowerMultiplicity = 0
lowerMultiplicity = 0 upperMultiplicity = 1

Figure 10.12: DcmDslConnectionTable configuration overview

547 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.4.7 DcmDslMainConnection

[ECUC_Dcm_00706] Definition of EcucParamConfContainerDef DcmDslMain

Connection d
Container Name DcmDslMainConnection
Parent Container DcmDslConnection
Description This container contains the configuration for a main connection of a diagnostic protocol.
Additionally it may contain references to ROE and Periodic connections if the protocol
type or protocol transmission type needs them.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDslProtocolRxConnectionId 1 [ECUC_Dcm_00826]
DcmDslProtocolRxTesterSourceAddr 0..1 [ECUC_Dcm_01115]
DcmDslPeriodicTransmissionConRef 0..1 [ECUC_Dcm_00707]
DcmDslProtocolComMChannelRef 1 [ECUC_Dcm_00952]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDslProtocolRx 1..* This container contains the configuration parameters of a
reception channel in a diagnostic connection.
The PDU referenced by this reception channel can consume
meta data items of type SOURCE_ADDRESS_16 and
TARGET_ADDRESS_16.
DcmDslProtocolTx 0..1 This container contains the configuration parameters of a
transmission channel in a diagnostic connection.
The PDU referenced by this transmission channel can produce
meta data items of type TARGET_ADDRESS_16 and
SOURCE_ADDRESS_16.

[ECUC_Dcm_00826] Definition of EcucIntegerParamDef DcmDslProtocolRxCon-

nectionId d
Parameter Name DcmDslProtocolRxConnectionId
Parent Container DcmDslMainConnection
Description Unique identifier of the tester which uses this connection for diagnostic communication.
Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 65535
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
5

548 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01115] Definition of EcucIntegerParamDef DcmDslProtocolRx

TesterSourceAddr d
Parameter Name DcmDslProtocolRxTesterSourceAddr
Parent Container DcmDslMainConnection
Description Tester source address uniquely describes a client and will be used e.g within the jump
to Bootloader interfaces. This parameter is not required for generic connections (Dcm
Pdus with MetaDataLength >= 1).
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00707] Definition of EcucReferenceDef DcmDslPeriodicTransmis-

sionConRef d
Parameter Name DcmDslPeriodicTransmissionConRef
Parent Container DcmDslMainConnection
Description Reference to a periodic transmission connection which is used for the processing of
periodic transmission events.
Multiplicity 0..1
Type Reference to DcmDslPeriodicTransmission
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
5

549 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00952] Definition of EcucReferenceDef DcmDslProtocolCom

MChannelRef d
Parameter Name DcmDslProtocolComMChannelRef
Parent Container DcmDslMainConnection
Description Reference to the ComMChannel on which the DcmDslProtocolRxPdu is received and
the DcmDslProtocolTxPdu is transmitted.
Multiplicity 1
Type Symbolic name reference to ComMChannel
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

550 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDslConnection:
EcucChoiceContainerDef

lowerMultiplicity = 1
upperMultiplicity = *

+choice

DcmDslMainConnection: EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 0

+subContainer +parameter +parameter

DcmDslProtocolTx: DcmDslProtocolRxConnectionId: DcmDslProtocolRxTesterSourceAddr:

EcucParamConfContainerDef EcucIntegerParamDef EcucIntegerParamDef

upperMultiplicity = 1 min = 0 min = 0

lowerMultiplicity = 0 max = 65535 max = 65535
lowerMultiplicity = 1 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 1
symbolicNameValue = true
+parameter

+reference
DcmDslTxConfirmationPduId:
EcucIntegerParamDef
DcmDslPeriodicTransmissionConRef:
min = 0 EcucReferenceDef
max = 65535
lowerMultiplicity = 0
withAuto = true
upperMultiplicity = 1
symbolicNameValue = true

+reference
+destination
DcmDslProtocolTxPduRef:
EcucReferenceDef DcmDslPeriodicTransmission: +choice

lowerMultiplicity = 1 EcucParamConfContainerDef
upperMultiplicity = 1 lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer
+reference
DcmDslProtocolRx: EcucParamConfContainerDef

upperMultiplicity = * DcmDslProtocolComMChannelRef:
lowerMultiplicity = 1 EcucReferenceDef

lowerMultiplicity = 1
upperMultiplicity = 1
+reference requiresSymbolicNameValue = true
+parameter
+parameter
DcmDslProtocolRxPduRef: DcmDslProtocolRxPduId: +destination
EcucReferenceDef EcucIntegerParamDef DcmDslProtocolRxAddrType:
EcucEnumerationParamDef
ComMChannel:
lowerMultiplicity = 1 min = 0
lowerMultiplicity = 1 EcucParamConfContainerDef
upperMultiplicity = 1 max = 65535
lowerMultiplicity = 1 upperMultiplicity = 1
lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 256
withAuto = true
symbolicNameValue = true

+destination
+literal +literal
Pdu: EcucParamConfContainerDef
DCM_PHYSICAL_TYPE: DCM_FUNCTIONAL_TYPE:
+destination lowerMultiplicity = 0
EcucEnumerationLiteralDef EcucEnumerationLiteralDef
upperMultiplicity = *

Figure 10.13: DcmDslMainConnection configuration overview

10.2.4.8 DcmDslProtocolRx

[ECUC_Dcm_00709] Definition of EcucParamConfContainerDef DcmDslProtocol

Rx d

551 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDslProtocolRx

Parent Container DcmDslMainConnection
Description This container contains the configuration parameters of a reception channel in a
diagnostic connection.
The PDU referenced by this reception channel can consume meta data items of type
SOURCE_ADDRESS_16 and TARGET_ADDRESS_16.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDslProtocolRxAddrType 1 [ECUC_Dcm_00710]
DcmDslProtocolRxPduId 1 [ECUC_Dcm_00687]
DcmDslProtocolRxPduRef 1 [ECUC_Dcm_00770]

No Included Containers

[ECUC_Dcm_00710] Definition of EcucEnumerationParamDef DcmDslProtocol

RxAddrType d
Parameter Name DcmDslProtocolRxAddrType
Parent Container DcmDslProtocolRx
Description Selects the addressing type of the reception channel. Physical addressing is used for
1:1 communication, functional addressing is used for 1:N communication.
For details refer to ISO 14229-1.
Multiplicity 1
Type EcucEnumerationParamDef
Range DCM_FUNCTIONAL_TYPE FUNCTIONAL = 1 to n communication
DCM_PHYSICAL_TYPE PHYSICAL = 1 to 1 communications using
physical addressing
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00687] Definition of EcucIntegerParamDef DcmDslProtocolRxPdu

Id d
Parameter Name DcmDslProtocolRxPduId
Parent Container DcmDslProtocolRx
Description Identifier of the PDU that is used for this reception channel.
Multiplicity 1
5

552 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU
withAuto = true

[ECUC_Dcm_00770] Definition of EcucReferenceDef DcmDslProtocolRxPduRef

d
Parameter Name DcmDslProtocolRxPduRef
Parent Container DcmDslProtocolRx
Description Reference to a Pdu in EcuC that is used for this reception channel.
Multiplicity 1
Type Reference to Pdu
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

10.2.4.9 DcmDslProtocolTx

[ECUC_Dcm_00711] Definition of EcucParamConfContainerDef DcmDslProtocol

Tx d
Container Name DcmDslProtocolTx
Parent Container DcmDslMainConnection
Description This container contains the configuration parameters of a transmission channel in a
diagnostic connection.
The PDU referenced by this transmission channel can produce meta data items of type
TARGET_ADDRESS_16 and SOURCE_ADDRESS_16.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDslTxConfirmationPduId 1 [ECUC_Dcm_00864]
DcmDslProtocolTxPduRef 1 [ECUC_Dcm_00772]

553 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

No Included Containers

[ECUC_Dcm_00864] Definition of EcucIntegerParamDef DcmDslTxConfirmation

PduId d
Parameter Name DcmDslTxConfirmationPduId
Parent Container DcmDslProtocolTx
Description Identifier of the PDU that is used by the lower level module for transmission
confirmation of responses on this channel.
Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU
withAuto = true

[ECUC_Dcm_00772] Definition of EcucReferenceDef DcmDslProtocolTxPduRef

d
Parameter Name DcmDslProtocolTxPduRef
Parent Container DcmDslProtocolTx
Description Reference to a Pdu in EcuC that is used for this transmission channel.
Multiplicity 1
Type Reference to Pdu
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

10.2.4.10 DcmDslPeriodicTransmission

[ECUC_Dcm_00741] Definition of EcucParamConfContainerDef DcmDslPeriodic

Transmission d

554 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDslPeriodicTransmission

Parent Container DcmDslConnection
Description This container contains the configuration of a periodic transmission connection.
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDslPeriodicConnection 0..255 This container contains the configuration of a transmission
channel for a periodic transmission connection.
The PDU referenced by this transmission channel can produce
meta data items of type TARGET_ADDRESS_16 and
SOURCE_ADDRESS_16.

DcmDslConnection:
EcucChoiceContainerDef

lowerMultiplicity = 1
upperMultiplicity = *

+choice
DcmDslPeriodicTxConfirmationPduId:
DcmDslPeriodicTransmission: DcmDslPeriodicConnection:
EcucIntegerParamDef
EcucParamConfContainerDef EcucParamConfContainerDef

+parameter min = 0
lowerMultiplicity = 0 requiresIndex = true
max = 65535
upperMultiplicity = 1 lowerMultiplicity = 0
lowerMultiplicity = 1
upperMultiplicity = 255
upperMultiplicity = 1
withAuto = true
symbolicNameValue = true

+subContainer
DcmDslPeriodicTxPduRef:
+reference EcucReferenceDef

lowerMultiplicity = 1
upperMultiplicity = 1

+destination

Pdu: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *

Figure 10.14: DcmDslPeriodicTransmission configuration overview

10.2.4.11 DcmDslPeriodicConnection

[ECUC_Dcm_00897] Definition of EcucParamConfContainerDef DcmDslPeriodic

Connection d

555 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDslPeriodicConnection

Parent Container DcmDslPeriodicTransmission
Description This container contains the configuration of a transmission channel for a periodic
transmission connection.
The PDU referenced by this transmission channel can produce meta data items of type
TARGET_ADDRESS_16 and SOURCE_ADDRESS_16.
Attributes: requiresIndex=true
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDslPeriodicTxConfirmationPduId 1 [ECUC_Dcm_00862]
DcmDslPeriodicTxPduRef 1 [ECUC_Dcm_00742]

No Included Containers

[ECUC_Dcm_00862] Definition of EcucIntegerParamDef DcmDslPeriodicTxCon-

firmationPduId d
Parameter Name DcmDslPeriodicTxConfirmationPduId
Parent Container DcmDslPeriodicConnection
Description Identifier of the PDU that is used by the lower level module for transmission
confirmation of responses on this channel.
Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU
withAuto = true

[ECUC_Dcm_00742] Definition of EcucReferenceDef DcmDslPeriodicTxPduRef d

Parameter Name DcmDslPeriodicTxPduRef
Parent Container DcmDslPeriodicConnection
Description Reference to a Pdu in EcuC that is used for this periodic transmission channel.
Multiplicity 1
Type Reference to Pdu
Post-Build Variant Value false
5

556 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

10.2.5 DcmDsp

[ECUC_Dcm_00712] Definition of EcucParamConfContainerDef DcmDsp d

Container Name DcmDsp
Parent Container DcmConfigSet
Description These parameters apply to Diagnostic Service Processing. There will always be one
set of these parameters per Dcm. Please note: Although the multiplicity is set to 0..1. It
can be expected that this container exists in any valid DCM configuration.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDataDefaultEndianness 1 [ECUC_Dcm_00987]
DcmDspDDDIDcheckPerSourceDID 0..1 [ECUC_Dcm_00966]
DcmDspEnableObdMirror 1 [ECUC_Dcm_01061]
DcmDspMaxDidToRead 0..1 [ECUC_Dcm_00638]
DcmDspMaxPeriodicDidToRead 0..1 [ECUC_Dcm_00956]
DcmDspPowerDownTime 0..1 [ECUC_Dcm_00818]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspAuthentication 0..1 This container contains the configuration for the UDS service
Authentication (0x29).
DcmDspClearDTC 0..1 This container contains the configuration for the Clear DTC
service.
DcmDspComControl 0..1 Provides the configuration of the CommunicationControl
mechanism.
DcmDspCommonAuthorization 0..* This container contains the configuration (parameters) for the
common Authorization being equal for several services /
sub-services.
DcmDspControlDTCSetting 0..1 Provide the configuration of the ControlDTCSetting mechanism.
DcmDspData 0..* This container contains the configuration (parameters) of a Data
belonging to a DID
DcmDspDataInfo 0..* This container contains the configuration (parameters) of one
Data.
DcmDspDid 0..* This container contains the configuration (parameters) of the
DID.
5

557 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspDidInfo 0..* This container contains the configuration (parameters) of the
DID’s Info
DcmDspDidRange 0..* This container defines the DID Range
DcmDspEcuReset 0..1 This container contains the configuration for DcmDspEcuReset
service
DcmDspMemory 0..1 This container contains the configuration of the memory access.
DcmDspMemoryTransfer 0..1 This container contains the configuration of the memory transfer.
DcmDspPeriodicTransmission 0..1 This container contains the configuration (parameters) for
Periodic Transmission Scheduler.
DcmDspPid 0..* This container defines the availability of a PID to the DCM.
DcmDspReadDTCInformation 0..1 Provides further configuration for the UDS service Read
DTCInformation processing.
DcmDspRequestControl 0..* This container contains the configuration (parameters) of the
"Request control of on-board system, test or component" service
(Service $08). The DCM will request the control using an R-Port
requiring a PortInteface RequestControlServices_{Tid}. The
R-Port is named RequestControlServices_{Tid} where {Tid} is
the name of the container DcmDspRequestControl.
DcmDspRequestFileTransfer 0..1 This container contains the configuration for RequestFile
Transfer. This container only exists if RequestFileTransfer is
configured.
DcmDspRoe 0..1 Provide the configuration of the ResponseOnEvent mechanism.
DcmDspRoutine 0..* This container contains the configuration (parameters) for
Routines
DcmDspSecurity 1 This container contains the configuration ( DSP parameter) for
security level configuration (per security level) Description This
container contains Rows of DcmDspSecurityRow
DcmDspSession 1 Parent container holding single rows to configure particular
sessions
DcmDspVehInfo 0..* This container contains the configuration (parameters) for one
single VehicleInfoType of service $09

[ECUC_Dcm_00987] Definition of EcucEnumerationParamDef DcmDspDataDe-

faultEndianness d
Parameter Name DcmDspDataDefaultEndianness
Parent Container DcmDsp
Description Defines the default endianness belonging to a DID, RID or PID if the corresponding
data does not define an endianness.
Multiplicity 1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at the lowest
address.
LITTLE_ENDIAN Most significant byte shall be stored at the
highest address
OPAQUE Opaque data endianness
Post-Build Variant Value false
5

558 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00966] Definition of EcucBooleanParamDef DcmDspDDDIDcheck

PerSourceDID d
Parameter Name DcmDspDDDIDcheckPerSourceDID
Parent Container DcmDsp
Description Defines the check for session, security and mode dependencies per source DIDs with
a ReadDataByIdentifier (0x22).
true: Dcm module shall check the session, security and mode dependencies per source
DIDs with a ReadDataByIdentifier (0x22) with DID in the range 0xF200 to 0xF3FF
false: Dcm module shall not check the session, security and mode dependencies per
source DIDs with a ReadDataByIdentifier (0x22) with DID in the range 0xF200 to 0x
F3FF
Multiplicity 0..1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01061] Definition of EcucBooleanParamDef DcmDspEnableObd

Mirror d
Parameter Name DcmDspEnableObdMirror
Parent Container DcmDsp
Description DcmDspEnableObdMirror defines whether a DID inside the OBD range (F400-F4FF)
and the OBD InfoType range (F800-F8FF) shall get the DID value as defined for OBD
on reception of the UDS Service ReadDataByIdentifier (0x22), or not. It also defines
whether a RID inside the OBD range (E000-E0FF) shall handle the RID as defined for
OBD on reception of the UDS Service RoutineControl (0x31), or not.
Multiplicity 1
Type EcucBooleanParamDef
5

559 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Default value false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00638] Definition of EcucIntegerParamDef DcmDspMaxDidToRead

d
Parameter Name DcmDspMaxDidToRead
Parent Container DcmDsp
Description Indicates the maximum allowed DIDs in a single "ReadDataByIdentifier" request.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 65535
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00956] Definition of EcucIntegerParamDef DcmDspMaxPeriodicDid

ToRead d
Parameter Name DcmDspMaxPeriodicDidToRead
Parent Container DcmDsp
Description Indicates the maximum allowed periodicDIDs which can be read in a single "ReadData
ByPeriodicIdentifier" request.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 65535
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
5

560 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00818] Definition of EcucIntegerParamDef DcmDspPowerDown

Time d
Parameter Name DcmDspPowerDownTime
Parent Container DcmDsp
Description This parameter indicates to the client the minimum time of the stand-by sequence the
server will remain in the power-down sequence.
The resolution of this parameter is one second per count.
The following values are valid: 00 - FE hex: 0 - 254 s powerDownTime; FF hex:
indicates a failure or time not available.
This value needs to be defined by the integrator according to the ECU capabilities. This
parameter has to be available if the service EcuReset, sub-service enableRapidPower
ShutDown is configured.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

561 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp: EcucParamConfContainerDef DcmDspMaxPeriodicDidToRead:

EcucIntegerParamDef
lowerMultiplicity = 0 +parameter
upperMultiplicity = 1 lowerMultiplicity = 0
upperMultiplicity = 1
min = 1
max = 65535

DcmDspPowerDownTime:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1
min = 0
max = 255

DcmDspMaxDidToRead:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1
min = 1
max = 65535

DcmDspRoutine:
+subContainer EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

DcmDspRequestFileTransfer:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDid: EcucParamConfContainerDef
+subContainer
upperMultiplicity = *
lowerMultiplicity = 0

DcmDspDidInfo:
+subContainer EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

DcmDspSession:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspSecurity:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 1
+parameter

DcmDspSecurityResetAttemptCounterOnTimeout:
EcucBooleanParamDef

defaultValue = false
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPid: EcucParamConfContainerDef
+subContainer
upperMultiplicity = *
lowerMultiplicity = 0

DcmDspVehInfo:
+subContainer EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

Figure 10.15: DcmDsp configuration overview Part1

562 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp: EcucParamConfContainerDef DcmDspEcuReset:

+subContainer EcucParamConfContainerDef
lowerMultiplicity = 0
upperMultiplicity = 1 lowerMultiplicity = 0
upperMultiplicity = 1
DcmDspRequestControl:
+subContainer EcucParamConfContainerDef

upperMultiplicity = *
DcmDspRoe: lowerMultiplicity = 0
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1
DcmDspComControl:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1
DcmDspDidRange:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *
DcmDspDDDIDcheckPerSourceDID:
+parameter EcucBooleanParamDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDataDefaultEndianness: +literal LITTLE_ENDIAN:

EcucEnumerationParamDef EcucEnumerationLiteralDef

+parameter +literal OPAQUE:

EcucEnumerationLiteralDef

+literal
BIG_ENDIAN:
EcucEnumerationLiteralDef

DcmDspClearDTC:
+subContainer EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 0 DcmDspEnableObdMirror:
EcucBooleanParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
defaultValue = false

Figure 10.16: DcmDsp configuration overview Part2

10.2.5.1 DcmDspReadDTCInformation

[ECUC_Dcm_01147] Definition of EcucParamConfContainerDef DcmDspRead

DTCInformation d
Container Name DcmDspReadDTCInformation
Parent Container DcmDsp
Description Provides further configuration for the UDS service ReadDTCInformation processing.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspReadDTCInformationSupportedObdUdsDtc 0..1 [ECUC_Dcm_01214]
Separation

563 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspReadDTCInformationUser 0..255 This container contains the configuration for user defined fault
DefinedFaultMemory memories in DcmDspReadDTCInformation.

[ECUC_Dcm_01214] Definition of EcucBooleanParamDef DcmDspReadDTCIn-

formationSupportedObdUdsDtcSeparation d
Parameter Name DcmDspReadDTCInformationSupportedObdUdsDtcSeparation
Parent Container DcmDspReadDTCInformation
Description If this parameter is set to true, the OBD UDS DTC separation is enabled. If this
parameter is not configured or set to false, the OBD UDS DTC separation is disabled.
Multiplicity 0..1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

10.2.5.2 DcmDspReadDTCInformationUserDefinedFaultMemory

[ECUC_Dcm_01148] Definition of EcucParamConfContainerDef DcmDspRead

DTCInformationUserDefinedFaultMemory d
Container Name DcmDspReadDTCInformationUserDefinedFaultMemory
Parent Container DcmDspReadDTCInformation
Description This container contains the configuration for user defined fault memories in DcmDsp
ReadDTCInformation.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspReadDTCInformationUserDefinedFaultMemoryId 1 [ECUC_Dcm_01149]
DcmDspReadDTCInformationUserDefinedFaultMemory 0..32 [ECUC_Dcm_01150]
RoleRef

No Included Containers

564 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01149] Definition of EcucIntegerParamDef DcmDspReadDTCInfor-

mationUserDefinedFaultMemoryId d
Parameter Name DcmDspReadDTCInformationUserDefinedFaultMemoryId
Parent Container DcmDspReadDTCInformationUserDefinedFaultMemory
Description Identifier used by external tester to identify the User defined event Memory.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01150] Definition of EcucReferenceDef DcmDspReadDTCInforma-

tionUserDefinedFaultMemoryRoleRef d
Parameter Name DcmDspReadDTCInformationUserDefinedFaultMemoryRoleRef
Parent Container DcmDspReadDTCInformationUserDefinedFaultMemory
Description Reference to DcmDspAuthenticationRow that defines a role in that this user defined
memory can be accessed.
Multiplicity 0..32
Type Reference to DcmDspAuthenticationRow
Post-Build Variant Multiplicity true
Post-Build Variant Value true
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

10.2.5.3 DcmDspAuthentication

[ECUC_Dcm_01151] Definition of EcucParamConfContainerDef DcmDspAuthen-

tication d

565 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspAuthentication

Parent Container DcmDsp
Description This container contains the configuration for the UDS service Authentication (0x29).
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspAuthenticationDefaultSessionTimeOut 0..1 [ECUC_Dcm_01161]
DcmDspAuthenticationGeneralNRC 0..1 [ECUC_Dcm_01159]
DcmDspAuthenticationRoleSize 1 [ECUC_Dcm_01152]
DcmDspAuthenticationWhiteListDIDMaxSize 0..1 [ECUC_Dcm_01155]
DcmDspAuthenticationWhiteListMemorySelectionMaxSize 0..1 [ECUC_Dcm_01157]
DcmDspAuthenticationWhiteListRIDMaxSize 0..1 [ECUC_Dcm_01156]
DcmDspAuthenticationWhiteListServicesMaxSize 0..1 [ECUC_Dcm_01154]
DcmDspAuthenticationDeauthenticatedRoleRef 1..32 [ECUC_Dcm_01153]
DcmDspAuthenticationGeneralNRCModeRuleRef 0..1 [ECUC_Dcm_01158]
DcmDspAuthenticationPersistStateModeRuleRef 0..1 [ECUC_Dcm_01160]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspAuthenticationConnection 0..* This container contains the authentication configuration use for a
dsl connection.
DcmDspAuthenticationRow 0..31 This container contains the definition of a single role. Each role
is a bit in the authentication role bitfield.
DcmDspAuthenticationTransmit 0..* This container contains the authentication configuration for the
Certificate subfunction trasnmitCertificate.

[ECUC_Dcm_01161] Definition of EcucFloatParamDef DcmDspAuthenticationDe-

faultSessionTimeOut d
Parameter Name DcmDspAuthenticationDefaultSessionTimeOut
Parent Container DcmDspAuthentication
Description Defines the number of seconds after which the Dcm makes a transition to
deauthenticated state, in case of no active communication.
Multiplicity 0..1
Type EcucFloatParamDef
Range [0 .. INF[
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
5

566 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01159] Definition of EcucIntegerParamDef DcmDspAuthentication

GeneralNRC d
Parameter Name DcmDspAuthenticationGeneralNRC
Parent Container DcmDspAuthentication
Description Defines the NRC that shall be send as replacement of all ISO 14229-1 defined NRCs in
case of invalid certificate or content.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01152] Definition of EcucIntegerParamDef DcmDspAuthentication

RoleSize d
Parameter Name DcmDspAuthenticationRoleSize
Parent Container DcmDspAuthentication
Description Defines the size in bytes for the role element within a certificate.
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 4
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

567 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01155] Definition of EcucIntegerParamDef DcmDspAuthentication

WhiteListDIDMaxSize d
Parameter Name DcmDspAuthenticationWhiteListDIDMaxSize
Parent Container DcmDspAuthentication
Description Defines the maximum size in bytes for the white list element within a certificate.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01157] Definition of EcucIntegerParamDef DcmDspAuthentication

WhiteListMemorySelectionMaxSize d
Parameter Name DcmDspAuthenticationWhiteListMemorySelectionMaxSize
Parent Container DcmDspAuthentication
Description Defines the maximum size in bytes for the white list element within a certificate.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01156] Definition of EcucIntegerParamDef DcmDspAuthentication

WhiteListRIDMaxSize d
Parameter Name DcmDspAuthenticationWhiteListRIDMaxSize
Parent Container DcmDspAuthentication
Description Defines the maximum size in bytes for the white list element within a certificate.
Multiplicity 0..1
Type EcucIntegerParamDef
5

568 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Range 1 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01154] Definition of EcucIntegerParamDef DcmDspAuthentication

WhiteListServicesMaxSize d
Parameter Name DcmDspAuthenticationWhiteListServicesMaxSize
Parent Container DcmDspAuthentication
Description Defines the maximum size in bytes for the white list element within a certificate.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01153] Definition of EcucReferenceDef DcmDspAuthentication

DeauthenticatedRoleRef d
Parameter Name DcmDspAuthenticationDeauthenticatedRoleRef
Parent Container DcmDspAuthentication
Description Reference to DcmDspAuthenticationRow that defines a role in that is used as
deauthenticated role.
Multiplicity 1..32
Type Reference to DcmDspAuthenticationRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

569 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01158] Definition of EcucReferenceDef DcmDspAuthentication

GeneralNRCModeRuleRef d
Parameter Name DcmDspAuthenticationGeneralNRCModeRuleRef
Parent Container DcmDspAuthentication
Description Mode rule that defines if the general NRC shall be send for all failures due to invalid
certificate or content.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01160] Definition of EcucReferenceDef DcmDspAuthenticationPer-

sistStateModeRuleRef d
Parameter Name DcmDspAuthenticationPersistStateModeRuleRef
Parent Container DcmDspAuthentication
Description References a mode rule that defines if the authentication state shall be persisted in
non-volatile memory.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.3.1 DcmDspAuthenticationTransmitCertificate

[ECUC_Dcm_01241] Definition of EcucParamConfContainerDef DcmDspAuthen-

ticationTransmitCertificate d

570 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspAuthenticationTransmitCertificate

Parent Container DcmDspAuthentication
Description This container contains the authentication configuration for the subfunction trasnmit
Certificate.
Post-Build Variant Multiplicity false
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspAuthenticationTransmitCertificateEvaluationId 1 [ECUC_Dcm_01242]
DcmDspAuthenticationTransmitCertificateFunction 0..1 [ECUC_Dcm_01244]
DcmDspAuthenticationTransmitCertificateRef 1 [ECUC_Dcm_01243]

No Included Containers

[ECUC_Dcm_01242] Definition of EcucIntegerParamDef DcmDspAuthentication

TransmitCertificateEvaluationId d
Parameter Name DcmDspAuthenticationTransmitCertificateEvaluationId
Parent Container DcmDspAuthenticationTransmitCertificate
Description Certificate evaluation id.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01244] Definition of EcucEnumerationParamDef DcmDspAuthenti-

cationTransmitCertificateFunction d
Parameter Name DcmDspAuthenticationTransmitCertificateFunction
Parent Container DcmDspAuthenticationTransmitCertificate
Description Provides a fixed semantics to this certificate that will lead to predefined actions in the
Dcm.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range SECURE_CODING This certificate is use write authenticated data.
5

571 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-Build Variant Multiplicity false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01243] Definition of EcucReferenceDef DcmDspAuthentication

TransmitCertificateRef d
Parameter Name DcmDspAuthenticationTransmitCertificateRef
Parent Container DcmDspAuthenticationTransmitCertificate
Description Reference to a KeyMCertificate used to handle the certificate.
Multiplicity 1
Type Symbolic name reference to KeyMCertificate
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.4 DcmDspAuthenticationRow

[ECUC_Dcm_01211] Definition of EcucParamConfContainerDef DcmDspAuthen-

ticationRow d
Container Name DcmDspAuthenticationRow
Parent Container DcmDspAuthentication
Description This container contains the definition of a single role. Each role is a bit in the
authentication role bitfield.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspAuthenticationRoleBitPosition 1 [ECUC_Dcm_01212]

No Included Containers

572 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01212] Definition of EcucIntegerParamDef DcmDspAuthentication

RoleBitPosition d
Parameter Name DcmDspAuthenticationRoleBitPosition
Parent Container DcmDspAuthenticationRow
Description Defines the bit number that represents the role in the authentication bit field. The bit
mask is aligned with the logical bit calculations: 2ˆDcmDspAuthenticationRoleBit
Position.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 31
Default value –
Scope / Dependency

10.2.5.5 DcmDspAuthenticationConnection

[ECUC_Dcm_01162] Definition of EcucParamConfContainerDef DcmDspAuthen-

ticationConnection d
Container Name DcmDspAuthenticationConnection
Parent Container DcmDspAuthentication
Description This container contains the authentication configuration use for a dsl connection.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspAuthenticationEcuChallengeLength 1 [ECUC_Dcm_01186]
DcmDspAuthenticationCertificatePublicKeyStoreJobRef 0..1 [ECUC_Dcm_01176]
DcmDspAuthenticationClientChallengeSignJobRef 1 [ECUC_Dcm_01174]
DcmDspAuthenticationConnectionCertificateRef 1 [ECUC_Dcm_01164]
DcmDspAuthenticationConnectionMainConnectionRef 1 [ECUC_Dcm_01163]
DcmDspAuthenticationECUCertificateKeyElementRef 0..1 [ECUC_Dcm_01178]
DcmDspAuthenticationECUCertificateRef 0..1 [ECUC_Dcm_01177]
DcmDspAuthenticationPublicKeyElementRef 0..1 [ECUC_Dcm_01166]
DcmDspAuthenticationRandomJobRef 1 [ECUC_Dcm_01173]
DcmDspAuthenticationRoleElementRef 1 [ECUC_Dcm_01167]
DcmDspAuthenticationVerifyProofOfOwnerShipClientJob 1 [ECUC_Dcm_01175]
Ref
DcmDspAuthenticationWhiteListDIDElementRef 0..1 [ECUC_Dcm_01169]
DcmDspAuthenticationWhiteListMemorySelectionElement 0..1 [ECUC_Dcm_01171]
Ref
5

573 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspAuthenticationWhiteListRIDElementRef 0..1 [ECUC_Dcm_01170]
DcmDspAuthenticationWhiteListServicesElementRef 0..1 [ECUC_Dcm_01168]

No Included Containers

[ECUC_Dcm_01186] Definition of EcucIntegerParamDef DcmDspAuthentication

EcuChallengeLength d
Parameter Name DcmDspAuthenticationEcuChallengeLength
Parent Container DcmDspAuthenticationConnection
Description Length in byte of the ECU challenge
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency

[ECUC_Dcm_01176] Definition of EcucReferenceDef DcmDspAuthenticationCer-

tificatePublicKeyStoreJobRef d
Parameter Name DcmDspAuthenticationCertificatePublicKeyStoreJobRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a CsmJob used to store the public key within the Csm.
Multiplicity 0..1
Type Symbolic name reference to CsmJob
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

574 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01174] Definition of EcucReferenceDef DcmDspAuthentication

ClientChallengeSignJobRef d
Parameter Name DcmDspAuthenticationClientChallengeSignJobRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a job used to sign the client challenge.
Multiplicity 1
Type Symbolic name reference to CsmJob
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01164] Definition of EcucReferenceDef DcmDspAuthentication

ConnectionCertificateRef d
Parameter Name DcmDspAuthenticationConnectionCertificateRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a KeyMCertificate used to store the certificate within the KeyM.
Multiplicity 1
Type Symbolic name reference to KeyMCertificate
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01163] Definition of EcucReferenceDef DcmDspAuthentication

ConnectionMainConnectionRef d
Parameter Name DcmDspAuthenticationConnectionMainConnectionRef
Parent Container DcmDspAuthenticationConnection
Description Reference to the dsl diagnostic connection that uses this authentication configuration.
5

575 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity 1
Type Reference to DcmDslMainConnection
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01178] Definition of EcucReferenceDef DcmDspAuthentication

ECUCertificateKeyElementRef d
Parameter Name DcmDspAuthenticationECUCertificateKeyElementRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a CryptoKeyElement used as server certificate during bi-directional
authentication.
Multiplicity 0..1
Type Symbolic name reference to CryptoKeyElement
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01177] Definition of EcucReferenceDef DcmDspAuthentication

ECUCertificateRef d
Parameter Name DcmDspAuthenticationECUCertificateRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a KeyMCertificate with the server certificate for bi-directional
authentication.
Multiplicity 0..1
Type Symbolic name reference to KeyMCertificate
Post-Build Variant Multiplicity false
Post-Build Variant Value false
5

576 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01166] Definition of EcucReferenceDef DcmDspAuthentication

PublicKeyElementRef d
Parameter Name DcmDspAuthenticationPublicKeyElementRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate data element with the public key in the certificate.
Multiplicity 0..1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01173] Definition of EcucReferenceDef DcmDspAuthentication

RandomJobRef d
Parameter Name DcmDspAuthenticationRandomJobRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate parse job used to parse the authentication certificate.
Multiplicity 1
Type Symbolic name reference to CsmJob
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
5

577 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01167] Definition of EcucReferenceDef DcmDspAuthenticationRole

ElementRef d
Parameter Name DcmDspAuthenticationRoleElementRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate data element with the role in the certificate.
Multiplicity 1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01175] Definition of EcucReferenceDef DcmDspAuthenticationVer-

ifyProofOfOwnerShipClientJobRef d
Parameter Name DcmDspAuthenticationVerifyProofOfOwnerShipClientJobRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a CsmJob used to verify the proof of ownership client in the Csm.
Multiplicity 1
Type Symbolic name reference to CsmJob
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

578 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01169] Definition of EcucReferenceDef DcmDspAuthentication

WhiteListDIDElementRef d
Parameter Name DcmDspAuthenticationWhiteListDIDElementRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate data element with the white list for data identifiers in the
certificate.
Multiplicity 0..1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01171] Definition of EcucReferenceDef DcmDspAuthentication

WhiteListMemorySelectionElementRef d
Parameter Name DcmDspAuthenticationWhiteListMemorySelectionElementRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate data element with the white list for user defined memory
selection in the certificate.
Multiplicity 0..1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

579 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01170] Definition of EcucReferenceDef DcmDspAuthentication

WhiteListRIDElementRef d
Parameter Name DcmDspAuthenticationWhiteListRIDElementRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate data element with the white list for routine identifiers in the
certificate.
Multiplicity 0..1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01168] Definition of EcucReferenceDef DcmDspAuthentication

WhiteListServicesElementRef d
Parameter Name DcmDspAuthenticationWhiteListServicesElementRef
Parent Container DcmDspAuthenticationConnection
Description Reference to a certificate data element with the white list in the certificate.
Multiplicity 0..1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

580 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.6 Communication Control

10.2.5.6.1 DcmDspComControl

[ECUC_Dcm_00900] Definition of EcucParamConfContainerDef DcmDspCom

Control d
Container Name DcmDspComControl
Parent Container DcmDsp
Description Provides the configuration of the CommunicationControl mechanism.
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspComControlAllChannel 0..* Collection of ComM channels which shall be controlled if all
networks are addressed.
DcmDspComControlSetting 0..1 Provide the configuration of the Communication control.
DcmDspComControlSpecific 0..* Assigns subnet number to ComM channel which will be
Channel controlled.
DcmDspComControlSubNode 0..65535 This container gives information about the node identification
number and the ComM channel used to address a sub-network.

581 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp:
EcucParamConfContainerDef
DcmDspAllComMChannelRef: EcucReferenceDef
lowerMultiplicity = 0
DcmDspComControlAllChannel: lowerMultiplicity = 1
upperMultiplicity = 1 +reference
EcucParamConfContainerDef upperMultiplicity = 1
requiresSymbolicNameValue = true
lowerMultiplicity = 0
upperMultiplicity = *
+subContainer

DcmDspComControl:
EcucParamConfContainerDef +subContainer +destination

lowerMultiplicity = 0 ComMChannel:
upperMultiplicity = 1 EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = 256

+parameter

DcmDspComControlAllChannelUsed:
+destination
EcucBooleanParamDef

upperMultiplicity = 1 +parameter
lowerMultiplicity = 1
defaultValue = true ComMChannelId:
EcucIntegerParamDef

min = 0
max = 255
withAuto = true
symbolicNameValue = true

DcmDspComControlSpecificChannel: DcmDspSpecificComMChannelRef:
EcucParamConfContainerDef EcucReferenceDef
+reference
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = * upperMultiplicity = 1
requiresSymbolicNameValue = true

DcmDspSubnetNumber:
+subContainer EcucIntegerParamDef
+parameter
min = 1
max = 14
lowerMultiplicity = 1
upperMultiplicity = 1

+parameter
DcmDspComControlSpecificChannelUsed:
EcucBooleanParamDef

upperMultiplicity = 1
lowerMultiplicity = 1
defaultValue = true
DcmDspComControlSetting:
EcucParamConfContainerDef
+subContainer
lowerMultiplicity = 0
upperMultiplicity = 1

+reference

DcmDspComControlCommunicationReEnableModeRuleRef: DcmModeRule:
EcucReferenceDef EcucParamConfContainerDef
+destination
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = *

Figure 10.17: DcmDspComControl configuration overview

10.2.5.6.2 DcmDspComControlAllChannel

[ECUC_Dcm_00901] Definition of EcucParamConfContainerDef DcmDspCom

ControlAllChannel d

582 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspComControlAllChannel

Parent Container DcmDspComControl
Description Collection of ComM channels which shall be controlled if all networks are addressed.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspComControlAllChannelUsed 1 [ECUC_Dcm_01045]
DcmDspAllComMChannelRef 1 [ECUC_Dcm_00902]

No Included Containers

[ECUC_Dcm_01045] Definition of EcucBooleanParamDef DcmDspComControl

AllChannelUsed d
Parameter Name DcmDspComControlAllChannelUsed
Parent Container DcmDspComControlAllChannel
Description Allow to activate or deactivate the usage of a ComM channel collection to be controlled,
for multi purpose ECUs
true = ComM channel collection used false = ComM channel collection not used
Multiplicity 1
Type EcucBooleanParamDef
Default value true
Post-Build Variant Value true
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

[ECUC_Dcm_00902] Definition of EcucReferenceDef DcmDspAllComMChannel

Ref d
Parameter Name DcmDspAllComMChannelRef
Parent Container DcmDspComControlAllChannel
Description Reference to ComM channel.
Multiplicity 1
Type Symbolic name reference to ComMChannel
Post-Build Variant Value true
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
5

583 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Scope / Dependency scope: ECU

10.2.5.6.3 DcmDspComControlSetting

[ECUC_Dcm_00943] Definition of EcucParamConfContainerDef DcmDspCom

ControlSetting d
Container Name DcmDspComControlSetting
Parent Container DcmDspComControl
Description Provide the configuration of the Communication control.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspComControlCommunicationReEnableModeRule 0..1 [ECUC_Dcm_00944]
Ref

No Included Containers

[ECUC_Dcm_00944] Definition of EcucReferenceDef DcmDspComControlCom-

municationReEnableModeRuleRef d
Parameter Name DcmDspComControlCommunicationReEnableModeRuleRef
Parent Container DcmDspComControlSetting
Description Reference to DcmModeRule Mode rule which controls re-enabling of communication
by DCM. [ref. SWS_Dcm_00753]
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

584 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.6.4 DcmDspComControlSpecificChannel

[ECUC_Dcm_00903] Definition of EcucParamConfContainerDef DcmDspCom

ControlSpecificChannel d
Container Name DcmDspComControlSpecificChannel
Parent Container DcmDspComControl
Description Assigns subnet number to ComM channel which will be controlled.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspComControlSpecificChannelUsed 1 [ECUC_Dcm_01046]
DcmDspSubnetNumber 1 [ECUC_Dcm_00905]
DcmDspSpecificComMChannelRef 1 [ECUC_Dcm_00904]

No Included Containers

[ECUC_Dcm_01046] Definition of EcucBooleanParamDef DcmDspComControl

SpecificChannelUsed d
Parameter Name DcmDspComControlSpecificChannelUsed
Parent Container DcmDspComControlSpecificChannel
Description Allow to activate or deactivate the usage of a Subnet assigned to the ComM channel
which will be controlled, for multi purpose ECUs.
true = Subnet used false = Subnet not used
Multiplicity 1
Type EcucBooleanParamDef
Default value true
Post-Build Variant Value true
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

[ECUC_Dcm_00905] Definition of EcucIntegerParamDef DcmDspSubnetNumber

d
Parameter Name DcmDspSubnetNumber
Parent Container DcmDspComControlSpecificChannel
Description Subnet Number which controls the specific ComMChannel.
5

585 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 14
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00904] Definition of EcucReferenceDef DcmDspSpecificCom

MChannelRef d
Parameter Name DcmDspSpecificComMChannelRef
Parent Container DcmDspComControlSpecificChannel
Description Reference to ComM channel.
Multiplicity 1
Type Symbolic name reference to ComMChannel
Post-Build Variant Value true
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

10.2.5.6.5 DcmDspComControlSubNode

[ECUC_Dcm_01033] Definition of EcucParamConfContainerDef DcmDspCom

ControlSubNode d
Container Name DcmDspComControlSubNode
Parent Container DcmDspComControl
Description This container gives information about the node identification number and the ComM
channel used to address a sub-network.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspComControlSubNodeId 1 [ECUC_Dcm_01031]
DcmDspComControlSubNodeUsed 1 [ECUC_Dcm_01032]
DcmDspComControlSubNodeComMChannelRef 1 [ECUC_Dcm_01030]

586 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

No Included Containers

[ECUC_Dcm_01031] Definition of EcucIntegerParamDef DcmDspComControl

SubNodeId d
Parameter Name DcmDspComControlSubNodeId
Parent Container DcmDspComControlSubNode
Description The node identification number DcmDspComControlSubNodeId is addressed by the
CommunicationControl (0x28) request.
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01032] Definition of EcucBooleanParamDef DcmDspComControl

SubNodeUsed d
Parameter Name DcmDspComControlSubNodeUsed
Parent Container DcmDspComControlSubNode
Description This parameter determines if a node control function is available or not.
Multiplicity 1
Type EcucBooleanParamDef
Default value true
Post-Build Variant Value true
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local

587 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01030] Definition of EcucReferenceDef DcmDspComControlSub

NodeComMChannelRef d
Parameter Name DcmDspComControlSubNodeComMChannelRef
Parent Container DcmDspComControlSubNode
Description This parameter references a ComM channel where this node is connected to.
Multiplicity 1
Type Symbolic name reference to ComMChannel
Post-Build Variant Value true
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

DcmDspComControl:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspComControlSubNode: DcmDspComControlSubNodeComMChannelRef: ComMChannel:

EcucParamConfContainerDef +reference EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 1 lowerMultiplicity = 1

upperMultiplicity = 65535 upperMultiplicity = 1 upperMultiplicity = 256
requiresSymbolicNameValue = true

DcmDspComControlSubNodeId:
EcucIntegerParamDef
+parameter
max = 65535
min = 1
upperMultiplicity = 1
lowerMultiplicity = 1

DcmDspComControlSubNodeUsed:
EcucBooleanParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
defaultValue = true

Figure 10.18: DcmDspComControlSubNode configuration overview

10.2.5.7 DcmDspCommonAuthorization

[ECUC_Dcm_01025] Definition of EcucParamConfContainerDef DcmDspCom-

monAuthorization d

588 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspCommonAuthorization

Parent Container DcmDsp
Description This container contains the configuration (parameters) for the common Authorization
being equal for several services / sub-services.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspCommonAuthorizationModeRuleRef 0..1 [ECUC_Dcm_01028]
DcmDspCommonAuthorizationSecurityLevelRef 0..* [ECUC_Dcm_01026]
DcmDspCommonAuthorizationSessionRef 0..* [ECUC_Dcm_01027]

No Included Containers

[ECUC_Dcm_01028] Definition of EcucReferenceDef DcmDspCommonAutho-

rizationModeRuleRef d
Parameter Name DcmDspCommonAuthorizationModeRuleRef
Parent Container DcmDspCommonAuthorization
Description Reference to DcmModeRule
Mode rule which controls this service/ sub-service. If there is no reference, no check of
the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

589 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01026] Definition of EcucReferenceDef DcmDspCommonAutho-

rizationSecurityLevelRef d
Parameter Name DcmDspCommonAuthorizationSecurityLevelRef
Parent Container DcmDspCommonAuthorization
Description Reference to DcmDspSecurityRow Security levels allowed to control this service/
sub-service. If there is no reference, no check of security level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01027] Definition of EcucReferenceDef DcmDspCommonAutho-

rizationSessionRef d
Parameter Name DcmDspCommonAuthorizationSessionRef
Parent Container DcmDspCommonAuthorization
Description Reference to DcmDspSessionRow Sessions allowed to control this service/
sub-service. If there is no reference, no check of session level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

590 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspCommonAuthorization: DcmDspCommonAuthorizationSecurityLevelRef: DcmDspSecurityRow:

EcucParamConfContainerDef EcucReferenceDef EcucParamConfContainerDef
+reference +destination
upperMultiplicity = * lowerMultiplicity = 0 upperMultiplicity = 31
lowerMultiplicity = 0 upperMultiplicity = * lowerMultiplicity = 0

DcmDspCommonAuthorizationSessionRef: DcmDspSessionRow:
EcucReferenceDef EcucParamConfContainerDef
+reference +destination
lowerMultiplicity = 0 upperMultiplicity = 31
upperMultiplicity = * lowerMultiplicity = 0

DcmDspCommonAuthorizationModeRuleRef: DcmModeRule:
+reference EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = *

Figure 10.19: DcmDspCommonAuthorization configuration overview

10.2.5.8 DIDs

10.2.5.8.1 DcmDspDid

[ECUC_Dcm_00601] Definition of EcucParamConfContainerDef DcmDspDid d

Container Name DcmDspDid
Parent Container DcmDsp
Description This container contains the configuration (parameters) of the DID.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDidIdentifier 1 [ECUC_Dcm_00602]
DcmDspDidSize 0..1 [ECUC_Dcm_01099]
DcmDspDidUsed 1 [ECUC_Dcm_00805]
DcmDspDidUsePort 1 [ECUC_Dcm_01122]
DcmDspDidBndMBlockIdRef 0..1 [ECUC_Dcm_01185]
DcmDspDidInfoRef 1 [ECUC_Dcm_00604]
DcmDspDidRef 0..* [ECUC_Dcm_00606]

591 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspDidSignal 0..* This container defines the reference to 1 DcmDspData container
and position relevant for this DID.
DcmDspDidSignalCompositePool 0..* Defines a collection of all contained signals for this root signal.
DcmDspDidSupportInfo 0..1 This container defines the support information to declare the
usability of the data bytes within the DIDs

[ECUC_Dcm_00602] Definition of EcucIntegerParamDef DcmDspDidIdentifier d

Parameter Name DcmDspDidIdentifier
Parent Container DcmDspDid
Description 2 byte Identifier of the DID
Within each DcmConfigSet all DcmDspDidIdentifier values shall be unique.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01099] Definition of EcucIntegerParamDef DcmDspDidSize d

Parameter Name DcmDspDidSize
Parent Container DcmDspDid
Description Length of a DID in byte(s).
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

592 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00805] Definition of EcucBooleanParamDef DcmDspDidUsed d

Parameter Name DcmDspDidUsed
Parent Container DcmDspDid
Description Allow to activate or deactivate the usage of a DID, for multi purpose ECUs
true = DID available false = DID not available
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value true
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

[ECUC_Dcm_01122] Definition of EcucEnumerationParamDef DcmDspDidUse

Port d
Parameter Name DcmDspDidUsePort
Parent Container DcmDspDid
Description Selects application interface type for DID data elements between a single operation for
all data elements or data element specific operations.
Multiplicity 1
Type EcucEnumerationParamDef
Range USE_ATOMIC_BNDM The DID shall be read/written from/to BndM.
USE_ATOMIC_NV_DATA_ A single sender receiver interface with Nv
INTERFACE Data-Ports is used for all data elements of this
DID.
USE_ATOMIC_SENDER_ A single sender receiver interface is used to
RECEIVER_INTERFACE access all data elements of this DID. The sender
receiver interface is typed with IsService=false.
USE_ATOMIC_SENDER_ A single sender receiver interface is used to
RECEIVER_INTERFACE_AS_ access all data elements of this DID. The sender
SERVICE receiver interface is typed with IsService=true.
USE_DATA_ELEMENT_ The data elements of this DID are collected by
SPECIFIC_INTERFACES using the data element specific interfaces
defined by DcmDspDataUsePort.
Default value USE_DATA_ELEMENT_SPECIFIC_INTERFACES
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency

593 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01185] Definition of EcucReferenceDef DcmDspDidBndMBlockId

Ref d
Parameter Name DcmDspDidBndMBlockIdRef
Parent Container DcmDspDid
Description Associate this DID with a BndM blockId.
Multiplicity 0..1
Type Symbolic name reference to BndMBlockDescriptor
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU
dependency: DcmDspDidUsePort == USE_ATOMIC_BNDM

[ECUC_Dcm_00604] Definition of EcucReferenceDef DcmDspDidInfoRef d

Parameter Name DcmDspDidInfoRef
Parent Container DcmDspDid
Description Reference to DcmDspDidInfo containing information on this DID.
Multiplicity 1
Type Reference to DcmDspDidInfo
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00606] Definition of EcucReferenceDef DcmDspDidRef d

Parameter Name DcmDspDidRef
Parent Container DcmDspDid
Description Reference to DcmDspDid in case this DID refer to one or serveral other DID’s
Attributes: requiresIndex=true
Multiplicity 0..*
Type Reference to DcmDspDid
Post-Build Variant Multiplicity false
5

594 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

595 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp:
EcucParamConfContainerDef
DcmDspData:
lowerMultiplicity = 0 EcucParamConfContainerDef
upperMultiplicity = 1 +subContainer
lowerMultiplicity = 0
upperMultiplicity = *

+destination

DcmDspDidDataRef:
EcucReferenceDef USE_ATOMIC_SENDER_RECEIVER_INTERFACE:
EcucEnumerationLiteralDef
lowerMultiplicity = 0
+reference upperMultiplicity = 1 +literal

DcmDspDidSignal:
EcucParamConfContainerDef USE_ATOMIC_NV_DATA_INTERFACE:
+parameter DcmDspDidByteOffset: EcucEnumerationLiteralDef
lowerMultiplicity = 0 EcucIntegerParamDef
upperMultiplicity = * +literal
lowerMultiplicity = 1
upperMultiplicity = 1
+subContainer USE_ATOMIC_BNDM:
+subContainer min = 0
max = 65535 EcucEnumerationLiteralDef
DcmDspDid:
EcucParamConfContainerDef +subContainer +literal
upperMultiplicity = * DcmDspDidInfoRef: DcmDspDidInfo:
lowerMultiplicity = 0 EcucReferenceDef +destination EcucParamConfContainerDef
+reference
lowerMultiplicity = 1 upperMultiplicity = *
upperMultiplicity = 1 lowerMultiplicity = 0

DcmDspDidIdentifier: DcmDspDidUsePort: EcucEnumerationParamDef

EcucIntegerParamDef
defaultValue = USE_DATA_ELEMENT_SPECIFIC_INTERFACES
+parameter lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 65535
+parameter

+destination DcmDspDidRef:
+literal
EcucReferenceDef

lowerMultiplicity = 0 USE_DATA_ELEMENT_SPECIFIC_INTERFACES:
+reference upperMultiplicity = * EcucEnumerationLiteralDef
requiresIndex = true +literal

USE_ATOMIC_SENDER_RECEIVER_INTERFACE_AS_SERVICE:
DcmDspDidUsed: EcucEnumerationLiteralDef
+parameter EcucBooleanParamDef

upperMultiplicity = 1
lowerMultiplicity = 1 DcmDspDidSupportInfoPos:
EcucIntegerParamDef

min = 0
DcmDspDidSupportInfo: +parameter max = 255
EcucParamConfContainerDef lowerMultiplicity = 1 DcmDspDidSupportInfoLen:
+subContainer upperMultiplicity = 1 EcucIntegerParamDef
lowerMultiplicity = 0
upperMultiplicity = 1 min = 0
max = 255
+parameter lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspDidSize:
EcucIntegerParamDef
+parameter BndMBlockIdentifier: EcucIntegerParamDef
min = 0
max = 65535 min = 0
lowerMultiplicity = 0 max = 65535
upperMultiplicity = 1 symbolicNameValue = true
+parameter

DcmDspDidBndMBlockIdRef:
EcucReferenceDef BndMBlockDescriptor:
+destination EcucParamConfContainerDef
+reference lowerMultiplicity = 0
upperMultiplicity = 1 lowerMultiplicity = 0
requiresSymbolicNameValue = true upperMultiplicity = *

Figure 10.20: DcmDspDid configuration overview

596 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.8.2 DcmDspDidInfo

[ECUC_Dcm_00607] Definition of EcucParamConfContainerDef DcmDspDidInfo

d
Container Name DcmDspDidInfo
Parent Container DcmDsp
Description This container contains the configuration (parameters) of the DID’s Info
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDDDIDMaxElements 0..1 [ECUC_Dcm_00970]
DcmDspDidDynamicallyDefined 1 [ECUC_Dcm_00612]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspDidControl 0..1 This container contains the configuration (parameters) of the DID
control.
DcmDspDidRead 0..1 This container contains the configuration (parameters) of the DID
read.
DcmDspDidWrite 0..1 This container contains the configuration (parameters) of the DID
write.

[ECUC_Dcm_00970] Definition of EcucIntegerParamDef DcmDspDDDIDMaxEle-

ments d
Parameter Name DcmDspDDDIDMaxElements
Parent Container DcmDspDidInfo
Description Maximum number of source elements of a DDDID.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

597 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00612] Definition of EcucBooleanParamDef DcmDspDidDynami-

callyDefined d
Parameter Name DcmDspDidDynamicallyDefined
Parent Container DcmDspDidInfo
Description Indicates if this DID can be dynamically defined
true = DID can be dynamically defined false = DID can not be dynamically defined
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

DcmDsp:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspDidInfo: DcmDspDidRead:
EcucParamConfContainerDef EcucParamConfContainerDef
+subContainer
upperMultiplicity = * upperMultiplicity = 1
lowerMultiplicity = 0 lowerMultiplicity = 0

DcmDspDidWrite:
EcucParamConfContainerDef
+subContainer
upperMultiplicity = 1
lowerMultiplicity = 0

DcmDspDidControl:
EcucParamConfContainerDef
+subContainer
upperMultiplicity = 1
lowerMultiplicity = 0

DcmDspDidDynamicallyDefined:
EcucBooleanParamDef
+parameter
upperMultiplicity = 1
lowerMultiplicity = 1

DcmDspDDDIDMaxElements:
EcucIntegerParamDef
+parameter lowerMultiplicity = 0
upperMultiplicity = 1
min = 1
max = 255

Figure 10.21: DcmDspDidInfo configuration overview

598 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.8.3 DcmDspDidRead

[ECUC_Dcm_00613] Definition of EcucParamConfContainerDef DcmDspDid

Read d
Container Name DcmDspDidRead
Parent Container DcmDspDidInfo
Description This container contains the configuration (parameters) of the DID read.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDidReadModeRuleRef 0..1 [ECUC_Dcm_00917]
DcmDspDidReadRoleRef 0..32 [ECUC_Dcm_01141]
DcmDspDidReadSecurityLevelRef 0..* [ECUC_Dcm_00614]
DcmDspDidReadSessionRef 0..* [ECUC_Dcm_00615]

No Included Containers

[ECUC_Dcm_00917] Definition of EcucReferenceDef DcmDspDidReadModeRule

Ref d
Parameter Name DcmDspDidReadModeRuleRef
Parent Container DcmDspDidRead
Description Reference to DcmModeRule
Mode rule which controls to read this DID. If there is no reference, no check of the
mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

599 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01141] Definition of EcucReferenceDef DcmDspDidReadRoleRef d

Parameter Name DcmDspDidReadRoleRef
Parent Container DcmDspDidRead
Description Reference to DcmDspAuthenticationRow that defines a role in that this DID can be
read.
Multiplicity 0..32
Type Reference to DcmDspAuthenticationRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00614] Definition of EcucReferenceDef DcmDspDidReadSecurity

LevelRef d
Parameter Name DcmDspDidReadSecurityLevelRef
Parent Container DcmDspDidRead
Description Reference to DcmDspSecurityRow Referenced security levels are allowed to read this
DID.
If there is no reference, no check of security level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

600 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00615] Definition of EcucReferenceDef DcmDspDidReadSession

Ref d
Parameter Name DcmDspDidReadSessionRef
Parent Container DcmDspDidRead
Description Reference to DcmDspSessionRow Referenced sessions are allowed to read this DID.
If there is no reference, no check of session level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

DcmDspDidInfo:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

+subContainer

DcmDspDidRead: DcmDspDidReadSecurityLevelRef: DcmDspSecurityRow:

EcucParamConfContainerDef EcucReferenceDef EcucParamConfContainerDef
+reference +destination
upperMultiplicity = 1 lowerMultiplicity = 0 upperMultiplicity = 31
lowerMultiplicity = 0 upperMultiplicity = * lowerMultiplicity = 0

DcmDspDidReadSessionRef: DcmDspSessionRow:
EcucReferenceDef EcucParamConfContainerDef
+reference +destination
lowerMultiplicity = 0 upperMultiplicity = 31
upperMultiplicity = * lowerMultiplicity = 0

DcmDspDidReadModeRuleRef: DcmModeRule:
EcucReferenceDef EcucParamConfContainerDef
+reference +destination
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = *

+reference

DcmDspDidReadRoleRef:
EcucReferenceDef
DcmDspAuthenticationRow:
+destination EcucParamConfContainerDef
lowerMultiplicity = 0
upperMultiplicity = 32
lowerMultiplicity = 0
upperMultiplicity = 31

Figure 10.22: DcmDspDidRead configuration overview

601 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.8.4 DcmDspDidSignal

[ECUC_Dcm_00813] Definition of EcucParamConfContainerDef DcmDspDidSig-

nal d
Container Name DcmDspDidSignal
Parent Container DcmDspDid, DcmDspDidSignalCompositePool
Description This container defines the reference to 1 DcmDspData container and position relevant
for this DID.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDataByteSize 0..1 [ECUC_Dcm_01106]
DcmDspDidByteOffset 1 [ECUC_Dcm_01105]
DcmDspDidDataRef 0..1 [ECUC_Dcm_00808]
DcmDspDidSignalCompositeRef 0..* [ECUC_Dcm_01232]

No Included Containers

For parameter table [ECUC_Dcm_01106] DcmDspDataByteSize, see definition below

container DcmDspData.

[ECUC_Dcm_01105] Definition of EcucIntegerParamDef DcmDspDidByteOffset d

Parameter Name DcmDspDidByteOffset
Parent Container DcmDspDidSignal
Description Defines the absolute byte offset of the data defined by DcmDspDidDataRef reference
to DcmDspData container in the DID.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

602 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00808] Definition of EcucReferenceDef DcmDspDidDataRef d

Parameter Name DcmDspDidDataRef
Parent Container DcmDspDidSignal
Description Reference to 1 DcmDspData container relevant for this DID.
Multiplicity 0..1
Type Reference to DcmDspData
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01232] Definition of EcucReferenceDef DcmDspDidSignalCompos-

iteRef d
Parameter Name DcmDspDidSignalCompositeRef
Parent Container DcmDspDidSignal
Description Reference to the contained signal.
Multiplicity 0..*
Type Reference to DcmDspDidSignalCompositePool
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.8.5 DcmDspDidSignalCompositePool

[ECUC_Dcm_01231] Definition of EcucParamConfContainerDef DcmDspDidSig-

nalCompositePool d
Container Name DcmDspDidSignalCompositePool
Parent Container DcmDspDid
Description Defines a collection of all contained signals for this root signal.
5

603 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-Build Variant Multiplicity false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspDidSignal 0..* This container defines the reference to 1 DcmDspData container
and position relevant for this DID.

10.2.5.8.6 DcmDspDidSupportInfo

[ECUC_Dcm_01102] Definition of EcucParamConfContainerDef DcmDspDidSup-

portInfo d
Container Name DcmDspDidSupportInfo
Parent Container DcmDspDid
Description This container defines the support information to declare the usability of the data bytes
within the DIDs
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDidSupportInfoLen 1 [ECUC_Dcm_01103]
DcmDspDidSupportInfoPos 1 [ECUC_Dcm_01100]

No Included Containers

[ECUC_Dcm_01103] Definition of EcucIntegerParamDef DcmDspDidSupportInfo

Len d
Parameter Name DcmDspDidSupportInfoLen
Parent Container DcmDspDidSupportInfo
Description Length of the support information in bytes.
Multiplicity 1
5

604 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01100] Definition of EcucIntegerParamDef DcmDspDidSupportInfo

Pos d
Parameter Name DcmDspDidSupportInfoPos
Parent Container DcmDspDidSupportInfo
Description Position of the support information in bytes.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

10.2.5.8.7 DcmDspDidRange

[ECUC_Dcm_00937] Definition of EcucParamConfContainerDef DcmDspDid

Range d
Container Name DcmDspDidRange
Parent Container DcmDsp
Description This container defines the DID Range
Configuration Parameters

605 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDidRangeHasGaps 1 [ECUC_Dcm_00941]
DcmDspDidRangeIdentifierLowerLimit 1 [ECUC_Dcm_00938]
DcmDspDidRangeIdentifierUpperLimit 1 [ECUC_Dcm_00939]
DcmDspDidRangeIsDidAvailableFnc 0..1 [ECUC_Dcm_00946]
DcmDspDidRangeMaxDataLength 1 [ECUC_Dcm_00940]
DcmDspDidRangeReadDataLengthFnc 0..1 [ECUC_Dcm_01067]
DcmDspDidRangeReadDidFnc 0..1 [ECUC_Dcm_00947]
DcmDspDidRangeUsePort 1 [ECUC_Dcm_00945]
DcmDspDidRangeWriteDidFnc 0..1 [ECUC_Dcm_00948]
DcmDspDidRangeInfoRef 1 [ECUC_Dcm_00950]

No Included Containers

[ECUC_Dcm_00941] Definition of EcucBooleanParamDef DcmDspDidRangeHas

Gaps d
Parameter Name DcmDspDidRangeHasGaps
Parent Container DcmDspDidRange
Description Parameter specifying if there are gaps in the DID range (parameter set to TRUE) or not
(parameter set to FALSE)
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00938] Definition of EcucIntegerParamDef DcmDspDidRangeIden-

tifierLowerLimit d
Parameter Name DcmDspDidRangeIdentifierLowerLimit
Parent Container DcmDspDidRange
Description Lower limit of DID range.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
5

606 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00939] Definition of EcucIntegerParamDef DcmDspDidRangeIden-

tifierUpperLimit d
Parameter Name DcmDspDidRangeIdentifierUpperLimit
Parent Container DcmDspDidRange
Description Upper limit of DID range.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00946] Definition of EcucFunctionNameDef DcmDspDidRangeIs

DidAvailableFnc d
Parameter Name DcmDspDidRangeIsDidAvailableFnc
Parent Container DcmDspDidRange
Description Function name to request from application if a specific DID is available within the range
or not. Only relevant if DcmDspDidRangeUsePort is set to false. This parameter is
related to the interface Xxx_IsDidAvailable.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
5

607 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00940] Definition of EcucIntegerParamDef DcmDspDidRangeMax

DataLength d
Parameter Name DcmDspDidRangeMaxDataLength
Parent Container DcmDspDidRange
Description Maximum data length in bytes
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01067] Definition of EcucFunctionNameDef DcmDspDidRange

ReadDataLengthFnc d
Parameter Name DcmDspDidRangeReadDataLengthFnc
Parent Container DcmDspDidRange
Description Function name to request from application the length of the data of a range DID.
Only relevant if DcmDspDidRangeUsePort is set to false. This parameter is related to
the interface Xxx_ReadDidRangeDataLength.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

608 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00947] Definition of EcucFunctionNameDef DcmDspDidRange

ReadDidFnc d
Parameter Name DcmDspDidRangeReadDidFnc
Parent Container DcmDspDidRange
Description Function name to request from application the data range value of a DID.(Read
Data-function). Only relevant if DcmDspDidRangeUsePort is set to false. This
parameter is related to the interface Xxx_ReadDidData.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00945] Definition of EcucBooleanParamDef DcmDspDidRangeUse

Port d
Parameter Name DcmDspDidRangeUsePort
Parent Container DcmDspDidRange
Description When the parameter DcmDspDidRangeUsePort is set to true the DCM will access the
Data using an R-Port requiring a PortInteface DataServices_DIDRange. In that case,
DcmDspDidRangeIsDidAvailableFnc, DcmDspDidRangeReadDidFnc and DcmDspDid
RangeWriteDidFnc are ignored and the RTE APIs are used. When the parameter Dcm
DspDidRangeUsePort is false, the DCM calls the functions defined in DcmDspDid
RangeIsDidAvailableFnc, DcmDspDidRangeReadDidFnc and DcmDspDidRangeWrite
DidFnc.
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

609 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00948] Definition of EcucFunctionNameDef DcmDspDidRange

WriteDidFnc d
Parameter Name DcmDspDidRangeWriteDidFnc
Parent Container DcmDspDidRange
Description Function name to request application to write the data range value of a DID.(Write
Data-function). Only relevant if DcmDspDidRangeUsePort is set to false. This
parameter is related to the interface Xxx_WriteDidData.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00950] Definition of EcucReferenceDef DcmDspDidRangeInfoRef d

Parameter Name DcmDspDidRangeInfoRef
Parent Container DcmDspDidRange
Description Reference to DcmDspDidInfo containing information on this DID Range.
Multiplicity 1
Type Reference to DcmDspDidInfo
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

610 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspDidRange: EcucParamConfContainerDef DcmDspDidRangeIdentifierLowerLimit:

+parameter EcucIntegerParamDef
lowerMultiplicity = 0
upperMultiplicity = * min = 0
max = 65535

DcmDspDidRangeIdentifierUpperLimit:
+parameter EcucIntegerParamDef

min = 0
max = 65535

DcmDspDidRangeMaxDataLength:
+parameter EcucIntegerParamDef

min = 0
max = 65535

+parameter DcmDspDidRangeHasGaps:
EcucBooleanParamDef

+parameter DcmDspDidRangeUsePort:
EcucBooleanParamDef

DcmDspDidRangeIsDidAvailableFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidRangeReadDataLengthFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidRangeReadDidFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidRangeWriteDidFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidRangeInfoRef: DcmDspDidInfo:
+reference EcucReferenceDef +destination EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

Figure 10.23: DcmDspDidRange configuration overview

10.2.5.8.8 DcmDspDidWrite

[ECUC_Dcm_00616] Definition of EcucParamConfContainerDef DcmDspDid

Write d
Container Name DcmDspDidWrite
Parent Container DcmDspDidInfo
Description This container contains the configuration (parameters) of the DID write.
Configuration Parameters

611 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDidWriteModeRuleRef 0..1 [ECUC_Dcm_00922]
DcmDspDidWriteRoleRef 0..32 [ECUC_Dcm_01142]
DcmDspDidWriteSecurityLevelRef 0..* [ECUC_Dcm_00617]
DcmDspDidWriteSessionRef 0..* [ECUC_Dcm_00618]

No Included Containers

[ECUC_Dcm_00922] Definition of EcucReferenceDef DcmDspDidWriteModeRule

Ref d
Parameter Name DcmDspDidWriteModeRuleRef
Parent Container DcmDspDidWrite
Description Reference to DcmModeRule
Mode rule which controls to write this DID. If there is no reference, no check of the
mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01142] Definition of EcucReferenceDef DcmDspDidWriteRoleRef d

Parameter Name DcmDspDidWriteRoleRef
Parent Container DcmDspDidWrite
Description Reference to DcmDspAuthenticationRow that defines a role in that this DID can be
written.
Multiplicity 0..32
Type Reference to DcmDspAuthenticationRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
5

612 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Scope / Dependency scope: ECU

[ECUC_Dcm_00617] Definition of EcucReferenceDef DcmDspDidWriteSecurity

LevelRef d
Parameter Name DcmDspDidWriteSecurityLevelRef
Parent Container DcmDspDidWrite
Description Reference to DcmDspSecurityRow Referenced security levels are allowed to wirte this
DID.
If there is no reference, no check of security level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00618] Definition of EcucReferenceDef DcmDspDidWriteSession

Ref d
Parameter Name DcmDspDidWriteSessionRef
Parent Container DcmDspDidWrite
Description Reference to DcmDspSessionRow Referenced sessions are allowed to write this DID.
If there is no reference, no check of session level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
5

613 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Scope / Dependency scope: ECU

DcmDspDidInfo:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

+subContainer

DcmDspDidWrite: DcmDspDidWriteSecurityLevelRef: DcmDspSecurityRow:

EcucParamConfContainerDef EcucReferenceDef EcucParamConfContainerDef
+reference +destination
upperMultiplicity = 1 lowerMultiplicity = 0 upperMultiplicity = 31
lowerMultiplicity = 0 upperMultiplicity = * lowerMultiplicity = 0

DcmDspDidWriteSessionRef: DcmDspSessionRow:
EcucReferenceDef EcucParamConfContainerDef
+reference +destination
lowerMultiplicity = 0 upperMultiplicity = 31
upperMultiplicity = * lowerMultiplicity = 0

DcmDspDidWriteModeRuleRef: DcmModeRule:
EcucReferenceDef EcucParamConfContainerDef
+reference +destination
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = *

+reference

DcmDspDidWriteRoleRef:
EcucReferenceDef
DcmDspAuthenticationRow:
lowerMultiplicity = 0 +destination EcucParamConfContainerDef
upperMultiplicity = 32
lowerMultiplicity = 0
upperMultiplicity = 31

Figure 10.24: DcmDspDidWrite configuration overview

10.2.5.9 DcmDspControlDTCSetting

[ECUC_Dcm_00935] Definition of EcucParamConfContainerDef DcmDspControl

DTCSetting d
Container Name DcmDspControlDTCSetting
Parent Container DcmDsp
Description Provide the configuration of the ControlDTCSetting mechanism.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmSupportDTCSettingControlOptionRecord 0..1 [ECUC_Dcm_00965]
DcmDspControlDTCSettingReEnableModeRuleRef 0..1 [ECUC_Dcm_00936]

614 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

No Included Containers

[ECUC_Dcm_00965] Definition of EcucBooleanParamDef DcmSupportDTCSet-

tingControlOptionRecord d
Parameter Name DcmSupportDTCSettingControlOptionRecord
Parent Container DcmDspControlDTCSetting
Description This configuration switch defines if the DTCSettingControlOptionRecord is in general
supported in the request message or not.
Multiplicity 0..1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00936] Definition of EcucReferenceDef DcmDspControlDTCSetting

ReEnableModeRuleRef d
Parameter Name DcmDspControlDTCSettingReEnableModeRuleRef
Parent Container DcmDspControlDTCSetting
Description Reference to DcmModeRule
Mode rule which controls re-enabling of controlDTCsetting by DCM. The DCM module
shall execute a ControlDTCSetting.Off (call Dem_EnableDTCSetting()) in case that the
referenced mode rule is not fulfilled anymore.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
5

615 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Scope / Dependency scope: ECU

DcmDsp:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspControlDTCSetting: DcmDspControlDTCSettingReEnableModeRuleRef: DcmModeRule:

EcucParamConfContainerDef EcucReferenceDef +destination EcucParamConfContainerDef
+reference
lowerMultiplicity = 0 lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1 upperMultiplicity = *

DcmSupportDTCSettingControlOptionRecord:
+parameter EcucBooleanParamDef

upperMultiplicity = 1
lowerMultiplicity = 0
defaultValue = false

Figure 10.25: DcmDspControlDTCSetting configuration overview

10.2.5.10 Data elements

10.2.5.10.1 DcmDspData

[ECUC_Dcm_00869] Definition of EcucParamConfContainerDef DcmDspData d

Container Name DcmDspData
Parent Container DcmDsp
Description This container contains the configuration (parameters) of a Data belonging to a DID
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDataByteSize 0..1 [ECUC_Dcm_01106]
DcmDspDataConditionCheckReadFnc 0..1 [ECUC_Dcm_00677]
DcmDspDataConditionCheckReadFncUsed 0..1 [ECUC_Dcm_00955]
DcmDspDataEcuSignal 0..1 [ECUC_Dcm_00825]
DcmDspDataEndianness 0..1 [ECUC_Dcm_00986]
DcmDspDataFreezeCurrentStateFnc 0..1 [ECUC_Dcm_00674]
DcmDspDataGetScalingInfoFnc 0..1 [ECUC_Dcm_00676]
DcmDspDataReadDataLengthFnc 0..1 [ECUC_Dcm_00671]
5

616 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDataReadEcuSignal 0..1 [ECUC_Dcm_00824]
DcmDspDataReadFnc 0..1 [ECUC_Dcm_00669]
DcmDspDataResetToDefaultFnc 0..1 [ECUC_Dcm_00673]
DcmDspDataReturnControlToEcuFnc 0..1 [ECUC_Dcm_00672]
DcmDspDataShortTermAdjustmentFnc 0..1 [ECUC_Dcm_00675]
DcmDspDataType 1 [ECUC_Dcm_00985]
DcmDspDataUsePort 1 [ECUC_Dcm_00713]
DcmDspDataWriteFnc 0..1 [ECUC_Dcm_00670]
DcmDspOdxDataDescription 0..1 [ECUC_Dcm_00988]
DcmDspDataInfoRef 0..1 [ECUC_Dcm_00811]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspDiagnosisScaling 0..1 This container contains the configuration (parameters) of an
alternative Diagnosis Representation. Out if this the scaling
between Diagnosis and ECU internal representation and vice
versa can be calculated.
DcmDspDidDataSupportInfo 0..1 This container defines the supported information.
DcmDspExternalSRDataElement 0..1 This container defines the source of data in a provided port
Class which shall be read respectively the target of data in a required
port which shall be written.
This container shall contain either one DcmSubElementInData
ElementInstance OR DcmDataElementInstance OR DcmSub
ElementInImplDataElementInstance reference.

[ECUC_Dcm_01106] Definition of EcucIntegerParamDef DcmDspDataByteSize d

Parameter Name DcmDspDataByteSize
Parent Container DcmDspData, DcmDspDidSignal
Description Defines the array length in bytes or the maximum array length for variable datalengths.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
5

617 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Scope / Dependency scope: ECU

[ECUC_Dcm_00677] Definition of EcucFunctionNameDef DcmDspDataCondition

CheckReadFnc d
Parameter Name DcmDspDataConditionCheckReadFnc
Parent Container DcmDspData
Description Function name to demand application if the conditions (e.g. System state) to read the
DID are correct. (ConditionCheckRead-function).
Multiplicity shall be equal to parameter DcmDspDataReadFnc. This parameter is
related to the interface Xxx_ConditionCheckRead.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00955] Definition of EcucBooleanParamDef DcmDspDataCondition

CheckReadFncUsed d
Parameter Name DcmDspDataConditionCheckReadFncUsed
Parent Container DcmDspData
Description This parameter determines if a condition check function is available or not.
Multiplicity 0..1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
5

618 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Scope / Dependency scope: local

[ECUC_Dcm_00825] Definition of EcucFunctionNameDef DcmDspDataEcuSignal

d
Parameter Name DcmDspDataEcuSignal
Parent Container DcmDspData
Description Function name to control the access to a certain ECU Signal by the DCM. (IoHwAb_
Dcm_<symbolic name of ECU signal>-function).
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00986] Definition of EcucEnumerationParamDef DcmDspDataEndi-

anness d
Parameter Name DcmDspDataEndianness
Parent Container DcmDspData
Description Defines the endianness of the data belonging to a DID in a diagnostic request or
response message.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at the lowest
address.
LITTLE_ENDIAN Most significant byte shall be stored at the
highest address.
OPAQUE Opaque data endianness
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
5

619 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00674] Definition of EcucFunctionNameDef DcmDspDataFreeze

CurrentStateFnc d
Parameter Name DcmDspDataFreezeCurrentStateFnc
Parent Container DcmDspData
Description Function name to request to application to freeze the current state of an IOControl.
(FreezeCurrentState-function).
This parameter is related to the interface Xxx_FreezeCurrentState.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00676] Definition of EcucFunctionNameDef DcmDspDataGetScal-

ingInfoFnc d
Parameter Name DcmDspDataGetScalingInfoFnc
Parent Container DcmDspData
Description Function name to request to application the scaling information of the DID. (GetScaling
Information-function). This parameter is related to the interface Xxxx_GetScaling
Information.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
5

620 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00671] Definition of EcucFunctionNameDef DcmDspDataReadData

LengthFnc d
Parameter Name DcmDspDataReadDataLengthFnc
Parent Container DcmDspData
Description Function name to request from application the data length of a DID. (ReadData
Length-function). This parameter is related to the interface Xxx_ReadDataLength.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00824] Definition of EcucFunctionNameDef DcmDspDataReadEcu

Signal d
Parameter Name DcmDspDataReadEcuSignal
Parent Container DcmDspData
Description Function name for read access to a certain ECU Signal by the DCM. (IoHwAb_Dcm_
Read<EcuSignalName>-function).
Only relevant if DcmDspDataUsePort==USE_ECU_SIGNAL.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
5

621 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00669] Definition of EcucFunctionNameDef DcmDspDataReadFnc

d
Parameter Name DcmDspDataReadFnc
Parent Container DcmDspData
Description Function name to request from application the data value of a DID. (Read
Data-function). This parameter is related to the interface Xxx_ReadData.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00673] Definition of EcucFunctionNameDef DcmDspDataResetTo

DefaultFnc d
Parameter Name DcmDspDataResetToDefaultFnc
Parent Container DcmDspData
Description Function name to request to application to reset an IOControl to default value. (Reset
ToDefault-function). This parameter is related to the interface Xxx_ResetToDefault.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
5

622 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00672] Definition of EcucFunctionNameDef DcmDspDataReturn

ControlToEcuFnc d
Parameter Name DcmDspDataReturnControlToEcuFnc
Parent Container DcmDspData
Description Function name to request to application to return control to ECU of an IOControl.
(ReturnControlToECU-function). This parameter is related to the interface Xxx_Return
ControlToECU.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00675] Definition of EcucFunctionNameDef DcmDspDataShort

TermAdjustmentFnc d
Parameter Name DcmDspDataShortTermAdjustmentFnc
Parent Container DcmDspData
Description Function name to request to application to adjust the IO signal. (ShortTerm
Adjustment-function).
This parameter is related to the interface Xxx_ShortTermAdjustment.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
5

623 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00985] Definition of EcucEnumerationParamDef DcmDspDataType

d
Parameter Name DcmDspDataType
Parent Container DcmDspData
Description Provide the implementation data type of data belonging to a DID.
Multiplicity 1
Type EcucEnumerationParamDef
BOOLEAN Type of the data is boolean.
Range
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the data is sint16.
SINT16_N Type of the data is sint16 array.
SINT32 Type of the data is sint32.
SINT32_N Type of the data is sint32 array.
SINT8 Type of the data is sint8.
SINT8_N Type of the data is sint8 array.
UINT16 Type of the data is uint16.
UINT16_N Type of the data is uint16 array.
UINT32 Type of the data is uint32.
UINT32_N Type of the data is uint32 array.
UINT8 Type of the data is uint8.
UINT8_DYN Type of the data is uint8 array with dynamic
length.
UINT8_N Type of the data is uint8 array.
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

624 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00713] Definition of EcucEnumerationParamDef DcmDspDataUse

Port d
Parameter Name DcmDspDataUsePort
Parent Container DcmDspData
Description Defines which interface shall be used to access the data.
Multiplicity 1
Type EcucEnumerationParamDef

Range USE_DATA_ASYNCH_CLIENT_ The DCM will access the Data using an R-Port
SERVER requiring a asynchronous ClientServertInterface
DataServices_{Data}. The R-Port is named Data
Services_{Data} where {Data} is the name of the
container DcmDspData.
USE_DATA_ASYNCH_CLIENT_ The Dcm will access the Data using an R-Port
SERVER_ERROR requiring a asynchronous ClientServertInterface
DataServices_{Data}. The parameter ErrorCode
can be returned to allow the application to trigger
a negative response during the operation. The
R-Port is named DataServices_{Data} where
{Data} is the name of the container DcmDspData.
USE_DATA_ASYNCH_FNC The DCM will access the Data using the
functions that are defined in parameters of type
EcucFunctionNameDef (but without DcmDsp
DataReadDataLengthFnc) in the DcmDspData
container. DCM_E_PENDING return is allowed.
OpStatus is existing as IN parameter.
USE_DATA_ASYNCH_FNC_ The DCM will access the Data using the
ERROR functions that are defined in parameters of type
EcucFunctionNameDef (but without DcmDsp
DataReadDataLengthFnc) in the DcmDspData
container. DCM_E_PENDING return is allowed.
OpStatus is existing as IN parameter. The
parameter ErrorCode can be returned to allow
the application to trigger a negative response
during the operation.
USE_DATA_ASYNCH_FNC_ The DCM will access the Data using the
PROXY functions that are defined in parameters of type
EcucFunctionNameDef (with DataLength and
ErrorCode parameter). DCM_E_PENDING
return is allowed. OpStatus is existing as IN
parameter.
Tags: atp.Status=draft
USE_DATA_SENDER_ The DCM will access the Data using an Port
RECEIVER requiring a SenderReceiverInteface (with is
Service=false) DataServices_{Data}. The Port is
namedDataServices_{Data} where {Data} is the
name of the container DcmDspData.
USE_DATA_SENDER_ The DCM will access the Data using an service
RECEIVER_AS_SERVICE Port requiring a SenderReceiverInteface (with is
Service=true) DataServices_{Data} . The Port is
namedDataServices_{Data} where {Data} is the
name of the container DcmDspData.
USE_DATA_SYNCH_CLIENT_ The DCM will access the Data using an R-Port
SERVER requiring a synchronous ClientServertInterface
DataServices_{Data}. The R-Port is named Data
Services_{Data} where {Data} is the name of the
container DcmDspData.
5

625 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
USE_DATA_SYNCH_FNC The DCM will access the Data using the
functions that are defined in parameters of type
EcucFunctionNameDef (but without DcmDsp
DataReadDataLengthFnc) in the DcmDspData
container. DCM_E_PENDING return value is not
allowed and OpStatus parameter is not existing
in the prototype.
USE_DATA_SYNCH_FNC_ The DCM will access the Data using the
PROXY functions that are defined in parameters of type
EcucFunctionNameDef (with DataLength and
ErrorCode parameter). DCM_E_PENDING
return value is not allowed and OpStatus
parameter is not existing in the prototype.
Tags: atp.Status=draft
USE_ECU_SIGNAL The DCM will access the Data using a direct
access to IoHwAb
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00670] Definition of EcucFunctionNameDef DcmDspDataWriteFnc

d
Parameter Name DcmDspDataWriteFnc
Parent Container DcmDspData
Description Function name to request application to write the data value of a DID. (Write
Data-function). This parameter is related to the interface Xxx_WriteData.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

626 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00988] Definition of EcucAddInfoParamDef DcmDspOdxDataDe-

scription d
Parameter Name DcmDspOdxDataDescription
Parent Container DcmDspData
Description Defines additional description for ODX documentation
Multiplicity 0..1
Type EcucAddInfoParamDef
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00811] Definition of EcucReferenceDef DcmDspDataInfoRef d

Parameter Name DcmDspDataInfoRef
Parent Container DcmDspData
Description Reference to 1 DcmDspDataInfo
Multiplicity 0..1
Type Reference to DcmDspDataInfo
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

627 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Dcm: EcucModuleDef NvMNvramBlockIdentifier: NvMBlockDescriptor:

EcucIntegerParamDef +parameter EcucParamConfContainerDef
upperMultiplicity = 1
lowerMultiplicity = 0 symbolicNameValue = true upperMultiplicity = 65536
min = 2 lowerMultiplicity = 1
max = 65535
DcmDsp: (from Nvm)
(from Nvm)
EcucParamConfContainerDef
DcmDspDataInfo:
+subContainer EcucParamConfContainerDef
lowerMultiplicity = 0
upperMultiplicity = 1
lowerMultiplicity = 0
upperMultiplicity = *

+destination

+subContainer DcmDspDataInfoRef:
EcucReferenceDef DcmDspDataShortTermAdjustmentFnc:
+reference EcucFunctionNameDef
DcmDspData: lowerMultiplicity = 0
EcucParamConfContainerDef upperMultiplicity = 1 lowerMultiplicity = 0
+parameter upperMultiplicity = 1
lowerMultiplicity = 0
upperMultiplicity = *
DcmDspDataReturnControlToEcuFnc:
+parameter EcucFunctionNameDef
DcmDspDataConditionCheckReadFnc:
lowerMultiplicity = 0 EcucFunctionNameDef
upperMultiplicity = 1
lowerMultiplicity = 0
+parameter
upperMultiplicity = 1

DcmDspDataResetToDefaultFnc:
+parameter EcucFunctionNameDef
DcmDspDataWriteFnc:
lowerMultiplicity = 0 EcucFunctionNameDef
upperMultiplicity = 1
lowerMultiplicity = 0
+parameter upperMultiplicity = 1

DcmDspDataByteSize:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1 DcmDspDataReadFnc:
min = 0 EcucFunctionNameDef
max = 65535
+parameter lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDataReadDataLengthFnc:
+parameter EcucFunctionNameDef
DcmDspDataFreezeCurrentStateFnc:
lowerMultiplicity = 0 EcucFunctionNameDef
upperMultiplicity = 1
+parameter lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDataGetScalingInfoFnc:
+parameter EcucFunctionNameDef
DcmDspDataEcuSignal:
lowerMultiplicity = 0 EcucFunctionNameDef
upperMultiplicity = 1
+parameter lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDataConditionCheckReadFncUsed:
+parameter EcucBooleanParamDef DcmDspDataReadEcuSignal:
EcucFunctionNameDef
lowerMultiplicity = 0
upperMultiplicity = 1 lowerMultiplicity = 0
+parameter
upperMultiplicity = 1

DcmDspDidDataSupportInfo: DcmDspDidDataSupportInfoBit:
+subContainer EcucParamConfContainerDef +parameter EcucIntegerParamDef

lowerMultiplicity = 0 min = 0
upperMultiplicity = 1 max = 255
lowerMultiplicity = 1
upperMultiplicity = 1

+reference
DcmDspDidSupportInfo:
DcmDspDidDataSupportInfoRef: EcucParamConfContainerDef
EcucReferenceDef +destination
lowerMultiplicity = 0
lowerMultiplicity = 1 upperMultiplicity = 1
upperMultiplicity = 1

Figure 10.26: DcmDspData1 configuration overview

628 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspData: DcmDspDataUsePort: +literal USE_DATA_SYNCH_CLIENT_SERVER:

EcucParamConfContainerDef EcucEnumerationParamDef EcucEnumerationLiteralDef

lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = * upperMultiplicity = 1 +literal
USE_DATA_ASYNCH_CLIENT_SERVER:
EcucEnumerationLiteralDef

+literal
USE_DATA_SENDER_RECEIVER:
EcucEnumerationLiteralDef

+literal
USE_DATA_SENDER_RECEIVER_AS_SERVICE:
EcucEnumerationLiteralDef

+literal
USE_DATA_SYNCH_FNC:
EcucEnumerationLiteralDef

+literal
USE_DATA_SYNCH_FNC_PROXY:
EcucEnumerationLiteralDef
+parameter
+literal
USE_ECU_SIGNAL: EcucEnumerationLiteralDef

+literal USE_DATA_ASYNCH_FNC:
EcucEnumerationLiteralDef

+literal
USE_DATA_ASYNCH_FNC_ERROR:
EcucEnumerationLiteralDef

+literal USE_DATA_ASYNCH_FNC_PROXY:
EcucEnumerationLiteralDef

+literal USE_DATA_ASYNCH_CLIENT_SERVER_ERROR:
EcucEnumerationLiteralDef

+literal
DcmDspDataType: BOOLEAN:
EcucEnumerationParamDef EcucEnumerationLiteralDef +literal
UINT8:
lowerMultiplicity = 1 EcucEnumerationLiteralDef
upperMultiplicity = 1
+literal
SINT8:
EcucEnumerationLiteralDef +literal
UINT16:
EcucEnumerationLiteralDef
+literal
SINT16:
EcucEnumerationLiteralDef +literal
UINT32:
EcucEnumerationLiteralDef

+literal
SINT32:
EcucEnumerationLiteralDef +literal
+parameter UINT8_N:
EcucEnumerationLiteralDef

+literal
SINT8_N:
EcucEnumerationLiteralDef +literal
UINT16_N:
EcucEnumerationLiteralDef

+literal
SINT16_N:
EcucEnumerationLiteralDef
+literal UINT32_N:
EcucEnumerationLiteralDef

+literal
SINT32_N:
EcucEnumerationLiteralDef
UINT8_DYN:
+literal EcucEnumerationLiteralDef

+literal
FLOAT:
EcucEnumerationLiteralDef
+literal FLOAT_N:
EcucEnumerationLiteralDef

Figure 10.27: DcmDspData2 configuration overview

629 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspDataType: +literal BOOLEAN:

EcucEnumerationParamDef
EcucEnumerationLiteralDef

DcmDspData: lowerMultiplicity = 1
upperMultiplicity = 1 +literal UINT8:
EcucParamConfContainerDef
EcucEnumerationLiteralDef
lowerMultiplicity = 0
+literal SINT8:
upperMultiplicity = *
EcucEnumerationLiteralDef

+literal UINT16:
+parameter EcucEnumerationLiteralDef
+literal SINT16:
EcucEnumerationLiteralDef

+literal UINT32:
EcucEnumerationLiteralDef

+literal SINT32:
EcucEnumerationLiteralDef

DcmDspDataByteSize:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1
min = 0
DcmDspDataEndianness: +literal max = 65535
LITTLE_ENDIAN:
EcucEnumerationParamDef
EcucEnumerationLiteralDef
lowerMultiplicity = 0
+parameter upperMultiplicity = 1 +literal OPAQUE:
EcucEnumerationLiteralDef

+literal
BIG_ENDIAN:
EcucEnumerationLiteralDef DcmDspOdxDataDescription:
EcucAddInfoParamDef
+parameter lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspAlternativeDataInterface: DcmDataElement: EcucForeignReferenceDef

+reference
EcucParamConfContainerDef
+subContainer lowerMultiplicity = 0
lowerMultiplicity = 0 upperMultiplicity = 1
upperMultiplicity = 1 destinationType = VARIABLE-DATA-PROTOTYPE
DcmDspDiagnosisScaling:
EcucChoiceContainerDef +choice +reference

lowerMultiplicity = 0 DcmPortInterfaceMapping: EcucForeignReferenceDef

upperMultiplicity = 1
lowerMultiplicity = 0
upperMultiplicity = 1
destinationType = PORT-INTERFACE-MAPPING
+reference

DcmNestedDataElement: EcucInstanceReferenceDef

lowerMultiplicity = 0
upperMultiplicity = 1
destinationContext = VARIABLE-DATA-PROTOTYPE DATA-PROTOTYPE
destinationType = DATA-PROTOTYPE
DcmDspInternalDataValue:
EcucIntegerParamDef
DcmDspDiagnosticDataElementRef:
EcucForeignReferenceDef lowerMultiplicity = 1
upperMultiplicity = 1
lowerMultiplicity = 1
upperMultiplicity = 1
destinationType = DIAGNOSTIC-DATA-ELEMENT +parameter

+reference
DcmDspAlternativeDataType: DcmDspTextTableMapping:
EcucParamConfContainerDef +subContainer EcucParamConfContainerDef
+choice
lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = *

+choice
+reference
DcmDspAlternativeDiagnosticDataElement: +parameter
EcucParamConfContainerDef DcmApplicationDataType:
EcucForeignReferenceDef DcmDspDiagnosisRepresentationDataValue:
lowerMultiplicity = 0 EcucIntegerParamDef
upperMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 lowerMultiplicity = 1
destinationType = APPLICATION-DATA-TYPE upperMultiplicity = 1

Figure 10.28: DcmDspSRData1 configuration overview

630 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspData: DcmDspExternalSRDataElementClass:
EcucParamConfContainerDef EcucChoiceContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = 1
+subContainer

DcmSubElementInDataElementInstance:
+choice EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+choice +choice

DcmDataElementInstance: DcmSubElementInImplDataElementInstance:
EcucParamConfContainerDef EcucParamConfContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 1

+reference

DcmDataElementInstanceRef: EcucInstanceReferenceDef

lowerMultiplicity = 1
upperMultiplicity = 1
destinationContext = ROOT-SW-COMPOSITION-PROTOTYPE SW-COMPONENT-PROTOTYPE PORT-PROTOTYPE
destinationType = AUTOSAR-DATA-PROTOTYPE

             

       

 !   "   

+reference

DcmSubElementInImplDataElementInstanceRef: EcucInstanceReferenceDef

             

       

 !   "   

+reference

DcmSubElementInDataElementInstanceRef: EcucInstanceReferenceDef

Figure 10.29: DcmDspSRData2 configuration overview

10.2.5.10.2 DcmDspDiagnosisScaling

[ECUC_Dcm_00993] Definition of EcucChoiceContainerDef DcmDspDiagnosis

Scaling d
Choice Container Name DcmDspDiagnosisScaling
Parent Container DcmDspData, DcmDspPidService01
Description This container contains the configuration (parameters) of an alternative Diagnosis
Representation. Out if this the scaling between Diagnosis and ECU internal
representation and vice versa can be calculated.

631 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

No Included Parameters

Container Choices
Container Name Multiplicity Scope / Dependency
DcmDspAlternativeDataInterface 0..1 This container contains the configuration (parameters) of an
alternative Diagnosis Representation by the means of a Variable
DataPrototoype in a DataInterface.
Additionally a reference to PortInterfaceMapping can be defined
which provide already the mapping rules between the Variable
DataPrototoype in a DataInterface used by the software
component (DcmDspExternalSRDataElementClass) and the
intended Diagnosis Representation defined by DcmData
Element.
DcmDspAlternativeDataType 0..1 This container contains the configuration (parameters) of an
alternative Diagnosis Representation by the means of an
ApplicationDataType.
Additionally the definition of a text table mapping can be a
defined for ApplicationDataTypes with a CompuMethod of
category TEXTTABLE and SCALE_LINEAR_AND_TEXTTABLE.
DcmDspAlternativeDiagnosticData 0..1 This container contains the configuration (parameters) of an
Element alternative Diagnosis Representation by the means of Diagnostic
Extract.

10.2.5.10.3 DcmDspArgumentScaling

[ECUC_Dcm_01062] Definition of EcucChoiceContainerDef DcmDspArgument

Scaling d
Choice Container Name DcmDspArgumentScaling
Parent Container DcmDspRequestRoutineResultsInSignal, DcmDspRequestRoutineResultsOutSignal,
DcmDspStartRoutineInSignal, DcmDspStartRoutineOutSignal, DcmDspStopRoutineIn
Signal, DcmDspStopRoutineOutSignal
Description This container contains the configuration (arguments) of an alternative Diagnosis
Representation. Out if this the scaling between Diagnosis and ECU internal
representation and vice versa can be calculated.

No Included Parameters

Container Choices
Container Name Multiplicity Scope / Dependency
DcmDspAlternativeArgumentData 0..1 This container contains the configuration (parameters) of an
alternative Diagnosis Representation by the means of a
ArgumentDataPrototype.
5

632 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Container Choices
Container Name Multiplicity Scope / Dependency
DcmDspAlternativeDataType 0..1 This container contains the configuration (parameters) of an
alternative Diagnosis Representation by the means of an
ApplicationDataType.
Additionally the definition of a text table mapping can be a
defined for ApplicationDataTypes with a CompuMethod of
category TEXTTABLE and SCALE_LINEAR_AND_TEXTTABLE.
DcmDspAlternativeDiagnosticData 0..1 This container contains the configuration (parameters) of an
Element alternative Diagnosis Representation by the means of Diagnostic
Extract.

DcmDspStartRoutineInSignal: DcmDspArgumentScaling:
EcucParamConfContainerDef EcucChoiceContainerDef
+subContainer
upperMultiplicity = * lowerMultiplicity = 0
lowerMultiplicity = 1 upperMultiplicity = 1
requiresIndex = true

DcmDspStartRoutineOutSignal: DcmDspAlternativeArgumentData:
EcucParamConfContainerDef EcucParamConfContainerDef
+choice
+subContainer
upperMultiplicity = * lowerMultiplicity = 0
lowerMultiplicity = 1 upperMultiplicity = 1
requiresIndex = true

DcmDspStopRoutineInSignal: +reference
EcucParamConfContainerDef
+subContainer DcmDataElement: EcucForeignReferenceDef
upperMultiplicity = *
lowerMultiplicity = 1
lowerMultiplicity = 1
upperMultiplicity = 1
requiresIndex = true
destinationType = ARGUMENT-DATA-PROTOTYPE

DcmDspStopRoutineOutSignal:
EcucParamConfContainerDef DcmDspAlternativeDataType:
+subContainer
+choice EcucParamConfContainerDef
upperMultiplicity = *
lowerMultiplicity = 1 lowerMultiplicity = 0
requiresIndex = true upperMultiplicity = 1

DcmDspRequestRoutineResultsInSignal: DcmDspAlternativeDiagnosticDataElement:
EcucParamConfContainerDef EcucParamConfContainerDef
+subContainer +choice
upperMultiplicity = * lowerMultiplicity = 0
lowerMultiplicity = 1 upperMultiplicity = 1
requiresIndex = true

DcmDspRequestRoutineResultsOutSignal:
EcucParamConfContainerDef +reference
+subContainer
upperMultiplicity = * DcmDspDiagnosticDataElementRef:
lowerMultiplicity = 1 EcucForeignReferenceDef
requiresIndex = true
lowerMultiplicity = 1
upperMultiplicity = 1
destinationType = DIAGNOSTIC-DATA-ELEMENT

Figure 10.30: DcmDspArgumentScaling configuration overview

633 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.10.4 DcmDspAlternativeArgumentData

[ECUC_Dcm_01055] Definition of EcucParamConfContainerDef DcmDspAlterna-

tiveArgumentData d
Container Name DcmDspAlternativeArgumentData
Parent Container DcmDspArgumentScaling
Description This container contains the configuration (parameters) of an alternative Diagnosis
Representation by the means of a ArgumentDataPrototype.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDataElement 1 [ECUC_Dcm_01056]

No Included Containers

[ECUC_Dcm_01056] Definition of EcucForeignReferenceDef DcmDataElement d

Parameter Name DcmDataElement
Parent Container DcmDspAlternativeArgumentData
Description Alternative Diagnosis Representation for the data defined by the means of a Argument
DataPrototype.
The CompuMethod of the data type of the referenced ArgumentDataPrototype will be
applied to the data type of the ArgumentDataPrototype in the interface used by the
Dcm.
Multiplicity 1
Type Foreign reference to ARGUMENT-DATA-PROTOTYPE
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency

10.2.5.10.5 DcmDspTextTableMapping

[ECUC_Dcm_00999] Definition of EcucParamConfContainerDef DcmDspTextTa-

bleMapping d

634 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspTextTableMapping

Parent Container DcmDspAlternativeDataType
Description The purpose of the DcmDspTextTableMapping is to associate a texttable value defined
in the context of the Dcm to a texttable value defined in the context of a CompuMethod
referenced by a DataType that shall be taken to create a dataElement in a Sender
ReceiverInterface. By this means it is possible to create a primitive version of a
TexttableMapping (which can only be applied if a dataElement already exists).
In other words, the DcmDspTextTableMapping provides a similar mechanism to the
TexttableMapping in a situation where the TexttableMapping cannot be applied since
the SenderReceiverInterface for the PortPrototype on the Dcm ServiceComponent
does not yet exist.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDiagnosisRepresentationDataValue 1 [ECUC_Dcm_01001]
DcmDspInternalDataValue 1 [ECUC_Dcm_01000]

No Included Containers

[ECUC_Dcm_01001] Definition of EcucIntegerParamDef DcmDspDiagnosisRep-

resentationDataValue d
Parameter Name DcmDspDiagnosisRepresentationDataValue
Parent Container DcmDspTextTableMapping
Description The data value in the diagnosis representation.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 18446744073709551615
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01000] Definition of EcucIntegerParamDef DcmDspInternalData

Value d
Parameter Name DcmDspInternalDataValue
Parent Container DcmDspTextTableMapping
Description The ECU internal data value.
Multiplicity 1
5

635 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type EcucIntegerParamDef
Range 0 .. 18446744073709551615
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.10.6 DcmDspAlternativeDataInterface

[ECUC_Dcm_00994] Definition of EcucParamConfContainerDef DcmDspAlterna-

tiveDataInterface d
Container Name DcmDspAlternativeDataInterface
Parent Container DcmDspDiagnosisScaling
Description This container contains the configuration (parameters) of an alternative Diagnosis
Representation by the means of a VariableDataPrototoype in a DataInterface.
Additionally a reference to PortInterfaceMapping can be defined which provide already
the mapping rules between the VariableDataPrototoype in a DataInterface used by the
software component (DcmDspExternalSRDataElementClass) and the intended
Diagnosis Representation defined by DcmDataElement.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDataElement 0..1 [ECUC_Dcm_00995]
DcmNestedDataElement 0..1 [ECUC_Dcm_01233]
DcmPortInterfaceMapping 0..1 [ECUC_Dcm_00996]

No Included Containers

636 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00995] Definition of EcucForeignReferenceDef DcmDataElement d

Parameter Name DcmDataElement
Parent Container DcmDspAlternativeDataInterface
Description Alternative Diagnosis Representation for the data defined by the means of a Variable
DataPrototoype in a DataInterface.
The CompuMethod of the data type of the referenced VariableDataPrototype will be
applied to the data type of the VariableDataPrototype in the interface used by the Dcm.
Multiplicity 0..1
Type Foreign reference to VARIABLE-DATA-PROTOTYPE
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency

[ECUC_Dcm_01233] Definition of EcucInstanceReferenceDef DcmNestedDataEl-

ement d
Parameter Name DcmNestedDataElement
Parent Container DcmDspAlternativeDataInterface
Description Alternative Diagnosis Representation for the data defined by the means of a Variable
DataPrototoype in a DataInterface.
The CompuMethod of the data type of the referenced VariableDataPrototype will be
applied to the data type of the VariableDataPrototype in the interface used by the Dcm.
Multiplicity 0..1
Type Instance reference to DATA-PROTOTYPE context: VARIABLE-DATA-PROTOTYPE
DATA-PROTOTYPE
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency

637 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00996] Definition of EcucForeignReferenceDef DcmPortInterface

Mapping d
Parameter Name DcmPortInterfaceMapping
Parent Container DcmDspAlternativeDataInterface
Description Optional reference to PortInterfaceMapping which defines the mapping rules.
The PortInterfaceMapping is used to get the DataPrototypeMapping that describes a
conversion between the data prototype referenced by DcmDataElement and the data
prototype referenced from DcmDspExternalSRDataElementClass.
Multiplicity 0..1
Type Foreign reference to PORT-INTERFACE-MAPPING
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency

10.2.5.10.7 DcmDspAlternativeDataType

[ECUC_Dcm_00997] Definition of EcucParamConfContainerDef DcmDspAlterna-

tiveDataType d
Container Name DcmDspAlternativeDataType
Parent Container DcmDspArgumentScaling, DcmDspDiagnosisScaling
Description This container contains the configuration (parameters) of an alternative Diagnosis
Representation by the means of an ApplicationDataType.
Additionally the definition of a text table mapping can be a defined for ApplicationData
Types with a CompuMethod of category TEXTTABLE and SCALE_LINEAR_AND_
TEXTTABLE.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmApplicationDataType 1 [ECUC_Dcm_00998]

638 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspTextTableMapping 0..* The purpose of the DcmDspTextTableMapping is to associate a
texttable value defined in the context of the Dcm to a texttable
value defined in the context of a CompuMethod referenced by a
DataType that shall be taken to create a dataElement in a
SenderReceiverInterface. By this means it is possible to create a
primitive version of a TexttableMapping (which can only be
applied if a dataElement already exists).
In other words, the DcmDspTextTableMapping provides a similar
mechanism to the TexttableMapping in a situation where the
TexttableMapping cannot be applied since the SenderReceiver
Interface for the PortPrototype on the Dcm ServiceComponent
does not yet exist.

[ECUC_Dcm_00998] Definition of EcucForeignReferenceDef DcmApplication

DataType d
Parameter Name DcmApplicationDataType
Parent Container DcmDspAlternativeDataType
Description Alternative Diagnosis Representation for the data defined by the means of a
ApplicationDataType of category VALUE, BOOLEAN or ARRAY.
The CompuMethod that applies to the referenced ApplicationDataType in case of
category VALUE or BOOLEAN will be applied to the data type of the VariableData
Prototype in the interface used by the Dcm.
Multiplicity 1
Type Foreign reference to APPLICATION-DATA-TYPE
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

10.2.5.10.8 DcmDspAlternativeDiagnosticDataElement

[ECUC_Dcm_01084] Definition of EcucParamConfContainerDef DcmDspAlterna-

tiveDiagnosticDataElement d
Container Name DcmDspAlternativeDiagnosticDataElement
Parent Container DcmDspArgumentScaling, DcmDspDiagnosisScaling
Description This container contains the configuration (parameters) of an alternative Diagnosis
Representation by the means of Diagnostic Extract.
Configuration Parameters

639 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDiagnosticDataElementRef 1 [ECUC_Dcm_01085]

No Included Containers

[ECUC_Dcm_01085] Definition of EcucForeignReferenceDef DcmDspDiagnostic

DataElementRef d
Parameter Name DcmDspDiagnosticDataElementRef
Parent Container DcmDspAlternativeDiagnosticDataElement
Description Alternative Diagnosis Representation for the data defined by the means of a Diagnostic
DataElement in the Diagnostic Extract.
This EcucForeignReference enables the access to all SwDataDefProps, in particular
BaseType, CompuMethod and DataConstr
The CompuMethod and DataConstr that applies to the referenced DiagnosticData
Element will be applied to the data type of the VariableDataPrototype in the interface
used by the Dcm. The mapped ImplementationDataType needs to match the given
BaseType.
Multiplicity 1
Type Foreign reference to DIAGNOSTIC-DATA-ELEMENT
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

10.2.5.10.9 DcmDataElementInstance

[ECUC_Dcm_01010] Definition of EcucParamConfContainerDef DcmDataEle-

mentInstance d
Container Name DcmDataElementInstance
Parent Container DcmDspExternalSRDataElementClass, DcmDspPidService01ExternalSRDataElement
Class
Description Instance Reference to the primitive data in a port where the data element is typed with
an ApplicationPrimitveDataType or an ImplementationDataType.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDataElementInstanceRef 1 [ECUC_Dcm_00991]

No Included Containers

640 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00991] Definition of EcucInstanceReferenceDef DcmDataElement

InstanceRef d
Parameter Name DcmDataElementInstanceRef
Parent Container DcmDataElementInstance
Description Instance Reference to the primitive or array data which shall be read or written.
Supported are VariableDataPrototypes in SenderReceiverInterfaces and NvData
Interfaces and ParameterDataPrototypes in ParameterInterfaces (read only). This
reference is applicable if the AutosarDataPrototype is typed with a ApplicationPrimitive
DataType of category VALUE or BOOLEAN or ApplicationArrayDataType or if the
AutosarDataPrototype is typed with a ImplementationDataType of category VALUE,
ARRAY or TYPE_REFERENCE that in turn boils down to VALUE or ARRAY
Multiplicity 1
Type Instance reference to AUTOSAR-DATA-PROTOTYPE context:
ROOT-SW-COMPOSITION-PROTOTYPE SW-COMPONENT-PROTOTYPE
PORT-PROTOTYPE
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency

10.2.5.10.10 DcmDspExternalSRDataElementClass

[ECUC_Dcm_00989] Definition of EcucChoiceContainerDef DcmDspExternalSR-

DataElementClass d
Choice Container Name DcmDspExternalSRDataElementClass
Parent Container DcmDspData
Description This container defines the source of data in a provided port which shall be read
respectively the target of data in a required port which shall be written.
This container shall contain either one DcmSubElementInDataElementInstance OR
DcmDataElementInstance OR DcmSubElementInImplDataElementInstance reference.

No Included Parameters

Container Choices
Container Name Multiplicity Scope / Dependency
DcmDataElementInstance 0..1 Instance Reference to the primitive data in a port where the data
element is typed with an ApplicationPrimitveDataType or an
ImplementationDataType.
DcmSubElementInDataElement 0..1 Instance Reference to the primitve sub-element (at any level) of
Instance composite data in a port where the data element is typed with an
ApplicationCompositeDataType.
5

641 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Container Choices
Container Name Multiplicity Scope / Dependency
DcmSubElementInImplData 0..1 Instance Reference to the primitve sub-element (at any level) of
ElementInstance composite data in a port where the data element is typed with an
ImplementationDataType.

10.2.5.10.11 DcmDspPidService01ExternalSRDataElementClass

[ECUC_Dcm_01080] Definition of EcucChoiceContainerDef DcmDspPidSer-

vice01ExternalSRDataElementClass d
Choice Container Name DcmDspPidService01ExternalSRDataElementClass
Parent Container DcmDspPidService01
Description This container defines the source of data in a provided port which shall be read
respectively the target of data in a required port which shall be written.
This container shall contain either one DcmSubElementInDataElementInstance OR
DcmDataElementInstance OR DcmSubElementInImplDataElementInstance reference.

No Included Parameters

Container Choices
Container Name Multiplicity Scope / Dependency
DcmDataElementInstance 0..1 Instance Reference to the primitive data in a port where the data
element is typed with an ApplicationPrimitveDataType or an
ImplementationDataType.
DcmSubElementInDataElement 0..1 Instance Reference to the primitve sub-element (at any level) of
Instance composite data in a port where the data element is typed with an
ApplicationCompositeDataType.
DcmSubElementInImplData 0..1 Instance Reference to the primitve sub-element (at any level) of
ElementInstance composite data in a port where the data element is typed with an
ImplementationDataType.

10.2.5.10.12 DcmSubElementInDataElementInstance

[ECUC_Dcm_01009] Definition of EcucParamConfContainerDef DcmSubElement

InDataElementInstance d

642 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmSubElementInDataElementInstance

Parent Container DcmDspExternalSRDataElementClass, DcmDspPidService01ExternalSRDataElement
Class
Description Instance Reference to the primitve sub-element (at any level) of composite data in a
port where the data element is typed with an ApplicationCompositeDataType.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmSubElementInDataElementInstanceRef 1 [ECUC_Dcm_00990]

No Included Containers

[ECUC_Dcm_00990] Definition of EcucInstanceReferenceDef DcmSubElementIn

DataElementInstanceRef d
Parameter Name DcmSubElementInDataElementInstanceRef
Parent Container DcmSubElementInDataElementInstance
Description Instance Reference to the primitve sub-element (at any level) of composite data in a
port which shall be read. Supported are VariableDataPrototypes in SenderReceiver
Interfaces and NvDataInterfaces and ParameterDataPrototypes in ParameterInterfaces
(read only). This reference is applicable if the AutosarDataPrototype is typed with a
ApplicationCompositeDataType.
Multiplicity 1
Type Instance reference to APPLICATION-COMPOSITE-ELEMENT-DATA-PROTOTYPE
context: ROOT-SW-COMPOSITION-PROTOTYPE SW-COMPONENT-PROTOTYPE
PORT-PROTOTYPE AUTOSAR-DATA-PROTOTYPE
APPLICATION-COMPOSITE-ELEMENT-DATA-PROTOTYPE*
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency

10.2.5.10.13 DcmSubElementInImplDataElementInstance

[ECUC_Dcm_01011] Definition of EcucParamConfContainerDef DcmSubElement

InImplDataElementInstance d
Container Name DcmSubElementInImplDataElementInstance
Parent Container DcmDspExternalSRDataElementClass, DcmDspPidService01ExternalSRDataElement
Class
5

643 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Description Instance Reference to the primitve sub-element (at any level) of composite data in a
port where the data element is typed with an ImplementationDataType.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmSubElementInImplDataElementInstanceRef 1 [ECUC_Dcm_00992]

No Included Containers

[ECUC_Dcm_00992] Definition of EcucInstanceReferenceDef DcmSubElementIn

ImplDataElementInstanceRef d
Parameter Name DcmSubElementInImplDataElementInstanceRef
Parent Container DcmSubElementInImplDataElementInstance
Description Instance Reference to the primitve sub-element (at any level) of composite data in a
port which shall be read. Supported are VariableDataPrototypes in SenderReceiver
Interfaces and NvDataInterfaces and ParameterDataPrototypes in ParameterInterfaces
(read only). This reference is applicable if the AutosarDataPrototype is typed with a
ImplementationDataType of category STRUCTURE or ARRAY. Please note that in case
of ARRAY the index attribute in the target reference has to be set to select a single
array element.
Multiplicity 1
Type Instance reference to IMPLEMENTATION-DATA-TYPE-ELEMENT context:
ROOT-SW-COMPOSITION-PROTOTYPE SW-COMPONENT-PROTOTYPE
PORT-PROTOTYPE AUTOSAR-DATA-PROTOTYPE
IMPLEMENTATION-DATA-TYPE-ELEMENT*
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency

10.2.5.10.14 DcmDspDidDataSupportInfo

[ECUC_Dcm_01104] Definition of EcucParamConfContainerDef DcmDspDidData

SupportInfo d
Container Name DcmDspDidDataSupportInfo
Parent Container DcmDspData
Description This container defines the supported information.
Configuration Parameters

644 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDidDataSupportInfoBit 1 [ECUC_Dcm_01097]
DcmDspDidDataSupportInfoRef 1 [ECUC_Dcm_01098]

No Included Containers

[ECUC_Dcm_01097] Definition of EcucIntegerParamDef DcmDspDidDataSupport

InfoBit d
Parameter Name DcmDspDidDataSupportInfoBit
Parent Container DcmDspDidDataSupportInfo
Description Referenced Bit of the SupportInfo
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01098] Definition of EcucReferenceDef DcmDspDidDataSupport

InfoRef d
Parameter Name DcmDspDidDataSupportInfoRef
Parent Container DcmDspDidDataSupportInfo
Description Reference to DcmDspDidSupportInfo
Multiplicity 1
Type Reference to DcmDspDidSupportInfo
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

645 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.10.15 DcmDspDataInfo

[ECUC_Dcm_00810] Definition of EcucParamConfContainerDef DcmDspDataInfo

d
Container Name DcmDspDataInfo
Parent Container DcmDsp
Description This container contains the configuration (parameters) of one Data.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDataScalingInfoSize 0..1 [ECUC_Dcm_00611]

No Included Containers

[ECUC_Dcm_00611] Definition of EcucIntegerParamDef DcmDspDataScalingInfo

Size d
Parameter Name DcmDspDataScalingInfoSize
Parent Container DcmDspDataInfo
Description If Scaling information service is available for this Data, it provides the size in bytes of
the scaling information.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

646 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmConfigSet:
EcucParamConfContainerDef

+subContainer

DcmDsp:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspDataInfo: DcmDspDataScalingInfoSize:
EcucParamConfContainerDef EcucIntegerParamDef
+parameter
lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = 1
min = 0
max = 4294967295

Figure 10.31: DcmDspDataInfo configuration overview

10.2.5.11 DcmDspDidControl

[ECUC_Dcm_00619] Definition of EcucParamConfContainerDef DcmDspDidCon-

trol d
Container Name DcmDspDidControl
Parent Container DcmDspDidInfo
Description This container contains the configuration (parameters) of the DID control.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDidControlMask 1 [ECUC_Dcm_01059]
DcmDspDidControlMaskSize 0..1 [ECUC_Dcm_01060]
DcmDspDidFreezeCurrentState 1 [ECUC_Dcm_00624]
DcmDspDidResetToDefault 1 [ECUC_Dcm_00623]
DcmDspDidShortTermAdjustment 1 [ECUC_Dcm_00625]
DcmDspDidControlModeRuleRef 0..1 [ECUC_Dcm_00923]
DcmDspDidControlRoleRef 0..32 [ECUC_Dcm_01143]
DcmDspDidControlSecurityLevelRef 0..* [ECUC_Dcm_00620]
DcmDspDidControlSessionRef 0..* [ECUC_Dcm_00621]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspDidControlEnableMask 0..32 The shortname of the container value defines the symbol of the
controlMask.

647 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01059] Definition of EcucEnumerationParamDef DcmDspDidCon-

trolMask d
Parameter Name DcmDspDidControlMask
Parent Container DcmDspDidControl
Description This indicates the presence of "controlEnableMask" in SWC service interfaces and
defines how the Dcm treats a service request.
Multiplicity 1
Type EcucEnumerationParamDef
Range DCM_CONTROLMASK_ The control enable mask record shall be
EXTERNAL forwarded within each interface and is handled
externally.
DCM_CONTROLMASK_ The control enable mask record is handled
INTERNAL internally and Dcm controls only the included
signals.
DCM_CONTROLMASK_NO No control enable mask handling.
Default value DCM_CONTROLMASK_INTERNAL
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01060] Definition of EcucIntegerParamDef DcmDspDidControl

MaskSize d
Parameter Name DcmDspDidControlMaskSize
Parent Container DcmDspDidControl
Description The value defines the size of the controlEnableMaskRecord in bytes.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 4294967294
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

648 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00624] Definition of EcucBooleanParamDef DcmDspDidFreezeCur-

rentState d
Parameter Name DcmDspDidFreezeCurrentState
Parent Container DcmDspDidControl
Description This indicates the presence of "FreezeCurrentState".
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00623] Definition of EcucBooleanParamDef DcmDspDidResetTo

Default d
Parameter Name DcmDspDidResetToDefault
Parent Container DcmDspDidControl
Description This indicates the presence of "ResetToDefault".
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00625] Definition of EcucBooleanParamDef DcmDspDidShortTerm

Adjustment d
Parameter Name DcmDspDidShortTermAdjustment
Parent Container DcmDspDidControl
Description This indicates the presence of "ShortTermAdjustment".
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
5

649 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Scope / Dependency scope: ECU

[ECUC_Dcm_00923] Definition of EcucReferenceDef DcmDspDidControlMode

RuleRef d
Parameter Name DcmDspDidControlModeRuleRef
Parent Container DcmDspDidControl
Description Reference to DcmModeRule
Mode rule which controls this DID. If there is no reference, no check of the mode rule
shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01143] Definition of EcucReferenceDef DcmDspDidControlRoleRef

d
Parameter Name DcmDspDidControlRoleRef
Parent Container DcmDspDidControl
Description Reference to DcmDspAuthenticationRow that defines a role in that this IO can be be
controlled.
Multiplicity 0..32
Type Reference to DcmDspAuthenticationRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

650 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00620] Definition of EcucReferenceDef DcmDspDidControlSecurity

LevelRef d
Parameter Name DcmDspDidControlSecurityLevelRef
Parent Container DcmDspDidControl
Description Reference to DcmDspSecurityRow Security levels allowed to control this DID. If there is
no reference, no check of security level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00621] Definition of EcucReferenceDef DcmDspDidControlSession

Ref d
Parameter Name DcmDspDidControlSessionRef
Parent Container DcmDspDidControl
Description Reference to DcmDspSessionRow Sessions allowed to control this DID. If there is no
reference, no check of session level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

651 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspDidInfo:
EcucParamConfContainerDef

upperMultiplicity = *
lowerMultiplicity = 0

+subContainer

DcmDspDidControl: DcmDspDidControlSecurityLevelRef: DcmDspSecurityRow:

+reference EcucReferenceDef +destination EcucParamConfContainerDef
EcucParamConfContainerDef

upperMultiplicity = 1 lowerMultiplicity = 0 upperMultiplicity = 31

lowerMultiplicity = 0 upperMultiplicity = * lowerMultiplicity = 0

DcmDspDidControlSessionRef: DcmDspSessionRow:
+reference EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 upperMultiplicity = 31
upperMultiplicity = * lowerMultiplicity = 0

DcmDspDidResetToDefault:
+parameter EcucBooleanParamDef DcmDspAuthenticationRow:
EcucParamConfContainerDef
lowerMultiplicity = 1
upperMultiplicity = 1 lowerMultiplicity = 0
upperMultiplicity = 31

DcmDspDidFreezeCurrentState: +destination
+parameter EcucBooleanParamDef

lowerMultiplicity = 1
DcmDspDidControlRoleRef:
upperMultiplicity = 1
+reference EcucReferenceDef

lowerMultiplicity = 0
upperMultiplicity = 32
+parameter DcmDspDidShortTermAdjustment:
EcucBooleanParamDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspDidControlMaskBitPosition:
DcmDspDidControlEnableMask:
+parameter EcucIntegerParamDef
+subContainer EcucParamConfContainerDef
lowerMultiplicity = 1
upperMultiplicity = 32
upperMultiplicity = 1
lowerMultiplicity = 0
min = 0
max = 31

DcmDspDidControlMask: EcucEnumerationParamDef +literal DCM_CONTROLMASK_INTERNAL:

EcucEnumerationLiteralDef
lowerMultiplicity = 1
upperMultiplicity = 1
defaultValue = DCM_CONTROLMASK_INTERNAL
+parameter +literal DCM_CONTROLMASK_EXTERNAL:
EcucEnumerationLiteralDef

+literal DCM_CONTROLMASK_NO:
EcucEnumerationLiteralDef

DcmDspDidControlMaskSize: EcucIntegerParamDef
+parameter lowerMultiplicity = 0
upperMultiplicity = 1
min = 1
max = 4294967294

Figure 10.32: DcmDspDidControl configuration overview

10.2.5.12 DcmDspDidControlEnableMask

[ECUC_Dcm_01057] Definition of EcucParamConfContainerDef DcmDspDidCon-

trolEnableMask d

652 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspDidControlEnableMask

Parent Container DcmDspDidControl
Description The shortname of the container value defines the symbol of the controlMask.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspDidControlMaskBitPosition 1 [ECUC_Dcm_01058]

No Included Containers

[ECUC_Dcm_01058] Definition of EcucIntegerParamDef DcmDspDidControl

MaskBitPosition d
Parameter Name DcmDspDidControlMaskBitPosition
Parent Container DcmDspDidControlEnableMask
Description Defines the position of the bit in the controlMask starting. The counting order is from
the most significant bit (MSB first) to least significant bit. A value of 0 identifies the most
significant bit in the MSB of the control enable mask. A value of 0 represents also the
first controlState parameter. The bit endianness is identical to the controlMask in UDS.
The number of possible and available bits is given by DcmDspDidControlMaskSize.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 31
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.13 Ecu Reset

10.2.5.13.1 DcmDspEcuReset

[ECUC_Dcm_01111] Definition of EcucParamConfContainerDef DcmDspEcuRe-

set d

653 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspEcuReset

Parent Container DcmDsp
Description This container contains the configuration for DcmDspEcuReset service
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspEcuResetRow 1..* This container contains the configuration for each DcmDspEcu
Reset subservice.

DcmDsp:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspEcuReset:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspEcuResetRow: DcmDspEcuResetId:
EcucParamConfContainerDef EcucIntegerParamDef
+parameter
lowerMultiplicity = 1 min = 0
upperMultiplicity = * max = 127
lowerMultiplicity = 1
upperMultiplicity = 1

DcmResponseToEcuReset: +literal BEFORE_RESET:

EcucEnumerationParamDef EcucEnumerationLiteralDef
+parameter lowerMultiplicity = 1
upperMultiplicity = 1
+literal AFTER_RESET:
EcucEnumerationLiteralDef

Figure 10.33: DcmDspEcuReset configuration overview

10.2.5.13.2 DcmDspEcuResetRow

[ECUC_Dcm_01112] Definition of EcucParamConfContainerDef DcmDspEcuRe-

setRow d

654 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspEcuResetRow

Parent Container DcmDspEcuReset
Description This container contains the configuration for each DcmDspEcuReset subservice.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspEcuResetId 1 [ECUC_Dcm_01113]
DcmResponseToEcuReset 1 [ECUC_Dcm_01039]

No Included Containers

[ECUC_Dcm_01113] Definition of EcucIntegerParamDef DcmDspEcuResetId d

Parameter Name DcmDspEcuResetId
Parent Container DcmDspEcuResetRow
Description Defines the subfunction ID
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 127
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01039] Definition of EcucEnumerationParamDef DcmResponseTo

EcuReset d
Parameter Name DcmResponseToEcuReset
Parent Container DcmDspEcuResetRow
Description Defines the answer to EcuReset service should come: Before or after the reset.
Multiplicity 1
Type EcucEnumerationParamDef
Range AFTER_RESET Answer to EcuReset service should come after
the reset.
5

655 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
BEFORE_RESET Answer to EcuReset service should come before
the reset.
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.14 Memory

10.2.5.14.1 DcmDspMemory

[ECUC_Dcm_00784] Definition of EcucParamConfContainerDef DcmDspMemory

d
Container Name DcmDspMemory
Parent Container DcmDsp
Description This container contains the configuration of the memory access.
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspAddressAndLengthFormat 0..1 This container contains the configuration of the supported
Identifier AddressAndLengthFormatIdentifiers for memory access.
DcmDspMemoryIdInfo 1..* Provides the value of memory identifier used to select the
desired memory device.
This container contains the configuration of the memory access
requested through diagnostic services : ReadMemoryBy
Address, WriteMemoryByAddress, DynamicallyDefineData
Identifier, RequestDownload and RequestUpload.

10.2.5.14.2 DcmDspMemoryTransfer

[ECUC_Dcm_01132] Definition of EcucParamConfContainerDef DcmDspMemory

Transfer d

656 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspMemoryTransfer

Parent Container DcmDsp
Description This container contains the configuration of the memory transfer.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspMemoryTransferUsePort 1 [ECUC_Dcm_01133]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspAddressAndLengthFormat 0..1 This container contains the configuration of the supported
Identifier AddressAndLengthFormatIdentifiers for memory access.
DcmDspMemoryTransferIdInfo 1..* Provides the value of memory identifier used to select the
desired memory device
This container contains the configuration of the memory access
requested through diagnostic services : RequestDownload,
RequestUpload, TransferData, RequestTransferExit

[ECUC_Dcm_01133] Definition of EcucBooleanParamDef DcmDspMemoryTrans-

ferUsePort d
Parameter Name DcmDspMemoryTransferUsePort
Parent Container DcmDspMemoryTransfer
Description If this parameter is set to true, the Dcm uses a port requiring a PortInterface Upload
Download. If the parameter is false, the DCM uses the according C-API callouts.
Multiplicity 1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.14.3 DcmDspAddressAndLengthFormatIdentifier

[ECUC_Dcm_00963] Definition of EcucParamConfContainerDef DcmDspAddress

AndLengthFormatIdentifier d

657 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspAddressAndLengthFormatIdentifier

Parent Container DcmDspMemory, DcmDspMemoryTransfer
Description This container contains the configuration of the supported AddressAndLengthFormat
Identifiers for memory access.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspSupportedAddressAndLengthFormatIdentifier 1..* [ECUC_Dcm_00964]

No Included Containers

[ECUC_Dcm_00964] Definition of EcucIntegerParamDef DcmDspSupportedAd-

dressAndLengthFormatIdentifier d
Parameter Name DcmDspSupportedAddressAndLengthFormatIdentifier
Parent Container DcmDspAddressAndLengthFormatIdentifier
Description This parameter defines the supported AddressAndLengthFormatIdentifier of the
request message.
Multiplicity 1..*
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

658 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspMemory:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspAddressAndLengthFormatIdentifier:
EcucParamConfContainerDef

lowerMultiplicity = 0
DcmDspSupportedAddressAndLengthFormatIdentifier:
upperMultiplicity = 1
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = *
min = 0
max = 255

Figure 10.34: DcmDspMemoryFormatIdentifier configuration overview

10.2.5.14.4 DcmDspMemoryIdInfo

[ECUC_Dcm_00911] Definition of EcucParamConfContainerDef DcmDspMemory

IdInfo d
Container Name DcmDspMemoryIdInfo
Parent Container DcmDspMemory
Description Provides the value of memory identifier used to select the desired memory device.
This container contains the configuration of the memory access requested through
diagnostic services : ReadMemoryByAddress, WriteMemoryByAddress, Dynamically
DefineDataIdentifier, RequestDownload and RequestUpload.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspMemoryIdValue 0..1 [ECUC_Dcm_00913]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspReadMemoryRangeBy 0..* Provides a memory range allowed for reading via labels (lower
LabelInfo and higher address configured as strings).
DcmDspReadMemoryRangeInfo 0..* Provides the range of memory address allowed for reading
DcmDspWriteMemoryRangeBy 0..* Provides a memory range allowed for writing via labels (lower
LabelInfo and higher address configured as strings).
DcmDspWriteMemoryRangeInfo 0..* Provides the range of memory address allowed for writting.

659 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00913] Definition of EcucIntegerParamDef DcmDspMemoryIdValue

d
Parameter Name DcmDspMemoryIdValue
Parent Container DcmDspMemoryIdInfo
Description Value of the memory device identifier used.
Each DcmDspMemoryIdInfo should have a unique ID.
The MemoryIdValue is retrieved from the request messages
(RMBA,WMBA,RD,RU,DDDI) according to ISO-14229-1 with the most significant byte
of the request parameter memoryAddress.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

660 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspMemory:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspMemoryIdInfo:
DcmDspMemoryIdValue: EcucIntegerParamDef
EcucParamConfContainerDef
+parameter lowerMultiplicity = 0
lowerMultiplicity = 1
upperMultiplicity = 1
upperMultiplicity = *
min = 0
max = 255

DcmDspReadMemoryRangeInfo:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *

DcmDspWriteMemoryRangeInfo:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *

DcmDspReadMemoryRangeByLabelInfo:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *

DcmDspWriteMemoryRangeByLabelInfo:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = *

Figure 10.35: DcmDspMemoryIdInfo configuration overview

10.2.5.14.5 DcmDspMemoryTransferIdInfo

[ECUC_Dcm_01137] Definition of EcucParamConfContainerDef DcmDspMemory

TransferIdInfo d
Container Name DcmDspMemoryTransferIdInfo
Parent Container DcmDspMemoryTransfer
Description Provides the value of memory identifier used to select the desired memory device
This container contains the configuration of the memory access requested through
diagnostic services : RequestDownload, RequestUpload, TransferData, Request
TransferExit
Configuration Parameters

661 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspMemoryIdValue 0..1 [ECUC_Dcm_01138]

No Included Containers

[ECUC_Dcm_01138] Definition of EcucIntegerParamDef DcmDspMemoryIdValue

d
Parameter Name DcmDspMemoryIdValue
Parent Container DcmDspMemoryTransferIdInfo
Description Value of the memory device identifier used.
Each DcmDspMemoryIdInfo should have a unique ID.
The MemoryIdValue is retrieved from the request messages
(RMBA,WMBA,RD,RU,DDDI) according to ISO-14229-1 with the most significant byte
of the request parameter memoryAddress.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

10.2.5.14.6 DcmDspReadMemoryRangeByLabelInfo

[ECUC_Dcm_01068] Definition of EcucParamConfContainerDef DcmDspRead

MemoryRangeByLabelInfo d
Container Name DcmDspReadMemoryRangeByLabelInfo
Parent Container DcmDspMemoryIdInfo
Description Provides a memory range allowed for reading via labels (lower and higher address
configured as strings).
Configuration Parameters

662 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspReadMemoryRangeByLabelHigh 1 [ECUC_Dcm_01070]
DcmDspReadMemoryRangeByLabelLow 1 [ECUC_Dcm_01069]
DcmDspReadMemoryRangeModeRuleRef 0..1 [ECUC_Dcm_01072]
DcmDspReadMemoryRangeSecurityLevelRef 0..* [ECUC_Dcm_01071]
DcmDspReadMemoryRangeSessionLevelRef 0..* [ECUC_Dcm_01088]

No Included Containers

[ECUC_Dcm_01070] Definition of EcucStringParamDef DcmDspReadMemory

RangeByLabelHigh d
Parameter Name DcmDspReadMemoryRangeByLabelHigh
Parent Container DcmDspReadMemoryRangeByLabelInfo
Description High memory address as label (string) of a range allowed for reading.
Multiplicity 1
Type EcucStringParamDef
Default value –
Regular Expression [a-zA-Z0-9_]([a-zA-Z0-9\._])*
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01069] Definition of EcucStringParamDef DcmDspReadMemory

RangeByLabelLow d
Parameter Name DcmDspReadMemoryRangeByLabelLow
Parent Container DcmDspReadMemoryRangeByLabelInfo
Description Low memory address as label (string) of a range allowed for reading.
Multiplicity 1
Type EcucStringParamDef
Default value –
Regular Expression [a-zA-Z0-9_]([a-zA-Z0-9\._])*
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

663 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01072] Definition of EcucReferenceDef DcmDspReadMemory

RangeModeRuleRef d
Parameter Name DcmDspReadMemoryRangeModeRuleRef
Parent Container DcmDspReadMemoryRangeByLabelInfo
Description Reference to DcmModeRule
Mode rule which controls read access on this memory address. If there is no reference,
no check of the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01071] Definition of EcucReferenceDef DcmDspReadMemory

RangeSecurityLevelRef d
Parameter Name DcmDspReadMemoryRangeSecurityLevelRef
Parent Container DcmDspReadMemoryRangeByLabelInfo
Description Link to the Security Access Levels needed for read access on this memory address. If
there is no reference, no check of security level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

664 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01088] Definition of EcucReferenceDef DcmDspReadMemory

RangeSessionLevelRef d
Parameter Name DcmDspReadMemoryRangeSessionLevelRef
Parent Container DcmDspReadMemoryRangeByLabelInfo
Description Link to the session level needed for access to this memory address range.
If there is no reference, no check of session level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

10.2.5.14.7 DcmDspReadMemoryRangeInfo

[ECUC_Dcm_00785] Definition of EcucParamConfContainerDef DcmDspRead

MemoryRangeInfo d
Container Name DcmDspReadMemoryRangeInfo
Parent Container DcmDspMemoryIdInfo
Description Provides the range of memory address allowed for reading
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspReadMemoryRangeHigh 1 [ECUC_Dcm_00787]
DcmDspReadMemoryRangeLow 1 [ECUC_Dcm_00786]
DcmDspReadMemoryRangeModeRuleRef 0..1 [ECUC_Dcm_00920]
DcmDspReadMemoryRangeSecurityLevelRef 0..* [ECUC_Dcm_00788]
DcmDspReadMemoryRangeSessionLevelRef 0..* [ECUC_Dcm_01086]

No Included Containers

665 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00787] Definition of EcucIntegerParamDef DcmDspReadMemory

RangeHigh d
Parameter Name DcmDspReadMemoryRangeHigh
Parent Container DcmDspReadMemoryRangeInfo
Description High memory address of a range allowed for reading
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 4294967294
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00786] Definition of EcucIntegerParamDef DcmDspReadMemory

RangeLow d
Parameter Name DcmDspReadMemoryRangeLow
Parent Container DcmDspReadMemoryRangeInfo
Description Low memory address of a range allowed for reading
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 4294967294
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00920] Definition of EcucReferenceDef DcmDspReadMemory

RangeModeRuleRef d
Parameter Name DcmDspReadMemoryRangeModeRuleRef
Parent Container DcmDspReadMemoryRangeInfo
Description Reference to DcmModeRule
Mode rule which controls read access on this memory address. If there is no reference,
no check of the mode rule shall be done.
Multiplicity 0..1
5

666 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00788] Definition of EcucReferenceDef DcmDspReadMemory

RangeSecurityLevelRef d
Parameter Name DcmDspReadMemoryRangeSecurityLevelRef
Parent Container DcmDspReadMemoryRangeInfo
Description Link to the Security Access Levels needed for read access on this memory address. If
there is no reference, no check of security level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01086] Definition of EcucReferenceDef DcmDspReadMemory

RangeSessionLevelRef d
Parameter Name DcmDspReadMemoryRangeSessionLevelRef
Parent Container DcmDspReadMemoryRangeInfo
Description Link to the session level needed for access to this memory address range.
If there is no reference, no check of session level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
5

667 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

10.2.5.14.8 DcmDspWriteMemoryRangeByLabelInfo

[ECUC_Dcm_01073] Definition of EcucParamConfContainerDef DcmDspWrite

MemoryRangeByLabelInfo d
Container Name DcmDspWriteMemoryRangeByLabelInfo
Parent Container DcmDspMemoryIdInfo
Description Provides a memory range allowed for writing via labels (lower and higher address
configured as strings).
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspWriteMemoryRangeByLabelHigh 1 [ECUC_Dcm_01075]
DcmDspWriteMemoryRangeByLabelLow 1 [ECUC_Dcm_01074]
DcmDspWriteMemoryRangeModeRuleRef 0..1 [ECUC_Dcm_01077]
DcmDspWriteMemoryRangeSecurityLevelRef 0..* [ECUC_Dcm_01076]
DcmDspWriteMemoryRangeSessionLevelRef 0..* [ECUC_Dcm_01089]

No Included Containers

[ECUC_Dcm_01075] Definition of EcucStringParamDef DcmDspWriteMemory

RangeByLabelHigh d
Parameter Name DcmDspWriteMemoryRangeByLabelHigh
Parent Container DcmDspWriteMemoryRangeByLabelInfo
Description High memory address as label (string) of a range allowed for writing.
5

668 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity 1
Type EcucStringParamDef
Default value –
Regular Expression [a-zA-Z0-9_]([a-zA-Z0-9\._])*
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01074] Definition of EcucStringParamDef DcmDspWriteMemory

RangeByLabelLow d
Parameter Name DcmDspWriteMemoryRangeByLabelLow
Parent Container DcmDspWriteMemoryRangeByLabelInfo
Description Low memory address as label (string) of a range allowed for writing.
Multiplicity 1
Type EcucStringParamDef
Default value –
Regular Expression [a-zA-Z0-9_]([a-zA-Z0-9\._])*
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01077] Definition of EcucReferenceDef DcmDspWriteMemory

RangeModeRuleRef d
Parameter Name DcmDspWriteMemoryRangeModeRuleRef
Parent Container DcmDspWriteMemoryRangeByLabelInfo
Description Reference to DcmModeRule
Mode rule which controls write access on this memory address. If there is no
reference, no check of the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
5

669 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01076] Definition of EcucReferenceDef DcmDspWriteMemory

RangeSecurityLevelRef d
Parameter Name DcmDspWriteMemoryRangeSecurityLevelRef
Parent Container DcmDspWriteMemoryRangeByLabelInfo
Description Link to the Security Access Levels needed for write access on this memory address. If
there is no reference, no check of security level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01089] Definition of EcucReferenceDef DcmDspWriteMemory

RangeSessionLevelRef d
Parameter Name DcmDspWriteMemoryRangeSessionLevelRef
Parent Container DcmDspWriteMemoryRangeByLabelInfo
Description Link to the session level needed for access to this memory address range.
If there is no reference, no check of session level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
5

670 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

671 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspReadMemoryRangeByLabelLow:
DcmDsp: DcmDspReadMemoryRangeByLabelInfo: EcucStringParamDef
EcucParamConfContainerDef EcucParamConfContainerDef
+parameter lowerMultiplicity = 1
lowerMultiplicity = 0 lowerMultiplicity = 0 upperMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = * regularExpression = [a-zA-Z0-9_]([a-zA-Z0-9\._])*

+subContainer DcmDspReadMemoryRangeByLabelHigh:
EcucStringParamDef
DcmDspMemory: +parameter
lowerMultiplicity = 1
EcucParamConfContainerDef
upperMultiplicity = 1
lowerMultiplicity = 0 regularExpression = [a-zA-Z0-9_]([a-zA-Z0-9\._])*
upperMultiplicity = 1

+subContainer DcmDspReadMemoryRangeSecurityLevelRef:
EcucReferenceDef
DcmDspMemoryIdInfo: +reference
lowerMultiplicity = 0
EcucParamConfContainerDef
upperMultiplicity = *
lowerMultiplicity = 1
upperMultiplicity = * +subContainer

+reference DcmDspReadMemoryRangeModeRuleRef:
EcucReferenceDef

lowerMultiplicity = 0
upperMultiplicity = 1
+reference

DcmDspReadMemoryRangeSessionLevelRef:
EcucReferenceDef
DcmModeRule: +destination
lowerMultiplicity = 0
upperMultiplicity = * EcucParamConfContainerDef

lowerMultiplicity = 1
upperMultiplicity = *

+destination +destination
+destination
DcmDspSessionRow:
EcucParamConfContainerDef +destination DcmDspSecurityRow:
EcucParamConfContainerDef
upperMultiplicity = 31
lowerMultiplicity = 0 upperMultiplicity = 31
lowerMultiplicity = 0

+destination

DcmDspWriteMemoryRangeByLabelInfo: DcmDspWriteMemoryRangeSessionLevelRef:
EcucParamConfContainerDef EcucReferenceDef
+reference lowerMultiplicity = 0
lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = *

+subContainer
DcmDspWriteMemoryRangeModeRuleRef:
EcucReferenceDef
+reference
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspWriteMemoryRangeSecurityLevelRef:
EcucReferenceDef
+reference
lowerMultiplicity = 0
upperMultiplicity = *

+parameter
DcmDspWriteMemoryRangeByLabelHigh:
DcmDspWriteMemoryRangeByLabelLow: +parameter EcucStringParamDef
EcucStringParamDef
lowerMultiplicity = 1
lowerMultiplicity = 1 upperMultiplicity = 1
upperMultiplicity = 1 regularExpression = [a-zA-Z0-9_]([a-zA-Z0-9\._])*
regularExpression = [a-zA-Z0-9_]([a-zA-Z0-9\._])*

Figure 10.36: DcmDspMemoryReadWriteByLabel configuration overview

672 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.14.9 DcmDspWriteMemoryRangeInfo

[ECUC_Dcm_00789] Definition of EcucParamConfContainerDef DcmDspWrite

MemoryRangeInfo d
Container Name DcmDspWriteMemoryRangeInfo
Parent Container DcmDspMemoryIdInfo
Description Provides the range of memory address allowed for writting.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspWriteMemoryRangeHigh 1 [ECUC_Dcm_00791]
DcmDspWriteMemoryRangeLow 1 [ECUC_Dcm_00790]
DcmDspWriteMemoryRangeModeRuleRef 0..1 [ECUC_Dcm_00916]
DcmDspWriteMemoryRangeSecurityLevelRef 0..* [ECUC_Dcm_00793]
DcmDspWriteMemoryRangeSessionLevelRef 0..* [ECUC_Dcm_01087]

No Included Containers

[ECUC_Dcm_00791] Definition of EcucIntegerParamDef DcmDspWriteMemory

RangeHigh d
Parameter Name DcmDspWriteMemoryRangeHigh
Parent Container DcmDspWriteMemoryRangeInfo
Description High memory address of a range allowed for writing.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 4294967294
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

673 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00790] Definition of EcucIntegerParamDef DcmDspWriteMemory

RangeLow d
Parameter Name DcmDspWriteMemoryRangeLow
Parent Container DcmDspWriteMemoryRangeInfo
Description Low memory address of a range allowed for writing
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 4294967294
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00916] Definition of EcucReferenceDef DcmDspWriteMemory

RangeModeRuleRef d
Parameter Name DcmDspWriteMemoryRangeModeRuleRef
Parent Container DcmDspWriteMemoryRangeInfo
Description Reference to DcmModeRule
Mode rule which controls write access on this memory address. If there is no
reference, no check of the mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

674 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00793] Definition of EcucReferenceDef DcmDspWriteMemory

RangeSecurityLevelRef d
Parameter Name DcmDspWriteMemoryRangeSecurityLevelRef
Parent Container DcmDspWriteMemoryRangeInfo
Description Link to the Security Access Levels needed for write access on this memory address. If
there is no reference, no check of security level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSecurityRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01087] Definition of EcucReferenceDef DcmDspWriteMemory

RangeSessionLevelRef d
Parameter Name DcmDspWriteMemoryRangeSessionLevelRef
Parent Container DcmDspWriteMemoryRangeInfo
Description Link to the session level needed for access to this memory address range.
If there is no reference, no check of session level shall be done.
Multiplicity 0..*
Type Reference to DcmDspSessionRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

675 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspMemory:
EcucParamConfContainerDef DcmDsp: DcmDspReadMemoryRangeLow:
+subContainer EcucParamConfContainerDef EcucIntegerParamDef
lowerMultiplicity = 0
upperMultiplicity = 1 lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 +parameter upperMultiplicity = 1
min = 0
max = 4294967294

+subContainer

DcmDspMemoryIdInfo: DcmDspReadMemoryRangeHigh:
DcmDspReadMemoryRangeInfo: EcucIntegerParamDef
EcucParamConfContainerDef
EcucParamConfContainerDef
lowerMultiplicity = 1 lowerMultiplicity = 1
lowerMultiplicity = 0 +parameter upperMultiplicity = 1
upperMultiplicity = *
upperMultiplicity = * min = 0
max = 4294967294

+subContainer

DcmDspReadMemoryRangeSessionLevelRef:
+reference EcucReferenceDef

lowerMultiplicity = 0
upperMultiplicity = *

+reference
DcmDspReadMemoryRangeSecurityLevelRef:
EcucReferenceDef
+reference
lowerMultiplicity = 0
DcmDspReadMemoryRangeModeRuleRef: upperMultiplicity = *
EcucReferenceDef

lowerMultiplicity = 0
upperMultiplicity = 1

+destination
+destination

DcmDspSessionRow:
EcucParamConfContainerDef
DcmModeRule:
EcucParamConfContainerDef upperMultiplicity = 31
lowerMultiplicity = 0
lowerMultiplicity = 1 +destination
upperMultiplicity = *
+destination

+subContainer +destination
DcmDspWriteMemoryRangeInfo:
EcucParamConfContainerDef
DcmDspSecurityRow:
lowerMultiplicity = 0 EcucParamConfContainerDef
upperMultiplicity = * +destination
upperMultiplicity = 31
lowerMultiplicity = 0

DcmDspWriteMemoryRangeHigh:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 4294967294
DcmDspWriteMemoryRangeModeRuleRef:
+reference EcucReferenceDef

lowerMultiplicity = 0
DcmDspWriteMemoryRangeLow: upperMultiplicity = 1
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1 DcmDspWriteMemoryRangeSecurityLevelRef:
min = 0 EcucReferenceDef
max = 4294967294 +reference
lowerMultiplicity = 0
upperMultiplicity = *

DcmDspWriteMemoryRangeSessionLevelRef:
EcucReferenceDef
+reference
lowerMultiplicity = 0
upperMultiplicity = *

Figure 10.37: DcmDspMemoryReadWrite configuration overview

676 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.15 PIDs

10.2.5.15.1 DcmDspPid

[ECUC_Dcm_00626] Definition of EcucParamConfContainerDef DcmDspPid d

Container Name DcmDspPid
Parent Container DcmDsp
Description This container defines the availability of a PID to the DCM.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspPidIdentifier 1 [ECUC_Dcm_00627]
DcmDspPidService 1 [ECUC_Dcm_00893]
DcmDspPidSize 1 [ECUC_Dcm_00870]
DcmDspPidUsed 1 [ECUC_Dcm_00806]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspPidData 1..* This container defines the parameter for a Signal in the PID.
DcmDspPidSupportInfo 0..* This container defines the support information (typically byte A)
to declare the usability of the data bytes within the so-called
packeted PIDs (e.g. PID$68).

[ECUC_Dcm_00627] Definition of EcucIntegerParamDef DcmDspPidIdentifier d

Parameter Name DcmDspPidIdentifier
Parent Container DcmDspPid
Description 1 byte Identifier of the PID
Within each DcmConfigSet all DcmDspPidIdentifier values shall be unique.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

677 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00893] Definition of EcucEnumerationParamDef DcmDspPidSer-

vice d
Parameter Name DcmDspPidService
Parent Container DcmDspPid
Description Indicates if a PID is used with service $01 and/or $02
Multiplicity 1
Type EcucEnumerationParamDef
Range DCM_SERVICE_01 A PID is used with service $01 only.
DCM_SERVICE_01_02 A PID is used with service $01 and $02. Allowed
with a PID configuration containing data
elements on byte basis.
DCM_SERVICE_02 A PID is used with service $02 only. Allowed with
a PID configuration containing data elements on
byte basis.
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00870] Definition of EcucIntegerParamDef DcmDspPidSize d

Parameter Name DcmDspPidSize
Parent Container DcmDspPid
Description Length of a PID in byte(s).
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00806] Definition of EcucBooleanParamDef DcmDspPidUsed d

Parameter Name DcmDspPidUsed
Parent Container DcmDspPid
Description Allow to activate or deactivate the usage of a PID, for multi purpose ECUs
true = PID is available false = PID is not available
5

678 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value true
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

679 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1 DcmDspPidUsed: EcucBooleanParamDef

upperMultiplicity = 1
+subContainer +parameter lowerMultiplicity = 1

DcmDspPid:
EcucParamConfContainerDef

upperMultiplicity = * DcmDspPidSize: EcucIntegerParamDef

lowerMultiplicity = 0 +parameter lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 255 DcmDspPidIdentifier: EcucIntegerParamDef

lowerMultiplicity = 1
upperMultiplicity = 1
+parameter min = 0
max = 255

DcmDspPidSupportInfo: DcmDspPidSupportInfoPos:
EcucParamConfContainerDef EcucIntegerParamDef
+parameter
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = * upperMultiplicity = 1
min = 0
max = 255
+subContainer

DcmDspPidSupportInfoLen:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 255
+destination

DcmDspPidDataSupportInfoRef:
EcucReferenceDef
+reference DcmDspPidDataSupportInfo:
lowerMultiplicity = 1 EcucParamConfContainerDef
upperMultiplicity = 1
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPidDataSupportInfoBit:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 255

DcmDspPidService: +literal DCM_SERVICE_01:

EcucEnumerationParamDef EcucEnumerationLiteralDef

+parameter +literal DCM_SERVICE_02:

EcucEnumerationLiteralDef

+literal DCM_SERVICE_01_02:
EcucEnumerationLiteralDef

Figure 10.38: DcmDspPid1 configuration overview

680 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspPid: DcmDspPidDataSupportInfo:
EcucParamConfContainerDef EcucParamConfContainerDef

upperMultiplicity = * lowerMultiplicity = 0
lowerMultiplicity = 0 upperMultiplicity = 1

+subContainer

+subContainer
DcmDspPidDataDemRef:
DcmDspPidData: DcmDspPidService02: EcucReferenceDef
EcucParamConfContainerDef +subContainer EcucParamConfContainerDef +reference
lowerMultiplicity = 0
lowerMultiplicity = 1 lowerMultiplicity = 0 upperMultiplicity = 1
upperMultiplicity = * upperMultiplicity = 1

+destination

DcmDspPidByteOffset: DemPidDataElement:
EcucIntegerParamDef EcucParamConfContainerDef
+parameter
min = 0 upperMultiplicity = 255
max = 255 lowerMultiplicity = 1
lowerMultiplicity = 1
upperMultiplicity = 1 (from Dem)

+parameter DcmDspPidDataByteSize:
EcucIntegerParamDef

min = 0
max = 255
lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspPidService01: DcmDspPidService01ExternalSRDataElementClass:
EcucParamConfContainerDef +subContainer EcucChoiceContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 1

DcmDspDiagnosisScaling:
EcucChoiceContainerDef
+subContainer
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPidDataReadFnc: EcucFunctionNameDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPidDataUsePort: +literal USE_DATA_SENDER_RECEIVER_AS_SERVICE:

EcucEnumerationParamDef EcucEnumerationLiteralDef

lowerMultiplicity = 1
upperMultiplicity = 1
+literal USE_DATA_SYNCH_CLIENT_SERVER:
EcucEnumerationLiteralDef

+parameter

+literal USE_DATA_SENDER_RECEIVER:
EcucEnumerationLiteralDef

+literal USE_DATA_SYNCH_FNC:
EcucEnumerationLiteralDef

Figure 10.39: DcmDspPid2 configuration overview

681 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspPidService01: DcmDspPidDataEndianness: +literal LITTLE_ENDIAN:

EcucParamConfContainerDef EcucEnumerationParamDef EcucEnumerationLiteralDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 +parameter upperMultiplicity = 1
+literal OPAQUE: EcucEnumerationLiteralDef

+literal BIG_ENDIAN:
EcucEnumerationLiteralDef

+parameter

DcmDspPidDataType: +literal BOOLEAN:

EcucEnumerationParamDef EcucEnumerationLiteralDef

lowerMultiplicity = 1 +literal UINT8:

upperMultiplicity = 1 EcucEnumerationLiteralDef

+literal SINT8:
EcucEnumerationLiteralDef

+literal UINT16:
EcucEnumerationLiteralDef

+literal SINT16:
EcucEnumerationLiteralDef

+literal UINT32:
EcucEnumerationLiteralDef

+literal SINT32:
EcucEnumerationLiteralDef

+literal UINT8_N:
EcucEnumerationLiteralDef

+literal SINT8_N:
EcucEnumerationLiteralDef

+literal UINT16_N:
EcucEnumerationLiteralDef

+literal SINT16_N:
EcucEnumerationLiteralDef

+literal UINT32_N:
EcucEnumerationLiteralDef

+literal SINT32_N:
EcucEnumerationLiteralDef

Figure 10.40: DcmDspPid3 configuration overview

10.2.5.15.2 DcmDspPidSupportInfo

[ECUC_Dcm_00871] Definition of EcucParamConfContainerDef DcmDspPidSup-

portInfo d
Container Name DcmDspPidSupportInfo
Parent Container DcmDspPid
Description This container defines the support information (typically byte A) to declare the usability
of the data bytes within the so-called packeted PIDs (e.g. PID$68).
Configuration Parameters

682 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspPidSupportInfoLen 1 [ECUC_Dcm_00873]
DcmDspPidSupportInfoPos 1 [ECUC_Dcm_00872]

No Included Containers

[ECUC_Dcm_00873] Definition of EcucIntegerParamDef DcmDspPidSupportInfo

Len d
Parameter Name DcmDspPidSupportInfoLen
Parent Container DcmDspPidSupportInfo
Description Length of the support information in bytes.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00872] Definition of EcucIntegerParamDef DcmDspPidSupportInfo

Pos d
Parameter Name DcmDspPidSupportInfoPos
Parent Container DcmDspPidSupportInfo
Description Position of the support information in bytes.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

683 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.15.3 DcmDspPidData

[ECUC_Dcm_00865] Definition of EcucParamConfContainerDef DcmDspPidData

d
Container Name DcmDspPidData
Parent Container DcmDspPid
Description This container defines the parameter for a Signal in the PID.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspPidByteOffset 1 [ECUC_Dcm_01107]
DcmDspPidDataByteSize 0..1 [ECUC_Dcm_01108]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspPidDataSupportInfo 0..1 This container defines the supported information.
DcmDspPidService01 0..1 Contains specific configuration parameter of PID for service $01.
This container exists only if DcmDspPidService is set to DCM_
SERVICE_01 or DCM_SERVICE_01_02.
DcmDspPidService02 0..1 Contains specific configuration parameter of PID for service $02.
This container exists only if DcmDspPidService is set to DCM_
SERVICE_02 or DCM_SERVICE_01_02.

[ECUC_Dcm_01107] Definition of EcucIntegerParamDef DcmDspPidByteOffset d

Parameter Name DcmDspPidByteOffset
Parent Container DcmDspPidData
Description This is the position in bytes of the PID structure and will not start at position 0 in case a
support information is available (for packeted PIDs).
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

684 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01108] Definition of EcucIntegerParamDef DcmDspPidDataByte

Size d
Parameter Name DcmDspPidDataByteSize
Parent Container DcmDspPidData
Description Defines the array length in bytes or the maximum array length for variable datalengths.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

10.2.5.15.4 DcmDspPidService01

[ECUC_Dcm_00894] Definition of EcucParamConfContainerDef DcmDspPidSer-

vice01 d
Container Name DcmDspPidService01
Parent Container DcmDspPidData
Description Contains specific configuration parameter of PID for service $01. This container exists
only if DcmDspPidService is set to DCM_SERVICE_01 or DCM_SERVICE_01_02.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspPidDataEndianness 0..1 [ECUC_Dcm_01012]
DcmDspPidDataReadFnc 0..1 [ECUC_Dcm_00629]
DcmDspPidDataType 1 [ECUC_Dcm_01018]
DcmDspPidDataUsePort 1 [ECUC_Dcm_00720]

685 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspDiagnosisScaling 0..1 This container contains the configuration (parameters) of an
alternative Diagnosis Representation. Out if this the scaling
between Diagnosis and ECU internal representation and vice
versa can be calculated.
DcmDspPidService01ExternalSR 0..1 This container defines the source of data in a provided port
DataElementClass which shall be read respectively the target of data in a required
port which shall be written.
This container shall contain either one DcmSubElementInData
ElementInstance OR DcmDataElementInstance OR DcmSub
ElementInImplDataElementInstance reference.

[ECUC_Dcm_01012] Definition of EcucEnumerationParamDef DcmDspPidData

Endianness d
Parameter Name DcmDspPidDataEndianness
Parent Container DcmDspPidService01
Description Defines the endianness of the data belonging to a PID in a diagnostic response
message.
If no DcmDspPidDataEndianness is defined the value of DcmDspDataDefault
Endianness is applicable.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at the lowest
address.
LITTLE_ENDIAN Most significant byte shall be stored at the
highest address
OPAQUE Opaque data endianness
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

686 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00629] Definition of EcucFunctionNameDef DcmDspPidDataRead

Fnc d
Parameter Name DcmDspPidDataReadFnc
Parent Container DcmDspPidService01
Description Function name for reading PID data value. This is only relevant if DcmDspPidDataUse
Port==USE_DATA_SYNCH_FNC.
This parameter is related to the interface Xxx_ReadData.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01018] Definition of EcucEnumerationParamDef DcmDspPidData

Type d
Parameter Name DcmDspPidDataType
Parent Container DcmDspPidService01
Description Provide the implementation data type of data belonging to a PID.
Multiplicity 1
Type EcucEnumerationParamDef
BOOLEAN Type of the data is boolean.
Range
SINT16 Type of the data is sint16.
SINT16_N Type of the data is sint16 array.
SINT32 Type of the data is sint32.
SINT32_N Type of the data is sint32 array.
SINT8 Type of the data is sint8.
SINT8_N Type of the data is sint8 array.
UINT16 Type of the data is uint16.
UINT16_N Type of the data is uint16 array.
UINT32 Type of the data is uint32.
UINT32_N Type of the data is uint32 array.
UINT8 Type of the data is uint8.
UINT8_N Type of the data is uint8 array.
Post-Build Variant Multiplicity false
5

687 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00720] Definition of EcucEnumerationParamDef DcmDspPidData

UsePort d
Parameter Name DcmDspPidDataUsePort
Parent Container DcmDspPidService01
Description If this parameter is set to USE_DATA_SYNCH_FNC, the Dcm will use the function
defined in DcmDspPidDataReadFnc to get the PID data value.
If this parameter is set to USE_DATA_SYNCH_CLIENT_SERVER, the Dcm will have
an R-Port requiring the interface DataServices_{Data}.
If this parameter is set to USE_DATA_SENDER_RECEIVER or USE_DATA_SENDER_
RECEIVER_AS_SERVICE, the DCM will have an R-Port requiring a SenderReceiver
Interface.
The R-Port is named DataServices_{Data} where {Data} is the name of the container
DcmDspPidData.
Multiplicity 1
Type EcucEnumerationParamDef
Range USE_DATA_SENDER_ –
RECEIVER
USE_DATA_SENDER_ –
RECEIVER_AS_SERVICE
USE_DATA_SYNCH_CLIENT_ –
SERVER
USE_DATA_SYNCH_FNC –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.15.5 DcmDspPidService02

[ECUC_Dcm_00895] Definition of EcucParamConfContainerDef DcmDspPidSer-

vice02 d

688 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspPidService02

Parent Container DcmDspPidData
Description Contains specific configuration parameter of PID for service $02. This container exists
only if DcmDspPidService is set to DCM_SERVICE_02 or DCM_SERVICE_01_02.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspPidDataDemRef 0..1 [ECUC_Dcm_00887]

No Included Containers

[ECUC_Dcm_00887] Definition of EcucReferenceDef DcmDspPidDataDemRef d

Parameter Name DcmDspPidDataDemRef
Parent Container DcmDspPidService02
Description Reference to DemPidDataElement in DEM configuration. Allows to link the DCM PID
and DEM PID configuration for Mode $02.
Multiplicity 0..1
Type Reference to DemPidDataElement
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

10.2.5.15.6 DcmDspPidDataSupportInfo

[ECUC_Dcm_00874] Definition of EcucParamConfContainerDef DcmDspPidData

SupportInfo d
Container Name DcmDspPidDataSupportInfo
Parent Container DcmDspPidData
Description This container defines the supported information.
Configuration Parameters

689 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspPidDataSupportInfoBit 1 [ECUC_Dcm_00876]
DcmDspPidDataSupportInfoRef 1 [ECUC_Dcm_00875]

No Included Containers

[ECUC_Dcm_00876] Definition of EcucIntegerParamDef DcmDspPidDataSupport

InfoBit d
Parameter Name DcmDspPidDataSupportInfoBit
Parent Container DcmDspPidDataSupportInfo
Description Referenced Bit of the SupportInfo
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00875] Definition of EcucReferenceDef DcmDspPidDataSupport

InfoRef d
Parameter Name DcmDspPidDataSupportInfoRef
Parent Container DcmDspPidDataSupportInfo
Description Reference to DcmDspPidSupportInfo
Multiplicity 1
Type Reference to DcmDspPidSupportInfo
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

690 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.16 DcmDspRequestControl

[ECUC_Dcm_00637] Definition of EcucParamConfContainerDef DcmDspRequest

Control d
Container Name DcmDspRequestControl
Parent Container DcmDsp
Description This container contains the configuration (parameters) of the "Request control of
on-board system, test or component" service (Service $08). The DCM will request the
control using an R-Port requiring a PortInteface RequestControlServices_{Tid}. The
R-Port is named RequestControlServices_{Tid} where {Tid} is the name of the
container DcmDspRequestControl.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspRequestControlInBufferSize 1 [ECUC_Dcm_00722]
DcmDspRequestControlInfoByte 0..1 [ECUC_Dcm_01078]
DcmDspRequestControlOutBufferSize 1 [ECUC_Dcm_00723]
DcmDspRequestControlTestId 1 [ECUC_Dcm_00656]

No Included Containers

[ECUC_Dcm_00722] Definition of EcucIntegerParamDef DcmDspRequestControl

InBufferSize d
Parameter Name DcmDspRequestControlInBufferSize
Parent Container DcmDspRequestControl
Description Number of bytes to be provided in the input buffer of the interface RequestControl
Services_{Tid} for OBD Service $08
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

691 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01078] Definition of EcucIntegerParamDef DcmDspRequestControl

InfoByte d
Parameter Name DcmDspRequestControlInfoByte
Parent Container DcmDspRequestControl
Description Manufacturer specific value reported to the tester for the record identifiers 0xE000 to
OxE1FF. (WWH-OBD use cases)
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00723] Definition of EcucIntegerParamDef DcmDspRequestControl

OutBufferSize d
Parameter Name DcmDspRequestControlOutBufferSize
Parent Container DcmDspRequestControl
Description Number of bytes to be provided in the output buffer of the interface RequestControl
Services_{Tid} for OBD Service $08
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00656] Definition of EcucIntegerParamDef DcmDspRequestControl

TestId d
Parameter Name DcmDspRequestControlTestId
Parent Container DcmDspRequestControl
Description Test Id for Service $08
Multiplicity 1
5

692 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

DcmDsp:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspRequestControl: DcmDspRequestControlTestId:
EcucParamConfContainerDef EcucIntegerParamDef

upperMultiplicity = * +parameter lowerMultiplicity = 1

lowerMultiplicity = 0 upperMultiplicity = 1
min = 0
max = 255

DcmDspRequestControlInBufferSize:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 255

DcmDspRequestControlOutBufferSize:
EcucIntegerParamDef
+parameter
upperMultiplicity = 1
lowerMultiplicity = 1
min = 0
max = 255

DcmDspRequestControlInfoByte:
EcucIntegerParamDef
+parameter lowerMultiplicity = 0
upperMultiplicity = 1
min = 0
max = 255

Figure 10.41: DcmDspRequestControl configuration overview

10.2.5.17 DcmDspRequestFileTransfer

[ECUC_Dcm_01034] Definition of EcucParamConfContainerDef DcmDspRequest

FileTransfer d

693 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspRequestFileTransfer

Parent Container DcmDsp
Description This container contains the configuration for RequestFileTransfer. This container only
exists if RequestFileTransfer is configured.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmRequestFileTransferFileSizeOrDirInfoParameter 1 [ECUC_Dcm_01035]
Length
DcmRequestFileTransferLengthFormatIdentifier 1 [ECUC_Dcm_01036]
DcmRequestFileTransferMaxFileAndDirName 0..1 [ECUC_Dcm_01130]
DcmRequestFileTransferUsePort 1 [ECUC_Dcm_01131]

No Included Containers

[ECUC_Dcm_01035] Definition of EcucIntegerParamDef DcmRequestFileTrans-

ferFileSizeOrDirInfoParameterLength d
Parameter Name DcmRequestFileTransferFileSizeOrDirInfoParameterLength
Parent Container DcmDspRequestFileTransfer
Description Defines the length (number of bytes, i.e. the value of fileSizeOrDirInfoParameter
Length) of the fileSizeUncompressedOrDirInfoLength and fileSizeCompressed in the
response of RequestFileTransfer.
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 4
Default value 4
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01036] Definition of EcucIntegerParamDef DcmRequestFileTrans-

ferLengthFormatIdentifier d
Parameter Name DcmRequestFileTransferLengthFormatIdentifier
Parent Container DcmDspRequestFileTransfer
Description Defines the length (number of bytes) of the maxNumberOfBlockLength parameter in
the response of RequestFileTransfer.
Multiplicity 1
5

694 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type EcucIntegerParamDef
Range 1 .. 4
Default value 4
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01130] Definition of EcucIntegerParamDef DcmRequestFileTrans-

ferMaxFileAndDirName d
Parameter Name DcmRequestFileTransferMaxFileAndDirName
Parent Container DcmDspRequestFileTransfer
Description Defines the maximum size allowed for the FileAndDirName parameter with RTE
interfaces used for RequestFileTransfer.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 65535
Default value 1
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01131] Definition of EcucBooleanParamDef DcmRequestFileTrans-

ferUsePort d
Parameter Name DcmRequestFileTransferUsePort
Parent Container DcmDspRequestFileTransfer
Description Defines if a C/S or C function call shall be used for RequestFileTransfer processing.
Multiplicity 1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

695 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspRequestFileTransfer: DcmRequestFileTransferFileSizeOrDirInfoParameterLength:
EcucParamConfContainerDef EcucIntegerParamDef
+parameter min = 1
lowerMultiplicity = 0
upperMultiplicity = 1 max = 4
defaultValue = 4
lowerMultiplicity = 1
upperMultiplicity = 1

DcmRequestFileTransferLengthFormatIdentifier:
EcucIntegerParamDef
+parameter min = 1
max = 4
defaultValue = 4
lowerMultiplicity = 1
upperMultiplicity = 1

DcmRequestFileTransferMaxFileAndDirName:
EcucIntegerParamDef
+parameter min = 1
max = 65535
defaultValue = 1
lowerMultiplicity = 0
upperMultiplicity = 1

DcmRequestFileTransferUsePort:
+parameter EcucBooleanParamDef

defaultValue = false
lowerMultiplicity = 1
upperMultiplicity = 1

Figure 10.42: DcmDspRequestFileTransfer configuration overview

10.2.5.18 Response on Event

10.2.5.18.1 DcmDspRoe

[ECUC_Dcm_00858] Definition of EcucParamConfContainerDef DcmDspRoe d

Container Name DcmDspRoe
Parent Container DcmDsp
Description Provide the configuration of the ResponseOnEvent mechanism.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspRoeMaxNumChangeOfDataIdentfierEvents 0..1 [ECUC_Dcm_01236]
DcmDspRoeMaxNumComparisonOfValueEvents 0..1 [ECUC_Dcm_01237]
DcmDspRoeMaxNumOfStoredDTCStatusChangedEvents 0..1 [ECUC_Dcm_01239]
DcmDspRoeMaxSupportedDIDLength 0..1 [ECUC_Dcm_01238]
DcmDspRoeSchedulerRate 1 [ECUC_Dcm_01235]
DcmDspRoeStoreEventSupport 1 [ECUC_Dcm_01234]

696 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

No Included Containers

[ECUC_Dcm_01236] Definition of EcucIntegerParamDef DcmDspRoeMaxNum

ChangeOfDataIdentfierEvents d
Parameter Name DcmDspRoeMaxNumChangeOfDataIdentfierEvents
Parent Container DcmDspRoe
Description Maximum number of events that can be simultaneously configured with SubFunction
onChangeOfDataIdentifier.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01237] Definition of EcucIntegerParamDef DcmDspRoeMaxNum

ComparisonOfValueEvents d
Parameter Name DcmDspRoeMaxNumComparisonOfValueEvents
Parent Container DcmDspRoe
Description Maximum number of events that can be simultaneously configured with SubFunction
onComparisonOfValues.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
5

697 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Scope / Dependency scope: local

[ECUC_Dcm_01239] Definition of EcucIntegerParamDef DcmDspRoeMaxNumOf

StoredDTCStatusChangedEvents d
Parameter Name DcmDspRoeMaxNumOfStoredDTCStatusChangedEvents
Parent Container DcmDspRoe
Description Maximum number of changed DTC events that can be stored within one DcmDspRoe
SchedulerRate interval.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01238] Definition of EcucIntegerParamDef DcmDspRoeMaxSup-

portedDIDLength d
Parameter Name DcmDspRoeMaxSupportedDIDLength
Parent Container DcmDspRoe
Description Maximum DID response size in bytes allowed for a DID that is used for onComparison
OfValues or onChangeOfDataIdentifier.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 4294967295
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
5

698 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Scope / Dependency scope: local

[ECUC_Dcm_01235] Definition of EcucFloatParamDef DcmDspRoeScheduler

Rate d
Parameter Name DcmDspRoeSchedulerRate
Parent Container DcmDspRoe
Description Calling rate of the RoE scheduler. The parameter value is defined in seconds and shall
be a multiple of DcmTaskTime.
Multiplicity 1
Type EcucFloatParamDef
Range [-INF .. INF]
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01234] Definition of EcucBooleanParamDef DcmDspRoeStore

EventSupport d
Parameter Name DcmDspRoeStoreEventSupport
Parent Container DcmDspRoe
Description Configures if ResponseOnEvent storageState is supported. If set to true, the use of the
storageState bit is supported and if set to false the use of the storageState bit is not
supported.
Multiplicity 1
Type EcucBooleanParamDef
Default value true
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

699 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspRoe: DcmDspRoeStoreEventSupport:
EcucParamConfContainerDef EcucBooleanParamDef
+parameter
lowerMultiplicity = 0 defaultValue = true
upperMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspRoeSchedulerRate:
+parameter EcucFloatParamDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspRoeMaxNumChangeOfDataIdentfierEvents:
EcucIntegerParamDef
+parameter
min = 0
max = 255
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspRoeMaxNumComparisonOfValueEvents:
EcucIntegerParamDef
+parameter
min = 0
max = 255
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspRoeMaxSupportedDIDLength:
EcucIntegerParamDef
+parameter
min = 1
max = 4294967295
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspRoeMaxNumOfStoredDTCStatusChangedEvents:
EcucIntegerParamDef
+parameter
min = 0
max = 255
lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.43: DcmDspRoe configuration overview

700 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.19 Routines

DcmDsp:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspRoutine: DcmDspRoutineIdentifier: EcucIntegerParamDef

EcucParamConfContainerDef +parameter
lowerMultiplicity = 1
upperMultiplicity = * upperMultiplicity = 1
lowerMultiplicity = 0 min = 0
max = 65535

DcmDspRoutineUsePort: EcucBooleanParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1

+literal
DcmDspRoutineFncSignature: ROUTINE_FNC_NORMAL:
EcucEnumerationParamDef EcucEnumerationLiteralDef
+parameter defaultValue = ROUTINE_FNC_NORMAL
lowerMultiplicity = 1
upperMultiplicity = 1
+literal ROUTINE_FNC_PROXY:
EcucEnumerationLiteralDef

DcmDspRoutineUsed: EcucBooleanParamDef
+parameter
upperMultiplicity = 1
lowerMultiplicity = 1

DcmDspStartRoutine:
+subContainer EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspStopRoutine:
+subContainer EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 0

DcmDspRequestRoutineResults:
+subContainer EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 0

DcmDspRoutineInfoByte: EcucIntegerParamDef

+parameter lowerMultiplicity = 0
upperMultiplicity = 1
min = 0
max = 255

Figure 10.44: DcmDspRoutine configuration overview

10.2.5.19.1 DcmDspRoutine

[ECUC_Dcm_00640] Definition of EcucParamConfContainerDef DcmDspRoutine

d

701 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspRoutine

Parent Container DcmDsp
Description This container contains the configuration (parameters) for Routines
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspRoutineFncSignature 1 [ECUC_Dcm_01215]
DcmDspRoutineIdentifier 1 [ECUC_Dcm_00641]
DcmDspRoutineInfoByte 0..1 [ECUC_Dcm_01063]
DcmDspRoutineUsed 1 [ECUC_Dcm_00807]
DcmDspRoutineUsePort 1 [ECUC_Dcm_00724]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspRequestRoutineResults 0..1 Provides the configuration of RequestResult subservice for
RoutineControl service. Existence indicates that the Request
RoutineResults in the RoutineControl is supported.
DcmDspStartRoutine 0..1 Provides the configuration of Start subservice for RoutineControl
service.
DcmDspStopRoutine 0..1 Provides the configuration of Stop subservice for RoutineControl
service. Existence indicates that the StopRoutine in the Routine
Control is supported.

[ECUC_Dcm_01215] Definition of EcucEnumerationParamDef DcmDspRoutine

FncSignature
Status: DRAFT
d
Parameter Name DcmDspRoutineFncSignature
Parent Container DcmDspRoutine
Description If the parameter is set to ROUTINE_FNC_NORMAL the routine control functions Dcm
DspStartRoutineFnc, DcmDspStopRoutineFnc or DcmDspRequestResultsRoutineFnc
are defined with the signature for a cluster local user with separate arguments per
signal. If the parameter is set to ROUTINE_FNC_PROXY the routine control functions
DcmDspStartRoutineFnc, DcmDspStopRoutineFnc or DcmDspRequestResultsRoutine
Fnc with a fixed number of arguments passing a common buffer for all signals and a
DataLength.
Tags: atp.Status=draft
Multiplicity 1
Type EcucEnumerationParamDef
Range ROUTINE_FNC_NORMAL Function calls with normal set of arguments used
for Sw Cluster internal interfaces.
Tags: atp.Status=draft
5

702 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
ROUTINE_FNC_PROXY Function call used with generic set of arguments
used for Dcm low proxy.
Tags: atp.Status=draft
Default value ROUTINE_FNC_NORMAL
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00641] Definition of EcucIntegerParamDef DcmDspRoutineIdenti-

fier d
Parameter Name DcmDspRoutineIdentifier
Parent Container DcmDspRoutine
Description 2 bytes Identifier of the RID
Within each DcmConfigSet all DcmDspRoutineIdentifier values shall be unique.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01063] Definition of EcucIntegerParamDef DcmDspRoutineInfo

Byte d
Parameter Name DcmDspRoutineInfoByte
Parent Container DcmDspRoutine
Description Manufacturer specific value reported to the tester for the record identifiers 0xE000 to
OxE1FF. (OBD use cases)
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
5

703 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00807] Definition of EcucBooleanParamDef DcmDspRoutineUsed

d
Parameter Name DcmDspRoutineUsed
Parent Container DcmDspRoutine
Description Allow to activate or deactivate the usage of a Routine, for multi purpose ECUs
True = Routine is available False = Routine is not available
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value true
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU

[ECUC_Dcm_00724] Definition of EcucBooleanParamDef DcmDspRoutineUse

Port d
Parameter Name DcmDspRoutineUsePort
Parent Container DcmDspRoutine
Description If this parameter is set to true, the DCM uses a port requiring a PortInterface Routine
Services_{RoutineName}.
The R-Port is named RoutineServices_{RoutineName} where {RoutineName} is the
name of the container DcmDspRoutine In that case, the configuration must not provide
function names in DcmDspStartRoutineFnc, DcmDspStopRoutineFnc or DcmDsp
RequestResultsRoutineFnc. If this is false, the DCM expects to find the names of the
functions to be used in DcmDspStartRoutineFnc, DcmDspStopRoutineFnc or DcmDsp
RequestResultsRoutineFnc.
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
5

704 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Scope / Dependency scope: ECU

10.2.5.19.2 DcmDspRequestRoutineResults

[ECUC_Dcm_01023] Definition of EcucParamConfContainerDef DcmDspRequest

RoutineResults d
Container Name DcmDspRequestRoutineResults
Parent Container DcmDspRoutine
Description Provides the configuration of RequestResult subservice for RoutineControl service.
Existence indicates that the RequestRoutineResults in the RoutineControl is supported.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspRequestRoutineResultsConfirmationEnabled 0..1 [ECUC_Dcm_01091]
DcmDspRequestRoutineResultsConfirmationFnc 0..1 [ECUC_Dcm_01090]
DcmDspRequestRoutineResultsFnc 0..1 [ECUC_Dcm_00753]
DcmDspRoutineInterfaceArgumentIntegrity 0..1 [ECUC_Dcm_01216]
DcmDspRequestRoutineResultsCommonAuthorizationRef 0..1 [ECUC_Dcm_01054]
DcmDspRequestRoutineResultsRoleRef 0..32 [ECUC_Dcm_01146]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspRequestRoutineResultsIn 0..1 Provide description of input parameter of RequestResult
subservice for RoutineControl service.
DcmDspRequestRoutineResults 0..1 Provide description of output parameter of RequestResult
Out subservice for RoutineControl service.

[ECUC_Dcm_01091] Definition of EcucBooleanParamDef DcmDspRequestRou-

tineResultsConfirmationEnabled d
Parameter Name DcmDspRequestRoutineResultsConfirmationEnabled
Parent Container DcmDspRequestRoutineResults
Description Allows to enable/disable the confirmation function to indicate the transmission of a
response to a RequestRoutineResults request
Multiplicity 0..1
Type EcucBooleanParamDef
Default value false
5

705 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01090] Definition of EcucFunctionNameDef DcmDspRequestRou-

tineResultsConfirmationFnc d
Parameter Name DcmDspRequestRoutineResultsConfirmationFnc
Parent Container DcmDspRequestRoutineResults
Description C-function to call if a transmission confirmation is needed by the issuer (BSW module)
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00753] Definition of EcucFunctionNameDef DcmDspRequestRou-

tineResultsFnc d
Parameter Name DcmDspRequestRoutineResultsFnc
Parent Container DcmDspRequestRoutineResults
Description Function name for request to application the results of a routine. (Routine_Request
Results-function)
This parameter is related to the interface Xxx_RequestResults.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
5

706 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01216] Definition of EcucBooleanParamDef DcmDspRoutineInter-

faceArgumentIntegrity d
Parameter Name DcmDspRoutineInterfaceArgumentIntegrity
Parent Container DcmDspRequestRoutineResults, DcmDspStartRoutine, DcmDspStopRoutine
Description Defines the value of ClientServerOperation.diagArgIntegrity for the created C/S
interface of this routine
Multiplicity 0..1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01054] Definition of EcucReferenceDef DcmDspRequestRoutine

ResultsCommonAuthorizationRef d
Parameter Name DcmDspRequestRoutineResultsCommonAuthorizationRef
Parent Container DcmDspRequestRoutineResults
Description Reference to DcmDspCommonAuthorization
Common authorization configuration taken from the referenced DcmDspRequest
RoutineResultsCommonAuthorizationRef. If there is no reference, no check on the
commonly defined authorization conditions shall be done to get the routine result.
Multiplicity 0..1
Type Reference to DcmDspCommonAuthorization
5

707 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01146] Definition of EcucReferenceDef DcmDspRequestRoutine

ResultsRoleRef d
Parameter Name DcmDspRequestRoutineResultsRoleRef
Parent Container DcmDspRequestRoutineResults
Description Reference to DcmDspAuthenticationRow that defines a role in that this routine results
can be read.
Multiplicity 0..32
Type Reference to DcmDspAuthenticationRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

708 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspRoutine:
EcucParamConfContainerDef DcmDspRequestRoutineResultsInSignalCompositePool: DcmDspRequestRoutineResultsInSignalCompositeSignalRef:
EcucParamConfContainerDef +destination EcucReferenceDef
upperMultiplicity = *
lowerMultiplicity = 0 lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = *

+subContainer +reference

+subContainer +subContainer
DcmDspRequestRoutineResultsInSignal:
DcmDspRequestRoutineResults: EcucParamConfContainerDef
EcucParamConfContainerDef DcmDspRequestRoutineResultsIn:
+subContainer +subContainer
EcucParamConfContainerDef upperMultiplicity = *
upperMultiplicity = 1 lowerMultiplicity = 1
lowerMultiplicity = 0 upperMultiplicity = 1
requiresIndex = true
lowerMultiplicity = 0

DcmDspRequestRoutineResultsOutSignalCompositePool: DcmDspRequestRoutineResultsOutSignalCompositeSignalRef:
EcucParamConfContainerDef +destination EcucReferenceDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = *

+subContainer +reference
+subContainer
DcmDspRequestRoutineResultsOutSignal:
DcmDspRequestRoutineResultsOut: EcucParamConfContainerDef
+subContainer EcucParamConfContainerDef +subContainer
upperMultiplicity = *
upperMultiplicity = 1 lowerMultiplicity = 1
lowerMultiplicity = 0 requiresIndex = true

DcmDspRequestRoutineResultsCommonAuthorizationRef: DcmDspCommonAuthorization:
+reference EcucReferenceDef +destination EcucParamConfContainerDef
lowerMultiplicity = 0 upperMultiplicity = *
upperMultiplicity = 1 lowerMultiplicity = 0

+parameter DcmDspRequestRoutineResultsFnc:
EcucFunctionNameDef
DcmDspRequestRoutineResultsRoleRef:
lowerMultiplicity = 0 EcucReferenceDef
upperMultiplicity = 1
lowerMultiplicity = 0
+reference upperMultiplicity = 32

DcmDspRequestRoutineResultsConfirmationEnabled:
EcucBooleanParamDef
+parameter
defaultValue = false
lowerMultiplicity = 0
upperMultiplicity = 1
+destination

DcmDspAuthenticationRow:
EcucParamConfContainerDef
DcmDspRequestRoutineResultsConfirmationFnc: lowerMultiplicity = 0
+parameter EcucFunctionNameDef upperMultiplicity = 31
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspRoutineInterfaceArgumentIntegrity:
+parameter
EcucBooleanParamDef

defaultValue = false
lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.45: DcmDspRequestRoutineResults configuration overview

10.2.5.19.3 DcmDspRequestRoutineResultsIn

[ECUC_Dcm_01116] Definition of EcucParamConfContainerDef DcmDspRequest

RoutineResultsIn d

709 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspRequestRoutineResultsIn

Parent Container DcmDspRequestRoutineResults
Description Provide description of input parameter of RequestResult subservice for RoutineControl
service.
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspRequestRoutineResultsIn 1..* Provides description of a routine signal used in RoutineControl
Signal service.
The ordering defined via the index attribute of the subcontainers
in this list represents the order of the dataIn_n elements in the
XXX_RequestResult function call.
DcmDspRequestRoutineResultsIn 0..* Defines a collection of all contained signals for this root signal.
SignalCompositePool

10.2.5.19.4 DcmDspRequestRoutineResultsInSignal

[ECUC_Dcm_01117] Definition of EcucParamConfContainerDef DcmDspRequest

RoutineResultsInSignal d
Container Name DcmDspRequestRoutineResultsInSignal
Parent Container DcmDspRequestRoutineResultsIn, DcmDspRequestRoutineResultsInSignalComposite
Pool
Description Provides description of a routine signal used in RoutineControl service.
The ordering defined via the index attribute of the subcontainers in this list represents
the order of the dataIn_n elements in the XXX_RequestResult function call.
Attributes: requiresIndex=true
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspRoutineParameterSize 0..1 [ECUC_Dcm_01119]
DcmDspRoutineSignalEndianness 0..1 [ECUC_Dcm_01121]
DcmDspRoutineSignalPos 1 [ECUC_Dcm_01118]
DcmDspRoutineSignalType 0..1 [ECUC_Dcm_01120]
DcmDspRequestRoutineResultsInSignalCompositeSignal 0..* [ECUC_Dcm_01228]
Ref

710 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspArgumentScaling 0..1 This container contains the configuration (arguments) of an
alternative Diagnosis Representation. Out if this the scaling
between Diagnosis and ECU internal representation and vice
versa can be calculated.

[ECUC_Dcm_01119] Definition of EcucIntegerParamDef DcmDspRoutineParam-

eterSize d
Parameter Name DcmDspRoutineParameterSize
Parent Container DcmDspRequestRoutineResultsInSignal
Description Provide the size of a RoutineControl parameter in bytes
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01121] Definition of EcucEnumerationParamDef DcmDspRoutine

SignalEndianness d
Parameter Name DcmDspRoutineSignalEndianness
Parent Container DcmDspRequestRoutineResultsInSignal
Description Defines the endianness of the data belonging to a Routine In Signal for RequestResult
subfunction.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at the lowest
address.
LITTLE_ENDIAN Most significant byte shall be stored at the
highest address
OPAQUE Opaque data endianness
Post-Build Variant Multiplicity false
Post-Build Variant Value false
5

711 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01118] Definition of EcucIntegerParamDef DcmDspRoutineSignal

Pos d
Parameter Name DcmDspRoutineSignalPos
Parent Container DcmDspRequestRoutineResultsInSignal
Description Provide the position of the signal in the RoutineControl request/response. The position
is defined in bits.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01120] Definition of EcucEnumerationParamDef DcmDspRoutine

SignalType d
Parameter Name DcmDspRoutineSignalType
Parent Container DcmDspRequestRoutineResultsInSignal
Description Provide the type of the signal in the RoutineControl request/response.
Multiplicity 0..1
Type EcucEnumerationParamDef

Range BOOLEAN Type of the signal is boolean.

FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the signal is sint16.
SINT16_N Type of the signal is sint16 array.
SINT32 Type of the signal is sint32.
5

712 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
SINT32_N Type of the signal is sint32 array.
SINT8 Type of the signal is sint8.
SINT8_N Type of the signal is sint8 array.
UINT16 Type of the signal is uint16.
UINT16_N Type of the signal is uint16 array.
UINT32 Type of the signal is uint32.
UINT32_N Type of the signal is uint32 array.
UINT8 Type of the signal is uint8.
UINT8_N Type of the signal is uint8 array.
VARIABLE_LENGTH Type of the signal is uint8[DcmDspRoutine
ParameterSize].
This is only valid for the last signal and when
DcmDspRoutineSignalType is set to VARIABLE_
LENGTH.
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01228] Definition of EcucReferenceDef DcmDspRequestRoutine

ResultsInSignalCompositeSignalRef d
Parameter Name DcmDspRequestRoutineResultsInSignalCompositeSignalRef
Parent Container DcmDspRequestRoutineResultsInSignal
Description Reference to the contained signal.
Multiplicity 0..*
Type Reference to DcmDspRequestRoutineResultsInSignalCompositePool
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

713 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.19.5 DcmDspRequestRoutineResultsInSignalCompositePool

[ECUC_Dcm_01227] Definition of EcucParamConfContainerDef DcmDspRequest

RoutineResultsInSignalCompositePool d
Container Name DcmDspRequestRoutineResultsInSignalCompositePool
Parent Container DcmDspRequestRoutineResultsIn
Description Defines a collection of all contained signals for this root signal.
Post-Build Variant Multiplicity false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspRequestRoutineResultsIn 1..* Provides description of a routine signal used in RoutineControl
Signal service.
The ordering defined via the index attribute of the subcontainers
in this list represents the order of the dataIn_n elements in the
XXX_RequestResult function call.

10.2.5.19.6 DcmDspRequestRoutineResultsOut

[ECUC_Dcm_00831] Definition of EcucParamConfContainerDef DcmDspRequest

RoutineResultsOut d
Container Name DcmDspRequestRoutineResultsOut
Parent Container DcmDspRequestRoutineResults
Description Provide description of output parameter of RequestResult subservice for Routine
Control service.
Configuration Parameters

No Included Parameters

714 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspRequestRoutineResults 1..* Provides description of a routine signal used in RoutineControl
OutSignal service.
The ordering defined via the index attribute of the subcontainers
in this list represents the order of the dataOutN elements in the
XXX_RequestResult function call.
DcmDspRequestRoutineResults 0..* Defines a collection of all contained signals for this root signal.
OutSignalCompositePool

10.2.5.19.7 DcmDspRequestRoutineResultsOutSignal

[ECUC_Dcm_00836] Definition of EcucParamConfContainerDef DcmDspRequest

RoutineResultsOutSignal d
Container Name DcmDspRequestRoutineResultsOutSignal
Parent Container DcmDspRequestRoutineResultsOut, DcmDspRequestRoutineResultsOutSignal
CompositePool
Description Provides description of a routine signal used in RoutineControl service.
The ordering defined via the index attribute of the subcontainers in this list represents
the order of the dataOutN elements in the XXX_RequestResult function call.
Attributes: requiresIndex=true
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspRoutineParameterSize 0..1 [ECUC_Dcm_00838]
DcmDspRoutineSignalEndianness 0..1 [ECUC_Dcm_01013]
DcmDspRoutineSignalPos 1 [ECUC_Dcm_00837]
DcmDspRoutineSignalType 0..1 [ECUC_Dcm_00881]
DcmDspRequestRoutineResultsOutSignalComposite 0..* [ECUC_Dcm_01230]
SignalRef

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspArgumentScaling 0..1 This container contains the configuration (arguments) of an
alternative Diagnosis Representation. Out if this the scaling
between Diagnosis and ECU internal representation and vice
versa can be calculated.

715 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00838] Definition of EcucIntegerParamDef DcmDspRoutineParam-

eterSize d
Parameter Name DcmDspRoutineParameterSize
Parent Container DcmDspRequestRoutineResultsOutSignal
Description Provide the size of a RoutineControl parameter in bytes
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01013] Definition of EcucEnumerationParamDef DcmDspRoutine

SignalEndianness d
Parameter Name DcmDspRoutineSignalEndianness
Parent Container DcmDspRequestRoutineResultsOutSignal
Description Defines the endianness of the data belonging to a Routine Out Signal for Request
Result subfunction.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at the lowest
address.
LITTLE_ENDIAN Most significant byte shall be stored at the
highest address
OPAQUE Opaque data endianness
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

716 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00837] Definition of EcucIntegerParamDef DcmDspRoutineSignal

Pos d
Parameter Name DcmDspRoutineSignalPos
Parent Container DcmDspRequestRoutineResultsOutSignal
Description Provide the position of the signal in the RoutineControl request/response. The position
is defined in bits.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00881] Definition of EcucEnumerationParamDef DcmDspRoutine

SignalType d
Parameter Name DcmDspRoutineSignalType
Parent Container DcmDspRequestRoutineResultsOutSignal
Description Provide the type of the signal in the RoutineControl request/response.
Multiplicity 0..1
Type EcucEnumerationParamDef
BOOLEAN Type of the signal is boolean.
Range
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the signal is sint16.
SINT16_N Type of the signal is sint16 array.
SINT32 Type of the signal is sint32.
SINT32_N Type of the signal is sint32 array.
SINT8 Type of the signal is sint8.
SINT8_N Type of the signal is sint8 array.
UINT16 Type of the signal is uint16.
UINT16_N Type of the signal is uint16 array.
UINT32 Type of the signal is uint32.
UINT32_N Type of the signal is uint32 array.
UINT8 Type of the signal is uint8.
UINT8_N Type of the signal is uint8 array.
5

717 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
VARIABLE_LENGTH Type of the signal is uint8[DcmDspRoutine
ParameterSize].
This is only valid for the last signal and when
DcmDspRoutineSignalType is set to VARIABLE_
LENGTH.
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01230] Definition of EcucReferenceDef DcmDspRequestRoutine

ResultsOutSignalCompositeSignalRef d
Parameter Name DcmDspRequestRoutineResultsOutSignalCompositeSignalRef
Parent Container DcmDspRequestRoutineResultsOutSignal
Description Reference to the contained signal.
Multiplicity 0..*
Type Reference to DcmDspRequestRoutineResultsOutSignalCompositePool
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.19.8 DcmDspRequestRoutineResultsOutSignalCompositePool

[ECUC_Dcm_01229] Definition of EcucParamConfContainerDef DcmDspRequest

RoutineResultsOutSignalCompositePool d
Container Name DcmDspRequestRoutineResultsOutSignalCompositePool
Parent Container DcmDspRequestRoutineResultsOut
Description Defines a collection of all contained signals for this root signal.
Post-Build Variant Multiplicity false
5

718 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspRequestRoutineResults 1..* Provides description of a routine signal used in RoutineControl
OutSignal service.
The ordering defined via the index attribute of the subcontainers
in this list represents the order of the dataOutN elements in the
XXX_RequestResult function call.

10.2.5.19.9 DcmDspStartRoutine

[ECUC_Dcm_01021] Definition of EcucParamConfContainerDef DcmDspStart

Routine d
Container Name DcmDspStartRoutine
Parent Container DcmDspRoutine
Description Provides the configuration of Start subservice for RoutineControl service.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspRoutineInterfaceArgumentIntegrity 0..1 [ECUC_Dcm_01216]
DcmDspStartRoutineConfirmationEnabled 0..1 [ECUC_Dcm_01093]
DcmDspStartRoutineConfirmationFnc 0..1 [ECUC_Dcm_01094]
DcmDspStartRoutineFnc 0..1 [ECUC_Dcm_00664]
DcmDspStartRoutineCommonAuthorizationRef 0..1 [ECUC_Dcm_01052]
DcmDspStartRoutineRoleRef 0..32 [ECUC_Dcm_01144]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStartRoutineIn 0..1 Provide description of input parameter of Start subservice for
RoutineControl service
DcmDspStartRoutineOut 0..1 Provide description of output parameter of Start subservice for
RoutineControl service.

719 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

For parameter table [ECUC_Dcm_01216] DcmDspRoutineInterfaceArgumentIntegrity,

see definition below container DcmDspRequestRoutineResults.

[ECUC_Dcm_01093] Definition of EcucBooleanParamDef DcmDspStartRoutine

ConfirmationEnabled d
Parameter Name DcmDspStartRoutineConfirmationEnabled
Parent Container DcmDspStartRoutine
Description Allows to enable/disable the confirmation function to indicate the transmission of a
response to a StartRoutine request
Multiplicity 0..1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01094] Definition of EcucFunctionNameDef DcmDspStartRoutine

ConfirmationFnc d
Parameter Name DcmDspStartRoutineConfirmationFnc
Parent Container DcmDspStartRoutine
Description C-function to call if a transmission confirmation is needed by the issuer (BSW module)
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

720 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00664] Definition of EcucFunctionNameDef DcmDspStartRoutine

Fnc d
Parameter Name DcmDspStartRoutineFnc
Parent Container DcmDspStartRoutine
Description Function name for request to application to start a routine. (Routine_Start-function)
This parameter is related to the interface Xxx_Start.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01052] Definition of EcucReferenceDef DcmDspStartRoutineCom-

monAuthorizationRef d
Parameter Name DcmDspStartRoutineCommonAuthorizationRef
Parent Container DcmDspStartRoutine
Description Reference to DcmDspCommonAuthorization
Common authorization configuration taken from the referenced DcmDspStartRoutine
CommonAuthorizationRef. If there is no reference, no check on the commonly defined
authorization conditions shall be done to start the routine.
Multiplicity 0..1
Type Reference to DcmDspCommonAuthorization
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

721 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01144] Definition of EcucReferenceDef DcmDspStartRoutineRole

Ref d
Parameter Name DcmDspStartRoutineRoleRef
Parent Container DcmDspStartRoutine
Description Reference to DcmDspAuthenticationRow that defines a role in that this routine can be
started.
Multiplicity 0..32
Type Reference to DcmDspAuthenticationRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

722 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspRoutine:
EcucParamConfContainerDef DcmDspStartRoutineInSignalCompositePool: DcmDspStartRoutineInSignalCompositeSignalRef:
EcucParamConfContainerDef +destination EcucReferenceDef
upperMultiplicity = *
lowerMultiplicity = 0 lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = *

+subContainer +reference

+subContainer +subContainer
DcmDspStartRoutineInSignal:
DcmDspStartRoutine:
EcucParamConfContainerDef
EcucParamConfContainerDef
DcmDspStartRoutineIn:
+subContainer EcucParamConfContainerDef +subContainer upperMultiplicity = *
lowerMultiplicity = 0
lowerMultiplicity = 1
upperMultiplicity = 1
upperMultiplicity = 1 requiresIndex = true
lowerMultiplicity = 0

DcmDspStartRoutineOutSignalCompositePool: DcmDspStartRoutineOutSignalCompositeSignalRef:
EcucParamConfContainerDef +destination EcucReferenceDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = *

+subContainer +reference

+subContainer

DcmDspStartRoutineOutSignal:
EcucParamConfContainerDef
DcmDspStartRoutineOut:
+subContainer EcucParamConfContainerDef +subContainer upperMultiplicity = *
lowerMultiplicity = 1
upperMultiplicity = 1
requiresIndex = true
lowerMultiplicity = 0

DcmDspStartRoutineCommonAuthorizationRef: DcmDspCommonAuthorization:
+reference EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 upperMultiplicity = *
upperMultiplicity = 1 lowerMultiplicity = 0

DcmDspStartRoutineFnc:
+parameter
EcucFunctionNameDef

lowerMultiplicity = 0 DcmDspStartRoutineRoleRef:
upperMultiplicity = 1 EcucReferenceDef
+reference
lowerMultiplicity = 0
upperMultiplicity = 32
DcmDspStartRoutineConfirmationEnabled:
EcucBooleanParamDef
+parameter
defaultValue = false
lowerMultiplicity = 0
upperMultiplicity = 1
+destination

DcmDspAuthenticationRow:
EcucParamConfContainerDef
DcmDspStartRoutineConfirmationFnc:
+parameter EcucFunctionNameDef lowerMultiplicity = 0
upperMultiplicity = 31
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspRoutineInterfaceArgumentIntegrity:
+parameter EcucBooleanParamDef

defaultValue = false
lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.46: DcmDspStartRoutine configuration overview

10.2.5.19.10 DcmDspStartRoutineIn

[ECUC_Dcm_00834] Definition of EcucParamConfContainerDef DcmDspStart

RoutineIn d

723 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspStartRoutineIn

Parent Container DcmDspStartRoutine
Description Provide description of input parameter of Start subservice for RoutineControl service
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStartRoutineInSignal 1..* Provide description of a routine signal used in RoutineControl
service.
The ordering defined via the index attribute of the subcontainers
in this list represents the order of the dataInN elements in the
XXX_Start function call.
DcmDspStartRoutineInSignal 0..* Defines a collection of all contained signals for this root signal.
CompositePool

724 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspStartRoutineIn:
EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 0
DcmDspRoutineSignalPos:
EcucIntegerParamDef

+subContainer lowerMultiplicity = 1
+parameter upperMultiplicity = 1
DcmDspStartRoutineInSignal: min = 0
EcucParamConfContainerDef max = 65535
DcmDspRoutineParameterSize:
upperMultiplicity = * EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
lowerMultiplicity = 0
requiresIndex = true
upperMultiplicity = 1
min = 0
max = 65535

+literal
DcmDspRoutineSignalType: BOOLEAN: EcucEnumerationLiteralDef
EcucEnumerationParamDef +literal

lowerMultiplicity = 0 UINT8: EcucEnumerationLiteralDef

upperMultiplicity = 1 +literal
UINT8_N: EcucEnumerationLiteralDef

+literal
SINT8_N: EcucEnumerationLiteralDef

+literal SINT8: EcucEnumerationLiteralDef

+literal
UINT16: EcucEnumerationLiteralDef
+literal
UINT16_N: EcucEnumerationLiteralDef

+literal
+parameter SINT16_N: EcucEnumerationLiteralDef
+literal
SINT16: EcucEnumerationLiteralDef

+literal
UINT32: EcucEnumerationLiteralDef
+literal
SINT32: EcucEnumerationLiteralDef

+literal
UINT32_N: EcucEnumerationLiteralDef

+literal
SINT32_N: EcucEnumerationLiteralDef
+literal
FLOAT: EcucEnumerationLiteralDef

+literal FLOAT_N: EcucEnumerationLiteralDef

+literal
VARIABLE_LENGTH: EcucEnumerationLiteralDef

LITTLE_ENDIAN:
+literal EcucEnumerationLiteralDef
DcmDspRoutineSignalEndianness:
+parameter EcucEnumerationParamDef +literal
OPAQUE:
lowerMultiplicity = 0 EcucEnumerationLiteralDef
upperMultiplicity = 1
+literal

BIG_ENDIAN:
DcmDspArgumentScaling: EcucEnumerationLiteralDef
+subContainer EcucChoiceContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspStartRoutineInSignalCompositeSignalRef:
+reference EcucReferenceDef

lowerMultiplicity = 0
upperMultiplicity = *

Figure 10.47: DcmDspStartRoutineIn configuration overview

725 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.19.11 DcmDspStartRoutineInSignal

[ECUC_Dcm_00845] Definition of EcucParamConfContainerDef DcmDspStart

RoutineInSignal d
Container Name DcmDspStartRoutineInSignal
Parent Container DcmDspStartRoutineIn, DcmDspStartRoutineInSignalCompositePool
Description Provide description of a routine signal used in RoutineControl service.
The ordering defined via the index attribute of the subcontainers in this list represents
the order of the dataInN elements in the XXX_Start function call.
Attributes: requiresIndex=true
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspRoutineParameterSize 0..1 [ECUC_Dcm_00847]
DcmDspRoutineSignalEndianness 0..1 [ECUC_Dcm_01016]
DcmDspRoutineSignalPos 1 [ECUC_Dcm_00846]
DcmDspRoutineSignalType 0..1 [ECUC_Dcm_00884]
DcmDspStartRoutineInSignalCompositeSignalRef 0..* [ECUC_Dcm_01220]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspArgumentScaling 0..1 This container contains the configuration (arguments) of an
alternative Diagnosis Representation. Out if this the scaling
between Diagnosis and ECU internal representation and vice
versa can be calculated.

[ECUC_Dcm_00847] Definition of EcucIntegerParamDef DcmDspRoutineParam-

eterSize d
Parameter Name DcmDspRoutineParameterSize
Parent Container DcmDspStartRoutineInSignal
Description Provide the size of a RoutineControl parameter in bytes
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
5

726 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01016] Definition of EcucEnumerationParamDef DcmDspRoutine

SignalEndianness d
Parameter Name DcmDspRoutineSignalEndianness
Parent Container DcmDspStartRoutineInSignal
Description Defines the endianness of the data belonging to a Routine In Signal for Start
subfunction.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at the lowest
address.
LITTLE_ENDIAN Most significant byte shall be stored at the
highest address
OPAQUE Opaque data endianness
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00846] Definition of EcucIntegerParamDef DcmDspRoutineSignal

Pos d
Parameter Name DcmDspRoutineSignalPos
Parent Container DcmDspStartRoutineInSignal
Description Provide the position of the signal in the RoutineControl request/response. The position
is defined in bits.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Value false
5

727 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00884] Definition of EcucEnumerationParamDef DcmDspRoutine

SignalType d
Parameter Name DcmDspRoutineSignalType
Parent Container DcmDspStartRoutineInSignal
Description Provide the type of the signal in the RoutineControl request/response.
Multiplicity 0..1
Type EcucEnumerationParamDef
BOOLEAN Type of the signal is boolean.
Range
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the signal is sint16.
SINT16_N Type of the signal is sint16 array.
SINT32 Type of the signal is sint32.
SINT32_N Type of the signal is sint32 array.
SINT8 Type of the signal is sint8.
SINT8_N Type of the signal is sint8 array.
UINT16 Type of the signal is uint16.
UINT16_N Type of the signal is uint16 array.
UINT32 Type of the signal is uint32.
UINT32_N Type of the signal is uint32 array.
UINT8 Type of the signal is uint8.
UINT8_N Type of the signal is uint8 array.
VARIABLE_LENGTH Type of the signal is uint8[DcmDspRoutine
ParameterSize].
This is only valid for the last signal and when
DcmDspRoutineSignalType is set to VARIABLE_
LENGTH.
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

728 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01220] Definition of EcucReferenceDef DcmDspStartRoutineInSig-

nalCompositeSignalRef d
Parameter Name DcmDspStartRoutineInSignalCompositeSignalRef
Parent Container DcmDspStartRoutineInSignal
Description Reference to the contained signal.
Multiplicity 0..*
Type Reference to DcmDspStartRoutineInSignalCompositePool
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.19.12 DcmDspStartRoutineInSignalCompositePool

[ECUC_Dcm_01219] Definition of EcucParamConfContainerDef DcmDspStart

RoutineInSignalCompositePool d
Container Name DcmDspStartRoutineInSignalCompositePool
Parent Container DcmDspStartRoutineIn
Description Defines a collection of all contained signals for this root signal.
Post-Build Variant Multiplicity false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStartRoutineInSignal 1..* Provide description of a routine signal used in RoutineControl
service.
The ordering defined via the index attribute of the subcontainers
in this list represents the order of the dataInN elements in the
XXX_Start function call.

729 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.19.13 DcmDspStartRoutineOut

[ECUC_Dcm_00835] Definition of EcucParamConfContainerDef DcmDspStart

RoutineOut d
Container Name DcmDspStartRoutineOut
Parent Container DcmDspStartRoutine
Description Provide description of output parameter of Start subservice for RoutineControl service.
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStartRoutineOutSignal 1..* Provide description of a routine signal used in RoutineControl
service.
The ordering defined via the index attribute of the subcontainers
in this list represents the order of the dataOutN elements in the
XXX_Start function call.
DcmDspStartRoutineOutSignal 0..* Defines a collection of all contained signals for this root signal.
CompositePool

730 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspStartRoutineOut:
EcucParamConfContainerDef

upperMultiplicity = 1 DcmDspRoutineSignalPos:
lowerMultiplicity = 0 EcucIntegerParamDef

lowerMultiplicity = 0
+subContainer upperMultiplicity = 1
DcmDspRoutineParameterSize:
+parameter min = 0
EcucIntegerParamDef
DcmDspStartRoutineOutSignal: max = 65535
EcucParamConfContainerDef lowerMultiplicity = 0
upperMultiplicity = 1
upperMultiplicity = * +parameter min = 0
lowerMultiplicity = 1 max = 65535
requiresIndex = true

+literal
DcmDspRoutineSignalType: BOOLEAN: EcucEnumerationLiteralDef
EcucEnumerationParamDef
+literal
lowerMultiplicity = 0 UINT8: EcucEnumerationLiteralDef
upperMultiplicity = 1 +literal

UINT8_N: EcucEnumerationLiteralDef
+literal
SINT8: EcucEnumerationLiteralDef

+literal
SINT8_N: EcucEnumerationLiteralDef

+literal
UINT16: EcucEnumerationLiteralDef

+literal
UINT16_N: EcucEnumerationLiteralDef

+literal
+parameter SINT16: EcucEnumerationLiteralDef

+literal
SINT16_N: EcucEnumerationLiteralDef

+literal
UINT32: EcucEnumerationLiteralDef

+literal
UINT32_N: EcucEnumerationLiteralDef

+literal
SINT32: EcucEnumerationLiteralDef

+literal
SINT32_N: EcucEnumerationLiteralDef

+literal
FLOAT: EcucEnumerationLiteralDef

+literal
FLOAT_N: EcucEnumerationLiteralDef

+literal
VARIABLE_LENGTH: EcucEnumerationLiteralDef

DcmDspRoutineSignalEndianness: +literal LITTLE_ENDIAN:

EcucEnumerationParamDef EcucEnumerationLiteralDef
+parameter
lowerMultiplicity = 0
+literal
upperMultiplicity = 1
OPAQUE:
EcucEnumerationLiteralDef

DcmDspArgumentScaling: +literal BIG_ENDIAN:

+subContainer EcucChoiceContainerDef EcucEnumerationLiteralDef

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspStartRoutineOutSignalCompositeSignalRef:
+reference EcucReferenceDef

lowerMultiplicity = 0
upperMultiplicity = *

Figure 10.48: DcmDspStartRoutineOut configuration overview

731 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.19.14 DcmDspStartRoutineOutSignal

[ECUC_Dcm_00848] Definition of EcucParamConfContainerDef DcmDspStart

RoutineOutSignal d
Container Name DcmDspStartRoutineOutSignal
Parent Container DcmDspStartRoutineOut, DcmDspStartRoutineOutSignalCompositePool
Description Provide description of a routine signal used in RoutineControl service.
The ordering defined via the index attribute of the subcontainers in this list represents
the order of the dataOutN elements in the XXX_Start function call.
Attributes: requiresIndex=true
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspRoutineParameterSize 0..1 [ECUC_Dcm_00850]
DcmDspRoutineSignalEndianness 0..1 [ECUC_Dcm_01017]
DcmDspRoutineSignalPos 0..1 [ECUC_Dcm_00867]
DcmDspRoutineSignalType 0..1 [ECUC_Dcm_00885]
DcmDspStartRoutineOutSignalCompositeSignalRef 0..* [ECUC_Dcm_01222]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspArgumentScaling 0..1 This container contains the configuration (arguments) of an
alternative Diagnosis Representation. Out if this the scaling
between Diagnosis and ECU internal representation and vice
versa can be calculated.

[ECUC_Dcm_00850] Definition of EcucIntegerParamDef DcmDspRoutineParam-

eterSize d
Parameter Name DcmDspRoutineParameterSize
Parent Container DcmDspStartRoutineOutSignal
Description Provide the size of a RoutineControl parameter in bytes
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
5

732 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01017] Definition of EcucEnumerationParamDef DcmDspRoutine

SignalEndianness d
Parameter Name DcmDspRoutineSignalEndianness
Parent Container DcmDspStartRoutineOutSignal
Description Defines the endianness of the data belonging to a Routine Out Signal for Start
subfunction.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at the lowest
address.
LITTLE_ENDIAN Most significant byte shall be stored at the
highest address
OPAQUE Opaque data endianness
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00867] Definition of EcucIntegerParamDef DcmDspRoutineSignal

Pos d
Parameter Name DcmDspRoutineSignalPos
Parent Container DcmDspStartRoutineOutSignal
Description Provide the position of the signal in the RoutineControl request/response. The position
is defined in bits.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Multiplicity false
5

733 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00885] Definition of EcucEnumerationParamDef DcmDspRoutine

SignalType d
Parameter Name DcmDspRoutineSignalType
Parent Container DcmDspStartRoutineOutSignal
Description Provide the type of the signal in the RoutineControl request/response.
Multiplicity 0..1
Type EcucEnumerationParamDef
BOOLEAN Type of the signal is boolean.
Range
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the signal is sint16.
SINT16_N Type of the signal is sint16 array.
SINT32 Type of the signal is sint32.
SINT32_N Type of the signal is sint32 array.
SINT8 Type of the signal is sint8.
SINT8_N Type of the signal is sint8 array.
UINT16 Type of the signal is uint16.
UINT16_N Type of the signal is uint16 array.
UINT32 Type of the signal is uint32.
UINT32_N Type of the signal is uint32 array.
UINT8 Type of the signal is uint8.
UINT8_N Type of the signal is uint8 array.
VARIABLE_LENGTH Type of the signal is uint8[DcmDspRoutine
ParameterSize].
This is only valid for the last signal and when
DcmDspRoutineSignalType is set to VARIABLE_
LENGTH.
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

734 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01222] Definition of EcucReferenceDef DcmDspStartRoutineOut

SignalCompositeSignalRef d
Parameter Name DcmDspStartRoutineOutSignalCompositeSignalRef
Parent Container DcmDspStartRoutineOutSignal
Description Reference to the contained signal.
Multiplicity 0..*
Type Reference to DcmDspStartRoutineOutSignalCompositePool
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.19.15 DcmDspStopRoutine

[ECUC_Dcm_01022] Definition of EcucParamConfContainerDef DcmDspStop

Routine d
Container Name DcmDspStopRoutine
Parent Container DcmDspRoutine
Description Provides the configuration of Stop subservice for RoutineControl service. Existence
indicates that the StopRoutine in the RoutineControl is supported.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspRoutineInterfaceArgumentIntegrity 0..1 [ECUC_Dcm_01216]
DcmDspStopRoutineConfirmationEnabled 0..1 [ECUC_Dcm_01095]
DcmDspStopRoutineConfirmationFnc 0..1 [ECUC_Dcm_01096]
DcmDspStopRoutineFnc 0..1 [ECUC_Dcm_00752]
DcmDspStopRoutineCommonAuthorizationRef 0..1 [ECUC_Dcm_01053]
DcmDspStopRoutineRoleRef 0..32 [ECUC_Dcm_01145]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStopRoutineIn 0..1 Provide description of input parameter of Stop subservice for
RoutineControl service.
DcmDspStopRoutineOut 0..1 Provide description of output parameter of Stop subservice for
RoutineControl service.

735 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

For parameter table [ECUC_Dcm_01216] DcmDspRoutineInterfaceArgumentIntegrity,

see definition below container DcmDspRequestRoutineResults.

[ECUC_Dcm_01095] Definition of EcucBooleanParamDef DcmDspStopRoutine

ConfirmationEnabled d
Parameter Name DcmDspStopRoutineConfirmationEnabled
Parent Container DcmDspStopRoutine
Description Allows to enable/disable the confirmation function to indicate the transmission of a
response to a StopRoutine request
Multiplicity 0..1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01096] Definition of EcucFunctionNameDef DcmDspStopRoutine

ConfirmationFnc d
Parameter Name DcmDspStopRoutineConfirmationFnc
Parent Container DcmDspStopRoutine
Description C-function to call if a transmission confirmation is needed by the issuer (BSW module)
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

736 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00752] Definition of EcucFunctionNameDef DcmDspStopRoutine

Fnc d
Parameter Name DcmDspStopRoutineFnc
Parent Container DcmDspStopRoutine
Description Function name for request to application to stop a routine. (Routine_Stop-function)
This parameter is related to the interface Xxx_Stop.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01053] Definition of EcucReferenceDef DcmDspStopRoutineCom-

monAuthorizationRef d
Parameter Name DcmDspStopRoutineCommonAuthorizationRef
Parent Container DcmDspStopRoutine
Description Reference to DcmDspCommonAuthorization
Common authorization configuration taken from the referenced DcmDspStopRoutine
CommonAuthorizationRef. If there is no reference, no check on the commonly defined
authorization conditions shall be done to stop the routine.
Multiplicity 0..1
Type Reference to DcmDspCommonAuthorization
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

737 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01145] Definition of EcucReferenceDef DcmDspStopRoutineRole

Ref d
Parameter Name DcmDspStopRoutineRoleRef
Parent Container DcmDspStopRoutine
Description Reference to DcmDspAuthenticationRow that defines a role in that this routine can be
stopped.
Multiplicity 0..32
Type Reference to DcmDspAuthenticationRow
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

738 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspRoutine:
EcucParamConfContainerDef DcmDspStopRoutineInSignalCompositePool: DcmDspStopRoutineInSignalCompositeSignalRef:
EcucParamConfContainerDef +destination EcucReferenceDef
upperMultiplicity = *
lowerMultiplicity = 0 lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = *

+subContainer +reference
+subContainer

DcmDspStopRoutine: +subContainer
EcucParamConfContainerDef DcmDspStopRoutineInSignal:
EcucParamConfContainerDef
upperMultiplicity = 1
lowerMultiplicity = 0 DcmDspStopRoutineIn: +subContainer upperMultiplicity = *
+subContainer EcucParamConfContainerDef lowerMultiplicity = 1
requiresIndex = true
upperMultiplicity = 1
lowerMultiplicity = 0

DcmDspStopRoutineOutSignalCompositePool: DcmDspStopRoutineOutSignalCompositeSignalRef:
EcucParamConfContainerDef +destination EcucReferenceDef

lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = *

+subContainer +reference

+subContainer
DcmDspStopRoutineOutSignal:
EcucParamConfContainerDef
DcmDspStopRoutineOut: +subContainer upperMultiplicity = *
+subContainer EcucParamConfContainerDef lowerMultiplicity = 1
upperMultiplicity = 1 requiresIndex = true
lowerMultiplicity = 0

DcmDspStopRoutineCommonAuthorizationRef: DcmDspCommonAuthorization:
+reference EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 upperMultiplicity = *
upperMultiplicity = 1 lowerMultiplicity = 0

DcmDspStopRoutineFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1 DcmDspStopRoutineRoleRef:
EcucReferenceDef
+reference
lowerMultiplicity = 0
upperMultiplicity = 32

DcmDspStopRoutineConfirmationEnabled:
EcucBooleanParamDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = 1
defaultValue = FALSE
+destination

DcmDspAuthenticationRow:
EcucParamConfContainerDef

DcmDspStopRoutineConfirmationFnc: lowerMultiplicity = 0
+parameter EcucFunctionNameDef upperMultiplicity = 31

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspRoutineInterfaceArgumentIntegrity:
+parameter EcucBooleanParamDef

defaultValue = false
lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.49: DcmDspStopRoutine configuration overview

739 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.19.16 DcmDspStopRoutineIn

[ECUC_Dcm_00832] Definition of EcucParamConfContainerDef DcmDspStop

RoutineIn d
Container Name DcmDspStopRoutineIn
Parent Container DcmDspStopRoutine
Description Provide description of input parameter of Stop subservice for RoutineControl service.
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStopRoutineInSignal 1..* Provide description of a routine signal used in RoutineControl
service.
The ordering defined via the index attribute of the subcontainers
in this list represents the order of the dataInN elements in the
XXX_Stop function call.
DcmDspStopRoutineInSignal 0..* Defines a collection of all contained signals for this root signal.
CompositePool

740 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspStopRoutineIn:
EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 0

DcmDspRoutineSignalPos:
EcucIntegerParamDef
+subContainer
lowerMultiplicity = 1
DcmDspStopRoutineInSignal: +parameter upperMultiplicity = 1
EcucParamConfContainerDef min = 0 DcmDspRoutineParameterSize:
max = 65535 EcucIntegerParamDef
upperMultiplicity = *
lowerMultiplicity = 1 +parameter lowerMultiplicity = 0
requiresIndex = true upperMultiplicity = 1
min = 0
+subContainer DcmDspArgumentScaling: max = 65535
EcucChoiceContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+literal
BOOLEAN: EcucEnumerationLiteralDef
DcmDspRoutineSignalType:
EcucEnumerationParamDef +literal
UINT8: EcucEnumerationLiteralDef
lowerMultiplicity = 0
upperMultiplicity = 1 +literal
UINT8_N: EcucEnumerationLiteralDef
+literal
SINT8: EcucEnumerationLiteralDef

+literal
SINT8_N: EcucEnumerationLiteralDef
+literal
UINT16: EcucEnumerationLiteralDef

+literal
UINT16_N: EcucEnumerationLiteralDef
+literal
SINT16: EcucEnumerationLiteralDef
+parameter
+literal
SINT16_N: EcucEnumerationLiteralDef
+literal
UINT32: EcucEnumerationLiteralDef

+literal
UINT32_N: EcucEnumerationLiteralDef

+literal
SINT32: EcucEnumerationLiteralDef
+literal
SINT32_N: EcucEnumerationLiteralDef

+literal
FLOAT: EcucEnumerationLiteralDef
+literal
FLOAT_N: EcucEnumerationLiteralDef
+literal
VARIABLE_LENGTH: EcucEnumerationLiteralDef

+literal LITTLE_ENDIAN:
DcmDspRoutineSignalEndianness:
EcucEnumerationLiteralDef
EcucEnumerationParamDef
+parameter
lowerMultiplicity = 0 +literal
OPAQUE:
upperMultiplicity = 1
EcucEnumerationLiteralDef
+literal
BIG_ENDIAN:
EcucEnumerationLiteralDef
+reference DcmDspStopRoutineInSignalCompositeSignalRef:
EcucReferenceDef

lowerMultiplicity = 0
upperMultiplicity = *

Figure 10.50: DcmDspRoutineStopIn configuration overview

10.2.5.19.17 DcmDspStartRoutineOutSignalCompositePool

[ECUC_Dcm_01221] Definition of EcucParamConfContainerDef DcmDspStart

RoutineOutSignalCompositePool d

741 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmDspStartRoutineOutSignalCompositePool

Parent Container DcmDspStartRoutineOut
Description Defines a collection of all contained signals for this root signal.
Post-Build Variant Multiplicity false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStartRoutineOutSignal 1..* Provide description of a routine signal used in RoutineControl
service.
The ordering defined via the index attribute of the subcontainers
in this list represents the order of the dataOutN elements in the
XXX_Start function call.

10.2.5.19.18 DcmDspStopRoutineInSignal

[ECUC_Dcm_00839] Definition of EcucParamConfContainerDef DcmDspStop

RoutineInSignal d
Container Name DcmDspStopRoutineInSignal
Parent Container DcmDspStopRoutineIn, DcmDspStopRoutineInSignalCompositePool
Description Provide description of a routine signal used in RoutineControl service.
The ordering defined via the index attribute of the subcontainers in this list represents
the order of the dataInN elements in the XXX_Stop function call.
Attributes: requiresIndex=true
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspRoutineParameterSize 0..1 [ECUC_Dcm_00841]
DcmDspRoutineSignalEndianness 0..1 [ECUC_Dcm_01014]
DcmDspRoutineSignalPos 1 [ECUC_Dcm_00840]
DcmDspRoutineSignalType 0..1 [ECUC_Dcm_00882]
DcmDspStopRoutineInSignalCompositeSignalRef 0..* [ECUC_Dcm_01224]

742 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspArgumentScaling 0..1 This container contains the configuration (arguments) of an
alternative Diagnosis Representation. Out if this the scaling
between Diagnosis and ECU internal representation and vice
versa can be calculated.

[ECUC_Dcm_00841] Definition of EcucIntegerParamDef DcmDspRoutineParam-

eterSize d
Parameter Name DcmDspRoutineParameterSize
Parent Container DcmDspStopRoutineInSignal
Description Provide the size of a RoutineControl parameter in bytes
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01014] Definition of EcucEnumerationParamDef DcmDspRoutine

SignalEndianness d
Parameter Name DcmDspRoutineSignalEndianness
Parent Container DcmDspStopRoutineInSignal
Description Defines the endianness of the data belonging to a Routine In Signal for Stop
subfunction.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at the lowest
address.
LITTLE_ENDIAN Most significant byte shall be stored at the
highest address
OPAQUE Opaque data endianness
Post-Build Variant Multiplicity false
Post-Build Variant Value false
5

743 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00840] Definition of EcucIntegerParamDef DcmDspRoutineSignal

Pos d
Parameter Name DcmDspRoutineSignalPos
Parent Container DcmDspStopRoutineInSignal
Description Provide the position of the signal in the RoutineControl request/response. The position
is defined in bits.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00882] Definition of EcucEnumerationParamDef DcmDspRoutine

SignalType d
Parameter Name DcmDspRoutineSignalType
Parent Container DcmDspStopRoutineInSignal
Description Provide the type of the signal in the RoutineControl request/response.
Multiplicity 0..1
Type EcucEnumerationParamDef

Range BOOLEAN Type of the signal is boolean.

FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the signal is sint16.
SINT16_N Type of the signal is sint16 array.
SINT32 Type of the signal is sint32.
5

744 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
SINT32_N Type of the signal is sint32 array.
SINT8 Type of the signal is sint8.
SINT8_N Type of the signal is sint8 array.
UINT16 Type of the signal is uint16.
UINT16_N Type of the signal is uint16 array.
UINT32 Type of the signal is uint32.
UINT32_N Type of the signal is uint32 array.
UINT8 Type of the signal is uint8.
UINT8_N Type of the signal is uint8 array.
VARIABLE_LENGTH Type of the signal is uint8[DcmDspRoutine
ParameterSize].
This is only valid for the last signal and when
DcmDspRoutineSignalType is set to VARIABLE_
LENGTH.
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01224] Definition of EcucReferenceDef DcmDspStopRoutineInSig-

nalCompositeSignalRef d
Parameter Name DcmDspStopRoutineInSignalCompositeSignalRef
Parent Container DcmDspStopRoutineInSignal
Description Reference to the contained signal.
Multiplicity 0..*
Type Reference to DcmDspStopRoutineInSignalCompositePool
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

745 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.19.19 DcmDspStopRoutineInSignalCompositePool

[ECUC_Dcm_01223] Definition of EcucParamConfContainerDef DcmDspStop

RoutineInSignalCompositePool d
Container Name DcmDspStopRoutineInSignalCompositePool
Parent Container DcmDspStopRoutineIn
Description Defines a collection of all contained signals for this root signal.
Post-Build Variant Multiplicity false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStopRoutineInSignal 1..* Provide description of a routine signal used in RoutineControl
service.
The ordering defined via the index attribute of the subcontainers
in this list represents the order of the dataInN elements in the
XXX_Stop function call.

10.2.5.19.20 DcmDspStopRoutineOut

[ECUC_Dcm_00833] Definition of EcucParamConfContainerDef DcmDspStop

RoutineOut d
Container Name DcmDspStopRoutineOut
Parent Container DcmDspStopRoutine
Description Provide description of output parameter of Stop subservice for RoutineControl service.
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStopRoutineOutSignal 1..* Provide description of a routine signal used in RoutineControl
service.
The ordering defined via the index attribute of the subcontainers
in this list represents the order of the dataOutN elements in the
XXX_Stop function call.
DcmDspStopRoutineOutSignal 0..* Defines a collection of all contained signals for this root signal.
CompositePool

746 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspStopRoutineOut:
EcucParamConfContainerDef

upperMultiplicity = 1
lowerMultiplicity = 0 DcmDspRoutineSignalPos:
EcucIntegerParamDef

lowerMultiplicity = 1 DcmDspRoutineParameterSize:
+subContainer upperMultiplicity = 1 EcucIntegerParamDef
+parameter min = 0
DcmDspStopRoutineOutSignal: max = 65535 lowerMultiplicity = 0
EcucParamConfContainerDef upperMultiplicity = 1
+parameter min = 0
upperMultiplicity = * max = 65535
lowerMultiplicity = 1
requiresIndex = true
+literal
BOOLEAN: EcucEnumerationLiteralDef
DcmDspRoutineSignalType:
EcucEnumerationParamDef +literal
UINT8: EcucEnumerationLiteralDef
lowerMultiplicity = 0
upperMultiplicity = 1 +literal
UINT8_N: EcucEnumerationLiteralDef

+literal
SINT8: EcucEnumerationLiteralDef

+literal
SINT8_N: EcucEnumerationLiteralDef

+literal
UINT16: EcucEnumerationLiteralDef

+literal
UINT16_N: EcucEnumerationLiteralDef

+literal
SINT16: EcucEnumerationLiteralDef
+parameter +literal
SINT16_N: EcucEnumerationLiteralDef

+literal
UINT32: EcucEnumerationLiteralDef

+literal
UINT32_N: EcucEnumerationLiteralDef

+literal
SINT32: EcucEnumerationLiteralDef

+literal
SINT32_N: EcucEnumerationLiteralDef

+literal
VARIABLE_LENGTH:
EcucEnumerationLiteralDef
+literal
FLOAT_N: EcucEnumerationLiteralDef

+literal
FLOAT: EcucEnumerationLiteralDef

DcmDspRoutineSignalEndianness: +literal LITTLE_ENDIAN:

EcucEnumerationParamDef EcucEnumerationLiteralDef
lowerMultiplicity = 0
upperMultiplicity = 1
+parameter +literal OPAQUE:
EcucEnumerationLiteralDef

+literal BIG_ENDIAN:
EcucEnumerationLiteralDef

DcmDspArgumentScaling:
+subContainer EcucChoiceContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+reference DcmDspStopRoutineOutSignalCompositeSignalRef:
EcucReferenceDef

lowerMultiplicity = 0
upperMultiplicity = *

Figure 10.51: DcmDspStopRoutineOut configuration overview

747 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.19.21 DcmDspStopRoutineOutSignal

[ECUC_Dcm_00842] Definition of EcucParamConfContainerDef DcmDspStop

RoutineOutSignal d
Container Name DcmDspStopRoutineOutSignal
Parent Container DcmDspStopRoutineOut, DcmDspStopRoutineOutSignalCompositePool
Description Provide description of a routine signal used in RoutineControl service.
The ordering defined via the index attribute of the subcontainers in this list represents
the order of the dataOutN elements in the XXX_Stop function call.
Attributes: requiresIndex=true
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspRoutineParameterSize 0..1 [ECUC_Dcm_00844]
DcmDspRoutineSignalEndianness 0..1 [ECUC_Dcm_01015]
DcmDspRoutineSignalPos 1 [ECUC_Dcm_00843]
DcmDspRoutineSignalType 0..1 [ECUC_Dcm_00883]
DcmDspStopRoutineOutSignalCompositeSignalRef 0..* [ECUC_Dcm_01226]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspArgumentScaling 0..1 This container contains the configuration (arguments) of an
alternative Diagnosis Representation. Out if this the scaling
between Diagnosis and ECU internal representation and vice
versa can be calculated.

[ECUC_Dcm_00844] Definition of EcucIntegerParamDef DcmDspRoutineParam-

eterSize d
Parameter Name DcmDspRoutineParameterSize
Parent Container DcmDspStopRoutineOutSignal
Description Provide the size of a RoutineControl parameter in bytes
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
5

748 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_01015] Definition of EcucEnumerationParamDef DcmDspRoutine

SignalEndianness d
Parameter Name DcmDspRoutineSignalEndianness
Parent Container DcmDspStopRoutineOutSignal
Description Defines the endianness of the data belonging to a Routine Out Signal for Stop
subfunction.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range BIG_ENDIAN Most significant byte shall be stored at the lowest
address.
LITTLE_ENDIAN Most significant byte shall be stored at the
highest address
OPAQUE Opaque data endianness
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00843] Definition of EcucIntegerParamDef DcmDspRoutineSignal

Pos d
Parameter Name DcmDspRoutineSignalPos
Parent Container DcmDspStopRoutineOutSignal
Description Provide the position of the signal in the RoutineControl request/response. The position
is defined in bits.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 65535
Default value –
Post-Build Variant Value false
5

749 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00883] Definition of EcucEnumerationParamDef DcmDspRoutine

SignalType d
Parameter Name DcmDspRoutineSignalType
Parent Container DcmDspStopRoutineOutSignal
Description Provide the type of the signal in the RoutineControl request/response.
Multiplicity 0..1
Type EcucEnumerationParamDef
BOOLEAN Type of the signal is boolean.
Range
FLOAT Type of the data is float.
FLOAT_N Type of the data is float array.
SINT16 Type of the signal is sint16.
SINT16_N Type of the signal is sint16 array.
SINT32 Type of the signal is sint32.
SINT32_N Type of the signal is sint32 array.
SINT8 Type of the signal is sint8.
SINT8_N Type of the signal is sint8 array.
UINT16 Type of the signal is uint16.
UINT16_N Type of the signal is uint16 array.
UINT32 Type of the signal is uint32.
UINT32_N Type of the signal is uint32 array.
UINT8 Type of the signal is uint8.
UINT8_N Type of the signal is uint8 array.
VARIABLE_LENGTH Type of the signal is uint8[DcmDspRoutine
ParameterSize].
This is only valid for the last signal and when
DcmDspRoutineSignalType is set to VARIABLE_
LENGTH.
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

750 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01226] Definition of EcucReferenceDef DcmDspStopRoutineOut

SignalCompositeSignalRef d
Parameter Name DcmDspStopRoutineOutSignalCompositeSignalRef
Parent Container DcmDspStopRoutineOutSignal
Description Reference to the contained signal.
Multiplicity 0..*
Type Reference to DcmDspStopRoutineOutSignalCompositePool
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.19.22 DcmDspStopRoutineOutSignalCompositePool

[ECUC_Dcm_01225] Definition of EcucParamConfContainerDef DcmDspStop

RoutineOutSignalCompositePool d
Container Name DcmDspStopRoutineOutSignalCompositePool
Parent Container DcmDspStopRoutineOut
Description Defines a collection of all contained signals for this root signal.
Post-Build Variant Multiplicity false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspStopRoutineOutSignal 1..* Provide description of a routine signal used in RoutineControl
service.
The ordering defined via the index attribute of the subcontainers
in this list represents the order of the dataOutN elements in the
XXX_Stop function call.

751 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.20 Session Security and Modes

10.2.5.20.1 DcmDspSecurity

[ECUC_Dcm_00764] Definition of EcucParamConfContainerDef DcmDspSecurity

d
Container Name DcmDspSecurity
Parent Container DcmDsp
Description This container contains the configuration ( DSP parameter) for security level
configuration (per security level) Description This container contains Rows of DcmDsp
SecurityRow
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspSecurityMaxAttemptCounterReadoutTime 1 [ECUC_Dcm_01101]
DcmDspSecurityResetAttemptCounterOnTimeout 0..1 [ECUC_Dcm_01210]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspSecurityRow 0..31 Definition of a single Row of configuration for security level
configuration (per security level) The name of this container is
used to define the name of the R-Port through which the DCM
accesses the interface SecurityAccess_{SecurityLevel}. The
R-Port is named SecurityAccess_{SecurityLevel} where
{SecurityLevel} is the name of the container DcmDspSecurity
Row. If there is no reference, no check of security level shall be
done.

[ECUC_Dcm_01101] Definition of EcucFloatParamDef DcmDspSecurityMaxAt-

temptCounterReadoutTime d
Parameter Name DcmDspSecurityMaxAttemptCounterReadoutTime
Parent Container DcmDspSecurity
Description Delay, in seconds, from startup (measured from the first call of the Dcm_Main
Function()), allowed for all AttemptCounter values to be obtained from the Application.
Must be a multiple of the DcmTaskTime.
min: A value equal to the DcmTaskTime
Multiplicity 1
Type EcucFloatParamDef
Range ]0 .. 65535[
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
5

752 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01210] Definition of EcucBooleanParamDef DcmDspSecurityReset

AttemptCounterOnTimeout d
Parameter Name DcmDspSecurityResetAttemptCounterOnTimeout
Parent Container DcmDspSecurity
Description This configuration parameter shall control the resetting behavior of SecurityAccess
AttemptCounter upon Delay Timer expiration. If this parameter is false, then it attempts
the SecurityAccess AttemptCounter not to reset when the delay timer expires. And if
the parameter is true, then it attempts the SecurityAccess AttemptCounter to reset
when the delay timer expires.
Multiplicity 0..1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

753 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Dcm: EcucModuleDef DcmDspSecurityRow: DcmDspSecuritySeedSize:

EcucParamConfContainerDef EcucIntegerParamDef
upperMultiplicity = 1
upperMultiplicity = 31 +parameter
lowerMultiplicity = 0 max = 4294967295
lowerMultiplicity = 0 min = 1
lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspSecurityKeySize:
+container EcucIntegerParamDef
+parameter
DcmConfigSet: max = 4294967295
EcucParamConfContainerDef min = 1
lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspSecurityADRSize:
+subContainer EcucIntegerParamDef
+parameter
DcmDsp: lowerMultiplicity = 0
EcucParamConfContainerDef upperMultiplicity = 1
min = 1
lowerMultiplicity = 0 max = 4294967295
upperMultiplicity = 1

DcmDspSecurityUsePort: +literalUSE_ASYNCH_CLIENT_SERVER:
+parameter EcucEnumerationParamDef EcucEnumerationLiteralDef

+subContainer lowerMultiplicity = 1
upperMultiplicity = 1
DcmDspSecurity:
USE_ASYNCH_FNC:
EcucParamConfContainerDef +literal
EcucEnumerationLiteralDef
lowerMultiplicity = 1 +subContainer
upperMultiplicity = 1

DcmDspSecurityGetAttemptCounterFnc:
+parameter EcucFunctionNameDef
+parameter
lowerMultiplicity = 0
DcmDspSecurityMaxAttemptCounterReadoutTime:
upperMultiplicity = 1
EcucFloatParamDef

min = 0
max = 65535
lowerMultiplicity = 1
upperMultiplicity = 1 DcmDspSecuritySetAttemptCounterFnc:
EcucFunctionNameDef
+parameter
+parameter
lowerMultiplicity = 0
DcmDspSecurityResetAttemptCounterOnTimeout: upperMultiplicity = 1
EcucBooleanParamDef

defaultValue = false
lowerMultiplicity = 0
upperMultiplicity = 1
DcmDspSecurityAttemptCounterEnabled:
+parameter EcucBooleanParamDef

DcmDspSecurityLevel: upperMultiplicity = 1
EcucIntegerParamDef lowerMultiplicity = 1

max = 63 +parameter
min = 1
lowerMultiplicity = 1 DcmDspSecurityGetSeedFnc:
upperMultiplicity = 1 EcucFunctionNameDef
+parameter
symbolicNameValue = true
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspSecurityNumAttDelay:
EcucIntegerParamDef
+parameter DcmDspSecurityCompareKeyFnc:
min = 1 +parameter EcucFunctionNameDef
max = 255
lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = 1

DcmDspSecurityDelayTime: DcmDspSecurityDelayTimeOnBoot:
EcucFloatParamDef EcucFloatParamDef
+parameter +parameter
min = 0 min = 0
lowerMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1
max = 65535 max = 65535

Figure 10.52: DcmDspSecurity configuration overview

754 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.20.2 DcmDspSecurityRow

[ECUC_Dcm_00759] Definition of EcucParamConfContainerDef DcmDspSecurity

Row d
Container Name DcmDspSecurityRow
Parent Container DcmDspSecurity
Description Definition of a single Row of configuration for security level configuration (per security
level) The name of this container is used to define the name of the R-Port through
which the DCM accesses the interface SecurityAccess_{SecurityLevel}. The R-Port is
named SecurityAccess_{SecurityLevel} where {SecurityLevel} is the name of the
container DcmDspSecurityRow. If there is no reference, no check of security level shall
be done.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspSecurityADRSize 0..1 [ECUC_Dcm_00725]
DcmDspSecurityAttemptCounterEnabled 1 [ECUC_Dcm_01050]
DcmDspSecurityCompareKeyFnc 0..1 [ECUC_Dcm_00969]
DcmDspSecurityDelayTime 1 [ECUC_Dcm_00757]
DcmDspSecurityDelayTimeOnBoot 1 [ECUC_Dcm_00726]
DcmDspSecurityGetAttemptCounterFnc 0..1 [ECUC_Dcm_01048]
DcmDspSecurityGetSeedFnc 0..1 [ECUC_Dcm_00968]
DcmDspSecurityKeySize 1 [ECUC_Dcm_00760]
DcmDspSecurityLevel 1 [ECUC_Dcm_00754]
DcmDspSecurityNumAttDelay 0..1 [ECUC_Dcm_00762]
DcmDspSecuritySeedSize 1 [ECUC_Dcm_00755]
DcmDspSecuritySetAttemptCounterFnc 0..1 [ECUC_Dcm_01049]
DcmDspSecurityUsePort 1 [ECUC_Dcm_00967]

No Included Containers

[ECUC_Dcm_00725] Definition of EcucIntegerParamDef DcmDspSecurityADR-

Size d
Parameter Name DcmDspSecurityADRSize
Parent Container DcmDspSecurityRow
Description Size in bytes of the AccessDataRecord used in GetSeed
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 4294967295
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
5

755 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01050] Definition of EcucBooleanParamDef DcmDspSecurityAt-

temptCounterEnabled d
Parameter Name DcmDspSecurityAttemptCounterEnabled
Parent Container DcmDspSecurityRow
Description This configuration parameter controls the existence of the APIs to set / get the attempt
counter values towards application (Xxx_SetSecurityAttemptCounter() / Xxx_Get
SecurityAttemptCounter()). In case of enabled, the security attempt counter values are
passed to application, whenever there is a change in the value. This allows storing the
values in nonvolatile RAM and restoring them at ECU startup.
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00969] Definition of EcucFunctionNameDef DcmDspSecurityCom-

pareKeyFnc d
Parameter Name DcmDspSecurityCompareKeyFnc
Parent Container DcmDspSecurityRow
Description Function name to request the result of a key comparison.
Parameter is only relevant if DcmDspSecurityUsePort=="USE_ ASYNCH_FNC". This
parameter is related to the interface Xxx_CompareKey.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
5

756 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00757] Definition of EcucFloatParamDef DcmDspSecurityDelay

Time d
Parameter Name DcmDspSecurityDelayTime
Parent Container DcmDspSecurityRow
Description Delay time after failed security access in seconds.
This is started after DcmDspSecurityNumAttDelay number of failed security accesses.
min: A negative value is not allowed.
Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 65535]
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00726] Definition of EcucFloatParamDef DcmDspSecurityDelay

TimeOnBoot d
Parameter Name DcmDspSecurityDelayTimeOnBoot
Parent Container DcmDspSecurityRow
Description Value of the delay timer in case of ’power on’ in seconds. This delay indicates the time
at ECU boot power-on time during which the Dcm does not accept a security access.
min: A negative value is not allowed.
Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 65535]
Default value –
Post-Build Variant Value false
5

757 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01048] Definition of EcucFunctionNameDef DcmDspSecurityGetAt-

temptCounterFnc d
Parameter Name DcmDspSecurityGetAttemptCounterFnc
Parent Container DcmDspSecurityRow
Description Function name to request the value of an attempt counter. This parameter is related to
the interface Xxx_ GetSecurityAttemptCounter.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00968] Definition of EcucFunctionNameDef DcmDspSecurityGet

SeedFnc d
Parameter Name DcmDspSecurityGetSeedFnc
Parent Container DcmDspSecurityRow
Description Callout function name used to request a seed. This parameter is related to the
interface Xxx_GetSeed.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
5

758 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00760] Definition of EcucIntegerParamDef DcmDspSecurityKey

Size d
Parameter Name DcmDspSecurityKeySize
Parent Container DcmDspSecurityRow
Description size of the security key (in Bytes).
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 4294967295
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00754] Definition of EcucIntegerParamDef DcmDspSecurityLevel d

Parameter Name DcmDspSecurityLevel
Parent Container DcmDspSecurityRow
Description Value of Security level. The locked state cannot be configured explicitly.
1,2,3...63: configuration dependent - Conversion formula to calculate SecurityLevel out
of tester requested
SecurityAccessType parameter: SecurityLevel = (SecurityAccessType (requestSeed) +
1) / 2
Type: Dcm_SecLevelType
Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 1 .. 63
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
5

759 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Scope / Dependency scope: local

[ECUC_Dcm_00762] Definition of EcucIntegerParamDef DcmDspSecurityNumAtt

Delay d
Parameter Name DcmDspSecurityNumAttDelay
Parent Container DcmDspSecurityRow
Description Number of failed security accesses after which the delay time is activated
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00755] Definition of EcucIntegerParamDef DcmDspSecuritySeed

Size d
Parameter Name DcmDspSecuritySeedSize
Parent Container DcmDspSecurityRow
Description size of the security seed (in Bytes).
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 4294967295
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

760 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01049] Definition of EcucFunctionNameDef DcmDspSecuritySetAt-

temptCounterFnc d
Parameter Name DcmDspSecuritySetAttemptCounterFnc
Parent Container DcmDspSecurityRow
Description Function name to set the value of an attempt counter. This parameter is related to the
interface Xxx_ SetSecurityAttemptCounter.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00967] Definition of EcucEnumerationParamDef DcmDspSecurity

UsePort d
Parameter Name DcmDspSecurityUsePort
Parent Container DcmDspSecurityRow
Description Defines which kind of interface shall be used for security access.
Multiplicity 1
Type EcucEnumerationParamDef
Range USE_ASYNCH_CLIENT_ The DCM will access the data using an R-Port
SERVER requiring a asynchronous ClientServertInterface
SecurityAccess_{SecurityLevel}.
The R-Port is described in DcmDspSecurityRow
description.
USE_ASYNCH_FNC The DCM will access the data using the functions
that are defined in the parameters DcmDsp
SecurityGetSeedFnc and DcmDspSecurity
CompareKeyFnc as well as the functions defined
in DcmDspSecurityGetAttemptCounterFnc and
DcmDspSecuritySetAttemptCounterFnc, if
enabled by the parameter DcmDspSecurity
AttemptCounterEnabled.
DCM_E_PENDING return is allowed and Op
Status is existing as IN parameter.
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
5

761 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-build time –
Scope / Dependency scope: local

10.2.5.20.3 DcmDspSession

[ECUC_Dcm_00769] Definition of EcucParamConfContainerDef DcmDspSession

d
Container Name DcmDspSession
Parent Container DcmDsp
Description Parent container holding single rows to configure particular sessions
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspSessionRow 0..31 This container holds all parameters needed to configure a single
session

762 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp: DcmDspSessionRow: DcmDspSessionLevel:

EcucParamConfContainerDef EcucParamConfContainerDef EcucIntegerParamDef

lowerMultiplicity = 0 upperMultiplicity = 31 +parameter max = 126

upperMultiplicity = 1 lowerMultiplicity = 0 min = 1
lowerMultiplicity = 1
upperMultiplicity = 1
symbolicNameValue = true

+subContainer
DcmDspSessionP2StarServerMax:
DcmDspSession:
EcucFloatParamDef
EcucParamConfContainerDef
+parameter
+subContainer min = 0
lowerMultiplicity = 1
lowerMultiplicity = 1
upperMultiplicity = 1
upperMultiplicity = 1
max = 100

DcmDspSessionP2ServerMax:
EcucFloatParamDef
+parameter
min = 0
lowerMultiplicity = 1
upperMultiplicity = 1
max = 1

+parameter

DcmDspSessionForBoot: +literal DCM_NO_BOOT:

EcucEnumerationParamDef EcucEnumerationLiteralDef

defaultValue = DCM_NO_BOOT
lowerMultiplicity = 1
upperMultiplicity = 1
+literal DCM_OEM_BOOT:
EcucEnumerationLiteralDef

+literal DCM_SYS_BOOT:
EcucEnumerationLiteralDef

+literal DCM_OEM_BOOT_RESPAPP:
EcucEnumerationLiteralDef

+literal DCM_SYS_BOOT_RESPAPP:
EcucEnumerationLiteralDef

Figure 10.53: DcmDspSession configuration overview

10.2.5.20.4 DcmDspSessionRow

[ECUC_Dcm_00767] Definition of EcucParamConfContainerDef DcmDspSession

Row d
Container Name DcmDspSessionRow
Parent Container DcmDspSession
Description This container holds all parameters needed to configure a single session
Configuration Parameters

763 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspSessionForBoot 1 [ECUC_Dcm_00815]
DcmDspSessionLevel 1 [ECUC_Dcm_00765]
DcmDspSessionP2ServerMax 1 [ECUC_Dcm_00766]
DcmDspSessionP2StarServerMax 1 [ECUC_Dcm_00768]

No Included Containers

[ECUC_Dcm_00815] Definition of EcucEnumerationParamDef DcmDspSession

ForBoot d
Parameter Name DcmDspSessionForBoot
Parent Container DcmDspSessionRow
Description This parameter defines whether this diagnostic session allows to jump to Bootloader
(OEM Bootloader or System Supplier Bootloader) and determines, from which unit the
final response will be sent. If this diagnostic session doesn’t allow to jump to
Bootloader the value DCM_NO_BOOT shall be chosen.
Multiplicity 1
Type EcucEnumerationParamDef
Range DCM_NO_BOOT This diagnostic session doesn’t allow to jump to
Bootloader.
DCM_OEM_BOOT This diagnostic session allows to jump to OEM
Bootloader and bootloader sends final response.
DCM_OEM_BOOT_RESPAPP This diagnostic session allows to jump to OEM
Bootloader and application sends final response.
DCM_SYS_BOOT This diagnostic session allows to jump to System
Supplier Bootloader and bootloader sends final
response.
DCM_SYS_BOOT_RESPAPP This diagnostic session allows to jump to System
Supplier Bootloader and application sends final
response.
Default value DCM_NO_BOOT
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

764 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00765] Definition of EcucIntegerParamDef DcmDspSessionLevel d

Parameter Name DcmDspSessionLevel
Parent Container DcmDspSessionRow
Description subFunction value of the DiagnosticSession.
0, 127 and all values above 127 are reserved by ISO
Multiplicity 1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 1 .. 126
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00766] Definition of EcucFloatParamDef DcmDspSessionP2Server

Max d
Parameter Name DcmDspSessionP2ServerMax
Parent Container DcmDspSessionRow
Description This is the session value for P2ServerMax in seconds (per Session). The AUTOSAR
configuration standard is to use SI units, so this parameter is defined as a float value in
seconds. DCM configuration tools must convert this float value to the appropriate value
format for the use in the software implementation of DCM. This value is reported to the
tester within the response to the ’Session Control’ service.
Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 1]
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

765 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00768] Definition of EcucFloatParamDef DcmDspSessionP2Star

ServerMax d
Parameter Name DcmDspSessionP2StarServerMax
Parent Container DcmDspSessionRow
Description This is the session value for P2*ServerMax in seconds (per Session). The AUTOSAR
configuration standard is to use SI units, so this parameter is defined as a float value in
seconds. DCM configuration tools must convert this float value to the appropriate value
format for the use in the software implementation of DCM. This value is reported to the
tester within the response to the ’Session Control’ service.
Multiplicity 1
Type EcucFloatParamDef
Range [0 .. 100]
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

10.2.5.20.5 DcmModeCondition

[ECUC_Dcm_00928] Definition of EcucParamConfContainerDef DcmModeCondi-

tion d
Container Name DcmModeCondition
Parent Container DcmProcessingConditions
Description This container contains the configuration of a mode condition or an environmental
conditions which can be used as argument in DcmModeRules.
One DcmModeCondition shall contain either one DcmSwcModeRef or one DcmBsw
ModeRef or one DcmSwcSRDataElementRef.
Please note that the Dcm acts as well as mode manager. Therefore the references
DcmSwcModeRef or one DcmBswModeRef. might point to provided ModeDeclaration
GroupPrototypes of the Dcm itself as well as to provided ModeDeclarationGroup
Prototypes of other Bsw Modules or software components.
In case of a configured DcmSwcModeRef or DcmBswModeRef only the DcmCondition
Type DCM_EQUALS or DCM_EQUALS_NOT are applicable.
In case of DcmSwcSRDataElementRef all literals of DcmConditionType are possible.
Configuration Parameters

766 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmConditionType 1 [ECUC_Dcm_00929]
DcmBswModeRef 0..1 [ECUC_Dcm_00931]
DcmModeConditionCertificateCompareElementRef 0..1 [ECUC_Dcm_01179]
DcmSwcModeRef 0..1 [ECUC_Dcm_00930]
DcmSwcSRDataElementRef 0..1 [ECUC_Dcm_01037]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmSwcDataElementValue 1 This container contains the configuration of a compare value.

[ECUC_Dcm_00929] Definition of EcucEnumerationParamDef DcmCondition

Type d
Parameter Name DcmConditionType
Parent Container DcmModeCondition
Description This parameter specifies what kind of comparison that is made for the evaluation of the
mode condition.
Multiplicity 1
Type EcucEnumerationParamDef

Range DCM_EQUALS –
DCM_EQUALS_NOT –
DCM_GREATER_OR_EQUAL –
DCM_GREATER_THAN –
DCM_LESS_OR_EQUAL –
DCM_LESS_THAN –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00931] Definition of EcucInstanceReferenceDef DcmBswModeRef

d
Parameter Name DcmBswModeRef
Parent Container DcmModeCondition
Description This parameter references a mode of a ModeDeclarationGroupPrototype provided by a
Basic Software Module used for the condition.
Please note that such ModeDeclarationGroupPrototype are owned by a Basic Software
Module Description in the role providedModeGroup.
Multiplicity 0..1
5

767 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Type Instance reference to MODE-DECLARATION context:
MODE-DECLARATION-GROUP-PROTOTYPE
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01179] Definition of EcucReferenceDef DcmModeConditionCertifi-

cateCompareElementRef d
Parameter Name DcmModeConditionCertificateCompareElementRef
Parent Container DcmModeCondition
Description Reference to a certificate data element that provides the compare value.
Multiplicity 0..1
Type Symbolic name reference to KeyMCertificateElement
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00930] Definition of EcucInstanceReferenceDef DcmSwcModeRef

d
Parameter Name DcmSwcModeRef
Parent Container DcmModeCondition
Description This parameter references a mode in a particular mode request port of a software
component that is used for the condition.
Multiplicity 0..1
Type Instance reference to MODE-DECLARATION context:
ROOT-SW-COMPOSITION-PROTOTYPE SW-COMPONENT-PROTOTYPE
P-PORT-PROTOTYPE MODE-DECLARATION-GROUP-PROTOTYPE
Post-Build Variant Multiplicity false
Post-Build Variant Value false
5

768 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01037] Definition of EcucChoiceReferenceDef DcmSwcSRDataEle-

mentRef d
Parameter Name DcmSwcSRDataElementRef
Parent Container DcmModeCondition
Description Reference to environmental conditions. It is possible to reference a S/R Receiver-Port
to read physical values and compare (equal, greater, less,...) them with a configured
value that is defined by DcmSwcDataElementValue.
Multiplicity 0..1
Type Choice reference to [ DcmDspExternalSRDataElementClass, DcmDspPidService01
ExternalSRDataElementClass ]
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

10.2.5.20.6 DcmSwcDataElementValue

[ECUC_Dcm_01123] Definition of EcucChoiceContainerDef DcmSwcDataEle-

mentValue d
Choice Container Name DcmSwcDataElementValue
Parent Container DcmModeCondition
Description This container contains the configuration of a compare value.

No Included Parameters

769 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Choices
Container Name Multiplicity Scope / Dependency
DcmSwcDataElementArray 0..1 This container contains the configuration of a array compare
value.
DcmSwcDataElementPrimitive 0..1 This container contains the configuration of a primitive compare
value.

10.2.5.20.7 DcmSwcDataElementPrimitive

[ECUC_Dcm_01124] Definition of EcucParamConfContainerDef DcmSwcDataEl-

ementPrimitive d
Container Name DcmSwcDataElementPrimitive
Parent Container DcmSwcDataElementValue
Description This container contains the configuration of a primitive compare value.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmSwcDataElementPrimitiveValue 1 [ECUC_Dcm_01126]

No Included Containers

[ECUC_Dcm_01126] Definition of EcucIntegerParamDef DcmSwcDataElement

PrimitiveValue d
Parameter Name DcmSwcDataElementPrimitiveValue
Parent Container DcmSwcDataElementPrimitive
Description Primitive compare value.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 18446744073709551615
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency

770 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.20.8 DcmSwcDataElementArray

[ECUC_Dcm_01125] Definition of EcucParamConfContainerDef DcmSwcDataEl-

ementArray d
Container Name DcmSwcDataElementArray
Parent Container DcmSwcDataElementValue
Description This container contains the configuration of a array compare value.
Configuration Parameters

No Included Parameters

Included Containers
Container Name Multiplicity Scope / Dependency
DcmSwcDataElementArray 0..* This container contains the configuration of a array element
Element compare value.

10.2.5.20.9 DcmSwcDataElementArrayElement

[ECUC_Dcm_01129] Definition of EcucParamConfContainerDef DcmSwcDataEl-

ementArrayElement d
Container Name DcmSwcDataElementArrayElement
Parent Container DcmSwcDataElementArray
Description This container contains the configuration of a array element compare value.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmSwcDataElementArrayElementIndex 1 [ECUC_Dcm_01127]
DcmSwcDataElementArrayElementValue 1 [ECUC_Dcm_01128]

No Included Containers

771 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01127] Definition of EcucIntegerParamDef DcmSwcDataElementAr-

rayElementIndex d
Parameter Name DcmSwcDataElementArrayElementIndex
Parent Container DcmSwcDataElementArrayElement
Description Index to an element of the compare value array.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 18446744073709551615
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency

[ECUC_Dcm_01128] Definition of EcucIntegerParamDef DcmSwcDataElementAr-

rayElementValue d
Parameter Name DcmSwcDataElementArrayElementValue
Parent Container DcmSwcDataElementArrayElement
Description Value of an array element compare value.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 18446744073709551615
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency

10.2.5.20.10 DcmModeRule

[ECUC_Dcm_00925] Definition of EcucParamConfContainerDef DcmModeRule d

772 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmModeRule

Parent Container DcmProcessingConditions
Description This container contains the configuration of a mode rule which represents a logical
expression with DcmModeConditions or other DcmModeRules as arguments.
All arguments are processed with the operator defined by DcmLogicalOperator, for
instance: Argument_A AND Argument_B AND Argument_C
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmLogicalOperator 0..1 [ECUC_Dcm_00926]
DcmModeRuleNrcValue 0..1 [ECUC_Dcm_00949]
DcmArgumentRef 1..* [ECUC_Dcm_00927]

No Included Containers

[ECUC_Dcm_00926] Definition of EcucEnumerationParamDef DcmLogicalOper-

ator d
Parameter Name DcmLogicalOperator
Parent Container DcmModeRule
Description This parameter specifies the logical operator to be used in the logical expression. If the
expression only consists of a single condition this parameter shall not be used.
Multiplicity 0..1
Type EcucEnumerationParamDef
Range DCM_AND –
DCM_OR –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

773 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00949] Definition of EcucIntegerParamDef DcmModeRuleNrcValue

d
Parameter Name DcmModeRuleNrcValue
Parent Container DcmModeRule
Description Optional parameter which defines the NRC to be sent in case the mode rule condition
is not valid.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 1 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00927] Definition of EcucChoiceReferenceDef DcmArgumentRef d

Parameter Name DcmArgumentRef
Parent Container DcmModeRule
Description This is a choice reference either to a mode condition or a an other mode rule serving
as sub-expression.
Attributes: requiresIndex=true
Multiplicity 1..*
Type Choice reference to [ DcmModeCondition, DcmModeRule ]
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

774 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDspComControlCommunicationReEnableModeRuleRef: DcmModeRule:
EcucReferenceDef +destination EcucParamConfContainerDef

lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = *

DcmDspCommonAuthorizationModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspWriteMemoryRangeModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidReadModeRuleRef: EcucReferenceDef
+destination
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDsdSidTabModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspControlDTCSettingReEnableModeRuleRef:
EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspReadMemoryRangeModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspClearDTCModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidWriteModeRuleRef:
EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspDidControlModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

DcmDsdSubServiceModeRuleRef:
EcucReferenceDef +destination

lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.54: DcmModeRuleUsage configuration overview

775 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.21 DcmDspVehInfo

[ECUC_Dcm_00630] Definition of EcucParamConfContainerDef DcmDspVehInfo

d
Container Name DcmDspVehInfo
Parent Container DcmDsp
Description This container contains the configuration (parameters) for one single VehicleInfoType of
service $09
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspVehInfoInfoType 1 [ECUC_Dcm_00631]
DcmDspVehInfoNODIProvResp 0..1 [ECUC_Dcm_01051]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmDspVehInfoData 1..* Data Item of an InfoType; ShortName is post-fix of the port
interface name.

[ECUC_Dcm_00631] Definition of EcucIntegerParamDef DcmDspVehInfoInfo

Type d
Parameter Name DcmDspVehInfoInfoType
Parent Container DcmDspVehInfo
Description value of InfoType.
Within each DcmConfigSet all DcmDspVehInfoInfoType values shall be unique.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

776 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01051] Definition of EcucBooleanParamDef DcmDspVehInfo

NODIProvResp d
Parameter Name DcmDspVehInfoNODIProvResp
Parent Container DcmDspVehInfo
Description Indicate the Dcm, which side is responsible to fill the number of data items (NODI),
Dcm or the provider of the InfoType data. In case the responsibility is on provider side,
only one DcmDspVehInfoData container is allowed.
• true: Provider is responsible for providing the number of data items parameter
• false or not existing: Dcm is responsible for providing the number of data items
parameter
Multiplicity 0..1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

DcmDsp:
EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspVehInfo: DcmDspVehInfoInfoType:
EcucParamConfContainerDef EcucIntegerParamDef
+parameter
upperMultiplicity = * lowerMultiplicity = 1
lowerMultiplicity = 0 upperMultiplicity = 1
min = 0
max = 255

DcmDspVehInfoDataReadFnc:
DcmDspVehInfoData: +parameter EcucFunctionNameDef
EcucParamConfContainerDef
lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = 1
lowerMultiplicity = 1

DcmDspVehInfoDataSize:
EcucIntegerParamDef
+parameter lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
+subContainer max = 255

DcmDspVehInfoDataOrder:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 255

DcmDspVehInfoDataUsePort:
+parameter EcucBooleanParamDef

lowerMultiplicity = 1
upperMultiplicity = 1

DcmDspVehInfoNODIProvResp:
EcucBooleanParamDef
+parameter
upperMultiplicity = 1
lowerMultiplicity = 0
defaultValue = false

Figure 10.55: DcmDspVehInfo configuration overview

777 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.22 DcmDspVehInfoData

[ECUC_Dcm_00888] Definition of EcucParamConfContainerDef DcmDspVehInfo

Data d
Container Name DcmDspVehInfoData
Parent Container DcmDspVehInfo
Description Data Item of an InfoType; ShortName is post-fix of the port interface name.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspVehInfoDataOrder 1 [ECUC_Dcm_00891]
DcmDspVehInfoDataReadFnc 0..1 [ECUC_Dcm_00889]
DcmDspVehInfoDataSize 1 [ECUC_Dcm_00890]
DcmDspVehInfoDataUsePort 1 [ECUC_Dcm_00727]

No Included Containers

[ECUC_Dcm_00891] Definition of EcucIntegerParamDef DcmDspVehInfoDataOr-

der d
Parameter Name DcmDspVehInfoDataOrder
Parent Container DcmDspVehInfoData
Description Defines the order of the data item in the InfoType; values: 0..255; first data item having
the order number 0; the next 1 and so on. The configuration of order needs to be
unique per InfoType.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

778 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00889] Definition of EcucFunctionNameDef DcmDspVehInfoData

ReadFnc d
Parameter Name DcmDspVehInfoDataReadFnc
Parent Container DcmDspVehInfoData
Description Callout function name for reading InfoType data item. Only required in case parameter
’DcmDspVehInfoDataUsePort’ is set to ’false’
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00890] Definition of EcucIntegerParamDef DcmDspVehInfoData

Size d
Parameter Name DcmDspVehInfoDataSize
Parent Container DcmDspVehInfoData
Description Size in bytes of the InfoType data item.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

779 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00727] Definition of EcucBooleanParamDef DcmDspVehInfoData

UsePort d
Parameter Name DcmDspVehInfoDataUsePort
Parent Container DcmDspVehInfoData
Description When this parameter is set to true the DCM will access the Data using an R-Port
requiring a PortInterface IInfotypeServices_{VehInfoData}. The R-Port is named
InfotypeServices_{VehInfoData} where {VEHINFODATA} is the name of the container
DcmDspVehInfoData. In that case, the DcmDspVehInfoDataReadFnc is ignored and
the RTE APIs are used.
When this parameter is set to false, the DCM calls the function defined in DcmDspVeh
InfoDataReadFnc.
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

10.2.5.23 DcmDspPeriodicTransmission

[ECUC_Dcm_00957] Definition of EcucParamConfContainerDef DcmDspPeriodic

Transmission d
Container Name DcmDspPeriodicTransmission
Parent Container DcmDsp
Description This container contains the configuration (parameters) for Periodic Transmission
Scheduler.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspMaxPeriodicDidScheduler 1 [ECUC_Dcm_00962]
DcmDspPeriodicTransmissionFastRate 0..1 [ECUC_Dcm_00960]
DcmDspPeriodicTransmissionMaxPeriodicFast 0..1 [ECUC_Dcm_01182]
Transmissions
DcmDspPeriodicTransmissionMaxPeriodicMedium 0..1 [ECUC_Dcm_01181]
Transmissions
DcmDspPeriodicTransmissionMaxPeriodicSlow 0..1 [ECUC_Dcm_01183]
Transmissions
DcmDspPeriodicTransmissionMediumRate 0..1 [ECUC_Dcm_00959]
DcmDspPeriodicTransmissionSchedulerType 1 [ECUC_Dcm_01180]
DcmDspPeriodicTransmissionSlowRate 0..1 [ECUC_Dcm_00958]

No Included Containers

780 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00962] Definition of EcucIntegerParamDef DcmDspMaxPeriodicDid

Scheduler d
Parameter Name DcmDspMaxPeriodicDidScheduler
Parent Container DcmDspPeriodicTransmission
Description Defines the maximum number of periodicDataIdentifiers that can be scheduled
concurrently.
Multiplicity 1
Type EcucIntegerParamDef
Range 1 .. 255
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00960] Definition of EcucFloatParamDef DcmDspPeriodicTrans-

missionFastRate d
Parameter Name DcmDspPeriodicTransmissionFastRate
Parent Container DcmDspPeriodicTransmission
Description This parameter give the transmission rate of the requested periodicDataIdentifiers to be
used if the parameter transmissionMode given in the ReadDataByPeriodicID request is
equal to 0x03 ("sendAtFastRate"). This parameter value in seconds have to be
configured as a multiple of DcmTaskTime.
min: A negative value and zero is not allowed.
Multiplicity 0..1
Type EcucFloatParamDef
Range [1E-4 .. 1]
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

781 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01182] Definition of EcucIntegerParamDef DcmDspPeriodicTrans-

missionMaxPeriodicFastTransmissions d
Parameter Name DcmDspPeriodicTransmissionMaxPeriodicFastTransmissions
Parent Container DcmDspPeriodicTransmission
Description Defines the maximum number of periodic connections used for fast transmission.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01181] Definition of EcucIntegerParamDef DcmDspPeriodicTrans-

missionMaxPeriodicMediumTransmissions d
Parameter Name DcmDspPeriodicTransmissionMaxPeriodicMediumTransmissions
Parent Container DcmDspPeriodicTransmission
Description Defines the maximum number of periodic connections used for medium transmission.
Multiplicity 0..1
Type EcucIntegerParamDef
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01183] Definition of EcucIntegerParamDef DcmDspPeriodicTrans-

missionMaxPeriodicSlowTransmissions d
Parameter Name DcmDspPeriodicTransmissionMaxPeriodicSlowTransmissions
Parent Container DcmDspPeriodicTransmission
Description Defines the maximum number of periodic connections used for slow transmission.
Multiplicity 0..1
Type EcucIntegerParamDef
5

782 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Range 0 .. 255
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00959] Definition of EcucFloatParamDef DcmDspPeriodicTrans-

missionMediumRate d
Parameter Name DcmDspPeriodicTransmissionMediumRate
Parent Container DcmDspPeriodicTransmission
Description This parameter give the transmission rate of the requested periodicDataIdentifiers to be
used if the parameter transmissionMode given in the ReadDataByPeriodicID request is
equal to 0x02 ("sendAtMediumRate"). This parameter value in seconds have to be
configured as a multiple of DcmTaskTime.
min: A negative value and zero is not allowed.
Multiplicity 0..1
Type EcucFloatParamDef
Range [1E-4 .. 1]
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01180] Definition of EcucEnumerationParamDef DcmDspPeriodic

TransmissionSchedulerType d
Parameter Name DcmDspPeriodicTransmissionSchedulerType
Parent Container DcmDspPeriodicTransmission
Description Defines the used scheduler type according to ISO 14229-1:2018 for read data by
periodic identifier.
Multiplicity 1
Type EcucEnumerationParamDef
5

783 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Range SCHEDULER_TYPE1 Selects the scheduler type#1 of ISO
14229-1:2018
SCHEDULER_TYPE2 Selects the scheduler type#2 of ISO
14229-1:2018
Default value SCHEDULER_TYPE1
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00958] Definition of EcucFloatParamDef DcmDspPeriodicTrans-

missionSlowRate d
Parameter Name DcmDspPeriodicTransmissionSlowRate
Parent Container DcmDspPeriodicTransmission
Description This parameter give the transmission rate of the requested periodicDataIdentifiers to be
used if the parameter transmissionMode given in the ReadDataByPeriodicID request is
equal to 0x01 ("sendAtSlowRate"). This parameter value in seconds have to be
configured as a multiple of DcmTaskTime.
min: A negative value and zero is not allowed.
Multiplicity 0..1
Type EcucFloatParamDef
Range [1E-4 .. 1]
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

784 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDsp: EcucParamConfContainerDef DcmDspPeriodicTransmission:

DcmDspPeriodicTransmissionSlowRate:
EcucParamConfContainerDef
lowerMultiplicity = 0 EcucFloatParamDef
upperMultiplicity = 1 lowerMultiplicity = 0 +parameter
min = 0.0001
upperMultiplicity = 1
max = 1
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPeriodicTransmissionMediumRate:
EcucFloatParamDef
+parameter
min = 0.0001
max = 1
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPeriodicTransmissionFastRate:
EcucFloatParamDef
+parameter
min = 0.0001
max = 1
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspMaxPeriodicDidScheduler:
EcucIntegerParamDef
+parameter
lowerMultiplicity = 1
upperMultiplicity = 1
min = 1
max = 255

+subContainer
DcmDspPeriodicTransmissionSchedulerType:
EcucEnumerationParamDef

+parameter defaultValue = SCHEDULER_TYPE1

lowerMultiplicity = 1
upperMultiplicity = 1

+literal +literal

SCHEDULER_TYPE2: SCHEDULER_TYPE1:
EcucEnumerationLiteralDef EcucEnumerationLiteralDef

DcmDspPeriodicTransmissionMaxPeriodicFastTransmissions:
EcucIntegerParamDef
+parameter
min = 0
max = 255
lowerMultiplicity = 0
upperMultiplicity = 1

DcmDspPeriodicTransmissionMaxPeriodicMediumTransmissions:
EcucIntegerParamDef
+parameter
min = 0
max = 255
lowerMultiplicity = 0
upperMultiplicity = 1

+parameter
DcmDspPeriodicTransmissionMaxPeriodicSlowTransmissions:
EcucIntegerParamDef

min = 0
max = 255
lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.56: DcmDspPeriodicTransmission configuration overview

785 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.5.24 DcmDspClearDTC

[ECUC_Dcm_01064] Definition of EcucParamConfContainerDef DcmDspClear

DTC d
Container Name DcmDspClearDTC
Parent Container DcmDsp
Description This container contains the configuration for the Clear DTC service.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDspClearDTCCheckFnc 0..1 [ECUC_Dcm_01066]
DcmDspClearDTCModeRuleRef 0..1 [ECUC_Dcm_01065]

No Included Containers

[ECUC_Dcm_01066] Definition of EcucFunctionNameDef DcmDspClearDTC-

CheckFnc d
Parameter Name DcmDspClearDTCCheckFnc
Parent Container DcmDspClearDTC
Description Callback function for condition check, manufacturer / supplier specific checks on the
groupOfDTC, which is requested to clear.
This parameter is related to the interface : Xxx_ClearDTCCheckFnc.
Multiplicity 0..1
Type EcucFunctionNameDef
Default value –
Regular Expression –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

786 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01065] Definition of EcucReferenceDef DcmDspClearDTCMode

RuleRef d
Parameter Name DcmDspClearDTCModeRuleRef
Parent Container DcmDspClearDTC
Description Reference to DcmModeRule
Mode rule which controls to clear the DTCs. If there is no reference, no check of the
mode rule shall be done.
Multiplicity 0..1
Type Reference to DcmModeRule
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: ECU

DcmDsp: EcucParamConfContainerDef

lowerMultiplicity = 0
upperMultiplicity = 1

+subContainer

DcmDspClearDTC: DcmDspClearDTCModeRuleRef: DcmModeRule:

EcucParamConfContainerDef +reference EcucReferenceDef +destination EcucParamConfContainerDef
upperMultiplicity = 1 lowerMultiplicity = 0 lowerMultiplicity = 1
lowerMultiplicity = 0 upperMultiplicity = 1 upperMultiplicity = *

DcmDspClearDTCCheckFnc:
+parameter EcucFunctionNameDef

lowerMultiplicity = 0
upperMultiplicity = 1

Figure 10.57: DcmDspClearDTC configuration overview

10.2.6 DcmGeneral

[ECUC_Dcm_00822] Definition of EcucParamConfContainerDef DcmGeneral d

787 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Container Name DcmGeneral

Parent Container Dcm
Description Contains general configuration parameters valid for the entire Dcm module.
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmDDDIDStorage 0..1 [ECUC_Dcm_00971]
DcmDevErrorDetect 1 [ECUC_Dcm_00823]
DcmEnableSecurityEventReporting 1 [ECUC_Dcm_01187]
DcmHeaderFileInclusion 0..* [ECUC_Dcm_01019]
DcmRespondAllRequest 1 [ECUC_Dcm_00600]
DcmS3ServerTimeoutOverwrite 0..1 [ECUC_Dcm_01240]
DcmTaskTime 1 [ECUC_Dcm_00820]
DcmVersionInfoApi 1 [ECUC_Dcm_00821]
DcmVinRef 0..1 [ECUC_Dcm_00984]

Included Containers
Container Name Multiplicity Scope / Dependency
DcmSecureCoding 0..1 Contains references to diagnostic elements that are used for the
secure coding process.
DcmSecurityEventRefs 0..1 Container for the references to IdsMEvent elements representing
the security events that the Dcm module shall report to the IdsM
in case the coresponding security related event occurs (and if
DcmEnableSecurityEventReporting is set to "true"). The
standardized security events in this container can be extended
by vendor-specific security events.
Tags: atp.Status=draft

[ECUC_Dcm_00971] Definition of EcucBooleanParamDef DcmDDDIDStorage d

Parameter Name DcmDDDIDStorage
Parent Container DcmGeneral
Description This configuration switch defines, whether DDDID definition is stored non-volatile or
not.
true: DDDID are stored non-volatile false: DDDID are only maintained volatile
Multiplicity 0..1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
5

788 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00823] Definition of EcucBooleanParamDef DcmDevErrorDetect d

Parameter Name DcmDevErrorDetect
Parent Container DcmGeneral
Description Switches the development error detection and notification on or off.
• true: detection and notification is enabled.
• false: detection and notification is disabled.
Multiplicity 1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01187] Definition of EcucBooleanParamDef DcmEnableSecurity

EventReporting
Status: DRAFT
d
Parameter Name DcmEnableSecurityEventReporting
Parent Container DcmGeneral
Description Switches the reporting of security events to the IdsM: - true: reporting is enabled. -
false: reporting is disabled.
Tags: atp.Status=draft
Multiplicity 1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

789 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01019] Definition of EcucStringParamDef DcmHeaderFileInclusion

d
Parameter Name DcmHeaderFileInclusion
Parent Container DcmGeneral
Description Name of the header file(s) to be included by the Dcm module containing the used
C-callback declarations.
Multiplicity 0..*
Type EcucStringParamDef
Default value –
Regular Expression [a-zA-Z0-9_]([a-zA-Z0-9\._])*
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00600] Definition of EcucBooleanParamDef DcmRespondAllRe-

quest d
Parameter Name DcmRespondAllRequest
Parent Container DcmGeneral
Description If set to FALSE the Dcm will not respond to diagnostic request that contains a service
ID which is in the range from 0x40 to 0x7F or in the range from 0xC0 to 0xFF
(Response IDs).
Multiplicity 1
Type EcucBooleanParamDef
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

790 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01240] Definition of EcucFloatParamDef DcmS3ServerTimeout

Overwrite d
Parameter Name DcmS3ServerTimeoutOverwrite
Parent Container DcmGeneral
Description Time for the server to keep a diagnostic session other than the defaultSession active
while not receiving any diagnostic request message. This parameter overwrites the 5s
recommend value of the S3server timeout in ISO 14229-2.
The parameter value is defined in seconds.
Multiplicity 0..1
Type EcucFloatParamDef
Range [5 .. INF[
Default value –
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

[ECUC_Dcm_00820] Definition of EcucFloatParamDef DcmTaskTime d

Parameter Name DcmTaskTime
Parent Container DcmGeneral
Description Allow to configure the time for the periodic cyclic task. Please note: This configuration
value shall be equal to the value in the RTE module.
The AUTOSAR configuration standard is to use SI units, so this parameter is defined
as float value in seconds. Dcm configuration tools must convert this float value to the
appropriate value format for the use in the software implementation of Dcm.
min: A negative value and zero is not allowed.
upperMultiplicity: Exactly one TaskTime must be specified per configuration.
lowerMultiplicity: Exactly one TaskTime must be specified per configuration.
Multiplicity 1
Type EcucFloatParamDef
Range ]0 .. INF[
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE,
VARIANT-POST-BUILD
Link time X VARIANT-LINK-TIME
Post-build time –
Scope / Dependency scope: local

791 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_00821] Definition of EcucBooleanParamDef DcmVersionInfoApi d

Parameter Name DcmVersionInfoApi
Parent Container DcmGeneral
Description Preprocessor switch to enable or disable the output Version info of the functionality.
Multiplicity 1
Type EcucBooleanParamDef
Default value false
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_00984] Definition of EcucReferenceDef DcmVinRef d

Parameter Name DcmVinRef
Parent Container DcmGeneral
Description Reference to the Did containing the VIN Information.
This parameter is needed for function Dcm_GetVin
Multiplicity 0..1
Type Reference to DcmDspDid
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

792 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmDevErrorDetect: EcucBooleanParamDef DcmGeneral: DcmVersionInfoApi: EcucBooleanParamDef

+parameter EcucParamConfContainerDef +parameter
upperMultiplicity = 1 upperMultiplicity = 1
lowerMultiplicity = 1 lowerMultiplicity = 1 lowerMultiplicity = 1
defaultValue = false upperMultiplicity = 1 defaultValue = false

DcmDDDIDStorage: EcucBooleanParamDef DcmTaskTime: EcucFloatParamDef

upperMultiplicity = 1 +parameter +parameter min = 0

lowerMultiplicity = 0 lowerMultiplicity = 1
defaultValue = false upperMultiplicity = 1
max = INF

DcmS3ServerTimeoutOverwrite: +parameter DcmRespondAllRequest: EcucBooleanParamDef

EcucFloatParamDef upperMultiplicity = 1
+parameter
lowerMultiplicity = 1
min = 5.0
max = INF
lowerMultiplicity = 0
upperMultiplicity = 1
DcmHeaderFileInclusion: EcucStringParamDef
+parameter
lowerMultiplicity = 0
upperMultiplicity = *
DcmVinRef: EcucReferenceDef +reference regularExpression = [a-zA-Z0-9_]([a-zA-Z0-9\._])*

lowerMultiplicity = 0
upperMultiplicity = 1

+parameter DcmEnableSecurityEventReporting:
EcucBooleanParamDef

defaultValue = false

+destination

DcmDspDid: EcucParamConfContainerDef DcmSecurityEventRefs:

+subContainer
EcucParamConfContainerDef
upperMultiplicity = *
lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1
+destination

+subContainer

DcmSecureCoding: DcmSecureCodingDataBufferSize:
DcmSecureCodingDataIdentifier:
+reference EcucParamConfContainerDef EcucIntegerParamDef
EcucReferenceDef
+parameter
lowerMultiplicity = 0 min = 0
lowerMultiplicity = 1
upperMultiplicity = 1 max = 4294967295
upperMultiplicity = *
lowerMultiplicity = 1
upperMultiplicity = 1

DcmSecureCodingValidationRoutine:
EcucReferenceDef +reference
DcmSecureCodingAuthenticationJobRef:
lowerMultiplicity = 1 +reference EcucReferenceDef
upperMultiplicity = 1 lowerMultiplicity = 1
upperMultiplicity = 1
requiresSymbolicNameValue = true

+destination
+destination
DcmDspRoutine:
EcucParamConfContainerDef CsmJob:
EcucParamConfContainerDef
upperMultiplicity = *
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = *

Figure 10.58: DcmGeneral configuration overview

793 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.6.1 DcmSecurityEventRefs

[ECUC_Dcm_01188] Definition of EcucParamConfContainerDef DcmSecurity

EventRefs
Status: DRAFT
d
Container Name DcmSecurityEventRefs
Parent Container DcmGeneral
Description Container for the references to IdsMEvent elements representing the security events
that the Dcm module shall report to the IdsM in case the coresponding security related
event occurs (and if DcmEnableSecurityEventReporting is set to "true"). The
standardized security events in this container can be extended by vendor-specific
security events.
Tags: atp.Status=draft
Post-Build Variant Multiplicity false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
SEV_UDS_AUTHENTICATION_FAILED 0..1 [ECUC_Dcm_01255]
SEV_UDS_AUTHENTICATION_NEEDED 0..1 [ECUC_Dcm_01251]
SEV_UDS_AUTHENTICATION_SUCCESSFUL 0..1 [ECUC_Dcm_01254]
SEV_UDS_CLEAR_DTC_FAILED 0..1 [ECUC_Dcm_01267]
SEV_UDS_CLEAR_DTC_SUCCESSFUL 0..1 [ECUC_Dcm_01266]
SEV_UDS_COMMUNICATION_CONTROL_FAILED 0..1 [ECUC_Dcm_01265]
SEV_UDS_COMMUNICATION_CONTROL_SUCCESSF 0..1 [ECUC_Dcm_01264]
UL
SEV_UDS_CONTROL_DTC_SETTING_FAILED 0..1 [ECUC_Dcm_01269]
SEV_UDS_CONTROL_DTC_SETTING_SUCCESSFUL 0..1 [ECUC_Dcm_01268]
SEV_UDS_ECU_RESET_FAILED 0..1 [ECUC_Dcm_01271]
SEV_UDS_ECU_RESET_SUCCESSFUL 0..1 [ECUC_Dcm_01270]
SEV_UDS_IO_CONTROL_FAILED 0..1 [ECUC_Dcm_01275]
SEV_UDS_IO_CONTROL_SUCCESSFUL 0..1 [ECUC_Dcm_01274]
SEV_UDS_REQUEST_FILE_TRANSFER_FAILED 0..1 [ECUC_Dcm_01263]
SEV_UDS_REQUEST_FILE_TRANSFER_SUCCESSFUL 0..1 [ECUC_Dcm_01262]
SEV_UDS_REQUEST_UP_DOWNLOAD_FAILED 0..1 [ECUC_Dcm_01261]
SEV_UDS_REQUEST_UP_DOWNLOAD_SUCCESSFUL 0..1 [ECUC_Dcm_01260]
SEV_UDS_ROUTINE_CONTROL_FAILED 0..1 [ECUC_Dcm_01273]
SEV_UDS_ROUTINE_CONTROL_SUCCESSFUL 0..1 [ECUC_Dcm_01272]
SEV_UDS_SECURITY_ACCESS_FAILED 0..1 [ECUC_Dcm_01253]
SEV_UDS_SECURITY_ACCESS_NEEDED 0..1 [ECUC_Dcm_01250]
SEV_UDS_SECURITY_ACCESS_SUCCESSFUL 0..1 [ECUC_Dcm_01252]
SEV_UDS_WRITE_DATA_FAILED 0..1 [ECUC_Dcm_01257]
5

794 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Included Parameters
Parameter Name Multiplicity ECUC ID
SEV_UDS_WRITE_DATA_SUCCESSFUL 0..1 [ECUC_Dcm_01256]
SEV_UDS_WRITE_MEMORY_FAILED 0..1 [ECUC_Dcm_01259]
SEV_UDS_WRITE_MEMORY_SUCCESSFUL 0..1 [ECUC_Dcm_01258]

No Included Containers

[ECUC_Dcm_01255] Definition of EcucReferenceDef SEV_UDS_AUTHENTICA-

TION_FAILED d
Parameter Name SEV_UDS_AUTHENTICATION_FAILED
Parent Container DcmSecurityEventRefs
Description Authentication (via Authentication SID 0x29) failed
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01251] Definition of EcucReferenceDef SEV_UDS_AUTHENTICA-

TION_NEEDED d
Parameter Name SEV_UDS_AUTHENTICATION_NEEDED
Parent Container DcmSecurityEventRefs
Description A diagnostic request was received while the required authentication to execute this
service is not given. NRC 0x34 (authenticationRequired) was returned.
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
5

795 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01254] Definition of EcucReferenceDef SEV_UDS_AUTHENTICA-

TION_SUCCESSFUL d
Parameter Name SEV_UDS_AUTHENTICATION_SUCCESSFUL
Parent Container DcmSecurityEventRefs
Description Succesfully authenticated (via Authentication SID 0x29)
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01267] Definition of EcucReferenceDef SEV_UDS_CLEAR_DTC_

FAILED d
Parameter Name SEV_UDS_CLEAR_DTC_FAILED
Parent Container DcmSecurityEventRefs
Description Clearing DTC information has been requested by SID 0x14 ClearDiagnostic
Information, but failed
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

796 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01266] Definition of EcucReferenceDef SEV_UDS_CLEAR_DTC_

SUCCESSFUL d
Parameter Name SEV_UDS_CLEAR_DTC_SUCCESSFUL
Parent Container DcmSecurityEventRefs
Description DTC information has been cleared by SID 0x14 ClearDiagnosticInformation
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01265] Definition of EcucReferenceDef SEV_UDS_COMMUNICA-

TION_CONTROL_FAILED d
Parameter Name SEV_UDS_COMMUNICATION_CONTROL_FAILED
Parent Container DcmSecurityEventRefs
Description The control of a communication has been requested by service SID 0x28
CommunicationControl, but failed
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

797 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01264] Definition of EcucReferenceDef SEV_UDS_COMMUNICA-

TION_CONTROL_SUCCESSFUL d
Parameter Name SEV_UDS_COMMUNICATION_CONTROL_SUCCESSFUL
Parent Container DcmSecurityEventRefs
Description The control of a communication has been requested by service SID 0x28
CommunicationControl successfully
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01269] Definition of EcucReferenceDef SEV_UDS_CONTROL_

DTC_SETTING_FAILED d
Parameter Name SEV_UDS_CONTROL_DTC_SETTING_FAILED
Parent Container DcmSecurityEventRefs
Description Control of DTC setting has been requested by service SID 0x85 ControlDTCSetting,
but failed
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

798 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01268] Definition of EcucReferenceDef SEV_UDS_CONTROL_

DTC_SETTING_SUCCESSFUL d
Parameter Name SEV_UDS_CONTROL_DTC_SETTING_SUCCESSFUL
Parent Container DcmSecurityEventRefs
Description The control of a DTC setting has been requested by service SID 0x85 Control
DTCSetting successfully
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01271] Definition of EcucReferenceDef SEV_UDS_ECU_RESET_

FAILED d
Parameter Name SEV_UDS_ECU_RESET_FAILED
Parent Container DcmSecurityEventRefs
Description ECU Reset has been requested by SID 0x11 ECUReset, but failed
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

799 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01270] Definition of EcucReferenceDef SEV_UDS_ECU_RESET_

SUCCESSFUL d
Parameter Name SEV_UDS_ECU_RESET_SUCCESSFUL
Parent Container DcmSecurityEventRefs
Description ECU has been reset by SID 0x11 ECUReset
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01275] Definition of EcucReferenceDef SEV_UDS_IO_CONTROL_

FAILED d
Parameter Name SEV_UDS_IO_CONTROL_FAILED
Parent Container DcmSecurityEventRefs
Description IOControl operation has been requested by service SID 0x2F InputOutputControlBy
Identifier, but failed
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

800 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01274] Definition of EcucReferenceDef SEV_UDS_IO_CONTROL_

SUCCESSFUL d
Parameter Name SEV_UDS_IO_CONTROL_SUCCESSFUL
Parent Container DcmSecurityEventRefs
Description IOControl operation has been requested by service SID 0x2F InputOutputControlBy
Identifier successfully
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01263] Definition of EcucReferenceDef SEV_UDS_REQUEST_

FILE_TRANSFER_FAILED d
Parameter Name SEV_UDS_REQUEST_FILE_TRANSFER_FAILED
Parent Container DcmSecurityEventRefs
Description A file transfer sequence has been requested with SID 0x38, but failed
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

801 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01262] Definition of EcucReferenceDef SEV_UDS_REQUEST_

FILE_TRANSFER_SUCCESSFUL d
Parameter Name SEV_UDS_REQUEST_FILE_TRANSFER_SUCCESSFUL
Parent Container DcmSecurityEventRefs
Description A file transfer sequence has been requested successfully with SID 0x38
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01261] Definition of EcucReferenceDef SEV_UDS_REQUEST_UP_

DOWNLOAD_FAILED d
Parameter Name SEV_UDS_REQUEST_UP_DOWNLOAD_FAILED
Parent Container DcmSecurityEventRefs
Description An upload / download sequence has been requested with SID 0x34 or SID 0x35, but
failed
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

802 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01260] Definition of EcucReferenceDef SEV_UDS_REQUEST_UP_

DOWNLOAD_SUCCESSFUL d
Parameter Name SEV_UDS_REQUEST_UP_DOWNLOAD_SUCCESSFUL
Parent Container DcmSecurityEventRefs
Description An upload / download sequence has been requested successfully with SID 0x34 or SID
0x35
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01273] Definition of EcucReferenceDef SEV_UDS_ROUTINE_CON-

TROL_FAILED d
Parameter Name SEV_UDS_ROUTINE_CONTROL_FAILED
Parent Container DcmSecurityEventRefs
Description The control of a routine has been requested by service SID 0x31 RoutineControl, but
failed
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

803 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01272] Definition of EcucReferenceDef SEV_UDS_ROUTINE_CON-

TROL_SUCCESSFUL d
Parameter Name SEV_UDS_ROUTINE_CONTROL_SUCCESSFUL
Parent Container DcmSecurityEventRefs
Description The control of a routine has been requested by service SID 0x31 RoutineControl
successfully
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01253] Definition of EcucReferenceDef SEV_UDS_SECURITY_AC-

CESS_FAILED d
Parameter Name SEV_UDS_SECURITY_ACCESS_FAILED
Parent Container DcmSecurityEventRefs
Description Unlocking of the ECU (via Security Access SID 0x27) failed
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

804 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01250] Definition of EcucReferenceDef SEV_UDS_SECURITY_AC-

CESS_NEEDED d
Parameter Name SEV_UDS_SECURITY_ACCESS_NEEDED
Parent Container DcmSecurityEventRefs
Description Tester has sent a diagnostic request without meeting the server’s security level
requirements for that service. NRC 0x33 (securityAccessDenied) was returned.
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01252] Definition of EcucReferenceDef SEV_UDS_SECURITY_AC-

CESS_SUCCESSFUL d
Parameter Name SEV_UDS_SECURITY_ACCESS_SUCCESSFUL
Parent Container DcmSecurityEventRefs
Description Successful unlocked the ECU (via Security Access SID 0x27)
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

805 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01257] Definition of EcucReferenceDef SEV_UDS_WRITE_DATA_

FAILED d
Parameter Name SEV_UDS_WRITE_DATA_FAILED
Parent Container DcmSecurityEventRefs
Description Change of Diagnostic data identifier has been requested by SID 0x2E WriteDataBy
Identifier, but failed
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01256] Definition of EcucReferenceDef SEV_UDS_WRITE_DATA_

SUCCESSFUL d
Parameter Name SEV_UDS_WRITE_DATA_SUCCESSFUL
Parent Container DcmSecurityEventRefs
Description Diagnostic data identifier has been written by SID 0x2E WriteDataByIdentifier
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

806 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01259] Definition of EcucReferenceDef SEV_UDS_WRITE_MEM-

ORY_FAILED d
Parameter Name SEV_UDS_WRITE_MEMORY_FAILED
Parent Container DcmSecurityEventRefs
Description Writting of Data into memory has been requested by SID 0x3D WriteMemoryBy
Address, but failed
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01258] Definition of EcucReferenceDef SEV_UDS_WRITE_MEM-

ORY_SUCCESSFUL d
Parameter Name SEV_UDS_WRITE_MEMORY_SUCCESSFUL
Parent Container DcmSecurityEventRefs
Description Data has been written into memory by SID 0x3D WriteMemoryByAddress
Multiplicity 0..1
Type Symbolic name reference to IdsMEvent
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

807 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmGeneral:
EcucParamConfContainerDef +parameter DcmEnableSecurityEventReporting:
EcucBooleanParamDef
lowerMultiplicity = 1
upperMultiplicity = 1 defaultValue = false

+subContainer

DcmSecurityEventRefs: SEV_UDS_SECURITY_ACCESS_NEEDED: IdsMEvent:

EcucParamConfContainerDef +reference EcucReferenceDef EcucParamConfContainerDef
+destination
lowerMultiplicity = 0 lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1 upperMultiplicity = 65535
requiresSymbolicNameValue = true

SEV_UDS_AUTHENTICATION_NEEDED: EcucReferenceDef
+reference lowerMultiplicity = 0 +destination
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_SECURITY_ACCESS_SUCCESSFUL:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_SECURITY_ACCESS_FAILED:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_AUTHENTICATION_SUCCESSFUL:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_AUTHENTICATION_FAILED: EcucReferenceDef
+reference lowerMultiplicity = 0 +destination
upperMultiplicity = 1
requiresSymbolicNameValue = true

(from IdsM)

Figure 10.59: DcmSecurityEventRefs1 configuration overview

808 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmSecurityEventRefs: IdsMEvent:
EcucParamConfContainerDef SEV_UDS_WRITE_DATA_SUCCESSFUL: EcucParamConfContainerDef
+reference EcucReferenceDef +destination
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 lowerMultiplicity = 0 upperMultiplicity = 65535
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_WRITE_DATA_FAILED: EcucReferenceDef
+reference +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_WRITE_MEMORY_SUCCESSFUL:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_WRITE_MEMORY_FAILED: EcucReferenceDef
+reference +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_REQUEST_UP_DOWNLOAD_SUCCESSFUL:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_REQUEST_UP_DOWNLOAD_FAILED:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_REQUEST_FILE_TRANSFER_SUCCESSFUL:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_REQUEST_FILE_TRANSFER_FAILED:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

(from IdsM)

Figure 10.60: DcmSecurityEventRefs2 configuration overview

809 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

DcmSecurityEventRefs: SEV_UDS_COMMUNICATION_CONTROL_SUCCESSFUL: IdsMEvent:

EcucParamConfContainerDef EcucReferenceDef EcucParamConfContainerDef
+reference +destination
lowerMultiplicity = 0 lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 1 upperMultiplicity = 1 upperMultiplicity = 65535
requiresSymbolicNameValue = true

SEV_UDS_COMMUNICATION_CONTROL_FAILED:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_CLEAR_DTC_SUCCESSFUL: EcucReferenceDef
+reference lowerMultiplicity = 0 +destination
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_CLEAR_DTC_FAILED: EcucReferenceDef
+reference +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_CONTROL_DTC_SETTING_SUCCESSFUL:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_CONTROL_DTC_SETTING_FAILED:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_ECU_RESET_SUCCESSFUL: EcucReferenceDef
+reference +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_ECU_RESET_FAILED: EcucReferenceDef
+reference +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_ROUTINE_CONTROL_SUCCESSFUL:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_ROUTINE_CONTROL_FAILED:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_IO_CONTROL_SUCCESSFUL:
+reference EcucReferenceDef +destination
lowerMultiplicity = 0
upperMultiplicity = 1
requiresSymbolicNameValue = true

SEV_UDS_IO_CONTROL_FAILED: EcucReferenceDef
+reference lowerMultiplicity = 0 +destination
upperMultiplicity = 1
requiresSymbolicNameValue = true

(from IdsM)

Figure 10.61: DcmSecurityEventRefs3 configuration overview

810 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.2.6.2 DcmSecureCoding

[ECUC_Dcm_01245] Definition of EcucParamConfContainerDef DcmSecureCod-

ing d
Container Name DcmSecureCoding
Parent Container DcmGeneral
Description Contains references to diagnostic elements that are used for the secure coding
process.
Post-Build Variant Multiplicity false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Configuration Parameters

Included Parameters
Parameter Name Multiplicity ECUC ID
DcmSecureCodingDataBufferSize 1 [ECUC_Dcm_01247]
DcmSecureCodingAuthenticationJobRef 1 [ECUC_Dcm_01249]
DcmSecureCodingDataIdentifier 1..* [ECUC_Dcm_01246]
DcmSecureCodingValidationRoutine 1 [ECUC_Dcm_01248]

No Included Containers

[ECUC_Dcm_01247] Definition of EcucIntegerParamDef DcmSecureCodingData

BufferSize d
Parameter Name DcmSecureCodingDataBufferSize
Parent Container DcmSecureCoding
Description Provides the size of the Dcm internal buffer to store data during the secure coding
sequence.
Multiplicity 1
Type EcucIntegerParamDef
Range 0 .. 4294967295
Default value –
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU

811 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

[ECUC_Dcm_01249] Definition of EcucReferenceDef DcmSecureCodingAuthen-

ticationJobRef d
Parameter Name DcmSecureCodingAuthenticationJobRef
Parent Container DcmSecureCoding
Description Reference to a CsmJob used to verify the authentication of the secure coding data in
the Csm.
Multiplicity 1
Type Symbolic name reference to CsmJob
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01246] Definition of EcucReferenceDef DcmSecureCodingData

Identifier d
Parameter Name DcmSecureCodingDataIdentifier
Parent Container DcmSecureCoding
Description Refers to a writeable data identifier that requires the secure coding process to write the
data.
Multiplicity 1..*
Type Reference to DcmDspDid
Post-Build Variant Multiplicity false
Post-Build Variant Value false
Multiplicity Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

[ECUC_Dcm_01248] Definition of EcucReferenceDef DcmSecureCodingValida-

tionRoutine d
Parameter Name DcmSecureCodingValidationRoutine
Parent Container DcmSecureCoding
Description Refers to a routine control that triggers the secure coding validation and data update
process.
Multiplicity 1
Type Reference to DcmDspRoutine
5

812 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local

813 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

10.3 Protocol Configuration Example

Figure 10.62: Examples of protocol configuration with focus on buffer / DcmPduId set-
tings

Above example shows protocol configuration at the use cases examples OBD and UDS
(used for customer enhanced diagnosis). It is assumed that for UDS communication,
there are functional and physical requests. There will be separate DcmPduRxIds for
functional and physical reception.

814 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

Concerning buffer configuration it is proposed to use a separate buffer for the func-
tional requests. This in correspondence to support the keep alive logic with functional
addressed TesterPresent commands.
It is also proposed to use a separate receive buffer for the OBD commands. This in
reference to support the protocol switch functionality.
It is allowed to share for both protocols the transmit buffer. Please note: The DcmDsl-
ProtocolRx has two possible configurations:
• functional
• physical
The physical shall have a 1:1 (or 1:0) dependency to the DcmDslMain-
Connection. (which means: DcmDslProtocolRxPduRef in combination
DCM_PROTOCOL_RX_ADDR_TYP = physical can exist only once per "Mod-
ule") The functional shall have a 1:n dependency to the DcmDslMain-
Connection. (which means: DcmDslProtocolRxPduRef in combination
DCM_PROTOCOL_RX_ADDR_TYP = functional can exist several times per "Module")
The DcmDslProtocolTx shall exist only once per "Module"

10.4 Published Information

For details refer to the chapter 10.3 "Published Information" in SWS_BSWGeneral [8].

815 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

A Change history of AUTOSAR traceable items

Please note that the lists in this chapter also include traceable items that have been
removed from the specification in a later version. These items do not appear as hyper-
links in the document.

A.1 Traceable item history of this document according to

AUTOSAR Release R24-11

A.1.1 Added Specification Items in R24-11

Number Heading
[ECUC_Dcm_01250] Definition of EcucReferenceDef SEV_UDS_SECURITY_ACCESS_NEEDED
[ECUC_Dcm_01251] Definition of EcucReferenceDef SEV_UDS_AUTHENTICATION_NEEDED
Definition of EcucReferenceDef SEV_UDS_SECURITY_ACCESS_
[ECUC_Dcm_01252]
SUCCESSFUL
[ECUC_Dcm_01253] Definition of EcucReferenceDef SEV_UDS_SECURITY_ACCESS_FAILED
Definition of EcucReferenceDef SEV_UDS_AUTHENTICATION_
[ECUC_Dcm_01254]
SUCCESSFUL
[ECUC_Dcm_01255] Definition of EcucReferenceDef SEV_UDS_AUTHENTICATION_FAILED
[ECUC_Dcm_01256] Definition of EcucReferenceDef SEV_UDS_WRITE_DATA_SUCCESSFUL
[ECUC_Dcm_01257] Definition of EcucReferenceDef SEV_UDS_WRITE_DATA_FAILED
Definition of EcucReferenceDef SEV_UDS_WRITE_MEMORY_
[ECUC_Dcm_01258]
SUCCESSFUL
[ECUC_Dcm_01259] Definition of EcucReferenceDef SEV_UDS_WRITE_MEMORY_FAILED
Definition of EcucReferenceDef SEV_UDS_REQUEST_UP_DOWNLOAD_
[ECUC_Dcm_01260]
SUCCESSFUL
Definition of EcucReferenceDef SEV_UDS_REQUEST_UP_DOWNLOAD_
[ECUC_Dcm_01261]
FAILED
Definition of EcucReferenceDef SEV_UDS_REQUEST_FILE_TRANSFER_
[ECUC_Dcm_01262]
SUCCESSFUL
Definition of EcucReferenceDef SEV_UDS_REQUEST_FILE_TRANSFER_
[ECUC_Dcm_01263]
FAILED
Definition of EcucReferenceDef SEV_UDS_COMMUNICATION_
[ECUC_Dcm_01264]
CONTROL_SUCCESSFUL
Definition of EcucReferenceDef SEV_UDS_COMMUNICATION_
[ECUC_Dcm_01265]
CONTROL_FAILED
[ECUC_Dcm_01266] Definition of EcucReferenceDef SEV_UDS_CLEAR_DTC_SUCCESSFUL
[ECUC_Dcm_01267] Definition of EcucReferenceDef SEV_UDS_CLEAR_DTC_FAILED
Definition of EcucReferenceDef SEV_UDS_CONTROL_DTC_SETTING_
[ECUC_Dcm_01268]
SUCCESSFUL
Definition of EcucReferenceDef SEV_UDS_CONTROL_DTC_SETTING_
[ECUC_Dcm_01269]
FAILED
5

816 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[ECUC_Dcm_01270] Definition of EcucReferenceDef SEV_UDS_ECU_RESET_SUCCESSFUL
[ECUC_Dcm_01271] Definition of EcucReferenceDef SEV_UDS_ECU_RESET_FAILED
Definition of EcucReferenceDef SEV_UDS_ROUTINE_CONTROL_
[ECUC_Dcm_01272]
SUCCESSFUL
[ECUC_Dcm_01273] Definition of EcucReferenceDef SEV_UDS_ROUTINE_CONTROL_FAILED
[ECUC_Dcm_01274] Definition of EcucReferenceDef SEV_UDS_IO_CONTROL_SUCCESSFUL
[ECUC_Dcm_01275] Definition of EcucReferenceDef SEV_UDS_IO_CONTROL_FAILED
[SWS_Dcm_01702] Reporting security access denied to IdsM
Security event context data definition: SEV_UDS_SECURITY_ACCESS_
[SWS_Dcm_01703]
NEEDED
[SWS_Dcm_01704] Reporting authentication required to IdsM
Security event context data definition: SEV_UDS_AUTHENTICATION_
[SWS_Dcm_01705]
NEEDED
[SWS_Dcm_01706] Reporting successful security access to IdsM
Security event context data definition: SEV_UDS_SECURITY_ACCESS_
[SWS_Dcm_01707]
SUCCESSFUL
[SWS_Dcm_01708] Reporting failed security access to IdsM
Security event context data definition: SEV_UDS_SECURITY_ACCESS_
[SWS_Dcm_01709]
FAILED
[SWS_Dcm_01710] Reporting successful authentication to IdsM
Security event context data definition: SEV_UDS_AUTHENTICATION_
[SWS_Dcm_01711]
SUCCESSFUL
[SWS_Dcm_01712] Reporting failed authentication to IdsM
Security event context data definition: SEV_UDS_AUTHENTICATION_
[SWS_Dcm_01713]
FAILED
[SWS_Dcm_01714] Reporting successful writing of data to IdsM
Security event context data definition: SEV_UDS_WRITE_DATA_
[SWS_Dcm_01715]
SUCCESSFUL
[SWS_Dcm_01716] Reporting writing of data failed to IdsM
[SWS_Dcm_01717] Security event context data definition: SEV_UDS_WRITE_DATA_FAILED
[SWS_Dcm_01718] Reporting successful up download to IdsM
Security event context data definition: SEV_UDS_REQUEST_UP_
[SWS_Dcm_01719]
DOWNLOAD_SUCCESSFUL
[SWS_Dcm_01720] Reporting up download failed to IdsM
Security event context data definition: SEV_UDS_REQUEST_UP_
[SWS_Dcm_01721]
DOWNLOAD_FAILED
[SWS_Dcm_01722] Reporting successful file transfer to IdsM
Security event context data definition: SEV_UDS_REQUEST_FILE_
[SWS_Dcm_01723]
TRANSFER_SUCCESSFUL
[SWS_Dcm_01724] Reporting file transfer failed to IdsM
Security event context data definition: SEV_UDS_REQUEST_FILE_
[SWS_Dcm_01725]
TRANSFER_FAILED
5

817 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[SWS_Dcm_01726] Reporting successful communication control to IdsM
Security event context data definition: SEV_UDS_COMMUNICATION_
[SWS_Dcm_01727]
CONTROL_SUCCESSFUL
[SWS_Dcm_01728] Reporting communication control failed to IdsM
Security event context data definition: SEV_UDS_COMMUNICATION_
[SWS_Dcm_01729]
CONTROL_FAILED
[SWS_Dcm_01730] Reporting successful clearing of dtc to IdsM
Security event context data definition: SEV_UDS_CLEAR_DTC_
[SWS_Dcm_01731]
SUCCESSFUL
[SWS_Dcm_01732] Reporting clearing of dtc failed to IdsM
[SWS_Dcm_01733] Security event context data definition: SEV_UDS_CLEAR_DTC_FAILED
[SWS_Dcm_01734] Reporting successful control of dtc to IdsM
Security event context data definition: SEV_UDS_CONTROL_DTC_
[SWS_Dcm_01735]
SETTING_SUCCESSFUL
[SWS_Dcm_01736] Reporting control of dtc failed to IdsM
Security event context data definition: SEV_UDS_CONTROL_DTC_
[SWS_Dcm_01737]
SETTING_FAILED
[SWS_Dcm_01738] Reporting successful reset of ECU to IdsM
Security event context data definition: SEV_UDS_ECU_RESET_
[SWS_Dcm_01739]
SUCCESSFUL
[SWS_Dcm_01740] Reporting reset of ECU failed to IdsM
[SWS_Dcm_01741] Security event context data definition: SEV_UDS_ECU_RESET_FAILED
[SWS_Dcm_01742] Reporting successful routine control to IdsM
Security event context data definition: SEV_UDS_ROUTINE_CONTROL_
[SWS_Dcm_01743]
SUCCESSFUL
[SWS_Dcm_01744] Reporting routine control failed to IdsM
Security event context data definition: SEV_UDS_ROUTINE_CONTROL_
[SWS_Dcm_01745]
FAILED
[SWS_Dcm_01746] Reporting successful IO control to IdsM
Security event context data definition: SEV_UDS_IO_CONTROL_
[SWS_Dcm_01747]
SUCCESSFUL
[SWS_Dcm_01748] Reporting IO control failed to IdsM
[SWS_Dcm_01749] Security event context data definition: SEV_UDS_IO_CONTROL_FAILED
[SWS_Dcm_01750] Reporting successful Memory Write operation to IdsM
Security event context data definition: SEV_UDS_WRITE_MEMORY_
[SWS_Dcm_01751]
SUCCESSFUL
[SWS_Dcm_01752] Reporting Write Memory failed to IdsM
Security event context data definition: SEV_UDS_WRITE_MEMORY_
[SWS_Dcm_01753]
FAILED
Table A.1: Added Specification Items in R24-11

818 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

A.1.2 Changed Specification Items in R24-11

Number Heading
[ECUC_Dcm_00690] Definition of EcucParamConfContainerDef DcmDsl
[ECUC_Dcm_00784] Definition of EcucParamConfContainerDef DcmDspMemory
[ECUC_Dcm_00858] Definition of EcucParamConfContainerDef DcmDspRoe
[ECUC_Dcm_00911] Definition of EcucParamConfContainerDef DcmDspMemoryIdInfo
Definition of EcucParamConfContainerDef DcmDspAuthentication
[ECUC_Dcm_01162]
Connection
Definition of EcucReferenceDef DcmDspAuthenticationPublicKeyElement
[ECUC_Dcm_01166]
Ref
Definition of EcucReferenceDef DcmDspAuthenticationWhiteListServices
[ECUC_Dcm_01168]
ElementRef
Definition of EcucReferenceDef DcmDspAuthenticationCertificatePublicKey
[ECUC_Dcm_01176]
StoreJobRef
[ECUC_Dcm_01177] Definition of EcucReferenceDef DcmDspAuthenticationECUCertificateRef
[ECUC_Dcm_01188] Definition of EcucParamConfContainerDef DcmSecurityEventRefs
Definition of EcucIntegerParamDef DcmDspRoeMaxNumComparisonOf
[ECUC_Dcm_01237]
ValueEvents
[ECUC_Dcm_01238] Definition of EcucIntegerParamDef DcmDspRoeMaxSupportedDIDLength
Definition of EcucIntegerParamDef DcmDspRoeMaxNumOfStored
[ECUC_Dcm_01239]
DTCStatusChangedEvents
[SWS_Dcm_00250]
[SWS_Dcm_00481]
[SWS_Dcm_00482]
[SWS_Dcm_00483]
[SWS_Dcm_00539] Definition of configurable interface Dcm_ReadMemory
[SWS_Dcm_00594]
[SWS_Dcm_00755] Definition of configurable interface Dcm_ProcessRequestTransferExit
[SWS_Dcm_00763] Definition of configurable interface <Module>_<DiagnosticService>
[SWS_Dcm_00796] Definition of configurable interface Xxx_ReadDataLength
[SWS_Dcm_00804] Definition of configurable interface Xxx_ReadDidData
[SWS_Dcm_00988] Definition of datatype Dcm_ProgConditionsType
[SWS_Dcm_01151] Definition of configurable interface Xxx_GetSeed
[SWS_Dcm_01182]
[SWS_Dcm_01183]
[SWS_Dcm_01204] Definition of configurable interface Xxx_Stop
[SWS_Dcm_01429]
[SWS_Dcm_01473] Check certificate content
[SWS_Dcm_01478] Mode declaration group per connection
[SWS_Dcm_01489] No persistency for deauthenticated roles by SWC
5

819 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[SWS_Dcm_01508] Sending positive response on verifyCertificateBidirectional
[SWS_Dcm_01517] White list access
[SWS_Dcm_01518] White list size check
[SWS_Dcm_01528] Transition into authenticated state
[SWS_Dcm_01540] Diagnostic service execution rights verification
[SWS_Dcm_01545] Read user defined memory by status mask authentication check
[SWS_Dcm_01546] Read user defined memory snapshot record authentication check
[SWS_Dcm_01547] Read user defined memory extended data record authentication check
[SWS_Dcm_01590] Security events for Dcm
[SWS_Dcm_01604] Delay parallel processing on the same application interface change
[SWS_Dcm_01630] Maximum number of comparison of value DIDs per scheduler
[SWS_Dcm_01632] Maximum number of changed DTCs per scheduler
[SWS_Dcm_01641] Support of UDS Services
[SWS_Dcm_01656] Subfunction 0x42 response values
[SWS_Dcm_91002] Definition of optional interfaces requested by module Dcm
[SWS_Dcm_91003] Definition of configurable interface Xxx_GetSeed
[SWS_Dcm_91013] Definition of configurable interface Xxx_RequestResults
[SWS_Dcm_91069] Definition of API function Dcm_SetDeauthenticatedRole
[SWS_Dcm_91071] Definition of configurable interface Dcm_ProcessTransferDataWrite
[SWS_Dcm_91073] Definition of Port Authentication_{Connection} provided by module Dcm
[SWS_Dcm_91091] Definition of configurable interface Xxx_ReadData
[SWS_Dcm_91092] Definition of configurable interface Xxx_WriteData
[SWS_Dcm_91093] Definition of configurable interface Xxx_GetScalingInformation
[SWS_Dcm_91094] Definition of configurable interface Xxx_GetScalingInformation
[SWS_Dcm_91095] Definition of configurable interface Xxx_WriteData
[SWS_Dcm_91097] Definition of configurable interface Xxx_ReadDataLength
[SWS_Dcm_91098] Definition of configurable interface Xxx_ReturnControlToECU
[SWS_Dcm_91099] Definition of configurable interface Xxx_ResetToDefault
[SWS_Dcm_91100] Definition of configurable interface Xxx_ResetToDefault
[SWS_Dcm_91102] Definition of configurable interface Xxx_FreezeCurrentState
[SWS_Dcm_91103] Definition of configurable interface Xxx_ShortTermAdjustment
Table A.2: Changed Specification Items in R24-11

820 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

A.1.3 Deleted Specification Items in R24-11

Number Heading
Definition of EcucParamConfContainerDef
[ECUC_Dcm_00679]
DcmDslCallbackDCMRequestService
[ECUC_Dcm_01189] Definition of EcucReferenceDef SEV_UDS_WRITE_INVALID_DATA
[ECUC_Dcm_01190] Definition of EcucReferenceDef SEV_UDS_SECURITY_ACCESS_DENIED
Definition of EcucReferenceDef
[ECUC_Dcm_01191]
SEV_UDS_COMMUNICATION_CONTROL_SWITCHED_OFF
[ECUC_Dcm_01192] Definition of EcucReferenceDef SEV_UDS_SERVICE_NOT_SUPPORTED
Definition of EcucReferenceDef
[ECUC_Dcm_01193]
SEV_UDS_SUBFUNCTION_NOT_SUPPORTED
Definition of EcucReferenceDef
[ECUC_Dcm_01194]
SEV_UDS_INCORRECT_MESSAGE_LENGTH_OR_FORMAT
Definition of EcucReferenceDef
[ECUC_Dcm_01195]
SEV_UDS_REQUEST_SEQUENCE_ERROR
[ECUC_Dcm_01196] Definition of EcucReferenceDef SEV_UDS_ECU_UNLOCK_SUCCESSFUL
Definition of EcucReferenceDef
[ECUC_Dcm_01197]
SEV_UDS_AUTHENTICATION_SUCCESSFUL
[ECUC_Dcm_01198] Definition of EcucReferenceDef SEV_UDS_CLEAR_DTC_SUCCESSFUL
[ECUC_Dcm_01199] Definition of EcucReferenceDef SEV_UDS_ECU_RESET
[ECUC_Dcm_01200] Definition of EcucReferenceDef SEV_UDS_WRITE_DATA
[ECUC_Dcm_01201] Definition of EcucReferenceDef SEV_UDS_REQUEST_DOWNLOAD
Definition of EcucReferenceDef
[ECUC_Dcm_01202]
SEV_UDS_DTC_SETTING_SWITCHED_OFF
[ECUC_Dcm_01203] Definition of EcucReferenceDef SEV_UDS_REQUEST_OUT_OF_RANGE
Definition of EcucReferenceDef
[ECUC_Dcm_01204]
SEV_UDS_REQUESTED_ACTIONS_REQUIRES_AUTHENTICATION
Definition of EcucReferenceDef
[ECUC_Dcm_01205]
SEV_UDS_SECURITY_ACCESS_NUMBER_OF_ATTEMPTS_EXCEEDED
Definition of EcucReferenceDef
[ECUC_Dcm_01206]
SEV_UDS_SECURITY_ACCESS_INVALID_KEY
Definition of EcucReferenceDef
[ECUC_Dcm_01207]
SEV_UDS_SECURITY_ACCESS_REQUIRED_TIME_DELAY_NOT_EXPIRED
Definition of EcucReferenceDef
[ECUC_Dcm_01208]
SEV_UDS_NUMBER_OF_FAILED_AUTHENTICATION_ATTEMPTS_EXCEEDED
[ECUC_Dcm_01209] Definition of EcucReferenceDef SEV_UDS_CERTIFICATE_FAILURE
[SWS_Dcm_00036]
[SWS_Dcm_00144]
[SWS_Dcm_00145]
[SWS_Dcm_00146]
[SWS_Dcm_00147]
5

821 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[SWS_Dcm_00459] Callback notification for preempted protocols
[SWS_Dcm_00624]
[SWS_Dcm_00625]
[SWS_Dcm_00668]
[SWS_Dcm_00669]
[SWS_Dcm_00670]
[SWS_Dcm_00671]
[SWS_Dcm_00672]
[SWS_Dcm_00673]
[SWS_Dcm_00674]
[SWS_Dcm_00692] Definition of ClientServerInterface CallbackDCMRequestServices
[SWS_Dcm_00728]
[SWS_Dcm_00775]
[SWS_Dcm_00943]
[SWS_Dcm_00945]
[SWS_Dcm_00949]
Definition of Port CallbackDCMRequestServices_{Name} required by
[SWS_Dcm_01033]
module Dcm
[SWS_Dcm_01190]
[SWS_Dcm_01194]
[SWS_Dcm_01339] Definition of configurable interface Xxx_StartProtocol
[SWS_Dcm_01340] Definition of configurable interface Xxx_StopProtocol
[SWS_Dcm_01394]
Table A.3: Deleted Specification Items in R24-11

A.1.4 Added Constraints in R24-11

none

A.1.5 Changed Constraints in R24-11

Number Heading
[SWS_Dcm_-
CONSTR_- Existence of size parameter
06002]
5

822 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[SWS_Dcm_-
CONSTR_- Define the usage of DcmDspRoutineParameterSize parameter
06008]
[SWS_Dcm_-
CONSTR_-
06105]
[SWS_Dcm_-
CONSTR_-
06106]
[SWS_Dcm_-
CONSTR_-
06107]
Table A.4: Changed Constraints in R24-11

A.1.6 Deleted Constraints in R24-11

none

A.2 Traceable item history of this document according to

AUTOSAR Release R23-11

A.2.1 Added Specification Items in R23-11

Number Heading
[SWS_Dcm_01641] Support of UDS Services
[SWS_Dcm_01642] Subfunction 0x01, 0x07 and 0x12 response values
Dem_SetDTCFilter() parameters values for subfunctions 0x01, 0x07 and
[SWS_Dcm_01643]
0x12
[SWS_Dcm_01644] Subfunction 0x02, 0x0A, 0x13, 0x15 and 0x17 response values
Dem_SetDTCFilter() parameters values for subfunctions 0x02, 0x0A, 0x13,
[SWS_Dcm_01645]
0x15 and0x17
[SWS_Dcm_01646] Subfunction 0x08 response values
[SWS_Dcm_01647] Dem_SetDTCFilter() parameters values for Subfunction 0x08
[SWS_Dcm_01648] Subfunction 0x09 response values
[SWS_Dcm_01649] Dem_SelectDTC() parameters values for subfunctions 0x06 and 0x19
Dem_SelectExtendedDataRecord() parameters values for subfunctions
[SWS_Dcm_01650]
0x06 and 0x19
[SWS_Dcm_01651] Subfunction 0x05 response values
5

823 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[SWS_Dcm_01652] Subfunctions 0x0B, 0x0C, 0x0D and 0x0E response values
Dem_GetDTCByOccurrenceTime() parameters values for subfunctions
[SWS_Dcm_01653]
0x0B, 0x0C, 0x0D and 0x0E
[SWS_Dcm_01654] Subfunction 0x14 response values
Dem_GetNextFilteredDTCAndFDC() parameters values for subfunctions
[SWS_Dcm_01655]
0x14
[SWS_Dcm_01656] Subfunction 0x42 response values
Dem_GetNextFilteredDTCAndSeverity() parameters values for subfunctions
[SWS_Dcm_01657]
0x42
[SWS_Dcm_01658] Dem_GetNextFilteredDTCAndSeverity return values
[SWS_Dcm_01659] Subfunction 0x55 response values
[SWS_Dcm_01660] Dem_SetDTCFilter() parameters values for subfunction 0x55
[SWS_Dcm_01661] InputOutputControlParameter definitions
[SWS_Dcm_01662] NRC managed by callout function for service 0x34
[SWS_Dcm_01663] NRC managed by callout function for service 0x35
[SWS_Dcm_01664] NRC managed by callout function for service 0x37
[SWS_Dcm_01665] NRC managed by callout function for service 0x36
[SWS_Dcm_01666] Concurrent tester present support
[SWS_Dcm_01667] Concurrent tester present from different connections
[SWS_Dcm_01668] S3Server session timer support
[SWS_Dcm_01669] Sessions and connections
[SWS_Dcm_01670] Change to default session upon S3Server elapses
[SWS_Dcm_01671] Message reception according to ISO 14229-2
[SWS_Dcm_01672] Mapping of T_DataSOM.ind
[SWS_Dcm_01673] Mapping of T_Data.ind
[SWS_Dcm_01674] Multi client handling
[SWS_Dcm_01675] Protocol resource availability
[SWS_Dcm_01676] Decline a second request with NRC 0x21
[SWS_Dcm_01677] Ignoring a second request
[SWS_Dcm_01678] Mulitple requests on the same connection
[SWS_Dcm_01679] Default S3 timeout value
[SWS_Dcm_01680] Overwritten S3 timeout value
[SWS_Dcm_01681] Support of subfunction transmitCertificate
[SWS_Dcm_01682] Verify certificateEvaluationId
[SWS_Dcm_01683] Certificate storage parsing and verification
[SWS_Dcm_01684] Starting the secure coding sequence
[SWS_Dcm_01685] Write Secure Coding DID for started secure coding sequence
[SWS_Dcm_01686] Write Secure Coding DID without a started secure coding sequence
[SWS_Dcm_01687] Write Secure Coding DID buffer overflow
5

824 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[SWS_Dcm_01688] Secure Coding validation trigger on inactive secure coding sequence
[SWS_Dcm_01689] Secure Coding validation trigger without written data
[SWS_Dcm_01690] Dcm internal processing of secure coding validation routine
[SWS_Dcm_01691] Authentication of secure coding data
[SWS_Dcm_01692] Successful authenticated secure coding data
[SWS_Dcm_01693] Successfully completed secure coding procedure
[SWS_Dcm_01694] Failed secure coding write
[SWS_Dcm_01695] Wrong signature for secure coding data
[SWS_Dcm_01696] Behavior on too long signature validation
Definition of Port AuthenticationStateModeSwitchInterface_{Connection}
[SWS_Dcm_91075]
provided by module Dcm
Table A.5: Added Specification Items in R23-11

A.2.2 Changed Specification Items in R23-11

Number Heading
[SWS_Dcm_00027]
[SWS_Dcm_00030]
[SWS_Dcm_00092] Definition of API function Dcm_CopyTxData
[SWS_Dcm_00094] Definition of callback function Dcm_StartOfReception
[SWS_Dcm_00143]
[SWS_Dcm_00293]
[SWS_Dcm_00295]
[SWS_Dcm_00333] Definition of imported datatypes of module Dcm
[SWS_Dcm_00338] Definition of API function Dcm_GetSecurityLevel
[SWS_Dcm_00339] Definition of API function Dcm_GetSesCtrlType
[SWS_Dcm_00376]
[SWS_Dcm_00377]
[SWS_Dcm_00378]
[SWS_Dcm_00379]
[SWS_Dcm_00380]
[SWS_Dcm_00381]
[SWS_Dcm_00382]
[SWS_Dcm_00392]
[SWS_Dcm_00442]
[SWS_Dcm_00464]
5

825 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[SWS_Dcm_00465]
[SWS_Dcm_00466]
[SWS_Dcm_00520] Definition of API function Dcm_ResetToDefaultSession
[SWS_Dcm_00539] Definition of configurable interface Dcm_ReadMemory
[SWS_Dcm_00540] Definition of configurable interface Dcm_WriteMemory
[SWS_Dcm_00543] Definition of configurable interface Dcm_SetProgConditions
[SWS_Dcm_00544] Definition of configurable interface Dcm_GetProgConditions
[SWS_Dcm_00556] Definition of API function Dcm_CopyRxData
[SWS_Dcm_00574]
[SWS_Dcm_00579]
[SWS_Dcm_00614] Definition of API function Dcm_DemTriggerOnDTCStatus
[SWS_Dcm_00641]
[SWS_Dcm_00685] Definition of ClientServerInterface SecurityAccess_{SecurityLevel}
[SWS_Dcm_00686] Definition of ClientServerInterface DataServices_{Data}
[SWS_Dcm_00687] Definition of SenderReceiverInterface DataServices_{Data}
[SWS_Dcm_00688] Definition of ClientServerInterface InfotypeServices_{VehInfoData}
[SWS_Dcm_00690] Definition of ClientServerInterface RoutineServices_{RoutineName}
[SWS_Dcm_00691] Definition of ClientServerInterface RequestControlServices_{Tid}
[SWS_Dcm_00694] Definition of ClientServerInterface ServiceRequestNotification
[SWS_Dcm_00698] Definition of ClientServerInterface DCMServices
[SWS_Dcm_00754] Definition of configurable interface Dcm_ProcessRequestDownload
[SWS_Dcm_00755] Definition of configurable interface Dcm_ProcessRequestTransferExit
[SWS_Dcm_00756] Definition of configurable interface Dcm_ProcessRequestUpload
[SWS_Dcm_00763] Definition of configurable interface <Module>_<DiagnosticService>
Definition of configurable interface <Module>_<DiagnosticService>_<Sub
[SWS_Dcm_00764]
Service>
[SWS_Dcm_00769] Definition of ClientServerInterface DataServices_DIDRange_{Range}
[SWS_Dcm_00793] Definition of configurable interface Xxx_ReadData
[SWS_Dcm_00794] Definition of configurable interface Xxx_WriteData
[SWS_Dcm_00796] Definition of configurable interface Xxx_ReadDataLength
[SWS_Dcm_00797] Definition of configurable interface Xxx_ConditionCheckRead
[SWS_Dcm_00798] Definition of configurable interface Xxx_GetScalingInformation
[SWS_Dcm_00802] Definition of configurable interface Xxx_ShortTermAdjustment
[SWS_Dcm_00803] Definition of configurable interface Xxx_IsDidAvailable
[SWS_Dcm_00804] Definition of configurable interface Xxx_ReadDidData
[SWS_Dcm_00805] Definition of configurable interface Xxx_WriteDidData
[SWS_Dcm_00950] Definition of API function Dcm_GetVin
[SWS_Dcm_00976] Definition of datatype Dcm_StatusType
[SWS_Dcm_00977] Definition of ImplementationDataType Dcm_SecLevelType
5

826 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[SWS_Dcm_00978] Definition of ImplementationDataType Dcm_SesCtrlType
[SWS_Dcm_00979] Definition of ImplementationDataType Dcm_ProtocolType
[SWS_Dcm_00980] Definition of ImplementationDataType Dcm_NegativeResponseCodeType
[SWS_Dcm_00981] Definition of datatype Dcm_CommunicationModeType
[SWS_Dcm_00982] Definition of datatype Dcm_ConfigType
[SWS_Dcm_00983] Definition of ImplementationDataType Dcm_ConfirmationStatusType
[SWS_Dcm_00984] Definition of ImplementationDataType Dcm_OpStatusType
[SWS_Dcm_00985] Definition of datatype Dcm_ReturnReadMemoryType
[SWS_Dcm_00986] Definition of datatype Dcm_ReturnWriteMemoryType
[SWS_Dcm_00987] Definition of datatype Dcm_EcuStartModeType
[SWS_Dcm_00988] Definition of datatype Dcm_ProgConditionsType
[SWS_Dcm_00989] Definition of datatype Dcm_MsgItemType
[SWS_Dcm_00990] Definition of datatype Dcm_MsgType
[SWS_Dcm_00991] Definition of datatype Dcm_MsgLenType
[SWS_Dcm_00993] Definition of datatype Dcm_IdContextType
[SWS_Dcm_00994] Definition of datatype Dcm_MsgContextType
[SWS_Dcm_01012] Definition of ImplementationDataType Dcm_RangeArray_{Range}Type
Definition of ImplementationDataType Dcm_InfoTypeServicesArray_{VehInfo
[SWS_Dcm_01013]
Data}Type
Definition of ImplementationDataType Dcm_RequestControlServicesIn
[SWS_Dcm_01014]
Array_{Tid}Type
Definition of ImplementationDataType Dcm_RequestControlServicesOut
[SWS_Dcm_01015]
Array_{Tid}Type
[SWS_Dcm_01017] Definition of ImplementationDataType Dcm_ScalingInfoArray_{Data}Type
Definition of ImplementationDataType Dcm_RequestData
[SWS_Dcm_01018]
Out_{Routine}_{Signal}PrimitivType
Definition of ImplementationDataType Dcm_RequestFlexibleOutArray
[SWS_Dcm_01019]
Data_{Routine}_{Signal}Type
Definition of ImplementationDataType Dcm_StartData
[SWS_Dcm_01020]
In_{Routine}_{Signal}PrimitivType
Definition of ImplementationDataType Dcm_StartData
[SWS_Dcm_01021]
Out_{Routine}_{Signal}PrimitivType
Definition of ImplementationDataType Dcm_StartFlexibleInArray
[SWS_Dcm_01022]
Data_{Routine}_{Signal}Type
Definition of ImplementationDataType Dcm_StartFlexibleOutArray
[SWS_Dcm_01023]
Data_{Routine}_{Signal}Type
Definition of ImplementationDataType Dcm_StopData
[SWS_Dcm_01024]
In_{Routine}_{Signal}PrimitivType
Definition of ImplementationDataType Dcm_StopData
[SWS_Dcm_01025]
Out_{Routine}_{Signal}PrimitivType
5

827 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
Definition of ImplementationDataType Dcm_StopFlexibleInArray
[SWS_Dcm_01026]
Data_{Routine}_{Signal}Type
Definition of ImplementationDataType Dcm_StopFlexibleOutArray
[SWS_Dcm_01027]
Data_{Routine}_{Signal}Type
[SWS_Dcm_01028] Definition of ImplementationDataType Dcm_KeyArray_{SecurityLevel}Type
[SWS_Dcm_01029] Definition of ImplementationDataType Dcm_SeedArray_{SecurityLevel}Type
[SWS_Dcm_01030] Definition of Port DCMServices provided by module Dcm
[SWS_Dcm_01031] Definition of Port DataServices_{Data} provided by module Dcm
Definition of Port DataServices_DIDRange_{Range} required by module
[SWS_Dcm_01034]
Dcm
[SWS_Dcm_01035] Definition of Port DataServices_{Data} required by module Dcm
[SWS_Dcm_01037] Definition of Port InfotypeServices_{VehInfoData} required by module Dcm
[SWS_Dcm_01038] Definition of Port RequestControlServices_{Tid} required by module Dcm
Definition of Port ServiceRequestManufacturerNotification_{Name} required
[SWS_Dcm_01039]
by module Dcm
[SWS_Dcm_01040] Definition of Port RoutineServices_{RoutineName} required by module Dcm
[SWS_Dcm_01041] Definition of Port SecurityAccess_{SecurityLevel} required by module Dcm
Definition of Port ServiceRequestSupplierNotification_{Name} required by
[SWS_Dcm_01042]
module Dcm
[SWS_Dcm_01068] Definition of API function Dcm_SetActiveDiagnostic
[SWS_Dcm_01121] Definition of ImplementationDataType Dcm_DataArrayTypeUint8_{Data}Type
[SWS_Dcm_01129]
[SWS_Dcm_01130]
[SWS_Dcm_01131]
[SWS_Dcm_01132]
[SWS_Dcm_01133]
[SWS_Dcm_01134]
[SWS_Dcm_01138] Definition of ImplementationDataType Dcm_DidSupportedType
[SWS_Dcm_01151] Definition of configurable interface Xxx_GetSeed
[SWS_Dcm_01152] Definition of configurable interface Xxx_GetSecurityAttemptCounter
[SWS_Dcm_01153] Definition of configurable interface Xxx_SetSecurityAttemptCounter
Definition of ImplementationDataType Dcm_SecurityAccessDataRecord
[SWS_Dcm_01159]
Array_{SecurityLevel}Type
[SWS_Dcm_01165] Definition of ImplementationDataType Dcm_RequestDataArrayType
[SWS_Dcm_01173]
[SWS_Dcm_01203] Definition of configurable interface Xxx_Start
[SWS_Dcm_01204] Definition of configurable interface Xxx_Stop
[SWS_Dcm_01270] Definition of configurable interface Xxx_ClearDTCCheckFnc
[SWS_Dcm_01271] Definition of configurable interface Xxx_ReadDidRangeDataLength
[SWS_Dcm_01273]
5

828 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[SWS_Dcm_01285] Definition of configurable interface Xxx_ReturnControlToECU
[SWS_Dcm_01286] Definition of configurable interface Xxx_ResetToDefault
[SWS_Dcm_01290] Definition of configurable interface Xxx_FreezeCurrentState
Definition of ImplementationDataType Dcm_InputOutputControlParameter
[SWS_Dcm_01305]
Type
[SWS_Dcm_01306] Definition of ImplementationDataType Dcm_IOOperationRequest_{DID}Type
[SWS_Dcm_01307] Definition of ImplementationDataType Dcm_IOOperationResponseType
[SWS_Dcm_01308] Definition of SenderReceiverInterface IOControlRequest_{DID}
[SWS_Dcm_01309] Definition of SenderReceiverInterface IOControlResponse_{DID}
[SWS_Dcm_01310] Definition of Port DataServices_{Data} required by module Dcm
[SWS_Dcm_01311] Definition of Port DataServices_{Data} provided/required by module Dcm
[SWS_Dcm_01312] Definition of Port IOControlRequest_{DID} provided/required by module Dcm
[SWS_Dcm_01313] Definition of Port IOControlResponse_{DID} required by module Dcm
[SWS_Dcm_01314] Definition of configurable interface Xxx_ResetToDefault
[SWS_Dcm_01315] Definition of configurable interface Xxx_FreezeCurrentState
[SWS_Dcm_01316] Definition of configurable interface Xxx_ShortTermAdjustment
[SWS_Dcm_01320] Definition of ImplementationDataType Dcm_ControlMask_{DID}Type
[SWS_Dcm_01338] Definition of configurable interface Xxx_RequestControl
[SWS_Dcm_01341] Definition of configurable interface Xxx_Indication
[SWS_Dcm_01342] Definition of configurable interface Xxx_Confirmation
[SWS_Dcm_01345]
[SWS_Dcm_01415] Behavior on application returning unexpected return code
[SWS_Dcm_01590] Security events for Dcm
[SWS_Dcm_91001] Definition of mandatory interfaces in module Dcm
[SWS_Dcm_91002] Definition of optional interfaces in module Dcm
[SWS_Dcm_91003] Definition of configurable interface Xxx_GetSeed
[SWS_Dcm_91004] Definition of configurable interface Xxx_CompareKey
[SWS_Dcm_91005] Definition of configurable interface Xxx_ReadData
[SWS_Dcm_91006] Definition of configurable interface Xxx_ReadData
[SWS_Dcm_91007] Definition of configurable interface Xxx_WriteData
[SWS_Dcm_91008] Definition of configurable interface Xxx_WriteData
[SWS_Dcm_91009] Definition of configurable interface Xxx_WriteData
[SWS_Dcm_91010] Definition of configurable interface Xxx_ReadDataLength
[SWS_Dcm_91011] Definition of configurable interface Xxx_ConditionCheckRead
[SWS_Dcm_91012] Definition of configurable interface Xxx_GetScalingInformation
[SWS_Dcm_91013] Definition of configurable interface Xxx_RequestResults
[SWS_Dcm_91014] Definition of configurable interface Xxx_GetInfotypeValueData
[SWS_Dcm_91015] Definition of datatype Dcm_ExtendedOpStatusType
[SWS_Dcm_91016] Definition of configurable interface Xxx_StartConfirmation
5

829 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[SWS_Dcm_91017] Definition of configurable interface Xxx_StopConfirmation
[SWS_Dcm_91018] Definition of configurable interface Xxx_RequestResultsConfirmation
[SWS_Dcm_91019] Definition of ModeDeclarationGroup DcmDiagnosticSessionControl
Definition of ModeSwitchInterface Dcm_DiagnosticSessionControlMode
[SWS_Dcm_91020]
SwitchInterface
[SWS_Dcm_91021] Definition of ModeDeclarationGroup DcmEcuReset
[SWS_Dcm_91022] Definition of ModeSwitchInterface Dcm_EcuResetModeSwitchInterface
[SWS_Dcm_91023] Definition of ModeDeclarationGroup DcmModeRapidPowerShutDown
Definition of ModeSwitchInterface Dcm_ModeRapidPowerShutDownMode
[SWS_Dcm_91024]
SwitchInterface
[SWS_Dcm_91025] Definition of ModeDeclarationGroup DcmCommunicationControl
Definition of ModeSwitchInterface CommunicationControlModeSwitch
[SWS_Dcm_91026]
Interface_{ComMChannelName}
[SWS_Dcm_91027] Definition of ModeDeclarationGroup DcmControlDTCSetting
Definition of ModeSwitchInterface Dcm_ControlDTCSettingModeSwitch
[SWS_Dcm_91028]
Interface
[SWS_Dcm_91031] Definition of ModeDeclarationGroup DcmSecurityAccess
Definition of ModeSwitchInterface Dcm_SecurityAccessModeSwitch
[SWS_Dcm_91032]
Interface
Definition of Port DiagnosticSessionControlModeSwitchInterface provided by
[SWS_Dcm_91033]
module Dcm
[SWS_Dcm_91034] Definition of Port EcuResetModeSwitchInterface provided by module Dcm
Definition of Port ModeRapidPowerShutDownModeSwitchInterface provided
[SWS_Dcm_91035]
by module Dcm
Definition of Port CommunicationControlModeSwitchInterface_{Com
[SWS_Dcm_91036]
MChannelName} provided by module Dcm
Definition of Port ControlDTCSettingModeSwitchInterface provided by
[SWS_Dcm_91037]
module Dcm
Definition of Port SecurityAccessModeSwitchInterface provided by module
[SWS_Dcm_91039]
Dcm
Definition of ImplementationDataType Dcm_RequestData
[SWS_Dcm_91040]
Out_{Routine}_{Signal}Type
Definition of ImplementationDataType Dcm_RequestData
[SWS_Dcm_91041]
Out_{Routine}_{Signal}ArrayType
Definition of ImplementationDataType Dcm_StartData
[SWS_Dcm_91042]
In_{Routine}_{Signal}Type
Definition of ImplementationDataType Dcm_StartData
[SWS_Dcm_91043]
In_{Routine}_{Signal}ArrayType
Definition of ImplementationDataType Dcm_StartData
[SWS_Dcm_91044]
Out_{Routine}_{Signal}Type
Definition of ImplementationDataType Dcm_StartData
[SWS_Dcm_91045]
Out_{Routine}_{Signal}ArrayType
5

830 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
Definition of ImplementationDataType Dcm_StopData
[SWS_Dcm_91046]
In_{Routine}_{Signal}Type
Definition of ImplementationDataType Dcm_StopData
[SWS_Dcm_91047]
In_{Routine}_{Signal}ArrayType
Definition of ImplementationDataType Dcm_StopData
[SWS_Dcm_91048]
Out_{Routine}_{Signal}Type
Definition of ImplementationDataType Dcm_StopData
[SWS_Dcm_91049]
Out_{Routine}_{Signal}ArrayType
[SWS_Dcm_91050] Definition of ImplementationDataType Dcm_ControlMask_{Data}ArrayType
[SWS_Dcm_91051] Definition of ImplementationDataType Dcm_DataElement_{Data}Type
Definition of ImplementationDataType Dcm_RequestData
[SWS_Dcm_91052]
In_{Routine}_{Signal}Type
Definition of ImplementationDataType Dcm_RequestFlexibleInArray
[SWS_Dcm_91053]
Data_{Routine}_{Signal}Type
Definition of ImplementationDataType Dcm_RequestData
[SWS_Dcm_91054]
In_{Routine}_{Signal}PrimitiveType
Definition of ImplementationDataType Dcm_RequestData
[SWS_Dcm_91055]
In_{Routine}_{Signal}ArrayType
[SWS_Dcm_91057] Definition of SenderReceiverInterface DataServices_{DID}
[SWS_Dcm_91058] Definition of Port DataServices_{DID} provided by module Dcm
[SWS_Dcm_91059] Definition of Port DataServices_{DID} required by module Dcm
[SWS_Dcm_91060] Definition of Port DataServices_{DID} provided/required by module Dcm
[SWS_Dcm_91061] Definition of SenderReceiverInterface DataServices_{DID}
Definition of ImplementationDataType Dcm_DataElement_{Data}_Primitive
[SWS_Dcm_91062]
Type
[SWS_Dcm_91063] Definition of ImplementationDataType Dcm_DataElement_{Data}_ArrayType
[SWS_Dcm_91064] Definition of ImplementationDataType Dcm_ResponseDataArrayType
[SWS_Dcm_91065] Definition of ClientServerInterface UploadDownloadServices
[SWS_Dcm_91066] Definition of ImplementationDataType Dcm_FileAndDirNameType
[SWS_Dcm_91067] Definition of ModeDeclarationGroup DcmAuthenticationState_{Connection}
[SWS_Dcm_91068] Definition of ImplementationDataType Dcm_AuthenticationRoleType
[SWS_Dcm_91069] Definition of API function Dcm_SetDeauthenticatedRole
[SWS_Dcm_91070] Definition of configurable interface Dcm_ProcessTransferDataRead
[SWS_Dcm_91071] Definition of configurable interface Dcm_ProcessTransferDataWrite
[SWS_Dcm_91072] Definition of ClientServerInterface Authentication
[SWS_Dcm_91073] Definition of Port Authentication_{Connection} required by module Dcm
Definition of ModeSwitchInterface Dcm_AuthenticationStateModeSwitch
[SWS_Dcm_91074]
Interface_{Connection}
[SWS_Dcm_91076] Definition of configurable interface Dcm_CsmAsyncJobFinished
Definition of configurable interface Dcm_KeyMAsyncCertificateVerify
[SWS_Dcm_91077]
Finished
5

831 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[SWS_Dcm_91078] Definition of configurable interface Dcm_ProcessRequestAddFile
[SWS_Dcm_91079] Definition of configurable interface Dcm_ProcessRequestDeleteFile
[SWS_Dcm_91080] Definition of configurable interface Dcm_ProcessRequestReplaceFile
[SWS_Dcm_91081] Definition of configurable interface Dcm_ProcessRequestReadFile
[SWS_Dcm_91082] Definition of configurable interface Dcm_ProcessRequestReadDir
[SWS_Dcm_91083] Definition of configurable interface Dcm_WriteFile
[SWS_Dcm_91084] Definition of Port UploadDownloadServices required by module Dcm
[SWS_Dcm_91085] Definition of configurable interface Dcm_ReadFileOrDir
[SWS_Dcm_91087] Definition of ImplementationDataType Dcm_Cemr_{DID}Type
Definition of ImplementationDataType Dcm_ControlMask_{Data}_Primitive
[SWS_Dcm_91089]
Type
[SWS_Dcm_91090] Definition of configurable interface Xxx_ReadData
[SWS_Dcm_91091] Definition of configurable interface Xxx_ReadData
[SWS_Dcm_91092] Definition of configurable interface Xxx_WriteData
[SWS_Dcm_91093] Definition of configurable interface Xxx_GetScalingInformation
[SWS_Dcm_91094] Definition of configurable interface Xxx_GetScalingInformation
[SWS_Dcm_91095] Definition of configurable interface Xxx_WriteData
[SWS_Dcm_91096] Definition of configurable interface Xxx_ReadDataLength
[SWS_Dcm_91097] Definition of configurable interface Xxx_ReadDataLength
[SWS_Dcm_91098] Definition of configurable interface Xxx_ReturnControlToECU
[SWS_Dcm_91099] Definition of configurable interface Xxx_ResetToDefault
[SWS_Dcm_91100] Definition of configurable interface Xxx_ResetToDefault
[SWS_Dcm_91101] Definition of configurable interface Xxx_FreezeCurrentState
[SWS_Dcm_91102] Definition of configurable interface Xxx_FreezeCurrentState
[SWS_Dcm_91103] Definition of configurable interface Xxx_ShortTermAdjustment
[SWS_Dcm_91104] Definition of configurable interface Xxx_ShortTermAdjustment
[SWS_Dcm_91105] Definition of configurable interface Xxx_Start
[SWS_Dcm_91106] Definition of configurable interface Xxx_Stop
[SWS_Dcm_91107] Definition of configurable interface Xxx_RequestResults
Definition of ImplementationDataType Dcm_DataElement_{Data}_Structured
[SWS_Dcm_91118]
Type
Definition of ImplementationDataType Dcm_RequestData
[SWS_Dcm_91119]
Out_{Routine}_{Signal}StructuredType
Definition of ImplementationDataType Dcm_RequestData
[SWS_Dcm_91120]
In_{Routine}_{Signal}StructuredType
Definition of ImplementationDataType Dcm_StartData
[SWS_Dcm_91121]
In_{Routine}_{Signal}StructuredType
Definition of ImplementationDataType Dcm_StartData
[SWS_Dcm_91122]
Out_{Routine}_{Signal}StructuredType
5

832 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
Definition of ImplementationDataType Dcm_StopData
[SWS_Dcm_91123]
In_{Routine}_{Signal}StructuredType
Definition of ImplementationDataType Dcm_StopData
[SWS_Dcm_91124]
Out_{Routine}_{Signal}StructuredType
Table A.6: Changed Specification Items in R23-11

A.2.3 Deleted Specification Items in R23-11

Number Heading
[SWS_Dcm_00112]
[SWS_Dcm_00113]
[SWS_Dcm_00140]
[SWS_Dcm_00141]
[SWS_Dcm_00541]
[SWS_Dcm_00557]
[SWS_Dcm_00560]
[SWS_Dcm_00655]
[SWS_Dcm_00656]
[SWS_Dcm_00788]
[SWS_Dcm_00789]
[SWS_Dcm_00790]
[SWS_Dcm_01128]
[SWS_Dcm_01145]
[SWS_Dcm_01146]
[SWS_Dcm_01168]
Table A.7: Deleted Specification Items in R23-11

A.2.4 Added Constraints in R23-11

Number Heading
[SWS_Dcm_-
CONSTR_- Not supported port interfaces for secure coding
06108]
5

833 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

4
Number Heading
[SWS_Dcm_-
CONSTR_- Static length of secure coding DIDs
06109]
[SWS_Dcm_-
CONSTR_- Secure Coding validation routine input parameter
06110]
[SWS_Dcm_-
CONSTR_- Secure Coding validation routine output parameter
06111]
[SWS_Dcm_-
CONSTR_- Secure Coding validation routine is synchronous
06112]
[SWS_Dcm_-
CONSTR_- Require asynchronous signature verification
06113]
Table A.8: Added Constraints in R23-11

A.2.5 Changed Constraints in R23-11

Number Heading
[SWS_Dcm_-
Usage of variable data length in case of S/R communication, NvRam access or
CONSTR_-
ECU signal access
06026]
Table A.9: Changed Constraints in R23-11

A.2.6 Deleted Constraints in R23-11

Number Heading
[SWS_Dcm_-
CONSTR_- Restrictions on datatype usage
06038]
[SWS_Dcm_-
CONSTR_- Dependency for DcmDspDataBlockIdRef
06067]
Table A.10: Deleted Constraints in R23-11

834 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager

 Specification of Diagnostic Communication
Manager
AUTOSAR CP R24-11

A.3 Not applicable requirements

[SWS_Dcm_NA_00999]
Upstream requirements: SRS_BSW_00159, SRS_BSW_00167, SRS_BSW_00168, SRS_-
BSW_00170, SRS_BSW_00171, SRS_BSW_00323, SRS_BSW_-
00336, SRS_BSW_00339, SRS_BSW_00344, SRS_BSW_00345,
SRS_BSW_00375, SRS_BSW_00380, SRS_BSW_00383, SRS_BSW_-
00384, SRS_BSW_00385, SRS_BSW_00386, SRS_BSW_00388,
SRS_BSW_00389, SRS_BSW_00390, SRS_BSW_00392, SRS_BSW_-
00393, SRS_BSW_00394, SRS_BSW_00395, SRS_BSW_00396,
SRS_BSW_00397, SRS_BSW_00398, SRS_BSW_00399, SRS_BSW_-
00400, SRS_BSW_00402, SRS_BSW_00403, SRS_BSW_00404,
SRS_BSW_00405, SRS_BSW_00406, SRS_BSW_00409, SRS_BSW_-
00416, SRS_BSW_00417, SRS_BSW_00419, SRS_BSW_00422,
SRS_BSW_00423, SRS_BSW_00425, SRS_BSW_00426, SRS_BSW_-
00427, SRS_BSW_00428, SRS_BSW_00429, SRS_BSW_00432,
SRS_BSW_00433, SRS_BSW_00437, SRS_BSW_00450, SRS_BSW_-
00451, SRS_BSW_00458, SRS_BSW_00461, SRS_BSW_00466,
SRS_BSW_00467, SRS_BSW_00469, SRS_BSW_00470, SRS_-
BSW_00471, SRS_BSW_00472, SRS_BSW_00478, RS_Diag_04002,
RS_Diag_04019, RS_Diag_04024, RS_Diag_04031, RS_Diag_04032,
RS_Diag_04057, RS_Diag_04063, RS_Diag_04064, RS_Diag_04068,
RS_Diag_04071, RS_Diag_04077, RS_Diag_04091, RS_Diag_04093,
RS_Diag_04097, RS_Diag_04105, RS_Diag_04107, RS_Diag_04109,
RS_Diag_04110, RS_Diag_04111, RS_Diag_04112, RS_Diag_04113,
RS_Diag_04117, RS_Diag_04118, RS_Diag_04120, RS_Diag_04121,
RS_Diag_04123, RS_Diag_04124, RS_Diag_04125, RS_Diag_04126,
RS_Diag_04127, RS_Diag_04129, RS_Diag_04131, RS_Diag_04133,
RS_Diag_04135, RS_Diag_04136, RS_Diag_04137, RS_Diag_04139,
RS_Diag_04140, RS_Diag_04148, RS_Diag_04150, RS_Diag_04151

dThese requirements are not applicable to this specification.c

835 of 835 Document ID 18: AUTOSAR_CP_SWS_DiagnosticCommunicationManager