Stats

  • Locked Locked
  • Replies 4
  • Subscribers 91
  • Views 15438
  • 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

OCV mode optimization in encounter

MadhuNS

Hi All,

Its been a general practise with our BE folks to use BCWC mode with some derate and dubb it as "equivalent" to OCV mode.

Its been a nighmarish to close design via ECO since timing engines using true OCV modes show much skewed timing when compared with encounters native timer.

Is there an OCV mode in encounter ? Since I'am novice wrt encounter grapevine says that since two libraries are required for OCV mode its not recommended,

which brings me to the next point has any one figured out a way to derate ECSM/NLDM library and use the derated library as the second library required by OCV.

Parents

  • Yes, Encounter timing would reflect differences on launch/capture paths due to min/max slew when in onChipVariation mode.  Other similar effects include:

    • Pin cap ranges in .libs
    • Crosstalk pull-in on capture clock paths
    I really don't think you need to create derated libraries.  Like Kari said, I see most customers I work with derating around a single set of .libs using set_timing_derate, setting up the corners using MMMC conventions and timing with onChipVaraition.
Reply

  • Yes, Encounter timing would reflect differences on launch/capture paths due to min/max slew when in onChipVariation mode.  Other similar effects include:

    • Pin cap ranges in .libs
    • Crosstalk pull-in on capture clock paths
    I really don't think you need to create derated libraries.  Like Kari said, I see most customers I work with derating around a single set of .libs using set_timing_derate, setting up the corners using MMMC conventions and timing with onChipVaraition.
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.