baseband-devel

baseband-devel@lists.osmocom.org

1981 discussions

Announcement of "OsmoDevCall" on April 23, 2021

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at April 23, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation by horiz0n: "YIG & YANG (Yet ANother yiG driver)" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Presentation Abstract: This talk will briefly introduce the working principles of YIG (Yttrium Iron Garnet) microwave circuits, their applications and finally conclude with a presentation of a recently developed driver circuit. Attendance is free of charge and open to anyone with an interest in Osmocom. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - 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, 2 months

Announcement of "OsmoDevCall" on April 9, 2021

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at April 9, 2021 at 20:00 CET at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation: pySim-shell - the next generation of pySim 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call Presentation Abstract: For more than a decade, pySim-prog has been the tool to configure/program SIM cards in research/lab/private cellular networks. Originally designed for very simplistic GSM-only SIM Cards, it was extended again and again to cover more use cases and parameters. There is a limit as to how far one can go with stuffing everything into command line arguments. In 2021, pySim-shell was created as the next generation tool. It features interactive navigation around the file system, editing capabilities, backup and restore of all [known] files, ... Attendance is free of charge and open to anyone with an interest in Osmocom. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - 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, 2 months

Unable to build layer23/src/mobile

by Babar Ali

Hi I am trying to build osmocombb on Ubuntu 18.04 with GCC-4.9 & arm-elf-gcc-4.5.2, I am getting the following error, how do I fix this issued. Making all in mobilemake[3]: Entering directory '/root/trx/src/host/layer23/src/mobile' CCLD mobilelibmobile.a(gsm322.o): In function `memset':/usr/include/x86_64-linux-gnu/bits/string_fortified.h:67: undefined reference to `__warn_memset_zero_len'collect2: error: ld returned 1 exit statusMakefile:379: recipe for target 'mobile' failedmake[3]: *** [mobile] Error 1make[3]: Leaving directory '/root/trx/src/host/layer23/src/mobile'Makefile:325: recipe for target 'all-recursive' failedmake[2]: *** [all-recursive] Error 1make[2]: Leaving directory '/root/trx/src/host/layer23/src'Makefile:350: recipe for target 'all-recursive' failedmake[1]: *** [all-recursive] Error 1make[1]: Leaving directory '/root/trx/src/host/layer23'Makefile:51: recipe for target 'layer23' failedmake: *** [layer23] Error 2 Regards Babar Ali

4 years, 2 months

osmocombb make error

by Babar Ali

Hi all, I am facing problem while compiling osmocombb on Ubuntu 18.04, i have tried libosmocore 0.9.0 / 1.1.0 but no luck, i have also tried to switch between gcc 4.9, 5, 7, all the time i have received same error, any idea to fix this issue, I have attached error log for reference, please. Regards Babar Ali

4 years, 3 months

Idea for 2021: Regular "OsmoDevCall"

by Harald Welte

Dear Osmocom community, as the pandemic continues and physical meetings are out of the question for the forseeable future, it would be a good idea to have a periodic virtual online meeting of the interested Osmocom community. I was thinking of a format where we would serve two major purposes: 1) technical talks about osmocom relevant topics - ideally current/recent developments * can be pre-recorded to avoid any problems with technical setup, streaming, ... * should ideally have a Q+A session at their initial "airing" during one OsmoDevCall 2) unstructured solicited social event (USSE) * random chat in audio (optionally video) * not recorded, obviously The recording of the technical presentation should then be permanently made available (like the presentations of our prior OsmoCon / OsmoDevCon). Not every OsmoDevCall would neccessarily need the two parts, but I think it would be great if we can make that happen. We could also have e.g. a two-weekly schedule for the USSE and a monthly schedule for the technical presentation. We'd need somebody to volunteer to "manage" the "broadcast" side of this, preferably somebody with at least some prior exposure to online events (like the c3voc). I'm using https://osmocom.org/issues/4928 to collect a tentative list of topics. Feel free to add your ideas there, as well as any comment/ feedback you may have. 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, 3 months

Osmocom Mailing List re-organization

by Harald Welte

