Z,
是的,CLKFX输出标称值为50%,+ / - 5%。
抖动是由ISE中的抖动计算器向导预测的。
占空比+/- 5%规范的原因只是“正常”工艺变化,因此我们假设给定部分的占空比为47%。
另一部分可能是51%,依此类推。
在占空比的顶部,存在上述抖动,来自抽头延迟线多路复用器选择不同的抽头以获得正确的频率(每9个输入时钟22个时钟)。
如果DCM模式使用CLKFB引脚,则每9个输入时钟,输出时钟(FX)被强制(硬对齐),以便CLKIN上升沿和CLKFX上升沿对齐到+/- 100ps
。
因此,来自抖动抖动的最大“命中”发生在每9个输入时钟或每22个输出时钟。
在查看使用CLKFX的上升沿或下降沿的时序时,不要忘记抖动和占空比。
如果您有适当的约束,这应该由工具自动完成。
检查一下,并确保CLKFX时钟域的数据路径有足够的松弛。
Austin Lesea主要工程师Xilinx San Jose
以上来自于谷歌翻译
以下为原文
z,
Yes, the CLKFX output is nominally 50%, +/- 5%.
The jitter is as predicted by the jitter calculator wizard in ISE.
The reason for the +/-5% specification on duty cycle is just "normal" process variations, so let us suppose a given part is 47% duty cycle. Another part might be 51%, and so on.
On top of the duty cycle, there is the jitter mentioned above, from the tapped delay line multiplexer choosing different taps to get the right freqency (22 clocks for every 9 input clocks).
If the DCM mode is such that the CLKFB pin is used, then every 9 input clocks, the output clock (FX) is forced (hard-aligned) so that the CLKIN rising edge, and the CLKFX rising edge align to +/- 100ps. Thus the biggest "hit" from the tap jitter occurs every 9 input clocks, or every 22 output clocks.
When looking at the timing of using the rising, or falling edge of CLKFX, don't forget the jitter, and the duty cycle. This should all get done automatically by the tools, if you have the proper constraint. Check that you do, and that you have sufficient slack on the data paths for the CLKFX clock domain.
Austin Lesea
Principal Engineer
Xilinx San Jose
Z,
是的,CLKFX输出标称值为50%,+ / - 5%。
抖动是由ISE中的抖动计算器向导预测的。
占空比+/- 5%规范的原因只是“正常”工艺变化,因此我们假设给定部分的占空比为47%。
另一部分可能是51%,依此类推。
在占空比的顶部,存在上述抖动,来自抽头延迟线多路复用器选择不同的抽头以获得正确的频率(每9个输入时钟22个时钟)。
如果DCM模式使用CLKFB引脚,则每9个输入时钟,输出时钟(FX)被强制(硬对齐),以便CLKIN上升沿和CLKFX上升沿对齐到+/- 100ps
。
因此,来自抖动抖动的最大“命中”发生在每9个输入时钟或每22个输出时钟。
在查看使用CLKFX的上升沿或下降沿的时序时,不要忘记抖动和占空比。
如果您有适当的约束,这应该由工具自动完成。
检查一下,并确保CLKFX时钟域的数据路径有足够的松弛。
Austin Lesea主要工程师Xilinx San Jose
以上来自于谷歌翻译
以下为原文
z,
Yes, the CLKFX output is nominally 50%, +/- 5%.
The jitter is as predicted by the jitter calculator wizard in ISE.
The reason for the +/-5% specification on duty cycle is just "normal" process variations, so let us suppose a given part is 47% duty cycle. Another part might be 51%, and so on.
On top of the duty cycle, there is the jitter mentioned above, from the tapped delay line multiplexer choosing different taps to get the right freqency (22 clocks for every 9 input clocks).
If the DCM mode is such that the CLKFB pin is used, then every 9 input clocks, the output clock (FX) is forced (hard-aligned) so that the CLKIN rising edge, and the CLKFX rising edge align to +/- 100ps. Thus the biggest "hit" from the tap jitter occurs every 9 input clocks, or every 22 output clocks.
When looking at the timing of using the rising, or falling edge of CLKFX, don't forget the jitter, and the duty cycle. This should all get done automatically by the tools, if you have the proper constraint. Check that you do, and that you have sufficient slack on the data paths for the CLKFX clock domain.
Austin Lesea
Principal Engineer
Xilinx San Jose
举报