Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 13886
  • 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

Problem with spectremdl.

AnnaS
Hi All,

I am facing some problem using this command:

spectremdl -batch Netlist.mdl -design nmos_test.scs  

The error log is:

.../linux/mmsim6.0.ISR26/tools.lnx86/bin/spectre: line 171:  2013 Segmentation fault      (coredumped) .../linux/mmsim6.0.ISR26/tools.lnx86/spectre/bin/spectre =mdl Netlist.mdl nmos_test.scs
 It will be great if someone can advise how to handle this.

Thanks,Anna
  • Andrew Beckett
    Anna,

    It's impossible to debug a generic internal error with the data that reproduced it, but I would say that that's rather an old MMSIM version (4-5 years old). You'd be best testing it with MMSIM71 and then reporting it to Cadence support if it is still a problem. It may have been fixed in the meantime.

    Regards,

    Andrew
  • AnnaS

    Hi Andrew,

    Thank you for advise. I have tried with versions: MMSIM7101_37E, MMSIM7101_66E, MMSIM7202 but problem still appears. Here is the log from:

    1. MMSIM7101_37E:

    [1]+  Aborted                 (core dumped) ${APPBINPATH}/${PROGRAM} "$@" 0<&3

    2. MMSIM7101_66E, MMSIM7202

     spectremdl: Command not found.

    Regards,

    Anna

     

  • Andrew Beckett
    Hi Anna,

    My guess is from the "command not found" cases that the installation does not have the "tools" link at the root of the MMSIM installation.

    MMSIM72 has not been released yet, so I'm guessing you must have some "early adopter" build.

    That said (assuming that the naming convention for your installations matches our version numbers (roughly), it would seem that there is still a problem with your examples in recent subversions.

    So my advice is to provide those testcases to Cadence Customer Support (you can log a service request via sourcelink - links to support should be found on the drop down menus on the Cadence web site), so that we can investigate, try to find workarounds, and get the problem to R&D to fix the bug.

    Best Regards,

    Andrew

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.