123 Main Street, New York, NY 10001

Digital bucks with PMBus/I²C enable online loop and threshold tuning without rework, provide telemetry and black-box logging for field diagnostics, and support scriptable sequencing to coordinate multi-rail bring-up/down safely. This page focuses on practical architecture, tuning touchpoints, and validation routines for servers, communications, industrial systems, and automotive controllers.

← Buck / Boost / Buck-Boost Regulators

Online loop/threshold config Telemetry & black-box logging Scriptable multi-rail sequencing
Digital Buck w/ PMBus Online tuning • Telemetry • Scriptable sequencing VIN Digital Buck PWM • ADC • Compensation PMBus/I²C VOUT Online loop & threshold config Telemetry / black-box Scriptable sequencing
Cover — Digital Buck with PMBus: online loop tuning, telemetry logging, and scriptable sequencing.

Architecture

The control stack links VOUT/VIN/IOUT/Temp sensing through an ADC and digital compensation to the PWM core, while a PMBus agent accesses a protected register map for online tuning and telemetry. A sequencing engine coordinates rail enables, PG dependencies, and fault policy.

Sensing & ADC • VOUT / VIN / IOUT / Temp • Fsense / averaging / decimation • Quantization (LSB → %VOUT) Digital Compensation • PID / biquad • Kp/Ki/Kd or b0,b1,b2,a1,a2 • Mode gates (PWM/PFM/APS) PWM Core • Duty limit / soft-start/stop • Pre-bias compatible • Spread-spectrum (if available) Protection • OV/UV / ILIM / Foldback / Thermal • Fault to PG/Sequencer Register Map • Config / Status / Diagnostics • Online-tunable vs OTP/MTP PMBus / I²C Agent • Voltage, thresholds, margining • Telemetry read / batch writes Telemetry & Black-Box • VIN/VOUT/IOUT/Temp, Fault code • Timestamped snapshots / FIFO depth Sequencing Engine • Rail enable graph / PG dependencies • Fault policy: latch / retry / hiccup PG / Rail Status Online Tuning Points: comp, thresholds, slew, modes Safety Gates: write-protect & limits
Control stack — sensing/ADC → digital compensation → PWM core; PMBus agent via protected register map; telemetry and sequencing side-bands.

PWM Core

Duty limiting, soft-start/stop, and pre-bias-safe startup. If spread-spectrum is available, verify loop phase margin under modulation and at worst-case load steps.

ADC Sampling

Choose Fsense and averaging to balance noise and latency. Quantization step (LSB) should map cleanly to %VOUT and threshold hysteresis to avoid chatter near UV/OV points.

Register Map

Separate configuration, status, and diagnostics. Clearly mark online-tunable vs OTP/MTP fields and require unlock sequences for dangerous writes in the field.

PMBus Layer

Implement page/rail addressing, voltage/threshold commands, margining, and telemetry reads. Support batch write-tables for production and service re-calibration.

Principles: Online Tuning & Safe Operating Limits

Expose only what is safe to tune online: compensation coefficients, OV/UV thresholds with hysteresis, temperature-based derating, and DVS/DVFS ramps. Guard every write with ranges, unlock sequences, and rollback snapshots. Start from offline sweeps, then refine on board under scripted step and thermal runs.

Compensation • PID/biquad ranges • Bandwidth clamps OV/UV Thresholds • %VOUT + hysteresis Temp Compensation • mV/°C or %/°C slopes DVS / DVFS • Ordered freq/voltage ramps Rollback & Black-Box • Snapshot: VIN/VOUT/IOUT/Temp • Fault code + timestamp • Known-good config store Safety Gates • Write-protect & unlock • Range limits & rate limits • Min phase margin guard • Thermal/ILIM overrides DVFS order: reduce freq → reduce voltage; reverse when increasing
Online tuning map — expose safe parameters, guard writes, and keep rollback snapshots for field service.

Compensation (online, but bounded)

Publish only bounded coefficients and clamp the loop bandwidth. Enforce a minimum phase margin target before accepting writes. Use scripted step/sweep to capture stability snapshots and allow one-click rollback.

OV/UV thresholds with hysteresis

Define thresholds in %VOUT and map to ADC LSBs with rounding rules. Hysteresis must exceed noise and ripple envelopes to avoid chatter, and link UV actions to the chosen fault policy.

Temperature-based derating

Apply mV/°C or %/°C slopes to voltage, current limit, or switching frequency. Log temperature points and state transitions in the black-box for post-mortem analysis.

DVS/DVFS ramp control

