I’m currently using my LimeSDR-USB on a Raspberry Pi 3, using an external power supply (9V, and current is around 500mA when doing nothing), and I’m having this kind of problem quite often.
It is most of the time solved by LimeUtil --update, but it takes several minutes and I’m concerned it is hiding a more severe issue (hopefully not a power-related one !). At least once, I had to unplug and power-cycle the device for it to fully recover (not clear how it went stuck that time).
I remember the device was completely unusable when running off only one USB2 port, and exhibiting the *ware loss much more often. Anyway the Raspberry Pi is only powered through a 1A, so supplying power through USB was hopeless from the very beginning. This is the reason I soldered wire to the Vcc Ext and Gnd pads next to the supply jack (when plugged directly to the Raspberry Pi 3 the jack isn’t accessible any more).
libusb found on the host is:
lrwxrwxrwx 1 root root 19 Oct 26 2016 libusb-1.0.so.0 -> libusb-1.0.so.0.1.0
-rw-r–r-- 1 root root 83888 Oct 26 2016 libusb-1.0.so.0.1.0
LimeSuite --info provides the following answer:
Library version: v17.10.0-g5326611d
Build timestamp: 2017-10-20
Interface version: v2017.10.0
Binary interface: 17.10-1
LimeSuite --find also find the device, not matter what *ware is in there (of course, else --update wouldn’t solve anything):
- [LimeSDR-USB, media=USB 2.0, module=STREAM, addr=1d50:6108, serial=0009060B00491F29]
After LimeUtil --update, here is the answer of LimeUtil --make:
Reference clock 30.720 MHz
Device name: LimeSDR-USB
Expansion name: UNSUPPORTED
Firmware version: 3
Hardware version: 4
Protocol version: 1
Gateware version: 2
Gateware revision: 11
Gateware target: LimeSDR-USB
Serial number: 0x9060b00491f29
Free connection… OK
Let me know if you need more info / testing, I have access to the device most of the time and can experiment a lot, except maybe power-cycle and unplug operation.