Examples and design pattern for VHDL verification
T. Meissner 8f92c2a446 Add description of osvvm_fsm_psl_coverage example 2 years ago
osvvm_fsm_coverage Fixed assert error by adding reset in assert precondition 2 years ago
osvvm_fsm_psl_coverage Add functional FSM coverage using OSVVM & PSL endpoints 2 years ago
psl_endpoint_eval_in_vhdl Add writing psl endpoint value into VHDL boolean signal 2 years ago
psl_test_endpoint Adapt to new GHDL feature to make endpoints visible in VHDL 2 years ago
LICENSE.md Add LGPL3 license file 2 years ago
README.md Add description of osvvm_fsm_psl_coverage example 2 years ago



Examples and design pattern for VHDL verification. All examples run with GHDL, the open source VHDL simulator. You have to use the latest version of GHDL, as the examples use features which where added to GHDL very recently.


Example to use OSVVMs CoveragePkg package to do FSM state coverage. State changes are used as BINS which are counted in an object of type CovPType. The testbench accesses these state coverage data CoveragePkg procedures. So, the testbench can react to the FSM coverage if necessary. Furthermore the state changes are checked by some PSL assertions.


This is the same as the osvvm_fsm_coverage but instead of using cross coverage of previous and current FSM state it’s using PSL endpoints to cover FSM state changes. There is a PSL endpoint for each state change we want to cover. The endpoints are synched in clock domain and used as simple BINs to do FSM state coverage as in the osvvm_fsm_coverage example. This example shows the power of evaluating PSL endpoints in VHDL, as you can describe complex behaviour over time a lot simpler in PSL than in VHDL.


Example to show a recently feature added to GHDL which allows to evaluate PSL endpoints in VHDL code. It simply defines an PSL endpoint and sets a boolean value dependent on the value of the PSL endpoint.


This example was as test case to check the feature of evaluating PSL endpoints in VHDL, which was recently added to GHDL. See GHDL issue #45 for details.