Kintex 7系列RX锁失败

你好
您能否提供有关您正在使用的IP和您的设计的更多详细信息
Vivado和核心版本以及RX Lock你在这里推荐
问候，萨蒂什-----------------------------------------------
--- --------------------------------------------请注意
- 如果提供的信息有用，请将答案标记为“接受为解决方案”。给予您认为有用的帖子。感谢.--
---------------------------- ---------------------
----------------------



以下为原文

Hi
 
Can you give more details on the IP you are using and your design
 
Vivado and core version and which RX Lock you are referrig here
Regards,

Satish

--------------------------------------------------​--------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful.
--------------------------------------------------​-------------------------------------------

在PCS环回模式下，如果没有从TXP / TXN到RXP / RXN的连接，则CDR的RXRECCLK输出预计不会好。
这是由于输入锁定时缺少数据转换。
如果设计需要RXRECCLK用于其结构逻辑，则设计可能会失败。
对于这些设计，建议在“锁定到参考”模式下使用CDR。按照以下步骤确保CDR处于“锁定到参考”模式：步骤1：驱动以下信号设置RXOUTCLKSEL以选择RXOUTCLKPCS，（或
）将RXCDRHOLD设置为1'b1并将RXCDROVRDEN设置为1'b0步骤2：对收发器执行完全RX复位GTRXRESETIf设计不使用RXRECCLK用于结构逻辑，仅需要步骤2。
谢谢和RegardsBalkrishan -----------------------------------------------
---------------------------------------------请将帖子标记为
一个答案“接受为解决方案”，以防它有助于解决您的查询。如果一个帖子引导到解决方案，请给予赞誉。



以下为原文

In PCS loopback mode, if there is no connection from TXP/TXN to RXP/RXN, then RXRECCLK output from CDR is not expected to be good.

This is due to a lack of data transitions at the input to lock to.

If a design requires RXRECCLK for its fabric logic, the design can fail.

For these designs, it is recommended to use CDR in "lock to reference" mode.

Follow the steps below to make sure that the CDR is in "lock to reference" mode:

Step1: Drive the following signals
Set RXOUTCLKSEL to select RXOUTCLKPCS,

(OR)

Set RXCDRHOLD to 1'b1 and RXCDROVRDEN to 1'b0



Step2: Perform a full RX reset of the transceiver

Pulse GTRXRESET

If a design does not use RXRECCLK for fabric logic, only Step 2 is required.Thanks and Regards
Balkrishan
--------------------------------------------------------------------------------------------
Please mark the post as an answer "Accept as solution" in case it helped resolve your query.
Give kudos in case a post in case it guided to the solution.

嗨，
感谢您的回复。为什么这个故障只发生在三块板上，剩下的17块板工作正常。这会在其他板上慢慢发生吗？
问候
巴拉



以下为原文

Hi ,
 
Thanks for the response.Why this failure occurs only on three board,remaining 17 boards are working fine.Will this occur slowly on other boards also?
 
Regards
bala

AR＃60488是否涉及此问题？
问候
巴拉



以下为原文

Does AR#60488 relate this issue?
 
Regards
bala

你好
在没有提供详细信息的情况下很难发表评论（已在第2篇帖子中提出要求）。
使用您正在使用的IP核，版本的核心和vivado / ISE版本详细解释您的问题
问候，萨蒂什-----------------------------------------------
--- --------------------------------------------请注意
- 如果提供的信息有用，请将答案标记为“接受为解决方案”。给予您认为有用的帖子。感谢.--
---------------------------- ---------------------
----------------------



以下为原文

Hi
 
It's difficult comment with out providing the details(Already requested this in 2nd post).
 
Explain you issue in detail with IP cores you are using,version of the cores and the vivado/ISE version
Regards,

Satish

--------------------------------------------------​--------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful.
--------------------------------------------------​-------------------------------------------

嗨，
它的vivado 2013，我们正在使用MTG核心115，115的一个频道失败，而同一组中的其他频道都很好。
问候
巴拉



以下为原文

Hi,
 
Its vivado 2013,and we   are using MTG core 115,and one of the channel of 115 is failing,whereas other channels in the same group are fine.
 
Regards
bala

你好
你能查看最新版的vivado吗？
什么是Gt向导中选择的协议。
问候，萨蒂什-----------------------------------------------
--- --------------------------------------------请注意
- 如果提供的信息有用，请将答案标记为“接受为解决方案”。给予您认为有用的帖子。感谢.--
---------------------------- ---------------------
----------------------



以下为原文

Hi
 
Can you check with latest version of vivado?
 
What is the protocol selected in the Gt wizard.
Regards,

Satish

--------------------------------------------------​--------------------------------------------
Kindly note- Please mark the Answer as "Accept as solution" if information provided is helpful.

Give Kudos to a post which you think is helpful.
--------------------------------------------------​-------------------------------------------

嗨，
是的，我们使用了最新的向导，但没有运气。
我们只选择了正确的协议，因为在40个板中，17个板显示了这个错误。
如果协议是一个问题，那么我们应该在所有板上看到这个错误。
将参考时钟的交流耦合电容从100nF替换为10nF也有助于恢复某些电路板。
我仍然怀疑RX复位序列，因为我们观察到这个错误，只要systemthrowsRXresetsequence和initWaitcount更多。
对于这样的问题，这可能是一个什么问题？
如果在所有董事会上都观察到问题，那么我们将更容易解决问题。 
问候
巴拉



以下为原文

Hi,
 
Yes we used latest wizard, but no luck.
 
We selected correct protocol only, because among 40 board, 17 board showing this error. If protocol is an issue, then we should see this error on all the boards.
 
Also replacing Ac coupling capacitor of reference clock from 100nF to 10nF helps to recover some of the board.
 
Still i am suspecting RX reset sequence as we observer this error whenever system throws RXresetsequence and initWaitcount is more.
 
What could be an issue for such issue? If the issue is observed on all the board, then it will be easier for us to fix.
                                                                                                                                                    
Regards
bala

这事有进一步更新吗。
我身边的另一个更新是，
当我们使用特定的晶体osc时，系统工作正常，而另一部分导致问题
问候
巴拉。



以下为原文

Any update on this.
 
One more update from my side is,
 
When we use particular crystal osc the system is workign fine ,whereas another part causing problem
 
Regards
bala.