SNIP_CLASSIC_LINSM_SECTION_7_1_8_Timeout_of_requests

7.1.8 Timeout of requests After calling LinIf_Wakeup the LinSM module is waiting for the LinIf module to confirm the wake up on the bus. There is a possibility that the confirmation is not received, and therefore the LinSM module will wait forever. The cause for a missing wakeup confirmation could be a problem in software, but also a bus failure or a problem in the master node. A slave node confirms a bus wakeup not after wakeup transmission like a master node, but with reception of the first LIN header from the master node. A LIN slave node shall repeat the wakeup frame transmission up to three times if the communication does not start. After three (failing) wakeup requests the node shall wait a minimum time before restarting the wake up process. [SWS_LinSM_00175] ⌈There shall be independent wakeup confirmation timers for each network.⌋ [SWS_LinSM_00162] ⌈The (countdown and expiration) handling of wakeup confirmation timers shall be done in the LinSM_MainFunction.⌋ [SWS_LinSM_00159] ⌈The wakeup confirmation timeout parameter LinSMConfirmationTimeout shall have a time that is either 0 or divisible by the LinSM_MainFunction (i.e. LinSM_MainFunction period * m; m integer >0).⌋ [SWS_LinSM_00100] ⌈Before the LinSM calls LinIf_Wakeup on a channel it shall start a wakeup confirmation timer for the according channel with the configured timeout parameter LinSMConfirmationTimeout if LinSMConfirmationTimeout > 0.⌋ [SWS_LinSM_00154] ⌈If LinSM_WakeupConfirmation is called on a channel before the wakeup confirmation timer has expired on the according channel LinSM shall stop the timer.⌋ [SWS_LinSM_00102] ⌈If a wakeup confirmation timer elapses (i.e. no wakeup confirmation occurred) and the maximum number of retries (LinSMModeRequestRepetitionMax) has been reached and LinSMDevErrorDetect (ECUC_LinSM_00206) is set to TRUE, the LinSM module shall report LINSM_E_CONFIRMATION_TIMEOUT to DET.⌋ Making the timeout optional enhances implementation size, if the timeout is not required: Note: If the configuration parameter LinSMConfirmationTimeout is set to zero the wakeup confirmation timer is not used, and hence a timeout cannot occur. This means that requirement [SWS_LinSM_00102] will not happen. [SWS_LinSM_00304] ⌈If a wakeup confirmation timer elapses (i.e. no wakeup confirmation occurred), LinSMNodeType is set to MASTER and ComM request is still COMM_FULL_COMMUNICATION then LinIf_Wakeup shall be called.⌋ Note: LinSM stops to retry when confirmation callback LinSM_WakeupConfirmation (SWS_LinSM_00132) occurs or timeout parameter LinSMConfirmationTimeout (ECUC_LinSM_00144) is expired and ComM requests COMM_NO_COMMUNICATION. [SWS_LinSM_00235] ⌈If a wakeup confirmation timer elapses (i.e. no wakeup confirmation occurred), the maximum number of retries (LinSMModeRequestRepetition Max) has not been reached, LinSMNodeType is set to Slave and ComM request is still COMM_FULL_COMMUNICATION then LinIf_Wakeup shall be called.⌋ [SWS_LinSM_00236] ⌈If a wakeup confirmation timer elapses (i.e. no wakeup confirmation occurred), the maximum number of retries (LinSMModeRequestRepetition Max) has been reached, LinSMNodeType is set to Slave then LinSM shall wait the silence-after-wakeup time (LinSMSilenceAfterWakeupTimeout) and afterwards restart the wakeup process by • calling LinIf_Wakeup if ComM request is still COMM_FULL_COMMUNICATION. • resetting the counter for maximum number of retries. ⌋ [SWS_LinSM_00237] ⌈If a wakeup confirmation timer elapses (i.e. no wakeup confirmation occurred), the maximum number of retries (LinSMModeRequestRepetitionMax) has been reached, LinSMNodeType is set to Slave, the silence-after-wakeup time (Lin SMSilenceAfterWakeupTimeout) has not expired and ComM requests COMM_FULL_ COMMUNICATION then the call of LinIf_Wakeup shall be delayed to the expiration of the silence-after-wakeup time.⌋