LimeSDR Mini - not recognised as USB 3.0 device

Hello,

Since upgrading to the last firmware (20.10) my LimeSDR Mini works only as USB 2.0 device, even in USB 3.0 ports (where it worked until the update).
Also, the LimeQuickTest fails:

[ TESTING STARTED ]
->Start time: Thu Jan 14 00:17:20 2021
->LimeSuite version: 20.10.0+dfsg-2

->Device: LimeSDR Mini, media=USB 2.0, module=FT601, addr=24607:1027, serial=1D589734EF6407, HW=3, GW=1.30
Warning: USB3 not available
Serial Number: 1D589734EF6407
Chip temperature: 34 C

[ Clock Network Test ]
->REF clock test
Test results: 41801; 54998; 2659 - PASSED
->VCTCXO test
Results : 6711068 (min); 6711221 (max) - PASSED
->Clock Network Test PASSED

[ FPGA EEPROM Test ]
->Read EEPROM
->Read data: 13 0A 17 13 0A 17 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
->Run Tests (TX_2 -> LNA_W):
CH0 (SXR=1000.0MHz, SXT=1005.0MHz): Result:(-21.2 dBFS, 5.00 MHz) - FAILED
->Run Tests (TX_1 -> LNA_H):
CH0 (SXR=2100.0MHz, SXT=2105.0MHz): Result:(-20.5 dBFS, 5.00 MHz) - FAILED
->RF Loopback Test FAILED

=> Board tests FAILED <=

Elapsed time: 3.15 seconds

if I downgrade to version 1.28 or lover (and use an older LimeQuickTest) the test is succesull every single time, although the LimeSDR Mini is still not recognised as USB 3.0:
[ TESTING STARTED ]
->Start time: Thu Jan 14 09:39:59 2021

->Device: LimeSDR Mini, media=USB 2.0, module=FT601, addr=24607:1027, serial=1D589734EF6407
Warning: USB3 not available
Serial Number: 1D589734EF6407

[ Clock Network Test ]
->REF clock test
Test results: 19964; 33161; 46358 - PASSED
->VCTCXO test
Results : 6711088 (min); 6711241 (max) - PASSED
->Clock Network Test PASSED

[ FPGA EEPROM Test ]
->Read EEPROM
->Read data: 13 0A 17 13 0A 17 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
->Run Tests (TX_2 -> LNA_W):
CH0 (SXR=1000.0MHz, SXT=1005.0MHz): Result:(-16.1 dBFS, 5.00 MHz) - PASSED
->Run Tests (TX_1 -> LNA_H):
CH0 (SXR=2100.0MHz, SXT=2105.0MHz): Result:(-14.6 dBFS, 5.00 MHz) - PASSED
->RF Loopback Test PASSED

=> Board tests PASSED <=

Elapsed time: 2.82 seconds

It appears that the device works despite this, but i haven’t tested it thoroughly.

I also tested the LimeSDR Mini on other USB 3.0 laptops and on neither is it recognized as a USB 3.0 device.

Something else that I found is that I receive an error if I try to upload the configuration from LimeSuiteGUI to the device (using the GUI --> Chip button). It only fails with the new (20.10) version.
On older versions it works.

Any help is appreciated.

Thanks,

Werni

@Zack, could you take a look and advise, please.

Hi @Werni,

It is quite strange, while LimeSDR-Mini gateware update does nothing to USB microcontroller configuration. Try to plug in LimeSDR-Mini to USB port directly (i.e. no cable). If this doesn’t help then then maybe physical damage of USB connector.

Regarding upload, I see 1.26 gateware version which is rather old in your picture. Try the latest one.

Hi @Zack,

Thanks for your time.

I don’t usualy use any cable to connect my LimeSDR Mini, it is plugged in directly.

I did upgrade the gateware version to 1.30, but after seeing the errors (connecting as USB 2.0, LimeQuickTests fails) I downgraded to see if there are any differences.

Why do you think is LimeQuickTest failing with the new gateware/LimeSuite software and not with the older one? how can i test if the USB is damaged (I don’t see how it could be damaged andI would like to know for sure)?

Thanks,

Werni

i found the problem: the USB connector got loose (from the LimeSDR Mini main board) and one of the connector pads on the Lime board also got detached.

I disoldered the USB connector and could put another if there weren’t for the detached pads.
Is there a way to repair it?

Thanks,

Werni