Hello all,
Could it be that at some point in time, linking against boost_thread
became necessary for programs that link against uhd?
ODR-DabMod [1] uses pkgconfig to find out how to properly link against
libuhd, whose .pc file [2] lists -lboost_system but not -lboost_thread.
ODR-DabMod isn't usin
gt;
> [sudo] uhd_images_downloader -t b2xx
>
> Regards,
> Michael
>
> On Tue, Jul 9, 2019 at 12:10 AM Matthias Brändli via USRP-users
> mailto:usrp-users@lists.ettus.com>> wrote:
>
> Dear Michael,
>
> First of all, thanks for the new UHD release to all peopl
Dear Michael,
First of all, thanks for the new UHD release to all people involved!
On 08/07/2019 20:35, Michael West wrote:
> This release includes [...] a new bootloader for B200
Is there more information about this change? Does this solve a specific
issue? I had a look at the relevant commits,
Hi Mark-Jan,
Thanks for your response.
On 03/05/2019 00:02, Mark-Jan Bastian wrote:
> For more in-depth USB debugging, there are external USB 2.0 and 3.x
> hardware bus analysers available, for example from the swiss company
> ellisys.com.
I have experience in USB protocol analysis from a previ
Dear all,
I'm maintaining ODR-DabMod[1], a Digital Audio Broadcasting modulator
which uses UHD to drive a USRP at 2048ksps, in most applications a B200.
ODR-DabMod runs the modulator and the UHD output in separate threads, to
ensure that a few modulated frames are always ready when the USRP needs
Hi Felix,
the following works for me (newlines added for readability), and I see
in the startup messages that it properly sets the master clock rate:
/usr/local/lib/uhd/examples/rx_samples_to_file
--args "serial=309B1E7,master_clock_rate=32768000"
--rate 2048000
--freq 2
--file /dev/n
Dear Felix,
I use the B200 to generate DAB signals (OFDM, 2048ksps sample rate,
1.5MHz effective BW, DQPSK) and while I cannot directly answer your
questions, maybe there are some pointers that could be useful to you.
I did get some feedback from Ettus about spurious signals that I wrote
down at