Coordinate with the SoC/FPGA clock domain: reduce frequency before voltage drops; when increasing, raise voltage first. Use slew-rate limits and temporary UV hysteresis widening to avoid false trips.

Quantization rule: align thresholds and hysteresis to ADC LSBs (prefer even steps to prevent foldback oscillations).

Design Rules: Threshold Mapping, Stability Margins & Load-Step Criteria

Configure thresholds from system tolerances, verify loop margins with sampling delays counted in, and qualify transient behavior with worst-case load steps and mode changes. Automate sweeps and keep batchable PMBus tables.

Threshold Mapping • Tolerances → %VOUT → mV • Round to ADC LSBs • Hysteresis ≥ 2–3× LSB Stability Targets • PM ≥ 45°, GM ≥ 6 dB • BW ≈ Fsw/10 … Fsw/6 • Count ADC/filter delay Load-Step Acceptance • Overshoot/undershoot ≤ ±3% • Settling within target τ • PWM/PFM switch criteria Automation & Reporting • Sweep & step scripts (hot/cold/room, lot spread) • Batch PMBus write-tables with readback verify • Black-box export for regression Protection Interplay • ILIM & foldback enter/exit • Fault policy: latch/retry/hiccup
Design checks — thresholds align to ADC LSBs, stability margins confirmed against sampling delay, and load-step acceptance with mode switching.

Threshold setup & hysteresis sizing

Start from system tolerances: UV = Vset×(1−M%), OV = Vset×(1+N%). Round limits to ADC LSBs and size hysteresis ≥ 2–3× LSB or above 3σ of ripple/noise, whichever is larger. Lock critical writes behind an unlock window.

Bandwidth placement & stability margins

Aim PM ≥ 45° and GM ≥ 6 dB; production target PM 50–60°. Keep bandwidth near Fsw/10…Fsw/6. Re-measure with spread-spectrum enabled and include ADC/filter latency in the phase budget.

Load steps & mode switching criteria

Use ΔI ≈ 50% Imax across light↔heavy transitions. Enforce ±(2–3)%VOUT window and settling within the target time constant. Switch PFM→PWM before hitting ripple or droop limits. Coordinate DVFS ramps to avoid compounded transients.

Noise envelope: quantify ripple and random noise (peak-to-peak and σ) and keep thresholds outside the envelope by a safe margin.

ADC-aligned thresholds PM ≥ 45° target ΔI ≥ 50% Imax PFM↔PWM switch logic Scripted sweeps

Sequencing: Scripted Multi-Rail Order, PG Graph & Fault Policies

Define enable order and dependencies with a PG graph, apply time guards, and bind each violation to a fault policy (latch, auto-retry, hiccup). Brown-out handling coordinates DVFS and controlled shutdown to keep the system safe.

Enable Order & PG Windows Rail A PG(A) stable Rail B enable after PG(A) Rail C enable after PG(B) Fault Policy Matrix • Over-current → hiccup N tries • UV/PG timeout → auto-retry • Thermal → latch until cool • OV → immediate shutdown Brown-Out Handling • Detect VIN/VOUT droop level and slope • Degrade: DVFS reduce freq → reduce V • If droop persists: controlled rail shutdown • Log event + pre/post samples in black-box Script Interface (PMBus tables) • Steps: set V, wait PG, if timeout → branch policy • Conditions: page/rail select, retries, back-off • Readback verify & CRC
Scripted sequencing — enable order with PG windows, fault policy decisions, and brown-out response.

Enable order & dependency graph

Use a rail graph: each rail enables only after its predecessors reach PG for a defined dwell time. Keep separate power-up and power-down scripts with timeouts and rollback steps.

Policy per fault class

Bind OC/UV/OV/OT to distinct actions. Cap auto-retry counts and add exponential back-off. Thermal faults usually latch until temperature clears and a manual or scripted reset occurs.

Brown-out coordination with DVFS

When VIN/VOUT sags, reduce clock first, then voltage ramps. If margins are not recovered, shut down non-critical rails first, preserving logging and safe state.

Keep scripts as PMBus tables that production and field service can reuse. Always include readback verification.

Telemetry & Black-Box: What to Log, How Often, and How to Read Health

Instrument rails with meaningful channels and right sampling tiers. Track health by regulation error, settling time, ripple statistics, and fault/event rate. On events, capture pre/post snapshots for post-mortem debugging.

