• 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. LIB File generation with ELC tool (Encounter Library Characterizer...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 94
  • Views 14455
  • 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

LIB File generation with ELC tool (Encounter Library Characterizer)

OLyonnais
OLyonnais over 15 years ago

Sorry if i'm on the wrong topic, please move it where it's better.  

I'm trying to get the ELC netlist  of my cell, from the spectre netlist (i need to modify all vdd! of my netlist by vdd, all the "0" by gnd etc...)

Once it's OK, i run a command create the design of my cell with ELC, and generate my lib file. Normally, i have to get the port definition of my cell for example with an inverter:

DESIGN (INV)

Port definition

INPUT A (A);

OUTPUT Y (Y);

SUPPLY0 GND (GND);

Instances

NOT(Y , A);

END_OF_DESIGN;

on my MUX design i have this message:


- bi-directional switch ( tranif1 NET077:D0 ) is found
- bi-directional switch ( tranif1 NET077:D1 ) is found
- bi-directional switch ( tranif1 NET79:D2 ) is found
- unknown directional port ( inout : D2 ) is found
- unknown directional port ( inout : D1 ) is found
- unknown directional port ( inout : D0 ) is found

 Why D0 D1 and D2 or inout, whereas that on my schematic, they are define as IN pin.

my ELC netlist : subckt My_MUX D0 D1 D2 S0 S0N S1 S1N Z vdd gnd

INOUT D0 (D0);

INOUT D1 (D1); 

INOUT D2 (D2); 

 

 I hope you undertood my trouble. if someone has an idea, thank you...

  • Cancel
  • Keeshik
    Keeshik over 15 years ago

    Dear OLyonnais,

    In your ELC simulation setup file, did you setup the pin definitions of the MUX? In the 'INDEX' statement, input pins are supposed to have 'Slew' definitions and output pins 'Load' definitons.

    In case there is dotlib which is already validated, you can use the "auto setup creation". Please use "db_prepare -create_setup" command to generate your setup file based on your existing dotlib file. Or, you can create setup file manually in case you start ELC from scratch.

    Hope this answers to your issue, but please contact me at 'keeshik@cadence' in case you still have issues.

    Regards, 

    Keeshik Oh 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Lamech
    Lamech over 14 years ago
    Hi Keeshik/OLyonnais, Is this problem fixed? I am having the same problem. That is also at a MUX inside a cell. If you share the solution it will be really helpful for me. Thanks in Advance. Charles
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago

     Halo Charles,

    Are you the guy who wrote the ELC tutorial available on the web? 

    Im using ELC for the first time and Im having some trouble since the help files are not too helpfull. I have a .scs file which defines the models of my technology. I find it difficult that the ELC tool does not accept the .scs file without some modification. The .scs file that I have declares some variables for each of the process corner in a "section" declaration, but the ELC tool is not happy with these "sections". Is it normal to need to edit the .scs model file that you received along with the process technology?

     Thanks,

    Chris

    • 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