baseband-devel May 2011

baseband-devel@lists.osmocom.org

52 participants
81 discussions

Help me I have a difficult problem
by adel 13 Jul '11

13 Jul '11

Hello I'm having a problem in the start mobile application ~/osmocom-bb$ cd src/host/layer23/src/mobile ~/osmocom-bb/src/host/layer23/src/mobile$ ./mobile 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. Failed to parse the config file: '/etc/osmocom/osmocom.cfg' Please check or create config file using: 'touch /etc/osmocom/osmocom.cfg' ~/osmocom-bb/src/host/layer23/src/mobile$ Please help me as soon as -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Help-me-I-have-a-difficult-probl… Sent from the baseband-devel mailing list archive at Nabble.com.

11 17

replacing the RX filter with a balun on the c139
by Joshua Lackey 30 Jun '11

30 Jun '11

I've been going over Sylvain's report on removing the RX filters, http://www.246tnt.com/gsm/rx_filter.html, and I had some slight differences on the c139 that I'm hoping someone can help me with. Similar to Sylvain's experience, the schematic doesn't match reality. Just as Sylvain describes, the signal from the balanced output appears to be going through inductors rather than capacitors and there isn't a bridging inductor. However on my c139, the unbalanced input is missing the inductor to ground on the EGSM path and is missing the capacitor to ground on the DCS path. (Sylvain had a capacitor to ground on DCS where the schematic has an inductor to ground.) You can find a picture of what I'm looking at here: http://thre.at/c139/c139rxfilters.jpg . I've placed the c139 schematics in that directory as well, http://thre.at/c139 . My guess is that the filters in the schematics had a different unbalanced impedance than the ones they ended up placing on the c139. But I'm not an EE, and that is just a guess. I can't read the markings on the filters I have, so I can't check the unbalanced input from a data sheet. I also don't have a way to measure the components that are there now so I can't try and compute the value. My question is, does this matter? That is, should I use the same balun that Sylvain chose or should I find one with a different unbalanced impedance? Alternatively, should I use the same baluns and just install an inductor (or capacitor on DCS) to ground so that it matches Sylvain's c123? Any ideas? (As an aside, the baluns that Sylvain chose aren't perfect for the US frequency range, but they should work okay.)

4 6

Invitation
by weberbe＠ee.ethz.ch 05 Jun '11

05 Jun '11

Hi list First of all: Thanks to all of you who actively develop OsmocomBB. Second: In the past few months I worked on an interface between a GSM transceiver and ABB towards the mobile application from OsmocomBB. The findings will be presented Tuesday, May 31, 1.55 pm in ETZ J64 at ETH in Zurich (Gloriastrasse 35, 8092 Zürich). You are all invited. The goal of this project was to understand the GSM protocol flow better in order to be able to extend the hardware towards higher layers. To this end, the mobile application (L2 and L3) was used. Benjamin

4 7

Testing protocol stack with OsmocomBB (cheap way)
by Drasko DRASKOVIC 05 Jun '11

05 Jun '11

