baseband-devel

baseband-devel@lists.osmocom.org

1982 discussions

Channel Synchronization Problem with USRP

by Alex Costouris

Hello, I have built a local GSM network with the Osmocom Stack and an Ettus B200. I can see and attach to the network with my smartphone. Now, i want to use another usrp to simulate a mobile device but i am having trouble with synchronization with the channel. I think the problem lays in the layer 1 control channel or maybe even with the mobile configuration file. It starts camping on the channel, gets sysinfo, ccch mode COMB but then following a FBSB RESP: result=255 i get a channel synch error. Any help in steering me to the right direction would be greatly appreciated. Thank you in advance. mobile configuration file: ! ! OsmocomBB example configuration for mobile application !! ! line vty no login ! gps device /dev/ttyACM0 gps baudrate default no gps enable ! no hide-default ! ms 1 layer2-socket /tmp/osmocom_l2 sap-socket /tmp/osmocom_sap sim sap network-selection-mode auto imei 123456789012345 0 imei-fixed no emergency-imsi no sms-service-center no call-waiting no auto-answer no force-rekey no clip no clir tx-power auto no simulated-delay stick 119 location-updating neighbour-measurement codec full-speed prefer codec half-speed no abbrev support sms a5/1 a5/2 p-gsm no e-gsm no r-gsm no gsm-850 no dcs no pcs class-900 4 class-850 4 class-dcs 1 class-pcs 1 channel-capability sdcch+tchf+tchh full-speech-v1 full-speech-v2 half-speech-v1 min-rxlev -106 dsc-max 90 no skip-max-per-band test-sim imsi 001010000000000 ki comp128 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 no barred-access rplmn 123 01 audio io-handler none no shutdown trxcon logs: 20201203162008375 DL1C NOTICE l1ctl_link.c:236 Init L1CTL link (/tmp/osmocom_l2) 20201203162008375 DTRX NOTICE trx_if.c:675 Init transceiver interface (127.0.0.1:6700) 20201203162008375 DSCH NOTICE sched_trx.c:136 Init scheduler 20201203162008375 DAPP NOTICE trxcon.c:341 Init complete 20201203162016623 DL1C NOTICE l1ctl_link.c:180 L1CTL has a new connection 20201203162016623 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162016623 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162017260 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162017260 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162017260 DL1C NOTICE l1ctl.c:399 Received power measurement request (GSM900: 119 -> 119) 20201203162017261 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162017261 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162017261 DL1C NOTICE l1ctl.c:342 Received FBSB request (GSM900 119) 20201203162017261 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162017261 DSCH NOTICE sched_trx.c:199 Add a new TDMA timeslot #0 20201203162017261 DSCH NOTICE sched_trx.c:274 (Re)configure TDMA timeslot #0 as BCCH+CCCH 20201203162017261 DSCH NOTICE sched_trx.c:431 Activating lchan=SCH on ts=0 20201203162017261 DSCH NOTICE sched_trx.c:431 Activating lchan=BCCH on ts=0 20201203162017261 DSCH NOTICE sched_trx.c:431 Activating lchan=RACH on ts=0 20201203162017261 DSCH NOTICE sched_trx.c:431 Activating lchan=CCCH on ts=0 20201203162017513 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1481847 (42/51) for CCCH …. 20201203162017768 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1481902 (46/51) for CCCH 20201203162017777 DSCH NOTICE sched_clck.c:136 Clock indication: fn=1481907 20201203162017892 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1481929 (22/51) for CCCH …. 20201203162018004 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1481953 (46/51) for CCCH 20201203162018012 DSCH NOTICE sched_clck.c:136 Clock indication: fn=1481958 20201203162018037 DL1C NOTICE l1ctl.c:482 Received CCCH mode request (2) 20201203162018037 DSCH NOTICE sched_trx.c:274 (Re)configure TDMA timeslot #0 as BCCH+CCCH+SDCCH/4+SACCH/4 20201203162018037 DSCH NOTICE sched_trx.c:431 Activating lchan=SCH on ts=0 20201203162018037 DSCH NOTICE sched_trx.c:431 Activating lchan=BCCH on ts=0 20201203162018037 DSCH NOTICE sched_trx.c:431 Activating lchan=RACH on ts=0 20201203162018037 DSCH NOTICE sched_trx.c:431 Activating lchan=CCCH on ts=0 20201203162018037 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162018037 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162018037 DSCH NOTICE sched_trx.c:223 Delete TDMA timeslot #0 20201203162018037 DL1C NOTICE l1ctl.c:342 Received FBSB request (GSM900 119) 20201203162018037 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162018037 DSCH NOTICE sched_trx.c:199 Add a new TDMA timeslot #0 20201203162018037 DSCH NOTICE sched_trx.c:274 (Re)configure TDMA timeslot #0 as BCCH+CCCH+SDCCH/4+SACCH/4 20201203162018037 DSCH NOTICE sched_trx.c:431 Activating lchan=SCH on ts=0 20201203162018037 DSCH NOTICE sched_trx.c:431 Activating lchan=BCCH on ts=0 20201203162018037 DSCH NOTICE sched_trx.c:431 Activating lchan=RACH on ts=0 20201203162018037 DSCH NOTICE sched_trx.c:431 Activating lchan=CCCH on ts=0 20201203162018498 DL1C NOTICE l1ctl.c:307 FBSB timer fired for ARFCN 119 20201203162018498 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162018498 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162018498 DSCH NOTICE sched_trx.c:223 Delete TDMA timeslot #0 20201203162018498 DL1C NOTICE l1ctl.c:342 Received FBSB request (GSM900 119) 20201203162018498 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162018498 DSCH NOTICE sched_trx.c:199 Add a new TDMA timeslot #0 20201203162018498 DSCH NOTICE sched_trx.c:274 (Re)configure TDMA timeslot #0 as BCCH+CCCH+SDCCH/4+SACCH/4 20201203162018498 DSCH NOTICE sched_trx.c:431 Activating lchan=SCH on ts=0 20201203162018498 DSCH NOTICE sched_trx.c:431 Activating lchan=BCCH on ts=0 20201203162018498 DSCH NOTICE sched_trx.c:431 Activating lchan=RACH on ts=0 20201203162018498 DSCH NOTICE sched_trx.c:431 Activating lchan=CCCH on ts=0 20201203162018520 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1481964 (6/102) for CCCH …. 20201203162018806 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482025 (67/102) for CCCH 20201203162018949 DSCH NOTICE sched_clck.c:136 Clock indication: fn=1482060 20201203162018960 DL1C NOTICE l1ctl.c:307 FBSB timer fired for ARFCN 119 20201203162018960 DL1C NOTICE l1ctl.c:694 Received L1CTL_DM_REL_REQ, switching back to CCCH 20201203162018960 DSCH NOTICE sched_trx.c:177 Reset scheduler 20201203162018960 DSCH NOTICE sched_trx.c:223 Delete TDMA timeslot #0 20201203162018960 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162018960 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162018961 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162018961 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162018961 DL1C NOTICE l1ctl.c:399 Received power measurement request (GSM900: 119 -> 119) 20201203162018963 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162018963 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162018963 DL1C NOTICE l1ctl.c:342 Received FBSB request (GSM900 119) 20201203162018963 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162018963 DSCH NOTICE sched_trx.c:199 Add a new TDMA timeslot #0 20201203162018963 DSCH NOTICE sched_trx.c:274 (Re)configure TDMA timeslot #0 as BCCH+CCCH 20201203162018963 DSCH NOTICE sched_trx.c:431 Activating lchan=SCH on ts=0 20201203162018963 DSCH NOTICE sched_trx.c:431 Activating lchan=BCCH on ts=0 20201203162018963 DSCH NOTICE sched_trx.c:431 Activating lchan=RACH on ts=0 20201203162018964 DSCH NOTICE sched_trx.c:431 Activating lchan=CCCH on ts=0 20201203162019070 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482184 (22/51) for CCCH …. 20201203162019890 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482361 (46/51) for CCCH 20201203162019898 DSCH NOTICE sched_clck.c:136 Clock indication: fn=1482366 20201203162019920 DL1C NOTICE l1ctl.c:482 Received CCCH mode request (2) 20201203162019920 DSCH NOTICE sched_trx.c:274 (Re)configure TDMA timeslot #0 as BCCH+CCCH+SDCCH/4+SACCH/4 20201203162019920 DSCH NOTICE sched_trx.c:431 Activating lchan=SCH on ts=0 20201203162019920 DSCH NOTICE sched_trx.c:431 Activating lchan=BCCH on ts=0 20201203162019920 DSCH NOTICE sched_trx.c:431 Activating lchan=RACH on ts=0 20201203162019920 DSCH NOTICE sched_trx.c:431 Activating lchan=CCCH on ts=0 20201203162019920 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162019920 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162019920 DSCH NOTICE sched_trx.c:223 Delete TDMA timeslot #0 20201203162019920 DL1C NOTICE l1ctl.c:342 Received FBSB request (GSM900 119) 20201203162019920 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162019920 DSCH NOTICE sched_trx.c:199 Add a new TDMA timeslot #0 20201203162019920 DSCH NOTICE sched_trx.c:274 (Re)configure TDMA timeslot #0 as BCCH+CCCH+SDCCH/4+SACCH/4 20201203162019920 DSCH NOTICE sched_trx.c:431 Activating lchan=SCH on ts=0 20201203162019920 DSCH NOTICE sched_trx.c:431 Activating lchan=BCCH on ts=0 20201203162019921 DSCH NOTICE sched_trx.c:431 Activating lchan=RACH on ts=0 20201203162019921 DSCH NOTICE sched_trx.c:431 Activating lchan=CCCH on ts=0 20201203162020382 DL1C NOTICE l1ctl.c:307 FBSB timer fired for ARFCN 119 20201203162020382 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162020382 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162020382 DSCH NOTICE sched_trx.c:223 Delete TDMA timeslot #0 20201203162020382 DL1C NOTICE l1ctl.c:342 Received FBSB request (GSM900 119) 20201203162020382 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162020382 DSCH NOTICE sched_trx.c:199 Add a new TDMA timeslot #0 20201203162020382 DSCH NOTICE sched_trx.c:274 (Re)configure TDMA timeslot #0 as BCCH+CCCH+SDCCH/4+SACCH/4 20201203162020382 DSCH NOTICE sched_trx.c:431 Activating lchan=SCH on ts=0 20201203162020382 DSCH NOTICE sched_trx.c:431 Activating lchan=BCCH on ts=0 20201203162020382 DSCH NOTICE sched_trx.c:431 Activating lchan=RACH on ts=0 20201203162020382 DSCH NOTICE sched_trx.c:431 Activating lchan=CCCH on ts=0 20201203162020405 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482372 (6/102) for CCCH …. 20201203162020687 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482433 (67/102) for CCCH 20201203162020834 DSCH NOTICE sched_clck.c:136 Clock indication: fn=1482468 20201203162020844 DL1C NOTICE l1ctl.c:307 FBSB timer fired for ARFCN 119 20201203162020844 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162020844 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162020844 DSCH NOTICE sched_trx.c:223 Delete TDMA timeslot #0 20201203162020844 DL1C NOTICE l1ctl.c:399 Received power measurement request (GSM900: 119 -> 119) 20201203162020846 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162020846 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162020846 DL1C NOTICE l1ctl.c:342 Received FBSB request (GSM900 119) 20201203162020846 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162020846 DSCH NOTICE sched_trx.c:199 Add a new TDMA timeslot #0 20201203162020846 DSCH NOTICE sched_trx.c:274 (Re)configure TDMA timeslot #0 as BCCH+CCCH 20201203162020846 DSCH NOTICE sched_trx.c:431 Activating lchan=SCH on ts=0 20201203162020846 DSCH NOTICE sched_trx.c:431 Activating lchan=BCCH on ts=0 20201203162020846 DSCH NOTICE sched_trx.c:431 Activating lchan=RACH on ts=0 20201203162020846 DSCH NOTICE sched_trx.c:431 Activating lchan=CCCH on ts=0 20201203162020953 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482592 (22/51) for CCCH …. 20201203162021298 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482667 (46/51) for CCCH 20201203162021307 DSCH NOTICE sched_clck.c:136 Clock indication: fn=1482672 20201203162021424 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482694 (22/51) for CCCH …. 20201203162021533 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482718 (46/51) for CCCH 20201203162021543 DSCH NOTICE sched_clck.c:136 Clock indication: fn=1482723 20201203162021660 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482745 (22/51) for CCCH …. 20201203162021770 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482769 (46/51) for CCCH 20201203162021779 DSCH NOTICE sched_clck.c:136 Clock indication: fn=1482774 20201203162021803 DL1C NOTICE l1ctl.c:482 Received CCCH mode request (2) 20201203162021803 DSCH NOTICE sched_trx.c:274 (Re)configure TDMA timeslot #0 as BCCH+CCCH+SDCCH/4+SACCH/4 20201203162021803 DSCH NOTICE sched_trx.c:431 Activating lchan=SCH on ts=0 20201203162021803 DSCH NOTICE sched_trx.c:431 Activating lchan=BCCH on ts=0 20201203162021803 DSCH NOTICE sched_trx.c:431 Activating lchan=RACH on ts=0 20201203162021803 DSCH NOTICE sched_trx.c:431 Activating lchan=CCCH on ts=0 20201203162021803 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162021803 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162021803 DSCH NOTICE sched_trx.c:223 Delete TDMA timeslot #0 20201203162021803 DL1C NOTICE l1ctl.c:342 Received FBSB request (GSM900 119) 20201203162021803 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162021803 DSCH NOTICE sched_trx.c:199 Add a new TDMA timeslot #0 20201203162021803 DSCH NOTICE sched_trx.c:274 (Re)configure TDMA timeslot #0 as BCCH+CCCH+SDCCH/4+SACCH/4 20201203162021803 DSCH NOTICE sched_trx.c:431 Activating lchan=SCH on ts=0 20201203162021803 DSCH NOTICE sched_trx.c:431 Activating lchan=BCCH on ts=0 20201203162021803 DSCH NOTICE sched_trx.c:431 Activating lchan=RACH on ts=0 20201203162021803 DSCH NOTICE sched_trx.c:431 Activating lchan=CCCH on ts=0 20201203162022265 DL1C NOTICE l1ctl.c:307 FBSB timer fired for ARFCN 119 20201203162022265 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162022265 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162022265 DSCH NOTICE sched_trx.c:223 Delete TDMA timeslot #0 20201203162022265 DL1C NOTICE l1ctl.c:342 Received FBSB request (GSM900 119) 20201203162022265 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162022265 DSCH NOTICE sched_trx.c:199 Add a new TDMA timeslot #0 20201203162022265 DSCH NOTICE sched_trx.c:274 (Re)configure TDMA timeslot #0 as BCCH+CCCH+SDCCH/4+SACCH/4 20201203162022265 DSCH NOTICE sched_trx.c:431 Activating lchan=SCH on ts=0 20201203162022265 DSCH NOTICE sched_trx.c:431 Activating lchan=BCCH on ts=0 20201203162022265 DSCH NOTICE sched_trx.c:431 Activating lchan=RACH on ts=0 20201203162022265 DSCH NOTICE sched_trx.c:431 Activating lchan=CCCH on ts=0 20201203162022309 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482786 (12/102) for CCCH …. 20201203162022518 DSCHD ERROR sched_lchan_xcch.c:102 Received bad data frame at fn=1482831 (57/102) for CCCH 20201203162022523 DL1C NOTICE l1ctl.c:426 Received reset request (1) 20201203162022523 DSCH NOTICE sched_trx.c:177 Reset scheduler and clock counter 20201203162022523 DSCH NOTICE sched_trx.c:223 Delete TDMA timeslot #0 20201203162022523 DL1D NOTICE l1ctl_link.c:81 L1CTL has lost connection …. mobile application logs: 000e> gsm322.c:1380 Start search of last registered PLMN (mcc=123 mnc=01 One, Two) <0002> gsm322.c:1384 Use RPLMN (mcc=123 mnc=01 One, Two) <0002> gsm322.c:810 new state 'A0 null' -> 'A1 trying RPLMN' <0003> gsm322.c:4060 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in state 'C0 null' <000e> gsm322.c:3642 Selecting PLMN (mcc=123 mnc=01 One, Two) <0003> gsm322.c:3650 Start stored cell selection. <0003> gsm322.c:833 new state 'C0 null' -> 'C2 stored cell selection' <0003> gsm322.c:2793 Scanning power for sticked cell. <0003> gsm322.c:2868 Scanning frequencies. (119..119) <0003> gsm322.c:2916 Found signal (ARFCN 119 rxlev -55 (55)) <0003> gsm322.c:2933 Done with power scanning range. <0003> gsm322.c:2793 Scanning power for sticked cell. <0003> gsm322.c:2845 Found 1 frequencies. <0003> gsm322.c:2258 Scanning frequency 119 (rxlev -55). <0003> gsm322.c:477 Sync to ARFCN=119 rxlev=-55 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2278 30 frequencies left in band 955..124 <000c> l1ctl.c:300 Dropping frame with 55 bit errors …. <000c> l1ctl.c:300 Dropping frame with 55 bit errors <0003> gsm322.c:2956 Channel synched. (ARFCN=119, snr=0, BSIC=63) <0003> gsm322.c:703 Starting CS timer with 4 seconds. <0001> gsm322.c:2979 using DSC of 90 <0003> gsm48_rr.c:4822 Channel provides data. <0003> gsm322.c:703 Starting CS timer with 4 seconds. <0001> gsm48_rr.c:1816 New SYSTEM INFORMATION 2 <000c> l1ctl.c:300 Dropping frame with 55 bit errors …. <000c> l1ctl.c:300 Dropping frame with 55 bit errors <0001> sysinfo.c:703 New SYSTEM INFORMATION 3 (mcc 123 mnc 01 lac 0x007c) <0001> gsm48_rr.c:1907 Changing CCCH_MODE to 2 <0001> gsm48_rr.c:1939 New SYSTEM INFORMATION 4 (mcc 123 mnc 01 lac 0x007c) <0001> sysinfo.c:615 Now updating previously received SYSTEM INFORMATION 4 <0001> gsm48_rr.c:1787 New SYSTEM INFORMATION 1 <0003> gsm322.c:2721 Received relevant sysinfo. <0003> gsm322.c:713 stopping pending CS timer. <0003> gsm322.c:2327 Scan frequency 119: Cell found. (rxlev -55 mcc 123 mnc 01 lac 007c) <0003> gsm322.c:1841 Select using access class <0003> gsm322.c:383 A (RLA_C (-55) - RXLEV_ACC_MIN (-110)) = 55 <0003> gsm322.c:385 B (MS_TXPWR_MAX_CCH (35) - p (33)) = 2 <0003> gsm322.c:387 C1 (A - MAX(B,0)) = 53 <0003> gsm322.c:1955 Cell ARFCN 119: Cell found, (rxlev=-55 mcc=123 mnc=01 lac=007c One, Two) <0003> gsm322.c:1970 Cell ARFCN 119 selected. <0003> gsm322.c:2428 Tune to frequency 119. <0003> gsm322.c:464 Sync to ARFCN=119 rxlev=-55 (Sysinfo, ccch mode COMB) <0003> gsm322.c:2455 Cell available. <0003> gsm322.c:4060 (ms 1) Event 'EVENT_CELL_FOUND' for Cell selection in state 'C2 stored cell selection' <000e> gsm322.c:3392 Camping normally on cell (ARFCN=119 mcc=123 mnc=01 One, Two) <0003> gsm322.c:833 new state 'C2 stored cell selection' -> 'C3 camped normally' <0005> gsm48_mm.c:4305 (ms 1) Received 'MM_EVENT_CELL_SELECTED' event in state MM IDLE, PLMN search <0005> gsm48_mm.c:904 new MM IDLE state PLMN search -> location updating needed <0005> gsm48_mm.c:904 new MM IDLE state location updating needed -> attempting to update <0005> gsm48_mm.c:424 starting T3212 (periodic loc. upd. delay) with 1800 seconds <0005> gsm48_mm.c:2285 Do Loc. upd. for IMSI attach. <000e> gsm48_mm.c:2204 Perform location update (MCC 123, MNC 01 LAC 0x007c) <0005> gsm48_mm.c:2340 LOCATION UPDATING REQUEST <0005> gsm48_mm.c:2360 using LAI (mcc 123 mnc 01 lac 0x007c) <0005> gsm48_mm.c:2370 using TMSI 0x9d4f59da <0005> gsm48_mm.c:909 new state MM IDLE, attempting to update -> wait for RR connection (location updating) <0001> gsm48_rr.c:5449 (ms 1) Message 'RR_EST_REQ' received in state idle (sapi 0) <000e> gsm48_rr.c:1299 Establish radio link due to mobility management request <0003> gsm322.c:4060 (ms 1) Event 'EVENT_LEAVE_IDLE' for Cell selection in state 'C3 camped normally' <0003> gsm322.c:833 new state 'C3 camped normally' -> 'connected mode 1' <0003> gsm322.c:3677 Going to camping (normal) ARFCN 119. <0003> gsm322.c:456 Sync to ARFCN=119, but there is a sync already pending <0001> gsm48_rr.c:359 new state idle -> connection pending <0001> gsm48_rr.c:1446 CHANNEL REQUEST: 00 (Location Update with NECI) <000c> l1ctl.c:169 FBSB RESP: result=255 <0003> gsm322.c:3001 Channel sync error, try again <0003> gsm322.c:464 Sync to ARFCN=119 rxlev=-55 (Sysinfo, ccch mode COMB) <000c> l1ctl.c:300 Dropping frame with 60 bit errors …. <000c> l1ctl.c:300 Dropping frame with 61 bit errors <0001> gsm48_rr.c:667 MON: f=119 lev=>=-47 snr= 0 ber= 61 LAI=123 01 007c ID=1e61 <000c> l1ctl.c:169 FBSB RESP: result=255 <0003> gsm322.c:3014 Channel sync error. <0003> gsm322.c:3018 free sysinfo ARFCN=119 <0003> gsm322.c:3027 Unselect cell due to sync error! <0003> gsm322.c:509 Unselecting serving cell. <0003> gsm322.c:3111 Loss of SACCH, Trigger RR abort. <000e> gsm48_rr.c:2879 Radio link lost signal <0001> gsm48_rr.c:2886 LOS during RACH request <0001> gsm48_rr.c:359 new state connection pending -> idle <0003> gsm322.c:4060 (ms 1) Event 'EVENT_RET_IDLE' for Cell selection in state 'connected mode 1' <0003> gsm322.c:3581 Cell not selected anymore, choose cell! <0003> gsm322.c:833 new state 'connected mode 1' -> 'C5 choose cell' <0003> gsm322.c:3523 No BA range(s), try sysinfo. <0003> gsm322.c:2480 No BA, because no sysinfo <0003> gsm322.c:3527 No BA on sysinfo, try stored BA list. <0003> gsm322.c:3537 No BA list to use. <0003> gsm322.c:4060 (ms 1) Event 'EVENT_NO_CELL_FOUND' for Cell selection in state 'C5 choose cell' <0003> gsm322.c:833 new state 'C5 choose cell' -> 'C1 normal cell selection' <0003> gsm322.c:2793 Scanning power for sticked cell. <0003> gsm322.c:2868 Scanning frequencies. (119..119) <0005> gsm48_mm.c:3902 (ms 1) Received 'RR_REL_IND' from RR in state wait for RR connection (location updating) (sapi 0) <0005> gsm48_mm.c:2739 RR link released after loc. upd. <000e> gsm48_mm.c:2683 Location update failed <000e> gsm48_mm.c:2693 Try location update later <0005> gsm48_mm.c:2694 Loc. upd. failed, retry #0 <0005> gsm48_mm.c:411 starting T3211 (loc. upd. retry delay) with 15.0 seconds <0005> gsm48_mm.c:1086 Not camping, wait for CS process to camp, it sends us CELL_SELECTED then. <0003> gsm322.c:2916 Found signal (ARFCN 119 rxlev -55 (55)) <0003> gsm322.c:2933 Done with power scanning range. <0003> gsm322.c:2793 Scanning power for sticked cell. <0003> gsm322.c:2845 Found 1 frequencies. <0003> gsm322.c:2258 Scanning frequency 119 (rxlev -55). <0003> gsm322.c:477 Sync to ARFCN=119 rxlev=-55 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2278 30 frequencies left in band 955..124 <0003> gsm322.c:2956 Channel synched. (ARFCN=119, snr=0, BSIC=63) <0003> gsm322.c:703 Starting CS timer with 4 seconds. <0001> gsm322.c:2979 using DSC of 90 <000c> l1ctl.c:300 Dropping frame with 55 bit errors …. <000c> l1ctl.c:300 Dropping frame with 55 bit errors <0003> gsm48_rr.c:4822 Channel provides data. <0003> gsm322.c:703 Starting CS timer with 4 seconds. <0001> gsm48_rr.c:1816 New SYSTEM INFORMATION 2 <000c> l1ctl.c:300 Dropping frame with 55 bit errors …. <000c> l1ctl.c:300 Dropping frame with 55 bit errors <0001> sysinfo.c:703 New SYSTEM INFORMATION 3 (mcc 123 mnc 01 lac 0x007c) <0001> gsm48_rr.c:1907 Changing CCCH_MODE to 2 <0001> gsm48_rr.c:1939 New SYSTEM INFORMATION 4 (mcc 123 mnc 01 lac 0x007c) <0001> sysinfo.c:615 Now updating previously received SYSTEM INFORMATION 4 <0001> gsm48_rr.c:1787 New SYSTEM INFORMATION 1 <0003> gsm322.c:2721 Received relevant sysinfo. <0003> gsm322.c:713 stopping pending CS timer. <0003> gsm322.c:2327 Scan frequency 119: Cell found. (rxlev -55 mcc 123 mnc 01 lac 007c) <0003> gsm322.c:1841 Select using access class <0003> gsm322.c:383 A (RLA_C (-55) - RXLEV_ACC_MIN (-110)) = 55 <0003> gsm322.c:385 B (MS_TXPWR_MAX_CCH (35) - p (33)) = 2 <0003> gsm322.c:387 C1 (A - MAX(B,0)) = 53 <0003> gsm322.c:1955 Cell ARFCN 119: Cell found, (rxlev=-55 mcc=123 mnc=01 lac=007c One, Two) <0003> gsm322.c:1970 Cell ARFCN 119 selected. <0003> gsm322.c:2428 Tune to frequency 119. <0003> gsm322.c:464 Sync to ARFCN=119 rxlev=-55 (Sysinfo, ccch mode COMB) <0003> gsm322.c:2455 Cell available. <0003> gsm322.c:4060 (ms 1) Event 'EVENT_CELL_FOUND' for Cell selection in state 'C1 normal cell selection' <000e> gsm322.c:3392 Camping normally on cell (ARFCN=119 mcc=123 mnc=01 One, Two) <0003> gsm322.c:833 new state 'C1 normal cell selection' -> 'C3 camped normally' <0005> gsm48_mm.c:4310 (ms 1) Received 'MM_EVENT_CELL_SELECTED' event in state wait for RR connection (location updating) <0005> gsm48_mm.c:1141 We are camping normally as returning to MM IDLE <0005> gsm48_mm.c:1166 Loc. upd. allowed. <0005> gsm48_mm.c:914 new state wait for RR connection (location updating) -> MM IDLE, location updating needed <0005> gsm48_mm.c:904 new MM IDLE state location updating needed -> attempting to update <0005> gsm48_mm.c:2222 Loc. upd. already pending. <000c> l1ctl.c:169 FBSB RESP: result=255 <0003> gsm322.c:3001 Channel sync error, try again <0003> gsm322.c:464 Sync to ARFCN=119 rxlev=-55 (Sysinfo, ccch mode COMB) <000c> l1ctl.c:300 Dropping frame with 60 bit errors …. <000c> l1ctl.c:300 Dropping frame with 60 bit errors <000c> l1ctl.c:169 FBSB RESP: result=255 <0003> gsm322.c:3014 Channel sync error. <0003> gsm322.c:3018 free sysinfo ARFCN=119 <0003> gsm322.c:3027 Unselect cell due to sync error!

4 years, 9 months

"Bad signalling message, sign_link returned error: Operation not permitted" - during voice call

by Mario Lucas

Dear team, I did set up GSM network with SDR (LimeSDRmini). SMS are ok. However when try to make voice call got following message on osmo-bsc terminal: <0003> abis_rsl.c:1372 (bts=0) CHAN RQD: reason: call re-establishment (ra=0x41, neci=0x01, chreq_reason=0x02) <0007> osmo_bsc_sigtran.c:305 Initializing resources for new SIGTRAN connection to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... <0007> osmo_bsc_sigtran.c:351 Opening new SIGTRAN connection (id=31) to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP <0003> abis_rsl.c:1372 (bts=0) CHAN RQD: reason: answer to paging (ra=0x9b, neci=0x01, chreq_reason=0x01) <0007> osmo_bsc_sigtran.c:305 Initializing resources for new SIGTRAN connection to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP... <0007> osmo_bsc_sigtran.c:351 Opening new SIGTRAN connection (id=32) to MSC: RI=SSN_PC,PC=0.23.1,SSN=BSSAP <0004> abis_nm.c:344 BTS 0 reported connected PCU version 0.8.0 <0016> input/ipaccess.c:411 Bad signalling message, sign_link returned error: Operation not permitted. <0016> input/ipaccess.c:411 Bad signalling message, sign_link returned error: Operation not permitted. WHat is this bad signalling message operation not permitted? -- Mario Lucas

