[Hackrf-dev] GNU Radio Companion

[Tom Rondeau]

On Fri, Jun 21, 2013 at 9:53 AM, Ben Gamari <bgamari.foss at gmail.com> wrote:

> Adam Laurie <adam at aperturelabs.com> writes:

>

>> On 20/06/13 13:51, Ben Gamari wrote:

>>>

>>> Note that you are running 3.6. I've been working with 3.7 which differs

>>> from 3.6 in a number of block names which explains your errors. If you

>>> don't want to hack on GnuRadio, you're probably better off sticking with

>>> 3.6.

>>

>> progress... I've edited the grc and replace the named modules with what

>> appear to be the 3.6 equivalents (attached)...

>>

>> However, I now get:

>>

>> linux; GNU C++ version 4.6.1; Boost_105300; UHD_003.005.003-83-g3924a4d7

>>

>> Using Volk machine: avx_64_mmx_orc

>> gr-osmosdr v0.0.2-1-gffd2bbf4 (0.0.3git) gnuradio 3.6.5

>> built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf

>> Using Jawbreaker with firmware git-8f55436

>>  >>> gr_fir_fff: using SSE

>> The program 'python' received an X Window System error.

>> This probably reflects a bug in the program.

>> The error was 'BadWindow (invalid Window parameter)'.

>>    (Details: serial 715 error_code 3 request_code 137 minor_code 4)

>>    (Note to programmers: normally, X errors are reported asynchronously;

>>     that is, you will receive the error a while after causing it.

>>     To debug your program, run it with the --sync command line

>>     option to change this behavior. You can then get a meaningful

>>     backtrace from your debugger if you break on the gdk_x_error()

>> function.)

>>

> Hmm, I have no idea what this might be due to. Odd. You might want to

> bring this to the gnuradio list[1].

>

> Cheers,

>

> - Ben

>

>

> [1] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Yes, this is something to talk about over on discuss-gnuradio.

Basically, we've been seeing some problems with different versions (of
something, not entirely sure what just yet) where you might have to
explicitly use '[ ]' to mark off a Python list. By default, we don't
do that and it's always worked, until recently. Easiest thing to do is
just define an empty window for your FFT block by using '[]'.

Tom