Assertions

You will learn

What an assertion is in code, and what it costs to check one every cycle.

An assertion is a check that stays in the design, every cycle, forever: not a testbench that runs once, but a sentence about the hardware that must hold while the hardware runs. The lesson's spec, formal, writes them as data -- immediate and concurrent, severities, clock and reset named -- because an assertion you cannot enumerate is an assertion you cannot discharge. The widget is the same idea at the door: each dependency the tool needs, present or not, checked in one call before anything runs.

Open the interactive lesson →