From Max.Suraev at fairwaves.co Mon Jun 1 13:58:11 2015 From: Max.Suraev at fairwaves.co (=?UTF-8?B?4piO?=) Date: Mon, 01 Jun 2015 15:58:11 +0200 Subject: segfault on bssgp test In-Reply-To: <555F3139.4080206@fairwaves.co> References: <555F3139.4080206@fairwaves.co> Message-ID: <556C64F3.9040301@fairwaves.co> Pardon for multiple copies, but this is really curious: gbprocy test also fails for me during OpenBSC build at gbproxy_test.c:1922 which also contains following misterious comment: /* TODO: The following breaks with the current libosmocore, enable it * again (and remove the plain expect_msg), when the msgb_bssgph patch * is integrated */ What is the status of this "msgb_bssgph patch" patch? Is there patchwork link available? I suspect it's still unmerged because swapping the lines as instructed in comment still results in crash with the latest libosmocore from git. Commenting out both lines produce sane-looking output but the test expectedly fails due to mismatch with expected output. I wonder if should comment out the 2nd line until the libosmocore patch is merged or perhaps consider merging the necessary patch? 22.05.2015 15:38, ? ?????: > Hi. > > Anyone else experienced this with latest libosmocore from git? > > ./testsuite.at:124: $abs_top_builddir/tests/gb/gprs_bssgp_test > stderr: > MESSAGE to 0x7f0000ff, msg length 12 > 02 00 81 01 01 82 0b 56 04 82 0b 55 > All NS-VCs for NSEI 2901 are either dead or blocked! > All NS-VCs for NSEI 2901 are either dead or blocked! > BSSGP BVCI=0 Rx BVC STATUS, cause=Protocol error - unspecified > BSSGP BVCI=1234 Rx BVC STATUS, cause=Unknown BVCI > NSEI=2901/BVCI=2989 Cannot handle PDU type 34 for unknown BVCI, NS BVCI 2989 > Unable to resolve NSEI 4660 to NS-VC! > Assert failed rc >= 0 gb/gprs_bssgp_test.c:229 > /home/user/source/libosmocore/tests/testsuite.dir/at-groups/19/test-source: line 25: > 8497 Aborted (core dumped) $abs_top_builddir/tests/gb/gprs_ > bssgp_test > -- best regards, Max, http://fairwaves.co From max.suraev at fairwaves.co Mon Jun 1 14:11:08 2015 From: max.suraev at fairwaves.co (Max) Date: Mon, 1 Jun 2015 16:11:08 +0200 Subject: [PATCH] ignore .deb build logs Message-ID: <1433167868-7907-1-git-send-email-max.suraev@fairwaves.co> Signed-off-by: Max --- .gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index 24c3af7..56133da 100644 --- a/.gitignore +++ b/.gitignore @@ -41,6 +41,7 @@ debian/tmp/ debian/libosmocore*.substvars debian/libosmocore/ debian/libosmocore.post*.debhelper +debian/*.log .tarball-version .version -- 2.1.4 From max.suraev at fairwaves.co Mon Jun 1 14:24:46 2015 From: max.suraev at fairwaves.co (Max) Date: Mon, 1 Jun 2015 16:24:46 +0200 Subject: [PATCH] Remove osmo_a5_1 and osmo_a5_2 from public API - use generic osmo_a5() instead Message-ID: <1433168686-1229-1-git-send-email-max.suraev@fairwaves.co> Signed-off-by: Max --- TODO-RELEASE | 1 + include/osmocom/gsm/a5.h | 2 - src/gsm/a5.c | 98 ++++++++++++++++++++++++------------------------ src/gsm/libosmogsm.map | 2 - 4 files changed, 49 insertions(+), 54 deletions(-) diff --git a/TODO-RELEASE b/TODO-RELEASE index d03aa49..ddae4c9 100644 --- a/TODO-RELEASE +++ b/TODO-RELEASE @@ -1,2 +1,3 @@ #library what description / commit summary line +libosmogsm api-change remove osmo_a5_1 and osmo_a5_2 - generic osmo_a5 should suffice for all use cases libosmogb abi-change bssgp: Fix bssgp_tx_fc_bvc parameter type diff --git a/include/osmocom/gsm/a5.h b/include/osmocom/gsm/a5.h index d22cdbb..9d12b03 100644 --- a/include/osmocom/gsm/a5.h +++ b/include/osmocom/gsm/a5.h @@ -54,7 +54,5 @@ osmo_a5_fn_count(uint32_t fn) * (converted internally to fn_count) */ int osmo_a5(int n, const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul); -void osmo_a5_1(const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul); -void osmo_a5_2(const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul); /*! @} */ diff --git a/src/gsm/a5.c b/src/gsm/a5.c index d0c7c5f..225ff87 100644 --- a/src/gsm/a5.c +++ b/src/gsm/a5.c @@ -101,54 +101,6 @@ _a5_3(const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul, bool fn_correct) _a5_4(ck, fn, dl, ul, fn_correct); } -/*! \brief Main method to generate a A5/x cipher stream - * \param[in] n Which A5/x method to use - * \param[in] key 8 or 16 (for a5/4) byte array for the key (as received from the SIM) - * \param[in] fn Frame number - * \param[out] dl Pointer to array of ubits to return Downlink cipher stream - * \param[out] ul Pointer to array of ubits to return Uplink cipher stream - * \returns 0 for success, -ENOTSUP for invalid cipher selection. - * - * Currently A5/[0-4] are supported. - * Either (or both) of dl/ul can be NULL if not needed. - */ -int -osmo_a5(int n, const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul) -{ - switch (n) - { - case 0: - if (dl) - memset(dl, 0x00, 114); - if (ul) - memset(ul, 0x00, 114); - break; - - case 1: - osmo_a5_1(key, fn, dl, ul); - break; - - case 2: - osmo_a5_2(key, fn, dl, ul); - break; - - case 3: - _a5_3(key, fn, dl, ul, true); - break; - - case 4: - _a5_4(key, fn, dl, ul, true); - break; - - default: - /* a5/[5..7] not supported here/yet */ - return -ENOTSUP; - } - - return 0; -} - - /* ------------------------------------------------------------------------ */ /* A5/1&2 common stuff */ /* ------------------------------------------------------------------------ */ @@ -261,7 +213,7 @@ _a5_1_get_output(uint32_t r[]) * Either (or both) of dl/ul can be NULL if not needed. */ void -osmo_a5_1(const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul) +_a5_1(const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul) { uint32_t r[3] = {0, 0, 0}; uint32_t fn_count; @@ -378,7 +330,7 @@ _a5_2_get_output(uint32_t r[]) * Either (or both) of dl/ul can be NULL if not needed. */ void -osmo_a5_2(const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul) +_a5_2(const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul) { uint32_t r[4] = {0, 0, 0, 0}; uint32_t fn_count; @@ -437,5 +389,51 @@ osmo_a5_2(const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul) ul[i] = _a5_2_get_output(r); } } +/*! \brief Main method to generate a A5/x cipher stream + * \param[in] n Which A5/x method to use + * \param[in] key 8 or 16 (for a5/4) byte array for the key (as received from the SIM) + * \param[in] fn Frame number + * \param[out] dl Pointer to array of ubits to return Downlink cipher stream + * \param[out] ul Pointer to array of ubits to return Uplink cipher stream + * \returns 0 for success, -ENOTSUP for invalid cipher selection. + * + * Currently A5/[0-4] are supported. + * Either (or both) of dl/ul can be NULL if not needed. + */ +int +osmo_a5(int n, const uint8_t *key, uint32_t fn, ubit_t *dl, ubit_t *ul) +{ + switch (n) + { + case 0: + if (dl) + memset(dl, 0x00, 114); + if (ul) + memset(ul, 0x00, 114); + break; + + case 1: + _a5_1(key, fn, dl, ul); + break; + + case 2: + _a5_2(key, fn, dl, ul); + break; + + case 3: + _a5_3(key, fn, dl, ul, true); + break; + + case 4: + _a5_4(key, fn, dl, ul, true); + break; + + default: + /* a5/[5..7] not supported here/yet */ + return -ENOTSUP; + } + + return 0; +} /*! @} */ diff --git a/src/gsm/libosmogsm.map b/src/gsm/libosmogsm.map index 22428a2..56f33d9 100644 --- a/src/gsm/libosmogsm.map +++ b/src/gsm/libosmogsm.map @@ -201,8 +201,6 @@ ms_pwr_ctl_lvl; ms_pwr_dbm; osmo_a5; -osmo_a5_1; -osmo_a5_2; osmo_auth_alg_name; osmo_auth_alg_parse; -- 2.1.4 From max.suraev at fairwaves.co Mon Jun 1 14:35:56 2015 From: max.suraev at fairwaves.co (Max) Date: Mon, 1 Jun 2015 16:35:56 +0200 Subject: [PATCH] Remove comp128 from public API - use osmocom/crypt/auth.h instead Message-ID: <1433169356-12908-1-git-send-email-max.suraev@fairwaves.co> Signed-off-by: Max --- TODO-RELEASE | 1 + include/Makefile.am | 6 +++--- include/osmocom/gsm/comp128.h | 4 ++-- src/gsm/auth_comp128v1.c | 2 +- src/gsm/comp128.c | 2 +- src/gsm/libosmogsm.map | 1 - tests/comp128/comp128_test.c | 1 - 7 files changed, 8 insertions(+), 9 deletions(-) diff --git a/TODO-RELEASE b/TODO-RELEASE index d03aa49..956b4be 100644 --- a/TODO-RELEASE +++ b/TODO-RELEASE @@ -1,2 +1,3 @@ #library what description / commit summary line +libosmogsm api-change remove comp128 from public API libosmogb abi-change bssgp: Fix bssgp_tx_fc_bvc parameter type diff --git a/include/Makefile.am b/include/Makefile.am index 52c6a38..b4da54e 100644 --- a/include/Makefile.am +++ b/include/Makefile.am @@ -51,8 +51,6 @@ nobase_include_HEADERS = \ osmocom/gsm/a5.h \ osmocom/gsm/abis_nm.h \ osmocom/gsm/apn.h \ - osmocom/gsm/comp128.h \ - osmocom/gsm/comp128v23.h \ osmocom/gsm/gan.h \ osmocom/gsm/gsm0341.h \ osmocom/gsm/gsm0411_smc.h \ @@ -121,7 +119,9 @@ endif noinst_HEADERS = \ osmocom/core/timer_compat.h \ - osmocom/gsm/kasumi.h + osmocom/gsm/kasumi.h \ + osmocom/gsm/comp128.h \ + osmocom/gsm/comp128v23.h osmocom/core/bit%gen.h: osmocom/core/bitXXgen.h.tpl $(AM_V_GEN)$(MKDIR_P) $(dir $@) diff --git a/include/osmocom/gsm/comp128.h b/include/osmocom/gsm/comp128.h index 33b997a..c45da37 100644 --- a/include/osmocom/gsm/comp128.h +++ b/include/osmocom/gsm/comp128.h @@ -9,10 +9,10 @@ #include /* - * Performs the COMP128 algorithm (used as A3/A8) + * Performs the COMP128v1 algorithm (used as A3/A8) * ki : uint8_t [16] * srand : uint8_t [16] * sres : uint8_t [4] * kc : uint8_t [8] */ -void comp128(const uint8_t *ki, const uint8_t *srand, uint8_t *sres, uint8_t *kc); +void comp128v1(const uint8_t *ki, const uint8_t *srand, uint8_t *sres, uint8_t *kc); diff --git a/src/gsm/auth_comp128v1.c b/src/gsm/auth_comp128v1.c index 41aef71..c40027e 100644 --- a/src/gsm/auth_comp128v1.c +++ b/src/gsm/auth_comp128v1.c @@ -28,7 +28,7 @@ static int c128v1_gen_vec(struct osmo_auth_vector *vec, struct osmo_sub_auth_data *aud, const uint8_t *_rand) { - comp128(aud->u.gsm.ki, _rand, vec->sres, vec->kc); + comp128v1(aud->u.gsm.ki, _rand, vec->sres, vec->kc); vec->auth_types = OSMO_AUTH_TYPE_GSM; return 0; diff --git a/src/gsm/comp128.c b/src/gsm/comp128.c index b7a2382..e36c20d 100644 --- a/src/gsm/comp128.c +++ b/src/gsm/comp128.c @@ -185,7 +185,7 @@ _comp128_permutation(uint8_t *x, uint8_t *bits) } void -comp128(const uint8_t *ki, const uint8_t *rand, uint8_t *sres, uint8_t *kc) +comp128v1(const uint8_t *ki, const uint8_t *rand, uint8_t *sres, uint8_t *kc) { int i; uint8_t x[32], bits[128]; diff --git a/src/gsm/libosmogsm.map b/src/gsm/libosmogsm.map index 22428a2..c80c15f 100644 --- a/src/gsm/libosmogsm.map +++ b/src/gsm/libosmogsm.map @@ -26,7 +26,6 @@ abis_nm_ipa_magic; osmo_sitype_strs; -comp128; dbm2rxlev; gprs_cipher_gen_input_i; diff --git a/tests/comp128/comp128_test.c b/tests/comp128/comp128_test.c index eb6fb12..d6a6401 100644 --- a/tests/comp128/comp128_test.c +++ b/tests/comp128/comp128_test.c @@ -6,7 +6,6 @@ #include #include -#include #include static struct osmo_sub_auth_data test_aux2 = { -- 2.1.4 From craig_comstock at yahoo.com Mon Jun 1 17:48:37 2015 From: craig_comstock at yahoo.com (Craig Comstock) Date: Mon, 1 Jun 2015 17:48:37 +0000 (UTC) Subject: bad crc 9bf1 References: <1432662358.953069542@f314.i.mail.ru> Message-ID: Alexander list.ru> writes: > > > Hello > Biggest thanks for the osmocombb project! > ? > I am trying to follow this wikki http://bb.osmocom.org/trac/wiki/flashing_new? to flash rssi app > ? > And facing this error > host/osmocon/osmoload fprogram 0 0x010000 compal_loader.bin > Loading 8192 bytes of memory at 0x10000 in chip 0 from file compal_loader.bin > bad crc 9bf1 (not 4190) at offset 0x00000000 > status 69206016, aborting > ? > How to solve it? > ? > I use latest jolly/menu git branch > HW: C115 and c113 ( e88) ?both providing same error > -- Sincerely, Alexander. > Are you on the latest code? I have had this problem before and think it is either due to stale code or host architecture. In the past I think there was a problem with running osmoload on 32-bit versus 64-bit hosts in computing the CRC. Search the mail archives, there is some talk about it there. From alexandr_x at list.ru Mon Jun 1 19:32:50 2015 From: alexandr_x at list.ru (=?UTF-8?B?QWxleGFuZGVy?=) Date: Mon, 01 Jun 2015 22:32:50 +0300 Subject: =?UTF-8?B?UmVbMl06IGJhZCBjcmMgOWJmMQ==?= In-Reply-To: References: <1432662358.953069542@f314.i.mail.ru> Message-ID: <1433187170.934898964@f376.i.mail.ru> Thank you for the reply. I have solved the problem. (Installed Debian 6 i386) ???????????, 1 ???? 2015, 17:48 UTC ?? Craig Comstock : >Alexander list.ru> writes: > >> >> >> Hello >> Biggest thanks for the osmocombb project! >> ? >> I am trying to follow this wikki >http://bb.osmocom.org/trac/wiki/flashing_new to flash rssi app >> ? >> And facing this error >> host/osmocon/osmoload fprogram 0 0x010000 compal_loader.bin >> Loading 8192 bytes of memory at 0x10000 in chip 0 from file compal_loader.bin >> bad crc 9bf1 (not 4190) at offset 0x00000000 >> status 69206016, aborting >> ? >> How to solve it? >> ? >> I use latest jolly/menu git branch >> HW: C115 and c113 ( e88) ?both providing same error >> -- Sincerely, Alexander. >> > >Are you on the latest code? I have had this problem before and think it is >either due to stale code or host architecture. In the past I think there was >a problem with running osmoload on 32-bit versus 64-bit hosts in computing >the CRC. Search the mail archives, there is some talk about it there. -- Sincerely, Alexander. -------------- next part -------------- An HTML attachment was scrubbed... URL: From radiarisainanasitraka at yahoo.fr Mon Jun 1 19:43:14 2015 From: radiarisainanasitraka at yahoo.fr (Dast) Date: Mon, 1 Jun 2015 12:43:14 -0700 (MST) Subject: Python Code Message-ID: <1433187794493-4026716.post@n3.nabble.com> I would really realize the project by Sylvain Minaut but my problem is that i can't find a script python consist to switch with another phone . ispy = identityspy(number, imsi); and ispy._apisms ?? Could someone help me please? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Python-Code-tp4026716.html Sent from the baseband-devel mailing list archive at Nabble.com. From francoip at stud.ntnu.no Tue Jun 2 14:37:25 2015 From: francoip at stud.ntnu.no (=?UTF-8?B?RnJhbsOnb2lzIFDDtm5zZ2Vu?=) Date: Tue, 2 Jun 2015 16:37:25 +0200 Subject: Master thesis feedback Message-ID: <20150602163725.3da0df48@ferdinand> Hello list, I'm writing a master thesis on: "GSM and GPRS security using OsmocomBB". The goal of this thesis is to describe the various attacks made possible by the project, and to analyze their impact on Norwegian networks. I finally have an almost complete draft for all the chapters: the chapters 2 and 3 introduce the necessary background, chapter 4 describes the eavesdropping attack, chapter 5 describes various DoS attacks, and finally chapter 6 analyzes their impact on Norwegian networks. I'm looking for feedback on this thesis, and I thought that the topic might interest subscribers of this mailing list! I would really appreciate any constructive criticism on this report, so if you have any please do not hesitate to contact me. The deadline is on the 8th of June, in one week, so there is not much time left. The thesis is available here: https://gitlab.com/francoip/thesis/blob/public/thesis.pdf Thanks a lot, Fran?ois P?nsgen From holger at freyther.de Tue Jun 2 19:07:30 2015 From: holger at freyther.de (Holger Freyther) Date: Tue, 2 Jun 2015 21:07:30 +0200 Subject: Master thesis feedback In-Reply-To: <20150602163725.3da0df48@ferdinand> References: <20150602163725.3da0df48@ferdinand> Message-ID: > On 02 Jun 2015, at 16:37, Fran?ois P?nsgen wrote: > > Hello list, Hi! interesting read and bonus points for not using github and making the source available! holger From francoip at stud.ntnu.no Wed Jun 3 11:33:34 2015 From: francoip at stud.ntnu.no (=?UTF-8?B?RnJhbsOnb2lzIFDDtm5zZ2Vu?=) Date: Wed, 3 Jun 2015 13:33:34 +0200 Subject: Master thesis feedback In-Reply-To: References: <20150602163725.3da0df48@ferdinand> Message-ID: <20150603133334.512eae29@ferdinand> On Tue, 2 Jun 2015 21:07:30 +0200 Holger Freyther wrote: > > > On 02 Jun 2015, at 16:37, Fran?ois P?nsgen > > wrote: > > > > Hello list, > > Hi! > > interesting read and bonus points for not using github and making the > source available! > > holger Hello, Thanks for the feedback! Fran?ois From max.suraev at fairwaves.co Fri Jun 5 11:44:19 2015 From: max.suraev at fairwaves.co (Max) Date: Fri, 5 Jun 2015 13:44:19 +0200 Subject: [PATCH] Fix automake warnings Message-ID: <1433504659-10382-1-git-send-email-max.suraev@fairwaves.co> Signed-off-by: Max --- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index acd153d..11c82a9 100644 --- a/configure.ac +++ b/configure.ac @@ -2,7 +2,7 @@ AC_INIT([libosmocore], m4_esyscmd([./git-version-gen .tarball-version]), [openbsc at lists.osmocom.org]) -AM_INIT_AUTOMAKE([foreign dist-bzip2 no-dist-gzip 1.6]) +AM_INIT_AUTOMAKE([foreign subdir-objects dist-bzip2 no-dist-gzip 1.6]) AC_CONFIG_TESTDIR(tests) dnl kernel style compile messages -- 2.1.4 From Max.Suraev at fairwaves.co Fri Jun 5 13:07:48 2015 From: Max.Suraev at fairwaves.co (=?UTF-8?B?4piO?=) Date: Fri, 05 Jun 2015 15:07:48 +0200 Subject: segfault on bssgp test In-Reply-To: <556C64F3.9040301@fairwaves.co> References: <555F3139.4080206@fairwaves.co> <556C64F3.9040301@fairwaves.co> Message-ID: <55719F24.3050000@fairwaves.co> Another person reproduced this on ubuntu 15.04 x86_64. Have anyone else hit it recently? 01.06.2015 15:58, ? ?????: > Pardon for multiple copies, but this is really curious: gbprocy test also fails for > me during OpenBSC build at gbproxy_test.c:1922 which also contains following > misterious comment: > > /* TODO: The following breaks with the current libosmocore, enable it > * again (and remove the plain expect_msg), when the msgb_bssgph patch > * is integrated */ > > What is the status of this "msgb_bssgph patch" patch? Is there patchwork link available? > > I suspect it's still unmerged because swapping the lines as instructed in comment > still results in crash with the latest libosmocore from git. > > Commenting out both lines produce sane-looking output but the test expectedly fails > due to mismatch with expected output. > > I wonder if should comment out the 2nd line until the libosmocore patch is merged or > perhaps consider merging the necessary patch? > > 22.05.2015 15:38, ? ?????: >> Hi. >> >> Anyone else experienced this with latest libosmocore from git? >> >> ./testsuite.at:124: $abs_top_builddir/tests/gb/gprs_bssgp_test >> stderr: >> MESSAGE to 0x7f0000ff, msg length 12 >> 02 00 81 01 01 82 0b 56 04 82 0b 55 >> All NS-VCs for NSEI 2901 are either dead or blocked! >> All NS-VCs for NSEI 2901 are either dead or blocked! >> BSSGP BVCI=0 Rx BVC STATUS, cause=Protocol error - unspecified >> BSSGP BVCI=1234 Rx BVC STATUS, cause=Unknown BVCI >> NSEI=2901/BVCI=2989 Cannot handle PDU type 34 for unknown BVCI, NS BVCI 2989 >> Unable to resolve NSEI 4660 to NS-VC! >> Assert failed rc >= 0 gb/gprs_bssgp_test.c:229 >> /home/user/source/libosmocore/tests/testsuite.dir/at-groups/19/test-source: line 25: >> 8497 Aborted (core dumped) $abs_top_builddir/tests/gb/gprs_ >> bssgp_test >> > > -- best regards, Max, http://fairwaves.co From holger at freyther.de Fri Jun 5 15:36:37 2015 From: holger at freyther.de (Holger Freyther) Date: Fri, 5 Jun 2015 17:36:37 +0200 Subject: segfault on bssgp test In-Reply-To: <55719F24.3050000@fairwaves.co> References: <555F3139.4080206@fairwaves.co> <556C64F3.9040301@fairwaves.co> <55719F24.3050000@fairwaves.co> Message-ID: > On 05 Jun 2015, at 15:07, ? wrote: > > Another person reproduced this on ubuntu 15.04 x86_64. Have anyone else hit it recently? https://build.opensuse.org/package/live_build_log/home:zecke23:stp/libosmocore/xUbuntu_14.04/i586 hits something like this too. Try to understand the difference between debian and the ubuntu toolchain. E.g. does the overload of ?sendto? work with the gold linker? From Max.Suraev at fairwaves.co Fri Jun 5 16:05:30 2015 From: Max.Suraev at fairwaves.co (=?UTF-8?B?4piO?=) Date: Fri, 05 Jun 2015 18:05:30 +0200 Subject: segfault on bssgp test In-Reply-To: References: <555F3139.4080206@fairwaves.co> <556C64F3.9040301@fairwaves.co> <55719F24.3050000@fairwaves.co> Message-ID: <5571C8CA.4030408@fairwaves.co> 05.06.2015 17:36, Holger Freyther ?????: > >> On 05 Jun 2015, at 15:07, ? wrote: >> >> Another person reproduced this on ubuntu 15.04 x86_64. Have anyone else hit it recently? > > > https://build.opensuse.org/package/live_build_log/home:zecke23:stp/libosmocore/xUbuntu_14.04/i586 > > hits something like this too. Try to understand the difference between debian > and the ubuntu toolchain. E.g. does the overload of ?sendto? work with the gold > linker? > Hmm.. so it works on Debian but not on Ubuntu? How do I check if gold is used as linker? -- best regards, Max, http://fairwaves.co From holger at freyther.de Fri Jun 5 16:19:33 2015 From: holger at freyther.de (Holger Freyther) Date: Fri, 5 Jun 2015 18:19:33 +0200 Subject: segfault on bssgp test In-Reply-To: <5571C8CA.4030408@fairwaves.co> References: <555F3139.4080206@fairwaves.co> <556C64F3.9040301@fairwaves.co> <55719F24.3050000@fairwaves.co> <5571C8CA.4030408@fairwaves.co> Message-ID: > On 05 Jun 2015, at 18:05, ? wrote: >> > > Hmm.. so it works on Debian but not on Ubuntu? How do I check if gold is used as linker? it is not only gold. My first suspicion would be to put a break point in sendto and see which is executed (the system one or the overload) From craig_comstock at yahoo.com Tue Jun 16 03:46:38 2015 From: craig_comstock at yahoo.com (Craig Comstock) Date: Tue, 16 Jun 2015 03:46:38 +0000 (UTC) Subject: c113a works Message-ID: <745238402.3654979.1434426398440.JavaMail.yahoo@mail.yahoo.com> FWIW, someone asked me whether c113 worked. I found a cheap 113a and hello_world loaded pretty well. The screen on my phone is shot but the backlight did come on.it works fine with the following command: craig at craig:~/c115-osmocom-bb/src$ host/osmocon/osmocon -p /dev/ttyUSB0 -m c123xor target/firmware/board/compal_e88/hello_world.compalram.bin? OsmocomBB Hello World (revision osmocon_v0.0.0-1754-gfc20a37) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: c5c63637a5039778 ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== entering interrupt loop -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Tue Jun 16 05:28:43 2015 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 16 Jun 2015 07:28:43 +0200 Subject: c113a works In-Reply-To: <745238402.3654979.1434426398440.JavaMail.yahoo@mail.yahoo.com> References: <745238402.3654979.1434426398440.JavaMail.yahoo@mail.yahoo.com> Message-ID: Good to know. Do you know if the hw is exactly the same as the c123 ? Cheers, Sylvain From alexandr_x at list.ru Tue Jun 16 17:51:33 2015 From: alexandr_x at list.ru (=?UTF-8?B?QWxleGFuZGVy?=) Date: Tue, 16 Jun 2015 20:51:33 +0300 Subject: =?UTF-8?B?UmVbMl06IGMxMTNhIHdvcmtz?= In-Reply-To: References: <745238402.3654979.1434426398440.JavaMail.yahoo@mail.yahoo.com> Message-ID: <1434477093.882532335@f237.i.mail.ru> i have c113a and c115 both works perfectly with bb. c113a? hw is?exactly same as the c115 http://bb.osmocom.org/trac/wiki/MotorolaC115. it is e87 but works fine with bb software as e88 c123 ???????, 16 ???? 2015, 7:28 +02:00 ?? Sylvain Munaut <246tnt at gmail.com>: >Good to know. > >Do you know if the hw is exactly the same as the c123 ? > >Cheers, > >???Sylvain -- Sincerely, Alexander. -------------- next part -------------- An HTML attachment was scrubbed... URL: From baumi525 at googlemail.com Tue Jun 23 20:26:01 2015 From: baumi525 at googlemail.com (Tobias XY) Date: Tue, 23 Jun 2015 22:26:01 +0200 Subject: Beginning with a Motorola C121 or C139 Message-ID: Hello list, i?m new here and i want to begin with the project osmocom on the Motorola C121 or C139. I have both mobile phones here and the USB to TTL Plug with the cable. How can i start now. Is there a tutorial? Greetings, Tobi -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierce403 at gmail.com Tue Jun 23 22:20:05 2015 From: pierce403 at gmail.com (Dean Pierce) Date: Tue, 23 Jun 2015 15:20:05 -0700 Subject: Beginning with a Motorola C121 or C139 In-Reply-To: References: Message-ID: Hey Tobi, I made a boot image that might help. https://mega.co.nz/#!uFIzxLxA!Bx-oMpZkKT_M3JEEruN5gzgGEhy_pkGmhp0uZWh9kjI It's essentially Kali with all the osmocom tools set up and good to go. All the scripts are built for a C139. Take a 16+ gig USB stick, and bunzip TWILIGHTVEGETABLE-1.0.img.bz2 > /dec/sdd (or whatever your USB stick is) Once you boot, plug in the phone, run ./rssi.sh to run the rssi app described here: https://bb.osmocom.org/trac/wiki/rssi.bin - DEAN On Tue, Jun 23, 2015 at 1:26 PM, Tobias XY wrote: > Hello list, > > i?m new here and i want to begin with the project osmocom on the Motorola > C121 or C139. I have both mobile phones here and the USB to TTL Plug with > the cable. How can i start now. Is there a tutorial? > > Greetings, > Tobi From pierce403 at gmail.com Tue Jun 23 22:21:04 2015 From: pierce403 at gmail.com (Dean Pierce) Date: Tue, 23 Jun 2015 15:21:04 -0700 Subject: Beginning with a Motorola C121 or C139 In-Reply-To: References: Message-ID: Also, when you boot the stick, make sure to boot to "persistent mode" so all the tools are there. - DEAN On Tue, Jun 23, 2015 at 3:20 PM, Dean Pierce wrote: > Hey Tobi, I made a boot image that might help. > https://mega.co.nz/#!uFIzxLxA!Bx-oMpZkKT_M3JEEruN5gzgGEhy_pkGmhp0uZWh9kjI > > It's essentially Kali with all the osmocom tools set up and good to > go. All the scripts are built for a C139. > Take a 16+ gig USB stick, and bunzip TWILIGHTVEGETABLE-1.0.img.bz2 > > /dec/sdd (or whatever your USB stick is) > > Once you boot, plug in the phone, run ./rssi.sh to run the rssi app > described here: > https://bb.osmocom.org/trac/wiki/rssi.bin > > - DEAN > > On Tue, Jun 23, 2015 at 1:26 PM, Tobias XY wrote: >> Hello list, >> >> i?m new here and i want to begin with the project osmocom on the Motorola >> C121 or C139. I have both mobile phones here and the USB to TTL Plug with >> the cable. How can i start now. Is there a tutorial? >> >> Greetings, >> Tobi From craig_comstock at yahoo.com Wed Jun 24 01:30:16 2015 From: craig_comstock at yahoo.com (Craig Comstock) Date: Wed, 24 Jun 2015 01:30:16 +0000 (UTC) Subject: Beginning with a Motorola C121 or C139 In-Reply-To: References: Message-ID: <833517740.3938.1435109416880.JavaMail.yahoo@mail.yahoo.com> It is also not too hard to follow the instructions here: http://bb.osmocom.org/trac/wiki/Software/GettingStarted summarized:- install some packages via your linux distribution- get, build and install libosmocore- build a gnu arm toolchain- get, build and use osmocom-bb firmware and tools A good list of hardware and their quirks is here: http://bb.osmocom.org/trac/wiki/Hardware/Phones -Craig From: Dean Pierce To: Tobias XY Cc: baseband-devel at lists.osmocom.org Sent: Tuesday, June 23, 2015 5:21 PM Subject: Re: Beginning with a Motorola C121 or C139 Also, when you boot the stick, make sure to boot to "persistent mode" so all the tools are there. ? - DEAN On Tue, Jun 23, 2015 at 3:20 PM, Dean Pierce wrote: > Hey Tobi, I made a boot image that might help. > https://mega.co.nz/#!uFIzxLxA!Bx-oMpZkKT_M3JEEruN5gzgGEhy_pkGmhp0uZWh9kjI > > It's essentially Kali with all the osmocom tools set up and good to > go.? All the scripts are built for a C139. > Take a 16+ gig USB stick, and? bunzip TWILIGHTVEGETABLE-1.0.img.bz2 > > /dec/sdd? (or whatever your USB stick is) > > Once you boot, plug in the phone, run? ./rssi.sh? to run the rssi app > described here: > https://bb.osmocom.org/trac/wiki/rssi.bin > >? - DEAN > > On Tue, Jun 23, 2015 at 1:26 PM, Tobias XY wrote: >> Hello list, >> >> i?m new here and i want to begin with the project osmocom on the Motorola >> C121 or C139. I have both mobile phones here and the USB to TTL Plug with >> the cable. How can i start now. Is there a tutorial? >> >> Greetings, >> Tobi -------------- next part -------------- An HTML attachment was scrubbed... URL: