The device starts transition from SLEEP state to
STANDBY state:
- If the nSLEEP pin goes high for a duration longer
than tWAKE, or
- If VDD supply > VDDPOR_RISE such that internal POR is released to
indicate a power-up.
The device goes through an initialization
sequence to load the internal registers and wake-up
all the blocks in the following sequence:
- At a certain time, tCOM from wake-up,
the device is capable of communication. This is
indicated by asserting the nFAULT pin low.
- This is followed by the time tREADY,
when the device wake-up is complete.
- At this point, the HW variant device enters STANDBY mode for all DIAG options in PH/EN
or PWM mode except RLVL5. For DIAG = RLVEL5, an nSLEEP wake-up pulse is required for
entry into STANDBY mode. For independent mode behavior, refer to Table 7-7 For SPI variant, once the device receives a CLR FAULT command through SPI as an acknowledgment of the wake-up from
the controller, the device enters the STANDBY state. This is indicated by the
de-assertion of the nFAULT pin. The driver is held in Hi-Z till this point.
- From here on, the device is ready to drive the
bridge based on the truth tables.
Refer to the
wake-up transients waveforms for the
illustration.