LimeSDR osmo-trx no work

#21

Well, if you’re using Ubuntu 16.04 I can send you my working versions of the OsmoTRX and OsmoNITB.

#22

Yes I am using 16.04, thank you
but that is not necessary at the moment.

My project (at the moment) need only basic functionality of osmo-trx…

Need just basic “pilot/beacon” signal kind of real base station emulation to provoke
any cell phone lost in countryside, with no regular network to try to communicate.
That signal I am ready to receive performing TDOA location (multilateration)
from 2 simultaneous positions. All within SAR task (Search and Rescue) in accordance
to ICAO Annex 12 recommendations.
At the moment I am using two sets combined of one limeSDR and one SDRPlay RSP1
with some antennas, LNA and PA in combinations. Tomorrow who knows, XTRX in
stack of 8 maybe :blush:

Project is within my learning curve, non commercial… it is aviation and marine safety voluntary level.
BRG
Djani

Here ref. on that already here on forum ->

1 Like
#23

All done according to the instructions, installed a new clean system Ubuntu 16.04 i386. But it does not work. :frowning:

serg@openbts:~$ uname -a
Linux openbts 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:54:58 UTC 2017 i686 i686 i686 GNU/Linux

serg@openbts:~$ sudo dmesg
[ 2831.554475] usb 1-1: Product: LimeSDR-USB
[ 2831.554481] usb 1-1: Manufacturer: Myriad-RF
[ 2831.554486] usb 1-1: SerialNumber: 0009070105C52D10
[ 3129.557541] usb 1-1: USB disconnect, device number 7
[ 3131.224077] usb 1-1: new high-speed USB device number 8 using ehci-pci
[ 3131.358487] usb 1-1: New USB device found, idVendor=1d50, idProduct=6108
[ 3131.358495] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3131.358502] usb 1-1: Product: LimeSDR-USB
[ 3131.358507] usb 1-1: Manufacturer: Myriad-RF
[ 3131.358512] usb 1-1: SerialNumber: 0009070105C52D10

serg@openbts:~$ uhd_config_info
linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-release

serg@openbts:~$ sudo SoapySDRUtil --find
######################################################

Soapy SDR – the SDR abstraction library

######################################################

Illegal instruction (core dumped)

serg@openbts:~$ sudo uhd_find_devices
linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-release

Illegal instruction (core dumped)
serg@openbts:~$

Any ideas?

#24

Ok, cool, good luck on getting your project working!

#25

@zodiac-tiger tnx, I am far from that but still ready to learn :blush:

@skyinlife
Soapy not properly installed…
Reinstall in accordance to @martywittrock instructions
When you have CubicSDR running with Lime than all with soapy is good.
BRG
Dj

1 Like
#26

Anyway.
Made a full reinstallation of soapy, rtl-sdr works very well, LimeSDR still does not work.

root@openbts:~# SoapySDRUtil --info
######################################################
## Soapy SDR – the SDR abstraction library
######################################################

Lib Version: v0.6.1-gba9ad2d2
API Version: v0.6.0
ABI Version: v0.6
Install root: /usr/local
Search path: /usr/local/lib/SoapySDR/modules0.6
Module found: /usr/local/lib/SoapySDR/modules0.6/libLMS7Support.so
Module found: /usr/local/lib/SoapySDR/modules0.6/librtlsdrSupport.so
Module found: /usr/local/lib/SoapySDR/modules0.6/libuhdSupport.so
Loading modules... linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-release

done
Available factories...lime, null, rtlsdr, uhd,

RTL-SDR
root@openbts:~# SoapySDRUtil --find
######################################################
## Soapy SDR – the SDR abstraction library
######################################################

linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-release

Detached kernel driver
Found Rafael Micro R820T tuner
Reattached kernel driver
Found device 0
  available = Yes
  driver = rtlsdr
  label = Generic RTL2832U OEM :: 00000000001
  manufacturer = Realtek
  product = RTL2838UHIDIR
  rtl = 0
  serial = 00000000001
  tuner = Rafael Micro R820T

LimeSDR

root@openbts:~# SoapySDRUtil --find
######################################################
## Soapy SDR -- the SDR abstraction library
######################################################

linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-release

Illegal instruction (core dumped)
#27

The configuration that works for me:

install script for Ubuntu 16.04:
install.sh

configuration files:
openbsc.cfg
osmo-bts.cfg

run commands:

osmo-nitb -c openbsc.cfg -l hlr.sqlite3 -P -C

