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

Spartan-6, DCM_CLKGEN - After changing the M and D via SPI, how long before the LOCK re-asserts?

Description

When I perform a simulation of the DCM_CLKGEN and change the M and D via SPI, the LOCK does not de-assert. Should it? Also, how long should it take to re-assert?

Solution


The is an issue in the unisim and simprim models in ISE 12.2 and earlier software.The LOCK does not de-assert after you change the M and D values. This issue is to be fixed in ISE Design Suite12.3.
The correct functionality of the LOCKED signal is described in the Spartan-6 FPGA Clocking Resources User Guide (UG382):
http://www.xilinx.com/support/documentation/user_guides/ug382.pdf
The LOCK re-asserts after PROGDONE has gone High. The length of time for this to occur is specified as LOCK_FX in the Spartan-6 FPGAData Sheet (DS162):
http://www.xilinx.com/support/documentation/data_sheets/ds162.pdf


Linked Answer Records

Associated Answer Records

Answer Number Answer Title Version Found Version Resolved
46790 Spartan-6 FPGA Design Assistant - Troubleshooting Common Clocking Problems N/A N/A
AR# 37648
Date Created 09/30/2010
Last Updated 12/15/2012
Status Active
Type General Article
Devices
  • Spartan-6 LX
  • Spartan-6 LXT