Man Page - rbx_get_noise_pin_details

Rubix STA-Setup PrimeTime Custom Command, ARM Ltd.

	NAME
	  rbx_get_noise_pin_details

	SYNTAX
	  rbx_get_noise_pin_details -noise_report <noise_report>

	ARGUMENTS
	  -noise_report <noise_report>
		This is the list of reports written out by report_noise with -nosplit option.
		The list could for example contain the reports written out by this command from
		sessions of different analysis conditions (PVT corners). But the information presented
		by this command is from within the PrimeTime session on which this command is run. So
		typically this command is run on a session (scenario) which has the worst noise violations.
		The report files cannot be in compressed format (zip, gzip etc).This is a mandatory option.

          -noise_region [all | above_low | below_high | below_low | above_high]
                Default: all
		If this value is all, then pins violating in all noise regions are reported. Alternatively
		one could choose to report only the pins in a given region with this option.


	DESCRIPTION
		This commands reads in a list of reports written by report_noise command, analyzes and
		them provides useful information. This command provides a many useful information about an
		noise victim pin which could be use for fixing the noise violations.

	EXAMPLE
                In the following example the pin u_ca57cpu/u_inst28/A reported in the noise report file report_noise_all_vio.rpt
		is analyzed and the information required for understanding and fixing it is presented by this command.

		pt_shell> rbx_get_noise_pin_details -noise_report  ../reports/report_noise_all_vio.rpt -noise_region all

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

		 Report    : rbx_get_noise_pin_details
		            -noise_report /projects/pj00610_junosoc/Users/ramswa02/apollo/sta/rubix_0.2.0_new/test_inputs/report_noise_all_vio.rpt
		 Design    : columbus64_apollo_integration
		 Version   : J-2014.06-SP3
		 Date      : Fri Apr 24 10:23:27 2015
		*********************************************************************************************
		# Slack_S  Slack_H    Is Clock  Pin                   Net              Driver                 Aggressors Count   { Aggressors }
		#-----------------------------------------------------------------------------------------------------------------------------------------------------------
		-          -          No        u_ca57cpu/u_inst28/A  u_ca57cpu/n_28   u_ca57cpu/u_inst27/Y   2			 { u_ca57cpu/n_24 u_ca57cpu/n_21 }


		1

		This reports shows the pin u_ca57cpu/u_inst28/A which has noise violation, the net u_ca57cpu/n_28 connected to
		it and u_ca57cpu/u_inst27/Y which is the driver of that net. The number of aggressors helps understanding the
		severity of the problem, quality of routing of the net and in many cases even the quality of routing in the
		region of the die the net belongs to.


Rubix STA-Setup PrimeTime Custom Command, ARM Ltd.