SNIP_CLASSIC_BSWM_SECTION_9_7_Transport_Protocol_message_reception

9.7 Transport Protocol message reception The following diagram (Figure 9.14) shows the reception of a TP message. The initiation of the message, the continuous copying of the data and the finish of the message are shown. The actual reception of the MRF/SRF is not shown in the diagram and it has the same behavior as frame reception. The TP message start is always initiated by receiving a SF or FF from the LIN Driver. In addition, if a SF or FF is received when there is an ongoing reception, a new TP message reception is initiated. Incoming data is provided to the PDU Router via the API PduR_LinTpCopyRxData. The continuous reception of the message is made by copying the N-SDU from the SRF. The TP message is finished after the last N-PDU (SF or CF) is received. The PDU Router is notified of the reception of the complete message. For LIN master nodes, the schedule table change to the applicative schedule is requested if a schedule table change is enabled by the configuration parameter. (see the parameter LinTpScheduleChangeDiag) «module» PduR BSW Task (OS task or cyclic call) «module» LinIf «module» BswM «module» LinSM alt TP status [TP reception message start / buffer request] [TP message reception] [TP message finish] opt Schedule table change is enabled loop LinIf_MainFunction_<ChannelId>() BswM_LinTp_RequestMode() LinIf_ScheduleRequest() LinSM_ScheduleRequest() Close Connection() PduR_LinTpCopyRxData() LinIf_MainFunction_<ChannelId>() PduR_LinTpStartOfReception() PduR_LinTpCopyRxData() LinIf_MainFunction_<ChannelId>() PduR_LinTpRxIndication() Figure 9.14: Transport Protocol message reception