7.2.1. Traditional Simulation

In traditional simulation-based verification, a testbench is created to apply a set of inputs to the design and check the outputs for correctness. Simulations are typically run for a fixed number of cycles or until specific corner cases are hit.

Traditional simulation-based verification involves creating a testbench, which is a specific environment where you can feed inputs into the design you are testing. The testbench's role is to then collect the outputs generated by the design in response to those inputs. The main goal is to ensure that the output behaves correctly as specified in the design documentation. Typically, the simulation is run for a defined number of cycles, or it continues until it runs into particular situations known as corner cases, which are unusual scenarios that could potentially cause errors.

Think of traditional simulation like conducting a series of experiments in a laboratory. You have a set of controlled conditions (inputs) and you observe the results (outputs). Just like a scientist who performs experiments and notes the results, engineers run simulations to check if their design behaves as it should.

● Pros: ○ Easy to set up and run. ○ Supports testing with a wide variety of test vectors and scenarios.

One of the main advantages of traditional simulation is that it is relatively straightforward to set up and execute. Engineers can quickly create a testbench and start running tests without needing extensive mathematical knowledge. Additionally, traditional simulation allows for testing against a vast range of input scenarios, which means engineers can explore different behaviors of the design by varying the inputs and observing how the system reacts in various situations.

Imagine trying out a recipe in cooking. It's easy to gather the ingredients (set up the testbench) and follow the instructions (run the tests). You can also try out different combinations and modifications (test vectors) to see how they affect the final dish, similar to how simulations allow for different scenarios to be tested.

● Cons: ○ Limited by the number of test cases defined. ○ Does not guarantee exhaustiveness—corner cases and bugs might be missed. ○ Can be time-consuming to run a large number of simulations.

While traditional simulation has its merits, it comes with notable downsides. One major limitation is that it is constrained by the number of test cases an engineer can define; if a bug occurs in an untested scenario, it will remain unnoticed. Furthermore, because simulations only check a subset of possible input combinations, it cannot guarantee the complete correctness of a design. As complexity increases, running numerous simulations can become very time-consuming, which can delay the overall project timeline.

Consider taking a pop quiz where you can only study a limited number of questions. If none of the questions you studied appear, you won't do well on the quiz. Similarly, limited test cases in simulation can lead to missing critical errors that only arise under certain conditions.

--