Stats

  • Locked Locked
  • Replies 24
  • Subscribers 131
  • Views 22811
  • 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

 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

 

  • Andrew Beckett

    Unknown said:

    1) For "echo $path" I got the following:

    /usr/lib64/qt-3.3/bin /usr/local/bin /usr/bin /bin

    If that's all that's in your path, it's hardly surprising that "which spectre" doesn't work or you get command not found. I'm not sure how you'd find "virtuoso" either!

    You mentioned earlier:

    Unknown said:

    4) Also here is what I have in my Unix code, it might help:
    set path=(<MMSIMinstDir>/bin ${path})
    #Variables and paths for IC51
    setenv CDS_INST_DIR <CadenceInstDir>
    setenv CDSDIR <CadenceInstDir>
    setenv CDS_INSTALL_DIR ${CDS_INST_DIR}/tools/dfII
    set path=( $CDS_INST_DIR/tools/bin $CDS_INST_DIR/tools/dfII/bin ${path})

    So does that mean you've not sourced this file? Or is this done in some kind of wrapper script that launches virtuoso? 

    Andrew

  • ImanKian

    Grrrreeeaaaaaaattttt !!! Good news!!
    Thanks Andrew, you are so helpful and unique !!!

    Well, I am not using wrapper script, by the way.

    The problem was in our installation manual was written that we should run the script using ./<script file>. Now I used <source script> and I got the following contents for "echo $path":

    /home/iki/ADS2013/bin:/home/iki/ADS2013/idf/ads_site:/home/iki/ADS2013/idf/config /home/iki/Cad/Tools/Mentor/calibre_2013.4_15/aoi_cal_2013.4_15.12/bin /home/iki/Cad/Tools/Cadence/IC_5/bin /home/iki/Cad/Tools/Cadence/IC_5/tools/bin /home/iki/Cad/Tools/Cadence/IC_5/tools/dfII/bin /home/iki/Cad/Tools/Cadence/MMSIM_12/bin /home/iki/Cad/Tools/Cadence/MMSIM_12/tools/bin /home/iki/Cad/Tools/Cadence/MMSIM_12/tools.lnx86/bin /home/iki/Cad/Tools/Cadence/MMSIM_12/tools.lnx86/dfII/bin /usr/lib64/qt-3.3/bin /usr/local/bin /usr/bin /bin /home/iki/Cad/Tools/Cadence/ASSURA_CDB5/tools/bin /home/iki/Cad/Tools/Cadence/ASSURA_CDB5/tools/assura/bin /home/iki/Cad/Tools/Cadence/PVE_12/bin /home/iki/Cad/Tools/Cadence/PVE_12/tools/bin /home/iki/Cad/Tools/Cadence/PVE_12/tools/dfII/bin

    However, while I have the <MMSIMinstDir> above <CDSinstDir>,  for "spectre -W" I get sub-version  5.10.41.121508.
    If I move it below <CDSinstDir> I get sub-version  12.1.1.164.isr15. Does it make sense? because previously It was there and I was able to simulate; the problem was "spectre -W" which used to failed every time because of ./   :) .

  • Andrew Beckett

    I'm not sure what  you mean by "above" and "below". This is a list which is left to right. In the list for $path that you've shown, the IC_5 paths are before  the MMSIM paths - so I would expect it to pick up the old spectre sub-version 5.10.41.121508 (which you don't want). If you ensure that the MMSIM paths are before the IC_5 path, then it would pick 12.1.1.164.isr15 (which you do want). Even MMSIM12.1 is old, but it's far younger than the 2008 version of spectre you would have been picking up otherwise.

    Regards,

    Andrew.

  • ImanKian

    Thanks a lot dear Andrew, I learned a lot indeed. I just conclude everything in this post.

    With below and above I meant the order of placing in the UNIX run script, which I guess you did not meant that and I always thought you meant that.

    In my UNIX run script, if I put set path=($MMSIM_12_11/bin:${path}) before set path=($CDS_INST_DIR/tools/bin:$CDS_INST_DIR/tools/dfII/bin:${path}), which is absolutely wrong and for "which spectre" I get <CDSinstDir>/tools/bin/spectre, and for "spectre -W" I get sub-version  5.10.41.121508, and for echo $path I see
    /home/iki/ADS2013/bin:/home/iki/ADS2013/idf/ads_site:/home/iki/ADS2013/idf/config /home/iki/Cad/Tools/Mentor/calibre_2013.4_15/aoi_cal_2013.4_15.12/bin /home/iki/Cad/Tools/Cadence/IC_5/tools/bin /home/iki/Cad/Tools/Cadence/IC_5/tools/dfII/bin /home/iki/Cad/Tools/Cadence/MMSIM_12/bin /usr/lib64/qt-3.3/bin /usr/local/bin /usr/bin /bin /home/iki/Cad/Tools/Cadence/ASSURA_CDB5/tools/bin /home/iki/Cad/Tools/Cadence/ASSURA_CDB5/tools/assura/bin /home/iki/Cad/Tools/Cadence/PVE_12/bin /home/iki/Cad/Tools/Cadence/PVE_12/tools/bin /home/iki/Cad/Tools/Cadence/PVE_12/tools/dfII/bin

    On the other hand, if I replace them for "which spectre" I get <MMSIMinstDir>/bin/spectre, and for "spectre -W" I get sub-version  12.1.1.164.isr15, and everything goes well. For echo $path I get what has come below and as it can be seen MMSIM_12 directory is prior to IC_5.
    /home/iki/ADS2013/bin:/home/iki/ADS2013/idf/ads_site:/home/iki/ADS2013/idf/config /home/iki/Cad/Tools/Mentor/calibre_2013.4_15/aoi_cal_2013.4_15.12/bin /home/iki/Cad/Tools/Cadence/MMSIM_12/bin /home/iki/Cad/Tools/Cadence/IC_5/tools/bin /home/iki/Cad/Tools/Cadence/IC_5/tools/dfII/bin /usr/lib64/qt-3.3/bin /usr/local/bin /usr/bin /bin /home/iki/Cad/Tools/Cadence/ASSURA_CDB5/tools/bin /home/iki/Cad/Tools/Cadence/ASSURA_CDB5/tools/assura/bin /home/iki/Cad/Tools/Cadence/PVE_12/bin /home/iki/Cad/Tools/Cadence/PVE_12/tools/bin /home/iki/Cad/Tools/Cadence/PVE_12/tools/dfII/bin

    I can conclude that the order that KornShell run these commands makes the difference. The last code will be replaced by anything which had come before that. Now I digested what you meant. Thanks 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.