Vivado 2016.3异常程序终止

你好，
描述：
第一次合成和实施是成功的。
我在设计中的两个防晒霜之间有一些不知不觉的消失。
所以我决定避免长的合成时间（在我的情况下，超过15~16h）并使用插入Debug-Core。
首先，我创建两个xdc文件，一个用于标记Signal，我想要调试，第二个用于插入调试核心，使用“设置调试”-Tool。
比我用两个新的XDC创建一个新的Implementation-Run。
并且只启动新的实施。
3小时后，vivado卡住并给我以下消息：
- 为了使它成为conmen，我用xxxxx替换了projektname。
阶段10后路由器时序
信息：[路线35-57]估计时间摘要|
WNS = 0.216 |
TNS = 0.000 |
WHS = 0.013 |
THS = 0.000 |
信息：[路线35-327]最终的时间数字基于路由器估计的时序分析。
要获得完整而准确的时序签收，请运行report_timing_summary。
阶段10后路由器时序|
校验和：29d48ef14
时间：cpu = 00:54:34;
逝去了= 00:21:24。
记忆（MB）：峰值= 6880.125;
增益= 414.199
信息：[路由35-16]路由器成功完成
时间：cpu = 00:55:44;
逝去了= 00:21:45。
记忆（MB）：峰值= 6880.125;
增益= 414.199
路由已完成。
信息：[共17-83]发布许可证：实施
遇到79个Infos，1个警告，2个严重警告和0个错误。
route_design成功完成
route_design：时间：cpu = 00:56:47;
逝去了= 00:22:25。
记忆（MB）：峰值= 6880.125;
增益= 521.445
信息：[通用17-600]以下参数具有非默认值。
general.maxThreads
编写砂矿数据库......
编写XDEF路由。
编写XDEF路由逻辑网。
编写XDEF路由特殊网。
写XDEF完成：时间：cpu = 00:02:36;
逝去了= 00:00:54。
记忆（MB）：峰值= 6880.125;
增益= 0.000
信息：[Common 17-1381]已生成检查点xxxxxxx_routed.dcp'。
write_checkpoint：Time（s）：cpu = 00:03:25;
逝去了= 00:01:56。
记忆（MB）：峰值= 6880.125;
增益= 0.000
信息：[DRC 23-27]运行8个线程的DRC
信息：[Coretcl 2-168] DRC的结果位于文件xxxxxxx_drc_routed.rpt中。
report_drc：时间：cpu = 00:02:10;
逝去了= 00:00:45。
记忆（MB）：峰值= 7055.496;
增益= 175.371
信息：[时序38-35]完成设置XDC时序约束。
信息：[DRC 23-133]运行8个线程的方法
异常程序终止（EXCEPTION_ACCESS_VIOLATION）
有关详细信息，请查看'xxxxxxx hs_err_pid32416.log'
在消息中显示，已成功路由的设计已写入DCP。
在hs_err_.log中只写入以下行：
##发生了意外错误（EXCEPTION_ACCESS_VIOLATION）#Stack：没有可用的堆栈跟踪，请改用hs_err_.dmp。
.dmp文件无法访问且具有空字节。
有人可以搞清楚，为什么要如何避免异常呢？

以上来自于谷歌翻译

以下为原文

Hello,

Description:
the first synthesis and implementation were successful. I've got some unknowing effaces between two sunblocks in the Design. So I decided to avoid the long synthesis time (in my case, more than 15~16h) and use the inserting the Debug-Core.

At first, I create two xdc-file, one to mark the Signal, which I want to debug, and the second to insert the debug-core using the "Set Up Debug"-Tool.
Than I create a new Implementation-Run additionally with the two new XDC. And Start only the new Implementation.

After 3h, the vivado stuck and give me the following messages:
-- to make it conmen, I replaced the projektname with xxxxx.
Phase 10 Post Router Timing
INFO: [Route 35-57] Estimated Timing Summary | WNS=0.216 | TNS=0.000 | WHS=0.013 | 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: 29d48ef14

Time (s): cpu = 00:54:34 ; elapsed = 00:21:24 . Memory (MB): peak = 6880.125 ; gain = 414.199
INFO: [Route 35-16] Router Completed Successfully

Time (s): cpu = 00:55:44 ; elapsed = 00:21:45 . Memory (MB): peak = 6880.125 ; gain = 414.199

