• 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. problems in using ELC(encounter library characterize)

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 94
  • Views 1895
  • 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

problems in using ELC(encounter library characterize)

wangweike
wangweike over 14 years ago

hi,thanks for you attention!

I use ELC in my work ,when i type the "db_prepare -force" there goes the warning:

elc>  db_prepare -force

==== Simplify Mode ====

MODEL FILE: amic5n.scs ( #size = 4486 )

Reading MODEL: AMI06N
Reading MODEL: AMI06P

SUBCKT FILE: amic5n.scs ( #size = 4486 )


SUBCKT FILE: dut_sub.scs ( #size = 287 )

Reading SUBCKT:INV
Expanding SUBCKT:INV
Writing : foo.ipdb/INV.design
Writing : foo.ipdb/INV.design/body/path
Writing : foo.ipdb/INV.design/body/instance
Writing : foo.ipdb/INV.design/body/net
Writing : foo.ipdb/INV.design/boundary/port
Reading : foo.ipdb/INV.design

==============================
      DESIGN : INV
==============================
--------------------

--------------------
D0000: : POWER
--------------------
=> 1 vectors generated
Writing : foo.ipdb/INV.design/simulate/spec
Writing : foo.ipdb/INV.design/simulate/subckt
[WARNING(db_prepare)]alone net : A is found. => [reset to ground]
[WARNING(db_prepare)]Please check whether supply nodes are marked global in the netlist, if not specify them with .global statements
[WARNING(db_prepare)]alone net : Y is found. => [reset to ground]
[WARNING(db_prepare)]Please check whether supply nodes are marked global in the netlist, if not specify them with .global statements
[WARNING(db_prepare)]alone net : VDD is found. => [reset to ground]
[WARNING(db_prepare)]Please check whether supply nodes are marked global in the netlist, if not specify them with .global statements
[WARNING(db_prepare)]alone net : GND is found. => [reset to ground]
[WARNING(db_prepare)]Please check whether supply nodes are marked global in the netlist, if not specify them with .global statements
Writing : foo.ipdb/INV.design/boundary/port
Writing : foo.ipdb/INV.design/body/type

================================
  stimulus generation  summary
================================
Name            #MOS    #DVEC   #RVEC
----------------------------------------
INV             0       1       0
----------------------------------------
                        1       0
 Reading setup file : setup.ss
 -          INV (CELL) -      typical - 2011-02-25 15:11:06 (2011-02-25 07:11:06 GMT)


then i type "db_date" ,it can not recognize the NOT gate

elc>  db_gate
==============================
      DESIGN : INV
==============================
DESIGN ( INV );
//      =================
//       PORT DEFINITION
//      =================
        SUPPLY0 GND ( GND );
        SUPPLY1 VDD ( VDD );
        FEEDTHRU A ( A );
        FEEDTHRU Y ( Y );
//      ===========
//       INSTANCES
//      ===========
END_OF_DESIGN;

- feed-through ( A ) is found
- feed-through ( Y ) is found

can you help me to deal with it ?thanks very much

  • Cancel
Parents
  • Thodoros
    Thodoros over 13 years ago

     Hello,

    Did you manage to solve this problem?

    I have the same case ()

    DESIGN INV should give

    INPUT A ( A );

    However it gives

     FEEDTHRU A ( A );

     

    As a result the gate is not recognized by the db_gate

    Thanks for your concern

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Thodoros
    Thodoros over 13 years ago

     Hello,

    Did you manage to solve this problem?

    I have the same case ()

    DESIGN INV should give

    INPUT A ( A );

    However it gives

     FEEDTHRU A ( A );

     

    As a result the gate is not recognized by the db_gate

    Thanks for your concern

    • 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