• 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. Encounter Library Characterizer (ELC Problem)

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 91
  • Views 12768
  • 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

Encounter Library Characterizer (ELC Problem)

Hatkar
Hatkar over 12 years ago

Problem during step2 

My dut.scs file

// Library name: UofU_Digital_Parts
// Cell name: INVX1
// View name: analog_extracted
subckt INVX1 A Y vdd gnd
    \+1 (Y A vdd vdd) ami06P w=6e-06 l=6e-07 as=9e-12 ad=9e-12 ps=9e-06 \
        pd=9e-06 m=1 region=sat
    \+0 (Y A gnd gnd) ami06N w=3e-06 l=6e-07 as=4.5e-12 ad=4.5e-12 ps=6e-06 \
        pd=6e-06 m=1 region=sat
ends INVX1
// End of subcircuit definition.

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

My  elccfg file

EC_SIM_USE_LSF=1;
EC_SIM_LSF_CMD=" ";
EC_SIM_LSF_PARALLEL=0; //Tried for 2, 3, 5, 7, 10 20 and 50
EC_SPICE_SIMPLIFY=true
EC_HALF_WIDTH_HOLD_FLAG=true
EC_SIM_NAME="spectre";
EC_SIM_TYPE="spectre";
EC_SPICE_SUPPLY1_NAMES="vdd";
EC_SPICE_SUPPLY0_NAMES="gnd";
SETUP = "setup.ss";
PROCESS = "typical";
MODEL = "ami_c5n_typ.scs";
SUBCKT = "dut.scs";

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

My Step1 Script

db_open foo
db_prepare -force
db_gate
db_close
exit

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

My Step2 Script

db_open foo
db_spice -s spectre -keep_log
db_close
exit

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

elc.log after Step1

[root@Arvind workdell]# source env.sh
[root@Arvind workdell]# elc -S step1
--------------------------------------------------------------------------------------------------
Encounter - Library Characterizer - Version v10.10-p001_1 - linux_x86 32-bit (12/01/2010 02:45:03)
--------------------------------------------------------------------------------------------------
[2000-2010]Cadence Design Systems, Inc. All rights reserved.
This work may not be copied, modified, re-published, uploaded, executed, or
distributed in any way, in any medium, whether in whole or in part, without
prior written permission from Cadence Design Systems, Inc.
set_var MANPATH = /Cadence/ETS/share/elc/man
elc>  db_open foo

Database : foo is now opened
elc>  db_prepare -force


==== Simplify Mode ====

