AUTOSAR Xcp

This service initializes interfaces and variables of the AUTOSAR XCP layer.

Returns the version information of this module.

Indication of a received PDU from a lower layer communication interface module.

The lower layer communication interface module confirms the transmission of a PDU, or the failure to transmit a PDU.

Scheduled function of the XCP module

Within this API , the upper layer module (called module) shall check whether the available data fits into the buffer size reported by Pdu Info Ptr - >Sdu Length. If it fits, it shall copy its data into the buffer provided by Pdu Info Ptr - >Sdu Data Ptr and update the length of the actual copied data in Pdu Info Ptr - >Sdu Length. If not, it returns E_ NOT_ OK without changing Pdu Info Ptr.

This API is used to turn on and off of the TX capabilities of used communication bus channel in XCP module.

This is the type of the data structure containing the initialization data for XCP.

Handles the enabling and disabling of the transmission mode

Black arrows: Data Path (Signals/Pdus) Orange arrows: Control Path (FlexRay Interface) [SWS_Xcp_00860] Location of the XCP module in the AUTOSAR communication stack Status: DRAFT Replaces: SWS_Xcp_00701 Upstream requirements: SRS_Xcp_29030 ⌈The AUTOSAR XCP Module and the bus specific Interfaces shall be located above the AUTOSAR PDU Routing module (PduR) [4]. ⌋

Black arrows: Data Path (Signals/Pdus) Orange arrows: Control Path (FlexRay Interface) [SWS_Xcp_00860] Location of the XCP module in the AUTOSAR communication stack Status: DRAFT Replaces: SWS_Xcp_00701 Upstream requirements: SRS_Xcp_29030 ⌈The AUTOSAR XCP Module and the bus specific Interfaces shall be located above the AUTOSAR PDU Routing module (PduR) [4]. ⌋

Black arrows: Data Path (Signals/Pdus) Orange arrows: Control Path (FlexRay Interface) [SWS_Xcp_00860] Location of the XCP module in the AUTOSAR communication stack Status: DRAFT Replaces: SWS_Xcp_00701 Upstream requirements: SRS_Xcp_29030 ⌈The AUTOSAR XCP Module and the bus specific Interfaces shall be located above the AUTOSAR PDU Routing module (PduR) [4]. ⌋

[SWS_Xcp_00705] Upstream requirements: SRS_Xcp_29009 ⌈The AUTOSAR XCP Module shall support the basic feature "Synchronous data ac- quisition (measurement) ". Please refer to [3]⌋

[SWS_Xcp_00706] Upstream requirements: SRS_Xcp_29013 ⌈The AUTOSAR XCP Module shall support the feature "Dynamic DAQ Configuration". according to [3]⌋

[SWS_Xcp_00707] Upstream requirements: SRS_Xcp_29010 ⌈The AUTOSAR XCP Module shall support the basic feature "Synchronous data stim- ulation" according to [3]⌋

[SWS_Xcp_00708] ⌈The AUTOSAR XCP Module shall support the basic feature "On- line memory calibration (read / write access) ", according to [3]⌋

[SWS_Xcp_00709] Upstream requirements: SRS_Xcp_29014 ⌈The AUTOSAR XCP Module shall support the feature "Timestamped Data Transfer", according to [3]⌋

[SWS_Xcp_00711] ⌈The AUTOSAR XCP Module shall support the feature "Block communication mode", according to [3]⌋

[SWS_Xcp_00761] Upstream requirements: SRS_Xcp_29015 ⌈The AUTOSAR XCP Module shall support the feature "Bypassing", according to [3]⌋

[SWS_Xcp_00766] Upstream requirements: SRS_Xcp_29016 ⌈The AUTOSAR XCP Module shall support the feature "Seed & Key" according to [3]⌋

[SWS_Xcp_00768] ⌈The ECU local time shall be derived from the AUTOSAR OS.⌋

Module Header File Imported Type Com Stack_ Types Com Stack_ Types.h Network Handle Type Com Stack_ Types.h Pdu Id Type Com Stack_ Types.h Pdu Info Type Com Stack_ Types.h Pdu Length Type Fr Fr_ General Types.h Fr _ Channel Type Os Os.h Status Type Os.h Tick Ref Type Os.h Tick Type Rte_ Os_ Type.h Counter Type Std Std_ Types.h Std _ Return Type Std_ Types.h Std _ Version Info Type

[SWS_Xcp_00824] ⌈The XCP Main Function shall be called cyclically.⌋

[SWS_Xcp_00825] ⌈If 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.⌋

