• 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. I observe following error when running xrun -sv

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 69
  • Views 7472
  • 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

I observe following error when running xrun -sv

Tarique mohd
Tarique mohd 10 months ago

Design hierarchy summary:
Instances Unique
Modules: 2 2
Verilog packages: 0 1
Registers: 15 15
Scalar wires: 12 -
Always blocks: 2 2
Initial blocks: 4 4
Pseudo assignments: 4 -
Simulation timescale: 100ps
Writing initial simulation snapshot: worklib.tb_light_fsm:sv
Loading snapshot worklib.tb_light_fsm:sv .................... Done
xcelium> source /eda/cadence/2023-24/RHELx86/XCELIUM_23.03.007/tools/xcelium/files/xmsimrc
xcelium> run
xmsim: *F,INTERR: INTERNAL EXCEPTION
Observed simulation time : 0 FS + 0
-----------------------------------------------------------------
The tool has encountered an unexpected condition and must exit.
Contact Cadence Design Systems customer support about this
problem and provide enough information to help us reproduce it,
including the logfile that contains this error message.
TOOL: xmsim(64) 23.03-s007
HOSTNAME: icdtsmc28nm.ewi.tudelft.nl
OPERATING SYSTEM: Linux 4.18.0-553.22.1.el8_10.x86_64 #1 SMP Wed Sep 25 09:20:43 UTC 2024 x86_64
MESSAGE: T(0): sv_seghandler - trapno -1 addr(0x4aa4ccc)
Stream rts_xfer
-----------------------------------------------------------------
csi-xmsim - CSI: Cadence Support Investigation, sending details to /users/mtarique/28nm/T28HPCP/SV_code/xmsim_4106232.err
csi-xmsim - CSI: investigation complete, send /users/mtarique/28nm/T28HPCP/SV_code/xmsim_4106232.err to Cadence Support

  • Cancel
Parents
  • tpylant
    tpylant 10 months ago

    Did you look at the /users/mtarique/28nm/T28HPCP/SV_code/xmsim_4106232.err file?

    Tim

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • Tarique mohd
    Tarique mohd 10 months ago in reply to tpylant

    Yes I saw message which direct to Cadence support, not sure about  the root cause, the message is as follows

    The tool has encountered an unexpected condition and must exit.
    Contact Cadence Design Systems customer support about this
    problem and provide enough information to help us reproduce it,
    including the logfile that contains this error message.
    TOOL: xmsim(64) 23.03-s007
    HOSTNAME: icdtsmc28nm.ewi.tudelft.nl
    OPERATING SYSTEM: Linux 4.18.0-553.22.1.el8_10.x86_64 #1 SMP Wed Sep 25 09:20:43 UTC 2024 x86_64
    MESSAGE: T(0): sv_seghandler - trapno -1 addr(0x4aa4ccc)
    Stream rts_xfer
    -----------------------------------------------------------------

    csi-xmsim - CSI: Cadence Support Investigation, recording details
    External Code in function: <unavailable> offset -65516
    External Code in function: <unavailable> offset -65536
    External Code in function: <unavailable> offset -65535
    Simulator Snap Shot: root (SSS_ROOT) in snapshot worklib.tb_light_fsm:sv (SSS)
    Intermediate File: root (IF_ROOT) in snapshot worklib.tb_light_fsm:sv (SSS)
    Intermediate File: root (IF_ROOT)
    Simulator Snap Shot: dynlib (SSS_DYNLIB) in snapshot worklib.tb_light_fsm:sv (SSS)
    Intermediate File: data block (IF_BLK) in snapshot worklib.tb_light_fsm:sv (SSS)
    Code Item: root (COD_ROOT)
    External Code in function: <unavailable> offset -65500
    External Code in function: <unavailable> offset -65518
    User Code in function: <unavailable> offset 42600727
    csi-xmsim - CSI: investigation complete took 0.010 secs, send this file to Cadence Support

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Tarique mohd
    Tarique mohd 10 months ago in reply to tpylant

    Yes I saw message which direct to Cadence support, not sure about  the root cause, the message is as follows

    The tool has encountered an unexpected condition and must exit.
    Contact Cadence Design Systems customer support about this
    problem and provide enough information to help us reproduce it,
    including the logfile that contains this error message.
    TOOL: xmsim(64) 23.03-s007
    HOSTNAME: icdtsmc28nm.ewi.tudelft.nl
    OPERATING SYSTEM: Linux 4.18.0-553.22.1.el8_10.x86_64 #1 SMP Wed Sep 25 09:20:43 UTC 2024 x86_64
    MESSAGE: T(0): sv_seghandler - trapno -1 addr(0x4aa4ccc)
    Stream rts_xfer
    -----------------------------------------------------------------

    csi-xmsim - CSI: Cadence Support Investigation, recording details
    External Code in function: <unavailable> offset -65516
    External Code in function: <unavailable> offset -65536
    External Code in function: <unavailable> offset -65535
    Simulator Snap Shot: root (SSS_ROOT) in snapshot worklib.tb_light_fsm:sv (SSS)
    Intermediate File: root (IF_ROOT) in snapshot worklib.tb_light_fsm:sv (SSS)
    Intermediate File: root (IF_ROOT)
    Simulator Snap Shot: dynlib (SSS_DYNLIB) in snapshot worklib.tb_light_fsm:sv (SSS)
    Intermediate File: data block (IF_BLK) in snapshot worklib.tb_light_fsm:sv (SSS)
    Code Item: root (COD_ROOT)
    External Code in function: <unavailable> offset -65500
    External Code in function: <unavailable> offset -65518
    User Code in function: <unavailable> offset 42600727
    csi-xmsim - CSI: investigation complete took 0.010 secs, send this file to Cadence Support

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • tpylant
    tpylant 10 months ago in reply to Tarique mohd

    It's a time 0 simulation crash. You would hope there would be some clues to what caused it but it is pointing to external code in an unavailable function name.

    You can try running with a different version but I'm just shooting in the dark.

    Tim

    • 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.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information