New requirements have been introduced into the DCM model that are causing this discrepancy. These requirements have been added based on new results from testing the DCM. The new requirements are as follows:
- The RST input signal is asynchronous and should be held High for
at least three clock cycles.
- While the DCM is in reset, a valid clock should be provided to the CLKIN pin of the DCM.
The older DCM model was not checking for this condition.
The Virtex-II/-II Pro and Spartan-3 User Guides list these requirements as well:
http://www.xilinx.com/xlnx/xweb/xil_publications_index.jsp?category=User+Guides Beginning with the ISE 8.1i Service Pack 2, if these requirements are not met, the LOCK signal will go to X.