Can If _ - Transmit Can If.h Requests transmission of a PDU. Det _ Report - Error Det.h Service to report development errors. Fr If _ Disable - L Pdu Fr If.h Wraps the Flex Ray Driver Function Fr_ Disable LPdu. It disables the hardware resource of an LPdu for transmission/ reception. Fr If _ - Reconfig L - Pdu Fr If.h Calls the Flex Ray Driver's API Fr_ Reconfig LPdu. The enum value "FR_ CHANNEL_ AB" shall not be used. Fr If _ - Transmit Fr If.h Requests transmission of a PDU. Get Counter - Value Os.h This service reads the current count value of a counter (returning either the hardware timer ticks if counter is driven by hardware or the software ticks when user driv es counter). Get Elapsed - Value Os.h This service gets the number of ticks between the current tick value and a previously read tick value. So Ad _ If - Transmit So Ad.h Requests transmission of a PDU.

[SWS_Xcp_00836] ⌈This is a list of functions provided for other modules.⌋

[SWS_Xcp_00840] ⌈If development error detection for the XCP module is enabled: if the function Xcp_<Lo>TxConfirmation is called before the XCP was initialized successfully, the function Xcp_<Lo>TxConfirmation shall raise the development error XCP_E_UNINIT and return.⌋()

[SWS_Xcp_00841] ⌈Caveats of Xcp_<Lo>TxConfirmation: • The call context is either on interrupt level (interrupt mode) or on task level • The Xcp module is initialized correctly. ⌋()

[SWS_Xcp_00842] ⌈If development error detection for the XCP module is enabled: if the function Xcp_<Lo>TriggerTransmit is called before the XCP was initialized successfully, the function Xcp_<Lo>TriggerTransmit shall raise the development error XCP_E_ UNINIT and return E_NOT_OK.⌋()

[SWS_Xcp_00843] ⌈Caveats of Xcp_<Lo>TriggerTransmit: • The call context is either on interrupt level (interrupt mode) or on task level • The Xcp module is initialized correctly. ⌋()

If Xcp_SetTransmissionMode(Channel, Mode) is called and parameter Mode equals XCP_TX_OFF , all TxPDUs which are assigned to Channel shall not be transmitted.

The AUTOSAR XCP Module shall support the feature “ Page switching “ , according to [ 13]

The code generator of the XCP Module shall generate the A2L IF_DATA section, based on the configuration of XCP

The AUTOSAR XCP Module shall support the feature “ Power - Up data transfer (R ESUME MODE) “ , according to [13]

The AUTOSAR XCP Module shall support the flash programming (PGM) according to [13]

Indication the end of a programming sequence is supported using the opti onal command "PROG RAM_RESET", w here the slave will go to disconnected state but without forcing a device reset

Type of error Related error code Error value Module not initialized XCP_ E_ UNINIT 0x02 API call with wrong PDU ID CP_ E_ INVALID_ PDUID 0x03 Initialization of XCP failed XCP_ E_ INIT_ FAILED 0x04 Null pointer has been passed as an argument XCP_ E_ PARAM_ POINTER 0x12

T he XCP module shall wait for the Xcp_<Lo>TxConfirmation (positive or negative) after each call to <Lo>_Transm it to avoid overwriting previously transmitted data

[SWS_Xcp_00860] Location of the XCP module in the AUTOSAR communication stack Status: DRAFT Replaces: SWS_Xcp_00701 Upstream requirements: SRS_Xcp_29030 ⌈The AUTOSAR XCP Module and the bus specific Interfaces shall be located above the AUTOSAR PDU Routing module (PduR) [4]. ⌋

[SWS_Xcp_00863] Waiting for call of Xcp_TxConfirmation to avoid overwritting previously transmitted data Status: DRAFT Replaces: SWS_Xcp_00859 Upstream requirements: SRS_Xcp_29030 ⌈The XCP module shall wait for the Xcp_TxConfirmation (positive or negative) after each call to PduR_XcpTransmit to avoid overwriting previously transmitted data.⌋

[SWS_Xcp_00868] Development error handling in context of Xcp_TxConfirma- tion Status: DRAFT Replaces: SWS_Xcp_00840 ⌈If 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.⌋

[SWS_Xcp_00869] Caveats on call of Xcp_TxConfirmation Status: DRAFT Replaces: SWS_Xcp_00841 ⌈Caveats of Xcp_TxConfirmation: • The call context is either on interrupt level (interrupt mode) or on task level • The Xcp module is initialized correctly. ⌋

[SWS_Xcp_00870] Development error handling in context of Xcp_Trigger- Transmit Status: DRAFT Replaces: SWS_Xcp_00842 ⌈If 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.⌋

[SWS_Xcp_00871] Caveats on call of Xcp_TriggerTransmit Status: DRAFT Replaces: SWS_Xcp_00843 ⌈Caveats of Xcp_TriggerTransmit: • The call context is either on interrupt level (interrupt mode) or on task level • The Xcp module is initialized correctly. ⌋

There are no mandatory interfaces.

[SWS_Xcp_CONSTR_00861] XcpRxPdu and XcpTxPdu constraint for keeping the local buffer Status: DRAFT Upstream requirements: SRS_Xcp_29003 ⌈Each XcpRxPdu and XcpTxPdu shall refer to global PDU that has KeepLocalP- duBuffer set to FALSE.⌋