Syhthesis err:[Timing 38-17] An error was encountered initializing graph

Hi zqsteve,

Thanks for contacting us regarding the issue. Could you please attach the full log into the thread?

Regards,
Baser

Hi awsbaser ,
Because this forum does not support uploading log files, so I past the relevant sections here. The details is attached the following.
Processing XDC Constraints
Initializing timing engine
Caught ... exception.
ERROR: [Timing 38-246] Caught exception 'ERROR: [Timing 38-432] Unexpected exception thrown while building timing graph
' while reading timing library and applying constraints.
Resolution: For technical support on this issue, please visit http://www.xilinx.com/support
tcmalloc: large alloc 1073741824 bytes == 0x2000832000 @ 0x2ad1ca2f663f 0x2ad1ddd4480e 0x24d4832000
tcmalloc: large alloc 1523728384 bytes == 0x20f0832000 @ 0x2ad1ca2f663f 0x2ad1e170f9a0
tcmalloc: large alloc 1523728384 bytes == 0x243c732000 @ 0x2ad1ca2f663f 0x2ad2030b6350
tcmalloc: large alloc 2147483648 bytes == 0x2d90b0a000 @ 0x2ad1ca2f663f 0x2ad1ddd4480e 0x2040832000
tcmalloc: large alloc 2147483648 bytes == 0x24e52a4000 @ 0x2ad1ca2f663f 0x2ad2030b5e3e 0x1fc8c32000
tcmalloc: large alloc 3094233088 bytes == 0x2a6f8da000 @ 0x2ad1ca2f663f 0x2ad1e170f9a0
tcmalloc: large alloc 3094233088 bytes == 0x2b27fbe000 @ 0x2ad1ca2f663f 0x2ad2030b6350
tcmalloc: large alloc 4294967296 bytes == 0x28e786a000 @ 0x2ad1ca2f663f 0x2ad1ddd4480e 0x2e10b0a000
tcmalloc: large alloc 4294967296 bytes == 0x275f3c2000 @ 0x2ad1ca2f663f 0x2ad2030b5e3e 0x25652a4000
tcmalloc: large alloc 6283452416 bytes == 0x25d4896000 @ 0x2ad1ca2f663f 0x2ad1e170f9a0
tcmalloc: large alloc 6283452416 bytes == 0x2bf782a000 @ 0x2ad1ca2f663f 0x2ad2030b6350
INFO: [Common 17-83] Releasing license: Synthesis
224 Infos, 138 Warnings, 0 Critical Warnings and 2 Errors encountered.
synth_design failed
ERROR: [Timing 38-17] An error was encountered initializing the timing graph. Analysis will not be performed.
Resolution: For technical support on this issue, please visit http://www.xilinx.com/support
INFO: [Common 17-206] Exiting Vivado at Tue Nov 3 13:41:06 2020...

Hi zqsteve, this appears to be a memory related issue. Could you let us know how much memory is available on the machine you are running on? It may be the case that the run needs more memory than is available to the machine.
An option to try would be to add -stack 2000 when launching Vivado, which allocates more memory for runs.

Hi kmorrisXilinx,
How should I use command "-stack 2000"? Is it a tcl command. When I use it in tcl console in vivado, the vivado does not recognize the command correctly. Then I use command "vivado& -stack 2000" in the linux , it still failed.

Hi zqsteve,

I believe kevin suggested calling vivado -stack 2000 &

Let me know if that doesn't work for you.

-Deep