osmo-bts-trx -c osmo-bts.cfg

sudo osmo-trx -e

4 Likes
LimeSDR as a GSM Base Station
#28

running but reporting version mismatch…

After update:

TERM 1
q@q-X756UX:~$ osmo-nitb -c openbsc.cfg -l hlr.sqlite3 -P -C
<0005> abis_nm.c:2800 (bts=0,trx=0) Changing adm. state Unlocked -> Unlocked [vty]
<001e> telnet_interface.c:104 telnet at 127.0.0.1 4242
<0005> bsc_init.c:465
WARNING: You are running an ‘accept-all’ network on a BTS that is not barred. This configuration is likely to interfere with production GSM networks and should only be used in a RF shielded environment such as a faraday cage!

<0020> input/ipaccess.c:848 enabling ipaccess BSC mode on 0.0.0.0 with OML 3002 and RSL 3003 TCP ports
<0017> smpp_smsc.c:1001 SMPP at 0.0.0.0 2775
<0025> control_if.c:826 CTRL at 127.0.0.1 4249
DB: Database initialized.
DB: Database prepared.
<0020> input/ipa.c:263 accept()ed new link from 127.0.0.1 to port 3002
<0005> abis_nm.c:507 BTS0 feature ‘EGPRS’ reported via OML does not match statically set feature: 0 != 1. Please fix.
<0005> abis_nm.c:507 BTS0 feature ‘OML Alerts’ reported via OML does not match statically set feature: 1 != 0. Please fix.
<0005> abis_nm.c:573 BTS0: ARI reported sw[0/2]: sysmobts is 0.7.0.20171207
<0005> abis_nm.c:446 BTS0 reported variant: omso-bts-trx
<0005> abis_nm.c:468 BTS0 Attribute Manufacturer Dependent State is unreported
<0005> abis_nm.c:573 BTS0: ARI reported sw[0/1]: TRX_PHY_VERSION is Unknown
<0020> input/ipa.c:263 accept()ed new link from 127.0.0.1 to port 3003
<0004> bsc_init.c:311 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 514 using MCC=1 MNC=1 LAC=1 CID=0 BSIC=63
<0020> input/ipaccess.c:243 Sign link vanished, dead socket
<0020> input/ipaccess.c:71 Forcing socket shutdown with no signal link set
^Csignal 2 received
<0005> bsc_init.c:94 shutting down OML for BTS 0
q@q-X756UX:~$

