Verification Academy

Search form

My Account Menu

  • Register
  • Log In
  • Topics
  • Courses
  • Forums
  • Patterns Library
  • Cookbooks
  • Events
  • More
  • All Topics
    The Verification Academy offers users multiple entry points to find the information they need. One of these entry points is through Topic collections. These topics are industry standards that all design and verification engineers should recognize. While we continue to add new topics, users are encourage to further refine collection information to meet their specific interests.

    • Languages & Standards

      • Portable Test and Stimulus
      • Functional Safety
      • Design & Verification Languages

    • Methodologies

      • UVM - Universal Verification Methodology
      • UVM Framework
      • UVM Connect
      • FPGA Verification
      • Coverage

    • Techniques & Tools

      • Verification IQ
      • Verification IP
      • Static-Based Techniques
      • Simulation-Based Techniques
      • Planning, Measurement, and Analysis
      • Formal-Based Techniques
      • Debug
      • Acceleration
  • All Courses
    The Verification Academy is organized into a collection of free online courses, focusing on various key aspects of advanced functional verification. Each course consists of multiple sessions—allowing the participant to pick and choose specific topics of interest, as well as revisit any specific topics for future reference. After completing a specific course, the participant should be armed with enough knowledge to then understand the necessary steps required for maturing their own organization’s skills and infrastructure on the specific topic of interest. The Verification Academy will provide you with a unique opportunity to develop an understanding of how to mature your organization’s processes so that you can then reap the benefits that advanced functional verification offers.

    • Universal Verification Methodology (UVM)

      • Introduction to UVM
      • UVM Basics
      • Advanced UVM
      • UVM Connect
      • UVM Debug
      • UVMF - One Bite at a Time

    • Featured Courses

      • Introduction to ISO 26262
      • Introduction to DO-254
      • Clock-Domain Crossing Verification
      • Portable Stimulus Basics
      • Power Aware CDC Verification
      • Power Aware Verification
      • SystemVerilog OOP for UVM Verification

    • Additional Courses

      • Assertion-Based Verification
      • An Introduction to Unit Testing with SVUnit
      • Evolving FPGA Verification Capabilities
      • Metrics in SoC Verification
      • SystemVerilog Testbench Acceleration
      • Testbench Co-Emulation: SystemC & TLM-2.0
      • Verification Planning and Management
      • VHDL-2008 Why It Matters

    • Formal-Based Techniques

      • Formal Assertion-Based Verification
      • Formal-Based Technology: Automatic Formal Solutions
      • Formal Coverage
      • Getting Started with Formal-Based Technology
      • Handling Inconclusive Assertions in Formal Verification
      • Sequential Logic Equivalence Checking

    • Analog/Mixed Signal

      • AMS Design Configuration Schemes
      • Improve AMS Verification Performance
      • Improve AMS Verification Quality
  • All Forum Topics
    The Verification Community is eager to answer your UVM, SystemVerilog and Coverage related questions. We encourage you to take an active role in the Forums by answering and commenting to any questions that you are able to.

    • UVM Forum

      • Active Questions
      • Solutions
      • Replies
      • No Replies
      • Search
      • UVM Forum

    • SystemVerilog Forum

      • Active Questions
      • Solutions
      • Replies
      • No Replies
      • Search
      • SystemVerilog Forum

    • Coverage Forum

      • Active Questions
      • Solutions
      • Replies
      • No Replies
      • Search
      • Coverage Forum

    • Additional Forums

      • Announcements
      • Downloads
      • OVM Forum
  • Patterns Library
    The Verification Academy Patterns Library contains a collection of solutions to many of today's verification problems. The patterns contained in the library span across the entire domain of verification (i.e., from specification to methodology to implementation—and across multiple verification engines such as formal, simulation, and emulation).

    • Implementation Patterns

      • Environment Patterns
      • Stimulus Patterns
      • Analysis Patterns
      • All Implementation Patterns

    • Specification Patterns

      • Occurrence Property Patterns
      • Order Property Patterns
      • All Specification Patterns

    • Pattern Resources

      • Start Here - Patterns Library Overview
      • Whitepaper - Taking Reuse to the Next Level
      • Verification Horizons - The Verification Academy Patterns Library
      • Contribute a Pattern to the Library
  • All Cookbooks
    Find all the methodology you need in this comprehensive and vast collection. The UVM and Coverage Cookbooks contain dozens of informative, executable articles covering all aspects of UVM and Coverage.

    • UVM Cookbook

      • UVM Basics
      • Testbench Architecture
      • DUT-Testbench Connections
      • Configuring a Test Environment
      • Analysis Components & Techniques
      • End Of Test Mechanisms
      • Sequences
      • The UVM Messaging System
      • Other Stimulus Techniques
      • Register Abstraction Layer
      • Testbench Acceleration through Co-Emulation
      • Debug of SV and UVM
      • UVM Connect - SV-SystemC interoperability
      • UVM Versions and Compatibility
      • UVM Cookbook

    • Coding Guidelines & Deployment

      • Code Examples
      • UVM Verification Component
      • Package/Organization
      • Questa/Compiling UVM
      • SystemVerilog Guidelines
      • SystemVerilog Performance Guidelines
      • UVM Guidelines
      • UVM Performance Guidelines

    • Coverage Cookbook

      • Introduction
      • What is Coverage?
      • Kinds of Coverage
      • Specification to Testplan
      • Testplan to Functional Coverage
      • Bus Protocol Coverage
      • Block Level Coverage
      • Datapath Coverage
      • SoC Coverage Example
      • Requirements Writing Guidelines
      • Coverage Cookbook
  • All Events
    No one argues that the challenges of verification are growing exponentially. What is needed to meet these challenges are tools, methodologies and processes that can help you transform your verification environment. These recorded seminars from Verification Academy trainers and users provide examples for adoption of new technologies and how to evolve your verification process.

    • Featured & On-Demand

      • Continuous Integration - March 28th
      • SystemVerilog Assertions
      • SoC Design & Functional Safety Flow
      • 2022 Functional Verification Study
      • Design Solutions as a Sleep Aid
      • CDC and RDC Assist
      • Formal and the Next Normal
      • Protocol and Memory Interface Verification
      • Webinar Calendar

    • On-Demand Library

      • Practical Flows for Continuous Integration
      • Lint vs Formal AutoCheck
      • The Three Pillars of Intent-Focused Insight
      • Formal Verification Made Easy
      • Fix FPGA Failures Faster
      • HPC Protocols & Memories
      • FPGA Design Challenges
      • High Defect Coverage
      • The Dog ate my RTL
      • Questa Lint & CDC
      • Complex Safety Architectures
      • Data Independence and Non-Determinism
      • Hierarchical CDC+RDC
      • All On-Demand Recordings

    • Recording Archive

      • Aerospace & Defense Tech Day
      • Exhaustive Scoreboarding
      • Improving Initial RTL Quality
      • CDC Philosophy
      • Hardware Emulation Productivity
      • Visualizer Debug Environment
      • Preparing for PCIe 6.0: Parts I & II
      • Automotive Functional Safety Forum
      • Siemens EDA Functional Verification
      • Improving Your SystemVerilog & UVM Skills
      • All Webinar Topics

    • Conferences & WRG

      • Industry Data & Surveys
      • DVCon 2023
      • DVCon 2022
      • DVCon 2021
      • Osmosis 2022
      • All Conferences

    • Siemens EDA Learning Center

      • SystemVerilog Fundamentals
      • SystemVerilog UVM
      • EDA Xcelerator Academy(Learning Services) Verification Training, Badging and Certification
      • View all Learning Paths
  • About Verification Academy
    The Verification Academy will provide you with a unique opportunity to develop an understanding of how to mature your organization's processes so that you can then reap the benefits that advanced functional verification offers.

    • Blog & News

      • Verification IQ
      • Verification Horizons Blog
      • Technical Resources

    • Verification Horizons Publication

      • Verification Horizons - March 2023
      • Verification Horizons - December 2022
      • Verification Horizons - July 2022
      • Issue Archive

    • About Us

      • Verification Academy Overview
      • Subject Matter Experts
      • Academy News
      • Contact Us

    • Training

      • Learning @OneGlance (PDF)
      • SystemVerilog & UVM Classes
      • Siemens EDA Classes
