Man Page - rbx_report_unconstrained_endpoints

Rubix STA-Setup PrimeTime Custom Command, ARM Ltd.

	NAME
	  rbx_report_unconstrained_endpoints

	SYNTAX
	  rbx_report_unconstrained_endpoints -output <output_file> -remove_clocks <list_of_clocks> -omit_insts_strings <list_of_instance_name_strings>

	ARGUMENTS
	  -output <output_file>
		The report is printed out to this file. This is a mandatory input.

	  -remove_clocks <list_of_clocks>
		Default: none
		The clocks given in this list are removed before unconstrained pins are checked for.
		For example if the design is constrained for both functional and test modes then
		one could choose to remove test clocks by specifying them in this option. Then this
		command would report the pins that are not constrained with-respect-to functional
		clocks only. Also removing a master clock does not result in its generated clocks being
		removed and vice versa. Hence the users should specify all the clocks they intend to remove.
		Note if this option is used then the PrimeTime session may not be usable in
		the usual way since some of the clocks will be missing. Hence either restart the session
		after using this command or redefine the removed clocks and make sure that the design is timed
		as intended, before further analysis.

	  -omit_insts_strings <list_of_instance_name_strings>
		Default: none
		If the check has to ignore certain instances or heirarchical instances then this option
		can be used. When the full_name of a timing endpoint pin matches one of the strings given
		in this list then that pin is ignored from this check. This is useful for example when
		sub-blocks with know constraints issues need to be omitted for the time being.
		See example below for more details.

	DESCRIPTION
		This check identifies the timing endpoints by looking up "is_data_pin" and "is_clock_gating_pin"
		attributes in the library. Then it checks if a timing path exists to each one of these endpoints.
		Then it reports every endpoint that does not have any timing path related to itself along with the
		reason for being unconstrained. Sometimes the unconstrained pin may not have "dominant_exception"
		attribute. In that case the reason will be "Not Known".

	EXAMPLE
                Lets say we have a design with three clocks defined in a session viz scan_clk, bist_clk and f_clk.
		Following command removes the clocks scan_clk and bist_clk and then checks for the endpoints that
		are not constrained. It also omits all the endpoints that are within bist controllers and scan compressor
		blocks. Say there are hierarchical instances i_sub1/i_memory_group_1/i_bist_controller, i_sub2/i_memory_group_2/i_bist_controller,
		i_sub2/i_scan_compressor in the design. All the timing endpoints within these blocks will be omitted
		for this analysis. For example if there is a register endpoint called i_sub2/i_memory_group_2/i_bist_controller/i_blk1/reg1/D
		then this will be omitted from the analysis.

		pt_shell> rbx_report_unconstrained_endpoints -output unconst.rpt -remove_clocks "scan_clk bist_clk" -omit_insts_strings "i_bist_controller i_scan_compressor"

		***********************************************************************
		 Rubix Custom Report

		 Report    : rbx_report_unconstrained_endpoints
		            -removed_clocks $remove_clocks
		            -omit_insts_strings $omit_insts_strings
		 Design    : my_design
		 Version   : J-2014.06-SP3
		 Date      : Tue Mar  3 17:22:02 2015
		***********************************************************************
		 Unconstrained pins are generated after removing the following clocks

		 $removed_clocks =
		                   scan_clk
		                   bist_clk
		***********************************************************************
		 All the instances with the following string(s) are omitted from the analysis

		 $omit_instance_strings =
		                   i_bist_controller
		                   i_scan_compressor
		***********************************************************************
		 Unconstrained pins are generated with the following clocks in the session
		                   f_clk
		***********************************************************************

		Unconstrained Reason	Unconstrained Pin
		-----------------------------------------------------------------------
		Not Known            	DFT_ieee1500_cell_CLKEVNT/DFT_ieee1500_flop/D
		Not Known            	DFT_ieee1500_cell_CLKGIC/DFT_ieee1500_flop/D
		Not Known            	sync_cell_1/R_reg_0/D
		Not Known            	sync_cell_2/R_reg_0/D

		***********************************************************************
		 Summary:
		      No of Data Endpoints unverified / verified     = 200/564035
		      No of ClkGate Endpoints unverified / verified  = 10/24850
		***********************************************************************

		1

		In this example there are 200 data endpoints and 10 clock gate enable pins in the blocks
		i_sub1/i_memory_group_1/i_bist_controller, i_sub2/i_memory_group_2/i_bist_controller
                and i_sub2/i_scan_compressor put together. Non of them are verified by this
		command as stated in the Summary portion.

Rubix STA-Setup PrimeTime Custom Command, ARM Ltd.