Problem running Quicktest on LimeSDR USB

PaulC · 12 February 2019 10:39

I’ve recently taken delivery of a LimeSDR USB board and am trying to get it working, using the directions in Quicktest. I am running on Windows 7 on a laptop with USB2.0 ports.

So far I have installed the device driver and the board successfully enumerates and I can see it in Device Manager under the USB devices as “Myriad-RF LimeSDR-USB”. I have installed LimeSuiteGUI by installing Pothos SDR environment (vc12-x64) and can connect to the LimeSDR board using the Options | Connection settings tab in the GUI, where it comes up as
“LimeSDR-USB [USB 2.0] 9072C02871918”. From connecting I can get the temperature of the board by clicking the “Read Temp” button. So everything seems to be working there.

I have downloaded the “self_test.ini” and “example.ini” files to be able to run the QuickTest, together with the waveform files (onetone, wcdma, LTE_DL_TM31_20MHZ in lms7suite_wfm directory - is there anywhere special this directory should live? Nothing mentioned in the Quicktest doc)

Following the directions in Quicktest I clicked the Open button in LimeSuiteGUI to open a file and selected “self_test.ini” When I hit ok, a dialog box comes up and tells me that it “Failed to load file” and in the log window I get
[10:24:59] ERROR: Write(64 bytes) failed
When I click ok on the dialog box the GUI hangs for several minutes and then writes out another load of the same error message in the log window. I have tried this several times and noticed that one of the two normally green LEDs flashes red during the time the error messages are printed in the log, once for each error message
I was surprised that there is any comms between the PC and board at this stage - I thought that I would have to press the GUI->Chip button before the settings read from the file would attempt to be transferred. Note that I haven’t got that far - the failure to load seems to screw up comms between the PC and LimeSDR to the extent that if I click Read Temp button I get back a value of 0, not around 50C as previously. The only way to restore comms is to unplug the LimeSDR USB and reinsert, then reconnect the GUI

Any idea what I am doing wrong, or have I missed downloading something? Could there be a problem with the format of the “self_test.ini” file? I have updated the gateway and firmware in the LimeSDR to match the versions expected by LimeSuiteGUI
Any help gratefully received
Thanks

andrewback · 14 February 2019 08:43

@Zack could you assist, please.

Zack · 14 February 2019 08:46

Hi @PaulC,

Test you board using LimeQuickTest and share the log file please.

PaulC · 14 February 2019 09:20

Hi @Zack
Here are the results of the LimeQuickTest. The test gets into the Loopback test and then just hangs
Regards
Paul

[ TESTING STARTED ]
->Start time: Thu Feb 14 09:14:24 2019

Gateware version mismatch!
Expected gateware version 2, revision 17
But found version 2, revision 19
Follow the FW and FPGA upgrade instructions:
http://wiki.myriadrf.org/Lime_Suite#Flashing_images
Or run update on the command line: LimeUtil --update

->Device: LimeSDR-USB, media=USB 2.0, module=FX3, serial=0009072C02871918, index=0
Warning: USB3 not available
Serial Number: 0009072C02871918

[ Clock Network Test ]
->FX3 GPIF clock test
Test results: 18724; 22480; 26236 - PASSED
->Si5351C test
CLK0: 17554 / 17554 - PASSED
CLK1: 17554 / 17554 - PASSED
CLK2: 17554 / 17554 - PASSED
CLK3: 17554 / 17554 - PASSED
CLK4: 17554 / 17554 - PASSED
CLK5: 17554 / 17554 - PASSED
CLK6: 17554 / 17554 - PASSED
->ADF4002 Test
Result: 10 - PASSED
->VCTCXO test
Results : 5112905 (min); 5113045 (max) - PASSED
->Clock Network Test PASSED

[ FPGA EEPROM Test ]
->Read EEPROM
->Read data: 12 07 19 12 07 19 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
Write(64 bytes) failed
SetPllFrequency: configure FPGA PLL, failed to write registers
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed
Write(64 bytes) failed

PaulC · 14 February 2019 09:25

Hi @Zack
Sorry I ran the test again to see if there would be a difference - it completed this time, with the following log file output

[ TESTING STARTED ]
->Start time: Thu Feb 14 09:22:02 2019

Gateware version mismatch!
Expected gateware version 2, revision 17
But found version 2, revision 19
Follow the FW and FPGA upgrade instructions:
http://wiki.myriadrf.org/Lime_Suite#Flashing_images
Or run update on the command line: LimeUtil --update

->Device: LimeSDR-USB, media=USB 2.0, module=FX3, serial=0009072C02871918, index=0
Warning: USB3 not available
Serial Number: 0009072C02871918

