SNIP_CLASSIC_LIN_SECTION_7_4_2_2_LIN_Slave_specific

7.4.2.2 LIN Slave specific Following requirements are only appicable for LIN Slave nodes. [SWS_Lin_00272] Upstream requirements: SRS_Lin_01578 ⌈The LIN driver shall be able to receive a LIN header at any time in LIN_CH_OPERATIONAL state. The header is composed of the break field, synch byte field, and protected identifier byte field as detailed in [1].⌋ [SWS_Lin_00280] ⌈On LIN header reception, the LIN driver shall call the header indication callback function LinIf_HeaderIndication with PduPtr->Pid set to the received PID value and PduPtr->SduPtr set to the (hardware or shadow) buffer of the LIN driver, to which the slave response shall be written by the upper layer.⌋ Note: If the LIN hardware unit provides the ID (frame identifier without parity bits) instead of the PID, the LIN driver is responsible to calculate the PID from the ID to comply with the callback interface. [SWS_Lin_00271] ⌈If the LIN hardware unit cannot detect invalid PIDs, the LIN driver shall not evaluate the PID value (i.e. it shall not verify parity bits in software). The LIN driver shall provide the PID as-received to the LIN interface module.⌋ [SWS_Lin_00281] ⌈While waiting for a new LIN header, the LIN driver shall call the error indication callback function LinIf_LinErrorIndication with error parameter LIN_ERR_HEADER when it detects bus events that do not comply to a valid LIN header (e.g incomplete LIN header).⌋ [SWS_Lin_00273] Upstream requirements: SRS_Lin_01578 ⌈The LIN driver shall be able to send, receive or ignore a LIN response.⌋ [SWS_Lin_00282] ⌈After the call of LinIf_HeaderIndication when the return value is E_OK, the LIN driver shall evaluate the PduPtr->Drc to determine the type of LIN response.⌋ [SWS_Lin_00284] ⌈If the LIN response is going to be received (LIN_FRAMERESPONSE_RX), the LIN driver shall evaluate the Cs and Dl members in parameter PduPtr (after the call of LinIf_HeaderIndication with return value E_OK) to configure the LIN response reception.⌋ [SWS_Lin_00274] Upstream requirements: SRS_Lin_01555, SRS_Lin_01503 ⌈After successful reception of a LIN response, the LIN driver shall directly make the received data available to the LIN interface module by calling the Rx indication callback function LinIf_RxIndication with the Lin_SduPtr parameter set to the reception data.⌋ [SWS_Lin_00283] Upstream requirements: SRS_Lin_01503, SRS_Lin_01522 ⌈If the LIN response is going to be transmitted (LIN_FRAMERESPONSE_TX), the LIN driver shall evaluate the Cs, Dl and SduPtr members in parameter PduPtr (after the call of LinIf_HeaderIndication with return value E_OK) to setup and transmit the LIN response.⌋ [SWS_Lin_00286] ⌈If the return value of LinIf_HeaderIndication is E_NOT_OK or the returned PduPtr->Drc is LIN_FRAMERESPONSE_IGNORE, the LIN driver shall ignore the response.⌋ [SWS_Lin_00275] Upstream requirements: SRS_Lin_01555 ⌈After successful transmission of a LIN response, the transmission shall be directly confirmed to the LIN Interface module by calling the Tx confirmation callback function LinIf_TxConfirmation.⌋ [SWS_Lin_00276] ⌈The LIN driver shall not report any events to the LIN interface module if the LIN response is ignored until the reception of a new LIN header.⌋ [SWS_Lin_00277] ⌈The LIN driver shall detect communication errors during response transmission and response reception. Once an error is detected, the current frame handling shall be aborted and the error indication callback function LinIf_LinErrorIndication shall be called.⌋ [SWS_Lin_00285] ⌈The handling of each relevant (i.e. not ignored) LIN response must be completed by a call to either LinIf_RxIndication, LinIf_TxConfirmation or LinIf_LinErrorIndication, latest before a new LIN header reception is indicated by a call of LinIf_HeaderIndication.⌋