- baseband-devel - lists.osmocom.org

Extract Kc from Phone?
by MATTHEW EVANS 22 Feb '11

22 Feb '11

Hi all, Does anyone have any suggestions with regard to models of phone in which it is easy to view the current Kc? I have a Motorola C115, Nokia 3310/6630, Android Desire, iPhone etc. I can get every everything from the in built field test modes, however I really want to get the current session key so that I can verify/analyse my captured bursts. Thanks, Matt.

7 8

Re: off-topic apologies - how to unlock sim (not phone)
by Sébastien Lorquet 22 Feb '11

22 Feb '11

Hi, the phone does not seem to be involved in this topic. It's only about the SIM. And you can't flash a sim like a baseband. That would be too easy. Sebastien On Tue, Feb 22, 2011 at 3:28 PM, Marius Cirsta <mforce2(a)gmail.com> wrote: > A nicer fix would be to flash it with some open source firmware :). > That would be cool and I guess it's what this project is all about. > > On Tue, Feb 22, 2011 at 5:24 AM, Harald Welte <laforge(a)gnumonks.org> > wrote: > > On 02/20/2011 02:07 AM, Scott Weisman wrote: > >> > >> I apologize for this in advance. I figure the collective GSM knowledge > >> here might be able to help me. > > > > Well, I think it is interesting from a 'scientific' point of view, i.e. > > understanding how such mechanism is implemented. > > > >> I have a SIM card that can only be used on one phone. The phone itself > is > >> unlocked. But the SIM won't work on any other phone. Does anyone know > >> anything about this or how to unlock a SIM to work on any phone? > > > > I think the first step is to trace what is happening between phone and > sim > > card, possibly by using osmocom simtrace. > > > > Once you have a trace, you can look at the messages and try to identify > the > > mechanism the SIM uses to identify the phone. After that, you could > > possibly implement a small program for a proxy SIM like bladox or > RebelSIM > > which patches the messages to make the SIM card happy. > > > > All in all not an easy undertaking, but it can definitely be solved. > > > > Regards, > > Harald > > > > > >

1 0

AW: AW: Fwd: gpsd support
by Andreas.Eversberg 22 Feb '11

22 Feb '11

hi dario, i just tried to compile master and your patch. (heaving gpsd installed) here are some problems: CC gps.o gps.c:41: error: 'gps' redeclared as different kind of symbol /usr/include/gps.h:127: error: previous definition of 'gps' was here gps.c: In function 'osmo_gpsd_cb': gps.c:73: warning: implicit declaration of function 'gps_waiting' gps.c: In function 'osmo_gpsd_open': gps.c:123: warning: implicit declaration of function 'gps_stream' gps.c:123: error: 'WATCH_ENABLE' undeclared (first use in this function) gps.c:123: error: (Each undeclared identifier is reported only once gps.c:123: error: for each function it appears in.) 1. the symbol "gps" is used as structure instance for struct osmo_gps. it is also used in an enum declaration at /usr/include/gps.h: ... enum {gps, glonass, unknown} system; ... 2. the declarations 'gps_waiting', 'gps_stream', 'WATCH_ENABLE' are not defined at gps.h this is maybe one reason why i failed to write gpsd support. symbols in the howtos and examples were missing. here is the latest version i got from the gentoo repository: * sci-geosciences/gpsd Latest version available: 2.32 Latest version installed: 2.32 Size of files: 603 kB Homepage: http://gpsd.berlios.de/ Description: GPS daemon and library to support USB/serial GPS devices and various GPS/mapping clients. License: BSD any ideas? andreas

4 4

AW: AW: AW: Fwd: gpsd support
by Andreas.Eversberg 22 Feb '11

22 Feb '11

> Then try to find what's the minimum version (see api changes in the > gpsd history I guess) and make sure in the configure to check it. i found it at http://gpsd.berlios.de/. not both apis must be supported, at least check for version 2.90 or later, to decide to use gpsd.

1 0

off-topic apologies - how to unlock sim (not phone)
by Scott Weisman 22 Feb '11

22 Feb '11

I apologize for this in advance. I figure the collective GSM knowledge here might be able to help me. I have a SIM card that can only be used on one phone. The phone itself is unlocked. But the SIM won't work on any other phone. Does anyone know anything about this or how to unlock a SIM to work on any phone? Yes, I have tried searching, but because PHONE unlocking is such a common theme, this just passes through the cracks. Thanks, Scott

2 1

hi all
by 麦田守望 22 Feb '11

22 Feb '11

who are know the motorola c375 c450 cant to do osmocom and have a fireware

1 0

AW: Fwd: gpsd support
by Andreas.Eversberg 22 Feb '11

22 Feb '11

> I have written the new code that supports gps selection at runtime > through cmdline switches. Send me any comment you have :). looks good to me. if you have access to git, just commit it, else send me all patches (or combined as one patch) and i will commit them.

1 0

[PATCH] Added run-time selection of the gps device.
by Dario Lombardo 21 Feb '11

21 Feb '11

