Toggle a force signal inside OVM sequence

Question

Hello everyone,

I have a in my TB

initial begin 
 
force DUT_TOP_INST.vt =0;
 #300ns;
force DUT_TOP_INST.vt =1;
 
end
 
Now i want to control this vt pad in my ovm_sequence how do i do that. I want to toggle it basically
Can i override force signal ??
 
 
Thanks in advance !

Answer 1

dave_59

Forum Moderator

10122 posts

June 22, 2020 at 12:39 pm

In reply to tejasakulu:

I believe you can apply the concepts in this paper to the OVM.

— Dave Rich, Verification Architect, Siemens EDA

Answer 2

tejasakulu

Full Access

51 posts

June 22, 2020 at 12:55 pm

In reply to dave_59:

Thanks dave for reply. But i cannot override a force until i call release right? So i need to release it and then i can toggle; with force being on if i try to override it doesn't work
Correct me if i'm wrong

Thanks

Answer 3

anil.khub

Full Access

2 posts

June 22, 2020 at 1:00 pm

In reply to tejasakulu:

One should never use force/release statements. BAD practice because of which you are running into the troubles. Use an interface and handle to the interface to manipulate the signals of those interfaces. I did a quick scan of white paper and describes the solution to your problem aptly.
-anil

Answer 4

Solution

dave_59

Forum Moderator

10122 posts

June 22, 2020 at 1:40 pm

In reply to tejasakulu:

Another force on a signal replaces an existing force—there's no need to release it first.

Also, there's no need to force to a literal constant. You can do

bit vr_reg;
initial force DUT_TOP_INST.vt =vr_reg;
initial begin
 #300ns;
 vr_reg = ~vr_reg;
end

That way you can set up a driver to modify the value of vr_reg directly.

— Dave Rich, Verification Architect, Siemens EDA

Answer 5

tejasakulu

Full Access

51 posts

July 01, 2020 at 4:31 pm

In reply to dave_59:

Thanks Dave

So you mean to say :

module testbench_top
bit vr_reg;
initial force DUT_TOP_INST.vt =vr_reg;
initial begin
 #300ns;
 vr_reg = ~vr_reg;
end
 
interface test;
logic a;
endinterface
 
class driver;
virtual test vif;
new = ()
task test();
vif.vr_reg =1 ;
#200ns
vif.vr_reg = 0;
endtask
 
Let me know if this what you meant "setup the driver to modify the value of vr_reg"
 
Thanks

Answer 6

anil.khub

Full Access

2 posts

July 01, 2020 at 11:00 pm

In reply to tejasakulu:

You need to get rid of force statements and initial blocks. You can look at the following example in

$QUESTA_HOME/examples/systemverilog/interfaces/controller

DUT_TOP_INST.vt should be part of your interface signals to drive or sample.

You are almost there. keep at it.
-anil

Languages & Standards

Methodologies

Techniques & Tools

Universal Verification Methodology (UVM)

Featured Courses

Additional Courses

Formal-Based Techniques

Analog/Mixed Signal

UVM Forum

SystemVerilog Forum

Coverage Forum

Additional Forums

Implementation Patterns

Specification Patterns

Pattern Resources

UVM Cookbook

Coding Guidelines & Deployment

Coverage Cookbook

Featured & On-Demand

On-Demand Library

Recording Archive

Conferences & WRG

Siemens EDA Learning Center

Blog & News

Verification Horizons Publication

About Us

Training

Solution

Portfolio

Explore

Siemens

Contact