baseband-devel March 2013

baseband-devel@lists.osmocom.org

25 participants
31 discussions

AW: The call has been rejected
by Andreas.Eversberg 12 Apr '13

12 Apr '13

hi josephli, > Read stored BA list mnc=01 the mobile application stores the last cells and neighbour cells (band allocation) of each network. this way the scanning is much faster when restarting. because you use the SIM card with MNC == 02 the first time, there is no band allocation stored for that. the mobile will do a full scan in this case. > while the sim card service I am tesing is actually with mnc 00 and 02. i know that MNC == 0 will not work until i commited improvements of cell selection process last sunday. you should retry that, but first try with an MNC > 0. can you provide debug output when trying a call? also can you provide VTY output of "show ms" before you make the call? regards, andreas

3 2

status report layer1 and layer23
by Andreas.Eversberg 11 Apr '13

11 Apr '13

hi, i just fixed some locking issues the last days. fix will follow. it took a bit longer, because there were some race conditions. it took up to about one hour until it crashed. my way to detect the area where the crash happened, was to turn on buzzer before that area, and turn it off after that area. after many hours of approximation, i finally found out that the major crash happend during _talloc_zero. (first it looks for a free memory chunk, then it allocates it.) since it can be called from all contexts (main, irq, fiq), it need to be locked against any interrupt, otherwise the memory chunk can be assigned multiple times. (the process of _talloc_free is "atomic" and requires no locking.) because it seems pretty stable, i think it is time to merge some branches into the master. (i made a 6 hours call yesterday. and no crash after bugfix ever since.) i will do that together with sylvain, if we find the time this weekend. currently i use the jolly/voice together with the sylvain/traffic branch. i am able to use an isdn phone togehter with linux-call-router and make/receive calls. audio is passed both ways. i think this is a stage where it actually become "usable". (if not moving arround.) one of my major work for the next weeks/months will be the neighbour cell measurement, cell re-selection, and handover. this is essential when moving with the phone. regards, andreas

2 1

osmocon via uart
by tom jerry 31 Mar '13

31 Mar '13

i have a motorola c118 and running osmocon in raspberry. Am using the uart available in gpio pins. What are the ideal settings in terms of baud rate to allow communication,as i can't get hello world working.the cable is ok since when i short tx and rx,and use minicom whatever i type on the keyboard appears on minicom. Thanks

1 0

NEWSDR'13 Workshop / OpenBSC / OsmocomBB
by Harald Welte 29 Mar '13

29 Mar '13

Hi All, as I've just been made aware of by a business contact, there is a NEWSDR'13 workshop which, among other things, has OsmocomBB and OpenBSC on the list of topics: http://ecewp.ece.wpi.edu/wordpress/sdr-boston/newsdr-13/call-for-papers/ Did anyone ever hear of this workshop? Did the organizers ever make contact with us? I'm a bit surprised that somebody organizes a workshop with "our" projects on the agenda without even sending the CfP to us. Or maybe I just missed it? In case somebody is submitting a paper there: Please make sure to coordinate here in order to avoid different developers/contributors from submitting similar/related topics. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 1

TRX CLK-indication and failing sync
by Erich Dachleger 29 Mar '13

29 Mar '13

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

3 9

Osmocom web Site Down
by R. Revert 23 Mar '13

23 Mar '13

*Hi * *every one, from the 20th of this mounth the web site as some problems , i will like to help if you guy's if maibe osmocom projects need's servers to host the website or anythink else, than i can help whit somo IT resources..* * * *please let me know.* * * *Thanks #__________________ Atte. **Rafael R.* *Security Information Architect * *CEH, CHFI, **ECSA, LPT, VCP5, CEI, VCI*

2 1

A -very old- Sagem Trace Phone
by DFTC2000 22 Mar '13

22 Mar '13

<http://baseband-devel.722152.n3.nabble.com/file/n4025938/sagem2G.jpg> Hi everyone, I'm looking for informations about this very old trace phone. (Power adaptor spec, band type ...) Thanks a lot for your help (I can take some other pics if you want) BR. Dan, France -- View this message in context: http://baseband-devel.722152.n3.nabble.com/A-very-old-Sagem-Trace-Phone-tp4… Sent from the baseband-devel mailing list archive at Nabble.com.

