- baseband-devel - lists.osmocom.org

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

09 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 09 Jan '12

09 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 09 Jan '12

09 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 08 Jan '12

08 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 08 Jan '12

08 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 08 Jan '12

08 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

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

07 Jan '12

Dear developers and users, i would like to know the current status of osmocom-bb on the motorola c123 and c140. I have both phones available and serious problems to keep in my operators network (o2 germany - 262 07) longer than a few seconds. I'm using my real sim (sim reader) but the quality seems to be very poor with that kind of devices. Are there any known problems? With several other devices (non osmocom firmware) and the same sim i have no problems at the same location. thanks in advance Stefan

2 1

Newbie DSP Questions
by Avner Ezra 05 Jan '12

05 Jan '12

Hi I'm newbie in DSP and SDR, but I'm really interested in this matter and I want to learn. I have bunch of questions which has short answers, if you can please answer them in easy terms and words, so I can understand them well. I hope this thread will help a lot of other newbies to understand DSP stuff better. I have a Linux with every needed tools like osmocomm, gnuradio, openbts, kalibrate, uhd drivers, ... and USRP N210 hardware ready. Everything works normal and well. A) Sometimes when I scan a network bandwidth like GSM1800 using kalibrate, I see some channels like 820, 538, etc. When I re-scan, I cannot find them. Does this mean that kalibrate finds a channel when a mobile handset has a live conversation or sms send or receive in progress? or what? B) I want to wideband capture for example 125 ARFCN. It needs 25MHz bandwidth which USRP N210 can handle and stream it easily. Even AFAIK I can double this number and capture 250 ARFCN using single N210 (50MHz, in USRPN210 data sheet it says it's capable of streaming 50MHz wide signals). How can I wideband capture 125 ARFCNs? I tried to do it using: ./uhd_rx_cfile.py -f `arfcncalc -a 512 -b 1800 -d` --samp-rate=25000000 -N 200000000 -g 70 b1.cfile What I understood and decided to write such command above: B-1) arfcncalc calculates frequency of first GSM1800 channel (512 ARFCN) which is start point (in above command) B-2) Sampling Rate is the bandwidth I want to capture, in our case it's 25MHz means 125 ARFCN which each ARFCN has 200kHz bandwidth B-3) 200M samples will be received (-N parameter) B-4) Gain value is 70, means it will boost antennas to maximum power to receive signals, I think USRPN210 max. gain is 80 B-5) My decimation rate here using 25M sampling rate and USRP N210 which has 100MHz ADC, will be 4. So if I decided to read cfile I have to use 4 as decimation rate. Please explain and tell me if I'm correct or wrong about above statements. Does this will work and I'll have a 125 ARFCN from 512 to 637 ARFCNs captures into b1.cfile? If so why in http://gnuradio.org/doc/doxygen-3.4/classusrp__source__base.html#adf8529d74… documentation, it says set_rx_freq should set center of frequency, so for example if you want to capture from 512 to 637, you should set frequency to frequency of ARFCN 574? C) How can I seperate and process 200khz by 200khz channels in wideband captured file? Thank you so much for your time Your help and answers will solve problem of a lot of newbies like me. Best Wishes

4 4

phones are not working
by Akib Sayyed 04 Jan '12

04 Jan '12

hello guys i am facing problem with registering phone on network what i am using cellphone: motorola c139 cable : FDTI FT232RL cable given on ccc aug ++++++++++++++++++++++++++++++++++++++++ command used to load ./host/osmocon/osmocon -m c140xor -p /dev/ttyUSB0 -c ./target/firmware/board/compal_e86/layer1.highram.bin ./target/firmware/board/compal_e86/chainload.compalram.bin ++++++++++++++++++++++++++++++++++++++++ show ms 1 command o/p MS '1' is up, MM connection active IMEI: 000000000000000 IMEISV: 0000000000000000 IMEI generation: fixed automatic network selection state: A1 trying RPLMN MCC=404 MNC=90 (India, AirTel) cell selection state: connected mode 1 ARFCN=613(DCS) MCC=404 MNC=90 LAC=0x0c2f CELLID=0x0aa2 (India, AirTel) radio ressource layer state: connection pending mobility management layer state: wait for RR connection (location updating) ++++++++++++++++++++++++++++++++++++++++ other tools tried : celllog works fine ++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++ Other issue details getting error FTM_TOOL error what i am using cellphone: motorola c123 cable : FDTI FT232RL cable given on ccc aug ++++++++++++++++++++++++++++++++++++++++ command used to load ./host/osmocon/osmocon -m c123xor -p /dev/ttyUSB0 ./target/firmware/board/compal_e88/layer1.compalram.bin ++++++++++++++++++++++++++++++++++++++++ here is log of error from c123 root@akib-laptop:~/osmocom_org/osmocom-bb/src# ./host/osmocon/osmocon -m c123xor -p /dev/ttyUSB0 ./target/firmware/board/compal_e88/layer1.compalram.bin got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 04 81 .. got 4 bytes from modem, data looks like: 1b f6 02 00 .... got 1 bytes from modem, data looks like: 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(./target/firmware/board/compal_e88/layer1.compalram.bin): file_size=55840, hdr_len=4, dnload_len=55847 got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 43 C Received PROMPT2 from phone, starting download handle_write(): 4096 bytes (4096/55847) handle_write(): 4096 bytes (8192/55847) handle_write(): 4096 bytes (12288/55847) handle_write(): 4096 bytes (16384/55847) handle_write(): 4096 bytes (20480/55847) handle_write(): 4096 bytes (24576/55847) handle_write(): 4096 bytes (28672/55847) handle_write(): 4096 bytes (32768/55847) handle_write(): 4096 bytes (36864/55847) handle_write(): 4096 bytes (40960/55847) handle_write(): 4096 bytes (45056/55847) handle_write(): 4096 bytes (49152/55847) handle_write(): 4096 bytes (53248/55847) handle_write(): 2599 bytes (55847/55847) handle_write(): finished got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 45 E got 1 bytes from modem, data looks like: 53 S got 1 bytes from modem, data looks like: 16 . Received DOWNLOAD NACK from phone, something went wrong :( got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l 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: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r ^C +++++++++++++++++++++++ Note: phones are locked to perticular provider -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

1 0

[osmocom-bb] [PATCH] Update .gitignore file for libosmocore
by Paul Wise 03 Jan '12

03 Jan '12

--- src/shared/libosmocore/.gitignore | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/src/shared/libosmocore/.gitignore b/src/shared/libosmocore/.gitignore index c77c750..5e75539 100644 --- a/src/shared/libosmocore/.gitignore +++ b/src/shared/libosmocore/.gitignore @@ -50,3 +50,6 @@ doc/html.tar src/crc*gen.c include/osmocom/core/crc*gen.h + +build-host +build-target -- 1.7.7.3

2 4

R: GPRS decode tutorial
by Luca Bongiorni 02 Jan '12

02 Jan '12

Hi Dario, i suggest you to download the last Sylvain's burst_ind, because is improved of some features and patch it manually with Nohl's patch. Then you will be able to dump the bursts using ccch_scan, instead of layer23. Cheers, Luca > Can someone drive me to the right direction? P.S: http://comments.gmane.org/gmane.comp.mobile.osmocom.baseband.devel/1754

3 2

Re: Compling pb with Ubuntu 11.04 64 bits
by Holger Hans Peter Freyther 01 Jan '12

01 Jan '12

On 01/01/2012 03:34 PM, Eric Tyberghien wrote: > Hi all > Hi Gustav, it is your third mail (one private, two to the list) but it is sadly not much of a dialogue. There is nothing wrong with Ubuntu 11.10 (11.04...) but apparently you changed more than jut 11.10 -> 11.04. From the little information you provide one can see you at least changed the place where you keep the sourcecode. So please keep your environment stable because otherwise you wasted the time of the ones that were kind enough to respond. So the path to success: 1.) Think, try to understand what happens 2.) Provide context when you are writing an email, what do you do, why do you do this? what you think should happen 3.) include complete output.... In this specific case: Find where the sourcecode of msgb_free is (the answer will be msgb.c), find the msgb.o (compiled object file) that was compiled for ARM. Look if there is a msgb_free in it (objdump,nm..) or if there is something wrong with this file (ls, file, readelf). My guess is that you did something funny during compile and ended up with a zero byte msgb.o. cheers holger

1 0

Compling pb with Ubuntu 11.04 64 bits
by Eric Tyberghien 01 Jan '12

01 Jan '12

Hi all I'll upgrade a Ubuntu 11.04 64 bits to 11.10 and it seems something was wrong. Now I have reinstall an "old" Ubuntu 11.04 64 bits from scratch and the compile process is fairly better but I obtain this failure : apps/hello_world/main.o: In function `console_rx_cb': apps/hello_world/main.c:59: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `sercomm_alloc_msgb': ../../shared/libosmocore/include/osmocom/core/msgb.h:330: undefined reference to `msgb_alloc' comm/libcomm.a(sercomm.o): In function `sercomm_drv_rx_char': comm/sercomm.c:246: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `dispatch_rx_msg': comm/sercomm.c:227: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `sercomm_drv_pull': comm/sercomm.c:161: undefined reference to `msgb_dequeue' comm/sercomm.c:188: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `sercomm_sendmsg': comm/sercomm.c:125: undefined reference to `msgb_enqueue' comm/libcomm.a(sercomm_cons.o): In function `msgb_alloc_headroom': ../../shared/libosmocore/include/osmocom/core/msgb.h:330: undefined reference to `msgb_alloc' make[1]: *** [board/compal_e88/hello_world.compalram.elf] error 1 make[1]: Leaving directory `/srv/osmocom-bb/src/target/firmware' make: *** [firmware] error 2 Any idea Regards

1 0

Re: Compiling failure with Ubuntu 11.10 64 bits
by Holger Hans Peter Freyther 01 Jan '12

01 Jan '12

On 01/01/2012 12:45 AM, Eric Tyberghien wrote: > Hi all > The config.log file is like that I think the relevant part is not in the log file. Put it somewhere and post a link, or preferable go through it yourself once more. Are you sure that autoconf/automake deal well with the encoding of your accents in the directories? thanks

1 0

Re: Compiling failure with Ubuntu 11.10 64 bits
by Peter Stuge 01 Jan '12

01 Jan '12

Eric Tyberghien wrote: > I'm using Ubuntu 11.10 64 bits and I try to compile osmocom-bb but > it fails due to the enable-linker-buid-id option not supported by > the ld linker How do you come to that conclusion? > make[1]: quittant le répertoire « > /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target » Please keep in mind to always export LANG=C LC_ALL=C when posting output, so that there are no translations from english which both make everything more difficult to understand and usually also are very very bad translations. Never send localized output unless asking on a local-only mailing list. > cd shared/libosmocore/build-host && ../configure Who runs this command? You or make? > checking whether the C compiler works... no > configure: error: in > `/home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-host': > configure: error: C compiler cannot create executables > See `config.log' for more details > make: *** [sharedroland(a)redhat.com> > /libosmocore/build-host/Makefile] Erreur 77 .. > $ ./configure configure -v --with-pkgversion=Ubuntu/Linaro 4.6.1-9ubuntu3 > --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs > --enable-languages=c,c++,fortran,objc,obj-c++,go --prefix=/usr > --program-suffix=-4.6 --enable-shared --disable-linker-build-id > --with-system-zlib --libexecdir=/usr/lib --without-included-gettext > --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 > --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu > --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin > --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic > --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu > --target=x86_64-linux-gnu Who is running the above and why? > configure:2839: checking for x86_64-linux-gnu-gcc > configure:2855: found /usr/bin/x86_64-linux-gnu-gcc So this is the compiler that would be used. > Thread model: posix > gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) > configure:3155: $? = 0 > configure:3144: x86_64-linux-gnu-gcc -V >&5 > x86_64-linux-gnu-gcc: error: unrecognized option '-V' > x86_64-linux-gnu-gcc: fatal error: no input files > compilation terminated. > configure:3155: $? = 4 > configure:3144: x86_64-linux-gnu-gcc -qversion >&5 > x86_64-linux-gnu-gcc: error: unrecognized option '-qversion' > x86_64-linux-gnu-gcc: fatal error: no input files > compilation terminated. > configure:3155: $? = 4 > configure:3175: checking whether the C compiler works > configure:3197: x86_64-linux-gnu-gcc conftest.c >&5 > /usr/local/bin/ld: unrecognized option '--build-id' > /usr/local/bin/ld: use the --help option for usage information > collect2: ld returned 1 exit status Find why /usr/bin/x86_64-linux-gnu-gcc invokes /usr/local/bin/ld. > Any idea ? I think you have simply created a broken build environment on your system. I have no idea how you did that, but you seem to just have a mess of toolchains. You need to clean that up and set up the neccessary system and target toolchains. Nothing more, nothing less. //Peter

1 0

Compiling failure with Ubuntu 11.10 64 bits
by Eric Tyberghien 01 Jan '12

01 Jan '12

Hi all I'm using Ubuntu 11.10 64 bits and I try to compile osmocom-bb but it fails due to the enable-linker-buid-id option not supported by the ld linker Here is the make : root@erict-G5360fr-m:/home/erict/Téléchargements/osmocom-bb/src# make cd shared/libosmocore/build-target && ../configure \ --host=arm-elf --enable-embedded --disable-shared \ --disable-tests ac_cv_header_sys_select_h=no \ --disable-tests ac_cv_header_sys_socket_h=no \ CFLAGS="-Os -ffunction-sections -I/home/erict/Téléchargements/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs" configure: WARNING: if you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-elf-strip... arm-elf-strip checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make sets $(MAKE)... (cached) yes checking for arm-elf-gcc... arm-elf-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... yes checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether arm-elf-gcc accepts -g... yes checking for arm-elf-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of arm-elf-gcc... gcc3 checking build system type... x86_64-unknown-linux-gnu checking host system type... arm-unknown-elf checking how to print strings... printf checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by arm-elf-gcc... /root/install/gnuarm-4.0.2/arm-elf/bin/ld checking if the linker (/root/install/gnuarm-4.0.2/arm-elf/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /root/install/gnuarm-4.0.2/bin/arm-elf-nm -B checking the name lister (/root/install/gnuarm-4.0.2/bin/arm-elf-nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 3458764513820540925 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert x86_64-unknown-linux-gnu file names to arm-unknown-elf format... func_convert_file_noop checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop checking for /root/install/gnuarm-4.0.2/arm-elf/bin/ld option to reload object files... -r checking for arm-elf-objdump... arm-elf-objdump checking how to recognize dependent libraries... unknown checking for arm-elf-dlltool... no checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for arm-elf-ar... arm-elf-ar checking for archiver @FILE support... no checking for arm-elf-strip... (cached) arm-elf-strip checking for arm-elf-ranlib... arm-elf-ranlib checking command to parse /root/install/gnuarm-4.0.2/bin/arm-elf-nm -B output from arm-elf-gcc object... ok checking for sysroot... no checking for arm-elf-mt... no checking for mt... mt configure: WARNING: using cross tools not prefixed with host triplet checking if mt is a manifest tool... no checking how to run the C preprocessor... arm-elf-gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... no checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... no checking for objdir... .libs checking if arm-elf-gcc supports -fno-rtti -fno-exceptions... no checking for arm-elf-gcc option to produce PIC... -fPIC -DPIC checking if arm-elf-gcc PIC flag -fPIC -DPIC works... yes checking if arm-elf-gcc static flag -static works... yes checking if arm-elf-gcc supports -c -o file.o... yes checking if arm-elf-gcc supports -c -o file.o... (cached) yes checking whether the arm-elf-gcc linker (/root/install/gnuarm-4.0.2/arm-elf/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... no checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... no checking whether to build shared libraries... no checking whether to build static libraries... yes checking for ANSI C header files... (cached) yes checking execinfo.h usability... no checking execinfo.h presence... no checking for execinfo.h... no checking for sys/select.h... (cached) no checking for sys/socket.h... (cached) no checking syslog.h usability... no checking syslog.h presence... no checking for syslog.h... no checking ctype.h usability... yes checking ctype.h presence... yes checking for ctype.h... yes checking for size_t... yes checking for working alloca.h... yes checking for alloca... yes checking for library containing dlopen... no checking for doxygen... false checking if arm-elf-gcc supports -fvisibility=hidden... yes configure: creating ./config.status config.status: creating libosmocore.pc config.status: creating libosmocodec.pc config.status: creating libosmovty.pc config.status: creating libosmogsm.pc config.status: creating include/osmocom/Makefile config.status: creating include/osmocom/vty/Makefile config.status: creating include/osmocom/codec/Makefile config.status: creating include/osmocom/crypt/Makefile config.status: creating include/osmocom/gsm/Makefile config.status: creating include/osmocom/gsm/protocol/Makefile config.status: creating include/osmocom/core/Makefile config.status: creating include/Makefile config.status: creating src/Makefile config.status: creating src/vty/Makefile config.status: creating src/codec/Makefile config.status: creating src/gsm/Makefile config.status: creating tests/Makefile config.status: creating tests/timer/Makefile config.status: creating tests/sms/Makefile config.status: creating tests/msgfile/Makefile config.status: creating tests/ussd/Makefile config.status: creating tests/smscb/Makefile config.status: creating tests/bits/Makefile config.status: creating utils/Makefile config.status: creating Doxyfile.core config.status: creating Doxyfile.gsm config.status: creating Doxyfile.vty config.status: creating Doxyfile.codec config.status: creating Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands cd shared/libosmocore/build-target && make make[1]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target » make all-recursive make[2]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target » Making all in include make[3]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude » Making all in osmocom make[4]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom » Making all in codec make[5]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom/codec » make[5]: Rien à faire pour « all ». make[5]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom/codec » Making all in crypt make[5]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom/crypt » make[5]: Rien à faire pour « all ». make[5]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom/crypt » Making all in gsm make[5]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom/gsm » Making all in protocol make[6]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom/gsm/protocol » make[6]: Rien à faire pour « all ». make[6]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom/gsm/protocol » make[6]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom/gsm » make[6]: Rien à faire pour « all-am ». make[6]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom/gsm » make[5]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom/gsm » Making all in core make[5]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom/core » make[5]: Rien à faire pour « all ». make[5]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom/core » make[5]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom » make[5]: Rien à faire pour « all-am ». make[5]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom » make[4]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude/osmocom » make[4]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude » make[4]: Rien à faire pour « all-am ». make[4]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude » make[3]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/i nclude » Making all in src make[3]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/s rc » Making all in . make[4]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/s rc » make[4]: Rien à faire pour « all-am ». make[4]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/s rc » Making all in vty make[4]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/s rc/vty » make[4]: Rien à faire pour « all ». make[4]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/s rc/vty » Making all in codec make[4]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/s rc/codec » make[4]: Rien à faire pour « all ». make[4]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/s rc/codec » Making all in gsm make[4]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/s rc/gsm » make[4]: Rien à faire pour « all ». make[4]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/s rc/gsm » make[3]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/s rc » Making all in tests make[3]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/t ests » make[4]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/t ests » make[4]: Rien à faire pour « all-am ». make[4]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/t ests » make[3]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/t ests » Making all in utils make[3]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/u tils » make[3]: Rien à faire pour « all ». make[3]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target/u tils » make[3]: entrant dans le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target » make[3]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target » make[2]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target » make[1]: quittant le répertoire « /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target » cd shared/libosmocore/build-host && ../configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make sets $(MAKE)... (cached) yes checking for gcc... gcc checking whether the C compiler works... no configure: error: in `/home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-host': configure: error: C compiler cannot create executables See `config.log' for more details make: *** [sharedroland(a)redhat.com> /libosmocore/build-host/Makefile] Erreur 77 The config.log file is like that root@erict-G5360fr-m:/home/erict/Téléchargements/osmocom-bb/src/shared/libos moco re# cat config.log This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by libosmocore configure UNKNOWN-dirty, which was generated by GNU Autoconf 2.68. Invocation command line was $ ./configure configure -v --with-pkgversion=Ubuntu/Linaro 4.6.1-9ubuntu3 --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++,go --prefix=/usr --program-suffix=-4.6 --enable-shared --disable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu ## --------- ## ## Platform. ## ## --------- ## hostname = erict-G5360fr-m uname -m = x86_64 uname -r = 3.0.0-14-generic uname -s = Linux uname -v = #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin PATH: /usr/games PATH: /root/install/gnuarm-4.0.2/bin ## ----------- ## ## Core tests. ## ## ----------- ## configure:2324: checking for a BSD-compatible install configure:2392: result: /usr/bin/install -c configure:2403: checking whether build environment is sane configure:2453: result: yes configure:2594: checking for a thread-safe mkdir -p configure:2633: result: /bin/mkdir -p configure:2646: checking for gawk configure:2662: found /usr/bin/gawk configure:2673: result: gawk configure:2684: checking whether make sets $(MAKE) configure:2706: result: yes configure:2800: checking whether make sets $(MAKE) configure:2822: result: yes configure:2839: checking for x86_64-linux-gnu-gcc configure:2855: found /usr/bin/x86_64-linux-gnu-gcc configure:2866: result: x86_64-linux-gnu-gcc configure:3135: checking for C compiler version configure:3144: x86_64-linux-gnu-gcc --version >&5 x86_64-linux-gnu-gcc (Ubuntu/Linaro 4.6.1-9ubuntu3) 4.6.1 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:3155: $? = 0 configure:3144: x86_64-linux-gnu-gcc -v >&5 Using built-in specs. COLLECT_GCC=x86_64-linux-gnu-gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.6.1/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.6.1-9ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++,go --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) configure:3155: $? = 0 configure:3144: x86_64-linux-gnu-gcc -V >&5 x86_64-linux-gnu-gcc: error: unrecognized option '-V' x86_64-linux-gnu-gcc: fatal error: no input files compilation terminated. configure:3155: $? = 4 configure:3144: x86_64-linux-gnu-gcc -qversion >&5 x86_64-linux-gnu-gcc: error: unrecognized option '-qversion' x86_64-linux-gnu-gcc: fatal error: no input files compilation terminated. configure:3155: $? = 4 configure:3175: checking whether the C compiler works configure:3197: x86_64-linux-gnu-gcc conftest.c >&5 /usr/local/bin/ld: unrecognized option '--build-id' /usr/local/bin/ld: use the --help option for usage information collect2: ld returned 1 exit status configure:3201: $? = 1 configure:3239: result: no configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "libosmocore" | #define PACKAGE_TARNAME "libosmocore" | #define PACKAGE_VERSION "UNKNOWN-dirty" | #define PACKAGE_STRING "libosmocore UNKNOWN-dirty" | #define PACKAGE_BUGREPORT "openbsc-devel(a)lists.openbsc.org" | #define PACKAGE_URL "" | #define PACKAGE "libosmocore" | #define VERSION "UNKNOWN-dirty" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } configure:3244: error: in `/home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore': configure:3246: error: C compiler cannot create executables See `config.log' for more details ## ---------------- ## ## Cache variables. ## ## ---------------- ## ac_cv_env_CC_set= ac_cv_env_CC_value= ac_cv_env_CFLAGS_set= ac_cv_env_CFLAGS_value= ac_cv_env_CPPFLAGS_set= ac_cv_env_CPPFLAGS_value= ac_cv_env_CPP_set= ac_cv_env_CPP_value= ac_cv_env_LDFLAGS_set= ac_cv_env_LDFLAGS_value= ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= ac_cv_env_build_alias_set=set ac_cv_env_build_alias_value=x86_64-linux-gnu ac_cv_env_host_alias_set=set ac_cv_env_host_alias_value=x86_64-linux-gnu ac_cv_env_target_alias_set=set ac_cv_env_target_alias_value=x86_64-linux-gnu ac_cv_path_install='/usr/bin/install -c' ac_cv_path_mkdir=/bin/mkdir ac_cv_prog_AWK=gawk ac_cv_prog_CC=x86_64-linux-gnu-gcc ac_cv_prog_make_make_set=yes ## ----------------- ## ## Output variables. ## ## ----------------- ## ACLOCAL='${SHELL} /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/missing --run aclocal-1.11' ALLOCA='' AMDEPBACKSLASH='' AMDEP_FALSE='' AMDEP_TRUE='' AMTAR='${SHELL} /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/missing --run tar' AM_BACKSLASH='\' AM_DEFAULT_VERBOSITY='0' AR='' AUTOCONF='${SHELL} /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/missing --run autoconf' AUTOHEADER='${SHELL} /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/missing --run autoheader' AUTOMAKE='${SHELL} /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/missing --run automake-1.11' AWK='gawk' CC='x86_64-linux-gnu-gcc' CCDEPMODE='' CFLAGS='' CPP='' CPPFLAGS='' CYGPATH_W='echo' DEFS='' DEPDIR='' DLLTOOL='' DOXYGEN='' DSYMUTIL='' DUMPBIN='' ECHO_C='' ECHO_N='-n' ECHO_T='' EGREP='' ENABLE_MSGFILE_FALSE='' ENABLE_MSGFILE_TRUE='' ENABLE_PLUGIN_FALSE='' ENABLE_PLUGIN_TRUE='' ENABLE_SERIAL_FALSE='' ENABLE_SERIAL_TRUE='' ENABLE_TALLOC_FALSE='' ENABLE_TALLOC_TRUE='' ENABLE_TESTS_FALSE='' ENABLE_TESTS_TRUE='' ENABLE_UTILITIES_FALSE='' ENABLE_UTILITIES_TRUE='' ENABLE_VTY_FALSE='' ENABLE_VTY_TRUE='' EXEEXT='' FGREP='' GREP='' HAVE_DOXYGEN_FALSE='' HAVE_DOXYGEN_TRUE='' INSTALL_DATA='${INSTALL} -m 644' INSTALL_PROGRAM='${INSTALL}' INSTALL_SCRIPT='${INSTALL}' INSTALL_STRIP_PROGRAM='$(install_sh) -c -s' LD='' LDFLAGS='' LIBOBJS='' LIBRARY_DL='' LIBS='' LIBTOOL='' LIPO='' LN_S='' LTLIBOBJS='' MAKEINFO='${SHELL} /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/missing --run makeinfo' MANIFEST_TOOL='' MKDIR_P='/bin/mkdir -p' NM='' NMEDIT='' OBJDUMP='' OBJEXT='' OTOOL64='' OTOOL='' PACKAGE='libosmocore' PACKAGE_BUGREPORT='openbsc-devel(a)lists.openbsc.org' PACKAGE_NAME='libosmocore' PACKAGE_STRING='libosmocore UNKNOWN-dirty' PACKAGE_TARNAME='libosmocore' PACKAGE_URL='' PACKAGE_VERSION='UNKNOWN-dirty' PATH_SEPARATOR=':' RANLIB='' SED='' SET_MAKE='' SHELL='/bin/bash' STRIP='' SYMBOL_VISIBILITY='' VERSION='UNKNOWN-dirty' ac_ct_AR='' ac_ct_CC='' ac_ct_DUMPBIN='' am__EXEEXT_FALSE='' am__EXEEXT_TRUE='' am__fastdepCC_FALSE='' am__fastdepCC_TRUE='' am__include='' am__isrc='' am__leading_dot='.' am__quote='' am__tar='${AMTAR} chof - "$$tardir"' am__untar='${AMTAR} xf -' bindir='${exec_prefix}/bin' build='x86_64-linux-gnu' build_alias='x86_64-linux-gnu' build_cpu='' build_os='' build_vendor='' datadir='${datarootdir}' datarootdir='${prefix}/share' docdir='${datarootdir}/doc/${PACKAGE_TARNAME}' dvidir='${docdir}' exec_prefix='NONE' host='x86_64-linux-gnu' host_alias='x86_64-linux-gnu' host_cpu='' host_os='' host_vendor='' htmldir='${docdir}' includedir='${prefix}/include' infodir='${datarootdir}/info' install_sh='${SHELL} /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/install-sh' libdir='/usr/lib' libexecdir='/usr/lib' localedir='${datarootdir}/locale' localstatedir='${prefix}/var' mandir='${datarootdir}/man' mkdir_p='/bin/mkdir -p' oldincludedir='/usr/include' pdfdir='${docdir}' prefix='/usr' program_transform_name='s&$$&-4.6&' psdir='${docdir}' sbindir='${exec_prefix}/sbin' sharedstatedir='${prefix}/com' sysconfdir='${prefix}/etc' target_alias='x86_64-linux-gnu' ## ----------- ## ## confdefs.h. ## ## ----------- ## /* confdefs.h */ #define PACKAGE_NAME "libosmocore" #define PACKAGE_TARNAME "libosmocore" #define PACKAGE_VERSION "UNKNOWN-dirty" #define PACKAGE_STRING "libosmocore UNKNOWN-dirty" #define PACKAGE_BUGREPORT "openbsc-devel(a)lists.openbsc.org" #define PACKAGE_URL "" #define PACKAGE "libosmocore" #define VERSION "UNKNOWN-dirty" configure: exit 77 oot@erict-G5360fr-m:/home/erict/Téléchargements/osmocom-bb/src/shared/libosm ocore# Any idea ? Best greetings for the new year Eric