Telemetry Channels • VIN / VOUT / IOUT / Temp • Duty / Fsw / PWM-PFM mode • PG state / margining level • Optional: error amp / comp state Sampling & Averaging • Run: 10–100 Hz • Burst on events: 1–2 kHz • Averaging, decimation, peak/valley Health Indicators • Regulation error (RMS / pk) • Settling time vs target • Ripple σ / peak-to-peak • Fault & UV event rate Black-Box Snapshot Frame • Trigger: fault, PG fail, brown-out, DVFS swap, temp limit • Fields: ts, VIN/VOUT/IOUT/Temp, mode, fault code • Ring buffer: N pre + N post samples • Export CSV/binary with readback auth
Telemetry design — channels and tiers, plus a snapshot frame for event-driven debugging.

Choose channels that diagnose causes, not just symptoms

Beyond VIN/VOUT/IOUT/Temp, add duty, mode, and PG state. Optional internal nodes (error amp output, comp states) help distinguish loop issues from power path issues.

Tiered sampling with burst windows around events

Use 10–100 Hz in steady state; switch to 1–2 kHz burst around events with small pre/post windows. Apply averaging/decimation to reduce noise while preserving edges.

Quantify health by error, settling and ripple statistics

Track regulation error (RMS and peak), settling time to window, ripple σ and peak-to-peak, and the rate of UV/fault events. Flag out-of-spec metrics for service actions.

Snapshot frames with pre/post samples

When triggers fire, capture timestamps, rails, mode and fault code together with a ring buffer of samples. Protect access, and allow CSV or binary export with authentication.

Retention vs coverage: pick a snapshot depth that fits your memory budget while keeping enough context (e.g., 64 pre + 128 post at 1 kHz).

Run 10–100 Hz Burst 1–2 kHz RMS/peak error Pre/Post snapshots CSV/BIN export

Validation: Tolerances, Cross-Temperature/Lot & In-System Calibration SOP

Before mass production, sweep BOM tolerances, validate stability and transients across temperature and lots, and execute an in-system calibration SOP. Close the loop with PMBus readback, black-box snapshots, and batchable write-tables for factory and field.

BOM Tolerance Sweep • Inductor L / DCR / ESR • Output/comp capacitors ESR • Divider resistors tolerance • MOSFET Rds(on) vs temp → Poles/zeros, BW, PM/GM Cross-Temperature × Lot Cold Room Hot Lot A Lot B Lot C Targets: PM ≥ 50°, GM ≥ 6 dB, overshoot ≤ ±3%VOUT In-System Calibration SOP 1. Read baseline config 2. Apply load & env setpoints 3. Tune thresholds/comp (bounded) 4. Readback verify & CRC 5. Commit MTP/OTP (if any) 6. Snapshot to black-box Acceptance Criteria & Reporting • PM 50–60° (min 45°), GM ≥ 6 dB; BW ≈ Fsw/10…Fsw/6 • Step transient: ±(2–3)%VOUT, settle within target τ • DVFS: no false UV, proper order • All thresholds aligned to ADC LSB; readback verified
Validation matrix — tolerance sweep, cross-temperature/lot checks, and a documented calibration SOP with readback.

BOM tolerance → poles/zeros → stability impact

Model L/C/ESR and divider spread, include MOSFET Rds(on) vs temperature, then identify worst-corner combinations that reduce phase margin or shift bandwidth outside targets.

Cross-temperature and cross-lot stress

Test Cold/Room/Hot across at least three lots. Log PM/GM/BW, overshoot/undershoot, settling time, UV/OV edges, and repeat with spread-spectrum enabled to capture worst cases.

Calibration SOP with readback and black-box

Use batchable PMBus tables. After each write, verify by readback and checksum; store a snapshot and the final table with operator, version, and timestamp for traceability.

Quantize thresholds and hysteresis to ADC LSBs (prefer even steps) and keep noise/ripple margins ≥ 3σ to avoid chatter.

Layout & EMI: Clean Sensing, Minimal Switching Loops & Solid Grounding

Stability and EMI start with routing: Kelvin voltage sense, robust current sense placement, minimized hot/output loops, and disciplined grounding. Add spread-spectrum/sync, π filtering, and stitching-via fences where needed.

Voltage Sense & ADC Routing • Kelvin sense at load; differential • Keep away from SW node • RC anti-alias / low-noise filter • AGND single-point tie to PGND Minimized Switching Loops • Hot loop: HS→SW→LS→Cin • Place Cin next to FETs + via array • Output loop: FET→L→Cout (short) • Keep dv/dt zones off sense lines EMI Techniques • Spread-spectrum / sync • π filters at in/out ports • Stitching-via fences (“walls”) • Clear return paths, no slots Current Sense & Grounding • Shunt (low/high-side) or inductor DCR; keep amp near source • Symmetric copper, short/wide high-current paths • PGND solid plane; AGND star-point at IC or jumper • Define ESD/connector return path explicitly
Layout guidance — Kelvin/differential sensing, minimized hot and output loops, disciplined grounding, and practical EMI aids.

