I’ve found some other posts relating to this too but I did my own research and I’m not sure if my board is bad or if it’s just the Firmware Version since 2.15 has broken things.
I just received my LimeSDR in the mail about 3 hours ago, fresh as can be. The first thing I did after receiving it was about 4 or 5 selfquicktests to make sure it really works, all the tests succeeded with no issue. After the tests succeeded i used LimeUtil --update to update to the latest gateway, 2.22. Doing the selfquicktests once more returns incredibly mixed results. Sometimes it passes but most times it presents the following:
[ RF Loopback Test ]
Note: The test should be run without anything connected to RF ports
->Configure LMS
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
LML RX phase search FAIL
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
SetPllFrequency: error configuring phase
LML TX phase search FAIL
Failed to set sample rate
->RF Loopback Test FAILED
The error “SetPllFrequency: error configuring phase” always seems to appear regardless. Since the original firmware returned Passed always with no issue I decided to downgrade firmware versions 1 by 1 to identify if an older firmware resolves this. After downgrading from 2.22 to 2.21,2.20,2.19…etc and finally to 2.14, I found that with firmware 2.14 we remove the “SetPllFrequency: error configuring phase” and the selfquicktest once again works without issue.
Obviously I would like to use the latest firmware, as 2.14 was created in 2018 and I don’t believe even includes SoapySDR compatibility as it wasn’t introduced until 2019 even.
Since older gatewares work I’m wondering, is this an issue with the latest gatewares causing this? Could this still be a faulty LimeSDR device even though tests with older gatewares work and remove the error, and sometimes it still passes even though it mostly errors out? And could this just be an issue with selfquicktest and the latest gateware for LimeSDR non mini and that I should instead just rely on the manual test results for the LimeSDR regular and keep using the latest 2.22 firmware? Thanks!
PS: I did in fact remove all my antennas prior to testing as it says do not connect anything to RF ports so that is not the issue.