# LimeSDR Mini 2.0 passes FTDI configuration but fails LimeQuickTest

**URL:** <https://discourse.myriadrf.org/t/limesdr-mini-2-0-passes-ftdi-configuration-but-fails-limequicktest/8190>\
**Category:** LimeSDR\
**Created:** [30 January 2024 17:45 UTC](https://discourse.myriadrf.org/t/limesdr-mini-2-0-passes-ftdi-configuration-but-fails-limequicktest/8190 "2024-01-30T17:45:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmossman](https://avatars.discourse-cdn.com/v4/letter/d/4da419/32.png) [@dmossman](https://discourse.myriadrf.org/u/dmossman)\
**Post date:** [30 January 2024 17:45 UTC](https://discourse.myriadrf.org/t/limesdr-mini-2-0-passes-ftdi-configuration-but-fails-limequicktest/8190/1 "2024-01-30T17:45:24Z")

</div>

LimeSDR newcomer here. I have a LimeSDR Mini 2.0 purchased from Crowdsupply. I am attempting to verify functionality of the device using LimeQuickTest.

The following steps on Windows 10 have been tested and verified working:

- LimeSDR connected to USB 3.0 port.
- FTDI FT601 USB 3.0 Bridge Device driver installed for the LimeSDR.
- FT60X Chip Configuration Programmer successfully reads configuration and matches the expected values in the documentation.
- LimeQuickTest\_20201029\_480bfea installed
- LED1 flashes red once when initially plugged into USB port, then blinks green.

The Device string on the bottom left corner of LimeQuickTest indicates it recognizes the LimeSDR as the serial number matches the configuration read by the FTDI tool. LimeQuickTest returns the following messages after running Start Test:

Failed to list USB Devices  
Failed to open device  
Failed to open. Device is busy.  
Error: Unable to connect  
Failed to connect

Any ideas for what could cause this issue and potential remedies?

---

<div class="post-metadata">

**Author:** ![ricardas](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/ricardas/32/86_2.png) [@ricardas](https://discourse.myriadrf.org/u/ricardas)\
**Post date:** [30 January 2024 19:29 UTC](https://discourse.myriadrf.org/t/limesdr-mini-2-0-passes-ftdi-configuration-but-fails-limequicktest/8190/2 "2024-01-30T19:29:11Z")

</div>

> [@dmossman](#):
>
> LimeQuickTest\_20201029

If that is the release date of the LimeQuickTest, then it didn’t had LimeSDR Mini v2.0 support. Detection works, as it’s identical among boards, but after that point the software don’t know what to do with it.

---

<div class="post-metadata">

**Author:** ![dmossman](https://avatars.discourse-cdn.com/v4/letter/d/4da419/32.png) [@dmossman](https://discourse.myriadrf.org/u/dmossman)\
**Post date:** [30 January 2024 19:35 UTC](https://discourse.myriadrf.org/t/limesdr-mini-2-0-passes-ftdi-configuration-but-fails-limequicktest/8190/3 "2024-01-30T19:35:31Z")

</div>

Thanks for the reply. That is the latest build available from the Myriad downloads site: [limesuite - downloads.myriadrf.org \> builds \> limesuite](https://downloads.myriadrf.org/builds/limesuite/)

Is there a newer version that supports the LimeSDR Mini v2.0? If not, what is the recommended procedure for checking device funtionality?

---

<div class="post-metadata">

**Author:** ![andrewback](https://avatars.discourse-cdn.com/v4/letter/a/22d042/32.png) [@andrewback](https://discourse.myriadrf.org/u/andrewback)\
**Post date:** [1 February 2024 13:45 UTC](https://discourse.myriadrf.org/t/limesdr-mini-2-0-passes-ftdi-configuration-but-fails-limequicktest/8190/5 "2024-02-01T13:45:22Z")

</div>

> [@dmossman](#):
>
> Is there a newer version that supports the LimeSDR Mini v2.0? If not, what is the recommended procedure for checking device funtionality?

It looks like a new Windows build needs uploading. More generally though I would recommend using Linux.