J
Jim Granville
Guest
austin wrote:
Suppose the clock starts as 'any trashy crystal', but is then fed via
another Xilinx DLL - is there a chain-limit of jitter degradation, in
such a system ?
This will become a more common scenario...
-jg
Austin,Marc,
It turns out that if you are going only to the DFS, and you do not move
the frequency very fast, you can sweep from min to max input (output)
frequency before losing lock.
The DLL is fussier, as it chooses to arrange its six delay lines based
on what options, range, and where it locks. So in the DLL, if you
start sweeping the frequency, you may get an overflow or underflow on
one of the delay lines, and lose lock.
We typically spec +/- 100 ppm, because just about any trashy crystal
can do that. In reality, +/- .01 is probably safe.
Suppose the clock starts as 'any trashy crystal', but is then fed via
another Xilinx DLL - is there a chain-limit of jitter degradation, in
such a system ?
This will become a more common scenario...
-jg