Term · Verification & Validation
Waveform
The time-versus-value display of signals recorded from a simulation or emulation run, the primary artefact of hardware debug. Modern viewers also show transactions, assertion results, source and schematic views tied to the same time cursor.
- Also known as
- Waves, Waveform dump
- Type
- Term
- Domain
- Verification & Validation, Debug
Notes
Dumping waves for a whole regression is impractical, so failing tests are normally rerun with the same seed and dumping enabled.
Overview
In chip verification, a waveform is the record of how signals change over time during a simulation or emulation run, displayed as traces in a waveform viewer, and it is the main tool engineers use to debug hardware. Looking at waveforms shows exactly what each signal did on each clock cycle around a failure, which is how most design and testbench bugs are found.
How it works
During a run, the simulator or emulator records value changes on selected signals into a waveform database. The simplest format is the Value Change Dump (VCD), a text format defined in the Verilog and SystemVerilog standards; commercial tools use compact proprietary formats, and open formats such as FST are used with open-source tools. Recording every signal in a large design for a long run produces huge files, so engineers choose which parts of the hierarchy and which time windows to dump.
A waveform viewer shows signals as rows against a time axis, with buses shown as values and transitions marked. Modern debug environments link the waveform to the source code, the schematic and the design hierarchy, so an engineer can click on a strange value and trace back through the logic that drove it. They also show transactions, such as bus reads and writes, as higher-level bars, and mark where assertions fired.
Analogue and mixed-signal simulations produce continuous waveforms of voltage and current, viewed in similar tools with measurements such as rise time, overshoot and frequency. In the lab, oscilloscopes and logic analysers capture waveforms from real silicon, which teams compare with simulation.
Examples
- Tracing a wrong value on a data bus back through a waveform to a state machine in the wrong state.
- A VCD file from an open-source simulator opened in GTKWave.
- Viewing bus transactions alongside signal traces to find which request was dropped.
- An analogue waveform showing a regulator's output overshooting when the load steps.
- Comparing an oscilloscope capture from first silicon with the simulated waveform for the same interface.
Why it matters
Debugging takes a large share of verification time, and waveforms are where most of it happens. Design and verification engineers use them every day, EDA vendors compete on debug tools, and verification infrastructure teams manage the storage they need.
In the chip lifecycle, waveforms are used from the first RTL simulation through verification and emulation, and post-silicon debug compares lab captures with simulated waveforms.
Related terms
Part of the Verification & Validation glossary, with every term in the topic and the lifecycles, tools and standards that use them.
Where it appears on the Hub
Used on 76 pages of the Hub. In each group, the pages that mention it most come first.
Skills
Tools
Suggest an improvement
Suggest an improvement to this entry
A clearer definition, an example, a correction or a source an editor can check. Editors review every suggestion before the entry changes.
Last reviewed . Written by The Semiconductor Hub editorial team. The full glossary