Analog for Digital Engineers · All levels

DACs (Digital-to-Analog)

Core digital-to-analog conversion principles, practical DAC architecture tradeoffs, static and dynamic linearity metrics, and reconstruction filtering needed for mixed-signal system design.

Section goal

Core digital-to-analog conversion principles, practical DAC architecture tradeoffs, static and dynamic linearity metrics, and reconstruction filtering needed for mixed-signal system design.

How to study this section

  1. Start with each topic hub and restate the mechanism in your own words.

  2. Use reports and debug pages to classify first failing boundaries.

  3. Practice worked examples and interview drills under fixed setup metadata.

  4. Close with checklist and execution impact before signoff claims.

Topics

  1. dac-fundamentals/ - DAC Fundamentals: Codes, Full-Scale Range, and Quantization Behavior

  2. dac-architectures/ - DAC Architectures: R-2R, Current-Steering, and Charge-Redistribution

  3. dac-static-and-dynamic-metrics/ - Static and Dynamic DAC Metrics: INL/DNL, Glitch, and SFDR

  4. reconstruction-and-filtering/ - Reconstruction and Filtering: Zero-Order Hold, Images, and Analog Smoothing

Related topics

Analog deep dive

DAC closure needs both static transfer quality and dynamic glitch/spectral discipline.

Concept diagram

diagram
DAC OUTPUT CHAIN

code mapping -> switching network -> output path -> reconstruction filter

Metric graph

diagram
DAC RISK MIX

major-carry glitches     █████
settling residuals       ████
image leakage            ███

Metrics and artifacts to collect

  • INL/DNL sweep package

  • glitch energy and settling trend

  • SFDR/THD versus output frequency

  • reconstruction filter compliance

Mini case study

Good static linearity masked dynamic spur failures driven by switching asymmetry and insufficient reconstruction margin.

Debug branches

  • Tie static transfer plots to dynamic spectral outcomes.

  • Inspect major-carry behavior separately from small-step transitions.

  • Validate output path with realistic load and package parasitics.

Senior review question

Ask: which source-path-victim boundary failed first, and which artifact proves it reproducibly?