After the MCU has set the start bit of an ESM (bit ESM_MCU_START or bit ESM_SOC_START), there are two possible scenarios:

1. The deglitched signal of the monitored input pin has a low level at the moment the MCU sets the start bit. In this scenario, the related ESM starts the following procedure:
   1. Start a timer with a time-length according the value configured in corresponding ESM_MCU_LMAX[7:0] or ESM_SOC_LMAX[7:0].
   2. Wait for a first rising edge on its deglitched input signal.
   3. If the rising edge comes before the configured time-length elapses, the ESM skips the next step and starts to monitor the high-pulse duration time. Hereafter, the ESM detects good-events or bad-events as described in Section 8.3.12.1.2.1. Figure 8-35 shows an example this scenario as Case Number 1.
   4. If the configured time-length (configured in corresponding ESM_MCU_LMAX[7:0] or ESM_SOC_LMAX[7:0]) elapses, the ESM detects a bad-event and increments the related error-counter with +2. Hereafter, the ESM detects good-events or bad-events as described in Section 8.3.12.1.2.1. Figure 8-37 shows an example this scenario as Case Number 3.
   5. If the ESM error-counter value is above its configured threshold, the related ESM has detected a so-called ESM-error and starts the Error-Handling Procedure as described in Section 8.3.12.1.2.1.
   6. During this Error-Handling Procedure, the ESM continues to monitor its related input pin, and updates the error-counter accordingly when it detects good-events or bad-events, until the Error-Handling Procedure reaches the step in which the ESM sends an ESM_x_RST trigger to the PFSM, which, depending on the PFSM configuration, resets the MCU or SoC. Figure 8-38 shows a scenario in which the device resets the MCU or SoC as Case Number 4.
   7. If the ESM error-counter reaches a value equal or less its configured threshold before the elapse of the configured delay-1 or delay-2 time-intervals and the MCU software clears all ESM related interrupt bits, the ESM-error is no longer present and the ESM stops the Error-Handling Procedure as described in Section 8.3.12.1.2.1.
2. The deglitched signal monitored input pin has a high level at the moment the MCU sets the start bit. In this scenario, the related ESM starts the following procedure:
   1. Start a timer with a time-length according the value configured in corresponding ESM_MCU_HMAX[7:0] or ESM_SOC_HMAX[7:0].
   2. Wait for a first falling edge on its deglitched input signal.
   3. If the falling edge comes before the configured time-length elapses, the ESM skips the next step and starts to monitor the low-pulse duration time. Hereafter, the ESM detects good-events or bad-events as described in Section 8.3.12.1.2.1. Figure 8-36 shows an example this scenario as Case Number 2.
   4. If the configured time-length (configured in corresponding ESM_MCU_HMAX[7:0] or ESM_SOC_HMAX[7:0]) elapses, the ESM detects a bad-event and increments the related error-counter with +2. Hereafter, the ESM detects good-events or bad-events as described in Section 8.3.12.1.2.1.
   5. If the ESM error-counter value is above its configured threshold, the related ESM has detected a so-called ESM-error and starts the Error-Handling Procedure as described in Section 8.3.12.1.2.1.
   6. During this Error-Handling Procedure, the ESM continues to monitor its related input pin, and updates the error-counter accordingly when it detects good-events or bad-events, until the Error-Handling Procedure reaches the step in which the ESM sends an ESM_x_RST trigger to the PFSM, which, depending on the PFSM configuration, resets the MCU or SoC, as Case Number 4.
   7. If the ESM error-counter reaches a value equal or less its configured threshold before the elapse of the configured delay-1 or delay-2 time-intervals and the MCU software clears all ESM related interrupt bits, the ESM-error is no longer present and the ESM stops the Error-Handling Procedure as described in Section 8.3.12.1.2.1.