LimeSDR report module as FX3 instead of STREAM


#1

When running the command SoapySDRUtil --find, my LimeSDR running the latest firmware report as:
driver = lime
index = 0
label = LimeSDR-USB [USB 2.0] 90778JUFC0B
media = USB 2.0
module = FX3
name = LimeSDR-USB
serial = 00090778JUFC0B
Note the line Module = FX3 instead of Module = STREAM as other LimeSDR reports in this forum.
Is this normal?


#2

Can you try it in a USB 3.0 port.


#3

I did tried it with USB 3, result is still the same.
driver = lime
index = 0
label = LimeSDR-USB [USB 3.0] 90778JUFC0B
media = USB 3.0
module = FX3
name = LimeSDR-USB
serial = 90778JUFC0B

The serial number is not the same ofcourse.


#4

OK, just updated a board, checked and I get the same — so I think all is good.

STREAM is an FPGA board that together with the LMS7002M EVB was first supported by Lime Suite, and is what the LimeSDR is based on, hence the name stuck. The name change likely makes sense.


#5

Thank you @andrewback, i thought something was wrong with my device since i was trying to run the combination of osmo-nitb, osmo-bts-tx and osmmo-tx; but osmo-tx complain with this error:
UHD Error: SetPllFrequency: error configuring phase
then after it run for about a 30seconds to a minite, osmo-trx shows this error :
UHDDevice.cpp:1021:writeSamples: UHD: Device send timed out
continously while osmo-bts-tx crashes immediately with:
Shutdown timer expired
Each and everytime i try, same results occurs.

Also, in windows 10 device, using the sample Pothos FM demo, the audio plays but the audio breaks and resume every seconds as the logs are running. Thought it was samplerate, i lowered it to 1M but still the same, switched port from USB2.0 to USB3.0; still the same.

Hence i think somehow the software update version 2.14 and 2.15 which are reporting the module as FX3 might might have broken something.

Can you check this too? @andrewback


#6

I don’t have the Osmocom stack set up right now, so can’t easily test. In general the best place for reporting issues with this is the OpenBSC mailing list.

@IgnasJ, @Zack, are you aware of any recent changes which might explain the problems described?


#7

Thank you much for the help.
I just got the LimeSDR USB 4 days ago and am exited to test everything.


#8

I have the same problem. I do an occasional (5-10 x / week) pull from osmocom.git and other sources of dependencies to rebuild my OsmoTRX stack, running on my Odroid XU4. My LimeSDR 1.4 board and the Osmocom stack was performing well until about ten days ago, when I began running into this message after less than a minute running,

UHD: Device send timed out

after which point I have to kill the osmo-trx process.

This message is emitted by osmo-trx.git/Transceiver52M/UHDDevice.cpp, in the UHD driver code @ line 1067.

Transceiver52M/UHDDevice.cpp-1062-      thread_enable_cancel(false);
Transceiver52M/UHDDevice.cpp-1063-      size_t num_smpls = tx_stream->send(bufs, len, metadata);
Transceiver52M/UHDDevice.cpp-1064-      thread_enable_cancel(true);
Transceiver52M/UHDDevice.cpp-1065-
Transceiver52M/UHDDevice.cpp-1066-      if (num_smpls != (unsigned) len) {
Transceiver52M/UHDDevice.cpp:1067:              LOG(ALERT) << "UHD: Device send timed out";
Transceiver52M/UHDDevice.cpp-1068-      }
Transceiver52M/UHDDevice.cpp-1069-
Transceiver52M/UHDDevice.cpp-1070-      return num_smpls;
Transceiver52M/UHDDevice.cpp-1071-}
Transceiver52M/UHDDevice.cpp-1072-

When I instrumented line 1067 to return both num_smpls and len,

LOG(ALERT) << "UHD: Device send timed out" << num_smpls << "/" << len;

it turns out that tx_stream->send(bufs, len, metadata) was returning with less than len bytes sent.

This is the console log from my last run, a couple of hours ago.

linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.003.HEAD-0-gef157678

