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
  • Calling randomize of config object

Calling randomize of config object

UVM 6758
UVM 211 config 4
shrawan_vaidya
shrawan_vaidya
Full Access
11 posts
August 31, 2017 at 3:22 am

Hi,

I am new to UVM and trying to get the proper understanding of using ::get, ::create, ::set_type_override for my config object.

I have a list of agents. Each agent has its own config (same type but with different randomization depending on each agent id). I generate my agent and also agent.config in my env using type_id::create. I realized that in my testcase when I do type_id::set_type_override, it does not change my config object. In each agent's build phase I am randomizing config. The reason for that is that the config has fields like ACTIVE/PASSIVE, and many other specific fields which are to be configured by the user using constraints. Once randomization is done I can accordingly create driver and monitor.
So in brief my questions -
1. For creating config in an agent -- Is ::create() is enough to take the settings of set_override in effect or do I need to use config.get(..) from config_db. If not found than do ::create.
2. When to call randomize()? Does my approach sound OK? I can ofcourse move agent's config to env as a list of configs and than pass a pointer to the agent. But still the issue of when to randomize remains. Please note that I want to put all parameters related to the agent in the config.

I saw the an earlier post on when to call randomize() but it did not resolve my issue, so had to post this one in a new thread. The earlier one was -
https://verificationacademy.com/forums/uvm/during-which-phase-call-randomize-uvm

Replies

Log In to Reply
sunils
sunils
Full Access
106 posts
August 31, 2017 at 4:10 am

In reply to shrawan_vaidya:

Hello Shrawan,

1. Use uvm_config_db in the build_phase() of ENV class to set the agent config handle. And get the agent config handle in build_phase() agent class.

2. Did you face any issue while randomizing the values in start of simulation pahse. As it si given in the link.

Regards,
Sunil

shrawan_vaidya
shrawan_vaidya
Full Access
11 posts
August 31, 2017 at 9:28 am

In reply to sunils:

1. My current code in env build_phase is something like this -

    for (int i=0; i<num_tx_lanes; i++) begin
      $sformat(instance_name, "tx_lane_agents[%0d]", i);
      // instantiate tx agent
      tx_lane_agents[i] = er_j204_lane_agent::type_id::create(instance_name, this);
      $sformat(instance_name, "TX_lane_config_%0d", i);
      // instantiate tx agent's config
      tx_lane_agents[i].cfg = er_j204_lane_config::type_id::create(instance_name, this);
      tx_lane_agents[i].cfg.lane_id = i;
      tx_lane_agents[i].cfg.lane_type = TX;
    end

Is it better to have list of configs instantiated in the env and then agent is passed the pointer of the config in env's build phase, something like
  tx_lane_agent[i] = cfg_l[i];

2. The config contains active_passive fields and many other parameters. active_passive won't be generated until randomization of cfg will happen. If I wait till start of simulation phase then how will I instantiate driver and monitor in the agent? active_passive information is required to instantiate driver and sequencer.

thanks
shrawan

dave_59
dave_59
Forum Moderator
10913 posts
August 31, 2017 at 9:48 am

In reply to shrawan_vaidya:
set_type_override() must be used before calling create(). Typically you do the override from a component at a higher level, like your test if necessary. What most people do is a uvm_config_db::set() in the env or test, and a corresponding uvm_config_db::get() in each agent.

— Dave Rich, Verification Architect, Siemens EDA

shrawan_vaidya
shrawan_vaidya
Full Access
11 posts
September 01, 2017 at 1:01 am

In reply to dave_59:

Thanks Dave!

Can I make provisions for both options given below -
1. Having user create his own config in the test and do set(). In the env I must then have a get() to get the config set from top
2. If in env get() fails I can do a ::create() to create a config. In this case any set_override() from the top will be effective as well.

I am still not able to understand where the config is randomized. If created in the test, no question of randomizing it again. We can simply do set() and get().
But if no one sets it from test, and it gets created in the env using ::create(), I need to randomize() it. Does this make sense?

thanks
shrawan

chr_sue
chr_sue
Full Access
3903 posts
September 01, 2017 at 4:45 am

In reply to shrawan_vaidya:

I believe you are mixing 2 things together.
Creating a config object has nothing to do with the config_db.
If you have created a config object you can pass this to the config_db using a config_db set.
Normally you are doing this either in the test or in the top_env (test is the prefered place).
If the config_object is in the config_db you can retrieve this object from any other place in the testbench hierarchy or even in the sequences. If the get Fails you are doing something wrong, because the object is in the config_db. Then you should debug your get and not simply create the same object twice.

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