Stats

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

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

 

  • If you're using CPF you're correct that most of the MMMC setup is defined in the CPF, but not all. The following solution provides an example of what is defined in the CPF and what additional info you have to define outside of the CPF (i.e. rc_corners, SI libs, etc.):

    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11575688

    After the CPF is loaded and MMMC environment is setup it gets saved to the viewDefinition.tcl file under the database directory.

    The CPF reference manual describes the commands used within the CPF.

    Hope this helps.

    Regards,

    Brian

  • 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

     

  • If you load the CPF then it will get saved to the EDI database. You'll see a *.cpfdb file under the *.enc.dat directory. A viewDefinition.tcl file will also exist. So when you restore the design your MMMC environment will be read in and you do not need to re-load the CPF.Run report_analysis_views after restoring the design to confirm this.

  • Hi, M.S.Sadri.

    I'm glad you were able to access the solution.

    For other university students, access is available through your on campus University Program contact (e.g. professor, IT, etc.). You can get an account to access various information, solutions, and documentation.

     

    pstark

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.