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

      • VA Live - Multiple Dates & Locations
      • Interconnect Formal
      • Formal and the Next Normal
      • Formal Verification Made Easy
      • Data Independence and Non-Determinism
      • Exhaustive Scoreboarding
      • Visualizer Debug Environment
      • Webinar Calendar
    • On-Demand Library

      • SystemVerilog Assertions
      • Practical Flows for Continuous Integration
      • Continuous Integration
      • Questa Verification IQ
      • Avery & Siemens VIP
      • Protocol and Memory Interface Verification
      • HPC Protocols & Memories
      • Preparing for PCIe 6.0: Parts I & II
      • High Defect Coverage
      • SoC Design & Functional Safety Flow
      • Complex Safety Architectures
      • All On-Demand Recordings
    • Recording Archive

      • Lint vs Formal AutoCheck
      • FPGA Design Challenges
      • Design Solutions as a Sleep Aid
      • Fix FPGA Failures Faster
      • CDC and RDC Assist
      • The Dog ate my RTL
      • Questa Lint & CDC
      • Hierarchical CDC+RDC
      • Improving Initial RTL Quality
      • CDC Philosophy
      • Hardware Emulation Productivity
      • The Three Pillars of Intent-Focused Insight
      • All Webinar Topics
    • Conferences & WRG

      • 2022 Functional Verification Study
      • Improving Your SystemVerilog & UVM Skills
      • Automotive Functional Safety Forum
      • Aerospace & Defense Tech Day
      • Siemens EDA Functional Verification
      • Industry Data & Surveys
      • DVCon 2023
      • DVCon 2022
      • DVCon 2021
      • Osmosis 2022
      • All Conferences
    • Siemens EDA Learning Center

      • EDA Xcelerator Academy(Learning Services) Verification Training, Badging and Certification
      • View all Xcelerator Academy classes
  • 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
UVM
  • Home
  • Forums
  • UVM
  • Is it necessary for comparison of data in scoreboard we should use check_phase??

Is it necessary for comparison of data in scoreboard we should use check_phase??

UVM 6753
uvm_scoreboard 5 check_phase 2 run_phase 6
Subhra Bera
Subhra Bera
Full Access
42 posts
March 22, 2018 at 11:54 pm

Actually I have some problem in comparing data in run_phase of scoreboard. When I am comparing in run phase of scoreboard the data's are not matching although when I am printing both data they are coming as same. But when I moved my comparing logic to check_phase then their is no mismatch. All data matched . What is the reason behind these mismatch in scoreboard's run phase ?

Replies

Log In to Reply
dave_59
dave_59
Forum Moderator
10909 posts
March 23, 2018 at 8:10 am

In reply to Subhra Bera:
Impossible to answer without knowing the timing of the data you are trying to compare, but most likely a race condition.

The purpose of the check_phase is to do comparisons after the test has finished executing, so it might be more appropriate to do the check there.

— Dave Rich, Verification Architect, Siemens EDA

chr_sue
chr_sue
Full Access
3896 posts
March 23, 2018 at 9:54 am

In reply to dave_59:

Did you try the case equality? There might be x or z in your data. Or the format is wrong.
There can be more reasons. Do you apply the compare data as a transaction?

Subhra Bera
Subhra Bera
Full Access
42 posts
March 23, 2018 at 11:01 am

In reply to chr_sue:
Yes I tried case equality but they did not work. Actually I am writing scoreboard logic for SPI. I have taken a queue of apb(master) sequence item in scoreboard. And another queue of SPI sequence item. I have taken an associative array in scoreboard for mimicking the DUT model.
I am poping out data from apb_queue and based on address(apb sequence item) I am storing the the data in the associative array. Then when spi_queue is getting its first data. Then I am comparing based on the character length.
SPI DUT has Tx0,Tx1,Tx2,Tx3,Rx0,Rx1,Rx2,Rx3,ctrl,divider,ss register. All are 32bit in size. There address are 00,04,08,0c,10,14,18 in hexadecimal(Tx and Rx registers address are same).ctrl[6:0] is the length of the character to be send and received.
when I am taking logic[31:0] char_len variable in scoreboard. In this variable I am storing associative_array[ctrl_addr]. And based on char_len[6:0](character length) I am comparing.
I have taken logic[127:0]Total_tx variable. And storing like Total_tx={Tx3,Tx2,Tx1,Tx0}; and then based on char_len[6:0] I am comparing. like

 for(int i=0;i<char_len;i++) begin
                           if(Total_tx[i]==MOSI[i]) (Mosi is the spi slave sequence item 
                          k++;                            data of 128 bit length logic type 
                       else                                                         variable)
                        break; 
                   end  

