ccopt_design

ccopt_design
[-help]
[-check_prerequisites]
[-ckSpec]
[-cts]
[-expandedViews]
[-genScriptOnly filename ]
[-import filename ]
[-inDir dirname ]
[-outDir dirname ]
[-prefix fileNamePrefix ]
[-runScript filename ]
Performs clock concurrent optimization (CCOpt) on the current loaded design in the EDI system. CCOpt optimizes both the
clock tree and the datapath to meet global timing constraints.

Parameters
-help Outputs a brief description that includes type and default
information for each ccopt_design parameter. For a detailed
description of the command and all of its parameters, use the man
command: man ccopt_design .
- Checks that all the prerequisites for running clock tree synthesis
check_prerequisites are fulfilled without actually doing CTS. For example, it checks
that the design is loaded, and the options set by that the user are
correct.
-ckSpec Runs the design using the EDI-CTS specification file. This mode
is a compatibility layer to enable the use of CCOpt technology
with existing EDI-CTS specification flows. It enables a translation
step that transforms constructs in the EDI-CTS specification file
into a CCOpt clock tree specification tcl script.
Note : The -ckSpec parameter is applicable both in the scripted
and native CCOpt flow. In the native CCOpt flow, this parameter
is used with the -cts parameter to specify that CTS part of
CCOpt will be performed using the old EDI-CTS specification
file.
-cts Turns off clock concurrent optimization, and performs only clock
tree synthesis (CTS) using the CCOpt engine. It does not perform
any datapath optimization or useful skew.
This parameter can be used with or without the –
ckSpec parameter. When used with the -ckSpec parameter, it
specifies that the CTS part of CCOpt will be performed using the
old EDI-CTS specification file.
When used without the -ckSpec parameter, ensure that the CCOpt
clock trees are already defined using
thecreate_ccopt_clock_tree_spec command.
This parameter is applicable both in the scripted and native
 CCOpt flow.
-expandedViews This parameter is not interpreted in CCOpt but passed directly
to optDesign . The parameter is same as optDesign-
expandedViews parameter, which is specified to generate detailed
view-specific timing reports at the end of
the optDesign command run.
- Executes the "generate" stage of ccopt_design . There are three
genScriptOnlyfilename stages; generate, run, and import. The generate stage exports
design files and generates the script that will be passed to CCOpt.
By default, ccopt_design executes all stages.
The filename argument specifies the name of the control script to
generate. By default, the filename used for the control script
is az_ccopt/ccopt.aztcl .
Note : This parameter is applicable in the scripted CCOpt flow.
However, in the native CCOpt flow, you can use this parameter
with the -ckSpec parameter. In this case, the translated CCOpt
clock tree specification tcl commands will be written out to a file
and not be evaluated. Without the -genScriptOnly parameter,
the CCOpt clock tree specification commands are immediately
evaluated.
-import filename Executes the "import" stage of ccopt_design . The import stage
converts the .azdb design database file output by the "run" stage
into standard design data files (DEF, netlist, routing guides etc.)
and loads this optimized design database back into the software.
The filename variable specifies the name of the .azdb database
to convert. Design files are created in the az_import directory.
By default, ccopt_design executes all stages.
The filename argument specifies the name of the saved design
database ( .azdb file) to import.
Note : This parameter is only applicable in the scripted CCOpt
flow.
-inDir dirname Specifies the directory in which the files created during the import
stage are stored. These design files include DEF, netlist, routing
guides, and so on.
The default directory is ./az_import .
Note : This parameter is only applicable in the scripted CCOpt
flow.
-outDir dirname For the scripted integration mode of CCOpt, this parameter
specifies the directory in which the files created during the
generate and run stages of CCOpt are stored. These design files
include control scripts, saved design databases and so on.
The default directory is ./az_ccopt .
 For the native integration mode mode of CCOpt, this parameter
specifies the directory where the software writes timing reports
that are generated after timing optimization.
The default directory is ./timingReports
Note : This parameter is only applicable in the scripted CCOpt
flow.
-prefixfileNamePrefix Specifies a prefix for optDesign report file names. This
parameter is only used in native integration mode of CCOpt.
Default : DesignName_DesignStage , where DesignStage is
preCTS, postCTS, or postRoute
-runScript filename Executes the "run" stage of ccopt_design . The run stage
performs optimization by running the control script generated by
the generate stage and then saves the optimized design database as
a .azdb file.
The filename argument specifies the name of the control script to
run.
Note : This parameter is only applicable in the scripted CCOpt
flow.

Examples

 The following command runs a complete CCOpt optimization:

ccopt_design

 The following sequence of commands runs each stage of CCOpt individually. This lets you perform debugging between each
stage, or perform customization of the CCOpt control script:
ccopt_design -genScriptOnly control.aztcl

creates the control script . /az_ccopt/control.aztcl

ccopt_design -runScript control.aztcl

performs an optimization run using the control script ./az_ccopt/control.aztcl , saving the optimized design
database as./az_ccopt/<design_name>.azdb

ccopt_design -import ./az_ccopt/<design_name>.azdb

converts the optimized .azdb file to standard design data files (DEF, netlist, routing guides etc.) in
the az_import directory, and loads this optimized design database back into the software

Related Topics

 Clock Tree Synthesis chapter in the EDI System User Guide

o Flow and Quick Start