September 2011 - baseband-devel

Engagetted !

by Sébastien Lorquet

http://www.engadget.com/2010/12/29/researchers-eavesdrop-on-encrypted-gsm-c… Congrats!

6 months, 1 week

5
5
0 0

Please can anyone advise me - FMTOOL Error and no further processing

by Raz Sharif

Dear all, I vae the C115 with a T1 USB to Serial cable with the Prolific chipset. When i run osmocon i get :- an its just sits there with no further processing. ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=17120, hdr_len=4, dnload_len=17127 read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=17120, hdr_len=4, dnload_len=17127 got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 2f 00 /. got 1 bytes from modem, data looks like: 1b . got 3 bytes from modem, data looks like: 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 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 got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . I think the cable is ok as when i run my fingers on the tip i get random Zeros so it appears to be talking to the cable. Also when i tried to run Mobile i get the :- even though i created the Mobile.cfg file in /etc/osmoco Failed to parse the config file: '/home/raz/.osmocom/bb/mobile.cfg' Please check or create config file using: 'touch /home/raz/.osmocom/bb/mobile.cfg' I have spent some hours researching the lists and trying various things to no avail but I want to continue until I resolve this issues and use this great stack to learn about the GSM network. Please advise. Great full for any help or pointers but this maybe a timing issue that is difficult to debug. Thanks Raz

7 years, 11 months

5
6
0 0

cell re-selection

by Andreas.Eversberg

hi, i did a lot of resarch and testing on cell selection and re-selection process the last two week. the cell selection process, network selection process (manual and automatic) and mobility management process were already implemented in OsmocomBB a long time, but turned out to be buggy and incomplete. i made test drives to check the process and debugged it. the re-selection process is new. it is used to track surrounding cells while listening to the BCCH of the current cell (camping on a cell). special extension to the layer1 firmare is used to measure neighbour cells. if an neighbour cell becomes 'better', the mobile switches to that cell, depening on different criteria. now it is possible to move with OsmocomBB. the re-selection process is not handover! handover is a process where a phone switches between cells while doing a call. handover is one next step to implement. the process is a little more complex, because it requires not only neighbour cell measurements, but also syncing to them without interrupting the traffic channel. most layer 3 stuff of handover is already implemented. if you like to play and test your moving OsmocomBB, you can check out the "jolly/roaming" branch. it contains the extension to layer1, as well as sim reader and fixes from "sylvain/testing" branch. use both "mobile" and "layer1" firmware from this branch. in order to see some process at VTY, you can do: enable monitor network 1 (continously display the strongest cell and neighbour cells) show ms 1 (to see current states) show neighbour-cells 1 (to see a more detailed current list of neighbours) andreas

8 years, 1 month

3
3
0 0

AW: The call has been rejected

by Andreas.Eversberg

hi josephli, > Read stored BA list mnc=01 the mobile application stores the last cells and neighbour cells (band allocation) of each network. this way the scanning is much faster when restarting. because you use the SIM card with MNC == 02 the first time, there is no band allocation stored for that. the mobile will do a full scan in this case. > while the sim card service I am tesing is actually with mnc 00 and 02. i know that MNC == 0 will not work until i commited improvements of cell selection process last sunday. you should retry that, but first try with an MNC > 0. can you provide debug output when trying a call? also can you provide VTY output of "show ms" before you make the call? regards, andreas

11 years

3
2
0 0

status report layer1 and layer23

by Andreas.Eversberg

hi, i just fixed some locking issues the last days. fix will follow. it took a bit longer, because there were some race conditions. it took up to about one hour until it crashed. my way to detect the area where the crash happened, was to turn on buzzer before that area, and turn it off after that area. after many hours of approximation, i finally found out that the major crash happend during _talloc_zero. (first it looks for a free memory chunk, then it allocates it.) since it can be called from all contexts (main, irq, fiq), it need to be locked against any interrupt, otherwise the memory chunk can be assigned multiple times. (the process of _talloc_free is "atomic" and requires no locking.) because it seems pretty stable, i think it is time to merge some branches into the master. (i made a 6 hours call yesterday. and no crash after bugfix ever since.) i will do that together with sylvain, if we find the time this weekend. currently i use the jolly/voice together with the sylvain/traffic branch. i am able to use an isdn phone togehter with linux-call-router and make/receive calls. audio is passed both ways. i think this is a stage where it actually become "usable". (if not moving arround.) one of my major work for the next weeks/months will be the neighbour cell measurement, cell re-selection, and handover. this is essential when moving with the phone. regards, andreas

11 years

2
1
0 0

Receiving on TS=1 ?

by Sylvain Munaut

Hi, I've hacked something together to quickly test non-combined CCCH. However, I've hit a problem when trying to receive anything on another timeslot than 0. The TX side seems to work fine as the BTS can see my location update request and answers with a reject, but on the MS side, I never see the reject and wireshark only shows invalid incohrent data on the RX. The frames for SDCCH/8 show really nothing valid (looks like random bytes), things like 09 80 7f 47 49 06 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 09 00 47 d5 2d 06 1e 00 00 69 7c a0 91 3d 22 ff ab fe 6c 4f 56 4f 36 ... while the frames for the associated SAACH show at least something gsm-like : 03 03 01 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b but that's not quite a SI5/6 ... To RX/TX on TS=1, I just delayed the RX/TX window by 625 bits (4 * 156.25) when I'm in dedicated channel mode by chaning the 'start' in l1s_tx_win_ctrl / l1s_rx_win_ctrl Is there something else that should be done ? Cheers, Sylvain

11 years, 9 months

2
5
0 0

burst_ind and TCH

by Mad

Hi Sylvain, hi list! I'm experimenting with burst_ind and TCHs right now and ran into some problem I couldn't solve yet. After receiving an Assignment Command for a hopping TCH/F I call l1ctl_tx_dm_est_req_h1() with all necessary parameters and tch_mode GSM48_CMODE_SPEECH_V1 or _EFR. After that I do get burst indications containing the received bits on up- and downlink for the active arfcn on each consecutive frame number. BUT the rx level measurements are most of the time very low and sporadic higher, surely not from that nearby bts and the very close cellphone. It looks like the layer1 doesn't "hit" the right timeslot on the right arfcn at the right time. There are some possible sources of error leading to that, like hopping parameters, channel number and MA list. But I checked these and I took all of them directly from the ASS CMD, the MA as word list in ascending order, like in layer23 IMM ASS handling. The specific AC doesn't have any specialties like Starting Time or "before time" parameters. So my question is if there is some obvious pitfall I'm missing and are there any suggestions how to debug that? Regards, Mad

11 years, 9 months

4
5
0 0

bursts****.dat

by Victor P

Hi, I am trying to use burst_ind branch of osmocom. I have noticed that layer23 creates bursts****.dat files when it indicates uplink. What data are written to these files and what should I use to see its data? Thank you.

11 years, 10 months

5
6
0 0

Use OsmocomBB as OpenBTS / airprobe clock generator

by Harald Welte

Hi! Recently we've had the idea of using OsmocomBB with a simple firmware that synchronizes to an existing GSM networks FCCH and use the resulting 13MHz clock to drive the USRP for airprobe or OpenBTS. Ideally, we would even use the Calypso-internal PLL (for ARM or DSP) to multiply it up to the required 52 MHz. However, neither the Openmoko nor the Compal/Motorola phones expose any of the 3 clock output pads :( So the only choice is to use something along the lines of the http://focus.ti.com/docs/prod/folders/print/cdcvf25084.html as a quad clock multiplier and attach it to the CLK13OUT signal of the phone. The chip is available for 9 USD in single quantities at digikey, and possibly cheaper at other sources. Combined with a sub-20EUR phone it might be a very cheap but still accurate frequency source for OpenBTS - at least as long as there are any commercial gsm networks available. 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)

12 years, 1 month

8
17
0 0

osmocombb and usrp

by Paul Lambert

Hello, I have a ursp1 working fine and I want to use my c123 to conenct to it with osmocombb. Now I face some problems. First of all I have no sim, so I do: sim testcard 1 001 01 The usrp runs a testnetwork (001 01) I don't know how I can associate with the usrp. I tried: network search (lot of output and also my testnet) network show (nothing happens) network select 1 001 01: Network not in list! Any idea what I'm doing wrong? Would be really Cool if i could use opensource only. With best regards, Paul

12 years, 2 months

3
3
0 0

Linux + u-boot port to MT6235

by Marcin Mielczarczyk

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

12 years, 3 months

13
37
0 0

calypso SIM driver on c139 (also: l1ctl SIM APDU)

by Gianni Tedesco

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.

12 years, 5 months

7
11
0 0

Problems while building osmocomBB

by Begerad Stefan

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

12 years, 6 months

