cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
3,057 Views
Registered: ‎05-15-2017

Unable to run 'tcl' file on Vivado 2016.4 version

Jump to solution

Hi, 
I am trying to run a .tcl file originally configured for 2014.4 on 2016.4 version of Vivado. However I am getting the following error:

while executing
"create_bd_cell -type ip -vlnv xilinx.com:ip:mig mig_0 "
    (procedure "create_root_design" line 111)
    invoked from within
"create_root_design """
    (file "all.tcl" line 405)

The tcl file uses the part 'xcku040-ffva1156-2' and tries to access the IP 'mig' which I believe is renamed/changed on later versions. Is there any workaround for this? 
Attaching the '.tcl' file for reference.

 

Steps I have done till now:

1. Changed the version number to 2016.4

2. tried replacing target boards.

3. tried on the same board with an alternate IP for mig.

4. tried on both 2016.4 and 2015.4 versions

 

None of these has worked so far

 

Tags (4)
0 Kudos
1 Solution

Accepted Solutions
Highlighted
Moderator
Moderator
5,434 Views
Registered: ‎11-09-2015

Re: Unable to run 'tcl' file on Vivado 2016.4 version

Jump to solution

Hi @ravikanth1984,

 

The workaround is to use 2014.4, generate the design and then move to 2016.4 and upgrade the IP (following the IP change log for changes that has to be made). If the IP does not exists, find which IP is the replacement.

 

After that you can regenerate a script for 2016.4 (file > write project tcl)

 

Regards,

 

Florent


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**

View solution in original post

1 Reply
Highlighted
Moderator
Moderator
5,435 Views
Registered: ‎11-09-2015

Re: Unable to run 'tcl' file on Vivado 2016.4 version

Jump to solution

Hi @ravikanth1984,

 

The workaround is to use 2014.4, generate the design and then move to 2016.4 and upgrade the IP (following the IP change log for changes that has to be made). If the IP does not exists, find which IP is the replacement.

 

After that you can regenerate a script for 2016.4 (file > write project tcl)

 

Regards,

 

Florent


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**

View solution in original post