discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] stop() and wait() on topblock does not work on OS


From: Stefan Oltmanns
Subject: Re: [Discuss-gnuradio] stop() and wait() on topblock does not work on OS X
Date: Thu, 25 Sep 2014 19:15:08 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:24.0) Gecko/20100101 Thunderbird/24.0

The NooElec R820T
(http://www.nooelec.com/store/sdr/sdr-receivers/nesdr-mini-rtl2832-r820t.html)
looks exactly like my R820T device, just a different branding. The
output I get:

gr-osmosdr v0.1.3-1-g4bb2fa4e (0.1.4git) gnuradio 3.7.5
built-in source types: file fcd rtl rtl_tcp rfspace
Using device #0 Realtek RTL2838UHIDIR SN: 00000001
Found Rafael Micro R820T tuner

I compiled with the same command-line, unfortunately I do not have
access to a 10.8 mac.

Am 25.09.2014 18:25, schrieb Michael Dickens:
> On Sep 25, 2014, at 10:22 AM, Stefan Oltmanns <address@hidden> wrote:
>> Unfortunately I do not have any other hardware than two different RTL
>> devices (one with E4000 tuner and one with R820T).
>> I attached the most simple program to reproduce that error, it just
>> connects the OsmoSDR source with a null sink, starts the flowgraph,
>> waits a second and then stops it and exit.
>> Working fine on Linux and Windows, but not on OS X (10.9), program never
>> returns. Same problem with all stuff (boost/libusb...) self build or
>> installed using ports.
>> Is someone able to find the bug?
> 
> I compiled your code using
> {{{
> c++ -O2 -I/opt/local/include -L/opt/local/lib -lgnuradio-osmosdr 
> -lgnuradio-runtime -lgnuradio-blocks -lboost_system-mt -Wall -o osmo_test 
> osmo_test.cc
> }}}
> then tried it using the following devices without issues (returns cleanly), 
> using MacPorts for all of the software installs, running on OSX 10.8.5 
> (latest updates), Xcode 5.1.1 (Build version 5B1008):
> 
> + HackRF Jawbreaker
> + NooElec R820T
> + ER B210
> 
> I'll try on 10.9 shortly, since maybe this is an OS specific issue. - MLD
> 
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]