2
2
0 0

Build fails on OSX Lion

by Martin Auer

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

12 years, 6 months

5
6
0 0

libosmocore patch to support custom baud rates on OS X

by Richard James

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; }

12 years, 6 months

3
4
0 0

R: Re: R: Layer23 missing

by Luca Bongiorni

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

12 years, 6 months

3
5
0 0

Re: baseband-devel Digest, Vol 20, Issue 26

by Bogdan Alecu

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

12 years, 6 months

1
0
0 0

Layer23 missing

by 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

12 years, 6 months

2
1
0 0

About sniff multi bursts in a frame, CCCH_CONF

by Aegean Chou

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

12 years, 7 months

2
1
0 0

Re: where is the gprs part source in the osmocom source tree?&In-Reply

by or_ora＠ovi.com

12 years, 7 months

2
1
0 0

Re: Re: About sniff multi bursts in a frame, CCCH_CONF

by Aegean Chou

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

12 years, 7 months

2
1
0 0

About sniff multi bursts in a frame, CCCH_CONF

by Aegean Chou

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

12 years, 7 months

2
1
0 0

Proposed patch for libosmocore/gsmtap

by iZsh

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

12 years, 7 months

1
0
0 0

IPv6 connectivity to bb.osmocom.org

by AndrXX

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é.

12 years, 7 months

2
1
0 0

what about femtocells?

by Sébastien Lorquet

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

12 years, 7 months

3
2
0 0

Issue with Airprobe & USRP1/RFX900/52M

by nghia phan

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

12 years, 7 months

1
0
0 0

GSM 850 / PCS 1900 : PLEASE HELP NEEDED

by rola

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.

12 years, 7 months

2
2
0 0

Architecture of oscomBB

by nghia phan

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

12 years, 7 months

2
1
0 0

RFC: libosmocore generic CRC

by Sylvain Munaut

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

12 years, 7 months

2
1
0 0

Failed to initialize flash! Why?

by Tobias Funke

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

12 years, 7 months

3
2
0 0

Comprehensive User Directive Manual Needed

by rola

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.

12 years, 7 months

4
10
0 0

Patch suggestion for wireshark's LAPDm dissector

by iZsh

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

12 years, 7 months

1
0
0 0

difference between ft232 and max 232?

by labad jala

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.

12 years, 7 months

5
4
0 0

Not able to download the sources from git clone git://git.osmocom.org/osmocom-bb.git

by karnatinagesh＠gmail.com

Hi, currently i am not able to download the sources from the git repository. git clone git://git.osmocom.org/osmocom-bb.git is there some issues with the git repository ?. regards, nageswara reddy. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Not-able-to-download-the-sources… Sent from the baseband-devel mailing list archive at Nabble.com.

12 years, 7 months

2
2
0 0

Not able to connect to Network using C-115 devices.

by nageswara reddy

Hi, Finally i am able to compile the GSM Stack code and flash into the Motorol Device C-115. i can see the "layer1.bin" on the display, but my device is not latched on to the N/W. - When i ran the HOST software of Mobile. i can see that SIM reader code is not working, and i can see the IMEI is hardcoded to "0000000000000000". - i captured the response of FBSB(Frequency and Time synchronization Burst), the result is comming as "255". can any one please help me how to resolve these issues so that i can latch on to the N/W. regards, nageswara reddy.

12 years, 7 months

4
3
0 0

Osmocom + USRP

by Alexander Chemeris

