UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Visitor skidaddytn
Visitor
538 Views
Registered: ‎11-17-2017

command line vivado sometimes waits for a keypress

I'm using "vivado -mode batch -source build.tcl" to build our bitstream and sometimes it is pausing to wait for a keypress, even though it never prompts me for such.   If I press enter it scrolls a lot of text at once and continues working.  

 

Almost always when it stops it is right after here:

 

# wait_on_run impl_1
[Wed Oct 31 10:22:09 2018] Waiting for impl_1 to finish...

It is at this point that it does a whole LOT of processing, but sometimes it needs me to press enter before it goes on:

 

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


Anyone know why it may be pausing here?  Its kind of annoying.  I'm using the Windows SDK kit version of "vivado".   I wonder if there is some kind of logic inside of vivado to pause if I have switched the active Window away from the one running vivado...   it would be odd, but possible I guess.  None of my other processing tools do that.

 

0 Kudos
2 Replies
Moderator
Moderator
475 Views
Registered: ‎05-31-2017

Re: command line vivado sometimes waits for a keypress

Hi @skidaddytn,

 

Ideally, Vivado should not pause. From your scenario, it seems that vivado is running but it is not printing the log and appears to be as if it has been paused. Please confirm if you are using the supported OS as mentioned at page 11 of UG973

0 Kudos
Visitor skidaddytn
Visitor
287 Views
Registered: ‎11-17-2017

Re: command line vivado sometimes waits for a keypress

O/S is Windows 10 1803.   I have figured out something however...  it does not pause as long as you leave the window *active*.   If you click the focus away from the command prompt window, then its like it waits for you to re-focus on the window before spewing out all the output.Very strange behavior as no other utilities have such a pause mechanism built in...     I did not even know it was possible for a command line application to act in such a way.    Luckily for our automated builds, no one is using the machine so it always completes.

 

0 Kudos