--- src/host/layer23/configure.ac | 2 +- src/host/layer23/include/osmocom/bb/common/gps.h | 13 ++++- src/host/layer23/src/common/gps.c | 64 ++++++++++++++++------ src/host/layer23/src/misc/app_cell_log.c | 48 ++++++++++------- src/host/layer23/src/mobile/vty_interface.c | 20 +++---- 5 files changed, 95 insertions(+), 52 deletions(-) diff --git a/src/host/layer23/configure.ac b/src/host/layer23/configure.ac index e1c718e..92ec30f 100644 --- a/src/host/layer23/configure.ac +++ b/src/host/layer23/configure.ac @@ -15,7 +15,7 @@ AC_PROG_RANLIB dnl checks for libraries PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore) PKG_CHECK_MODULES(LIBOSMOVTY, libosmovty) -AC_CHECK_LIB(gps, gps_open, CFLAGS+=" -D_USE_GPSD" LDFLAGS+=" -lgps",,) +AC_CHECK_LIB(gps, gps_open, CFLAGS+=" -D_HAVE_GPSD" LDFLAGS+=" -lgps",,) dnl checks for header files AC_HEADER_STDC diff --git a/src/host/layer23/include/osmocom/bb/common/gps.h b/src/host/layer23/include/osmocom/bb/common/gps.h index b7500db..8096dd8 100644 --- a/src/host/layer23/include/osmocom/bb/common/gps.h +++ b/src/host/layer23/include/osmocom/bb/common/gps.h @@ -19,17 +19,24 @@ * */ +enum { + GPS_TYPE_UNDEF, + GPS_TYPE_GPSD, + GPS_TYPE_SERIAL +}; + struct osmo_gps { /* GPS device */ uint8_t enable; + uint8_t gps_type; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD char gpsd_host[32]; char gpsd_port[6]; -#else +#endif + char device[32]; uint32_t baud; -#endif /* current data */ uint8_t valid; /* we have a fix */ diff --git a/src/host/layer23/src/common/gps.c b/src/host/layer23/src/common/gps.c index 55dd239..24d6c51 100644 --- a/src/host/layer23/src/common/gps.c +++ b/src/host/layer23/src/common/gps.c @@ -26,8 +26,9 @@ #include <stdlib.h> #include <errno.h> #include <time.h> +#include <stdbool.h> -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD #include <gps.h> #endif @@ -39,13 +40,13 @@ struct osmo_gps gps = { 0, -#ifdef _USE_GPSD + GPS_TYPE_UNDEF, +#ifdef _HAVE_GPSD "localhost", "2947", -#else +#endif "/dev/ttyACM0", 0, -#endif 0, 0, 0,0 @@ -53,11 +54,11 @@ struct osmo_gps gps = { static struct bsc_fd gps_bfd; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD static struct gps_data_t* gdata; -int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) +int osmo_gpsd_cb(struct bsc_fd *bfd, unsigned int what) { struct tm *tm; unsigned diff = 0; @@ -102,13 +103,13 @@ gps_not_ready: return -1; } -int osmo_gps_open(void) +int osmo_gpsd_open(void) { LOGP(DGPS, LOGL_INFO, "Connecting to gpsd at '%s:%s'\n", gps.gpsd_host, gps.gpsd_port); gps_bfd.data = NULL; gps_bfd.when = BSC_FD_READ; - gps_bfd.cb = osmo_gps_cb; + gps_bfd.cb = osmo_gpsd_cb; gdata = gps_open(gps.gpsd_host, gps.gpsd_port); if (gdata == NULL) { @@ -129,7 +130,7 @@ int osmo_gps_open(void) return 0; } -void osmo_gps_close(void) +void osmo_gpsd_close(void) { if (gps_bfd.fd <= 0) return; @@ -142,11 +143,11 @@ void osmo_gps_close(void) gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ } -#else +#endif static struct termios gps_termios, gps_old_termios; -static int osmo_gps_line(char *line) +static int osmo_serialgps_line(char *line) { time_t gps_now, host_now; struct tm *tm; @@ -241,7 +242,7 @@ static int nmea_checksum(char *line) return (strtoul(line+1, NULL, 16) == checksum); } -int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) +int osmo_serialgps_cb(struct bsc_fd *bfd, unsigned int what) { char buff[128]; static char line[128]; @@ -265,7 +266,7 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) if (!nmea_checksum(line)) fprintf(stderr, "NMEA checksum error\n"); else - osmo_gps_line(line); + osmo_serialgps_line(line); continue; } line[lpos++] = buff[i++]; @@ -276,7 +277,7 @@ int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) return 0; } -int osmo_gps_open(void) +int osmo_serialgps_open(void) { int baud = 0; @@ -287,7 +288,7 @@ int osmo_gps_open(void) gps_bfd.data = NULL; gps_bfd.when = BSC_FD_READ; - gps_bfd.cb = osmo_gps_cb; + gps_bfd.cb = osmo_serialgps_cb; gps_bfd.fd = open(gps.device, O_RDONLY); if (gps_bfd.fd < 0) return gps_bfd.fd; @@ -327,7 +328,7 @@ int osmo_gps_open(void) return 0; } -void osmo_gps_close(void) +void osmo_serialgps_close(void) { if (gps_bfd.fd <= 0) return; @@ -343,11 +344,38 @@ void osmo_gps_close(void) gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ } -#endif - void osmo_gps_init(void) { memset(&gps_bfd, 0, sizeof(gps_bfd)); } +int osmo_gps_open(void) +{ + switch (gps.gps_type) { +#ifdef _HAVE_GPSD + case GPS_TYPE_GPSD: + return osmo_gpsd_open(); +#endif + case GPS_TYPE_SERIAL: + return osmo_serialgps_open(); + + default: + return 0; + } +} + +void osmo_gps_close(void) +{ + switch (gps.gps_type) { +#ifdef _HAVE_GPSD + case GPS_TYPE_GPSD: + return osmo_gpsd_close(); +#endif + case GPS_TYPE_SERIAL: + return osmo_serialgps_close(); + + default: + return; + } +} diff --git a/src/host/layer23/src/misc/app_cell_log.c b/src/host/layer23/src/misc/app_cell_log.c index 7a2c67a..40aac5a 100644 --- a/src/host/layer23/src/misc/app_cell_log.c +++ b/src/host/layer23/src/misc/app_cell_log.c @@ -92,13 +92,12 @@ static int l23_getopt_options(struct option **options) {"logfile", 1, 0, 'l'}, {"rach", 1, 0, 'r'}, {"no-rach", 1, 0, 'n'}, -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD {"gpsd-host", 1, 0, 'g'}, - {"gpsd-port", 1, 0, 'p'} -#else + {"gpsd-port", 1, 0, 'p'}, +#endif {"gps", 1, 0, 'g'}, {"baud", 1, 0, 'b'} -#endif }; *options = opts; @@ -109,15 +108,15 @@ static int l23_cfg_print_help() { printf("\nApplication specific\n"); printf(" -l --logfile LOGFILE Logfile for the cell log.\n"); - printf(" -r --rach RACH Nr. of RACH bursts to send.\n"); - printf(" -n --no-rach Send no rach bursts.\n"); -#ifdef _USE_GPSD + printf(" -r --rach RACH Nr. of RACH bursts to send.\n"); + printf(" -n --no-rach Send no rach bursts.\n"); +#ifdef _HAVE_GPSD printf(" -g --gpsd-host HOST 127.0.0.1. gpsd host.\n"); - printf(" -p --port PORT 2947. gpsd port\n"); -#else - printf(" -g --gps DEVICE /dev/ttyACM0. GPS device.\n"); - printf(" -b --baud BAUDRAT The baud rate of the GPS device\n"); + printf(" -p --port PORT 2947. gpsd port\n"); #endif + printf(" -f --gps DEVICE /dev/ttyACM0. GPS serial device.\n"); + printf(" -b --baud BAUDRAT The baud rate of the GPS device\n"); + return 0; } @@ -133,41 +132,52 @@ static int l23_cfg_handle(int c, const char *optarg) case 'n': RACH_MAX = 0; break; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD case 'g': snprintf(gps.gpsd_host, ARRAY_SIZE(gps.gpsd_host), "%s", optarg); /* force string terminator */ gps.gpsd_host[ARRAY_SIZE(gps.gpsd_host) - 1] = '\0'; + if (gps.gps_type != GPS_TYPE_UNDEF) + goto cmd_line_error; + gps.gps_type = GPS_TYPE_GPSD; LOGP(DGPS, LOGL_INFO, "Using gpsd host %s\n", gps.gpsd_host); break; case 'p': snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "%s", optarg); /* force string terminator */ gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0'; + gps.gps_type = GPS_TYPE_GPSD; LOGP(DGPS, LOGL_INFO, "Using gpsd port %s\n", gps.gpsd_port); break; -#else - case 'g': +#endif + case 'f': snprintf(gps.device, ARRAY_SIZE(gps.device), "%s", optarg); /* force string terminator */ gps.device[ARRAY_SIZE(gps.device) - 1] = '\0'; - LOGP(DGPS, LOGL_INFO, "Using GPS device %s\n", gps.device); + if (gps.gps_type != GPS_TYPE_UNDEF) + goto cmd_line_error; + gps.gps_type = GPS_TYPE_SERIAL; + LOGP(DGPS, LOGL_INFO, "Using GPS serial device %s\n", gps.device); break; case 'b': gps.baud = atoi(optarg); + gps.gps_type = GPS_TYPE_SERIAL; LOGP(DGPS, LOGL_INFO, "Setting GPS baudrate to %u\n", gps.baud); break; -#endif } return 0; + +cmd_line_error: + printf("\nYou can't specify both gpsd and serial gps!!\n\n"); + exit(1); } static struct l23_app_info info = { .copyright = "Copyright (C) 2010 Andreas Eversberg\n", -#ifdef _USE_GPSD - .getopt_string = "l:r:ng:p:", +#ifdef _HAVE_GPSD + .getopt_string = "l:r:nf:b:g:p:", #else - .getopt_string = "l:r:ng:b:", + .getopt_string = "l:r:nf:b:", #endif .cfg_supported = l23_cfg_supported, .cfg_getopt_opt = l23_getopt_options, diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c index 7888f01..fadc152 100644 --- a/src/host/layer23/src/mobile/vty_interface.c +++ b/src/host/layer23/src/mobile/vty_interface.c @@ -855,7 +855,7 @@ DEFUN(cfg_no_gps_enable, cfg_no_gps_enable_cmd, "no gps enable", return CMD_SUCCESS; } -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", "GPS receiver\nSelect gpsd host and port\n" "IP and port (optional) of the host running gpsd") @@ -872,6 +872,7 @@ DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "2947"); gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0'; } + gps.gps_type = GPS_TYPE_GPSD; if (gps.enable) { osmo_gps_close(); if (osmo_gps_open()) { @@ -883,13 +884,15 @@ DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", return CMD_SUCCESS; } -#else +#endif + DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", "GPS receiver\nSelect serial device\n" "Full path of serial device including /dev/") { strncpy(gps.device, argv[0], sizeof(gps.device)); gps.device[sizeof(gps.device) - 1] = '\0'; + gps.gps_type = GPS_TYPE_SERIAL; if (gps.enable) { osmo_gps_close(); if (osmo_gps_open()) { @@ -901,9 +904,7 @@ DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", return CMD_SUCCESS; } -#endif -#ifndef _USE_GPSD DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " "(default|4800|""9600|19200|38400|57600|115200)", "GPS receiver\nSelect baud rate\nDefault, don't modify\n\n\n\n\n\n") @@ -924,7 +925,6 @@ DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " return CMD_SUCCESS; } -#endif /* per MS config */ DEFUN(cfg_ms, cfg_ms_cmd, "ms MS_NAME", @@ -1204,16 +1204,15 @@ static int config_write(struct vty *vty) { struct osmocom_ms *ms; -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD vty_out(vty, "gpsd host %s%s", gps.gpsd_host, VTY_NEWLINE); vty_out(vty, "gpsd port %s%s", gps.gpsd_port, VTY_NEWLINE); -#else +#endif vty_out(vty, "gps device %s%s", gps.device, VTY_NEWLINE); if (gps.baud) vty_out(vty, "gps baudrate %d%s", gps.baud, VTY_NEWLINE); else vty_out(vty, "gps baudrate default%s", VTY_NEWLINE); -#endif vty_out(vty, "%sgps enable%s", (gps.enable) ? "" : "no ", VTY_NEWLINE); vty_out(vty, "!%s", VTY_NEWLINE); @@ -2305,12 +2304,11 @@ int ms_vty_init(void) install_element(ENABLE_NODE, &call_retr_cmd); install_element(ENABLE_NODE, &call_dtmf_cmd); -#ifdef _USE_GPSD +#ifdef _HAVE_GPSD install_element(CONFIG_NODE, &cfg_gps_host_cmd); -#else +#endif install_element(CONFIG_NODE, &cfg_gps_device_cmd); install_element(CONFIG_NODE, &cfg_gps_baud_cmd); -#endif install_element(CONFIG_NODE, &cfg_gps_enable_cmd); install_element(CONFIG_NODE, &cfg_no_gps_enable_cmd); -- 1.7.4 --------------070003050405000809030404--

1 0

success with Pirelli DP-L10 on live network - useful hints for newbies
by Leif Jakob 20 Feb '11

20 Feb '11

Hi, for anyone also playing with the Pirelli phone, I got mine running on a live network. Here's my recipe: - change header files for Pirelli (see wiki) - compile source - setup usb modprobe -v cp210x echo "0489 e003" > /sys/bus/usb-serial/drivers/cp210x/new_id - attach phone without battery on USB - from src run ./host/osmocon/osmocon -p /dev/ttyUSB0 -m romload ./target/firmware/board/pirelli_dpl10/layer1.highram.bin now the tricky part: sometimes the romloader succeeds when you insert the battery, but most times you have to power on the phone and then power off (now the bootloader uploads the .bin) - run mobile (you need to touch an empty osmocom.cfg) ./host/layer23/src/mobile/mobile -i 127.0.0.1 telnet localhost 4247 - play via telnet - you can't break anything now the real fun, enable transmitting - enable transmitter (don't forget to "make clean") in Makefile - select your local channel (I used an other phones cellid and looked up the channel) stick <number> - use random IMEI (000.. didn't work on my network) imei-random 15 - use test sim (if you know your IMSI/KI - I could't get the SIM working) test-sim imsi 22801<secret> ki comp128 <secret> If all works, you'll find in your logfile something like: TMSI 0x25f0ec42 (636546114) assigned if your keys are wrong, you'll see something like: gsm48_mm.c:1581 AUTHENTICATION REJECT I wasn't able to make any real calls from the mobile to any landline but at least signalling in the other direction worked: telnet showed: Incoming call (from +49711xxxxx) Have fun Leif

1 0

RE: Soft GSM client
by Abdul Hakeem 18 Feb '11

18 Feb '11

Hello, I was wondering if there is a soft GSM client....the sort you could run like a sip client on your laptop to connect to the GSM/UMTS network just like UMA/GAN phones do via Up interface. Regards, Abdul Hakeem

4 6

Mediatek MT6235 status (Sciphone G2)
by Marcin.Mielczarczyk＠tieto.com 18 Feb '11

18 Feb '11

Hi list, After some break finally I managed to describe and commit all changes made to MT6235 Linux port during last one and the half month. Currently I got full Angstrom Linux distribution running with UI. Now you can run everything what I'm writing below without changing Sciphone's original firmware. Just use osmocon to load U-Boot to RAM and SD card which has rootfs (with Linux kernel placed in /boot/uImage). For the beginning I chose OPIE, which runs on both versions of Sciphone - with 32MB and 64MB of RAM. OPIE is based on Qtopia which is lightweight and runs pretty fast on MT6235. When you run OPIE on Sciphone G2 it works as full blown PDA. In OPIE there is no telephony support. I also ran X window server with blackbox and matchbox window managers. It runs fine with this difference that sometimes I got oops messages concerning memory on phones with 32MB of RAM . I'll investigate it in the future. Next step is running SHR and Android (probably only on 64MB versions). Android will be working very slow, but from marketing point of view "Android" is magic word so I guess it'll bring more interest into project. For building Linux distributions I chose OpenEmbedded where you can build a lot of Linux variations. To be able to do this I prepared patch which adds Sciphone G2 target and adds U-Boot and Linux kernel repositories from OsmocomBB project. All details regarding OE are described on wiki: http://bb.osmocom.org/trac/wiki/SciphoneDreamG2 With above patches you're able now to build Linux distribution with any configuration by yourself (Angtrom, SHR, QTE, OPIE, GPE, etc.). Video presenting how Angstrom Linux with OPIE is running on Sciphone G2 is placed under following link: http://www.youtube.com/watch?v=-_guRruQi0I As you can see, there is already new OsmocomBB logo. When it's on white background, it means that U-Boot is running, when it's on black background it menas that Linux is starting up. On above video I used phone (32MB of RAM) which has only U-Boot flashed, everything else is running from SD card. Unfortunatelly OPIE has a lot of elements on boarders of screen (scrolling, application close, etc.) and Sciphone's touchscreen has pretty bad quality and it doesn't work well. You have to be patient while operating it. In the middle of screen it works pretty well. I'm going to improve touchscreen driver, so hopefully it'll work better. I prepared ready to load images from above presentation for people who want to try it out without building: http://downloads.qi-hardware.com/people/marcin/sciphone_g2_mt6235/images/ Below is short status what's going on now in Linux work. Peripherals which are already running under Linux: 1) GPIO 2) clocks 3) timers 4) SD card 5) LCD frame buffer 6) touch screen 7) keypad 8) NAND - not yet finished under Linux as I had no motivation to finish it (it fully runs under U-Boot) 9) RTC - not yet integrated 10) U-Boot has been rebased to newest version and commit history was cleaned - preparations for mainlining of Sciphone G2 port Topics on which we're working now: 1) rebase Sicphone's kernel to newest version 2) USB 3) Audio - needs to know how DSP is working 4) Android porting I hope above software will also run on your devices. BR, Marcin

9 24

baseband-devel unsubscribe notification
by mailman-bounces＠lists.osmocom.org 18 Feb '11

18 Feb '11

arslangali(a)inbox.ru has been removed from baseband-devel.

1 0

gpsd support
by Dario Lombardo 16 Feb '11

16 Feb '11

Hi all here I am with the first patch to support gpsd. The new code is used only if libgps is found, otherwise old code is used. There is an issue I had to bypass when integrating old code: the osmocom gps_* funcs have identical names to the libgps api :(. So I had to rename the osmocom gps functions to osmo_gps_*. Unfortunately when using logic names for functions sometimes it creates collisions with other code :). Hope this doesn't create new issues. Tell me if you think it can be considered good from coding approach and if it works :). Cheers Dario.

4 8

AW: gpsd support
by Andreas.Eversberg 16 Feb '11

16 Feb '11

On Tue, Feb 15, 2011 at 05:37:48PM +0100, Dario Lombardo wrote: > Hi guys > Any news this side? Are patches ok? Are you planning to merge them? If not, > tell me what's wrong so I can change it. hi dario, sorry, but i did not follow this list the last days. just apply the patch. it seems ok to me. best regards, andreas

1 0

who can to do motorola c375 use osmocom
by 麦田守望 16 Feb '11

16 Feb '11

hi every one</:includetail> who can to do motorola c375 use osmocom </:includetail> please call me thinks </:includetail>

1 0

Re: suggesting new mailing lists for osmocombb
by Aaron Zauner 15 Feb '11

15 Feb '11

hi, its probably best if you post this on the public mailing list, not directly to me, as i am not that involved with the project (this reply is CC to the baseband-devel btw. - so that you dont have to remail it, and everything is in context :)). so long! azet On Tue, Feb 15, 2011 at 9:45 PM, Brian Wiborg <baccenfutter(a)c-base.org> wrote: > On 02/14/2011 08:05 AM, Aaron Zauner wrote: >> >> hi, >> >> as there has been much spam ongoing and countless discussions of >> build-problems from users >> who didnt read the (not quite so good) documentation. i am suggesting a >> new mailing list for new- >> comers, buildproblems and so on. i am a bit frustrated over reading >> countless threads that have >> nothing to do with actual development. >> >> just a suggestion. >> >> so long >> azet >> -- >> "I have no certainties, at most probabilities." -- Renato Caccioppoli > > hi aaron, > > to make it short: > have you folks considered just moving the noise to irc? I'd be really > interested maintaining and developing such a #channel and help the community > collaboratively grow. who would this best be discussed with? > > best regards > brian > -- "I have no certainties, at most probabilities." -- Renato Caccioppoli

1 0

suggesting new mailing lists for osmocombb
by Aaron Zauner 15 Feb '11

15 Feb '11

hi, as there has been much spam ongoing and countless discussions of build-problems from users who didnt read the (not quite so good) documentation. i am suggesting a new mailing list for new- comers, buildproblems and so on. i am a bit frustrated over reading countless threads that have nothing to do with actual development. just a suggestion. so long azet -- "I have no certainties, at most probabilities." -- Renato Caccioppoli

12 15

mt6516
by Marius Cirsta 14 Feb '11

14 Feb '11

Hi Does anyone have any info on Mediatek MT6516 ? I'd like to take a look at a datasheet if possible and I also know Android had been ported to it. Any chance of some open source code being released by Mediatek ? Thanks.

3 2

MTK6325
by J T Dsouza 14 Feb '11

14 Feb '11

I have three of PK168+ Mediatek 6325. Is it possible to use these?

2 1

Re: Hello, Fonts and a LCDgui (plain text)
by Aaron Zauner 14 Feb '11

14 Feb '11

sounds quite interesting, but is it even possible to run osmocombb natively without host and target program (thus with connection to a pc/notebook)? azet -- "I have no certainties, at most probabilities." -- Renato Caccioppoli

1 0

GsmMap glocation sources
by Bogdan Alecu 14 Feb '11

14 Feb '11

Hi all, Sorry for the delay, here are the sources for glocation program I made which uses Google API to get your location. ____________________________________________________________________________________ Need Mail bonding? Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users. http://answers.yahoo.com/dir/?link=list&sid=396546091

3 2

Pirelli DP-L10 support for burst_ind
by Mad 13 Feb '11

13 Feb '11

Hi Sylvain, hi Steve, hi list! I did some kind of backport of Pirelli DP-L10 support for the burst_ind branch, patch attached. Remember that after applying you still have to swap the UARTs as mentioned in the wiki to maintain compatibility with the usual configuration in compal phones. The convenient thing with using the Pirelli with burst_ind is that it works out-of-the-box at high serial speed using its standard usb cable (without 2.5 jack to serial to ftdi-usb constructions). But there is one issue I came across with layer23, after a short time of normal operation when returning from DCH to CCH it just gets stuck. The FBSB request returns 255 as result so I guess the fw was not able to resyncronize. When a new request is made by restarting layer23, it works again for some time. Perhaps it has something to do with the used calibration values like SYSTEM_INHERENT_GAIN for the gain control etc. which could be different with the Pirelli layout? BTW, Sylvain, will there be an integration of burst_ind functionality into the master branch at some time, do you have some plan for this? Regards, Mad

1 0

motorola c375 to do
by 麦田守望 12 Feb '11

12 Feb '11

who know the motorola can to do is it have fireware?

1 0

[PATCH] Added gpsd support.
by Dario Lombardo 10 Feb '11

10 Feb '11

--- src/host/layer23/configure.ac | 1 + src/host/layer23/include/osmocom/bb/common/gps.h | 6 ++ src/host/layer23/src/common/gps.c | 106 +++++++++++++++++++++- src/host/layer23/src/misc/app_cell_log.c | 32 ++++++- src/host/layer23/src/mobile/vty_interface.c | 41 +++++++++ 5 files changed, 182 insertions(+), 4 deletions(-) diff --git a/src/host/layer23/configure.ac b/src/host/layer23/configure.ac index 1be98ee..e1c718e 100644 --- a/src/host/layer23/configure.ac +++ b/src/host/layer23/configure.ac @@ -15,6 +15,7 @@ AC_PROG_RANLIB dnl checks for libraries PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore) PKG_CHECK_MODULES(LIBOSMOVTY, libosmovty) +AC_CHECK_LIB(gps, gps_open, CFLAGS+=" -D_USE_GPSD" LDFLAGS+=" -lgps",,) dnl checks for header files AC_HEADER_STDC diff --git a/src/host/layer23/include/osmocom/bb/common/gps.h b/src/host/layer23/include/osmocom/bb/common/gps.h index 467cee5..b7500db 100644 --- a/src/host/layer23/include/osmocom/bb/common/gps.h +++ b/src/host/layer23/include/osmocom/bb/common/gps.h @@ -22,8 +22,14 @@ struct osmo_gps { /* GPS device */ uint8_t enable; + +#ifdef _USE_GPSD + char gpsd_host[32]; + char gpsd_port[6]; +#else char device[32]; uint32_t baud; +#endif /* current data */ uint8_t valid; /* we have a fix */ diff --git a/src/host/layer23/src/common/gps.c b/src/host/layer23/src/common/gps.c index dfca3b2..55dd239 100644 --- a/src/host/layer23/src/common/gps.c +++ b/src/host/layer23/src/common/gps.c @@ -27,6 +27,10 @@ #include <errno.h> #include <time.h> +#ifdef _USE_GPSD +#include <gps.h> +#endif + #include <osmocore/utils.h> #include <osmocom/bb/common/osmocom_data.h> @@ -35,15 +39,111 @@ struct osmo_gps gps = { 0, +#ifdef _USE_GPSD + "localhost", + "2947", +#else "/dev/ttyACM0", 0, - +#endif 0, 0, - 0,0, + 0,0 }; static struct bsc_fd gps_bfd; + +#ifdef _USE_GPSD + +static struct gps_data_t* gdata; + +int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) +{ + struct tm *tm; + unsigned diff = 0; + + gps.valid = 0; + + /* gps is offline */ + if (gdata->online) + goto gps_not_ready; + + /* gps has no data */ + if (gps_waiting(gdata)) + goto gps_not_ready; + + /* polling returned an error */ + if (gps_poll(gdata)) + goto gps_not_ready; + + /* data are valid */ + if (gdata->set & LATLON_SET) { + gps.valid = 1; + gps.gmt = gdata->fix.time; + tm = localtime(&gps.gmt); + diff = time(NULL) - gps.gmt; + gps.latitude = gdata->fix.latitude; + gps.longitude = gdata->fix.longitude; + + LOGP(DGPS, LOGL_INFO, " time=%02d:%02d:%02d %04d-%02d-%02d, " + "diff-to-host=%d, latitude=%do%.4f, longitude=%do%.4f\n", + tm->tm_hour, tm->tm_min, tm->tm_sec, tm->tm_year + 1900, + tm->tm_mday, tm->tm_mon + 1, diff, + (int)gps.latitude, + (gps.latitude - ((int)gps.latitude)) * 60.0, + (int)gps.longitude, + (gps.longitude - ((int)gps.longitude)) * 60.0); + } + + return 0; + +gps_not_ready: + LOGP(DGPS, LOGL_DEBUG, "gps is offline"); + return -1; +} + +int osmo_gps_open(void) +{ + LOGP(DGPS, LOGL_INFO, "Connecting to gpsd at '%s:%s'\n", gps.gpsd_host, gps.gpsd_port); + + gps_bfd.data = NULL; + gps_bfd.when = BSC_FD_READ; + gps_bfd.cb = osmo_gps_cb; + + gdata = gps_open(gps.gpsd_host, gps.gpsd_port); + if (gdata == NULL) { + LOGP(DGPS, LOGL_ERROR, "Can't connect to gpsd\n"); + return -1; + } + gps_bfd.fd = gdata->gps_fd; + if (gps_bfd.fd < 0) + return gps_bfd.fd; + + if (gps_stream(gdata, WATCH_ENABLE, NULL) == -1) { + LOGP(DGPS, LOGL_ERROR, "Error in gps_stream()\n"); + return -1; + } + + bsc_register_fd(&gps_bfd); + + return 0; +} + +void osmo_gps_close(void) +{ + if (gps_bfd.fd <= 0) + return; + + LOGP(DGPS, LOGL_INFO, "Disconnecting from gpsd\n"); + + bsc_unregister_fd(&gps_bfd); + + gps_close(gdata); + gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ +} + +#else + static struct termios gps_termios, gps_old_termios; static int osmo_gps_line(char *line) @@ -243,6 +343,8 @@ void osmo_gps_close(void) gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ } +#endif + void osmo_gps_init(void) { memset(&gps_bfd, 0, sizeof(gps_bfd)); diff --git a/src/host/layer23/src/misc/app_cell_log.c b/src/host/layer23/src/misc/app_cell_log.c index 0d61226..7a2c67a 100644 --- a/src/host/layer23/src/misc/app_cell_log.c +++ b/src/host/layer23/src/misc/app_cell_log.c @@ -92,8 +92,13 @@ static int l23_getopt_options(struct option **options) {"logfile", 1, 0, 'l'}, {"rach", 1, 0, 'r'}, {"no-rach", 1, 0, 'n'}, +#ifdef _USE_GPSD + {"gpsd-host", 1, 0, 'g'}, + {"gpsd-port", 1, 0, 'p'} +#else {"gps", 1, 0, 'g'}, {"baud", 1, 0, 'b'} +#endif }; *options = opts; @@ -103,11 +108,16 @@ static int l23_getopt_options(struct option **options) static int l23_cfg_print_help() { printf("\nApplication specific\n"); - printf(" -l --logfile LOGFILE Logfile for the cell log.\n"); + printf(" -l --logfile LOGFILE Logfile for the cell log.\n"); printf(" -r --rach RACH Nr. of RACH bursts to send.\n"); printf(" -n --no-rach Send no rach bursts.\n"); +#ifdef _USE_GPSD + printf(" -g --gpsd-host HOST 127.0.0.1. gpsd host.\n"); + printf(" -p --port PORT 2947. gpsd port\n"); +#else printf(" -g --gps DEVICE /dev/ttyACM0. GPS device.\n"); printf(" -b --baud BAUDRAT The baud rate of the GPS device\n"); +#endif return 0; } @@ -123,6 +133,20 @@ static int l23_cfg_handle(int c, const char *optarg) case 'n': RACH_MAX = 0; break; +#ifdef _USE_GPSD + case 'g': + snprintf(gps.gpsd_host, ARRAY_SIZE(gps.gpsd_host), "%s", optarg); + /* force string terminator */ + gps.gpsd_host[ARRAY_SIZE(gps.gpsd_host) - 1] = '\0'; + LOGP(DGPS, LOGL_INFO, "Using gpsd host %s\n", gps.gpsd_host); + break; + case 'p': + snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "%s", optarg); + /* force string terminator */ + gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0'; + LOGP(DGPS, LOGL_INFO, "Using gpsd port %s\n", gps.gpsd_port); + break; +#else case 'g': snprintf(gps.device, ARRAY_SIZE(gps.device), "%s", optarg); /* force string terminator */ @@ -133,14 +157,18 @@ static int l23_cfg_handle(int c, const char *optarg) gps.baud = atoi(optarg); LOGP(DGPS, LOGL_INFO, "Setting GPS baudrate to %u\n", gps.baud); break; +#endif } - return 0; } static struct l23_app_info info = { .copyright = "Copyright (C) 2010 Andreas Eversberg\n", +#ifdef _USE_GPSD + .getopt_string = "l:r:ng:p:", +#else .getopt_string = "l:r:ng:b:", +#endif .cfg_supported = l23_cfg_supported, .cfg_getopt_opt = l23_getopt_options, .cfg_handle_opt = l23_cfg_handle, diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c index ecefc89..7888f01 100644 --- a/src/host/layer23/src/mobile/vty_interface.c +++ b/src/host/layer23/src/mobile/vty_interface.c @@ -855,6 +855,35 @@ DEFUN(cfg_no_gps_enable, cfg_no_gps_enable_cmd, "no gps enable", return CMD_SUCCESS; } +#ifdef _USE_GPSD +DEFUN(cfg_gps_host, cfg_gps_host_cmd, "gps host HOST:PORT", + "GPS receiver\nSelect gpsd host and port\n" + "IP and port (optional) of the host running gpsd") +{ + char* colon = strstr(argv[0], ":"); + if (colon != NULL) { + memcpy(gps.gpsd_host, argv[0], colon - argv[0] - 1); + gps.gpsd_host[colon - argv[0]] = '\0'; + memcpy(gps.gpsd_port, colon, strlen(colon)); + gps.gpsd_port[strlen(colon)] = '\0'; + } else { + snprintf(gps.gpsd_host, ARRAY_SIZE(gps.gpsd_host), "%s", argv[0]); + gps.gpsd_host[ARRAY_SIZE(gps.gpsd_host) - 1] = '\0'; + snprintf(gps.gpsd_port, ARRAY_SIZE(gps.gpsd_port), "2947"); + gps.gpsd_port[ARRAY_SIZE(gps.gpsd_port) - 1] = '\0'; + } + if (gps.enable) { + osmo_gps_close(); + if (osmo_gps_open()) { + vty_out(vty, "Failed to connect to gpsd host!%s", + VTY_NEWLINE); + return CMD_WARNING; + } + } + + return CMD_SUCCESS; +} +#else DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", "GPS receiver\nSelect serial device\n" "Full path of serial device including /dev/") @@ -872,7 +901,9 @@ DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", return CMD_SUCCESS; } +#endif +#ifndef _USE_GPSD DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " "(default|4800|""9600|19200|38400|57600|115200)", "GPS receiver\nSelect baud rate\nDefault, don't modify\n\n\n\n\n\n") @@ -893,6 +924,7 @@ DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " return CMD_SUCCESS; } +#endif /* per MS config */ DEFUN(cfg_ms, cfg_ms_cmd, "ms MS_NAME", @@ -1172,11 +1204,16 @@ static int config_write(struct vty *vty) { struct osmocom_ms *ms; +#ifdef _USE_GPSD + vty_out(vty, "gpsd host %s%s", gps.gpsd_host, VTY_NEWLINE); + vty_out(vty, "gpsd port %s%s", gps.gpsd_port, VTY_NEWLINE); +#else vty_out(vty, "gps device %s%s", gps.device, VTY_NEWLINE); if (gps.baud) vty_out(vty, "gps baudrate %d%s", gps.baud, VTY_NEWLINE); else vty_out(vty, "gps baudrate default%s", VTY_NEWLINE); +#endif vty_out(vty, "%sgps enable%s", (gps.enable) ? "" : "no ", VTY_NEWLINE); vty_out(vty, "!%s", VTY_NEWLINE); @@ -2268,8 +2305,12 @@ int ms_vty_init(void) install_element(ENABLE_NODE, &call_retr_cmd); install_element(ENABLE_NODE, &call_dtmf_cmd); +#ifdef _USE_GPSD + install_element(CONFIG_NODE, &cfg_gps_host_cmd); +#else install_element(CONFIG_NODE, &cfg_gps_device_cmd); install_element(CONFIG_NODE, &cfg_gps_baud_cmd); +#endif install_element(CONFIG_NODE, &cfg_gps_enable_cmd); install_element(CONFIG_NODE, &cfg_no_gps_enable_cmd); -- 1.7.4 --------------010406050303050102020702--

1 0

FCCH and SCH
by list_mailing 10 Feb '11

10 Feb '11

Hello, I'm newbie to osmocomm and GSM too....I'm studying the protocol and the source code...but I have many doubts...the first one is the following: 1. Which are the routines handling FCCH and SCH in osmocom source code? 2. When I load layer1 firmware and load mobile app, FCCH and SCH are automatically handled by this application? Sorry if my questions are stupid for you, but it's a litlle bit complicate moving in the code, above all for a newbie. Thanks in advance. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/FCCH-and-SCH-tp2363201p2363201.h… Sent from the baseband-devel mailing list archive at Nabble.com.

2 2

[PATCH] Renamed gps_* functions to osmo_gps_* functions to avoid overlap with libgps functions.
by Dario Lombardo 10 Feb '11

10 Feb '11

--- src/host/layer23/include/osmocom/bb/common/gps.h | 10 +++++----- src/host/layer23/src/common/gps.c | 16 ++++++++-------- src/host/layer23/src/misc/cell_log.c | 6 +++--- src/host/layer23/src/mobile/app_mobile.c | 4 ++-- src/host/layer23/src/mobile/vty_interface.c | 12 ++++++------ 5 files changed, 24 insertions(+), 24 deletions(-) diff --git a/src/host/layer23/include/osmocom/bb/common/gps.h b/src/host/layer23/include/osmocom/bb/common/gps.h index e45cbc5..467cee5 100644 --- a/src/host/layer23/include/osmocom/bb/common/gps.h +++ b/src/host/layer23/include/osmocom/bb/common/gps.h @@ -19,7 +19,7 @@ * */ -struct gps { +struct osmo_gps { /* GPS device */ uint8_t enable; char device[32]; @@ -31,10 +31,10 @@ struct gps { double latitude, longitude; }; -extern struct gps gps; +extern struct osmo_gps gps; -int gps_open(void); -void gps_close(void); -void gps_init(void); +int osmo_gps_open(void); +void osmo_gps_close(void); +void osmo_gps_init(void); diff --git a/src/host/layer23/src/common/gps.c b/src/host/layer23/src/common/gps.c index a092cd0..dfca3b2 100644 --- a/src/host/layer23/src/common/gps.c +++ b/src/host/layer23/src/common/gps.c @@ -33,7 +33,7 @@ #include <osmocom/bb/common/logging.h> #include <osmocom/bb/common/gps.h> -struct gps gps = { +struct osmo_gps gps = { 0, "/dev/ttyACM0", 0, @@ -46,7 +46,7 @@ struct gps gps = { static struct bsc_fd gps_bfd; static struct termios gps_termios, gps_old_termios; -static int gps_line(char *line) +static int osmo_gps_line(char *line) { time_t gps_now, host_now; struct tm *tm; @@ -141,7 +141,7 @@ static int nmea_checksum(char *line) return (strtoul(line+1, NULL, 16) == checksum); } -int gps_cb(struct bsc_fd *bfd, unsigned int what) +int osmo_gps_cb(struct bsc_fd *bfd, unsigned int what) { char buff[128]; static char line[128]; @@ -165,7 +165,7 @@ int gps_cb(struct bsc_fd *bfd, unsigned int what) if (!nmea_checksum(line)) fprintf(stderr, "NMEA checksum error\n"); else - gps_line(line); + osmo_gps_line(line); continue; } line[lpos++] = buff[i++]; @@ -176,7 +176,7 @@ int gps_cb(struct bsc_fd *bfd, unsigned int what) return 0; } -int gps_open(void) +int osmo_gps_open(void) { int baud = 0; @@ -187,7 +187,7 @@ int gps_open(void) gps_bfd.data = NULL; gps_bfd.when = BSC_FD_READ; - gps_bfd.cb = gps_cb; + gps_bfd.cb = osmo_gps_cb; gps_bfd.fd = open(gps.device, O_RDONLY); if (gps_bfd.fd < 0) return gps_bfd.fd; @@ -227,7 +227,7 @@ int gps_open(void) return 0; } -void gps_close(void) +void osmo_gps_close(void) { if (gps_bfd.fd <= 0) return; @@ -243,7 +243,7 @@ void gps_close(void) gps_bfd.fd = -1; /* -1 or 0 indicates: 'close' */ } -void gps_init(void) +void osmo_gps_init(void) { memset(&gps_bfd, 0, sizeof(gps_bfd)); } diff --git a/src/host/layer23/src/misc/cell_log.c b/src/host/layer23/src/misc/cell_log.c index 93616f2..a0f9769 100644 --- a/src/host/layer23/src/misc/cell_log.c +++ b/src/host/layer23/src/misc/cell_log.c @@ -787,8 +787,8 @@ int scan_init(struct osmocom_ms *_ms) memset(&timer, 0, sizeof(timer)); osmol2_register_handler(ms, &rcv_rsl); gps.enable = 1; - gps_init(); - if (gps_open()) + osmo_gps_init(); + if (osmo_gps_open()) gps.enable = 0; if (!strcmp(logname, "-")) @@ -809,7 +809,7 @@ int scan_exit(void) { LOGP(DSUM, LOGL_INFO, "Scanner exit\n"); if (gps.valid) - gps_close(); + osmo_gps_close(); if (logfp) fclose(logfp); unregister_signal_handler(SS_L1CTL, &signal_cb, NULL); diff --git a/src/host/layer23/src/mobile/app_mobile.c b/src/host/layer23/src/mobile/app_mobile.c index 822ea64..1bedb55 100644 --- a/src/host/layer23/src/mobile/app_mobile.c +++ b/src/host/layer23/src/mobile/app_mobile.c @@ -333,7 +333,7 @@ int l23_app_exit(void) unregister_signal_handler(SS_L1CTL, &mobile_signal_cb, NULL); unregister_signal_handler(SS_GLOBAL, &global_signal_cb, NULL); - gps_close(); + osmo_gps_close(); return 0; } @@ -353,7 +353,7 @@ int l23_app_init(int (*mncc_recv)(struct osmocom_ms *ms, int, void *), mncc_recv_app = mncc_recv; - gps_init(); + osmo_gps_init(); vty_init(&vty_info); ms_vty_init(); diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c index 4cc2209..ecefc89 100644 --- a/src/host/layer23/src/mobile/vty_interface.c +++ b/src/host/layer23/src/mobile/vty_interface.c @@ -835,7 +835,7 @@ DEFUN(network_search, network_search_cmd, "network search MS_NAME", DEFUN(cfg_gps_enable, cfg_gps_enable_cmd, "gps enable", "GPS receiver") { - if (gps_open()) { + if (osmo_gps_open()) { gps.enable = 1; vty_out(vty, "Failed to open GPS device!%s", VTY_NEWLINE); return CMD_WARNING; @@ -849,7 +849,7 @@ DEFUN(cfg_no_gps_enable, cfg_no_gps_enable_cmd, "no gps enable", NO_STR "Disable GPS receiver") { if (gps.enable) - gps_close(); + osmo_gps_close(); gps.enable = 0; return CMD_SUCCESS; @@ -862,8 +862,8 @@ DEFUN(cfg_gps_device, cfg_gps_device_cmd, "gps device DEVICE", strncpy(gps.device, argv[0], sizeof(gps.device)); gps.device[sizeof(gps.device) - 1] = '\0'; if (gps.enable) { - gps_close(); - if (gps_open()) { + osmo_gps_close(); + if (osmo_gps_open()) { vty_out(vty, "Failed to open GPS device!%s", VTY_NEWLINE); return CMD_WARNING; @@ -882,8 +882,8 @@ DEFUN(cfg_gps_baud, cfg_gps_baud_cmd, "gps baudrate " else gps.baud = atoi(argv[0]); if (gps.enable) { - gps_close(); - if (gps_open()) { + osmo_gps_close(); + if (osmo_gps_open()) { gps.enable = 0; vty_out(vty, "Failed to open GPS device!%s", VTY_NEWLINE); -- 1.7.4 --------------010406050303050102020702 Content-Type: text/x-patch; name="0002-Added-gpsd-support.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0002-Added-gpsd-support.patch"

1 0

moving layer23 into the phone
by Harald Welte 09 Feb '11

09 Feb '11

On Tue, Feb 08, 2011 at 09:08:40AM +0100, Rade Girel wrote: > Thats true, but i for myself hope that one day the layer23 code is > moved into the phone. At that time i would really like to have a > tested, accepted in short usable UI on th osmocomBB compal phones. I think we can start by moving the stuff step by step into the phone, if anyone wants to work on this, it would be much appreciated. Layer2 (LAPDm) should be relatively simple, but starting from RR/MM/CC and the cell reselection I expect some more difficulties... 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)

6 7

Requesting SIM file 0x2fe2 - mobile application problem
by Grzegusz 09 Feb '11

09 Feb '11

Hi, I have problem with ./mobile application. When I run this application I have only information that sending APDU (class 0xa0, ins 0xa4). Some more information: 1. At first I started layer1 firmware n motorola C115 ./osmocon -p /dev/ttyS0 -m c123xor /root/osmocom-bb/src/target/firmware/board/compal_e88/layer1.compalram.bin 2. Second I execute ./mobile ./mobile -i 224.0.0.0 3. I pressed power button on my phone. After this I received only this following information: <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:3471 init PLMN process <0003> gsm322.c:3472 init Cell Selection process <0003> gsm322.c:3522 Read stored BA list (mcc=260 mnc=02 Poland, Era) <0003> gsm322.c:3522 Read stored BA list (mcc=260 mnc=01 Poland, Plus) <0003> gsm322.c:3522 Read stored BA list (mcc=260 mnc=06 Poland, Play) <0003> gsm322.c:3522 Read stored BA list (mcc=260 mnc=03 Poland, Orange) Mobile '1' initialized, please start phone now! VTY available on port 4247. <0004> subscriber.c:556 Requesting SIM file 0x2fe2 <000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000e> sim.c:697 go MF <000e> sim.c:241 SELECT (file=0x3f00) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4) I am waiting, waiting, waiting but unfortunately without progress... Bellow my osmocom.cfg file: ! ! OsmocomBB () configuration saved from vty !! ! line vty no login ! gps device /dev/ttyACM0 gps baudrate default no gps enable ! ms 1 layer2-socket /tmp/osmocom_l2 sap-socket /tmp/osmocom_sap sim reader network-selection-mode auto imei 000000000000000 0 imei-fixed no emergency-imsi no call-waiting no auto-answer no clip no clir tx-power auto no simulated-delay no stick location-updating codec full-speed prefer codec half-speed no abbrev support sms a5/1 a5/2 p-gsm e-gsm r-gsm dcs class-900 4 class-dcs 1 channel-capability sdcch+tchf+tchh full-speech-v1 full-speech-v2 half-speech-v1 min-rxlev -106 dsc-max 90 exit test-sim imsi 001010000000000 ki xor 00 00 00 00 00 00 00 00 00 00 00 00 no barred-access no rplmn hplmn-search foreign-country exit no shutdown exit ! Unfortunately I have no idea how to resolve this problem so please help me... br, Grzegusz

2 1

Hello, Fonts and a LCDgui (plain text)
by Rade Girel 08 Feb '11

08 Feb '11

Hello OsmocomBB list members, To shortly introduce myself, i am a sysadmin with much spare time and a Motorola C115 mobile phone. I came to this place after watching a recording of the OsmocomBB talk at the 27c3. That really started my interest on opensource GSM. After reading the wikipages and the mailing list archives i downloaded the sources and had a fully compiling OsmocomBB setup within a few hours. Great work! After slaying some headphonecables and an usbcable i hooked my c115 onto the serialport of my pc and it booted out of the box! Since i am neither a programmer nor an electronic engineer i thought about what i could be interested in doing that contrbiutes to OsmocomBB. (Learning a little C has not hurt too many people i think. so i am on it.) I didnt find it at http://bb.osmocom.org/trac/wiki/AreasOfWork but in the Mailinglistarchives of April-2010 i stumbled upon Christian Vogels post "Subject: PATCH: 5x8 font". After some manual patching i made it to compile the demo app (Printing all available characters in the font from upper left corner down to the bottom. Now that looked allmost like a phone :) It seems like there have not been any follow ups on proportional fonts and the remaining ascii characters as well as the possibility to view different sizes of fonts on the screen. Because there is not much to see on the C115 and there is no navigationsystem of any kind implemented in the compal_e88 firmware I typed together a ericsson clone menu structure with a total of 330 menuitems (transations english to german allmost finished) to have something to display once the proportional 5x8 fonts are finished. now i would continue to write a menu action handler that checks if a navigation key is pressed if a entry in the menu is selected lets look if there is a PhoneMenu "muid" with the siblings "suid" the menu is drawn. if it is a sibling only a switch case list where all actions get caught and processed will handle it. Well, what do you think about that? Should it be built in another way? Am i to early in typing menue structures while the whole "rendering" is not sorted out in any way? Does anyone work on the fonts or a UI? I really am not able judge whether a nested structure monster like this really is the right solution. What it definitly is it is easy to read understand and extend. at least for me ;) if someone wants it i can post the complete menu (~1200 lines) somewhere. Best wishes, Rade Below are some snipplets of the things i allready did: ...sniplets... struct PhoneMenu { &nbspint muid; /* menu uid */ &nbspconst char* menuLabel_en; /* menu name, english */ &nbspconst char* menuLabel_de; /* menu name, german */ &nbspchar siblings; /* amount of siblings within the menu */ &nbspstruct PhoneMenuSibling pms[]; /* nested structure below */ }; struct PhoneMenuSibling { &nbspint suid; /* sibling uid */ &nbspconst char* siblingLabel_en; /* label in english */ &nbspconst char* siblingLabel_de; /* label in german */ }; .... A Menu looks like this: struct PhoneMenu menu = /* the startscreen */ { 0, "Main Menu", /* menu label */ "HauptmenÃ¼", /* menu label in german language */ 6, /* 6 items in the list below */ { {1, "Phonebook", "Telefonbuch"}, {2, "Messages", "Nachrichten"}, {3, "Call information", "Anrufinformation"}, {4, "Active call", "Aktive Verbindung"}, {5, "Settings", "Einstellungen"}, {6, "Extras", "Extras"} } }; struct PhoneMenu menu_phone_book = { 1, "Phone book", "Telefonbuch", 10, { {11, "Call Contact", "Kontak Anrufen"}, {12, "Add Contact", "Kontakt hinzufÃ¼gen"}, {13, "Edit Contact", "Kontakte bearbeiten"}, {14, "Business Cards", "Visitenkarten"}, {15, "Call from SIM", "Adresse aus SIM"}, {16, "Groups", "Gruppen"}, {17, "Calling Cards", "Rufkarten"}, {18, "Options", "Optionen"}, {19, "Memory status", "Speicherverbrauch"} {10, "Special numbers", "Spezialnummern"} } }; ....... struct PhoneMenu menu_phone_book_business_cards_receive = { 143, "Receive", "empfange Visitenkarte", 2, { {1431, "Via Infrared", "via Infrarot"}, {1432, "Via Bluetooth", "via Bluetooth"} } };

4 5

Hello, Fonts and a LCDgui
by Rade Girel 07 Feb '11

07 Feb '11

3 2

Re: Emergency number
by Bogdan Alecu 07 Feb '11

07 Feb '11

>Do you run your own network? How do you plan to test your modifications? No, I'm not running my own network. I tried to make an emergency call and I got a voice saying to call to different numbers (police, fire dept, etc). That's why I need to know exactly what number is dialed from Osmocom and where I can modify it. I looked on the code but couldn't find (maybe I'm too tired).