1 0

Not able to see measurement reports in wireshark
by Mehrin Javed 21 Mar '13

21 Mar '13

Dear all, I have successfully made a call from the master branch of Osmocom-bb . After integrating it to wireshark, I am able to see system information 5 and 6 but I am unable to see the measurement reports and voice traffic. Following is what i am able to see when i execute the mobile application . There are valid measurement reports being generated , but why cant i view them in wireshark.? Looking forwards to your response as soon as possible. [0;m[1;32m<0005> gsm48_mm.c:3911 (ms 1) Received 'RR_DATA_IND' from RR in state MM connection active (sapi 0) [0;m[1;33m<0006> gsm48_cc.c:2161 (ms 1) Received 'MMCC_DATA_IND' in CC state MO_CALL_PROC [0;m[1;33m<0006> gsm48_cc.c:2115 (ms 1) Received 'ALERTING' in CC state MO_CALL_PROC [0;m[1;33m<0006> gsm48_cc.c:717 received ALERTING [0;m[1;33m<0006> gsm48_cc.c:243 new state MO_CALL_PROC -> CALL_DELIVERED [0;m[1;33m<0006> gsm48_cc.c:196 (ms 1 ti 0) Sending 'MNCC_ALERT_IND' to MNCC. [0;m[1;37m<0009> mnccms.c:387 Call is alerting [0;m[1;34m<0001> gsm48_rr.c:662 MON: f=57 lev=-75 snr=62 ber=151 LAI=410 03 e165 ID=9463 TA=0 pwr=10 TS=1 [0;m[1;34m<0001> gsm48_rr.c:2864 MEAS REP: pwr=10 TA=0 meas-invalid=0 rxlev-full=-75 rxlev-sub=-75 rxqual-full=0 rxqual-sub=0 dtx 0 ba 0 no-ncell-n 0 [0;m[1;34m<0001> gsm48_rr.c:4767 Indicated ta 0 (actual ta 0) [0;m[1;34m<0001> gsm48_rr.c:4769 Indicated tx_power 10 [0;m[1;34m<0001> gsm48_rr.c:4767 Indicated ta 0 (actual ta 0) [0;m[1;34m<0001> gsm48_rr.c:4769 Indicated tx_power 10 [0;m[1;34m<0001> gsm48_rr.c:662 MON: f=57 lev=-70 snr=49 ber= 81 LAI=410 03 e165 ID=9463 TA=0 pwr=10 TS=1 [0;m[1;34m<0001> gsm48_rr.c:2864 MEAS REP: pwr=10 TA=0 meas-invalid=0 rxlev-full=-70 rxlev-sub=-70 rxqual-full=0 rxqual-sub=0 dtx 0 ba 0 no-ncell-n 0 [0;m[1;34m<0001> gsm48_rr.c:4767 Indicated ta 0 (actual ta 0) [0;m[1;34m<0001> gsm48_rr.c:4769 Indicated tx_power 14 Thanks and Regards

1 0

Sharp drop in SNR during TCH
by Bhaskar11 20 Mar '13

20 Mar '13

Dear Sylvain, I'm studying traffic data using ccch_scan in burstind branch. In prim_sniff.c I track the SNR levels in l1s_sniff_resp() using code from print_tch.c to read snr values from: dsp_api.db_r->a_serv_demod[D_SNR]; I find that the level changes sharply from ccch mode to tch mode. In ccch mode most of the snr values are 16384. After switching to tch mode they range from 200 to 600 typically! Is this normal? Am I doing something wrong when changing mode? Below is the dump of snr values and freq_err during the run. B. =============== data dump fnx = fn % 26; freq_err = ANGLE_TO_FREQ(dsp_api.db_r->a_serv_demod[D_ANGLE]); snr = dsp_api.db_r->a_serv_demod[D_SNR]; fnx=6, bidx=0, freq_err=-24, snr=16384. SACCH fnx=7, bidx=0, freq_err=-6, snr=16384. SACCH fnx=8, bidx=0, freq_err=9, snr=16384. SACCH fnx=9, bidx=0, freq_err=-15, snr=16384. SACCH fnx=25, bidx=0, freq_err=-26, snr=16384. fnx=0, bidx=0, freq_err=10, snr=16384. fnx=1, bidx=0, freq_err=38, snr=16384. fnx=2, bidx=0, freq_err=-14, snr=*16384*. fnx=24, bidx=0, freq_err=46, snr=*16384*. fnx=25, bidx=0, freq_err=23, snr=*16384*. fnx=0, bidx=0, freq_err=-1, snr=*16384*. afc_correct(error=-1Hz, arfcn=24): delta=0, afc_dac(old=544,new=544) fnx=1, bidx=0, freq_err=22, snr=16384. *(Immediate Assignment starts here)* L1CTL_FBSB_REQ (arfcn=4, flags=0x7) Starting FCCH RecognitionFB0 (1266881:8): TOA= 8784, Power= -61dBm, Angle=10831Hz afc_correct(error=10831Hz, arfcn=4): delta=1283, afc_dac(old=-700,new=583) FB0 (1266892:9): TOA=10032, Power= -61dBm, Angle= -340Hz afc_correct(error=-340Hz, arfcn=4): delta=-40, afc_dac(old=583,new=543) FB1 (1266902:8): TOA= 8755, Power= -61dBm, Angle= 0Hz afc_correct(error=0Hz, arfcn=4): delta=0, afc_dac(old=543,new=543) fn_offset=1266900 (fn=1266902 + attempt=8 + ntdma = 6) delay=8 (fn_offset=1266900 + 11 - fn=1266902 - 1 scheduling next FB/SB detection task with delay 8 =>FB @ FNR 1266900 fn_offset=1266900 qbits=4836 Synchronize_TDMA LOST 3717! SB1 (2533807:1): TOA= 26, Power= -61dBm, Angle= 176Hz => SB 0x00a9dd65: BSIC=25 fn=1266912(955/10/21)=> DSP reports SB in bit that is 1127709799 bits in the future?!? Synchronize_TDMA => DSP reports FB in bit that is 1127709776 bits in the future?!? LOST 1907! afc_correct(error=4Hz, arfcn=4): delta=0, afc_dac(old=543,new=543) L1CTL_DM_EST_REQ (arfcn=12545, chan_nr=0x15, tsc=1) LOST 3047! *(tch mode is now active)* fnx=4, bidx=0, freq_err=-92, snr=*238*. fnx=6, bidx=0, freq_err=-132, snr=*82*. fnx=8, bidx=0, freq_err=103, snr=*145*. fnx=10, bidx=0, freq_err=-234, snr=*316*. fnx=12, bidx=0, freq_err=-89, snr=*292*. SACCH fnx=13, bidx=0, freq_err=46, snr=*270*. fnx=15, bidx=0, freq_err=35, snr=*387*. fnx=17, bidx=0, freq_err=201, snr=*1055*. fnx=19, bidx=0, freq_err=130, snr=549. fnx=21, bidx=0, freq_err=-94, snr=51. fnx=23, bidx=0, freq_err=-52, snr=173. fnx=0, bidx=0, freq_err=157, snr=322. fnx=2, bidx=0, freq_err=107, snr=95. afc_correct(error=12Hz, arfcn=24): delta=1, afc_dac(old=543,new=544) fnx=4, bidx=0, freq_err=86, snr=135. fnx=6, bidx=0, freq_err=-126, snr=207. ====================================

2 2

PROBLEM WHEN INSTALL LIPO-OSMO-DSP
by alishageri 17 Mar '13

17 Mar '13

WHEN I GIT LIPO-OSMO-DSP AND TYPE IN TERMENAL MAKE O HAVE PROBLE THAT SAY MAKE *** NO TARGET SPESIFIC AND NO MAKEFILE FOUND . STOP CAN ANY BODY TELL ME WHAT IS THE WRONG -- View this message in context: http://baseband-devel.722152.n3.nabble.com/PROBLEM-WHEN-INSTALL-LIPO-OSMO-D… Sent from the baseband-devel mailing list archive at Nabble.com.

2 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel March 2013