Hi Xavier, Option 3 is the correct choice. I think if you had installed Vivado 2019.2 then it should have just compiled. Vivado is mostly backwards compatible and so Vivado 2019.1 won't necessarily recognise vivado 2019.1.1 scripting. I think that is your issue.
Anyway, great tips from Jonathon going forward - always use the versions as specified in the readthedocs first! Kind regards, Adam Isaacson South African Radio Astronomy Observatory (SARAO) Hardware Manager Cell: (+27) 825639602 Tel: (+27) 215067300 email: [email protected] On Wed, Sep 9, 2020 at 8:10 AM Xavier Bosch <[email protected]> wrote: > Hi Jonathon, > > Thank you for your response. SOLVED! > I opted to follow option 3) i.e.: install 2019.1.1 and it worked like a > charm! > ReadTheDocumetns webpage is correct, asks for 2019.1.1, I am surprised by > the level of version dependency of these TCL scripts. > Thank you again, > Best, > XB > > > On Tue, Sep 8, 2020 at 11:02 PM Jonathon Kocz <[email protected]> wrote: > >> Hi Xavi, >> >> As I found recently, the block diagram tcl scripts are *really* pedantic >> about the version they are run in. If it doesn't match, they just don't >> run, and then the design can't be compiled. >> >> Checking out git, it looks like this happened during the last hardware >> porting workshop, and the docs should have been updated to be accurate a >> few months ago. - It looks like they ask for Vivado 2019.1.1 >> https://casper-toolflow.readthedocs.io/en/latest/src/Installing-the-Toolflow.html, >> but there might be a page we missed with old instructions. If there is one >> with 2019.1 listed, can you let me know and I'll get it fixed. >> >> A few things you could try: >> >> 1) Edit the tcl script for the block diagram so it checks for version >> 2019.1 instead of 2019.1.1 (a little risky, but it might work - >> https://github.com/casper-astro/mlib_devel/blob/master/jasper_library/hdl_sources/infrastructure/red_pitaya.tcl >> line 23) >> 2) Regenerate the block diagram as the error message suggests (a bit more >> effort than 1, but not too bad) >> 3) Upgrading to 2019.1.1 should solve the problem. >> >> Cheers, >> Jonathon >> >> >> On Tue, 8 Sep 2020 at 22:13, Xavier Bosch <[email protected]> >> wrote: >> >>> Hi all, >>> >>> I installed a fresh 16.04 Ubuntu with Xilinx Vivado 2019.1 and Matalb >>> 2018a, as readthedocs suggested for the RedPitaya board. >>> I am using the master branch from mlib_devel commit >>> ee6841c5b6392e1a9e6b302e2edbe875034efdcf from Thu 28 May, 2020. >>> >>> I created the pithon3 virtual environment and installed the >>> requirements >>> As a comment my stratsg.local file is correctly populated except for the >>> variable "XML2VHDL_PATH", that I do not know how to configure, it seems a >>> new parameter to me. >>> >>> I succeeded in compiling an old SNAP design, no problems. Then I >>> proceeded to do a new design inspired by the Wide-ish band Spectrometer >>> Tutorial and I got an error message as follows (see screenshot): >>> >>> >>> *ERROR: [BD_TCL-109] This script was generated using Vivado <2019.1.1> >>> and is being run in <2019.1> of Vivado. Please run the script in Vivado >>> <2019.1.1> 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.* >>> *WARNING: [Vivado 12-818] No files matched >>> '/home/javierb/workspace/designs/rpitaya_test01/myproj/myproj.srcs/sources_1/bd/red_pitaya/red_pitaya.bd >>> <http://red_pitaya.bd>'* >>> *# generate_target all [get_files [get_property directory >>> [current_project]]/myproj.srcs/sources_1/bd/red_pitaya/red_pitaya.bd >>> <http://red_pitaya.bd>]* >>> *WARNING: [Vivado 12-818] No files matched >>> '/home/javierb/workspace/designs/rpitaya_test01/myproj/myproj.srcs/sources_1/bd/red_pitaya/red_pitaya.bd >>> <http://red_pitaya.bd>'* >>> *# make_wrapper -files [get_files [get_property directory >>> [current_project]]/myproj.srcs/sources_1/bd/red_pitaya/red_pitaya.bd >>> <http://red_pitaya.bd>] -top* >>> *# add_files -norecurse [get_property directory >>> [current_project]]/myproj.srcs/sources_1/bd/red_pitaya/hdl/red_pitaya_wrapper.vhd* >>> *ERROR: [Vivado 12-172] File or Directory >>> '/home/javierb/workspace/designs/rpitaya_test01/myproj/myproj.srcs/sources_1/bd/red_pitaya/hdl/red_pitaya_wrapper.vhd' >>> does not exist* >>> *INFO: [Common 17-206] Exiting Vivado at Tue Sep 8 14:32:38 2020...* >>> *Traceback (most recent call last):* >>> * File >>> "/home/javierb/workspace/mlib_devel/jasper_library/exec_flow.py", line 226, >>> in <module>* >>> * synth_strat=opts.synth_strat, impl_strat=opts.impl_strat)* >>> * File "/home/javierb/workspace/mlib_devel/jasper_library/toolflow.py", >>> line 1834, in compile* >>> * raise Exception('Vivado failed!')* >>> *Exception: Vivado failed!**Error using jasper (line 23)* >>> *Backend build failed! Check log files for more information * >>> >>> >>> >>> My understanding is that there is a conflict between the Vivado 19.1.1 >>> and some other part that requires 19.1. >>> I am confident I followed the installation steps recommended at >>> readthedocs.com website. >>> Have you seen an error like that before? Any idea what it could be? >>> >>> Thank you for your time, >>> XB >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "[email protected]" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAMehrA1Jo7VJiBfGeiES1VNZbHZwR_Gc08C-o4WSbPjury2Jsg%40mail.gmail.com >>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAMehrA1Jo7VJiBfGeiES1VNZbHZwR_Gc08C-o4WSbPjury2Jsg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "[email protected]" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAPU71P-wTYz3_jTX4G%2BL-AGombn5i7_be7u%3DvGj_i-37JRLSuA%40mail.gmail.com >> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAPU71P-wTYz3_jTX4G%2BL-AGombn5i7_be7u%3DvGj_i-37JRLSuA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups " > [email protected]" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAMehrA3a7FqZiam6bwOMYccZ_VY9qwk-FgpzXd8_Hg4jVSt7Yw%40mail.gmail.com > <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAMehrA3a7FqZiam6bwOMYccZ_VY9qwk-FgpzXd8_Hg4jVSt7Yw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CADTJ%3DnHvnE1SEe4bEt3-rA-V3yuORMPE4zz5NHs_2pduqTbpSQ%40mail.gmail.com.