Hi all, going through the documentation, I am trying to figure out what would be the best way to have whole protocol stack communication with OsmocomBB. Now, I understand that osmocon can be used to load layer1 into phones RAM, so that this code turns on Calypso and communicate with DSP with AT commands. Then osmocon gets messages from layer1 via RS232 and can distribute them to the mobile application, which sends them to layer23 for further processing or via GSM tap to Wireshark or outputs them on stdout. What I am most interested in how do we insert pacgaes on the other side of the stack, i.e. via telephone air interface (packets that will traverse through Rita, Iota, Calypso down to stdout of host). From what I understand we need some kind of BTS, and I can see that GNU Radio is used for this purpose. But for this, as I understand USPRP (http://en.wikipedia.org/wiki/Universal_Software_Radio_Peripheral) FPGA motherboard with both RX and TX doughterboards is needed, which can go up to 1k eur (too expensive for a hobbist). I was wondering so, what is the best and the cheapest way to inject packets at the protocol stack on the phone and analyze some packet flow later with Wireshark - i.e. to get some usage of the OsmocomBB and to see how it works. At this point I can only run Hello World application, or "mobile" app without any usage (or I do not know how to use it). What would be the best way to start playing around without spending too much money. Speaking of this, what would be the price of the cheapest existing packet generator that can transmit them via Um (i.e. what is the price of the cheapest BTS)? Is there some open source FPGA that can be used for this purpose? Thanks for your explanations and best regards, Drasko

5 17

First OsmocomBB Connection Tests (Unsuccessful)
by Drasko DRASKOVIC 02 Jun '11

02 Jun '11

Hi all, I am trying to have some OsmocomBB communication and my procedure is following : 1) I start osmocon with layer1 sw : ./osmocon -p /dev/ttyUSB1 -m c123xor ../../target/firmware/board/compal_e88/layer1.compalram.bin It now waits for power on button from the phone 2) In the other terminal I start mobile application : ./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. VTY available on port 4247. No Mobile Station defined, creating: MS '1' <000e> sim.c:1206 init SIM client <0005> gsm48_cc.c:61 init Call Control <0001> gsm48_rr.c:4944 init Radio Ressource process <0004> gsm48_mm.c:1220 init Mobility Management process <0004> gsm48_mm.c:971 Selecting PLMN SEARCH state, because no SIM. <0002> gsm322.c:3472 init PLMN process <0003> gsm322.c:3473 init Cell Selection process Mobile '1' initialized, please start phone now! 3) Now I press a "power-on" button on the phone and I have logs comming out on the both terminals. I guess that MS is doing various cell power measurements and trying to discass with near-by cells over controle channels. However, in ./osmocon terminal it finishes like this : $ ./osmocon -p /dev/ttyUSB1 -m c123xor ../../target/firmware/board/compal_e88/layer1.compalram.bin got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 81 . got 4 bytes from modem, data looks like: 1b f6 02 00 .... got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): file_size=47700, hdr_len=4, dnload_len=47707 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(): 1023 bytes (1023/47707) handle_write(): 768 bytes (1791/47707) handle_write(): 768 bytes (2559/47707) handle_write(): 768 bytes (3327/47707) ... handle_write(): 768 bytes (44031/47707) handle_write(): 768 bytes (44799/47707) handle_write(): 768 bytes (45567/47707) handle_write(): 768 bytes (46335/47707) handle_write(): 768 bytes (47103/47707) handle_write(): 604 bytes (47707/47707) 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-884-gd76345a) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: 2c903414df039b3f ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!! 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 1201! L1CTL_RESET_REQ: FULL!L1CTL_PM_REQ start=0 end=124 PM MEAS: ARFCN=0, 32 dBm at baseband, -105 dBm at RF PM MEAS: ARFCN=0, 32 dBm at baseband, -105 dBm at RF ... PM MEAS: ARFCN=98, 36 dBm at baseband, -101 dBm at RF PM MEAS: ARFCN=99, 39 dBm at baseband, -98 dBm at RF PM MEAS: ARFCN=100, 31 dBm at baseband, -106 dBm at RF PM MEAS: ARFCN=101, 30 dBm at baseband, -107 dBm at RF PM MEAS: ARFCN=110, 36 dBm at baseband, -101 dBm at RF PM MEAS: ARFCN=111, 34 dBm at baseband, -103 dBm at RF PM MEAS: ARFCN=112, 31 dBm at baseband, -107 dBm at RF PM MEAS: ARFCN=113, 33 dBm at baseband, -104 dBm at RF ... L1CTL_PM_REQ start=955 end=1023 PM MEAS: ARFCN=955, 26 dBm at baseband, -111 dBm at RF PM MEAS: ARFCN=955, 26 dBm at baseband, -111 dBm at RF PM MEAS: ARFCN=956, 27 dBm at baseband, -110 dBm at RF PM MEAS: ARFCN=957, 26 dBm at baseband, -111 dBm at RF PM MEAS: ARFCN=958, 27 dBm at baseband, -110 dBm at RF PM MEAS: ARFCN=959, 25 dBm at baseband, -112 dBm at RF ... PM MEAS: ARFCN=1020, 37 dBm at baseband, -100 dBm at RF PM MEAS: ARFCN=1021, 41 dBm at baseband, -96 dBm at RF PM MEAS: ARFCN=1022, 31 dBm at baseband, -106 dBm at RF PM MEAS: ARFCN=1023, 42 dBm at baseband, -95 dBm at RF L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=121, flags=0x7) Starting FCCH RecognitionFB0 (1735:8): TOA= 9600, Power= -52dBm, Angle= 1218Hz FB1 (1745:8): TOA= 9563, Power= -52dBm, Angle= 174Hz fn_offset=1744 (fn=1745 + attempt=8 + ntdma = 7)m delay=9 (fn_offset=1744 + 11 - fn=1745 - 1 scheduling next FB/SB detection task with delay 9 =>FB @ FNR 1744 fn_offset=1744 qbits=3068 Synchronize_TDMA LOST 3054! What would this LOST 3054! say ? It does not sound good anyway, but at this point I am not skilled enough to read OsmocomBB logs. On the other side, in the ./mobile terminal I have something like this : <0002> gsm322.c:3099 (ms 1) Event 'EVENT_SWITCH_ON' for automatic PLMN selection in state 'A0 null' <000d> gsm322.c:1056 SIM is removed <0002> gsm322.c:1057 SIM is removed <0002> gsm322.c:512 new state 'A0 null' -> 'A6 no SIM inserted' <0003> gsm322.c:3319 (ms 1) Event 'EVENT_SWITCH_ON' for Cell selection in state 'C0 null' <0003> gsm322.c:2992 Switch on without SIM. <0003> gsm322.c:541 new state 'C0 null' -> 'C6 any cell selection' <0003> gsm322.c:2405 Getting PM for frequency 0 twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2416 Found signal (frequency 2 rxlev -105 (5)) <0003> gsm322.c:2416 Found signal (frequency 3 rxlev -106 (4)) <0003> gsm322.c:2416 Found signal (frequency 4 rxlev -86 (24)) <0003> gsm322.c:2416 Found signal (frequency 5 rxlev -68 (42)) <0003> gsm322.c:2416 Found signal (frequency 6 rxlev -86 (24)) ... <0003> gsm322.c:2405 Getting PM for frequency 512 twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2416 Found signal (frequency 512 rxlev -93 (17)) <0003> gsm322.c:2416 Found signal (frequency 516 rxlev -90 (20)) ... <0003> gsm322.c:2416 Found signal (frequency 1023 rxlev -95 (15)) <0003> gsm322.c:2349 Found 201 frequencies. <0003> gsm322.c:258 Sync to ARFCN=121 rxlev=-54 (No sysinfo yet, ccch mode NONE) <0002> gsm322.c:3099 (ms 1) Event 'EVENT_USER_RESEL' for automatic PLMN selection in state 'A6 no SIM inserted' Can somebody explain me what the hell is happening here ? I am watching all these nice Harald's presentations, like one here : http://www.youtube.com/watch?v=H7rNKZdASBE, but I am not obtaining list of cells like presented to which I can synchronize to. Actually, show cell is giving me : OsmocomBB> show cell 1 arfcn |MCC |MNC |LAC |cell ID|forb.LA|prio |min-db |max-pwr|rx-lev -------+-------+-------+-------+-------+-------+-------+-------+-------+------- OsmocomBB> As you can see, I am pretty much lost here and I would highly appreciate helping hand. Thanks and best regards, Drasko

3 7

[PATCH 1/2] mtk: uart: remove forgotten calypso-include
by Wolfram Sang 30 May '11

30 May '11

Dunno how that survived... Signed-off-by: Wolfram Sang <wolfram(a)the-dreams.de> --- src/target/firmware/board/mediatek/uart.c | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/src/target/firmware/board/mediatek/uart.c b/src/target/firmware/board/mediatek/uart.c index ff82245..8e86b20 100644 --- a/src/target/firmware/board/mediatek/uart.c +++ b/src/target/firmware/board/mediatek/uart.c @@ -36,8 +36,6 @@ #include <comm/sercomm.h> -#include <calypso/irq.h> - /* MT622x */ #if 0 #define BASE_ADDR_UART1 0x80130000 -- 1.7.2.5

2 3

Re: target/firmware/board/compal_e88/loader.compalram.bin T191 cable out of order
by Uli Kleemann 30 May '11

30 May '11

Hi Konrad, sorry for that but anyway thanks for your advice with the software. Which software would you like to recommend to fix that? Regards, -- Uli Kleemann

1 0

mobile crashes
by weberbe＠ee.ethz.ch 29 May '11

29 May '11

Hi guys I just run into a problem and was wondering whether anybody has experienced the same: When I start mobile with GSMTAB support (./mobile -i localhost) it crashes immediately after the first GSMTAB packet was sent. Any ideas or remedies? I compiled the current master branch and am using Ubuntu 11.04 Ben

4 6

Nokia 3310 tracing
by Duncan Salerno 28 May '11

28 May '11

Hi, I've put together a small program that puts Nokia 3310 phones into debug mode (via serial/USB cable) and forwards all sent/received GSM messages and SIM APDUs via GSMTAP to be viewed realtime in Wireshark. This allows you to see the message flows for a real phone on a real network. Nokia 3310's are very cheap and easy to come by, so should appeal to a wide audience. Thought osmocom might be a good home for this utility - could it go into git, and a short page on bb.osmocom.org? Duncan

2 2

hmm, sorry, data cable question
by labad jala 27 May '11

27 May '11

Hello techies! I am new to the list and I acquired a c139. I'd like to buy a rs232/jack 2,5mm named t191 flash (and not unlock) cable. They look 100% the same (even stickers). Is this important? I understand that I have also to use a rs232/usb adapter. The one I have (U232P9 with link/tx/rx leds) gives +/-9,4 v. So my concern is to not fry the Moto..Any advise welcome. Cheers.

8 10

← Newer
1
2
3
4
5
6
7
8
9
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel May 2011