Clean voltage sensing with Kelvin picks

Sense at the load with differential pairs, filter with small RC, and keep traces far from the SW node. Tie AGND to PGND at a single star point close to the IC.

Robust current sense and amplifier placement

Choose shunt or DCR sensing based on efficiency and bandwidth. Place the amplifier near the source, route symmetrically, and provide thermal symmetry for accurate readings.

Shrink hot/output loops to cut EMI at the source

Place input ceramics next to FETs with via arrays; keep the output loop (FET→inductor→Cout) short. Keep high dv/dt copper away from sense lines and analog nodes.

Spread, sync, filter and fence

Enable spread-spectrum or sync to move energy; add π filters where cables exit; build stitching-via “walls”; ensure uninterrupted return paths without plane slots under critical signals.

Review Gerbers for sense/ground topology and loop areas before fabrication. A 10-minute pre-flight often saves a full spin.

Kelvin sense Hot loop minimization AGND–PGND star point Spread-spectrum Stitching-via fences

IC Selection Matrix: PMBus-Capable Digital Buck Options Across Seven Vendors

Compare PMBus/I²C digital bucks by interface support, output current range, switching frequency, telemetry depth, sequencing features, protections, sync/spread options, automotive AEC-Q100 availability, and packaging notes. Values are typical capability ranges for quick shortlist building.

Legend Interface IOUT (A) Fsw (kHz/MHz) Telemetry Sequencing Protections Sync/Spread AEC-Q100 Package / Notes
Legend — columns referenced by the matrix below.
Vendor / Family (examples)
Interface
IOUT Range
Fsw
Telemetry
Sequencing
Protections
Sync/Spread
AEC-Q100
Pkg / Notes
TI — PMBus Digital Bucks
PMBusSMBus/I²C
2–30 A (single); multi-phase via controllers
200 kHz – 2 MHz
VIN/VOUT/IOUT/Temp, fault log
Enable graph, margining, PG timers
OV/UV/ILIM, foldback, thermal
EXT SYNC, spread-spectrum (select)
Select parts
QFN/QFP; strong toolchain & app notes
Renesas — Digital VR/PMBus Bucks
PMBusI²C
3–60 A (controller/monolithic)
300 kHz – 1.5 MHz
V/I/Temp + black-box depth options
Rail dependency & retry policies
Latch/auto-retry/hiccup configurable
SYNC IN/OUT; dither on some
Broad availability
PQFN/QFN; VRM heritage
Microchip — Digital Power Ecosystem
PMBusI²C
1–20 A (mono) / higher via controllers
200 kHz – 2 MHz
Rich telemetry + scriptable logs
Table-driven sequencing engine
OV/UV/ILIM/TSD with policies
SYNC, optional spread
Select industrial/auto
QFN/QFP; MPLAB integration
onsemi — Configurable Bucks
PMBusI²C
1–20 A
200 kHz – 1.5 MHz
Core voltage/current/temp
Enable/PG timers, dependencies
Comprehensive with foldback
SYNC; dither on variants
Automotive options
QFN/DFN; compact footprints
NXP — PMBus-Ready Power (SoC/Auto)
PMBus/I²C
1–10 A (buck channels)
300 kHz – 2 MHz
Essential V/I/T + PG state
Rail graph tied to PG
Standard set + thermal
SYNC (select)
Yes on key parts
QFN; strong auto ecosystem
ST — Digital/Managed Bucks
PMBusI²C
1–20 A
250 kHz – 2.2 MHz
Voltage/current/temp + logs
PG/enable order & timers
OV/UV/ILIM/TSD
SYNC; spread on variants
Multiple options
QFN/QFP; STM32 tooling synergy
Infineon — Digital Bucks/Controllers
PMBusI²C
3–40 A (controller-based up)
300 kHz – 1.5 MHz
V/I/T; black-box depth by part
Graph + fault policy hooks
OV/UV/ILIM, hiccup/latch
SYNC; spread on select
Available
PQFN/QFN; efficient FET options

Notes: Ranges summarize commonly available capabilities in each vendor family and may vary by device. Use this matrix to shortlist; confirm exact specs from the chosen datasheet.

