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
  • Reference model

Reference model

UVM 6753
module 1 #uvm 278 #systemverilog 102
JH_Engineer
JH_Engineer
Full Access
6 posts
August 28, 2018 at 6:02 am

Hi Guys,

I have a questions about Reference model,

  • what does it mean?
  • how we build and implement it?
  • does it just like the design module? ,do we actually build a module that implement the spec.?

Please, refer me to articles or papers that explain it, or if there is an practical example.

Thank you in advance!.

Replies

Log In to Reply

Solution

Solution

dave_59
dave_59
Forum Moderator
10908 posts
August 28, 2018 at 2:30 pm

In reply to JH_Engineer:

A reference model is an executable specification - a golden model that predicts the correct results from the provided stimulus. How one implements a reference model is as varied the way specifications are written as well as each design.

Sometimes you are re-doing a design to fit on a smaller part. The reference model could be the previous design.

Many designs implement mathematical algorithms implemented in MatLAb or similar environments. They can generate C code to be used as a reference model.

This is a really big topic, so it's difficult to explain in this forum.

— Dave Rich, Verification Architect, Siemens EDA

JH_Engineer
JH_Engineer
Full Access
6 posts
August 28, 2018 at 10:48 pm

Thank you Dave.

muneebullashariff
muneebullashariff
Full Access
21 posts
November 03, 2018 at 2:13 am

In reply to dave_59:

Quote:
In reply to JH_Engineer:

A reference model is an executable specification - a golden model that predicts the correct results from the provided stimulus. How one implements a reference model is as varied the way specifications are written as well as each design.

Sometimes you are re-doing a design to fit on a smaller part. The reference model could be the previous design.

Many designs implement mathematical algorithms implemented in MatLAb or similar environments. They can generate C code to be used as a reference model.

This is a really big topic, so it's difficult to explain in this forum.

Hi Dave,

In the industry most of the reference models are written in C.
Why is this c-based reference models ubiquitous?
Also, could we write them using SV? In this case we need not use DPIs.

Thank you,

Regards,
Muneeb

dave_59
dave_59
Forum Moderator
10908 posts
November 03, 2018 at 11:16 am

In reply to muneebullashariff:

Whether you see a lot of C reference models or not depends on which industry you are in. In many cases, C reference models are made available for use in other environments beside RTL verification, so why re-write these modules in SystemVerilog?

— Dave Rich, Verification Architect, Siemens EDA

muneebullashariff
muneebullashariff
Full Access
21 posts
November 04, 2018 at 12:23 am

In reply to dave_59:

Quote:
In reply to muneebullashariff:

Whether you see a lot of C reference models or not depends on which industry you are in. In many cases, C reference models are made available for use in other environments beside RTL verification, so why re-write these modules in SystemVerilog?

Hi Dave,

Many thanks for your reply.

I have a requirement to develop the reference model for the processor. Moreover, the test-bench is developed using SV and UVM.

In which language should I code my reference model:
Using C or
Using SV

Furthermore, what is the best way to verify the reference model?

Regards,
Muneeb

chr_sue
chr_sue
Full Access
3893 posts
November 04, 2018 at 7:19 am

In reply to muneebullashariff:

Quote:

I have a requirement to develop the reference model for the processor. Moreover, the test-bench is developed using SV and UVM.

In which language should I code my reference model:
Using C or
Using SV

Furthermore, what is the best way to verify the reference model?

There is no common answer to your question. It depends on what you want to do with your reference model and where it will be used.
In a lot of cases you can reuse models written in C/C++ for use in system design. If you have such a model it should be already verified.
If you have an algorithmic design implementing certain algorithm you might use a Matlab model and connection Matlab to your UVM environment.
If you have a communication application the reference model might be quite simple because you have to store your data from the seperate streams in queues or tlm_fifos.
If you have no other application it depends which language is more familiar to oyu.

verif_learner
verif_learner
Forum Access
394 posts
November 04, 2018 at 8:09 am

In reply to muneebullashariff:

Quote:
In reply to dave_59:

Quote:
In reply to muneebullashariff:

Whether you see a lot of C reference models or not depends on which industry you are in. In many cases, C reference models are made available for use in other environments beside RTL verification, so why re-write these modules in SystemVerilog?

Hi Dave,

Many thanks for your reply.

I have a requirement to develop the reference model for the processor. Moreover, the test-bench is developed using SV and UVM.

In which language should I code my reference model:
Using C or
Using SV

Furthermore, what is the best way to verify the reference model?

Regards,
Muneeb

Apart from what other members here have mentioned, keep also in mind that a reference model is expected to be a model against which you would conclude whether the DUT is correct or not.
Now, the features can themselves be temporal by nature.
If this is the case and any of the following is true then you are better off using SV for modelling:
1) you want to verify the temporal behaviour of the DUT
2) you have no other way to verify the temporal behaviour other than modelling it in reference model. For example, transactional level temporal checks can be easily done using assertions and should be the first choice. Deep sequential behaviour are hard to be captured using assertions. So, these will be mostly done in SV

Please also be aware that a reference model need not be monolithic. In fact, it is common to accomplish overall reference model behaviour using "sum of parts" approach. Meaning, many reference models can be combined to get the overall behaviour. So, you can have some in C++ domain and some in SV domain depending on all the above criteria mentioned above and by other members here.

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