Soapy and LimeSuite successfully recognize the LimeSDR.
However, inside of GNURadio when I am using the Osmocom source block, it reports null source when I have device arguments āsoapy=0,driver=limeā or when I dont put any device arguments.
The osmocom block does not list āsoapyā as a built in source, which I believe is the issue.
Iām having a lot of trouble trying to make āsoapyā a built in sourceā¦
Any help is appreciated!
Yes, with āsudo apt-get install gr-osmosdrā. Iāve tried it on 4 computers, and it worked on 1 computer because āsoapyā was a ābuilt-in sourceā. The āsoapyā component was disabled on the other 3 computers. Iām not sure how to install gr-osmosdr such that āsoapyā is in the āenabled components listā.
Odd. I just checked and my gr-osmosdr is from the Myriad-RF PPA.
With SoapySDR from packages and making sure you also have libsoapysdr-dev installed, you could try removing the gr-osmosdr package and building just this from source.
SoapySDR is technically part of Pothosware and this has its own discussion group, so it could also be worth posting there if you donāt have any luck.
Could you be more specific about which PPA in Myriad-RF you downloaded with āsudo apt-get install gr-osmocomā?
I have Soapy as an enabled component when I install gr-osmocom in the root directory with:
git clone git://git.osmocom.org/gr-osmosdr
cd gr-osmosdr/
mkdir build
cd build/
cmake ā¦/
make
sudo make install
sudo ldconfig
ā¦but, when its finished, the osmocom block is not available in gnuradio.
It seems the only way for me to see the component is to install gr-osmosdr in my user name directory, but the osmocom block doesnāt show up as having āsoapyā as a built in source.
After installing SoapySDR, LimeSuite, then,
if I do āapt search SoapySDRā, it gives me a list of modules I can install. I installed anything that looked pertinent.
Gnuradio worked, but when I installed gr-osmosdr with:
Installing gr-osmosdr package is enough to bring in any dependencies like soapysdr. And in addition you will want soapysdr-module-lms7 and limesuite for limesuite command line utils and soapysdr bindings.
And very importantly, be careful with mixing libraries/packages from source and from package managers. Things in /usr (binaries from package managers) and things in /usr/local (source builds) are usually both in the default search path (modules, runtime libraries, python etc) and its easy to make things crash with ABI issues or python errors. If you follow these rules you should be ok (like in general, not just for projects in this ecosystem):
never install the same piece of software from both apt and from source. Only one must exist at a time
if a software is installed from source, all software dependent on this must also be installed from source
and following rules 1 and 2: if a runtime library is installed from apt, but you need to compile a dependency against it, do install the corresponding -dev development package
So its totally cool to mix and match packages available in the PPA and source builds, but you need to follow the chain of dependencies. People do it all the time to get particular features updated, but to avoid rebuilding the entire kitchen sink. So judging from the comments above, you might have a few things to cleanup/revisit to get your software install sane.
It is possible to install such driver stack on Odroid ARM boards. Especially XU4 may be worth a shot because of USB 3.0 support (in fact, I have used LimeSDR via GNURadio on this board without any issues). But we canāt really tell whether it will be powerful enough for your application or not
I have an XU4. Could you send me the history of the terminal commands you used to set up LimeSDR via GNURadio? Did you have to use snappy?
My problem is that I canāt get āsoapyā to be a built in source in the osmocom block on the Odroid XU4. Iāve gotten it to work on x86 architectures.
Basically you should follow this order of software installation:
SoapySDR
LimeSuite
UHD (optional, or as I see it: highly recommended because of limited functionality of Osmocom sources/sinks)
GNURadio
gr-osmocom
SoapyUHD (as above)
Especially, gr-osmocom should be installed after installing SoapySDR & LimeSuite combo. I believe this is the mistake you made. But you should be able to resolve the issue by reinstalling gr-osmocom now.
My way of making everything work was building from source every software listed above, unfortunately I got no terminal history available at the moment. But there are details instructions how to build all of it.