10.06.2016 Views

eldo_user

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Running Eldo<br />

Eldo Initialization File<br />

# This line is a comment<br />

[env]<br />

# There must be no blanks between variable name, equal sign<br />

# and variable valueOPTION_DIR=.<br />

MODEL_DIR=../models<br />

LIB_DIR=../libs<br />

[argu]<br />

-outpath $OPTION_DIR/results<br />

-gwl jwdb<br />

-compat<br />

[netlist]<br />

.option noascii notrc<br />

.include $OPTION_DIR/options.inc<br />

.option post probe<br />

An example with two levels of inclusion:<br />

• File name: $HOME/<strong>eldo</strong>.ini. File content:<br />

[argu]<br />

-use_proc all<br />

[include]<br />

$HOME/config/command.ini<br />

[netlist]<br />

.probe i<br />

• File name: $HOME/config/command.ini. File content:<br />

[netlist]<br />

.probe v<br />

[include]<br />

$HOME/config/option.ini<br />

• File name: $HOME/config/option.ini. File content:<br />

[netlist]<br />

.option tuning=vhigh<br />

The complete [netlist] section elaborated by the simulator is built from <strong>eldo</strong>.ini which includes<br />

command.ini which itself includes option.ini. As a consequence, the final SPICE section<br />

contains the lines from option.ini first, then the section from command.ini, and lastly from<br />

<strong>eldo</strong>.ini, as below:<br />

.option tuning=vhigh<br />

.probe v<br />

.probe i<br />

Tip<br />

See also “Eldo Arguments” and the “.INCLUDE ” command in the Eldo Reference Manual.<br />

Related Topics<br />

Invoking Eldo<br />

52<br />

Eldo® User's Manual, 15.3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!