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

Design Advisory for Spartan-6 - BUFPLL LOCK output always high in Bank 2


**The fix for this issue is in the ISE 13.4 software, which is now available on www.xilinx.com/download**

The BUFPLL LOCK output in Bank 2 of all Spartan-6 devices does not function properly using ISE 13.3 and earlier software.


In ISE 13.4 and later software, the BUFPLL LOCK output behaves as expected in all banks. InISE 13.3 and earliersoftware, in all Spartan-6 devices, a modeling was identified for BUFPLLs in Bank 2 (BUFPLL_X1Y0, BUFPLL_X1Y1). As a result, the BUFPLL LOCK output has beenconnected High. Because the LOCK output is used only as a status signal, the BUFPLL and any IOLOGIC connected within Bank 2 will operate correctly. In the event that the PLL is reset, the BUFPLL output signals will be reset as well, consistent with normal BUFPLL operation, although LOCK will stay high throughout.

The BUFPLL LOCK output serves the exact same function as the PLL LOCKED signal except that it does not go high until the PLL has locked and the BUFPLL has aligned the SERDESSTROBE signal correctly. Because a user could be using the LOCK output to control the start of operation, designs may start before the BUFPLL or potentially the PLL has correctly locked. Designs using XAPP1064 in Bank 2 should be modified. MIG/MCB designs will not be affected.

The following show the LOCK behavior of the BUFPLL in Bank 2:

Next Steps:

  • Identify if a BUFPLL inBank 2 is used. This can be done in FPGA Editor or PlanAhead tool bylocating BUFPLL_X1Y0 andBUFPLL_X1Y1 and ascertaining whether they have been used in the design. It can also be done by looking at the Timing Report and searching for BUFPLL_X1Y0 and BUFPLL_X1Y1 to see if they are used.
  • The effect of this issue on a design depends on how the LOCK signal is used in the design. If one or both of the BUFPLLs in Bank 2 are used, determine the application risk of LOCK always being high. Here are a two examples ofitems to check:
    • Is the LOCK signal used to enable/reset downstream logic such as IOSERDES?
    • If the PLL output clock is lost but the BUFPLL LOCK signal is still high, could that have a negative effect on the design?
  • If the LOCK signal is required in the design, see below for a possible alternative.


  • Use ISE 13.4 software, which is now available.Re-implement the design with that version.

If ISE 13.4 cannot be used, some other options include:

  • Move the PLL/BUFPLL to a bank other than Bank 2.
  • Emulate the BUFPLL LOCK output by registering the LOCKED output of the PLL using a slice FF. Use this registered LOCKED signal as you would the LOCK output of the BUFPLL. This signal will be very similar to the correct behavior of LOCK. Designs with multiple BUFPLLs for multiple banks will commonly combine LOCK signals to ensure operation does not begin until all banks have properly locked.
  • Contact Xilinx Technical Support for additional options: www.support.xilinx.com

Linked Answer Records

Master Answer Records

Answer Number Answer Title Version Found Version Resolved
34856 Design Advisory Master Answer Record for Spartan-6 FPGA N/A N/A

Associated Answer Records

Answer Number Answer Title Version Found Version Resolved
34856 Design Advisory Master Answer Record for Spartan-6 FPGA N/A N/A
43769 Design Advisory Master Answer Record for Spartan-6 FPGA SP601 Evaluation Kit N/A N/A
AR# 45011
Date Created 12/05/2011
Last Updated 01/16/2013
Status Active
Type Design Advisory
  • Spartan-6 LX
  • Spartan-6 LXT
  • ISE Design Suite - 12.1
  • ISE Design Suite - 12.2
  • ISE Design Suite - 12.3
  • More
  • ISE Design Suite - 12.4
  • ISE Design Suite - 13
  • ISE Design Suite - 13.1
  • ISE Design Suite - 13.2
  • ISE Design Suite - 13.3
  • Less