[sv-ec] RE: [sv-ac] Regarding Coverage features

From: Arturo Salz <Arturo.Salz_at_.....>
Date: Mon Nov 21 2005 - 11:41:50 PST
Saurabh,

 

You can assign null to either a standalone covergroup instance or to a
class containing the covergroup. In either case the covergroup instance
will (eventually) be removed, provided there are no other references to
the instance in the system. It is a good methodology to call the stop()
method before assigning null to the instance. That will guarantee that
instance from collecting coverage at that point.

 

            Arturo

 

________________________________

From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org] On Behalf Of
Eduard Cerny
Sent: Monday, November 21, 2005 9:18 AM
To: Shrimal, Saurabh Kumar; Eduard Cerny; sv-ec@eda.org; sv-ac@eda.org
Subject: RE: [sv-ac] Regarding Coverage features

 

Hi,

 

there are covergroup instance methods called start and stop, Section
18.7.

Also, I suppose that if a cg is in a class, then assigning a null value
to the ionstance variable would effectively remove the cg instance,
Section 7.26.

 

best regards,

ed

 

	 

	
________________________________


	From: Shrimal, Saurabh Kumar
[mailto:saurabh.kumar.shrimal@intel.com] 
	Sent: Monday, November 21, 2005 8:25 AM
	To: Eduard Cerny; sv-ec@eda.org; sv-ac@eda.org
	Subject: RE: [sv-ac] Regarding Coverage features

	Hi ED,

	 

	   Means the same feature of "bind"  can be used for assertions
as well as for module,interface,program( in which I defined  the
covergroups). So, code syntax for binding of coverage will be like this
:

	 

	>file : cover.sv

	 

	Program coverage (input clk,input a,b,c)

	Class test;

	 

	  Covergroup cg @(posedge clk)

	{

	   // coverpoints and bins.......

	}

	  Endgroup

	 

	Endclass

	Endprogram

	 

	Bind stimulus.dut coverage cover1( clk,a,b,c);

	 

	//where stimulus is top level testbench and dut is the RTL
,instantiated under this.

	 

	 

	And ,ED  can u please suggest something for the point no. 2 & 3
, written below:

	 

	      2.  How can we do on/off with the covergroups??Like in
Randomization , we r having " rand_mode() / constraint_mode()"
predefined methods to do that at run time . So, is there any pre defined
method to do that ??

	 

	      3.  Since we r using dynamic allocation/execution for
covergroup/classes by using "new" , so at run time as per our
requirement in the modelling, can we use "delete" , and keep off that
particular coverage/class object handler ??.

	 

	 

	 

	Thanks & Regards

	-Saurabh Kumar Shrimal

	
________________________________


	From: Eduard Cerny [mailto:Eduard.Cerny@synopsys.com] 
	Sent: Monday, November 21, 2005 6:13 PM
	To: Shrimal, Saurabh Kumar; sv-ec@eda.org; sv-ac@eda.org
	Subject: RE: [sv-ac] Regarding Coverage features

	 

	Hello Saurabh,

	 

	you can bind any module, interface or program to any other such
object definition or instance. (The exception is that module cannot be
bound to a program.) It is like instantiation but done from the outside
and can also be done only to an instance.

	 

	Best regards,

	ed

	 

		 

		
________________________________


		From: owner-sv-ac@eda.org [mailto:owner-sv-ac@eda.org]
On Behalf Of Shrimal, Saurabh Kumar
		Sent: Saturday, November 19, 2005 12:30 PM
		To: sv-ec@eda.org; sv-ac@eda.org
		Subject: [sv-ac] Regarding Coverage features

		Hi,

		 

		   I am having few doubts with respect to coverage
supports provided by SV.

		 

		1.	Is it possible to use "bind " keyword to bind my
file which is having all the information of coverpoints ??? as LRM says
that similar we can do with assertions only, so is it possible with
covergroups also. 

		 

		      2.  How can we do on/off with the
covergroups??Like in Randomization , we r having " rand_mode() /
constraint_mode()" predefined methods to do that at run time . So, is
there any pre defined method to do that ??

		 

		      3.  Since we r using dynamic allocation/execution
for covergroup/classes by using "new" , so at run time as per our
requirement in the modelling, can we use "delete" , and keep off that
particular coverage/class object handler ??.

		 

		 

		Regards

		-Saurabh

		 
Received on Mon Nov 21 11:42:14 2005

This archive was generated by hypermail 2.1.8 : Mon Nov 21 2005 - 11:43:41 PST