and then if k==char_lenth then data matches.
But Tx_Total=10203040102030401020304010203040;
MOSI= XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX40(30 X, 2 DIGIT)
CHAR_LEN =8 BUT data is not matching.
chr_sue
chr_sue
Full Access
3896 posts
March 23, 2018 at 11:49 am

In reply to Subhra Bera:

You should show how you are extracting your transactions. This help might hrlp to resolve the issue.

Subhra Bera
Subhra Bera
Full Access
42 posts
March 25, 2018 at 9:08 pm

In reply to chr_sue:

//Macros to create the uvm_analysis_imp ports (just an export + write function)
  `uvm_analysis_imp_decl(_apb_port) 
  `uvm_analysis_imp_decl(_spi_port)
 
class spi_scoreboard extends uvm_scoreboard;
  `uvm_component_utils(spi_scoreboard)
string m_name;
virtual irq_if irq_if_1;
///golden reference model
logic [31:0] dut_model_w[*];//for mimicing the  writing into the dut reg
logic [31:0] dut_model_r[*];//for mimicing the reading from the dut reg
logic[31:0] ctrl_reg_value;// to know the ctrl register value
logic[127:0] Tx_reg_value,Rx_reg_value;
logic[6:0] char_len;
// for checking purpose
int k,l;
 
apb_seq_item apb_item,apb_item_2;
spi_seq_item spi_item,spi_item_2;
 
uvm_analysis_imp_apb_port#(apb_seq_item,spi_scoreboard)apb_imp;
uvm_analysis_imp_spi_port#(spi_seq_item,spi_scoreboard)spi_imp;
 
//queue to store data which will come from apb and spi side
apb_seq_item apb_dataQ[$];
spi_seq_item spi_dataQ[$];
logic[127:0] MOSIDATA,MISODATA;
 
extern function new(string name="spi_scoreboard",uvm_component parent =null);
extern function void build_phase(uvm_phase phase);
extern task run_phase( uvm_phase phase );
extern function void write_apb_port(apb_seq_item apb_item_1);
extern function void write_spi_port(spi_seq_item spi_item_1);
extern function void extract_phase( uvm_phase phase );
extern function void check_phase(uvm_phase phase);
extern function void report_phase( uvm_phase phase );
 
 
endclass:spi_scoreboard
 
 
 function spi_scoreboard::new (string name="spi_scoreboard", uvm_component parent=null);
    super.new(name, parent);
     m_name=name;
  endfunction : new
 
function void spi_scoreboard:: build_phase(uvm_phase phase);
 super.build_phase(phase);
 if(!uvm_config_db#(virtual irq_if)::get(this,"","irq_if",irq_if_1))
  `uvm_fatal("NO IRQ IF",{"virtual interface of IRQ must be set for:",get_full_name(),".irq_if"});
 spi_imp=new("spi_imp",this);
 apb_imp=new("apb_imp",this);
endfunction:build_phase
 
 
function void spi_scoreboard:: write_apb_port(apb_seq_item apb_item_1);
       $cast(apb_item,apb_item_1.clone());
      `uvm_info(get_type_name(),$sformatf("writing in the apb write method \n %s",apb_item.sprint()), UVM_LOW)
      apb_dataQ.push_back(apb_item);
 
 
endfunction
 
 
function void spi_scoreboard:: write_spi_port(spi_seq_item spi_item_1);
    $cast(spi_item,spi_item_1.clone());
    `uvm_info(get_type_name(),$sformatf("writing in spi write method \n %s",spi_item.sprint()),UVM_LOW)
    spi_dataQ.push_back(spi_item);
endfunction
 
