I am having an issue very similar to @sgoudelis. I just received my LimeSDR mini and wanted to get a minimal functioning system or at least check that the hardware was functioning. SoapySDRUtil finds it correctly and identifies it as the LimeSDR mini (though it often states the connection as USB 2.0 and I have to reconnect). Gqrx, SoapySDR and LimeSuite are all compiled from source using the latest versions. The terminal output from starting gqrx seems to indicate a hardware level issue or at least a LimeSuite issue.
---------@---------:~$ gqrx
gr-osmosdr v0.1.4-98-gc653754d (0.1.5git) gnuradio 3.7.11
built-in source types: file fcd rtl_tcp hackrf rfspace soapy redpitaya
Resampling audio 96000 → 48000
BookmarksFile is /home/---------/.config/gqrx/bookmarks.csv
gr-osmosdr v0.1.4-98-gc653754d (0.1.5git) gnuradio 3.7.11
built-in source types: file fcd rtl_tcp hackrf rfspace soapy redpitaya
[INFO] Make connection: ‘LimeSDR Mini [USB 3.0] 1D398DB2355BCC’
[INFO] Reference clock 40.00 MHz
[INFO] Device name: LimeSDR-Mini
[INFO] Reference: 4e+07 MHz
[ERROR] SetPllFrequency: timeout, busy bit is still 1
[INFO] LMS7002M calibration values caching Disable
[ERROR] SetPllFrequency: timeout, busy bit is still 1
[WARNING] LNAL has no connection to RF ports
[INFO] RX LPF configured
[ERROR] MCU error code(6): Invalid Rx path
I have also rebuilt LimeSuite after doing “git checkout ebd027169defc9689d1eefa0f57d4df617b7cc4d” which was what the maintainer of SDRAngel suggested in the github issue to revert a recent change in the LimeSuite source code but that caused further issues shown below
[ERROR] SetFrequencyCGEN(640 MHz) failed:
INT: 63 FRAC: 0 DIV_OUTCH_CGEN: 1
VCO: 2560 MHz RefClk: 40 MHz
TuneVCO(CGEN) - VCO too low
[ERROR] SetFrequencyCGEN(640 MHz) failed:
INT: 63 FRAC: 0 DIV_OUTCH_CGEN: 1
VCO: 2560 MHz RefClk: 40 MHz
TuneVCO(CGEN) - VCO too low
For gqrx I am using the config file that @andrewback suggested in another thread (LimeSDR Mini Drivers and Tests - #4 by andrewback)
Looking for any definitive way to confirm that this is a hardware issue with the LimeSDR mini or if it is a software issue with the current version of LimeSuite