[ Clock Network Test ]
->FX3 GPIF clock test
Test results: 22884; 26640; 30396 - PASSED
->Si5351C test
CLK0: 17554 / 17554 - PASSED
CLK1: 17554 / 17554 - PASSED
CLK2: 17554 / 17554 - PASSED
CLK3: 17554 / 17554 - PASSED
CLK4: 17554 / 17554 - PASSED
CLK5: 17554 / 17554 - PASSED
CLK6: 17554 / 17554 - PASSED
->ADF4002 Test
Result: 10 - PASSED
->VCTCXO test
Results : 5112906 (min); 5113047 (max) - PASSED
->Clock Network Test PASSED

[ FPGA EEPROM Test ]
->Read EEPROM
->Read data: 12 07 19 12 07 19 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
Read(64 bytes) failed
SetPllFrequency: configure FPGA PLL, failed to write registers
->Run Tests (TX_2-> LNA_L):
SetFrequencySXT(805 MHz) - cannot deliver frequency
->Run Tests (TX_1 -> LNA_W):
SetFrequencySXT(1805 MHz) - cannot deliver frequency
->Run Tests (TX_2-> LNA_H):
SetFrequencySXT(2505 MHz) - cannot deliver frequency
->RF Loopback Test FAILED

=> Board tests FAILED <=

Elapsed time: 3.87 seconds

Zack · 14 February 2019 09:52

Could you test it via USB3?

PaulC · 21 February 2019 09:58

Hi @Zack
Sorry for the slow reply - I’ve been trying to source a PC with USB3 and cabling so I can run the test as you suggested.

I have connected the board to the USB3 port with a 1m extender cable (USB3 A plug to USB3 A socket)

The first time I tried it, LimeQuickTest app ran ok, but since then I haven’t managed to get it to work; it always fails in the RF Loopback Test.

I have tried it multiple times, sometimes back-to-back with a previous run and other times depowering the LimeSDR-USB board between runs, but it always fails in the TX_1->LNA_W and TX_2->LNA_H tests in the Loopback

Enclosing a sample log file of one of the failing runs

[ TESTING STARTED ]
->Start time: Thu Feb 21 09:48:16 2019

Gateware version mismatch!
Expected gateware version 2, revision 17
But found version 2, revision 19
Follow the FW and FPGA upgrade instructions:
http://wiki.myriadrf.org/Lime_Suite#Flashing_images
Or run update on the command line: LimeUtil --update

->Device: LimeSDR-USB, media=USB 3.0, module=FX3, serial=0009072C02871918, index=0
Serial Number: 0009072C02871918

[ Clock Network Test ]
->FX3 GPIF clock test
Test results: 37842; 41598; 45354 - PASSED
->Si5351C test
CLK0: 17554 / 17554 - PASSED
CLK1: 17554 / 17554 - PASSED
CLK2: 17554 / 17554 - PASSED
CLK3: 17554 / 17554 - PASSED
CLK4: 17554 / 17554 - PASSED
CLK5: 17554 / 17554 - PASSED
CLK6: 17554 / 17554 - PASSED
->ADF4002 Test
Result: 10 - PASSED
->VCTCXO test
Results : 5112904 (min); 5113045 (max) - PASSED
->Clock Network Test PASSED

[ FPGA EEPROM Test ]
->Read EEPROM
->Read data: 12 07 19 12 07 19 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_L):
CH0 (SXR=800.0MHz, SXT=805.0MHz): Result:(-16.3 dBFS, 5.00 MHz) - PASSED
CH1 (SXR=800.0MHz, SXT=805.0MHz): Result:(-18.4 dBFS, 5.00 MHz) - PASSED
->Run Tests (TX_1 -> LNA_W):
CH0 (SXR=1800.0MHz, SXT=1805.0MHz): Result:(-21.8 dBFS, 5.00 MHz) - FAILED
CH1 (SXR=1800.0MHz, SXT=1805.0MHz): Result:(-21.2 dBFS, 5.00 MHz) - FAILED
->Run Tests (TX_2-> LNA_H):
CH0 (SXR=2500.0MHz, SXT=2505.0MHz): Result:(-69.4 dBFS, 19.04 MHz) - FAILED
CH1 (SXR=2500.0MHz, SXT=2505.0MHz): Result:(-68.3 dBFS, -24.24 MHz) - FAILED
->RF Loopback Test FAILED

=> Board tests FAILED <=

Elapsed time: 2.17 seconds

liborw · 17 January 2020 16:59

Same problem here, have you solved it?