Shape Builder 18-119无法创建I/OLOGIC路由

弗拉德，
你能告诉我们以下实例的连通性吗？
system_i / ddr3_ctrl / u_system_ddr3_ctrl_0_mig / u_memc_ui_top_axi / mem_intfc0 / ddr_phy_top0 / u_ddr_mc_phy_wrapper / gen_dqs_iobuf_HP.gen_dqs_iobuf [0] .gen_dqs_diff.u_iobuf_dqs / IBUFDS / IBUFDS_S
ddr3_sdram_dqs_p [0]
谢谢，
迪皮卡。
谢谢，迪皮卡.----------------------------------------------
---------------------------------------------- Google之前的问题
张贴。
如果某人的帖子回答了您的问题，请将帖子标记为“接受为解决方案”。
如果你看到一个特别好的和信息丰富的帖子，考虑给它Kudos（左边的明星）



以下为原文

Hi Vlad,
 
Can you show us the connectivity of below instances
 
system_i/ddr3_ctrl/u_system_ddr3_ctrl_0_mig/u_memc_ui_top_axi/mem_intfc0/ddr_phy_top0/u_ddr_mc_phy_wrapper/gen_dqs_iobuf_HP.gen_dqs_iobuf[0].gen_dqs_diff.u_iobuf_dqs/IBUFDS/IBUFDS_S
 
ddr3_sdram_dqs_p[0]
 
 
Thanks,
Deepika.
Thanks,
Deepika.
--------------------------------------------------------------------------------------------
Google your question before posting. If someone's post answers your question, mark the post as answer with "Accept as solution". If you see a particularly good and informative post, consider giving it Kudos (the star on the left)

嗨Deepika，
谢谢你的回应。
获得了sch和pdf的原理图。
还有一个缩放版本显示8个DQS信号。
希望这就是你的要求。
对此的帮助非常高兴。
我们的时间分数非常高，看起来就像这些网。
问候
弗拉德
弗拉迪斯拉夫·穆拉文
schematic.pdf 19 KB
schematic.sch 75 KB
schematic_zoom.pdf 338 KB



以下为原文

Hi Deepika,
Thanks for responsing to this.
Attahed schematic, both sch and pdf. There is also a zoomed version showing 8 DQS signals.
Hope this is what you asked.
Help on this is very much apprecaited. Our timing score is very high and looks like it is around these nets.
Regards
Vlad
 
Vladislav Muravin            schematic.pdf ‏19 KB                schematic.sch ‏75 KB                schematic_zoom.pdf ‏338 KB

在什么vivado版本中你得到CW消息？
你打开了phys_opt_design吗？
--------------------------------------------------
-----------------------不要忘记回答，kudo，并接受为解决方案.-------------
--------------------------------------------------
----------



以下为原文

In what vivado version did you get the CW messages? Did you turn on phys_opt_design?
-------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

2014.2，Linux x64
我们在选择之后运行phy_opt并且在重新定时之后运行
弗拉迪斯拉夫·穆拉文



以下为原文

2014.2, Linux x64
we run phy_opt after opt and after route with retiming
 
Vladislav Muravin

已经存在针对物理优化的CR（＃799432）。
事实证明只有在打开phys_opt_design时才能看到CW。
该问题目前正在调查中。
--------------------------------------------------
-----------------------不要忘记回答，kudo，并接受为解决方案.-------------
--------------------------------------------------
----------



以下为原文

There's already a CR (#799432) against physical optimization. It turns out the CW is only seen when phys_opt_design is turned on.
The issue is currently under investigation.
-------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

嗨，我很高兴，
谢谢你。
你能否告诉我哪个phy_opt运行有助于CR？
我们在post-place或post_route之后运行的那个？
问候
弗拉德
弗拉迪斯拉夫·穆拉文



以下为原文

Hi graces,
Thanks for this.
Can you please tell me which of the phy_opt runs is contributing to that CR?
The one we run post-place or post_route?
Regards
Vlad
Vladislav Muravin

我做了一些实验，首先我禁用了post0place phy_opt，然后是post-route。
在这两种情况下，当我们没有调用phy_opt时，警告没有出现，但是时间分数很大。
大部分违规行为发生在AXI互连和/或DDR3接口上。
数百和数百条路径，-1.8ns松弛。
以前，重新定时是一个很大的帮助。
最重要的是，我们需要解决这个问题。
有什么建议么？
问候
弗拉德
弗拉迪斯拉夫·穆拉文



以下为原文

I did some experiments, first I've disabled the post0place phy_opt and then post-route.
In both cases, the warnings did not appear when we did not invoke the phy_opt, but the timing score is huge. The bulk of the violations is on the AXI interconnect and/or DDR3 interface. Hundreds and hundreds of paths with -1.8ns slack. Previously, the retiming was a great help. Bottom line is, we need a solution to this problem. Any suggestions?
Regards
Vlad
Vladislav Muravin

您可以检查两个版本的设计，以查看被抱怨的I / O是否具有相同的连接和路由。
主IBUFDS的输出应通过非占用的ILOGIC站点进行路由。
如果I / O形状没有差异，我认为您仍然可以使用phys_opt_design并忽略该消息。
--------------------------------------------------
-----------------------不要忘记回答，kudo，并接受为解决方案.-------------
--------------------------------------------------
----------



以下为原文

You may check the two editions of design to see if the I/Os that are being complained about have the same connections and routing.
The output of the master IBUFDS should be routed through an non-occupied ILOGIC site.
 
If there're no differences with respect to the I/O shape, I think you can still use the phys_opt_design and ignore the message.
-------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------

谢谢Grace。
我在6月24日恢复了我们的设计（我们修改控制thesystem_bd.tcl）。
在这个设计中，我实际得到0 TNS，我只看到上述警告的一个实例，但这是因为我们在路由后设法得到WNS = 0，因此没有调用路由后的phy_opt。
在原理图上，主IBUFDS在上周的设计版本中路由，将很快检查最新版本。
我目前正在进行几次实验迭代，看看我们在哪个阶段开始遇到这些问题。
这个CR预计会在2014年3月修复吗？
谢谢你的建议。
弗拉德
弗拉迪斯拉夫·穆拉文



以下为原文

Thanks Grace.
 
I reverted back to our design as it was on June 24th (we revision-control the system_bd.tcl). In this design, where I actually get a 0 TNS, I see only one instance of the above warnings, but this is because we've managed to get WNS=0 after routing so post-route phy_opt was not invoked.
 
On the schematic, the master IBUFDS is routed in the last week's version of the design, will check the latest shortly. I am currently going through several experimental iterations to see at which point we started having these issues.
 
Is this CR expected to be fixed in 2014.3?
 
Thanks for the suggestions.
Vlad
Vladislav Muravin