Jump to content

mastrick

Members
  • Content Count

    48
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Like
    mastrick got a reaction from ljepson74 in randomize() with inside syntax   
    Also, you might want to keep your randomize() call outside the assert().  Otherwise, simulators may not call the randomize at all if you disable assertions (e.g. to temporarily work around a problem).  You can assign the return from randomize() to a variable and then assert that variable.
  2. Like
    mastrick got a reaction from tudor.timi in randomize() with inside syntax   
    Also, you might want to keep your randomize() call outside the assert().  Otherwise, simulators may not call the randomize at all if you disable assertions (e.g. to temporarily work around a problem).  You can assign the return from randomize() to a variable and then assert that variable.
  3. Like
    mastrick got a reaction from wszhong631 in the parent-child relationship of add method of uvm_phase   
    You are correct.  That is Mantis 4427, whose fix did not get into the UVM 1.2 release.
  4. Like
    mastrick got a reaction from twk1156 in initialization sequence question   
    If you are using run-time phasing, you simply need to have your environment start the init sequence in some phase before main (perhaps the configure phase), holding the objection until that sequence completes, and then tell test developers that they must run their sequences in main phase (which is the intent of main phase).
×
×
  • Create New...