123 Main Street, New York, NY 10001

Regenerative (StrongARM-Type) Dynamic Latch Comparator

← Back to:Comparators & Schmitt Triggers

StrongARM (regenerative) latches win when a clocked decision must be both fast and energy-efficient. Real-world success is set by three things: decision-time tail, offset/memory, and kickback—measure and guardband them, then integrate safely into SAR/TDC interfaces.

What this page solves (StrongARM in real systems)

A StrongARM-type regenerative latch is a clocked dynamic comparator: it consumes energy mainly during the evaluate phase, then uses positive feedback to amplify a tiny differential input into a full-swing digital decision. This page focuses on when that clocked, dynamic behavior is the right tool—and what system-level constraints it introduces.

The decision triangle (what must be balanced)
  • Speed: decision time depends strongly on overdrive and node capacitances.
  • Energy per decision: dynamic action limits static power, but evaluate pulses draw peak current.
  • Error & disturbance: input-referred uncertainty and kickback must be managed at the interface.
Where StrongARM is commonly used (only the “natural fits”)
  • SAR ADC comparator: repeated decisions make energy/decision critical; decision window is clock-defined.
  • TDC arbiter / race detector: small arrival-time differences require fast, symmetric regeneration.
  • Time pickoff / ToF echo gating: extracts a timing event from a threshold crossing with a defined evaluate moment.
  • Low-VDD fast thresholding: dynamic latch can outperform biased solutions when static current is constrained.
Practical “use it / avoid it” trigger
  • Use a StrongARM-type latch when a clocked decision window is acceptable and speed/energy-per-decision dominate.
  • Plan mitigation when the source is high impedance or sampling-sensitive: treat kickback as a first-order interface risk.
  • Expect tails at small overdrive: metastability-like long delays must be guarded by timing margin or re-sampling.
StrongARM comparator system map: SAR loop, TDC arbiter, and time pickoff Block diagram showing three common contexts where a clocked StrongARM regenerative latch is used, with clocked evaluate tags. StrongARM Regenerative Latch CLK EVAL SAR Loop CDAC Input Logic Update TDC Arbiter Edge A Edge B Time Pickoff / ToF Gating Signal Threshold Timestamp Latch/FF Clock defines the decision window; regeneration delivers a fast digital decision but disturbs the input unless managed.

StrongARM topology in one view

A StrongARM latch can be understood as four mandatory functional blocks: an input pair that creates an initial differential, a regenerative core that amplifies it exponentially, a reset / precharge network that removes memory between decisions, and output nodes that set the effective time constant and interface to digital sampling.

What each block “buys” and what it can break
  • Input pair: converts ΔVin into a small node imbalance; limits appear at low VDD and extreme common-mode.
  • Regenerative core: sets the speed/overdrive relationship; asymmetry turns into systematic offset and decision bias.
  • Reset / precharge: prevents “memory” and correlation; incomplete reset creates history-dependent thresholds.
  • Output nodes: define the time constant and metastability tail; loading and sampling timing must be budgeted.
Common add-ons (used to fix a specific interface problem)
  • Preamp-latch: improves small-overdrive decisions and reduces kickback; costs power/area and adds its own noise budget.
  • Input isolation: protects high-impedance sources and sampling networks; costs bandwidth and adds input capacitance.
  • Hybrid assist: adds static bias or controlled gain to stabilize corners; costs static current and complexity.
StrongARM comparator topology: input pair, regenerative core, reset, and outputs with common add-ons Block diagram showing the core functional blocks of a StrongARM regenerative latch and optional preamp, isolation, and hybrid assist modules. VINP VINN OUTP OUTN StrongARM Core Input Pair Regen Core Reset Prechg O N CLK Optional Add-ons Preamp Isolation Assist The core is clocked and memory-sensitive; add-ons exist to control kickback, small-overdrive speed, and corner robustness.

Two-phase operation: reset/precharge → evaluate/regenerate

A StrongARM latch is fundamentally a two-phase machine. In reset / precharge, internal nodes are forced back to a known, repeatable starting point. In evaluate / regenerate, the clock releases the latch and positive feedback amplifies a tiny input imbalance into a full digital decision. Most real failures come from treating this timing as “ideal” when it is not.

What reset must actually accomplish (node-level view)
  • Output nodes: return to a defined level (or near-zero differential) so each decision starts from the same baseline.
  • Regeneration core: remove residual charge that would otherwise bias the next decision (“memory”).
  • Symmetry: ensure both sides see comparable reset strength; asymmetry behaves like systematic input offset.
Define the decision window in engineering terms
  • t0: the effective evaluate edge at the latch core (clock arrival + internal gating).
  • t_valid: the moment OUTP/OUTN is valid for the next stage (crossing or sufficient swing).
  • t_decision = t_valid − t0: the time budget that must be met across overdrive and corners.
The three common timing traps (symptom → cause → quick check)
  • History-dependent decisions → incomplete reset leaves charge (“memory”) → lengthen reset time or lower clock rate and confirm the bias collapses.
  • Bias at near-zero input → clock feedthrough creates a fake initial imbalance → change clock swing/edge rate and check whether the decision bias tracks the clock.
  • Threshold shifts across modes → duty-cycle changes reshape reset/evaluate overlap → hold reset width constant and sweep duty to see if the threshold moves.
