The violations are categorizes based on the reason why they cannot be fixed

The violations are categorizes based on the reason

This preview shows page 145 - 148 out of 502 pages.

The violations are categorizes based on the reason why they cannot be fixed. When you use this command, you must specify the type of violation you want to analyze by specifying one of the following setting with the -type option: max_trans to analyze maximum-transition violations setup to analyze setup violations hold to analyze hold violations only_lib to analyze library settings that affect optimization In addition, you can specify the following: A threshold for identifying high-fanout nets by using the -fanout option. By default, the tool considers nets with a fanout larger than 30 to be high-fanout nets. A slack threshold for identifying small timing violations by using the -slack option. By default, the tool considers any slack violation less than 5 picoseconds as a small violation. Nets for maximum-transition analysis by using the -drc_nets . By default, analyzes all nets for maximum-transition violations. Endpoints for setup and hold analysis by using the -endpoints option. By default, analyzes all endpoints for setup and hold violations. An output file name by using the -output option. The tool adds a .txt extension to the output file name you specify. By default, the tool generates a file named analyze_design_violations.txt.
Image of page 145
Chapter 3: Placement and Optimization Analyzing the Power 3-70 IC Compiler™ II Implementation User Guide L-2016.03-SP4 IC Compiler™ II Implementation User Guide Version L-2016.03-SP4 Analyzing the Power To calculate and report the power for a block, use the report_power command. The tool uses the value of the cell_leakage_power attribute of the library cells in the block to calculate the leakage power. If a cell does not have a cell_leakage_power attribute, the tool use the value of the library-level default_cell_leakage_power attribute for that cell. The IC Compiler II tool supports the following methods for calculating the leakage power: Average When using this method, the calculation is based on equal weighted probabilities for all states. Unconditional When using this method, the calculation is based purely on the attribute values. State When using this method, the calculation is based on the state of each instance, as set by the set_case_analysis command. If there is no case-analysis constraint set on an instance, the tool assumes equal weighted probabilities for all states. Change the method used for leakage-power calculation by using the power.leakage_mode application option. icc2_shell> set_app_options -name power.leakage_mode -value average By default, the report_power command calculates the leakage power by using the average method and reports a power summary for all active, power-enabled corners for the whole chip.
Image of page 146
Chapter 3: Placement and Optimization Analyzing the Power 3-71 IC Compiler™ II Implementation User Guide Version L-2016.03-SP4 Example 3-6 shows a default power report.
Image of page 147
Image of page 148

You've reached the end of your free preview.

Want to read all 502 pages?

  • Fall '19
  • Clock signal, Electronic design automation, Clock distribution network, nets

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture