• 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. Reg: generating a .vsif file before running a regression...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 21129
  • 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

Reg: generating a .vsif file before running a regression in vManager 15.10

Shobith
Shobith over 9 years ago

Hello,

We are trying to understand the vManager tool and here are the some doubts we are stuck with:

1. How do we create a .vsif file to run a regression in the vManager tool?

2. How to link the spec, verification plan, and the test case. What we have figured out is how to generate a vplan with respect to the specification document. But, How do we link already generated vplan with the .vsif file and run a regression in vManager? 

Thank you in advance.

Regards,

Shobith E.

  • Cancel
Parents
  • StephenH
    StephenH over 9 years ago

    Hi Shobith.

    The attributes like sv_seed get copied into environment variables that you can use inside your run_script. For the seed, you have $BRUN_SV_SEED, and this would be used in your run_script as:

    irun -R -svseed $BRUN_SV_SEED

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • StephenH
    StephenH over 9 years ago

    Hi Shobith.

    The attributes like sv_seed get copied into environment variables that you can use inside your run_script. For the seed, you have $BRUN_SV_SEED, and this would be used in your run_script as:

    irun -R -svseed $BRUN_SV_SEED

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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