2 2

thinking about the sim
by Sébastien Lorquet 07 Feb '11

07 Feb '11

Hello, I was walking through trac while I came across this file: http://bb.osmocom.org/trac/browser/src/host/layer23/src/common/sim.c I see here: 183 /* send APDU to card reader */ 184 static int sim_apdu_send(struct osmocom_ms *ms, uint8_t *data, uint16_t length) 185 { 186 LOGP(DSIM, LOGL_INFO, "sending APDU (class 0x%02x, ins 0x%02x)\n", 187 data[0], data[1]); 188 l1ctl_tx_sim_req(ms, data, length); 189 return 0; 190 } ohoh, that's hardcoded. If we would like to have a software SIM, a SIM in a card reader on the PC, or a real sim in the MS, I think this would this be the correct place to plug a modular sim implementation. I mean something that looks like: struct osmocom_sim_ops { int (*sim_apdu_init)(.....); int (*sim_apdu_fini)(.....); void (*sim_op_reset)(.....); void (*sim_apdu_send)(.....); void (*sim_response_callback)(.....); }; void ms_register_sim_driver(struct osmocom_ms *ms, struct osmocom_sim_ops *ops); this could be a part of struct osmocom_ms. I would be easy to have 3 implementations: -sim in the mobile, using the current calls 'l1ctl_tx_sim_req' 'l1ctl_tx_sim_conf' -sim in PCSC using pcsclite or winscard, and a command-line option to select the reader (by index, by name, or first reader with a card inside for simple setups) -virtual sim using pure software What do you think about this? Regards Sebastien

4 6

Emergency number
by Bogdan Alecu 07 Feb '11

07 Feb '11

Hello, What number is it dialed when I place the emergency call? Maybe you could also point me to where I find that number as I want to modify it. Thanks. Regards, Bogdan

3 2

Re: GsmMap without GPS
by Bogdan Alecu 07 Feb '11

07 Feb '11

Hi all, Harald - I will put the sourcecode later on today. The reason I didn't was because the code it's not so clean and good - but it works. Martynas - my phone remain stationary and in fact I have over 40 cells (from other networks too). I don't find it to be a lot. About the precision, Google returned "accuracy":3875.0" which is surprisingly true. I was about 3-4km away from the final coordinates. Maybe I'll modify the code to give the position for each cell it finds. Tomas - No proprietary libraries, the code will be here in the evening. It's not so professional done, but considering that it took me somewhere around 30 minutes, I'm good with it. Regards, Bogdan

1 0

GsmMap without GPS
by Bogdan Alecu 06 Feb '11

06 Feb '11

As I said in a previous post, I don't see why I need to have a GPS to get an approximation of my location. I then suggested using an open source cell list or Google API. So, I have just finished writing a program that parses your kml file from the gsmmap, send the request to Google and it will get your approx location (just like Google Maps on your mobile) and write the result in another kml file. The program is written in Java. To run it under windows: C:\Program Files\Java\jdk1.6.0_17\bin>java -jar glocation.jar Usage: glocation -i <path to input file> -o <output file> C:\Program Files\Java\jdk1.6.0_17\bin>java -jar glocation.jar -i c:\gsm.kml -o final.kml Name : MNC 03 (T-Mobile) Name : LAC 3030 Name : CELL-ID 0031 Name : CELL-ID 0032 Name : CELL-ID 135c Name : CELL-ID 24a7 Name : CELL-ID 4c2a Name : CELL-ID 4c31 Name : CELL-ID 4d10 Name : CELL-ID 51e3 Name : CELL-ID 537b Name : CELL-ID 5567 Name : CELL-ID 5f8a Name : LAC 4010 Name : CELL-ID 4c34 Name : CELL-ID 5b4b --------------------------------------- Sending data to Google... {"location":{"latitude":48.21451,"longitude":16.356414,"accuracy":511.0},"access _token":"2:BaEsaRey871FCt1e:A5vJ-lyJuPrukpMV"} lat=48.21451 long=16.356414

3 3

Wiki & Osmocom.cfg
by Luca Antani 06 Feb '11

06 Feb '11

Hi list! Thanks to the mailing-list's archive i found how to activate the "sim reader" option on osmocom.cfg. Now i'm trying to find on the wiki some more infos about osmocom.cfg configuration, but seems to be missing. Some hints?! Thank you for attention Regards Luca

1 0

how to dump phone firmware
by Scott Weisman 05 Feb '11

05 Feb '11

I recently acquired the Pirelli phone. I was wondering if there was a way to dump the stock firmware in the phone for exploration? Thanks, Scott

2 1

Re: Non Standard Baud Rates?
by MATTHEW EVANS 04 Feb '11

04 Feb '11

*bump* Anyone have any thoughts / advice on this? Many Thanks, Matt. ----- Original Message ---- From: MATTHEW EVANS <mattjevans(a)btinternet.com> To: baseband-devel(a)lists.osmocom.org Sent: Friday, 21 January, 2011 21:08:36 Subject: Non Standard Baud Rates? Hi, I'm trying to get the burst_ind branch working at the higher speed baud rates. I have a USB to Serial FTDI Cable (FT232R) plus the T191. This setup works fine with the main trunk of osmocombb. When I fire up osmocon, layer1 appears to download to the phone and runs successfully. Osmocon then logs 'Received DOWNLOAD ACK from phone, your code is running now!'. The phone has layer1.bin displayed as usual. However it goes no further and just hangs. Could anyone please give any advice on what to try next? Thanks, Matt.

1 0

Re: in deep trouble
by Bogdan Alecu 03 Feb '11

03 Feb '11

Make sure of the following: 1. Edit ~/.bashrc and put export PATH=$PATH:<YOURPATH>/install/bin , where "yourpath" is your full path to where arm-elf-gcc is located 2. restart your computer (sometimes it helps) 3. run the "make" under the same user that has the above path (no sudo make !!!)

4 3

AGCH question.
by Leonardo Nve 03 Feb '11

03 Feb '11

Hi everyone. I´m coding a fuzzer with osmocombb API, I expect send you something good in a mounth or two (It depends how much work i have). I have two questions. First, I triying a simple SMS handler, to send and receive. With wireshark I don´t see RACH request, I suppose it is because the DSP inside the phone manage it, am I wrong? About this, I don´t have knowledge about electronics, so I don´t want touch, any filter. So I need to see the RACH of the same phone were osmo is running, not another. The second question is about SI AGCH response, I didn´t find the algorithm to know which SDCCH channel gives the BTS to the MS to send/recv LAPDm bursts. --- Leonardo Nve leonardo.nve(a)gmail.com ---

3 3

in little deep trouble
by Sarfraz Alam Khan 03 Feb '11

03 Feb '11

hi, i typed "make osmocon" and "make layer23" and got some output.but i did not get the firmware binaries in *src/target/firmware/board/compal_e88 *and* in **src/host/osmocon/osmocon*, in *src/host/layer23/src/misc* and * layer23/src/mobile*. instead i got files like *.o,*.c etc.. plz help

2 1

in deep trouble
by Sarfraz Alam Khan 03 Feb '11

03 Feb '11

hi, i am having errors while bulding osmocom.I tried finding the solution in archives(that of zaki and others) but was unable to figure out. the error is: configure: error: in `/home/gsm/pro/osmocom-bb/src/shared/libosmocore/build-target': configure: error: C compiler cannot create executables See `config.log' for more details make: *** [shared/libosmocore/build-target/Makefile] Error 77 i am also attaching the config.log file plz help me out.

2 1

[PATCH] Two minor patches for the firmware
by Holger Freyther 02 Feb '11

02 Feb '11

Hi laf0rge, I was building the firmware with a GCC 4.5.2 created by Steve-m's script and had to include limits.h for UINT_MAX. While reading the code I stumbled across a typo... I think the patches can be picked to master as well. holger

2 3

SIMtrace issues
by tsaitgaist 02 Feb '11

02 Feb '11

