10-24-2016 08:22 AM
We are using Vivado 2014 32-bit Webpack edition. It worked fine at first, but now it is taking well over an hour to synthesize simple designs. What could be causing this?
10-24-2016 08:35 AM
Hi @ccdoss,
You could have change the strategy for the synthesis, try with the vivado default for the synthesis:
Try also to use the maximum of jobs available (right click on Run Synthesis):
With a Webpack, your license should be on your machine. But in the case the license is on a server, it could takes some time to access it.
Make sure you don't have multiple paths for the licenses (and in particular path to servers)
Hope that helps,
Regards,
Florent
10-24-2016 11:24 AM
Can you share the vivado synthesis runme.log file which will be locates in <project>/<project>.runs/synth_1/ folder?
--Syed
10-24-2016 10:17 PM
Check if the multi-threading option is disabled:
https://www.xilinx.com/support/answers/52905.html
Also, is there any specific reason for not using 64-bit? Can you check the runtime(32-bit and 64-bit) with simple Vivado example designs to make sure this is not a project based issue.
Thanks,
Anusheel
-----------------------------------------------------------------------------------------------
Search for documents/answer records related to your device and tool before posting query on forums.
Search related forums and make sure your query is not repeated.
Please mark the post as an answer "Accept as solution" in case it helps to resolve your query.
Helpful answer -> Give Kudos
-----------------------------------------------------------------------------------------------
10-25-2016 06:49 AM
10-25-2016 06:51 AM
10-25-2016 07:08 AM
It appears that it is not trying to synthesize at all, as the process uses 0% CPU. It has been running for over 20 minutes, and here is the current progress:
Here is the current log:
Is there something causing it to stall after a certain number of projects?
10-25-2016 07:34 AM - edited 10-25-2016 07:37 AM
Hi @ccdoss,
When we are talking about log, we are talking about the .log files created by Vivado. This contains tool outputs.
The .log file is created in the path from where you have started vivado. If you have started Vivado from the desktop icon, to know the directory from which you will run Vivado, right-click on the icon and click properties. The Start in field indicated you the folder:
Please get the vivado.log file from this folder and attached it to this port.
Please also make sure you have the right to write in these folder.
Regards,
Florent
10-25-2016 07:56 AM
10-25-2016 08:08 AM
Hum...does not give much more information.
Please wait for the synthesis to finish (if finish one day...) and send the log again.
Hope we will have more information
10-25-2016 08:36 AM
10-25-2016 08:40 AM
Please share the runme.log file from the following location:
C:/Users/student/Desktop/Basys3-master/Projects/GPIO/proj/GPIO.runs/synth_1/runme.log
--Syed
10-25-2016 08:45 AM
It also hasn't been produced. His run was still at 0% complete, as is the one I started 2 hours ago. I'm under the impression it's not going to produce synthesis output until it finishes. Which appears to be able to take days on designs ISE does in under a minute.
Something has to be causing it to stall. The students were initially able to do designs within a few minutes. Then gradually it took longer until it took an hour or so. Now it is taking days.
10-25-2016 08:56 AM
Hi @ccdoss,
It looks like a known issue with 2014.x:
Can you try to run the file <your_project_path>/<your_project_name>.runs/synth_1/runme.log
You should have the following error:
CScript Error: Can't find script engine ...
Because the Jscript engine is disable.
Please move to a more recent version of Vivado.
Regards,
Florent
10-25-2016 09:20 AM
This is the latest version we can use because we have 32-bit machines in there.
10-25-2016 11:43 PM
Hi @ccdoss,
I have sent you a workaround in PM.
Regards,
Florent
10-26-2016 06:42 AM
It gave me an error. Would this work:
10-26-2016 06:50 AM
Hi @ccdoss,
Yes that should work. If not, the lab edition for 2015.4 can be installed on a 32bit OS and contains the Vivado Device Programmer.
You can also try to re-install Vivado on the machine on which it fails
Regards,
Florent
10-29-2016 11:30 PM
I am facing exact same problem. I have tried reinstalling vivado 2016.3 but still the synthesis is taking infinite time and I am unable to get any results. When installed on my friend's system, it is working nicely.
I have Vivado WebPack 2016.3.
10-31-2016 01:36 AM
Hi @adi1,
Can you create a new post on the forum. This is not the same version so I don't think this is the root cause.
In the new post please add the .log files that you have:
-> vivado.log created in the folder from where you have started vivado (if starting from desktop icon, click right > Properties > start in to konw the folder)
-> runme.log in the folder <project_name>.runs/synth_1
Thanks and Regards,
Florent