Ask a Question
OVM
  • Home
  • Forums
  • OVM
  • scoreboard

scoreboard

OVM 2524
sethulekshmi
sethulekshmi
Forum Access
29 posts
March 12, 2010 at 3:47 am

hello,
I have a monitor at the output of the DUT and a predictor . outputs of the predictor and the monitor should be connected to the scoreboard.

i have done it as given in one of the threads :


//Declaration inside processor monitor
ovm_analysis_port #(OUT_item) proc_mon_port;
:)proc_mon_port.write(OUT_item); -----error in this line
//Declaration inside predictor
ovm_analysis_port #(OUT_item) predictor_port;
:)predictor_port.write(OUT_item); -----error in this line

//Declarations inside ovm_scoreboard

//Declare two ovm_analysis_export to receive transactions from
monitors and predictor

ovm_analysis_export #(OUT_item) proc_mon_export;
ovm_analysis_export #(OUT_item) predictor_export;

//Declare two tlm_analysis_fifo to connect to ovm_analysis_export
//to get the transactions

tlm_analysis_fifo #(OUT_item) proc_mon_fifo;
tlm_analysis_fifo #(OUT_item) predictor_fifo;

//Connect ovm_analysis_export and tlm_analysis_fifo using
//connect function inside ovm_scoreboard
function void connect;
proc_mon_export.connect(proc_mon_fifo.analysis_export);
predictor_export.connect(predictor_fifo.analysis_export);
endfunction: connect