hi, I'll be listing some issues I found in SIMtrace. This is to warn future users. I don't have time now, but I intend to work on this project in 1 or 2 weeks and correct these bugs. 1. when starting host program simtrace, the firmware will first return ATR. This is an error if simtrace is started after the card has been reseted. The program should use the state of the reset and vcc lines to know the state. 2. when using a usb hub, having a lot of USB traffic, or poor USB signal quality (I don't know exactly), bulk read timeouts can occur in host program simtrace/at91sam7/host/main.c line 230: rc = usb_bulk_read(udev, SIMTRACE_IN_EP, buf, sizeof(buf), 100000); rc is -110 (REQUEST_TIMEOUT). I increased the timeout (100000) so to have less errors (but they still occur), and I ignore this error instead of exiting (tracing still works). 3. it seems simtrace can loose track of the I/O stream after some traffic. see pcsc_apdu.log to see the original, and simtrace_apdu.log for the captured traffic. in the end, simtrace misses: APDU: A0 C0 00 00 0F and does a wrong following APDU parsing The problem occurs when using a OmniKey CardMan 5321 and Alcor Micro AU9520. Thus the reader should not be the origin. Also, if only the command where the error occurs is sent, no bytes are skipped. But another error occurs (see next bug) 4. when executing only the last commands, then it is wrongly interpreted (as ATR), but no bytes are skipped ATR (12): 3b 0a 41 00 3f 43 00 01 50 29 01 02 ATR (66): a0 a4 00 00 02 a4 7f 20 9f 17 a0 a4 00 00 02 a4 6f ad 9f 0f a0 c0 00 00 0f c0 00 00 00 03 6f ad 04 00 04 f0 44 01 02 00 00 90 00 a0 b0 00 00 03 b0 00 00 00 90 00 3b 0a 41 00 3f 43 00 01 50 29 01 02 I already wrote a SIM traffic parser for the PC before simtrace appeared. I used a logic analyzer to record the traffic. I will integrate the ATR and APDU parsing/checking into the simtrace firmware. Wrong recorded traffic will be discarded instead of affecting the rest of the parsing. thanks, kevin

3 3

cell_log and debug
by Dario Lombardo 01 Feb '11

01 Feb '11

Shame on me when I'm not able to print debug messages from cell_log :) but... cell_log -d DRR,3 doesn't give me any additional output. I would like to see the line LOGP(DRR, LOGL_INFO, "IMMEDIATE ASSIGNMENT:\n"); from cell_log.c. Can anybody help me?

2 1

http mirror for osmocom-bb.git ?
by Sébastien Lorquet 01 Feb '11

01 Feb '11

Hi, I know we have a http git mirror for openbsc. Do we have the same for osmocom-bb.git? the git tcp port is censored where I'm connected from. Sorry if I misread the list archive :( Sebastien

3 3

osmocomSIM
by tsaitgaist 31 Jan '11

31 Jan '11

Hi, how about opening the sub-project osmocomSIM ? This could include: - SIMtrace from Harald - SAP server from Andreas - SIM on javacard from Sébastien - future software/virtual SIM which could use SAP server - speaking about A38, Ki, SIM features, ... kevin

2 2

What I am doing wrong? G2
by Панфилов Дмитрий 31 Jan '11

31 Jan '11

Hi! So, I decide to play with my G2 SciPhone (My phone has configuration as follows: 512Mb (64MB) NAND + 32MB RAM) But I could not run U-Boot... The first step seems to be good. I run Osmocon and download "loader" to the phone. I got "Running on mt62xx in environment mtkram HW_CODE = 0x6235" message. After executing $ ./osmoload memload 0x500000 u-boot.bin I can see progress and successfull download of u-boot.bin First of all I tried to use u-boot from here http://downloads.qi-hardware.com/people/marcin/g2_uboot.bin (http://downloads.qi-hardware.com/people/marcin/g2_uboot.bin) Executing $ ./osmoload jump 0x500000 leads to... nothing. I can see black screen. That's all. Also I compilled u-boot from git using toolchain kindly given by Andrew :-) $ ./osmoload jump 0x500000 leads to gray screen after flashing white for a moment. It looks like wrong LCD controller or driver. So... The simple question. What I am doing wrong? :)

1 0

[PATCH 2/2] typo: Fix typo, transform reqyests to requests.
by Holger Hans Peter Freyther 31 Jan '11

31 Jan '11

--- firmware/src/pcd/main_dumbreader.c | 2 +- firmware/src/pcd/main_hid.c | 2 +- firmware/src/pcd/main_presence.c | 2 +- firmware/src/pcd/main_pwm.c | 2 +- firmware/src/pcd/main_usb.c | 2 +- firmware/src/picc/main_openpicc.c | 2 +- firmware/src/simtrace/main_simtrace.c | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/firmware/src/pcd/main_dumbreader.c b/firmware/src/pcd/main_dumbreader.c index 62695f0..9c8dd13 100644 --- a/firmware/src/pcd/main_dumbreader.c +++ b/firmware/src/pcd/main_dumbreader.c @@ -88,7 +88,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); rc632_unthrottle(); diff --git a/firmware/src/pcd/main_hid.c b/firmware/src/pcd/main_hid.c index 9735c3d..c9d8fd1 100644 --- a/firmware/src/pcd/main_hid.c +++ b/firmware/src/pcd/main_hid.c @@ -50,7 +50,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); /* try unthrottling sources since we now are [more] likely to diff --git a/firmware/src/pcd/main_presence.c b/firmware/src/pcd/main_presence.c index f61878f..4ead264 100644 --- a/firmware/src/pcd/main_presence.c +++ b/firmware/src/pcd/main_presence.c @@ -157,7 +157,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); rc632_unthrottle(); } diff --git a/firmware/src/pcd/main_pwm.c b/firmware/src/pcd/main_pwm.c index 7db6b72..50fd363 100644 --- a/firmware/src/pcd/main_pwm.c +++ b/firmware/src/pcd/main_pwm.c @@ -262,7 +262,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); /* try unthrottling sources since we now are [more] likely to diff --git a/firmware/src/pcd/main_usb.c b/firmware/src/pcd/main_usb.c index fcd3306..7892e77 100644 --- a/firmware/src/pcd/main_usb.c +++ b/firmware/src/pcd/main_usb.c @@ -35,7 +35,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); /* try unthrottling sources since we now are [more] likely to diff --git a/firmware/src/picc/main_openpicc.c b/firmware/src/picc/main_openpicc.c index 74700f8..93ca4b6 100644 --- a/firmware/src/picc/main_openpicc.c +++ b/firmware/src/picc/main_openpicc.c @@ -251,7 +251,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); udp_unthrottle(); diff --git a/firmware/src/simtrace/main_simtrace.c b/firmware/src/simtrace/main_simtrace.c index 5e4302e..740d35d 100644 --- a/firmware/src/simtrace/main_simtrace.c +++ b/firmware/src/simtrace/main_simtrace.c @@ -95,7 +95,7 @@ void _main_func(void) /* first we try to get rid of pending to-be-sent stuff */ usb_out_process(); - /* next we deal with incoming reqyests from USB EP1 (OUT) */ + /* next we deal with incoming requests from USB EP1 (OUT) */ usb_in_process(); udp_unthrottle(); -- 1.7.3.5 --------------090305060903020708070409--

1 0

[PATCH 1/2] vsprintf.c: Fix compilation by including limits.h
by Holger Hans Peter Freyther 31 Jan '11

31 Jan '11

The INT_MAX define was not known to this code with a GCC 4.5.2/binutils 2.21/newlib 1.19.0 toolchain as build for osmocomBB. Include limits.h to fix that. --- firmware/lib/vsprintf.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/firmware/lib/vsprintf.c b/firmware/lib/vsprintf.c index 5da7c02..799eb78 100644 --- a/firmware/lib/vsprintf.c +++ b/firmware/lib/vsprintf.c @@ -17,6 +17,7 @@ */ #include <stdarg.h> +#include <limits.h> #include <sys/types.h> #include <string.h> #include <asm/ctype.h> -- 1.7.3.5 --------------090305060903020708070409 Content-Type: text/x-patch; name="0002-typo-Fix-typo-transform-reqyests-to-requests.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0="0002-typo-Fix-typo-transform-reqyests-to-requests.patch"

1 0

Reading / sending SMS
by Bogdan Alecu 31 Jan '11

31 Jan '11

Hello, Has anyone managed to read (receive) or to send an SMS to Osmocom phone? I haven't found any vty command that would allow this. Also if I send an SMS to Osmocom the phone starts a location update every 1 minute or so and on the phone that sent the message I get the non-delivery report. Could someone give me some tips on how to send/receive SMS?

2 1

track ticket
by tsaitgaist 31 Jan '11

31 Jan '11

Hi, Could it be possible to enable the ticket system in trac ? It could be used to add suggestions/bugs/todo/..., avoid overloading the mailing list, and keep trac of them. For example, how about changing the mobile welcome message from: Welcome to the OpenBSC Control interface to: Welcome to the osmocom Control interface it makes more sense when using osmocomBB. thanks, kevin

4 4

Re: Channel info
by Bogdan Alecu 31 Jan '11

31 Jan '11

When I look in the output of the mobile app I see that IMSI paging goes almos up to 50%. It's almost like for every TMSI I get below a IMSI paging. That's why I asked from the beginning because I get a lot of IMSI there.

1 0

Re: Channel info
by Bogdan Alecu 31 Jan '11

31 Jan '11

When I look in the output of the mobile app I see that IMSI paging goes almos up to 50%. It's almost like for every TMSI I get below a IMSI paging. That's why I asked from the beginning because I get a lot of IMSI there.

2 2

[RFC] simplify intra-mobile event passing
by Harald Welte 30 Jan '11

30 Jan '11

Hi! I've been playing with some code earlier today, trying to reuse the RR implementation of 'mobile' but without 'MM' and '03.22' code. Next step was to play with RR+MM but without 03.22. Both were not that easy to do, given the various different function calls between those modules. While trying to resolve it, I discovered that we have many sequences like gsm322_msgb_alloc() followed by some error checking and a final gsm322_plmn_senmsg(). Similar pattersn could be seen for gsm48_mmevent. I've tried to simplify/unify this code a bit, as you can see from the attached patches (also in laforge/mobile_event branch). It's not tested yet, but I would like to get some comments on it. Initially I thought to use libosmocore signal code, but then signals are _emitted_, and they don't fit the picture where we have some incoming events into e.g. 03.22 code - as all the events are already labelled GSM322 and thus by the recipient, not its originator. So now there is one gsm322_event_input() and a gsm48_mmevent_input() function each. Somebody who wants to reuse partial 'mobile' code can simply provide stub functions for either one of those (or both)... The goal of this exercise is to have a tool that can open a dedicated channel to a user-specified cell and then send user-specified messages while optionally taking care of loc upd / auth / ciphering in order to make the network happy. 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)

1 0

[PATCH 3/3] [mobile] introduce and use gsm48_mmevevent_input()
by Harald Welte 30 Jan '11

30 Jan '11

... instead of using sequences of gsm48_mmevent_msgb_alloc() followed by gsm48_mmevent_msg() --- .../layer23/include/osmocom/bb/mobile/gsm48_mm.h | 4 +- src/host/layer23/src/mobile/app_mobile.c | 5 +-- src/host/layer23/src/mobile/gsm322.c | 41 +++----------------- src/host/layer23/src/mobile/gsm48_mm.c | 41 ++++++++++++-------- src/host/layer23/src/mobile/gsm48_rr.c | 6 +-- src/host/layer23/src/mobile/subscriber.c | 31 +++------------ 6 files changed, 41 insertions(+), 87 deletions(-) diff --git a/src/host/layer23/include/osmocom/bb/mobile/gsm48_mm.h b/src/host/layer23/include/osmocom/bb/mobile/gsm48_mm.h index 447dc95..c141d5c 100644 --- a/src/host/layer23/include/osmocom/bb/mobile/gsm48_mm.h +++ b/src/host/layer23/include/osmocom/bb/mobile/gsm48_mm.h @@ -210,8 +210,8 @@ struct gsm48_mm_conn { int gsm48_mm_init(struct osmocom_ms *ms); int gsm48_mm_exit(struct osmocom_ms *ms); struct msgb *gsm48_mmr_msgb_alloc(int msg_type); -struct msgb *gsm48_mmevent_msgb_alloc(int msg_type); -int gsm48_mmevent_msg(struct osmocom_ms *ms, struct msgb *msg); +int gsm48_mmevent_input(struct osmocom_ms *ms, int msg_type, + const uint8_t *data, unsigned int len); int gsm48_mmr_downmsg(struct osmocom_ms *ms, struct msgb *msg); int gsm48_rr_dequeue(struct osmocom_ms *ms); int gsm48_mmxx_dequeue(struct osmocom_ms *ms); diff --git a/src/host/layer23/src/mobile/app_mobile.c b/src/host/layer23/src/mobile/app_mobile.c index b3c3284..4e6a803 100644 --- a/src/host/layer23/src/mobile/app_mobile.c +++ b/src/host/layer23/src/mobile/app_mobile.c @@ -124,10 +124,7 @@ int mobile_exit(struct osmocom_ms *ms, int force) struct msgb *nmsg; ms->shutdown = 1; /* going down */ - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_IMSI_DETACH); - if (!nmsg) - return -ENOMEM; - gsm48_mmevent_msg(mm->ms, nmsg); + gsm48_mmevent_input(ms, GSM48_MM_EVENT_IMSI_DETACH, NULL, 0); return -EBUSY; } diff --git a/src/host/layer23/src/mobile/gsm322.c b/src/host/layer23/src/mobile/gsm322.c index 3243afc..60b24cb 100644 --- a/src/host/layer23/src/mobile/gsm322.c +++ b/src/host/layer23/src/mobile/gsm322.c @@ -1174,17 +1174,12 @@ static int gsm322_a_hplmn_search_start(struct osmocom_ms *ms, struct msgb *msg) /* manual mode selected */ static int gsm322_a_sel_manual(struct osmocom_ms *ms, struct msgb *msg) { - struct msgb *nmsg; - /* restart state machine */ gsm322_a_switch_off(ms, msg); ms->settings.plmn_mode = PLMN_MODE_MANUAL; gsm322_m_switch_on(ms, msg); - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_USER_PLMN_SEL); - if (!nmsg) - return -ENOMEM; - gsm48_mmevent_msg(ms, nmsg); + gsm48_mmevent_input(ms, GSM48_MM_EVENT_USER_PLMN_SEL, NULL, 0); return 0; } @@ -1461,17 +1456,12 @@ static int gsm322_m_choose_plmn(struct osmocom_ms *ms, struct msgb *msg) /* auto mode selected */ static int gsm322_m_sel_auto(struct osmocom_ms *ms, struct msgb *msg) { - struct msgb *nmsg; - /* restart state machine */ gsm322_m_switch_off(ms, msg); ms->settings.plmn_mode = PLMN_MODE_AUTO; gsm322_a_switch_on(ms, msg); - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_USER_PLMN_SEL); - if (!nmsg) - return -ENOMEM; - gsm48_mmevent_msg(ms, nmsg); + gsm48_mmevent_input(ms, GSM48_MM_EVENT_USER_PLMN_SEL, NULL, 0); return 0; } @@ -2684,14 +2674,8 @@ static int gsm322_c_any_cell_sel(struct osmocom_ms *ms, struct msgb *msg) /* after re-selection, indicate no cell found */ if (cs->state == GSM322_C6_ANY_CELL_SEL || cs->state == GSM322_C8_ANY_CELL_RESEL) { - struct msgb *nmsg; - /* tell that we have no cell found */ - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_NO_CELL_FOUND); - if (!nmsg) - return -ENOMEM; - gsm48_mmevent_msg(ms, nmsg); - + gsm48_mmevent_input(ms, GSM48_MM_EVENT_NO_CELL_FOUND, NULL, 0); } else { new_c_state(cs, GSM322_C6_ANY_CELL_SEL); } @@ -2737,7 +2721,6 @@ static int gsm322_c_any_cell_resel(struct osmocom_ms *ms, struct msgb *msg) static int gsm322_c_camp_normally(struct osmocom_ms *ms, struct msgb *msg) { struct gsm322_cellsel *cs = &ms->cellsel; - struct msgb *nmsg; LOGP(DSUM, LOGL_INFO, "Camping normally on cell (arfcn=%d mcc=%s " "mnc=%s %s, %s)\n", cs->sel_arfcn, gsm_print_mcc(cs->sel_mcc), @@ -2745,10 +2728,7 @@ static int gsm322_c_camp_normally(struct osmocom_ms *ms, struct msgb *msg) gsm_get_mnc(cs->sel_mcc, cs->sel_mnc)); /* tell that we have selected a (new) cell */ - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_CELL_SELECTED); - if (!nmsg) - return -ENOMEM; - gsm48_mmevent_msg(ms, nmsg); + gsm48_mmevent_input(ms, GSM48_MM_EVENT_CELL_SELECTED, NULL, 0); new_c_state(cs, GSM322_C3_CAMPED_NORMALLY); @@ -2759,7 +2739,6 @@ static int gsm322_c_camp_normally(struct osmocom_ms *ms, struct msgb *msg) static int gsm322_c_camp_any_cell(struct osmocom_ms *ms, struct msgb *msg) { struct gsm322_cellsel *cs = &ms->cellsel; - struct msgb *nmsg; LOGP(DSUM, LOGL_INFO, "Camping on any cell (arfcn=%d mcc=%s " "mnc=%s %s, %s)\n", cs->sel_arfcn, gsm_print_mcc(cs->sel_mcc), @@ -2768,10 +2747,7 @@ static int gsm322_c_camp_any_cell(struct osmocom_ms *ms, struct msgb *msg) /* tell that we have selected a (new) cell */ - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_CELL_SELECTED); - if (!nmsg) - return -ENOMEM; - gsm48_mmevent_msg(ms, nmsg); + gsm48_mmevent_input(ms, GSM48_MM_EVENT_CELL_SELECTED, NULL, 0); new_c_state(cs, GSM322_C7_CAMPED_ANY_CELL); @@ -2878,8 +2854,6 @@ static int gsm322_c_choose_cell(struct osmocom_ms *ms, struct msgb *msg) /* After location updating, we choose the last cell */ if (gm->same_cell) { - struct msgb *nmsg; - if (!cs->selected) { printf("No cell selected when ret.idle, please fix!\n"); exit(0L); @@ -2896,10 +2870,7 @@ static int gsm322_c_choose_cell(struct osmocom_ms *ms, struct msgb *msg) new_c_state(cs, GSM322_C3_CAMPED_NORMALLY); /* tell that we have selected the cell, so RR returns IDLE */ - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_CELL_SELECTED); - if (!nmsg) - return -ENOMEM; - gsm48_mmevent_msg(ms, nmsg); + gsm48_mmevent_input(ms, GSM48_MM_EVENT_CELL_SELECTED, NULL, 0); return 0; } diff --git a/src/host/layer23/src/mobile/gsm48_mm.c b/src/host/layer23/src/mobile/gsm48_mm.c index 4652f34..6400373 100644 --- a/src/host/layer23/src/mobile/gsm48_mm.c +++ b/src/host/layer23/src/mobile/gsm48_mm.c @@ -658,7 +658,7 @@ struct msgb *gsm48_mmxx_msgb_alloc(int msg_type, uint32_t ref, } /* allocate MM event message */ -struct msgb *gsm48_mmevent_msgb_alloc(int msg_type) +static struct msgb *gsm48_mmevent_msgb_alloc(int msg_type) { struct msgb *msg; struct gsm48_mm_event *mme; @@ -710,7 +710,7 @@ int gsm48_mmr_downmsg(struct osmocom_ms *ms, struct msgb *msg) } /* queue MM event message */ -int gsm48_mmevent_msg(struct osmocom_ms *ms, struct msgb *msg) +static int gsm48_mmevent_msg(struct osmocom_ms *ms, struct msgb *msg) { struct gsm48_mmlayer *mm = &ms->mmlayer; @@ -905,14 +905,10 @@ static void new_mm_state(struct gsm48_mmlayer *mm, int state, int substate) /* resend detach event, if flag is set */ if (state == GSM48_MM_ST_MM_IDLE && mm->delay_detach) { - struct msgb *nmsg; - mm->delay_detach = 0; - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_IMSI_DETACH); - if (!nmsg) - return; - gsm48_mmevent_msg(mm->ms, nmsg); + gsm48_mmevent_input(mm->ms, GSM48_MM_EVENT_IMSI_DETACH, + NULL, 0); } /* 4.4.2 start T3212 in MM IDLE mode if not started or has expired */ @@ -2431,7 +2427,8 @@ static int gsm48_mm_rel_loc_upd_rej(struct osmocom_ms *ms, struct msgb *msg) } memset(&ngm, 0, sizeof(ngm)); ngm.reject = mm->lupd_rej_cause; - gsm322_event_input(ms, GSM322_EVT_PLMN, msg_type, &ngm, sizeof(ngm)); + gsm322_event_input(ms, GSM322_EVT_PLMN, msg_type, + (uint8_t *)&ngm, sizeof(ngm)); /* forbidden list */ switch (mm->lupd_rej_cause) { @@ -4088,13 +4085,7 @@ static int gsm48_mmr_reg_req(struct osmocom_ms *ms) /* trigger detach of sim card */ static int gsm48_mmr_nreg_req(struct osmocom_ms *ms) { - struct gsm48_mmlayer *mm = &ms->mmlayer; - struct msgb *nmsg; - - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_IMSI_DETACH); - if (!nmsg) - return -ENOMEM; - gsm48_mmevent_msg(mm->ms, nmsg); + gsm48_mmevent_input(ms, GSM48_MM_EVENT_IMSI_DETACH, NULL, 0); return 0; } @@ -4121,4 +4112,22 @@ static int gsm48_rcv_mmr(struct osmocom_ms *ms, struct msgb *msg) return rc; } +int gsm48_mmevent_input(struct osmocom_ms *ms, int msg_type, + const uint8_t *data, unsigned int len) +{ + struct msgb *nmsg = gsm48_mmevent_msgb_alloc(msg_type); + int rc; + + if (!nmsg) + return -ENOMEM; + if (data && len) { + uint8_t *cur = msgb_push(nmsg, len); + if (!cur) { + msgb_free(nmsg); + return -EIO; + } + memcpy(cur, data, len); + } + return gsm48_mmevent_msg(ms, nmsg); +} diff --git a/src/host/layer23/src/mobile/gsm48_rr.c b/src/host/layer23/src/mobile/gsm48_rr.c index 177b272..afb53cb 100644 --- a/src/host/layer23/src/mobile/gsm48_rr.c +++ b/src/host/layer23/src/mobile/gsm48_rr.c @@ -1560,7 +1560,6 @@ fail: static int gsm48_new_sysinfo(struct osmocom_ms *ms, uint8_t type) { struct gsm48_sysinfo *s = ms->cellsel.si; - struct msgb *nmsg; struct gsm322_msg em; /* update list of measurements, if BA(SACCH) is complete and new */ @@ -1600,10 +1599,7 @@ static int gsm48_new_sysinfo(struct osmocom_ms *ms, uint8_t type) (uint8_t *)&em, sizeof(em)); /* send timer info to location update process */ - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_SYSINFO); - if (!nmsg) - return -ENOMEM; - gsm48_mmevent_msg(ms, nmsg); + gsm48_mmevent_input(ms, GSM48_MM_EVENT_SYSINFO, NULL, 0); return 0; } diff --git a/src/host/layer23/src/mobile/subscriber.c b/src/host/layer23/src/mobile/subscriber.c index 3ba78f3..24d7f94 100644 --- a/src/host/layer23/src/mobile/subscriber.c +++ b/src/host/layer23/src/mobile/subscriber.c @@ -855,25 +855,16 @@ int gsm_subscr_generate_kc(struct osmocom_ms *ms, uint8_t key_seq, if ((subscr->sim_type != GSM_SIM_TYPE_READER && subscr->sim_type != GSM_SIM_TYPE_TEST) || !subscr->sim_valid || no_sim) { - struct gsm48_mm_event *nmme; + uint8_t dummy_sres[4] = { 0x12, 0x34, 0x56, 0x78 }; LOGP(DMM, LOGL_INFO, "Sending dummy authentication response\n"); - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_AUTH_RESPONSE); - if (!nmsg) - return -ENOMEM; - nmme = (struct gsm48_mm_event *) nmsg->data; - nmme->sres[0] = 0x12; - nmme->sres[1] = 0x34; - nmme->sres[2] = 0x56; - nmme->sres[3] = 0x78; - gsm48_mmevent_msg(ms, nmsg); - + gsm48_mmevent_input(ms, GSM48_MM_EVENT_AUTH_RESPONSE, + dummy_sres, sizeof(dummy_sres)); return 0; } /* test SIM */ if (subscr->sim_type == GSM_SIM_TYPE_TEST) { - struct gsm48_mm_event *nmme; uint8_t sres[4]; struct gsm_settings *set = &ms->settings; @@ -885,12 +876,8 @@ int gsm_subscr_generate_kc(struct osmocom_ms *ms, uint8_t key_seq, subscr->key_seq = key_seq; LOGP(DMM, LOGL_INFO, "Sending authentication response\n"); - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_AUTH_RESPONSE); - if (!nmsg) - return -ENOMEM; - nmme = (struct gsm48_mm_event *) nmsg->data; - memcpy(nmme->sres, sres, 4); - gsm48_mmevent_msg(ms, nmsg); + gsm48_mmevent_input(ms, GSM48_MM_EVENT_AUTH_RESPONSE, + sres, sizeof(sres)); return 0; } @@ -924,7 +911,6 @@ static void subscr_sim_key_cb(struct osmocom_ms *ms, struct msgb *msg) uint16_t payload_len = msg->len - sizeof(*sh); struct msgb *nmsg; struct sim_hdr *nsh; - struct gsm48_mm_event *nmme; uint8_t *data; /* error handling */ @@ -961,12 +947,7 @@ static void subscr_sim_key_cb(struct osmocom_ms *ms, struct msgb *msg) sim_job(ms, nmsg); /* return signed response */ - nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_AUTH_RESPONSE); - if (!nmsg) - return; - nmme = (struct gsm48_mm_event *) nmsg->data; - memcpy(nmme->sres, payload, 4); - gsm48_mmevent_msg(ms, nmsg); + gsm48_mmevent_input(ms, GSM48_MM_EVENT_AUTH_RESPONSE, payload, 4); msgb_free(msg); } -- 1.7.2.3 --Kj7319i9nmIyA2yE--

