Autosar CP Sws XCP
Autosar CP Sws XCP
AUTOSAR CP R24-11
4
• Editorial changes
AUTOSAR • Harmonize descriptions of identical API
2016-11-30 4.3.0 Release functions
Management
• Removal of unused artifacts and
obsolete elements
• Debugging support marked as obsolete
AUTOSAR
• Editorial changes
2015-07-31 4.2.2 Release
Management • Modifications in some parameters
multiplicity of XcpDaqlist container
• Editorial changes
• Minor corrections
AUTOSAR
2014-10-31 4.2.1 Release • Changed the multiplicity of
Management XcpEventChannelTriggeredDaqListRef
4
• Added parameters for Event Channel
and Timestamp configuration
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.
Contents
1 Introduction and functional overview 8
3 Related documentation 10
3.1 Input documents & related standards and norms . . . . . . . . . . . . . 10
3.2 Related specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4 Constraints and assumptions 12
4.1 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2 Applicability to car domains . . . . . . . . . . . . . . . . . . . . . . . . . 12
5 Dependencies to other modules 13
5.1 AUTOSAR RTE (BSW Scheduler) . . . . . . . . . . . . . . . . . . . . . . 13
5.2 AUTOSAR PDU Routing module (PduR) . . . . . . . . . . . . . . . . . . 13
5.3 AUTOSAR FlexRay Interface . . . . . . . . . . . . . . . . . . . . . . . . 13
5.4 AUTOSAR CAN Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.5 AUTOSAR SocketAdaptor . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.6 AUTOSAR RTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.7 AUTOSAR OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.8 AUTOSAR Diagnostic Event Manager . . . . . . . . . . . . . . . . . . . 14
5.9 AUTOSAR Default Error Tracer . . . . . . . . . . . . . . . . . . . . . . . 14
5.10 File structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
5.10.1 Code file structure . . . . . . . . . . . . . . . . . . . . . . . . . 14
6 Requirements Tracing 15
7 Functional specification 18
7.1 XCP on CAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.2 XCP on FlexRay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.3 XCP on Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7.4 General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
7.5 Error Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.5.1 Development Errors . . . . . . . . . . . . . . . . . . . . . . . . 26
7.5.2 Runtime Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.5.3 Transient Faults . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.5.4 Production Errors . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.5.5 Extended Production Errors . . . . . . . . . . . . . . . . . . . . 27
7.6 Version checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7.7 Security Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
8 API specification 28
8.1 Imported types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
8.2 Type definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
8.2.1 Xcp_ConfigType . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Acronym: Description:
AUTOSAR AUTomotive Open System ARchitecture
A2L File Extension for an ASAM 2MC Language File
ASAM Association for Standardization of Automation and Measuring Systems
BSW Basic Software
CAN Controller Area Network
CanIf CAN Interface
CTO Command Transfer Object
DAQ Data AcQuisition, Data AcQuisition Packet
DTO Data Transfer Object
ECU Electronic Control Unit
FrIf FlexRay Interface
LPDU Data Link Layer PDU
MCD Measurement Calibration and Diagnostics
MISRA Motor Industry Software Reliability Association
ODT Object Descriptor Table
PDU Protocol Data Unit
RAM Random Access Memory
ROM Read Only Memory
SchM Schedule Manager
SVN Subversion
SRS Software Requirements Specification
STIM Data Stimulation packet
SW Software
SWS Software Specification
TCP/IP Transfer Control Protocol / Internet Protocol
TS Time Stamp
UDP/IP User Datagram Protocol / Internet Protocol
URL Uniform Resource Locator
XCP Universal Calibration Protocol
XML Extensible Markup Language
ISR Interrupt Service Routine
DET Default Error Tracer (AUTOSAR BSW module)
3 Related documentation
[1] Glossary
AUTOSAR_FO_TR_Glossary
[2] General Specification of Basic Software Modules
AUTOSAR_CP_SWS_BSWGeneral
[3] ASAM XCP - The Universal Measurement and Calibration Protocol: ASAM_XCP_
Part1-Overview - Version 1.1
http://www.asam.net
[4] Specification of PDU Router
AUTOSAR_CP_SWS_PDURouter
[5] Specification of Linklayer Sdu Routing Module
AUTOSAR_CP_SWS_LSduRouter
[6] General Requirements on Basic Software Modules
AUTOSAR_CP_RS_BSWGeneral
[7] Requirements on Module XCP
AUTOSAR_CP_RS_XCP
[8] ASAM XCP - Transport Layer Specification XCP on CAN: ASAM_XCP_Part3
Transport-Layer-Specification_XCPonCAN - Version 1.2
http://www.asam.net
[9] Specification of CAN Interface
AUTOSAR_CP_SWS_CANInterface
[10] ASAM XCP - Transport Layer Specification XCP on FlexRay: ASAM_XCP_Part3-
Transport-Layer-Specification_XCPonFlexRay-Version 1.1
http://www.asam.net
[11] Specification of FlexRay Interface
AUTOSAR_CP_SWS_FlexRayInterface
[12] ASAM XCP - Transport Layer Specification XCP on Ethernet: ASAM_XCP_Part3-
Transport-Layer-Specification_XCPonEthernet (TCP_IP&UDP_IP) - Version 1.1
http://www.asam.net
[13] Specification of Socket Adaptor
AUTOSAR_CP_SWS_SocketAdaptor
4.1 Limitations
The following XCP features are currently out of scope:
• The SET_DAQ_ID command according to the XCP CAN Transport Layer Speci-
fication is not part of the AUTOSAR XCP module
• Currently, the AUTOSAR RTE does not offer APIs for direct communication with
XCP
• For further details concerning the supported feature set, please refer to [3]
• NAX is only configurable through the ASAM configuration file A2L.
Please note:
For the communications bus LIN, no ASAM XCP is specified.
5.7 AUTOSAR OS
In order to be able to use the time stamped feature of XCP, an AUTOSAR OS Counter
is used.
[SWS_Xcp_00501]
Upstream requirements: SRS_BSW_00419, SRS_BSW_00383, SRS_BSW_00346, SRS_BSW_-
00380
dThe code file structure shall not be defined within this specification completely. At this
point it shall be pointed out that the code-file structure shall include the following files
named:
• Xcp.c - general source code file of the module XCP
• Xcp_Cfg.c - for pre-compile time configurable parameters
• Xcp_Lcfg.c - for link time configurable parameters and
• Xcp_PBcfg.c - for post build time configurable parameters.
c
These files shall contain all link time and post-build time configurable parameters.
6 Requirements Tracing
The following tables reference the requirements specified in [6] and [7] 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
[SRS_BSW_00003] All software modules shall provide [SWS_Xcp_00807]
version and identification information
[SRS_BSW_00101] The Basic Software Module shall be [SWS_Xcp_00803]
able to initialize variables and
hardware in a separate initialization
function
[SRS_BSW_00159] All modules of the AUTOSAR Basic [SWS_Xcp_00102]
Software shall support a tool based
configuration
[SRS_BSW_00167] All AUTOSAR Basic Software [SWS_Xcp_00103] [SWS_Xcp_00104]
Modules shall provide configuration [SWS_Xcp_00105]
rules and constraints to enable
plausibility checks
[SRS_BSW_00318] Each AUTOSAR Basic Software [SWS_Xcp_00807]
Module file shall provide version
numbers in the header file
[SRS_BSW_00327] Error values naming convention [SWS_Xcp_00763]
[SRS_BSW_00344] BSW Modules shall support link-time [SWS_Xcp_00741]
configuration
[SRS_BSW_00345] BSW Modules shall support [SWS_Xcp_00742]
pre-compile configuration
[SRS_BSW_00346] All AUTOSAR Basic Software [SWS_Xcp_00501]
Modules shall provide at least a basic
set of module files
[SRS_BSW_00358] The return type of init() functions [SWS_Xcp_00803]
implemented by AUTOSAR Basic
Software Modules shall be void
[SRS_BSW_00373] The main processing function of each [SWS_Xcp_00823]
AUTOSAR Basic Software Module
shall be named according the defined
convention
[SRS_BSW_00374] All Basic Software Modules shall [SWS_Xcp_00807]
provide a readable module vendor
identification
[SRS_BSW_00379] All software modules shall provide a [SWS_Xcp_00807]
module identifier in the header file
and in the module XML description
file.
[SRS_BSW_00380] Configuration parameters being [SWS_Xcp_00501]
stored in memory shall be placed into
separate c-files
[SRS_BSW_00383] The Basic Software Module [SWS_Xcp_00501]
specifications shall specify which
other configuration files from other
modules they use at least in the
description
[SRS_BSW_00402] Each module shall provide version [SWS_Xcp_00807]
information
[SRS_BSW_00404] BSW Modules shall support [SWS_Xcp_00742]
post-build configuration
5
4
Requirement Description Satisfied by
[SRS_BSW_00405] BSW Modules shall support multiple [SWS_Xcp_00803]
configuration sets
[SRS_BSW_00407] Each BSW module shall provide a [SWS_Xcp_00807]
function to read out the version
information of a dedicated module
implementation
[SRS_BSW_00411] All AUTOSAR Basic Software [SWS_Xcp_00807]
Modules shall apply a naming rule for
enabling/disabling the existence of
the API
[SRS_BSW_00414] Init functions shall have a pointer to a [SWS_Xcp_00803]
configuration structure as single
parameter
[SRS_BSW_00419] If a pre-compile time configuration [SWS_Xcp_00501]
parameter is implemented as const
it should be placed into a separate
c-file
[SRS_BSW_00424] BSW module main processing [SWS_Xcp_00823]
functions shall not be allowed to enter
a wait state
[SRS_BSW_00433] Main processing functions are only [SWS_Xcp_00823]
allowed to be called from task bodies
provided by the BSW Scheduler
[SRS_Xcp_29001] The AUTOSAR XCP module shall be [SWS_Xcp_00701] [SWS_Xcp_00860]
located above the bus interfaces /
Socket Adaptor
[SRS_Xcp_29002] The AUTOSAR XCP shall make use [SWS_Xcp_00712] [SWS_Xcp_00714]
of the data transmit- and receive APIs [SWS_Xcp_00720] [SWS_Xcp_00734]
of the Bus Interfaces [SWS_Xcp_00862]
[SRS_Xcp_29003] The AUTOSAR XCP messages shall [SWS_Xcp_00702] [SWS_Xcp_CONSTR_00861]
be identified by unique PDU-IDs
[SRS_Xcp_29004] The XCP Specification Version 1.1 [SWS_Xcp_00703]
shall be used
[SRS_Xcp_29005] XCP on CAN shall be supported [SWS_Xcp_00713]
[SRS_Xcp_29006] XCP on FlexRay shall be supported [SWS_Xcp_00719]
[SRS_Xcp_29007] XCP on Ethernet shall be supported [SWS_Xcp_00733]
[SRS_Xcp_29008] The code generator of the XCP [SWS_Xcp_00853]
Module shall generate the A2L IF_
DATA section
[SRS_Xcp_29009] The slave shall transfer the contents [SWS_Xcp_00705]
of the elements defined in each ODT
of the DAQ-list to the master
[SRS_Xcp_29010] Synchronous Data Stimulation shall [SWS_Xcp_00707]
be the inverse mode of Synchronous
Data Acquisition
[SRS_Xcp_29012] The XCP master shall already send [SWS_Xcp_00710]
the next request before having
received the response on the
previous request
[SRS_Xcp_29013] It shall be possible to configure the [SWS_Xcp_00706]
DAQ Lists dynamically
[SRS_Xcp_29014] It shall be possible to transmit a [SWS_Xcp_00709]
timestamp within the XCP packet
5
4
Requirement Description Satisfied by
[SRS_Xcp_29015] It shall be possible to bypass data by [SWS_Xcp_00761]
making use of Synchronous Data
Acquisition and Synchronous Data
Stimulation simultaneously
[SRS_Xcp_29016] The feature "Seed&Key" shall be [SWS_Xcp_00766]
used for protection handling purpose
[SRS_Xcp_29017] The AUTOSAR XCP module shall [SWS_Xcp_00803]
implement an interface for
initialization.
[SRS_Xcp_29018] Page switching shall be supported [SWS_Xcp_00852]
[SRS_Xcp_29019] DAQ configuration storing with [SWS_Xcp_00854]
power-up data transfer (RESUME
mode) shall be supported
[SRS_Xcp_29020] Flash Programming for ECU [SWS_Xcp_00855] [SWS_Xcp_00856]
development purposes
[SRS_Xcp_29030] The AUTOSAR XCP module shall be [SWS_Xcp_00863]
located above the PduR
[SRS_Xcp_29031] The AUTOSAR XCP shall make use [SWS_Xcp_00864] [SWS_Xcp_00865]
of the data transmit- and receive APIs [SWS_Xcp_00866]
of the PduR
Table 6.1: Requirements Tracing
7 Functional specification
The specification of the module XCP shall define all parameters and interfaces, which
are required to use the ASAM XCP protocol specification within an AUTOSAR environ-
ment.
[SWS_Xcp_00701]
Status: OBSOLETE
Use instead: SWS_Xcp_00860
Upstream requirements: SRS_Xcp_29001
dThe AUTOSAR XCP Module be located above the bus specific Interfaces in case of
FlexRay and Can. In case of Ethernet, the AUTOSAR XCP module shall be located
above the Socket Adaptor.c
dThe AUTOSAR XCP Module and the bus specific Interfaces shall be located above
the AUTOSAR PDU Routing module (PduR) [4].c
[SWS_Xcp_00702]
Upstream requirements: SRS_Xcp_29003
dFor transmitting and receiving of XCP messages, unique PDU-IDs shall be used.c
dEach XcpRxPdu and XcpTxPdu shall refer to global PDU that has KeepLocalP-
duBuffer set to FALSE.c
[SWS_Xcp_00703]
Upstream requirements: SRS_Xcp_29004
dThe AUTOSAR XCP Module shall support the ASAM XCP Specification Version 1.1,
except for XCP on CAN where ASAM XCP Specification Version 1.2 shall be sup-
ported.c
[SWS_Xcp_00705]
Upstream requirements: SRS_Xcp_29009
dThe AUTOSAR XCP Module shall support the basic feature "Synchronous data ac-
quisition (measurement) ". Please refer to [3]c
[SWS_Xcp_00706]
Upstream requirements: SRS_Xcp_29013
dThe AUTOSAR XCP Module shall support the feature "Dynamic DAQ Configuration".
according to [3]c
[SWS_Xcp_00707]
Upstream requirements: SRS_Xcp_29010
dThe AUTOSAR XCP Module shall support the basic feature "Synchronous data stim-
ulation" according to [3]c
[SWS_Xcp_00708] dThe AUTOSAR XCP Module shall support the basic feature "On-
line memory calibration (read / write access) ", according to [3]c
[SWS_Xcp_00709]
Upstream requirements: SRS_Xcp_29014
dThe AUTOSAR XCP Module shall support the feature "Timestamped Data Transfer",
according to [3]c
[SWS_Xcp_00768] dThe ECU local time shall be derived from the AUTOSAR OS.c
[SWS_Xcp_00711] dThe AUTOSAR XCP Module shall support the feature "Block
communication mode", according to [3]c
[SWS_Xcp_00761]
Upstream requirements: SRS_Xcp_29015
dThe AUTOSAR XCP Module shall support the feature "Bypassing", according to [3]c
[SWS_Xcp_00766]
Upstream requirements: SRS_Xcp_29016
dThe AUTOSAR XCP Module shall support the feature "Seed & Key" according to [3]c
[SWS_Xcp_00712]
Status: OBSOLETE
Use instead: SWS_Xcp_00862
Upstream requirements: SRS_Xcp_29002
dFor sending and receiving of calibration data, the sending and receiving APIs specified
within the AUTOSAR BSW Bus Interfaces (FlexRay Interface, CAN Interface, TCP/IP
Socket Adaptor) shall be used. Please refer to chapter 7.1, 7.2 and 7.3.c
dFor sending and receiving of calibration via CAN, FlexRay and Ethernet (i.e. TCP/IP),
the sending and receiving APIs specified within the AUTOSAR PDU Routing module
(PduR) [4] shall be used. Please refer to chapter 7.1, 7.2 and 7.3.c
Note: AUTOSAR PDU Routing module (PduR) [4] and AUTOSAR BSW Linklayer Sdu
Routing Module (LSduR) route the XCP data as PDU to the according AUTOSAR BSW
Bus Interfaces (CAN Interface, FlexRay Interface and Ethernet Interface (via Socket
Adapter and TcpIp module)). The transmission and reception paths differ slighlty.
For example the transmission path is denoted in the following items. Please refer
to Chapter 9 for more details:
• XCP data transmitted on CAN or FlexRay: XCP -> PduR -> LSduR ->
<Can|Fr>If
• XCP data transmitted on Ethernet (via. TcpIp): XCP -> PduR -> SoAd ->
TcpIp -> LSduR -> EthIf
[SWS_Xcp_00852]
Upstream requirements: SRS_Xcp_29018
dThe AUTOSAR XCP Module shall support the feature "Page switching", according to
[3]c
[SWS_Xcp_00853]
Upstream requirements: SRS_Xcp_29008
dThe code generator of the XCP Module shall generate the A2L IF_DATA section,
based on the configuration of XCPc
[SWS_Xcp_00854]
Upstream requirements: SRS_Xcp_29019
dThe AUTOSAR XCP Module shall support the feature "Power-Up data transfer (RE-
SUME MODE)", according to [3]c
[SWS_Xcp_00855]
Upstream requirements: SRS_Xcp_29020
dThe AUTOSAR XCP Module shall support the flash programming (PGM) according
to [3]c
[SWS_Xcp_00856]
Upstream requirements: SRS_Xcp_29020
dIndication the end of a programming sequence is supported using the optional com-
mand "PROGRAM_RESET", where the slave will go to disconnected state but without
forcing a device resetc
[SWS_Xcp_00859]
Status: OBSOLETE
Use instead: SWS_Xcp_00863
dThe XCP module shall wait for the Xcp_<Lo>TxConfirmation (positive or negative)
after each call to <Lo>_Transmit to avoid overwriting previously transmitted datac
dFThe XCP module shall wait for the Xcp_TxConfirmation (positive or negative) af-
ter each call to PduR_XcpTransmit to avoid overwriting previously transmitted data.c
[SWS_Xcp_00713]
Upstream requirements: SRS_Xcp_29005
dThe AUTOSAR XCP Module shall support the CAN communications bus according to
[8]c
[SWS_Xcp_00714]
Status: OBSOLETE
Use instead: SWS_Xcp_00864
Upstream requirements: SRS_Xcp_29002
dXCP data sent and received via CAN, the PDUs have to be transmitted and received
using the transmitting and receive APIs provided by the AUTOSAR CAN Interface,
according to [9]c
dXCP data sent and received via CAN, the PDUs shall be transmitted and received
using the transmit and receive APIs provided by the AUTOSAR PDU Routing module
(PduR) [4].c
[SWS_Xcp_00715] dFor sending and receiving XCP data via CAN, at least two differ-
ent CAN identifiers have to be configured to be used by XCP.c
[SWS_Xcp_00719]
Upstream requirements: SRS_Xcp_29006
dThe AUTOSAR XCP Module shall support the FlexRay communications bus accord-
ing to [10]c
[SWS_Xcp_00720]
Status: OBSOLETE
Use instead: SWS_Xcp_00865
Upstream requirements: SRS_Xcp_29002
dXCP data sent and received via FlexRay, the PDUs have to be transmitted and re-
ceived using the transmit and receive APIs provided by the AUTOSAR FlexRay Inter-
face according to [11].c
dXCP data sent and received via FlexRay, the PDUs shall be transmitted and received
using the transmit and receive APIs provided by the AUTOSAR PDU Routing module
(PduR) [4].c
[SWS_Xcp_00721] dAll XCP on FlexRay LPDUs always are event driven. Please refer
to Chapter 1.1.2 "FlexRay Frame Type" of [10]c
Note:
This restriction prevents disturbances of ongoing FlexRay communication.
[SWS_Xcp_00724] dThe FlexRay PDU length used by the AUTOSAR XCP module
shall be set using the corresponding parameters according to [10]c
[SWS_Xcp_00726] dThe ASAM MCD 2MC description file (i.e. A2L file) describes to
which extent the XCP-dedicated buffers of a specific slave can be configured for XCP
communication.c
[SWS_Xcp_00728] dThe XCP master gets the information about the XCP dedicated
FlexRay Communication Controller buffers from the ASAM MCD 2MC description file.c
[SWS_Xcp_00731] dFor XCP on FlexRay, the Tail consists of a Control Field contain-
ing optional FILL bytes according to [10].c
[SWS_Xcp_00732] dThe AUTOSAR XCP module shall be able to pack multiple XCP
messages into one FlexRay Frame according to [10].c
[SWS_Xcp_00733]
Upstream requirements: SRS_Xcp_29007
dThe AUTOSAR XCP Module shall support the Ethernet communications bus accord-
ing to [12]c
[SWS_Xcp_00734]
Status: OBSOLETE
Use instead: SWS_Xcp_00866
Upstream requirements: SRS_Xcp_29002
dXCP data sent and received via Ethernet, the PDUs have to be transmitted and
received using the transmitting and receive APIs provided by the AUTOSAR Socket
Adaptor according to [13].c
[SWS_Xcp_00866] Use APIs of PduR for exchanging data via Ethernet (i.e. TcpIp)
Status: DRAFT
Replaces: SWS_Xcp_00734
Upstream requirements: SRS_Xcp_29031
dXCP data sent and received via Ethernet, the PDUs have to be transmitted and re-
ceived using the transmitting and receive APIs provided by the AUTOSAR PDU Router
according to [4].c
[SWS_Xcp_00736] dThe AUTOSAR XCP slave only accepts one connection at the
time.c
[SWS_Xcp_00737] dIf the socket is closed while in XCP connected state, the slave
device will perform an XCP disconnect, which means that all data acquisition will be
stopped.c
[SWS_Xcp_00740] dThe upper performance limit depends on the protocol stack of the
host system. The corresponding parameters defined according to [12] have to be set.c
[SWS_Xcp_00710]
Upstream requirements: SRS_Xcp_29012
dThe AUTOSAR XCP Module shall support the feature "Interleaved communication
mode", according to according to [3]c
[SWS_Xcp_00741]
Upstream requirements: SRS_BSW_00344
[SWS_Xcp_00742]
Upstream requirements: SRS_BSW_00404, SRS_BSW_00345
dThe XCP module shall support pre-compile time, link-time and post-build-time config-
uration.c
[SWS_Xcp_00763]
Upstream requirements: SRS_BSW_00327
dThe error values and EventIds are named in capital letters according to the scheme
XCP_E_<NAME>, where NAME describes the error/EventId and may consist of sev-
eral words separated by underscores.c
8 API specification
8.2.1 Xcp_ConfigType
8.3.1 Xcp_Init
d
Service Name Xcp_Init
Syntax void Xcp_Init (
const Xcp_ConfigType* Xcp_ConfigPtr
)
Service ID [hex] 0x00
Sync/Async Synchronous
Reentrancy Non Reentrant
Parameters (in) Xcp_ConfigPtr Pointer to a selected configuration structure
Parameters (inout) None
Parameters (out) None
Return value void –
Description This service initializes interfaces and variables of the AUTOSAR XCP layer.
Available via Xcp.h
8.3.2 Xcp_GetVersionInfo
[SWS_Xcp_00825] dIf development error detection for the Xcp module is en-
abled, then the function Xcp_GetVersionInfo shall check whether the param-
eter VersioninfoPtr is a NULL pointer (NULL_PTR). If VersioninfoPtr is a NULL
pointer, then the function Xcp_GetVersionInfo shall raise the development error
XCP_E_PARAM_POINTER and return.c
8.3.3 Xcp_SetTransmissionMode
4
Parameters (out) None
Return value None
Description This API is used to turn on and off of the TX capabilities of used communication bus channel in
XCP module.
Available via Xcp.h
Note: It could be derived from <Bus>If configuration and the global PDU parameter, to
which specific communication channel the PDU is assigned to.
8.4.1 Xcp_RxIndication
4
Parameters (in) RxPduId ID of the received PDU.
PduInfoPtr Contains the length (SduLength) of the received PDU, a pointer
to a buffer (SduDataPtr) containing the PDU, and the MetaData
related to this PDU.
Parameters (inout) None
Parameters (out) None
Return value None
Description Indication of a received PDU from a lower layer communication interface module.
Available via Xcp.h
[SWS_Xcp_00847]
Status: OBSOLETE
Use instead: SWS_Xcp_00867
dThe callback function Xcp_RxIndication shall inform the DET, if development error
detection is enabled (XCP_DEV_ERROR_DETECT is set to TRUE) and if function call
has failed because of the following reasons:
• Xcp was not initialized (XCP_E_UNINIT)
• PduInfoPtr equals NULL_PTR (XCP_E_PARAM_POINTER)
• Invalid PDUID (XCP_E_INVALID_PDUID)
c
8.4.2 Xcp_TxConfirmation
Note:
The callback function Xcp_TxConfirmation is called by the Bus Interfaces, Ethernet
Socket Adaptor or CDD and is implemented by the Xcp module.
[SWS_Xcp_00840]
Status: OBSOLETE
Use instead: SWS_Xcp_00868
dIf development error detection for the XCP module is enabled: if the function Xcp_-
<Lo>TxConfirmation is called before the XCP was initialized successfully, the func-
tion Xcp_<Lo>TxConfirmation shall raise the development error XCP_E_UNINIT
and return.c
dIf development error detection for the XCP module is enabled: if the function Xcp_-
TxConfirmation is called before the XCP was initialized successfully, the function
Xcp_TxConfirmation shall raise the development error XCP_E_UNINIT and re-
turn.c
[SWS_Xcp_00841]
Status: OBSOLETE
Use instead: SWS_Xcp_00869
dCaveats of Xcp_<Lo>TxConfirmation:
• The call context is either on interrupt level (interrupt mode) or on task level
• The Xcp module is initialized correctly.
c
dCaveats of Xcp_TxConfirmation:
• The call context is either on interrupt level (interrupt mode) or on task level
• The Xcp module is initialized correctly.
c
8.4.3 Xcp_TriggerTransmit
4
Description Within this API, the upper layer module (called module) shall check whether the available data
fits into the buffer size reported by PduInfoPtr->SduLength. If it fits, it shall copy its data into the
buffer provided by PduInfoPtr->SduDataPtr and update the length of the actual copied data in
PduInfoPtr->SduLength. If not, it returns E_NOT_OK without changing PduInfoPtr.
Available via Xcp.h
Note:
The callback function Xcp_TriggerTransmit is called by the Bus Interfaces, Ether-
net Socket Adaptor or CDD and is implemented by the Xcp module.
[SWS_Xcp_00842]
Status: OBSOLETE
Use instead: SWS_Xcp_00870
dIf development error detection for the XCP module is enabled: if the function
Xcp_<Lo>TriggerTransmit is called before the XCP was initialized success-
fully, the function Xcp_<Lo>TriggerTransmit shall raise the development error
XCP_E_UNINIT and return E_NOT_OK.c
dIf development error detection for the XCP module is enabled: if the function
Xcp_TriggerTransmit is called before the XCP was initialized successfully, the
function Xcp_TriggerTransmit shall raise the development error XCP_E_UNINIT
and return E_NOT_OK.c
[SWS_Xcp_00843]
Status: OBSOLETE
Use instead: SWS_Xcp_00871
dCaveats of Xcp_<Lo>TriggerTransmit:
• The call context is either on interrupt level (interrupt mode) or on task level
• The Xcp module is initialized correctly.
c
dCaveats of Xcp_TriggerTransmit:
• The call context is either on interrupt level (interrupt mode) or on task level
• The Xcp module is initialized correctly.
c
8.5.1 Xcp_MainFunction
d
Service Name Xcp_MainFunction
Syntax void Xcp_MainFunction (
void
)
Service ID [hex] 0x04
Description Scheduled function of the XCP module
Available via SchM_Xcp.h
In this chapter, all interfaces are listed where the target function could be configured.
The target function is usually a call-back function. The names of these kind of inter-
faces is not fixed because they are configurable.
The XCP module offers configurable interfaces to be used by Complex Driver(s).
9 Sequence diagrams
PduR_XcpTransmit()
FrIf_Transmit()
LSduR_FrIfTriggerTransmit()
Xcp_TriggerTransmit()
Fr_TransmitTxLPdu()
Fr_CheckTxLPduStatus()
LSduR_FrIfTxConfirmation()
Xcp_TxConfirmation()
LSduR_FrIfRxIndication()
Xcp_RxIndication()
PduR_XcpTransmit()
CanIf_Transmit()
Can_Write()
CanIf_TxConfirmation()
LSduR_CanIfTxConfirmation()
Xcp_TxConfirmation()
CanIf_RxIndication()
LSduR_CanIfRxIndication()
Xcp_RxIndication()
PduR_XcpTransmit()
SoAd_IfTransmit()
PduR_SoAdlfTxConfirmation()
Xcp_TxConfirmation()
PduR_SoAdIfRxIndication()
Xcp_RxIndication()
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
XCP.
Chapter 10.3 specifies published information of the module XCP.
[SWS_Xcp_00102]
Upstream requirements: SRS_BSW_00159
dThe listed configuration items can be derived from a network description database,
which is based on the EcuConfigurationTemplate. The configuration tool shall extract
all information to configure the XCP.c
[SWS_Xcp_00103]
Upstream requirements: SRS_BSW_00167
dThe configuration tool must check the consistency of the configuration at configuration
time.c
[SWS_Xcp_00104]
Upstream requirements: SRS_BSW_00167
dConfiguration rules and constraints for plausibility checks shall be performed during
configuration time, wherever possible.c
[SWS_Xcp_00105]
Upstream requirements: SRS_BSW_00167
10.2.1 Xcp
Included Containers
Container Name Multiplicity Scope / Dependency
XcpConfig 1 This container contains the configuration parameters and sub
containers of the AUTOSAR Xcp module.
XcpGeneral 1 This container contains the general configuration parameters of
the XCP.
10.2.2 XcpGeneral
Included Parameters
Parameter Name Multiplicity ECUC ID
XcpDaqConfigType 1 [ECUC_Xcp_00164]
XcpDaqCount 1 [ECUC_Xcp_00012]
XcpDevErrorDetect 1 [ECUC_Xcp_00003]
XcpFlashProgrammingEnabled 1 [ECUC_Xcp_00181]
XcpIdentificationFieldType 1 [ECUC_Xcp_00170]
XcpMainFunctionPeriod 1 [ECUC_Xcp_00014]
5
4
Included Parameters
Parameter Name Multiplicity ECUC ID
XcpMaxCto 1 [ECUC_Xcp_00004]
XcpMaxDto 1 [ECUC_Xcp_00005]
XcpMaxEventChannel 1 [ECUC_Xcp_00011]
XcpMinDaq 1 [ECUC_Xcp_00013]
XcpOdtCount 1 [ECUC_Xcp_00054]
XcpOdtEntriesCount 1 [ECUC_Xcp_00059]
XcpOdtEntrySizeDaq 1 [ECUC_Xcp_00177]
XcpOdtEntrySizeStim 1 [ECUC_Xcp_00178]
XcpOnCanEnabled 1 [ECUC_Xcp_00006]
XcpOnCddEnabled 1 [ECUC_Xcp_00009]
XcpOnEthernetEnabled 1 [ECUC_Xcp_00008]
XcpOnFlexRayEnabled 1 [ECUC_Xcp_00007]
XcpPrescalerSupported 1 [ECUC_Xcp_00169]
XcpSuppressTxSupport 1 [ECUC_Xcp_00176]
XcpTimestampTicks 1 [ECUC_Xcp_00167]
XcpTimestampType 1 [ECUC_Xcp_00166]
XcpTimestampUnit 1 [ECUC_Xcp_00168]
XcpVersionInfoApi 1 [ECUC_Xcp_00002]
XcpCounterRef 1 [ECUC_Xcp_00162]
XcpNvRamBlockIdRef 0..1 [ECUC_Xcp_00180]
No Included Containers
4
Scope / Dependency scope: ECU
dependency: If DAQ_CONFIG_TYPE = dynamic, MAX_DAQ equals MIN_DAQ+DAQ_
COUNT.
4
Multiplicity 1
Type EcucFloatParamDef
Range ]0 .. 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
4
Post-build time –
Scope / Dependency scope: ECU
dependency: This parameter is available only if XcpDaqConfigType is set to "1" i.e
DAQ_DYNAMIC
4
Post-build time –
Scope / Dependency scope: local
4
Scope / Dependency scope: local
4
Post-Build Variant Multiplicity true
Post-Build Variant Value true
Multiplicity Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time –
Post-build time X VARIANT-POST-BUILD
Value Configuration Class Pre-compile time X VARIANT-PRE-COMPILE
Link time –
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: local
10.2.3 XcpConfig
No Included Parameters
Included Containers
Container Name Multiplicity Scope / Dependency
XcpCommunicationChannel 0..* This container represents the configuration of the communication
channel of XCP.
XcpDaqList 1..* This container contains the configuration of the DAQs.
XcpEventChannel 1..* This container contains the configuration of event channels on
the XCP slave.
XcpPageSwitching 0..1 This container represents configuration of the page switching
feature.
XcpPdu 1..* Contains PDU information. A PDU may be either a transmission
PDU or a reception PDU.
Xcp: EcucModuleDef
lowerMultiplicity = 0
upperMultiplicity = 1
+container
lowerMultiplicity = 1
upperMultiplicity = *
XcpEventChannel:
+subContainer EcucParamConfContainerDef
lowerMultiplicity = 1
upperMultiplicity = *
XcpDaqList: XcpOdt:
EcucParamConfContainerDef +subContainer EcucParamConfContainerDef
lowerMultiplicity = 1 lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = *
+subContainer
XcpDto:
+subContainer EcucParamConfContainerDef
lowerMultiplicity = 0
upperMultiplicity = *
XcpCommunicationChannel:
+subContainer EcucParamConfContainerDef
upperMultiplicity = *
lowerMultiplicity = 0
XcpPageSwitching: XcpSegment:
+subContainer EcucParamConfContainerDef +subContainer EcucParamConfContainerDef
lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1 upperMultiplicity = *
10.2.4 XcpDaqList
Included Parameters
Parameter Name Multiplicity ECUC ID
XcpDaqListNumber 1 [ECUC_Xcp_00051]
XcpDaqListType 1 [ECUC_Xcp_00052]
XcpMaxOdt 1 [ECUC_Xcp_00053]
XcpMaxOdtEntries 1 [ECUC_Xcp_00058]
Included Containers
Container Name Multiplicity Scope / Dependency
XcpDto 0..* This container collects data transfer object specific parameters
for the DAQ list.
XcpOdt 0..* This container contains ODT-specific parameter for the DAQ list.
10.2.5 XcpDto
Included Parameters
Parameter Name Multiplicity ECUC ID
XcpDtoPid 1 [ECUC_Xcp_00066]
XcpDto2PduMapping 1 [ECUC_Xcp_00067]
No Included Containers
10.2.6 XcpOdt
Included Parameters
Parameter Name Multiplicity ECUC ID
XcpOdtEntryMaxSize 1 [ECUC_Xcp_00060]
XcpOdtNumber 0..1 [ECUC_Xcp_00057]
XcpOdt2DtoMapping 0..1 [ECUC_Xcp_00056]
Included Containers
Container Name Multiplicity Scope / Dependency
XcpOdtEntry 1..* This container collects all configuration parameters that
comprise an ODT entry.
4
Multiplicity 0..1
Type EcucIntegerParamDef (Symbolic Name generated for this parameter)
Range 0 .. 251
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
10.2.7 XcpOdtEntry
Included Parameters
Parameter Name Multiplicity ECUC ID
XcpOdtEntryAddress 0..1 [ECUC_Xcp_00063]
XcpOdtEntryBitOffset 0..1 [ECUC_Xcp_00179]
XcpOdtEntryLength 0..1 [ECUC_Xcp_00064]
XcpOdtEntryNumber 0..1 [ECUC_Xcp_00062]
No Included Containers
4
Link time –
Post-build time –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU
4
Post-build time –
Scope / Dependency scope: ECU
XcpDaqList: EcucParamConfContainerDef
lowerMultiplicity = 1
upperMultiplicity = *
+subContainer
+subContainer
XcpOdt:
XcpOdt2DtoMapping:
EcucParamConfContainerDef
+reference EcucReferenceDef XcpDto:
+destination
lowerMultiplicity = 0 EcucParamConfContainerDef
lowerMultiplicity = 0
upperMultiplicity = *
upperMultiplicity = 1 lowerMultiplicity = 0
upperMultiplicity = *
XcpOdtNumber:
EcucIntegerParamDef
+parameter min = 0
max = 251
symbolicNameValue = true
lowerMultiplicity = 0
upperMultiplicity = 1
XcpOdtEntryMaxSize:
+parameter EcucIntegerParamDef
min = 0
max = 254
XcpOdtEntry: XcpOdtEntryNumber:
EcucParamConfContainerDef EcucIntegerParamDef
+parameter
lowerMultiplicity = 1 min = 0
upperMultiplicity = * max = 254
lowerMultiplicity = 0
upperMultiplicity = 1
XcpOdtEntryAddress:
+parameter EcucLinkerSymbolDef
lowerMultiplicity = 0
upperMultiplicity = 1
+subContainer
XcpOdtEntryLength:
EcucIntegerParamDef
+parameter
min = 0
max = 255
lowerMultiplicity = 0
upperMultiplicity = 1
XcpOdtEntryBitOffset:
EcucIntegerParamDef
+parameter
min = 0
max = 31
lowerMultiplicity = 0
upperMultiplicity = 1
10.2.8 XcpEventChannel
Included Parameters
Parameter Name Multiplicity ECUC ID
XcpEventChannelConsistency 1 [ECUC_Xcp_00171]
XcpEventChannelMaxDaqList 1 [ECUC_Xcp_00153]
XcpEventChannelNumber 1 [ECUC_Xcp_00152]
XcpEventChannelPriority 1 [ECUC_Xcp_00154]
XcpEventChannelTimeCycle 1 [ECUC_Xcp_00173]
XcpEventChannelTimeUnit 0..1 [ECUC_Xcp_00174]
XcpEventChannelType 1 [ECUC_Xcp_00172]
XcpEventChannelTriggeredDaqListRef 0..* [ECUC_Xcp_00151]
No Included Containers
4
Post-Build Variant Value false
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: ECU
4
TIMESTAMP_UNIT_1PS Unit is 1 picosecond.
TIMESTAMP_UNIT_1S Unit is 1 second.
TIMESTAMP_UNIT_1US Unit is 1 microsecond.
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
dependency: Dependent on the Parameter EventChannelTimeCycle. When this
parameter is set to 0, the entire event channel time unit parameter shall be ignored.
4
Type Reference to XcpDaqList
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
XcpConfig:
EcucParamConfContainerDef XcpEventChannelTriggeredDaqListRef:
EcucReferenceDef +literal EVENT:
EcucEnumerationLiteralDef
lowerMultiplicity = 0
upperMultiplicity = *
+reference
+subContainer
XcpEventChannel:
EcucParamConfContainerDef +parameter
TIMESTAMP_UNIT_1PS:
lowerMultiplicity = 1
+literal EcucEnumerationLiteralDef
upperMultiplicity = *
XcpEventChannelTimeUnit:
EcucEnumerationParamDef
lowerMultiplicity = 0
upperMultiplicity = 1 +literal TIMESTAMP_UNIT_10PS:
+parameter EcucEnumerationLiteralDef
TIMESTAMP_UNIT_100PS:
+literal EcucEnumerationLiteralDef
XcpEventChannelNumber:
+parameter EcucIntegerParamDef +literal TIMESTAMP_UNIT_1NS:
EcucEnumerationLiteralDef
min = 0
max = 65534
symbolicNameValue = true
+literal TIMESTAMP_UNIT_10NS:
EcucEnumerationLiteralDef
XcpEventChannelTimeCycle:
EcucIntegerParamDef
+parameter
min = 0
+literal TIMESTAMP_UNIT_100NS:
max = 255
EcucEnumerationLiteralDef
lowerMultiplicity = 1
upperMultiplicity = 1
min = 0
max = 255
+literal TIMESTAMP_UNIT_10US:
EcucEnumerationLiteralDef
XcpEventChannelMaxDaqList:
+parameter EcucIntegerParamDef
min = 0
max = 255 TIMESTAMP_UNIT_100US:
+literal EcucEnumerationLiteralDef
TIMESTAMP_UNIT_100MS:
+literal EcucEnumerationLiteralDef
+literal DAQ_STIM:
EcucEnumerationLiteralDef
+literal
TIMESTAMP_UNIT_1S:
EcucEnumerationLiteralDef
10.2.9 XcpPdu
No Included Parameters
Container Choices
Container Name Multiplicity Scope / Dependency
XcpRxPdu 0..1 This container specifies received PDUs.
XcpTxPdu 0..1 This container specifies transmission PDUs.
Xcp: EcucModuleDef
lowerMultiplicity = 0
upperMultiplicity = 1 XcpTxPduId:
EcucIntegerParamDef
XcpTxPdu:
EcucParamConfContainerDef +parameter min = 0
+container max = 65535
lowerMultiplicity = 0 withAuto = true
XcpConfig: EcucParamConfContainerDef upperMultiplicity = 1 symbolicNameValue = true
+reference XcpTxPduRef:
EcucReferenceDef
+choice
+subContainer
XcpPdu: +destination
EcucChoiceContainerDef
Pdu:
lowerMultiplicity = 1 EcucParamConfContainerDef
upperMultiplicity = *
lowerMultiplicity = 0
upperMultiplicity = *
+destination
lowerMultiplicity = 0
+choice upperMultiplicity = 1
XcpRxPduId:
EcucIntegerParamDef
+parameter
min = 0
max = 65535
withAuto = true
symbolicNameValue = true
10.2.10 XcpRxPdu
Included Parameters
Parameter Name Multiplicity ECUC ID
XcpRxPduId 1 [ECUC_Xcp_00106]
XcpRxPduRef 1 [ECUC_Xcp_00107]
No Included Containers
10.2.11 XcpTxPdu
Included Parameters
Parameter Name Multiplicity ECUC ID
XcpTxPduId 1 [ECUC_Xcp_00103]
XcpTxPduRef 1 [ECUC_Xcp_00104]
No Included Containers
4
Link time –
Post-build time X VARIANT-POST-BUILD
Scope / Dependency scope: ECU
10.2.12 XcpCommunicationChannel
Included Parameters
Parameter Name Multiplicity ECUC ID
XcpChannelRxPduRef 0..1 [ECUC_Xcp_00185]
XcpChannelTxPduRef 1 [ECUC_Xcp_00184]
XcpComMChannelRef 1 [ECUC_Xcp_00186]
No Included Containers
Xcp: EcucModuleDef
lowerMultiplicity = 0
upperMultiplicity = 1
+container
XcpConfig: EcucParamConfContainerDef
XcpTxPduRef:
EcucReferenceDef
+reference
+subContainer
XcpTxPdu:
XcpCommunicationChannel: XcpChannelTxPduRef: +destination EcucParamConfContainerDef
+reference
EcucParamConfContainerDef EcucReferenceDef
lowerMultiplicity = 0
upperMultiplicity = * upperMultiplicity = 1
lowerMultiplicity = 0 +destination
XcpChannelRxPduRef: +destination
+reference EcucReferenceDef XcpRxPdu:
+destination
EcucParamConfContainerDef
upperMultiplicity = 1
lowerMultiplicity = 0 lowerMultiplicity = 0
upperMultiplicity = 1
+reference
XcpRxPduRef:
EcucReferenceDef
10.2.13 XcpPageSwitching
No Included Parameters
Included Containers
Container Name Multiplicity Scope / Dependency
XcpSegment 0..* This container represents configuration of the page switching
segment element.
Xcp: EcucModuleDef
lowerMultiplicity = 0
upperMultiplicity = 1
+container
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = * upperMultiplicity = 1
XcpWorkingPageAddress:
+parameter EcucLinkerSymbolDef
+subContainer lowerMultiplicity = 1
upperMultiplicity = 1
XcpPageSwitching:
EcucParamConfContainerDef +subContainer
lowerMultiplicity = 0
upperMultiplicity = 1 XcpSegmentLength:
+parameter EcucIntegerParamDef
lowerMultiplicity = 1
upperMultiplicity = 1
XcpPage: XcpPageAddress:
+subContainer EcucParamConfContainerDef+parameter EcucLinkerSymbolDef
lowerMultiplicity = 0 lowerMultiplicity = 1
upperMultiplicity = 254 upperMultiplicity = 1
10.2.14 XcpSegment
Included Parameters
Parameter Name Multiplicity ECUC ID
XcpReferencePageAddress 1 [ECUC_Xcp_00189]
XcpSegmentLength 1 [ECUC_Xcp_00191]
XcpWorkingPageAddress 1 [ECUC_Xcp_00190]
Included Containers
Container Name Multiplicity Scope / Dependency
XcpPage 0..254 This container represents configuration of the optional page
element.
4
Regular Expression –
Value Configuration Class Pre-compile time X All Variants
Link time –
Post-build time –
Scope / Dependency scope: local
10.2.15 XcpPage
Included Parameters
Parameter Name Multiplicity ECUC ID
XcpPageAddress 1 [ECUC_Xcp_00193]
No Included Containers
[SWS_Xcp_NA_00999]
Upstream requirements: SRS_BSW_00171, SRS_BSW_00170, SRS_BSW_00375, SRS_BSW_-
00416, SRS_BSW_00168, SRS_BSW_00423, SRS_BSW_00425,
SRS_BSW_00426, SRS_BSW_00427, SRS_BSW_00428, SRS_BSW_-
00432, SRS_BSW_00336, SRS_BSW_00417, SRS_BSW_00161,
SRS_BSW_00162, SRS_BSW_00005, SRS_BSW_00415, SRS_BSW_-
00164, SRS_BSW_00325, SRS_BSW_00413, SRS_BSW_00347,
SRS_BSW_00335, SRS_BSW_00410, SRS_BSW_00314, SRS_BSW_-
00328, SRS_BSW_00312, SRS_BSW_00006, SRS_BSW_00377,
SRS_BSW_00306, SRS_BSW_00309, SRS_BSW_00360, SRS_BSW_-
00330, SRS_BSW_00331, SRS_BSW_00009, SRS_BSW_00401,
SRS_BSW_00172, SRS_BSW_00010, SRS_BSW_00333, SRS_BSW_-
00321, SRS_BSW_00341, SRS_Xcp_29008
Number Heading
[SWS_Xcp_00102]
[SWS_Xcp_00103]
[SWS_Xcp_00104]
[SWS_Xcp_00105]
[SWS_Xcp_00501]
[SWS_Xcp_00701]
[SWS_Xcp_00702]
[SWS_Xcp_00703]
[SWS_Xcp_00705]
[SWS_Xcp_00706]
[SWS_Xcp_00707]
[SWS_Xcp_00708]
[SWS_Xcp_00709]
[SWS_Xcp_00710]
[SWS_Xcp_00711]
[SWS_Xcp_00712]
[SWS_Xcp_00713]
[SWS_Xcp_00714]
[SWS_Xcp_00715]
[SWS_Xcp_00716]
[SWS_Xcp_00718]
[SWS_Xcp_00719]
[SWS_Xcp_00720]
[SWS_Xcp_00721]
[SWS_Xcp_00722]
[SWS_Xcp_00723]
[SWS_Xcp_00724]
5
4
Number Heading
[SWS_Xcp_00725]
[SWS_Xcp_00726]
[SWS_Xcp_00728]
[SWS_Xcp_00729]
[SWS_Xcp_00730]
[SWS_Xcp_00731]
[SWS_Xcp_00732]
[SWS_Xcp_00733]
[SWS_Xcp_00734]
[SWS_Xcp_00735]
[SWS_Xcp_00736]
[SWS_Xcp_00737]
[SWS_Xcp_00738]
[SWS_Xcp_00739]
[SWS_Xcp_00740]
[SWS_Xcp_00741]
[SWS_Xcp_00742]
[SWS_Xcp_00761]
[SWS_Xcp_00763]
[SWS_Xcp_00766]
[SWS_Xcp_00768]
[SWS_Xcp_00801] Definition of imported datatypes of module Xcp
[SWS_Xcp_00802]
[SWS_Xcp_00803] Definition of API function Xcp_Init
[SWS_Xcp_00807] Definition of API function Xcp_GetVersionInfo
[SWS_Xcp_00813] Definition of callback function Xcp_<Lo>RxIndication
[SWS_Xcp_00814] Definition of callback function Xcp_<Lo>TxConfirmation
[SWS_Xcp_00823] Definition of scheduled function Xcp_MainFunction
[SWS_Xcp_00824]
[SWS_Xcp_00825]
[SWS_Xcp_00832] Definition of optional interfaces in module Xcp
[SWS_Xcp_00835] Definition of callback function Xcp_<Lo>TriggerTransmit
[SWS_Xcp_00836]
[SWS_Xcp_00840]
[SWS_Xcp_00841]
[SWS_Xcp_00842]
[SWS_Xcp_00843]
[SWS_Xcp_00844] Definition of callback function Xcp_SetTransmissionMode
5
4
Number Heading
[SWS_Xcp_00845] Definition of datatype Xcp_ConfigType
[SWS_Xcp_00846] Definition of datatype Xcp_TransmissionModeType
[SWS_Xcp_00847]
[SWS_Xcp_00848]
[SWS_Xcp_00849]
[SWS_Xcp_00850]
[SWS_Xcp_00852]
[SWS_Xcp_00853]
[SWS_Xcp_00854]
[SWS_Xcp_00855]
[SWS_Xcp_00856]
[SWS_Xcp_00857] Definiton of development errors in module Xcp
[SWS_Xcp_00859]
[SWS_Xcp_91001] Definition of mandatory interfaces in module Xcp
[SWS_Xcp_NA_-
00999]
Table B.1: Added Specification Items in R22-11
none
none
Number Heading
[SWS_Xcp_00102]
[SWS_Xcp_00103]
[SWS_Xcp_00104]
[SWS_Xcp_00105]
[SWS_Xcp_00501]
[SWS_Xcp_00701]
[SWS_Xcp_00702]
[SWS_Xcp_00703]
[SWS_Xcp_00705]
[SWS_Xcp_00706]
[SWS_Xcp_00707]
[SWS_Xcp_00708]
[SWS_Xcp_00709]
[SWS_Xcp_00710]
[SWS_Xcp_00711]
[SWS_Xcp_00712]
[SWS_Xcp_00713]
[SWS_Xcp_00714]
[SWS_Xcp_00715]
[SWS_Xcp_00716]
[SWS_Xcp_00718]
[SWS_Xcp_00719]
[SWS_Xcp_00720]
[SWS_Xcp_00721]
[SWS_Xcp_00722]
[SWS_Xcp_00723]
[SWS_Xcp_00724]
[SWS_Xcp_00725]
[SWS_Xcp_00726]
[SWS_Xcp_00728]
[SWS_Xcp_00729]
[SWS_Xcp_00730]
[SWS_Xcp_00731]
5
4
Number Heading
[SWS_Xcp_00732]
[SWS_Xcp_00733]
[SWS_Xcp_00734]
[SWS_Xcp_00735]
[SWS_Xcp_00736]
[SWS_Xcp_00737]
[SWS_Xcp_00738]
[SWS_Xcp_00739]
[SWS_Xcp_00740]
[SWS_Xcp_00741]
[SWS_Xcp_00742]
[SWS_Xcp_00761]
[SWS_Xcp_00763]
[SWS_Xcp_00766]
[SWS_Xcp_00768]
[SWS_Xcp_00801] Definition of imported datatypes of module Xcp
[SWS_Xcp_00802]
[SWS_Xcp_00803] Definition of API function Xcp_Init
[SWS_Xcp_00807] Definition of API function Xcp_GetVersionInfo
[SWS_Xcp_00813] Definition of callback function Xcp_<Lo>RxIndication
[SWS_Xcp_00814] Definition of callback function Xcp_<Lo>TxConfirmation
[SWS_Xcp_00823] Definition of scheduled function Xcp_MainFunction
[SWS_Xcp_00824]
[SWS_Xcp_00825]
[SWS_Xcp_00832] Definition of optional interfaces in module Xcp
[SWS_Xcp_00835] Definition of callback function Xcp_<Lo>TriggerTransmit
[SWS_Xcp_00836]
[SWS_Xcp_00840]
[SWS_Xcp_00841]
[SWS_Xcp_00842]
[SWS_Xcp_00843]
[SWS_Xcp_00844] Definition of callback function Xcp_SetTransmissionMode
[SWS_Xcp_00845] Definition of datatype Xcp_ConfigType
[SWS_Xcp_00846] Definition of datatype Xcp_TransmissionModeType
[SWS_Xcp_00847]
[SWS_Xcp_00848]
[SWS_Xcp_00849]
[SWS_Xcp_00850]
5
4
Number Heading
[SWS_Xcp_00852]
[SWS_Xcp_00853]
[SWS_Xcp_00854]
[SWS_Xcp_00855]
[SWS_Xcp_00856]
[SWS_Xcp_00857] Definiton of development errors in module Xcp
[SWS_Xcp_00859]
[SWS_Xcp_91001] Definition of mandatory interfaces in module Xcp
[SWS_Xcp_NA_-
00999]
Table B.2: Added Specification Items in R23-11
none
none
Number Heading
[SWS_Xcp_00860] Location of the XCP module in the AUTOSAR communication stack
[SWS_Xcp_00862] Sending and receiving of calibration data
Waiting for call of Xcp_TxConfirmation to avoid overwritting previously
[SWS_Xcp_00863]
transmitted data
[SWS_Xcp_00864] Use APIs of PduR for exchanging data via CAN
[SWS_Xcp_00865] Use APIs of PduR for exchanging data via FlexRay
[SWS_Xcp_00866] Use APIs of PduR for exchanging data via Ethernet (i.e. TcpIp)
[SWS_Xcp_00867] Development error handling in context of Xcp_RxIndication
[SWS_Xcp_00868] Development error handling in context of Xcp_TxConfirmation
5
4
Number Heading
[SWS_Xcp_00869] Caveats on call of Xcp_TxConfirmation
[SWS_Xcp_00870] Development error handling in context of Xcp_TriggerTransmit
[SWS_Xcp_00871] Caveats on call of Xcp_TriggerTransmit
Table B.3: Added Specification Items in R24-11
Number Heading
[SWS_Xcp_00701]
[SWS_Xcp_00712]
[SWS_Xcp_00714]
[SWS_Xcp_00720]
[SWS_Xcp_00734]
[SWS_Xcp_00813] Definition of callback function Xcp_RxIndication
[SWS_Xcp_00814] Definition of callback function Xcp_TxConfirmation
[SWS_Xcp_00832] Definition of optional interfaces requested by module Xcp
[SWS_Xcp_00835] Definition of callback function Xcp_TriggerTransmit
[SWS_Xcp_00840]
[SWS_Xcp_00841]
[SWS_Xcp_00842]
[SWS_Xcp_00843]
[SWS_Xcp_00847]
[SWS_Xcp_00859]
Table B.4: Changed Specification Items in R24-11
none
Number Heading
[SWS_Xcp_CONSTR_00861] XcpRxPdu and XcpTxPdu constraint for keeping the local buffer
Table B.5: Added Constraints in R24-11
none
none