//Define the task run to get the transaction using get method
task run;
begin
chk_data();
end
endtask: run

task chk_data();
OUT_item proc_mon, predictor;
forever begin
proc_mon_fifo.get(proc_mon);
predictor_fifo.get(predictor);

if(proc_mon.OUT_item == predictor.OUT_item )
$display("match");

end
endtask: chk_data

// Connections inside the environment
// Now connecting the two differenct ovm_monitor with the
// ovm_scoreboard using the connect function

function void connect();
ctl_proc_mon_1.proc_mon_port.connect(ctl_scoreboard.proc_mon_export);
ctl_predictor_2.predictor_port.connect(ctl_scoreboard.predictor_export);
endfunction: connect

pls help......

Replies

Log In to Reply
kurts
kurts
Full Access
150 posts
March 12, 2010 at 12:36 pm

In your monitor, do you have a build() function with the following lines?

proc_mon_port = new("proc_mon_port",this);
predictor_port = new("predictor_port",this);

Forgetting to create the ports would cause an error on the lines that you mentioned.

-Kurt

sethulekshmi
sethulekshmi
Forum Access
29 posts
March 13, 2010 at 3:06 am

Sir,
i got it corrected by writing it inside the function new.


Now i had problem with the run task.


in the scoreboard how can i compare the output from the predictor and the monitor and display that both are same.


I wrote it as
task run;
begin
@(posedge PROC.clk)
chk_data();
end
endtask: run

task chk_data();
OUT_item ER902_mon, predictor;
forever begin
ER902_mon_fifo.get(ER902_mon);
$display(OUT_item.ddm_out);
predictor_fifo.get(predictor);
$display(OUT_item.pdd_out);
if (ER902_mon.OUT_item ==predictor.OUT_item )
$display("match");
endtask: chk_data

sethulekshmi
sethulekshmi
Forum Access
29 posts
March 13, 2010 at 3:09 am

Sir,
i got it corrected by writing it inside the function new().


Now i had problem with the run task.


in the scoreboard how can i compare the output from the predictor and the monitor and display that both are same.


I wrote it as
task run;
begin
@(posedge PROC.clk)
chk_data();
end
endtask: run


task chk_data();
:)OUT_item proc_mon, predictor; ==== error at this line
forever begin
proc_mon_fifo.get(proc_mon);
$display(OUT_item.ddm_out);
predictor_fifo.get(predictor);
$display(OUT_item.pdd_out);
if (proc_mon.OUT_item ==predictor.OUT_item )
$display("match");
end
endtask: chk_data

pla help.....

desperado
desperado
Forum Access
118 posts
March 14, 2010 at 9:22 pm

Hello,

Wish this would be helpful in understanding in connecting monitor with the scoreboard.,

Quote:

