05-20-2019 10:31 AM
I am fairly new to both Vivado and TCL, so I figured I would kill two birds with one stone, since I'd like to get a better handle on TCL.
Say I create a port in the block diagram and set the 'type' to 'data'. (See attached screengrab.) If I want to later change the type to 'clk', in the Block Design editor of Vivado 2018.3 I apparently must delete the port and then re-add it to the BD, since External Port Properties panel will not allow me to change the 'type' field.
1) Can I change the 'type' field with a TCL command that simply changes that field and leaves the port name, direction, width, etc., intact?
2) Does the type field actually affect synthesis or implementation, or is it for organizational purposes?
Thanks.
05-20-2019 09:19 PM - edited 05-20-2019 09:41 PM
The property TYPE associated with any BD port is a read-only property.
which means once you create a port by selecting type as reset it is assigned to that port and user can not change it.
The only way around is to delete and create a new port. (as you mentioned)
also setting the port type affects the flow.
for example, if you set a port type as a clock then synthesis will insert BUFG's and Implementation will use clock routing resources for the net associated with that particular port.
and also for the purpose of organization of ports
for example, to collect all external resets of the BD you can use the following command
show_objects -name find_1 [get_bd_ports -filter { TYPE =~ "*rst*" } ]
The best way to not to get in this blunder is to use Make External instead of Create Port... for Xilinx IP's
--Suraj
05-20-2019 09:19 PM - edited 05-20-2019 09:41 PM
The property TYPE associated with any BD port is a read-only property.
which means once you create a port by selecting type as reset it is assigned to that port and user can not change it.
The only way around is to delete and create a new port. (as you mentioned)
also setting the port type affects the flow.
for example, if you set a port type as a clock then synthesis will insert BUFG's and Implementation will use clock routing resources for the net associated with that particular port.
and also for the purpose of organization of ports
for example, to collect all external resets of the BD you can use the following command
show_objects -name find_1 [get_bd_ports -filter { TYPE =~ "*rst*" } ]
The best way to not to get in this blunder is to use Make External instead of Create Port... for Xilinx IP's
--Suraj