• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. Verification Plan using Eplanner

Stats

  • Locked Locked
  • Replies 19
  • Subscribers 65
  • Views 20403
  • 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

Verification Plan using Eplanner

Manish Verma
Manish Verma over 16 years ago

 Hi....

 

Can anybody explain me How to map checkers(check that statement) into vplan using eplanner?

 

Thanks! 

  • Cancel
  • archive
    archive over 16 years ago
    Hi Manish,

    Which CMS are you using and what version of it?


    Thanks,

    Ilana.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Manish Verma
    Manish Verma over 16 years ago

    Hi Ilana,

    I didn't understand your question(Which CMS are you using and what version of it?)? 

     Previously I am using vManager 8.1 version. But after Chris mail I tried with vManager 8.2 version also. It giving error:

    "export: `-collect_checks_expects=TRUE': not a valid identifier" .

    I am using the same script which I posted previously. Should I have to change any of the script for vManager 8.2 version for CMS.

     

    Thanks!

    Manish 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mahi27
    mahi27 over 13 years ago
    Hi, I used the above script to enable the checkers. But it is enabling all the checkers. I wanted to disable some of the checkers which is not required for the verification. I tried the following : covers.set_cover_check(".*(instance_name)", FALSE); eg. covers.set_cover_check("vr_axi_env.*(axi_evc)",FALSE); but I am getting the following compilation error as : cover expect/check : set_cover_check(".(instance_name)", FALSE); Please let me know how to disable the checkers. Thanks, Mahi
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 13 years ago

    Hello Mahi.

    Please note that set_cover_check() has nothing to do with disabling checks, it only controls the coverage of the checks.

    Assuming that you want to disable the coverage of the checks but keep the checks active for error checking, then set_cover_check()  is the right method to use. However I'm not sure that your patterns are written properly. Note that if you wish to refer to specific instances then the pattern match string should include "e_path=sys." and the full path to the instance.

    Here are the examples from the cdnshelp documentation:

      covers.set_cover_check("my_unit.*", FALSE);

      covers.set_cover_check("my_unit.*check*", TRUE);

      covers.set_cover_check("my_unit.check1(e_path==sys.my_u1)", FALSE); 

    Thus (if we assume axi_evc is an instance under sys) your example becomes:

      covers.set_cover_check("vr_axi_env.*(e_path==sys.axi_evc)", FALSE); 

    If you don't care about which instance to zap:

      covers.set_cover_check("vr_axi_env.*", FALSE);

     

    Steve. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mahi27
    mahi27 over 13 years ago
    Thanks Steve, I tried all the way. but still its viewing in VPLAN. I want to remove from the VPLAN coverage. And under checker coverage , we have two instance: 1)"e Types" and 2) "e instance" I am to disable the checker coverage under "e Instance". But its not effecting anything in "e Types". Please let me know how to disable the checker of "e Type" instance Thanks, Mahi....
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 13 years ago

    Hello Mahi.

    I'm sorry but I don't understand what you're asking.

    If you don't want a check in the vPlan, then you need to remove it from the vPlan, not from the coverage model. You can remove the check from the vPlan by editing it in Enterprise Planner, or by using the local refinements in vManager's vPlan windoe, simply right-click on the check and select "Disable".

    May I suggest that you contact your local Cadence AE or file a service request at http://support.cadence.com/, as I think it would be a lot easier to resolve this if someone can talk with you directly and perhaps do a shared-screen (Webex) session with you to see what you're trying to achieve. 

    Regards,

    Steve. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mahi27
    mahi27 over 13 years ago
    Hi Steve, Yes, I asked the same question with cadence by filing a SR ticket. But still they also gave the same answer what you gave. Anyway .. thanks for your guidance. I will try ... Thanks, Mahiiii
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • mahi27
    mahi27 over 13 years ago
    Hello Steve. I have one doubt ... The set_cover_check() method .. exactly in which location I have to write... Means, in testcase or in the environment .. Thanks, Mahi
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 13 years ago
    It should not matter whether you put this in your environment or your testcases, so long as all the tests execute that code.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
<

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information