SLDS222C October 2019 – October 2023 TPS65313-Q1
PRODUCTION DATA
The system MCU can activate the ABIST scheduler in the ACTIVE state through the ABIST_GROUPx_START control bits in the SAFETY_ABIST_CTRL register when the ABIST_SCHED_EN configuration bit in the SAFETY_CFG2 register is set. When enabled, the scheduler runs continuously until it is commanded to stop by clearing the ABIST_GROUP_xSTART control bits or when the device goes from the ACTIVE state. The ABIST scheduler cannot run in the DIAGNOSTIC and SAFE state (setting the ABIST_SCHED_EN configuration bit has no impact on ABIST runs in the DIAGNOSTIC and SAFE states when the ABIST_GROUPx_START control bits are set).
At any time when an ABIST group of tests is set to run, the ABIST tests are activated only during the analog comparator output steady state (sampled analog comparator output matches respective deglitched output and SPI status bit).
If none of the previously listed conditions are met, initiation of an ABIST run will be delayed. The maximum wait time to start an ABIST is time limited by its ABIST time-out function.
If any of the scheduled diagnostic tests fail during an ABIST run when the device is in the ACTIVE state or an ABIST start time-out event occurs, the device response depends on the ABIST_ACTIVE_FAIL_RESP configuration bit setting in the SAFETY_CFG2 register.
If the ABIST_ACTIVE_FAIL_RESP bit is set to 0b, the following occurs:
If the ABIST_ACTIVE_FAIL_RESP bit is set to 1b, the following occurs:
An ABIST-start time-out event can indicate a deglitch function failure, which can be detected by observing the GROUPx_ERR bit being set, but none of the individual status bits in the
SAFETY_ABIST_ERR_STATx
registers are set. A deglitch function failure can be detected by the LBIST as well. Before a scheduled ABIST run, two cases of analog comparator failures can occur. These cases are defined as follows:
After the deglitch time, the analog comparator output propagates through the deglitch function and is latched in a SPI-mapped register bit.
The ABIST start condition is met (the analog comparator output is equal to the deglitch function output) and the ABIST run starts.
Because the analog comparator is stuck HIGH (for an example, driving HIGH all the time even when a monitored voltage is in the nominal range) the ABIST run detects an analog comparator failure and signals an ABIST run fail.
The ABIST start condition is met (the analog comparator output is equal to the deglitch function output) and the ABIST run starts.
Because the analog comparator is stuck LOW (for an example, driving LOW all the time even when a monitored voltage is in the OV range) the ABIST run detects an analog comparator failure and signals an ABIST run fail.
Undervoltage and overvoltage comparator diagnostic tests do not impact the regulated output-voltage rails. This ABIST run does not check the current limit circuit of the regulators and the circuits of the VREG UV, VREG OV, VIN UV, and VIN OV voltage monitors. When the VREG regulator is enabled, running the VREG UV and VREG OV diagnostics causes the VREG output to become uncontrollable and for that reason not included in this ABIST run.
Figure 11-11 shows an example with tests for all four ABIST groups when the ABIST_GROUP1_START, ABIST_GROUP2_START, ABIST_GROPU_START3, and ABIST_GROUP_START4 control bits are set.
Figure 11-12 shows an example with tests for two ABIST groups when only the ABIST_GROUP1_START and ABIST_GROUP3_START control bits are set.
The ABIST scheduler runs the activated ABIST group of tests periodically in the ACTIVE state when at least one of the ABIST_GROUPx_START bits is set and while the ABIST_SCHED_EN configuration bit is set. The test repetition period is programmable through the ABIST_SCHED_DLY configuration bits in the SAFETY_CFG8 register. This time period is defined by Figure 11-10. The time delay between any two ABIST groups of tests can be from 281.6 ms to 10380.9 s.
In the ACTIVE state, the t2 time interval is defined by Equation 1
where