1 0

[PATCH 2/3] [mobile] replace 3 different gsm322_makesend_* functions with one
by Harald Welte 30 Jan '11

30 Jan '11

The new function is gsm322_event_input() and uses the event type as a function argument. --- .../layer23/include/osmocom/bb/mobile/gsm322.h | 12 +++- src/host/layer23/src/mobile/app_mobile.c | 8 ++-- src/host/layer23/src/mobile/gsm322.c | 56 +++++--------------- src/host/layer23/src/mobile/gsm48_mm.c | 34 +++++++----- src/host/layer23/src/mobile/gsm48_rr.c | 9 ++-- src/host/layer23/src/mobile/vty_interface.c | 9 ++-- 6 files changed, 57 insertions(+), 71 deletions(-) diff --git a/src/host/layer23/include/osmocom/bb/mobile/gsm322.h b/src/host/layer23/include/osmocom/bb/mobile/gsm322.h index 3cd275f..30d96ee 100644 --- a/src/host/layer23/include/osmocom/bb/mobile/gsm322.h +++ b/src/host/layer23/include/osmocom/bb/mobile/gsm322.h @@ -32,6 +32,13 @@ #define GSM322_PLMN_SEARCH 10 #define GSM322_HPLMN_SEARCH 11 +/* GSM 03.22 event types */ +enum gsm322_evt_type { + GSM322_EVT_C, /* direct cell event, no queue */ + GSM322_EVT_CS, /* enqueue cs->event_queue */ + GSM322_EVT_PLMN, /* enqueue plmn->event_queue */ +}; + /* GSM 03.22 events */ #define GSM322_EVENT_SWITCH_ON 1 #define GSM322_EVENT_SWITCH_OFF 2 @@ -172,9 +179,8 @@ struct gsm322_msg { int gsm322_init(struct osmocom_ms *ms); int gsm322_exit(struct osmocom_ms *ms); -int gsm322_makesend_plmn_msg(struct osmocom_ms *ms, int msg_type, uint8_t *data, unsigned int len); -int gsm322_makesend_cs_event(struct osmocom_ms *ms, int msg_type, uint8_t *data, unsigned int len); -int gsm322_makesend_c_event(struct osmocom_ms *ms, int msg_type, uint8_t *data, unsigned int len); +int gsm322_event_input(struct osmocom_ms *ms, enum gsm322_evt_type type, + int msg_type, uint8_t *data, unsigned int len); int gsm322_plmn_dequeue(struct osmocom_ms *ms); int gsm322_cs_dequeue(struct osmocom_ms *ms); int gsm322_add_forbidden_la(struct osmocom_ms *ms, uint16_t mcc, diff --git a/src/host/layer23/src/mobile/app_mobile.c b/src/host/layer23/src/mobile/app_mobile.c index 3d2100c..b3c3284 100644 --- a/src/host/layer23/src/mobile/app_mobile.c +++ b/src/host/layer23/src/mobile/app_mobile.c @@ -104,10 +104,10 @@ int mobile_signal_cb(unsigned int subsys, unsigned int signal, break; default: /* no SIM, trigger PLMN selection process */ - gsm322_makesend_plmn_msg(ms, GSM322_EVENT_SWITCH_ON, - NULL, 0); - gsm322_makesend_cs_event(ms, GSM322_EVENT_SWITCH_ON, - NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, + GSM322_EVENT_SWITCH_ON, NULL, 0); + gsm322_event_input(ms, GSM322_EVT_CS, + GSM322_EVENT_SWITCH_ON, NULL, 0); } ms->started = 1; diff --git a/src/host/layer23/src/mobile/gsm322.c b/src/host/layer23/src/mobile/gsm322.c index 1429737..3243afc 100644 --- a/src/host/layer23/src/mobile/gsm322.c +++ b/src/host/layer23/src/mobile/gsm322.c @@ -3604,8 +3604,8 @@ int gsm322_exit(struct osmocom_ms *ms) return 0; } -int gsm322_makesend_c_event(struct osmocom_ms *ms, int msg_type, - uint8_t *data, unsigned int len) +int gsm322_event_input(struct osmocom_ms *ms, enum gsm322_evt_type type, + int msg_type, uint8_t *data, unsigned int len) { struct msgb *nmsg = gsm322_msgb_alloc(msg_type); int rc; @@ -3621,46 +3621,18 @@ int gsm322_makesend_c_event(struct osmocom_ms *ms, int msg_type, } memcpy(cur, data, len); } - rc = gsm322_c_event(ms, nmsg); - msgb_free(nmsg); - - return rc; -} - -int gsm322_makesend_cs_event(struct osmocom_ms *ms, int msg_type, - uint8_t *data, unsigned int len) -{ - struct msgb *nmsg = gsm322_msgb_alloc(msg_type); - - if (!nmsg) - return -ENOMEM; - - if (data && len) { - uint8_t *cur = msgb_push(nmsg, len); - if (!cur) { - msgb_free(nmsg); - return -EIO; - } - memcpy(cur, data, len); + switch (type) { + case GSM322_EVT_C: + rc = gsm322_c_event(ms, nmsg); + msgb_free(nmsg); + break; + case GSM322_EVT_CS: + rc = gsm322_cs_sendmsg(ms, nmsg); + break; + case GSM322_EVT_PLMN: + rc = gsm322_plmn_sendmsg(ms, nmsg); + break; } - return gsm322_cs_sendmsg(ms, nmsg); -} - -int gsm322_makesend_plmn_msg(struct osmocom_ms *ms, int msg_type, - uint8_t *data, unsigned int len) -{ - struct msgb *nmsg = gsm322_msgb_alloc(msg_type); - - if (!nmsg) - return -ENOMEM; - if (data && len) { - uint8_t *cur = msgb_push(nmsg, len); - if (!cur) { - msgb_free(nmsg); - return -EIO; - } - memcpy(cur, data, len); - } - return gsm322_plmn_sendmsg(ms, nmsg); + return rc; } diff --git a/src/host/layer23/src/mobile/gsm48_mm.c b/src/host/layer23/src/mobile/gsm48_mm.c index 58253bd..4652f34 100644 --- a/src/host/layer23/src/mobile/gsm48_mm.c +++ b/src/host/layer23/src/mobile/gsm48_mm.c @@ -1123,8 +1123,8 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg) GSM48_MM_SST_NORMAL_SERVICE); /* send message to PLMN search process */ - gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS, - NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, + GSM322_EVENT_REG_SUCCESS, NULL, 0); return 0; } if (!s->att_allowed) { @@ -1133,8 +1133,8 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg) GSM48_MM_SST_NORMAL_SERVICE); /* send message to PLMN search process */ - gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS, - NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, + GSM322_EVENT_REG_SUCCESS, NULL, 0); return 0; } /* else, continue */ @@ -1150,8 +1150,8 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg) GSM48_MM_SST_LIMITED_SERVICE); /* send message to PLMN search process */ - gsm322_makesend_plmn_msg(ms, GSM322_EVENT_ROAMING_NA, - NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, + GSM322_EVENT_ROAMING_NA, NULL, 0); return 0; } @@ -1165,7 +1165,8 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg) GSM48_MM_SST_LIMITED_SERVICE); /* send message to PLMN search process */ - gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_FAILED, NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, + GSM322_EVENT_REG_FAILED, NULL, 0); return 0; } @@ -1733,7 +1734,8 @@ static int gsm48_mm_imsi_detach_end(struct osmocom_ms *ms, struct msgb *msg) } /* send SIM remove event to gsm322 */ - gsm322_makesend_plmn_msg(ms, GSM322_EVENT_SIM_REMOVE, NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, + GSM322_EVENT_SIM_REMOVE, NULL, 0); /* CS process will trigger return to MM IDLE / No SIM */ return 0; @@ -1993,7 +1995,7 @@ static int gsm48_mm_loc_upd(struct osmocom_ms *ms, struct msgb *msg) _stop: mm->lupd_pending = 0; /* send message to PLMN search process */ - gsm322_makesend_plmn_msg(ms, msg_type, NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, msg_type, NULL, 0); return 0; } @@ -2062,7 +2064,8 @@ static int gsm48_mm_loc_upd_normal(struct osmocom_ms *ms, struct msgb *msg) LOGP(DMM, LOGL_INFO, "Loc. upd. not allowed.\n"); /* send message to PLMN search process */ - gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_FAILED, NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, + GSM322_EVENT_REG_FAILED, NULL, 0); return 0; } @@ -2083,7 +2086,8 @@ static int gsm48_mm_loc_upd_normal(struct osmocom_ms *ms, struct msgb *msg) GSM48_MM_SST_NORMAL_SERVICE); /* send message to PLMN search process */ - gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS, NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, + GSM322_EVENT_REG_SUCCESS, NULL, 0); return 0; } @@ -2318,7 +2322,8 @@ static int gsm48_mm_rx_loc_upd_acc(struct osmocom_ms *ms, struct msgb *msg) } /* send message to PLMN search process */ - gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS, NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, + GSM322_EVENT_REG_SUCCESS, NULL, 0); /* follow on proceed */ if (TLVP_PRESENT(&tp, GSM48_IE_MOBILE_ID)) @@ -2426,7 +2431,7 @@ static int gsm48_mm_rel_loc_upd_rej(struct osmocom_ms *ms, struct msgb *msg) } memset(&ngm, 0, sizeof(ngm)); ngm.reject = mm->lupd_rej_cause; - gsm322_makesend_plmn_msg(ms, msg_type, NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, msg_type, &ngm, sizeof(ngm)); /* forbidden list */ switch (mm->lupd_rej_cause) { @@ -4068,7 +4073,8 @@ static int gsm48_mmr_reg_req(struct osmocom_ms *ms) struct gsm48_mmlayer *mm = &ms->mmlayer; /* schedule insertion of SIM */ - gsm322_makesend_plmn_msg(ms, GSM322_EVENT_SIM_INSERT, NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, + GSM322_EVENT_SIM_INSERT, NULL, 0); /* 4.2.1.2 SIM is inserted in state NO IMSI */ if (mm->state == GSM48_MM_ST_MM_IDLE diff --git a/src/host/layer23/src/mobile/gsm48_rr.c b/src/host/layer23/src/mobile/gsm48_rr.c index 4a48dc8..177b272 100644 --- a/src/host/layer23/src/mobile/gsm48_rr.c +++ b/src/host/layer23/src/mobile/gsm48_rr.c @@ -408,8 +408,8 @@ static void new_rr_state(struct gsm48_rrlayer *rr, int state) memset(&em, 0, sizeof(em)); em.same_cell = 1; } - gsm322_makesend_c_event(rr->ms, GSM322_EVENT_RET_IDLE, - (uint8_t *)&em, sizeof(em)); + gsm322_event_input(rr->ms, GSM322_EVT_C, GSM322_EVENT_RET_IDLE, + (uint8_t *)&em, sizeof(em)); /* reset any BA range */ rr->ba_ranges = 0; } @@ -1189,7 +1189,8 @@ static int gsm48_rr_chan_req(struct osmocom_ms *ms, int cause, int paging) * NOTE: this must be sent unbuffered, because the state may not * change until idle mode is left */ - rc = gsm322_makesend_c_event(ms, GSM322_EVENT_LEAVE_IDLE, NULL, 0); + rc = gsm322_event_input(ms, GSM322_EVT_C, GSM322_EVENT_LEAVE_IDLE, + NULL, 0); if (rc) { if (paging) return rc; @@ -1595,7 +1596,7 @@ static int gsm48_new_sysinfo(struct osmocom_ms *ms, uint8_t type) /* send sysinfo event to other layers */ memset(&em, 0, sizeof(em)); em.sysinfo = type; - gsm322_makesend_cs_event(ms, GSM322_EVENT_SYSINFO, + gsm322_event_input(ms, GSM322_EVT_CS, GSM322_EVENT_SYSINFO, (uint8_t *)&em, sizeof(em)); /* send timer info to location update process */ diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c index e3e7c47..d83dae8 100644 --- a/src/host/layer23/src/mobile/vty_interface.c +++ b/src/host/layer23/src/mobile/vty_interface.c @@ -689,8 +689,8 @@ DEFUN(network_select, network_select_cmd, "network select MS_NAME MCC MNC", memset(&ngm, 0, sizeof(ngm)); ngm.mcc = mcc; ngm.mnc = mnc; - gsm322_makesend_plmn_msg(ms, GSM322_EVENT_CHOOSE_PLMN, - (uint8_t *)&ngm, sizeof(ngm)); + gsm322_event_input(ms, GSM322_EVT_PLMN, GSM322_EVENT_CHOOSE_PLMN, + (uint8_t *)&ngm, sizeof(ngm)); return CMD_SUCCESS; } @@ -820,7 +820,8 @@ DEFUN(network_search, network_search_cmd, "network search MS_NAME", if (!ms) return CMD_WARNING; - gsm322_makesend_plmn_msg(ms, GSM322_EVENT_USER_RESEL, NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, + GSM322_EVENT_USER_RESEL, NULL, 0); return CMD_SUCCESS; } @@ -1265,7 +1266,7 @@ DEFUN(cfg_ms_mode, cfg_ms_mode_cmd, "network-selection-mode (auto|manual)", msg_type = GSM322_EVENT_SEL_MANUAL; if (msg_type < 0) return CMD_WARNING; - gsm322_makesend_plmn_msg(ms, msg_type, NULL, 0); + gsm322_event_input(ms, GSM322_EVT_PLMN, msg_type, NULL, 0); return CMD_SUCCESS; } -- 1.7.2.3 --Kj7319i9nmIyA2yE Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0003-mobile-introduce-and-use-gsm48_mmevevent_input.patch"

1 0

[PATCH 1/3] [mobile] simplify code to send events into GSM 3.22 code
by Harald Welte 30 Jan '11

30 Jan '11

