10-19-2020 01:30 AM
Hello,
I've met said warning message.
It turns out there is a bug in
function
proc get_psu_config {name} {
set ps_periph [hsi::get_cells -hier zynq_ultra_ps_e_0]
where the "instance name" "zynq_ultrascale_ps_0_e" is hardwired.
I did use a different instance name in my design and thus this "proc" failed.
I suggest to replace this with something similiar to
hsi::get_cells -filter { IP_NAME == "zynq_ultra_ps_e" }
Regards,
10-21-2020 07:06 AM
Hi @larice,
Thanks for reporting that.
I have created a change request to our development team in order to fix that.
10-21-2020 07:06 AM
Hi @larice,
Thanks for reporting that.
I have created a change request to our development team in order to fix that.
10-21-2020 08:38 AM
Thank You,
Best Regards,
Robert
10-26-2020 03:15 AM
namespace eval _tcl { proc get_script_folder {} { set script_path [file normalize [info script]] set script_folder [file dirname $script_path] return $script_folder } } variable script_folder set script_folder [_tcl::get_script_folder] ################################################################ # Check if script is running in correct Vivado version. ################################################################ set scripts_vivado_version 2018.3 set current_vivado_version [version -short] if { [string first $scripts_vivado_version $current_vivado_version] == -1 } { puts "" common::send_msg_id "BD_TCL-1002" "WARNING" "This script was generated using Vivado <$scripts_vivado_version> without IP versions in the create_bd_cell commands, but is now being run in <$current_vivado_version> of Vivado. There may have been major IP version changes between Vivado <$scripts_vivado_version> and <$current_vivado_version>, which could impact the parameter settings of the IPs." }