“路由器成功完成”后发生了什么？

你好@ moon5756
路由成功完成后，路由器将报告使用routed_summary.rpt中的实际路由延迟计算的估计时序摘要。
此外，还会生成某种报告，例如drc.rpt，methodology.rpt，power report。
所有这些报告都位于项目目录的.runs / impl_1文件夹中。
您可以检查runme.log以验证这一点。
问候
罗希特
RegardsRohit -------------------------------------------------
---------------------------------------------请注意 - 请注明
答案为“接受为解决方案”，如果提供的信息是有帮助的。给予您认为有用并回复导向的帖子。感谢K--
--------------------------------------------------
----------------------



以下为原文

Hi @moon5756
 
Once the routing is done successfully, the router reports an estimated timing summary calculated using actual routing delays in the routed_summary.rpt . Additionally there are also certain kind of reports being generated  such as drc.rpt, methodology.rpt, power report.
All these reports are located in your .runs/impl_1 folder of your project directory.
You can check your runme.log to verify this.
 
Regards
Rohit
 
Regards
Rohit
----------------------------------------------------------------------------------------------
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 and reply oriented.
----------------------------------------------------------------------------------------------

@thakurr
谢谢回复！
有什么方法可以跳过这个过程吗？
我想在5分22秒而不是9分6秒内完成路由。
谢谢！



以下为原文

@thakurr
 
Thanks for the reply!
 
Is there any way that I can possibly skip the process? I want to finish routing in 5min 22seconds instead of 9 min 6seconds.
 
Thanks!

你好@ moon5756
有什么方法可以跳过这个过程吗？
我希望在5分22秒内完成路由，而不是9分6秒。
在项目模式下，这更多地受工具控制，并通过Vivado运行自动生成。
但是，在非项目模式下，无论是否要生成这些报告，都具有完全的灵活性。
这是因为非项目模式是用户可管理的。
问候
罗希特
RegardsRohit -------------------------------------------------
---------------------------------------------请注意 - 请注明
答案为“接受为解决方案”，如果提供的信息是有帮助的。给予您认为有用并回复导向的帖子。感谢K--
--------------------------------------------------
----------------------



以下为原文

Hi @moon5756
 
Is there any way that I can possibly skip the process? I want to finish routing in 5min 22seconds instead of 9 min 6seconds.
 
In project mode this is more under tool control and generated automatically with Vivado runs. However in non-project mode you have full flexibility whether you want to generate these reports or not. This is because non-project mode is user manageable.
 
Regards
Rohit
 
Regards
Rohit
----------------------------------------------------------------------------------------------
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 and reply oriented.
----------------------------------------------------------------------------------------------

None


以下为原文

@thakurr
 
Thanks! I am doing with non-project option and looking at route_design section of ug835, but what options would work?
I doubt it's an issue with a report because for some design, the gap I stated is relatively small(30 seconds), but this case it's about 5 minute. The entire log is shown below.
 
 
 
# route_design
Command: route_design
Attempting to get a license for feature 'Implementation' and/or device 'xczu9eg-es2'
INFO: [Common 17-349] Got license for feature 'Implementation' and/or device 'xczu9eg-es2'
INFO: [Common 17-1223] The version limit for your license is '2018.02' and will expire in -28 days. A version limit expiration means that, although you may be able to continue to use the current version of tools or IP with this license, you will not be eligible for any updates or new releases.
Running DRC as a precondition to command route_design
INFO: [DRC 23-27] Running DRC with 8 threads
INFO: [Vivado_Tcl 4-198] DRC finished with 0 Errors
INFO: [Vivado_Tcl 4-199] Please refer to the DRC report (report_drc) for more information.