Sat Apr  7 12:24:52 2018 DLGLOBAL <0001> telnet_interface.c:104 telnet at 127.0.0.1 4237
Sat Apr  7 12:24:52 2018 DLCTRL <0008> control_if.c:863 CTRL at 127.0.0.1 4236
Config Settings
   Log Level............... 0
   Device args.............
   TRX Base Port........... 5700
   TRX Address............. 127.0.0.1
   GSM Core Address.........127.0.0.1
   Channels................ 1
   Tx Samples-per-Symbol... 4
   Rx Samples-per-Symbol... 4
   EDGE support............ 1
   Reference............... 0
   C0 Filler Table......... 3
   Multi-Carrier........... 0
   Tuning offset........... 0
   RSSI to dBm offset...... 0
   Swap channels........... 0
   Tx Antennas............. 'BAND1'
   Rx Antennas............. 'LNAW'

Sat Apr  7 12:24:53 2018 DMAIN <0000> Logger.cpp:53 [tid=3070091264] Using discovered UHD device addr=1d50:6108,driver=lime,label=LimeSDR-USB [USB 3.0] 9070105C62B09,media=USB 3.0,module=FX3,name=LimeSDR-USB,serial=0009070105C62B09,type=soapy
-- Make connection: 'LimeSDR-USB [USB 3.0] 9070105C62B09'
-- Reference clock 30.72 MHz
-- Device name: LimeSDR-USB
-- Reference: 3.072e+07 MHz
-- LMS7002M calibration values caching Disable
Sat Apr  7 12:24:54 2018 DMAIN <0000> Logger.cpp:53 [tid=3070091264] Antennas configured successfully
Sat Apr  7 12:24:54 2018 DMAIN <0000> Logger.cpp:53 [tid=3070091264] Rates configured for LimeSDR 4 SPS
-- Filter calibrated. Filter order-4th, filter bandwidth set to 5 MHz.Real pole 1st order filter set to 2.5 MHz. Preemphasis filter not active
-- TX LPF configured
-- RX LPF configured
Sat Apr  7 12:24:55 2018 DMAIN <0000> Logger.cpp:53 [tid=3070091264] Supported Tx gain range [-12; 64]
Sat Apr  7 12:24:55 2018 DMAIN <0000> Logger.cpp:53 [tid=3070091264] Supported Rx gain range [-12; 61]
Sat Apr  7 12:24:55 2018 DMAIN <0000> Logger.cpp:53 [tid=3070091264] Default setting Tx gain for channel 0 to 26
Sat Apr  7 12:24:55 2018 DMAIN <0000> Logger.cpp:53 [tid=3070091264] Default setting Rx gain for channel 0 to 24.5
Sat Apr  7 12:24:55 2018 DMAIN <0000> Logger.cpp:53 [tid=3070091264]
Single USRP:
  Device: FX3
  Mboard 0: LimeSDR-USB
  RX Channel: 0
    RX DSP: 0
    RX Dboard: 0
    RX Subdev: SoapyRF
  RX Channel: 1
    RX DSP: 1
    RX Dboard: 1
    RX Subdev: SoapyRF
  TX Channel: 0
    TX DSP: 0
    TX Dboard: 0
    TX Subdev: SoapyRF
  TX Channel: 1
    TX DSP: 1
    TX Dboard: 1
    TX Subdev: SoapyRF
