Hardware verification is proving that a chip design does what its specification says before it is built. A fabricated chip cannot be patched like software, so verification often takes more effort than the design itself. It combines simulation, formal proofs and emulation on programmable hardware, since no single method is enough.
Key concepts
- Testbench: code that drives a design under test with inputs and checks its outputs.
- Constrained-random stimulus: generating many legal random inputs to reach cases a person would not write.
- Assertions: properties about signals over time that are checked in simulation or proven formally.
- Coverage: functional and code coverage show which behaviours the tests have actually exercised.
- Formal verification: proving properties for all inputs, or showing two designs equivalent.
Vocabulary
- DUT: the design under test.
- Reference model: a simple, trusted model whose outputs are compared with the design's.
- UVM: a standard methodology and class library for building reusable testbenches.
- Corner case: a rare combination of conditions where bugs gather.
What to study, in order
- Digital design and a hardware description language, with a simulator running your own design.
- Write a self-checking testbench for a counter and a small state machine.
- Add random stimulus, a reference model and coverage, and read the coverage holes.
- Write assertions for a bus protocol and check them in simulation and with a formal tool.
- Verify a small processor core against a simple instruction model.