Not new but almost unused Lime-SDR mini died on me? (failed to start rx mode)

[vega4]

So once it arrived, everything worked. I played around with Universal Radio Hacker and stuff.

Due to lack of time, it ended up in a locker after a couple of days.

Until today that is, which is when I pulled it out just to see that:

Universal Radio Hacker wouldn’t be able to use it (Raspberry Pi 3):

LimeSDR-OPEN (LimeSDR Mini, media=USB 3, module=FT601, serial=1D5881B332D4B1, index=0): Success

LimeSDR-INIT: Error Code: -1 (-1)

LimeSDR: failed to start rx mode

Thought maybe was something wrong with Rasp… USB 2.0 instead of 3.0 …maybe voltage too low and stuff… so I bought an USB HUB, which was supposed to give it more joice… nothing… same…

So I plugged it into a Windows 10 box. Same.

Run tests:

[ TESTING STARTED ]
->Start time: Wed May  4 13:27:50 2022
->LimeSuite version: 20.10.0-g1480bfea

->Device: LimeSDR Mini, media=USB 3, module=FT601, serial=1D5881B332D4B1, index=0, HW=3, GW=1.30
  Serial Number: 1D5881B332D4B1
 Chip temperature: 45 C

[ Clock Network Test ]
->REF clock test
  Test results: 22116; 35313; 48510 - PASSED
->VCTCXO test
  Results : 6711085 (min); 6711238 (max) - PASSED
->Clock Network Test PASSED

[ FPGA EEPROM Test ]
->Read EEPROM
->Read data: 13 0A 15 13 0A 15 02
->FPGA EEPROM Test PASSED

[ LMS7002M Test ]
->Perform Registers Test
->External Reset line test
  Reg 0x20: Write value 0xFFFD, Read value 0xFFFD
  Reg 0x20: value after reset 0x0FFFF
->LMS7002M Test PASSED

[ RF Loopback Test ]
->Configure LMS
TuneVCO(CGEN) - failed to lock (cmphl!=0)
SetFrequencyCGEN(61.44 MHz) failed
TuneVCO(CGEN) - failed to lock (cmphl!=0)
SetFrequencyCGEN(122.88 MHz) failed
Failed to set sample rate
->RF Loopback Test FAILED

=> Board tests FAILED <=

Elapsed time: 3.02 seconds

which is when I started to become worried… but come on… I said to myself…it must be something with firmware… maybe… right?

Flashed it like 3 times…not with --update but explicitly providing bin files… nothing.

Looks dead.

Ideas?

[ricardas]

It does not look completely dead. Seems the failure is CGEN PLL is not locking on.
Start LimeSuiteGUI, go to Options->Connection settings, connect to device, click “Default” button at the top. Go to CGEN tab, set CLK_H frequency to 61.44 MHz, click “Calculate”, there should be no errors. If it fails, try changing CSW_VCO_CGEN values to 0 and 255, doing that check if the VCO Comparators values changes.

[vega4]

As soon as I clicked the DEFAULT button it showed a dialog box saying it failed and log:

20:02:05] INFO: Disconnected control port
[20:03:14] INFO: Reference clock 40.00 MHz
[20:03:14] INFO: Connected Control port: LimeSDR-Mini FW:6 HW:3 Protocol:1 GW:1.30 Ref Clk: 40.00 MHz
[20:03:30] ERROR: TuneVCO(CGEN) - failed to lock (cmphl!=0)
[20:03:30] ERROR: SetFrequencyCGEN(61.44 MHz) failed

Further when I try to use CLKGEN is says:

[20:07:02] ERROR: TuneVCO(CGEN) - failed to lock (cmphl!=0)
[20:07:02] ERROR: SetFrequencyCGEN(61.44 MHz) failed

[vega4]

As I try toggling the CSW_VCO_GEN parameter, the Comprator value remains unchanged. It’s High:0 Low:0 all the time.

What happened to my Lime?=/ strangest thing is… it was in a locker all that time.

[vega4]

If I change CSW_VCO_GEN to 0 from 254 (it wont let for 255) and click calculate again, it throws an arror nd jumps back to 254. Same on WIndows same on Linux.

Log during the entire process, which you’ve suggested:

[20:13:25] INFO: Disconnected control port
[20:13:51] INFO: Reference clock 40.00 MHz
[20:13:51] INFO: Connected Control port: LimeSDR-Mini FW:6 HW:3 Protocol:1 GW:1.30 Ref Clk: 40.00 MHz
Pressing DEFAULT button:
[20:14:05] ERROR: TuneVCO(CGEN) - failed to lock (cmphl!=0)
[20:14:05] ERROR: SetFrequencyCGEN(61.44 MHz) failed
Further:
[20:14:38] ERROR: TuneVCO(CGEN) - failed to lock (cmphl!=0)
[20:14:38] ERROR: SetFrequencyCGEN(61.44 MHz) failed
Trying to play with the slider:
[20:15:01] ERROR: TuneVCO(CGEN) - failed to lock (cmphl!=0)
[20:15:01] ERROR: SetFrequencyCGEN(61.44 MHz) failed
[20:15:07] ERROR: TuneVCO(CGEN) - failed to lock (cmphl!=0)
[20:15:07] ERROR: SetFrequencyCGEN(61.44 MHz) failed
[20:15:19] ERROR: TuneVCO(CGEN) - failed to lock (cmphl!=0)
[20:15:19] ERROR: SetFrequencyCGEN(61.44 MHz) failed

[vega4]

The lime was used a couple of times. Spent 12 + months in a locker in a 3D printed protective casing . USB 3.0 from Asus Zenbook was everything it was ever connected to… and the antennas it shipped with. now the rasp.

[vega4]

From what I understand, and from the logs it seems that the process which you’ve outlined depicts the exactly same API calls the URH was attempting to accomplish, why the assumption tht these wouldn’t fail from Lime Suite?

[ricardas]

the “Calculate” button starts a tuning algorithm, that searches for a suitable CSW_VCO_CGEN value using comparators as guides. I asked to manually try setting CSW_VCO_CGEN values to 0 and 255, to see if the comparators are working properly. Apparently in your case they are always 0, so that explains why the algorithm fails.
I have no idea why the comparators have stopped working, it’s definitely not a software/firmware issue.

[vega4]

Anyone else? I don’t really have hardware knowledge needed to assess low-level inertias of this equipment.

Even ‘hardware-fellas’, I talked to, who do high-precision soldiering on daily basis not really know how to tackle this.

I cannot find many of such cases on the Internet, did I just get extremely unlucky?

[vega4]

[vega4]

[vega4]

Maybe some knowledgeable folk could take a look at the above, please?

[vega4]

No idea what happened to it. It was unused in original casing, the transparent one, with screws in each corner, with logo cut out. It worked just fine 12+ months ago, was fed with USB 3.0 and 2.0 from asus zenbook… guess I already said that… tried flashing older firmwares/gatewares - no luck. Last time it was plugged in- it worked just fine.

[vega4]

Any guidance for ‘hardware-fellas’ as to which part/elements of the board ‘to check’ would be appreciated.

[vega4]

Anyone ? It’s like I still haven’t thrown it away.

[vega4]

In my desperation I will allow myself to tag @Zack as of the 1-3 people who reply on this forum he seems to be knowledgeable in hardware.

[Zack]

Hi @vega4,
Contact the seller to see if it is still under warranty and ask for replacement. Something is wrong with clock generator inside of LMS7002M.