instead of gsm322_msgb_alloc() followed by a sendmsg with intermittent error checks we now have only a single function call. --- .../layer23/include/osmocom/bb/mobile/gsm322.h | 7 +- src/host/layer23/src/mobile/app_mobile.c | 13 +-- src/host/layer23/src/mobile/gsm322.c | 69 ++++++++++++++- src/host/layer23/src/mobile/gsm48_mm.c | 88 +++++--------------- src/host/layer23/src/mobile/gsm48_rr.c | 33 +++----- src/host/layer23/src/mobile/vty_interface.c | 31 +++---- 6 files changed, 118 insertions(+), 123 deletions(-) diff --git a/src/host/layer23/include/osmocom/bb/mobile/gsm322.h b/src/host/layer23/include/osmocom/bb/mobile/gsm322.h index 467ff39..3cd275f 100644 --- a/src/host/layer23/include/osmocom/bb/mobile/gsm322.h +++ b/src/host/layer23/include/osmocom/bb/mobile/gsm322.h @@ -172,10 +172,9 @@ struct gsm322_msg { int gsm322_init(struct osmocom_ms *ms); int gsm322_exit(struct osmocom_ms *ms); -struct msgb *gsm322_msgb_alloc(int msg_type); -int gsm322_plmn_sendmsg(struct osmocom_ms *ms, struct msgb *msg); -int gsm322_cs_sendmsg(struct osmocom_ms *ms, struct msgb *msg); -int gsm322_c_event(struct osmocom_ms *ms, struct msgb *msg); +int gsm322_makesend_plmn_msg(struct osmocom_ms *ms, int msg_type, uint8_t *data, unsigned int len); +int gsm322_makesend_cs_event(struct osmocom_ms *ms, int msg_type, uint8_t *data, unsigned int len); +int gsm322_makesend_c_event(struct osmocom_ms *ms, int msg_type, uint8_t *data, unsigned int len); int gsm322_plmn_dequeue(struct osmocom_ms *ms); int gsm322_cs_dequeue(struct osmocom_ms *ms); int gsm322_add_forbidden_la(struct osmocom_ms *ms, uint16_t mcc, diff --git a/src/host/layer23/src/mobile/app_mobile.c b/src/host/layer23/src/mobile/app_mobile.c index 822ea64..3d2100c 100644 --- a/src/host/layer23/src/mobile/app_mobile.c +++ b/src/host/layer23/src/mobile/app_mobile.c @@ -79,7 +79,6 @@ int mobile_signal_cb(unsigned int subsys, unsigned int signal, { struct osmocom_ms *ms; struct gsm_settings *set; - struct msgb *nmsg; if (subsys != SS_L1CTL) return 0; @@ -105,14 +104,10 @@ int mobile_signal_cb(unsigned int subsys, unsigned int signal, break; default: /* no SIM, trigger PLMN selection process */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_SWITCH_ON); - if (!nmsg) - return -ENOMEM; - gsm322_plmn_sendmsg(ms, nmsg); - nmsg = gsm322_msgb_alloc(GSM322_EVENT_SWITCH_ON); - if (!nmsg) - return -ENOMEM; - gsm322_cs_sendmsg(ms, nmsg); + gsm322_makesend_plmn_msg(ms, GSM322_EVENT_SWITCH_ON, + NULL, 0); + gsm322_makesend_cs_event(ms, GSM322_EVENT_SWITCH_ON, + NULL, 0); } ms->started = 1; diff --git a/src/host/layer23/src/mobile/gsm322.c b/src/host/layer23/src/mobile/gsm322.c index 3c920e4..1429737 100644 --- a/src/host/layer23/src/mobile/gsm322.c +++ b/src/host/layer23/src/mobile/gsm322.c @@ -45,6 +45,8 @@ static void gsm322_cs_loss(void *arg); static int gsm322_cs_select(struct osmocom_ms *ms, int any, int plmn_allowed); static int gsm322_m_switch_on(struct osmocom_ms *ms, struct msgb *msg); +static int gsm322_c_event(struct osmocom_ms *ms, struct msgb *msg); + #define SKIP_MAX_PER_BAND #warning HACKING!!! @@ -182,7 +184,7 @@ const char *get_event_name(int value) /* allocate a 03.22 event message */ -struct msgb *gsm322_msgb_alloc(int msg_type) +static struct msgb *gsm322_msgb_alloc(int msg_type) { struct msgb *msg; struct gsm322_msg *gm; @@ -198,7 +200,7 @@ struct msgb *gsm322_msgb_alloc(int msg_type) } /* queue PLMN selection message */ -int gsm322_plmn_sendmsg(struct osmocom_ms *ms, struct msgb *msg) +static int gsm322_plmn_sendmsg(struct osmocom_ms *ms, struct msgb *msg) { struct gsm322_plmn *plmn = &ms->plmn; @@ -208,7 +210,7 @@ int gsm322_plmn_sendmsg(struct osmocom_ms *ms, struct msgb *msg) } /* queue cell selection message */ -int gsm322_cs_sendmsg(struct osmocom_ms *ms, struct msgb *msg) +static int gsm322_cs_sendmsg(struct osmocom_ms *ms, struct msgb *msg) { struct gsm322_cellsel *cs = &ms->cellsel; @@ -3304,7 +3306,7 @@ static struct cellselstatelist { #define CELLSELSLLEN \ (sizeof(cellselstatelist) / sizeof(struct cellselstatelist)) -int gsm322_c_event(struct osmocom_ms *ms, struct msgb *msg) +static int gsm322_c_event(struct osmocom_ms *ms, struct msgb *msg) { struct gsm322_cellsel *cs = &ms->cellsel; struct gsm322_msg *gm = (struct gsm322_msg *) msg->data; @@ -3602,4 +3604,63 @@ int gsm322_exit(struct osmocom_ms *ms) return 0; } +int gsm322_makesend_c_event(struct osmocom_ms *ms, int msg_type, + uint8_t *data, unsigned int len) +{ + struct msgb *nmsg = gsm322_msgb_alloc(msg_type); + int rc; + if (!nmsg) + return -ENOMEM; + + if (data && len) { + uint8_t *cur = msgb_push(nmsg, len); + if (!cur) { + msgb_free(nmsg); + return -EIO; + } + memcpy(cur, data, len); + } + rc = gsm322_c_event(ms, nmsg); + msgb_free(nmsg); + + return rc; +} + +int gsm322_makesend_cs_event(struct osmocom_ms *ms, int msg_type, + uint8_t *data, unsigned int len) +{ + struct msgb *nmsg = gsm322_msgb_alloc(msg_type); + + if (!nmsg) + return -ENOMEM; + + if (data && len) { + uint8_t *cur = msgb_push(nmsg, len); + if (!cur) { + msgb_free(nmsg); + return -EIO; + } + memcpy(cur, data, len); + } + return gsm322_cs_sendmsg(ms, nmsg); +} + +int gsm322_makesend_plmn_msg(struct osmocom_ms *ms, int msg_type, + uint8_t *data, unsigned int len) +{ + struct msgb *nmsg = gsm322_msgb_alloc(msg_type); + + if (!nmsg) + return -ENOMEM; + + if (data && len) { + uint8_t *cur = msgb_push(nmsg, len); + if (!cur) { + msgb_free(nmsg); + return -EIO; + } + memcpy(cur, data, len); + } + return gsm322_plmn_sendmsg(ms, nmsg); +} diff --git a/src/host/layer23/src/mobile/gsm48_mm.c b/src/host/layer23/src/mobile/gsm48_mm.c index 15bbd27..58253bd 100644 --- a/src/host/layer23/src/mobile/gsm48_mm.c +++ b/src/host/layer23/src/mobile/gsm48_mm.c @@ -1118,33 +1118,23 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg) && cs->sel_lac == subscr->lac && !mm->lupd_periodic) { if (subscr->imsi_attached) { - struct msgb *nmsg; - LOGP(DMM, LOGL_INFO, "Valid in location area.\n"); new_mm_state(mm, GSM48_MM_ST_MM_IDLE, GSM48_MM_SST_NORMAL_SERVICE); /* send message to PLMN search process */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_SUCCESS); - if (!nmsg) - return -ENOMEM; - gsm322_plmn_sendmsg(ms, nmsg); - + gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS, + NULL, 0); return 0; } if (!s->att_allowed) { - struct msgb *nmsg; - LOGP(DMM, LOGL_INFO, "Attachment not required.\n"); new_mm_state(mm, GSM48_MM_ST_MM_IDLE, GSM48_MM_SST_NORMAL_SERVICE); /* send message to PLMN search process */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_SUCCESS); - if (!nmsg) - return -ENOMEM; - gsm322_plmn_sendmsg(ms, nmsg); - + gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS, + NULL, 0); return 0; } /* else, continue */ @@ -1155,17 +1145,13 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg) && (gsm_subscr_is_forbidden_plmn(subscr, cs->sel_mcc, cs->sel_mnc) || gsm322_is_forbidden_la(ms, cs->sel_mcc, cs->sel_mnc, cs->sel_lac))) { - struct msgb *nmsg; - LOGP(DMM, LOGL_INFO, "Selected cell is forbidden.\n"); new_mm_state(mm, GSM48_MM_ST_MM_IDLE, GSM48_MM_SST_LIMITED_SERVICE); /* send message to PLMN search process */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_ROAMING_NA); - if (!nmsg) - return -ENOMEM; - gsm322_plmn_sendmsg(ms, nmsg); + gsm322_makesend_plmn_msg(ms, GSM322_EVENT_ROAMING_NA, + NULL, 0); return 0; } @@ -1174,17 +1160,12 @@ static int gsm48_mm_cell_selected(struct osmocom_ms *ms, struct msgb *msg) if (set->plmn_mode == PLMN_MODE_MANUAL && (plmn->mcc != cs->sel_mcc || plmn->mnc != cs->sel_mnc)) { - struct msgb *nmsg; - LOGP(DMM, LOGL_INFO, "Selected cell not found.\n"); new_mm_state(mm, GSM48_MM_ST_MM_IDLE, GSM48_MM_SST_LIMITED_SERVICE); /* send message to PLMN search process */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_FAILED); - if (!nmsg) - return -ENOMEM; - gsm322_plmn_sendmsg(ms, nmsg); + gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_FAILED, NULL, 0); return 0; } @@ -1729,7 +1710,6 @@ static int gsm48_mm_imsi_detach_end(struct osmocom_ms *ms, struct msgb *msg) { struct gsm48_mmlayer *mm = &ms->mmlayer; struct gsm_subscriber *subscr = &ms->subscr; - struct msgb *nmsg; LOGP(DMM, LOGL_INFO, "IMSI has been detached.\n"); @@ -1753,10 +1733,7 @@ static int gsm48_mm_imsi_detach_end(struct osmocom_ms *ms, struct msgb *msg) } /* send SIM remove event to gsm322 */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_SIM_REMOVE); - if (!nmsg) - return -ENOMEM; - gsm322_plmn_sendmsg(ms, nmsg); + gsm322_makesend_plmn_msg(ms, GSM322_EVENT_SIM_REMOVE, NULL, 0); /* CS process will trigger return to MM IDLE / No SIM */ return 0; @@ -1999,7 +1976,6 @@ static int gsm48_mm_loc_upd(struct osmocom_ms *ms, struct msgb *msg) struct gsm48_sysinfo *s = &cs->sel_si; struct gsm_subscriber *subscr = &ms->subscr; struct gsm_settings *set = &ms->settings; - struct msgb *nmsg; int msg_type; /* (re)start only if we still require location update */ @@ -2017,10 +1993,7 @@ static int gsm48_mm_loc_upd(struct osmocom_ms *ms, struct msgb *msg) _stop: mm->lupd_pending = 0; /* send message to PLMN search process */ - nmsg = gsm322_msgb_alloc(msg_type); - if (!nmsg) - return -ENOMEM; - gsm322_plmn_sendmsg(ms, nmsg); + gsm322_makesend_plmn_msg(ms, msg_type, NULL, 0); return 0; } @@ -2076,7 +2049,6 @@ static int gsm48_mm_loc_upd_normal(struct osmocom_ms *ms, struct msgb *msg) struct gsm_subscriber *subscr = &ms->subscr; struct gsm322_cellsel *cs = &ms->cellsel; struct gsm48_sysinfo *s = &cs->sel_si; - struct msgb *nmsg; /* in case we already have a location update going on */ if (mm->lupd_pending) { @@ -2090,10 +2062,7 @@ static int gsm48_mm_loc_upd_normal(struct osmocom_ms *ms, struct msgb *msg) LOGP(DMM, LOGL_INFO, "Loc. upd. not allowed.\n"); /* send message to PLMN search process */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_FAILED); - if (!nmsg) - return -ENOMEM; - gsm322_plmn_sendmsg(ms, nmsg); + gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_FAILED, NULL, 0); return 0; } @@ -2114,10 +2083,7 @@ static int gsm48_mm_loc_upd_normal(struct osmocom_ms *ms, struct msgb *msg) GSM48_MM_SST_NORMAL_SERVICE); /* send message to PLMN search process */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_SUCCESS); - if (!nmsg) - return -ENOMEM; - gsm322_plmn_sendmsg(ms, nmsg); + gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS, NULL, 0); return 0; } @@ -2256,7 +2222,6 @@ static int gsm48_mm_rx_loc_upd_acc(struct osmocom_ms *ms, struct msgb *msg) struct gsm48_loc_area_id *lai = (struct gsm48_loc_area_id *) gh->data; unsigned int payload_len = msgb_l3len(msg) - sizeof(*gh); struct tlv_parsed tp; - struct msgb *nmsg; if (payload_len < sizeof(struct gsm48_loc_area_id)) { short_read: @@ -2353,10 +2318,7 @@ static int gsm48_mm_rx_loc_upd_acc(struct osmocom_ms *ms, struct msgb *msg) } /* send message to PLMN search process */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_SUCCESS); - if (!nmsg) - return -ENOMEM; - gsm322_plmn_sendmsg(ms, nmsg); + gsm322_makesend_plmn_msg(ms, GSM322_EVENT_REG_SUCCESS, NULL, 0); /* follow on proceed */ if (TLVP_PRESENT(&tp, GSM48_IE_MOBILE_ID)) @@ -2408,8 +2370,8 @@ static int gsm48_mm_rel_loc_upd_rej(struct osmocom_ms *ms, struct msgb *msg) { struct gsm48_mmlayer *mm = &ms->mmlayer; struct gsm_subscriber *subscr = &ms->subscr; - struct msgb *nmsg; - struct gsm322_msg *ngm; + struct gsm322_msg ngm; + int msg_type; LOGP(DMM, LOGL_INFO, "Loc. upd. rejected (cause %d)\n", mm->lupd_rej_cause); @@ -2450,23 +2412,21 @@ static int gsm48_mm_rel_loc_upd_rej(struct osmocom_ms *ms, struct msgb *msg) } /* send event to PLMN search process */ - switch(mm->lupd_rej_cause) { + switch (mm->lupd_rej_cause) { case GSM48_REJECT_ROAMING_NOT_ALLOWED: - nmsg = gsm322_msgb_alloc(GSM322_EVENT_ROAMING_NA); + msg_type = GSM322_EVENT_ROAMING_NA; break; case GSM48_REJECT_IMSI_UNKNOWN_IN_HLR: case GSM48_REJECT_ILLEGAL_MS: case GSM48_REJECT_ILLEGAL_ME: - nmsg = gsm322_msgb_alloc(GSM322_EVENT_INVALID_SIM); + msg_type = GSM322_EVENT_INVALID_SIM; break; default: - nmsg = gsm322_msgb_alloc(GSM322_EVENT_REG_FAILED); + msg_type = GSM322_EVENT_REG_FAILED; } - if (!nmsg) - return -ENOMEM; - ngm = (struct gsm322_msg *)nmsg->data; - ngm->reject = mm->lupd_rej_cause; - gsm322_plmn_sendmsg(ms, nmsg); + memset(&ngm, 0, sizeof(ngm)); + ngm.reject = mm->lupd_rej_cause; + gsm322_makesend_plmn_msg(ms, msg_type, NULL, 0); /* forbidden list */ switch (mm->lupd_rej_cause) { @@ -4106,13 +4066,9 @@ static int gsm48_mm_ev(struct osmocom_ms *ms, int msg_type, struct msgb *msg) static int gsm48_mmr_reg_req(struct osmocom_ms *ms) { struct gsm48_mmlayer *mm = &ms->mmlayer; - struct msgb *nmsg; /* schedule insertion of SIM */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_SIM_INSERT); - if (!nmsg) - return -ENOMEM; - gsm322_plmn_sendmsg(ms, nmsg); + gsm322_makesend_plmn_msg(ms, GSM322_EVENT_SIM_INSERT, NULL, 0); /* 4.2.1.2 SIM is inserted in state NO IMSI */ if (mm->state == GSM48_MM_ST_MM_IDLE diff --git a/src/host/layer23/src/mobile/gsm48_rr.c b/src/host/layer23/src/mobile/gsm48_rr.c index dc2226a..4a48dc8 100644 --- a/src/host/layer23/src/mobile/gsm48_rr.c +++ b/src/host/layer23/src/mobile/gsm48_rr.c @@ -375,8 +375,8 @@ static void new_rr_state(struct gsm48_rrlayer *rr, int state) rr->state = state; if (state == GSM48_RR_ST_IDLE) { - struct msgb *msg, *nmsg; - struct gsm322_msg *em; + struct msgb *msg; + struct gsm322_msg em; /* release dedicated mode, if any */ l1ctl_tx_dm_rel_req(rr->ms); @@ -403,16 +403,13 @@ static void new_rr_state(struct gsm48_rrlayer *rr, int state) * cell selection process returned to camping state * again. (after cell reselection) */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_RET_IDLE); - if (!nmsg) - return; /* return to same cell after LOC.UPD. */ if (rr->est_cause == RR_EST_CAUSE_LOC_UPD) { - em = (struct gsm322_msg *) nmsg->data; - em->same_cell = 1; + memset(&em, 0, sizeof(em)); + em.same_cell = 1; } - gsm322_c_event(rr->ms, nmsg); - msgb_free(nmsg); + gsm322_makesend_c_event(rr->ms, GSM322_EVENT_RET_IDLE, + (uint8_t *)&em, sizeof(em)); /* reset any BA range */ rr->ba_ranges = 0; } @@ -1192,11 +1189,7 @@ static int gsm48_rr_chan_req(struct osmocom_ms *ms, int cause, int paging) * NOTE: this must be sent unbuffered, because the state may not * change until idle mode is left */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_LEAVE_IDLE); - if (!nmsg) - return -ENOMEM; - rc = gsm322_c_event(ms, nmsg); - msgb_free(nmsg); + rc = gsm322_makesend_c_event(ms, GSM322_EVENT_LEAVE_IDLE, NULL, 0); if (rc) { if (paging) return rc; @@ -1567,7 +1560,7 @@ static int gsm48_new_sysinfo(struct osmocom_ms *ms, uint8_t type) { struct gsm48_sysinfo *s = ms->cellsel.si; struct msgb *nmsg; - struct gsm322_msg *em; + struct gsm322_msg em; /* update list of measurements, if BA(SACCH) is complete and new */ if (s @@ -1600,12 +1593,10 @@ static int gsm48_new_sysinfo(struct osmocom_ms *ms, uint8_t type) } /* send sysinfo event to other layers */ - nmsg = gsm322_msgb_alloc(GSM322_EVENT_SYSINFO); - if (!nmsg) - return -ENOMEM; - em = (struct gsm322_msg *) nmsg->data; - em->sysinfo = type; - gsm322_cs_sendmsg(ms, nmsg); + memset(&em, 0, sizeof(em)); + em.sysinfo = type; + gsm322_makesend_cs_event(ms, GSM322_EVENT_SYSINFO, + (uint8_t *)&em, sizeof(em)); /* send timer info to location update process */ nmsg = gsm48_mmevent_msgb_alloc(GSM48_MM_EVENT_SYSINFO); diff --git a/src/host/layer23/src/mobile/vty_interface.c b/src/host/layer23/src/mobile/vty_interface.c index 4cc2209..e3e7c47 100644 --- a/src/host/layer23/src/mobile/vty_interface.c +++ b/src/host/layer23/src/mobile/vty_interface.c @@ -658,8 +658,7 @@ DEFUN(network_select, network_select_cmd, "network select MS_NAME MCC MNC", { struct osmocom_ms *ms; struct gsm322_plmn *plmn; - struct msgb *nmsg; - struct gsm322_msg *ngm; + struct gsm322_msg ngm; struct gsm322_plmn_list *temp; uint16_t mcc = gsm_input_mcc((char *)argv[1]), mnc = gsm_input_mnc((char *)argv[2]); @@ -687,13 +686,11 @@ DEFUN(network_select, network_select_cmd, "network select MS_NAME MCC MNC", return CMD_WARNING; } - nmsg = gsm322_msgb_alloc(GSM322_EVENT_CHOOSE_PLMN); - if (!nmsg) - return CMD_WARNING; - ngm = (struct gsm322_msg *) nmsg->data; - ngm->mcc = mcc; - ngm->mnc = mnc; - gsm322_plmn_sendmsg(ms, nmsg); + memset(&ngm, 0, sizeof(ngm)); + ngm.mcc = mcc; + ngm.mnc = mnc; + gsm322_makesend_plmn_msg(ms, GSM322_EVENT_CHOOSE_PLMN, + (uint8_t *)&ngm, sizeof(ngm)); return CMD_SUCCESS; } @@ -818,16 +815,12 @@ DEFUN(network_search, network_search_cmd, "network search MS_NAME", "Network ...\nTrigger network search\nName of MS (see \"show ms\")") { struct osmocom_ms *ms; - struct msgb *nmsg; ms = get_ms(argv[0], vty); if (!ms) return CMD_WARNING; - nmsg = gsm322_msgb_alloc(GSM322_EVENT_USER_RESEL); - if (!nmsg) - return CMD_WARNING; - gsm322_plmn_sendmsg(ms, nmsg); + gsm322_makesend_plmn_msg(ms, GSM322_EVENT_USER_RESEL, NULL, 0); return CMD_SUCCESS; } @@ -1256,7 +1249,7 @@ DEFUN(cfg_ms_mode, cfg_ms_mode_cmd, "network-selection-mode (auto|manual)", { struct osmocom_ms *ms = vty->index; struct gsm_settings *set = &ms->settings; - struct msgb *nmsg; + int msg_type = -1; if (!ms->plmn.state) { if (argv[0][0] == 'a') @@ -1267,12 +1260,12 @@ DEFUN(cfg_ms_mode, cfg_ms_mode_cmd, "network-selection-mode (auto|manual)", return CMD_SUCCESS; } if (argv[0][0] == 'a') - nmsg = gsm322_msgb_alloc(GSM322_EVENT_SEL_AUTO); + msg_type = GSM322_EVENT_SEL_AUTO; else - nmsg = gsm322_msgb_alloc(GSM322_EVENT_SEL_MANUAL); - if (!nmsg) + msg_type = GSM322_EVENT_SEL_MANUAL; + if (msg_type < 0) return CMD_WARNING; - gsm322_plmn_sendmsg(ms, nmsg); + gsm322_makesend_plmn_msg(ms, msg_type, NULL, 0); return CMD_SUCCESS; } -- 1.7.2.3 --Kj7319i9nmIyA2yE Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0002-mobile-replace-3-different-gsm322_makesend_-function.patch"

1 0

Channel info
by Bogdan Alecu 30 Jan '11

30 Jan '11

Hello, I noticed that when I start the mobile application, after the phone chooses a specific channel I get different messages regarding IMSI saying that it's not for us. What are these messages? Phones that camp on this channel? If so, I tried turning off/on a phone from the same operator but I can't see my IMSI showing up.

5 9

Gpio driver for calypso
by Michal Demin 29 Jan '11

29 Jan '11

Hello, I have created few patches that aim to add abstraction for gpio handling. First patch adds functions: gpio_config - configure gpio as input/output gpio_read - read state of gpio(s) gpio_write - write/toggle state of gpio(s) gpio_set_handler - enables interrupt on given gpio. Also changes board init files to make them more sane :-) Second patch adds interrupt demuxing and masking into keypad driver as gpio and keypad are handled by the same peripheral. It would make sense to split the keypad driver into calypso-specific and generic stuff once there is support for other chipsets. Also note that interrupt levels in datasheet are active low (p.120), my testing shows otherwise. Michal Demin

1 1

doesn't get output from osmocon
by tobsen 29 Jan '11

29 Jan '11

Hi, sorry if I shouldn`t write correclly, i`m not that good in english. i have a Motorola c118 and this usb/serial cable: http://www.gsmbase.de/shop/show_product.php?products_id=620 here 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 on the phone. nothing happend. again. nothing happend, no output, no upload/download to/from the phone... what is my fault? can you help me? i have tested it with: -m 123 ; -m 118xor ; -m 118 (the same thing) my system is ubuntu 10.10 (not in a virtual box or something else). thanks a lot, tobsen -- View this message in context: http://baseband-devel.722152.n3.nabble.com/doesn-t-get-output-from-osmocon-… Sent from the baseband-devel mailing list archive at Nabble.com.

6 6

Documentation for 'mobile' in the wiki
by Harald Welte 29 Jan '11

29 Jan '11

Hi guys, I think it is desparately needed that we write more documentation about the 'mobile' program in our wiki. It just occurred to me today that no such page exists so far, and I've created it at http://bb.osmocom.org/trac/wiki/mobile I believe a simple reference of commands is not even all that important (after all, there is 'list' in the telnet interface), but somethnig like common scenarios like * behaving like a normal phone with cell-selection (using real sim) * behaving like a normal phone with cell-selection (using simulated sim) * how to lock to a certain ARFCN/cell * how to manually trigger location area update * how to send/receive sms * how to make mo/mt phone call It would be great if some of the more experienced people would find a couple of minutes to contribute to it. Thanks a lot in advance. 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)

1 0

Bounce action notification
by mailman＠lists.osmocom.org 28 Jan '11

28 Jan '11

This is a Mailman mailing list bounce action notice: List: baseband-devel Member: arslangali(a)inbox.ru Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman(a)lists.osmocom.org.

1 0

Re: Motorola usb cable
by Nikolaus Kohl 27 Jan '11

27 Jan '11

>> To make it work you have to recompile the module pl2303, with this >> patch >> (my kernel is 2.6.35.10-74.fc14.i686). Be careful to setup the right >> values in the kernel root Makefile in order to fit your running >> kernel. > > Not necessarily. You should also be able to check without recompiling. > > Just go to the drivers-directory in sysfs: > > cd /sys/bus/usb/drivers/<driver> > which <driver>?I cannot find any pl2303 driver here. (Debian and ubuntu 8.04)> and echo the data to the file new_id (as root): > > echo "067b 0307" > new_id > > This should bind the driver to the new_id. Niko

3 2

[PATCH] How to compile osmocom on NetBSD
by Pierre Pronchery 26 Jan '11

26 Jan '11

Hi baseband developers, a couple days ago I managed to compile osmocom's binaries and firmware files from a NetBSD host, using a cross-compilation toolchain generated with the standard build script on this system. This was actually quite straightforward, but required some patches and tricks, so I figured it'd be worth posting it here. I will write the procedure in more details on my blog [1], in my case it was enough to do this: $ CPATH="/usr/include" gmake \ CROSS_TOOL_PREFIX="/home/arm/tools/bin/arm--netbsdelf-" The patch itself is certainly more interesting to discuss here. I do not expect it to be fully merged, but I think it may raise interesting points: - src/shared/libosmocore/src/Makefile.am linking with "-ldl" is hardcoded, but breaks the build on systems where it is not required; this is a usual portability issue, already solved about a thousand times, I'll try to come up with a cleaner solution here. - src/shared/libosmocore/src/gsm_utils.c I think this one is quite elegant, allowing to build even without support for backtraces; an additional #warning would help though/ - src/shared/libosmocore/src/msgfile.c here I had to bluntly emulate the functionality of the getline() call, which seems to be specific to glibc; again, it'd certainly be nicer if I added a test for HAVE_GETLINE or something along this line. - src/shared/libosmocore/src/talloc.c again, talloc seems to rely on strnlen() being part of the libc, which is already known to not be the case on MacOS X; considering it also absent of NetBSD fixes the build for me. - src/target/firmware/include/stdint.h this one is definitely more ugly, since I tricked the cross-compiler to believe /usr/include matches its specific needs I ended up with some essential type definitions already; therefore, I am not sure if this workaround would not be more harmful upstream than not. Anyway, the actual patch is attached. A few more things to NetBSD users: - my previous patch about building without GNU make is also necessary; - I haven't tested the resulting binaries on a NetBSD host; - the firmware images seem to be only partly functional at the moment. HTH, -- khorben

1 1

Re: Trouble building Osmocom
by Holger Freyther 26 Jan '11

26 Jan '11

On 06/08/2010 09:41 PM, Huseyin Turan wrote: > root@name1-desktop:/home/name1/osmocom/gnuarm-4.0.2/bin# ls -l arm-elf-gcc > -rwxrwxrwx 1 name1 name1 112344 2006-02-17 23:59 arm-elf-gcc > root@name1-desktop:/home/name1/osmocom/gnuarm-4.0.2/bin# ./arm-elf-gcc > bash: ./arm-elf-gcc: cannot execute binary file > root@name1-desktop:/home/name1/osmocom/gnuarm-4.0.2/bin# uname -a > Linux name1-desktop 2.6.28-19-generic #61-Ubuntu SMP Wed May 26 23:35:15 > UTC 2010 i686 GNU/Linux > please try b.) again (you miss the file part) and also please reply to the mailinglist.

6 10

Re: Cell_log > gsmmap
by Bogdan Alecu 26 Jan '11

26 Jan '11

I just thought of another way of using cell_log without GPS. The resulting KML could be parsed and sent to opencellid project, this way we could get the lat-long coordinates and afterward create another kml and send it to Google. Ex: http://www.opencellid.org/cell/get?mcc=232&mnc=01&cellid=1721&lac=4269

2 1

[PATCH] Added command line switches to cell_log to change default gps device and baud rate.
by Dario Lombardo 26 Jan '11

26 Jan '11

--- src/host/layer23/src/misc/app_cell_log.c | 17 ++++++++++++++++- 1 files changed, 16 insertions(+), 1 deletions(-) diff --git a/src/host/layer23/src/misc/app_cell_log.c b/src/host/layer23/src/misc/app_cell_log.c index 84f5a83..9c05108 100644 --- a/src/host/layer23/src/misc/app_cell_log.c +++ b/src/host/layer23/src/misc/app_cell_log.c @@ -29,6 +29,7 @@ #include <osmocom/bb/common/l1ctl.h> #include <osmocom/bb/common/l23_app.h> #include <osmocom/bb/common/logging.h> +#include <osmocom/bb/common/gps.h> #include <osmocom/bb/misc/cell_log.h> #include <osmocore/talloc.h> @@ -91,6 +92,8 @@ static int l23_getopt_options(struct option **options) {"logfile", 1, 0, 'l'}, {"rach", 1, 0, 'r'}, {"no-rach", 1, 0, 'n'}, + {"gps", 1, 0, 'g'}, + {"baud", 1, 0, 'b'} }; *options = opts; @@ -103,6 +106,8 @@ static int l23_cfg_print_help() printf(" -l --logfile LOGFILE Logfile for the cell log.\n"); printf(" -r --rach RACH Nr. of RACH bursts to send.\n"); printf(" -n --no-rach Send no rach bursts.\n"); + printf(" -g --gps DEVICE /dev/ttyACM0. GPS device.\n"); + printf(" -b --baud BAUDRATE The baud rate of the GPS device\n"); return 0; } @@ -118,6 +123,16 @@ static int l23_cfg_handle(int c, const char *optarg) case 'n': RACH_MAX = 0; break; + case 'g': + snprintf(gps.device, ARRAY_SIZE(gps.device), "%s", optarg); + /* force string terminator */ + gps.device[ARRAY_SIZE(gps.device - 1)] = '\0'; + LOGP(DGPS, LOGL_INFO, "Using GPS device %s\n", gps.device); + break; + case 'b': + gps.baud = atoi(optarg); + LOGP(DGPS, LOGL_INFO, "Setting GPS baudrate to %u\n", gps.baud); + break; } return 0; @@ -125,7 +140,7 @@ static int l23_cfg_handle(int c, const char *optarg) static struct l23_app_info info = { .copyright = "Copyright (C) 2010 Andreas Eversberg\n", - .getopt_string = "l:r:n", + .getopt_string = "l:r:ng:b:", .cfg_supported = l23_cfg_supported, .cfg_getopt_opt = l23_getopt_options, .cfg_handle_opt = l23_cfg_handle, -- 1.7.3.4 --------------090907080903040108080303--

1 0

Re: Cell_log > gsmmap
by Bogdan Alecu 26 Jan '11

26 Jan '11

Or even better, use Google API and this way you could also include the Signal strenght and Timing advance for a better position. See http://translate.google.com/translate?js=y&prev=_t&hl=en&ie=UTF-8&layout=1&… --- On Wed, 1/26/11, Bogdan Alecu <b.alecu(a)yahoo.com> wrote: From: Bogdan Alecu <b.alecu(a)yahoo.com> Subject: Re: Cell_log > gsmmap To: Cc: baseband-devel(a)lists.osmocom.org Date: Wednesday, January 26, 2011, 7:27 AM I just thought of another way of using cell_log without GPS. The resulting KML could be parsed and sent to opencellid project, this way we could get the lat-long coordinates and afterward create another kml and send it to Google. Ex: http://www.opencellid.org/cell/get?mcc=232&mnc=01&cellid=1721&lac=4269

1 0

[PATCH] Adjust top-level Makefile for arm-none-eabi toolchain
by Peter Stuge 25 Jan '11

25 Jan '11

The gnuarm.com toolchain works fine but is very old. And although it is based on newlib, the os name in the tuple that we used to configure for is arm-elf-linux, which is of course bogus since we are not building Linux applications. Finally, CC= should never be set, instead configure should detect the right compiler using the --host tuple. --- src/Makefile | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/Makefile b/src/Makefile index b3594c1..e66f0ff 100644 --- a/src/Makefile +++ b/src/Makefile @@ -1,10 +1,10 @@ # this is not really used as we don't do 'make install'. You can still specify # it in case you _want_ to manually 'make install' the target libosmocore. -CROSS_INST_PREFIX=/usr/local/stow/osmocom-bb/arm-elf +CROSS_INST_PREFIX ?= /usr/local/stow/osmocom-bb/arm-2010.09 # this is the prefix of your cross-toolchain programs -CROSS_TOOL_PREFIX=arm-elf- +CROSS_TOOL_PREFIX ?= arm-none-eabi- TOPDIR=$(shell pwd) OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \ @@ -37,9 +37,9 @@ shared/libosmocore/build-target: shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target cd shared/libosmocore/build-target && ../configure \ - --host=arm-elf-linux --disable-vty --enable-panic-infloop \ + --host=arm-none-eabi --disable-vty --enable-panic-infloop \ --disable-shared --disable-talloc --disable-tests \ - CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" + CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile cd shared/libosmocore/build-target && make -- 1.7.2

4 6

[PATCH] Adjust top-level Makefile for arm-none-eabi toolchain
by Peter Stuge 25 Jan '11

25 Jan '11

The gnuarm.com toolchain works fine but is very old. And although it is based on newlib, the tuple that we used to configure for was arm-elf-linux, which is of course bogus since we aren't building Linux applications. This patch optimizes for the CodeSourcery G++ Lite 2010.09 ARM EABI toolchain, and assumes that it was unpacked next to the old one. Download here: http://www.codesourcery.com/sgpp/lite/arm/portal/release1592 (I haven't gotten the Linux Installer to work, so I recommend the TAR.) And since CC is detected by configure when a valid host tuple is given and that toolchain is sane there's no need for us to hard-code the gnuarm.com compiler name in our Makefile. --- src/Makefile | 11 +++++++---- 1 files changed, 7 insertions(+), 4 deletions(-) diff --git a/src/Makefile b/src/Makefile index b3594c1..f2d935b 100644 --- a/src/Makefile +++ b/src/Makefile @@ -1,10 +1,13 @@ # this is not really used as we don't do 'make install'. You can still specify # it in case you _want_ to manually 'make install' the target libosmocore. -CROSS_INST_PREFIX=/usr/local/stow/osmocom-bb/arm-elf +CROSS_INST_PREFIX ?= /usr/local/stow/osmocom-bb/arm-2010.09 + +# this is the host tuple of your cross-toolchain +HOST ?= arm-none-eabi- # this is the prefix of your cross-toolchain programs -CROSS_TOOL_PREFIX=arm-elf- +CROSS_TOOL_PREFIX ?= $(CROSS)- TOPDIR=$(shell pwd) OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \ @@ -37,9 +40,9 @@ shared/libosmocore/build-target: shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target cd shared/libosmocore/build-target && ../configure \ - --host=arm-elf-linux --disable-vty --enable-panic-infloop \ + --host=$(HOST) --disable-vty --enable-panic-infloop \ --disable-shared --disable-talloc --disable-tests \ - CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" + CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile cd shared/libosmocore/build-target && make -- 1.7.2 --dMyqICaxQaaUjrCL--

1 0

[PATCH] Allow top-level Makefile to use arm-none-eabi toolchain
by Peter Stuge 25 Jan '11

25 Jan '11

The gnuarm.com toolchain works fine but is very old. And although it is based on newlib, the tuple that we used to configure for was arm-elf-linux, which is bogus since we aren't building for Linux. This patch optimizes for the CodeSourcery G++ Lite 2010.09 ARM EABI toolchain instead, and for libosmocore installation it assumes that the new toolchain was unpacked next to the old one. Download it here: http://www.codesourcery.com/sgpp/lite/arm/portal/release1592 (The Linux Installer seems not to work reliably so I recommend the TAR.) Since CC is detected by configure when the host tuple points to a sane toolchain we shouldn't hard-code the gnuarm.com compiler. The patch autodetects arm-elf-gcc installed in PATH, and uses arm-elf as prefix if it is found. Otherwise, it defaults to arm-none-eabi. make CROSS_HOST=arm-xyzzy can be used to override on the command line. --- src/Makefile | 11 +++++++---- 1 files changed, 7 insertions(+), 4 deletions(-) diff --git a/src/Makefile b/src/Makefile index b3594c1..402f28a 100644 --- a/src/Makefile +++ b/src/Makefile @@ -1,10 +1,13 @@ # this is not really used as we don't do 'make install'. You can still specify # it in case you _want_ to manually 'make install' the target libosmocore. -CROSS_INST_PREFIX=/usr/local/stow/osmocom-bb/arm-elf +CROSS_INST_PREFIX ?= /usr/local/stow/osmocom-bb/arm-2010.09 + +# this is the host tuple of your cross-toolchain +CROSS_HOST ?= $(shell which arm-elf-gcc >/dev/null 2>&1 && echo arm-elf || echo arm-none-eabi) # this is the prefix of your cross-toolchain programs -CROSS_TOOL_PREFIX=arm-elf- +CROSS_TOOL_PREFIX=$(CROSS_HOST)- TOPDIR=$(shell pwd) OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \ @@ -37,9 +40,9 @@ shared/libosmocore/build-target: shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target cd shared/libosmocore/build-target && ../configure \ - --host=arm-elf-linux --disable-vty --enable-panic-infloop \ + --host=$(CROSS_HOST) --disable-vty --enable-panic-infloop \ --disable-shared --disable-talloc --disable-tests \ - CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" + CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile cd shared/libosmocore/build-target && make -- 1.7.2 --ibvzjYYg+QDzMCy1--

1 0

[PATCH] Adjust top-level Makefile for arm-none-eabi toolchain
by Peter Stuge 25 Jan '11

25 Jan '11

The gnuarm.com toolchain works fine but is very old. And although it is based on newlib, the tuple that we used to configure for was arm-elf-linux, which is of course bogus since we aren't building Linux applications. This patch optimizes for the CodeSourcery G++ Lite 2010.09 ARM EABI toolchain, and assumes that it was unpacked next to the old one. Download here: http://www.codesourcery.com/sgpp/lite/arm/portal/release1592 (I haven't gotten the Linux Installer to work, so I recommend the TAR.) And since CC is detected by configure when a valid host tuple is given and that toolchain is sane there's no need for us to hard-code the gnuarm.com compiler name in our Makefile. --- src/Makefile | 11 +++++++---- 1 files changed, 7 insertions(+), 4 deletions(-) diff --git a/src/Makefile b/src/Makefile index b3594c1..bb34175 100644 --- a/src/Makefile +++ b/src/Makefile @@ -1,10 +1,13 @@ # this is not really used as we don't do 'make install'. You can still specify # it in case you _want_ to manually 'make install' the target libosmocore. -CROSS_INST_PREFIX=/usr/local/stow/osmocom-bb/arm-elf +CROSS_INST_PREFIX ?= /usr/local/stow/osmocom-bb/arm-2010.09 + +# this is the host tuple of your cross-toolchain +HOST ?= arm-none-eabi- # this is the prefix of your cross-toolchain programs -CROSS_TOOL_PREFIX=arm-elf- +CROSS_TOOL_PREFIX ?= $(HOST)- TOPDIR=$(shell pwd) OSMOCORE_CONFIGURE_ENV= LIBOSMOCORE_LIBS=$(TOPDIR)/shared/libosmocore/build-host/src/.libs/libosmocore.a \ @@ -37,9 +40,9 @@ shared/libosmocore/build-target: shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/libosmocore/build-target cd shared/libosmocore/build-target && ../configure \ - --host=arm-elf-linux --disable-vty --enable-panic-infloop \ + --host=$(HOST) --disable-vty --enable-panic-infloop \ --disable-shared --disable-talloc --disable-tests \ - CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" + CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile cd shared/libosmocore/build-target && make -- 1.7.2 --nEsDIrWrg+hrB7l1--