MODEL FILE: ami_c5n_typ.scs ( #size = 2808 )

Reading MODEL: AMI06N
Reading MODEL: AMI06P

SUBCKT FILE: ami_c5n_typ.scs ( #size = 2808 )


SUBCKT FILE: dut.scs ( #size = 375 )

Reading SUBCKT:INVX1
Expanding SUBCKT:INVX1
Writing : foo.ipdb/AMI06N.device
Writing : foo.ipdb/AMI06N.device/boundary/port
Writing : foo.ipdb/AMI06P.device
Writing : foo.ipdb/AMI06P.device/boundary/port
Writing : foo.ipdb/INVX1.design
Writing : foo.ipdb/INVX1.design/body/path
Writing : foo.ipdb/INVX1.design/body/instance
Writing : foo.ipdb/INVX1.design/body/net
Writing : foo.ipdb/INVX1.design/boundary/port
Reading : foo.ipdb/INVX1.design

==============================
      DESIGN : INVX1
==============================
------------------------------
        A  :  Y 
------------------------------
D0000:  R  :  F  : DELAY(A)
D0001:  F  :  R  : DELAY(A)
------------------------------
=> 2 vectors generated
Writing : foo.ipdb/INVX1.design/simulate/spec
Writing : foo.ipdb/INVX1.design/simulate/subckt
Writing : foo.ipdb/INVX1.design/boundary/port
Writing : foo.ipdb/INVX1.design/body/type

================================
  stimulus generation  summary 
================================
Name        #MOS    #DVEC    #RVEC
----------------------------------------
INVX1        2    2    0   
----------------------------------------
            2    0
 Reading setup file : setup.ss
 -        INVX1 (CELL) -      typical - 2013-05-01 13:34:58 (2013-05-01 08:04:58 GMT)

elc>  #db_gsim -force

elc>  db_gate


==============================
      DESIGN : INVX1
==============================
DESIGN ( INVX1 );
//    =================
//     PORT DEFINITION
//    =================
    INPUT A ( A );
    OUTPUT Y ( Y );
    SUPPLY0 GND ( GND );
    SUPPLY1 VDD ( VDD );
//    ===========
//     INSTANCES
//    ===========
    NOT ( Y, A );
END_OF_DESIGN;


elc>  db_close

Database : foo is closed
elc>  exit


Memory : 3.02M
Time   : 0.12 (user), 0.01 (sys), 0.13 (cpu), 0.63 (real)
[root@Arvind workdell]#
-------------------------------------------------------------------------------------------------------------

elc.log after Step2

[root@Arvind workdell]# elc -S step2
--------------------------------------------------------------------------------------------------
Encounter - Library Characterizer - Version v10.10-p001_1 - linux_x86 32-bit (12/01/2010 02:45:03)
--------------------------------------------------------------------------------------------------
[2000-2010]Cadence Design Systems, Inc. All rights reserved.
This work may not be copied, modified, re-published, uploaded, executed, or
distributed in any way, in any medium, whether in whole or in part, without
prior written permission from Cadence Design Systems, Inc.
set_var MANPATH = /Cadence/ETS/share/elc/man
elc>  db_open foo

Database : foo is now opened
elc>  db_spice -s spectre -keep_log


   DESIGN        PROCESS       #ID         STATUS     IPDB
-------------+-------------+----------+--------------+-----------
INVX1          typical       D0000         SIMULATE    foo        
INVX1          typical       D0001         SIMULATE    foo        
============|=============|=============|==========|==============
INVX1          typical       2          2            foo        
--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*
 2013-05-01 13:36:14 (2013-05-01 08:06:14 GMT) : Vectors Launched 2/2
super-user execution is restricted. If you want to disable this feature, invoke ipsc with '-r' option.
super-user execution is restricted. If you want to disable this feature, invoke ipsc with '-r' option.

-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
               Simulation Summary               
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
-------------+-------------+----------+--------------+-----------
-------------+-------------+----------+------------+-----------+------------
   DESIGN    |   PROCESS   |   #ID    |   STAGE    |  STATUS   |    IPDB
-------------+-------------+----------+------------+-----------+------------
INVX1          typical       D0000     UNEXPECTED   (-5)FAIL        foo        
INVX1          typical       D0001     UNEXPECTED   (-5)FAIL        foo        
-------------+-------------+----------+------------+----------

[INFO(db_spice)] Check the encounterlc.log/<ipdb_name>/<DESIGN>_<PROCESS>_<ID>.log file to determine the cause of the failure. The SPICE simulation log file can be found in the /Cadence/workdell/encounterlc.work/<DESIGN>_<PROCESS>_<ID>/ directory.

-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
 - Total Simulation : 2
 - Total Passed     : 0(0.00%)
 - Total Failed     : 2(100.00%)
-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
elc>  db_close

Database : foo is closed
elc>  exit


Memory : 3.02M
Time   : 5.05 (user), 0.11 (sys), 5.16 (cpu), 5.19 (real)
[root@Arvind workdell]#
---------------------------------------------------------------------------------------------------------------------------

Problem is encounterlc.log file is not created, so not able to find out problem.

Do not understand meaning of super-user execution is restricted. If you want to disable this feature, invoke ipsc with '-r' option.

Please let me know solution if anyone faced same problem

Thanks,

 

 

  • 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