functional coverage in verilog

Guest
Hi,
We have a environment in verilog and I have worked on specman but new
to verilog test bench. I have no idea of how to implement functional
coverage in verilog. I want to have a seperate coverage file so that I
dont need to load that file when functional coverage is not required.
It will be great if somebody throws any information.

Thanks
Sid
 
I dont think there is any concept of coverage included in verilog
except by using assertions but you might be able to do it in system
verilog.

siddhartha79.p@gmail.com wrote:
Hi,
We have a environment in verilog and I have worked on specman but new
to verilog test bench. I have no idea of how to implement functional
coverage in verilog. I want to have a seperate coverage file so that I
dont need to load that file when functional coverage is not required.
It will be great if somebody throws any information.

Thanks
Sid
 
siddhartha79.p@gmail.com wrote:
Hi,
We have a environment in verilog and I have worked on specman but new
to verilog test bench. I have no idea of how to implement functional
coverage in verilog. I want to have a seperate coverage file so that I
dont need to load that file when functional coverage is not required.
It will be great if somebody throws any information.

Thanks
Sid
Functional coverage support goes beyond language constructs. There is a
need for simulator to communicate with external database to
store/acess coverage data. Also, there is a need to merge collected
coverage data, explore it in the user-friendly form etc.

Verilog does not provide ready-to use functional coverage constructs,
although it is possible to build parametric OVL-style coverage monitors
for the coverage collection purposes. It is also possible to write
simple PLIs to communicate with external database, but it requires some
development efforts.

EDA vendors provide functional coverage support for Verilog simulation
using PSL and SV. While PSL support is usually given "for free", there
is a need to pay extra $$$ for SV support. The good news are that there
is built-in tool support for functional coverage collection, merging,
viewing etc. while the bad news is that this process is not
straightforward (at least in my experience).

Regards,
-Alex
 

Welcome to EDABoard.com

Sponsor

Back
Top