• 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. Documentation for MMMC flow with CPF

Stats

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

Documentation for MMMC flow with CPF

mamsadegh
mamsadegh over 13 years ago

Hi,

In SOC Encounter Users Guide, Chapter 43, "Performing Multi-Mode Multi-Corner Timing Analysis and Optimization" , describes MMMC flow completely however, I feel this description is supposing that you don't have a CPF file in your design, since most of the parts in the flow will be actually done in the CPF file and we don't need to do them manually. 

Is this correct?

In other words, The ".view" file, which is used for configuring MMMC, should be created automatically from CPF. Right now, as what I see from version 10.11 of encounter, this does not happen and you should create the .view manually. 

Is there any documentation , describing MMMC flow, considering also CPF file created and loaded for the design? or any script examples? 

thanks

 

  • Cancel
Parents
  • mamsadegh
    mamsadegh over 13 years ago

    hi

    Ok, I read the solution.

    So, when I issue , "loadCPF" and "commitCPF" for my design in encounter, the analysis views will be created automatically based on the CPF file and all I need to do is just to add the proper RC corner to each analysis view. 

    more over, 

    when you load the design for the first time in encounter environment to perform initial place&route, the CPF will be read automatically by the scripts (produced by RC compiler) however, when you performed P&R and you stored the design, if your Restore it, CPF is not read and you should do this part yourself. 

    more over, this "viewDefinition" file , which is created automatically by the tool when storing the design, should be cleared or should 

    be commented completely , because this part is what you should do yourself through your script. 

    is that correct?

     

    regards

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • mamsadegh
    mamsadegh over 13 years ago

    hi

    Ok, I read the solution.

    So, when I issue , "loadCPF" and "commitCPF" for my design in encounter, the analysis views will be created automatically based on the CPF file and all I need to do is just to add the proper RC corner to each analysis view. 

    more over, 

    when you load the design for the first time in encounter environment to perform initial place&route, the CPF will be read automatically by the scripts (produced by RC compiler) however, when you performed P&R and you stored the design, if your Restore it, CPF is not read and you should do this part yourself. 

    more over, this "viewDefinition" file , which is created automatically by the tool when storing the design, should be cleared or should 

    be commented completely , because this part is what you should do yourself through your script. 

    is that correct?

     

    regards

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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