[问答]

在Kintex 7中找到具有不同IODELAY组约束的相同形状的IODELAY单元格

8586 Kintex

我已成功级联IDELAYCTRL模块，以便在Xilinx版主和员工的帮助下增加分接头延迟，尤其是@syedz和@marcb。
为了下一步，我在N Path of Differential Buffer中整合了两个以上的IDELAYCTRL模块。
在实施过程中，我得到了以下DRC错误：
[DRC PLIDC-5]具有冲突组的IDELAYCTRL IODELAY形状：找到具有不同IODELAY组约束的IODELAY单元格，形状相同。
IODELAY单元及其受限于此形状的组是：'mb_subsystem_i / Slave_Pre_iDelay / inst / pins [0] .idelaye2_bus：mb_subsystem_pre_idelay_0_group''mb_subsystem_i / pre_idelay / inst / pins [0] .idelaye2_bus：mb_subsystem_cascaded_Pre_Delay'
带有IODELAY组的IODELAYCTRL组是：
最后IODELAY_GROUPsSr.No.IDELAYCTRLIODELAY_GROUP1mb_subsystem_i / axi_ethernet_0 /安装/ MAC /安装/ tri_mode_ethernet_mac_idelayctrl_common_itri_mode_ethernet_mac_iodelay_grp2mb_subsystem_i / mig_7series_0 / u_mb_subsystem_mig_7series_0_0_mig / u_iodelay_ctrl / u_idelayctrl_200MB_SUBSYSTEM_MIG_7SERIES_0_0_IODELAY_MIG03mb_subsystem_i / Post_iDelay /安装/ delayctrlmb_subsystem_cascaded_Post_delay4mb_subsystem_i / pre_idelay /安装/ delayctrlmb_subsystem_cascaded_Pre_DelayAdditional IODELAY GROUPS5mb_subsystem_i / Slave_Post_iDelay /安装/ delayctrlmb_subsystem_Post_iDelay_0_group6mb_subsystem_i / Slave_Pre_iDelay /安装/ delayctrlmb_subsystem_pre_idelay_0_group
请帮助我解决这个问题。
问候，
穆赫辛

以上来自于谷歌翻译

以下为原文

I have successfully cascaded the IDELAYCTRL modules to increase the tap delays with the help of Xilinx Moderators and Employees, especially @syedz and @marcb. For the next step, i have integarted two more IDELAYCTRL Modules in the N Path of Differential Buffer. During implementation,i got following DRC Error:

[DRC PLIDC-5] IDELAYCTRL IODELAY shape with conflicting groups: Found IODELAY cells with different IODELAY group constraints in the same shape. The IODELAY cells and its group constrained to this shape are: 'mb_subsystem_i/Slave_Pre_iDelay/inst/pins[0].idelaye2_bus : mb_subsystem_pre_idelay_0_group' 'mb_subsystem_i/pre_idelay/inst/pins[0].idelaye2_bus : mb_subsystem_cascaded_Pre_Delay'

The IODELAYCTRL Groups with IODELAY Groups are:

Final IODELAY_GROUPs
Sr.No.	IDELAYCTRL	IODELAY_GROUP
1	mb_subsystem_i/axi_ethernet_0/inst/mac/inst/tri_mode_ethernet_mac_idelayctrl_common_i	tri_mode_ethernet_mac_iodelay_grp
2	mb_subsystem_i/mig_7series_0/u_mb_subsystem_mig_7series_0_0_mig/u_iodelay_ctrl/u_idelayctrl_200	MB_SUBSYSTEM_MIG_7SERIES_0_0_IODELAY_MIG0
3	mb_subsystem_i/Post_iDelay/inst/delayctrl	mb_subsystem_cascaded_Post_delay
4	mb_subsystem_i/pre_idelay/inst/delayctrl	mb_subsystem_cascaded_Pre_Delay
Additional IODELAY GROUPS
5	mb_subsystem_i/Slave_Post_iDelay/inst/delayctrl	mb_subsystem_Post_iDelay_0_group
6	mb_subsystem_i/Slave_Pre_iDelay/inst/delayctrl	mb_subsystem_pre_idelay_0_group