-- Transceiver active with 1 channel(s)
Sat Apr  7 12:24:56 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is POWEROFF
Sat Apr  7 12:24:56 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is RXTUNE 892400
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528]
Tune Result:
    Target RF  Freq: 892.400000 (MHz)
    Actual RF  Freq: 892.399995 (MHz)
    Target DSP Freq: -0.000005 (MHz)
    Actual DSP Freq: -0.000005 (MHz)

Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is TXTUNE 937400
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528]
Tune Result:
    Target RF  Freq: 937.400000 (MHz)
    Actual RF  Freq: 937.399995 (MHz)
    Target DSP Freq: 0.000005 (MHz)
    Actual DSP Freq: 0.000005 (MHz)

Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is SETTSC 7
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] Changing TSC from 0 to 7
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is POWERON
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] Starting the transceiver
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] Starting radio device
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] Starting USRP...
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=2858140512] Unable to set the thread priority. Performance may be negatively affected.
Please see the general application notes in the manual for instructions.
EnvironmentError: OSError: error in pthread_setschedparam
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] Tx calibration finished
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] Rx calibration finished
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] Initial timestamp 128520
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] The current time is 0.119575 seconds
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] Radio started
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3007415136] Unable to set the thread priority. Performance may be negatively affected.
Please see the general application notes in the manual for instructions.
EnvironmentError: OSError: error in pthread_setschedparam
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] Unable to set the thread priority. Performance may be negatively affected.
Please see the general application notes in the manual for instructions.
EnvironmentError: OSError: error in pthread_setschedparam
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Unable to set the thread priority. Performance may be negatively affected.
Please see the general application notes in the manual for instructions.
EnvironmentError: OSError: error in pthread_setschedparam
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3004466016] Unable to set the thread priority. Performance may be negatively affected.
Please see the general application notes in the manual for instructions.
EnvironmentError: OSError: error in pthread_setschedparam
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is SETPOWER 0
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1468456
Sat Apr  7 12:24:57 2018 DMAIN <0000> Logger.cpp:53 [tid=2977952608] L
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=2850026336] popping from TX, samples popped 0/1020
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=2858140512] Unknown error -1436828532 at 0.121458 sec.
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] Set TX gain to 64.0412dB (asked for 64dB)
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is SETSLOT 0 5
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is SETSLOT 1 1
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is SETSLOT 1 13
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is SETSLOT 2 1
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is SETSLOT 3 1
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is SETSLOT 4 13
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is SETSLOT 5 13
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is SETSLOT 6 13
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is SETSLOT 7 13
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=2977952608] L
Sat Apr  7 12:24:58 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1468672
Sat Apr  7 12:24:59 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1468889
Sat Apr  7 12:25:00 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1469106
Sat Apr  7 12:25:01 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1469323
Sat Apr  7 12:25:02 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1469540
Sat Apr  7 12:25:03 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1469756
Sat Apr  7 12:25:04 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1469973
Sat Apr  7 12:25:05 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1470190
Sat Apr  7 12:25:05 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:05 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:05 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:06 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:06 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:06 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:06 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1470407
Sat Apr  7 12:25:06 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:06 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:07 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:07 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:07 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:07 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:07 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:07 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:07 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:07 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:07 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1470624
Sat Apr  7 12:25:07 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:07 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:08 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:08 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:08 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:08 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:08 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1470840
Sat Apr  7 12:25:08 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:08 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:08 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:09 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:09 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:09 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:09 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1471057
Sat Apr  7 12:25:09 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:09 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:09 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:10 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
[10 more of the same...] Sat Apr  7 12:25:10 2018 DMAIN <0000> Logger.cpp:53 [tid=3007349600] Clipping detected on received RACH or Normal Burst
Sat Apr  7 12:25:10 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1471274
Sat Apr  7 12:25:11 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1471491
......
Sat Apr  7 12:25:33 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1476261
Sat Apr  7 12:25:34 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1476478
Sat Apr  7 12:25:35 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is NOHANDOVER 0 0
Sat Apr  7 12:25:35 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1476694
Sat Apr  7 12:25:36 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1476911
Sat Apr  7 12:25:36 2018 DMAIN <0000> Logger.cpp:53 [tid=2977952608] L
Sat Apr  7 12:25:37 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1477164
Sat Apr  7 12:25:38 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1477382
Sat Apr  7 12:25:39 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1477599
Sat Apr  7 12:25:40 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is NOHANDOVER 0 0
Sat Apr  7 12:25:40 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1477816
Sat Apr  7 12:25:41 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1478033
Sat Apr  7 12:25:42 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1478250
Sat Apr  7 12:25:43 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1478467
Sat Apr  7 12:25:44 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1478684
Sat Apr  7 12:25:45 2018 DMAIN <0000> Logger.cpp:53 [tid=3069682528] command is NOHANDOVER 0 0
Sat Apr  7 12:25:45 2018 DMAIN <0000> Logger.cpp:53 [tid=3007382368] ClockInterface: sending IND CLOCK 1478901
Sat Apr  7 12:25:46 2018 DMAIN <0000> Logger.cpp:53 [tid=3007415136] UHD: Device send timed out
Sat Apr  7 12:25:46 2018 DMAIN <0000> Logger.cpp:53 [tid=3007415136] UHD: Device send timed out
.......
Sat Apr  7 12:25:55 2018 DMAIN <0000> Logger.cpp:53 [tid=3007415136] UHD: Device send timed out
Sat Apr  7 12:25:56 2018 DMAIN <0000> Logger.cpp:53 [tid=3007415136] UHD: Device send timed out
Sat Apr  7 12:25:56 2018 DMAIN <0000> Logger.cpp:53 [tid=3007415136] UHD: Device send timed out
Sat Apr  7 12:25:56 2018 DMAIN <0000> Logger.cpp:53 [tid=3007415136] UHD: Device send timed out
^Csignal 2 received
shutting down
Shutting down transceiver...
Sat Apr  7 12:25:56 2018 DMAIN <0000> Logger.cpp:53 [tid=3070091264] Stopping the transceiver

