奥斯汀写道:
b,
使用的DCM是否具有CLKFX输出?
在DFS模式(合成)中,失败是停止转换(当LOCKED保持为真时)。
当时钟源的抖动超出DFS能够跟踪的抖动时,就会发生这种情况。
嗨,奥斯汀,谢谢你的阅读。
没有DFS,只有DLL。
输入时钟丢失有一个状态标志,这对我们没有帮助,但检查是否需要复位也很好。
在我挖掘并将DCM LOCKED带到测试点之前,我考虑过检查,然后我读了详细信息并意识到无输入时钟状态行保持复位状态,直到DCM锁定为止。
我曾假设DCM没有锁定,所以它不是一个有用的输出。
现在,我发现DCM已锁定,我应该重新评估。
您可能必须创建一个活动检测器来强制重置。
这就是我的想法。
很简单。
在DLL相关的DCM输出的情况下,我不知道输入时钟是好的任何情况,并且输出时钟被卡住。
这可能是一个不好的部分(这一部分有这个问题)?
“好”的消息是,这发生在不止一块板上!
(多个板上的可重复错误比在一块板上发生的要好。)
每个板有两个S6(总共16个ADC通道,8个馈送一个FPGA),问题主要发生在一个特定的FPGA和通道上。
有几次我看到它会影响另一个FPGA上的同一个通道。
尽管FPGA使用很少,但它们都是消防呼吸器,所以有一个冷却块,冷却水通过它安装在FPGA上。
好的,更深入研究报告。
----------------------------是的,我这样做是为了谋生。
以上来自于谷歌翻译
以下为原文
austin wrote:
b,
Is that DCM in use have a CLKFX output?
In the DFS mode (synthesis) the failure is to stop transistioning (while LOCKED remains true). It happens when the clock source has jitter beyond what the DFS is able to track.
Hi, Austin, thanks for reading.
No DFS, just the DLL.
There is a status flag for the loss of input clock, and that is not going to help, but that also is good to check to see if a reset is required.
Before I dug in and brought out the DCM LOCKED to a test point, I had considered checking that, then I read the details and realized that the no-input-clock status line is held in reset until the DCM locks. I had assumed that the DCM wasn't locking, so it wasn't a useful output. Now that I see that the DCM locked goes true, I should reassess.
You may have to create an activity detector to force a reset.
That is what I figured. Simple enough.
In the case of the DLL releated outputs of the DCM, I am unaware of any case where the input clock is good, and the output clock is stuck. Might this be a bad part (this one part has this problem)?
The "good" news is that this this happens on more than one board! (Repeatable bugs across more than one board are better than it happening on one board.)
Each board has two of the S6s (total 16 ADC channels, 8 feeding one FPGA), and the problem occurs mostly on one specific FPGA and channel. A couple of times I have seen it affect the same channel on the other FPGA.
Even though the FPGAs are lightly utilized, they are firebreathers, so there is a cooling block with chilled water running through it mounted against the FPGAs.
OK, more delving into reports.
----------------------------Yes, I do this for a living.
奥斯汀写道:
b,
使用的DCM是否具有CLKFX输出?
在DFS模式(合成)中,失败是停止转换(当LOCKED保持为真时)。
当时钟源的抖动超出DFS能够跟踪的抖动时,就会发生这种情况。
嗨,奥斯汀,谢谢你的阅读。
没有DFS,只有DLL。
输入时钟丢失有一个状态标志,这对我们没有帮助,但检查是否需要复位也很好。
在我挖掘并将DCM LOCKED带到测试点之前,我考虑过检查,然后我读了详细信息并意识到无输入时钟状态行保持复位状态,直到DCM锁定为止。
我曾假设DCM没有锁定,所以它不是一个有用的输出。
现在,我发现DCM已锁定,我应该重新评估。
您可能必须创建一个活动检测器来强制重置。
这就是我的想法。
很简单。
在DLL相关的DCM输出的情况下,我不知道输入时钟是好的任何情况,并且输出时钟被卡住。
这可能是一个不好的部分(这一部分有这个问题)?
“好”的消息是,这发生在不止一块板上!
(多个板上的可重复错误比在一块板上发生的要好。)
每个板有两个S6(总共16个ADC通道,8个馈送一个FPGA),问题主要发生在一个特定的FPGA和通道上。
有几次我看到它会影响另一个FPGA上的同一个通道。
尽管FPGA使用很少,但它们都是消防呼吸器,所以有一个冷却块,冷却水通过它安装在FPGA上。
好的,更深入研究报告。
----------------------------是的,我这样做是为了谋生。
以上来自于谷歌翻译
以下为原文
austin wrote:
b,
Is that DCM in use have a CLKFX output?
In the DFS mode (synthesis) the failure is to stop transistioning (while LOCKED remains true). It happens when the clock source has jitter beyond what the DFS is able to track.
Hi, Austin, thanks for reading.
No DFS, just the DLL.
There is a status flag for the loss of input clock, and that is not going to help, but that also is good to check to see if a reset is required.
Before I dug in and brought out the DCM LOCKED to a test point, I had considered checking that, then I read the details and realized that the no-input-clock status line is held in reset until the DCM locks. I had assumed that the DCM wasn't locking, so it wasn't a useful output. Now that I see that the DCM locked goes true, I should reassess.
You may have to create an activity detector to force a reset.
That is what I figured. Simple enough.
In the case of the DLL releated outputs of the DCM, I am unaware of any case where the input clock is good, and the output clock is stuck. Might this be a bad part (this one part has this problem)?
The "good" news is that this this happens on more than one board! (Repeatable bugs across more than one board are better than it happening on one board.)
Each board has two of the S6s (total 16 ADC channels, 8 feeding one FPGA), and the problem occurs mostly on one specific FPGA and channel. A couple of times I have seen it affect the same channel on the other FPGA.
Even though the FPGAs are lightly utilized, they are firebreathers, so there is a cooling block with chilled water running through it mounted against the FPGAs.
OK, more delving into reports.
----------------------------Yes, I do this for a living.
举报