August 24, 2010 -- With the advent of a new era in verification technology based on an advanced HVL like SystemVerilog, the concept of random-stimulus-based verification was born to verify today’s multi-million gate designs. In concept, every verification engineer fancies the idea of random-stimuli-driven verification, but as is rightly said – "Everything comes with a cost" and the cost here is a big concern that haunts the life of every verification engineer:

How do I close my verification? When can I say I am done?

To answer such questions, SystemVerilog as a language came up with the concept of functional coverage that is much more accurate of a measure compared to the traditional code coverage techniques. We concentrate mainly on this SV feature, adding one more dimension to it — configurability.

Methodology like OVM has brought in the concept of reusability of environment/ agent (mainly consisting of driver/ monitor/ sequencer) across projects. But, on the other hand, a user tends to create a coverage model that is usually coupled very tightly to the specifications of the given project. In the process, he/she ends up writing a separate coverage model for every project, compromising the reusability aspect and violating the methodology mantra! Keeping the above limitation in view, we would like to present the user with one possible solution – configurable and reusable coverage model, sighting AMBA AXI protocol as the case study for discussion.

Parag Goel and Sakshi Bajaj. (Goel is Senior Design Engineer at AppliedMicro and Bajaj is a Design Engineer II at AppliedMicro.)