Routing Is Done.
INFO: [Common 17-83] Releasing license: Implementation
79 Infos, 1 Warnings, 2 Critical Warnings and 0 Errors encountered.
route_design completed successfully
route_design: Time (s): cpu = 00:56:47 ; elapsed = 00:22:25 . Memory (MB): peak = 6880.125 ; gain = 521.445
INFO: [Common 17-600] The following parameters have non-default value.
general.maxThreads
Writing placer database...
Writing XDEF routing.
Writing XDEF routing logical nets.
Writing XDEF routing special nets.
Write XDEF Complete: Time (s): cpu = 00:02:36 ; elapsed = 00:00:54 . Memory (MB): peak = 6880.125 ; gain = 0.000
INFO: [Common 17-1381] The checkpoint xxxxxxx_routed.dcp' has been generated.
write_checkpoint: Time (s): cpu = 00:03:25 ; elapsed = 00:01:56 . Memory (MB): peak = 6880.125 ; gain = 0.000

INFO: [DRC 23-27] Running DRC with 8 threads
INFO: [Coretcl 2-168] The results of DRC are in file xxxxxxx_drc_routed.rpt.
report_drc: Time (s): cpu = 00:02:10 ; elapsed = 00:00:45 . Memory (MB): peak = 7055.496 ; gain = 175.371
INFO: [Timing 38-35] Done setting XDC timing constraints.
INFO: [DRC 23-133] Running Methodology with 8 threads
Abnormal program termination (EXCEPTION_ACCESS_VIOLATION)
Please check ' xxxxxxx hs_err_pid32416.log' for details

In the Message is shown, that a successfully routed Design has been written in a DCP.
In the hs_err_.log is only this lines are written:
#
# An unexpected error has occurred (EXCEPTION_ACCESS_VIOLATION)
#
Stack:
no stack trace available, please use hs_err_.dmp instead.

the .dmp file ist not accessible and with a Null-byte.

Could someone to figure it out, why an how to avoid the Exception?

赵雪培

2018-11-6 11:46:46

@hailuwang，
这是一个崩溃vivado崩溃。
您可以检查在/.runs/impl文件夹中是否生成了raduted dcp文件。
如果是，那么继续设计打开Vivado中的检查点，您就可以生成比特流或分析路由设计结果。
要调试崩溃问题，您可以共享post opt dcp文件吗？
仅供参考：查看此答复记录以调试崩溃问题：
https://www.xilinx.com/support/answers/55854.html
--Syed
--------------------------------------------------
-------------------------------------------请注意 - 请标记答案
如果提供的信息有用，请“接受为解决方案”。给予您认为有用并回复导向的帖子。感谢Kudos .------------------------
--------------------------------------------------
-------------------

以上来自于谷歌翻译

以下为原文

@hailuwang,

This is a crash vivado crash. Can you check if the raouted dcp file is generated in /.runs/impl folder.

If yes, then to move forward with the design open the checkpoint in Vivado and you can generate the bitstream or analyze the routed design results.

To debug the crash issue, Can you share the post opt dcp file?

FYI: Check this Answer Record to debug crash issues:
https://www.xilinx.com/support/answers/55854.html

--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.
---------------------------------------------------------------------------------------------

张蕾

2018-11-6 11:52:06

@syedz
谢谢你的回复。
我没有在我的历史中看到我的帖子，因为我已经提出它了。
我有路由的dcp并且可以手动生成比特流。
看起来很好，很有效。
但是我对崩溃感到担忧。
为了获得比特流，我想逃避report_mehtodology，我认为它自动生成Vivado 16.3作为Default。
它必须在命令中报告：report_methodology。
你能检查一下案件吗？
我可以提供日志和dmp文件。
这次有点运气，写了一个dmp文件。
hs_err_pid9236.dmp 263 KB
hs_err_pid9236.log 1 KB

以上来自于谷歌翻译

以下为原文

@syedz

Thanks for the Replying. I didn't see my post in mine history, since I've posed it, any more.

I've got the routed dcp and could manually generate a bitstream. It looks fine and works. But I have a concern with the Crash. To get a bitstream, I've to escape the report_mehtodology, which automatically generated form Vivado 16.3 as Default, I think.

It must be cashed in the command: report_methodology. Could you check and investigate the case.

I can provide the log and dmp file. With some luck this time, a dmp-file was written.

hs_err_pid9236.dmp ‏263 KB

hs_err_pid9236.log ‏1 KB

周臻庸

回帖（2）

赵雪培

张蕾

相关问答

ubuntu1604无法启动vivado2016.3的sdk

vivado 2016.4异常程序终止

安装了Vivado 2016.3启动Vivado时目录中没有Spartan 7设备？

Vivado 2013.4异常程序终止（11）

如何为ES1设备提供电路板文件以支持Vivado 2016.4？

Vivado 2016.3中对任何System Verilog功能的支持是否有所改变？

Vivado内部异常

vivado版本实现运行属性窗口显示日志并且工具没有停止，请问应该如何操作才能解决这个问题？

2016.3文档导航器错误

FATAL ERROR：Vivado模拟器无法恢复

20万+工程师都在用，免费PCB检查工具