discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: gr-soapy with lime driver no go


From: Aardric
Subject: Re: gr-soapy with lime driver no go
Date: Wed, 13 Oct 2021 19:13:02 +0000

Current status on the limeSDR with gnuradio 3.9.3:
(1) works with gr-osmosdr using driver=lime,soapy=0
(2) works with the gr-limesdr built from the gr39 branch of
https://github.com/daniestevez/gr-limesdr/tree/gr39
(3) works as expected with SoapySDRUtil
(4) does NOT work with gr-soapy lime-sdr source block
(5) rtl dongle works with the gr-soapy rtl-sdr source block.


On 2021-10-10 5:00 p.m., Aardric wrote:
> Hail,
>      My rtl-sdr soapy source block runs with attached hardware but
> running the flow graph with the lime source block throws out the
> unpleasant response:
>
>     File "./test39_lime-sdr.py", line 88, in __init__
>       stream_args, tune_args, settings)
> RuntimeError: SoapySDR::Device::make() no match
>
>   > SoapySDRUtil --find="driver=lime"
> ######################################################
> ##     Soapy SDR -- the SDR abstraction library     ##
> ######################################################
>
> Found device 0
>     addr = 1d50:6108
>     driver = lime
>     label = LimeSDR-USB [USB 3.0] 9081C05C4212E
>     media = USB 3.0
>     module = FX3
>     name = LimeSDR-USB
>     serial = 0009081C05C4212E
>
>
>    --init--
>           self.soapy_limesdr_source_0 = None
>           dev = 'driver=lime'
>           stream_args = ''
>           tune_args = ['']
>           settings = ['']
>
>           self.soapy_limesdr_source_0 = soapy.source(dev, "fc32", 1,
> "driver='lime'",stream_args, tune_args, settings)
>
> I don't know why the dev_args input of "driver='lime'" is required.
>
> git branch gnuradio 3.9-maint
> built with PyBOMBS (on 2021-10-09)
> opensuse Leap 15.2.
>
> The web page https://wiki.gnuradio.org/index.php/Soapy was informative
> but didn't tell me where to go next with this. Before I begin the
> daunting (for a non-developer) task of exploring more deeply, I thought
> to query this forum for obvious suggestions or known solution (or bug
> status).
>
> Rick
>




reply via email to

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