http://ovmworld.org/forums/showthread.php?t=877&highlight=connecting+monitor+with+scoreboard

Thanks,
Desperado

Vaibhav Tekale
Vaibhav Tekale
Full Access
151 posts
March 14, 2010 at 10:11 pm

Hi,

You can use the "compare" method of the sequence_item/transaction class.

Quote:

if(mon_data.compare(pred_data)) begin
$display("DATA MATCH!!!");
end else begin
$display("DATA MISMATCH!!!");
end

Regards,

sethulekshmi
sethulekshmi
Forum Access
29 posts
March 15, 2010 at 1:11 pm

Sir,
to connect the predictor and the monitor i have done the following things:

predictor has a drive item out_item and monitor has a drive item out_item1 .
i have used put() method in both the predictor and monitor to put the data into the scoreboard.

//========================================
ovm_blocking_put_imp #(out_item ER902_scoreboard) put_export;
2172: ovm_blocking_put_imp #(out_item1, ER902_scoreboard) put_export;

when i have written like this , i had the error as
2172): 'put_export' already declared in this scope (ER902_scoreboard).

//=========================================
ovm_blocking_put_imp #(out_item,out_item1 ER902_scoreboard) put_export;

the error is syntax error.
//===================================

how can i implement the put_export of scoreboard with 2 different drive items.??

i tried put() method in the predictor and get() method in the monitor with 2 drive items.....
then the problem is only the value in predictor is updated. the monitor value is alway zero,(no change)


class ER902_scoreboard extends ovm_scoreboard;

logic [31:0] smdd_out;
logic [31:0] spdd_out;

out_item OUT_item;
out_item1 OUT_item1;

:) ovm_blocking_put_imp #(out_item ,ER902_scoreboard) put_export;
:)ovm_blocking_put_imp #(out_item1, ER902_scoreboard) put_export;


`ovm_component_utils_begin(ER902_scoreboard)
`ovm_field_object(OUT_item1,OVM_ALL_ON)
`ovm_field_object(OUT_item,OVM_ALL_ON)
`ovm_component_utils_end


function new (string name, ovm_component parent);
super.new(name, parent);
ovm_report_info("", "ER902_scoreboard::new");
put_export = new("put_export",this);
ovm_report_info("", "Called put_export::new");

endfunction : new

:) task put(out_item OUT_item, out_item1 OUT_item1);
begin

fork


$display("sequences in scoreboard from predictor");
spdd_out =OUT_item.pddm_out;
$display("spdd_out =%b",spdd_out);

$display("sequences in scoreboard from monitor");
smdd_out =OUT_item1.ddm_out;
$display("smdd_out =%b",smdd_out);





join
// end
end
endtask : put


endclass :ER902_scoreboard

pls help....

Vaibhav Tekale
Vaibhav Tekale
Full Access
151 posts
March 15, 2010 at 10:24 pm

Hi,

Here you need to use macro "`ovm_blocking_put_imp_decl("

Quote:

`ovm_blocking_put_imp_decl(_P1)
`ovm_blocking_put_imp_decl(_P2)

class ER902_scoreboard extends ovm_scoreboard;

logic [31:0] smdd_out;
logic [31:0] spdd_out;

out_item OUT_item;
out_item1 OUT_item1;

ovm_blocking_put_imp_P1 #(out_item ,ER902_scoreboard) put_export;
ovm_blocking_put_imp_P2 #(out_item1 ,ER902_scoreboard) put_export1;
`ovm_component_utils_begin(ER902_scoreboard)
`ovm_field_object(OUT_item1,OVM_ALL_ON)
`ovm_field_object(OUT_item,OVM_ALL_ON)
`ovm_component_utils_end


function new (string name, ovm_component parent);
super.new(name, parent);
ovm_report_info("", "ER902_scoreboard::new");
put_export = new("put_export",this);
put_export1 = new("put_export1",this);
ovm_report_info("", "Called put_export::new");

endfunction : new

task put_P1(out_item OUT_item);
// ...........
endtask : put_P1

task put_P2(out_item1 OUT_item1);
// ...........
endtask : put_P2


Hope this helps you.

Regards,

sethulekshmi
sethulekshmi
Forum Access
29 posts
March 16, 2010 at 4:33 am