4 years, 9 months

Osmocom C files syntax understanding

by Mario Lucas

Dear baseband-developers team, Would you be so kind to advise me on the following: I desire (dramatically want very much) to learn / understand Osmocom projects. I am a beginner in programming and i try to understand / learn C files that the project is build of. As an example i tried to learn / understand for example an Osmocom message buffer — msgb.h file. But immediately faced some syntax difficulties: This is the extract of msgb.h file: struct msgb { struct llist_head list; /*!< \brief linked list header */ /* Part of which TRX logical channel we were received / transmitted */ /* FIXME: move them into the control buffer */ union { void *dst; /*!< \brief reference of origin/destination */ struct gsm_bts_trx *trx; }; As it can be seen a structure «msgb» has as one of its components another structure — «gsm_bts_trx» But in whole Osmocom BB project files i could not find definition / description of struct «gsm_bts_trx». Would you kindly advise me please how to see which components / constituents / elements are in this gsm_bts_trx structure? From which components is struct gsm_bts_trx build of? Thank you so much for your kind advise. -- Mario Lucas

4 years, 9 months

Dropped packets by HW.... Dumping Stale bursts

by Mario Lucas

Dear all, I am using LimeSDRmini to run osmo-bts… During operation from time-to time (and sometimes quite frequently) following messages pop-up in terminal: «Dropped packets by HW!» and «Dumping Stale bursts...» I guess my LimeSDRmini is dropping some packets. LimeSDRmini configuration is: Firmware 6, Hardware 3, Protocol1, Gateware 1.3. Would you advise — may be there is more or less stable firmware version that to some extent is stable while working with Osmo-bts ? Thanks -- Mario Lucas

4 years, 9 months

PCU socket not connected, dropping message

by Mario Lucas

Dear baseband developers team, I built home gsm network with Osmo-stp-msc-hlr-bsc-bts, osmo-trx limeSDR. I managed and registered phones. I did send sms between each other. However when i decided to make a call — i noticed following message in terminal: «PCU socket not connected, dropping message». I searched on Osmocom web site and it is said that pcu socket is involved in GPRS things (i.e. in internet). Therefore why does such message appears when i try to make simple call between two mobiles — it has nothing to do with GPRS… And what would you advise me how to resolve this ? P.S. initially when i was about to start osmo-bts-trx i got message «PCU L1 socket failed» and i just renamed the pcu_bts file to some other name and osmo-bts-trx started. Thank you so much for your kind reply. Best regards -- Mario Lucas

4 years, 9 months

fixeria trx.highram.bin stuck

by Mario Lucas

Dear all, Pls help me with the following issue: I want to run a transceiver having motorola c115… i follow the procedure described in CalypsoBTS page : http://osmocom.org/projects/baseband/wiki/CalypsoBTS without chainloader i get: /home/ubuntu# /home/ubuntu/trx/src/host/osmocon/./osmocon -m c123xor -p /dev/ttyUSB0 /home/ubuntu/trx/src/target/firmware/board/compal_e88/trx.highram.bin got 7 bytes from modem, data looks like: 66 74 6d 74 6f 6f 6c ftmtool Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: c1 . got 1 bytes from modem, data looks like: 66 f and with chainloader i get: /home/ubuntu# /home/ubuntu/trx/src/host/osmocon/./osmocon -m c123xor -p /dev/ttyUSB0 -c /home/ubuntu/trx/src/target/firmware/board/compal_e88/trx.highram.bin got 2 bytes from modem, data looks like: 04 81 .. got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(chainloader): file_size=32, hdr_len=4, dnload_len=39 got 1 bytes from modem, data looks like: 00 . it seems with chainloader it is trying to do more but still stuck…. pls help…. Mario -- Mario Lucas

4 years, 9 months

OsmoDevCon / COVID-19

by Harald Welte

Dear fellow Osmocom developers, as you all know, we've sadly had to postpone OsmoDevCon 2020 back in April this year. At the time, we discussed to re-visit the situation in October 2020. While legally it is no problem at all to host an event with ~ 20 participants in Berlin/Germany (specific regulations really only start from 50+ participants) - I'm not entirely convinced it would be the smartest move. Legality and public health regulations are only one part of the equation - common sense and profound care for the key members of our community for sure are more relevant considerations to me. I'm not 100% in favour and not 100% against. Hence, I would like to get your input. Should we a) try to get an event organized on-site in Berlin? We'd have to move to a larger venue than IN-Berlin with proper ventilation and sufficient space so we can keep physical distance, but I think that's manageable for sysmocom as organizer. b) simply postpone to 2021? I'm convinced the situation will not change significantly (in a positive way) until late April 2021, so it's not really a "solution" as it will likely mean we have to think of late 2021 or 2022. c) plan some kind of online conference? To be honest, I think this model works fine for events where a single speaker wants to give lectures to hundreds or thousands of participants. But OsmoDevCon is much more interactive. We could record or live-stream some talks or screencasts from home, sure. But that only captures one part of the event. We could also try to set a date for a collaborative mumble, or the like - for the "hallway track". What are your thoughts? Let's avoid cross-posting the discussion to all of the mailing lists and simply have it on openbsc(a)lists.osmocom.org. Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

4 years, 12 months

Osmocom scheduled outage on *2020-07-19 9am CEST*

by Harald Welte

There is an urgent need to migrate our most important public infrastructure to a new server, and I will be doing that on *Sunday, July 19 2020*, starting about 9am CEST. The migration involves redmine (main osmocom.org website), jenkins, gerrit, git, and cgit. In theory, the migration should be quick. I would expect (significantly) less than one hour of downtime. However, we all know Murphys law. Services not affected are mail (including mailman lists), ftp, dns. So in case of doubt, we can still use mailing lists to communicate. In case anyone urgently needs osmocom source code on Sunday morning during the downtime: There are public mirrors available on github. Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

5 years, 1 month

OsmocomBB

by Антон Левченко

Hello! During build OsmocomBB I have problem. When I do "make", I get errors: *** No rule to make target `geo.c', needed by `geo.o'. Stop. vgsm@vgsm:~/osmocom/osmocombb/src$ make nofirmware make -C host/layer23 make[1]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23' Making all in include make[2]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include' Making all in osmocom make[3]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom' Making all in bb make[4]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom/bb' Making all in common make[5]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom/bb/common' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom/bb/common' Making all in misc make[5]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom/bb/misc' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom/bb/misc' Making all in mobile make[5]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom/bb/mobile' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom/bb/mobile' make[5]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom/bb' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom/bb' make[4]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom/bb' make[4]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom' make[3]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include/osmocom' make[3]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include' make[2]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/include' Making all in src make[2]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/src' Making all in common make[3]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/src/common' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/src/common' Making all in misc make[3]: Entering directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/src/misc' make[3]: *** No rule to make target `geo.c', needed by `geo.o'. Stop. make[3]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/src/misc' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/vgsm/osmocom/osmocombb/src/host/layer23' make: *** [layer23] Error 2 vgsm@vgsm:~/osmocom/osmocombb/src$

5 years, 4 months

Osmocom GTM-900B carrier board

by Harald Welte

Hi all! It is quite some time since it was brought to our attention that there's an old Huawei module that also uses the Ti Calypso chipset and hence can be used with OsmocomBB: The GTM-900B. It's just a modem module with a FPC connector, so no easy to use interfaces for any of the related signals, no SIM holder, etc. At sysmocom we've finally found some time to do a carrier board design for this, which will expose all the relevant signals (audio, UARTs, power, reset, ...). Martin (Cc) is working on it right now. The discussion regarding this breakout board can be followed at https://osmocom.org/issues/4030 If you have any input, please provide it now, as we are trying to complete this design by the end of the week so we can order prottoypes. The actual design files (EAGLE) including a PDF export of the schematics can be found in the osmo-small-hardware.git repository. Thanks for your input. Once the prototype is validated, we plan to make the boards (bundled with GTM900B) available in the sysmocom webshop. Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

5 years, 4 months

← Newer
1
...
9
10
11
12
13
14
15
...
199
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel