Stats

  • Locked Locked
  • Replies 5
  • Subscribers 65
  • Views 15251
  • 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

Exclude functional coverage for particular test

Ravisinha
Hi All, I am running regression for my SOC and that list contains the register write-read test also, and because of that my vr_ad functional coverage is 100%. Is that any way/switch by which for register write-read testcase i can disable collecting the functional coverage in SPECMAN. Thanks in advance.

  • An excellent question, as this highlights the danger of relying on automatic coverage.

    In vr_ad you can constrain the has_coverage field of your vr_ad_map or vr_ad_reg_file. By default it's TRUE, but if you constrain it to FALSE then you won't get any coverage collected. So, in your test file you can do something like:

    extend my_env {
      keep not my_map.has_coverage;
    };

    The nice thing about this is that has_coverage simply disables the emission of the coverage event, so it doesn't change the coverage model itself. This means all your tests can be merged without conflict.

  • Hi Stephen, Thanks for ur help, In my verification environment vr_ad is getting loaded at last so i was not able to do the above line of code because till that time my_env was no such feild("reg_mem.addr_maps") so what i did is, i extended vr_ad_group and did that. extend vr_ad_group{ keep soft has_coverage == FALSE; };

  •  Surely your test file would be the last one loaded, so you could have put the extend in there?

  • Yes that's true but the problem here was I was using the legacy code of my client and in the testcase only they are calling the setup file in which vr_ad is also getting compiled.

  • This should not cause a problem. For example:

    // test.e
    <'
    import my_env_config;
    extend my_env {
      keep not mem_map.has_coverage;
    };
    '>

    If you're still having difficulty, please can you file a service request on http://support.cadence.com/ so we can organise some more appropriate support?

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.