baseband-devel May 2014

baseband-devel@lists.osmocom.org

17 participants
33 discussions

Re: Error loading firmware onto Motorola C115.
by msokolov＠ivan.Harhan.ORG 30 Jul '14

30 Jul '14

Ravi Sharan <ravisharan(a)iith.ac.in> wrote: > I am trying out osmocom-bb with the Motorla C115. [...] < I get the following error: > > $ osmocon -p /dev/ttyUSB0 -m c123 > ~/osmocom-bb/src/target/firmware/board/compal_e88/hello_world.compalram.bin > [snipped the part where everything goes as it should] > 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 :( Try -m c123xor instead of -m c123. HTH, SF

4 6

[PATCH] Update GPRS cipher API to comply with ETSI TS 155.22
by Max 17 Jun '14

17 Jun '14

--- include/osmocom/crypt/gprs_cipher.h | 8 ++++++-- src/gsm/gprs_cipher_core.c | 20 +++++++++++++++++--- src/gsm/libosmogsm.map | 1 + 3 files changed, 24 insertions(+), 5 deletions(-) diff --git a/include/osmocom/crypt/gprs_cipher.h b/include/osmocom/crypt/gprs_cipher.h index 3051071..b6b8e93 100644 --- a/include/osmocom/crypt/gprs_cipher.h +++ b/include/osmocom/crypt/gprs_cipher.h @@ -10,6 +10,7 @@ enum gprs_ciph_algo { GPRS_ALGO_GEA1, GPRS_ALGO_GEA2, GPRS_ALGO_GEA3, + GPRS_ALGO_GEA4, _GPRS_ALGO_NUM }; @@ -28,7 +29,7 @@ struct gprs_cipher_impl { /* As specified in 04.64 Annex A. Uses Kc, IV and direction * to generate the 1523 bytes cipher stream that need to be * XORed wit the plaintext for encrypt / ciphertext for decrypt */ - int (*run)(uint8_t *out, uint16_t len, uint64_t kc, uint32_t iv, + int (*run)(uint8_t *out, uint16_t len, uint8_t *kc, uint32_t iv, enum gprs_cipher_direction direction); }; @@ -40,11 +41,14 @@ int gprs_cipher_load(const char *path); /* function to be called by core code */ int gprs_cipher_run(uint8_t *out, uint16_t len, enum gprs_ciph_algo algo, - uint64_t kc, uint32_t iv, enum gprs_cipher_direction dir); + uint8_t *kc, uint32_t iv, enum gprs_cipher_direction dir); /* Do we have an implementation for this cipher? */ int gprs_cipher_supported(enum gprs_ciph_algo algo); +/* Return key length for supported cipher, in bytes */ +unsigned gprs_cipher_key_length(enum gprs_ciph_algo algo); + /* GSM TS 04.64 / Section A.2.1 : Generation of 'input' */ uint32_t gprs_cipher_gen_input_ui(uint32_t iov_ui, uint8_t sapi, uint32_t lfn, uint32_t oc); diff --git a/src/gsm/gprs_cipher_core.c b/src/gsm/gprs_cipher_core.c index b9a22a1..450272b 100644 --- a/src/gsm/gprs_cipher_core.c +++ b/src/gsm/gprs_cipher_core.c @@ -26,8 +26,8 @@ #include <osmocom/core/utils.h> #include <osmocom/core/linuxlist.h> #include <osmocom/core/plugin.h> - #include <osmocom/crypt/gprs_cipher.h> +#include <osmocom/gsm/gea.h> static LLIST_HEAD(gprs_ciphers); @@ -53,12 +53,14 @@ int gprs_cipher_register(struct gprs_cipher_impl *ciph) int gprs_cipher_load(const char *path) { /* load all plugins available from path */ - return osmo_plugin_load_all(path); + if (path) + return osmo_plugin_load_all(path); + return 0; } /* function to be called by core code */ int gprs_cipher_run(uint8_t *out, uint16_t len, enum gprs_ciph_algo algo, - uint64_t kc, uint32_t iv, enum gprs_cipher_direction dir) + uint8_t *kc, uint32_t iv, enum gprs_cipher_direction dir) { if (algo >= ARRAY_SIZE(selected_ciphers)) return -ERANGE; @@ -73,6 +75,18 @@ int gprs_cipher_run(uint8_t *out, uint16_t len, enum gprs_ciph_algo algo, return selected_ciphers[algo]->run(out, len, kc, iv, dir); } +unsigned gprs_cipher_key_length(enum gprs_ciph_algo algo) +{ + switch (algo) { + case GPRS_ALGO_GEA0: return 0; + case GPRS_ALGO_GEA1: return 8; + case GPRS_ALGO_GEA2: return 8; + case GPRS_ALGO_GEA3: return 8; + case GPRS_ALGO_GEA4: return 16; + default: return 0; + } +} + int gprs_cipher_supported(enum gprs_ciph_algo algo) { if (algo >= ARRAY_SIZE(selected_ciphers)) diff --git a/src/gsm/libosmogsm.map b/src/gsm/libosmogsm.map index 3a4a643..3beb1e9 100644 --- a/src/gsm/libosmogsm.map +++ b/src/gsm/libosmogsm.map @@ -31,6 +31,7 @@ gprs_cipher_load; gprs_cipher_register; gprs_cipher_run; gprs_cipher_supported; +gprs_cipher_key_length; gprs_tlli_type; gprs_tmsi2tlli; -- 1.8.3.2

3 3

Osmovom-BB on Raspberry Pi
by Richard Menedetter 16 Jun '14

16 Jun '14

Hi All Just wanted to confirm that I got Osmocom-BB up and running on a Raspberry Pi. I did not use the GPIO UART pins but USB <-> serial converters. I tried Motorola C118 and C155 with success. Everything you need is already described: http://bb.osmocom.org/trac/wiki/GnuArmToolchain http://bb.osmocom.org/trac/wiki/libosmocore http://bb.osmocom.org/trac/wiki/Software/GettingStarted?redirectedfrom=Gett… My previous problem seems to have been a not fully compatible crosscompiled toolchain. (it worked mostly, but I could not log-in to a cell and the spectrum view crashed on the RSSI Firmware. Also if you want transmit capability (or flashing) then you need to activate those features in the makefile. Thanks Sylvain (confirming c118 will work) and all others who are involved!! PS: Any news on the "emulated BTS" that has been presented at last years chaos communication congress? I have 2 C118s + 1 normal USB serial dongle + 1 capable of burst ind. I hope this will suffice to also run also a possible future 1 trasmit phone + 1 receive phone configuration. I assume that even without the filter change it should be enough to send a few meters of distance.

5 10

about sms lost
by Swift 29 May '14

29 May '14

Hi I lost many sms(sent by myself) using the luca/gsmmap branch with my c118 and cp2102; Could the sylvain/burst_ind branch or other branches fix the problem? Regards, Swift. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/about-sms-lost-tp4026485.html Sent from the baseband-devel mailing list archive at Nabble.com.

1 1

lost sms
by changchuan618＠gmail.com 29 May '14

29 May '14

2 2

lost sms
by Swift 29 May '14

29 May '14

Hi I built the luca/gsmmap branch, and saw many messages in the wireshark with protocol GSM_SMS; but when I tried to capture my sms (sending by my own phone), it does not work, I can not see my sms in wireshark; then I used another phone to send a message to my phone, I saw nothing in wireshark too; Could anyone tell me why? Is it a problem about time slot ? Regards, Swift -------------------------------------------------------------------------------- -- View this message in context: http://baseband-devel.722152.n3.nabble.com/lost-sms-tp4026483.html Sent from the baseband-devel mailing list archive at Nabble.com.

2 1

Manual For VTY interface
by R M 28 May '14

28 May '14

Hi, While browsing through the wiki, I did not find a page for the VTY interface. Does it really not exist or did I miss it ? If it does not exist, I am planning to write one and send it to the mailing list. I have gone through some of the commands while reading the code and I want to share what I have learnt. Regards, RM

2 1

Re: http://bb.osmocom.org/trac/ Why no visit?
by Paul Wise 28 May '14

28 May '14

On Wed, May 28, 2014 at 3:00 PM, Holger Hans Peter Freyther wrote: > which language (simplified chinese?) do you offer to trac. There > were no pending updates for babel/trac. Could you give me the HTTP > request you make? wget --header='Accept-Language: zh-cn,en;q=0.5' http://bb.osmocom.org/trac/ -- bye, pabs http://bonedaddy.net/pabs3/

2 1

http://bb.osmocom.org/trac/ Why no visit?
by warriornew 28 May '14

28 May '14

<http://baseband-devel.722152.n3.nabble.com/file/n4026475/QQ%E6%88%AA%E5%9B%…> Why recently osmocombb website can't visit? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/http-bb-osmocom-org-trac-Why-no-… Sent from the baseband-devel mailing list archive at Nabble.com.

3 2

Bounce action notification
by mailman＠lists.osmocom.org 27 May '14

27 May '14

This is a Mailman mailing list bounce action notice: List: baseband-devel Member: bjoern.riemer(a)fokus.fraunhofer.de 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel May 2014