09-20-2017 06:29 AM
I have a tcl hook script that I would like to run after bitstream generation in the Vivado project flow. One of the things that the hook script does is copies output files that we would like to preserve in revision control from inside the project tree to a separate, revision-controlled folder. One of these files is the .ltx file, which stores the debug probe configuration.
The problem I am having is that, apparently, the .ltx file is written *after* the bitgen tcl.post hook script is called, because the .ltx file being copied is the one from the prior run, not the current run. Is there any way to call my hook script after *all* Vivado project post-processing steps are complete?
Alternatively, if there was a way to generate the .ltx file on my own in my script, that would be acceptable, although less desirable.
09-20-2017 07:43 AM
You can generate the ltx file using write_debug_probes command.
09-20-2017 07:47 AM
How can I determine exactly what argument values write_debug_probes is called with by the Vivado project manager? I did not see a call to it in my .log or .jou files.
09-20-2017 08:00 AM
The command would be as below
09-20-2017 09:10 AM
Thank you. I will give that a try and see if the results are as I expect.
What about my original question: Is there any way to call my hook script after *all* Vivado project post-processing steps are complete?
09-20-2017 11:21 PM
No, I dont think we have anything like that.