JAJSRN4A July 2023 – October 2023 TPS25984
PRODUCTION DATA
Applications which need higher current input protection along with digital interface for telemetry, control, configurability can use one or more TPS25984x device(s) in parallel with TPS25990x as shown in Figure 9-3
TPS25990x is a 60-A integrated eFuse with PMBus® Telemetry interface.
In this configuration, the TPS25990x acts as the primary device and controls the other TPS25984x devices in the chain which are designated as secondary devices. This configuration is achieved by connecting the primary device as follows:
SWEN is pulled up to a 3.3-V to 5-V standby rail. This rail must be powered up independent of the eFuse ON/OFF status.
The secondary devices must be connected in the following manner:
The following pins of all devices must be connected together:
In this configuration, all the devices are powered up and enabled simultaneously.
Power up: After power up or enable, all the eFuse devices initially hold their SWEN low till the internal blocks are biased and initialized correctly. After that, each device releases its own SWEN. After all devices have released their SWEN, the combined SWEN goes high and the devices are ready to turn on their respective FETs at the same time.
Inrush: During inrush, because the DVDT pins are tied together to a single DVDT capacitor all the devices turn on the output with the same slew rate (SR). Choose the common DVDT capacitor (CDVDT) as per Equation 22 and Equation 23.
Refer to TPS25990x for more details.
The internal balancing circuits ensure that the load current is shared among all devices during start-up. This action prevents a situation where some devices turn on faster than others and experience more thermal stress as compared to other devices. This can potentially result in premature or partial shutdown of the parallel chain, or even SOA damage to the devices. The current balancing scheme ensures the inrush capability of the chain scales according to the number of devices connected in parallel, thereby ensuring successful start-up with larger output capacitances or higher loading during start-up. All devices hold their respective PG signals low during start-up. After the output ramps up fully and reaches steady-state, each device releases its own PG pulldown. Because the DVDT pins of all devices are tied together, the internal gate high detection of all devices is synchronized. There can be some threshold or timing mismatches between devices leading to PG assertion in a staggered manner. However, because the PG pins of all devices are tied together, the combined PG signal becomes high only after all devices have released their PG pulldown. This signals the downstream load that it is okay to draw power.
Steady-state: During steady-state, all devices share current nearly equally using the active current sharing mechanism which actively regulates the respective device RDSON to evenly distribute current across all the devices in the parallel chain. After PG is asserted, de-assertion is controlled only by TPS25990x and based on VOUT_PGTH register setting.
Overcurrent during steady-state: The circuit-breaker threshold for the parallel chain is based on the total system current rather than the current flowing through individual devices. This is done by connecting the IMON pins of all the devices together to a single resistor (RIMON) to GND. Similarly, the IREF pins of all devices are tied together and TPS25990x uses internal programmable DAC (VIREF) to generate a common reference for the overcurrent protection block in all the devices. This action helps minimize the contribution of VIREF variation to the overall mismatch in overcurrent threshold between devices.
In this case, choose the RIMON as per the following Equation 16:
The start-up current limit and active current sharing threshold for each device is set independently using the ILIM pin. The RILIM value for each individual eFuse must be selected based on the following equation:
Where N = number of devices in parallel chain (1 × TPS25990x + (N - 1) × TPS25984x)
Other variations: The IREF pin can be driven from an external precision voltage reference.
During an overcurrent event, the overcurrent detection of all the devices is triggered simultaneously. This in turn triggers the overcurrent blanking timer (OC_TIMER) in TPS25990x. The TPS25990x uses the OC_TIMER expiry event as a trigger to pull the SWEN low for all the devices, thereby initiating the circuit-breaker action for the whole chain at the same time. This mechanism ensures that mismatches in the current distribution, overcurrent thresholds and OC_TIMER intervals among the devices do not degrade the accuracy of the circuit-breaker threshold of the complete parallel chain or the overcurrent blanking interval. However, the secondary devices also maintain their backup overcurrent timer and can trigger the shutdown of the whole chain if the primary device fails to do so within a certain interval.
Severe overcurrent (short-circuit): If there is a severe fault at the output (for example, output shorted to ground with a low impedance path), the current builds up rapidly to a high value and triggers the fast-trip response in each device. The devices use two thresholds for fast-trip protection – a user-adjustable threshold (ISFT = 2 × IOCP in steady-state or ISFT = 1.5 × ILIM during inrush) as well as a fixed threshold (IFFT only during steady-state). After the fast-trip, the TPS25990x relies on the SC_RETRY config bit in the DEVICE_CONFIG register to determine if the whole chain enters a latched fault or performs a fast recovery by restarting in current limit manner. If it enters a latched fault, the devices remain latched off till the device is power cycled or re-enabled, or auto-retry with a delay based on the RETRY_CONFIG register setting.