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

Spartan-3A/-3AN /-3ADSP - What are the implications of using adjacent DCMs when the reset signal is not shared?


The Spartan-3 family User Guide provides the following recommendation for the Extended Spartan-3A family: 

"In the Extended Spartan-3A families, when two adjacent DCMs are used, the outputs should be considered valid once both DCMs are LOCKED.

Adjacent DCMs should share the same reset signal."


If an application is using adjacent DCMs without a shared reset, if either DCM loses LOCK, it is possible that there will be an effect on the output clocks of the other running DCM.

This can be seen as up to an additional 500pS of jitter on the output clocks. 

The following diagram shows the layout of the DCMs along with the adjacent pairs. For devices with less than 8 DCMs (for example, a Spartan-3A 200 which has 4 DCM located at the top and bottom of the device), each of these pairs are adjacent DCMs:

AR# 33350
Date Created 09/30/2010
Last Updated 09/11/2014
Status Active
Type General Article
  • Spartan-3A
  • Spartan-3A DSP
  • Spartan-3AN
  • Digital Clock Manager (DCM) Module