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 30,
Jakub,
If you specify:
uhd_find_devices.exe --args type=b200
Do you still see it hang?
Sam
On Fri, Aug 30, 2019 at 11:06 AM Jakub Rybka wrote:
> Hello Sam,
>
>rolling back to libusb 1.0.21 does indeed make things work better, but
> I must say far from perfect.
>
> D:\Libs\bin>uhd_find_de
Hello Sam,
rolling back to libusb 1.0.21 does indeed make things work better, but
I must say far from perfect.
D:\Libs\bin>uhd_find_devices.exe
[INFO] [UHD] Win32; Microsoft Visual C++ version 14.1; Boost_106900;
UHD_3.14.1.0-release
No UHD Devices Found
Without any device connected, I fi
Hey Jakub,
Thanks for the additional details. I can confirm that I've seen some
suspicious behavior from with UHD 3.14.1.0 binary on my machine since you
sent this in. It seems like libusb 1.0.22 causes crashing behavior with
uhd_find_devices. I rolled this back to libusb 1.0.21 and things seem to
Sam,
I do have drivers installed on Windows 10 machine. I can manage the code
to run by modifying UHD driver (commenting out libusb_unref_device), and
my radio is then properly found. What is bugging me, that even original
Ettus compiled UHD installer from files.ettus.com fails. If there are n
Jakub,
I'll look into this. The issues you're reporting with the binary are
probably what I'll want to try to reproduce first. Can you be more specific
as to the behavior of your system during the crash you're reporting?
Screenshots would be useful if there are dialogs present during / after the
c