task spi_scoreboard:: run_phase( uvm_phase phase );
      forever begin
 
 
         foreach(apb_dataQ[i]) begin
           apb_item_2=apb_dataQ.pop_front();
          `uvm_info(m_name,$sformatf("Scoreboard \n %s",apb_item_2.sprint()),UVM_LOW)
              if(apb_item_2.we) begin
                    dut_model_w[apb_item_2.addr]=apb_item_2.data;
                   // $display("dut_model_w=%p",dut_model_w);
                end
 
             else begin
               dut_model_r[apb_item_2.addr]=apb_item_2.data;
                //$display("dut_model_r=%p",dut_model_r);
              end
 
 
          end
 
           Tx_reg_value={dut_model_w[32'h0c],dut_model_w[32'h08],dut_model_w[32'h04],dut_model_w[32'h00]};
           Rx_reg_value={dut_model_r[32'h0c],dut_model_r[32'h08],dut_model_r[32'h04],dut_model_r[32'h00]};
 
           ctrl_reg_value = dut_model_w[32'h10];
           char_len=ctrl_reg_value[6:0];
                  wait(spi_dataQ.size())begin
                      spi_item_2= spi_dataQ.pop_front();
                      MOSIDATA=spi_item_2.MOSIDATA;
                      MISODATA=spi_item_2.MISODATA;
                      $display($time,"MOSIDATA[127:0]::%b\n MISODATA[127:0]::%b",MOSIDATA[127:0],MISODATA[127:0]);
 
                  end
            end
 
endtask
 
 
 
 
function void spi_scoreboard::  extract_phase(uvm_phase phase);
super.extract_phase(phase);
 
  foreach(apb_dataQ[i]) begin
           apb_item_2=apb_dataQ.pop_front();
          `uvm_info(m_name,$sformatf("Scoreboard \n %s",apb_item_2.sprint()),UVM_LOW)
              if(apb_item_2.we) begin
                    dut_model_w[apb_item_2.addr]=apb_item_2.data;
                   // $display("dut_model_w=%p",dut_model_w);
                end
 
             else begin
               dut_model_r[apb_item_2.addr]=apb_item_2.data;
                //$display("dut_model_r=%p",dut_model_r);
              end
          end
     Rx_reg_value={dut_model_r[32'h0c],dut_model_r[32'h08],dut_model_r[32'h04],dut_model_r[32'h00]};
endfunction
 
function void spi_scoreboard::  check_phase(uvm_phase phase);
super.check_phase(phase);
 
//compare logic
    begin
      for(int j=0;j<char_len;j++) begin
          if(MOSIDATA[j]===Tx_reg_value[j])
             k++;
          else 
            break;
       end
 
      for(int m=0;m<char_len;m++) begin
          if(MISODATA[m]===Rx_reg_value[m])
             l++;
          else
            break;
       end
   end
       apb_dataQ.delete();
       spi_dataQ.delete();
 
endfunction
 
 
 
 
function void spi_scoreboard:: report_phase( uvm_phase phase );
//report
 super.report_phase(phase);
    `uvm_info(get_type_name(), "============================", UVM_NONE)
    `uvm_info(get_type_name(), "Scoreboard Results", UVM_NONE)
     if(char_len==k&&char_len==l)begin
                   `uvm_info(get_type_name(), "TEST PASSED", UVM_NONE)
                   `uvm_info(m_name,$sformatf("CONSIDERED CHARACTER LENGTH::%d",char_len),UVM_LOW)
                   `uvm_info(m_name,$sformatf("DATA SENT FROM APB MASTER IS MATCHED WITH DATA IN MOSI LINE::\n\n\n       MOSI DATA SENT FROM APB MASTER::%b\n MOSI DATA COLLECTED FROM SPI MONITOR::%b\n\n",Tx_reg_value[127:0],  MOSIDATA[127:0] ),UVM_LOW)
                   `uvm_info(m_name,$sformatf("DATA SENT FROM SPI SLAVE IS MATCHED WITH DATA IN MISO LINE::\n\n\n        MISO DATA SENT FROM SPI SLAVE::%b\n MISO DATA COLLECTED FROM APB MONITOR::%b\n\n",MISODATA[127:0],Rx_reg_value[127:0]),UVM_LOW)
 
          end
        else begin 
                 `uvm_info(get_type_name(), "TEST FAILED", UVM_NONE)
 
    `uvm_info(get_type_name(), "============================", UVM_NONE)
          end
endfunction

Quote:
Here actually I have written 12 sequence item through apb_driver within which 8 of which are writing operation and 4 are reading operation. All of the sequence item are coming to queue of type apb_seq_item. But the first 8(write seq item) are stored in the queue first and the scoreboard run_phase is taking out those 8 item from the queue and after that it completes run_phase. But the apb_seq_item which come some time after to the queue, scoreboard is not considering them in run_phase. If I use extract phase then only it able to extract the remaining sequence item . Otherwise it is not happening . Why this problem is coming?
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