Please Help me out in this Problem.

Regards,
Mohsin

2018-11-8 11:29:47　　评论 淘帖0 邀请回答

您可以邀请以下用户，快速回答问题

asd008
该类别下有 32 个回答。

邀请回答
aaaa321
该类别下有 27 个回答。

邀请回答
doublelove
该类别下有 26 个回答。

邀请回答
vynywrwr
该类别下有 21 个回答。

邀请回答
hgjhgd
该类别下有 19 个回答。

邀请回答
bwerwer
该类别下有 18 个回答。

邀请回答
hanyan533
该类别下有 18 个回答。

邀请回答
Jaionm
该类别下有 18 个回答。

邀请回答
handsomelchcpp
该类别下有 17 个回答。

邀请回答
wang2222222
该类别下有 17 个回答。

邀请回答
ningee
该类别下有 16 个回答。

邀请回答
binro
该类别下有 16 个回答。

邀请回答
myf888
该类别下有 15 个回答。

邀请回答
wznnzw
该类别下有 15 个回答。

邀请回答
yhxc
该类别下有 14 个回答。

邀请回答
armortech
该类别下有 14 个回答。

邀请回答
60user25
该类别下有 14 个回答。

邀请回答
zcy615
该类别下有 14 个回答。

邀请回答
wanglinhua2627
该类别下有 14 个回答。

邀请回答
guotong1984
该类别下有 14 个回答。

邀请回答

张琨

相关推荐

4个回答

答案对人有帮助，有参考价值 0 你好@ mohsin_ch。根据以前问题的经验，增量设计流程的使用看起来是一个因素。冲突将介于设计的引用版本和增量版本之间的IODELAY_GROUP值之间。您是否可以尝试创建包含所有新延迟实例和分组的更新参考DCP？ -------------------------------------------------- -----------------------不要忘记回答，kudo，并接受为解决方案.------------- -------------------------------------------------- ---------- 在原帖中查看解决方案以上来自于谷歌翻译以下为原文 Hi @mohsin_ch. From experience with the previous issues, the usage of the incremental design flow looks to be a factor. The conflict would be between the IODELAY_GROUP value between the reference and incremental versions of the design. Can you try creating an updated reference DCP to use that contains all of the new delay instances and grouping? ------------------------------------------------------------------------- Don’t forget to reply, kudo, and accept as solution. ------------------------------------------------------------------------- View solution in original post

2018-11-8 11:37:26 评论举报俞丽

答案对人有帮助，有参考价值 0 你好@ mohsin_ch。根据以前问题的经验，增量设计流程的使用看起来是一个因素。冲突将介于设计的引用版本和增量版本之间的IODELAY_GROUP值之间。您是否可以尝试创建包含所有新延迟实例和分组的更新参考DCP？ -------------------------------------------------- -----------------------不要忘记回答，kudo，并接受为解决方案.------------- -------------------------------------------------- ---------- 以上来自于谷歌翻译以下为原文 Hi @mohsin_ch. From experience with the previous issues, the usage of the incremental design flow looks to be a factor. The conflict would be between the IODELAY_GROUP value between the reference and incremental versions of the design. Can you try creating an updated reference DCP to use that contains all of the new delay instances and grouping? ------------------------------------------------------------------------- Don’t forget to reply, kudo, and accept as solution. -------------------------------------------------------------------------

2018-11-8 11:53:17 评论举报俞丽

答案对人有帮助，有参考价值 0 感谢您的回复....请指导我如何创建更新的参考DCP？以上来自于谷歌翻译以下为原文 Thanks for the reply....Please guide me how to create an updated reference DCP?

2018-11-8 12:01:43 评论举报陈丽霞

答案对人有帮助，有参考价值 0 @marcb，请告诉我如何创建一个包含所有新延迟实例和分组的更新参考DCP？我认为这是我被困的问题。请帮帮我......我此时真的很需要。以上来自于谷歌翻译以下为原文 @marcb, Plese guide me how can i create an updated reference DCP to use that contains all of the new delay instances and grouping? I think this is the problem in which i am trapped. Please help me...I am really needy at this time.

2018-11-8 12:10:37 评论举报陈丽霞