1 0

Hide extension..
by MArc Richter 30 Dec '11

30 Dec '11

Hey! So is it possibel to to hide the sender extension with SMS ? regards Marc

4 5

Quick Recap of running the 28C3 network
by Holger Hans Peter Freyther 29 Dec '11

29 Dec '11

Hi all, just a quick review of things we saw/learned during the congress * OsmocomBB LAPDm and nanoBTS LAPDm appear to have some communication issues leading to timeouts (nanoBTS resends a message with N(R) not incremented as a response to our I frame with Identity Response (or timeout) but with the old data). We don't have a fix/clear understanding of this yet... looks a bit like a bug in the nanoBTS firmware (but then other phones appear to work just fine) * CHANNEL ACTIVATION NACK on a TS. No idea why (maybe we closed a channel with our auto-timer but the nanoBTS thinks it is open). IIRC the nanoBTS sends us a report about open channels, we should cross-check every n-th report with our view of the channels... on top of that we should block failed channels (configurable, still to do). * Open channels... E.g. with a nanoBTS reboot or "drop bts connection ", there was a bug in libosmo-abis that the e1inp_event was not sent as the link was already taken out of the list of sign links when close is called (fixed in libosmo-abis and sharing code between rsl.c and ipaccess.c) * one OML NACK drops all BTS.. The code is there to deal with a crashed BTS to not have it connected in a bad state... (fixed in zecke/28c3) * subscriber queue, thanks to jolly's SMS setup we increased the amount of SMS and there still appear to be paths in the code that do not properly release the transaction/subscr_put and the queue got stuck. We should start by merging jolly's sms rework.. and see how we can move the queue out of process... * Local End Release for SAPI > 0 should be done in the channel release code, we need to implement T3109... thanks to jolly reading GSM 08.58/04.08 with me and discussing the normal/abnormal case. I have some work in progress (only tested the success case) patches in the zecke/28c3 branch. * I uploaded our scripts but somehow the core dumping does not work correctly (core_pattern appears to be right though) for running the network * Purging subscribers from the VLR, we do it too aggressively (on failed paging), it should take the periodic updating timer into account. * Sometimes i miss dates.. e.g. when was the channel opened probably some more things I forgot now, would be a great opportunity if someone gives a hand in cleaning things up. holger PS: jenkins will be back in january, ZFS crashed, the secret key was on the ZFS, grep didn't find the backup script...

1 0

Re: baseband-devel Digest, Vol 23, Issue 24
by Andres Berroa 20 Dec '11

20 Dec '11

Yes, the SIM works on other phones, even on the same phone with the original firmware, so I suspect it's a driver problem. On Tue, Dec 20, 2011 at 7:00 AM, <baseband-devel-request(a)lists.osmocom.org>wrote: > Send baseband-devel mailing list submissions to > baseband-devel(a)lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osmocom.org/mailman/listinfo/baseband-devel > or, via email, send a message with subject or body 'help' to > baseband-devel-request(a)lists.osmocom.org > > You can reach the person managing the list at > baseband-devel-owner(a)lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of baseband-devel digest..." > > Today's Topics: > > 1. Re: Fwd: SIM_JOB_RUN_GSM_ALGO fails (Sebastien Lorquet) > > > ---------- Forwarded message ---------- > From: Sebastien Lorquet <sebastien(a)lorquet.fr> > To: baseband-devel(a)lists.osmocom.org > Cc: > Date: Mon, 19 Dec 2011 17:01:53 +0100 > Subject: Re: Fwd: SIM_JOB_RUN_GSM_ALGO fails > Hi, > > SW1SW2 = 0000 let me think that the command was not actually sent to the > card, or the card was mute, or the error is very low level. > > is the failing sim OK in a real phone? > > Regards, > Sebastien > > PS: A very minor point, I don't know how the debug function is supposed to > work, but the "data=" field is not the data, but the whole command. > > Le 19/12/2011 16:36, Ethan Brown a écrit : > > Hello, > > The command SIM_JOB_RUN_GSM_ALGO fails on one of my sim cards. Here is > the log from mobile app: > > <0005> gsm48_mm.c:1637 AUTHENTICATION REQUEST (seq > 0) > > <0005> subscriber.c:957 Generating KEY at > SIM > > <000f> sim.c:209 got new job: SIM_JOB_RUN_GSM_ALGO > (handle=00000006) > > <000f> sim.c:539 RUN GSM > ALGORITHM > > <000f> sim.c:187 sending APDU (class 0xa0, ins 0x88, data=a0 88 00 00 10 > 92 15 a4 00 40 78 f7 7e b0 8c 31 19 99 56 01 93 ) > <000f> sim.c:877 received APDU (len=0 sw1=0x00 > sw2=0x00) > > <000f> sim.c:953 command > failed > > <000f> sim.c:151 sending result to callback function > (type=1) > > <0005> subscriber.c:991 key generation on SIM failed (cause 2) > > > And this is the log from L1: > > SIM Request (21): a0 88 00 00 10 92 15 a4 00 40 78 f7 7e b0 8c 31 19 99 56 > 01 93 > Triggering SIM transmission Character underflow!Triggering SIM reception > Max characters received!SIM: ACK does not match request, response[0]=60, > sim_data[1]=88 > SIM Response (2): 00 00 > > > The SIM I used for that test is somewhat different than other SIMs I have > tested and worked before. I attached a picture of two SIMs I used. The > green SIM is the one that fails running SIM_JOB_RUN_GSM_ALGO. The white > one works perfectly. > > > > _______________________________________________ > baseband-devel mailing list > baseband-devel(a)lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/baseband-devel > >

2 1

Fwd: SIM_JOB_RUN_GSM_ALGO fails
by Ethan Brown 19 Dec '11

19 Dec '11

Hello, The command SIM_JOB_RUN_GSM_ALGO fails on one of my sim cards. Here is the log from mobile app: <0005> gsm48_mm.c:1637 AUTHENTICATION REQUEST (seq 0) <0005> subscriber.c:957 Generating KEY at SIM <000f> sim.c:209 got new job: SIM_JOB_RUN_GSM_ALGO (handle=00000006) <000f> sim.c:539 RUN GSM ALGORITHM <000f> sim.c:187 sending APDU (class 0xa0, ins 0x88, data=a0 88 00 00 10 92 15 a4 00 40 78 f7 7e b0 8c 31 19 99 56 01 93 ) <000f> sim.c:877 received APDU (len=0 sw1=0x00 sw2=0x00) <000f> sim.c:953 command failed <000f> sim.c:151 sending result to callback function (type=1) <0005> subscriber.c:991 key generation on SIM failed (cause 2) And this is the log from L1: SIM Request (21): a0 88 00 00 10 92 15 a4 00 40 78 f7 7e b0 8c 31 19 99 56 01 93 Triggering SIM transmission Character underflow!Triggering SIM reception Max characters received!SIM: ACK does not match request, response[0]=60, sim_data[1]=88 SIM Response (2): 00 00 The SIM I used for that test is somewhat different than other SIMs I have tested and worked before. I attached a picture of two SIMs I used. The green SIM is the one that fails running SIM_JOB_RUN_GSM_ALGO. The white one works perfectly.

2 1

Re: burst couter in app_cch_scan
by lonelysurfer＠web.de 17 Dec '11

17 Dec '11

the tables from your conv_tch_afs.c I thought, that I need them to get the voice. ___________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

1 0

Re: burst couter in app_cch_scan
by lonelysurfer＠web.de 17 Dec '11

17 Dec '11

...ASF-Tables for the different channel codec modes ___________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

2 2

Re: burst couter in app_cch_scan
by lonelysurfer＠web.de 17 Dec '11

17 Dec '11

>It should work for the SACCH and SACCH but will _not_ decode the FACCH You mean the counter should work for SACH and FACCH? I know...other channels are decoded differently. Thats why I am asking. I am trying to implement FACH and hopefully ASF. I used your tch_h_1 mframe task to grab the tch. Best regards, Tobias ___________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

2 1

burst couter in app_cch_scan
by lonelysurfer＠web.de 17 Dec '11

17 Dec '11

is the burst couter in app_cch_scans local_burst_decode() bid = -1; ... if (bid == -1) return; also working for tch? Im asking, because "if (bid == -1)" is not triggered correctly with my tch samples. Regards, Tobias ___________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

2 1

Please report all known bugs/issues to trac!
by Harald Welte 16 Dec '11

16 Dec '11

Hi all! I would like to ask everyone to report known issues with OsmocomBB to the trac at http://bb.osmocom.org/trac/newticket I think there is a lot of knowledge already somwewhere in the project, but it's not readily available. Especially as there is some movement towards creating an actual usable phone, it would be great to have a collection of all known problems in the existing code. Don't worry too much if you don't know the correct component to which to attach the report, we will figure that out. If you don't have a wiki account for bb.osmocom.org, just send me a mail and I will create it. Thanks for your cooperation! -- - 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

RFC: Osmocom developer workshop 2012
by Harald Welte 14 Dec '11

14 Dec '11

<DISCLAIMER> Please follow-up to openbsc(a)lists.osmocom.org </DISCLAIMER> Hi all, this idea has been around for quite some time, and for 2012 I really want to turn it into reality: I'd like to have a Osmocom developer workshop The idea here is to get all the active contributors of the project together for a couple of days (maybe 2-4 days), in order to exchange ideas, get to know each other better and last but not least work together on ironing out some of the more difficult issues. * City: Regarding the location: I think for me it is only possible to organize it if it is to be held in Berlin. I'mn happy if somebody else wants to host it at some other location, but then that person would also have to take care of local organization. Berlin also has good train and flight connections, which is definitely a plus. * Venue: If it is in Berlin, we might consider talking with c-base or Raumfahrtagentur as possible venues. * Date: Regarding a proposed date, I'm completely open for suggestions. Of course there shouldn't be any overlap with other major FOSS or Sescurity related conferences, and it should also not coincide with major public holidays, as that only makes travel + accomodation more expensive. * Funding: As we don't have that many commercial users of Osmocom projects, getting funding for e.g. travel / accomodation is probably going to be difficult. We can ask the "usual suspects" among those commercial users we know,, but I guess it will only be possible in exceptional cases to provide that kind of funding. Any ideas / comments / feedback is much appreciated. If somebody has a particular suggestion. <DISCLAIMER> Please follow-up to openbsc(a)lists.osmocom.org </DISCLAIMER> Cheers, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 2

[PATCH] osmocon: correct parsing of -m
by Alexander Huemer 14 Dec '11

14 Dec '11

--- src/host/osmocon/osmocon.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/src/host/osmocon/osmocon.c b/src/host/osmocon/osmocon.c index 5f28992..fc29506 100644 --- a/src/host/osmocon/osmocon.c +++ b/src/host/osmocon/osmocon.c @@ -123,6 +123,7 @@ enum dnload_mode { MODE_C155, MODE_ROMLOAD, MODE_MTK, + MODE_INVALID, }; struct dnload { @@ -1184,7 +1185,7 @@ static int parse_mode(const char *arg) else if (!strcasecmp(arg, "mtk")) return MODE_MTK; - return -1; + return MODE_INVALID; } #define HELP_TEXT \ @@ -1413,7 +1414,7 @@ int main(int argc, char **argv) break; case 'm': dnload.mode = parse_mode(optarg); - if (dnload.mode < 0) + if (dnload.mode == MODE_INVALID) usage(argv[0]); break; case 's': -- 1.7.8

3 10

Filter Replacement and sharing experience
by Holger Hans Peter Freyther 14 Dec '11

14 Dec '11

Hi all, there appears to be moderate interest in doing the filter rework and I encourage anyone that modified a phone to share the experience with all of us. I have created a simple docbook that uses the pictures uploaded by Luka and annotates them with a "calloutlist". The docbook xml can be found here[1] and the draft PDF is in the wiki as well. It would be nice if all of us could contribute about the motivation of the rework, maybe a bit of history (how the RX path was identified, how new baluns were selected, ...), experience/tools used during the rework, review the draft, note the differences of the various phones. cheers holger [1] http://bb.osmocom.org/trac/attachment/wiki/Hardware/FilterReplacement/userm…

3 5

About DSP API
by Ethan Brown 13 Dec '11

13 Dec '11

Do any of you know where can I find documentation about the DSP API used in Osmocom?

2 10

Re: Creating a real usable phone using OsmocomBB
by Alexander Chemeris 13 Dec '11

13 Dec '11

Harald, interesting information! Do you have a link to those carrier predictions? -- Alexander Chemeris Sent from my Android device. Sorry for my brevity. On Dec 13, 2011 6:19 PM, "Harald Welte" <laforge(a)gnumonks.org> wrote: Hi Alexander, On Tue, Dec 13, 2011 at 04:09:56PM +0300, Alexander Chemeris wrote: > Excuse me for offtopic: I won... it depends on the Operator and where you are. They all only use 2100 MHz for 3G, not the lower 900/1800 MHz bands (which they could do legally after a EU regulation). But yes, indoor coverage can be really bad. For example in my apartment it is difficult to have 3G of all operators, and the one I use mostly (Eplus) barely has 2G coverage here. T-mobile and Vodafone are generally better. It's of course different if you're at major locations like train stations or the big squares downtown... Another note: I've recently seen some operator predictions for Germany, and they assume something like GSM being in operation until 2020 - definitely significantly longer than the life time of their existing GSM licenses (expiring in 2016). This tells us a lot about the installed/deployed user base, as well as the limited 3/3.5/4G coverage.. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ===================...

2 1

Re: Creating a real usable phone using OsmocomBB
by Alexander Chemeris 13 Dec '11

13 Dec '11

Interesting. In Moscow WiMAX quality is very unstable, but 3G/UMTS works pretty well. At least it's much faster then EDGE. Coverage is another topic, but it's not that bad given that 3G is still being rolled out. Having only this experience I expected similar situation in other major cities. Apparently different history and background make their corrections. -- Alexander Chemeris Sent from my Android device. Sorry for my brevity. On Dec 13, 2011 6:47 PM, "Peter Stuge" <peter(a)stuge.se> wrote: Alexander Chemeris wrote: > Excuse me for offtopic: I wonder why there is no 3G in Berlin? This > lo... Sorry - I was unclear. There are networks, but there is not nearly enough capacity for all users. This isn't neccessarily because of inadequate infrastructure, it may just be the best we can do with the shared medium at the cost of what the market is prepared to pay. When a Berlin friend visited Sweden his 3G USB modem LED was suddenly shining with a color he had never seen before. //Peter

1 0

Re: Creating a real usable phone using OsmocomBB
by Alexander Chemeris 13 Dec '11

13 Dec '11

Excuse me for offtopic: I wonder why there is no 3G in Berlin? This looks quite weird. -- Alexander Chemeris Sent from my Android device. Sorry for my brevity. On Dec 13, 2011 4:59 PM, "Peter Stuge" <peter(a)stuge.se> wrote: Harald Welte wrote: > > I'm not sure if there are any modems based on Calypso chipset, but > > even ... Don't be so sure. I've met competent engineers who have very weird issues with their M2M equipment being suddenly unreachable on the network without the modem reporting any error status. > Sierra, Cinterion, Wavecom and others have a well-established market, > and their products do ve... This is also not neccessarily for us to see. I think it's an interesting and relevant parallell track. There's no reason *not* to do it when it is *easier* than the other things we want to do, is my reasoning somehow. > The target user for the "OsmocomBB based phone" would be primarily a > "free software enthusiast... Also not neccessarily the only market we have. By now it's easy to customize your smartphone with tons of apps and so on, but regular users also like to change technology to fit them now and then. OK, it could be argued that they fall under the definition of free software enthusiasts, but the people I think of usually don't. > And such users are interested in real telephones, notin modems for > embedded systems. Maybe they have laptops and would like to use open source internet connectivity as well. In Berlin there's e.g. never 3G service available anyway, so 2G-only may be fine. Just because it's not for me or you doesn't mean that noone else will not want it. :) //Peter

4 3

Re: Creating a real usable phone using OsmocomBB
by Alexander Chemeris 13 Dec '11

13 Dec '11

Hi Harald and all, I want to point that except usual mobile phones there are GSM modems which do not require any UI and thus require less work to be done. Also they are often connected to a power grid and don't have strict power consumption limits. And at last, but not at least modem users often need some peculiat functionality, which they would love to see embedded. And that's where OsmocomBB stands out significantly from all existing modems. I'm not sure if there are any modems based on Calypso chipset, but even a phone serving as a modem may suffice in some cases. -- Alexander Chemeris Sent from my Android device. Sorry for my brevity. On Dec 11, 2011 2:55 PM, "Harald Welte" <laforge(a)gnumonks.org> wrote: Hi all! I've mentioned this before, and I keep getting back to it: With all the great work that has been put into OsmocomBB, we are "at an arms lengh" away from being able to create a true Free Software mobile phone. We already have the hardware drivers, protocol stack and even the 'mobile' program which can be used for making and receiving voice calls and sending/receiving SMS text messages on real GSM networks! While the journey has been a lot of fun and everyone involved has learned a lot, we have so far been catering mstly about "scratching our own itch", i.e. implementing what we needed in order to satisfy our ego and/or to implement the ideas we had regarding cellular security. I believe we cannot miss the bigger opportunity here to put our code into bigger use: To create something like a very simple GSM feature phone. When we look at various areas of computing like Operating Systems or Web browsers, Free Software is not just "the hobby project catching up" with the vendors of proprietary software. Free Software can compete. In the cellular area, we have still not managed to even implement the most basic GSM feature phone that existed 15 years ago using proprietary software. We need to work on closing that gap. We need to show that a small community of Free Software developers can actually implement what teams of hundreds of engineers did in a proprietary software setting 15 years ago - despite all the lack of hardware documentation or any kind of positive feedback from the cellular chipset, handset or operator industry. If we don't at least get a 2G GSM cellphone implemented now, it will probably not happen before 2G networks become insignificant in large parts of the world. This is a call to all hands, please support this project! Regards, Harald == Technical aspects == I believe the first major decision is whether we focus on 1) the Openmoko FreeRunner / Neo1973 phones Advantages: * large screen for UI with bells and whistles * lots of RAM and Flash, even script languages or compilation on the device itself possible * second processor doesn't require us to run stack + UI on once CPU * easier debugging of UI * various existing telephony middleware and phone dialer UI projects of which hopefully one could be recycled or 2) the Motorola/Compal C1xx phones Advantags: * many more phones available, even after our software is released * lower cost of the individual phone * less power consumption due to only one small ARM7 core * smaller screen also means less fancy UI requirements Problems: * full stack + UI needs to run on calypso (L2/L3) and we'd probably some kind of RTOS like NuttX instead of our 'bare iron' code. ==== What we need in any case ==== * power management on the baseband processor through all of the stack (though it's mostly a driver/L1 kind of thing) == Summary / Opinion == It seems like running the OsmocomBB layer1 + 'mobile' as-is on the Openmoko baseband + application processor might be the quicker road to progress. Sure, the power consumption will be horrible as the AP will have to be woken up for each and every SI message, neighbor cell measurment or paging request that ew see comining in in our paging group (even in idle mode). But then, there is always the negative impact of using a relatively complex system, with two processors, a complex software stack (Linux, X11, toolkit, etc.) on one of them, etc. On the other hand, using the C1xx phones will result in a much more widely available result. The phones can still be bought in batches of 1,000 units, and they are small enough for lots of people to carry around. Furthermore, the battery lifetime is far beyond anything you would ever be able to achieve on a power-hungry smartphone platform. I believe it would be the "smart' solution, as it means we need to get everything integrated, etc. What does the community on this list think? Which way shoul we go? But maybe the best thing is to actually stat working on the power management aspects, as we will need them in both cases. Happy hacking, 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)