Hi Harald and all, I have a client who is interested in an USRP-based MS side implementation. I think that that OsmocomBB is a natural choice for the higher-level stack, but I have only vague idea about its current state. As I understand, burst coding/modulation, reference clock management and GSM clock management should be implemented to get a working MS. Is there anything else to implement? How well is API to Calypso DSP is abstracted in OsmocomBB? (Sorry for my brevity and no googling, I'm abroad on GPRS for few weeks)

12 years, 7 months

2
2
0 0

How to change the log setting through vty?

by josephli

Hello, I have got the logging details of all c files in the directory ../layer23/src/mobile. And now I also want to check the log in the directory of layer23/src/common/lapdm.c. I found the file logging_vty.c is similar to interface_vty.c so I tried several times but it didnt work. Can any one guide me how to use the vty to change the logging setting? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/How-to-change-the-log-setting-th… Sent from the baseband-devel mailing list archive at Nabble.com.

12 years, 7 months

1
0
0 0

Motorola C119

by Basem Ahmed

Hi All, I got new Motorola phone modeled "C119" Its shape like feature Motorola C118 but i tried to programmed with OSMOCON utility with the loader or with the simtest applications but it did not work ,So any help please ? Thanks

12 years, 7 months

3
3
0 0

serial issues on fast PC

by Job

Hi, While testing on a new PC I ran into the following issue. Same phone (C115), same USB cable FTDI RS232 + RS232 -> 3v3, works on a slow Atom PC with latest osmocom-bb git, but fails with fmtool error on a fast i7 core PC. The fail happens after sending the first 4096 bytes with a NACK from the phone. Once in many tries it actually does download something but then fails to run the image. Has anyone seen such behaviour? Any ideas on what might go wrong? If not I'll spend some time to debug it. Best regards, Job

12 years, 7 months

2
2
0 0

[PATCH 0/2] Adding embedded and utilities to configure options

by Job

Hi, Attached are the patches to update configure.ac and some Makefile.am to use more default option selection style. I commented the docdir var in the main Makefile.am. The second patch contains the addition of --disable-utilities and --enable-embedded options. I never made a patch mail before so let me know if anything is missing. Best regards, Job ==== job (2): Adapted configure options to autoconf default behaviour Added autoconf option for utilities and embedded Makefile.am | 2 +- configure.ac | 55 ++++++++++++++++++++++++++++++++++++++-------------- utils/Makefile.am | 2 + 3 files changed, 43 insertions(+), 16 deletions(-) -- 1.7.4.1

12 years, 7 months

3
6
0 0

Re: Bug in frequency list generation of libosmocore

by Dieter Spaar

Hello, appended is another patch for fixing a bug in the calculation of the frequency lists. This time the patch is for the "Range 256 format". The problem is that the operand for the "smod" operation might be negative, in this case the simplified version won't work as expected. In the patch I introduced a separate function for "smod" which takes care of the sign. I have not yet checked if the other formats are also affected, this would be the case if the "smod" operand can be negative. There might be other solutions to fix the problem without the need for a separate function, however I have not thought further about it. A test vector is the following frequency list ("Range 256 format", first byte is the length): 09 8b 1c 83 8c 15 ef 02 2d 30 The correct ARFCNs are 569 571 576 578 586 608 712 715 719 The uncorrected version would instead return: 444 457 460 464 569 576 578 586 608 This means four ARFCNs are wrong which will cause problems if for example the frequency list contains the ARFCNs for hopping. Best regards, Dieter Dieter Spaar, Germany spaar(a)mirider.augusta.de

12 years, 7 months

2
1
0 0

900MHz packet radio?

by Paul Gardner-Stephen

Greetings all, At the Serval Project we have created a mobile mesh telephony system that currently works over wifi.

12 years, 7 months

4
9
0 0

Re: baseband-devel Digest, Vol 20, Issue 1

by Paul Gardner-Stephen

On Thu, Sep 1, 2011 at 7:30 PM, <baseband-devel-request(a)lists.osmocom.org> wrote: Hello, Thank you Dieter and Scott for your fast responses. > ---------- Forwarded message ---------- > From: "Dieter Spaar" <spaar(a)mirider.augusta.de> > To: baseband-devel(a)lists.osmocom.org > Date: Thu, 01 Sep 2011 07:59:31 CEST > Subject: Re: 900MHz packet radio? > Hello Paul, > > On Thu, 1 Sep 2011 13:41:11 +0930, "Paul Gardner-Stephen" <paul(a)servalproject.org> wrote: >> >> So, as the open-source group with the most experience reprogramming >> baseband radios, what is the feasibility of creating a >> proof-of-concept using the types of phones you already work with to >> send and receive arbitrary data packets without reliance on a cell >> tower (even for time synchronisation)? > > It depends a lot on what you want to use on the lower layers > (e.g. Modulation). The TI Calypso based phones have a built-in > GMSK hardware modulator, so it is GMSK. Also the symbolrate is > fixed to the one used by GSM. I had assumed that the modulation would be fixed in this way, and it is not an issue for what I am wanting to do. In fact, it makes a lot of sense to keep the GSM modulation for simplicity. > Then there is the DSP which does the signal processing work. Its > again tied to the GSM standard (format of the burst and length). > It might be possible to put something else into the relativ small > RAM inside the DSP, but this could be a huge effort. This seems to me to be the hardest part of the whole process. When you say a huge effort, do you think it would be possible for someone to be able to get something working if they were able to work on it full-time for a few months? > Besides that you have to modify the hardware of the phone (remove > a filter) so that the phone can receive another phone. But this > is probably the smallest problem of all. Indeed, this is the smallest problem I think. In fact, if we use the part of the ISM915 band that is right next to the GSM band, then my understanding is the filter will only attenuate by a few db -- although I am happy to be corrected on this point. > Best regards, > Dieter > -- > Dieter Spaar, Germany spaar(a)mirider.augusta.de > > > > > ---------- Forwarded message ---------- > From: Scott Weisman <sweisman(a)pobox.com> > To: baseband-devel <baseband-devel(a)lists.osmocom.org> > Date: Thu, 1 Sep 2011 10:18:21 +0300 > Subject: Re: 900MHz packet radio? > I think you would be better taking your existing hardware, which must be somewhat custom to begin with (since it works over wifi) and use something like a HopeRF module (http://www.hoperf.com/) or similar. HopeRF has transceivers with power output up 100mW, data rates up to 256kbps, and a choice of 4 different bands (315, 433, 868, 915). This sounds like it would be a far easier choice to incorporate into your already-working system than hacking OsmocomBB-capable phones. > There is a lot of development from many different companies in this area and quite a bit of hacker activity as well. We are exploring that path simultaneously, and have a batch of the exactly the HopeRF modules that we will use, to demonstrate the range and utility of using the ISM band for long-range mesh telephony. But it is important also that we prove that it can be done using the baseband radio in a phone. We all know that it can if we have the freedom to design the baseband radio from scratch, but that it can also be done it is also important that I show that for handsets where the baseband radio can be reprogrammed without changing the hardware. It all boils down to being able to deflect any straw arguments that might be raised against the feasibility of long-range mesh telephony using baseband radio. Paul. > Scott > > On Thu, Sep 1, 2011 at 7:11 AM, Paul Gardner-Stephen <paul(a)servalproject.org> wrote: >> >> Greetings all, >> >> At the Serval Project we have created a mobile mesh telephony system >> that currently works over wifi. >> >> >From the outset, we have wanted to get it working on the ISM915 and/or >> ISM868 bands that are located adjacent to the GSM 850/900 frequency >> allocations. >> >> My initial investigations and enquiries indicate that this should be >> possible by creative programming of the baseband processor in many >> models of phones. The trick, as I suspect you well know, is the >> difficulty in getting the information and tools required to reprogram >> these radios. >> >> I am now in a position to potentially fund further work on this. >> >> So, as the open-source group with the most experience reprogramming >> baseband radios, what is the feasibility of creating a >> proof-of-concept using the types of phones you already work with to >> send and receive arbitrary data packets without reliance on a cell >> tower (even for time synchronisation)? >> >> I know there are a lot of constraints and problems, but I am most >> interested in creative solutions that can get us to a working >> prototype, however crude, that can be used to demonstrate the >> feasibility of what I am proposing. >> >> If this discussion is off-topic here, I am happy to hold the >> conversation at the serval-project-developers google group, but I am >> equally comfortable with it continuing here. >> >> Thanks in advance, >> Paul Gardner-Stephen. >> Shuttleworth Telecommunications Fellow at Flinders University. >> > > > _______________________________________________ > baseband-devel mailing list > baseband-devel(a)lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/baseband-devel > >

12 years, 7 months

1
0
0 0

Re: 900MHz packet radio?

by Dieter Spaar

Hello Paul, On Thu, 1 Sep 2011 13:41:11 +0930, "Paul Gardner-Stephen" <paul(a)servalproject.org> wrote: > > So, as the open-source group with the most experience reprogramming > baseband radios, what is the feasibility of creating a > proof-of-concept using the types of phones you already work with to > send and receive arbitrary data packets without reliance on a cell > tower (even for time synchronisation)? It depends a lot on what you want to use on the lower layers (e.g. Modulation). The TI Calypso based phones have a built-in GMSK hardware modulator, so it is GMSK. Also the symbolrate is fixed to the one used by GSM. Then there is the DSP which does the signal processing work. Its again tied to the GSM standard (format of the burst and length). It might be possible to put something else into the relativ small RAM inside the DSP, but this could be a huge effort. Besides that you have to modify the hardware of the phone (remove a filter) so that the phone can receive another phone. But this is probably the smallest problem of all. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

12 years, 7 months

1
0
0 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel September 2011