10-31-2018 11:25 AM - edited 10-31-2018 11:31 AM
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.
11-05-2018 09:06 PM
02-25-2019 08:50 AM
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.