-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design upgrade to 2019.1 #1
Comments
Hi,
In the scripts, you can just simply change the check comparison of 2018.3
to 2019.1 and it should work fine.
Kind regards,
Ussama
…On Mon, Jun 8, 2020 at 2:57 AM Bilge Mirac Atici ***@***.***> wrote:
Hello, I'm trying to build PYNQ image for my Zybo Z7-10. As shown in the
link <https://discuss.pynq.io/t/3rd-party-images-for-zynq-boards/431> I'm
using your projects. I would like to build PYNQ 2.5 that requires SDK
2019.1. However, design file and script was generated using 2018.3 Is there
any chance to upgrade it to 2019.1?
Thanks in advance.
-- Build output --
This script was generated using Vivado <2018.3> and is being run in
<2019.1> of Vivado. Please run the script in Vivado <2018.3> then open the
design in Vivado <2019.1>. Upgrade the design by running "Tools => Report
=> Report IP Status...", then run write_bd_tcl to create an updated script.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBFVIFIFW45A5WXGK72CYDRVRAQLANCNFSM4NX3AZMA>
.
|
Thanks for fast response. I will try, however, one of the guides I read before said that designs are compatible with only version which it was generated. Did you ever do this trick before? And also, do I need to edit both two files; |
Hi again. I tried to change Vivado version to 2019.1 on two files, mentioned before. I also would like to use board-agnostic image to shorten image build time. So my command is:
However, I got different error. It is shown below. Do you have any idea about that? Thanks in advance, bests.
|
has there been any update to this, or @miracatici did you ever have any success on this. I'm currently in the same position trying to get pynq 2.5 running on a zybo z7-10 |
Well I thought it was finally going to work, but it ended up failing. Here is the error.
EDIT: apprently this problem was from running directly off of the /pynq drive created for the vagrant vm. cloning the pynq git into /workspace got me up to the error that @ussamazahid96 has. |
Okay, so I figured out that error. Vivado didn't have the board files for any of the digilent boards. Installing all of those plus deleting the failed Zybo project from sdbuild allowed it to progress further. I am curious in that it appears to be using the general |
Sorry, unfortunately I didn't push forward this study due to lack of time. However it's more than welcome to share your build result. If you got success, you might create a merge request about this improvement? |
Hello, I am trying to build a PYNQ image for my Zybo Z7 - 20 however, there are many issues that I ran into. Just a quick question, why doesn't anyone post the Zybo image files for PYNQ? Are we required to build one for ourselves for it to work? |
Been trying to find a Zybo Z7-20 image file for PYNQ however, only guides that are not fully complete are found and I am unsure of the necessary steps that are needed to take at times, so I am unable to create my own image file. |
Hello, I'm trying to build PYNQ image for my Zybo Z7-10. As shown in the link I'm using your projects. I would like to build PYNQ 2.5 that requires SDK 2019.1. However, design file and script was generated using 2018.3 Is there any chance to upgrade it to 2019.1?
Thanks in advance.
-- Build output --
This script was generated using Vivado <2018.3> and is being run in <2019.1> of Vivado. Please run the script in Vivado <2018.3> then open the design in Vivado <2019.1>. Upgrade the design by running "Tools => Report => Report IP Status...", then run write_bd_tcl to create an updated script.
The text was updated successfully, but these errors were encountered: