UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 18928

LogiCORE SPI-4.2 (POS-PHY L4) v6.1 - Timing analyzer reports "0 items analyzed" for an SPI-4.2 timing constraint

Description

General Description 

After I implement an SPI-4.2 v6.1 core, the trace report file (.twr) shows several timing paths that have 0 items analyzed.

Solution

This occurs because duplicated constraints are present in the NCF (TS_RDClk_P_REF and TS_SysClk_P_REF). These constraints are identical to those in the UCF (TS_RDClk_P and TS_SysClk_P). Therefore, only one of these constraints is fully analyzed.  

 

Note that a duplicated constraint in the NCF files is used as a reference constraint to generate the other constraints in the NCF file. This shows the dependencies of those constraints to the chosen core performance.  

 

These messages can be safely ignored. 

 

The duplicated timing constraints are as follows:  

 

1. Analyzed:  

================================================================================ 

Timing constraint: TS_RDClk_P = PERIOD TIMEGRP "RDClk_P" 2.119 nS HIGH 50.000000% ;  

 

3417 items analyzed, 0 timing errors detected. (0 setup errors, 0 hold errors)  

Minimum period is 2.045ns.  

--------------------------------------------------------------------------------  

Duplicated:  

================================================================================ 

Timing constraint: TS_RDClk_P_REF = PERIOD TIMEGRP "RDClk_P_REF" 2.119 nS HIGH 

50.000000 % ;  

 

0 items analyzed, 0 timing errors detected.  

--------------------------------------------------------------------------------  

 

2. Analyzed:  

================================================================================ 

Timing constraint: TS_SysClk_P = PERIOD TIMEGRP "SysClk_P" 2.119 nS HIGH 50.000000% ;  

 

102 items analyzed, 0 timing errors detected. (0 setup errors, 0 hold errors)  

Minimum period is 1.971ns.  

--------------------------------------------------------------------------------  

Duplicated:  

================================================================================ 

Timing constraint: TS_SysClk_P_REF = PERIOD TIMEGRP "SysClk_P_REF" 2.119 nS  

HIGH 50.000000 % ;  

 

0 items analyzed, 0 timing errors detected.  

--------------------------------------------------------------------------------  

 

3. Analyzed:  

================================================================================ 

Timing constraint: TS_pl4_snk_top0_pl4_snk_clk0_snkclk_dcmo = PERIOD TIMEGRP  

"pl4_snk_top0_pl4_snk_clk0_snkclk_dcmo" TS_RDClk_P_REF * 2.000000 HIGH 50.000 % ;  

 

15581 items analyzed, 0 timing errors detected. (0 setup errors, 0 hold errors)  

Minimum period is 4.212ns.  

--------------------------------------------------------------------------------  

Duplicated:  

================================================================================ 

Timing constraint: TS_RDClkDiv_GP = PERIOD TIMEGRP "RDClkDiv_GP" TS_RDClk_P * 

2.000000 HIGH 50.000 % ;  

 

0 items analyzed, 0 timing errors detected.  

--------------------------------------------------------------------------------  

 

4. Analyzed:  

================================================================================ 

Timing constraint: TS_pl4_src_clk0_SrcClk_dcmo_0 = PERIOD TIMEGRP 

"pl4_src_clk0_SrcClk_dcmo_0" TS_SysClk_P_REF * 2.000000 HIGH 50.000 % ;  

 

10122 items analyzed, 0 timing errors detected. (0 setup errors, 0 hold errors)  

Minimum period is 4.061ns.  

--------------------------------------------------------------------------------  

Duplicated:  

================================================================================ 

Timing constraint: TS_pl4_src_clk0_SrcClk_dcmo = PERIOD TIMEGRP 

"pl4_src_clk0_SrcClk_dcmo" TS_SysClk_P * 2.000000 HIGH 50.000 % ;  

 

0 items analyzed, 0 timing errors detected.  

--------------------------------------------------------------------------------

AR# 18928
Date Created 09/03/2007
Last Updated 05/16/2014
Status Archive
Type General Article