Mikio,
Thanks much for pointing me to the correct documentation. That seems to be
doing the trick.
Regards,
Jeff
Original message
From: Mikio Fukushima
Date: 9/1/19 7:59 PM (GMT-06:00)
To: Jeff S
Cc: usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Starting from
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*.
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
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
Sam,
I do NOT see it hang if I specify --args type=b200. I also found out,
that it does not hang every time without specifying hint.
Jakub.
Dne 2019-08-30 18:23, Sam Reiter napsal:
Jakub,
If you specify:
uhd_find_devices.exe --args type=b200
Do you still see it hang?
Sam
On Fri, Aug
Hey Sam,
thank you for your answer. Is your suggested [1] really useful for the
RFNoC Radio Blocks I am using? I think I only can use the commands from
path/include/ettus/rfnoc_radio.h, because the RFNoC_Radio Blocks are not
derived from usrp_block. (As far as I know)
I then tried the timed
Dear Michael,
Thanks a lot for the clarifications, it's indeed an issue we ran into.
I'm going to try this out now.
Cheers
mpb
On 23/08/2019 19:28, Michael West wrote:
> Hi Matthias,
>
> The new B200 bootloader helps with failures to enumerate the device when
> it is plugged in before the