• 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 charaterizer could not read the hspice...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 94
  • Views 14044
  • 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 charaterizer could not read the hspice IBM model file

Satendra
Satendra over 15 years ago

 Hi Everyone,

I am new on ELC. I ran the tool for characterizing my design but it could not even read the model files. Can anyone please help me on this.

I read several posting on this blog and tried everything but could fix it.

My elccfg looks like this

EC_SIM_USE_LSF=1;
EC_SIM_LSF_CMD="";
EC_SIM_LSF_PARALLEL=3;
EC_SIM_TYPE="hspice" ;
EC_SIM_NAME="hspice" ;
#EC_SPICE_SIMPLIFY =1;
EC_SPICE_SUPPLY1_NAMES="vdd! VDD!";
EC_SPICE_SUPPLY0_NAMES="vss! VSS!";

SUBCKT="./netlists/static_shifter_cell.pex.netlist";
MODEL="../hspice_test/models/design.inc";

SETUP="demosetup.cfg";
PROCESS="process_corner";


 I tried replacing Model with LIB but did not work. I even created model_type file with these commands in it

* This first line should be a comment line in the MODEL_FILE we are creating

simulator lang=spice

.lib "/hspice_test/models/design.inc" tt

 Still I could not get any success.

Satendra

 

 

  • Cancel
Parents
  • Keeshik
    Keeshik over 15 years ago

    Dear Satendra,

    There could be many different reasons why your simulator fails reading in the model files in your ELC simulations. As the best way to find out the reason, I'd recommend you to run stand-alone simulation using a spice deck created within ELC.

    Please add -keep_work to your db_spice command in ELC command file. This will keep the Spice decks in the directory name, encounterlec.work by default. Go to one of directory, then run your simulator. This will save the spice log, where you'll see the error messages which may tell you, for example, which model files are missing, or if model syntax is not accepted, etc. 

    The "MODEL" keyword in your ELC config file needs the spice models, not the dotlibs.

    Please let me know if you still get problem.  You can reach me by the email, keeshik@cadence.com

    Regards,
    Keeshik 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Keeshik
    Keeshik over 15 years ago

    Dear Satendra,

    There could be many different reasons why your simulator fails reading in the model files in your ELC simulations. As the best way to find out the reason, I'd recommend you to run stand-alone simulation using a spice deck created within ELC.

    Please add -keep_work to your db_spice command in ELC command file. This will keep the Spice decks in the directory name, encounterlec.work by default. Go to one of directory, then run your simulator. This will save the spice log, where you'll see the error messages which may tell you, for example, which model files are missing, or if model syntax is not accepted, etc. 

    The "MODEL" keyword in your ELC config file needs the spice models, not the dotlibs.

    Please let me know if you still get problem.  You can reach me by the email, keeshik@cadence.com

    Regards,
    Keeshik 

    • 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