10.06.2016 Views

eldo_user

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Eldo Control Language<br />

Eldo Control Language Limitations<br />

The .MPRUN command is not supported at the task level but at the testbench level. ECL<br />

sequential loop statements are not supported; the .MPRUN command has no effect on<br />

the ECL statements: for, step, and while. For example, it is not possible to distribute<br />

each simulation executed inside a sequential “for” loop. For a given simulation (run<br />

from an ECL task), if the netlist to simulate contains a .MPRUN command and a .MC<br />

command for example, then the Monte Carlo runs of this simulation will be distributed<br />

as usual. See the “.MPRUN with Monte Carlo Analysis Example” on page 1133.<br />

Simulations executed inside ECL parallel loop statements can be distributed using the<br />

.ELDO_CL_MPRUN command.<br />

• The .AGE and .DEX commands are supported inside testbenches even if they are<br />

directly instantiated in the netlist.<br />

• The Eldo Control Language is supported by Eldo Premier, with limitations. The<br />

functionality described in “Simulation Dynamic Control” on page 1014 is not supported.<br />

• Eldo Interactive mode is not compatible with the Eldo Control Language: it does not<br />

support netlists containing tasks. Netlists containing only testbench instantiations,<br />

without any tasks can however be run using the Eldo Interactive mode.<br />

• Eldo Control Language may sometimes generate large .wdb files; especially when a task<br />

runs a simulation creating many waveforms and if all these waveform results are saved<br />

into task local variables, the main .wdb file can be much larger than the temporary .wdb<br />

file generated during the simulation. One of the following options can be used to solve<br />

this possible issue:<br />

o<br />

o<br />

.option KEEP_ELDO_CL_TEMP_WAVES=0<br />

For more details on this option, see the “wdb File” section in “Simulation” on<br />

page 1114. This is the preferred solution, but the disadvantage is that waveforms that<br />

need to be saved to be visualized have to be saved explicitly using the “Functions<br />

Operating on wdb Files” described in “Library of Functions for Tasks” on page 854.<br />

.option USE_ELDO_CL_SAFE_WAVE_CP=0<br />

This option deactivation has two major disadvantages:<br />

• Possible impact on the execution speed of Eldo Control Language tasks: the<br />

execution of a task running many simulations generating waveforms will be<br />

longer (if these waveform results are saved into task local variables for each<br />

simulation).<br />

• In some cases the Eldo Control Language won’t be able to generate a compound<br />

waveform simulation result (FAILED TO GET WAVE error). This will happen,<br />

for example, with AC simulations when trying to generate a vdb or vp<br />

waveform, for example:<br />

.plot ac w_db=vdb(out) w_p=vp(out)<br />

Workaround: replace the .PLOT command with a v complex waveform plot:<br />

Eldo® User's Manual, 15.3 807

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

Saved successfully!

Ooh no, something went wrong!