赛灵思
直播中

王静

7年用户 684经验值
私信 关注
[问答]

如何分享Spartan 3E DCM时钟输入频率变化信息

数据表显示,Spartan3E DCM可以处理高达1nSec的输入时钟边沿时序变化,前提是这种情况发生在“数百万”周期内。
但是,我有一个应用程序,在每小时10ppm的区域内频率变化可能很慢,总共50pmm,我找不到有关DCM是否会容忍这一点的任何信息。
有没有人对此有任何了解,他们愿意分享或了解任何其他信息来源?
谢谢你的帮助。
罗伯特

以上来自于谷歌翻译


以下为原文

The data sheet says that the Spartan3E  DCMs can cope with up to 1nSec of input clock edge timing variation provided this occurs over "millions" of cycles. However, I have an application where there may be slow frequency changes in the region of 10ppm per hour up to a total of 50pmm and I can't find any information about whether the DCMs wouldl tolerate this. Does anyone have any knowledge on this that they are willing to share or know of any source of additional information?

Thanks for any help.

Robert

回帖(2)

康志强

2019-7-18 10:03:08
嗨奥斯汀,
感谢您的回复,JITTER_FILTER参数看起来好像很有用。
问候
罗伯特

以上来自于谷歌翻译


以下为原文

Hi Austin,
 
Thanks for reply, the JITTER_FILTER parameter looks as if it may be useful.
 
Regards
 
 
Robert
举报

潘晶燕

2019-7-18 10:10:41
R,
如果您在验证时遇到任何困难,请尝试各种JITTER_FILTER值。
我怀疑它与DCM跟踪没有任何不同,但是在一些系统中存在突然的频率偏移,这有助于将采样减少到跳过的最少数量的时钟。
Austin Lesea主要工程师Xilinx San Jose

以上来自于谷歌翻译


以下为原文

R,
 
If you have any difficulty while verifying, try various JITTER_FILTER values.  I suspect it will make no diffefrence to DCM tracking, but there are sudden frequency shifts in some systems where it helps by reducing the sampling to the fewest number of clocks skipped.
Austin Lesea
Principal Engineer
Xilinx San Jose
举报

更多回帖

发帖
×
20
完善资料,
赚取积分