AR# 17706

|

9.1i PrimeTime - The clock skew differs between TRACE and PrimeTime

Description

When I perform a timing analysis in the Xilinx Timing Analysis tools and PrimeTime, I notice that the clock skew is different. Why is this the case?

Solution

The skew calculation in the Xilinx Timing tools creates issues because TRACE treats FF-to-FF paths on global clocks differently than FF-to-FF paths on local clocks.

Synopsys has provided a script that produces timing results in PrimeTime that are close to TRACE for Virtex-II Pro and Spartan-3.

AR# 17706
Date 01/18/2010
Status Archive
Type General Article
People Also Viewed