Some error happend in building OpenBTS by LimeSDR on Ubuntu 16.04


#1

I installed

SoapySDR (From Source)
LimeSuite
UHD
SoapyUHD (From Source)

then I build OpenBTS for B200.

I can run the osmo-trx,use:

sudo ./osmo-trx -s 4 -c 1 -e -l INFO -f

But when I run the OpenBTS,it will exit within 10 seconds.The output is:

Starting the system…
ALERT 14541:14541 2018-02-16T14:48:07.6 TRXManager.cpp:520:setSlot: SETSLOT(0,5) failed with status -1
ALERT 14541:14541 2018-02-16T14:48:10.9 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status -1
ALERT 14541:14541 2018-02-16T14:48:10.9 GSML1FEC.cpp:587:handoverPending: SCH handover clear failed
ALERT 14541:14541 2018-02-16T14:48:14.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status -1
ALERT 14541:14541 2018-02-16T14:48:14.1 GSML1FEC.cpp:587:handoverPending: FCCH handover clear failed
ALERT 14541:14541 2018-02-16T14:48:14.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status -1
ALERT 14541:14541 2018-02-16T14:48:14.1 GSML1FEC.cpp:587:handoverPending: BCCH handover clear failed
ALERT 14541:14541 2018-02-16T14:48:14.1 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status -1
ALERT 14541:14541 2018-02-16T14:48:14.2 GSML1FEC.cpp:587:handoverPending: C0T0 SDCCH/4-0 handover clear failed
ALERT 14541:14541 2018-02-16T14:48:14.2 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status -1
ALERT 14541:14541 2018-02-16T14:48:14.2 GSML1FEC.cpp:587:handoverPending: C0T0 SDCCH/4-0-SACCH handover clear failed
ALERT 14541:14541 2018-02-16T14:48:14.3 TRXManager.cpp:565:clearHandover: NOHANDOVER(0) failed with status -1
ALERT 14541:14541 2018-02-16T14:48:14.3 GSML1FEC.cpp:587:handoverPending: C0T0 SDCCH/4-1 handover clear failed
ALERT 14541:14541 2018-02-16T14:48:14.8 TRXManager.cpp:520:setSlot: SETSLOT(1,1) failed with status -1
ALERT 14541:14541 2018-02-16T14:48:14.8 TRXManager.cpp:520:setSlot: SETSLOT(2,1) failed with status -1
ALERT 14541:14541 2018-02-16T14:48:14.8 TRXManager.cpp:520:setSlot: SETSLOT(3,1) failed with status -1
ALERT 14541:14541 2018-02-16T14:48:14.8 TRXManager.cpp:520:setSlot: SETSLOT(4,1) failed with status -1
ALERT 14541:14541 2018-02-16T14:48:14.8 TRXManager.cpp:480:setPower: SETPOWER failed with status -1
1518763694.874931 140342853199680:
system ready

1518763694.875114 140342853199680:
use the OpenBTSCLI utility to access CLI

1518763694.876176 140342853199680: OpenBTSCLI network socket support for tcp:49300

OpenBTS> EMERG 14541:14553 2018-02-16T14:48:24.8 TRXManager.cpp:107:clockHandler: TRX clock interface timed out, assuming TRX is dead.

Broadcast message from systemd-journald@limesdr (Fri 2018-02-16 14:48:24 CST):

openbts[14541]: EMERG 14541:14553 2018-02-16T14:48:24.8 TRXManager.cpp:107:clockHandler: TRX clock interface timed out, assuming TRX is dead.

I google the error “TRX clock interface timed out, assuming TRX is dead” ,find a solution for BladeRF and YateBTS,it seems happend on the clock frequency.
But what should I do to solve this quetion about LimeSDR?

@andrewback @martywittrock Thank you.


#2

@BG6WRI,

This is a job for @joshblum - I’m certain that he would know why this is happening…

73 de Marty, KN0CK


#3

Thank you very much!


#4

@joshblum
Nice to meet you!
Have you seen this situation?
I Google it but just find the solutions on BladeRF and USRP,and the solutions is not useful for LimeSDR.
Thank you.


#5

I have also the same error, i don’t know whod to solve it ?