August 2011 - baseband-devel - lists.osmocom.org

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

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

[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

Re: GRPS decode - trying to download firmware to C123

by smithmr103＠gmail.com

12 years, 7 months

1
0
0 0

GRPS decode - trying to download firmware to C123

by smithmr103＠gmail.com

Hello list, I'm newbee so excuse me for my very basic question. I follow all the instructions on srlabs.de/gprs given by Karsten I have a C123 and a USB / jack 2.5mm - pl2303 based :( All steps are fine until I try to programm the compal ram ;) ./host/osmocon/osmocon -m c123xor -p /dev/ttyUSB0 ./target/firmware/board/compal_e88/layer1.compalram.bin I get : ... PROMPT1... ... PROMPT2... handle_write(): xxxx bytes (xxxx/yyyy) ... ... handle_write(): xxxx bytes (xxxx/yyyy) Received 1 byte : xx Received 1 bytes : yy ... ... Finally I received e.r.r.o.r (byte by byte) NOT ACK RECEIVED... I can also get (not with the same firmware...) : ... PROMPT1... ... PROMPT2... handle_write(): xxxx bytes (xxxx/yyyy) ... ... handle_write(): finished and then... nothing... I'm going to test the cable, as Philipp has told to Pavel. I also bought a RS232 / Jack unlocking Motorola (C123) cable and I own a BlackBox FTDI based USB/RS232 cable... So I'll test it as soon as I receive the cable. Do you think is a matter of cable, who is supposed to be osmocom compatible, or a phone issue or even the USB port... ? Thank you very much for your help and excuse me again with this kind of 'stupid' question about cable. I read almost all the subjects, I did a lot of experimentations in a lot of git branch (master, testing, burst_ind - of course not working with PL2303 ... + d1cb8ea9b784c7acbafbb2fdcedbdf4655c2f6f5 not working too) I think it must work at least in the master branch... Smith

12 years, 7 months

3
5
0 0

Suggestion from the PR department

by Ingo Albrecht

Hey guys I've been noticing the neverending stream of serial cable issues popping up here. To end this, I have a suggestion: how about checking the cable type via sysfs? Greets prom

12 years, 7 months

2
1
0 0

GPRS decode:FTDI cable

by list_mailing＠libero.it

Please, can someone suggest a model for the FTDI cable? I have found different types on internet, but I'd like to buy one it will be definitively ok. Thanks in advance.

12 years, 7 months

2
1
0 0

R: Re: GPRS Vs EDGE - Trying to decode my own sessions

by Luca Bongiorni

Hi all, just to explain what i mean, i've attached a sample and the log from layer23. http://pastebin.com/pepx0tdv As you can see from the log i got the immediate-assign. and the i can see the slots. The only thing that i could be strange is the signal strength that sometimes is good and sometimes reaches -100 dBm. Here is the gprsdecode's output: http://pastebin.com/p7XrtKAt Obviously i tried other ARFCNs of all operators (with different c118/c123, FTDI cable) and i got always the same behaviour. Have you some hints to suggest? Tomorrow i will try with some DP-L10 and pubblish the relative results. P.S: As i already stated, Nohl's samples are well decoded and showed into wireshark. Regards, Luca > Hi Harald, > > Actually i could use some old phones that supports only GPRS (e.g. t68i, t39m, etc..), but these phones are not enough useful and i will explain why: > > - i would like to use a phone that has field-test engineering; > - i would like to set the phone to camp only in a fixed ARFCN. > > I was also trying a Pirelli DP-L10, but unfortunately i can only fix the band and not the arfcn. > > > Btw... after a while i finally found how to force my Blackberry to work on GPRS on a fixed arfcn: > > - Select an arfcn; > - Lock to this cell; [ http://tinyurl.com/3dcc6vm ] > - Disable Uplink 8-PSK; [ http://tinyurl.com/3dxp85d ] > > Finally the phone is ready to start the tests. [ http://tinyurl.com/3rhldrn ] > > > As you can see, that engineering field-test is very useful because is showing which Coding Scheme and TS are used. > > > Unfortunately at this point... even if i tried a lot of times, i could see imm-ass, the TS, but when i'm trying to decode the dumps... nothing is decoded and i cannot even decode third-party sessions that obviously i could find on the same arfcn that i'm using. > > So, at this state of art, I could decode only samples released from Nohl. > Someone else is having same problems? > > > Regards, > > Luca >

12 years, 7 months

1
0
0 0

OT: Chinese C118 supply?

by Harald Welte

Hi all, at the CCC Camp two weeks ago, a Chinese guy approached me, stating that there he has contacts to a considerable supply of very inexpensive C1xx family phones in China. Unfortunately we didn't exchange contact details, so I'm trying this route. If you are the person that has talked to me about this topic, pleaes contact me by private e-mail. I would love to use this opportunity to provide inexpensive C1xx phones to the larger OsmocomBB user community. Thanks in advance, 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, 8 months

1
0
0 0

GPRS Vs EDGE - Trying to decode my own sessions

by Luca Bongiorni

Hi all, i'm testing gprsdecode with osmocomBB and using the samples provided from Nohl works well. Using a Blackberry 8300 and my Wind's sim, i tried to dump some my internet sessions. Unfortunately even if i'm locking the MS to a fixed ARFCN, it is "upgrading" from GRPS to EDGE very quickly and i cannot dump an entire session and then decode it on gprsdecode. The only datas i could decode and view on wireshark are few "malformed packets". As i suppose the problem is that i'm not able to fix the MS to work only on gprs. Which phone did Luca use to make his tests? (just a simple one that was not EDGE capable? ) Which was the successful-rate of (third-party) decoded sessions? I'm asking it, because i'm not even able to "see" other's phones sessions... ok, could be possible that everyone else is using only EDGE... but seems strange. Have you some hints for that? Thank you for attention. Regards, Luca

12 years, 8 months

3
4
0 0

Re: neighbour cell measurement

by Dieter Spaar

Hello Andreas, hello Harald, On Thu, 14 Jul 2011 13:44:16 +0200, "Harald Welte" <laforge(a)gnumonks.org> wrote: > > The patches look fine to me. I'd wait for another day if Sylvain or > Dieter have any comments, but otherwise they can be merged. The patches are fine for me. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

12 years, 8 months

3
2
0 0

Fwd: Re: neighbour cell measurement

by Andreas Eversberg

xuchenyu wrote: > > Hello! I think that your neighbour cell measurement code is at the branch > > remotes/origin/laforge/neigh_sb > > > hi xuchenyu, this in an incomplete an experimental code. once finished, it will measure neighbour cells during a call. neighbour cell measurment is supported in idle mode only, if you use master branch, or better "sylvain/testing" branch for some fixes and SIM support. you can enable neighbour cell monitor at VTY: "monitor network 1". regards, andreas

12 years, 8 months

1
0
0 0

Re: C115 using loader.compalram.bin&In-Reply

by or_ora＠ovi.com

12 years, 8 months

1
0
0 0

OsmocomBB project Maillist

by jbvl2005＠t-online.de

Hello Team, would you pls put me in your emaillist ? I am a german guy how interst in this project and other electronic projekts. Is it possible to get a littel help to flash my one motorloa c117 ? Thanks and greets from jens germany :D

12 years, 8 months

1
0
0 0

No SIM on GTA02

by radiant radiant

Hi folks. Running layer1 (no TX) on GTA02 with host applications compiled for GTA02 also. Layer1 seems not able to communicate with SIM card, and so no IMSI etc. Mobile enters in "emergency calls only" mode. Simtest firmware also fails. SIM and phone hardware is checked working with fsogsmd. I cannot find any configure switch to disable/enable SIM, and it has no sense on simtest firmware anyway. Has anything to do with this note on sim.h and the fact that on GTA02 you should cycle the baseband power after osmocon start for romloader to begin? /* Known Bugs: 1.) After powering down the simcard communication stops working */ logs: mobile over layer1 (no TX): ----- <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 <0003> gsm322.c:5081 Read stored BA list (mcc=XXX mnc=XX $COUNTRY, $NETWORK) <0003> gsm322.c:5081 Read stored BA list (mcc=XXX mnc=XX $COUNTRY, $NETWORK) <0003> gsm322.c:5081 Read stored BA list (mcc=XXX mnc=XX $COUNTRY, $NETWORK) *** 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! <0002> gsm322.c:3804 (ms 1) Event 'EVENT_SWITCH_ON' for automatic PLMN selection in state 'A0 null' <000e> gsm322.c:1356 SIM is removed <0002> gsm322.c:1357 SIM is removed <0002> gsm322.c:800 new state 'A0 null' -> 'A6 no SIM inserted' ----------------- simtest firmware : ----------------SIMTEST----8<----------------- Initializing driver: Power up simcard: (0 bytes) Reset simcard: (0 bytes) 79 f0 ce db f3 cd 8e 7a 10 a1 6c 3a 61 6f 8f (15 bytes) Test Phase 1: Testing bare sim commands... * Testing SELECT: Selecting MF ==> Status word: ffff * Testing SELECT: Selecting DF_GSM ==> Status word: ffff * Testing SELECT: Selecting EF_IMSI ==> Status word: ffff * Testing STATUS: ==> Status word: ffff * Testing READ BINARY: ==> Status word: ffff Data: db 0 0 0 0 0 0 0 0 (9 bytes) ------------END SIMTEST----8<----------------- On the other hand, on GTA02 osmocon or romloader doesn't start if battery is not attached. Keeps staying on "Sending beacon". Regards

12 years, 8 months

1
0
0 0

Re: GSM-850

by Dieter Spaar

Hello Sylvain, On Mon, 22 Aug 2011 16:35:04 +0200, "Sylvain Munaut" <246tnt(a)gmail.com> wrote: > > I think some phones just have swapped IQ lines for easier routing .... This wouldn't explain why the C122 GSM-850/1900 needs the "I/Q-swap" for GSM-850 TX only. And if I remember, Harald tried it with a GSM-900/1800 phone on GSM-850 (of course there are filter issues in this case) and it required the "I/Q-swap" again for GSM-850 only. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

12 years, 8 months

2
1
0 0

GSM-850

by Dieter Spaar

Hello, I don't know if anyone has already successfully used OsmocomBB with GSM-850. It seems that although receiving on GSM-850 works, there are issues when transmitting. The phone produces a signal on the correct ARFCN, however the BTS can't make use of it. The problem seems to be "I/Q-swap", something which can be turned on in the DSP independently for receiving and transmitting. So far it seems that this was not needed, at least for receiving and also for tranmitting when using GSM-900/1800/1900. However for GSM-850 it seems to be essential for transmitting. It is not clear if different phones behave differently, this might be the case. Also it might be the case that some phones require to turn on "I/Q-swap" when receiving on certain bands. Considering all those uncertainties of "I/Q-swap" the appended patch should be considered as a suggestion, it might be neccessary to make it dependend on the phone and also to introduce a similar function for receiving. At least with the patch a C122 GSM-850/1900 phone now works on GSM-850 too. Thank you very much to Harald who remembered that there was this "I/Q-swap" thing for the DSP. Best regards, Dieter Dieter Spaar, Germany spaar(a)mirider.augusta.de

12 years, 8 months

2
1
0 0

Preparing mobile for osmocombb

by Pavel Baturko

Hi All, Do I need to prepare my phone for uploading the firmware with osmocon tool? I tried to load firmware on Motorola C118 and C115 with Prolific PL2303 USB to serial adaptor (computer->usb->com->3.5mm jack->2.5mm jack->phone) and when I briefly press the power-on button of my phone as it's stated in manual - I got no response from phone. Seems it does nothing. Cable seems to be working, because it detect contact with phone's 2.5mm socket when I plug it into phone as - 'got 1 bytes from modem, data looks like: 00 .'. Thanks, Pavel

12 years, 8 months

2
1
0 0

libosmocore/osmocombb build error

by Job

Hi, When building osmocombb with an updated src/shared/libosmocore (0.3.6) the build fails due to make attempting to build utils/osmo-arfcn.c for build-target which does not have stdio. I have no patch as I was not sure what the preferred way to solve it is. Maybe a --disable-utils like for tests? Best regards, Job make[3]: Entering directory `osmocom-bb/src/shared/libosmocore/build-target/utils' CC osmo-arfcn.o ../../utils/osmo-arfcn.c: In function 'arfcn2freq': ../../utils/osmo-arfcn.c:43: warning: incompatible implicit declaration of built-in function 'fprintf' ../../utils/osmo-arfcn.c:43: error: 'stderr' undeclared (first use in this function)

12 years, 8 months

3
4
0 0

can we tune osmocombb to 2.4 ghz open band

by Akib Sayyed

is it possible to tune or use osmocombb to use 2.4 ghz. whole idea is using OpenBTS on 2.4 ghz on BTS side .and osmocombb on 2.4ghz on phone side will it work?? -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

12 years, 8 months

2
1
0 0

Enabling PCS bands on the C139 (originally on PCS)

by Lokkju Brennr

I keep forgetting how to make this work, and it just came up in IRC again, so I thought I would archive the answer to the list: per tnt: in src/target/firmware/board/compal/rffe_dualband.c , the rffe_get_rx_ports might need to have PCS1900 instead of DCS1800 Some phones have different RF wiring and we can't autodetect it ... (the thing is that unless you try manually or look at the PCB you can't really tell ... some PCS phones have it wired to the DCS input ...)

12 years, 8 months

1
0
0 0

interact osmocombb with OpenBTS

by josephli

Hello every, I recently set up the equipment and tried to communicate with the public PLMN and it worked well at that stage. Then I tried to camp on the OpenBTS after switching on the SIM card. When it progressed to location updating request step, the OpenBTS can not receive identity response from MS. The timer t3210 was fired as long as passing a certain period of time and location updating request was sending again iteratively. Anyway location updating was failed. I checked through wireshark from the mobile phone side, showing that MS did send the response however OpenBTS did not receive somehow. Also the timing advance (ta) during that process became 127 which was abnormal, out of the maximum value of 63. I suspected it was also caused by the failure of reception. Is there something wrong about the decoding at OpenBTS side or data packing error at MS side? Is there any way to fix it? Many thanks, Li -- View this message in context: http://baseband-devel.722152.n3.nabble.com/interact-osmocombb-with-OpenBTS-… Sent from the baseband-devel mailing list archive at Nabble.com.

12 years, 8 months

4
5
0 0

Failing channel assignment

by Dieter Spaar

Hello, I noticed some issues in the following situation, I used the "testing" branch (I think it affects both current "testing" branches): - the signalling channel is an SDCCH/8 on a timeslot different from TS0, for example on TS4 - an ASSIGNMENT COMMAND switches to another channel on a different TS than the SDCCH/8, e.g. to TS2 Now the following two problems can happen: 1.) The ASSIGNMENT COMMAND releases the SDCCH/8 with an L1CTL_DM_REL_REQ. Depending on when the L1CTL_DM_REL_REQ is received, it could be that there are still burst scheduled for transmit (e.g. for the SACCH). Due to the L1CTL_DM_REL_REQ, rfch_get_params() will return wrong data (l1s.dedicated.type is now set to GSM_DCHAN_NONE) and the transmit of the bursts happens on the wrong ARFCN and/or TS. My temporary workaround is to clear every item in the scheduler including the current bucket when a L1CTL_DM_REL_REQ is received, this action requires to disable the FIQ, otherwise problems might happen. 2.) There is some code to check for a switch to a lower timeslot in check_lost_frame(). However it can happen that this code gets not triggered although it should: The ASSIGNMENT COMMAND causes a L1CTL_DM_REL_REQ, l1s.dedicated.type is now GSM_DCHAN_NONE ("0"). The next call to check_lost_frame() resets "last_ts" to 0. Now the new channel is assigned (in the example from above its a switch from TS4 to TS 2) and a "LOST" occures, however the required increment of the GSM time does not happen because "last_ts" is 0 although it should be 4. My current workaround is to not reset "last_ts" to 0 in check_lost_frame() but during "L1CTL_RESET_REQ: FULL!". I don't post any patches because my changes are really just ugly workaround which seem to work in (most) situations where it I otherwise observe failures. To really solve this issues something else should be done, maybe put the whole switch of a channel into an atomic operation instead of doing several operations (this is just an idea, maybe there are better solutions). Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

12 years, 8 months

1
0
0 0

SMS status?

by Andrew Reusch

Hi all, I work in a research lab and we're interested in using your stack to send SMS. I've got some time on my hands and a working OpenBTS stack (USRP), so I will probably go ahead and start implementing it in the mobile app. Before I start I just wanted to ask first about the status of mobile-originated SMS? I saw some traffic in the archives a few months back from Gianni about mobile-terminated SMS, but nothing recent about mobile-originated SMS. Barring that, any suggestions on where to start? :) I'm kinda new here. Assuming I get something solid working, I'd of course be willing to contribute it back to the codebase. Thanks, Andrew

12 years, 8 months

3
4
0 0

osmocomBB purpose & GSMs

by aik821 aik821

Hi all, I'm new in these forums and osmocomBB. I was wondering, how does osmocomBB work. install 2 packages, one on the phone and the other on a PC Host? And then you are able to call/sms and anything a GSM phone can do? And you can change the GSM protocol/stack if you want to? So pretty much your PC becomes a GSM terminal? also Are there any simple guides to setup the whole thing? Ahmed

12 years, 8 months

2
1
0 0

tx signal strength

by screaming-pain

Hi all, probably is a silly question but is there a way to set the tx signal strength of the ms? thanks, loretta -- View this message in context: http://baseband-devel.722152.n3.nabble.com/tx-signal-strength-tp3245572p324… Sent from the baseband-devel mailing list archive at Nabble.com.

12 years, 8 months

1
0
0 0

Loading firmware on C118

by Павел Батурко

Hi all, I'm using Motorola C118 and Prolific PL2303 USB to serial adaptor on Ubuntu 10.10. I'm trying to run $ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin and I got got 1 bytes from modem, data looks like: 00 . I press power button and nothing happens. If rub the connector - lines such as I provided above are appears. Is it means that cable is ok? And what could be the problem? Thanks, Pavel

12 years, 8 months

1
0
0 0

Bug in frequency list generation of libosmocore

by Dieter Spaar

Hello, there is a small bug in the calculation of the "Range 1024" format frequency list. A patch is appended. I post it here because I found it while working with OsmocomBB. Best regards, Dieter Dieter Spaar, Germany spaar(a)mirider.augusta.de

12 years, 8 months

1
0
0 0

Fwd: i got C115 device . now i am searching for the cable to flash the Build on to the device.

by Alvin Schurman

---------- Forwarded message ---------- From: Alvin Schurman <alvin.schurman(a)gmail.com> Date: Tue, Aug 9, 2011 at 5:37 PM Subject: Re: i got C115 device . now i am searching for the cable to flash the Build on to the device. To: nagesh reddy <karnatinagesh(a)gmail.com> I too have a C115 at home. I ordered it to flash and so I could experience a little hands-on learning with GPRS. The first thing I noticed was that there was no usb port or data cable input of any kind on the phone. After a little digging, I found that it has a line of JTAG pads under the battery. I wasn't equipped or trained to tackle JTAG so I stopped where you are. Hopefully, you'll get an answer so I can pick up where I left off when I'm back home with my C115. Cheers, Al On Tue, Aug 9, 2011 at 9:48 AM, nagesh reddy <karnatinagesh(a)gmail.com>wrote: > Hi Guys, > > > i got the Motorola C115 device and i want to flash the Build into the > device. from where can i get the cable > so that i can flash the stack and seee. > > > > regards, > nagesh. > > >

12 years, 8 months

1
0
0 0

i got C115 device . now i am searching for the cable to flash the Build on to the device.

by nagesh reddy

Hi Guys, i got the Motorola C115 device and i want to flash the Build into the device. from where can i get the cable so that i can flash the stack and seee. regards, nagesh.

12 years, 8 months

2
1
0 0

RRLP support in osmocombb

by Akib Sayyed

i am bit new to GSM and osmocombb. does osmocombb support RRLP protocol. @herald i saw in your presentation that we can send custom time advance. does that related to RRLP. also can we fake position using osmocombb? -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

12 years, 8 months

1
0
0 0

Issue with GSM1800/1900

by Dieter Spaar

Hello Andreas, there is a small issue with GSM1800/1900 in the mobile application: When a location update is performed, the wrong power capability is set in Mobile Station Classmark 1. As a workaround I fixed it this way: --- ./host/layer23/src/mobile/gsm48_mm.c Mon Jul 25 15:40:50 2011 +++ r:./host/layer23/src/mobile/gsm48_mm.c Thu Aug 04 13:15:09 2011 @@ -2321,7 +2321,11 @@ gsm_print_mcc(subscr->mcc), gsm_print_mnc(subscr->mnc), subscr->lac); /* classmark 1 */ +#if 0 pwr_lev = gsm48_current_pwr_lev(set, rr->cd_now.arfcn); +#else /* cd_now not yet set, take selected cell ARFCN !? */ + pwr_lev = gsm48_current_pwr_lev(set, rr->ms->cellsel.sel_arfcn); +#endif gsm48_encode_classmark1(&nlu->classmark1, sup->rev_lev, sup->es_ind, set->a5_1, pwr_lev); /* MI */ The reason for the the wrong power capability comes from the fact that "rr->cd_now" is not yet set and so the ARFCN is 0 which causes the GSM900 power capability to be used. It is set to "Class 4" in the configuration file per default, however this value is not defined for GSM1800/1900. I am not sure if my workaround is perfect, you are the expert for "mobile" ;-) Although this might sound like not that important (networks with OpenBSC or OpenBTS don't care at all about the value) there are some real networks out there which don't like it. On a related note: The default TX power calibration curve for GSM900 causes too less TX power for GSM1800/1900, expecially for low power settings. I will try to improve my current workaround for this and provide a patch. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

12 years, 8 months

2
1
0 0

Invitation to connect on LinkedIn

by Nageswara Reddy

I'd like to add you to my professional network on LinkedIn. - Nageswara Nageswara Reddy Sr Tech Leader at Aricent Technologies Bengaluru Area, India Confirm that you know Nageswara Reddy: https://www.linkedin.com/e/-5d8k6r-gqxioekp-57/isd/3755268124/Ee1Qtm6Z/ View Nageswara's profile: http://www.linkedin.com/e/-5d8k6r-gqxioekp-57/LawAMDCaoL5bNI_JVaTOJ82bmKOYl… -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/-5d8k6r-gqxioekp-57/LawAMDCaoL5bNI_JVaTOJ82bmKOYl… (c) 2011 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

12 years, 8 months

1
0
0 0

returning twice in lapdm.c

by screaming-pain

Dear all, in the if starting at line 1591 in lapdm.c there are two return, maybe you want to fix this 1591 if (!mctx.dl) { LOGP(DLAPDM, LOGL_NOTICE, "Received frame for unsupported " "SAPI %d!\n", sapi); return -EINVAL; msgb_free(msg); return -EIO; 1597 } Regards, Loretta -- View this message in context: http://baseband-devel.722152.n3.nabble.com/returning-twice-in-lapdm-c-tp321… Sent from the baseband-devel mailing list archive at Nabble.com.

12 years, 8 months

4
7
0 0

small bug?

by Job

Hi, I noticed in src/target/firmware/calypso/dsp.c: static void dsp_pre_boot(const struct dsp_section *bootcode) { dputs("Assert DSP into Reset\n"); calypso_reset_set(RESET_DSP, 1); if (bootcode) { dputs("Loading initial DSP bootcode (API boot mode)\n"); dsp_upload_sections_api(dsp_bootcode, DSP_BASE_API_MIRROR); It seems that the intention is to pass bootcode to dsp_upload_sections_api, but it is still using the hardcoded dsp_bootcode. No functional impact as it is nowhere used with any other bootcode. Best regards, Job

12 years, 8 months

2
1
0 0

where is the gprs part source in the osmocom source tree?

by John Wu

Hi all, I need the GPRS source code for reference, where is it in osmocom source tree?

12 years, 8 months

2
1
0 0

C115 using loader.compalram.bin

by Bruce, Bryan

Hello, I am using a C115 with a t191 cable. We have completed the "Getting Started" steps and have compiled all the necessary code. I are currently trying to run osmocon to download code onto the phone. The following output appears when we run the script: bruceb@ubuntu:~/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 1 bytes from modem, data looks like: 2d - got 1 bytes from modem, data looks like: 34 4 got 1 bytes from modem, data looks like: 29 ) got 1 bytes from modem, data looks like: 28 ( got 1 bytes from modem, data looks like: 32 2 got 1 bytes from modem, data looks like: 39 9 got 1 bytes from modem, data looks like: 30 0 got 1 bytes from modem, data looks like: 20 got 1 bytes from modem, data looks like: 2d - got 1 bytes from modem, data looks like: 34 4 got 1 bytes from modem, data looks like: 29 ) got 1 bytes from modem, data looks like: 0a . got 1 bytes from modem, data looks like: 0d . got 1 bytes from modem, data looks like: 02 . These lines continue and no script indicates anything is being downloaded, as shown on the wiki site. I have unlocked the phone and put it in "earphone" mode beforehand. I have also tried to press the power button as directed to. Are there any suggestions on how to fix this problem? Thank you, Bryan Bruce

12 years, 8 months

2
1
0 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel August 2011