Specification of Large Data COMAUTOSAR CP R20-11Document TitleSpecification of Large DataCOMDocument OwnerDocument ResponsibilityDocument Identification NoAUTOSARAUTOSAR655Document StatusPart of AUTOSAR StandardPart of Standard ReleasepublishedClassic PlatformR20-11Document Change HistoryDateRelease Changed by2020-11-30 R20-11 AUTOSARReleaseManagement2019-11-28 R19-11 gementAUTOSARReleaseManagement2014-10-311 of 474.2.1AUTOSARReleaseManagementChange Description Clean up error section Changed Document Status fromFinal to published Clean up diagrams in chapter 10 Changed Document Status fromFinal to published Header File Cleanupminorcorrections / clarifications / editorialchanges; For details please refer tothe ChangeDocumentation Minor corrections / clarifications /editorial changes; for details pleaserefer to the ChangeDocumentation Introduced reliable TxConfirmation Minor corrections Fixed TriggerTransmit for dynamiclength PDUsAdded PreCompile configurationclass for all symbolicNameValueparametersInitial ReleaseDocument ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-11DisclaimerThis work (specification and/or software implementation) and the material containedin it, as released by AUTOSAR, is for the purpose of information only. AUTOSARand the companies that have contributed to it shall not be liable for any use of thework.The material contained in this work is protected by copyright and other types ofintellectual property rights. The commercial exploitation of the material contained inthis work requires a license to such intellectual property rights.This work may be utilized or reproduced without any modification, in any form or byany means, for informational purposes only. For any other purpose, no part of thework may be utilized or reproduced, in any form or by any means, without permissionin writing from the publisher.The work has been developed for automotive applications only. It has neither beendeveloped, nor tested for non-automotive applications.The word AUTOSAR and the AUTOSAR logo are registered trademarks.2 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-11Table of Contents1Introduction and functional overview . 52Acronyms and abbreviations. 63Related documentation . documents. 7Related standards and norms . 7Related specification . 7Constraints and assumptions. 84.14.25Limitations . 8Applicability to car domains . 8Dependencies to other modules . . 9PDU Router . 9Default Error Tracer (DET). 9File structure . 96Requirements traceability . 107Functional specification . 127.1 Initialization . 127.2 De-initialization . 127.3 Overall . 127.4 Transmission . 137.4.1 IF. 137.4.2 TP . 137.5 Reception . 147.5.1 IF. 147.5.2 TP . 147.6 Error classification . 147.6.1 Development Errors . 147.6.2 Runtime Errors . 157.6.3 Transient Faults . 157.6.4 Production Errors . 157.6.5 Extended Production Errors . 158API specification . 168.1 Imported types . 168.2 Type definitions . 168.2.1 LdCom ConfigType . 168.3 Function definitions . 178.3.1 LdCom Init . 178.3.2 LdCom DeInit . 178.3.3 LdCom GetVersionInfo. 188.3.4 LdCom Transmit . 198.4 Call-back functions and notifications . 198.4.1 LdCom CopyTxData . 203 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-118.4.2 LdCom TpTxConfirmation . 218.4.3 LdCom StartOfReception . 228.4.4 LdCom CopyRxData . 238.4.5 LdCom TpRxIndication . 248.4.6 LdCom RxIndication . 248.4.7 LdCom TxConfirmation . 258.4.8 LdCom TriggerTransmit . 268.5 Scheduled functions . 278.6 Expected Interfaces . 278.6.1 Mandatory Interfaces. 278.6.2 Optional Interfaces . 278.6.3 Configurable interfaces . 278.7 Service Interfaces . 339Sequence diagrams . 349.1 Transmission . 349.1.1 TP-API . 349.1.2 IF-API . 359.1.3 TriggerTransmit . 359.2 Reception . 369.2.1 TP-API . 369.2.2 IF-API . 3610Configuration specification . 3710.1Containers and configuration parameters . 3710.1.1LdCom . 3710.1.2LdComConfig . 3810.1.3LdComGeneral . 3810.1.4LdComIPdu . 3910.2Published Information . 46114 of 47Not applicable requirements . 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-111Introduction and functional overviewThis specification specifies the functionality, API and the configuration of theAUTOSAR Basic Software module LdCom.Within the AUTOSAR Layered Architecture the AUTOSAR LdCom module is placedbetween RTE and the PDU Router, see [1].The AUTOSAR LdCom module provides an alternative Interaction Layer Mechanism.By focusing on spontaneous, non-cyclic communication without serializing, filteringand conversion an efficient implementation of the module without local buffers isachieved.Main Features: 5 of 47Provision of signal oriented data interface for the RTEProvision of received signals to RTESupport of large and dynamic length data typesSupport of IF- and TP-based communicationProvision of PDU oriented data interface towards PduRDocument ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-112Acronyms and abbreviationsAbbreviation /Acronym:DEMDET6 of 47Description:Diagnostic Event ManagerDefault Error TracerDocument ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-113Related documentation3.1 Input documents[1] AUTOSAR Layered Software ArchitectureAUTOSAR EXP LayeredSoftwareArchitecture.pdf[2] AUTOSAR General Requirements on Basic Software ModulesAUTOSAR SRS BSWGeneral.pdf[3] AUTOSAR General Specification for Basic Software ModulesAUTOSAR SWS BSWGeneral.pdf[4] Specification of RTEAUTOSAR SWS RTE.pdf[5] Specification of PDU RouterAUTOSAR SWS PDURouter.pdf[6] Specification of System TemplateAUTOSAR RS SystemTemplate.pdf[7] Specification of Default Error TracerAUTOSAR SWS DefaultErrorTracer.pdf3.2 Related standards and norms3.3 Related specificationAUTOSAR provides a General Specification on Basic Software (SWS BSWGeneral)[3], which is also valid for this SWS.Thus, the specification SWS BSW General [3]shall be considered as additional andrequired specification for this SWS.7 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-114Constraints and assumptions4.1 LimitationsEfficient COM supports communication of linear opaque byte wise data in a veryresource-saving way. It does so by skipping all functionality not required for eventbased non-cyclic communication.Efficient COM does not apply any changes like for instance endianness conversion tothe data it transports.Prerequisites for usage of Efficient COM:- PDU contains only 1 Signal and no ISignalGroup- The Signal is of type byte array with either fixed or dynamic length- Transmission mode is either triggered or triggered without repetition- Transmission mode selection is not used- No update bit is used- No minimum delay time is used- No timeout supervision is used- No byte order conversion is used- No Rx/Tx Filtering- No Signal Invalidation4.2 Applicability to car domainsNo restrictions.8 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-115Dependencies to other modules5.1 RTEFor RTE the AUTOSAR LdCom module is an additional mean to send and receivesignals. In AUTOSAR, the RTE is the higher layer above the LdCom module. Forfurther information, see[4].5.2 PDU RouterThe AUTOSAR LdCom module uses both sets of PDU Router’s upper layer moduleAPIs. That is the APIs for upper layer modules that use TP and the APIs for upperlayer modules that do not use TP. This is necessary since the LdCom moduleforwards I-PDUs either unfragmented via simple L-PDUs or fragmented via TP.The following summarizes the functionality of the AUTOSAR LdCom module needsfrom the underlying layer PDU Router: Indication of incoming I-PDUsSending interface for outgoing I-PDUs including the confirmation if an I-PDUhas been sent by the communication controllerTrigger interface to enable the PDU router to cause a transmission from theAUTOSAR LdCom moduleData forwarding for TP communication5.3 Default Error Tracer (DET)The DET provides services to store development errors (for further information, see[7]).5.4 File structure[SWS LDCOM 00050]⌈The LdCom implementation shall include Det.h ifLdComDevErrorDetect is enabled.⌋ (SRS BSW 00350)9 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-116Requirements traceabilityRequirementDescriptionSRS BSW 00003 All software modules shallprovide version andidentification informationSatisfied bySWS LDCOM 00024, SWS LDCOM 00045SRS BSW 00101 The Basic Software Module SWS LDCOM 00007, SWS LDCOM 00008,shall be able to initializeSWS LDCOM 00022variables and hardware ina separate initializationfunctionSRS BSW 00305 Data types namingconventionSWS LDCOM 00052SRS BSW 00336 Basic SW module shall beable to shutdownSWS LDCOM 00023SRS BSW 00337 Classification ofdevelopment errorsSWS LDCOM 00018SRS BSW 00344 BSW Modules shallsupport link-timeconfigurationSWS LDCOM 00022SRS BSW 00350 All AUTOSAR BasicSWS LDCOM 00050Software Modules shallallow the enabling/disablingof detection and reportingof development errors.SRS BSW 00358 The return type of init()functions implemented byAUTOSAR Basic SoftwareModules shall be voidSWS LDCOM 00022SRS BSW 00384 The Basic Software Module SWS LDCOM 00020, SWS LDCOM 00035specifications shall specifyat least in the descriptionwhich other modules theyrequireSRS BSW 00400 Parameter shall beselected from multiple setsof parameters after codehas been loaded andstartedSWS LDCOM 00052SRS BSW 00404 BSW Modules shallsupport post-buildconfigurationSWS LDCOM 00022, SWS LDCOM 00052SRS BSW 00405 BSW Modules shallsupport multipleconfiguration setsSWS LDCOM 00022SRS BSW 00407 Each BSW module shallprovide a function to readout the version informationof a dedicated moduleimplementationSWS LDCOM 00024, SWS LDCOM 00045SRS BSW 00414 Init functions shall have aSWS LDCOM 0002210 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-11pointer to a configurationstructure as singleparameterSRS BSW 00438 Configuration data shall be SWS LDCOM 00052defined in a structureSRS Com 02044 AUTOSAR COM andLargeDataCOM shallprovide a transmitconfirmation functionSWS LDCOM 00046, SWS LDCOM 00053SRS Com 02108 Support of Large DataCOMSWS LDCOM 00005, SWS LDCOM 00009,SWS LDCOM 00035, SWS LDCOM 00046SRS Com 02109 Large Data COM shallSWS LDCOM 00012, SWS LDCOM 00013,support Transport Protocol- SWS LDCOM 00015, SWS LDCOM 00016,like communicationSWS LDCOM 00017, SWS LDCOM 00027,SWS LDCOM 00028, SWS LDCOM 00029,SWS LDCOM 00030, SWS LDCOM 00031,SWS LDCOM 00035, SWS LDCOM 00036,SWS LDCOM 00037, SWS LDCOM 00038,SWS LDCOM 00039, SWS LDCOM 00040,SWS LDCOM 00048, SWS LDCOM 00049SRS Com 02110 Large Data COM shallsupport Interface-likecommunicationSWS LDCOM 00010, SWS LDCOM 00014,SWS LDCOM 00026, SWS LDCOM 00032,SWS LDCOM 00035, SWS LDCOM 00041,SWS LDCOM 00046, SWS LDCOM 00054,SWS LDCOM 00055, SWS LDCOM 00056SRS Com 02111 Large Data COM shallsupport TransmissionTriggered by lower layerSWS LDCOM 00011, SWS LDCOM 00033,SWS LDCOM 00042, SWS LDCOM 00047SRS Rte 00246SWS LDCOM 0004111 of 47Support of Efficient COMfor large dataDocument ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-117Functional specification7.1 Initialization[SWS LDCOM 00007]⌈The AUTOSAR LdCom module’s initialization functionLdCom Init shall initialize all internal data.⌋(SRS BSW 00101)7.2 De-initialization[SWS LDCOM 00008]⌈The AUTOSAR LdCom module shall provide the APIfunction LdCom DeInit for de-initialization of the AUTOSAR LdCom module. Insidethis function call all de-initialization shall take place.⌋(SRS BSW 00101)7.3 Overall[SWS LDCOM 00005]⌈When called by PduR LdCom shall use the passed PDU Idas Handle Id (LdComHandleIdECUC LdCom 00005), to derive the actualAPI fromconfiguration and use it when passing the call towards RTE.⌋(SRS Com 02108)See Table 1: API to Parameter mapping for a mapping of API names used in thisdocument to the ECUC Parameter containing the actual name configured for this APIper signal.As per naming convention of the RTE sn is the name of theLdComIPdu.API-NameRte LdComCbkCopyTxData sn Rte LdComCbkTpTxConfirmation sn Rte LdComCbkRxIndication sn Rte LdComCbkStartOfReception sn Rte LdComCbkCopyRxData sn Rte LdComCbkTpRxIndication sn Rte LdComCbkTriggerTransmit sn Rte LdComCbkTxConfirmation sn ECUC TxConfirmationTable 1: API to Parameter mapping[SWS LDCOM 00009]⌈When called by the RTE, LdCom shall use the Signal Id ("id"parameter in the call) as LdComHandleId (ECUC LdCom 00005) to look-up thecorrect LdComIPdu in the LdCom configuration. Using the LdComPduRefconfiguration parameter (ECUC LdCom 00010)the corresponding PDU Id in the12 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-11PduR'S configuration shall be derived. This PDU Id shall then be used whenforwarding the call towards the PduR.⌋(SRS Com 02108)7.4 TransmissionTransmission is initiated by RTE (LdCom Transmit) or PduR (TriggerTransmit) butnot by LdCom on its own.7.4.1 IF[SWS LDCOM 00010]⌈When LdCom Transmit is invoked, LdCom shall invokePduR LdComTransmit by replacing the Signal Id by the according PDU Id.⌋(SRS Com 02110)[SWS LDCOM 00011]⌈When LdCom TriggerTransmit is invoked, LdCom shallinvoke Rte LdComCbkTriggerTransmit sn based on the PDU Id passed to ofLdCom TriggerTransmit as parameter.⌋(SRS Com 02111)[SWS LDCOM 00046]⌈When LdCom TxConfirmation is invoked, LdCom shallinvoke Rte LdComCbkTxConfirmation sn based on the PDU Id passed to ofLdCom TxConfirmation as parameter ⌋(SRS Com 02044, SRS Com 02108,SRS Com 02110)7.4.2 TP[SWS LDCOM 00012]⌈LdCom shall pass invocations of LdCom Transmit toPduR LdComTransmit by replacing the Signal Id by the according PDU Id.⌋(SRS Com 02109)[SWS LDCOM 00013]⌈LdCom shall forward invocations of LdCom CopyTxDataand LdCom TpTxConfirmation to RTE by invoking the correspondingRte LdComCbkCopyTxData sn or Rte LdComCbkTpTxConfirmation sn basedon the PDU Id passed to LdCom CopyTxData and LdCom TpTxConfirmation asparameter.⌋(SRS Com 02109)13 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-117.5 Reception7.5.1 IF[SWS LDCOM 00014]⌈When LdCom RxIndication is invoked,LdCom shall call thecorresponding Rte LdComCbkRxIndication sn based on the PDU Id passed to ofLdCom RxIndication as parameter.⌋(SRS Com 02110)7.5.2 TP[SWS LDCOM 00015]⌈When LdCom StartOfReception is invoked by PduR,LdComshall call the corresponding Rte LdComCbkStartOfReception sn based on thePDU Id passed to of LdCom StartOfReception as parameter.⌋(SRS Com 02109)[SWS LDCOM 00016]⌈When LdCom CopyRxData is invoked by PduR,LdComshall call Rte LdComCbkCopyRxData sn based on the PDU Id passed to ofLdCom CopyRxData as parameter.⌋(SRS Com 02109)[SWS LDCOM 00017]⌈When LdCom TpRxIndication is invoked by PduR,LdComshall call the corresponding Rte LdComTpRxIndication sn based on the PDU Idpassed to of LdCom TpRxIndication as parameter.⌋(SRS Com 02109)7.6 Error classificationSection 7.2 "Error Handling" of the document "General Specification of BasicSoftware Modules" describes the error handling of the Basic Software in detail.Above all, it constitutes a classification scheme consisting of five error types whichmay occur in BSW modules.Based on this foundation, the following section specifies particular errors arranged inthe respective subsections below.7.6.1 Development Errors[SWS LDCOM 00018]⌈Development Error TypesType of errorRelated error codeValue [hex]Error code if any other API service,except LdCom GetVersionInfo iscalled before the AUTOSAR LdCommodule was initialized withLdCom Init or after a call toLdCom DeinitAPI service called with a NULLLDCOM E UNINIT0x02LDCOM E PARAM POINTER0x0314 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-11pointer. In case of this error, the APIservice shall return immediatelywithout any further action, except forreporting this development error.API service called with wrong PDU- LDCOM E INVALID PDU SDU ID 0x04ID0x05API service called with wrong Signal- LDCOM E INVALID SIGNAL IDIDLDCOM E INIT FAILED0x06Invalid configuration set selection⌋ (SRS BSW 00337 )7.6.2 Runtime ErrorsThere are no runtime errors.7.6.3 Transient FaultsThere are no transient faults.7.6.4 Production ErrorsThere are no production errors.7.6.5 Extended Production ErrorsThere are no extended production errors.15 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-118API specification8.1 Imported typesIn this chapter, all types included from the following modules are listed:Imported Types[SWS LDCOM 00020]⌈ModuleHeader FileImported TypeComStack Types.hBufReq ReturnTypeComStack Types.hPduIdTypeComStack Types.hPduInfoTypeComStack Types.hPduLengthTypeComStack Types.hRetryInfoTypeComStack Types.hTpDataStateTypeStd Types.hStd ReturnTypeStd Types.hStd VersionInfoTypeComStack TypesStd⌋(SRS BSW 00384)8.2 Type definitions8.2.1 LdCom ConfigType[SWS LDCOM 00052]⌈NameLdCom ConfigTypeKindStructureimplementation specificElementsType--CommentThe contents of the initialization data structure are implementationspecificDescriptionThis type contains the implementation-specific post build configuration structure.AvailableviaLdCom.h⌋(SRS BSW 00400, SRS BSW 00438, SRS BSW 00404, SRS BSW 00305)16 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-118.3 Function definitionsThis is a list of functions provided for upper layer modules.Note: All functions in this chapter requires previous initialization (LdCom Init), exceptthe following ones: LdCom Init LdCom GetVersionInfo8.3.1 LdCom Init[SWS LDCOM 00022]⌈Service NameLdCom InitSyntaxvoid LdCom Init (const LdCom ConfigType* config)Service ID[hex]0x01Sync/AsyncSynchronousReentrancyNon ReentrantParameters Return valueNoneDescriptionThis service initializes internal and external interfaces and variables of theAUTOSAR LdCom module for the further processing.Available viaLdCom.hPointer to the AUTOSAR LdCom module's configuration data.⌋(SRS BSW 00344, SRS BSW 00404, SRS BSW 00405, SRS BSW 00101,SRS BSW 00358, SRS BSW 00414)8.3.2 LdCom DeInit[SWS LDCOM 00023]⌈Service NameLdCom DeInitSyntaxvoid LdCom DeInit (17 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-11void)Service ID [hex]0x02Sync/AsyncSynchronousReentrancyNon ReentrantParameters (in)NoneParameters(inout)NoneParameters (out)NoneReturn valueNoneDescriptionWith a call to LdCom DeInit the AUTOSAR LdCom module is put into an notinitialized state.Available viaLdCom.h⌋(SRS BSW 00336)8.3.3 LdCom GetVersionInfo[SWS LDCOM 00024]⌈Service NameLdCom GetVersionInfoSyntaxvoid LdCom GetVersionInfo (Std VersionInfoType* versioninfo)Service ID [hex]0x03Sync/AsyncSynchronousReentrancyNon ReentrantParameters (in)NoneParameters (inout)NoneParameters (out)versioninfoReturn valueNoneDescriptionReturns the version information of this module.Available viaLdCom.hPointer to where to store the version information of this module.⌋(SRS BSW 00407, SRS BSW 00003)18 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-11[SWS LDCOM 00045]⌈The API LdCom GetVersionInfo shall be configuredbyLdComVersionInfoAPI.⌋(SRS BSW 00407, SRS BSW 00003 )8.3.4 LdCom Transmit[SWS LDCOM 00026]⌈Service NameLdCom TransmitSyntaxStd ReturnType LdCom Transmit (PduIdType Id,const PduInfoType* InfoPtr)Service ID [hex]0x49Sync/AsyncSynchronousReentrancyReentrant for different Ids. Non reentrant for the same Id.IdIdentifier of the signal to be transmitted.InfoPtrLength of and pointer to the signal data and pointer to MetaData.Parameters (in)Parameters(inout)NoneParameters (out)NoneReturn valueStd ReturnTypeDescriptionRequests transmission of a signal.Available viaLdCom.hE OK: Transmit request has been accepted.E NOT OK: Transmit request has not been accepted.⌋(SRS Com 02110)8.4 Call-back functions and notificationsThis is a list of functions provided for other modules.[SWS LDCOM 00048]⌈LdCom CopyTxData, LdCom TpTxConfirmation shall onlybe available if at least one LdComIPdu has LdComIPduDirection configured toLDCOM SEND and LdComApiType configured to LDCOM TP.⌋ (SRS Com 02109)[SWS LDCOM 00049]⌈LdCom StartOfReception, LdCom CopyRxData,LdCom TpRxIndicationshall only be available if at least one LdComIPdu has19 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-11LdComIPduDirection configured to LDCOM RECEIVE and LdComApiTypeconfigured to LDCOM TP.⌋(SRS Com 02109)[SWS LDCOM 00054]⌈LdCom TxConfirmation shall only be available if at least oneLdComIPdu has LdComIPduDirection configured to LDCOM SEND andLdComApiType configured to LDCOM IF.⌋ (SRS Com 02110)[SWS LDCOM 00055]⌈LdCom RxIndication shall only be available if at least one LdComIPdu hasLdComIPduDirection configured to LDCOM RECEIVE and LdComApiTypeconfigured to LDCOM IF.⌋ (SRS Com 02110)Note: All functions in this chapter requires that the LdCom module is initializedcorrectly.8.4.1 LdCom CopyTxData[SWS LDCOM 00027]⌈ServiceNameLdCom CopyTxDataSyntaxBufReq ReturnType LdCom CopyTxData (PduIdType id,const PduInfoType* info,const RetryInfoType* retry,PduLengthType* availableDataPtr)Service tidIdentification of the transmitted I-PDU.infoProvides the destination buffer (SduDataPtr) and the number of bytes tobe copied (SduLength). If not enough transmit data is available, no datais 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 beused to indicate state changes in the retry parameter or to query thecurrent amount of available data in the upper layer module. In this case,the SduDataPtr may be a NULL PTR.retryThis parameter is used to acknowledge transmitted data or to retransmitdata after transmission problems.If the retry parameter is a NULL PTR, it indicates that the transmit datacan be removed from the buffer immediately after it has been copied.Otherwise, the retry parameter must point to a valid RetryInfoTypeelement.If TpDataState indicates TP CONFPENDING, the previously copiedParameters(in)20 of 47Document ID 655:AUTOSAR SWS LargeDataCOM

Specification of Large Data COMAUTOSAR CP R20-11data must remain in the TP buffer to be available for error recovery. TPDATACONF indicates that all data that has been copied before this callis confirmed and can be removed from the TP buffer. Data copied bythis API call is excluded and will be confirmed later. TP DATARETRYindicates that this API call shall copy previously copied data in order torecover from an error. In this case TxTpDataCnt specifies the offset inbytes from the current data copy ableDataPtrIndicates the remaining number of bytes that are available in the upperlayer module's Tx buffer. availableDataPtr can be used by TP modulesthat support dynamic payload lengths (e.g. FrIsoTp) to determine thesize of the following CFs.ReturnvalueBufReq ReturnTypeBUFREQ OK: Data has been copied to the transmit buffer completelyas requested.BUFREQ E BUSY: Request could not be fulfilled, because the requiredamount of Tx data is not available. The

Clean up diagrams in chapter 10 Changed Document Status from Final to published 2018-10-31 4.4.0 AUTOSAR Release Management Header File Cleanupminor . Specification of Large Data COM AUTOSAR C