JAJSIR5C October 2019 – October 2023 TPS65313-Q1
PRODUCTION DATA
In any of the operating states (RESET, DIAGNOSTIC, ACTIVE, and SAFE), if the BUCK2 switching-clock error is detected while the internal OSC clock source is in good condition, the following occurs:
If the BUCK2 is configured as an NRES source and when the BUCK2 output discharges to less than its UV-threshold level, the device goes into the RESET state. In the RESET state, the BUCK2 regulator is enabled again only after the BUCK2 regulator discharges below the VBUCK2_RESTART_LEVEL voltage level and the SYNC_IN, and when the PLL (or VCO) and fSW_BUCK2 clock monitors indicate that the clocks are in good condition. Enabling again the BUCK2 regulator is followed by a full ABIST run during an NRES extension after there is no active RESET state condition.
If an ABIST run in the RESET state fails (because of a clock monitor failure or any other failure), the device goes into the SAFE state again, repeating the same procedure until the device error counter reaches its programmed power-down threshold value and the device goes into the OFF state.
While the device is in the SAFE state, the system MCU can detect if a reported clock failure occurred because of a clock-monitor failure or a true clock failure. A false clock failure occurs when a clock monitor fails. In case of false clock-failure detection, the system MCU can disable clock monitoring. As a single-point failure, clock monitoring failure is not a critical failure, and therefore, the system MCU can ignore it.
While the device is in the RESET state and when the BUCK2 regulator is enabled again, the device goes into the OFF state if the BUCK2 output does not ramp up within the time-out interval for the RESET state.
If the BUCK2 regulator is not configured as a RESET state condition, as the BUCK2 output discharges to less than its UV-threshold level, then the device stays in the SAFE state. The system MCU can enable the BUCK2 regulator by setting the BUCK2_EN control bit in the PWR_CTRL control register.