• 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. xmsim is not exiting the simulation for this error

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 65
  • Views 19604
  • 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

xmsim is not exiting the simulation for this error

ChinookPass
ChinookPass over 5 years ago

xmsim is not exiting the simulation for this error. It is unusual for the simulator to not exit for an error. I have just started using uvm and this is occurring during the randomization step for a sequencer item.

xmsim: *E,RNDCNSTE

I am using -EXIT on the command line.

I am using Xcelium 19.03-s013.

Any insights are appreciated. Thanks.

-Jim

  • Cancel
Parents
  • StephenH
    StephenH over 5 years ago

    That's done by design because the randomisation failure is expected to be handled by the testbench. There are plenty of valid use cases where you expect randomisation to fail and you don't want that to reflect as a failed test. For example in CPU verification you try 1st pass to randomise all the "ideal" constraints, if it fails you disable some of the constraints and try again so that you still get an instruction generated, but it might be not quite your preferred one.
    If you really want the test to stop and fail due to over-constraint, simply upgrade it to an error using the xrun option "-xmfatal RNDCNSTE".

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

    That's done by design because the randomisation failure is expected to be handled by the testbench. There are plenty of valid use cases where you expect randomisation to fail and you don't want that to reflect as a failed test. For example in CPU verification you try 1st pass to randomise all the "ideal" constraints, if it fails you disable some of the constraints and try again so that you still get an instruction generated, but it might be not quite your preferred one.
    If you really want the test to stop and fail due to over-constraint, simply upgrade it to an error using the xrun option "-xmfatal RNDCNSTE".

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • ChinookPass
    ChinookPass over 5 years ago in reply to StephenH

    Thanks for the information, StephenH. This is very helpful.

    -Jim

    • 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