# LimeSDR Mini, Technical issue. Chip reset failed. Read (64 bytes) failed Write (64 bytes) failed

**URL:** <https://discourse.myriadrf.org/t/limesdr-mini-technical-issue-chip-reset-failed-read-64-bytes-failed-write-64-bytes-failed/5865>\
**Category:** LimeSDR\
**Created:** [10 March 2020 09:50 UTC](https://discourse.myriadrf.org/t/limesdr-mini-technical-issue-chip-reset-failed-read-64-bytes-failed-write-64-bytes-failed/5865 "2020-03-10T09:50:50Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Zack](https://yyz2.discourse-cdn.com/flex034/user_avatar/discourse.myriadrf.org/zack/32/89_2.png) [@Zack](https://discourse.myriadrf.org/u/Zack)\
**Post date:** [23 February 2021 09:09 UTC](https://discourse.myriadrf.org/t/limesdr-mini-technical-issue-chip-reset-failed-read-64-bytes-failed-write-64-bytes-failed/5865/7 "2021-02-23T09:09:51Z")

</div>

> [@f4gkr](#):
>
> So very probably the issue is that the FT601 has a different mode and is not recognized correctly by the API now

I can not think off how it could happen unless user performs this procedure intentionally. Your case is quite special.  
Anyway, here is FT601 configuration we use:

> [@Dead USB](https://discourse.myriadrf.org/t/dead-usb/6909/6):
>
> Hi @9H1LO, It really looks like FT601 was damaged in this case. Here is FT601 configuration we use:

---

_[View the full topic](https://discourse.myriadrf.org/t/limesdr-mini-technical-issue-chip-reset-failed-read-64-bytes-failed-write-64-bytes-failed/5865)._