• 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. Custom IC Design
  3. Spectre error when simulating with extracted view

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 125
  • Views 18497
  • 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

Spectre error when simulating with extracted view

Pyroblast
Pyroblast over 10 years ago

Hi,

As the topic says, when I do a simulation with the extracted view I get this error:


ERROR (SFE-400): multiple case sensitive symbols have been created which match the case insensitive symbol `C2'.

Does anyone know what this means? How can I solve this?

This C2 is a MOM CAP ASY MM.

From what I can understand there might be an issue with this cap, but don't know what and why. Doesn't make any sense.


Regards.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    OK, I should have searched for the text of the message, not the SFE-400 bit. I've reproduced it with the model files you're using (or a very similar version). I think you must have cut-and-pasted that incorrectly (it was SFE-404 in the log file you sent me too).

    It turns out that the error message was actually SFE-404 (I tried a variety of versions and they were all SFE-404):

        ERROR (SFE-404): Multiple case sensitive symbols have been created which match the case insensitive symbol `C1'.

    This is covered in solution 11540588 (I know you won't be able to see this), and is related to the fact that the model files have insensitive=yes enabled. The issue is that there is currently a limitation where hierarchical names can't have a mixture of case sensisitive and insensitive components. It is happening because you have the option in your netlist:

    saveOptions options save=allpub pwr=all currents=all useprobes=yes

    This is causing it to attempt to save the currents for both capacitors and this causes the message. If you rename one of the capacitors, or don't save all currents, this won't be a problem. I don't believe it will affect the circuit though.

    It's on the list of things to be fixed - it's just not trivial to fix so hasn't happened yet. CCR 1375493 is one such CCR about this.

    Kind Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    OK, I should have searched for the text of the message, not the SFE-400 bit. I've reproduced it with the model files you're using (or a very similar version). I think you must have cut-and-pasted that incorrectly (it was SFE-404 in the log file you sent me too).

    It turns out that the error message was actually SFE-404 (I tried a variety of versions and they were all SFE-404):

        ERROR (SFE-404): Multiple case sensitive symbols have been created which match the case insensitive symbol `C1'.

    This is covered in solution 11540588 (I know you won't be able to see this), and is related to the fact that the model files have insensitive=yes enabled. The issue is that there is currently a limitation where hierarchical names can't have a mixture of case sensisitive and insensitive components. It is happening because you have the option in your netlist:

    saveOptions options save=allpub pwr=all currents=all useprobes=yes

    This is causing it to attempt to save the currents for both capacitors and this causes the message. If you rename one of the capacitors, or don't save all currents, this won't be a problem. I don't believe it will affect the circuit though.

    It's on the list of things to be fixed - it's just not trivial to fix so hasn't happened yet. CCR 1375493 is one such CCR about this.

    Kind Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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