Question

Use vpi_register_cb(), setting the cb_rtn element to the function to be invoked and the reason element of the s_cb_data structure to one of the following values, to place an assertion system callback.

cbAssertionSysInitialized
occurs after the system has initialized. No assertion-specific actions can be performed until this callback
completes. The assertion system can initialize before cbStartOfSimulation does or afterwards.

cbAssertionSysStart
the assertion system has become active and starts processing assertion attempts. This always occur after
cbAssertionSysInitialized. By default, the assertion system is “started” on simulation startup, but
the user can delay this by using assertion system control actions.

cbAssertionSysStop
the assertion system has been temporarily suspended. While stopped no assertion attempts are processed
and no assertion-related callbacks occur. The assertion system can be stopped and resumed an arbitrary
number of times during a single simulation run.

cbAssertionSysEnd
occurs when all assertions have completed and no new attempts shall start. Once this callback occurs no
more assertion-related callbacks shall occur and assertion-related actions shall have no further effect. This
typically occurs after the end of simulation.

cbAssertionSysReset
occurs when the assertion system is reset, e.g., due to a system control action.

The callback routine invoked follows the normal VPI callback prototype and is passed an s_cb_data containing the callback reason and any user data provided to the vpi_register_cb() call.