• 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. Error found by spectre during circuit read-in--can't find...

Stats

  • Locked Locked
  • Replies 24
  • Subscribers 127
  • Views 22085
  • 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

Error found by spectre during circuit read-in--can't find process.scs library

jdgriggs
jdgriggs over 16 years ago

 Hi everyone

 I've recently have come across an error that have not come across before and i'm hoping one of you may have an answer for me.  For some unapparent reason the input.scs cannot not seem to find my process.scs libs. This just occured but previously Cadence has been running fine.

 here is what the output files gives

----------------------------------------------------------------------------------------------------------------------------------------------------------- 

Environment variable:
    SPECTRE_DEFAULTS=-E
Command line:
    /apps/ic/rel/tools.sun4v/spectre/bin/32bit/spectre -env artist5.1.0  \
        +escchars +log ../psf/spectre.out +inter=mpsc  \
        +mpssession=spectre0_19025_1 -format sst2 -raw ../psf  \
        +lqtimeout 900 input.scs
spectre pid = 19183

Loading /apps/ic/rel/tools.sun4v/cmi/lib/4.0/libinfineon_sh.so ...
Loading /apps/ic/rel/tools.sun4v/cmi/lib/4.0/libnortel_sh.so ...
Loading /apps/ic/rel/tools.sun4v/cmi/lib/4.0/libphilips_sh.so ...
Loading /apps/ic/rel/tools.sun4v/cmi/lib/4.0/libsparam_sh.so ...
Loading /apps/ic/rel/tools.sun4v/cmi/lib/4.0/libstmodels_sh.so ...
spectre (ver. 5.10.41_USR5.053107 -- 31 May 2007).
Includes RSA BSAFE(R) Cryptographic or Security Protocol Software from RSA
        Security, Inc.

Simulating `input.scs' on pearl at 12:48:43 PM, Wed Apr 8, 2009.

Error found by spectre during circuit read-in.
    "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/process.scs" 1501: Unknown
        parameter name `k_wafer' used to initialize parameter `n_spec'.
    "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/process.scs" 1501: Unknown
        parameter name `cor_rx_tt' used to initialize parameter `xcor_rx'.
    "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/process.scs" 1501: Unknown
        parameter name `cor_rx_ff' used to initialize parameter `xcor_rx'.
    "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/process.scs" 1501: Unknown
        parameter name `cor_rx_ss' used to initialize parameter `xcor_rx'.
.
.
.

Created directory ahdlcmi (770)
Created directory
        ahdlcmi/_libs_IBM_PDK_cmrf7sf_rel_Spectre_models_hacap.va.ahdlcmi/
        (770)
Opening directory ahdlcmi (770)
Created directory
        ahdlcmi/_libs_IBM_PDK_cmrf7sf_rel_Spectre_models_mvcap.va.ahdlcmi/
        (770)

Error found by spectre in `dindpw', during circuit read-in.
    "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/dindpw.scs" 151: Syntax error in
        specification of `prpw'.
    "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/dindpw.scs" 194: Unknown
        parameter name `mmatd' found in expression.
Error found by spectre in `divpnp', during circuit read-in.
    "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/divpnp.scs" 228: Syntax error in
        specification of `lbh'.
    "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/divpnp.scs" 279: Unknown
        parameter name `mmatd' found in expression.

.
.
.
.               then finally ends

.
.
.