Minimal timing data fields (for simulation, bring-up, and vendor questions)
  • t_reset_min: shortest reset that eliminates memory and bias.
  • t_eval_to_valid: evaluate-to-valid latency under the minimum expected overdrive.
  • valid_condition: what the next stage uses as “valid” (crossing, swing threshold, or FF input limit).
  • clock_sensitivity: qualitative note on swing/edge-rate/duty dependence.
StrongARM two-phase timing: reset and evaluate with decision window markers Timing diagram showing CLK, RESET, input differential, and complementary outputs with t0, t_valid, and t_decision annotations. CLK RESET ΔVIN OUTP/OUTN t0 t_valid t_decision t_reset t_eval memory risk Reset establishes repeatable initial conditions; evaluate starts at t0 and must reach a valid output by t_valid.

Regeneration math that matters (decision time vs overdrive)

Regeneration behaves like an exponential amplifier: a tiny initial differential grows rapidly once positive feedback takes over. The key system insight is that decision time is a logarithmic function of initial imbalance. When overdrive is small, the latch needs far more “gain-time” to reach a valid output—creating long-delay tails that must be budgeted.

The engineering model (keep the shape, not the derivation)
  • Growth: ΔV(t) ≈ ΔV0 · e^(t/τ)
  • Time-to-valid: t_decision ≈ τ · ln(ΔV_target / ΔV0)
  • What sets τ: stronger transconductance (gm) and smaller effective node capacitance shorten τ.
Why small overdrive becomes “slow” (and sometimes looks like metastability)
  • ΔV0 is the start line: smaller ΔV0 requires more exponential gain-time to reach the same ΔV_target.
  • ln(1/ΔV0) grows fast: below a certain overdrive, timing tails dominate worst-case latency.
  • Engineering implication: do not qualify only “typical” delay—review t_pd versus overdrive and corners.
What to ask for / what to verify (actionable metrics)
  • t_pd(OD): delay versus overdrive across PVT and load conditions.
  • Minimum OD: smallest overdrive that still meets timing with acceptable tail risk.
  • Decision margin: define “valid” at the digital interface (crossing or swing threshold) and budget to that point.
Regeneration exponential growth: different overdrive values create different crossing times Plot-style diagram showing exponential differential growth from three different initial values to a target level, with corresponding crossing times and tau annotation. t ΔV V_target ΔV0 high ΔV0 mid ΔV0 low t1 t2 t3 t ≈ τ · ln(Vt/ΔV0) Smaller initial imbalance (lower overdrive) pushes the crossing time out, creating long-delay tails that must be budgeted.

Offset: where it comes from and why “dynamic” can still drift

In a StrongARM latch, “offset” is not only device mismatch. Any mechanism that creates a non-zero initial imbalance at the start of evaluation (or shifts the internal operating point during regeneration) behaves like an effective input offset. That is why a dynamic latch can still show drift across duty cycle, clock swing, supply noise, and corners.

Offset sources (categorized by what must fix them)
  • Mismatch (layout/sizing): input pair mismatch, cross-coupled asymmetry, and unequal switch injection create a systematic bias.
  • Charge memory (reset/timing): incomplete reset leaves residual charge, making the next decision depend on the previous result.
  • Clock injection (clock routing/edge): feedthrough can create a “fake” ΔV0 at t0, especially when the true overdrive is small.
  • Supply & ground bounce (PDN/layout): evaluate current steps shift internal bias points and appear as input offset during the decision window.
Recognize the “dynamic drift” pattern (fast checks before deep analysis)
  • Offset changes with duty/reset width: prioritize charge memory and reset asymmetry; lengthen reset and verify the bias collapses.
  • Offset changes with clock swing/edge rate: prioritize clock injection; compare slow/fast edge conditions and check sign consistency.
  • Offset worsens at low VDD / high T: prioritize PVT sensitivity; reduced headroom and gm magnify asymmetries and injection artifacts.
Minimal offset budget fields (trackable and testable)
  • VOS_mismatch: systematic bias from mismatch (Monte Carlo + temperature trend).
  • VOS_memory: bias that depends on reset width, frequency, or decision history.
  • VOS_clk: bias that tracks clock swing/edge/duty (feedthrough dominated).
  • VOS_PDN: bias that tracks supply ripple or ground bounce during evaluate.
Offset budget map for a StrongARM regenerative latch Three-column map showing offset sources, impact paths, and controllable mitigation levers such as layout, reset timing, and power integrity. Sources Impact Path Controls Mismatch devices / symmetry Charge Memory reset quality Clock Injection feedthrough Supply / GND bounce ΔV0 Bias initial imbalance OP Shift during evaluate Layout symmetry / guard Reset timing / strength Clock routing / shield PDN decap / return Treat offset as “anything that creates ΔV0 bias or shifts the operating point during evaluate” and fix the dominant path first.

Noise & input-referred uncertainty (why jitter shows up as voltage error)

For a regenerative latch, noise is best understood as decision uncertainty: even with the same input condition, the effective switching threshold spreads around an ideal value. This spread can be expressed as an input-referred uncertainty (σV,in). When overdrive approaches that uncertainty band, both error rate and delay tails rise rapidly.

Noise sources (where they enter in a StrongARM latch)
  • kT/C at reset: thermal noise sets a baseline differential at the start of evaluate.
  • Device noise in evaluate: input pair and regeneration devices inject random perturbations during the most sensitive window.
  • Regeneration randomness: with very small initial imbalance, random perturbations can determine the winner.
  • Supply coupling: PDN ripple and ground motion modulate the internal operating point and appear as threshold spread.
