CS-LIME-26 (LimeSDR Mini 2.0) is defective

Hello Team,

One of our customers purchased CS-LIME-26 and claim part is defective. They provided following information,


One of the parts—in this case, the “LimeSDR Mini 2.0”—is “defective,” though the focus here should be on limited functionality rather than a hardware defect. There was no damage to the part or the packaging that could have caused the defect.

After a driver update (USB reset following the LimeSDR update with the LimeSDR connected), the LimeSDR Mini 2.0 is no longer recognized. I noticed this because the RX and TX LEDs were flashing red intermittently along with the standby LED. A subsequent test with the LimeSuite software revealed that the USB driver was loaded, the device was recognized as “unknown” with FW 6 and a 40 MHz clock, but no further functions were available.

However, the LimeSDR is recognized by SDR-Cube. Since SDR-Cube uses its own FX3 communication protocol, the device (bootloader, FPGA, etc.) isn’t classically defective; rather, an incorrect firmware version was likely installed during the automatic update, which no longer allows operation with my applications.

However, while searching for the latest firmware downloads, I discovered that they are not available. Furthermore, I learned that this appears to be a common problem when updating the LimeSDR Mini 2.0, usually resulting in the bootloader being corrupted.

There is no visible external damage. If you need a hard copy or a photo of the conditions described above, I will provide it to you. For safety reasons—to prevent further damage to the device—I have disconnected it and have not put it back into operation to date; however, I would need to do so.

I hope the information provided has given you an understanding of the item’s defect, and I hope that you or your team will be able to assist me further.

-------------------------

Could you please review the information provided by the customer and confirm whether the part appears to be defective? Additionally, are there any troubleshooting steps or recommendations that could help the customer resolve the issue?

Best,

Usman

Hi,

this looks like an unsuccessful/incompatible update resulted in corrupted FPGA gateware, rather than a hardware defect.

-At this point, recovery will most likely require reprogramming the FPGA through JTAG cable.

-Please provide the exact software, version, and update procedure that was used.

-Was it working before update?

-Can you see any LED activity when board is connected to USB3.0 port?

-Is board detected with lsusb on linux or Device manager on Window?

Regards,
Vytautas