• 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. How to disable vr_axi checks

Stats

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

How to disable vr_axi checks

deviprasada
deviprasada over 11 years ago

Hi I am new to vr_axi enviorment,in my testbench i have some axi interfaces. I want to understand how to disable vr_axi checks like below

"ERR_VR_AXI190***"

  • Cancel
  • StephenH
    StephenH over 11 years ago

    Hi.

    This is done using the set_check() method, either at the start of the test, or even just during a part of the test, since you can switch the errors back on again if you wish. Here's a simple time-zero example.

    extend sys {
      run() is also {
        set_check("...ERR_VR_AXI190...",WARNING); // or IGNORE or ERROR_CONTINUE etc.
      };
    };

    More information can be found in the "cdnshelp"  tool by searching for "set_check". There are also vr_axi examples of using set_check in the vr_axi package itself, e.g. in the file:

    VIPCAT11.30.007-s/packages/vr_axi/examples/e/axi3/vr_axi_config_template.e

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • deviprasada
    deviprasada over 11 years ago

    Thanks  i am using axi vip enviornment in my enviornment,on top of axi there is uvm sv wrapper for doing transactions , in test enviornment i am doing like below,but i am not seeing any effect with this . I dont want these axi messages to dumped in irun.log .Just want to disable all vr_axi_agent_monitor checks

     vr_axi::set_vip_cmd("set_check \"...VR_AXI**...\" IGNORE");

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 11 years ago

    You were close but the command is "set check" not "set_check". Here's an example from the examples directory, the file is VIPCAT11.30.007-s/vips/amba_axi/vr_axi/examples/sv/axi3/interface/vr_axi_test.sv:

    vr_axi::set_vip_cmd("set check \"...VR_AXI242...\" IGNORE");
     

    You should probably not use the stars in the pattern match expression either, the ellipsis (...) is equivalent to ".*" so already matches what you're trying to match with the star.

    BTW, why do you want to turn off all the AXI checks in the log? Surely you want to know about protocol errors, otherwise what's the point of running a VIP?

    If you really don't want any checks at all, then you would do better to turn off completely rather than letting them run and just masking the messages. There is a "has_checks" field in vr_axi_master_agent_configand vr_axi_slave_agent_config which you can use to disable the checks completely.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • deviprasada
    deviprasada over 11 years ago

    Thanks,i got it. Now tool ignores the error with below command.

    vr_axi::set_vip_cmd("set check \"...VR_AXI242...\" IGNORE");

    I dont want to disable all axi checks i want to disable only one check which checks for wdata when wvalid is low. Error message is something like this. I want to know whether we can disable only this particular check below. These error statements are occupying lot of log space

     ERR_VR_AXI*_MASTER_BAD_DATA_SIGNAL_VALUE_WHEN_WVALID_LOW

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 11 years ago

     OK, sounds like you're sorted then. You confused me when you said "Just want to disable all vr_axi_agent_monitor checks". :-)

    • 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