Dear Osmocom community, This topic has been past due for way too many years by now: A re-organization of our major mailing lists. I would like to propose the following changes. Pleas let me know if you have any comments or feedback. I'm aware that renaming will mean people have to update their mail filter rules, but I think we're long past the point where the names of some of our lists started to confuse users. == openbsc(a)lists.osmocom.org == * openbsc doesn't exist anymore since OsmoNITB, which is also obsolete * does already cover anything "Osmocom CNI" related * Proposed new name: osmocom-cni(a)lists.osmocom.org == osmocom-net-gprs(a)lists.osmocom.org == This date back to when GPRS was a highly experimental add-on to our GSM code base. This list should simply be merged with openbsc@ as osmocom-cni(a)lists.osmocom.org == simtrace(a)lists.osmocom.org == Historically was created to cover only the simtrace project. We should rename this to osmocom-simcard(a)lists.osmocom.org or something along those lines. I would like to suggest it covers * SIMtrace / SIMtrace2 hardware + firmware * pySim and related tools for working with SIM/USIM/UICC cards * any other information / discussion related to SIM/USIM/UICC cards, like OTA, ARA-M, ... == osmodevcon(a)lists.osmocom.org == This has been a private list for people attending OsmoDevCon I would like to open up list membership to the general public, and ensure it also covers the new OsmoDevCall. We could then have discussions regarding feedback, topics, scheduling, etc. on that list. Maybe rename it to osmocom-events(a)lists.osmocom.org instead? To differentiate: osmocom-event-orga(a)lists.osmocom.org should remain a private list related to organizational / administrative topics of those involved with organizing future events. == nextepc(a)lists.osmocom.org == Should have been renamed to open5gs(a)lists.osmocom.org quite some time ago, I simply forgot about it. My apologies. -- - 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, 4 months

Tonight: OsmocomBBs 11th anniversary party (online, of course)

by Harald Welte

Dear Osmocom community, today marks the 11th birthday of OsmocomBB, which had originally been announced on February 19, 2010 in the following mailing list post: https://lists.osmocom.org/pipermail/baseband-devel/2010-February/000142.html As we missed to properly celebrate the 10th anniversary, I'd like to use the off-by-one occasion to invite anyone interested to a spontaneous online birthday party tonight. As the original announcement was at 19:02:04 UTC, the online meeting today will also start at 19:02:04 UTC (that's roughly 8pm CET for those of us in the EU) at https://meet.sysmocom.de/OsmocomBB (password: Calypso) I know it's very shot notice, but I still thought it's a good idea, let's see whom of the past or current developers and users will be joining. There's no structure, presentation or anything. Just some USSE (Unstructured Supplementary Social Event). 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, 4 months

LimeSDR output power during GSM set up

by Mario Lucas

Dear forum, I am setting / running GSM network with LimeSdr and Osmo-packgaes: osmo-bts-trx osmo-bsc osmo-hlr osmo-msc osmo-pcu osmo-stp osmo-trx-lms and as i understand the only option to vary / set up output power is through the → osmo-bsc → trx 0 nominal power 23 ! to use full TRX power, set max_power_red 0 max_power_red 20 So does this mean that 23-20=3 dbm? With this set up i instruct LimeSDRmini to transmit 3dbm signal into the air? If so — when i brought phone just into the very vicinity of LimeSDR antena (touching phone and SDR antena) on my smartphone screen i got signal -60 dbm …why did i get such a low figure ? Also if you know is there any supporting application / software that can tell at what dBm LimeSDRmini is sending RF into air? -- Mario Lucas

4 years, 6 months

trx output power config in bts

by Mario Lucas

Dear team could you pls help me with this question In bts config we have following entries: trx 0 nominal power 23 ! to use full TRX power, set max_power_red 0 max_power_red 20 and osmotrx tx-attenuation (oml|<0-50>) So why do we need these «max_power_red 20» and «osmotrx tx-attenuation» which both as i understand weaken the signal? If we want to have a weak signal why we just don’t use only «nominal power» with whatever weak or strong signal value we want? -- Mario Lucas

4 years, 6 months

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, 7 months

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel