Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Rubix STA-Setup PrimeTime Custom Command, ARM Ltd.
- NAME
- rbx_analyze_rc011
- SYNTAX
- rbx_analyze_rc011 -pt_log <primetime_log_file_with_rc011> [-check_type setup | hold] [-rc011_slack_lesser_than lesser_slack_limit]
- ARGUMENTS
- -pt_log <primetime_log_file_with_rc011>
- This is the log file which contains the RC-011 error messages.
- The log files cannot be in compressed format (zip, gzip etc).
- This is a mandatory option.
- -check_type [setup | hold]
- Default: setup
- o setup - Checks the impact of RC-011 messages on setup timing.
- o hold - Checks the impact of RC-011 messages on hold timing.
- -rc011_slack_lesser_than <lesser_slack_limit>
- Default: 0
- This command calculates the setup or hold slacks that would result
- on certain paths after the RC-011 errors related to those paths are
- fixed. This option directs the command to report only the paths with
- slack less (more negative) than lesser_slack_limit.
- DESCRIPTION
- RC-011 errors of one or more timing arcs in a path may not cause timing violation
- if the slack of that path is considerably higher than the sum of those arc delays.
- This command reads the RC-011 errors from a log file and checks the impact of each
- error on paths slack. If there are multiple cells in a path with RC-011 error then
- the cumulative effect of in-accuracies in delay calculation of all these cells is taken
- into account. Designers can use the report generted by this command to make a decision
- of wheather they want to fix the errors or waive them.
- Generally setup and hold analysis are run as different scenarios and consequently different
- log files could be generated. -check_type option of this command could be used to
- analyze the impact on either setup or hold timing based on the RC-011 errors present
- in the log file specified with -pt_log option. This command analyzes both scenarios where
- the RC-011 is caused by output load being outside the table limits and input slew being
- outside the table limits.
- EXAMPLE
- In the following example a STA session with RC-011 errors is restored. Then in this restored
- session the following command is run to check the impact of RC-011 errors on the hold timing.
- The log file "design_hold_scenario.log" is generated by the run that created "scen1_hold_anal.session".
- pt_shell> restore_session scen1_hold_anal.session
- pt_shell> rbx_analyze_rc011 -pt_log design_hold_scenario.log -check_type hold -rc011_slack_lesser_than 0.400
- *********************************************************************************************
- Rubix Custom Report
- Report : rbx_analyze_rc011
- -pt_log design_hold_scenario.log
- -check_type hold
- -rc011_slack_lesser_than 0.400
- Design : my_design
- Version : J-2014.06-SP3
- Date : Fri Apr 3 14:33:43 2015
- *********************************************************************************************
- Type:
- OL - Over Table Limit
- UL - Under Table Limit
- Type RC011-Slack Path-hold-Slack Endpoint
- ---- ----------- ---------------- --------
- Stage Delay RC011-Data-Pins
- ----------- ---------------
- OL 0.381 0.380 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/cp_gov_wdata_rs_o_reg_0/R
- 0.029 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/PlaceOpt_FE_OFC34940_n_1599/A
- OL 0.385 0.384 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/excl_mon_cleared_o_reg/R
- 0.029 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/PlaceOpt_FE_OFC34940_n_1599/A
- OL 0.341 0.340 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/gov_cp_ack_reg/R
- 0.029 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/PlaceOpt_FE_OFC34940_n_1599/A
- OL 0.366 0.365 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/gov_int_active_reg/R
- 0.029 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/PlaceOpt_FE_OFC34940_n_1599/A
- OL 0.390 0.389 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/gov_mbistreq_cpu_o_reg/R
- 0.029 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/PlaceOpt_FE_OFC34940_n_1599/A
- OL 0.364 0.363 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/vsei_level_req_reg/R
- 0.029 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/PlaceOpt_FE_OFC34940_n_1599/A
- UL 0.070 0.100 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53scu/u_scu_master/g_ace_u_master_ace/scu_ext_dw_data_reg_56/SI
- 0.037 u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53scu/u_scu_master/g_ace_u_master_ace/DFT_multi_mode_115/B0
- Type RC011-Clock-Pin
- ---- ---------------
- OL, UL u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/AZ_cdb_INV_cpuclk_post_occ_G1_L66_795/A
- OL u_columbus64_apollo_core_integration/u_columbus64_apollo_core/u_CORTEXA53/u_ca53_l2/u_ca53_l2noram/u_ca53governor/g_governor_cpu_3_u_governor_cpu/u_governor_cpu_slice/inv_scu_tag_state_reg/CK
- 1
- Note that the "Type" column shows if the extrapolation is done over the table limit
- or below the table limit. The first part of the report shows the data pins with RC-011
- violations and the second part shows the clock pins with this vioaltion. The command
- does not do any triaging on the clock pins since in general such violations on clock
- circuitry cannot be waived and have to be fixed.
- Rubix STA-Setup PrimeTime Custom Command, ARM Ltd.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
