DEV Community

朱常
朱常

Posted on

Multi-Rail PMU: PMIC Architecture for SoCs, Processors and FPGAs

Multi-Rail PMU: PMIC Architecture for SoCs, Processors and FPGAs


Overview
A modern application processor, FPGA or SoC does not run from a single rail. It needs a low-voltage high-current core rail, an I/O rail at the interface logic level, a memory rail for DDR, an analog rail for PLLs and sensing, and a clock or backup rail - often six to a dozen supplies. A multi-rail power management unit (PMU) integrates several DC-DC converters, LDOs, sequencing and telemetry into one chip sized for that processor family. This article explains why the SoC power tree looks the way it does, how a PMU packs multiple rails, and the efficiency-versus-flexibility trade-off that drives the architecture.
  1. Why SoCs Need Many Rails A system-on-chip splits its transistors into voltage domains because each block has different power requirements:
  2. Core logic runs at the lowest practical voltage to minimize dynamic power (CV2f), often below 1 V, and draws the highest current.
  3. I/O blocks run at the interface standard level (1.8 V, 2.5 V or 3.3 V) and must match the external buses.
  4. Memory (DDR3/LPDDR4) needs a defined VDD and VDDQ rail with tight ripple and sequencing.
  5. Analog blocks, PLLs and ADCs need quiet, low-current rails that tolerate little switching noise.
  6. Real-time clock or always-on domains need a tiny, always-available rail.
    Each domain has its own voltage, current, sequencing and noise requirement, which is why a discrete regulator-per-rail approach becomes unwieldy.

  7. What a PMU Integrates
    A typical PMU contains:

  8. Multiple synchronous buck converters (often three to five) for the main rails, each with its own inductor and an internal FET.

  9. Several LDOs for analog, PLL and always-on rails.

  10. Power-on reset, sequencing state machine and enable outputs that bring rails up in the processor's required order.

  11. Protection: over-voltage, under-voltage, over-current and thermal shutdown on each rail.

  12. A serial interface (usually I2C) for the host to read fault status, adjust output voltages, and reconfigure rails.

  13. Often a RTC, a coin-cell backup input, and a general-purpose power-good output.
    The TI TPS65218 family is a representative PMU: it integrates three DC-DC step-down converters plus LDOs and sequencing and is paired with Sitara AM335x/AM437x processors and with NXP i.MX 8M Mini through pre-programmed variants (per datasheet). Companion parts such as the LP8733 family add extra bucks and LDOs for higher-current cores (per datasheet).

  14. Efficiency vs Flexibility
    Integrating rails into one PMU saves board area, BOM count and sequencing glue, but it constrains the rails to what the PMU supports. The fixed output voltages, current limits and sequence order are chosen for a specific processor family. Designers who need a non-standard rail, a different current limit, or a rail count outside the PMU's capability either add a discrete regulator for the spare rail or use a more flexible (and larger) controller-based design. Pre-programmed variants (EEPROM or one-time programmable memory) ship with the voltage and sequence settings already loaded for a given processor, reducing host firmware effort.

  15. The Buck / LDO Mix
    The PMU's buck converters handle the high-current rails - core, memory and main I/O - because buck efficiency dominates at those currents. The LDOs handle the quiet, low-current analog rails where a small amount of dropout loss is acceptable in exchange for low noise. Some PMUs also use load switches instead of LDOs for always-off rails to cut standby leakage. PFM (pulse-frequency modulation) light-load mode on the bucks preserves efficiency at low system activity, which matters in battery-powered and always-on products.

  16. Power-Tree Planning
    Before selecting a PMU, the engineer builds a power tree: list every rail the SoC requires, its voltage, current, sequencing requirement, ripple budget and noise tolerance. Then map that tree onto the PMU's rails. Common planning checks:

  17. Does any buck support the core rail's peak current (including DDR and CPU bursts)?

  18. Does an LDO cover the analog/PLL noise requirement?

  19. Does the sequencing order match the SoC's power-on sequence (core before I/O, I/O before memory, etc.)?

  20. Are the power-good and reset timing compatible with the processor boot?

  21. Is there enough margin for the input supply range (battery vs adapter)?

  22. Design Considerations

  23. Choose the PMU variant pre-programmed for your processor if one exists; it removes the most firmware and sequencing risk.

  24. Assign the highest-current rails to the bucks, the quiet rails to the LDOs, and never use a buck for a noise-sensitive analog rail.

  25. Place the inductors close to the PMU with short switch-node traces; the switch node is the main radiator.

  26. Route I2C away from the inductor and switch node so that telemetry reads are not corrupted.

  27. Size input and output capacitors for the recommended ESR and ripple current; a PMU's buck loop is tuned to a specific capacitor range.

  28. Verify thermal: several rails dissipate loss in one package, so check the package thermal rating and copper area at total output power.

  29. Leave one spare rail or external enable for future board revisions; PMUs are chosen per board and cannot easily be re-pinned.

FAQ
Q: When should I use a PMU instead of discrete regulators?
A: When you have a known processor with a multi-rail requirement and you want one chip, one layout and one sequenced power tree; discrete parts win when the rail set is non-standard or needs more current than the PMU provides.

Q: Can a PMU be used with any processor?
A: No. PMUs are chosen per processor family; the output voltages and sequence order are tuned to that SoC's datasheet. Generic PMUs exist but require more host configuration.

Q: What is the serial interface on a PMU for?
A: The host reads fault status, adjusts output voltages on the fly, re-enables rails, and reads temperature or current telemetry over I2C.

Q: Why not just use a buck for every rail?
A: Because a buck's switching noise would contaminate analog and PLL rails. LDOs are used on quiet low-current rails despite their lower efficiency.

Q: How many rails does a typical PMU provide?
A: Commonly three to five bucks plus two to four LDOs, enough to power a mid-range application processor with its memory and I/O (typical - refer to official datasheet for the specific device).

For exact specifications and design guidance, refer to the official datasheets for the Texas Instruments TPS65218 family and the LP8733 companion PMUs.

Top comments (0)