• 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 reinvoke a simulation by changing some testbench...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 18310
  • 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 reinvoke a simulation by changing some testbench code in Simvision?

Saru K S
Saru K S over 6 years ago

In simvision how to reinvoke a simulation when some testbench code is changed such that the changes are included after the reinvoke ?

Thanks in advance!

  • Cancel
Parents
  • StephenH
    StephenH over 6 years ago

    If you compiled and ran with a single xrun command, then the SimVision menu "Simulation -> Reinvoke Simulator" does exactly what you want, it'll recompile and load the new simulation snapshot ready to re-run.

    If you compiled using a separate xrun command, you might get away with re-running that manually, then in SimVision use the reinvoke as above. The only gotcha is that xrun puts a NFS lock on the xcelium.d (working) directory to prevent you recompiling whilst running the simulation. You can bypass that with the -nolock switch but then the onus is on you to avoid crashing simulations by recomipling. We don't really recommend this flow at present.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Reply
  • StephenH
    StephenH over 6 years ago

    If you compiled and ran with a single xrun command, then the SimVision menu "Simulation -> Reinvoke Simulator" does exactly what you want, it'll recompile and load the new simulation snapshot ready to re-run.

    If you compiled using a separate xrun command, you might get away with re-running that manually, then in SimVision use the reinvoke as above. The only gotcha is that xrun puts a NFS lock on the xcelium.d (working) directory to prevent you recompiling whilst running the simulation. You can bypass that with the -nolock switch but then the onus is on you to avoid crashing simulations by recomipling. We don't really recommend this flow at present.

    • Cancel
    • Vote Up +1 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