eldo_user

Simulator Compatibility
Troubleshooting the Spectre to Eldo Flow
Priority Rules
The language of any file is determined based on the rules prioritized below (where
XYZ=SPECTRE | ELDO | SPICE). The first applied rule determines the file’s language without
any further rule checking.
1. If “simulator lang=XYZ” is specified inside the file, then the language of the file is
XYZ.
2. If “included lang=XYZ” is specified before a .include file statement, then the language
of this included file is XYZ, and the language within “included lang=XYZ … end
lang=XYZ” should also be XYZ.
3. If “-i ” is specified in the command line of spect2el, then the language of file
is Eldo.
4. If the file extension is “.scs”, then its language is Spectre.
5. If the file extension is “.sp”, then its language is SPICE.
6. If “-lang XYZ” is specified in the command line of spect2el, then the language of all
remaining files is XYZ (these files are not included in any of the above cases).
7. If none of the above rules are applied, then the language of the file is SPICE.
This applies to the standalone converter and also the Spectre compatibility flow (invoking Eldo
with the command eldo -sp).
Related Topics
Spectre Compatibility Flow
Troubleshooting the Spectre to Eldo Flow
Spectre to Eldo Converter
Troubleshooting the Spectre to Eldo Flow
Some tips on troubleshooting the Spectre to Eldo flow.
Include Files
The spice_command_file must not include the spectre_file, and vice versa. Eldo automatically
performs the link between these files. Attempting to include the Spectre file will not function,
and the simulation will stop.
• The SPICE file includes the Spectre file.
Eldo will not be able to parse the Spectre file, leading to the following syntax error
message (example):
186
Eldo® User's Manual, 15.3