The timeouts occur using both version 2.15 and 2.16 of the LimeSDR firmware, loaded via LimeUtil --update.

Before running into this problem, I was able to run the board for 30 minutes to two hours at a stretch, powered via the same USB 3.0 powered hub. All heat-emitting components are suitably heatsinked as well.

Any ideas where I should look next?


#9

I also have same issue. If I downgrade to 17.03 for example, then no such issue here.

Have you fixed this issue?

BTW, if the module = FX3, I have to change the mapping string from “STREAM” to “FX3” in UHDDevice.cpp (681). Else can’t start osmo-trx. Can you please list the version of modules you installed?

Thanks.


#10

My advice would be that, if you have a working Osmocom stack stick with it — and don’t go chasing the latest commits. That is, unless you’re prepared to unpick and attempt to fix any breakages yourself.

There is work under way to greatly simplify running the Osmocom stack with LimeSDR hardware, and in the process make it a lot more robust. However, until this work is completed I would strongly suggest sticking with whatever versions of software you have previously found to work.


#11

In my opinion i still say that, the problems comes from the Firmware update in the LIMESDR. Especially versions from 2.14.
I tried to compile previous versions of the osmoscom stack, but still the same problem occurs.
Also the name change from STREAM to FX3 has somehow affected the UHD drivers which makes the Limesdr misbehave.


#12

UHD support comes via SoapySDR.

@joshblum, do you know if the STREAM -> FX3 change could have caused any problems in SoapySDR or beyond?


#13

Hi, @sglee - I concur. Rebuilding LimeSuite from tag v17.12.0 (which permits me to load firmware 2.12) permits me to use my LimeSDR as before: No more “Device send timed out” error (nor “UHD Error: SetPllFrequency: error configuring phase”), and osmo-trx functions as before. Am able to once more get my two old phones sending SMS to and ringing each other up. Very cool.

[INFO] Make connection: 'LimeSDR-USB [USB 3.0] 9070105C62B09'
[INFO] Reference clock 30.720 MHz
[INFO] Device name: LimeSDR-USB
[INFO] Reference: 30.72 MHz
[INFO] Init LMS7002M(0)
[INFO] Ver=7, Rev=1, Mask=1
[INFO] LMS7002M calibration values caching Disable

----------------------------------------------------
-- Device identification
----------------------------------------------------
  driver=STREAM
  hardware=LimeSDR-USB
  boardSerialNumber=0x9070105c62b09
  firmwareVersion=4
  hardwareVersion=4
  protocolVersion=1

Other components of the OsmoBSC stack remain the same. In particular, SoapyUHD and SoapySDR are built from the master branch.

I’m intrigued by the “device send timed out” error. After the LimeSDR mini was released, there were some bits of code refactored in LimeSuite. One of the places I’ll take a peek at later is where handling of USB transfers differ, between FT601 and Cypress FX3.

I’ll continue to track LimeSuite HEAD on my test platform; will probably buy a second LimeSDR for that test rig, and keep this Lime (flashed with 2.12) to continue to play with the osmo stack.


#14

Not really an issue in general, but I think the limesuite fork of osmotrx was using the key/value pair module=STREAM in a few places to differentiate its specific limesdr settings.


#15

For all who have trouble making Osmocom stack to work with LimeSDR, the trick lies on its firmware.
Simply clone the LimeSuite git, checkout to tags/v17.12.0, build it, and downgrade your LimeSDR to firmware v17.12 using the LimeUtil --upgrade utility.
Fire up the Osmocom stack(you can use even the latest git version), ignore the Firmware upgrade alert, and right there all will work fine.
Maybe future firmware will sort out this isssue; but till then, this works okay.


#16

Yeah, right now the LimeSuite 17.12 Firmware is working perfectly for me. Eventually, I’ll upgrade with caution, but for now my Osmocom stack is working better than ever before!