Stats

  • Locked Locked
  • Replies 3
  • Subscribers 92
  • Views 15028
  • 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

Typical value Missing in the triplets in a generated SDF File

vicky
I generated an SDF file using a ETS for single operating condition. In the generated file, the typical timing of the triplet was missing. In the old signalstorm we used to get the same value updtaed in all the triplets but now how come I get only the min and max values.

In the sdf file normal the delay values are updtaed as tripets i.e min:typ:max. In the ETS when I dump the  sdf I see only the min::max values getting upadted. I would like to know the reason
Parents

  •  SignalStorm stand-alone delay calculation was capable of performing delay calculation for min,typ, and max at the same time - and provided facilities for controlling what when into the various SDF delay slots.  In ETS (and EDI), nonMMMC mode only supports two delay slots - best and worst under bcWc mode, and early/late under OCV mode - so, simply Typical delays never get calculated.  We have chosen to keep the Typ SDF slot empty rather than populate it - by replicated either the min or max slot, or averaging them.    This way, there is no confusion with how the Typ value was calculated (or not) by someone using the SDF.

     In MMMC mode, the system will calculate delays for as many corners as you want.  The write_sdf  command has the functionality to allow the user to specify which data gets used to populate each of the SDF min:typ:max slots.

     

    Regards,

     

    Ed

Reply

  •  SignalStorm stand-alone delay calculation was capable of performing delay calculation for min,typ, and max at the same time - and provided facilities for controlling what when into the various SDF delay slots.  In ETS (and EDI), nonMMMC mode only supports two delay slots - best and worst under bcWc mode, and early/late under OCV mode - so, simply Typical delays never get calculated.  We have chosen to keep the Typ SDF slot empty rather than populate it - by replicated either the min or max slot, or averaging them.    This way, there is no confusion with how the Typ value was calculated (or not) by someone using the SDF.

     In MMMC mode, the system will calculate delays for as many corners as you want.  The write_sdf  command has the functionality to allow the user to specify which data gets used to populate each of the SDF min:typ:max slots.

     

    Regards,

     

    Ed

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.