TRX CLK-indication and failing sync

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/.

Erich Dachleger edachleger at yahoo.com
Sun Mar 10 09:57:00 UTC 2013


Hi list,

I recently built the testing branch and openbts with respect to the transceiver-app.
I built openbts without compilation flags for uhd and resamp(saw on irc that that should'nt be required)
and without gnuradio.And I use the example sql openbts.db. I then use rssi-app to find the strongest reference cell and modify openbts.db

But when I upload the firmware Lost messages occur after a series of stale burst-messages.

openbts outputs a long chain of <0011> trx.c:512 TRX DATA  .....
interupted by single <0011> trx.c:190 TRX CLK Indication-messages.

And phones of cannot register to openbts-network  or even see it when doing manual scan.
Can the timing advance parameter and the BSIC parameterbe inserted to the openbts.db to remedy the failure of sync of the osmocom-phone-bts? If not can other measures be taken?

regards
erich


Output from upload of firmware:
----------------

Received DOWNLOAD ACK from phone, your code is running now!
Enabled Compal ramloader -> Calypso romloader chainloading mode
Received ident ack from phone, sending parameter sequence
read_file(../../target/firmware/board/compal_e88/trx.highram.bin): file_size=62964, hdr_len=0, dnload_len=62967
Received parameter ack from phone, starting download
Finished, sent 63 blocks in total
Received branch ack, your code is running now!
battery_compal_e88_init: starting up


OSMOCOM TRX (revision osmocon_v0.0.0-1747-geeafd9f-modified)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: 0dd7253ccb039bd6
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
======================================================================
Assert DSP into Reset
Releasing DSP from Reset
Installing DSP extensions patch
Setting some dsp_api.ndb values
Setting API NDB parameters
Finishing download phase
DSP Download Status: 0x0002
DSP API Version: 0x3606 0x0000
LOST 819!
BAT-ADC: 558   3   0   0 1023 389 364 227 
    Charger at 26 mV.
    Battery at 3814 mV.
    Charging at 0 mA.
    Battery capacity is 77%.
    Battery range is 3199..3999 mV.
    Battery full at 468 LSB .. full at 585 LSB
    Charging at 239 LSB (204 mA).
    BCICTL2=0x3ff
    battery-info.flags=0x00000000
    bat_compal_e88_chg_state=0
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=1, flags=0x7)
Starting FCCH RecognitionFB0 (1271:1): TOA=  384, Power= -64dBm, Angle=-9235Hz
FB1 (1275:2): TOA= 1219, Power= -62dBm, Angle= 2081Hz
  fn_offset=1273 (fn=1275 + attempt=2 + ntdma = 0)
  delay=8 (fn_offset=1273 + 11 - fn=1275 - 1
  scheduling next FB/SB detection task with delay 8
FB1 (1295:11): TOA=12467, Power= -62dBm, Angle=  389Hz
  fn_offset=1293 (fn=1295 + attempt=11 + ntdma = 9)
  delay=8 (fn_offset=1293 + 11 - fn=1295 - 1
  scheduling next FB/SB detection task with delay 8
=>FB @ FNR 1293 fn_offset=1293 qbits=4684
Synchronize_TDMA
LOST 3660!
SB1 (2590:1): TOA=   27, Power= -64dBm, Angle=  431Hz
=> SB 0x00a6d3f1: BSIC=60 fn=1240157(935/ 9/41) qbits=16
Synchronize_TDMA
=>FB @ FNR 2589 fn_offset=1240157 qbits=4924
LOST 1909!
BAT-ADC: 558   3   0   0 1023 390 365 230 
    Charger at 26 mV.
    Battery at 3814 mV.
    Charging at 0 mA.
    Battery capacity is 77%.
    Battery range is 3199..3999 mV.
    Battery full at 468 LSB .. full at 585 LSB
    Charging at 239 LSB (204 mA).
    BCICTL2=0x3ff
    battery-info.flags=0x00000000
LOST 1877!
    bat_compal_e88_chg_state=0
LOST 1873!
BTS MODE: 2 850
STALE BURST 2246
STALE BURST 2247
STALE BURST 2248
STALE BURST 2249
STALE BURST 2289
LOST 1884!
LOST 1866!
BAT-ADC: 554   4   0   0 1023 416 387 226 
    Charger at 34 mV.
    Battery at 3787 mV.
-----------------
-----------------
Test with another strong reference cell
ARFCN 53:
----------
L1CTL_FBSB_REQ (arfcn=53, flags=0x7)
Starting FCCH RecognitionLOST 2063!
FB0 (1629405:2): TOA= 1776, Power= -87dBm, Angle=-5747Hz
FB1 (1629416:9): TOA=10523, Power= -87dBm, Angle= -514Hz
  fn_offset=1629415 (fn=1629416 + attempt=9 + ntdma = 8)
  delay=9 (fn_offset=1629415 + 11 - fn=1629416 - 1
  scheduling next FB/SB detection task with delay 9
=>FB @ FNR 1629415 fn_offset=1629415 qbits=1908
Synchronize_TDMA
key=19 released
LOST 2618!
SB1 (543187:1): TOA=   30, Power= -88dBm, Angle= -409Hz
=> SB 0x0160516d: BSIC=27 fn=894398(674/24/11) qbits=28
Synchronize_TDMA
=>FB @ FNR 543186 fn_offset=894398 qbits=4936
LOST 1914!
L1CTL_NEIGH_PM_REQ new list with 8 entries
nb_cmd(0) and rxnb.msg != NULLccch_mode=0
TOA AVG is not 16 qbits, correcting (got 20)
TOA AVG is not 16 qbits, correcting (got 15)
...................
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20130310/9cb5dec8/attachment.htm>


More information about the baseband-devel mailing list