What Neel says in the previous is correct, but it doesn't answer your question. This error is telling you that the script is having issues with the Vivado licenses on your PC. One of the first things that the *uhd_image_builder.py *script does is execute *setupenv.sh *in *fpga/usrp3/top/x300*. To attempt to debug, navigate to that directory, and execute the setup script manually from the command line *(source ./setupenv.sh* on Linux) and then try to launch Vivado from the command line. If Vivado launches successfully, go the Help-->License Manager and make sure there aren't any expired licenses and that Vivado is properly recognizing your 2018.3 license. If Vivado doesn't launch, make sure that the setup script is pointing to the location where you installed Vivado.
You might also try running *uhd_image_builder.py -c*, which will clean up any old IP cores and regenerate them. -Robin On Mon, Sep 2, 2019 at 8:08 AM Neel Pandeya via USRP-users < usrp-users@lists.ettus.com> wrote: > Hello Steve: > > In the UHD 3.14 release series, RFNoC requires the use of Xilinx Vivado > version 2017.4. In the UHD 3.15 release series, RFNoC will require the use > of Xilinx Vivado version 2018.3. Other versions of Vivado have not been > tested and are not supported. Please note that 3.15.0.0 has not been > released yet. I would suggest that you continue using the 3.14 release > series until 3.15.0.0 is available, and this will allow you to continue > using Vivado 2017.4. Your Xilinx license should allow you to install and > use multiple versions of Vivado. Please let me know if you have any > further questions. > > --Neel Pandeya > > > > On Mon, 2 Sep 2019 at 09:05, shachar J. brown via USRP-users < > usrp-users@lists.ettus.com> wrote: > >> Hi all, >> >> I have been working for a long while with rfnoc on an X310. >> >> I have lately upgraded the rfnoc, and now when I try to run >> uhd_image_builder.py I receive an error indicating I need Vivado 2018.12, >> while my licence is for 2018.3. Upgrading the Vivado is currently not >> available. >> >> 1. Is there any workaround for using the updated rfnoc version alongside >> Vivado 2018.3 or older? >> 2. If the first suggestion is not an option, is there any way to >> downgrade the rfnoc to a version that is compatiable with Vivado 2018.3 or >> older? >> >> Thanks in advance! >> Steve >> >> _______________________________________________ >> USRP-users mailing list >> USRP-users@lists.ettus.com >> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >> > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
