• 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. Digital Implementation
  3. ELC not using spectre

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 94
  • Views 14249
  • 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

ELC not using spectre

Khenglish
Khenglish over 11 years ago

ELC seems to always read in files as spice format even though I have "simulator lang = spectre" without the quotes at the top of every .scs file.  In addition I have:

set_var EC_SIM_NAME "spectre"
set_var EC_SIM_TYPE "spectre"

in my script every time before I do any database operation.

These are the types of warnings and errors I am getting (list is really 50x longer mostly referenceing ASSERT.  this is just the end of it):

 [WARNING(db_prepare)] spice syntax warning: ASSERT : no definition of the subckt
 => XVBD_CHECK ASSERT
[WARNING(db_prepare)] spice syntax warning: ASSERT : no definition of the subckt
 => XVBS_CHKFWD ASSERT
[WARNING(db_prepare)] spice syntax warning: ASSERT : no definition of the subckt
 => XVBD_CHKFWD ASSERT
[WARNING(db_prepare)] spice syntax warning: PINMOD : no definition of the subckt
 => XD A C SX PINMOD
[ERROR(db_prepare)] spice syntax error: DIODENWX : illegal port definition of macro
 => XAVD364_1 SUB VDD GND DIODENWX

Notice that is says spice every time instead of spectre.  Maybe this is just a program issue where it always says that spice is used even if it's not, but I have no idea.

So is spice really be used?  And if so then how do I make it use spectre?

  • Cancel
  • great  ljx
    great ljx over 11 years ago

    Dear Khenglish,

    I am so happy when I saw your question ,because I also use the ELC  .I hope that we can contact more times when we are in trouble with the  ELC.

     I have never meet your error,but when you run db_prepare  ,it will load the setup.ss ,so I double that there may be some error in the setup.ss ,and don't forget edit it with the vi , and your subckt  may be not correct ,you can change  "XAVD364_1 SUB VDD GND DIODENWX " to  "XAVD364_1  (SUB VDD GND DIODENWX)   your_pmos_model " .

    I hope it helps 

    thaks,and when you are avaliable ,you can look the   http://www.cadence.com/Community/forums/p/30141/1336431.aspx#1336431 ,

    Liu

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Khenglish
    Khenglish over 11 years ago

    I fixed the one error.  It was because when fixing my file format for ELC I accidentally messed up the inputs to that diode.  It is not giving me an error that it cannot find the ASSERT subckt.  I'm pretty sure this is a spice vs spectre error since ASSERT is not a circuit, but a spectre command to verify proper output.

    Again if anyone knows why ELC is reading files as spice instead of spectre, I would like to know.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • maple
    maple over 11 years ago
    Try adding "simulator lang=spectre" in your netlist and see if it solves the problem.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Khenglish
    Khenglish over 11 years ago
    It's already there.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • KALYANICH
    KALYANICH over 9 years ago

    Hi,

    I'm also using elc for library characterization.

    I've a spectre model file from scl which divides each model(diodes, transistors..) into different sections. When i run the script, i'm getting an error that says a subcircuit is already defined at db_prepare -force command; which is actually defined only once in the model file

    Have you faced any issue like this?

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

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

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