baseband-devel

baseband-devel@lists.osmocom.org

1 participants
2024 discussions

Bezahlen Sie die Rechnung 91145445088561
by OpenBSC 05 Jun '18

05 Jun '18

Guten Morgen , in der Anlage sende ich Ihnen den unterzeichneten Vertrag. Die Rechnung wird zur Zahlung vorbereitet und ist unter dem folgenden Link verfügbar. >>> http://hbmonte.com/DOC/Rechnungszahlung-Nr050648/ Herzliche Grüße, OpenBSC

1 0

mobile and triggering UL while in state C7/A4?
by Holger Freyther 29 May '18

29 May '18

Hey, so while trying to load test a system (using virtual-phy, osmo-bts-virtual) I noticed that the average time for the first UL to succeed is quite high. After some digging it turns out it is the "mobile" behavior and not the RAN. The nice thing about mobile is it tries to follow the GSM state machines, the bad thing is I don't know what the correct behavior is! What happens (ignoring that most of it is async)? * mobile starts * PLMN search starts * For some bad luck no arfcn is found. * The system enters the C6 state * It makes another search, finds an arfcn, selects a cell, starts a timer, C7 state entered * An UL is attempted and blocked by "mobile" (GSM322_EVENT_REG_FAILED sent) * The any timer times out (30s, statically initialized) * PLMN search starts * A cell is found... * ... * An UL is attempted and not blocked. Compressed logs: <0003> gsm322.c:834 new state 'PLMN search' -> 'C0 null' <0002> gsm322.c:3823 (ms 00003) Event 'EVENT_PLMN_SEARCH_END' for automatic PLMN selection in state 'A0 null' .. <0002> gsm322.c:811 new state 'A0 null' -> 'A4 wait for PLMN to appear' <....> <0003> gsm322.c:834 new state 'C6 any cell selection' -> 'C0 null' <0002> gsm322.c:3823 (ms 00003) Event 'EVENT_NO_CELL_FOUND' for automatic PLMN selection in state 'A4 wait for PLMN to appear' <...> <0005> gsm48_mm.c:4312 (ms 00003) Received 'MM_EVENT_NO_CELL_FOUND' event in state MM IDLE, no cell available <0003> gsm322.c:479 Sync to ARFCN=514(DCS) rxlev=-63 (No sysinfo yet, ccch mode NONE) ... <0003> gsm322.c:2719 Received relevant sysinfo. <0003> gsm322.c:713 stopping pending CS timer. ... <000e> gsm322.c:3415 Camping on any cell (ARFCN=514(DCS) mcc=001 mnc=01 Test, Test) <0003> gsm322.c:725 Starting 'any cell selection' timer with 30 seconds. <0003> gsm322.c:834 new state 'C6 any cell selection' -> 'C7 camped on any cell' <0005> gsm48_mm.c:4312 (ms 00003) Received 'MM_EVENT_CELL_SELECTED' event in state MM IDLE, no cell available <0005> gsm48_mm.c:905 new MM IDLE state no cell available -> location updating needed <0005> gsm48_mm.c:905 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:2228 Loc. upd. not allowed. <---- dropped!!! <0002> gsm322.c:3823 (ms 00003) Event 'EVENT_REG_FAILED' for automatic PLMN selection in state 'A4 wait for PLMN to appear' <0002> gsm322.c:3830 Event unhandled at this state. <...> 30s timeout here.. <0003> gsm322.c:3307 'Any cell selection timer' timed out. Starting special search to find allowed PLMNs. <0003> gsm322.c:834 new state 'C7 camped on any cell' -> 'ANY search' What do the specs say? GSM 03.22 define the C states (and refers to 05.08): • C6 Any Cell Selection - This is where the MS is unable to camp normally on any cell of the selected PLMN, or cannot obtain service because of certain responses to a location registration (LR) attempt. It is searching for a cell of any PLMN to camp on (so that emergency calls can be made). • C7 Camped on any Cell - This is where the MS has camped on a cell irrespective of its PLMN identity, so that emergency calls can be made. 3gpp 23.122 defines the A states: • A4 Wait for PLMNs to appear - There are no allowable and available PLMNs at present and the MS is waiting for one to appear. GSM 05.08: For the cell selection, the MS shall be able to select the correct (fourth strongest) cell and be able to respond to paging on that cell within 30 seconds of switch on, when the three strongest cells are not suitable. This assumes a valid SIM with PIN disabled and ideal radio conditions. This requirement is not applicable for multi-RAT mobile stations. The tolerance on all the timing requirements in clause 6 is ± 10 %, except for PENALTY_TIME where it is ± 2 s. What makes sense: Unfortunately the commit adding the check to gsm48_mm_loc_upd_normal doesn't answer why in specific this was done. Given the GSM 05.08 the timeout of 30s seems too high by itself. As a first approximation I intend to make it configurable. I am not sure how to fix as I don't find the spec reference. Do you? One constraint of GSM 03.22 is to save battery when not finding a network but I don't find a clear answer when to leave C7. In GSM 05.08 I couldn't find what I was searching for either. So maybe power scans are better than attempting a UL but maybe we can try to do a UL earlier if the "any" PLMN looks like our HPLMN? Or do gsm48_mm_loc_upd_normal when in GSM322_C7_CAMPED_ANY_CELL.. What do you think? holger

1 0

OsmoCon 2018 CfP / submit your topic[s] *now* !
by Harald Welte 25 May '18

25 May '18

