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# 20332

LogiCORE Generic Framing Procedure (GFP) v1.2 - "WARNING:Par:62 - Timing constraints have not been met"

Description

General Description: 

When running the example design through implementation, the following warning might occur in the PAR report file (routed.par): 

 

"WARNING:Par:62 - Timing constraints have not been met. 

 

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

* TS_M_CLK = PERIOD TIMEGRP "M_CLK" 5.900 | 5.900ns | 6.190ns | 4  

nS HIGH 50.000000 % | | |  

--------------------------------------------------------------------------------"

Solution

The example design provided runs the GFP Core through implementation with default performance requirements. However, the GFP Core will run at higher frequencies than the example design illustrates. For maximum frequency ranges, refer to the GFP data sheet. 

 

The example design brings all internal Core I/Os out to pads. In a real application, all of the GFP I/Os interface to other IP Cores, or to user logic. Because all I/Os are routed to pads, the example design should not be used to measure maximum Core operating performance. Rather, the best method of determining operating frequencies is in a real application interfacing to the GFP Core. Note that if timing simulation is performed, you are limited to the maximum operating frequency as reported by PAR. 

 

This issue will be fixed in the next GFP release, scheduled for Q1 2005. If you need a fix for this sooner, please contact the Xilinx hotline.

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