Starting Routing Task
INFO: [Route 35-254] Multithreading enabled for route_design using a maximum of 8 CPUs
Checksum: PlaceDB: 79aea397 ConstDB: 0 ShapeSum: d456f0d0 RouteDB: 8ba1b830
Phase 1 Build RT Design
Phase 1 Build RT Design | Checksum: 138276f17
Time (s): cpu = 00:02:31 ; elapsed = 00:01:48 . Memory (MB): peak = 5148.863 ; gain = 0.000 ; free physical = 117600 ; free virtual = 138777
Phase 2 Router Initialization
Phase 2.1 Create Timer
Phase 2.1 Create Timer | Checksum: 1b1c1609e
Time (s): cpu = 00:02:42 ; elapsed = 00:01:59 . Memory (MB): peak = 5148.863 ; gain = 0.000 ; free physical = 117600 ; free virtual = 138777
Phase 2.2 Fix Topology Constraints
Phase 2.2 Fix Topology Constraints | Checksum: 1b1c1609e
Time (s): cpu = 00:02:44 ; elapsed = 00:02:01 . Memory (MB): peak = 5148.863 ; gain = 0.000 ; free physical = 117600 ; free virtual = 138777
Phase 2.3 Pre Route Cleanup
Phase 2.3 Pre Route Cleanup | Checksum: fefc4bb0
Time (s): cpu = 00:02:45 ; elapsed = 00:02:02 . Memory (MB): peak = 5148.863 ; gain = 0.000 ; free physical = 117600 ; free virtual = 138777
INFO: [Route 35-445] Local routing congestion detected. At least 247 CLBs have high pin utilization, which can impact runtime and timing closure. Top ten contiguous CLBs with high pin utilization are:
[CLEM_X25Y101 -> CLEM_X25Y90]
[CLEM_X36Y85 -> CLEM_X36Y74]
[CLEM_X10Y245 -> CLEM_X10Y244]
[CLEL_R_X10Y361 -> CLEL_R_X10Y360]
Phase 2.4 Global Clock Net Routing
Number of Nodes with overlaps = 0
Phase 2.4 Global Clock Net Routing | Checksum: 15f329038
Time (s): cpu = 00:02:57 ; elapsed = 00:02:10 . Memory (MB): peak = 5148.863 ; gain = 0.000 ; free physical = 117592 ; free virtual = 138769
Phase 2.5 Update Timing
Phase 2.5 Update Timing | Checksum: 1b2a7c096
Time (s): cpu = 00:06:55 ; elapsed = 00:03:00 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117587 ; free virtual = 138764
INFO: [Route 35-416] Intermediate Timing Summary | WNS=1.085 | TNS=0.000 | WHS=-0.027 | THS=-0.106 |
Phase 2 Router Initialization | Checksum: 24a270541
Time (s): cpu = 00:08:15 ; elapsed = 00:03:20 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117587 ; free virtual = 138764
Phase 3 Initial Routing
Phase 3 Initial Routing | Checksum: 2f434e89f
Time (s): cpu = 00:08:25 ; elapsed = 00:03:23 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117585 ; free virtual = 138763
Phase 4 Rip-up And Reroute
Phase 4.1 Global Iteration 0
Number of Nodes with overlaps = 1264
Number of Nodes with overlaps = 227
Number of Nodes with overlaps = 27
Number of Nodes with overlaps = 4
Number of Nodes with overlaps = 2
Number of Nodes with overlaps = 0
Phase 4.1.1 Update Timing
Phase 4.1.1 Update Timing | Checksum: 2847c7324
Time (s): cpu = 00:10:47 ; elapsed = 00:04:17 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117587 ; free virtual = 138765
INFO: [Route 35-416] Intermediate Timing Summary | WNS=1.086 | TNS=0.000 | WHS=0.026 | THS=0.000 |
Phase 4.1 Global Iteration 0 | Checksum: 2847c7324
Time (s): cpu = 00:10:48 ; elapsed = 00:04:18 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117588 ; free virtual = 138765
Phase 4 Rip-up And Reroute | Checksum: 2847c7324
Time (s): cpu = 00:10:48 ; elapsed = 00:04:19 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117587 ; free virtual = 138765
Phase 5 Delay and Skew Optimization
Phase 5.1 Delay CleanUp
Phase 5.1 Delay CleanUp | Checksum: 2847c7324
Time (s): cpu = 00:10:52 ; elapsed = 00:04:20 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117588 ; free virtual = 138765
Phase 5.2 Clock Skew Optimization
Phase 5.2 Clock Skew Optimization | Checksum: 2847c7324
Time (s): cpu = 00:10:53 ; elapsed = 00:04:21 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117588 ; free virtual = 138765
Phase 5 Delay and Skew Optimization | Checksum: 2847c7324
Time (s): cpu = 00:10:54 ; elapsed = 00:04:21 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117587 ; free virtual = 138764
Phase 6 Post Hold Fix
Phase 6.1 Hold Fix Iter
Phase 6.1.1 Update Timing
Phase 6.1.1 Update Timing | Checksum: 26ae72bfc
Time (s): cpu = 00:11:46 ; elapsed = 00:04:43 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117587 ; free virtual = 138764
INFO: [Route 35-416] Intermediate Timing Summary | WNS=1.086 | TNS=0.000 | WHS=0.026 | THS=0.000 |
Phase 6.1 Hold Fix Iter | Checksum: 2390ec9f0
Time (s): cpu = 00:11:47 ; elapsed = 00:04:44 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117587 ; free virtual = 138764
Phase 6 Post Hold Fix | Checksum: 2390ec9f0
Time (s): cpu = 00:11:48 ; elapsed = 00:04:44 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117588 ; free virtual = 138765
Phase 7 Route finalize
Router Utilization Summary
Global Vertical Routing Utilization = 0.34249 %
Global Horizontal Routing Utilization = 0.399326 %
Routable Net Status*
*Does not include unroutable nets such as driverless and loadless.
Run report_route_status for detailed report.
Number of Failed Nets = 0
Number of Unrouted Nets = 0
Number of Partially Routed Nets = 0
Number of Node Overlaps = 0
Phase 7 Route finalize | Checksum: 2796779d7
Time (s): cpu = 00:11:58 ; elapsed = 00:04:48 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117589 ; free virtual = 138766
Phase 8 Verifying routed nets
Verification completed successfully
Phase 8 Verifying routed nets | Checksum: 2796779d7
Time (s): cpu = 00:11:58 ; elapsed = 00:04:48 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117589 ; free virtual = 138766
Phase 9 Depositing Routes
Phase 9 Depositing Routes | Checksum: 2796779d7
Time (s): cpu = 00:12:31 ; elapsed = 00:05:21 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117588 ; free virtual = 138765
Phase 10 Post Router Timing
INFO: [Route 35-57] Estimated Timing Summary | WNS=1.086 | TNS=0.000 | WHS=0.026 | THS=0.000 |
INFO: [Route 35-327] The final timing numbers are based on the router estimated timing analysis. For a complete and accurate timing signoff, please run report_timing_summary.
Phase 10 Post Router Timing | Checksum: 2796779d7
Time (s): cpu = 00:12:32 ; elapsed = 00:05:22 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117588 ; free virtual = 138765
INFO: [Route 35-16] Router Completed Successfully
Time (s): cpu = 00:16:34 ; elapsed = 00:09:06 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117589 ; free virtual = 138766
Routing Is Done.
INFO: [Common 17-83] Releasing license: Implementation
14 Infos, 0 Warnings, 0 Critical Warnings and 0 Errors encountered.
route_design completed successfully
route_design: Time (s): cpu = 00:18:18 ; elapsed = 00:10:21 . Memory (MB): peak = 5172.734 ; gain = 23.871 ; free physical = 117589 ; free virtual = 138766
# write_checkpoint leaf_0_routed.dcp

