Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 4101
  • 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

Simvision: xmsim: *E,TRRANGEC: range constraint violation

quantumion

Dear community,

I run some simulations with xrun and I get the following error:

--------------------------------

xmsim: *E,TRRANGEC: range constraint violation.
File: ../VHDL/system1.vhd, line = 482, pos = 33
Scope: device1.dut:INST_system1:Events
Time: 102562 NS + 8

Set "rangecnst_severity_level" xmsim tcl variable to ignore this error.
Type `help -variable rangecnst_severity_level` on xcelium> prompt.

xcelium>

--------------------------------

I note that this only happens with ta subset of 5 out many test-benches.

Then the way to suppess the error, thus having a workaround to make the simulation run, is by using the proposed command in the Simvision Console window:

set rangecnst_severity_level ignore

Question

How severe could the issues be in the first place? Can it be considered reliable, to suppress the error by lowering the severity level, or would this run the simulation, ignoring the conditions that cause this error?

In the description of the commnand: 

"VHDL simulation errors and stop simulation if range constraint is detected. This variable allows range constraint to proceed the simulation"

 

How can I read/find which constraints are 1. located 2. then removed/ignored?

Thank you in advance

Parents

  • The range constraint is VHDL's terminology for the dimensions of the array / vector, thus a range constraint violation means that you're trying to access an element index that's outside of the declared bounds of the vector.

    In simple terms, if your vector is "std_logic_vector (7 downto 0)" and you try to access element "8" you would get the range constraint violation.

    The error message points you to the offending line of code so it should be fairly simple to run in GUI mode with "-access +r" so that you can view signal values. Run the simulation till it hits the error, open the source browser window in SimVision and hit the "yellow arrow" button that takes you to the current line of source code. If you have value annotation enabled, then you'll see the offending index value (assuming it's a variable and not a constant, obviously the constant would be visible anyway). SimVision should show you the bounds of the vector as well.

Reply

  • The range constraint is VHDL's terminology for the dimensions of the array / vector, thus a range constraint violation means that you're trying to access an element index that's outside of the declared bounds of the vector.

    In simple terms, if your vector is "std_logic_vector (7 downto 0)" and you try to access element "8" you would get the range constraint violation.

    The error message points you to the offending line of code so it should be fairly simple to run in GUI mode with "-access +r" so that you can view signal values. Run the simulation till it hits the error, open the source browser window in SimVision and hit the "yellow arrow" button that takes you to the current line of source code. If you have value annotation enabled, then you'll see the offending index value (assuming it's a variable and not a constant, obviously the constant would be visible anyway). SimVision should show you the bounds of the vector as well.

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.