3 2

Re: Creating a real usable phone using OsmocomBB
by msokolov＠ivan.Harhan.ORG 13 Dec '11

13 Dec '11

Hello folks, Just my two cents: one factor that seems to be overlooked in the C1xx vs. GTA0x decision is the support for different GSM RF bands. From my reading of the OsmocomBB wiki, it appears that all those C1xx phones support only EGSM and DCS1800 bands, but not PCS1900. It seems like most current active developers are located in world regions where EGSM and DCS1800 bands are used, but in my area the only usable GSM band is PCS1900, or maybe GSM850 too: haven't been able to try the latter as I don't have any devices that support it. OTOH, my Neo Freerunner (which is currently doing shelf duty as a paperweight lacking functional source-enabled Calypso fw) supports the PCS1900 band in addition to EGSM and DCS1800. But if the community goes the C1xx route and produces GPL code that runs fully on the Calypso, no PC needed, does power mgmt and implements some UI on the Calypso-controlled LCD and keypad, I expect no difficulty with taking that code, replacing the Calypso-based UI with some simple protocol for interfacing with the UI over the modem UART (maybe not the same as the infamous AT command interface, but doing the same job on the same level of abstraction), and running it on my GTA02, hence I'm not complaining. As far as the power management etc advantages of the simpler phones without an application processor: does anyone know of any basic Leonardo-style phones which are like the famous C1xx, but support the PCS1900 band, are physically available, and documented no worse than C1xx in terms of the availability of schematics and docs for display and other non-Calypso components? The fact that C1xx phones can be bought in 1000 unit quantities is great news for those living in areas with EGSM/DCS1800 services, but doesn't do much good for those living in PCS1900/GSM850 lands... MS

7 10

Re: Creating a real usable phone using OsmocomBB
by msokolov＠ivan.Harhan.ORG 12 Dec '11

12 Dec '11

Denis 'GNUtoo' Carikli <GNUtoo(a)no-log.org> wrote: > That's exactly what I was thinking about, since running the layer23 on the > Application CPU is not a so good idea, it renders the phone usable only for a > small period of time(since,in that configuration, you cannot suspend the AP > CPU because it has to run the telephony code). It's obvious that running layer23 on the AP is a *terrible* idea. It needs to move into the Calypso (or other BP) before there can be any serious thought of OsmocomBB truly replacing the existing proprietary BP code. However, my own skill & knowledge level is nowhere close to what would be needed for that job. But I was thinking of taking the current sorry state of things (layer23 external to the BP) and making it run on a self-contained GTA02: have the Samsung AP run layer23 instead of acting as a pass- through to a PC, then add some UI to it: the very same UI I wanted to implement in the first place before I got sidetracked to the baseband issues. The result of that would be having the GTA02 act as a "normal" feature phone in every way except for draining the battery in a couple of hours while doing nothing. The last aspect would make it rather unusable practically (unless perhaps one replaces the standard Li-ion battery with an automotive-sized lead-acid one), but it would be a tangible hands-on "teaser" of what would be possible if someone with the necessary knowledge and skills took the bother to redesign the code (move layer23 into the Calypso) such that proper PM could be implemented. > Why is AT bad? what other protocol do you propose? What Peter said: : Um, no, it's the other way around. AT is 30 years of horrible. If I were able to lay my hands on some source for an *existing* implementation of the AT command interface on the BP side, I would have no problem with implementing it on the AP side in my UI. But if I have to write the code from scratch on both sides of the interface, I'll probably implement some ad hoc protocol of my own rather than attempt to implement the "standard" one and get it wrong. MS

1 0

Trouble with C117 while using osmocon
by Sreeraj R 11 Dec '11

11 Dec '11

