baseband-devel

baseband-devel@lists.osmocom.org

2022 discussions

Re: random net disconn. - o2 germany - motorola c123 + c140
by Stefan Bauer 10 Jan '12

10 Jan '12

-----Ursprüngliche Nachricht----- Von: Sylvain Munaut <246tnt(a)gmail.com> > I didn't change anything, I just compiled the git. > > For some unknown reason, some ARM toolchain produce "half working" > binaries ... we have no idea why that happens. For me, i'm happy now as i can debug and test this gsm stuff further. thank you again. > What's the toolchain you use ? Well, i just used the following sources and put them together: wget http://www.gnuarm.com/binutils-2.17.tar.bz2 wget http://www.gnuarm.com/gcc-4.1.1.tar.bz2 wget http://www.gnuarm.com/newlib-1.14.0.tar.gz wget http://www.gnuarm.com/insight-6.5.tar.bz2 wget http://ftp.gnu.org/gnu/gdb/gdb-6.7.tar.bz2 According to some german howto from here: http://www.alphapogo.de/ > Could you send be the binary you compiled ? Sure - please find the binary here: http://www.plzk.de/layer1.compalram.bin 4479603075372ce89c215178a9ad48f3 layer1.compalram.bin Stefan

2 1

Re: random net disconn. - o2 germany - motorola c123 + c140
by Stefan Bauer 10 Jan '12

10 Jan '12

-----Ursprüngliche Nachricht----- Von: Sylvain Munaut <246tnt(a)gmail.com> Gesendet: Mo 09.01.2012 14:12 Betreff: Re: random net disconn. - o2 germany - motorola c123 + c140 An: Stefan Bauer <stefan.bauer(a)cubewerk.de>; CC: baseband-devel(a)lists.osmocom.org; > > thank you for your time. Here is the L1-log: > > > > http://www.plzk.de/layer1.log > > Could you retry with this layer1 firmware : > > http://minus.com/mdAV5dFRb I just tried it. No luck. It seems, that this FW lacks TX-support? http://www.plzk.de/layer1-newFW.log Stefan

2 1

AW: random net disconn. - o2 germany - motorola c123 + c140
by Stefan Bauer 10 Jan '12

10 Jan '12

-----Ursprüngliche Nachricht----- Von: Sylvain Munaut <246tnt(a)gmail.com> Gesendet: Mo 09.01.2012 12:37 Betreff: Re: random net disconn. - o2 germany - motorola c123 + c140 An: Stefan Bauer <stefan.bauer(a)cubewerk.de>; CC: baseband-devel(a)lists.osmocom.org; > > Is it possible, that i miss an important part in my setup? To be honest, i > followed quite strictly all the informations in the public wiki. > > Post the L1 logs (from osmocon) ... because the log you post contain > no low level information whatsoever (those happen on the phone and not > on the pc software). thank you for your time. Here is the L1-log: http://www.plzk.de/layer1.log Stefan

2 1

AW: random net disconn. - o2 germany - motorola c123 + c140
by Stefan Bauer 09 Jan '12

09 Jan '12

