LimeSDR-USB gateware version is not recognizeable (temperature related)

Just received my LimeSDR-USB from Crowd Supply.
Unfortunately, the board doesn’t work, every time I tried to connect to the board through LimeSuit on Windows, it gives me “Read (64 bytes) error” and GW version 0.0, at the same time I can see the FX3 LED blinking red every 1 second or so.
I’ve tried both USB3.0 and 2.0 on 3 different PCs, and reprogramed the board multiple times but get no luck.
Zack mentioned the power supply issue in another thread, but I don’t think it’s the case since I was using a bench supply to power the board, the current draw is around 450mA @ 9V.

Has anyone encountered this problem before? Or is this just a defective HW?

I only have one suggestion:
Did you press the SW1 - FX3 reset push-button?
https://wiki.myriadrf.org/LimeSDR-USB_User_Guide

Hi yindra,

Yeah, I tried but didn’t help.
I can see the device called “Myriad-RF LimeSDR-USB” shows up normally, the link between PC and FX3 should be fine. Also, FPGA1 LED is blinking red so I believe the GW is loaded from EEPROM as well.

Maybe something wrong between the FX3 and FPGA?

If you are able to reprogram the LimeSDR-USB, I recommend reverting back to LimeSuite 18.04 (around 4 June 2018), because that version plays nice with USB 2.0.

I have read some people had issues with Windows 10.

I was able to successfully install the Cypress drivers for FX3 on Windows 7 and read/write to the LimeSDR-USB. Also, I was able to read/write to the LimeSDR-USB in Ubuntu 16.04 LTS.

I found 18.04 here, released on Apr 6 though:

I will try it out and update the result later, thanks

PS:Just realized it’s in source code, will go find executable somewhere else.

Just tried LimeSuite 18.04 (LimeSuiteGUI_20180406_d6bc28.exe from this page index - powered by h5ai v0.29.1 (https://larsjung.de/h5ai/))
It can program the board successfully, this is expected, but I still get the same error when I connect to the board:

[13:43:43] WARNING: Gateware version mismatch!
Expected gateware version 2, revision 16
But found version 0, revision 0
Follow the FW and FPGA upgrade instructions:
Lime Suite - Myriad-RF Wiki
Or run update on the command line: LimeUtil --update

[13:43:43] ERROR: Read(64 bytes) failed
[13:43:43] ERROR: Write(64 bytes) failed
[13:43:43] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] ERROR: Write(64 bytes) failed
[13:44:09] INFO: Connected Control port: LimeSDR-USB FW:4 HW:4 Protocol:1 GW:0.0 Ref Clk: -0.00 MHz

I don’t understand why you say that the board was programmed successfully, because that print out indicates that you have not run LimeUtil --update with LimeSuite 18.04.

I followed the instruction to program the board in LimeSuite (under Windows10):

Modules -> Programming -> select Auto -> click Program.
The popup windows said it was successful.

Do I have to do it under Linux with LimeUtil?

I’m concerned because LimeSuiteGUI is not reading the gateway version or revision

Please reply with the INFO messages printed in LimeSuiteGUI when you connect to LimeSDR-USB.

[14:10:26] INFO: Connected Control port: LimeSDR-USB FW:4 HW:4 Protocol:1 GW:0.0 Ref Clk: -0.00 MHz

As I mentioned in the title, the GW version is not recognizable (always 0.0 even I flashed the EEPROM multiply times, both automatically and manually), I got the same issue on a Windows7 machine so I don’t believe it’s OS related.

Thank you for your help anyway, I will request an exchange and see if there is any difference.

With the Lime connected, go to CMD (Command Line) and copy/paste the command surrounded by asterisks.
This should update the firmware/gateware & you should be off to the races.

Ed

Hi AA7QQ,

Thank you for your reply, but I don’t think it’s the root cause.

The board doesn’t work no matter I program the FX3 and FPGA under command line or GUI.

This thread gave me an idea about the issue:

I just tried to warm up the FX3 chip by using a rework station, and the board starts to work! It fails again after cool down though, but now I can confirm the issue is temperature related.

@andrewback Might be a soldering quality issue?

Sounds like it. Asked Crowd Supply to arrange an RMA.

hmmm my lime makes the same problems … always shows gateware 0 (even after a longer warm up time) …
i tried with two different pc (win7 and win10) on usb 2 and usb3
last thing i could try is external power source (12v)
. should i also try to carefully warm it up a bit and try if that helps?!? … if yes … then maybe i also have a device with a bad solder spot?!? … should i ask for an rma also?!?
greetz dg9bfc sigi

If external power doesn’t work for you, highly likely it’s a faulty HW. Crowdsupply send me a new one and that works out of the box.

Finally I can put my things together.

Andrew, I appear to be having the same heat related issue. Above 60F it works fine, below I see all the R/W failures. Everything has been fine up until the last couple of weeks. Has there been any solution proposed, and if not is an RMA option available? I use the Lime in a Radio Astronomy application, so temp swings are hard to avoid.

If this behaviour is consistent I would suggest an RMA.