CRITICAL WARNING: [Project 1-840] The design checkpoint file was generated for an IP by an out of context synthesis run and should not be used directly as a source in a Vivado flow.

[kemache]

Hello,

I am using SDAccel 2018.3. When building an sdaccel example I got the following error:

ERROR: [VPL 60-704] Integration error, problem implementing dynamic region, place_design ERROR, please look at the run log file 'test3/System/binary_container_1/link/vivado/prj/prj.runs/impl_1/runme.log' for more information
ERROR: [VPL 60-806] Failed to finish platform linker
ERROR: [XOCC 60-398] vpl failed
ERROR: [XOCC 60-626] Kernel link failed to complete
ERROR: [XOCC 60-703] Failed to finish linking
make: *** [binary_container_1.xclbin] Erreur 1

Please find as attachement the log file.

The building project stops at the phase3.2 Commit Most Macros & LUTRAMs. I found no errors but many critical warnings and warnings in the log file attached in this post. The first critical warning is the following:

CRITICAL WARNING: [Project 1-840] The design checkpoint file 'test3/System/binary_container_1/link/vivado/prj/prj.runs/my_rm_synth_1/pfm_dynamic.dcp' was generated for an IP by an out of context synthesis run and should not be used directly as a source in a Vivado flow. Constraints and other files related to the IP are only stored in the xci/xcix, not the checkpoint. It is strongly recommended that that the original IP source file (.xci/.xcix) be used.

I did some research in the internet and I have found this :

AR# 69690 Vivado IP Flows - [Vivado 12-5470] The design checkpoint file '….dcp' was generated for an IP by an out of context synthesis run and should not directly be used as a source in a Vivado flow

But I dont know how to do that in SDAccel 2018.3.

Any hints would be greatly appreciated.

[hongh]

It seems place_design stage in Vivado crashed, which causes the issue.

You can try to run place_design based on the opt.dcp in Vivado to check whether the issue still occurs.

Please also confirm that you are using the supported operating system.

[kemache]

Hello @hongh 

Thank you for your response.

I think that the amount of memory is not sufficient for the develoment for the platform I am using (VCU1525). I just found the system recuirement for the alveo (the recuired system memory is 64GB) but not for the VCU1525. Could you please tell me what are the system requirement for the VCU1525 ?

Thanks,

[hongh · Accepted solution]

VCU1525 uses the same chip with U200, so I think they can share the similar system requirement.

[kemache]

Hello @hongh 

Thank you for your response.

[kemache]

HI @hongh 

The build completes now, the problem was the memory size.

The size of the system memory I am using is 32 GB so no need to 64 GB for developpment for the VCU1525.

Thank you,  

[hongh]

Hi, @kemache  ,

Thanks for sharing the root cause.