-----Ursprüngliche Nachricht----- Von: Stefan Bauer <stefan.bauer(a)cubewerk.de> > I moved closer to the cell. I got associated to the cell with much better > quality. Then the channel switch was initiated by the software - without luck - > logs attached: I tested another provider. This time Vodafone. The rx-quality is even better: (my cell #33 is -64) <0004> gsm322.c:4783 Measurement result for ARFCN 16: -95 <0004> gsm322.c:4783 Measurement result for ARFCN 20: -93 <0004> gsm322.c:4783 Measurement result for ARFCN 21: -96 <0004> gsm322.c:4783 Measurement result for ARFCN 22: -92 <0004> gsm322.c:4783 Measurement result for ARFCN 25: -92 <0004> gsm322.c:4783 Measurement result for ARFCN 33: -64 <0004> gsm322.c:4783 Measurement result for ARFCN 34: -84 <0004> gsm322.c:4783 Measurement result for ARFCN 43: -87 <0004> gsm322.c:4783 Measurement result for ARFCN 44: -86 <0004> gsm322.c:4783 Measurement result for ARFCN 48: -81 <0004> gsm322.c:4783 Measurement result for ARFCN 49: -94 <0004> gsm322.c:4783 Measurement result for ARFCN 82: -94 <0004> gsm322.c:4783 Measurement result for ARFCN 86: -74 <0004> gsm322.c:4783 Measurement result for ARFCN 87: -93 <0004> gsm322.c:4783 Measurement result for ARFCN 88: -92 <0004> gsm322.c:4783 Measurement result for ARFCN 95: -92 <0004> gsm322.c:4783 Measurement result for ARFCN 123: -84 <0004> gsm322.c:4783 Measurement result for ARFCN 124: -79 <0004> gsm322.c:4691 RLA_C of serving cell: -55 <0004> gsm322.c:374 A (RLA_C (-55) - RXLEV_ACC_MIN (-106)) = 51 <0004> gsm322.c:376 B (MS_TXPWR_MAX_CCH (33) - p (33)) = 0 <0004> gsm322.c:377 C1 (A - MAX(B,0)) = 51 <0004> gsm322.c:400 C2 = C1 - CELL_RESELECT_OFFSET (0) = 51 (special case) <0004> gsm322.c:4746 #1 ARFCN=33 RLA_C=-64 <0004> gsm322.c:4746 #2 ARFCN=86 RLA_C=-75 <0004> gsm322.c:4746 #3 ARFCN=124 RLA_C=-80 <0004> gsm322.c:4746 #4 ARFCN=48 RLA_C=-82 <0004> gsm322.c:4746 #5 ARFCN=123 RLA_C=-82 <0004> gsm322.c:4746 #6 ARFCN=34 RLA_C=-83 <0004> gsm322.c:4569 Syncing to new neighbour cell 33. For unknown reasons, the sync fails again: <0003> gsm322.c:469 Sync to ARFCN=33 rxlev=-68 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2937 Channel synched. (ARFCN=33, snr=16, BSIC=25) <0001> gsm322.c:2958 using DSC of 90 <0004> gsm322.c:4640 Synced to neighbour cell 33. <0003> gsm322.c:692 Starting CS timer with 2 seconds. <0003> gsm48_rr.c:4941 Channel provides data. <0001> gsm48_rr.c:1887 New SYSTEM INFORMATION 2 <0001> sysinfo.c:719 New SYSTEM INFORMATION 3 (mcc 262 mnc 01 lac 0x430a) <0001> gsm48_rr.c:2012 Changing CCCH_MODE to 1 <0003> gsm322.c:702 stopping pending CS timer. <0003> gsm322.c:2567 Relevant sysinfo of neighbour cell is now received or updated. <0004> gsm322.c:4661 Read from neighbour cell 33 (rxlev -68). <0004> gsm322.c:4569 Syncing to new neighbour cell 86. <0003> gsm322.c:469 Sync to ARFCN=86 rxlev=-78 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2980 Channel sync error, try again <0003> gsm322.c:469 Sync to ARFCN=86 rxlev=-78 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=86 <0004> gsm322.c:4640 Failed to sync to neighbour cell 86. <0004> gsm322.c:4569 Syncing to new neighbour cell 124. <0003> gsm322.c:469 Sync to ARFCN=124 rxlev=-83 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2980 Channel sync error, try again <0003> gsm322.c:469 Sync to ARFCN=124 rxlev=-83 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=124 <0004> gsm322.c:4640 Failed to sync to neighbour cell 124. <0004> gsm322.c:4569 Syncing to new neighbour cell 48. <0003> gsm322.c:469 Sync to ARFCN=48 rxlev=-83 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2980 Channel sync error, try again <0003> gsm322.c:469 Sync to ARFCN=48 rxlev=-83 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=48 <0004> gsm322.c:4640 Failed to sync to neighbour cell 48. <0004> gsm322.c:4569 Syncing to new neighbour cell 123. <0003> gsm322.c:469 Sync to ARFCN=123 rxlev=-85 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2980 Channel sync error, try again <0003> gsm322.c:469 Sync to ARFCN=123 rxlev=-85 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=123 <0004> gsm322.c:4640 Failed to sync to neighbour cell 123. <0004> gsm322.c:4569 Syncing to new neighbour cell 34. <0003> gsm322.c:469 Sync to ARFCN=34 rxlev=-86 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2980 Channel sync error, try again <0003> gsm322.c:469 Sync to ARFCN=34 rxlev=-86 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=34 <0004> gsm322.c:4640 Failed to sync to neighbour cell 34. <0004> gsm322.c:4122 Re-select using access class with Emergency class. <0004> gsm322.c:4142 Checking cell of ARFCN 33 for cell re-selection. <0004> gsm322.c:374 A (RLA_C (-64) - RXLEV_ACC_MIN (-106)) = 42 <0004> gsm322.c:376 B (MS_TXPWR_MAX_CCH (33) - p (33)) = 0 <0004> gsm322.c:377 C1 (A - MAX(B,0)) = 42 <0004> gsm322.c:400 C2 = C1 - CELL_RESELECT_OFFSET (0) = 42 (special case) <0004> gsm322.c:4198 -> Cell of is in the same LA, so CRH = 0 <0004> gsm322.c:4142 Checking cell of ARFCN 86 for cell re-selection. <0004> gsm322.c:4164 Skip cell: There are no system informations available. <0004> gsm322.c:4142 Checking cell of ARFCN 124 for cell re-selection. <0004> gsm322.c:4164 Skip cell: There are no system informations available. <0004> gsm322.c:4142 Checking cell of ARFCN 48 for cell re-selection. <0004> gsm322.c:4164 Skip cell: There are no system informations available. <0004> gsm322.c:4142 Checking cell of ARFCN 123 for cell re-selection. <0004> gsm322.c:4164 Skip cell: There are no system informations available. <0004> gsm322.c:4142 Checking cell of ARFCN 34 for cell re-selection. <0004> gsm322.c:4164 Skip cell: There are no system informations available. <0004> gsm322.c:4624 Syncing back to serving cell <0003> gsm322.c:463 Sync to ARFCN=46 rxlev=-56 (Sysinfo, ccch mode NON-COMB) <0001> gsm48_rr.c:679 MON: no cell info <0003> gsm322.c:2980 Channel sync error, try again <0003> gsm322.c:463 Sync to ARFCN=46 rxlev=-56 (Sysinfo, ccch mode NON-COMB) <0003> gsm322.c:2980 Channel sync error, try again <0003> gsm322.c:463 Sync to ARFCN=46 rxlev=-56 (Sysinfo, ccch mode NON-COMB) <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=46 <0003> gsm322.c:3005 Unselect cell due to sync error! <0003> gsm322.c:498 Unselecting serving cell. <0003> gsm322.c:3072 Loss of CCCH, Trigger re-selection. <0003> gsm322.c:4035 (ms 1) Event 'EVENT_CELL_RESEL' for Cell selection in state 'C7 camped on any cell' <0003> gsm322.c:823 new state 'C7 camped on any cell' -> 'C8 any cell re-selection' <0003> gsm322.c:4334 Checking cell with ARFCN 33 for cell re-selection. (C2 = 42) <0003> gsm322.c:4334 Checking cell with ARFCN 86 for cell re-selection. (C2 = 0) <0003> gsm322.c:4345 Skip cell: not suitable and/or allowable. <0003> gsm322.c:4334 Checking cell with ARFCN 124 for cell re-selection. (C2 = 0) <0003> gsm322.c:4345 Skip cell: not suitable and/or allowable. <0003> gsm322.c:4334 Checking cell with ARFCN 48 for cell re-selection. (C2 = 0) <0003> gsm322.c:4345 Skip cell: not suitable and/or allowable. <0003> gsm322.c:4334 Checking cell with ARFCN 123 for cell re-selection. (C2 = 0) <0003> gsm322.c:4345 Skip cell: not suitable and/or allowable. <0003> gsm322.c:4334 Checking cell with ARFCN 34 for cell re-selection. (C2 = 0) <0003> gsm322.c:4345 Skip cell: not suitable and/or allowable. <0003> gsm322.c:4372 Best neighbour cell with ARFCN 33 selected. (normal priority) <0003> gsm322.c:4405 Scanning ARFCN 33 of neighbour cell during cell reselection. <0003> gsm322.c:469 Sync to ARFCN=33 rxlev=-68 (No sysinfo yet, ccch mode NONE) <0005> gsm48_mm.c:4329 (ms 1) Received 'MM_EVENT_LOST_COVERAGE' event in state MM IDLE, limited service <0005> gsm48_mm.c:1059 Selecting PLMN SEARCH state, because no cell selected. <0005> gsm48_mm.c:912 new MM IDLE state limited service -> PLMN search Is it possible, that i miss an important part in my setup? To be honest, i followed quite strictly all the informations in the public wiki. Stefan

2 1

AW: random net disconn. - o2 germany - motorola c123 + c140
by Stefan Bauer 09 Jan '12

09 Jan '12

-----Ursprüngliche Nachricht----- Von: Stefan Bauer <stefan.bauer(a)cubewerk.de> > I'm gonna try to move closer to the BTS tomorrow and collect some informations. > If the quality stays poor, i can only attach an additional antenna to the phone. Ok - here is the status - not quite surprising: I moved closer to the cell. I got associated to the cell with much better quality. Then the channel switch was initiated by the software - without luck - logs attached: http://www.plzk.de/mobile2.log Any idea why the channel sync fails several times and even the fallback switch to the serving cell at the end? I have doubts that it is an antenna/RX-issue. If i use the motorola with original firmware, i have no issues and can immediately start a phone-call. Thank you in advance Stefan

1 0

Re: random net disconn. - o2 germany - motorola c123 + c140
by Stefan Bauer 09 Jan '12

09 Jan '12

-----Ursprüngliche Nachricht----- Von: Harald Welte <laforge(a)gnumonks.org> > Are you sure your other phones are using O2 in GSM mode, not 3G? It > could be that the other phones use 3G and thus have better coverage > indication. Hi Harald, i have a pretty old nokia phone (6310) and it's only able to do GSM. That was used for my comparison. > > Is it possible, that my provider does not like the random imei-feature > > of osmocom? > > That might very well be, but is completley unrelated to a RF signal > level as it is measured by your phone (which leads to the problem you > are observing). I'm gonna try to move closer to the BTS tomorrow and collect some informations. If the quality stays poor, i can only attach an additional antenna to the phone. Thank you. Stefan

1 0

Re: random net disconn. - o2 germany - motorola c123 + c140
by Stefan Bauer 09 Jan '12

09 Jan '12

-----Ursprüngliche Nachricht----- Von: Holger Hans Peter Freyther <holger(a)freyther.de> Gesendet: So 08.01.2012 17:03 Betreff: Re: random net disconn. - o2 germany - motorola c123 + c140 An: baseband-devel(a)lists.osmocom.org; > On 01/08/2012 04:27 PM, Stefan Bauer wrote: > > > > > PING. Nobody with an idea on my issue? > > What about you? Reading the log, do you see anything that looks weird? E.g. > how likely is it that you simply have bad coverage of O2 for GSM in the area > you are. What do you think about log entries like this? Well, the coverage is perfect with my other cell phones at the exactly same position in my office. Is it possible, that my provider does not like the random imei-feature of osmocom? Is it best practise to use the real sim and not only extracting the key from original sim and fake it? thank you Stefan

2 1

Re: random net disconn. - o2 germany - motorola c123 + c140
by Stefan Bauer 09 Jan '12

09 Jan '12

-----Ursprüngliche Nachricht----- > Hi Peter, > > please find the log-file of mobile here: > > http://www.plzk.de/mobile.log PING. Nobody with an idea on my issue? Regards Stefan

2 1

Re: random net disconn. - o2 germany - motorola c123 + c140
by Stefan Bauer 07 Jan '12

07 Jan '12

-----Ursprüngliche Nachricht----- Von: Peter Stuge <peter(a)stuge.se> Gesendet: Sa 07.01.2012 00:31 Betreff: Re: random net disconn. - o2 germany - motorola c123 + c140 An: baseband-devel(a)lists.osmocom.org; > Stefan Bauer wrote: > > serious problems to keep in my operators network (o2 germany - > > 262 07) longer than a few seconds. > > Can you crank up the logging to max and share the logs from a clean > start of connection through disconnect? Hi Peter, please find the log-file of mobile here: http://www.plzk.de/mobile.log I hope this will bring some light into my problem. Thank you in advance Stefan

1 0

Linux + u-boot port to MT6235
by Marcin Mielczarczyk 07 Jan '12

07 Jan '12

Hi All! That's true, I managed to run U-Boot on MT6235, but linux kernel is not fully functional yet (it's fresh stuff as I managed to ran it on Tuesday and then I was off to conference). For MT6235 development I chose Sciphone G2, which is pretty cheap. After some time I managed to download code to SRAM (just 64KB) using MTK's FlashTool. MTK FlashTool communicates over UART directly with MT6235 bootloader and sends its own chunk of code (about 58KB) which is executed in SRAM and communicates with FlashTool. I found on pudn.com some pack to customize code loaded by FlashTool, thanks to which I could download my own code to SRAM (without JTAG). The problem was that it had to be linked with some security libraries which occupied about 56KB and not much memory left for my own code. Then I decided to try find JTAG pins to get all control on MT6235. That took me sometime, but finally I succeeded. The other bigger issue was initializing DRAM controller to be able to download bigger code (linux kernel + uboot) to external RAM. In sciphone there is problem that all interesting chips are under metal shield which is pretty havily soldered. In this case I couldn't read what kind of RAM memory is mounted without destroying the board (I don't have such soldering machine which could unsolder so big metal shield). Thanks to JTAG I could attach to target and then dump DRAM controller registers from processor running MTK's software, but setting these values after processor start and configuration of PLL didn't work. I decided to disassemble bootloader which could show me how DRAM controller is initialized and how code fron NAND is loaded (to be able to flash U-Boot and kernel to NAND so MT6235 will start my code automatically and I will not have to use JTAG). Currently I have knowledge how internal MT6235 bootloader is loading code from memory during startup and I also extracted procedure of DRAM controller initialization. Thanks to that I'm able to run U-Boot from the very begining of processor startup. The problem is that I have just one piece of Sciphone G2 and I don't want to flash it yet to not break existing code in it. Thanks to running device I'm able to attach with JTAG and check how peripherals are configured (i.e. LCD, MMC, etc.). I have backup of flash, but I'm not 100% sure if I will flash it back, phone will startup. That's why I bought second piece of Sciphone G2 and should receive it today or on Tuesday (this Monday is holiday in Poland). In this case I'll flash U-Boot to NAND and try to make it working. Then we could load the rest of code from U-Boot (to RAM or NAND over serial). You can see how my setup looks on attached picture. The good thing about it is that the same bootloader is used in MT622x, so it should be fairly easy to do the same on phones based on that SoCs (but unfortuantely it's just ARM7). If it comes to code, of course I can share it on "git.osmocom.org". Currently it's just basic port of U-Boot and not much for linux kernel, but I'm working on this now so I'll push it when it'll be ready. Currently I'm working on driver for NAND memory for U-Boot, so we could flash linux kernel. When that will be ready I'll push the code. Then I'll switch to linux kernel and when it'll be functional I also push the code. At this stage you will not need to have JTAG and you could load the code over serial in U-Boot. If it comes to GSM I didn't work with it before. I actualy worked 6 months in L2/3 team for LTE (on RRC) but it's different story. That could be really outstanding thing if we could run first phone ever with whole code open (from BB up to APP). BR, Marcin

13 37

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel