Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 14617
  • 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

Transient simulation output files

Gurunath Kadam

Hi all,

I have following code:

<code>

simulator lang = spectre

parameters
+ v_vdd = 0.990

xringoinv (ven rn_i ro_o vdd vss) ringosc_sim_sub

ven (ven 0) vsource type=dc dc=0.990
vdd (vdd 0) vsource type=pulse val0=0 val1=v_vdd delay=2n rise=100p fall=100p width=50m period=100m
vss (vss 0) vsource type=dc dc=+0.0 mag=0.0 phase=0.0

vddsweep sweep param=v_vdd start=0.85 stop=1.15 step=0.05{
trsweep tran step=0.01n stop=10n
export freq=oceanEval("1/delay(?wf1 v(\"ro_o\") ?value1 value(v(\"vdd\") 10n)/2 ?edge1 'rising ?nth1 3 ?wf2 v(\"ro_o\") ?value2 value(v(\"vdd\") 10n)/2 ?edge2 'rising ?nth2 4)")
}

//some simulatorOptions

Spectre options rawfmt=psfascii rawfile="ringo_tb.psf" measoutput=detail

//some circuit

//some lib

</code>

I don't know how to write the Freq parameters in each case in an output file. Something like in two columns VDD freq.

Thank you

  • Okay, so after going through Spectre manual more than once I realized there is probably no way to do this in Spectre stand alone, but I need to use SpectreMDL. I was already using Ocean equations for measurements!

  • I have now a *.scs file and another *.mdl file.

    As I check I ran only spectre *.scs file which runs fine.

    My *.mdl file is as follows:

    ..............................

    alias measurement runtran {
    export real deltaxOut
    run trsweep
    deltaxOut = deltax( sig1=V(ro_o), sig2=V(ro_o), dir1=’rise, \
    thresh1 = 0.45, dir2=’rise, thresh2=0.45, start1=4n, start2=4n )
    }

    run runtran

    ...........................

    When I run:

    spectremdl -b *.mdl -d *.scs

    My output files (*.measure, *.mt0) do not have any measurements reported in them. I don't know what is wrong.

    Any help?

    Thanks. 

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.