Error found by spectre in `sbdnw', during circuit read-in.
    "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/sbdnw.scs" 156: Name mismatch in
        closing cell definition (sbdnw!=sbd).

spectre terminated prematurely due to fatal error.

------------------------------------------------------------------------------------------------------------------------------------------------------------

I don't understand what could be causing this error all of a sudden any insight you can offer would be appreciated.

 Regards
JG

 

  • Cancel
  • EricCDN
    EricCDN over 16 years ago

    You are using 5141 spectre.  The PDK most likely requires "SFE" which is the default in later versions of spectre.  Try using spectre 7.0 or 7.1.  If you must use 5141 spectre, add +csfe to userCmdLineOption in ADE.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jdgriggs
    jdgriggs over 16 years ago

    Hi Eric

    Thanks for the help...it worked partially however now it says that I have a error for hierarchy flattening.

     ----------------------------------------------------------------------------------------------------------------------------------------------------

    Environment variable:
        SPECTRE_DEFAULTS=-E
    Command line:
        /apps/ic/rel/tools.sun4v/spectre/bin/32bit/spectre -env artist5.1.0  \
            +escchars +log ../psf/spectre.out +inter=mpsc  \
            +mpssession=spectre0_19388_4 -format sst2 -raw ../psf  \
            +lqtimeout 900 +csfe input.scs
    spectre pid = 19730

    Loading /apps/ic/rel/tools.sun4v/cmi/lib/4.0/libinfineon_sh.so ...
    Loading /apps/ic/rel/tools.sun4v/cmi/lib/4.0/libnortel_sh.so ...
    Loading /apps/ic/rel/tools.sun4v/cmi/lib/4.0/libphilips_sh.so ...
    Loading /apps/ic/rel/tools.sun4v/cmi/lib/4.0/libsparam_sh.so ...
    Loading /apps/ic/rel/tools.sun4v/cmi/lib/4.0/libstmodels_sh.so ...
    spectre (ver. 5.10.41_USR5.053107 -- 31 May 2007).
    Includes RSA BSAFE(R) Cryptographic or Security Protocol Software from RSA
            Security, Inc.

    Simulating `input.scs' on pearl at 2:15:52 PM, Wed Apr 8, 2009.

    .
    .
    .
    .

    Error found by spectre during hierarchy flattening.
        "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/process.scs" 95: parameter
            `s_ntox': Unknown parameter name `k_ntoxinv' found in expression.
            
        "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/process.scs" 107: parameter
            `s_pvtl': Unknown parameter name `k_wafer' found in expression.
           
        "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/process.scs" 95: parameter
            `s_ntox': Unknown parameter name `k_ntoxinv' found in expression.
           
        "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/process.scs" 40: parameter
            `n_spec': Unknown parameter name `k_wafer' found in expression.
           
        "/libs/IBM_PDK/cmrf7sf/rel/Spectre/models/process.scs" 40: parameter
            `n_spec': Unknown parameter name `k_wafer' found in expression.

    .

    .

    .

               then finally the words of death....

     

    spectre terminated prematurely due to fatal error.

    ---------------------------------------------------------------------------------------------------------------------------------------------------------

    Thanks for the response, it is appreciated.  I curious to know why is this happening now after its been working fine until then.

    JG

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 16 years ago

    Hi,

    has the process.scs file changed at all?  I've seen strange error messages in the past when the file was missing the appropriate EOF character, or was a "DOS text/Windows text" formatted file.  Not sure if this helps at all, but it may be worth looking at.

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • EricCDN
    EricCDN over 16 years ago

    What section is the "k_ntoxinv" and "k_wafer" parameters defined in?  Are you including that section?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jdgriggs
    jdgriggs over 16 years ago

    Hey guys thanks for the response ...Our lab will be moving to the IC6.1.3 this summer so we are just maintaining the 5.1.41 until then...if possible could you share a little more insight on what you mean by section i.e. library. According to the output file this is located in the process.scs files.  And when you mean "including that section" are you refering to the .cdsint file?

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • EricCDN
    EricCDN over 16 years ago

    You need to specify the section on the Model Library Setup form in ADE.  Make sure the section that defines those parameters is included using this form. 

    As a side note, you don't need to use 5141 spectre with IC 5141.  You can use MMSIM 7.0 or 7.1 spectre with IC 5141.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 16 years ago

    I've seen this kind of problem happen when somebody installs a new version of MMSIM (e.g. MMSIM70 or MMSIM71) and doesn't go in and create the "tools" link. Unfortunately unlike other streams, the tools link for MMSIM62, 70 or 71 does not get created at installation or configuration time (there's a CCR for this) - so you have to create it manually (i.e. create the link from tools to tools.sun4v or tools.lnx86 etc).

    Because of this, people often end up with a UNIX path which is <MMSIMinstDir>/tools/bin <ICinstDir>/tools/bin <ICinstDir>/tools/dfII/bin and as a result, they unwittingly end up with spectre from IC5141.

    I just wondered whether that was why it had started failing recently for you...

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jdgriggs
    jdgriggs over 16 years ago

    Well after talking to my advisor I found out that he did recently install an updated pdk for our process.

    @ Eric the Model Library Setup reads normal, i do believe that the section is included

    ~/..../.../Spectre/models/design.scs
    ~/..../.../Spectre/models/process.scs

    @Andrew thanks for the suggestion I am about to reseach it furthter to find out if that's the problem

     JG 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • tkhan
    tkhan over 16 years ago

    Also, I think cmrf7sf is not compatible with IC610. Theres a post on the MOSIS user group regarding this, although it is about a year old now. Check your cdslib release notes to verify what version of IC they used to test the PDK. I'm using cmrf8sf and I'm pretty sure they're still testing on IC5141. For the sake of simplicity, why not use (if you have it) allModels.scs instead of design.scs, process.scs and fixed_cor.scs? (I havent used 7sf, i'm assuming the kit structure is the same as 8sf).

    Updating IBM kits can be tricky. You have the rel@ link in your pdk folder so you are using the latest files... you mentioned that you patched your kit recently, did you start having these problems after doing so? try making rel point to an older kit version and see if it works. if it does, then something went wrong when patching your kit. You don't need to define section for the model files, your .cdsenv should read:

    spectre.envOpts modelFiles “../rel/Spectre/models/design.scs ../rel/Spectre/models/fixed_corner.scs
    ../rel/Spectre/models/process.scs”

    spectre.envOpts  includePath  string "../rel/Specre/models"

    of course you would make your own site-specific adjustments for the paths. 

    Can you check your spectre version? type "spectre -W" in terminal. Maybe you have the correct version of MMSIM but if its not defined in the PATH before IC, you'll still be using spectre from the IC stream.

     

    Check this link.. its the weblog of the system admin of UofChicago's EE dept. S/he details how they troubleshoot cadence and mosis kits. https://hepblog.uchicago.edu/hep/hep4/

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ImanKian
    ImanKian over 9 years ago

    Excuse me,
    What is CCR?
    I have the same problem. I have installed MMSIM_12_11 and there is a folder 'tools.lnx86' in it, but there is no 'tools' folder also I guess I miss an 'etc' folder inside installed MMSIM folder. I would highly appreciate your help. Thanks.

    • 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