[SOLVED] CRPR Threshold in PT

Hi all!

I performed timing analysis in PT DMSA and have found that my "clock reconvergence pessimism" in report is 0 (crpr analysis is active), but my timing path has common clock path and CRPR value should be non-zero. I used "report_crpr" command on this path, results are presented below:

Common Clock: clk
Launching edge at common point: RISING
Capturing edge at common point: RISING
CRPR threshold: 0.1

Arrival Times (Static) Early Late CRP
---------------------------------------------------------------
Rise 0.1705 0.1896 0.0191
Fall 0.1675 0.1870 0.0195
---------------------------------------------------------------

Arrival Times (Dynamic) Early Late CRP
---------------------------------------------------------------
Rise 0.1641 0.1960 0.0319
Fall 0.1610 0.1935 0.0325
---------------------------------------------------------------

Selection Details
---------------------------------------------------------------
Arrival Times: Using Dynamic Arrivals
Edge Match: Match, using rise CRP
---------------------------------------------------------------
clock reconvergence pessimism 0.0319


Information: The CRP value reported by report_timing and report_clock_timing will be -0.0000. (UITE-468)

1

Click to expand...

As seen, we have difference btw actual and reported in the timing report values (UITE-468 message). I tried to reduce "CRPR_threshold" value from this report ( by seting " timing_crpr_threshold_ps" command), but it does not work, I can only increase "CRPR threshold" value, but not decrease. The question is - how I can set this CRPR Threshold value and make CRP value from this report and from "report_timing" equal?

The problem is solved by updating PT tool.