Stats

  • Locked Locked
  • Replies 2
  • Subscribers 66
  • Views 13970
  • 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

cross coverage between different vr_ad registers

lakku

Hi,

I am trying to achieve cross coverage b/w two different vr_ad registers, like when register -1 is accessed then i want to get the cross coverage on the register -2 fields.. (Assume that register2 is configured with some values before register-1 access)..  i tried many ways but i failed to see the coverage collection for such items..

Please let me know whether it is possible?? If not is it possible to get the cross coverage on diffrent register fields?? My coverage scenario is as follows..  Need solution for this

Ex scenario:

extend  vr_ad_reg {
   event reg_1_e;
};

extend REG2 vr_ad_reg {
  cover reg_1_e is {
   cross REG2_FLD1,REG2_FLD2,REG2_FLD3;
  };
};

extend REG1 vr_ad_reg {
 post_access(direction : vr_ad_rw_t) is only {
    if direction == READ {
       emit reg_1_e;
    };
};

  • StephenH

    The example you posted won't work because there is one reg_1_e event for each instance of vr_ad_reg, it's not one event shared across all struct instances.

    What you need to do is make a pointer to REG2 inside REG1, so that you can emit the event on REG2.
    Try something along these lines:

    extend REG2 vr_ad_reg {
      event reg_1_e;
      cover reg_1_e is { ... };
    };
    extend REG1 vr_ad_reg {
      !p_reg2 : REG2 vr_ad_reg;
      post_access(direction:vr_ad_rw_t) is also {
        if direction==READ and p_reg2 != NULL {
          emit p_reg2.reg_1_e;
        };
      };
    };
    extend MY vr_ad_reg_file {
      post_generate() is also {
        reg1.p_reg2 = reg2;
      };
    };

  • lakku

    Hi Stephen,

     Thank you very much for the solution . It is working now..

    Regards

    Lakku

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.