1 0

C99 [was Fwd: Cell_log > gsmmap]
by Dieter Spaar 25 Jan '11

25 Jan '11

Hello Holger, On Tue, 25 Jan 2011 16:51:02 +0100, "Holger Hans Peter Freyther" <holger(a)freyther.de> wrote: > > Almost perfect. I can apply and modify myself or you could do two things. We > tend to avoid the '//' comments, they were only added in C99 and used to be a > GCC extension for C. This is a good one ;-) One of the biggest problems when I tried a long time ago to compile any of OpenBSC or OsmocomBB with a different compiler than GCC were designated initializer which are _heavily_ used all over the sources (I don't question their advantage, I only mention it). They are a C99 feature (besides the library function snprintf() in the patch you commented). So I would not care about the '//', this was the smallest problem I had when I did my porting experiment (in fact the compilers I am aware of silently accept it). Just out of interest, do we really want to to avoid C99 ? I know there is this implicit "kernel style" coding rule, does it include C99 ? Please note that I don't want to discuss this, I use GCC from Cygwin and can find workarounds for Linux specific issues on Windows on my own, so I don't care that much. I am just interested in the reasons for using C99 or not. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

5 5

RE:Cell_log > gsmmap
by Bogdan Alecu 25 Jan '11

25 Jan '11

A Wiki on how to use it would be great!

2 3

Fwd: Cell_log > gsmmap
by MArc Richter 25 Jan '11

25 Jan '11

Do i need a GPS Reciver ? I tought that it will calculate the location over Triangulation ? On Tue, Jan 25, 2011 at 10:34 AM, Holger Hans Peter Freyther < holger(a)freyther.de> wrote: > On 01/25/2011 08:33 AM, MArc Richter wrote: > > > But when i convert it into a kml file with gsmmap i can't see any GPS > > koordinates. Why ? > > Do you have a GPS receiver attached to your computer? > >

12 42

Cell_log > gsmmap
by MArc Richter 25 Jan '11

25 Jan '11

Hey! I've tryed out the Cell_log tool to get the Location of the GSM cells. But when i convert it into a kml file with gsmmap i can't see any GPS koordinates. Why ? I use the Sylvain branch an compiled with TX support thx

2 1

question on pirelli dp l10
by Scott Weisman 25 Jan '11

25 Jan '11

I looked more into this phone recently and found out it supported SIP over WiFi as well. Does anyone know about the software running the phone? How are the VOIP codecs handled? Is there hardware support for them? Finally, does code and/or drivers already exist for the hardware components? I happened to be looking for something exactly like this anyway. Cool to know that OsmocomBB can (potentially) work on it too. Scott

2 2

Re: Sniff Code..shown @chao conf.. CCC
by Aaron Zauner 24 Jan '11

24 Jan '11

Oh, i also found this: http://permalink.gmane.org/gmane.comp.gnu.radio.general/31145 -> http://en.wikipedia.org/wiki/Manoj_Kumar lol. so long, azet

6 7

[PATCH] Support GNU make when it is not called "make"
by Pierre Pronchery 24 Jan '11

24 Jan '11

Hi baseband developers, just a small patch to help where GNU make is not directly called "make". HTH, -- khorben

1 0

Creatng a list of known issues somewhere
by Holger Hans Peter Freyther 24 Jan '11

24 Jan '11

Hi all, it appears that we all know of some issues but we are not writing them down. Would it make sense to start using the bugtracker for that? Or just a dedicated wiki site?

2 2

problems getting Pirelli DP-L10 to work
by Leif Jakob 24 Jan '11

24 Jan '11

Hi, maybe I'm missing something, but when I read that the Pirelli DP-L10 would be supported I tried to get it running: I didn't patch my usb-module, but used: modprobe -v cp210x echo "0489 e003" > /sys/bus/usb-serial/drivers/cp210x/new_id from the steve-m/testing-branch I compiled the firmware and loaded it with ./host/osmocon/osmocon -p /dev/ttyUSB0 -m romload target/firmware/board/pirelli_dpl10/hello_world.highram.bin onto the phone... that worked but I was never able to see any messages after the upload: Received block ack from phone Sending checksum: 0xaa Checksum on phone side matches, let's branch to your code Branching to 0x00820000 Received branch ack, your code is running now! ... there it stayed forever ... I'm pretty sure that the code runs, because I commented in init.c the keyboard lighting code and it didn't light up after upload. I've tried other bins but to no success. Any hint or am it too early playing with that hardware? Greetings Leif

2 1

Regarding IMSI detach DoS
by Bogdan Alecu 24 Jan '11

24 Jan '11

Hello, In order for this attack to work it has to be on a GSM network because on 3G there is a higher security mechanism. A way to protect against this, for the opperator, could be to implement 3G over 900Mhz so this way even if the targeted phones are on 2G they will still be protected. Am I right? Regards, Bogdan

2 1

serial cable
by Tommy R. 23 Jan '11

23 Jan '11

Hey, I ordered the serial cable coming from dealextreme and it has not arrived yet. I noticed today that the link was taken off the wiki due to it not being at TTL levels. I was wondering if I bought a Nokia serial cable (the ones that have the prolific chips in them) which runs at 3.3v out of the box, could I just connect the tx and rx pins to the cable I had bought and it would possibly work or would that be a bad idea and I should cut my losses and kill the order. -- -Tom

2 1

Sniff Code..shown @chao conf.. CCC
by Marten Christophe 23 Jan '11

23 Jan '11

Hello All, Pls help me, any one who can Kindly give me code or even binary file for sniff code which Sylvain demonstrated in chao meeting, it will solve my purpose, i can See, in video he made the same interface to tune to a ARFCN, TS , and hopping sequence as i requested a long time back to mailling list It will be great help for poor students. my project don't required any a5 creaking so it wont be used as unlawful means. so far i have arranged 12 USRP1 to run openBTS. I just wanted to do the same, which Sylvain have done in video @ chao presentation, except cracking the encryption as i will configure openBTS as a5/0 coz it’s education transmission not necessary to encrypt kindly do me a favour in shake of charity. Pls reply to my query pls help me in the shake of poor students. I promise will keep that code secret and will not disclose to any one else. or pls advise me how i can modify existing code up to that level. Kindly reply on my request , can you pls provide me Sniff software? it will help me allot, my NGO can deploy a pilot project at least Kind Regards,

4 3

Non Standard Baud Rates?
by MATTHEW EVANS 22 Jan '11

22 Jan '11

Hi, I'm trying to get the burst_ind branch working at the higher speed baud rates. I have a USB to Serial FTDI Cable (FT232R) plus the T191. This setup works fine with the main trunk of osmocombb. When I fire up osmocon, layer1 appears to download to the phone and runs successfully. Osmocon then logs 'Received DOWNLOAD ACK from phone, your code is running now!'. The phone has layer1.bin displayed as usual. However it goes no further and just hangs. Could anyone please give any advice on what to try next? Thanks, Matt.

2 1

Why my phone can't attach the network?
by xuchenyu 22 Jan '11

22 Jan '11

Thanks to Tomas and ton, I can run osmocombb on the phone. But the phone can't attach the network, can't make a call, can't recognise the SIM card. I found that this was no BCCH received in wireshark. And when I type some command via telnet localhost, it always output "Command incomplete" Anybody can give me some solution? Thanks! -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Why-my-phone-can-t-attach-the-ne… Sent from the baseband-devel mailing list archive at Nabble.com.

2 1

Re:radio is not started
by Bogdan Alecu 21 Jan '11

21 Jan '11

I guess you have the default configuration: "No Mobile Station defined, creating: MS '1'" After you start "mobile" application, select "enable" and then "write". This will write your configuration to /etc/osmocom/osmocom.cfg After that edit this file and set from no sim to sim reader. Restart the mobile application and it should work.

2 3

Motorola usb cable
by Dario Lombardo 21 Jan '11

21 Jan '11

Hello everydoby I have Motorola-branded prolific usb cable. This cable, once inserted in a port, claims to be a 0307 chipset adapter, and Linux kernel doesn't recognize it: not working. Someone told me that Motorola has changed the label in those cables that claim to be 0307, but they are pl2303. Does anyone have one of these cables working? I've tried many ways, including udev, to make it work, but no success. My next step is to recompile the kernel module, but I was wondering if someone has solved it in another way. Bye Dario.

3 4

Pirelli DP-L10 support, steve-m/testing branch
by Steve Markgraf 20 Jan '11

20 Jan '11

Hi all, last weekend I have grinded down a DP-L10 pcb and traced the TSPACT wiring of this board. I've added support for this phone, along with a few other changes in my branch steve-m/testing. Changes include: * Add support for Pirelli DP-L10 * Add TX support for the gta0x devices * separate board images for the Compal E86 (Motorola C139/C140) (display/keypad backlight now works by default) If anyone wants to test those changes (especially the freerunner TX support, since I have no freerunner), please feel free to do so. I tested the other changes and didn't find any regressions, so if no one else does, we can merge it to master soon. One thing I noticed during testing: The C139/C140 seem to have a different SYSTEM_INHERENT_GAIN, I compared the RX levels of several C118/C123/C155 with several C139/C140, and the reported rx level was always at around 18-20dBm worse than with the C123. Regards, Steve

1 1

radio is not started
by Muhammad Rasyid Sahputra 20 Jan '11

20 Jan '11

Hi, I tried to follow instruction on SIM Reader wiki, but seems I got different result. OsmocomBB> enable OsmocomBB# sim reader 1 OsmocomBB# show subscriber Mobile Subscriber of MS '1': IMSI: Status: U2_NOT_UPDATED IMSI detached LAI: invalid Access barred cells: no Access classes: OsmocomBB# show 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 CECS : no VGCS : no VBS : no SMS : yes 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# show ms MS '1' is down, radio is not started IMEI: 000000000000000 IMEISV: 0000000000000000 IMEI generation: fixed automatic network selection state: A0 null cell selection state: C0 null radio ressource layer state: idle mobility management layer state: MM idle, PLMN search from the layer23 part, $ ./mobile -i 127.0.0.1 -d 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. mobile: option requires an argument -- d 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:3471 init PLMN process <0003> gsm322.c:3472 init Cell Selection process <0003> gsm322.c:3526 No stored BA list Mobile '1' initialized, please start phone now! <0004> subscriber.c:556 Requesting SIM file 0x2fe2 <000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000e> sim.c:697 go MF <000e> sim.c:241 SELECT (file=0x3f00) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4) can't perform location update, and from the error, is that mean the application failed to read the simcard correctly? and what's the meaning of "Mobile '1' initialized, please start phone now!", is it starting the phone by push the power button? if so, since the firmware is loaded I can't make the phone start like using original firmware. If i push the button, it will show message like Found flash of 2097152 bytes at 0x0 with 2 regions Region 0 of 31 pages with 65536 bytes each. Region 1 of 8 pages with 8192 bytes each. key=20 pressed Powering off due to keypress. I am using motorola c118 anw. any clue about this error? Thanks. Best Regards, Rasyid

1 0

USB fetmocell: What's about the sofware?
by Fabio Pietrosanti (naif) 19 Jan '11

19 Jan '11

Hi all, i noticed that article http://www.eetimes.com/electronics-news/4212228/Picochip-shares-femtocell-r… speaking about 3G basestation on USB dongle. That's really cool, i don't know about the hardware, but for sure when those device will be out the hacking perspective would be really interesting for projects like OpenBSC and OsmocomBB . -naif

1 0

sim reader code / master branch / ...
by Harald Welte 19 Jan '11

19 Jan '11

Hi all! In order to avoid the most common problems, I propose exporting something like a feature bitmask on the L1CTL, i.e. * L1CTL user code (layer23) can send a L1CTL_GET_FEAT_REQ request * laye1 in the phone sends a L1CTL_GET_FEAT_RESP with all the bits set to 1 for the features it supports * L1CTL user code (layer23) can then check if all the features it needs are supported by the L1. IF not, it can simply abort or print a warning to the user. We can simply extend the size of the bitmask over time if we need more bits. Obvious bits I would consider are: - is this firmware compiled with TX support? - does this firmware contain a SIM reader driver? - does this firmware support BURST_IND? Maybe we could also include a static header containing a compile timestamp or the git date/revision that the firmware was built, as well as a name of the board. Now I know, nice idea, who will implement it? I currently have othe priorities, but if somebody lurking on this list is looking for a relatively simple way to contribute back to the project (without knowing anything about GSM!) this might be something useful you could do. 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)

4 5

Re: wiki: SIMReader Was: Sim on C115 & C118
by Dobrica Pavlinusic 19 Jan '11

19 Jan '11

On Mon, Jan 17, 2011 at 11:46:50AM -0800, Bogdan Alecu wrote: > Hello, > > Sorry for writing you directly to your email. Thank you very much for the wiki. I was wondering if you have some knowledge about the "sim test" mode. I tried it by filling in the IMSI and MCC MNC. After I start the layer2 in a few seconds layer1 crashes. What I am trying to achieve is to send a IMSI detach to the network for the specified IMSI. Maybe you could give me a hand with this. This is often second question after getting SIM working, so I want to share what I know. However, I'm not an expert, and most of this is gathered from presentations and speaking with people who know more than I do, so I wanted to bounce this against mailing list for additional comments. As far as I understand it, to connect to provider network, you need provider's ki which is shared secret between network and sim card. There are some practical attacks on older sim cards which are used by multi-network sim cards. It seems there is limited number of brute-force interations that cards support before disabling themself and that changed somehow in recent cards. Best SIM explanation I found so far is on 27C3 wiki about GSM network: http://events.ccc.de/congress/2010/wiki/GSM#Why_do_I_need_to_buy_your_SIM_c… > --- On Mon, 1/17/11, Dobrica Pavlinusic <dpavlin(a)rot13.org> wrote: > > > From: Dobrica Pavlinusic <dpavlin(a)rot13.org> > Subject: wiki: SIMReader Was: Sim on C115 & C118 > To: "Bogdan Alecu" <b.alecu(a)yahoo.com> > Cc: dario.lombardo(a)libero.it, baseband-devel(a)lists.osmocom.org > Date: Monday, January 17, 2011, 7:05 PM > > > On Mon, Jan 17, 2011 at 10:24:51AM -0800, Bogdan Alecu wrote: > > I was going to ask the same question because I have same problem with sim reader mode. However I haven't used Sylvain test. I will and come back with an update. > > There seems to be sufficiant interest for using SIM reader, so I created > page on wiki which might serve as good pointer: > > http://bb.osmocom.org/trac/wiki/SIMReader > > -- > Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org > Unix addict. Internet consultant. http://www.rot13.org/~dpavlin > > > > -- Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin

4 6

Why my C118 can't send DOWNLOAD ACK?
by xuchenyu 18 Jan '11

18 Jan '11

~/src/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123 ../../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: 2f / got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 1b . got 2 bytes from modem, data looks like: f6 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: 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=50932, hdr_len=4, dnload_len=50939 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/50939) handle_write(): 4096 bytes (8192/50939) handle_write(): 4096 bytes (12288/50939) handle_write(): 4096 bytes (16384/50939) handle_write(): 4096 bytes (20480/50939) handle_write(): 4096 bytes (24576/50939) handle_write(): 4096 bytes (28672/50939) handle_write(): 4096 bytes (32768/50939) handle_write(): 4096 bytes (36864/50939) handle_write(): 4096 bytes (40960/50939) handle_write(): 4096 bytes (45056/50939) handle_write(): 4096 bytes (49152/50939) handle_write(): 1787 bytes (50939/50939) handle_write(): finished It stopped here for very long time, I have tried with XOR and without XOR for many times! Please help me to verify this issue! thanks very much! -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Why-my-C118-can-t-send-DOWNLOAD-… Sent from the baseband-devel mailing list archive at Nabble.com.

2 1

Toolchain tests, problems and a few workarounds...
by Wolfram Sang 18 Jan '11

18 Jan '11

Hi, at 27c3, I tested some toolchains with osmocom-bb and found a few build-problems, even with the recommended gnuarm-3.4.3. I want to document them here, so other people can find hints about it. *** GNUARM 3.4.3 TOOLCHAIN master branch ============= ../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory Holger suggested to manually remove this line. It is fixed upstream in libosmocore and osmocom-bb needs to be synced to it. Please do :) remotes/origin/steve-m/loader_sciphone ====================================== 1) First problem is: In file included from ../../include/osmocore/msgb.h:23, from ../../src/msgb.c:27: /home/wsa/Dev/osmocom-bb/src/target/firmware/include/stdint.h:13:25: stdint.h: No such file or directory Cherry-picking e0a605819c39187a494e43cf591f2e79a9d9903f (stdint.h: Next attempt at making this work with various compilers) helps. 2) It then runs into the problem of the master branch. 3) After this is fixed, I get ../../../src/codec/gsm610.c:24:20: stdint.h: No such file or directory ../../../src/codec/gsm610.c:33: error: parse error before "gsm610_bitorder" which needs 733c894c18c127ce5c023e39609b7d2b9e748e7e (build: Use absolute path in the CFLAGS for libosmocore target build) as a fix. 4) This then, leads to: arm-elf-ld: address 0x400054d4 of board/mt62xx/loader.mtkram.elf section .text is not within region LRAM which is sadly also present when you just cherry-pick the main patch d04761d19c432201f7c0f10c72f788fb695d466a ([WIP] Modify loader for use as first stage bootloader on MT62xx devices) on top of current master + its build fix. So, does it seem sensible to simply rebase this branch to master which would eliminate the first three problems? Or at least cherry-pick the above fixes? Also, the workarounds for gcc3 do not look very sustainable (see custom stdint.h). Is it a mid-term option to remove that stuff if a reliable pre-built gcc4 is available? (I am working on that, see below). BTW the linker error was not further worked on yet. I got a prebuilt binary now. It is possibly helpful to put it on the G2-wikipage, so people wanting to work on the Linux-support only are spared from the above hassle. *** CUSTOM 4.3.2 TOOLCHAIN every branch ============ The configure-stage of libosmocom already fails for the target with error 77. The config.log says in detail: configure:3231: checking whether the C compiler works configure:3253: arm-elf-gcc -Os -ffunction-sections -I/home/wsa/Dev/osmocom-bb/src/target/firmware/include conftest.c >&5 /home/opt/OSELAS.Toolchain-1.99.3/arm-elf/gcc-4.3.2-newlib-1.16.0-binutils-2.18/bin/../lib/gcc/arm-elf/4.3.2/../../../../arm-elf/lib/libc.a(lib_a-exit.o): In function `exit': /home/mkl/himalia-pengutronix/toolchain/releases/OSELAS.Toolchain-1.99.3.6/platform-arm-elf-gcc-4.3.2-newlib-1.16.0-binutils-2.18/build-target/newlib-1.16.0/newlib/libc/stdlib/exit.c:65: undefined reference to `_exit' /home/opt/OSELAS.Toolchain-1.99.3/arm-elf/gcc-4.3.2-newlib-1.16.0-binutils-2.18/bin/../lib/gcc/arm-elf/4.3.2/../../../../arm-elf/lib/libc.a(lib_a-sbrkr.o): In function `_sbrk_r': /home/mkl/himalia-pengutronix/toolchain/releases/OSELAS.Toolchain-1.99.3.6/platform-arm-elf-gcc-4.3.2-newlib-1.16.0-binutils-2.18/build-target/newlib-1.16.0/newlib/libc/reent/sbrkr.c:60: undefined reference to `_sbrk' 27c3 was too interesting ;) so I haven't fixed this yet. The Mac-toolchains also throw this and I also have seen it on the list before, so I hope I can work on it the next days. So much for now. It would be nice if someone with write-access to the repo could comment on my questions and/or fix the low-hanging fruits. I will hopefully be able to send some updates soon, too (famous last words). It was great to meet you all in person! All the best, Wolfram

1 1

Re: R: Re: C115 loader.compalram.bin
by Tomas Kopsa 18 Jan '11

18 Jan '11

Hi Lia, I have tested another cable (USB <-> 2,5 jack, speacial for Compal phones) - it is the same chip (Prolific) and I am able to load firmware too. Although it is the same chip, there is a difference that this one makes the osmocon printing those messages instantly when phone is not connected: got 1 bytes from modem, data looks like: f5 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: f5 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: f5 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: fd . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: f5 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: fd . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: ea . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: ea . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: ea . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: ea . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: fd . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: ea If I connect phone, printing stops. Here is what happened when I tried to load firmware without xor (-m c123) and pressed the button: (This happened every attempt without xor flag) Received PROMPT2 from phone, starting download handle_write(): 1087 bytes (1087/50947) got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 45 E got 1 bytes from modem, data looks like: 53 S got 1 bytes from modem, data looks like: 16 . Received DOWNLOAD NACK from phone, something went wrong :( got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 00 . If you have USB adapter (I guess you have), you dont need to check model, check 'lsusb' [root@amilo osmocon]# lsusb Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub *Bus 002 Device 017: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port* If you have Prolific, which is very common, I encourage you to use xor flag. You can also try to switch on your phone to check if original firmware boots. I experienced during my early tests, that phone crashed (probably SRAM) and it was unable to boot even original fw. In case phone is crashed, reconnect battery and it will fix itself. Here is the ACK after hello world load: handle_write(): 768 bytes (17919/19787) handle_write(): 768 bytes (18687/19787) handle_write(): 768 bytes (19455/19787) handle_write(): 332 bytes (19787/19787) 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 Hello World (revision osmocon_v0.0.0-754-gb5abcb6-modified) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: efce3b1ce1001255 ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ============================================== Looking forward your response, Tomas > Hi Tomas, > > thanks for your feedback. > > Actually, I've tried both flags (woth/without xor extension), but hte > result is the same. > > So, in your opinioni, the problem could depend on the cable? > > I don't have the cable model now, but I can send you this information > Tuesday. > > Thanks again. > > cheers. > > lia > > ----Messaggio originale---- > Da: deacon(a)volny.cz > Data: 16-gen-2011 4.26 > A: <list_mailing(a)libero.it> > ubut Ogg: Re: C115 loader.compalram.bin > > Hello, > I have C115 too and I use '-m c123xor' switch, the phone mostly > boots on 1st button push (I never reacher full load with '-m c123'). > > ./osmocon -p /dev/ttyUSB0 -m c123xor > ../../target/firmware/board/compal_e88/hello_world.compalram.bin > ./osmocon -p /dev/ttyUSB0 -m c123xor > ../../target/firmware/board/compal_e88/loader.compalram.bin > ./osmocon -p /dev/ttyUSB0 -m c123xor > ../../target/firmware/board/compal_e88/layer1.compalram.bin > > I have FTDI USB<->RS232 + Calypso serial. When load fails (with > xor), I have a feeling that it helps reconnection cable to the phone. > (I have also Calypso USB cable which I haven't tested yet, will > report later.) > > - Tomas > > >>> Hello. >>> I'm trying to load the loader.compalram.bin. >>> The behaviour is very strange because sometimes the download is complete and >>> successfull, sometimes; in particular, in this case, the download is complete, >>> but any ACK is sent back from the mobile phone (see below). >>> ./osmocon -p /dev/ttyUSB0 -m c123 ../.. >>> /target/firmware/board/compal_e99/loader.compalram.bin >>> got 2 bytes from modem, data looks like: 2e c8 .. >>> 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_e99/loader.compalram.bin): >>> file_size=21752, hdr_len=4, dnload_len=21759 >>> 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/21759) >>> handle_write(): 4096 bytes (8192/21759) >>> handle_write(): 4096 bytes (12288/21759) >>> handle_write(): 4096 bytes (16384/21759) >>> handle_write(): 4096 bytes (20480/21759) >>> handle_write(): 1279 bytes (21759/21759) >>> handle_write(): finished >>> >>> >>> The target phone is C115. I tried compal_exx and the result is the same :-( >>> >>> Please, can someone help me to understand the reasons? >>> Thanks in advance. >>> >>> >>> >>> >> > > >

6 6

[PATCH] Makefile: be more robust against toolchains without syscalls
by Michael Grzeschik 18 Jan '11

18 Jan '11

Several toolchains are missing syscalls provided by the libc used. For example, if the newlib was build with the configure flag "--disable-newlib-supplied-syscalls". To prevent the configure check for things like "_exit" in osmocom the CFLAGS+="-nostartfiles -nodefaultlibs" helps a lot. Signed-off-by: Michael Grzeschik <mgr(a)xviews.de> Acked-by: Wolfram Sang <wolfram(a)the-dreams.de> --- src/Makefile | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/Makefile b/src/Makefile index a0dea5d..b3594c1 100644 --- a/src/Makefile +++ b/src/Makefile @@ -39,7 +39,7 @@ shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/li cd shared/libosmocore/build-target && ../configure \ --host=arm-elf-linux --disable-vty --enable-panic-infloop \ --disable-shared --disable-talloc --disable-tests \ - CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include" + CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile cd shared/libosmocore/build-target && make -- 1.7.2.3

3 2

AW: you know phone maybe can made USRP
by Andreas.Eversberg 18 Jan '11

18 Jan '11

sylvain, looks like you are talking to a spam bot. (harald already did earlier :)

1 0

you know phone maybe can made USRP
by 麦田守望 18 Jan '11

18 Jan '11

do you know Which phone can made USRP thanks

3 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel