Hello Ricardo Nuszkowski,

Sorry, I forgot to edit my e-mail before sending it out: you probably
should ask this to MyriadRF guys first, and then move to other forums.

Regards,
Kyeong Su Shin

On Tue, Nov 14, 2017 at 2:46 PM, Kyeong Su Shin <[email protected]> wrote:

> Hello Ricardo Nuszkowski,
>
> The error messages are saying that it failed to initialize your radio
> hardware properly. It is either gr-osmosdr or SoapySDR (I think this is
> more likely), not really (the main tree) GNU Radio's fault. I recommend
> asking the same question on their mailing lists or forums as well. (I think
> myriadrf is the right place to ask).
>
> The first error message is probably related to this:
> https://discourse.myriadrf.org/t/limesdr-arrived-but-
> cant-get-it-to-work/744/11
>
> I am not sure about the second error message - it does complain about your
> sampling rate settings, though.
>
> When the failure happens, the Osmocom source is automatically replaced to
> a null source, which does nothing. So, you will get an empty WX waterfall
> window. (by the way, I suggest considering QT waterfall or QT-fosphor, as
> WX GUI is not supported well anymore.)
>
> Regards,
> Kyeong Su Shin
>
> On Tue, Nov 14, 2017 at 1:58 PM, Ricardo Nuszkowski <
> [email protected]> wrote:
>
>> Hello,
>>
>> We will be running a basic flow graph to test our antenna with the
>> LimeSDR.
>> The flowgraph is basically an osmocom source--> WX GUI waterfall sink.
>>
>>
>> It will run perfectly fine for some operations and then every once in a
>> while we will run it and get this error. It then works fine after we hit
>> the reset button on the LimeSDR.
>>
>> We will get this error.
>>
>> Generating: '/home/ground/Documents/top_block.py'
>>
>> Executing: /usr/bin/python2 -u /home/ground/Documents/top_block.py
>>
>> gr-osmosdr v0.1.4-98-gc653754d (0.1.5git) gnuradio 3.7.11.1
>> built-in source types: file osmosdr fcd rtl rtl_tcp rfspace soapy
>> redpitaya
>> [INFO] Make connection: 'LimeSDR-USB [USB 2.0] 9070602491E35'
>> [1m [33m[WARNING] Gateware version mismatch!
>>   Expected gateware version 2, revision 11
>>   But found version 0, revision 0
>>   Follow the FW and FPGA upgrade instructions:
>>   http://wiki.myriadrf.org/Lime_Suite#Flashing_images
>>   Or run update on the command line: LimeUtil --update
>> [0m
>> [INFO] Device name: LimeSDR-USB
>> [INFO] Reference: 30.72 MHz
>> [INFO] Init LMS7002M(0)
>> [INFO] Ver=0, Rev=0, Mask=0
>>
>> FATAL: ResetChip() failed
>>
>> Trying to fill up 1 missing channel(s) with null source(s).
>> This is being done to prevent the application from crashing
>> due to gnuradio bug #528.
>>
>>
>> (top_block.py:4176): Gtk-WARNING **: gtk_widget_size_allocate(): attempt
>> to allocate widget with width -5 and height 20
>>
>> (top_block.py:4176): Gtk-WARNING **: gtk_widget_size_allocate(): attempt
>> to allocate widget with width -5 and height 20
>>
>> (top_block.py:4176): Gtk-WARNING **: gtk_widget_size_allocate(): attempt
>> to allocate widget with width -5 and height 20
>>
>> (top_block.py:4176): Gtk-WARNING **: gtk_widget_size_allocate(): attempt
>> to allocate widget with width -5 and height 20
>>
>> >>> Done (return code -9)
>>
>>
>> Ocassionally, we also get this error as well:
>>
>> Generating: '/home/ground/Documents/top_block.py'
>>
>> Executing: /usr/bin/python2 -u /home/ground/Documents/top_block.py
>>
>> gr-osmosdr v0.1.4-98-gc653754d (0.1.5git) gnuradio 3.7.11.1
>> built-in source types: file osmosdr fcd rtl rtl_tcp rfspace soapy
>> redpitaya
>> [INFO] Make connection: 'LimeSDR-USB [USB 2.0] 9070602491E35'
>> [INFO] Reference clock 30.720 MHz
>> [INFO] Device name: LimeSDR-USB
>> [INFO] Reference: 30.72 MHz
>> [INFO] Init LMS7002M(0)
>> [INFO] Ver=7, Rev=1, Mask=1
>> [INFO] LMS7002M calibration values caching Disable
>> [1m [31m[ERROR] [0m
>> [1m [33m[WARNING] SoapyLMS7::setSampleRate(): not a power of two factor:
>> TSP Rate = 15.36 MHZ, Requested rate = 10 MHz [0m
>> [1m [31m[ERROR] [0m
>> [1m [31m[ERROR] [0m
>> [1m [31m[ERROR] setBandwidth(Rx, 1, 30 MHz) Failed - [0m
>>
>> FATAL:
>>
>> Trying to fill up 1 missing channel(s) with null source(s).
>> This is being done to prevent the application from crashing
>> due to gnuradio bug #528.
>>
>> If anyone knows what is going on, that would be great.
>>
>> Ricardo
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> [email protected]
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
>
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to