Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 3821
  • 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

ncsim *N COVAUO message

Jeff000

Look into the ncsim log below, the covergroup instances, through are in the same covergoup type, do have their own names. Then why ncsim still output such *N message? 

Is there any potential risk, or how can I get rid of such *N messages?

Thanks.

ncsim: *N, COVAUO: (File: AAA.svh, Line: 45):(Time: 879220 NS + 118) Instance coverage of covergroup instance (worklib.dut_pkg::reg_XXX#(int unsigned,4294967295,0,5)::cg8365_1) inside UVM object will be accumulated with instance coverage of other covergroup instances with the same instance name (dut_pkg.reg_XXX#(int unsigned, -1, 0, 5)::cg.reg_Y_set_w_cov_1) and not separately.
ncsim: *N, COVAUO: (File: AAA.svh, Line: 45):(Time: 879220 NS + 118) Instance coverage of covergroup instance (worklib.dut_pkg::reg_XXX#(int unsigned,4294967295,0,5)::cg8327_1) inside UVM object will be accumulated with instance coverage of other covergroup instances with the same instance name (dut_pkg.reg_XXX#(int unsigned, -1, 0, 5)::cg.reg_Y_set_w_cov_2) and not separately.
ncsim: *N, COVAUO: (File: AAA.svh, Line: 45):(Time: 879220 NS + 118) Instance coverage of covergroup instance (worklib.dut_pkg::reg_XXX#(int unsigned,4294967295,0,5)::cg8129_1) inside UVM object will be accumulated with instance coverage of other covergroup instances with the same instance name (dut_pkg.reg_XXX#(int unsigned, -1, 0, 5)::cg.reg_Y_set_w_cov_3) and not separately.

Parents
  • Thanks Steve for your kind reply！

    One more question,
    In case of moving the covergroup into a uvm_component, then when I attempt to create multiple instances of that covergroup, does that mean it still needs to instantiate the corresponding uvm_componnet with distinct name so as to leverage the UVM hierarchy to identify each instance?
Reply
  • Thanks Steve for your kind reply！

    One more question,
    In case of moving the covergroup into a uvm_component, then when I attempt to create multiple instances of that covergroup, does that mean it still needs to instantiate the corresponding uvm_componnet with distinct name so as to leverage the UVM hierarchy to identify each instance?
Children
No Data

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.