Sir,
I had tried the program as u have written... still my problem is, in the scoreboard i could only get the output from monitor ie from task put_P2.
//=======================================================


`ovm_blocking_put_imp_decl(_P1)
`ovm_blocking_put_imp_decl(_P2)

class ER902_scoreboard extends ovm_scoreboard;

logic [31:0] smdd_out;
logic [31:0] spdd_out;

out_item OUT_item;// predictor
out_item1 OUT_item1; //monitor

ovm_blocking_put_imp_P1 #(out_item ,ER902_scoreboard) put_export;
ovm_blocking_put_imp_P2 #(out_item1 ,ER902_scoreboard) put_export1;

`ovm_component_utils_begin(ER902_scoreboard)
`ovm_field_object(OUT_item,OVM_ALL_ON)
`ovm_field_object(OUT_item1,OVM_ALL_ON)
`ovm_component_utils_end

function new (string name, ovm_component parent);
super.new(name, parent);
ovm_report_info("", "ER902_scoreboard::new");
put_export = new("put_export",this);
put_export1 = new("put_export1",this);
ovm_report_info("", "Called put_export::new");
endfunction : new

task put_P1(out_item OUT_item);
$display("sequences in scoreboard from predictor");
spdd_out =OUT_item.pddm_out; //============"ERROR" ===sequences in scoreboard from predictor
// # ** Fatal: (SIGSEGV) Bad handle or reference
$display("spdd_out =%b",spdd_out);
endtask : put_P1


task put_P2(out_item1 OUT_item1);
$display("sequences in scoreboard from monitor");
smdd_out =OUT_item1.ddm_out;
$display("smdd_out =%b",smdd_out);
endtask : put_P2
//====================================
.

pls help

Vaibhav Tekale
Vaibhav Tekale
Full Access
151 posts
March 16, 2010 at 6:24 am

Hi,

Have you connected "ovm_blocking_put_imp_P1 #(out_item ,ER902_scoreboard) put_export;" port?

Regards,

sethulekshmi
sethulekshmi
Forum Access
29 posts
March 16, 2010 at 11:29 am

SIr,
i tried to write the "connect function" in the scoreboard .. but is not working....

connection b/w

"ovm_blocking_put_imp_P1 #(out_item ,ER902_scoreboard) put_export;"
and
ovm_blocking_put_port #(out_item) put_port;

pls help

sethulekshmi
sethulekshmi
Forum Access
29 posts
March 16, 2010 at 9:19 pm

Sir,
I ahve connected the monitor and scoreboard as
mon_er902.put_port1.connect(score_er902.put_export1);
and
predictor and scoreboard as
pre_dictor.put_port.connect(score_er902.put_export);
in the environment.

My ports and exports are

for predictor
ovm_blocking_put_imp_P1 #(out_item ,ER902_scoreboard) put_export;
ovm_blocking_put_port #(out_item) put_port;

for monitor
ovm_blocking_put_imp_P2 #(out_item1 ,ER902_scoreboard) put_export1;
ovm_blocking_put_port #(out_item1) put_port1;

how should i connect this in scoreboard.
pls help....

Vaibhav Tekale
Vaibhav Tekale
Full Access
151 posts
March 17, 2010 at 12:06 am

Hi,

It seems that connection are correct. Can you make sure that predictor is not sending nulll packets..

Regards,

sethulekshmi
sethulekshmi
Forum Access
29 posts
March 17, 2010 at 5:17 am

Sir ,
I got it corrected. Thank u for ur help.
regards
lakshmi

Siemens Digital Industries Software

Siemens Digital Industries Software

#TodayMeetsTomorrow

Portfolio

  • Cloud
  • Mendix
  • Electronic Design Automation
  • MindSphere
  • Design, Manufacturing and PLM Software
  • View all Portfolio

Explore

  • Community
  • Blog
  • Online Store

Siemens

  • About Us
  • Careers
  • Events
  • News and Press
  • Customer Stories
  • Partners
  • Trust Center

Contact

  • VA - Contact Us
  • PLM - Contact Us
  • EDA - Contact Us
  • Worldwide Offices
  • Support Center
  • Give us Feedback
© Siemens 2023
Terms of Use Privacy Statement Cookie Statement DMCA