AR# 38174

描述

解决方案

This warning can occur in two scenarios:

• When the tools place the PLL instance in a location where the global clock routing cannot be accessed. This prevents the tools from routing the signals to the proper buffers and causes the failure. Manually constraining the PLL instance to a different location should help to resolve the issue. Following is an example constraint:
  

  INST "clock_generator_0/clock_generator_0/PLL1_INST/Using_PLL_ADV.PLL_ADV_inst" LOC=PLL_ADV_X0Y5;
  
  

  This specific constraint will be different depending on the design. This issue was tested in 12.3 and there were no warning messages in the design.
  
• When using multiple resources in the Clock Generator block (e.g., DCM and PLL both configured within the Clock Generator). The Clock Generator then produces a LOCKED signal output which is the DCM_LOCKED signal ANDed with the PLL_LOCKED signal. However, when using the MPMC block in a Spartan-6 device, it is unroutable to connect this combined CLK_GEN_LOCKED signal to the MPMC input LOCKED pin because the MPMC for the Spartan-6 device must use the BUFPLL_MCB which has to connect to the PLL_LOCKED signal directly, or else the unroutable situation described above can occur. This is a hardware limitation in Spartan-6 FPGA. To work around this issue, it is necessary to split the DCM and PLL clocking configurations into two Clock Generator cores; and as such, use two Clock Management Tiles on the device. This ultimately allows the PLL_LOCKED signal to be output directly from the Clock Generator instance 1 block into the MPMC and connect directly to the BUFPLL_MCB. CRs have been filed to help identify this issue by enhancing the message from the Router and also improving the documentation.