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

LogiCORE Generic Framing Procedure (GFP) v1.3 - Release Notes and Known Issues for the GFP Core

Description

This Release Note is for the Generic Framing Procedure (GFP) Core v1.3. The core is being re-released in 8.1i IP Update 1 to be fully compatible with ISE 8.1i. This particular version was initially released in 7.1i IP Update 1 and was available in 7.1i IP Update 2. 

 

- New Features 

- Bug Fixes 

- Known Issues 

 

NOTE: The GFP v1.3 version released in IP Update #1 for 8.1i is the only one that can be used with the ISE8.1i. The previous releases are compatible with ISE7.1i. There were no changes made to the core other than the added ISE 8.1i support; therefore, the Known Issues mentioned in this Answer Record are still applicable. 

 

For installation instructions and design tool requirements for 7.1i IP Update 1, see (Xilinx Answer 21019)

For installation instructions and design tool requirements for 7.1i IP Update 2, see (Xilinx Answer 21737)

For installation instructions and design tool requirements for 8.1i IP Update 1, see (Xilinx Answer 22155).

Solution

New Features in v1.3  

 

- Support added for ISE 8.1i 

 

Bug Fixes in v1.3  

 

CR 197627: PAR fails timing constraint 

Symptom: 1 constraint not met. 

 

CR 197909: 64-bit Transparent UNMAP Core drops a cycle of data  

Symptom: A word of data is dropped if a stall is induced on the UNMAP line interface while writing transparent frames. 

 

CR 197760: 64-bit loopback module creates an invalid stream  

Symptom: The 64-bit loopback (in VHDL only), when parallel hunting is enabled, creates an invalid stream if two back-to-back EOFs are received. 

 

CR 197898: 64-bit core loses synchronization when a certain pattern of frames is received  

Symptom: The UNMAP Core loses synchronization on a frame when in "parallel hunt" or "idle hunt" mode if a frame with length n+1, n+2, or n+3 bytes (where n is a multiple of 8 bytes) is received, followed by a very short (4 byte) frame. 

 

CR 197902: 64-bit core loses synchronization when barker-scrambling is off  

Symptom: The UNMAP Core loses synchronization on a frame when barker-scrambling is disabled, and a frame is received that ends in at least 32 "0". 

 

Known Issues in v1.3  

When implementing GFP design example, a MAP error reports that the design is too large for the targeted device.  

See (Xilinx Answer 21295).

AR# 21030
Date Created 09/04/2007
Last Updated 05/19/2014
Status Archive
Type General Article