TERM 2
q@q-X756UX:~$ osmo-bts-trx -c osmo-bts.cfg
((*))
|
/ \ OsmoBTS
<0017> control_if.c:826 CTRL at 127.0.0.1 4238
<0010> telnet_interface.c:104 telnet at 127.0.0.1 4241
<0012> input/ipaccess.c:886 enabling ipaccess BTS mode, OML connecting to 127.0.0.1:3002
<000b> trx_if.c:595 Open transceiver for phy0.0
<0012> input/ipa.c:129 connection done.
<0012> input/ipaccess.c:707 received ID get
<0001> oml.c:229 O&M Get Attributes [0], Manufacturer Dependent State is unsupported by TRX.
<0001> oml.c:680 Ignoring T200[0] (150 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[1] (180 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[2] (180 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[3] (1680 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[4] (520 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[5] (165 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:680 Ignoring T200[6] (1680 ms) as sent by BSC due to suspected LAPDm bug!
<0001> oml.c:1049 ADM state already was Unlocked
<0012> input/ipa.c:129 connection done.
<0012> input/ipaccess.c:707 received ID get
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<000b> trx_if.c:172 No response from transceiver for phy0.0
<0007> l1sap.c:462 Invalid condition detected: Frame difference is 37557-0 > 1!
<0001> bts.c:210 Shutting down BTS 0, Reason No clock from osmo-trx
Shutdown timer expired
q@q-X756UX:~$

TERM 3
q@q-X756UX:~$ sudo osmo-trx -e
[sudo] password for q:
linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-3-g122bfae1

opening configuration table from path :memory:
Info: SSE3 support compiled in and supported by CPU
Info: SSE4.1 support compiled in and supported by CPU
Config Settings
Log Level… NOTICE
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… Enabled
Reference… Internal
C0 Filler Table… Disabled
Multi-Carrier… Disabled
Tuning offset… 0
RSSI to dBm offset… 0
Swap channels… 0

– Make connection: ‘LimeSDR-USB [USB 3.0] 9060B00471638’
– Reference clock 30.720 MHz
– Device name: LimeSDR-USB
– Reference: 30.72 MHz
– Init LMS7002M(0)
– Ver=7, Rev=1, Mask=1
– LMS7002M calibration values caching Disable
– Transceiver active with 1 channel(s)
NOTICE 139796007827200 17:24:06.6 Transceiver.cpp:791:driveControl: Changing TSC from 0 to 7
NOTICE 139796007827200 17:24:06.6 Transceiver.cpp:244:start: Starting the transceiver
ALERT 139796007761664 17:24:07.4 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time
ALERT 139796007761664 17:24:07.4 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time
ALERT 139796007761664 17:24:07.4 UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 0.144997
ALERT 139796007761664 17:24:07.4 UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 0.144997
ALERT 139796007761664 17:24:07.4 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time
ALERT 139796007761664 17:24:07.4 UHDDevice.cpp:867:check_rx_md_err: UHD: Loss of monotonic time
ALERT 139796007761664 17:24:07.4 UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 0.144997
ALERT 139796007761664 17:24:07.4 UHDDevice.cpp:868:check_rx_md_err: Current time: 0, Previous time: 0.144997
ERR 139796007761664 17:24:07.6 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=246840 time_end=159120
ERR 139796007761664 17:24:07.6 UHDDevice.cpp:1383:write: Skipping buffer data: timestamp=246840 time_end=159120

^CReceived shutdown signalShutting down transceiver…
NOTICE 139796007499584 17:24:31.2 Transceiver.cpp:298:stop: Stopping the transceiver
NOTICE 139796007499584 17:24:31.3 Transceiver.cpp:324:stop: Transceiver stopped
q@q-X756UX:~$

*My Ctrl C termination…

** TX output 50 ohm terminated

Some Alerts, some Errors, but it seems ok… or not :blush:

#29

@Zack any recent firmware/gateware updates that could have broken support for applications such as OsmoTRX?

#30

Hey, thanks for this. I created a fresh install of Ubuntu 16.04 in VMWare fusion and now OsmoTRX is communicating with OsmoNITB. Unfortunately, I’m also getting the errors reported below, but I’m on the right track now.

EDIT: Actually, despite the errors and warnings it appears to be working! Great!!

#31

Second to that, on my side.
Cell phone can see my local G2 network,
connect
and
with *#100# able to get the number.

Later, sqliteDB checked, IMEI of my cell recorded ok

BRG
Djani

Copy of TERM 1 to 3, during the test =>

#32

@andrewback @9a4db would you please share step by step installation guide of osmoTRX+osmoBTS on Raspberry PI, i am newbie and required help, i just watched https://www.crowdsupply.com/lime-micro/limesdr-mini/updates/gsm-base-station-demo,

#33

Please use above set posted by IgnasJ
That one reporting some errors and warnings but working.
On my side I am able to connect on network,
request the cell number by typing *#100#
than SMS between each other, call goes too but sometimes
have timeout on them. Max number of 2 cell phones tested.

#34

@IgnasJ thanks i’ll try this.

#36

please help

#37

Please do not post lengthy output such as this direct to the forum and instead use something like Pastebin and share a link to it.

Note that I didn’t use any of those configure flags you selected and in particular I’m not sure if –with-neon works on a Raspberry Pi. Try configure without any options, as per the script Ignas shared.

#38

@andrewback i tried without options as per install.sh script but the same compiler loop.

#39

Not sure what to suggest, other than trying to work out what the problem is by searching to see if others have encountered this. Failing which posting to the Osmocom mailing list.

#40

@andrewback Successfully comlied and run, just made a fresh installation,

1 Like
#42

I was able to successfully fire up a GSM900 (arfcn 975) with osmo-nitb, osmo-btx-trx, and osmo-trx. The downlink at 925.2 Mhz is visible in GQRX with RTL dongle. Looks great and terminal log messages appear to be clean. Cell phones discover it as “Test PLMN 1-1”.

Then I try to attach a cell phone to it ( I run it with “auth policy accept-all” ) and none of the phones I tried can connect to the network. I can see uplink bursts from cell phones on GQRX around 880.2Mhz, but no activity in terminals and then a message on the cell comes up “Cannot register with the network at this time…”. Does anyone know how to debug this issue? Do I need to run something else in addition to osmo-nitb, osmo-btx-trx, and osmo-trx to allow registration? thanks.