Could someone give me a reality check on how fast the Vivado tool chain is expected to run? I mean the entire Synthesis, Implementation, Generate Bitstream sequence.
Here's what I get on a simple "hello world" design involving a single top.v with a simple 40-bit counter, sending 8 outputs to pins, no additional IP, targeting a CMod A7-35. I am using pretty much out-of-the-box settings in Vivado, so far as I am aware.
If I make a minor change to top.v, then click on "Generate Bitstream", this invokes the entire chain (no surprise), which takes a total of over 3 minutes to run, using 100% of one CPU, and sometimes up to an additional 50% of another.
Windows 7, on AMD Phenom 6 core CPU with 8G or RAM. There does not seem to be undue memory paging and not all that much disk activity in general, so this seems to be CPU bound.
Is this normal? Or am I unwittingly asking it to go particularly slow somehow?
Question
gwideman
Hi folks.
Could someone give me a reality check on how fast the Vivado tool chain is expected to run? I mean the entire Synthesis, Implementation, Generate Bitstream sequence.
Here's what I get on a simple "hello world" design involving a single top.v with a simple 40-bit counter, sending 8 outputs to pins, no additional IP, targeting a CMod A7-35. I am using pretty much out-of-the-box settings in Vivado, so far as I am aware.
If I make a minor change to top.v, then click on "Generate Bitstream", this invokes the entire chain (no surprise), which takes a total of over 3 minutes to run, using 100% of one CPU, and sometimes up to an additional 50% of another.
Windows 7, on AMD Phenom 6 core CPU with 8G or RAM. There does not seem to be undue memory paging and not all that much disk activity in general, so this seems to be CPU bound.
Is this normal? Or am I unwittingly asking it to go particularly slow somehow?
Graham
Link to comment
Share on other sites
5 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.