你好@ moon5756
感谢您分享详细日志，实际上我错过了之前共享的那部分日志。
对不起。
我也觉得这不是一个报告问题，因为所有报告都是在路由成功后生成的。
你正在使用哪个操作系统？
您能否确保使用支持的操作系统和您正在使用的Vivado版本？
请分享设计或发布地点dcp以在我们的最后重现这一点。
问候
罗希特
RegardsRohit -------------------------------------------------
---------------------------------------------请注意 - 请注明
答案为“接受为解决方案”，如果提供的信息是有帮助的。给予您认为有用并回复导向的帖子。感谢K--
--------------------------------------------------
----------------------



以下为原文

Hi @moon5756
 
Thanks for sharing the detailed log, actually i missed that short portion of log you shared before. Sorry for that.
I do also feel that is not a reporting issue as all the reports are generated once routing is successfull.
Between which OS you are using? Can you make sure you use supported OS with Vivado version you are using?
Please share the design or post place dcp to reproduce this at our end.
 
Regards
Rohit
Regards
Rohit
----------------------------------------------------------------------------------------------
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 and reply oriented.
----------------------------------------------------------------------------------------------

@thakurr
嗨，我不能公开分享这个文件。
你能把你的电子邮件地址发给我私信，这样我就可以把你的ade.dcp发给你，这样你就可以运行route_design了吗？
我不认为我可以在私人邮件中附加文件，对吗？
谢谢。