Input-referred view (what the system should budget)
  • σV,in defines an uncertainty band around the ideal threshold.
  • If the minimum expected overdrive is not comfortably larger than σV,in, worst-case latency and wrong decisions increase.
  • Voltage uncertainty becomes timing uncertainty when the input slope is finite (edge pickoff and TDC-style uses).
Minimal uncertainty budget fields (portable across SAR and TDC)
  • σV,in: input-referred threshold spread under the operating clock and load.
  • dominant_window: which part of evaluate is most sensitive (early evaluate is often critical).
  • PSU coupling note: qualitative sensitivity to supply ripple/ground motion during evaluate.
  • mapping: SAR (code noise/spurs) or TDC (time jitter) as the primary risk indicator.
Threshold spread: noise mapped to input-referred uncertainty (sigma V in) Diagram showing an ideal threshold line and a histogram-like spread representing noise, with sigma V in annotation and mapping to SAR code noise and TDC time jitter. Threshold Spread V Vth_ideal σV,in SAR Mapping Code Noise TDC / Pickoff Time Jitter Noise creates a threshold distribution; budget σV,in and ensure minimum overdrive stays well above that uncertainty band.

Input common-mode, headroom, and near-rail behavior

A StrongARM latch is clocked and dynamic, but it is still an analog front-end during the decision window. The input common-mode (VICM) and supply headroom determine whether the input pair and regeneration core stay in a region that provides enough gm, enough VDS, and enough regen strength. Near the rails, both speed and offset typically degrade, and worst-case delay tails expand.

What VICM changes inside the latch (engineering view)
  • Input-pair gm: VICM shifts VGS headroom; weak inversion or linear-region operation reduces gm and slows regeneration.
  • Device VDS headroom: limited VDS in low-VDD corners reduces effective gain and increases sensitivity to mismatch and injection.
  • Regen core strength: when VDD is low, the cross-coupled pair has less overdrive and the decision tail worsens at small input overdrive.
Low-VDD traps that show up only after bring-up
  • “Works but slow”: the latch still flips, but t_pd grows sharply in corners because gm collapses near the rails.
  • “Works but biased”: near-rail operation magnifies clock/reset injection, creating apparent offset drift versus duty and edge rate.
  • “Does not start”: regeneration is too weak at VDD_min and the output never reaches a valid digital level in time.
Minimal VICM operating-window fields (portable across designs)
  • VICM_min @ VDD_min, T_max and VICM_max @ VDD_min, T_max.
  • t_pd @ VICM corners: mid-VICM and near-rail points under minimum expected overdrive.
  • offset sensitivity vs VICM: whether bias grows rapidly near either rail.
  • fail signature: no-flip, slow-tail, or biased decisions.
Operating region map: VICM versus VDD for a StrongARM latch Region map showing OK, marginal, and no-go areas as VICM approaches supply rails and as VDD decreases, with simple labels for gm drop and weak regeneration. VICM → (Low … Mid … High) VDD VDD_nom VDD_min OK region stable speed / offset Marginal near-rail Marginal near-rail No-go at VDD_min corners gm drop weak regen window shrinks Verify VICM_min/max at VDD_min and near-rail corners; tails and offset sensitivity often expand rapidly near the rails.

