https://billauer.se/blog/2016/02/vivado-runs-tcl-bash/ Anything I found worthy to write down. Thu, 26 Mar 2026 13:15:15 +0000 hourly 1 http://wordpress.org/?v=3.1.2 https://billauer.se/blog/2016/02/vivado-runs-tcl-bash/comment-page-1/#comment-1299 glen english Wed, 18 Oct 2017 02:48:02 +0000 https://billauer.se/blog/?p=4931#comment-1299 Great stuff, saved me alot of time thanks very much Great stuff, saved me alot of time
thanks very much

]]> https://billauer.se/blog/2016/02/vivado-runs-tcl-bash/comment-page-1/#comment-1252 David Epping Thu, 20 Apr 2017 10:04:50 +0000 https://billauer.se/blog/?p=4931#comment-1252 @Evgeni Hi, report_property works on runs for me, as does get_property (just tested on Vivado 2016.1). You can query the NEEDS_REFRESH property or filter based on it, for what you want to do: get_runs -filter {NEEDS_REFRESH == "1"} @Evgeni Hi, report_property works on runs for me, as does get_property (just tested on Vivado 2016.1).
You can query the NEEDS_REFRESH property or filter based on it, for what you want to do:
get_runs -filter {NEEDS_REFRESH == “1″}

]]> https://billauer.se/blog/2016/02/vivado-runs-tcl-bash/comment-page-1/#comment-1226 Evgeni Stavinov Fri, 27 Jan 2017 23:29:44 +0000 https://billauer.se/blog/?p=4931#comment-1226 I'm looking for a way to determine which runs in the current project are out-of-context. "get_runs" TCL command seems to be the right choice. However, it lists all synthesis runs if using "-filter {IS_SYNTHESIS}". "report_property" also doesn't work on runs. I’m looking for a way to determine which runs in the current project are out-of-context. “get_runs” TCL command seems to be the right choice. However, it lists all synthesis runs if using “-filter {IS_SYNTHESIS}”. “report_property” also doesn’t work on runs.

]]>