SNIP_CLASSIC_CANIF_SECTION_9_4_Transmit_confirmation_polling_mode

9.4 Transmit confirmation (polling mode) CanIf User BSW Scheduler «module» CanIf «module» Can «Peripheral» CanController loop Cyclic Task of Interface alt Pending Tx confirmation [Tx confirmation is pending ] [No Tx confirmation is pending] CanIf_TxConfirmation(PduIdType) Check for pending TX confirmations() Can_MainFunction_Write() Can_MainFunction_Write() <User_TxConfirmation>(PduIdType, Std_ReturnType) CanIf_TxConfirmation() <User_TxConfirmation>() Check for pending TX confirmations() Figure 9.4: Transmit confirmation polling driven Activity Description Cyclic Task CanDrv The service Can_MainFunction_Write() is called by the BSW Scheduler. Check for pending transmit confirmations Can_MainFunction_Write() checks the underlying CAN Controller(s) about pending transmit confirmations of previously succeeded transmit events. Transmit Confirmation The acknowledged CAN frame signals a successful transmission to the sending CAN Controller. Confirmation to CanIf CanDrv calls the service CanIf_TxConfirmation(). The parameter CanTxPduId specifies the L-PDU previously sent by Can_Write(). CanDrv must store the all in HTHs pending L-PDU Ids in an array organized per HTH to avoid new search of the L-PDU ID for call of CanIf_TxConfirmation(). Confirmation to upper layer Calling of the corresponding upper layer confirmation service <User_TxConfirmation>(id, E_OK). It signals a successful L-SDU transmission to the upper layer.