FAQs: Practical Tuning, Sequencing, Telemetry & Validation

Short, field-tested answers for PMBus digital bucks. Each item ends with a quick link back to the relevant section above for deeper guidance.

Which compensation parameters are safe for online tuning?
Expose bounded coefficients only: PID (Kp/Ki/Kd) or biquad (b0,b1,b2,a1,a2) within tested ranges. Clamp closed-loop bandwidth and enforce a minimum phase-margin guard before accepting writes. Use scripted step/sweep to verify stability and store a rollback snapshot after each accepted change.
How to align OV/UV thresholds and hysteresis to ADC LSBs?
Define limits in %VOUT, convert to mV, then quantize to the nearest ADC LSB. Make hysteresis ≥2–3× LSB or above 3σ of ripple/noise—whichever is larger—to avoid chatter near the edges. Always verify by readback after programming.
Recommended telemetry sampling rates in run vs event windows?
Use 10–100 Hz in steady run. Around events (PG timeout, UV/OV, DVFS) capture a short burst at 1–2 kHz with pre/post windows. Apply averaging/decimation in run mode; keep raw samples in the burst window for post-mortem analysis.
How to read loop health from error, settling and ripple stats?
Track regulation error (RMS and peak), settling time into the target window after steps, and ripple σ/pp. Stable loops show consistent error, bounded settling, and low event rate. Degradations hint at margin loss, quantization or layout noise.
What triggers a black-box snapshot and what does it store?
Triggers: faults, PG failures, brown-out entry/exit, DVFS swaps, temperature threshold crossings. Store timestamp, VIN/VOUT/IOUT/Temp, mode, fault code and a ring buffer of pre/post samples. Export as CSV or binary with read-auth.
How to choose fault policy for PG timeouts and UV events?
Use auto-retry with capped attempts for transient UV/PG timeouts. Use hiccup for over-current to lower thermal stress. Thermal typically latches until cool-down and manual/scripted reset. Log each decision in the black-box.
What is the correct DVFS order during brown-out?
Reduce clock first, then reduce voltage with a bounded slew. When recovering, raise voltage before increasing frequency. If margins do not recover, shut down non-critical rails by script while logging the event.
Does spread-spectrum affect stability targets?
It can shift bandwidth edges and phase dips. Keep BW ≈ Fsw/10…Fsw/6 and re-measure PM/GM with spread on. Count ADC/filter latency in the phase budget and re-verify worst-case steps.
How to minimize hot/output loops on PCB layout?
Place input ceramics next to the FETs with dense via arrays; route the hot loop HS→SW→LS→Cin tightly. Keep the output loop FET→L→Cout short and away from sense lines; avoid plane slots under critical paths.
Best practice for Kelvin voltage sense and AGND–PGND tie?
Kelvin sense at the load using a differential pair; RC filter near the ADC pin. Keep far from SW copper. Tie AGND to PGND at a single star point close to the IC or a dedicated jumper to control return paths.
Validation acceptance targets before mass production?
PM ≥ 50° (min 45°), GM ≥ 6 dB; BW ≈ Fsw/10…Fsw/6; step overshoot/undershoot ≤ ±(2–3)%VOUT with settling within target τ; DVFS without false UV; thresholds/hysteresis aligned to ADC LSB and verified by readback.
Typical DVS/DVFS slew and limits to avoid false UV?
Use device-specific limits, but 2–10 mV/µs is common for core rails. Temporarily widen UV hysteresis during DVS steps and ensure mode gates (PFM→PWM) switch before droop reaches the limit.
How are dangerous writes protected in the field?
Use unlock sequences and write-protect regions. Validate ranges and rate limits in firmware. Require readback+CRC to commit, and log each session into the black-box with operator/time/version for traceability.
How to organize sequencing tables and verify writes?
Use page/rail addressing and step rows: set V → wait PG (dwell) → branch on timeout. Keep retry counters and exponential back-off. After batch writes, perform readback verify and store the applied table version.
Any tips for AEC-Q100 temperature corners?
Verify across cold/room/hot and at least three lots. Track PM/GM/BW and UV/OV edges; account for Rds(on) and ESR drift. Apply temperature-based derating for current/frequency where needed.

Submit Your BOM for a 48-Hour Digital Buck Review

What you get in 48 hours

We return a concise report: recommended IC shortlist, initial compensation targets, ADC-aligned thresholds, and a draft sequencing table. Works across TI / Renesas / Microchip / onsemi / NXP / ST / Infineon.