cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
muellera
Adventurer
Adventurer
2,999 Views
Registered: ‎02-22-2016

Error during Design Initialization: "Internal Data Exception: HDDMProto::readMessage failed"

Jump to solution

Hi,

 

I get the following error during Implementation, at step "Design Initialization".

[Common 17-49] Internal Data Exception: HDDMProto::readMessage failed

It is not possible to work around this error by simply changing the implementation strategy, as proposed here.

 

This is the complete output found at project.runs\impl_1\runme.log (obfuscated identifiers and path names):

 

*** Running vivado
    with args -log FOOX.vdi -applog -m64 -product Vivado -messageDb vivado.pb -mode batch -source FOOX.tcl -notrace


****** Vivado v2017.4.1 (64-bit)
  **** SW Build 2117270 on Tue Jan 30 15:32:00 MST 2018
  **** IP Build 2095745 on Tue Jan 30 17:13:15 MST 2018
    ** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.

source FOOX.tcl -notrace
add_files: Time (s): cpu = 00:00:18 ; elapsed = 00:00:18 . Memory (MB): peak = 553.605 ; gain = 0.000
Command: link_design -top FOOX -part xcku5p-ffvb676-2-e
Design is defaulting to srcset: sources_1
Design is defaulting to constrset: constrs_1
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Project 1-454] Reading design checkpoint '<hidden_path>'
INFO: [Netlist 29-17] Analyzing 2743 Unisim elements for replacement
INFO: [Netlist 29-28] Unisim Transformation completed in 2 CPU seconds
INFO: [Project 1-479] Netlist was created with Vivado 2017.4.1
INFO: [Device 21-403] Loading part xcku5p-ffvb676-2-e
64 Infos, 0 Warnings, 0 Critical Warnings and 0 Errors encountered.
link_design completed successfully
ERROR: [Common 17-49] Internal Data Exception: HDDMProto::readMessage failed
INFO: [Common 17-206] Exiting Vivado at Mon Jun 18 14:14:26 2018...

I am using Vivado 2017.4.1 on a Windows 10 64 bit Host.

 

0 Kudos
1 Solution

Accepted Solutions
muellera
Adventurer
Adventurer
2,613 Views
Registered: ‎02-22-2016
I have not seen this error again on Vivado 2018.2, however the design has changed significantly since I posted the error.
Closing this thread due to moderator request.

View solution in original post

0 Kudos
6 Replies
peadard
Moderator
Moderator
2,983 Views
Registered: ‎02-07-2008

Hi @muellera, does the issue occur if just one checkpoint is read in? What are these checkpoints that are being read in? IP?

 

Are you able to try 2018.1?

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
peadard
Moderator
Moderator
2,950 Views
Registered: ‎02-07-2008

Hi @muellera, with 2018.2 now available, are you able to try 2018.2 rather than 2018.1?

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
muellera
Adventurer
Adventurer
2,943 Views
Registered: ‎02-22-2016

Hi, @peadard, those checkpoints are all OOC IP, 80% Xilinx IP, 20% user and 3rd party IP.

I will investigate using 2018.2; however, if this causes major IP changes, I won't follow that path to the end.

 

0 Kudos
peadard
Moderator
Moderator
2,941 Views
Registered: ‎02-07-2008

Hi @muellera, thanks for the information. For the Xilinx IP, could you try reading in the .xci instead of the DCP to see if that helps?

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
syedz
Moderator
Moderator
2,912 Views
Registered: ‎01-16-2013

@muellera,

 

Can you update us on this thread? Also, can you try using non-ooc (Global) run and see if you still see the same error?

 

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

Did you check our new quick reference timing closure guide (UG1292)?
---------------------------------------------------------------------------------------------
0 Kudos
muellera
Adventurer
Adventurer
2,614 Views
Registered: ‎02-22-2016
I have not seen this error again on Vivado 2018.2, however the design has changed significantly since I posted the error.
Closing this thread due to moderator request.

View solution in original post

0 Kudos