• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. Migration from UVM1.1 to UVM1.2: Problems with Register...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 66
  • Views 17316
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Migration from UVM1.1 to UVM1.2: Problems with Register Viewer + Warnings

zoombarabar
zoombarabar over 9 years ago

Dear All,

I have recently migrated from using UVM 1.1 to UVM 1.2. I have noticed there are additional warnings and problems with UVM Register Viewer in Incisive 14.10.011 version.

UVM_WARNING : reporter [UVM/RSRC/NOREGEX] a resource with meta characters in the field name has been created "regmodel.P1_REGS"

UVM_WARNING : reporter [UVM/RSRC/NOREGEX] a resource with meta characters in the field name has been created "regmodel.P2_REGS"

Additionally, I am not able to view any registers in the register viewer. Any support regarding the same would be very helpful.

Thank you.

Greetings. 

Sagar.

  • Cancel
  • StephenH
    StephenH over 9 years ago

    Hi Sagar.

    This might be related to which UVM library version you use, can you let us know if it's still a problem when you switch to the CDNS-1.2 (per your other topic on this forum).

    Additionally, can you explain how you generated your UVM_REG class definitions? Did you use a builder tool like reg_verifier, or something else?

    Regards,

    Steve

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • zoombarabar
    zoombarabar over 9 years ago

    Hi Steve,

    this is a new problem I am facing (that I am not able to see the registers in the register viewer) after successful migration to CDNS1.2.

    When I was using 1.1, there was no problem with the UVM register viewer (but with the hdl path definition), but after migration, I could open the register viewer, but with no register content inside. The only changes made was to migrate from UVM1.1d to 1.2.

    Regards, 

    Sagar.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • rkaur9
    rkaur9 over 3 years ago in reply to StephenH

    Hello Stephen,

    i am running one uvm environment on uvm1.1d version , where i am trying to factory override monitor ,but getting error in xrun:

    is it not required to declare another analysis port in overriden class apart  from base monitor:

    please suggest,thnks

    UVM_INFO classes_v/axi_agent.sv(37) @ 0: uvm_test_top.m_env.m_axi_agent [UMONITOR] axi_agent
    UVM_INFO @ 0: uvm_test_top.m_env.m_axi_agent.m_driver [uvm_test_top.m_env.m_axi_agent.m_driver] Build driver
    UVM_INFO classes_v/overide_monitor.sv(22) @ 0: uvm_test_top.m_env.m_axi_agent.m_monitor [OVERRIDE MONITOR BUILD]
    UVM_INFO classes_v/overide_monitor.sv(24) @ 0: uvm_test_top.m_env.m_axi_agent.m_monitor [OVERRIDE MONITOR BUILD] override monitor -----------------------------------------
    Name Type Size Value
    -----------------------------------------
    m_monitor override_monitor - @3611
    aport uvm_analysis_port - @3723
    -----------------------------------------

    UVM_INFO classes_v/axi_scoreboard.sv(24) @ 0: uvm_test_top.m_env.m_axi_scoreboard [SCOREBOARD] BUILD
    xmsim: *E,TRNULLID: NULL pointer dereference.
    File: /pkg/cadence-xcelium-/21.02.001/i686-linux/tools/methodology/UVM/CDNS-1.1d/sv/src/base/uvm_port_base.svh, line = 463, pos = 38
    Scope: worklib.uvm_pkg::uvm_port_base#(uvm_pkg::uvm_tlm_if_base#(T,T))::connect
    Time: 0 FS + 13
    Verilog Stack Trace:
    0: function worklib.uvm_pkg::uvm_port_base#(uvm_pkg::uvm_tlm_if_base#(T,T))::connect at /pkg/cadence-xcelium-/21.02.001/i686-linux/tools/methodology/UVM/CDNS-1.1d/sv/src/base/uvm_port_base.svh:463
    1: function worklib.$unit_0x746ee0b2::axi_agent@2763_4.connect_phase at ./classes_v/axi_agent.sv:42
    2: function worklib.uvm_pkg::uvm_connect_phase@685_2.exec_func at /pkg/cadence-xcelium-/21.02.001/i686-linux/tools/methodology/UVM/CDNS-1.1d/sv/src/base/uvm_common_phases.svh:96
    3: function worklib.uvm_pkg::uvm_bottomup_phase@685_2.execute at /pkg/cadence-xcelium-/21.02.001/i686-linux/tools/methodology/UVM/CDNS-1.1d/sv/src/base/uvm_bottomup_phase.svh:108
    4: function worklib.uvm_pkg::uvm_bottomup_phase@685_2.traverse at /pkg/cadence-xcelium-/21.02.001/i686-linux/tools/methodology/UVM/CDNS-1.1d/sv/src/base/uvm_bottomup_phase.svh:81
    5: function worklib.uvm_pkg::uvm_bottomup_phase@685_2.traverse at /pkg/cadence-xcelium-/21.02.001/i686-linux/tools/methodology/UVM/CDNS-1.1d/sv/src/base/uvm_bottomup_phase.svh:61
    6: function worklib.uvm_pkg::uvm_bottomup_phase@685_2.traverse at /pkg/cadence-xcelium-/21.02.001/i686-linux/tools/methodology/UVM/CDNS-1.1d/sv/src/base/uvm_bottomup_phase.svh:61
    7: function worklib.uvm_pkg::uvm_bottomup_phase@685_2.traverse at /pkg/cadence-xcelium-/21.02.001/i686-linux/tools/methodology/UVM/CDNS-1.1d/sv/src/base/uvm_bottomup_phase.svh:61
    8: task worklib.uvm_pkg::uvm_phase@728_2.execute_phase at /pkg/cadence-xcelium-/21.02.001/i686-linux/tools/methodology/UVM/CDNS-1.1d/sv/src/base/uvm_phase.svh:1168
    9: process in worklib.uvm_pkg::uvm_phase::m_iterate_through_phases at /pkg/cadence-xcelium-/21.02.001/i686-linux/tools/methodology/UVM/CDNS-1.1d/sv/src/base/uvm_phase.svh:1997

    NOTE: You may recompile using -linedebug, in case of any discrepency in line/file information in above call stack

    agent.sv


    function void axi_agent::connect_phase(uvm_phase phase);
    m_driver.seq_item_port.connect(m_seqr.seq_item_export);
    -> m_monitor.mon_aport.connect(agent_aport);   
    endfunction

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information