Jump to content
  • 0

Having trouble to generate a Project from digilent's Github


rappysaha

Question

Hi,

I am trying to generate a project from Digilent's GitHub. I followed this following manual:

1) https://reference.digilentinc.com/learn/programmable-logic/tutorials/genesys-2-user-demo/start

2) https://reference.digilentinc.com/learn/software/tutorials/vivado-projects-from-digilent-github/start?redirect=1id=vivado/github

so, When I execute the command "source ./create_project.tcl" according to the manual link 2, it gives me following error messages:

"ERROR: This script was generated using Vivado <2015.4> and is being run in <2016.2> of Vivado. Please run the script in Vivado <2015.4> then open the design in Vivado <2016.2>. Upgrade the design by running "Tools => Report => Report IP Status...", then run write_bd_tcl to create an updated script.
 

ERROR: [BD 5-229] Please open or create a block design first.
 

ERROR: [Common 17-39] 'get_bd_designs' failed due to earlier errors."

So, how can I solve the problem? Do I need to download Vivado 2015.4 or I can do it on the Vivado 2016.2?

Any suggestion will be appreciated.

Thanks.

Link to comment
Share on other sites

4 answers to this question

Recommended Posts

Hi rappysaha,

I know that some projects you are able to make a simple one line change and have the project succcessfully work on a different version of Vivado, but I do not know if that is the case here; I have asked some of our applications engineers about this for further input.

Thanks,
JColvin

Link to comment
Share on other sites

Hello rappysaha,

You could download Vivado 2015.4 and use it to generate the project. From there you can follow the first error message you listed and open the project in Vivado 2016.2 and run Report IP Status. You won't need to run write_bd_tcl again in order to update the script unless you plan on distributing your project. You could also wait for an update to the .tcl script to get it working in Vivado 2016.2. I will reply back here once that has been done.

 

AndrewHolzer

Link to comment
Share on other sites

My practice is to remove the line that checks for the vivado version.

It will then often fail to find particular versions of IPs, so I add Tcl code to use different versions of the IP cores depending on the version of Vivado being used. Check the release notes of the IP to be sure its interface has not changed incompatibly.

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...