I tried osmo-pcu but the output was like that.

I built everything again but my network hardly shows up, and with the name of the carrier for the SIM, not the name I assign !.

pi@raspberrypi:~ $ osmo-pcu -r 1

No config file: 'osmo-pcu.cfg' Using default config.

<0001> osmobts_sock.cpp:227 Opening OsmoPCU L1 interface to OsmoBTS

<0001> osmobts_sock.cpp:264 Failed to connect to the osmo-bts PCU socket, delaying... '/tmp/pcu_bts'

<0001> osmobts_sock.cpp:227 Opening OsmoPCU L1 interface to OsmoBTS

<0001> osmobts_sock.cpp:264 Failed to connect to the osmo-bts PCU socket, delaying... '/tmp/pcu_bts'

^CSignal 2 received.

full talloc report on 'Osmo-PCU context' (total 1 bytes in 1 blocks)

pi@raspberrypi:~ $ sudo osmo-pcu -r 1

No config file: 'osmo-pcu.cfg' Using default config.

<0001> osmobts_sock.cpp:227 Opening OsmoPCU L1 interface to OsmoBTS

<0001> osmobts_sock.cpp:285 osmo-bts PCU socket has been connected

<0001> pcu_l1_if.cpp:357 BTS not available

pi@raspberrypi:~ $

On Mon, Sep 5, 2016 at 11:14 AM, Neels Hofmeyr <nhofmeyr@sysmocom.de> wrote:

On Fri, Sep 02, 2016 at 03:18:30PM +0100, Abdulghafar Shabaneh wrote:
> Now I ran the osmo-nitb, osmo-bts-trx and osmo-trx all together with the
> USRP2 with FLEX900 daughter board GSM900 band, it all works well except the
> mobile is not able to register on the network.

I haven't looked at your error logs in detail, this is just what comes to
mind:

Response speed may be an issue. Hopefully the pi is fast enough, and maybe
try to run
osmo-bts-trx -r 1
and
osmo-pcu -r 1
for real-time priority (may need sudo).

Also, the timing source for the SDR may be an issue. I am told e.g. the
B200 is known to be unreliable without a quality timing source, and
results improve with a proper 10MHz clock connected.

~Neels