Kickback & input disturbance (the #1 SAR killer)

Kickback is the input-side disturbance caused by large internal node swings during evaluate and regeneration. In a StrongARM latch, fast output transitions and switch injection can couple charge back to the input nodes. In SAR systems, that disturbance can corrupt sampling, create code-dependent error, and generate spurs even when the latch delay looks fine.

The three dominant kickback paths
  • Capacitive coupling: internal regen/output node swings couple through Cgd/Cin back to VINP/VINN.
  • Switch injection: reset/isolation devices inject unequal charge, creating a differential glitch.
  • CM → DM conversion: common-mode input motion converts to differential error due to imperfect symmetry.
SAR consequences (how kickback looks in measurements)
  • Sampling corruption: the held voltage shifts during the compare window.
  • Code-dependent error: the disturbance depends on internal state and decision history, producing deterministic spurs.
  • R_source sensitivity: higher source impedance increases glitch amplitude and settling time, worsening SFDR/ENOB.
Mitigation ladder (choose the first level that meets timing and spur targets)
  • R / RC at input: simplest damping; costs settling time and may raise noise.
  • Isolation / sampling network: add isolation switch or adjust C; costs kT/C and complexity.
  • Preamp-latch: isolates kickback at the cost of power and area.
  • Shield / bootstrapped: strongest suppression but highest design and verification burden.
Quick kickback diagnosis (three-step)
  1. Hold the input at a stiff level and toggle only the comparator clock; look for a clock-synchronous input glitch.
  2. Change source impedance (or add a small series R); verify whether spur/instability scales with R_source.
  3. Shift the evaluate timing relative to sampling; confirm whether the problem moves with the decision window.
Kickback paths in a StrongARM latch and mitigation blocks Block diagram showing input network, StrongARM internal blocks, three coupling arrows returning to the input, and a mitigation ladder on the right. Input Network R_source C_sample VINP / VINN StrongARM Input Pair Regen Core Reset / Precharge OUTP / OUTN Mitigation R / RC Isolation Preamp Shield C-coupling Injection CM → DM StrongARM internal swings can couple back to VIN; mitigate with the first ladder level that meets settling and spur targets.

Clocking, reset quality, and metastability control

A StrongARM latch is only as repeatable as its decision start condition. Clock edge shape, duty cycle, and reset release define the t0 of evaluation. If t0 varies or reset leaves memory, offset and delay distribution widen, and small-overdrive conditions develop a long metastability tail. The fix is not “a faster latch” but a controlled clock/reset profile and a defined sampling instant with guardband.

Clock edge and duty: what they change (practical view)
  • Edge rate: changes feedthrough and the consistency of evaluate release; asymmetry can look like effective offset.
  • Clock swing: changes injection strength and internal node kick; sensitivity often increases near rails and low VDD.
  • Duty cycle: changes effective reset time and reset–evaluate overlap, which can reintroduce memory and correlated spurs.
Reset quality: eliminate memory without creating new bias
  • Complete: residual charge must collapse so the next decision is not history-dependent.
  • Symmetric: reset and precharge should not inject unequal charge that becomes ΔV0 bias.
  • Isolated: reset activity should not disturb the input network or PDN during the compare window.
Metastability tail: why “small overdrive” needs a sampling guardband
  • With small initial imbalance, regeneration needs more time to separate the nodes; decision-time becomes a distribution with a long tail.
  • A fixed capture delay can be unsafe; the sampling instant must be placed beyond the tail onset with explicit guardband.
  • Downstream SR latches or flip-flops must meet setup/hold with the comparator output already in a valid digital region.
Minimal clock/reset + metastability fields (portable)
  • clk_swing, edge_rate_class, duty_range_supported.
  • t_reset_min (condition that removes memory) and history_dependency (yes/no + notes).
  • sampling_instant (relative to evaluate start) and guardband_margin (tail-aware margin).
Metastability tail: decision-time distribution and sampling instant Histogram-like distribution of decision time with a long tail under small overdrive, and a vertical sampling instant line with guardband indication. Decision Time Distribution decision time → small overdrive sampling instant risk safe guardband Place the capture point beyond the long tail under small overdrive; qualify reset and clock edge to stabilize the decision start.

Integration recipes: SAR ADC & TDC (only the comparator interface)

These recipes focus on the comparator interface only: which nodes must be stable, which phases must not overlap, and which budgets must be checked so that StrongARM decisions remain deterministic. The goal is reliable integration without expanding into SAR or TDC architecture details.

SAR ADC interface (comparator-only checklist)
  • Node ownership: the comparator sees the CDAC top-plate behavior during switching; compare only after the node is settled.
  • Phase separation: ensure switching transients do not overlap the evaluate window (non-overlap is a requirement, not an optimization).
  • Kickback isolation: select the lightest mitigation (R/RC → isolation → preamp) that meets SFDR and settling targets.
  • Decision-time budget: include worst-case small-overdrive bits and a tail-aware capture margin from the downstream latch/FF.
TDC / arbiter interface (comparator-only checklist)
  • Path symmetry: edge A and edge B must see matched routing, buffering, and loading; mismatch becomes time offset.
  • Async handling: define how the arbiter result enters the clock domain (metastability must be contained, not ignored).
  • Tail-aware capture: small effective overdrive and slow input slopes increase tail risk; sampling windows must include guardband.
Minimal interface fields (record once, reuse)
  • compare_window, settling_margin, kickback_mitigation_level (SAR).
  • path_skew_budget, input_slope_class, sync_strategy_note (TDC).
  • capture_point and guardband (tail-aware for both).
Integration mini-blocks: SAR loop and TDC arbiter using a StrongARM latch Two side-by-side block diagrams. Left: SAR loop with CDAC, StrongARM and SAR logic with sampling and compare phases. Right: TDC arbiter with edge inputs, StrongARM, and thermometer/encoder with symmetry and sync blocks. SAR Interface CDAC Top-Plate Node StrongARM SAR Logic φ_sample φ_compare R / Iso TDC / Arbiter Edge A Edge B StrongARM Thermo / Enc match paths Sync Define non-overlap phases and tail-aware capture for SAR; match paths and contain metastability for TDC/arbiter interfaces.

Engineering checklist & verification tests (bring-up playbook)

This playbook closes the loop from simulation to layout to bench correlation and production guardband. The intent is repeatability: the same fields used to sign off PVT/Monte-Carlo must also be measurable on the bench, so failures can be localized to offset / delay tail / kickback / clock-reset injection / PDN bounce.

Simulation sign-off (PVT + mismatch Monte-Carlo)
  • Offset: run PVT and mismatch MC; record mean/σ and any tail behavior under near-rail VICM and VDD_min.
  • tpd(OD): sweep overdrive in 3 bins (small / medium / large); include worst-case corners and duty/edge-rate bins.
  • Metastability tail flag: under small overdrive, check if decision-time distribution develops a long tail; plan capture guardband accordingly.
  • Kickback estimate: extract input-referred disturbance (symmetry and scaling with input capacitance/source impedance).
Layout review (strongarm-specific)
  • Symmetry & matching: mirror the input pair, cross-coupled core, and reset devices; keep parasitic imbalance minimal.
  • Shield & separation: keep CLK and large-swing OUT nodes away from VIN nodes; use shielding routes where coupling is unavoidable.
  • Clock routing consistency: matched path length and loading for clock/reset distribution to stabilize the evaluate start condition.
  • Ground-bounce control: short return loops and local decoupling to reduce input-referred offset caused by transient current spikes.
Bench verification hooks (fast localization)
  • tpd vs OD: measure delay distribution (p50/p99) at small/medium/large OD; record tail presence and capture recommendation.
  • Kickback: hold VIN with a stiff source and toggle only CLK; measure input glitch peak and symmetry; repeat with R_source bins.
  • Metastability tail: force very small OD and capture a histogram-like delay distribution; place sampling instant beyond the tail with guardband.
  • Reset memory: sweep reset width/duty; check for history dependence (bias or spur moves with duty/edge).
Production-facing minimum set (guardband and correlation)
  • Corner guardband: base capture timing on p99 + margin at worst-case small OD and VDD_min/T_max.
  • Temperature drift note: track whether offset/tail/kickback worsen at hot/cold extremes.
  • Supply-noise sensitivity: record whether ripple or ground bounce shifts decision behavior or increases tail risk.
  • Minimal bins: lot, VDD bin, temperature point, t_pd bin, tail flag, kickback flag.
Verification flow for StrongARM latch: simulation to guardband with correlation loops Flowchart showing Sim, Layout, Bench, Correlation, and Guardband blocks with feedback arrows from Bench to Layout and from Correlation to Sim. Sim PVT MC Layout match shield Bench t_pd kickback Correlation align model GB p99 bins bring-up feedback correlation closes loop Use the same fields across Sim, Bench, and Production so failures map to offset, tail risk, kickback, or injection paths.

Applications (where StrongARM is the right hammer)

These application recipes focus on StrongARM-specific advantages and failure modes. Each recipe is structured as key specs → risk points → structure suggestions, so integration decisions stay actionable instead of becoming a generic use-case list.

SAR ADC comparator
Key specs
  • Energy per decision and repeatable evaluate start.
  • tpd at small overdrive (tail-aware capture margin).
  • Kickback amplitude and symmetry seen by the CDAC/top-plate node.
  • VICM window and near-rail sensitivity at VDD_min/T_max.
Risk points
  • Kickback corrupts sampling and creates code-dependent spurs.
  • Compare phase overlaps switching transient (insufficient non-overlap).
  • Small-OD tail causes intermittent wrong decisions when capture is too early.
Structure suggestions
  • Light: non-overlap phases + small R/RC damping if settling margin exists.
  • Medium: isolation switch / adjusted sampling network to limit kickback into the top-plate.
  • Heavy: preamp-latch interface when R_source is high or spur targets are strict.
ToF / echo pick-off (time decision)
Key specs
  • Input slope tolerance and threshold uncertainty (tail risk under slow edges).
  • Clock/reset consistency to stabilize the evaluate start.
  • Supply/ground transient sensitivity (false trigger risk).
Risk points
  • Slow-ramp inputs amplify metastability tail and increase timing jitter.
  • Clock feedthrough shifts effective threshold or creates correlated timing bias.
  • PDN bounce injects input-referred error during the pick-off instant.
Structure suggestions
  • Light: define a clean sampling window; ensure stable reset and non-overlap gating.
  • Medium: symmetric routing/loading and explicit guardband beyond the tail onset.
  • Heavy: add a conditioning stage (preamp/limiter) when slope and noise vary widely.
TDC arbiter (arrival-time difference)
Key specs
  • Path symmetry budget (routing, buffers, loads).
  • Tail-aware capture for near-simultaneous arrivals.
  • Defined synchronization strategy into the clock domain.
Risk points
  • A/B mismatch turns into systematic time offset (bias) rather than random noise.
  • Async boundary expands metastability beyond the arbiter if not contained.
  • Thermometer/encoding becomes unstable when capture is placed inside the tail region.
Structure suggestions
  • Light: enforce strict path matching and identical loading.
  • Medium: add capture guardband and a defined sync chain for the arbiter result.
  • Heavy: redundant sampling/arbiter hardening when tail risk must be minimized.
Low-VDD fast threshold detect (dynamic energy advantage)
Key specs
  • VDD_min operating window and near-rail behavior.
  • Reset robustness (memory removal) under corners.
  • Offset and tail sensitivity versus VDD and temperature.
Risk points
  • Regen becomes weak at VDD_min; decision tails expand and valid-level timing slips.
  • Near-rail inputs increase bias sensitivity to injection and asymmetry.
  • Incomplete reset creates history dependence (apparent drift) across operating modes.
Structure suggestions
  • Light: keep thresholds away from rails and qualify reset width across VDD/T corners.
  • Medium: stabilize the threshold source (buffer/divider strategy) and reduce injection coupling.
  • Heavy: add a front-end stage when near-rail operation is unavoidable and tail risk must be bounded.
Application recipe cards for StrongARM latch integration A 2×2 grid of mini block diagrams: SAR, ToF pick-off, TDC arbiter, and low-VDD detect. Each card shows key blocks, arrows, and a single key risk tag. SAR CDAC StrongARM Logic Kickback ToF Pick-off Echo In StrongARM Time Tag Tail TDC Arbiter Edge A Edge B StrongARM Match Low-VDD Detect Threshold StrongARM Valid Near-rail Each card highlights a StrongARM-specific risk: kickback, tail risk, path match, and near-rail sensitivity.

IC selection logic (what to ask vendors / what to measure)

StrongARM-style regenerative latches are often internal building blocks (SAR ADC / TDC / ToF). When selecting external comparators for prototypes, evaluation boards, or interface verification, the selection must be driven by sampled decision timing, small-overdrive tail risk, and input disturbance (kickback). This section provides a practical decision flow, a vendor RFQ checklist, a bench verification plan, and a short list of concrete part numbers to start evaluation.

Step 0 — decide “buy comparator” vs “build StrongARM latch”
Choose an external comparator when:
  • A PCB prototype needs fast thresholding or timing pick-off without a custom silicon latch.
  • The goal is interface verification (output logic levels, capture window, latency budget) rather than minimum energy/decision.
  • Power/area is secondary to repeatability and time-to-measurement.
Consider a StrongARM-like custom latch when:
  • Energy per decision and clocked evaluation are first-order constraints (SAR/TDC at high rate).
  • The system operates frequently in small overdrive and tail behavior must be shaped by design.
  • Kickback and input disturbance must be minimized beyond what discrete comparators can guarantee.
What to ask vendors (RFQ checklist that prevents surprises)
Request data in a form that can be validated on the bench. Typical-only numbers are insufficient for latch-like use cases.
  • tpd vs Overdrive curve (at least small/medium/large OD) with conditions: VDD, VICM, temperature, output load, and input source impedance assumptions.
  • Delay dispersion / tail hints: any p99/p999 data, or guidance for safe sampling instant under small OD / slow slopes.
  • Latch / LE timing (if present): setup/hold to LE/CLK, recovery time, and whether output is transparent vs sampled.
  • Input loading & coupling: Cin (single-ended/differential), bias currents, and any notes on input kickback/disturbance.
  • VICR / near-rail behavior: guaranteed operating region across VDD_min/T corners; identify crossover and degraded regions.
  • Output type & levels: open-drain vs push-pull vs LVDS/CML/PECL, valid-level timing, and required termination.
  • Power/disable behavior: shutdown entry/exit time and whether re-enable creates memory-like behavior.
What to measure (bench plan: 3 must-tests + 2 add-ons)
Must-test #1 — tpd distribution vs overdrive (tail-aware)
  • Sweep OD in bins: small (worst-case), medium, large; collect delay distribution (p50 / p99).
  • Pass rule: capture point must be placed beyond p99 with explicit guardband at VDD_min/T_hot.
Must-test #2 — kickback / input disturbance (SAR killer)
  • Hold VIN at a stiff source; toggle only CLK/LE; measure input glitch peak (ΔV) and symmetry.
  • Repeat with R_source bins; if ΔV scales strongly with R_source, mitigation is mandatory (R/RC, isolation, or preamp).
Must-test #3 — reset/LE memory (history dependence)
  • Sweep reset width / duty / LE timing; check whether output bias depends on previous decision (memory).
  • Fail signature: repeatable bias shift or correlated spur that moves with duty/edge-rate bins.
Add-ons (high ROI for ruggedness)
  • VICM×VDD map: validate near-rail and VDD_min operation regions on real boards.
  • Supply sensitivity: inject controlled ripple; observe whether tail/kickback signatures worsen.
Risk → spec mapping (select by failure mode, not by marketing)
SAR: kickback → Cin / input structure / isolation option → bench ΔV_kb vs R_source.
TDC arbiter: tail risk → t_pd(OD) + dispersion → small-OD delay histogram and guardband.
ToF pick-off: threshold uncertainty → jitter/uncertainty notes + slope tolerance → false-trigger and time-tag spread.
Low-VDD detect: near-rail failure → VICR/VDD_min behavior → VICM×VDD working map under corners.
Concrete part numbers (starter shortlist for evaluation)

The list below is intentionally short and bucketed. Exact latch/LE options, output interfaces, and speed grades vary by device and suffix; verify the final choice against datasheet timing tables and interface requirements.

Bucket A — ultra-high-speed comparators (timing pick-off / high-rate evaluation)
  • ADCMP580 / ADCMP581 / ADCMP582 (Analog Devices) — high-speed timing chains; evaluate tail risk and capture window.
  • ADCMP572 / ADCMP573 (Analog Devices) — high-speed family; evaluate interface and small-OD behavior.
Bucket B — high-speed comparators with latch/enable-friendly operation (sampled decision workflows)
  • LMH7322 (Texas Instruments) — commonly used where latch-enable style capture is required; validate LE timing and recovery.
  • LTC6752 (Analog Devices) — family often used for fast thresholding; validate output type and capture assumptions.
  • LTC6754 (Analog Devices) — higher-speed family; validate output interface (LVDS/CML variants) and termination needs.
Bucket C — low-voltage fast threshold detect (logic-friendly, VDD-focused)
  • TLV3501 (Texas Instruments) — low-voltage, fast push-pull comparator; validate near-rail behavior and supply sensitivity.
  • LMV7219 (Texas Instruments) — low-voltage comparator option for edge shaping; validate tail behavior if used for sampled decisions.
Bucket D — high-voltage domain thresholding (protection-side, interface-first)
  • TLV1805 (Texas Instruments) — higher input-voltage monitoring family; validate input protection and output interfacing.
  • LMV7239 (Texas Instruments) — option for robust thresholding; validate input common-mode and output type for the target domain.
Minimal logging fields (copy into lab notes)
part_number:
output_type:
vdd_bin:
temp_point:
vicm_point:
od_bin: [small|med|large]
tpd_p50_ns:
tpd_p99_ns:
tail_flag: [0|1]
kickback_dv_pk_mV:
kickback_symmetry_note:
reset_memory_flag: [0|1]
capture_instant_ns:
guardband_ns:
        
Selection flow: ask, measure, decide for StrongARM-like use cases Block flow from Use case to Must-have checks to Vendor RFQ to Bench tests to Decision/guardband, with two branching hints for tail risk and kickback risk. Use case SAR / TDC ToF / VDD Must-have LE / levels VICM / VDD Ask vendor t_pd(OD) Cin / VICR Bench tests tail check kickback Dec pass GB small OD → tail risk → capture guardband SAR → kickback dominates Selection is validated by tail-aware timing and kickback measurements, then locked with production guardband fields.

Request a Quote

Accepted Formats

pdf, csv, xls, xlsx, zip

Attachment

Drag & drop files here or use the button below.

FAQs (StrongARM / Regenerative latch)

These FAQs close long-tail questions strictly within the StrongARM/regenerative latch boundary: clock/reset quality, decision-time tail, offset/memory, kickback, VICM/headroom, and when a preamp-latch becomes necessary. Each answer includes quick actions and logging fields.

Why does the offset change with clock duty cycle or frequency?
Short answer: Duty/frequency changes alter the reset/evaluate initial conditions and clock injection, so the latch starts each decision from a different “zero,” shifting the apparent input-referred offset.
Likely causes (top 3)
  • Reset not fully clearing nodes → memory becomes duty-dependent.
  • Clock feedthrough / charge injection asymmetry changes with edge rate and duty.
  • Supply/ground bounce increases with toggle rate → input-referred bias shifts.
Do this next (with thresholds)
  • Duty sweep: test 40% / 50% / 60% and log offset shift. Flag if offset changes by > 3× the typical noise sigma.
  • Reset-width sweep: increase reset width until offset stops moving. Pass when further reset increase changes offset by < 10% of the previous step.
  • Edge-rate check: reduce CLK drive strength (slower edge). Flag if offset shift scales strongly with edge rate.
Log fields
f_clk, duty, edge_rate_bin, reset_width, VICM, VDD, temp, offset_estimate, noise_sigma, memory_flag
How much overdrive is needed to guarantee a bounded decision time?
Short answer: “Bounded” means the delay distribution meets the capture budget at corners: choose the minimum overdrive such that p99(tpd) + guardband ≤ capture_budget at VDDmin/Thot.
Likely causes of underestimating OD
  • Using typical tpd instead of p99 / tail-aware metrics.
  • Ignoring corners (VDDmin, Thot) where regeneration slows.
  • Counting on ideal reset while real reset leaves residual ΔV.
Do this next (with thresholds)
  • Measure p50/p99: collect ≥ 1k samples for each OD bin (small/med/large). Pass if p99 meets the capture budget with margin.
  • Corner repeat: repeat the smallest OD bin at VDDmin/Thot. Fail if p99 grows > 2× vs nominal or tail emerges.
  • Set guardband: choose guardband ≥ (p99 − p50) at worst corner, then add integration margin for downstream sampling.
Log fields
OD_bin, N_samples, tpd_p50, tpd_p99, capture_budget, guardband, VDD, temp, VICM, tail_flag
What causes “memory” between decisions and how to eliminate it?
Short answer: Memory occurs when internal nodes do not return to a deterministic reset state; residual charge and asymmetric injection bias the next decision. Fix it by enforcing a clean reset and symmetric discharge paths.
Likely causes (top 3)
  • Reset window too short for node RC constants.
  • Unequal reset device strength/parasitics (left vs right).
  • Clock/reset overlap or feedthrough leaving one side pre-biased.
Do this next (with thresholds)
  • AB pattern test: alternate +OD and −OD; compute Δoffset between AB vs BA sequences. Flag if Δoffset > 2× noise sigma.
  • Reset sweep: increase reset width until Δoffset collapses. Pass when Δoffset drops by ≥ 70% from baseline.
  • Non-overlap check: enforce non-overlap between reset and evaluate. Fail if overlap causes polarity-dependent bias.
Log fields
pattern_type, OD_level, reset_width, nonoverlap_ns, memory_metric, VDD, temp, edge_rate_bin
How to tell kickback is the dominant error in a SAR loop?
Short answer: Kickback dominates when an input glitch synchronous to compare events scales with source impedance and produces code-correlated artifacts (spurs / repeatable wrong decisions). Confirm by isolating the compare clock and measuring ΔV at the CDAC/top-plate node.
Likely kickback signatures
  • Input node glitch aligned to the compare edge/phase.
  • Error worsens with higher source impedance or longer trace.
  • Code-dependent spurs or repeatable error patterns near decision boundaries.
Do this next (with thresholds)
  • Clock-only toggle: hold VIN constant; toggle only compare clock/phase. Flag if ΔV_in_glitch is clearly measurable and repeatable.
  • Rsource sweep: increase Rsource by 5×–10×. Flag if ΔV_in_glitch increases > 2×.
  • Mitigation A/B test: add small series R or RC damping. Pass if artifact/spur reduces by ≥ 6 dB without violating timing budget.
Log fields
compare_phase, ΔV_in_glitch_pk, R_source, RC_damping, spur_delta_dB, tpd_budget_ok, VDD, VICM
Why does it work in sim but fail at low VDD / high temp?
Short answer: Corners reduce transconductance and headroom, slowing regeneration and amplifying reset imperfections. The result is larger delay tails, more memory, and degraded VICM/near-rail behavior.
Most common corner failures (StrongARM-specific)
  • Regeneration slows → p99(tpd) blows up under small OD.
  • Reset becomes incomplete → memory-induced offset appears.
  • Input pair/core loses headroom → VICM region shrinks near rails.
Do this next (with thresholds)
  • Repeat small-OD delay distribution at corners: VDDmin/Thot. Fail if p99 exceeds capture_budget or tail_flag toggles from 0→1.
  • Reset stress test: shorten reset by 20% steps. Flag if offset/memory grows abruptly (reset margin too small).
  • VICM scan: test 3 points (low/mid/high). Fail if one region shows persistent wrong polarity or unstable output.
Log fields
VDD, temp, VICM_point, OD_bin, tpd_p50, tpd_p99, capture_budget, tail_flag, memory_metric
How to measure metastability tail on the bench quickly?
Short answer: Force very small overdrive (or slow input slope) and record decision delay many times. A long tail shows up as a small number of very late decisions; the sampling instant must be placed beyond p99 plus margin.
What makes tails show up
  • Near-zero OD decisions (input close to threshold).
  • Slow ramps (small dV/dt) effectively reduce OD at the sampling instant.
  • Weak regeneration at corners (VDDmin/Thot).
Do this next (with thresholds)
  • Tail setup: set OD to the smallest repeatable value and collect ≥ 2k delay samples.
  • Tail metric: compute p99 and p999 if possible. Flag tail if (p99 − p50) is > 5× larger than in the medium-OD bin.
  • Sampling instant: set sampling ≥ p99 + margin. Fail if errors persist when sampling is moved beyond p99.
Log fields
OD_small, slope_bin, N_samples, tpd_p50, tpd_p99, tpd_p999, sampling_instant, VDD, temp, tail_flag
When is a preamp-latch mandatory vs optional?
Short answer: A preamp-latch becomes mandatory when kickback or tail risk cannot be bounded within the capture and spur budgets. It is optional when small damping/isolation fixes kickback and p99 delay stays within margin at corners.
Mandatory triggers (any one is enough)
  • Kickback causes measurable input corruption that scales with Rsource and creates spurs.
  • Small-OD p99 delay exceeds capture_budget at VDDmin/Thot (tail risk).
  • Near-rail/VDD constraints leave insufficient regeneration headroom.
Do this next (with thresholds)
  • Try light mitigation first: add small series R / RC or isolation switch. Pass if spur reduces ≥ 6 dB and timing margin remains.
  • Tail decision: if p99(tpd) still violates capture_budget at corners, choose preamp-latch.
  • Kickback decision: if ΔV_kb_pk remains large and code-correlated after damping, choose preamp-latch.
Log fields
ΔV_kb_pk, spur_delta_dB, OD_bin, tpd_p99, capture_budget, VDD, temp, mitigation_used, preamp_needed_flag
What layout asymmetry most often creates systematic offset?
Short answer: The most common systematic offset comes from left/right asymmetry in the input pair, cross-coupled core, and reset/clock coupling. Any unequal parasitic loading or injection maps to a repeatable input-referred bias.
Top asymmetries to audit (StrongARM-specific)
  • Input devices not mirrored (device orientation, well proximity, routing parasitics).
  • Reset devices and discharge paths unequal (effective R/C differs).
  • CLK routed closer to one input/output node (unequal capacitive injection).
Do this next (with thresholds)
  • Mirror check: enforce strict L/R mirroring for devices and routes. Flag if any unmatched jog/length exists near sensitive nodes.
  • Parasitic delta check: compare extracted C/R. Flag if ΔC or ΔR is > 5% on critical nodes (inputs, outputs, reset paths).
  • Clock coupling check: relocate/guard CLK routes. Pass if duty-dependent offset reduces materially after the change.
Log fields
symmetry_pass, ΔC_critical_pct, ΔR_critical_pct, clk_route_match, offset_before, offset_after, duty_sensitivity
Can RC at the input fix chatter without breaking speed?
Short answer: Input RC can reduce chatter by filtering noise and slowing crossings, but it also reduces effective overdrive at the sampling instant and can increase delay tails. Use RC only if p99 timing and tail risk remain bounded.
Common trade-offs
  • RC reduces high-frequency noise but increases crossing time uncertainty under sampled evaluation.
  • RC plus source impedance can enlarge kickback-induced droop recovery time.
  • Over-filtering increases small-OD exposure → tail risk grows.
Do this next (with thresholds)
  • A/B timing check: measure p99(tpd) before/after RC. Fail if p99 increases > 30% or violates capture_budget.
  • Tail check: repeat the smallest OD bin. Fail if tail_flag changes 0→1 after adding RC.
  • Chatter metric: count multi-toggles per crossing. Pass if toggles reduce ≥ 80% without timing failure.
Log fields
R_in, C_in, tpd_p99_before, tpd_p99_after, tail_flag, capture_budget, chatter_count_before, chatter_count_after
What is the quickest way to sanity-check VICM compatibility?
Short answer: Test three VICM points (low/mid/high) at VDDmin/Thot using a small and medium OD. If any region shows unstable polarity, exploding p99 delay, or persistent mis-decisions, VICM compatibility is not guaranteed.
Why VICM fails in practice
  • Headroom loss pushes devices out of their intended operating region.
  • Near-rail behavior amplifies offset and slows regeneration.
  • Reset/evaluate injection becomes more asymmetric at extreme VICM.
Do this next (with thresholds)
  • 3-point VICM scan: low/mid/high VICM. Fail if any point shows wrong polarity over repeated trials.
  • Timing sanity: measure p99(tpd) at each VICM point. Fail if p99 grows > 2× relative to the mid-VICM point or violates capture_budget.
  • Corner confirmation: repeat at VDDmin/Thot. Pass only if the same VICM region remains stable.
Log fields
VICM_low, VICM_mid, VICM_high, VDD, temp, OD_bin, polarity_fail_flag, tpd_p99_by_vicm, capture_budget