• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. Some confusion about "setAnalysisMode" command

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 91
  • Views 1409
  • 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

Some confusion about "setAnalysisMode" command

BackerShu
BackerShu over 11 years ago

 Hello Guys,

 

I have some confusion about the "setAnalysisMode" during P&R using Encounter. Please enlight.

The related part of the script is as following, and I am using EDI13.2.

---------------------------------------------------------

optDesign -postCTS -hold

 # Run global routing
routeDesign

setDelayCalMode -engine aae -SIAware true
setAnalysisMode -analysisType onChipVariation -cppr both

# Final opt
#optDesign -postRoute -si

optDesign -postRoute

 -----------------------------------------------

The confusion I have is about analysisType.

1. Usually, bcwc is used. What is the difference between onChipVariation and bcwc?

2. I checked the postCTS timing report (*_postCTS_all.tarpt & *_postCTS_all_hold.tarpt), the fastLib is used for setup time, and slowLib is used for hold time. I think bcwc type will also do the same thing.

As you can see in the above script, the onChipVariation is done after "optDesign -postCTS -hold", will this change the final timing? or in other words, is the final timing based on bcwc or onChipVariation?

 (BTW, I checked the report for postRoute *_postRoute_all.tarpt. I think this is for setup time, and the report says slowLib is used. I am not sure which Lib is used for hold time after postRoute.

I also checked the report *_postRoute.SI_Glitches.rpt which says that "Total number of glitch violations: 0")

 

Please let me know if you need more information. Thank you inadvance.

 

 

  • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information