以下为原文

@thakurr
Hi, I can't share the file in public. Can you send me your email address in a private message so that I can send you the placed.dcp so that you can run route_design? I don't think I can attach a file in private message here, right?
 
Thanks.

你好@ moon5756
感谢您分享帖子位置dcp离线。
我在它上面运行了route_design，这是“路由器成功完成”和“路由完成”之间的时间差距（我在Windows 7中尝试过，64位）。
因此，在我的最后，两者之间的时间差距大约是2分40秒，这比通常要高，因为设计的利用率是正常的。
我不知道究竟是什么导致这个，但从WHS值0.016 ns，我可以猜测该工具很难修复保持。
合成后的WHS值是多少？
问候
罗希特
RegardsRohit -------------------------------------------------
---------------------------------------------请注意 - 请注明
答案为“接受为解决方案”，如果提供的信息是有帮助的。给予您认为有用并回复导向的帖子。感谢K--
--------------------------------------------------
----------------------



以下为原文

Hi @moon5756
 
Thanks for sharing the post place dcp offline. I ran route_design over it and here is the timing gap between "Router Completed succesfully" and "Routing is done" (FYI i tried in Windows 7, 64 bit).

So at my end also the time gap between the two is some 2 minutes 40 sec which is high than usual seeking the fact that the utilization of the design is normal. 
I don't know the what exactly is causing this but  from the WHS value which is 0.016 ns, i can guess that tool is having hard time to fix the hold. What is the WHS value after synthesis? 
 
Regards
Rohit
 
Regards
Rohit
----------------------------------------------------------------------------------------------
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 and reply oriented.
----------------------------------------------------------------------------------------------

@ moon5756，
这个帖子有什么更新？
如果您需要更多信息/说明，请告诉我们。
--Syed
--------------------------------------------------
-------------------------------------------请注意 - 请标记答案
如果提供的信息有用，请“接受为解决方案”。给予您认为有用并回复导向的帖子。感谢Kudos .------------------------
--------------------------------------------------
-------------------



以下为原文

@moon5756,
 
Any update on this thread? Let us know if you need more information/clarification. 
 
--Syed
---------------------------------------------------------------------------------------------
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 and reply oriented.
---------------------------------------------------------------------------------------------

嗨@ syedz，
我尝试了不同的方法，这个问题消失了。
我已经能够确切地找出导致这种行为的原因。
谢谢。



以下为原文

Hi @syedz,
 
I tried different approach and this issue is gone. I have been able to exactly figure out what caused this behavior though.
 
Thanks.