MM,
You decide where to put the pins.
Input clocks to the DCM should come from the global clock IO pins (those
IBUFG routes are optimized for 0 delay).
Output clocks should go to a BUFG where they can get used by the things
that need them.
If you wish to observe a clock, route the BUFG to a IOB, set the IOB to
be a DDR, set the top DFF D input to '1', and the bottom DFF D input to
a '0'.
This preserves the duty cycle to within a few tens of ps, and you may
then see exactly what your clock is doing.
Using a differential output standard, and measuring the output
differentially will allow you to see the jitter on the internal BUFG,
excluding any ground or Vcc bounce (as the differential output and
differential measurement ignores common mode changes!).
The CLOCK_FB (feedback clock) to the DCM should always come from the
source which you are trying to align to create 0 skew: ie. the output
BUFG itself, or if that output is sent off-chip, another global clock
input pins (IBUFG)-- 0 skew is created at the point where the clock is
delivered off-chip..
Austin
MM wrote:
> <[email protected]> wrote in message
> news:[email protected]...
>> The only problem is that i have no idee which pins belong to the
>> DCM...and don't know how to connect the DCM's clock outputs to the
>> DIFF CLK output-pins in order to measure them.
>> So if anybody could tell me which bank and pin-number belongs to the
>> DCM(s) i would be very happy 
>>
>
> There are no pins belonging to DCMs. There are pins dedicated as clock
> inputs though. Usually pin assignments are handled in the project's UCF
> file. For your differential output you need to instantiate a differential
> driver in your HDL code and assign the pins in the UCF.. Driving clock out
> of the chip is better done with a DDR register in IOB, but this is another
> issue, probably not important for you at this point.
>
>
> /Mikhail
>
>
>
>