Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi)

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.

Dario Lombardo dario.lombardo.ml at gmail.com
Mon Feb 25 13:21:46 UTC 2013


I'm not succeeding in using the osmocom transceiver.

When openbts starts, the output shown is (a bunch of)

<0011> trx.c:190 TRX CLK Indication 1029029
<0011> trx.c:512 TRX Data 1029080:0:0:aac274073b9d407eb0bc014ed71e20
<0011> trx.c:512 TRX Data 1029081:0:0:61dbebb006fec0f9895e448fcafd10
<0011> trx.c:512 TRX Data 1029082:0:0:378d60f0c61b90eb0c9e1208114190
<0011> trx.c:512 TRX Data 1029083:0:0:a013ce5f9090c67e18229311431a30

When the osmocom mobile tries to attach, the output becomes

<0011> trx.c:512 TRX Data 1029491:0:0:a013ce5f9090c67e18229311431a30
<0012> l1ctl.c:351 Reset received: Starting sync.
<0011> trx.c:512 TRX Data 1029539:0:0:a14dd532a16dc062d07c030e055510
<0011> trx.c:512 TRX Data 1029540:0:0:82b7c400ae9e53e9bd7a0007bf5460
<0011> trx.c:512 TRX Data 1029541:0:0:842dd0834051146707753011978620
<0011> trx.c:512 TRX Data 1029542:0:0:9000ea751006a7f0380b57d421fe50
<0012> l1ctl.c:305 Sync failed, retrying ...
<0012> l1ctl.c:351 Reset received: Starting sync.
<0011> trx.c:512 TRX Data 1029590:0:0:aac274073b9d407eb0bc014ed71e20
<0011> trx.c:512 TRX Data 1029591:0:0:61dbebb006fec0f9895e448fcafd10
<0011> trx.c:512 TRX Data 1029592:0:0:378d60f0c61b90eb0c9e1208114190
<0011> trx.c:512 TRX Data 1029593:0:0:a013ce5f9090c67e18229311431a30
<0012> l1ctl.c:308 Sync acquired, wait for BCCH ...
<0012> l1ctl.c:351 Reset received: Starting sync.
<0012> l1ctl.c:308 Sync acquired, wait for BCCH ...
<0012> l1ctl.c:351 Reset received: Starting sync.
<0011> trx.c:512 TRX Data 1029641:0:0:8062948a52a104e0402112806004a0
<0011> trx.c:512 TRX Data 1029642:0:0:118a5288440000e102854a018a1600
<0011> trx.c:512 TRX Data 1029643:0:0:408904254000607400058000200220
<0011> trx.c:512 TRX Data 1029644:0:0:44a542052054286588022012a16200
<0012> l1ctl.c:308 Sync acquired, wait for BCCH ...
<0012> l1ctl.c:351 Reset received: Starting sync.
<0011> trx.c:512 TRX Data 1029692:0:0:aac274073b9d407eb0bc014ed71e20
<0011> trx.c:512 TRX Data 1029693:0:0:61dbebb006fec0f9895e448fcafd10
<0011> trx.c:512 TRX Data 1029694:0:0:378d60f0c61b90eb0c9e1208114190
<0011> trx.c:512 TRX Data 1029695:0:0:a013ce5f9090c67e18229311431a30
<0011> trx.c:512 TRX Data 1029743:0:0:a14dd532a16dc062d07c030e055510
<0011> trx.c:512 TRX Data 1029744:0:0:82b7c400ae9e53e9bd7a0007bf5460
<0011> trx.c:512 TRX Data 1029745:0:0:842dd0834051146707753011978620
<0011> trx.c:512 TRX Data 1029746:0:0:9000ea751006a7f0380b57d421fe50
<0012> l1ctl.c:308 Sync acquired, wait for BCCH ...
<0012> l1ctl.c:351 Reset received: Starting sync.

Until I get

ALERT 3063667520 TRXManager.cpp:93:clockHandler: TRX clock interface
timed out, assuming TRX is dead.

from openbts.

Output from osmocom mobile is

<0003> gsm322.c:2939 Channel synched on wrong ARFCN=XX, syncing on
right ARFCN again...
<0003> gsm322.c:474 Sync to ARFCN=0 rxlev=<=-110 (No sysinfo yet, ccch
mode NONE)

XX is the arfcn of the reference cell. Changing it doesn't change the
behavior. I've put this value as param for transceiver, according to
the instructions.
Any suggestion?
Thanks a lot.
Dario.




More information about the baseband-devel mailing list