Designing with DrMOS, Part II: Application Guidelines
Mar 1, 2011 12:00 PM
Sanjay Havanur, Principal Applications Engineer Alpha and Omega Semiconductor
A new class of power modules combine the driver and the MOSFETs in a single package, offering compact and efficient power conversion solutions. These DrMOS power modules are an excellent solution optimized for high frequency power conversion at high output currents.
News & Features From Auto Electronics
Committed to improving hybrid electric cars
New Motors for Hybrid Vehicles
Battery Firms Battle for Hybrid Hegemony
Innovative Bipolar Plates for Fuel Cells
See More Headlines
Top Articles
Exploring Current Transformer Applications
Ultracapacitor Technology Powers Electronic Circuits
Buck-Converter Design Demystified
Sensorless Motor Control Simplifies Washer Drives
PET Resources
Buyer's Guide
Conferences
Engineering Jobs
Power Electronics Events
Rent Our Lists
Spotlight on Digital Power
Find a downloadable version of this story in pdf format at the end of the story.
Traditionally in synchronous buck designs, the PWM controller and its driver have been a single unit, for cost and space considerations. The downside was that the PWM IC with the most desired features did not always come with the most powerful driver. Nor was it possible to closely match that one driver to different power devices. DrMOS offers a logical solution to the problem, putting all the unintelligent components of the buck converter in one package. Co-packaging the driver with two MOSFETs has its challenges but gives a great deal of flexibility to designers, who can derive a logic level PWM signal from anywhere in their system.
Since the PWM signal is provided from an external controller or a digital processor, extra care must be taken during start up. DrMOS modules must be powered up and enabled before the PWM input is applied. It should be ensured that PWM signal is applied through a proper soft-start sequence to minimize inrush current in the converter. Powering the module with a full duty cycle PWM signal already applied may lead to a number of undesirable consequences. If the DISB# is used similar caution is necessary to ensure proper sequencing with the PWM controller. Every time the power module is disabled through DISB#, there will be no output and the external controller may enter into open loop and put out a PWM signal with maximum duty ratio possible. If the DrMOS is re-enabled by simply taking DSBL# high, there will be extremely large inrush currents while the output voltage builds up again which may drive the system into current limit. There might be unpredictable consequences such as inductor saturation, overloading of input or even a catastrophic failure of the device. It is recommended that PWM controller be disabled whenever the DrMOS power stage is disabled or non operational for any reason. The PWM controller should always be enabled with a soft start to minimize stresses on the converter.
MODULE LOSS AND EFFICIENCY
Intel Rev 3.0 specifications impose fairly stringent limits on module loss and efficiency on DrMOS power trains. Under the specific boundary conditions of 12Vin /1Vout /25A (28A max) with operating frequency of 300 kHz to 1 MHz, the target for module losses is 6W maximum. The actual performance of AOZ5006 is shown in Fig. 1.
As with any SMT power device the so-called “rated current” of a DrMOS module is no indicator of its performance
USING RBOOT
The boost supply for driving the high side MOSFET is generated by connecting a small capacitor between the BOOT pin and the switching node VSWH. It is recommended that this capacitor CBOOT be connected as close as possible to the device across pins 4 and 15. Boost diode is integrated into the package. Fig. 2 shows RBOOT, an optional resistor used by many designers to slow down the turn on speed of the high side MOSFET. The value is a compromise to keep both the switching time and VSWH node spikes as low as possible and is typically 1Ω ~ 10Ω. Fig. 3 shows the impact of various values of RBOOT on VSWH voltage at V
Continue on next page
Acceptable Use Policy blog comments powered by Disqus