Dear Osmocom community, one of the main difficulty with OsmoCon 2017 last year was that nobody submitted talks / discussions within the deadline, early enough to allow for proper planning. This lead to the situation where the sysmocom team had to come up with a schedule/agenda on their own. Later on *much after the CfP deadline*, people then squeezed in talks, making the overall schedule too full. It is up to you to avoid this situation again in 2018 by submitting your talk *RIGHT NOW*. We will be very strict regarding late submissions. So if you would like to shape the Agenda of OsmoCon 2018, this is your chance. Please use it. We will have to create a schedule soon, as [almost] nobody will register to a conference unless the schedule is known. If there's not sufficient contribution in terms of CfP response from the wider community, don't complain later that 90% of the talks are from sysmocom team members and only about the Cellular Network Infrastructure topics. You have been warned. Please make your CfP submission in time at https://pretalx.sysmocom.de/osmocon2018/cfp before the CfP deadline on *2018-05-30 23:59 (Europe/Berlin)* Thanks for your kind attention. Looking forward to meet with the community at OsmoCon 2018 in October. 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)

1 0

Calypso Image
by Nikos Balkanas 24 May '18

24 May '18

Hi, I've downloaded Calypso's image. I would like to study it. Who did the analysis and what tools did he used for it in http://osmocom.org/projects/baseband/wiki/HardwareCalypsoDSP? TIA Nikos

2 5

Bad crc
by messiah 18 May '18

18 May '18

Hey thereAlready days working on osmocom...At last my compiler worked out on firmware bin's compilation. So now i start with loader, all fine. But when i was uploading loader from phone there was some issues like "bad crc" in all lines. I noticed that it created file like 8kb in src dir, so to be sure i checked other guys on web, they have same size of that file. So i decided to continue and after i erased 0x01000 page i tried to reupload that file back to check but it saying bad crc and aborting. Hope its not critical for menu loading, which will used for layer1, rssi, etc.? Can somebody share with me that native loader bin file, in case? -- Sent from: http://baseband-devel.722152.n3.nabble.com/

1 0

osmocom-bb compilation problems
by Nikos Balkanas 17 May '18

17 May '18

Hi, I've been following the installation directions from the wiki, Getting Started. After generating the arm-none-eabi toolchain, I proceeded with make. I get errors over system files: In file included from /usr/include/x86_64-linux-gnu/sys/socket.h:26:0, from /usr/include/netinet/in.h:23, from /usr/include/arpa/inet.h:22, from l1ctl.c:29: /usr/include/x86_64-linux-gnu/sys/uio.h: In function ‘readv’: /usr/include/x86_64-linux-gnu/sys/uio.h:40:3: error: expected declaration specifiers before ‘__wur’ __wur; ^ /usr/include/x86_64-linux-gnu/sys/uio.h:51:3: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__wur’ __wur; ^ These includes are system files and test out fine in my programs. Any idea what's going on? TIA Nikos

5 16

Osmocon
by Nikos Balkanas 15 May '18

15 May '18

Hi, To run osmocom-bb I need to install and use osmocon. Can't find it in git repos. Where is it hiding? TIA Nikos

4 8

osmocom-bb installation help
by Nikos Balkanas 14 May '18

14 May '18

Hi, I am new to this list. I use ubuntu 14.04.02. I am trying to configure/compile latest master osmocom-bb. I ran into a few problems/questions: According to the src/README.building file, I should get the arm toolchain from gnuarm.com This should be updated, gnuarm.com doesn't have any downloads any more. Instead I installed gcc-arm-linux-gnueabi from ubuntu reps 1) normal gcc seems to support x-compiling for arm CPUs. Why not use that? 2) Your stock Makefile tests for CROSS_HOST against arm-elf-gcc. This should be updated to test also against arm-linux-gnueabi-gcc from gcc-arm-linux-gnueabi package 3) configure warnings: configure: WARNING: unrecognized options: --disable-tests, --disable-tests. Should be disabled if not supported any more checking for arm-linux-gnueabi-mt... no checking for mt... mt configure: WARNING: using cross tools not prefixed with host triplet Is there a problem to use the OS mt? 4) configure asks for libosmovty >= 0.10.0. libosmovty is part of libosmocore. Latest libosmocore master provides libosmovty 0.9.0.16-abc4:( These 2 should really be synchronized. Where can I find suitable libosmocore to work with latest osmocom-bb, or latest osmocom-bb that works with latest libsomocore? TIA, Nikos

3 4

Re: osmocom-bb installation problems
by Neels Hofmeyr 14 May '18

14 May '18

On Sat, May 12, 2018 at 11:35:51AM +0300, Nikos Balkanas wrote: > Dear Harald, > > It was already pointed out to me, by Craig, that I was using the wrong > list:( > I was using this list, because osmocom-bb configure told me so, in each > warning:( Hmm, might be worth a patch. > Already have moved thread to baseband-devel. > I arrived at this conclusion probably because git clone libosmocore (master > branch), > gives me libosmovty 0.9.0.16:( > Will check out your link. If you are building from source: the git tagged version is put in a file called .version. Sometimes I needed to remove that manually and start from scratch (autoreconf -fi; configure) to get a newer version. Maybe that helps? ~N

2 1

[HELP]: Traffic Channels in OsmocomBB
by Keval Prajapati 10 May '18

10 May '18

Dear All, Is anyone is there, who can help me with Traffic channels of GSM in OscmocomBB. I want to know that how may traffic channels (Speech & Data) of GSM are supported in the OsmocomBB? Regards, Keval Pankhaniya

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel