Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 13484
  • 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

Importing Verilog-A code

Hosseineslahi7

Hi All,

I wish you are well. 
I have imported a Verilog-A code of a specific model of a transistor in Cadence. I could create transistor symbol and run simulations for a few days. However, after a while, I saw this error once I tried to run the same simulations:
"Internal error found in spectre during AHDL read-in, during circuit read-in, during hierarchy flattening.

Encountered a critical error during simulation. Please run `mmsimpack' to pack the test case (use mmsimpack -h option to get detailed usage), and submit the case via Cadence Online Support, including the package tar file and any other information that can help identify the problem.
    FATAL (SPECTRE-18): Segmentation fault."

This is weird because it was working and, then, stopped suddenly. I wonder if anyone sees something like this before? And, is there any solution?
Cheers,
Parents
  • Andrew Beckett

    You should do what the error message says - report it to Cadence support. It's almost certainly a bug, and diagnosing it without seeing the model and a testcase that demonstrates the problem is going to be hard. Something must have changed to trigger the error (simulators are general deterministic beasts), but it's almost certainly data dependent.

    If you're not using a very recent Spectre version, you might want to try with something that is as up to date as possible (e.g. the latest SPECTRE19.1 hot fix) as it's quite possible that whatever issue it's hitting has been solved already.

    Andrew.

Reply
  • Andrew Beckett

    You should do what the error message says - report it to Cadence support. It's almost certainly a bug, and diagnosing it without seeing the model and a testcase that demonstrates the problem is going to be hard. Something must have changed to trigger the error (simulators are general deterministic beasts), but it's almost certainly data dependent.

    If you're not using a very recent Spectre version, you might want to try with something that is as up to date as possible (e.g. the latest SPECTRE19.1 hot fix) as it's quite possible that whatever issue it's hitting has been solved already.

    Andrew.

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.