Open JulianKemmerer opened 2 years ago
Talking about some kind of csv pipeline description input AND output
capability
As well as better summary of latency,fmax from the tool
Should really produce vhdl
directory that contains all VHDL files for that final run.
Then existing output .tcl
and .qip
files pointing into that adjacent vhdl directory should be easy to package up.
Otherwise end up needing to send whole output directory with log files and many VHDL files - gets big...
Vitis could use AXIS specific mapping of ports
map_axi_stream io_and_ctrl_in_data_0 io_and_ctrl_in_valid_0 in_ready_return_output_0 clk_300p0_0 input_stream slave
map_axi_stream out_data_return_output_0 out_valid_return_output_0 io_and_ctrl_out_ready_0 clk_300p0_0 output_stream master
Some kind of pragma to mark AXIS interfaces?
^ in the coming months should be able to squeeze in time for some kind of --xo
option to make vivado produce an .xo file with those axi mappings are needed for the ip export
Might need to be --xo_axis
specific to saying 'make an AXIS mapped IO .xo file'
I think can infer which signals belong to axis by name valid
ready
data
for now....
ex. csv, json or something idk?