Hi all, I am just a beginner and is using the following hardware Phone : C117 Serial Adapter : CP2102 based The propt message that I am getting is different compared to that mentioned in the wiki (http://bb.osmocom.org/trac/wiki/CompalRamloader). Command: ./osmocon -d t -p /dev/ttyUSB0 -m c123 ../../target/firmware/board/compal_e88/loader.compalram.bin Gives me the following data {00,f1,01,72,82,bf,7d,fd,7f,00,a6,51,d2,51,0a,3a,02,4d,a3,a3,da,00,00} Entire log after short power button key press is http://pastebin.com/AqcNm6dq. Can anyone give some pointers, or did I go wrong somewhere. The wiki specifies C117 board is similar to C123. regards Sreeraj R

2 1

Re: gnuarm version
by R M 10 Dec '11

10 Dec '11

Hi, I am using this version of GNU Arm. http://www.gnuarm.com/bu-2.15_gcc-3.4.3-c-c++-java_nl-1.12.0_gi-6.1.exe Regards, RM On 12/4/11, Juantxi <juantxipazos(a)yahoo.es> wrote: > > Hello, what version of gnuarm uses? > thank >

1 0

Re: RFC: Osmocom developer workshop 2012
by Harald Welte 05 Dec '11

05 Dec '11

Hi! Thinking a bit more about timing, it seems that the second half of March is a good idea. April is a bad idea, at least for the first two weeks, as this is easter holiday time in a lot of German states. This will cause lots of tourists, as well as full hotels, trains, flights, etc. So I'd propose something like four days in the second half of march. Should we try to overlap/extend a weekend? I guess this would help people with e regular dayjob, as not as many holidays would be required. If there are no objections in the next 48 hours, I will talk to C-Base about availability during that timeframe. 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)

3 4

Script for parsing boot loader into COFF
by R M 03 Dec '11

03 Dec '11

Hi, Is there a script for parsing the boot loader code into a COFF format so that it can be loaded into IDA? Regards, RM

1 0

MTK and Infineon-based phones
by Martin Hinner 28 Nov '11

28 Nov '11

Hi Marcin, On Sun, Nov 27, 2011 at 1:17 AM, Marcin Mielczarczyk <marcin.mielczarczyk(a)gmail.com> wrote: > Note, that on the market there is much more Mediatek phones based on ARM7 > (MT622x) than on ARM9 (MT623x). You are right, it makes sense. My mistake. I was only working with flash dumps so far... I have spent some time analyzing mtk-phone project. There is a lot of files missing, but the situation is not so bad. My feeling is that some of the files were simply deleted from the project... (interrupted upload?) I made a list of all files needed to link binary image (from .lis file). Then I did: find . -name '*.c' Then I ran ar l on al mtk-lib .lib files (these can be quite easily disassembled). And finally diff helped to find what is missing... We're missing only these files (no .obj in .lib or .c is present in the project): -lic.c -drvflash.c -l1c_trace.c -l1d2_trace.c -l1d3_trace.c -l1d_edge_trace.c -l1d_trace.c -l1sc_trace.c -l1trc.c -l4drv.c -sst_decrypt.c -sst_intrctrl.c -sst_secure.c -trcmod.c I think none of these are needed for our stuff. Then we are missing .c files, but have .obj in .lib (only important files) dp_engine.lib: awb_bitstream.c (unknown for what is this) dsp_ram.lib: ddload.c dsp_ram.lib: dsp_ptch_6223.c (we can get this from binary) dsp_ram.lib: idma.c l1.lib: l1csm.c l1.lib: l1dsm.c l1.lib: m*.c (it's a lot of files !!!!!!!!!!!!) In fact this is end of all important routines... Tracing functions: l1.lib: l1i_amr_trace.c l1.lib: l1i_cs_trace.c l1.lib: l1sc_trace.c l1.lib: l1t_amr_trace.c l1.lib: l1c3_trace.c l1.lib: l1c4_trace.c l1.lib: l1c_csd_trace.c l1.lib: l1c_trace.c l1.lib: l1d2_trace.c l1.lib: l1d3_trace.c l1.lib: l1d_edge_trace.c l1.lib: l1d_trace.c l1.lib: rftool_gsm.c (shows how to call various functions) Only for testing: l1.lib: l1tst_afc.c l1.lib: l1tst_agc.c l1.lib: l1tst_cfg.c l1.lib: l1tst_cont.c l1.lib: l1tst_fcb.c l1.lib: l1tst_fhc.c l1.lib: l1tst_nbtx.c l1.lib: l1tst_pm.c l1.lib: l1tst_ul.c I have already tried to disassemble some of them and it all makes sense, most of functions are very simple and some files are not even needed. My feeling is that we have all needed to understand the DSP functionality / L1 part of the ARM code! The biggest problem is that m*.c files depend on hardware (a lot of #ifdefs), so this needs to be analyzed on firmware downloaded from hardware. [ Question: why such cryptic names such as m12170.c ? ] I also have list of functions in those files, if anyone's interested in helping me with locating what is important and what is not... (34 kB). Martin

2 2

MTK and Infineon-based phones
by Martin Hinner 27 Nov '11

27 Nov '11

Hi, I spent a few hours today looking at CCC presentations and osmocom code. Good and interesting work! I have a couple of questions... This is my first experience with GSM phones reverse engineering, so sorry if I am wrong, but it seems to be quite difficult for me to obtain four Calypso-based phones (yes, I know I can order them from webshop for a few euros, but I will need more of them if my experiments are successfull). On the other hand, I have access to very cheap phones using Infineon PMB7880 (C166 + DSP) or MTK (ARM9) chipsets. Currently, I do have some information (datasheet&code) for MTK platform, and I see there is implementation of "secondary bootloader" for these phones, but no layer1 yet. I also have very basic documentation of Infineon SoC, plus I have knowledge of the C166 code and I can very easily play with it (reverse engineer firmware & assemble my own code). Is it feasible to create layer1 implementation for Infineon and/or MTK? Is there anyone willing to help with this? Here are my additional questions related to the above question: - Is there any documentation of mask-rom bootloader for Infineon C166 core? - At this moment I do not understand how does the DSP on the PMB7880 work, if RF part is accessible from both DSP and C166 or just the DSP. - How is it with Infineon DSP code, is it present in flash memory, or is it ROM-only thing? Anyone has the code dump? - Is anyone (who has experience with Calypso layer1) willing to help with implementing the same on Infineon or MTK platform? - If anyone has any resources for these two plaforms, I would be grateful if you can send them to me. I will add that I have spent many many nights disassembling car control units using Infineon/Siemens C166 core (since 2002?), so Infineon platform is very attractive for me (the flash is only 2MB for some phones, it's easy to read code, etc...). Thanks, Martin

6 12

[PATCH] i2c: fix maximum address an I2C chip can assign
by Alan Carvalho de Assis 27 Nov '11

27 Nov '11

I2C bus support up to 128 devices (mask 0x7F), but current calypso driver is masked it to 64 (0x3F). I discover it because Motorola W220 has an I/O expander PCA9537 at address 0x49 which could be reached. Signed-off-by: Alan Carvalho de Assis <acassis(a)gmail.com>

2 1

RFC Wiki re-org of bb.osmocom.org
by Holger Hans Peter Freyther 27 Nov '11

27 Nov '11

Hi, I have recently tried to find some information in our wiki and it was more difficult than I think it should be. I would like to propose and then implement some restructuring. So first of all I think we have good enough content, it is just a matter of structure. Front Page: I would like to have a very simple and structured entry. Mainly pointing to other projects, History, Software and Hardware? Hardware Pages Our hardware pages are mostly the same but actually quite different. I would like to find the following information on each page: - Which firmware/board to use (compal_e88)... - Picture of assembled/disassembled device - Knowledge we have I would like to move all Hardware/MotorolaCXX. The example would be to have hardware/ like this[1] and hardware/MotorolaC118 like this[2]. Software Pages: We have the Getting Started but there appears to be a gap from having a toolchain (or building one) and knowing how the various parts are connected to each other. I have not thought about it too much though. History Pages: I would move some older information in there. E.g. our never started/finished Calypso based design, maybe some parts of the project history. comments? ideas? holger [1] http://wiki.openwrt.org/toh/start#supported.hardware.-.router.type [2] http://wiki.openwrt.org/toh/buffalo/whr-g125

3 2

uplink sniffing
by Lorik Sefaj 26 Nov '11

26 Nov '11

Hi all, Just received my C123 (from http://shop.sysmocom.de/) with filter rework and it works great. I have one problem with the "burst*.dat" files when i do uplink sniffing, basically there are no files produced and when they are produced most of the time they are empty? This doesn't happen when i do downlink sniffing. Is this a stupid question or am I missing something... cheers, L.

4 5

OsmocomBB Bootstrapping
by Kurtis Heimerl 26 Nov '11

26 Nov '11

Hello baseband-devel(a)lists.osmocom.org! I've just started my first OsmocomBB project, using a Motorola V171 and the source code in the main git repository. The short hand version of the story is that we're looking into modifying the GSM MS stack to allow for the BTS to save some power. This is research being done at the University of California, and we're sorta amazed at how wonderful OsmocomBB is for this particular project. Thanks for the work! Progress has generally been good, and I've been able to build and run the "hello world" e99 application. Following that, I've moved onto the mobile app... and run into an issue that I can't seem to resolve by searching your mailing lists. Basically, each individual process runs fine: osmocon installs the compal_e99/layer1.compalram.bin image onto a c155 device mobile connects (though it doesn't see the SIM for some reason...) and the terminal is available and active. I'm not able to do much though, as the MS isn't on yet. Upon turning the MS on, it scans for a while, eventually detecting my own cell tower. Terminal is active during this search. Unfortunately, shortly after detecting and syncing with my tower (ARFCN 51), the terminal freezes. osmocon begins repeating the following error: "Failed to write msg to the socket.." and nothing else moves. Kaput. Terminal does not respond to any messages sent. This is my problem, as I'd like to make a call. PRE-POWERUP mobile: http://pastebin.com/tPm9ux83 POST-POWERUP mobile: http://pastebin.com/fMD1Kth6 osmocon: http://pastebin.com/nc3QGGgD terminal says: kheimerl@darth-maul /tmp $ telnet localhost 4247 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Welcome to the OsmocomBB control interface OsmocomBB> % (MS 1) % No service. My intuition is that I've missed setting some key variables in the related configuration files (~/.osmocom/osmocom.cfg, ~/.osmocom/bb/mobile.cfg). though I can't find ANY documentation about what's supposed to be in those things. Any and all help would be appreciated.

4 4

Re: osmocom-bb cygwin
by R M 26 Nov '11

26 Nov '11

Hi, Its better you send the mail to the list rather than just to me. In that way you get more help. I have built osmocom using cygwin. But I am unable to get the code downloaded into the phone. I am facing timing issues. I am still looking into the issue though. The instructions to install cygwin are found at: http://cygwin.com/. By default cygwin installs just the basic tools. Once you have installed the basic tools, you have to run the installer again to get the tools required for building osmocom. The tools required are given in the Wiki at this link: http://bb.osmocom.org/trac/wiki/GettingStarted. Once you have done that you need to install gnu arm. In the same wiki you have the links to download the cygwin version of GNU Arm. The ftdi cable I use is at this link:http://www.sparkfun.com/products/8772. Regards, RM On 11/24/11, Juantxi <juantxipazos(a)yahoo.es> wrote: > hello, > osmocom-bb got compile using cygwin? > packages could tell me that you downloaded? > which cable did you use? > > I am interested in doing > thanks >

1 0

Bug in gprs decode software
by Dario Lombardo 25 Nov '11

25 Nov '11

Hi guys Today I'm experiencing a bug in the gprs decode software. In rlcmac.c:190, when li_off and f->len get invalid values, we have a buffer overflow in the mempy(). In my case f->len=15, li_off=135. The really stupid patch to avoid it is below: simply jumps the case. I'm not able to investigate why li_off becames greater than f->len, causing the crash. Maybe a check should added. Have some other seen this crash? diff --git a/rlcmac.c b/rlcmac.c index eea02ce..d76a8d6 100644 --- a/rlcmac.c +++ b/rlcmac.c @@ -187,11 +187,14 @@ void process_blocks(struct gprs_tbf *t, int ul) print_pkt(llc_data, llc_len); fflush(stdout); } - memcpy(llc_data, &f->data[li_off], f->len-li_off); - llc_len = f->len - li_off; - llc_first_bsn = bsn; - llc_last_bsn = bsn; - t->start_bsn = bsn; + + if (f->len > li_off && f->len-li_off > 65536) { + memcpy(llc_data, &f->data[li_off], f->len-li_off); + llc_len = f->len - li_off; + llc_first_bsn = bsn; + llc_last_bsn = bsn; + t->start_bsn = bsn; + } } }

1 1

[PATCH 0/0] firmware janitor work to reduce compiler warnings
by Alexander Huemer 24 Nov '11

24 Nov '11

This patch series reduces the number of warnings emitted during firmware compilation. No functional changes. The patches could NOT be TESTED, so please try them before merging. Kind regards, -Alexander Huemer

5 23

[PATCH] rf: dereference pointer
by Alexander Huemer 21 Nov '11

21 Nov '11

--- src/target/firmware/rf/mt6139.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/target/firmware/rf/mt6139.c b/src/target/firmware/rf/mt6139.c index a9a6d32..d48e652 100644 --- a/src/target/firmware/rf/mt6139.c +++ b/src/target/firmware/rf/mt6139.c @@ -39,13 +39,13 @@ static void mt6139_compute_pll(uint32_t f_vco_100khz, /* To compute Nint, we assume Nfrac is zero */ *nint = (fvco_100khz / (10 * 2 * 26)) - (0 / 130); - if (nint > 127) + if (*nint > 127) printf("VCO Frequency %u kHz is out of spec\n", f_vco_100khz); /* Compute Nfract using the pre-computed Nint */ /* Nfrac = ( (Fvco/2*26) - Nint) * 130 */ /* Nfrac = ( (Fvco*130)/(2*26) - (Nint * 130) */ - *nfrac = (f_vco_100khz*130)/(52*10) - (nint * 130); + *nfrac = (f_vco_100khz*130)/(52*10) - (*nint * 130); } /* Set ARFCN. Takes 2 reg_write, i.e. 8 TPU instructions */ -- 1.7.8.rc1

3 3

OsmocomBB on Motorola W220
by Alan Carvalho de Assis 20 Nov '11

20 Nov '11

Hi all, I want to know if someone here already tried osmocombb on Motorola W220? This cell phone is powered by D751749ZPH, but at least my model (W220 E2) doesn't communicate with "osmocon". The problem is not serial cable because it work correctly with C115. After some search I discovered the uart is disabled by software, some firmware version let users to enable it after entering on engineering mode (*#**372#), unfortunately my firmware doesn't have this option at eng. mode. You can see a picture of my W220 board here: http://acassis.files.wordpress.com/2011/11/sam_1634.jpg If someone has some idea for an alternative option (JTAG?) please tell me. BR, Alan

2 2

Re: Diff between TWL3014 and TWL3025
by msokolov＠ivan.Harhan.ORG 19 Nov '11

19 Nov '11

Sylvain Munaut <246tnt(a)gmail.com> wrote: > Google for TWL3016 SWCS010 and check for yourself Thanks once again! OK, so TWL3016 *is* Syren indeed, and it does have additional features over Iota. But EDGE modulation support isn't one of them. If my reading of the doc is correct, the additional features of Syren over Iota are I2S audio, high voltage charger input and the USB regulator support. Does this agree with your reading? MS

1 0

Re: Diff between TWL3014 and TWL3025
by msokolov＠ivan.Harhan.ORG 19 Nov '11

19 Nov '11

Steve Markgraf <steve(a)steve-m.de> wrote: > Search Google for "TWL3025 SWRS021", last hit. Thanks, got it. (In my case it was the middle of the 3 results rather than the last.) I wonder about all these Chinese websites... It looks like they have a healthier attitude about sharing this kind of stuff than the Westerners do. So far we've known about 52rd.com hosting "contraband" phone handset chip documents, and now we know there's also baisi.net... But I find it strange that only PDF datasheets and PPT presentations have been found so far, and not, for example, any of the source/object-mix packages that must have been given for the firmware side of things by TI et al to the same folks (phone makers?) to whom they've given the chip docs. NDA etc issues ought to be the same... Or maybe I just haven't been looking hard enough... Would anyone here perchance happen to have a link to some place on one of those Chinese sites that has the original FW source (or semi-source, as in bits of source mixed with binary object blobs) for the Leonardo reference board or for some other Calypso-based HW version that's more readily available (as in HW availability) than the famous TSM30 version? (I realize that it would never be acceptable to use any such code in a Western FOSS project like OsmocomBB, but I would still *love* to take a peek at the original code for some phone whose HW is better understood and/or more readily available than the TSM30.) > Both TWL3014 and TWL3025 are Iota, TWL3016 is Syren. Hmm. I agree that TWL3025 must be some equivalent Iota variant, and I think you are right about TWL3016 being Syren: the Rita_intro.pdf document in my collection (see my FTP site) says "It is compatible with Iota (TWL3014) and Syren (TWL3016) ABB chips". However, the Iota_intro.pdf document (same FTP site) shows the Nausica->Iota->Syren evolutionary line and lists Syren as EDGE-capable. But Sylvain says TWL3016 doesn't do EDGE either. Hmm. Are you sure? MS

2 1

Re: Diff between TWL3014 and TWL3025
by msokolov＠ivan.Harhan.ORG 18 Nov '11

18 Nov '11

Steve Markgraf <steve(a)steve-m.de> wrote: > Well, some time ago I diffed the TWL3014 and TWL3025 datasheets, Where did you find the TWL3025 datasheet? Wading through 52rd.com, or is there some other source I'm unaware of? > there is no technical difference at all (only 3014 replaced with 3025, > and some minor formatting changes). > [...] > I suspect that TI renamed > the chip because of some changes in the manufacturing process. Hmm, interesting. > Given that both chips work fine with osmocom (with the same revision of > DSP rom code on the Calypso side of things), What OsmocomBB-supported phones use TWL3014? Sylvain Munaut <246tnt(a)gmail.com> wrote: > > supposedly called Syren rather than Iota and supports EDGE modulation. > No it doesn't. > [...] > > Is it a Iota variant or a Syren variant? > I think they're all called "Iota" that's a generic designation for the ABB. I believe that the codenames refer to specific generations for each function, rather than to functions like DBB/ABB/RF. For example, it seems that Calypso succeeded Hercules in the DBB role, and Rita succeeded Clara in the RF role. I remember seeing somewhere that Iota's successor was/is Syren, whereas its predecessor in the ABB role was Nausica. But if TWL3016 and TWL3025 are both Iotas, which chip is then Syren? Does anyone know? MS

3 2

Diff between TWL3014 and TWL3025
by msokolov＠ivan.Harhan.ORG 18 Nov '11

18 Nov '11

Hello GSM BB hackers, I wonder, would anyone here happen to know what are the main diffs between the TWL3014 and TWL3025 ABB chips? TWL3025 is the chip that appears to be used in most of the phones currently supported by OsmocomBB, but the presumably older TWL3014 is the only one for which we have docs as part of the Calypso and Leonardo documentation set at: ftp://ifctfvax.Harhan.ORG/pub/GSM/Calypso (The above FTP server is mine, but the content originates from the 52rd.com Chinese forum linked to from some of the OsmocomBB wiki pages.) Hence me wondering if anyone here knows what the actual differences are... I also recall seeing somewhere (don't remember where) that Iota strictly means TWL3014, and that its successor (TWL3016?) is supposedly called Syren rather than Iota and supports EDGE modulation. If that is true, where does the TWL3025 fit into that picture then? Is it a Iota variant or a Syren variant? It ought to be newer than TWL3016, right? Does that mean it ought to support EDGE? If so, what stands in the way of EDGE support in phones like GTA02 that use the TWL3025 ABB? Lack of Calypso DSP support? Or an RF front-end that isn't compatible with EDGE modulation? Or is TWL3025 a step backward from TWL3016, without EDGE support? If so, would anyone happen to know what its raison-d'etre is? What does it offer over the TWL3014? Just wondering... MS

3 2

Compile with DEBUG fail / i2c.c
by Stefan Mandl 15 Nov '11

15 Nov '11

Hello all, if you compile with #ifdef DEBUG, 2 litte typo errors came up... Regrads from stefan my patch... --- a/src/target/firmware/calypso/i2c.c +++ b/src/target/firmware/calypso/i2c.c @@ -67,7 +67,7 @@ int i2c_write(uint8_t chip, uint32_t addr, int alen, const uint8_t *buffer, int if (len > 16) return -1; - printd("i2c_write(chip=0x%02u, addr=0x%02u): ", chip, addr) + printd("i2c_write(chip=0x%02u, addr=0x%02u): ", chip, addr); writeb(chip & 0x3f, I2C_REG(DEVICE_REG)); writeb(addr & 0xff, I2C_REG(ADDRESS_REG)); @@ -91,7 +91,7 @@ int i2c_write(uint8_t chip, uint32_t addr, int alen, const uint8_t *buffer, int /* wait until transfer completes */ while (1) { uint8_t reg = readb(I2C_REG(STATUS_ACTIVITY_REG)); - printd("I2C Status: 0x%02x\n", rerg & 0xf); + printd("I2C Status: 0x%02x\n", reg & 0xf); if (!(reg & I2C_STATUS_IDLE)) // 0: idle 1: not idle break;

2 1

burst_ind not working
by Dario Lombardo 11 Nov '11

11 Nov '11

Hi guys I'm not able to use cell_log under the burst_ind branch. I checkout the master, compile and run osmocon/cell_log. Everything works (I can see the cells). I checkout the branch, recompile, and run the same commands as before, but I get from layer1: [...] PM MEAS: ARFCN=71, 0 dBm at baseband, -138 dBm at RF DSP Error Status: 8 PM MEAS: ARFCN=72, 0 dBm at baseband, -138 dBm at RF DSP Error Status: 8 PM MEAS: ARFCN=73, 0 dBm at baseband, -138 dBm at RF [...] for every arfcn. Cell_log doesn't log anything: [...] <000e> cell_log.c:359 Measurement done <000e> cell_log.c:368 Measure from 0 to 124 <000e> cell_log.c:368 Measure from 512 to 885 <000e> cell_log.c:368 Measure from 955 to 1023 [...] I don't think it's a hardware problem, since it works with master. Am I missing something in the branch? Is anyone experiencing the same problem? Bye. Dario.

3 3

c1xx with filter re-work
by Lorik Sefaj 10 Nov '11

10 Nov '11

Hi all, Considering my soldering skills and the fact that I just ruined a c123 trying to replace the filters (which was working perfectly with patched burst_ind and got me a lot of downlink traffic to work with). Anyways without wasting your time my question is: does anybody have a c1xx with filter re-work for sale? I'd like to get some uplink traffic Thanks a lot and keep up the great work, J

3 5

Sony J120?
by Jay R. Worthington 08 Nov '11

08 Nov '11

Hi 'yall, before i break out the soldering iron, has someone already tried the J120? It seem's to be a tad newer version of the J100, but with an (FM-) Radio, the specs lists it as Calypso Chipset... Regards, Jay

1 0

calypso SIM driver on c139 (also: l1ctl SIM APDU)
by Gianni Tedesco 08 Nov '11

08 Nov '11

The SIM and the SIM reader in the phone and the mechanical contact between them are definitely working because the SIM can be accessed from the motorola firmware, from another phone and from a PC smartcard reader with no PIN or anything. However, under simtest firmware no data is received by the phone, even the ATR is zero bytes... Anybody had this problem? Also, is l1CTL SIM APDU command not implemented in the layer1 firmware? How are people making calls without a SIM? :P Gianni ----------------SIMTEST----8<----------------- Initializing driver: SIM: Registering interrupt handler for simcard-interface ====================== CALYPSO SIM REGISTER DUMP ===================== Reg_sim_cmd register (R/W) - FFFE:0000 |-REG_SIM_CMD = 0000 | |-REG_SIM_CMD_CMDCARDRST = 0 ==> SIM card reset sequence disabled. | |-REG_SIM_CMD_CMDIFRST = 0 | |-REG_SIM_CMD_CMDSTOP = 0 | |-REG_SIM_CMD_CMDSTART = 0 | |-REG_SIM_CMD_MODULE_CLK_EN = 0 ==> Clock of the module disabled. |-REG_SIM_STAT = 000b | |-REG_SIM_STAT_STATNOCARD = 1 ==> No card! | |-REG_SIM_STAT_STATTXPAR = 1 ==> Parity ok! | |-REG_SIM_STAT_STATFIFOFULL = 0 | |-REG_SIM_STAT_STATFIFOEMPTY = 1 ==> Fifo empty! |-REG_SIM_CONF1 = 000c | |-REG_SIM_CONF1_CONFCHKPAR = 0 ==> Parity check on reception disabled. | |-REG_SIM_CONF1_CONFCODCONV = 0 ==> Coding convention is direct (normal). | |-REG_SIM_CONF1_CONFTXRX = 1 ==> SIO line direction is in transmit mode. | |-REG_SIM_CONF1_CONFSCLKEN = 1 ==> SIM clock in normal mode. | |-REG_SIM_CONF1_reserved = 0 ==> ETU period is CONFETUPERIOD. | |-REG_SIM_CONF1_CONFSCLKDIV = 0 ==> SIM clock frequency is 13/4 Mhz. | |-REG_SIM_CONF1_CONFSCLKLEV = 0 ==> SIM clock idle level is low. | |-REG_SIM_CONF1_CONFETUPERIOD = 0 ==> ETU period is 372/8*1/Fsclk. | |-REG_SIM_CONF1_CONFBYPASS = 0 ==> Hardware timers and start and stop sequences are normal. | |-REG_SIM_CONF1_CONFSVCCLEV = 0 ==> SVCC Level is low (Only valid when CONFBYPASS = 1). | |-REG_SIM_CONF1_CONFSRSTLEV = 0 ==> SRST Level is low (Only valid when CONFBYPASS = 1). | |-REG_SIM_CONF1_CONFTRIG = 0x0 (FIFO trigger level) | |-REG_SIM_CONF1_CONFSIOLOW = 0 |-REG_SIM_CONF2 = 0940 | |-REG_SIM_CONF2_CONFTFSIM = 0x0 (time delay for filtering of SIM_CD) | |-REG_SIM_CONF2_CONFTDSIM = 0x4 (time delay for contact activation/deactivation) | |-REG_SIM_CONF2_CONFWAITI = 0x9 (CONFWAITI overflow wait time between two received chars) |-REG_SIM_IT = 0000 | |-REG_SIM_IT_SIM_NATR = 0 ==> On read access to REG_SIM_IT. | |-REG_SIM_IT_SIM_WT = 0 ==> On read access to REG_SIM_IT. | |-REG_SIM_IT_SIM_OV = 0 ==> On read access to REG_SIM_IT. | |-REG_SIM_IT_SIM_TX = 0 ==> On write access to REG_SIM_DTX or on switching | | from transmit to receive mode (CONFTXRX bit) | |-REG_SIM_IT_SIM_RX = 0 ==> On read access to REG_SIM_DRX. |-REG_SIM_DRX = 0100 | |-REG_SIM_DRX_SIM_DRX = 0x0 (next data byte in FIFO available for reading) | |-REG_SIM_DRX_STATRXPAR = 1 ==> Parity Ok. |-REG_SIM_DTX = 00 (next data byte to be transmitted) |-REG_SIM_MASKIT = 003f | |-REG_SIM_MASKIT_MASK_SIM_NATR = 1 ==> No-answer-to-reset interrupt is masked. | |-REG_SIM_MASKIT_MASK_SIM_WT = 1 ==> Character wait-time overflow interrupt is masked. | |-REG_SIM_MASKIT_MASK_SIM_OV = 1 ==> Receive overflow interrupt is masked. | |-REG_SIM_MASKIT_MASK_SIM_TX = 1 ==> Waiting characters to be transmit interrupt is masked. | |-REG_SIM_MASKIT_MASK_SIM_RX = 1 ==> Waiting characters to be read interrupt is masked. | |-REG_SIM_MASKIT_MASK_SIM_CD = 1 ==> SIM card insertion/extraction interrupt is masked. |-REG_SIM_IT_CD = fffe0010 |-REG_SIM_IT_CD_IT_CD = 0 ==> SIM card insertion/extraction interrupt is unmasked. Power up simcard: * Power enabled! * Clock enabled! * Reset released! SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Character underflow! (0 bytes) Reset simcard: * Reset pulled down! * Reset released! SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Character underflow! (0 bytes) SIM-T0: Transceiving APDU-Header: (a0 a4 00 00 02) SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-T0: Case 2: No input / Output of known length (See also GSM 11.11 Page 34) SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Character underflow! SIM-T0: T0 Protocol error: Missing ACK byte -- aborting! SIM-T0: Transceiving APDU-Header: (a0 c0 00 00 0f) SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-T0: Case 4: Input / No output (See also GSM 11.11 Page 34) SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Character underflow! SIM-T0: T0 Protocol error: Incorrect or missing answer -- aborting! e0 73 d7 b9 ae ea bf 7e f7 3b 7f 6f 32 fe 25 (15 bytes) Test Phase 1: Testing bare sim commands... * Testing SELECT: Selecting MF SIM-T0: Transceiving APDU-Header: (a0 a4 00 00 02) SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-T0: Case 2: No input / Output of known length (See also GSM 11.11 Page 34) SIM-ISR: Interrupt caught: Waiting characters to be read... SIM-ISR: Interrupt caught: Character underflow! SIM-T0: T0 Protocol error: Missing ACK byte -- aborting! ==> Status word: ffff * Testing SELECT: Selecting DF_GSM SIM-T0: Transceiving APDU-Header: (a0 a4 00 00 02) SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... SIM-ISR: Interrupt caught: Waiting for character to transmit... At this point it hangs "forever" - well at least half hour.

7 11

GPRS decode tutorial
by Dario Lombardo 08 Nov '11

08 Nov '11

Hello everybody Not sure if someone has pointed it out already, but I'm getting stuck following the gprs decode tutorial [...] - Prepare OsmocomBB's burst_ind branch cd ~/gprs_sniffer/osmocom-bb git checkout origin/sylvain/burst_ind git checkout d1cb8ea9b784c7acbafbb2fdcedbdf4655c2f6f5 At this point I get fatal: reference is not a tree: d1cb8ea9b784c7acbafbb2fdcedbdf4655c2f6f5 Next step fails too... pretty obvious... # patch -p1 < ~/gprs_sniffer/gprs_multi.patch can't find file to patch at input line 5 [...] Can someone drive me to the right direction? Thanks! Dario

4 4

cp2102 (betemcu, B75937)
by lonelysurfer 08 Nov '11

08 Nov '11

...a never ending story: i have a working ftdi-ttl, but the cp2102-adapters (http://www.ebay.de/itm/USB-2-0-to-TTL-UART-6PIN-CP2102-Module-Serial-Conver…) with the same cable dont work under ubuntu or windows. if i rub the top of the 2.55mm with my finger random data appears. but the loader doesnt upload the firmware. i used the txd, rxd and gnd pins and checked the connections with a multimeter. i tested -m c123xor, -m c123 and the default firmware. flashing custom baudrates was no problem. drivers are installed correctly (stady ttyusb0 under ubuntu/ com1 under win). is there any hint? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/cp2102-betemcu-B75937-tp3489323p… Sent from the baseband-devel mailing list archive at Nabble.com.

1 0

Re: Pirelli never syncs
by Andres Berroa 07 Nov '11

07 Nov '11

I'm trying to sync to the 1800 or the 900 bands with the Pirelli, I'm not using 850/1900. I tried ccch_scan with different cells. I attached the logs. On Mon, Nov 7, 2011 at 11:48 AM, Sylvain Munaut <246tnt(a)gmail.com> wrote: > > The only thing it's different from you it's > > I live in the Caribbean, but I have GSM networks on all four bands. > > And what band are you trying to sync to ? And with which hardware ? > > The ARFCN of PCS and DCS are overlapped and so I have no idea how > 'mobile' behaves in that case. > > You can try the ccch_scan binary with the -a option to force going to > a cell and just see if the bcch sync works at all. > (for PCS ARFCN you have to add 32768 to the arfcn number). > > Cheers, > > Sylvain >

1 0

Pirelli never syncs
by Andres Berroa 07 Nov '11

07 Nov '11

Hello everybody, I bought several Pirelli DP-L10. I checked out the master branch of Osmocom, changed the console.h and sercomm.h, and enabled the CONFIG_TX_ENABLE option. The code compiled successfully. I loaded the compiled firmware onto the Pirelli with osmocon, and after it loaded, I ran cell_log and mobile. But the phone never syncs to a cell. I first tried with the "no stick" option. But after this, I tried to find a strong cell (I used a Blackberry 9300 for this, it has a nice engineering screen). I found cells from -76 dbm to -104 dbm. I tried them all with the "stick xxx" option, but still, the phone does not sync to this cells. The last thing I tried was using the binaries a friend provided me. He compiled the code on his computer, he tested those binaries at his home, with his Pirelli, and it worked: he could sync. He sent me those same binaries, but still no luck, the phone cannot sync. I have tried this on 4 different computers, 2 different versions of Ubuntu, on Debian, and on a Mac. It doesn't seem it's an operating system problem, but I wanted to test it anyway. The only thing it's different from you it's I live in the Caribbean, but I have GSM networks on all four bands. Now, if I use my sim on the Pirelli, with the original firmware, it works. I can even make a call, so I think it's not a hardware problem. I tested with Nokia C118 on a 850Mhz network, but same story. I'm posting my mobile.cfg file, and some logs. Thank you for your help.

1 0

Re: delay in SIM reader interrupt handler
by Dieter Spaar 01 Nov '11

01 Nov '11

Hello Andreas, On Tue, 01 Nov 2011 12:28:05 +0100, "jolly" <andreas(a)eversberg.eu> wrote: > > i removed the delay, and it works. i checked the tsm30 source code. it > also sets the IO to input right after writing the last TX byte. (i guess > that the controller will trigger the IO switching at the end of > transmission.) so why do we need that delay? are there any problems? I can't tell you exactly what went wrong (it was months ago that I worked on this part). But most certainly one of my Test SIMs did not work without this delay. So I would suggest to leave a comment at this place in case problems with certain SIMs occur. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

1 0

delay in SIM reader interrupt handler
by jolly 01 Nov '11

01 Nov '11

hi dieter, i like to clean up and merge the sim reader code with master branch. while looking at the code i found a delay_ms(1) in interrupt handler: ------- /* Used by: calypso_sim_transmit() to transmit the data */ if(regVal & REG_SIM_IT_SIM_TX) { #if (SIM_DEBUG == 1) puts(" Waiting for transmit...\n"); #endif if(sim_tx_character_count >= sim_tx_character_length) { txDoneFlag = 1; } else { writew(*tx_buffer,REG_SIM_DTX); tx_buffer++; sim_tx_character_count++; #if 1 /* Dieter: set to 0 to get problems with some cards */ /* its essential to immediately switch to RX after TX is done */ if(sim_tx_character_count >= sim_tx_character_length) { /* TODO: set a proper delay here, 4 is to long if not debugging and no delay is too short */ delay_ms(1); /* Switch I/O direction to input */ writew(readw(REG_SIM_CONF1) & ~REG_SIM_CONF1_CONFTXRX, REG_SIM_CONF1); } #endif } } --------- i removed the delay, and it works. i checked the tsm30 source code. it also sets the IO to input right after writing the last TX byte. (i guess that the controller will trigger the IO switching at the end of transmission.) so why do we need that delay? are there any problems? regards, andreas

1 0

SMS support for osmocombb
by Andreas Eversberg 31 Oct '11

31 Oct '11

hi, i just finished SMS support for osmocombb. everything is committed in my jolly/testing branch. in order to support SMS, i extracted the SMS transcoding from openbsc. (jolly/sms branch) the SMC and SMR layer protocols are extracted and rewritten and use messages between layers and have state machines. they are added to libosmocore also. (jolly/sms branch) openbsc (jolly/sms branch) now uses the SMS layers and transcoding of libosmocore. LAPDm now supports correct handling of SAPI 3 datalink, especially on SACCH. the mobility management and radio ressource layers of osmocombb now support MM connections with SAPI 3. i have tested it on test BTS setup only, so feel free to run it and report bugs. regards, andreas

1 0

Problems while building osmocomBB
by Begerad Stefan 28 Oct '11

28 Oct '11

Hi guys, I dunno if that is the right place for my concern about building the osmocomBB source. Here is what I already have done: - downloading the sources for osmocomBB and GNU toolchain for ARM, - setting the PATH for the arm-elf-* executables, - calling make in the src directory. Now, this appears as response of the make command in the terminal: cd shared/libosmocore/build-host && ../configure configure: error: cannot find install-sh, install.sh, or shtool in ".." "../.." "../../.." make: *** [shared/libosmocore/build-host/Makefile] Error 1. If you need details about my system, you can look at the following snippet from the config.log file: This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by libosmocore configure UNKNOWN, which was generated by GNU Autoconf 2.65. Invocation command line was $ ../configure ## --------- ## ## Platform. ## ## --------- ## hostname = ubuntu-stefan uname -m = x86_64 uname -r = 2.6.32-24-generic uname -s = Linux uname -v = #41-Ubuntu SMP Thu Aug 19 01:38:40 UTC 2010 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin PATH: /usr/games PATH: /home/stefan/osmocomBB/gnuarm-4.0.2/bin ## ----------- ## ## Core tests. ## ## ----------- ## configure:2032: error: cannot find install-sh, install.sh, or shtool in ".." "../.." "../../..". So, I would be very glad, if someone could give me a hint to solve the problem. Thank you in advance. Regards, begy

2 2

moving SMS core code into libosmocore
by jolly 24 Oct '11

24 Oct '11

hi, i am thinking about moving sms code from openbsc to libsomocore. my idea is to move the core code of openbsc to libosmocore's src/gsm and include/osmocom/gsm/ respectively. one problem is that the transaction structure of osmocombb and openbsc is different. for sms support there could be a common part inside the union of each transaction: struct gsm_trans { ... union { ... struct { uint8_t link_id; /* RSL Link ID to be used for this trans */ int is_mt; /* is this a MO (0) or MT (1) transfer */ enum gsm411_cp_state cp_state; struct osmo_timer_list cp_timer; enum gsm411_rp_state rp_state; struct gsm_sms *sms; } sms; }; }; i would suggest to move the common part to libosmocore and name it "gsm_trans_sms". then both openbsc and osmocombb can use the same sms structure. also the "gsm_sms" structure itself must be generalized and not rely on openbsc structures. (i have not yet looked at it.) to get reference to the private gsm_trans, openbsc and osmocombb can now use "container_of" in the specific sms glue code. any ideas / suggestions? andreas

1 0

GSM Muti-antenna Receiver
by 天行 23 Oct '11

23 Oct '11

Hi all: I try make usrp work on Muti-antenna mode , 1 to downlink , 1 to uplink. first , i only decode downlink, it can found FCCH,but can't decode sch. any suggestion? tianxing@tianxing-MS-7345:~/gsm/airprobe-gprs/gsm-receiver/src/python$ ./gsm_reive_usrp_mono.py -c 122 A side: Flex 900 Rx MIMO B B side: Flex 900 Rx MIMO B gain_a: 45.0 gain_b: 45.0 A side: The carrier frequency is set as 959400000.0 B side: The carrier frequency is set as 959400000.0 mux_val = 0x2301 input_rate: 571428.571429 sample rate: 0.527472527473 filter_cutoff: 145000.0 filter_t_width: 10000.0 >>> gr_fir_ccc: using SSE input_rate: 571428.571429 sample rate: 0.527472527473 filter_cutoff: 145000.0 filter_t_width: 10000.0 >>> gr_fir_ccf: using SSE Key: '0000000000000000' Configuration: '0C' Configuration TS: 0 configure_receiver 1319360150.211137 3014114160: fcch found on position: 24508 1319360150.211206 3014114160: freq_offset: -2659.853516 1319360150.254086 3014114160: fcch found on position: 77189 1319360150.254132 3014114160: freq_offset: -261.283386 sch.c:260 ERR: conv_decode 11 1319360150.307770 3014114160: fcch found on position: 135276 1319360150.307814 3014114160: freq_offset: -2574.190186 sch.c:260 ERR: conv_decode 10 1319360150.352075 3014114160: fcch found on position: 188023 1319360150.352120 3014114160: freq_offset: -375.097321 sch.c:260 ERR: conv_decode 8

1 0

AMR support
by Aegean Chou 23 Oct '11

23 Oct '11

Hi, all The osmocomBB no AMR support yet now (only FR, HR and EFR). /* no AMR yet */ void dsp_load_tch_param(struct gsm_time *next_time, if (tch_mode) { switch (l1s.tch_mode) { case GSM48_CMODE_SPEECH_V1: *tch_mode = *tch_f_hn ? TCH_FS_MODE : TCH_HS_MODE; break; case GSM48_CMODE_SPEECH_EFR: *tch_mode = *tch_f_hn ? TCH_EFR_MODE : SIG_ONLY_MODE; break; default: *tch_mode = SIG_ONLY_MODE; } } i checked the product datasheet, the C123 can support AMR from the beginning. does anyone can give me some information to patch it? BTW, i havn't 30 source, so i can't reference it. Best regards Aegean Chou

2 1

Build fails on OSX Lion
by Martin Auer 21 Oct '11

21 Oct '11

Hi, when I try to build osmocombb on OSX Lion with MacPorts it fails because it cannot find linux/serial.h. I think it is needed to set some data rate for RS232? Is there a way to overcome this for OSX? Thanks in advance, Martin ../../src/serial.c:41:26: error: linux/serial.h: No such file or directory bash-3.2# make -e CROSS_TOOL_PREFIX=arm-elf-gcc-4.6 cd shared/libosmocore && autoreconf -i glibtoolize: putting auxiliary files in `.'. glibtoolize: copying file `./ltmain.sh' glibtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. glibtoolize: copying file `m4/libtool.m4' glibtoolize: copying file `m4/ltoptions.m4' glibtoolize: copying file `m4/ltsugar.m4' glibtoolize: copying file `m4/ltversion.m4' glibtoolize: copying file `m4/lt~obsolete.m4' configure.ac:14: installing `./config.sub' configure.ac:5: installing `./missing' configure.ac:5: installing `./install-sh' configure.ac:14: installing `./config.guess' src/Makefile.am: installing `./depcomp' mkdir shared/libosmocore/build-target cd shared/libosmocore/build-target && ../configure \ --host=arm-elf --enable-embedded --disable-shared \ --disable-tests ac_cv_header_sys_select_h=no \ --disable-tests ac_cv_header_sys_socket_h=no \ CFLAGS="-Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs" configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ../install-sh -c -d checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking for arm-elf-strip... arm-elf-strip checking whether make sets $(MAKE)... (cached) yes checking for arm-elf-gcc... arm-elf-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether arm-elf-gcc accepts -g... yes checking for arm-elf-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of arm-elf-gcc... gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking build system type... i386-apple-darwin11.1.0 checking host system type... arm-unknown-elf checking how to print strings... printf checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by arm-elf-gcc... /Volumes/Speicher/opt/local/arm-elf/bin/ld checking if the linker (/Volumes/Speicher/opt/local/arm-elf/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /opt/local/bin//arm-elf-nm -B checking the name lister (/opt/local/bin//arm-elf-nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 196608 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /Volumes/Speicher/opt/local/arm-elf/bin/ld option to reload object files... -r checking for arm-elf-objdump... arm-elf-objdump checking how to recognize dependent libraries... unknown checking for arm-elf-ar... arm-elf-ar checking for arm-elf-strip... (cached) arm-elf-strip checking for arm-elf-ranlib... arm-elf-ranlib checking command to parse /opt/local/bin//arm-elf-nm -B output from arm-elf-gcc object... ok checking how to run the C preprocessor... arm-elf-gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... no checking for objdir... .libs checking if arm-elf-gcc supports -fno-rtti -fno-exceptions... no checking for arm-elf-gcc option to produce PIC... -fPIC -DPIC checking if arm-elf-gcc PIC flag -fPIC -DPIC works... yes checking if arm-elf-gcc static flag -static works... yes checking if arm-elf-gcc supports -c -o file.o... yes checking if arm-elf-gcc supports -c -o file.o... (cached) yes checking whether the arm-elf-gcc linker (/Volumes/Speicher/opt/local/arm-elf/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... no checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... no checking whether to build shared libraries... no checking whether to build static libraries... yes checking for ANSI C header files... (cached) yes checking execinfo.h usability... no checking execinfo.h presence... no checking for execinfo.h... no checking for sys/select.h... (cached) no checking for sys/socket.h... (cached) no checking syslog.h usability... no checking syslog.h presence... no checking for syslog.h... no checking ctype.h usability... yes checking ctype.h presence... yes checking for ctype.h... yes checking for doxygen... false checking if arm-elf-gcc supports -fvisibility=hidden... yes configure: creating ./config.status config.status: creating libosmocore.pc config.status: creating libosmocodec.pc config.status: creating libosmovty.pc config.status: creating libosmogsm.pc config.status: creating include/osmocom/Makefile config.status: creating include/osmocom/vty/Makefile config.status: creating include/osmocom/codec/Makefile config.status: creating include/osmocom/crypt/Makefile config.status: creating include/osmocom/gsm/Makefile config.status: creating include/osmocom/gsm/protocol/Makefile config.status: creating include/osmocom/core/Makefile config.status: creating include/Makefile config.status: creating src/Makefile config.status: creating src/vty/Makefile config.status: creating src/codec/Makefile config.status: creating src/gsm/Makefile config.status: creating tests/Makefile config.status: creating tests/timer/Makefile config.status: creating tests/sms/Makefile config.status: creating tests/msgfile/Makefile config.status: creating tests/ussd/Makefile config.status: creating tests/smscb/Makefile config.status: creating tests/bits/Makefile config.status: creating utils/Makefile config.status: creating Doxyfile.core config.status: creating Doxyfile.gsm config.status: creating Doxyfile.vty config.status: creating Doxyfile.codec config.status: creating Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands cd shared/libosmocore/build-target && make echo UNKNOWN > ../.version-t && mv ../.version-t ../.version make all-recursive Making all in include Making all in osmocom Making all in codec make[5]: Nothing to be done for `all'. Making all in crypt make[5]: Nothing to be done for `all'. Making all in gsm Making all in protocol make[6]: Nothing to be done for `all'. make[6]: Nothing to be done for `all-am'. Making all in core make[5]: Nothing to be done for `all'. make[5]: Nothing to be done for `all-am'. make[4]: Nothing to be done for `all-am'. Making all in src Making all in . /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT timer.lo -MD -MP -MF .deps/timer.Tpo -c -o timer.lo ../../src/timer.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT timer.lo -MD -MP -MF .deps/timer.Tpo -c ../../src/timer.c -o timer.o mv -f .deps/timer.Tpo .deps/timer.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT select.lo -MD -MP -MF .deps/select.Tpo -c -o select.lo ../../src/select.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT select.lo -MD -MP -MF .deps/select.Tpo -c ../../src/select.c -o select.o mv -f .deps/select.Tpo .deps/select.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT signal.lo -MD -MP -MF .deps/signal.Tpo -c -o signal.lo ../../src/signal.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT signal.lo -MD -MP -MF .deps/signal.Tpo -c ../../src/signal.c -o signal.o mv -f .deps/signal.Tpo .deps/signal.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT msgb.lo -MD -MP -MF .deps/msgb.Tpo -c -o msgb.lo ../../src/msgb.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT msgb.lo -MD -MP -MF .deps/msgb.Tpo -c ../../src/msgb.c -o msgb.o mv -f .deps/msgb.Tpo .deps/msgb.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT bits.lo -MD -MP -MF .deps/bits.Tpo -c -o bits.lo ../../src/bits.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT bits.lo -MD -MP -MF .deps/bits.Tpo -c ../../src/bits.c -o bits.o mv -f .deps/bits.Tpo .deps/bits.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT bitvec.lo -MD -MP -MF .deps/bitvec.Tpo -c -o bitvec.lo ../../src/bitvec.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT bitvec.lo -MD -MP -MF .deps/bitvec.Tpo -c ../../src/bitvec.c -o bitvec.o mv -f .deps/bitvec.Tpo .deps/bitvec.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT statistics.lo -MD -MP -MF .deps/statistics.Tpo -c -o statistics.lo ../../src/statistics.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT statistics.lo -MD -MP -MF .deps/statistics.Tpo -c ../../src/statistics.c -o statistics.o ../../src/statistics.c: In function 'osmo_counter_get_by_name': ../../src/statistics.c:72:3: warning: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration] mv -f .deps/statistics.Tpo .deps/statistics.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT write_queue.lo -MD -MP -MF .deps/write_queue.Tpo -c -o write_queue.lo ../../src/write_queue.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT write_queue.lo -MD -MP -MF .deps/write_queue.Tpo -c ../../src/write_queue.c -o write_queue.o mv -f .deps/write_queue.Tpo .deps/write_queue.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT utils.lo -MD -MP -MF .deps/utils.Tpo -c -o utils.lo ../../src/utils.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT utils.lo -MD -MP -MF .deps/utils.Tpo -c ../../src/utils.c -o utils.o ../../src/utils.c: In function 'get_value_string': ../../src/utils.c:33:2: warning: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'uint32_t' [-Wformat] ../../src/utils.c: In function 'get_string_value': ../../src/utils.c:49:3: warning: implicit declaration of function 'strcasecmp' [-Wimplicit-function-declaration] mv -f .deps/utils.Tpo .deps/utils.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT socket.lo -MD -MP -MF .deps/socket.Tpo -c -o socket.lo ../../src/socket.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT socket.lo -MD -MP -MF .deps/socket.Tpo -c ../../src/socket.c -o socket.o mv -f .deps/socket.Tpo .deps/socket.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT logging.lo -MD -MP -MF .deps/logging.Tpo -c -o logging.lo ../../src/logging.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT logging.lo -MD -MP -MF .deps/logging.Tpo -c ../../src/logging.c -o logging.o ../../src/logging.c: In function 'log_parse_category_mask': ../../src/logging.c:162:2: warning: implicit declaration of function 'strdup' [-Wimplicit-function-declaration] ../../src/logging.c:162:15: warning: incompatible implicit declaration of built-in function 'strdup' [enabled by default] ../../src/logging.c:169:2: warning: implicit declaration of function 'strtok' [-Wimplicit-function-declaration] ../../src/logging.c:169:17: warning: assignment makes pointer from integer without a cast [enabled by default] ../../src/logging.c:172:4: warning: implicit declaration of function 'strstr' [-Wimplicit-function-declaration] ../../src/logging.c:172:18: warning: incompatible implicit declaration of built-in function 'strstr' [enabled by default] ../../src/logging.c:197:27: warning: assignment makes pointer from integer without a cast [enabled by default] ../../src/logging.c: In function '_file_output': ../../src/logging.c:427:2: warning: implicit declaration of function 'fprintf' [-Wimplicit-function-declaration] ../../src/logging.c:427:2: warning: incompatible implicit declaration of built-in function 'fprintf' [enabled by default] ../../src/logging.c:428:2: warning: implicit declaration of function 'fflush' [-Wimplicit-function-declaration] ../../src/logging.c: In function 'log_target_create_file': ../../src/logging.c:500:2: warning: implicit declaration of function 'fopen' [-Wimplicit-function-declaration] ../../src/logging.c:500:23: warning: assignment makes pointer from integer without a cast [enabled by default] ../../src/logging.c: In function 'log_target_find': ../../src/logging.c:524:4: warning: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration] ../../src/logging.c: In function 'log_target_destroy': ../../src/logging.c:546:4: warning: implicit declaration of function 'fclose' [-Wimplicit-function-declaration] ../../src/logging.c: In function 'log_target_file_reopen': ../../src/logging.c:559:23: warning: assignment makes pointer from integer without a cast [enabled by default] mv -f .deps/logging.Tpo .deps/logging.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT logging_syslog.lo -MD -MP -MF .deps/logging_syslog.Tpo -c -o logging_syslog.lo ../../src/logging_syslog.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT logging_syslog.lo -MD -MP -MF .deps/logging_syslog.Tpo -c ../../src/logging_syslog.c -o logging_syslog.o mv -f .deps/logging_syslog.Tpo .deps/logging_syslog.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT rate_ctr.lo -MD -MP -MF .deps/rate_ctr.Tpo -c -o rate_ctr.lo ../../src/rate_ctr.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT rate_ctr.lo -MD -MP -MF .deps/rate_ctr.Tpo -c ../../src/rate_ctr.c -o rate_ctr.o ../../src/rate_ctr.c: In function 'rate_ctr_get_group_by_name_idx': ../../src/rate_ctr.c:153:3: warning: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration] mv -f .deps/rate_ctr.Tpo .deps/rate_ctr.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsmtap_util.lo -MD -MP -MF .deps/gsmtap_util.Tpo -c -o gsmtap_util.lo ../../src/gsmtap_util.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsmtap_util.lo -MD -MP -MF .deps/gsmtap_util.Tpo -c ../../src/gsmtap_util.c -o gsmtap_util.o mv -f .deps/gsmtap_util.Tpo .deps/gsmtap_util.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT crc16.lo -MD -MP -MF .deps/crc16.Tpo -c -o crc16.lo ../../src/crc16.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT crc16.lo -MD -MP -MF .deps/crc16.Tpo -c ../../src/crc16.c -o crc16.o mv -f .deps/crc16.Tpo .deps/crc16.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT panic.lo -MD -MP -MF .deps/panic.Tpo -c -o panic.lo ../../src/panic.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT panic.lo -MD -MP -MF .deps/panic.Tpo -c ../../src/panic.c -o panic.o mv -f .deps/panic.Tpo .deps/panic.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT backtrace.lo -MD -MP -MF .deps/backtrace.Tpo -c -o backtrace.lo ../../src/backtrace.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT backtrace.lo -MD -MP -MF .deps/backtrace.Tpo -c ../../src/backtrace.c -o backtrace.o mv -f .deps/backtrace.Tpo .deps/backtrace.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT conv.lo -MD -MP -MF .deps/conv.Tpo -c -o conv.lo ../../src/conv.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT conv.lo -MD -MP -MF .deps/conv.Tpo -c ../../src/conv.c -o conv.o mv -f .deps/conv.Tpo .deps/conv.Plo /bin/sh ../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT application.lo -MD -MP -MF .deps/application.Tpo -c -o application.lo ../../src/application.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT application.lo -MD -MP -MF .deps/application.Tpo -c ../../src/application.c -o application.o mv -f .deps/application.Tpo .deps/application.Plo /bin/sh ../libtool --tag=CC --mode=link arm-elf-gcc -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -version-info 2:0:0 -o libosmocore.la -rpath /usr/local/lib timer.lo select.lo signal.lo msgb.lo bits.lo bitvec.lo statistics.lo write_queue.lo utils.lo socket.lo logging.lo logging_syslog.lo rate_ctr.lo gsmtap_util.lo crc16.lo panic.lo backtrace.lo conv.lo application.lo libtool: link: arm-elf-ar cru .libs/libosmocore.a timer.o select.o signal.o msgb.o bits.o bitvec.o statistics.o write_queue.o utils.o socket.o logging.o logging_syslog.o rate_ctr.o gsmtap_util.o crc16.o panic.o backtrace.o conv.o application.o libtool: link: arm-elf-ranlib .libs/libosmocore.a libtool: link: ( cd ".libs" && rm -f "libosmocore.la" && ln -s "../libosmocore.la" "libosmocore.la" ) Making all in vty make[4]: Nothing to be done for `all'. Making all in codec /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/codec -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm610.lo -MD -MP -MF .deps/gsm610.Tpo -c -o gsm610.lo ../../../src/codec/gsm610.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/codec -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm610.lo -MD -MP -MF .deps/gsm610.Tpo -c ../../../src/codec/gsm610.c -o gsm610.o mv -f .deps/gsm610.Tpo .deps/gsm610.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/codec -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm620.lo -MD -MP -MF .deps/gsm620.Tpo -c -o gsm620.lo ../../../src/codec/gsm620.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/codec -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm620.lo -MD -MP -MF .deps/gsm620.Tpo -c ../../../src/codec/gsm620.c -o gsm620.o mv -f .deps/gsm620.Tpo .deps/gsm620.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/codec -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm660.lo -MD -MP -MF .deps/gsm660.Tpo -c -o gsm660.lo ../../../src/codec/gsm660.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/codec -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm660.lo -MD -MP -MF .deps/gsm660.Tpo -c ../../../src/codec/gsm660.c -o gsm660.o mv -f .deps/gsm660.Tpo .deps/gsm660.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/codec -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm690.lo -MD -MP -MF .deps/gsm690.Tpo -c -o gsm690.lo ../../../src/codec/gsm690.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/codec -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm690.lo -MD -MP -MF .deps/gsm690.Tpo -c ../../../src/codec/gsm690.c -o gsm690.o mv -f .deps/gsm690.Tpo .deps/gsm690.Plo /bin/sh ../../libtool --tag=CC --mode=link arm-elf-gcc -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -o libosmocodec.la -rpath /usr/local/lib gsm610.lo gsm620.lo gsm660.lo gsm690.lo libtool: link: arm-elf-ar cru .libs/libosmocodec.a gsm610.o gsm620.o gsm660.o gsm690.o libtool: link: arm-elf-ranlib .libs/libosmocodec.a libtool: link: ( cd ".libs" && rm -f "libosmocodec.la" && ln -s "../libosmocodec.la" "libosmocodec.la" ) Making all in gsm /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT a5.lo -MD -MP -MF .deps/a5.Tpo -c -o a5.lo ../../../src/gsm/a5.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT a5.lo -MD -MP -MF .deps/a5.Tpo -c ../../../src/gsm/a5.c -o a5.o mv -f .deps/a5.Tpo .deps/a5.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT rxlev_stat.lo -MD -MP -MF .deps/rxlev_stat.Tpo -c -o rxlev_stat.lo ../../../src/gsm/rxlev_stat.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT rxlev_stat.lo -MD -MP -MF .deps/rxlev_stat.Tpo -c ../../../src/gsm/rxlev_stat.c -o rxlev_stat.o mv -f .deps/rxlev_stat.Tpo .deps/rxlev_stat.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT tlv_parser.lo -MD -MP -MF .deps/tlv_parser.Tpo -c -o tlv_parser.lo ../../../src/gsm/tlv_parser.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT tlv_parser.lo -MD -MP -MF .deps/tlv_parser.Tpo -c ../../../src/gsm/tlv_parser.c -o tlv_parser.o mv -f .deps/tlv_parser.Tpo .deps/tlv_parser.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT comp128.lo -MD -MP -MF .deps/comp128.Tpo -c -o comp128.lo ../../../src/gsm/comp128.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT comp128.lo -MD -MP -MF .deps/comp128.Tpo -c ../../../src/gsm/comp128.c -o comp128.o mv -f .deps/comp128.Tpo .deps/comp128.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm_utils.lo -MD -MP -MF .deps/gsm_utils.Tpo -c -o gsm_utils.lo ../../../src/gsm/gsm_utils.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm_utils.lo -MD -MP -MF .deps/gsm_utils.Tpo -c ../../../src/gsm/gsm_utils.c -o gsm_utils.o ../../../src/gsm/gsm_utils.c: In function 'gsm_7bit_encode': ../../../src/gsm/gsm_utils.c:253:13: warning: variable 'z' set but not used [-Wunused-but-set-variable] mv -f .deps/gsm_utils.Tpo .deps/gsm_utils.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT rsl.lo -MD -MP -MF .deps/rsl.Tpo -c -o rsl.lo ../../../src/gsm/rsl.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT rsl.lo -MD -MP -MF .deps/rsl.Tpo -c ../../../src/gsm/rsl.c -o rsl.o mv -f .deps/rsl.Tpo .deps/rsl.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm48.lo -MD -MP -MF .deps/gsm48.Tpo -c -o gsm48.lo ../../../src/gsm/gsm48.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm48.lo -MD -MP -MF .deps/gsm48.Tpo -c ../../../src/gsm/gsm48.c -o gsm48.o ../../../src/gsm/gsm48.c: In function 'gsm48_mi_to_string': ../../../src/gsm/gsm48.c:348:4: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'uint32_t' [-Wformat] mv -f .deps/gsm48.Tpo .deps/gsm48.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm48_ie.lo -MD -MP -MF .deps/gsm48_ie.Tpo -c -o gsm48_ie.lo ../../../src/gsm/gsm48_ie.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm48_ie.lo -MD -MP -MF .deps/gsm48_ie.Tpo -c ../../../src/gsm/gsm48_ie.c -o gsm48_ie.o mv -f .deps/gsm48_ie.Tpo .deps/gsm48_ie.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm0808.lo -MD -MP -MF .deps/gsm0808.Tpo -c -o gsm0808.lo ../../../src/gsm/gsm0808.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm0808.lo -MD -MP -MF .deps/gsm0808.Tpo -c ../../../src/gsm/gsm0808.c -o gsm0808.o mv -f .deps/gsm0808.Tpo .deps/gsm0808.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT sysinfo.lo -MD -MP -MF .deps/sysinfo.Tpo -c -o sysinfo.lo ../../../src/gsm/sysinfo.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT sysinfo.lo -MD -MP -MF .deps/sysinfo.Tpo -c ../../../src/gsm/sysinfo.c -o sysinfo.o mv -f .deps/sysinfo.Tpo .deps/sysinfo.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gprs_cipher_core.lo -MD -MP -MF .deps/gprs_cipher_core.Tpo -c -o gprs_cipher_core.lo ../../../src/gsm/gprs_cipher_core.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gprs_cipher_core.lo -MD -MP -MF .deps/gprs_cipher_core.Tpo -c ../../../src/gsm/gprs_cipher_core.c -o gprs_cipher_core.o mv -f .deps/gprs_cipher_core.Tpo .deps/gprs_cipher_core.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm0480.lo -MD -MP -MF .deps/gsm0480.Tpo -c -o gsm0480.lo ../../../src/gsm/gsm0480.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm0480.lo -MD -MP -MF .deps/gsm0480.Tpo -c ../../../src/gsm/gsm0480.c -o gsm0480.o ../../../src/gsm/gsm0480.c: In function 'parse_process_uss_req': ../../../src/gsm/gsm0480.c:405:7: warning: pointer targets in passing argument 1 of 'gsm_7bit_decode' differ in signedness [-Wpointer-sign] ../../../include/osmocom/gsm/gsm_utils.h:59:5: note: expected 'char *' but argument is of type 'uint8_t *' mv -f .deps/gsm0480.Tpo .deps/gsm0480.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT abis_nm.lo -MD -MP -MF .deps/abis_nm.Tpo -c -o abis_nm.lo ../../../src/gsm/abis_nm.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT abis_nm.lo -MD -MP -MF .deps/abis_nm.Tpo -c ../../../src/gsm/abis_nm.c -o abis_nm.o mv -f .deps/abis_nm.Tpo .deps/abis_nm.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm0502.lo -MD -MP -MF .deps/gsm0502.Tpo -c -o gsm0502.lo ../../../src/gsm/gsm0502.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT gsm0502.lo -MD -MP -MF .deps/gsm0502.Tpo -c ../../../src/gsm/gsm0502.c -o gsm0502.o mv -f .deps/gsm0502.Tpo .deps/gsm0502.Plo /bin/sh ../../libtool --tag=CC --mode=compile arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT lapdm.lo -MD -MP -MF .deps/lapdm.Tpo -c -o lapdm.lo ../../../src/gsm/lapdm.c libtool: compile: arm-elf-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../../src/gsm -I../../../include -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -MT lapdm.lo -MD -MP -MF .deps/lapdm.Tpo -c ../../../src/gsm/lapdm.c -o lapdm.o ../../../src/gsm/lapdm.c: In function 'lapdm_t200_cb': ../../../src/gsm/lapdm.c:608:2: warning: format '%u' expects argument of type 'unsigned int', but argument 8 has type 'uint32_t' [-Wformat] ../../../src/gsm/lapdm.c:710:3: warning: format '%u' expects argument of type 'unsigned int', but argument 7 has type 'uint32_t' [-Wformat] ../../../src/gsm/lapdm.c: In function 'lapdm_rx_u': ../../../src/gsm/lapdm.c:1136:5: warning: implicit declaration of function 'memcmp' [-Wimplicit-function-declaration] ../../../src/gsm/lapdm.c: In function 'rslms_rx_rll_est_req': ../../../src/gsm/lapdm.c:1800:12: warning: assignment discards 'const' qualifier from pointer target type [enabled by default] ../../../src/gsm/lapdm.c: In function 'rslms_rx_rll_udata_req': ../../../src/gsm/lapdm.c:1892:11: warning: assignment discards 'const' qualifier from pointer target type [enabled by default] ../../../src/gsm/lapdm.c: In function 'rslms_rx_rll_data_req': ../../../src/gsm/lapdm.c:1934:11: warning: assignment discards 'const' qualifier from pointer target type [enabled by default] mv -f .deps/lapdm.Tpo .deps/lapdm.Plo /bin/sh ../../libtool --tag=CC --mode=link arm-elf-gcc -fPIC -Wall -Os -ffunction-sections -I/opt/local/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs -version-info 1:0:0 -o libosmogsm.la -rpath /usr/local/lib a5.lo rxlev_stat.lo tlv_parser.lo comp128.lo gsm_utils.lo rsl.lo gsm48.lo gsm48_ie.lo gsm0808.lo sysinfo.lo gprs_cipher_core.lo gsm0480.lo abis_nm.lo gsm0502.lo lapdm.lo ../../src/libosmocore.la libtool: link: arm-elf-ar cru .libs/libosmogsm.a a5.o rxlev_stat.o tlv_parser.o comp128.o gsm_utils.o rsl.o gsm48.o gsm48_ie.o gsm0808.o sysinfo.o gprs_cipher_core.o gsm0480.o abis_nm.o gsm0502.o lapdm.o libtool: link: arm-elf-ranlib .libs/libosmogsm.a libtool: link: ( cd ".libs" && rm -f "libosmogsm.la" && ln -s "../libosmogsm.la" "libosmogsm.la" ) Making all in tests make[4]: Nothing to be done for `all-am'. Making all in utils make[3]: Nothing to be done for `all'. make[3]: Nothing to be done for `all-am'. mkdir shared/libosmocore/build-host cd shared/libosmocore/build-host && ../configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ../install-sh -c -d checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes checking whether make sets $(MAKE)... (cached) yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking build system type... i386-apple-darwin11.1.0 checking host system type... i386-apple-darwin11.1.0 checking how to print strings... printf checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld checking if the linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) is GNU ld... no checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm checking the name lister (/usr/bin/nm) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 196608 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld option to reload object files... -r checking for objdump... no checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm output from gcc object... ok checking for dsymutil... dsymutil checking for nmedit... nmedit checking for lipo... lipo checking for otool... otool checking for otool64... no checking for -single_module linker flag... yes checking for -exported_symbols_list linker flag... yes checking for -force_load linker flag... yes checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fno-common -DPIC checking if gcc PIC flag -fno-common -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports shared libraries... yes checking dynamic linker characteristics... darwin11.1.0 dyld checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for ANSI C header files... (cached) yes checking execinfo.h usability... yes checking execinfo.h presence... yes checking for execinfo.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking syslog.h usability... yes checking syslog.h presence... yes checking for syslog.h... yes checking ctype.h usability... yes checking ctype.h presence... yes checking for ctype.h... yes checking for doxygen... false checking if gcc supports -fvisibility=hidden... yes configure: creating ./config.status config.status: creating libosmocore.pc config.status: creating libosmocodec.pc config.status: creating libosmovty.pc config.status: creating libosmogsm.pc config.status: creating include/osmocom/Makefile config.status: creating include/osmocom/vty/Makefile config.status: creating include/osmocom/codec/Makefile config.status: creating include/osmocom/crypt/Makefile config.status: creating include/osmocom/gsm/Makefile config.status: creating include/osmocom/gsm/protocol/Makefile config.status: creating include/osmocom/core/Makefile config.status: creating include/Makefile config.status: creating src/Makefile config.status: creating src/vty/Makefile config.status: creating src/codec/Makefile config.status: creating src/gsm/Makefile config.status: creating tests/Makefile config.status: creating tests/timer/Makefile config.status: creating tests/sms/Makefile config.status: creating tests/msgfile/Makefile config.status: creating tests/ussd/Makefile config.status: creating tests/smscb/Makefile config.status: creating tests/bits/Makefile config.status: creating utils/Makefile config.status: creating Doxyfile.core config.status: creating Doxyfile.gsm config.status: creating Doxyfile.vty config.status: creating Doxyfile.codec config.status: creating Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands cd shared/libosmocore/build-host && make make all-recursive Making all in include Making all in osmocom Making all in vty make[5]: Nothing to be done for `all'. Making all in codec make[5]: Nothing to be done for `all'. Making all in crypt make[5]: Nothing to be done for `all'. Making all in gsm Making all in protocol make[6]: Nothing to be done for `all'. make[6]: Nothing to be done for `all-am'. Making all in core make[5]: Nothing to be done for `all'. make[5]: Nothing to be done for `all-am'. make[4]: Nothing to be done for `all-am'. Making all in src Making all in . /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT timer.lo -MD -MP -MF .deps/timer.Tpo -c -o timer.lo ../../src/timer.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT timer.lo -MD -MP -MF .deps/timer.Tpo -c ../../src/timer.c -fno-common -DPIC -o .libs/timer.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT timer.lo -MD -MP -MF .deps/timer.Tpo -c ../../src/timer.c -o timer.o >/dev/null 2>&1 mv -f .deps/timer.Tpo .deps/timer.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT select.lo -MD -MP -MF .deps/select.Tpo -c -o select.lo ../../src/select.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT select.lo -MD -MP -MF .deps/select.Tpo -c ../../src/select.c -fno-common -DPIC -o .libs/select.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT select.lo -MD -MP -MF .deps/select.Tpo -c ../../src/select.c -o select.o >/dev/null 2>&1 mv -f .deps/select.Tpo .deps/select.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT signal.lo -MD -MP -MF .deps/signal.Tpo -c -o signal.lo ../../src/signal.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT signal.lo -MD -MP -MF .deps/signal.Tpo -c ../../src/signal.c -fno-common -DPIC -o .libs/signal.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT signal.lo -MD -MP -MF .deps/signal.Tpo -c ../../src/signal.c -o signal.o >/dev/null 2>&1 mv -f .deps/signal.Tpo .deps/signal.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT msgb.lo -MD -MP -MF .deps/msgb.Tpo -c -o msgb.lo ../../src/msgb.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT msgb.lo -MD -MP -MF .deps/msgb.Tpo -c ../../src/msgb.c -fno-common -DPIC -o .libs/msgb.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT msgb.lo -MD -MP -MF .deps/msgb.Tpo -c ../../src/msgb.c -o msgb.o >/dev/null 2>&1 mv -f .deps/msgb.Tpo .deps/msgb.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT bits.lo -MD -MP -MF .deps/bits.Tpo -c -o bits.lo ../../src/bits.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT bits.lo -MD -MP -MF .deps/bits.Tpo -c ../../src/bits.c -fno-common -DPIC -o .libs/bits.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT bits.lo -MD -MP -MF .deps/bits.Tpo -c ../../src/bits.c -o bits.o >/dev/null 2>&1 mv -f .deps/bits.Tpo .deps/bits.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT bitvec.lo -MD -MP -MF .deps/bitvec.Tpo -c -o bitvec.lo ../../src/bitvec.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT bitvec.lo -MD -MP -MF .deps/bitvec.Tpo -c ../../src/bitvec.c -fno-common -DPIC -o .libs/bitvec.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT bitvec.lo -MD -MP -MF .deps/bitvec.Tpo -c ../../src/bitvec.c -o bitvec.o >/dev/null 2>&1 mv -f .deps/bitvec.Tpo .deps/bitvec.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT statistics.lo -MD -MP -MF .deps/statistics.Tpo -c -o statistics.lo ../../src/statistics.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT statistics.lo -MD -MP -MF .deps/statistics.Tpo -c ../../src/statistics.c -fno-common -DPIC -o .libs/statistics.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT statistics.lo -MD -MP -MF .deps/statistics.Tpo -c ../../src/statistics.c -o statistics.o >/dev/null 2>&1 mv -f .deps/statistics.Tpo .deps/statistics.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT write_queue.lo -MD -MP -MF .deps/write_queue.Tpo -c -o write_queue.lo ../../src/write_queue.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT write_queue.lo -MD -MP -MF .deps/write_queue.Tpo -c ../../src/write_queue.c -fno-common -DPIC -o .libs/write_queue.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT write_queue.lo -MD -MP -MF .deps/write_queue.Tpo -c ../../src/write_queue.c -o write_queue.o >/dev/null 2>&1 mv -f .deps/write_queue.Tpo .deps/write_queue.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT utils.lo -MD -MP -MF .deps/utils.Tpo -c -o utils.lo ../../src/utils.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT utils.lo -MD -MP -MF .deps/utils.Tpo -c ../../src/utils.c -fno-common -DPIC -o .libs/utils.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT utils.lo -MD -MP -MF .deps/utils.Tpo -c ../../src/utils.c -o utils.o >/dev/null 2>&1 mv -f .deps/utils.Tpo .deps/utils.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT socket.lo -MD -MP -MF .deps/socket.Tpo -c -o socket.lo ../../src/socket.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT socket.lo -MD -MP -MF .deps/socket.Tpo -c ../../src/socket.c -fno-common -DPIC -o .libs/socket.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT socket.lo -MD -MP -MF .deps/socket.Tpo -c ../../src/socket.c -o socket.o >/dev/null 2>&1 mv -f .deps/socket.Tpo .deps/socket.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT logging.lo -MD -MP -MF .deps/logging.Tpo -c -o logging.lo ../../src/logging.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT logging.lo -MD -MP -MF .deps/logging.Tpo -c ../../src/logging.c -fno-common -DPIC -o .libs/logging.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT logging.lo -MD -MP -MF .deps/logging.Tpo -c ../../src/logging.c -o logging.o >/dev/null 2>&1 mv -f .deps/logging.Tpo .deps/logging.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT logging_syslog.lo -MD -MP -MF .deps/logging_syslog.Tpo -c -o logging_syslog.lo ../../src/logging_syslog.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT logging_syslog.lo -MD -MP -MF .deps/logging_syslog.Tpo -c ../../src/logging_syslog.c -fno-common -DPIC -o .libs/logging_syslog.o ../../src/logging_syslog.c:47: warning: type qualifiers ignored on function return type libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT logging_syslog.lo -MD -MP -MF .deps/logging_syslog.Tpo -c ../../src/logging_syslog.c -o logging_syslog.o >/dev/null 2>&1 mv -f .deps/logging_syslog.Tpo .deps/logging_syslog.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT rate_ctr.lo -MD -MP -MF .deps/rate_ctr.Tpo -c -o rate_ctr.lo ../../src/rate_ctr.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT rate_ctr.lo -MD -MP -MF .deps/rate_ctr.Tpo -c ../../src/rate_ctr.c -fno-common -DPIC -o .libs/rate_ctr.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT rate_ctr.lo -MD -MP -MF .deps/rate_ctr.Tpo -c ../../src/rate_ctr.c -o rate_ctr.o >/dev/null 2>&1 mv -f .deps/rate_ctr.Tpo .deps/rate_ctr.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT gsmtap_util.lo -MD -MP -MF .deps/gsmtap_util.Tpo -c -o gsmtap_util.lo ../../src/gsmtap_util.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT gsmtap_util.lo -MD -MP -MF .deps/gsmtap_util.Tpo -c ../../src/gsmtap_util.c -fno-common -DPIC -o .libs/gsmtap_util.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT gsmtap_util.lo -MD -MP -MF .deps/gsmtap_util.Tpo -c ../../src/gsmtap_util.c -o gsmtap_util.o >/dev/null 2>&1 mv -f .deps/gsmtap_util.Tpo .deps/gsmtap_util.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT crc16.lo -MD -MP -MF .deps/crc16.Tpo -c -o crc16.lo ../../src/crc16.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT crc16.lo -MD -MP -MF .deps/crc16.Tpo -c ../../src/crc16.c -fno-common -DPIC -o .libs/crc16.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT crc16.lo -MD -MP -MF .deps/crc16.Tpo -c ../../src/crc16.c -o crc16.o >/dev/null 2>&1 mv -f .deps/crc16.Tpo .deps/crc16.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT panic.lo -MD -MP -MF .deps/panic.Tpo -c -o panic.lo ../../src/panic.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT panic.lo -MD -MP -MF .deps/panic.Tpo -c ../../src/panic.c -fno-common -DPIC -o .libs/panic.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT panic.lo -MD -MP -MF .deps/panic.Tpo -c ../../src/panic.c -o panic.o >/dev/null 2>&1 mv -f .deps/panic.Tpo .deps/panic.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT backtrace.lo -MD -MP -MF .deps/backtrace.Tpo -c -o backtrace.lo ../../src/backtrace.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT backtrace.lo -MD -MP -MF .deps/backtrace.Tpo -c ../../src/backtrace.c -fno-common -DPIC -o .libs/backtrace.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT backtrace.lo -MD -MP -MF .deps/backtrace.Tpo -c ../../src/backtrace.c -o backtrace.o >/dev/null 2>&1 mv -f .deps/backtrace.Tpo .deps/backtrace.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT conv.lo -MD -MP -MF .deps/conv.Tpo -c -o conv.lo ../../src/conv.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT conv.lo -MD -MP -MF .deps/conv.Tpo -c ../../src/conv.c -fno-common -DPIC -o .libs/conv.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT conv.lo -MD -MP -MF .deps/conv.Tpo -c ../../src/conv.c -o conv.o >/dev/null 2>&1 mv -f .deps/conv.Tpo .deps/conv.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT application.lo -MD -MP -MF .deps/application.Tpo -c -o application.lo ../../src/application.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT application.lo -MD -MP -MF .deps/application.Tpo -c ../../src/application.c -fno-common -DPIC -o .libs/application.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT application.lo -MD -MP -MF .deps/application.Tpo -c ../../src/application.c -o application.o >/dev/null 2>&1 mv -f .deps/application.Tpo .deps/application.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT plugin.lo -MD -MP -MF .deps/plugin.Tpo -c -o plugin.lo ../../src/plugin.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT plugin.lo -MD -MP -MF .deps/plugin.Tpo -c ../../src/plugin.c -fno-common -DPIC -o .libs/plugin.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT plugin.lo -MD -MP -MF .deps/plugin.Tpo -c ../../src/plugin.c -o plugin.o >/dev/null 2>&1 mv -f .deps/plugin.Tpo .deps/plugin.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT talloc.lo -MD -MP -MF .deps/talloc.Tpo -c -o talloc.lo ../../src/talloc.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT talloc.lo -MD -MP -MF .deps/talloc.Tpo -c ../../src/talloc.c -fno-common -DPIC -o .libs/talloc.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT talloc.lo -MD -MP -MF .deps/talloc.Tpo -c ../../src/talloc.c -o talloc.o >/dev/null 2>&1 mv -f .deps/talloc.Tpo .deps/talloc.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT msgfile.lo -MD -MP -MF .deps/msgfile.Tpo -c -o msgfile.lo ../../src/msgfile.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT msgfile.lo -MD -MP -MF .deps/msgfile.Tpo -c ../../src/msgfile.c -fno-common -DPIC -o .libs/msgfile.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT msgfile.lo -MD -MP -MF .deps/msgfile.Tpo -c ../../src/msgfile.c -o msgfile.o >/dev/null 2>&1 mv -f .deps/msgfile.Tpo .deps/msgfile.Plo /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT serial.lo -MD -MP -MF .deps/serial.Tpo -c -o serial.lo ../../src/serial.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../../src -I../../include -fPIC -Wall -g -O2 -MT serial.lo -MD -MP -MF .deps/serial.Tpo -c ../../src/serial.c -fno-common -DPIC -o .libs/serial.o ../../src/serial.c:41:26: error: linux/serial.h: No such file or directory ../../src/serial.c: In function 'osmo_serial_set_custom_baudrate': ../../src/serial.c:159: error: storage size of 'ser_info' isn't known ../../src/serial.c:161: error: 'TIOCGSERIAL' undeclared (first use in this function) ../../src/serial.c:161: error: (Each undeclared identifier is reported only once ../../src/serial.c:161: error: for each function it appears in.) ../../src/serial.c:167: error: 'ASYNC_SPD_CUST' undeclared (first use in this function) ../../src/serial.c:167: error: 'ASYNC_LOW_LATENCY' undeclared (first use in this function) ../../src/serial.c:170: error: 'TIOCSSERIAL' undeclared (first use in this function) ../../src/serial.c:159: warning: unused variable 'ser_info' ../../src/serial.c: In function 'osmo_serial_clear_custom_baudrate': ../../src/serial.c:189: error: storage size of 'ser_info' isn't known ../../src/serial.c:191: error: 'TIOCGSERIAL' undeclared (first use in this function) ../../src/serial.c:197: error: 'ASYNC_LOW_LATENCY' undeclared (first use in this function) ../../src/serial.c:200: error: 'TIOCSSERIAL' undeclared (first use in this function) ../../src/serial.c:189: warning: unused variable 'ser_info' make[4]: *** [serial.lo] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all] Error 2 make: *** [shared/libosmocore/build-host/src/.libs/libosmocore.la] Error 2

5 6

[ANNOUNCE] First OsmocomGMR code release
by Harald Welte 16 Oct '11

16 Oct '11

First Osmocom GMR code release As some of the readers may already know, a couple of Osmocom developers have been working on a new sub-project: OsmocomGMR. The primary goal of this project is to provide a reusable and clean implementation of the various layers of GMR-1. What is GMR-1 ? Well, it stands for "GEO Mobile Radio" and it's a set of specifications describing a satellite based mobile phone network heavily inspired from GSM. One of the major commercial operators of GMR-1 technology is "Thuraya", providing coverage over Europe/Africa/Asia/Australia. So far the implementation focused on the lowest layers: * Physical layer with FCCH sync and demodulation support for * pi4-CBPSK and pi4-CQPSK bursts. * Channel coding layer (scrambling/puncturing/convolutional coding/crc/interleaving/...) And some ancillary tools to exploit those: * A good capture tool to listen to particular ARFCN(s) and channelize them properly * Wireshark support (BCCH only so far) The first 'demo application' using all of the above provides functionalities similar to what airprobe is for GSM: An air interface protocol analyzer that goes all the way from capturing data off-the-air to sending packets to wireshark for analysis. Limited to BCCH only currently but this will evolve with time. Development was mainly done by Sylvain Munaut, with help from Dimitri Stolnikov (early signal captures and his great capture tool), Harald Welte (initiating the project) and Steve Margraf (testing different setup and antenna ideas). If you'd like to know more, you are encourated to read the wiki (http://gmr.osmocom.org/) and join the mailing list (http://lists.osmocom.org/mailman/listinfo/gmr) -- - 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

Re: Vitelcom TSM30 source code
by msokolov＠ivan.Harhan.ORG 12 Oct '11

12 Oct '11

R M <rm.engineer84(a)gmail.com> wrote: > I am looking for Vitelcom TSM30 source code. I tried searching for it > in Google. I am not able to find it. I have already helped the OP out off-list. In case anyone else is looking for a copy of that code and all known mirrors have been pulled: I have a copy in my possession, and I've been meaning to put it up on my FTP server, i.e., a new public mirror that would be completely shutdown-proof. (I don't use clouds, I run everything on my own physical HW in my own physical control, housed in my own personal datacenter on my own soil which I have declared to be my own nation with my own laws, so no one in the world can make me take anything down.) However, I am very very technologically-backwards, and my current server HW/OS platform is too ancient to host a 500 MiB blob. (The booty is in the form of an ISO image and appears to contain a huge Windows-based development environment in addition to the actual source.) For ages I've been meaning to set up an additional FTP server on newer HW that can host such big stuff, but that progress is very very slow-going for a bunch of personal reasons. Because I consider it to be my fault that I still haven't followed through with my ages-old promise of setting up that new FTP server, I hereby attempt to make up for it somewhat by making the following offer: if anyone would like a copy of that TSM30 source code, is not able to find it anywhere else, and is not willing to wait however many more months for me to set up that darned server, you can give me your snail mail address and I'll send you a CD-R recorded from that 500 MiB ISO image. With the above out of the way, I happen to have some unanswered questions about the TSM30 phone itself which I wonder if perhaps someone in this community might have some answers to, so I've decided to use this thread (started by someone else to whom I have no relation) to try asking them. :-) (And yes, I've already tried Googling quite extensively.) OK, here we go: 1. Would anyone happen to know the basic specs for the TSM30 phone from an ordinary user's perspective? Which GSM bands does it support? What kind of features does it offer? Judging from a cursory bird's-eye-level look at the source code, it seems to be a few notches above a basic primitive phone like Mot C123, but not quite a smartphone either. I realize that one can probably extract all the answers from the source if one were to study it for months on end (I had no idea it would be this huge!), but I was wondering if anyone already happened to know the answer. Basically I'm trying to decide if it would be worth my while to try to acquire an actual TSM30 hardware unit - which in itself seems to be very non-trivial. 2. Has anyone been able to find a service manual and/or schematics for this phone? 3. Does anyone know the hardware in the TSM30 compares against other Calypso-based phones, such as Mot C123, Openmoko GTA02 or the Leonardo reference design? What are the similarities and differences? TIA a lot for any clues, MS

1 0

Vitelcom TSM30 source code
by R M 09 Oct '11

09 Oct '11

Hi, I am looking for Vitelcom TSM30 source code. I tried searching for it in Google. I am not able to find it. The link that is provided in the wiki is dead. Has any one else found it? If yes can you please provide me the link also. Regards RM

1 0

Re: baseband-devel Digest, Vol 21, Issue 4
by Akib Sayyed 06 Oct '11

06 Oct '11

only DSP patch is released which allow you to sniff one time slot out of 7. rest code is not published and i guess will never be published On Thu, Oct 6, 2011 at 3:30 PM, <baseband-devel-request(a)lists.osmocom.org>wrote: > Send baseband-devel mailing list submissions to > baseband-devel(a)lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osmocom.org/mailman/listinfo/baseband-devel > or, via email, send a message with subject or body 'help' to > baseband-devel-request(a)lists.osmocom.org > > You can reach the person managing the list at > baseband-devel-owner(a)lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of baseband-devel digest..." > > Today's Topics: > > 1. Sniff code.. as shown in c27 video (Marten Christophe) > > > ---------- Forwarded message ---------- > From: Marten Christophe <technosabby(a)gmail.com> > To: Sylvain Munaut <246tnt(a)gmail.com> > Date: Thu, 6 Oct 2011 01:26:59 +0000 > Subject: Sniff code.. as shown in c27 video > > Hello Sylvain, > > If sniff code has been released as shown in the chao Video conference c27 > .. if any sniff code have been merged to any of Osmocom branch, lately i > have lost the track of mails and git for quit a some time. > > Kind Regards, > > _______________________________________________ > baseband-devel mailing list > baseband-devel(a)lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/baseband-devel > > -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

1 0

Sniff code.. as shown in c27 video
by Marten Christophe 06 Oct '11

06 Oct '11

Hello Sylvain, If sniff code has been released as shown in the chao Video conference c27 .. if any sniff code have been merged to any of Osmocom branch, lately i have lost the track of mails and git for quit a some time. Kind Regards,

1 0

libosmocore patch to support custom baud rates on OS X
by Richard James 02 Oct '11

02 Oct '11

This patch should allow custom baud-rate setting to work on OS X; tested on Mac OS X 10.7 with a FT232BL-based adapter. diff --git a/src/shared/libosmocore/src/serial.c b/src/shared/libosmocore/src/serial.c index 26cf59d..d702153 100644 --- a/src/shared/libosmocore/src/serial.c +++ b/src/shared/libosmocore/src/serial.c @@ -38,8 +38,9 @@ #include <sys/ioctl.h> #include <sys/types.h> #include <sys/stat.h> +#ifdef __linux__ #include <linux/serial.h> - +#endif #include <osmocom/core/serial.h> @@ -155,6 +156,7 @@ osmo_serial_set_baudrate(int fd, speed_t baudrate) int osmo_serial_set_custom_baudrate(int fd, int baudrate) { +#ifdef __linux__ int rc; struct serial_struct ser_info; @@ -174,6 +176,23 @@ osmo_serial_set_custom_baudrate(int fd, int baudrate) } return _osmo_serial_set_baudrate(fd, B38400); /* 38400 is a kind of magic ... */ +#elsif defined(__APPLE__) +#ifndef IOSSIOSPEED +#define IOSSIOSPEED _IOW('T', 2, speed_t) +#endif + int rc; + + unsigned int speed = baudrate; + rc = ioctl(fd, IOSSIOSPEED, &speed); + if (rc < 0) { + dbg.perror("ioctl(IOSSIOSPEED)"); + return -errno; + } + return 0; +#else +#warning osmo_serial_set_custom_baudrate: unsupported platform + return 0; +#endif } /*! \brief Clear any custom baudrate @@ -186,6 +205,7 @@ int osmo_serial_clear_custom_baudrate(int fd) { int rc; +#ifdef __linux__ struct serial_struct ser_info; rc = ioctl(fd, TIOCGSERIAL, &ser_info); @@ -202,7 +222,7 @@ osmo_serial_clear_custom_baudrate(int fd) dbg_perror("ioctl(TIOCSSERIAL)"); return -errno; } - +#endif return 0; }

3 4

Ciphermode
by Ronny Moser 02 Oct '11

02 Oct '11

Hi guys.. I have a question about cipher mode. I saw, that currently a5/1 and a5/2 is implemented. Now, I want to force the phone to use no encryption (A5/0). Is it enough to disable both of these algos? Because when I tried that, I was not longer able to sign in.. Are there any patches that are necessary, or may it be, that the network is not willing to provide a non-encrypted connection? Usually, the phone is using A5/1 and with that algo, everything is working fine.. Thanks for your help. Ronny

2 3

R: Re: R: Layer23 missing
by Luca Bongiorni 30 Sep '11

30 Sep '11

Hi Bogdan, > I've used all types of phones and different networks - same result. If I capture the uplink then every time after a > few seconds I get "segmentation fault". My guess is that in a controlled environment it's going to work, but with a live one, where you have a > lot of arfcn (on a quick scan I get about 50 on my location) it's unlikely to work. well, the success could depends from many things: - wich cable are you using: FTDI or CP2102; - which phone you have tried: sometimes the jack on C1xx could be not so clean or used and it could create problems of communication at high baudrates. - the environment that you are using: public network, as i saw from my tests, is quite horrible to make tests (eg. arfcn hopping). Using a DP-L10 and modifying the AFC value, seems to work well on public netwroks, even if, sometimes it get stuck: problem related with channel hopping/sync IIRC. I used a Blackberry Test Field to disable EDGE and identify which ARFCN that doesn't hop on GPRS: ( eg. this one is hopping, others may not [1] ) Obviously a private and controlled environment could give you the full percentage of success. Regards, Luca [1] http://tinyurl.com/gprs-hopping

3 5

Re: baseband-devel Digest, Vol 20, Issue 26
by Bogdan Alecu 30 Sep '11

30 Sep '11

Hi Luca, I've noticed the change and manual patched everything, but for me seems that it's not going to work. If I capture the downlink, sometimes it capture some bursts, other times not, but even so there is nothing to decode - the arfcn is correct. I've used all types of phones and different networks - same result. If I capture the uplink then every time after a few seconds I get "segmentation fault". My guess is that in a controlled environment it's going to work, but with a live one, where you have a lot of arfcn (on a quick scan I get about 50 on my location) it's unlikely to work. Bogdan ________________________________ From: "baseband-devel-request(a)lists.osmocom.org" <baseband-devel-request(a)lists.osmocom.org> To: baseband-devel(a)lists.osmocom.org Sent: Friday, September 30, 2011 1:00 PM Subject: baseband-devel Digest, Vol 20, Issue 26 ----- Forwarded Message ----- Send baseband-devel mailing list submissions to baseband-devel(a)lists.osmocom.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.osmocom.org/mailman/listinfo/baseband-devel or, via email, send a message with subject or body 'help' to baseband-devel-request(a)lists.osmocom.org You can reach the person managing the list at baseband-devel-owner(a)lists.osmocom.org When replying, please edit your Subject line so it is more specific than "Re: Contents of baseband-devel digest..." Today's Topics: 1. Layer23 missing (Bogdan Alecu) Hello, I'm trying to use the gprsdecode but when I try to patch it there is no layer3.c and also it can't find " d1cb8ea9b784c7acbafbb2fdcedbdf4655c2f6f5" in the tree. Can someone explain a little bit the new steps? Regards, Bogdan _______________________________________________ baseband-devel mailing list baseband-devel(a)lists.osmocom.org https://lists.osmocom.org/mailman/listinfo/baseband-devel

1 0

Layer23 missing
by Bogdan Alecu 30 Sep '11

30 Sep '11

Hello, I'm trying to use the gprsdecode but when I try to patch it there is no layer3.c and also it can't find " d1cb8ea9b784c7acbafbb2fdcedbdf4655c2f6f5" in the tree. Can someone explain a little bit the new steps? Regards, Bogdan

2 1

About sniff multi bursts in a frame, CCCH_CONF
by Aegean Chou 28 Sep '11

28 Sep '11

Hi, Sylvain Munaut Another method, same error, and i tried any _ONE_ ts, it's no problem. static const struct mframe_sched_item mf_ccch[] = { { .sched_set = SNIFF_CCCH0, .modulo = 51, .frame_nr = 6 }, { .sched_set = SNIFF_CCCH2, .modulo = 51, .frame_nr = 6 }, { .sched_set = SNIFF_CCCH4, .modulo = 51, .frame_nr = 6 }, { .sched_set = SNIFF_CCCH6, .modulo = 51, .frame_nr = 6 }, { .sched_set = SNIFF_CCCH0, .modulo = 51, .frame_nr = 12 }, { .sched_set = SNIFF_CCCH2, .modulo = 51, .frame_nr = 12 }, { .sched_set = SNIFF_CCCH4, .modulo = 51, .frame_nr = 12 }, { .sched_set = SNIFF_CCCH6, .modulo = 51, .frame_nr = 12 }, { .sched_set = SNIFF_CCCH0, .modulo = 51, .frame_nr = 16 }, { .sched_set = SNIFF_CCCH2, .modulo = 51, .frame_nr = 16 }, { .sched_set = SNIFF_CCCH4, .modulo = 51, .frame_nr = 16 }, { .sched_set = SNIFF_CCCH6, .modulo = 51, .frame_nr = 16 }, { .sched_set = SNIFF_CCCH0, .modulo = 51, .frame_nr = 22 }, { .sched_set = SNIFF_CCCH2, .modulo = 51, .frame_nr = 22 }, { .sched_set = SNIFF_CCCH4, .modulo = 51, .frame_nr = 22 }, { .sched_set = SNIFF_CCCH6, .modulo = 51, .frame_nr = 22 }, { .sched_set = SNIFF_CCCH0, .modulo = 51, .frame_nr = 26 }, { .sched_set = SNIFF_CCCH2, .modulo = 51, .frame_nr = 26 }, { .sched_set = SNIFF_CCCH4, .modulo = 51, .frame_nr = 26 }, { .sched_set = SNIFF_CCCH6, .modulo = 51, .frame_nr = 26 }, { .sched_set = SNIFF_CCCH0, .modulo = 51, .frame_nr = 32 }, { .sched_set = SNIFF_CCCH2, .modulo = 51, .frame_nr = 32 }, { .sched_set = SNIFF_CCCH4, .modulo = 51, .frame_nr = 32 }, { .sched_set = SNIFF_CCCH6, .modulo = 51, .frame_nr = 32 }, { .sched_set = SNIFF_CCCH0, .modulo = 51, .frame_nr = 36 }, { .sched_set = SNIFF_CCCH2, .modulo = 51, .frame_nr = 36 }, { .sched_set = SNIFF_CCCH4, .modulo = 51, .frame_nr = 36 }, { .sched_set = SNIFF_CCCH6, .modulo = 51, .frame_nr = 36 }, { .sched_set = SNIFF_CCCH0, .modulo = 51, .frame_nr = 42 }, { .sched_set = SNIFF_CCCH2, .modulo = 51, .frame_nr = 42 }, { .sched_set = SNIFF_CCCH4, .modulo = 51, .frame_nr = 42 }, { .sched_set = SNIFF_CCCH6, .modulo = 51, .frame_nr = 42 }, { .sched_set = SNIFF_CCCH0, .modulo = 51, .frame_nr = 46 }, { .sched_set = SNIFF_CCCH2, .modulo = 51, .frame_nr = 46 }, { .sched_set = SNIFF_CCCH4, .modulo = 51, .frame_nr = 46 }, { .sched_set = SNIFF_CCCH6, .modulo = 51, .frame_nr = 46 }, { .sched_set = NULL } }; const struct tdma_sched_item sniff_ccch0_sched_set[] = { SCHED_ITEM_DT(l1s_sniff_cmd, 0, 0, 0), SCHED_END_FRAME(), SCHED_ITEM_DT(l1s_sniff_cmd, 0, 0, 1), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 0, 0), SCHED_ITEM_DT(l1s_sniff_cmd, 0, 0, 2), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 0, 1), SCHED_ITEM_DT(l1s_sniff_cmd, 0, 0, 3), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 0, 2), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 0, 3), SCHED_END_FRAME(), SCHED_END_SET() }; const struct tdma_sched_item sniff_ccch2_sched_set[] = { SCHED_ITEM_DT(l1s_sniff_cmd, 0, 4, 0), SCHED_END_FRAME(), SCHED_ITEM_DT(l1s_sniff_cmd, 0, 4, 1), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 4, 0), SCHED_ITEM_DT(l1s_sniff_cmd, 0, 4, 2), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 4, 1), SCHED_ITEM_DT(l1s_sniff_cmd, 0, 4, 3), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 4, 2), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 4, 3), SCHED_END_FRAME(), SCHED_END_SET() }; const struct tdma_sched_item sniff_ccch4_sched_set[] = { SCHED_ITEM_DT(l1s_sniff_cmd, 0, 8, 0), SCHED_END_FRAME(), SCHED_ITEM_DT(l1s_sniff_cmd, 0, 8, 1), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 8, 0), SCHED_ITEM_DT(l1s_sniff_cmd, 0, 8, 2), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 8, 1), SCHED_ITEM_DT(l1s_sniff_cmd, 0, 8, 3), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 8, 2), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 8, 3), SCHED_END_FRAME(), SCHED_END_SET() }; const struct tdma_sched_item sniff_ccch6_sched_set[] = { SCHED_ITEM_DT(l1s_sniff_cmd, 0, 12, 0), SCHED_END_FRAME(), SCHED_ITEM_DT(l1s_sniff_cmd, 0, 12, 1), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 12, 0), SCHED_ITEM_DT(l1s_sniff_cmd, 0, 12, 2), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 12, 1), SCHED_ITEM_DT(l1s_sniff_cmd, 0, 12, 3), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 12, 2), SCHED_END_FRAME(), SCHED_ITEM(l1s_sniff_resp, -5, 12, 3), SCHED_END_FRAME(), SCHED_END_SET() }; ======= 2011-09-26 14:10:17 ======= >> the bts arround me uses MultiCCCH, it's CCCH_CONF = 110 (6), so it uses TS0, TS2, TS4 and TS6 in a frame for PCH/AGCH. > >Mmm ,interesting, I had never seen that option being used before. What >network is this. > >> but the burst_ind only CCCH-CONF 0 & 1 are supported, it can sniff TS0 only, so only catch 1/4 IMM ASS for me. >> my OWN phone, it's just not in TS0 (i use nokia netmonitor to check it), so i can't catch it at all (phones use IMSI to decide page group). > >Well, it's your own phone (or any known target phone), you know the >IMSI, hence the paging group ... > > >> i think the bottleneck is the DSP, as the DSP task (ALLC_DSP_TASK) can only process one TS of a frame (it's enough for phone), >> i think maybe backup/restore the DSP task variable patch needed, i'm new to the DSP disassemble and patch, anyone can help? thanks > >That's gonna be _very_ hard, the DSP uses _plenty_ of global variables ... > >But OTOH, instead of using the normal 'RX task', you can use the sniff >task to listen to the CCCH. The sniff task will _not_ do the channel >decoding (i.e. you'll have to call xcch_decode to get the actual 23 >bytes L2 frame), but it can sniff up to 4 bursts in a frame. just look >at how sdcch sniffing is done, it currently sniff 2 timeslot 0 & 3 (to >get DL & UL). > >This way you won't need any hard DSP patching, just a minor patch on >the firmware to convert CCCH listening to burst_ind (leave the BCCH >task as-it is, just mod the CCCH). And then a patch in the host app to >call xcch_decode appropriately and feed the results 'as if' it cames >from the phone directly. > >Cheers, > > Sylvain = = = = = = = = = = = = = = = = = = = = Best regards 　　　　　　　　Aegean Chou 　　　　　　　　aegean2000(a)21cn.com 　　　　　　　　　　2011-09-28

2 1

Re: where is the gprs part source in the osmocom source tree?&In-Reply
by or_ora＠ovi.com 26 Sep '11

26 Sep '11

2 1

Re: Re: About sniff multi bursts in a frame, CCCH_CONF
by Aegean Chou 26 Sep '11

26 Sep '11

Hi, Sylvain Munaut It's china mobile, i can provide more information if you need. Thanks for pointing out the right way, i'll try to modify codes according to BCCH'. BTW, i modify TS (line l1s_rx_win_ctrl _ONLY_) from 0 to 2, 4 and 6, the TS2 and TS4 work well, but the TS6 crash very soon because FCCH error, for example, what's wrong? (high TS -> low TS)? THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!! Assert DSP into Reset Releasing DSP from Reset Installing DSP sniff patch Setting some dsp_api.ndb values Setting API NDB parameters DSP Download Status: 0x0001 DSP API Version: 0x0000 0x0000 Finishing download phase DSP Download Status: 0x0002 DSP API Version: 0x3606 0x0000 LOST 1831! L1CTL_FBSB_REQ (arfcn=70, flags=0x7) Starting FCCH RecognitionFB0 (11:6): TOA= 7200, Power= -69dBm, Angle= 3691Hz FB1 (21:8): TOA= 9651, Power= -69dBm, Angle= 103Hz fn_offset=20 (fn=21 + attempt=8 + ntdma = 7) delay=9 (fn_offset=20 + 11 - fn=21 - 1 scheduling next FB/SB detection task with delay 9 =>FB @ FNR 20 fn_offset=20 qbits=3420 Synchronize_TDMA LOST 3186! SB1 (46:1): TOA= 29, Power= -69dBm, Angle= 217Hz => SB 0x00c12184: BSIC=33 fn=89118(67/16/21) qbits=24 Synchronize_TDMA =>FB @ FNR 45 fn_offset=89118 qbits=4932 LOST 1912! TOA AVG is not 16 qbits, correcting (got 20) L1CTL_DM_EST_REQ (arfcn=4866, chan_nr=0x41, tsc=1) LOST 2110! L1CTL_DM_REL_REQL1CTL_FBSB_REQ (arfcn=70, flags=0x7) Starting FCCH RecognitionLOST 3515! FB0 (91861:3): TOA= 2544, Power= -67dBm, Angle= 3754Hz FB1 (91871:8): TOA= 8751, Power= -67dBm, Angle= 40Hz fn_offset=91869 (fn=91871 + attempt=8 + ntdma = 6) delay=8 (fn_offset=91869 + 11 - fn=91871 - 1 scheduling next FB/SB detection task with delay 8 =>FB @ FNR 91869 fn_offset=91869 qbits=4820 Synchronize_TDMA LOST 3711! SB1 (183745:1): TOA= 29, Power= -67dBm, Angle= 160Hz => SB 0x01e12284: BSIC=33 fn=91882(69/24/31) qbits=24 Synchronize_TDMA =>FB @ FNR 183744 fn_offset=91882 qbits=4932 LOST 1912! L1CTL_DM_EST_REQ (arfcn=4866, chan_nr=0x69, tsc=1) LOST 2109! L1CTL_DM_REL_REQL1CTL_FBSB_REQ (arfcn=70, flags=0x7) Starting FCCH RecognitionLOST 3516! FB0 (92514:8): TOA= 8784, Power= -67dBm, Angle= 3696Hz FB1 (92524:8): TOA= 8755, Power= -67dBm, Angle= 69Hz fn_offset=92522 (fn=92524 + attempt=8 + ntdma = 6) delay=8 (fn_offset=92522 + 11 - fn=92524 - 1 scheduling next FB/SB detection task with delay 8 =>FB @ FNR 92522 fn_offset=92522 qbits=4836 Synchronize_TDMA LOST 3717! SB1 (185051:1): TOA= 27, Power= -66dBm, Angle= 47Hz => SB 0x00852284: BSIC=33 fn=92535(69/ 1/21) qbits=16 Synchronize_TDMA =>FB @ FNR 185050 fn_offset=92535 qbits=4924 LOST 1909! TOA AVG is not 16 qbits, correcting (got 19) L1CTL_DM_EST_REQ (arfcn=4866, chan_nr=0x73, tsc=1) LOST 2578! L1CTL_DM_REL_REQL1CTL_FBSB_REQ (arfcn=70, flags=0x7) Starting FCCH RecognitionLOST 3047! FB0 (93574:9): TOA=10032, Power= -72dBm, Angle= 3770Hz FB1 (93585:9): TOA=10003, Power= -72dBm, Angle= -11Hz fn_offset=93583 (fn=93585 + attempt=9 + ntdma = 7) delay=8 (fn_offset=93583 + 11 - fn=93585 - 1 scheduling next FB/SB detection task with delay 8 =>FB @ FNR 93583 fn_offset=93583 qbits=4828 Synchronize_TDMA LOST 3713! SB1 (187172:1): TOA= 27, Power= -72dBm, Angle= 132Hz => SB 0x01582384: BSIC=33 fn=93596(70/22/11) qbits=16 Synchronize_TDMA =>FB @ FNR 187171 fn_offset=93596 qbits=4924 LOST 1910! L1CTL_DM_EST_REQ (arfcn=4866, chan_nr=0x43, tsc=1) LOST 2578! L1CTL_DM_REL_REQL1CTL_FBSB_REQ (arfcn=70, flags=0x7) Starting FCCH RecognitionLOST 3047! FB0 (94186:1): TOA= 48, Power= -68dBm, Angle= 3743Hz FB1 (94197:9): TOA=10007, Power= -68dBm, Angle= 3738Hz fn_offset=94195 (fn=94197 + attempt=9 + ntdma = 7) delay=8 (fn_offset=94195 + 11 - fn=94197 - 1 scheduling next FB/SB detection task with delay 8 FB1 (94217:11): TOA=12507, Power= -68dBm, Angle= 3783Hz fn_offset=94215 (fn=94217 + attempt=11 + ntdma = 9) delay=8 (fn_offset=94215 + 11 - fn=94217 - 1 scheduling next FB/SB detection task with delay 8 FB1 (94237:11): TOA=12507, Power= -69dBm, Angle= 3743Hz fn_offset=94235 (fn=94237 + attempt=11 + ntdma = 9) delay=8 (fn_offset=94235 + 11 - fn=94237 - 1 scheduling next FB/SB detection task with delay 8 FB1 (94248:2): TOA= 1259, Power= -69dBm, Angle= 3689Hz fn_offset=94246 (fn=94248 + attempt=2 + ntdma = 0) delay=8 (fn_offset=94246 + 11 - fn=94248 - 1 scheduling next FB/SB detection task with delay 8 ... ... ======= 2011-09-26 14:10:17 ======= >> the bts arround me uses MultiCCCH, it's CCCH_CONF = 110 (6), so it uses TS0, TS2, TS4 and TS6 in a frame for PCH/AGCH. > >Mmm ,interesting, I had never seen that option being used before. What >network is this. > >> but the burst_ind only CCCH-CONF 0 & 1 are supported, it can sniff TS0 only, so only catch 1/4 IMM ASS for me. >> my OWN phone, it's just not in TS0 (i use nokia netmonitor to check it), so i can't catch it at all (phones use IMSI to decide page group). > >Well, it's your own phone (or any known target phone), you know the >IMSI, hence the paging group ... > > >> i think the bottleneck is the DSP, as the DSP task (ALLC_DSP_TASK) can only process one TS of a frame (it's enough for phone), >> i think maybe backup/restore the DSP task variable patch needed, i'm new to the DSP disassemble and patch, anyone can help? thanks > >That's gonna be _very_ hard, the DSP uses _plenty_ of global variables ... > >But OTOH, instead of using the normal 'RX task', you can use the sniff >task to listen to the CCCH. The sniff task will _not_ do the channel >decoding (i.e. you'll have to call xcch_decode to get the actual 23 >bytes L2 frame), but it can sniff up to 4 bursts in a frame. just look >at how sdcch sniffing is done, it currently sniff 2 timeslot 0 & 3 (to >get DL & UL). > >This way you won't need any hard DSP patching, just a minor patch on >the firmware to convert CCCH listening to burst_ind (leave the BCCH >task as-it is, just mod the CCCH). And then a patch in the host app to >call xcch_decode appropriately and feed the results 'as if' it cames >from the phone directly. > >Cheers, > > Sylvain = = = = = = = = = = = = = = = = = = = = Best regards Steve

2 1

About sniff multi bursts in a frame, CCCH_CONF
by Aegean Chou 26 Sep '11

26 Sep '11

Dear all, the bts arround me uses MultiCCCH, it's CCCH_CONF = 110 (6), so it uses TS0, TS2, TS4 and TS6 in a frame for PCH/AGCH. but the burst_ind only CCCH-CONF 0 & 1 are supported, it can sniff TS0 only, so only catch 1/4 IMM ASS for me. my OWN phone, it's just not in TS0 (i use nokia netmonitor to check it), so i can't catch it at all (phones use IMSI to decide page group). i read the source briefly, and modify prim_rx_nb.c line "l1s_rx_win_ctrl(arfcn, L1_RXWIN_NB, 0);" for TS2, TS4, TS6 temporarily, but this way i'll need 4 phones to catch ONE station. it's very strange, and not beauty. i think the bottleneck is the DSP, as the DSP task (ALLC_DSP_TASK) can only process one TS of a frame (it's enough for phone), i think maybe backup/restore the DSP task variable patch needed, i'm new to the DSP disassemble and patch, anyone can help? thanks Best Regards Steve

2 1

Proposed patch for libosmocore/gsmtap
by iZsh 23 Sep '11

23 Sep '11

Please find attached a proposed patch for libosmocore The modifications are needed if we want to be able to send a gsmtap packet with a type different than GSMTAP_TYPE_UM. It's a fairly straightforward patch. Best Regards, iZsh

1 0

IPv6 connectivity to bb.osmocom.org
by AndrXX 23 Sep '11

23 Sep '11

Hi All, Is IPv6 connectivity to bb.osmocom.org down for me or for everybody? $ host -6 bb.osmocom.org bb.osmocom.org has address 213.95.46.201 bb.osmocom.org has IPv6 address 2001:780:45:f046::201 $ ping6 2001:780:45:f046::201 PING 2001:780:45:f046::201(2001:780:45:f046::201) 56 data bytes ^C --- 2001:780:45:f046::201 ping statistics --- 6 packets transmitted, 0 received, 100% packet loss, time 4999ms $ telnet 2001:780:45:f046::201 80 Trying 2001:780:45:f046::201... telnet: connect to address 2001:780:45:f046::201: Connection timed out $ traceroute 2001:780:45:f046::201 traceroute to 2001:780:45:f046::201 (2001:780:45:f046::201), 30 hops max, 80 byte packets 1 * * * 2 gige-g2-4.core1.fra1.he.net (2001:470:0:69::1) 75.265 ms 75.266 ms 75.552 ms 3 gi0-3-rt1-ffm2.core.noris.net (2001:7f8::3031:0:1) 72.963 ms 72.883 ms 72.891 ms 4 vl604-rt3-nbg3.core.noris.net (2001:780:40:10::1) 75.429 ms 75.448 ms 75.416 ms 5 fa0-0-31-rt6-nbg3.access.noris.net (2001:780:40:23::5) 75.374 ms 75.048 ms 75.128 ms 6 2001:780:0:f::13 (2001:780:0:f::13) 75.030 ms 50.987 ms 50.882 ms 7 * * * 8 * * * (...) 29 * * * 30 * * * Regards, André.

2 1

what about femtocells?
by Sébastien Lorquet 22 Sep '11

22 Sep '11

Hi all, Do you see any interest in the domain of femtocells? this model, that will be sold in France, claims to be pluggable (probably via ethernet) into nearly any ISP provided home router (internet "box"). http://www.pcinpact.com/actu/news/65810-sfr-mobile-adsl-3g-femto.htm Is it in any way comparable to the nanoBTS and other stuff you're hacking nowadays ? Regards Sebastien

3 2

Issue with Airprobe & USRP1/RFX900/52M
by nghia phan 21 Sep '11

21 Sep '11

Hello everyone, I'm looking for help. I have downloaded and built Airprobe (gsm-receiver, gssm, ) on my Ubuntu machine. a/ Using the capture file provided on the web site, I could get a first level of decoding done: nphan@ubuntu:~/airprobe/gsm-receiver/src/python$ more capture_941.8M_112.log Key: '0000000000000000' Configuration: '' No configuration set. configure_receiver 1670173 0: 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 1670177 0: 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 1670183 0: 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 1670187 0: 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 1670193 0: 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 1670197 0: 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 1670204 0: 01 06 07 60 00 25 54 a8 f9 74 05 5e 18 73 2b 2b 2b 2b 2b 2b 2b 2b 2b 1670208 0: 01 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 1670214 0: 01 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 1670218 0: 01 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 1670224 0: 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 1670228 0: 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 1670234 0: 15 06 21 00 01 00 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b but in wireshark I can't see any decoded info such as BCCH system info etc... b/ It looks like my capture isn't working properly either (ie I can't even get the 1st level of decoding as with capture file provided in the web site). nphan@ubuntu:~/airprobe/gsm-receiver/src/python$ ./capture.sh 953.4M /usr/local/bin/usrp_rx_cfile.py Capturing for 10 seconds to capture_953.4M_112.cfile (4642850 samples) Using RX d'board B: Flex 900 Rx USB sample rate 571.428k nphan@ubuntu:~/airprobe/gsm-receiver/src/python$ ./go.sh capture_953.4M_112.cfile >>> gr_fir_ccc: using SSE >>> gr_fir_ccf: using SSE Key: '0000000000000000' Configuration: '' No configuration set. configure_receiver gr_buffer::allocate_buffer: warning: tried to allocate 115 items of size 568. Due to alignment requirements 512 were allocated. If this isn't OK, consider padding your structure to a power-of-two bytes. On this platform, our allocation granularity is 4096 bytes. nphan@ubuntu:~/airprobe/gsm-receiver/src/python$ I have a USRP1 with 2 RFX900 with a ClockTamer providing 52Mhz clock. I have changed the various Python scripts so that the RFX daughter on side B and RX2 are selected. I have also changed the clock rate to 52M to match my HW. I have input the frequency of a known BTS (which kal can see and measure the offset). Any hints about what is wrong in my set-up or process? Thanks Nghia

1 0

GSM 850 / PCS 1900 : PLEASE HELP NEEDED
by rola 21 Sep '11

21 Sep '11

Hi All, I have done all what I could in setting up the project and running of it as indicated in the wiki and mailing list. It has been over two weeks of trial and error of figuring out of what the problem is that led me to this conclusion that OsmocomBB project might not be designed optimally for US GSM Bands (GSM 850/ PCS 1900). The system could not get synchronised to a frequency when FSBS request is carried out. I read from the mailing-list about the possible modification to be done on the file rffe_dualband.c for GSM band in US in order to resolve the issue of synchronisation. I made a changed of DCS 1800 to PCS 1900 and yet the output remain the same with no difference. Perhaps, I am still overlooking a possible detail that might make the MS not synchronising. However the power measure is of average -90dBm which I think might be too low for required level. If there can be anyone with any clue to resolve or shed more light on this issue I am kindly requesting for assistance I have my configuration and output as followed: SYSTEM CONFIGURATION: OS : Ubuntu 10.10 Maverick Meerkat TI- Calypso: Motorola C155 (US Model) Cable: PL2303 USB cable Tool-chain: Self compiled GNUArm tool-chain based on instruction on http://bb.osmocom.org/trac/wiki/GnuArmToolchain OsmocomBB Branch: Successful installation of both Master and Sylvain branch with modification to Makefile to enable transmitting PROGRAM OUTPUTS: Running OsmocomBB (Sylvain Branch) Osmocon Output 1 : rola@amira:~/test2-osmocom-bb/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c155 ../../target/firmware/board/compal_e99/layer1.compalram.bin got 1 bytes from modem, data looks like: 00 . got 6 bytes from modem, data looks like: 1b f6 02 00 41 01 ....A. got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(../../target/firmware/board/compal_e99/layer1.compalram.bin): file_size=53804, hdr_len=4, dnload_len=53811 got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 43 C Received PROMPT2 from phone, starting download handle_write(): 4096 bytes (4096/53811) handle_write(): 4096 bytes (8192/53811) handle_write(): 4096 bytes (12288/53811) handle_write(): 4096 bytes (16384/53811) handle_write(): 4096 bytes (20480/53811) handle_write(): 4096 bytes (24576/53811) handle_write(): 4096 bytes (28672/53811) handle_write(): 4096 bytes (32768/53811) handle_write(): 4096 bytes (36864/53811) handle_write(): 4096 bytes (40960/53811) handle_write(): 4096 bytes (45056/53811) handle_write(): 4096 bytes (49152/53811) handle_write(): 4096 bytes (53248/53811) handle_write(): 563 bytes (53811/53811) handle_write(): finished got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 03 . got 1 bytes from modem, data looks like: 42 B Received DOWNLOAD ACK from phone, your code is running now! OSMOCOM Layer 1 (revision osmocon_v0.0.0-1111-ge838620) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: 7e570d2eb10393bb ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== Power up simcard: Assert DSP into Reset Releasing DSP from Reset Setting some dsp_api.ndb values Setting API NDB parameters DSP Download Status: 0x0001 DSP API Version: 0x0000 0x0000 Finishing download phase DSP Download Status: 0x0002 DSP API Version: 0x3606 0x0000 LOST 3907! LOST 3750! Above output was done with Mobile App not in used. Running Osmocon with Mobile App. Mobile App Output 1: rola@amira:~$ cd test2-osmocom-bb/osmocom-bb/src/host/layer23/src/mobile/ rola@amira:~/test2-osmocom-bb/osmocom-bb/src/host/layer23/src/mobile$ ./mobile -i 127.0.0.1 Copyright (C) 2008-2010 ... Contributions by ... License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. <000f> sim.c:1206 init SIM client <0006> gsm48_cc.c:63 init Call Control <0001> gsm48_rr.c:5100 init Radio Ressource process <0005> gsm48_mm.c:1312 init Mobility Management process <0005> gsm48_mm.c:1035 Selecting PLMN SEARCH state, because no SIM. <0002> gsm322.c:5023 init PLMN process <0003> gsm322.c:5024 init Cell Selection process *** Warning: Mobile '1' has default IMEI: 000000000000000 This could relate your identitiy to other users with default IMEI. *** Mobile '1' initialized, please start phone now! VTY available on port 4247. <0005> subscriber.c:567 Requesting SIM file 0x2fe2 <000f> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000f> sim.c:697 go MF <000f> sim.c:241 SELECT (file=0x3f00) <000f> sim.c:187 sending APDU (class 0xa0, ins 0xa4) ******The above output runs with MS still turned off. Telnet Output: rola@amira:~$ telnet localhost 4247 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Welcome to the OsmocomBB control interface OsmocomBB> en OsmocomBB# sim read 1 OsmocomBB# conf t OsmocomBB(config)# ms 1 OsmocomBB(ms)#noshutdown % Unknown command. OsmocomBB(ms)# % (MS 1) % No service. OsmocomBB(ms)#en OsmocomBB# sh ms MS '1' is up, service is unavailable IMEI: 000000000000000 IMEISV: 0000000000000000 IMEI generation: fixed automatic network selection state: A4 wait for PLMN to appear cell selection state: C6 any cell selection radio ressource layer state: idle mobility management layer state: MM idle, no cell available OsmocomBB# sh support Supported features of MS '1': Phase 2 mobile station R-GSM : yes E-GSM : yes P-GSM : yes GSM900 Class : 4 DCS 1800 : yes DCS Class : 1 GSM 850 : disabled PCS 1900 : disabled GSM 480 : no GSM 450 : no CECS : no VGCS : no VBS : no SMS : no SS_IND : yes PS_CAP : no CMSP : no SoLSA : no LCSVA : no LOC_SERV : no A5/1 : yes A5/2 : yes A5/3 : no A5/4 : no A5/5 : no A5/6 : no A5/7 : no A5/1 : yes Channels : SDCCH + TCH/F + TCH/H Full-Rate V1 : yes Full-Rate V2 : yes Full-Rate V3 : no Half-Rate V1 : yes Half-Rate V3 : no Min RXLEV : -106 OsmocomBB# **** Clearly above under supporrt command, PCS 1900 and GSM 850 is disabled. I have no clue of how turn it on. Osmocon Output 2: PM MEAS: ARFCN=120, 35 dBm at baseband, -102 dBm at RF PM MEAS: ARFCN=121, 41 dBm at baseband, -97 dBm at RF PM MEAS: ARFCN=122, 40 dBm at baseband, -97 dBm at RF PM MEAS: ARFCN=123, 41 dBm at baseband, -96 dBm at RF PM MEAS: ARFCN=124, 41 dBm at baseband, -97 dBm at RF L1CTL_PM_REQ start=512 end=885 PM MEAS: ARFCN=512, 43 dBm at baseband, -94 dBm at RF PM MEAS: ARFCN=512, 40 dBm at baseband, -97 dBm at RF PM MEAS: ARFCN=513, 40 dBm at baseband, -97 dBm at RF - - - PM MEAS: ARFCN=883, 41 dBm at baseband, -96 dBm at RF PM MEAS: ARFCN=884, 43 dBm at baseband, -94 dBm at RF PM MEAS: ARFCN=885, 44 dBm at baseband, -94 dBm at RF L1CTL_PM_REQ start=955 end=1023 PM MEAS: ARFCN=955, 41 dBm at baseband, -96 dBm at RF PM MEAS: ARFCN=955, 37 dBm at baseband, -101 dBm at RF - - - PM MEAS: ARFCN=1021, 43 dBm at baseband, -94 dBm at RF PM MEAS: ARFCN=1022, 36 dBm at baseband, -101 dBm at RF PM MEAS: ARFCN=1023, 41 dBm at baseband, -96 dBm at RF L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=872, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=1002, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=1000, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=983, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=979, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=966, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=962, flags=0x7) Starting FCCH RecognitionLOST 1885! LOST 1865! L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=958, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=957, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=879, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=877, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=876, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=874, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=871, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=867, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=849, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=844, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=839, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=837, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=835, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=828, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=827, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=826, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=824, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=820, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=818, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=817, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=811, flags=0x7) Starting FCCH RecognitionL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=809, flags=0x7) ^C rola@amira:~/test2-osmocom-bb/osmocom-bb/src/host/osmocon$ **** The FBSB yield no result Mobile App Output2: <0003> gsm322.c:2900 Found signal (ARFCN 648(DCS) rxlev -94 (16)) <0003> gsm322.c:2900 Found signal (ARFCN 649(DCS) rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 650(DCS) rxlev -94 (16)) <0003> gsm322.c:2900 Found signal (ARFCN 651(DCS) rxlev -94 (16)) <0003> gsm322.c:2900 Found signal (ARFCN 652(DCS) rxlev -93 (17)) <0003> gsm322.c:2900 Found signal (ARFCN 653(DCS) rxlev -94 (16)) <0003> gsm322.c:2900 Found signal (ARFCN 654(DCS) rxlev -94 (16)) <0003> gsm322.c:2900 Found signal (ARFCN 655(DCS) rxlev -94 (16)) <0003> gsm322.c:2900 Found signal (ARFCN 656(DCS) rxlev -94 (16)) - - -- - <0003> gsm322.c:2900 Found signal (ARFCN 876(DCS) rxlev -93 (17)) <0003> gsm322.c:2900 Found signal (ARFCN 877(DCS) rxlev -93 (17)) <0003> gsm322.c:2900 Found signal (ARFCN 878(DCS) rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 879(DCS) rxlev -93 (17)) <0003> gsm322.c:2900 Found signal (ARFCN 880(DCS) rxlev -94 (16)) <0003> gsm322.c:2900 Found signal (ARFCN 881(DCS) rxlev -94 (16)) <0003> gsm322.c:2900 Found signal (ARFCN 882(DCS) rxlev -94 (16)) <0003> gsm322.c:2900 Found signal (ARFCN 883(DCS) rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 884(DCS) rxlev -94 (16)) <0003> gsm322.c:2900 Found signal (ARFCN 885(DCS) rxlev -94 (16)) <0003> gsm322.c:2912 Done with power scanning range. <0003> gsm322.c:2790 Scanning power for all frequencies. <0003> gsm322.c:2851 Scanning frequencies. (955..955) <0003> gsm322.c:2900 Found signal (ARFCN 955 rxlev -96 (14)) <0003> gsm322.c:2888 Getting PM for ARFCN 955 twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2900 Found signal (ARFCN 955 rxlev -101 (9)) <0003> gsm322.c:2900 Found signal (ARFCN 956 rxlev -100 (10)) <0003> gsm322.c:2900 Found signal (ARFCN 957 rxlev -93 (17)) <0003> gsm322.c:2900 Found signal (ARFCN 958 rxlev -93 (17)) <0003> gsm322.c:2900 Found signal (ARFCN 959 rxlev -96 (14)) -- -- -- -- <0003> gsm322.c:2900 Found signal (ARFCN 998 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 999 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1000 rxlev -93 (17)) <0003> gsm322.c:2900 Found signal (ARFCN 1001 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1002 rxlev -93 (17)) <0003> gsm322.c:2900 Found signal (ARFCN 1003 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1004 rxlev -101 (9)) <0003> gsm322.c:2900 Found signal (ARFCN 1005 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1006 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1007 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1008 rxlev -101 (9)) <0003> gsm322.c:2900 Found signal (ARFCN 1009 rxlev -101 (9)) <0003> gsm322.c:2900 Found signal (ARFCN 1010 rxlev -101 (9)) <0003> gsm322.c:2900 Found signal (ARFCN 1011 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1012 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1013 rxlev -101 (9)) <0003> gsm322.c:2900 Found signal (ARFCN 1014 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1015 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1016 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1017 rxlev -101 (9)) <0003> gsm322.c:2900 Found signal (ARFCN 1018 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1019 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1020 rxlev -96 (14)) <0003> gsm322.c:2900 Found signal (ARFCN 1021 rxlev -94 (16)) <0003> gsm322.c:2900 Found signal (ARFCN 1022 rxlev -101 (9)) <0003> gsm322.c:2900 Found signal (ARFCN 1023 rxlev -96 (14)) <0003> gsm322.c:2912 Done with power scanning range. <0003> gsm322.c:2790 Scanning power for all frequencies. <0003> gsm322.c:2828 Found 568 frequencies. <0003> gsm322.c:2248 Scanning frequency 872(DCS) (rxlev -92). <0003> gsm322.c:469 Sync to ARFCN=872(DCS) rxlev=-92 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 40 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=872(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 1002 (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=1002 rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 30 frequencies left in band 955..124 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=1002 <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 1000 (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=1000 rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 29 frequencies left in band 955..124 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=1000 <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 983 (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=983 rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 28 frequencies left in band 955..124 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=983 <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 979 (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=979 rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 27 frequencies left in band 955..124 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=979 <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 966 (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=966 rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 26 frequencies left in band 955..124 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=966 <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 962 (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=962 rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 25 frequencies left in band 955..124 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=962 <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 958 (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=958 rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 24 frequencies left in band 955..124 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=958 <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 957 (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=957 rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 23 frequencies left in band 955..124 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=957 <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 879(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=879(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 39 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=879(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 877(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=877(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 38 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=877(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 876(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=876(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 37 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=876(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 874(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=874(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 36 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=874(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 871(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=871(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 35 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=871(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 867(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=867(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 34 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=867(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 849(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=849(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 33 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=849(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 844(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=844(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 32 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=844(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 839(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=839(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 31 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=839(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 837(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=837(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 30 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=837(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 835(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=835(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 29 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=835(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 828(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=828(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 28 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. -- -- -- <0003> gsm322.c:2268 23 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=818(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 817(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=817(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 22 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=817(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 811(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=811(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 21 frequencies left in band 512..885 <0003> gsm322.c:2993 Channel sync error. <0003> gsm322.c:2998 free sysinfo ARFCN=811(DCS) <0003> gsm322.c:2734 Cell selection failed, sync timeout. <0003> gsm322.c:2248 Scanning frequency 809(DCS) (rxlev -93). <0003> gsm322.c:469 Sync to ARFCN=809(DCS) rxlev=-93 (No sysinfo yet, ccch mode NONE) <0003> gsm322.c:2268 20 frequencies left in band 512..885 **** The output displayed cell selection failure. The process repeats itself continuously Thanks Rasak -- View this message in context: http://baseband-devel.722152.n3.nabble.com/GSM-850-PCS-1900-PLEASE-HELP-NEE… Sent from the baseband-devel mailing list archive at Nabble.com.

2 2

Architecture of oscomBB
by nghia phan 18 Sep '11

18 Sep '11

Hello everyone, I'm new to OscomBB and have few questions about its architecture. I have ordered the C123 and the serial cable. Note: I have OpenBTS running quite well and would like now to explore the other end. I did look at the Software Overview page and have the following questions: a/ where can I log the raw burst (156 bits)? [ not the IQ samples ] on the PC? on the ARM7? b/ on the downllink path, how is the FCH detection process split between dsp, arm7 and PC? ie from raw burst to FCH detection indication and offset value. c/ on the downllink path, how is the SCH decode process split between dsp, arm7 and PC? ie from raw burst to GSM frame number, BSIC etc.. d/ on the downllink path, how is the BCCH decode process split between dsp, arm7 and PC? ie from raw burst to System Informations... d/ on the uplink path, how the RACH encode process (RACH_REQ) is split between dsp, arm7 and PC? Thank your for your kind answers. Rgds Nghia

2 1

RFC: libosmocore generic CRC
by Sylvain Munaut 17 Sep '11

17 Sep '11

Hi, I've just pused in libosmocore a branch sylvain/crc with a proposal for some generic CRC function. The goal here is to provide a base implementation so that channel coding/decoding of the various other projects can use this as a base rather than reimplement their own for each poly. The API is targeted towards that use (using array of ubit_t rather than a buffer of packed bits). The code is generated from a template and expanded into a 8 / 16 / 32 / 64 bits version by the Makefile (each capable of supporting any crc length inferior or equal to that. So a CRC12 would use the 16bits state function). Appropriate doxygen doc is included. If nobody has objection / comments / ... I'll go ahead and merge it. Cheers, Sylvain

2 1

Failed to initialize flash! Why?
by Tobias Funke 17 Sep '11

17 Sep '11

Hi, sorry if I shouldn`t write correclly, i'm not that good in english. i have a Motorola c118 and now aFTDI cable. my problem: compiling was successfully. than i run osmocon: ./osmocon -p /dev/ttyUSB0 -m c123xor /home/test/install/osmocom-bb/src/target/firmware/board/compal_e88/layer1.ramload.bin i pressed power button and get this output: 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(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=17184, hdr_len=4, dnload_len=17191 got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 43 C Received PROMPT2 from phone, starting download handle_write(): 4096 bytes (4096/17191) handle_write(): 4096 bytes (8192/17191) handle_write(): 4096 bytes (12288/17191) handle_write(): 4096 bytes (16384/17191) handle_write(): 807 bytes (17191/17191) handle_write(): finished got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 03 . got 1 bytes from modem, data looks like: 42 B Received DOWNLOAD ACK from phone, your code is running now! Received DOWNLOAD ACK from phone, your code is running now! OSMOCOM Loader (revision osmocon_v0.0.0-1108-g7bbd2ac) ====================================================================== Running on compal_e88 in environment compalram Failed to initialize flash! _____________________ Why initializing flash failed? what is my fault? can you help me? thanks a lot, tobsen

3 2

Comprehensive User Directive Manual Needed
by rola 16 Sep '11

16 Sep '11

Hi all, I am really thrill to set up OsmocomBB program single handedly after scourging through mailing list and crash learning linux environment from online tutorials. This is an amazing project with a lot of concept and idea that can only be acquired through years of working as a developer. I really appreciate the great work each and everyone put into this project and I am taking advantage of this to set myself back as a programmer. Could there be a comprehensive documentation on how to setup the the project from the first stage of firmware download to the linking of various applications to the running osmocon program. It took a lot of time to get myself around the project before I could finally set it up. Beside the core participant programmers and those that were previously familiar with this nature of application many of the interested enthusiast like me are left in the dark on what to do at one point or the other during the set up of the project. For an instance after successfully setting up the osmocomBB, I couldn't run the program with my C155 just for the fact that I mistakenly took the passing parameter for C155 for "C155xor" following the given example based on C123. It took me over two days to realized where the error was all because I was having legitimate error report of "NACK" that was explained on the blog to be due to different transmission rate between the hosting system and the MS onboard chip. By stroke of luck, I removed the "xor" based on solution suggested for similar issue on different Motorola model and VIOLA !!! firmware completes downloading and I'm set on track . The funniest thing is that it was after I've resolved the problem that I later read the reference to the C155 parameter passing. Secondly, setting up config file for MOBILE APP was like searching for needle in the hail. My thought was that the file needed to contain a written configuration of VTY with telnet parameters. That took me on a journey of learning what telnet is, what Virtual Terminal is. Anyway, I learn a lot from googling here and there before I finally read in some solution that the file is just an empty file. I know that it might be trivial issue to many of the grounded programmers but to some like me it was really a big issue. Right now I am running the Mobile App and about to setup the patch wireshark but still have no clue of what command to send through the telnet interface or what next to do on the Mobile prompt section. It will be a nice to have a compiled possible errors that newbies might encounter and as well a basic step on what to do at each stage of setting up and running of the programs. Just to give a little background about myself; I have a two semester of wireless technology as part of my graduate study and I intend to use OsmocomBB as the basis of my thesis on analyzing GSM Um interface. Great work guys and God bless. Rasak -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Comprehensive-User-Directive-Man… Sent from the baseband-devel mailing list archive at Nabble.com.

4 10

Patch suggestion for wireshark's LAPDm dissector
by iZsh 15 Sep '11

15 Sep '11

Hello, (my first post to this ML) Sylvain told me it might be a good place to post this. Please find attached a small patch for wireshark's LAPDm dissector. It currently fails at reassembling LAPDm packets when processing multiple streams at the same time insofar as it always assume the fragmented type I LAPDm frames belong to the same stream. This is of course wrong if you process, for instance, all the timeslots of a S{D,A}CCH channel. The proposed patch, which might not be ideal but seems to work better with my testcase (and not worse), identifies the stream using the tuple (link direction, timeslot, subslot). I reused the packet_info's circuit_id field for this, which should be safe enough to use. Let me know if you have any comments., hopefully this could be committed upstream by someone with commit access. Best Regards, iZsh

1 0

difference between ft232 and max 232?
by labad jala 15 Sep '11

15 Sep '11

Hello techies. Is there a big difference between ft232 and max232? I have taken apart this cable : http://www.cellcorner.com/xshp/unlock-phone-codes/motorola-t190-t191-t193-u… and a picture is attached. By the way, the pinout and voltage (+4v) doesn't seem to match so I'd like to solder it the proper way..Any advise welcome. Cheers.

5 4

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel