cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
diptyajit
Visitor
Visitor
13,411 Views
Registered: ‎03-21-2013

Automating VIO interaction using TCL in Vivado 2014.1

Jump to solution

I am in the process of automating a 'live' debug on a Virtex 7 enabled board. I have already written a TCL script which takes the source files through the entire Vivado flow, generates  a bitstream and programs the board.

 

The idea is to have a script kick in at this point, which will control the VIO as per requirements. I can drive the OUTPUT of a VIO core, and the relevant command for this is commit_hw_vio(pg 114, UG 835). But I cannot find an equivalent TCL command to either -

 

(a) Explicitly READ from the VIO INPUT  or,

(b) Export the current INPUT value to a log of some sort.

 

I am only interested in the TCL interface since I would like to use VIvado in its - batch mode and feed it a script.

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
vemulad
Xilinx Employee
Xilinx Employee
22,145 Views
Registered: ‎09-20-2012

Hi,

 

I think you can use below command to read input probe value.

 

get_property INPUT_VALUE [get_hw_probes BUTTON_IBUF]

 

where BUTTON_IBUF is the input probe of VIO core.

 

Refer to page-74 of http://www.xilinx.com/support/documentation/sw_manuals/xilinx2014_1/ug908-vivado-programming-debugging.pdf

 

Thanks,

Deepika.

Thanks,
Deepika.
--------------------------------------------------------------------------------------------
Google your question before posting. If someone's post answers your question, mark the post as answer with "Accept as solution". If you see a particularly good and informative post, consider giving it Kudos (the star on the left)

View solution in original post

3 Replies
vemulad
Xilinx Employee
Xilinx Employee
22,146 Views
Registered: ‎09-20-2012

Hi,

 

I think you can use below command to read input probe value.

 

get_property INPUT_VALUE [get_hw_probes BUTTON_IBUF]

 

where BUTTON_IBUF is the input probe of VIO core.

 

Refer to page-74 of http://www.xilinx.com/support/documentation/sw_manuals/xilinx2014_1/ug908-vivado-programming-debugging.pdf

 

Thanks,

Deepika.

Thanks,
Deepika.
--------------------------------------------------------------------------------------------
Google your question before posting. If someone's post answers your question, mark the post as answer with "Accept as solution". If you see a particularly good and informative post, consider giving it Kudos (the star on the left)

View solution in original post

diptyajit
Visitor
Visitor
13,397 Views
Registered: ‎03-21-2013

Addition

 

I have also found the csevio TCL commands thanks to this post

 

http://forums.xilinx.com/t5/Design-Tools-Others/How-to-drive-pre-assigned-input-via-VIO/td-p/459418

 

 but since the hardware debug section is integrated in Vivado, will the old  UG029 (v14.3 Oct 2012) manual intended for the Chipscope tool also hold true for Vivado 2014.1 ? 

 

Similar questions and solutions are available here 

 

http://forums.xilinx.com/t5/Design-Tools-Others/ChipScope-Engine-Tcl-interface/td-p/59658

 

But the date of the thread (2010) leads me to question if there is something new available that I am not aware of ?

0 Kudos
diptyajit
Visitor
Visitor
13,390 Views
Registered: ‎03-21-2013

Thanks Deepika ! That is the easiest way

 

 

0 Kudos