Jump to content

dave_59

Members
  • Content Count

    385
  • Joined

  • Last visited

  • Days Won

    20

dave_59 last won the day on August 28 2018

dave_59 had the most liked content!

2 Followers

About dave_59

  • Rank
    Senior Member

Contact Methods

  • Website URL
    http://go.mentor.com/drich

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Linc, Your code works correctly on three other EDAPlayground simulators.
  2. @ljepson74, All you have to do is import uvm_pkg::uvm_enum_wrapper; and you've got this handy little class to use, you don't even need to have a class based testbench.
  3. Verbosity has already been processed before you get to the report catcher. https://accellera.mantishub.io/view.php?id=7211
  4. The UVM field macros do not handle OOP very well, and is one of the many reason we do not recommend using them. It would be much simpler and more efficient to use the streaming operator exactly as you wrote it in a do_pack method.
  5. The link answers the question on how to apply a distribution to any set of constraints. The dist construct only works with explicit values.
  6. https://verificationacademy.com/forums/systemverilog/distributed-weightage-constraint#reply-46525
  7. You always incur overhead for automation. Performance rapidly deteriorates as you introduce dependencies with other random variables. For example, suppose you need 8 unique values between 10 and 20. You are going be calling $urandom_range many extra times throwing away values that don't meet the constraints. And it becomes very difficult to know when there are no solutions, and you end up in infinite loops looking for solutions that are very hard to find or don't exist. This is what a constraint solver does for you. Since constraints are tied to the class inheritance system, they provide
  8. Give your error message a unique ID. Use set_report_severity_id_override to change the severity of that ID from UVM_ERROR to UVM_INFO. Then call get_id_count at the end of your test to make sure it's non-zero.
  9. The return code usually indicates successful completion of the tool and is unrelated to completion of the test. Non-zero return codes would be OS specific error codes. The SystemVerilog standard way of indicating pass/fail status is using the $info/$warning/$error/$fatal messages. Most tools are essentially catch the UVM reports and convert them to one of the SystemVerilog messages. They also have a way of detecting the most severe message issued during a run and you can use that information for determining pass/fail status.
  10. This was recently discussed here. The assertion should fail because disable_assert is false at the start of the attempt.
  11. Works for me in Questa, and in the VCS on edaplayground.com. I mean I get no compilation errors, did not check the functionality of your code. Maybe you are using an older version, Also, I suggest using *.SystemVerilog as file extension of using *.v and -sverilog switch. That helps keep legacy Verilog files working.
×
×
  • Create New...