From akibsayyed at gmail.com Sat Feb 23 16:06:56 2013 From: akibsayyed at gmail.com (Akib Sayyed) Date: Sat, 23 Feb 2013 19:06:56 +0300 Subject: is the Viterbi decode for the AFS provided by Sylvain right? In-Reply-To: References: <1343292447286-4025236.post@n3.nabble.com> Message-ID: Dear Sylvain In code provided above there is no *conv_tch_afs_XX_XX_next_term_state* &* conv_tch_afs_10_2_next_term_state*struct for some of bitrate so its giving wrong output for convolution decode. is it possible to give complete conv_tch_afs.c decode. On Thu, Jul 26, 2012 at 12:23 PM, Sylvain Munaut <246tnt at gmail.com> wrote: > > search some materials, find that the decode method of AFS convolutional > > code is different from the EFS`, it use RSC, and need SOVA(soft output > > viterbi algorithm). am i right? > > No. > > It _does_ use RSC (and the viterbi code in libosmocore supports RSC). > But that has nothing to do with SOVA and SOVA is _not_ required at > all. > > AFAIK, the AMR code I sent a while is correct. Just to be sure I > attached the latest version I have. I haven't tested all the modes but > at least 12.2 and 10.2 should be correct. > > Cheers, > > Sylvain > -- Akib Sayyed Matrix-Shell akibsayyed at gmail.com akibsayyed at matrixshell.com Mob:- +91-966-514-2243 -------------- next part -------------- An HTML attachment was scrubbed... URL: From peter at stuge.se Sat Feb 23 17:04:41 2013 From: peter at stuge.se (Peter Stuge) Date: Sat, 23 Feb 2013 18:04:41 +0100 Subject: is the Viterbi decode for the AFS provided by Sylvain right? In-Reply-To: References: <1343292447286-4025236.post@n3.nabble.com> Message-ID: <20130223170441.20313.qmail@stuge.se> Akib Sayyed wrote: > In code provided above there is no > *conv_tch_afs_XX_XX_next_term_state* &* > conv_tch_afs_10_2_next_term_state*struct for some of bitrate Ohnoes! Maybe you have to do some coding in order to use it. //Peter From zero-kelvin at gmx.de Sun Feb 3 20:50:49 2013 From: zero-kelvin at gmx.de (dexter) Date: Sun, 03 Feb 2013 21:50:49 +0100 Subject: Osmocom Berlin User Group meeting In-Reply-To: <20120818115942.GV29525@prithivi.gnumonks.org> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> Message-ID: <510ECDA9.6050009@gmx.de> Hi folks. This is the announcement for the next Osmocom Berlin meeting. Feb 6, 8pm @ CCC Berlin, Marienstr. 11, 10117 Berlin There is no formal presentation scheduled for this meeting. If you are interested to show up, feel free to do so. There is no registration required. The meeting is free as in "free beer", despite no actual free beer being around. Regards, Philipp Maier From zero-kelvin at gmx.de Tue Feb 19 18:08:42 2013 From: zero-kelvin at gmx.de (dexter) Date: Tue, 19 Feb 2013 19:08:42 +0100 Subject: Osmocom Berlin User Group meeting In-Reply-To: <20120818115942.GV29525@prithivi.gnumonks.org> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> Message-ID: <5123BFAA.4090602@gmx.de> Hi folks. This is the announcement for the next Osmocom Berlin meeting. Feb 20, 8pm @ CCC Berlin, Marienstr. 11, 10117 Berlin There is no formal presentation scheduled for this meeting. If you are interested to show up, feel free to do so. There is no registration required. The meeting is free as in "free beer", despite no actual free beer being around. Regards, Philipp Maier From niceguy108 at gmail.com Fri Feb 1 05:12:02 2013 From: niceguy108 at gmail.com (Bhaskar11) Date: Fri, 1 Feb 2013 10:42:02 +0530 Subject: Structure of traffic data in burst_ind messages In-Reply-To: <1359644928095-4025787.post@n3.nabble.com> References: <1359644928095-4025787.post@n3.nabble.com> Message-ID: Yes, I send the command l1ctl_tx_fbsb_req(ms, ms->test_arfcn, L1CTL_FBSB_F_FB0 | L1CTL_FBSB_F_SB, 100, 0, app_state.ccch_mode, dbm2rxlev(-85)); before switching channels. Now most of the channels stick on for much longer, but a few drop within seconds. But I cannot know for sure if this has "worked" until I can decode and recognise some FACCH commands. On AMR HR I get data like: TCH/H (hl=0, hu=0) in FN=1864368 DL SACCH Detected FACCH (hl=1, hu=0) in FN=1864369 DL Detected FACCH (hl=1, hu=0) in FN=1864371 DL Detected FACCH (hl=1, hu=1) in FN=1864373 DL Detected FACCH (hl=1, hu=1) in FN=1864375 DL Detected FACCH (hl=1, hu=1) in FN=1864386 DL Detected FACCH (hl=1, hu=1) in FN=1864388 DL Detected FACCH (hl=1, hu=1) in FN=1864390 DL Detected FACCH (hl=1, hu=1) in FN=1864392 DL TCH/H (hl=0, hu=0) in FN=1864394 DL SACCH Detected FACCH (hl=1, hu=1) in FN=1864395 DL Detected FACCH (hl=1, hu=1) in FN=1864397 DL Detected FACCH (hl=1, hu=1) in FN=1864399 DL Detected FACCH (hl=1, hu=0) in FN=1864401 DL Detected FACCH (hl=1, hu=1) in FN=1864403 DL Detected FACCH (hl=1, hu=0) in FN=1864405 DL Detected FACCH (hl=1, hu=1) in FN=1864408 DL Detected FACCH (hl=1, hu=0) in FN=1864410 DL TCH/H (hl=0, hu=0) in FN=1864420 DL SACCH which does not look correct because I think the FACCH should be in groups of 4. Any explanations? Suggestions? B. On Thu, Jan 31, 2013 at 8:38 PM, Pe wrote: > Hi, Bhaskar11 > Did you resolve problem with low snr? > Do you make synchronization on SCH before going to TCH, after Assignment > Command? > > > > -- > View this message in context: > http://baseband-devel.722152.n3.nabble.com/Structure-of-traffic-data-in-burst-ind-messages-tp4025762p4025787.html > Sent from the baseband-devel mailing list archive at Nabble.com. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From niceguy108 at gmail.com Fri Feb 1 20:10:05 2013 From: niceguy108 at gmail.com (Bhaskar11) Date: Sat, 2 Feb 2013 01:40:05 +0530 Subject: Structure of traffic data in burst_ind messages In-Reply-To: References: <1359644928095-4025787.post@n3.nabble.com> Message-ID: Looks like the problem is because of DTX because the FACCH bursts vanish during speech and return during pause. Anyone has experience with DTX? B. On Fri, Feb 1, 2013 at 10:42 AM, Bhaskar11 wrote: > Yes, I send the command > l1ctl_tx_fbsb_req(ms, ms->test_arfcn, > L1CTL_FBSB_F_FB0 | L1CTL_FBSB_F_SB, 100, 0, > app_state.ccch_mode, dbm2rxlev(-85)); > before switching channels. > > Now most of the channels stick on for much longer, but a few drop within > seconds. > > But I cannot know for sure if this has "worked" until I can decode and > recognise some FACCH commands. > > On AMR HR I get data like: > > TCH/H (hl=0, hu=0) in FN=1864368 DL SACCH > Detected FACCH (hl=1, hu=0) in FN=1864369 DL > Detected FACCH (hl=1, hu=0) in FN=1864371 DL > Detected FACCH (hl=1, hu=1) in FN=1864373 DL > Detected FACCH (hl=1, hu=1) in FN=1864375 DL > Detected FACCH (hl=1, hu=1) in FN=1864386 DL > Detected FACCH (hl=1, hu=1) in FN=1864388 DL > Detected FACCH (hl=1, hu=1) in FN=1864390 DL > Detected FACCH (hl=1, hu=1) in FN=1864392 DL > TCH/H (hl=0, hu=0) in FN=1864394 DL SACCH > Detected FACCH (hl=1, hu=1) in FN=1864395 DL > Detected FACCH (hl=1, hu=1) in FN=1864397 DL > Detected FACCH (hl=1, hu=1) in FN=1864399 DL > Detected FACCH (hl=1, hu=0) in FN=1864401 DL > Detected FACCH (hl=1, hu=1) in FN=1864403 DL > Detected FACCH (hl=1, hu=0) in FN=1864405 DL > Detected FACCH (hl=1, hu=1) in FN=1864408 DL > Detected FACCH (hl=1, hu=0) in FN=1864410 DL > TCH/H (hl=0, hu=0) in FN=1864420 DL SACCH > > which does not look correct because I think the FACCH should be in groups > of 4. > > Any explanations? Suggestions? > > B. > > > On Thu, Jan 31, 2013 at 8:38 PM, Pe wrote: > >> Hi, Bhaskar11 >> Did you resolve problem with low snr? >> Do you make synchronization on SCH before going to TCH, after Assignment >> Command? >> >> >> >> -- >> View this message in context: >> http://baseband-devel.722152.n3.nabble.com/Structure-of-traffic-data-in-burst-ind-messages-tp4025762p4025787.html >> Sent from the baseband-devel mailing list archive at Nabble.com. >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From oxccoxcc at yandex.ru Tue Feb 12 12:16:57 2013 From: oxccoxcc at yandex.ru (Pe) Date: Tue, 12 Feb 2013 04:16:57 -0800 (PST) Subject: Structure of traffic data in burst_ind messages In-Reply-To: References: <1359644928095-4025787.post@n3.nabble.com> Message-ID: <1360671417865-4025826.post@n3.nabble.com> Hi, Bhaskar I have the same problem with periodical channel dropping from snr 255 to snr less then 10. It is not because of DTX, as i think. May be it is because of handovers, but dropping is too often. I did not use FACCH information yet. Can you get a reference to document with facch decoding scheme? google didnt help. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Structure-of-traffic-data-in-burst-ind-messages-tp4025762p4025826.html Sent from the baseband-devel mailing list archive at Nabble.com. From niceguy108 at gmail.com Tue Feb 12 13:37:58 2013 From: niceguy108 at gmail.com (Bhaskar11) Date: Tue, 12 Feb 2013 19:07:58 +0530 Subject: Structure of traffic data in burst_ind messages In-Reply-To: <1360671417865-4025826.post@n3.nabble.com> References: <1359644928095-4025787.post@n3.nabble.com> <1360671417865-4025826.post@n3.nabble.com> Message-ID: You can know if it is DTX by checking for SID messages before it drops and before it resumes. A simple way to check if it is DTX is to watch SNR level during speech/pause. If you are *not* using AMR, then you can check signal strength only for the mandatory frames which are listed in TS 05.08 / 8.3. FACCH specs will be in TS 05.03. But AFAIK it will not help for this purpose. You cannot Google these things. You will have to read the specs from the 3GPP website http://www.3gpp.org/specification-numbering B On Tue, Feb 12, 2013 at 5:46 PM, Pe wrote: > Hi, Bhaskar > I have the same problem with periodical channel dropping from snr 255 to > snr > less then 10. It is not because of DTX, as i think. May be it is because of > handovers, but dropping is too often. > I did not use FACCH information yet. > Can you get a reference to document with facch decoding scheme? google > didnt > help. > > > > -- > View this message in context: > http://baseband-devel.722152.n3.nabble.com/Structure-of-traffic-data-in-burst-ind-messages-tp4025762p4025826.html > Sent from the baseband-devel mailing list archive at Nabble.com. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From qiuhan1989 at gmail.com Fri Feb 1 11:00:33 2013 From: qiuhan1989 at gmail.com (qiuhan1989) Date: Fri, 1 Feb 2013 03:00:33 -0800 (PST) Subject: Problems about analysis of content in memory Message-ID: <1359716433918-4025791.post@n3.nabble.com> I tried to dump some parts of memory using osmoload. Here is my problem, When I tried to dump from 0x0, there is a piece of memory filled up with "f". I guess maybe it's ROM and when I call the memcpy in RAM, I actually cannot read things in ROM. Can anyone confirm my guess? Then I found there is a memory protection unit (ti-calypso2.pdf). Then I dumped the values from FFFF FF00 (registers of MPU), I got all zeros... Does this mean there is no memory protection active? Or maybe because actually the phone is not turned on. So there would be some flash which don't have electricity on... Anyone can help me? Thank you in advance. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Problems-about-analysis-of-content-in-memory-tp4025791.html Sent from the baseband-devel mailing list archive at Nabble.com. From wsmd78 at gmail.com Sat Feb 2 13:41:50 2013 From: wsmd78 at gmail.com (shrek wu) Date: Sat, 2 Feb 2013 21:41:50 +0800 Subject: windows pc tool Message-ID: hi burney help me to see ot best regards shrek wu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PC???????development.ppt Type: application/vnd.ms-powerpoint Size: 2742272 bytes Desc: not available URL: From qiuhan1989 at gmail.com Sat Feb 2 15:56:33 2013 From: qiuhan1989 at gmail.com (qiuhan1989) Date: Sat, 2 Feb 2013 07:56:33 -0800 (PST) Subject: windows pc tool In-Reply-To: References: Message-ID: <1359820593046-4025795.post@n3.nabble.com> This is Chinese. What do you want for this slides? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/windows-pc-tool-tp4025794p4025795.html Sent from the baseband-devel mailing list archive at Nabble.com. From tyruskam at gmail.com Mon Feb 4 19:48:32 2013 From: tyruskam at gmail.com (ty) Date: Mon, 4 Feb 2013 22:48:32 +0300 Subject: Anyone tried this board Message-ID: Came across this neat implementation. Havent had a chance to use it. Wanted to know if anyone has given it a try http://www.kickstarter.com/projects/1085541682/bladerf-usb-30-software-defined-radio?ref=live -tyrus -------------- next part -------------- An HTML attachment was scrubbed... URL: From niceguy108 at gmail.com Tue Feb 5 05:27:32 2013 From: niceguy108 at gmail.com (Bhaskar11) Date: Tue, 5 Feb 2013 10:57:32 +0530 Subject: Content of burst data in burst_ind branch Message-ID: Can you please clarify what kind of preprocessing has been done for bursts in burst_ind data? Does TCH/F data come through with block-diagonal de-interleaved? Or does come as 8 interleaved bursts? I think all the intra-burst de-interleaving has already been done at DSP level. Is this correct? B -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Tue Feb 5 06:51:15 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 5 Feb 2013 07:51:15 +0100 Subject: Content of burst data in burst_ind branch In-Reply-To: References: Message-ID: > Can you please clarify what kind of preprocessing has been done for bursts > in burst_ind data? None. > Does TCH/F data come through with block-diagonal de-interleaved? Or does > come as 8 interleaved bursts? It's _exactly_ what was on the air, there is _no_ processing whatsoever beyond demodulation. > I think all the intra-burst de-interleaving has already been done at DSP > level. Is this correct? No. Cheers, Sylvain From edachleger at yahoo.com Tue Feb 5 16:01:11 2013 From: edachleger at yahoo.com (Erich Dachleger) Date: Tue, 5 Feb 2013 16:01:11 +0000 (GMT) Subject: Vedr: Content of burst data in burst_ind branch In-Reply-To: References: Message-ID: <1360080071.43886.YahooMailNeo@web171204.mail.ir2.yahoo.com> Hi list, Are all the obtained bursts.dat files useless when they are captured by unmodified burst_ind?When I use the standard burst_ind I obtain a chain of burst-files.I also sometime see displayed the word SACCH/8 on the log-screen. If one tries to single out burst-files belonging to SACCH/8 or TCH/F would these be useful as inputs to kraken after being converted to keystream? Somewhere on this list I read that captured data must? be converted to the MAC-block,if one looks for frames, and that code could be found in airprobe .What ist the meaning of that? Aren't the MAC-block alreday displayed when using burst_ind? regards erich ________________________________ Fra: Bhaskar11 Til: Sylvain Munaut <246tnt at gmail.com>; osmocomBB Sendt: Tirsdag, 5. februar 2013 6.27 Emne: Content of burst data in burst_ind branch Can you please clarify what kind of preprocessing has been done for bursts in ?burst_ind?data? Does TCH/F data come through with block-diagonal de-interleaved? Or does come as 8 interleaved bursts? I think all the intra-burst de-interleaving has already been done at DSP level. Is this correct? B -------------- next part -------------- An HTML attachment was scrubbed... URL: From bharathseelam at hotmail.com Tue Feb 5 06:07:57 2013 From: bharathseelam at hotmail.com (bharath seelam) Date: Tue, 5 Feb 2013 06:07:57 +0000 Subject: =?utf-8?Q?Osmocom-BB_compilation_Problem?= Message-ID: Hi Everyone, When i tried to install the osmocombb for the first time which was a couple of days back i encountered with a problem and did some minor modification in the code. >gsm411_sms.c: In function ?gsm411_tx_sms_submit?: >gsm411_sms.c:657: warning: passing argument 4 of ?gsm411_smc_init? from incompatible pointer type >/usr/local/include/osmocom/gsm/gsm0411_smc.h:46: note: expected ?int (*)(struct gsm411_smc_inst *, int, struct msgb *, int)? but argument is of type ?int (*)(struct gsm411_smc_inst *, int, struct msgb *)? >gsm411_sms.c:657: error: too many arguments to function ?gsm411_smc_init? >gsm411_sms.c:659: error: too many arguments to function ?gsm411_smr_init? >gsm411_sms.c: In function ?gsm411_rcv_sms?: >gsm411_sms.c:911: warning: passing argument 4 of ?gsm411_smc_init? from incompatible pointer type >/usr/local/include/osmocom/gsm/gsm0411_smc.h:46: note: expected ?int (*)(struct gsm411_smc_inst *, int, struct msgb *, int)? but argument is of type ?int (*)(struct gsm411_smc_inst *, int, struct msgb *)? by seeing this error i opened the respective file(gsm411_sms.c) in my local pc and i observed that the lines which was mentioned as error and find the below . gsm411_smc_init(&trans->sms.smc_inst, transaction_id, 0, gsm411_mn_recv, gsm411_mm_send); but in the header file (gsm0411_smc.h) only four arguments are defined void gsm411_smc_init(struct gsm411_smc_inst *inst, int network, int (*mn_recv) (struct gsm411_smc_inst *inst, int msg_type, struct msgb *msg), so i removed the extra argument transaction_id in the function(gsm411_smc_init) and also did the same with the respective lines where i was getting an error (from the file gsm411_sms.c). i have done a change like the below by assuming thatevery msg is a mobile originated mesage gsm411_smc_init(&trans->sms.smc_inst, transaction_id, 0, gsm411_mn_recv, gsm411_mm_send); Kindly assist me if i was doing wrong. Thanks in advance and Apologies if my observation was wrong. Regards, Bharath -------------- next part -------------- An HTML attachment was scrubbed... URL: From bharathseelam at hotmail.com Tue Feb 5 06:10:08 2013 From: bharathseelam at hotmail.com (bharath seelam) Date: Tue, 5 Feb 2013 11:40:08 +0530 Subject: Osmocom-BB compilation problem Message-ID: Hi Everyone, When i tried to install the osmocombb for the first time which was a couple of days back i encountered with a problem and did some minor modification in the code. >gsm411_sms.c: In function ?gsm411_tx_sms_submit?:>gsm411_sms.c:657: warning: passing argument 4 of ?gsm411_smc_init? from incompatible pointer type>/usr/local/include/osmocom/gsm/gsm0411_smc.h:46: note: expected ?int (*)(struct gsm411_smc_inst *, int, struct msgb *, int)? but argument is of type ?int (*)(struct gsm411_smc_inst *, int, struct msgb *)?>gsm411_sms.c:657: error: too many arguments to function ?gsm411_smc_init?>gsm411_sms.c:659: error: too many arguments to function ?gsm411_smr_init?>gsm411_sms.c: In function ?gsm411_rcv_sms?:>gsm411_sms.c:911: warning: passing argument 4 of ?gsm411_smc_init? from incompatible pointer type>/usr/local/include/osmocom/gsm/gsm0411_smc.h:46: note: expected ?int (*)(struct gsm411_smc_inst *, int, struct msgb *, int)? but argument is of type ?int (*)(struct gsm411_smc_inst *, int, struct msgb *)? by seeing this error i opened the respective file(gsm411_sms.c) in my local pc and i observed that the lines which was mentioned as error and find the below . gsm411_smc_init(&trans->sms.smc_inst, transaction_id, 0, gsm411_mn_recv, gsm411_mm_send); but in the header file (gsm0411_smc.h) only four arguments are defined void gsm411_smc_init(struct gsm411_smc_inst *inst, int network, int (*mn_recv) (struct gsm411_smc_inst *inst, int msg_type, struct msgb *msg), so i removed the extra argument transaction_id in the function(gsm411_smc_init) and also did the same with the respective lines where i was getting an error (from the file gsm411_sms.c). i have done a change like the below by assuming thatevery msg is a mobile originated mesage gsm411_smc_init(&trans->sms.smc_inst, transaction_id, 0, gsm411_mn_recv, gsm411_mm_send); Kindly assist me if i was doing wrong. Thanks in advance and Apologies if my observation was wrong. Regards,Bharath -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Tue Feb 5 12:13:03 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 5 Feb 2013 13:13:03 +0100 Subject: Osmocom-BB compilation problem In-Reply-To: References: Message-ID: > Kindly assist me if i was doing wrong. You need to follow the instructions exactly and use libosmocore from the git and not try to use the embedded one for the host build. Cheers, Sylvain From niceguy108 at gmail.com Tue Feb 5 18:22:37 2013 From: niceguy108 at gmail.com (Bhaskar11) Date: Tue, 5 Feb 2013 23:52:37 +0530 Subject: Problem with softbits in osmo_ubit2pbit() Message-ID: While playing with ccch_scan, I came across a strange problem. At some point the code uses: /* Convert to softbits */ for (i=0; i<116; i++) bursts[(116*bid)+i] = bt[i] ? - (bi->snr >> 1) : (bi->snr >> 1); After this, "xcch_decode()" works ok and "osmo_ubit2pbit_ext()" also works ok. But "osmo_ubit2pbit()" fails as it converts almost all softbits to 0xFF. Is this a bug or a "feature"? Do we need to recode "osmo_ubit2pbit" so that its bit-checking is more robust as in "osmo_ubit2pbit_ext"? Sylvain, can you explain the idea of using softbits instead of hard binary? Is it for GSMTAP to represent signal strength? Thanks in advance for your help. B -------------- next part -------------- An HTML attachment was scrubbed... URL: From niceguy108 at gmail.com Tue Feb 12 03:46:58 2013 From: niceguy108 at gmail.com (Bhaskar11) Date: Tue, 12 Feb 2013 09:16:58 +0530 Subject: Problem with softbits in osmo_ubit2pbit() In-Reply-To: References: Message-ID: I've figured this one out. Just sharing in case it helps other newbies like me. Softbits are necessary for convolutional decoding only. For all other processing hardbits should be used. There is no problem with "osmo_ubit2pbit_ext()". We just have to feed it hardbits and not softbits! :-) B On Tue, Feb 5, 2013 at 11:52 PM, Bhaskar11 wrote: > While playing with ccch_scan, I came across a strange problem. > > At some point the code uses: > /* Convert to softbits */ > for (i=0; i<116; i++) > bursts[(116*bid)+i] = bt[i] ? - (bi->snr >> 1) : (bi->snr >> 1); > > > After this, "xcch_decode()" works ok and "osmo_ubit2pbit_ext()" also works > ok. But "osmo_ubit2pbit()" fails as it converts almost all softbits to 0xFF. > > Is this a bug or a "feature"? Do we need to recode "osmo_ubit2pbit" so > that its bit-checking is more robust as in "osmo_ubit2pbit_ext"? > > Sylvain, can you explain the idea of using softbits instead of hard > binary? Is it for GSMTAP to represent signal strength? > > Thanks in advance for your help. > > B > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pabftk at gmail.com Wed Feb 6 08:08:32 2013 From: pabftk at gmail.com (Pavel Baturko) Date: Wed, 6 Feb 2013 08:08:32 +0000 Subject: [PATCH] Support of UCS2 for SMS/USSD Message-ID: Hi list, Attached 3 patches for decoding UCS2 MT-SMS and incoming USSD. Main idea: convert UCS2 text to UTF-8, check if terminal supports UTF-8 and if yes - print, otherwise - print in hex, and notify VTY to check mobile log (since we can't send UTF text to VTY, if someone knows how to do it - please tell me). Waiting for comments. Thanks, Pavel -------------- next part -------------- A non-text attachment was scrubbed... Name: osmocore-ucs2.patch Type: application/octet-stream Size: 4577 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ussd-ucs2.patch Type: application/octet-stream Size: 3625 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sms-ucs2.patch Type: application/octet-stream Size: 2161 bytes Desc: not available URL: From andreas at eversberg.eu Wed Feb 6 11:09:27 2013 From: andreas at eversberg.eu (jolly) Date: Wed, 06 Feb 2013 12:09:27 +0100 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: References: Message-ID: <511239E7.1030301@eversberg.eu> Pavel Baturko wrote: > Attached 3 patches for decoding UCS2 MT-SMS and incoming USSD. > Main idea: convert UCS2 text to UTF-8, check if terminal supports > UTF-8 and if yes - print, otherwise - print in hex, and notify VTY to > check mobile log (since we can't send UTF text to VTY, if someone > knows how to do it - please tell me). > hi paval, the patches for osmocombb look good to me, except that the UTF encoded text is not only displayed on VTY, but also not written to sms.txt file. look at gsm340_rx_sms_deliver() where linefeeds from sms-text are removed for the vty output. you could also remove (or replace by '?') non-ascii characters there. then it can be displayed on VTY too. you can apply the osmocombb patches, after the libosmocore patch is applied to master of libosmocore. for applying the libosmocore patch, i cannot give green light, because holger was recently working on sms code, so i would ask him. regards, andreas From pabftk at gmail.com Wed Feb 6 11:40:22 2013 From: pabftk at gmail.com (Pavel Baturko) Date: Wed, 6 Feb 2013 15:40:22 +0400 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: <511239E7.1030301@eversberg.eu> References: <511239E7.1030301@eversberg.eu> Message-ID: Hi Andreas, Thanks for comments. > the patches for osmocombb look good to me, except that the UTF encoded > text is not only displayed on VTY, but also not written to sms.txt file. > you could also remove (or replace by '?') > non-ascii characters there. then it can be displayed on VTY too. Am I right that you are proposing to display only ascii part of text and save it also in sms.txt file instead of status messages like 'SMS was printed ...'? For all non-ascii SMSs this will looks like '??? ?? ?????' at VTY, is it ok? > you can apply the osmocombb patches, after the libosmocore patch is > applied to master of libosmocore. for applying the libosmocore patch, i > cannot give green light, because holger was recently working on sms > code, so i would ask him. I'll wait for Holger's answer. Thanks, Pavel From andreas at eversberg.eu Wed Feb 6 12:00:58 2013 From: andreas at eversberg.eu (jolly) Date: Wed, 06 Feb 2013 13:00:58 +0100 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: References: <511239E7.1030301@eversberg.eu> Message-ID: <511245FA.6050403@eversberg.eu> Pavel Baturko wrote: > Am I right that you are proposing to display only ascii part of text > and save it also in sms.txt file instead of status messages like 'SMS > was printed ...'? For all non-ascii SMSs this will looks like '??? ?? > ?????' at VTY, is it ok? > i don't know about coding of UTF, but wikipedia reads that all ASCII characters are UTF-8 characters, so i guess that all characters except non-ASCII character should be visible. am i wrong? From pabftk at gmail.com Wed Feb 6 12:21:53 2013 From: pabftk at gmail.com (Pavel Baturko) Date: Wed, 6 Feb 2013 16:21:53 +0400 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: <511245FA.6050403@eversberg.eu> References: <511239E7.1030301@eversberg.eu> <511245FA.6050403@eversberg.eu> Message-ID: Hi, > i don't know about coding of UTF, but wikipedia reads that all ASCII > characters are UTF-8 characters, so i guess that all characters except > non-ASCII character should be visible. am i wrong? Yes, they will be visible, but I'm talking about SMSs without ASCII chars except spaces/numbers/dots/commas/etc. In that case all words (in national language for example) will not be visible at VTY and user will see many '?' symbols if change non-ascii chars to '?' and spaces/comms/etc, and I think such representation of original text will be not very good (if I correctly understand your first comment). Thanks, Pavel From andreas at eversberg.eu Wed Feb 6 13:21:51 2013 From: andreas at eversberg.eu (jolly) Date: Wed, 06 Feb 2013 14:21:51 +0100 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: References: <511239E7.1030301@eversberg.eu> <511245FA.6050403@eversberg.eu> Message-ID: <511258EF.4010806@eversberg.eu> > Yes, they will be visible, but I'm talking about SMSs without ASCII > chars except spaces/numbers/dots/commas/etc. In that case all words > (in national language for example) will not be visible at VTY and user > will see many '?' symbols if change non-ascii chars to '?' and > spaces/comms/etc, and I think such representation of original text > will be not very good (if I correctly understand your first comment). > ok then, why not print your message about encoded type to VTY, but store message in sms.txt. the gsm340_rx_sms_deliver() function could take two arguments, one text for the vty and one to store. From pabftk at gmail.com Wed Feb 6 14:07:33 2013 From: pabftk at gmail.com (Pavel Baturko) Date: Wed, 6 Feb 2013 18:07:33 +0400 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: <511258EF.4010806@eversberg.eu> References: <511239E7.1030301@eversberg.eu> <511245FA.6050403@eversberg.eu> <511258EF.4010806@eversberg.eu> Message-ID: > ok then, why not print your message about encoded type to VTY, but store > message in sms.txt. the gsm340_rx_sms_deliver() function could take two > arguments, one text for the vty and one to store. Ok, I'll prepare new patch and send it when ready. Thanks, Pavel From pabftk at gmail.com Thu Feb 7 22:26:26 2013 From: pabftk at gmail.com (Pavel Baturko) Date: Thu, 7 Feb 2013 22:26:26 +0000 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: References: <511239E7.1030301@eversberg.eu> <511245FA.6050403@eversberg.eu> <511258EF.4010806@eversberg.eu> Message-ID: Hi, Attached new version. SMS text will be saved to sms.txt file in any case (in case of UCS2 SMSs with non-ASCII chars this file should be opened with UTF-8 encoding) but on VTY user will see notice that SMS text can't be printed. Thanks, Pavel -------------- next part -------------- A non-text attachment was scrubbed... Name: sms-ucs2-v2.patch Type: application/octet-stream Size: 2681 bytes Desc: not available URL: From andreas at eversberg.eu Fri Feb 8 07:24:07 2013 From: andreas at eversberg.eu (jolly) Date: Fri, 08 Feb 2013 08:24:07 +0100 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: References: <511239E7.1030301@eversberg.eu> <511245FA.6050403@eversberg.eu> <511258EF.4010806@eversberg.eu> Message-ID: <5114A817.1000302@eversberg.eu> > > Hi, > > Attached new version. SMS text will be saved to sms.txt file in any > case (in case of UCS2 SMSs with non-ASCII chars this file should be > opened with UTF-8 encoding) but on VTY user will see notice that SMS > text can't be printed. > > Thanks, > Pavel > hi pavael, this looks good to me now. you can commit it as soon as the libosmocore patch is accepted and committed. best regards, andreas From pabftk at gmail.com Fri Feb 8 07:48:40 2013 From: pabftk at gmail.com (Pavel Baturko) Date: Fri, 8 Feb 2013 07:48:40 +0000 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: <5114A817.1000302@eversberg.eu> References: <511239E7.1030301@eversberg.eu> <511245FA.6050403@eversberg.eu> <511258EF.4010806@eversberg.eu> <5114A817.1000302@eversberg.eu> Message-ID: > this looks good to me now. you can commit it as soon as the libosmocore > patch is accepted and committed. Should I ask someone for committing to libosmocore? And can I commit to osmocom-bb repo directly (I think I can't)? Or I should re-ask for committing when libosmocore will be ready? Thanks, Pavel From laforge at gnumonks.org Fri Feb 8 09:39:19 2013 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 8 Feb 2013 10:39:19 +0100 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: References: Message-ID: <20130208093919.GB21324@prithivi.gnumonks.org> Hi Pavel, sorry to be the party pooper, but I don't like the libosmocore patch for two reasons: 1) a popen to the locale command is really ugly. First of all, it will synchronously block the process issuing that command. Typical libosmocore-using processes are single-threaded and expect library calls to be non-blocking. Secondly, I really hate the idea of spawning other processes, executing other executables. It sounds lieke an ugly hack. Is there no way to get the information programmatically, e.g. by using localeconv(3) ? 2) the function "ucs2_to_utf8_decode" is cluttering the global namespace even further. Yes, it is in principle not a function related to gsm, but I'd still appreciate if it would start with osmo_ or gsm_ prefix in order to make sure we don't clash with applications or other libraries using the same symbol name. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) -------------- next part -------------- A non-text attachment was scrubbed... Name: osmocore-ucs2.patch Type: application/octet-stream Size: 4577 bytes Desc: not available URL: From pabftk at gmail.com Fri Feb 8 09:55:52 2013 From: pabftk at gmail.com (Pavel Baturko) Date: Fri, 8 Feb 2013 13:55:52 +0400 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: <20130208093919.GB21324@prithivi.gnumonks.org> References: <20130208093919.GB21324@prithivi.gnumonks.org> Message-ID: Hi Harald, > Is there no way to get the information > programmatically, e.g. by using localeconv(3) ? Another way to get this information that I know is smthng like that: + old_locale = setlocale(LC_ALL, NULL); + curr_locale = setlocale(LC_ALL, ""); + for (i = 0; i < strlen(curr_locale); i++) + curr_locale[i] = tolower(curr_locale[i]); + have_utf8_locale = ((strstr(curr_locale, "utf-8") != NULL) || + (strstr(curr_locale, "utf8" ) != NULL)) ? 1 : 0; + setlocale(LC_ALL, old_locale); Not sure if it's ok because of temporary changing of current locale. unfortunately I was not able to find better ways to check locale. > 2) the function "ucs2_to_utf8_decode" is cluttering the global namespace > even further. Yes, it is in principle not a function related to > gsm, but I'd still appreciate if it would start with osmo_ or gsm_ > prefix in order to make sure we don't clash with applications or > other libraries using the same symbol name. I can move it to utils.c, is it acceptable? And of course add "osmo_" prefix. Thanks, Pavel From laforge at gnumonks.org Fri Feb 8 10:14:06 2013 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 8 Feb 2013 11:14:06 +0100 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: References: <20130208093919.GB21324@prithivi.gnumonks.org> Message-ID: <20130208101406.GD21324@prithivi.gnumonks.org> Hi Pavel, On Fri, Feb 08, 2013 at 01:55:52PM +0400, Pavel Baturko wrote: > Another way to get this information that I know is smthng like that: > + old_locale = setlocale(LC_ALL, NULL); > + curr_locale = setlocale(LC_ALL, ""); > + for (i = 0; i < strlen(curr_locale); i++) > + curr_locale[i] = tolower(curr_locale[i]); > + have_utf8_locale = ((strstr(curr_locale, "utf-8") != NULL) || > + (strstr(curr_locale, "utf8" ) != NULL)) ? 1 : 0; > + setlocale(LC_ALL, old_locale); > Not sure if it's ok because of temporary changing of current locale. > unfortunately I was not able to find better ways to check locale. the locale setting is only for the current program. And as indicated, at least so far, most libosmocore users are single-threaded, i.e. nobody would notice if the locale was different for a very short amount of time. Furthermore, assuming that the code is not called all that often (i.e. only once at program startup) I wouldn't be worried about that so much. I am not an expert in locale.h matters, but it would somehow be strange to me if you cannot determine utf-8 support without having to actually change the locale. Is anyone on this list more familiar with it? > > 2) the function "ucs2_to_utf8_decode" is cluttering the global namespace > > even further. Yes, it is in principle not a function related to > > gsm, but I'd still appreciate if it would start with osmo_ or gsm_ > > prefix in order to make sure we don't clash with applications or > > other libraries using the same symbol name. > I can move it to utils.c, is it acceptable? And of course add "osmo_" prefix. yes, that would be appreciated, thanks. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From pabftk at gmail.com Fri Feb 8 10:29:17 2013 From: pabftk at gmail.com (Pavel Baturko) Date: Fri, 8 Feb 2013 14:29:17 +0400 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: <20130208101406.GD21324@prithivi.gnumonks.org> References: <20130208093919.GB21324@prithivi.gnumonks.org> <20130208101406.GD21324@prithivi.gnumonks.org> Message-ID: Hi Harald, > the locale setting is only for the current program. And as indicated, > at least so far, most libosmocore users are single-threaded, i.e. nobody > would notice if the locale was different for a very short amount of > time. Furthermore, assuming that the code is not called all that often > (i.e. only once at program startup) I wouldn't be worried about that so > much. I can add some kind of global var which will indicate UTF-8 support and init it when app starting with code above (or other code if will find better one). Then use it in case of SMS/USSD receving. > I am not an expert in locale.h matters, but it would somehow be strange > to me if you cannot determine utf-8 support without having to actually > change the locale. Is anyone on this list more familiar with it? I asked some time ago, but there was no answer.. setlocale function with NULL argument always returns "C" - Minimal "C" locale - if locale was not changed before, with arguments rather than NULL - changes the locale. Thanks, Pavel From laforge at gnumonks.org Fri Feb 8 12:24:05 2013 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 8 Feb 2013 13:24:05 +0100 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: References: <20130208093919.GB21324@prithivi.gnumonks.org> <20130208101406.GD21324@prithivi.gnumonks.org> Message-ID: <20130208122405.GK21324@prithivi.gnumonks.org> Hi Pavel, On Fri, Feb 08, 2013 at 02:29:17PM +0400, Pavel Baturko wrote: > > time. Furthermore, assuming that the code is not called all that often > > (i.e. only once at program startup) I wouldn't be worried about that so > > much. > I can add some kind of global var which will indicate UTF-8 support > and init it when app starting with code above (or other code if will > find better one). Then use it in case of SMS/USSD receving. This sounds reasonable. Please make the global variable static and hide it to the caller. So only on the first call to the function it will do the setlocale() trick, then store the result in a variable. All further calls to the function will then retunr the variable instead of setlocale() and friends. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From pabftk at gmail.com Sun Feb 10 11:55:22 2013 From: pabftk at gmail.com (Pavel Baturko) Date: Sun, 10 Feb 2013 11:55:22 +0000 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: <20130208122405.GK21324@prithivi.gnumonks.org> References: <20130208093919.GB21324@prithivi.gnumonks.org> <20130208101406.GD21324@prithivi.gnumonks.org> <20130208122405.GK21324@prithivi.gnumonks.org> Message-ID: Hi, Here are updated versions of patches: Functions for converting ucs2->utf8 and checking current locale are moved to util.c. Function for checking current locale rewrited to use 'setlocale' instead of external 'locale' cmd call. Support of UTF is checked just once in 'l23_app_init' and then used via static var. Thanks, Pavel -------------- next part -------------- A non-text attachment was scrubbed... Name: sms-ucs2-v2.patch Type: application/octet-stream Size: 3150 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: osmocore-ucs2-v2.patch Type: application/octet-stream Size: 3467 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ussd-ucs2-v2.patch Type: application/octet-stream Size: 4602 bytes Desc: not available URL: From pabftk at gmail.com Wed Feb 13 14:30:57 2013 From: pabftk at gmail.com (Pavel Baturko) Date: Wed, 13 Feb 2013 14:30:57 +0000 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: References: <20130208093919.GB21324@prithivi.gnumonks.org> <20130208101406.GD21324@prithivi.gnumonks.org> <20130208122405.GK21324@prithivi.gnumonks.org> Message-ID: Hi Harald, Have you had a chance to look at last versions of patches? Thanks, Pavel On Sun, Feb 10, 2013 at 11:55 AM, Pavel Baturko wrote: > Hi, > > Here are updated versions of patches: > Functions for converting ucs2->utf8 and checking current locale are > moved to util.c. > Function for checking current locale rewrited to use 'setlocale' > instead of external 'locale' cmd call. > Support of UTF is checked just once in 'l23_app_init' and then used > via static var. > > Thanks, > Pavel From pabftk at gmail.com Wed Feb 27 04:30:05 2013 From: pabftk at gmail.com (Pavel Baturko) Date: Wed, 27 Feb 2013 04:30:05 +0000 Subject: [PATCH] Support of UCS2 for SMS/USSD In-Reply-To: References: <20130208093919.GB21324@prithivi.gnumonks.org> <20130208101406.GD21324@prithivi.gnumonks.org> <20130208122405.GK21324@prithivi.gnumonks.org> Message-ID: Just kindly reminder.. Thanks, Pavel On Wed, Feb 13, 2013 at 2:30 PM, Pavel Baturko wrote: > Hi Harald, > > Have you had a chance to look at last versions of patches? > > Thanks, > Pavel > > On Sun, Feb 10, 2013 at 11:55 AM, Pavel Baturko wrote: >> Hi, >> >> Here are updated versions of patches: >> Functions for converting ucs2->utf8 and checking current locale are >> moved to util.c. >> Function for checking current locale rewrited to use 'setlocale' >> instead of external 'locale' cmd call. >> Support of UTF is checked just once in 'l23_app_init' and then used >> via static var. >> >> Thanks, >> Pavel From mchedly at gmail.com Sun Feb 10 02:36:00 2013 From: mchedly at gmail.com (jet-lee) Date: Sat, 9 Feb 2013 18:36:00 -0800 (PST) Subject: C123 can't send DOWNLOAD ACK Message-ID: <1360463760108-4025820.post@n3.nabble.com> Hi, my problem is, that I can download the firmware on the motorola c123, but I can't send a DOWNLOAD ACK. The Firmware is on the Phone, because I see the "HELLO WORLD" example on the phone screen. I build my own "RS232-to-2.5mm"-Cable and I think it works.... Another thing is, at the end of the download I become permanently the INFO " got 1 bytes ...". Can anybody help me? (Sorry my english is very sad :( ) Here is the output: root at debian:./osmocon -p /dev/ttyS0 -d t -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin got 2 bytes from modem, data looks like: 06 c1 .. 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_e88/hello_world.compalram.bin): file_size=25108, hdr_len=4, dnload_len=25115 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(): 4095 bytes (4095/25115) handle_write(): 3840 bytes (7935/25115) handle_write(): 3840 bytes (11775/25115) handle_write(): 3840 bytes (15615/25115) handle_write(): 3840 bytes (19455/25115) handle_write(): 3840 bytes (23295/25115) handle_write(): 1820 bytes (25115/25115) handle_write(): finished 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: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: ff . got 1 bytes from modem, data looks like: bf . got 1 bytes from modem, data looks like: ff . 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: ff . got 1 bytes from modem, data looks like: ff . got 1 bytes from modem, data looks like: ff . 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: 00 . 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: dc . got 1 bytes from modem, data looks like: 98 . got 1 bytes from modem, data looks like: 9f . got 1 bytes from modem, data looks like: ff . got 1 bytes from modem, data looks like: 9f . ..... -- View this message in context: http://baseband-devel.722152.n3.nabble.com/C123-can-t-send-DOWNLOAD-ACK-tp4025820.html Sent from the baseband-devel mailing list archive at Nabble.com. From holger at freyther.de Mon Feb 11 09:33:59 2013 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Mon, 11 Feb 2013 10:33:59 +0100 Subject: C123 can't send DOWNLOAD ACK In-Reply-To: <1360463760108-4025820.post@n3.nabble.com> References: <1360463760108-4025820.post@n3.nabble.com> Message-ID: <20130211093359.GF21255@xiaoyu.lan> On Sat, Feb 09, 2013 at 06:36:00PM -0800, jet-lee wrote: > root at debian:./osmocon -p /dev/ttyS0 -d t -m c123xor > ../../target/firmware/board/compal_e88/hello_world.compalram.bin did you try without the xor? which toolchain do you use? From niceguy108 at gmail.com Tue Feb 12 03:41:20 2013 From: niceguy108 at gmail.com (Bhaskar11) Date: Tue, 12 Feb 2013 09:11:20 +0530 Subject: Interleave coding for TCH FS and HS Message-ID: While studying FS coding, I created the attached drawing. The code used for de-interleaving is: void tch_fr_deinterleave313(ubit_t *mC, int blockoffset) //see 3GPP TS 05.03 / 3.1.3 { for (int k = 0; k < 456; k++) { int B = ( k + blockoffset ) % 8; int j = 2 * ((49 * k) % 57) + ((k % 8) / 4); mC[k] = mI[B][j]; } } Now I want to study HS coding and de-interleaving. The GSM specs 05.03 / 3.2.3 only mentions a table for interleave coding and not a formula for matching j with k. Why is that? I tried to find a formula by looking a the table pattern, but it looks quite inconsistent. If there is no formula for coding/decoding HS, then do we have to use table lookup for each bit? Sounds very inefficient. Or am I missing something? B -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: GSM TCH-F Interleave.jpg Type: image/jpeg Size: 121729 bytes Desc: not available URL: From akibsayyed at gmail.com Thu Feb 14 16:43:52 2013 From: akibsayyed at gmail.com (Akib Sayyed) Date: Thu, 14 Feb 2013 22:13:52 +0530 Subject: Sniffing to RACH Message-ID: Hello list I am trying to sniff TS0 of BTS for purpose of sniffing RACH. but i am bit confused in this. i attached my code in mail. short description: 1. changed IMM_ASS to single RF and allow to jump as per IMM_ASS only once and no Hoppoing 2. while jumping to single RF imm ass used chan_nr=40 (40 & 7 =0) 3. added own function for decoding ccch. current problem able to decode PCH and AGCH properly but its slow in action. but if i use following modification in mframe_sched.c static const struct mframe_sched_item mf_ccch[] = { { .sched_set = SNIFF_QUAD_DL, .modulo = 51, .frame_nr = 6 }, { .sched_set = SNIFF_QUAD_UL, .modulo = 51, .frame_nr = 6 +15 }, { .sched_set = SNIFF_QUAD_DL, .modulo = 51, .frame_nr = 12}, { .sched_set = SNIFF_QUAD_UL, .modulo = 51, .frame_nr = 12 +15}, { .sched_set = SNIFF_QUAD_DL, .modulo = 51, .frame_nr = 16 }, { .sched_set = SNIFF_QUAD_UL, .modulo = 51, .frame_nr = 16 +15}, { .sched_set = SNIFF_QUAD_DL, .modulo = 51, .frame_nr = 22 }, { .sched_set = SNIFF_QUAD_UL, .modulo = 51, .frame_nr = 22 +15}, { .sched_set = SNIFF_QUAD_DL, .modulo = 51, .frame_nr = 26 }, { .sched_set = SNIFF_QUAD_UL, .modulo = 51, .frame_nr = 26+15 }, { .sched_set = SNIFF_QUAD_DL, .modulo = 51, .frame_nr = 32 }, { .sched_set = SNIFF_QUAD_UL, .modulo = 51, .frame_nr = 32 +15}, { .sched_set = SNIFF_QUAD_DL, .modulo = 51, .frame_nr = 36 }, { .sched_set = SNIFF_QUAD_UL, .modulo = 51, .frame_nr = 36 +15}, { .sched_set = SNIFF_QUAD_DL, .modulo = 51, .frame_nr = 42 }, { .sched_set = SNIFF_QUAD_UL, .modulo = 51, .frame_nr = 42 +15}, { .sched_set = SNIFF_QUAD_DL, .modulo = 51, .frame_nr = 46 }, { .sched_set = SNIFF_QUAD_UL, .modulo = 51, .frame_nr = 46 +15}, { .sched_set = NULL } }; it becomes very faster but I am not sure whether its correct or will give me correct out put. -- Akib Sayyed Matrix-Shell akibsayyed at gmail.com akibsayyed at matrixshell.com Mob:- +91-966-514-2243 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: app_ccch_scan.c Type: text/x-csrc Size: 22881 bytes Desc: not available URL: From dagar1935 at hotmail.co.uk Fri Feb 15 05:11:21 2013 From: dagar1935 at hotmail.co.uk (dagar) Date: Thu, 14 Feb 2013 21:11:21 -0800 (PST) Subject: OsmocomBB Mobile Call Setup Weird behaviour Message-ID: <1360905081275-4025830.post@n3.nabble.com> OK am testing the mobile app with C123 using real sim but getting some odd behaviour (have tested with main branch & sylvian testing branch and results have been similar to this) The results below are from using sylvian testing branch build as described here http://bb.osmocom.org/trac/wiki/SIMReader config tx is enabled etc I can download the layer1 firmware to the phone ok - mobile app seems to run ok aswell but when I try to make a call or sms this is where there's some odd behaviour . On my first attempt to make a call I can hear the call trying to be made but an automated message is played saying I have dialed an incorrect number (this normally happens if the number is dialed in an incorrect format) In previous attempts I have tried all the formats I can think of but have never been able to get a successful call to go through as of yet but if I dial it through the phone (without osmocom) normally everything works fine.. 07780000000 +447780000000 447780000000 00447780000000 Usually after the first call the phone then mysteriously deregisters from the network there is no service and when I restart osmocon/mobile etc I still cannot register on the network it just keeps scannning frequenceies and failing to connect with the network. On my first osmocon log when i managed to connect to the network after the call was released there were alot of DSP Error Status: 32 messages and then no service. I have gone through the logs but I still can't figure out why a) the call is failing to go through correctly b) why it seems like I get kicked of the network if I try to make a call Here are my full outputs 1ST ATTEMPT - MANAGED TO PLACE CALL THEN CONNECTION DROPPED Osmocon output - https://www.box.com/s/xdqi7azezprf4g7erz9h Mobile output - https://www.box.com/s/gqcdas9eqso0nchat011 Telnet output - https://www.box.com/s/lcazgabtmous0xheklmc 2ND ATTEMPT - FAILED TO CONNECT Osmocon output - https://www.box.com/s/c42vi7ows8p14h0hr45m Mobile output - https://www.box.com/s/eqygysqommur46ywgqrs Telnet output - https://www.box.com/s/kmympl0g0l8zb3xjyu8d 3RD ATTEMPT - FAILED TO CONNECT Osmocon output - https://www.box.com/s/gb9aw9p05pqy1v5fpxke Mobile output - https://www.box.com/s/llo751tuvvu1p5v31eur Telnet output - https://www.box.com/s/t8e63lqrad87f35uylge Extract from telnet OsmocomBB# % (MS 1) % Trying to registering with network... % (MS 1) % On Network, normal service: Guernsey, T-Mobile show ms MS '1' is up, service is normal IMEI: 35972800609#### IMEISV: 359728006093#### IMEI generation: fixed automatic network selection state: A2 on PLMN MCC=234 MNC=30 (Guernsey, T-Mobile) cell selection state: C3 camped normally ARFCN=628(DCS) MCC=234 MNC=30 LAC=0x084f CELLID=0xf65d (Guernsey, T-Mobile) radio ressource layer state: idle mobility management layer state: MM idle, normal service OsmocomBB# call 1 +44772228#### OsmocomBB# % (MS 1) % Call has been released % (MS 1) % On Network, normal service: Guernsey, T-Mobile call 1 +44772228#### % (MS 1) % Searching network... show ms % (MS 1) % On Network, normal service: Guernsey, T-Mobile call 1 44772228#### OsmocomBB# % (MS 1) % Call is proceeding % (MS 1) % Call is alerting % (MS 1) % Call: Remote hangs up % (MS 1) % Trying to registering with network... % (MS 1) % Trying to registering with network... % (MS 1) % Searching network... % (MS 1) % No service. % (MS 1) % Power off! CALL SETUP EXTRACT FROM 1ST MOBILE APP OUTPUT -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OsmocomBB-Mobile-Call-Setup-Weird-behaviour-tp4025830.html Sent from the baseband-devel mailing list archive at Nabble.com. From 246tnt at gmail.com Fri Feb 15 07:00:37 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Fri, 15 Feb 2013 08:00:37 +0100 Subject: OsmocomBB Mobile Call Setup Weird behaviour In-Reply-To: <1360905081275-4025830.post@n3.nabble.com> References: <1360905081275-4025830.post@n3.nabble.com> Message-ID: Hi, > The results below are from using sylvian testing branch build as described > here http://bb.osmocom.org/trac/wiki/SIMReader > Retry with the main branch (and make sure the phone has been hard rebooted / battery removed). The sylvain/testing branch currently includes some _highly_ experimental DSP patch that seems to break some stuff. Cheers, Sylvain From dagar1935 at hotmail.co.uk Fri Feb 15 08:29:24 2013 From: dagar1935 at hotmail.co.uk (dagar) Date: Fri, 15 Feb 2013 00:29:24 -0800 (PST) Subject: OsmocomBB Mobile Call Setup Weird behaviour In-Reply-To: References: <1360905081275-4025830.post@n3.nabble.com> Message-ID: <1360916964568-4025832.post@n3.nabble.com> Thanks just did a hard reset and ran on main branch and its working ok :) on one sim at least planning to test more later.... -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OsmocomBB-Mobile-Call-Setup-Weird-behaviour-tp4025830p4025832.html Sent from the baseband-devel mailing list archive at Nabble.com. From niceguy108 at gmail.com Sat Feb 16 10:46:53 2013 From: niceguy108 at gmail.com (Bhaskar11) Date: Sat, 16 Feb 2013 16:16:53 +0530 Subject: reference to TS 08.05 Message-ID: The code for rxlev2dbm refers to TS 08.05 Chapter 8.1.4, but TS 08.05 is now marked as "withdrawn". Can you please point me to the correct reference for this? Thx. -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Sat Feb 16 11:05:56 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sat, 16 Feb 2013 12:05:56 +0100 Subject: reference to TS 08.05 In-Reply-To: References: Message-ID: > The code for rxlev2dbm refers to TS 08.05 Chapter 8.1.4, but TS 08.05 is now > marked as "withdrawn". Looks to be a typo. It's 05.08 chapter 8.1.4 Cheers, Sylvain From critsit1234 at gmail.com Sat Feb 16 13:50:38 2013 From: critsit1234 at gmail.com (cris crazy) Date: Sat, 16 Feb 2013 19:20:38 +0530 Subject: Trouble in making CALL Message-ID: Hi all, I am facing an error while trying to make a call from vty here is my mobile.cfg output ! ! OsmocomBB () configuration saved from vty !! ! line vty no login ! gps device /dev/ttyACM0 gps baudrate default gps enable ! no hide-default ! ms 1 layer2-socket /tmp/osmocom_l2 sap-socket /tmp/osmocom_sap sim reader network-selection-mode auto imei 415239521974659 0 imei-random 15 no emergency-imsi no sms-service-center no call-waiting no auto-answer no force-rekey clip no clir tx-power auto no simulated-delay no stick location-updating neighbour-measurement codec full-speed prefer codec half-speed no abbrev support sms a5/1 a5/2 p-gsm e-gsm r-gsm no gsm-850 dcs no pcs class-900 4 class-850 4 class-dcs 1 class-pcs 1 channel-capability sdcch+tchf+tchh full-speech-v1 full-speech-v2 half-speech-v1 min-rxlev -100 dsc-max 90 no skip-max-per-band 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 ! the debbuging output is <0009> mnccms.c:570 Make call to 123456789 <0009> mnccms.c:150 support TCH/H also <0009> mnccms.c:174 support full rate v2 <0009> mnccms.c:178 support full rate v1 <0009> mnccms.c:187 support half rate v1 <0006> transaction.c:76 ms 1 allocates transaction (proto 3 trans_id 255 callref 1 mem 0xf408d0) <0006> gsm48_cc.c:243 new state NULL -> MM_CONNECTION_PEND <0006> gsm48_cc.c:507 Sending MMCC_EST_REQ <0005> gsm48_mm.c:3783 (ms 1) Received 'MMCC_EST_REQ' event in state MM idle <0005> gsm48_mm.c:3786 -> substate PLMN search <0005> gsm48_mm.c:3788 -> callref 1, transaction_id 255 <0005> gsm48_mm.c:3051 Init MM Connection, not in normal state. <0006> gsm48_cc.c:2161 (ms 1) Received 'MMCC_REL_IND' in CC state MM_CONNECTION_PEND <0006> gsm48_cc.c:196 (ms 1 ti ff) Sending 'MNCC_REL_IND' to MNCC. <0006> gsm48_cc.c:243 new state MM_CONNECTION_PEND -> NULL <0006> transaction.c:104 ms 1 frees transaction (mem 0xf408d0) <0009> mnccms.c:372 Call has been released (cause 21) <0009> mnccms.c:71 (call 1) Call removed. and also my ms output from vty OsmocomBB> enable OsmocomBB# show ms MS '1' is up, service is limited IMEI: 418873812577882 IMEISV: 4188738125778820 IMEI generation: random (15 trailing digits) automatic network selection state: A0 null cell selection state: C0 null radio ressource layer state: idle mobility management layer state: MM idle, PLMN search OsmocomBB# show subsccriber 1 % Unknown command. OsmocomBB# show sub OsmocomBB# show subscriber 1 OsmocomBB# show subscriber 1 Mobile Subscriber of MS '1': IMSI: 405025012498239 ICCID: 89910255110124982391 Status: U1_UPDATED IMSI detached TMSI 0x1d315a07 LAI: MCC 405 MNC 025 LAC 0x42d8 (405, TATA DOCOMO) Key: sequence 2 a6 78 30 12 22 45 0b 03 Access barred cells: no Access classes: Kindly assist me with some suggestions. Regards, Cris -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas at eversberg.eu Mon Feb 18 09:27:04 2013 From: andreas at eversberg.eu (jolly) Date: Mon, 18 Feb 2013 10:27:04 +0100 Subject: Trouble in making CALL In-Reply-To: References: Message-ID: <5121F3E8.8060506@eversberg.eu> cris crazy wrote: > OsmocomBB# show ms > MS '1' is up, service is limited > IMEI: 418873812577882 > IMEISV: 4188738125778820 > IMEI generation: random (15 trailing digits) > automatic network selection state: A0 null > cell selection state: C0 null > radio ressource layer state: idle > mobility management layer state: MM idle, PLMN search hi, it seems that you did not yet started your phone, since the network search has not started. service remains limited until you are attached to the network, but you don't. did you start layer 1? try bcch_scan and ccch_scan app to check if your phone works and you can sync to a cell. regards, andreas p.s. please don't make private infos like your IMSI public. they could be abused. From critsit1234 at gmail.com Mon Feb 18 21:19:57 2013 From: critsit1234 at gmail.com (cris crazy) Date: Tue, 19 Feb 2013 02:49:57 +0530 Subject: Trouble in making CALL In-Reply-To: <5121F3E8.8060506@eversberg.eu> References: <5121F3E8.8060506@eversberg.eu> Message-ID: Hi Andreas, Thanks for your suggestions ... Below is the output after loading the layer1 to mobile OsmocomBB Layer 1 (revision osmocon_v0.0.0-1747-geeafd9f-modified) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: ee180728b042174d ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== Power up simcard: Assert DSP into Reset Releasing DSP from Reset Installing DSP extensions patch Setting some dsp_api.ndb values Setting API NDB parameters Finishing download phase DSP Download Status: 0x0002 DSP API Version: 0x3606 0x0000 LOST 7089! and i am able to see the layer 1 osmocom-bb in the mobile. As per your suggestion i checked with bcch_scan here is the output snippet from the console of ./bcch_scan arfcn=853 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=870 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=876 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=877 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=881 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=882 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=885 rxlev=1 <000c> l1ctl.c:118 FBSB RESP: result=255 arfcn=-1 rxlev=0 It goes on like this and finally ends with negative value. and in osmocon console the output is like Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=849, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=853, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=870, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=876, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=877, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=881, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=882, flags=0x7) Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=885, flags=0x7 by this i assume that my mobile is not able to sync with the network ..please correct me if i was wrong... and also kindly assist me for any kind of modifications. thanks in advance Regards, Cris On Mon, Feb 18, 2013 at 2:57 PM, jolly wrote: > cris crazy wrote: > > OsmocomBB# show ms > > MS '1' is up, service is limited > > IMEI: 418873812577882 > > IMEISV: 4188738125778820 > > IMEI generation: random (15 trailing digits) > > automatic network selection state: A0 null > > cell selection state: C0 null > > radio ressource layer state: idle > > mobility management layer state: MM idle, PLMN search > hi, > > it seems that you did not yet started your phone, since the network > search has not started. service remains limited until you are attached > to the network, but you don't. did you start layer 1? try bcch_scan and > ccch_scan app to check if your phone works and you can sync to a cell. > > regards, > > andreas > > p.s. please don't make private infos like your IMSI public. they could > be abused. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From critsit1234 at gmail.com Wed Feb 20 16:51:24 2013 From: critsit1234 at gmail.com (cris crazy) Date: Wed, 20 Feb 2013 22:21:24 +0530 Subject: Trouble in making CALL In-Reply-To: References: <5121F3E8.8060506@eversberg.eu> Message-ID: Hi, I'm kindly requesting some suggests for the below issue as i totally don't know how to resolve/rectify it. Regards, Cris On Tue, Feb 19, 2013 at 2:49 AM, cris crazy wrote: > Hi Andreas, > > Thanks for your suggestions ... > > Below is the output after loading the layer1 to mobile > > OsmocomBB Layer 1 (revision osmocon_v0.0.0-1747-geeafd9f-modified) > ====================================================================== > Device ID code: 0xb4fb > Device Version code: 0x0000 > ARM ID code: 0xfff3 > cDSP ID code: 0x0128 > Die ID code: ee180728b042174d > ====================================================================== > REG_DPLL=0x2413 > CNTL_ARM_CLK=0xf0a1 > CNTL_CLK=0xff91 > CNTL_RST=0xfff3 > CNTL_ARM_DIV=0xfff9 > ====================================================================== > Power up simcard: > Assert DSP into Reset > Releasing DSP from Reset > Installing DSP extensions patch > Setting some dsp_api.ndb values > Setting API NDB parameters > Finishing download phase > DSP Download Status: 0x0002 > DSP API Version: 0x3606 0x0000 > LOST 7089! > > and i am able to see the layer 1 osmocom-bb in the mobile. > > As per your suggestion i checked with bcch_scan > > here is the output snippet from the console of ./bcch_scan > > arfcn=853 rxlev=1 > <000c> l1ctl.c:118 FBSB RESP: result=255 > arfcn=870 rxlev=1 > <000c> l1ctl.c:118 FBSB RESP: result=255 > arfcn=876 rxlev=1 > <000c> l1ctl.c:118 FBSB RESP: result=255 > arfcn=877 rxlev=1 > <000c> l1ctl.c:118 FBSB RESP: result=255 > arfcn=881 rxlev=1 > <000c> l1ctl.c:118 FBSB RESP: result=255 > arfcn=882 rxlev=1 > <000c> l1ctl.c:118 FBSB RESP: result=255 > arfcn=885 rxlev=1 > <000c> l1ctl.c:118 FBSB RESP: result=255 > arfcn=-1 rxlev=0 > > It goes on like this and finally ends with negative value. > > and in osmocon console the output is like > > Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=849, flags=0x7) > Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=853, flags=0x7) > Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=870, flags=0x7) > Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=876, flags=0x7) > Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=877, flags=0x7) > Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=881, flags=0x7) > Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=882, flags=0x7) > Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=885, flags=0x7 > > > by this i assume that my mobile is not able to sync with the network > ..please correct me if i was wrong... > > > and also kindly assist me for any kind of modifications. > > thanks in advance > > Regards, > Cris > > > > > > > On Mon, Feb 18, 2013 at 2:57 PM, jolly wrote: > >> cris crazy wrote: >> > OsmocomBB# show ms >> > MS '1' is up, service is limited >> > IMEI: 418873812577882 >> > IMEISV: 4188738125778820 >> > IMEI generation: random (15 trailing digits) >> > automatic network selection state: A0 null >> > cell selection state: C0 null >> > radio ressource layer state: idle >> > mobility management layer state: MM idle, PLMN search >> hi, >> >> it seems that you did not yet started your phone, since the network >> search has not started. service remains limited until you are attached >> to the network, but you don't. did you start layer 1? try bcch_scan and >> ccch_scan app to check if your phone works and you can sync to a cell. >> >> regards, >> >> andreas >> >> p.s. please don't make private infos like your IMSI public. they could >> be abused. >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From niceguy108 at gmail.com Thu Feb 21 12:28:11 2013 From: niceguy108 at gmail.com (Bhaskar11) Date: Thu, 21 Feb 2013 17:58:11 +0530 Subject: Trouble in making CALL In-Reply-To: References: <5121F3E8.8060506@eversberg.eu> Message-ID: Hi Chris, I have had similar problems. Some suggestions you can try out. 1. Put a real IMEI code. Some networks check for "fake" IMEI codes which were common in some mobiles and refuse connections to those mobiles. Your case looks like one. Once it works, you can try to randomise the last few digits only. Quite possibly this will solve your problem. 2. Put the real IMSI code of your SIM. 3. Do a cold start and try again. Sometimes the connection is unstable. I have no idea why. 4. Enable "stick" option. 5. Try manual network selection. 6. Put correct SMS service centre number. Let the list know what works. :-) Good luck! B On Wed, Feb 20, 2013 at 10:21 PM, cris crazy wrote: > Hi, > > I'm kindly requesting some suggests for the below issue as i totally don't > know how to resolve/rectify it. > > > Regards, > Cris > > > On Tue, Feb 19, 2013 at 2:49 AM, cris crazy wrote: > >> Hi Andreas, >> >> Thanks for your suggestions ... >> >> Below is the output after loading the layer1 to mobile >> >> OsmocomBB Layer 1 (revision osmocon_v0.0.0-1747-geeafd9f-modified) >> ====================================================================== >> Device ID code: 0xb4fb >> Device Version code: 0x0000 >> ARM ID code: 0xfff3 >> cDSP ID code: 0x0128 >> Die ID code: ee180728b042174d >> ====================================================================== >> REG_DPLL=0x2413 >> CNTL_ARM_CLK=0xf0a1 >> CNTL_CLK=0xff91 >> CNTL_RST=0xfff3 >> CNTL_ARM_DIV=0xfff9 >> ====================================================================== >> Power up simcard: >> Assert DSP into Reset >> Releasing DSP from Reset >> Installing DSP extensions patch >> Setting some dsp_api.ndb values >> Setting API NDB parameters >> Finishing download phase >> DSP Download Status: 0x0002 >> DSP API Version: 0x3606 0x0000 >> LOST 7089! >> >> and i am able to see the layer 1 osmocom-bb in the mobile. >> >> As per your suggestion i checked with bcch_scan >> >> here is the output snippet from the console of ./bcch_scan >> >> arfcn=853 rxlev=1 >> <000c> l1ctl.c:118 FBSB RESP: result=255 >> arfcn=870 rxlev=1 >> <000c> l1ctl.c:118 FBSB RESP: result=255 >> arfcn=876 rxlev=1 >> <000c> l1ctl.c:118 FBSB RESP: result=255 >> arfcn=877 rxlev=1 >> <000c> l1ctl.c:118 FBSB RESP: result=255 >> arfcn=881 rxlev=1 >> <000c> l1ctl.c:118 FBSB RESP: result=255 >> arfcn=882 rxlev=1 >> <000c> l1ctl.c:118 FBSB RESP: result=255 >> arfcn=885 rxlev=1 >> <000c> l1ctl.c:118 FBSB RESP: result=255 >> arfcn=-1 rxlev=0 >> >> It goes on like this and finally ends with negative value. >> >> and in osmocon console the output is like >> >> Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=849, flags=0x7) >> Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=853, flags=0x7) >> Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=870, flags=0x7) >> Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=876, flags=0x7) >> Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=877, flags=0x7) >> Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=881, flags=0x7) >> Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=882, flags=0x7) >> Starting FCCH RecognitionL1CTL_FBSB_REQ (arfcn=885, flags=0x7 >> >> >> by this i assume that my mobile is not able to sync with the network >> ..please correct me if i was wrong... >> >> >> and also kindly assist me for any kind of modifications. >> >> thanks in advance >> >> Regards, >> Cris >> >> >> >> >> >> >> On Mon, Feb 18, 2013 at 2:57 PM, jolly wrote: >> >>> cris crazy wrote: >>> > OsmocomBB# show ms >>> > MS '1' is up, service is limited >>> > IMEI: 418873812577882 >>> > IMEISV: 4188738125778820 >>> > IMEI generation: random (15 trailing digits) >>> > automatic network selection state: A0 null >>> > cell selection state: C0 null >>> > radio ressource layer state: idle >>> > mobility management layer state: MM idle, PLMN search >>> hi, >>> >>> it seems that you did not yet started your phone, since the network >>> search has not started. service remains limited until you are attached >>> to the network, but you don't. did you start layer 1? try bcch_scan and >>> ccch_scan app to check if your phone works and you can sync to a cell. >>> >>> regards, >>> >>> andreas >>> >>> p.s. please don't make private infos like your IMSI public. they could >>> be abused. >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From deamon at n8byte.com Mon Feb 18 17:40:55 2013 From: deamon at n8byte.com (Alexander Schwankner) Date: Mon, 18 Feb 2013 18:40:55 +0100 Subject: Can't get arm toolchain Message-ID: *Dear folks,* Recently I tried to compile osmocomBB on ubuntu 120.10 and arch linux. I always run into problems trying to get the arm toolchain. I can't reach gnuarch.com because it is down, nor get the paket from the ubuntu ppa because it is also down or corrupted. Is there any other source where I can get the arm toolchain or any howto wich could help me? Thanks :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrmoor4 at web.de Mon Feb 18 17:56:38 2013 From: mrmoor4 at web.de (Alexander Schwankner) Date: Mon, 18 Feb 2013 18:56:38 +0100 Subject: Can't get arm toolchain Message-ID: *Dear folks,* Recently I tried to compile osmocomBB on ubuntu 120.10 and arch linux. I always run into problems trying to get the arm toolchain. I can't reach gnuarch.com because it is down, nor get the paket from the ubuntu ppa because it is also down or corrupted. Is there any other source where I can get the arm toolchain or any howto wich could help me? Thanks :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From edachleger at yahoo.com Mon Feb 18 19:05:26 2013 From: edachleger at yahoo.com (Erich Dachleger) Date: Mon, 18 Feb 2013 19:05:26 +0000 (GMT) Subject: Can't get arm toolchain In-Reply-To: References: Message-ID: <1361214326.16029.YahooMailNeo@web171206.mail.ir2.yahoo.com> Hi, There is a toolchain-buildscript on the osmocom wiki which is the recommended way of getting a functional toolchain. regards erich ________________________________ Fra: Alexander Schwankner Til: baseband-devel at lists.osmocom.org Sendt: Mandag, 18. februar 2013 18.56 Emne: Can't get arm toolchain Dear folks, Recently I tried to compile osmocomBB on ubuntu 120.10 and arch linux. I always run into problems trying to get the arm toolchain. I can't reach gnuarch.com because it is down, nor get the paket from the ubuntu ppa because it is also down or corrupted. Is there any other source where I can get the arm toolchain or any howto wich could help me? Thanks :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrmoor4 at web.de Mon Feb 18 19:10:19 2013 From: mrmoor4 at web.de (Alexander Schwankner) Date: Mon, 18 Feb 2013 20:10:19 +0100 Subject: Can't get arm toolchain In-Reply-To: <1361214326.16029.YahooMailNeo@web171206.mail.ir2.yahoo.com> References: <1361214326.16029.YahooMailNeo@web171206.mail.ir2.yahoo.com> Message-ID: *Hi, * *thanks for the answer. I got it right now to work, with this script, it is not so tricky as I excpected :)* *Now everything is compiled well and I'm trying to flash the firmware on my c123.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From GNUtoo at no-log.org Wed Feb 20 22:00:25 2013 From: GNUtoo at no-log.org (Denis 'GNUtoo' Carikli) Date: Wed, 20 Feb 2013 23:00:25 +0100 Subject: Can't get arm toolchain In-Reply-To: References: <1361214326.16029.YahooMailNeo@web171206.mail.ir2.yahoo.com> Message-ID: <20130220230025.264c7b86@m4a785t-m.gnutoo.workgroup> On Mon, 18 Feb 2013 20:10:19 +0100 Alexander Schwankner wrote: > *Hi, * Hi, > *thanks for the answer. I got it right now to work, with this script, > it is not so tricky as I excpected :)* > > *Now everything is compiled well and I'm trying to flash the firmware > on my c123.* Are you aware that flashing is not mandatory and that you can just load the firmware each time you want it? Denis. From mrmoor4 at web.de Thu Feb 21 07:43:15 2013 From: mrmoor4 at web.de (Alexander Schwankner) Date: Thu, 21 Feb 2013 08:43:15 +0100 Subject: Can't get arm toolchain In-Reply-To: <20130220230025.264c7b86@m4a785t-m.gnutoo.workgroup> References: <1361214326.16029.YahooMailNeo@web171206.mail.ir2.yahoo.com> <20130220230025.264c7b86@m4a785t-m.gnutoo.workgroup> Message-ID: hi, Yes, I know, thats not so bad... But I have a question, the loader.bin can flash the phone, will this make the firmware persistent? Just a hypothetical question. ;) 2013/2/20 Denis 'GNUtoo' Carikli > On Mon, 18 Feb 2013 20:10:19 +0100 > Alexander Schwankner wrote: > > > *Hi, * > Hi, > > > *thanks for the answer. I got it right now to work, with this script, > > it is not so tricky as I excpected :)* > > > > *Now everything is compiled well and I'm trying to flash the firmware > > on my c123.* > Are you aware that flashing is not mandatory and that you can just load > the firmware each time you want it? > > Denis. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmjerry04 at gmail.com Tue Feb 19 08:55:41 2013 From: tmjerry04 at gmail.com (tom jerry) Date: Tue, 19 Feb 2013 11:55:41 +0300 Subject: osmocombb and raspberry pi Message-ID: hi everyone.is it possible to connect motorola c118 to the raspberry GPIO pins,since they are 3v3 logic? What is the current limitation as the GPIO pins can provide only 8mA? Is it possible to use the lcd of the c118 or the RTC on the raspberry pi via the GPIO pins? Can i use the connection via the GPIO Instead of the pl2303 based cable. Thanks. From choukoumoun at gmail.com Tue Feb 19 21:23:47 2013 From: choukoumoun at gmail.com (choukoumoun) Date: Tue, 19 Feb 2013 22:23:47 +0100 Subject: osmocombb and raspberry pi In-Reply-To: References: Message-ID: <5123ED63.1000805@gmail.com> hello, the first question is it possible to compile osmocom-bb on Rasperry ? On 19/02/2013 09:55, tom jerry wrote: > hi everyone.is it possible to > connect motorola c118 to the > raspberry > GPIO pins,since they are 3v3 logic? > What is the current limitation as > the GPIO pins can provide only > 8mA? > Is it possible to use the lcd of the > c118 or the RTC on the raspberry > pi via the GPIO pins? > Can i use the connection via the > GPIO Instead of the pl2303 based > cable. > Thanks. From tmjerry04 at gmail.com Wed Feb 20 05:16:57 2013 From: tmjerry04 at gmail.com (tom jerry) Date: Wed, 20 Feb 2013 08:16:57 +0300 Subject: osmocombb and raspberry pi In-Reply-To: <5123ED63.1000805@gmail.com> References: <5123ED63.1000805@gmail.com> Message-ID: yes its possible. See below comments.gmane.org/gmane.comp.mobile.osmocom.baseband.devel/3199 On 2/20/13, choukoumoun wrote: > hello, > > the first question is it possible to compile osmocom-bb on Rasperry ? > > > On 19/02/2013 09:55, tom jerry wrote: >> hi everyone.is it possible to >> connect motorola c118 to the >> raspberry >> GPIO pins,since they are 3v3 logic? >> What is the current limitation as >> the GPIO pins can provide only >> 8mA? >> Is it possible to use the lcd of the >> c118 or the RTC on the raspberry >> pi via the GPIO pins? >> Can i use the connection via the >> GPIO Instead of the pl2303 based >> cable. >> Thanks. > > > From ricsi at gmx.at Wed Feb 20 08:49:50 2013 From: ricsi at gmx.at (Richard Menedetter) Date: Wed, 20 Feb 2013 09:49:50 +0100 (CET) Subject: Aw: Re: osmocombb and raspberry pi In-Reply-To: References: <5123ED63.1000805@gmail.com>, Message-ID: Hi All I have tried it on Raspberry Pi. First I thought both are ARM, so no crosscompile needed. I think the hello world example worked, but nothing else. So I searched for a crosscompile howto, and compiled another Toolchain on the Pi. That worked much better. I did not use the internal UART, but used an external USB dongle. I could use the RSSI monitor, and also the layer1 worked to some extent. I could see the phone making the channel measurements, but at the end it did not associate with any channel. Does somebody have a setup on RPi where he/she can make actual calls (and hence associate with a cell)? If yes could you share how you did it? (maybe I compiled to the wrong platform?) Thanx in advance CU, Ricsi > Gesendet: Mittwoch, 20. Februar 2013 um 06:16 Uhr > Von: "tom jerry" > An: choukoumoun , baseband-devel at lists.osmocom.org > Betreff: Re: osmocombb and raspberry pi > > yes its possible. > See below > comments.gmane.org/gmane.comp.mobile.osmocom.baseband.devel/3199 > From osmocom at ehlers.info Wed Feb 20 14:36:06 2013 From: osmocom at ehlers.info (Tim Ehlers) Date: Wed, 20 Feb 2013 15:36:06 +0100 (CET) Subject: Aw: Re: osmocombb and raspberry pi In-Reply-To: References: <5123ED63.1000805@gmail.com>, Message-ID: On Wed, 20 Feb 2013, Richard Menedetter wrote: Hi Richard, > I have tried it on Raspberry Pi. > First I thought both are ARM, so no crosscompile needed. > I think the hello world example worked, but nothing else. > > So I searched for a crosscompile howto, and compiled another Toolchain on the Pi. > That worked much better. > I did not use the internal UART, but used an external USB dongle. > I could use the RSSI monitor, and also the layer1 worked to some extent. > I could see the phone making the channel measurements, but at the end it did not associate with any channel. > > Does somebody have a setup on RPi where he/she can make actual calls > (and hence associate with a cell)? If yes could you share how you did > it? (maybe I compiled to the wrong platform?) mhh, I did it the same way. I use the raspbian image from the raspberry pi foundation. I compiled exactly this version: http://bb.osmocom.org/trac/wiki/GnuArmToolchain My raspberry is resetting when I pull the USB-UART Adapter. But if it is present while booting, I can use /dev/ttyUSB0 and the mobile-app is working like on x86-Architecture: OsmocomBB# show ms MS '1' is up, service is normal IMEI: 3532900XXXXXXXX IMEISV: 353290XXXXXXXXXX IMEI generation: fixed automatic network selection state: A2 on PLMN MCC=262 MNC=07 (Germany, O2) cell selection state: C3 camped normally ARFCN=XXX(DCS) MCC=262 MNC=07 LAC=0xXXXX CELLID=0xXXXX (Germany, O2) radio ressource layer state: idle mobility management layer state: MM idle, normal service Even OpenBTS with sylvain-testing code is working. Cheers Tim From tmjerry04 at gmail.com Wed Feb 20 16:41:11 2013 From: tmjerry04 at gmail.com (tom jerry) Date: Wed, 20 Feb 2013 19:41:11 +0300 Subject: Aw: Re: osmocombb and raspberry pi In-Reply-To: References: <5123ED63.1000805@gmail.com> Message-ID: hi Tim, the RPi is resetting because the motorola cxx connected via USB is drawing more current than available.have you tried using a powered usb hub? Have tried using the UART on the gpio? From osmocom at ehlers.info Thu Feb 21 13:40:31 2013 From: osmocom at ehlers.info (Tim Ehlers) Date: Thu, 21 Feb 2013 14:40:31 +0100 (CET) Subject: Aw: Re: osmocombb and raspberry pi In-Reply-To: References: <5123ED63.1000805@gmail.com> Message-ID: On Wed, 20 Feb 2013, tom jerry wrote: Hi, > the RPi is resetting because the motorola cxx connected via USB is > drawing more current than available.have you tried using a powered usb > hub? how can that be? The Phone has a charger and a battery. Using TTL could not cost much of power. Or did I miss something? But if you are right, an active USB hub would surely help. I will test that out. > Have tried using the UART on the gpio? Not yet. That will be one of the next tasks. Cheers Tim From tmjerry04 at gmail.com Fri Feb 22 22:30:44 2013 From: tmjerry04 at gmail.com (tom jerry) Date: Sat, 23 Feb 2013 01:30:44 +0300 Subject: Aw: Re: osmocombb and raspberry pi In-Reply-To: References: <5123ED63.1000805@gmail.com> Message-ID: hi, with osmocombb,is it possible to do voip? On 2/20/13, tom jerry wrote: > hi Tim, > the RPi is resetting because the motorola cxx connected via USB is > drawing more current than available.have you tried using a powered usb > hub? > Have tried using the UART on the gpio? > From choukoumoun at gmail.com Wed Feb 20 20:20:03 2013 From: choukoumoun at gmail.com (choukoumoun) Date: Wed, 20 Feb 2013 21:20:03 +0100 Subject: osmocombb and raspberry pi In-Reply-To: References: <5123ED63.1000805@gmail.com> Message-ID: <51252FF3.30602@gmail.com> Niiiiiiiiiice thanks !!!! On 20/02/2013 06:16, tom jerry wrote: > yes its possible. > See below > comments.gmane.org/gmane.comp.mobile.osmocom.baseband.devel/3199 > > > On 2/20/13, choukoumoun wrote: >> hello, >> >> the first question is it possible to compile osmocom-bb on Rasperry ? >> >> >> On 19/02/2013 09:55, tom jerry wrote: >>> hi everyone.is it possible to >>> connect motorola c118 to the >>> raspberry >>> GPIO pins,since they are 3v3 logic? >>> What is the current limitation as >>> the GPIO pins can provide only >>> 8mA? >>> Is it possible to use the lcd of the >>> c118 or the RTC on the raspberry >>> pi via the GPIO pins? >>> Can i use the connection via the >>> GPIO Instead of the pl2303 based >>> cable. >>> Thanks. >> >> From holger at freyther.de Sun Feb 24 08:57:32 2013 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Sun, 24 Feb 2013 09:57:32 +0100 Subject: Anyone interested in broken C118s? Message-ID: <20130224085732.GC5101@xiaoyu.lan> Hi, I have about 8 broken C118 and wonder if someone would be interested to save them from the recycling system. The defects vary but in some cases it is a broken buzzer, issues with the SIM card holder, missing or broken audio socket. This will just be the phone, no battery, no charger. I would like to get rid of them in batches of two. Is anyone interested? The postage should be paid by the receiver. cheers holger From ricsi at gmx.at Sun Feb 24 13:49:22 2013 From: ricsi at gmx.at (Richard Menedetter) Date: Sun, 24 Feb 2013 14:49:22 +0100 (CET) Subject: Osmovom-BB on Raspberry Pi Message-ID: 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=GettingStarted 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. From 246tnt at gmail.com Sun Feb 24 14:33:42 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sun, 24 Feb 2013 15:33:42 +0100 Subject: Osmovom-BB on Raspberry Pi In-Reply-To: References: Message-ID: > PS: Any news on the "emulated BTS" that has been presented at last years chaos communication congress? http://bb.osmocom.org/trac/wiki/Software/Transceiver Cheers, Sylvain From martin.zicke at gmx.de Thu Feb 28 02:02:05 2013 From: martin.zicke at gmx.de (Madin) Date: Wed, 27 Feb 2013 18:02:05 -0800 (PST) Subject: Osmovom-BB on Raspberry Pi In-Reply-To: References: Message-ID: <1362016925226-4025886.post@n3.nabble.com> Hi nice to hear your success, but I've got stuck with it at making osmocom-bb: ============================================ ..... config.status: creating Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing tests/atconfig commands config.status: executing depfiles commands config.status: executing libtool commands configure: WARNING: unrecognized options: --disable-tests, --disable-tests cd shared/libosmocore/build-target && make make[1]: Entering directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target' make all-recursive make[2]: Entering directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target' Making all in include make[3]: Entering directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/include' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/include' Making all in src make[3]: Entering directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/src' make all-am make[4]: Entering directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/src' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/src' make[3]: Leaving directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/src' Making all in src/vty make[3]: Entering directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/src/vty' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/src/vty' Making all in src/codec make[3]: Entering directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/src/codec' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/src/codec' Making all in src/gsm make[3]: Entering directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/src/gsm' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/src/gsm' Making all in src/gb make[3]: Entering directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/src/gb' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/src/gb' Making all in tests make[3]: Entering directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/tests' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/tests' Making all in utils make[3]: Entering directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/utils' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target/utils' make[3]: Entering directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target' make[3]: Leaving directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target' make[2]: Leaving directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target' make[1]: Leaving directory `/home/pi/osmocom-bb/src/shared/libosmocore/build-target' make -C host/layer23 make[1]: Entering directory `/home/pi/osmocom-bb/src/host/layer23' Making all in include make[2]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/include' Making all in osmocom make[3]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom' Making all in bb make[4]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom/bb' Making all in common make[5]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom/bb/common' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom/bb/common' Making all in misc make[5]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom/bb/misc' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom/bb/misc' Making all in mobile make[5]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom/bb/mobile' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom/bb/mobile' make[5]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom/bb' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom/bb' make[4]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom/bb' make[4]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom' make[3]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/include/osmocom' make[3]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/include' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/include' make[2]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/include' Making all in src make[2]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/src' Making all in common make[3]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/src/common' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/src/common' Making all in misc make[3]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/src/misc' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/src/misc' Making all in mobile make[3]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/src/mobile' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/src/mobile' make[3]: Entering directory `/home/pi/osmocom-bb/src/host/layer23/src' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/src' make[2]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23/src' make[2]: Entering directory `/home/pi/osmocom-bb/src/host/layer23' make[2]: Nothing to be done for `all-am'. make[2]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23' make[1]: Leaving directory `/home/pi/osmocom-bb/src/host/layer23' make -C target/firmware CROSS_COMPILE=arm-elf- make[1]: Entering directory `/home/pi/osmocom-bb/src/target/firmware' LD board/compal_e88/hello_world.highram.elf arm-elf-ld: error: Source object ../../shared/libosmocore/build-target/src/.libs/libosmocore.a(msgb.o) has EABI version 5, but target board/compal_e88/hello_world.highram.elf has EABI version 0 arm-elf-ld: failed to merge target specific data of file ../../shared/libosmocore/build-target/src/.libs/libosmocore.a(msgb.o) make[1]: *** [board/compal_e88/hello_world.highram.elf] Error 1 make[1]: Leaving directory `/home/pi/osmocom-bb/src/target/firmware' make: *** [firmware] Error 2 pi at raspberrypi ~/osmocom-bb/src $ ============================================== Does anyone have a clue - and can help me - what I've been doing wrong (again ;-))? Thanks in advance, regards, Martin -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Osmovom-BB-on-Raspberry-Pi-tp4025859p4025886.html Sent from the baseband-devel mailing list archive at Nabble.com. From dario.lombardo.ml at gmail.com Mon Feb 25 09:54:20 2013 From: dario.lombardo.ml at gmail.com (Dario Lombardo) Date: Mon, 25 Feb 2013 10:54:20 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) Message-ID: Hi, I'm having a try with your software. A small suggestion I can give you is about the chapter "Starting OpenBTS" of your howto: a better way to host the transceiver script is to create a new dir under the openbts root (lets call it TransceiverOSMOCOM) that hosts your script. Then to create a link in the apps dir that point to the new transceiver, to follow the model openbts uses. This allows the user to switch between many hardware pieces using the same openbts installation (if compilation flags apply), avoiding to overwrite your script if openbts compilation instructions are literally followed. Just my 2 cents. Dario. On Sun, Feb 24, 2013 at 3:33 PM, Sylvain Munaut <246tnt at gmail.com> wrote: >> PS: Any news on the "emulated BTS" that has been presented at last years chaos communication congress? > > http://bb.osmocom.org/trac/wiki/Software/Transceiver > > Cheers, > > Sylvain > From dario.lombardo.ml at gmail.com Mon Feb 25 13:21:46 2013 From: dario.lombardo.ml at gmail.com (Dario Lombardo) Date: Mon, 25 Feb 2013 14:21:46 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: I'm not succeeding in using the osmocom transceiver. When openbts starts, the output shown is (a bunch of) <0011> trx.c:190 TRX CLK Indication 1029029 <0011> trx.c:512 TRX Data 1029080:0:0:aac274073b9d407eb0bc014ed71e20 <0011> trx.c:512 TRX Data 1029081:0:0:61dbebb006fec0f9895e448fcafd10 <0011> trx.c:512 TRX Data 1029082:0:0:378d60f0c61b90eb0c9e1208114190 <0011> trx.c:512 TRX Data 1029083:0:0:a013ce5f9090c67e18229311431a30 When the osmocom mobile tries to attach, the output becomes <0011> trx.c:512 TRX Data 1029491:0:0:a013ce5f9090c67e18229311431a30 <0012> l1ctl.c:351 Reset received: Starting sync. <0011> trx.c:512 TRX Data 1029539:0:0:a14dd532a16dc062d07c030e055510 <0011> trx.c:512 TRX Data 1029540:0:0:82b7c400ae9e53e9bd7a0007bf5460 <0011> trx.c:512 TRX Data 1029541:0:0:842dd0834051146707753011978620 <0011> trx.c:512 TRX Data 1029542:0:0:9000ea751006a7f0380b57d421fe50 <0012> l1ctl.c:305 Sync failed, retrying ... <0012> l1ctl.c:351 Reset received: Starting sync. <0011> trx.c:512 TRX Data 1029590:0:0:aac274073b9d407eb0bc014ed71e20 <0011> trx.c:512 TRX Data 1029591:0:0:61dbebb006fec0f9895e448fcafd10 <0011> trx.c:512 TRX Data 1029592:0:0:378d60f0c61b90eb0c9e1208114190 <0011> trx.c:512 TRX Data 1029593:0:0:a013ce5f9090c67e18229311431a30 <0012> l1ctl.c:308 Sync acquired, wait for BCCH ... <0012> l1ctl.c:351 Reset received: Starting sync. <0012> l1ctl.c:308 Sync acquired, wait for BCCH ... <0012> l1ctl.c:351 Reset received: Starting sync. <0011> trx.c:512 TRX Data 1029641:0:0:8062948a52a104e0402112806004a0 <0011> trx.c:512 TRX Data 1029642:0:0:118a5288440000e102854a018a1600 <0011> trx.c:512 TRX Data 1029643:0:0:408904254000607400058000200220 <0011> trx.c:512 TRX Data 1029644:0:0:44a542052054286588022012a16200 <0012> l1ctl.c:308 Sync acquired, wait for BCCH ... <0012> l1ctl.c:351 Reset received: Starting sync. <0011> trx.c:512 TRX Data 1029692:0:0:aac274073b9d407eb0bc014ed71e20 <0011> trx.c:512 TRX Data 1029693:0:0:61dbebb006fec0f9895e448fcafd10 <0011> trx.c:512 TRX Data 1029694:0:0:378d60f0c61b90eb0c9e1208114190 <0011> trx.c:512 TRX Data 1029695:0:0:a013ce5f9090c67e18229311431a30 <0011> trx.c:512 TRX Data 1029743:0:0:a14dd532a16dc062d07c030e055510 <0011> trx.c:512 TRX Data 1029744:0:0:82b7c400ae9e53e9bd7a0007bf5460 <0011> trx.c:512 TRX Data 1029745:0:0:842dd0834051146707753011978620 <0011> trx.c:512 TRX Data 1029746:0:0:9000ea751006a7f0380b57d421fe50 <0012> l1ctl.c:308 Sync acquired, wait for BCCH ... <0012> l1ctl.c:351 Reset received: Starting sync. Until I get ALERT 3063667520 TRXManager.cpp:93:clockHandler: TRX clock interface timed out, assuming TRX is dead. from openbts. Output from osmocom mobile is <0003> gsm322.c:2939 Channel synched on wrong ARFCN=XX, syncing on right ARFCN again... <0003> gsm322.c:474 Sync to ARFCN=0 rxlev=<=-110 (No sysinfo yet, ccch mode NONE) XX is the arfcn of the reference cell. Changing it doesn't change the behavior. I've put this value as param for transceiver, according to the instructions. Any suggestion? Thanks a lot. Dario. From 246tnt at gmail.com Mon Feb 25 13:28:09 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 25 Feb 2013 14:28:09 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: > When the osmocom mobile tries to attach, the output becomes WTF are you trying to do ? You can't use the phone with both the 'transceiver' and the 'mobile' application at the same time ! Cheers, Sylvain From dario.lombardo.ml at gmail.com Mon Feb 25 13:33:03 2013 From: dario.lombardo.ml at gmail.com (Dario Lombardo) Date: Mon, 25 Feb 2013 14:33:03 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: That's obvious. I'm using 2 phones. One as bts, other as subscriber. On Mon, Feb 25, 2013 at 2:28 PM, Sylvain Munaut <246tnt at gmail.com> wrote: >> When the osmocom mobile tries to attach, the output becomes > > WTF are you trying to do ? > > You can't use the phone with both the 'transceiver' and the 'mobile' > application at the same time ! > > > Cheers, > > Sylvain From 246tnt at gmail.com Mon Feb 25 13:35:04 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 25 Feb 2013 14:35:04 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: > That's obvious. I would think so, but from the logs, it really looks like the same phone is trying to act as both. Try not using 'mobile' at all and just use any plain old phone. (or the phone with its original firmware). Cheers, Sylvain From dario.lombardo.ml at gmail.com Mon Feb 25 13:58:47 2013 From: dario.lombardo.ml at gmail.com (Dario Lombardo) Date: Mon, 25 Feb 2013 14:58:47 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: This is what happens when using original motorola fw (logs from openbts, cut where reported) 1361800521.515924 3073959680: Starting the system... transceiver: no process found 36 41 1 <0011> trx.c:419 TRX Control recv: |RXTUNE|897000| <0011> trx.c:331 Setting C0 ARFCN to 35 (GSM900) <0011> trx.c:220 TRX Control send: |RSP RXTUNE 0 897000| <0011> trx.c:419 TRX Control recv: |TXTUNE|942000| <0011> trx.c:220 TRX Control send: |RSP TXTUNE 0 942000| <0011> trx.c:419 TRX Control recv: |SETBSIC|2| <0011> trx.c:220 TRX Control send: |RSP SETBSIC 0| <0011> trx.c:419 TRX Control recv: |SETMAXDLY|1| <0011> trx.c:220 TRX Control send: |RSP SETMAXDLY 0 1| <0011> trx.c:419 TRX Control recv: |SETRXGAIN|47| <0011> trx.c:220 TRX Control send: |RSP SETRXGAIN 0 47| <0011> trx.c:419 TRX Control recv: |POWERON|| <0011> trx.c:220 TRX Control send: |RSP POWERON 0| <0011> trx.c:419 TRX Control recv: |SETPOWER|0| <0011> trx.c:220 TRX Control send: |RSP SETPOWER 0 0| <0011> trx.c:419 TRX Control recv: |SETSLOT|0 5| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 5| <0011> trx.c:512 TRX Data 2348:0:0:abca74273bbd00fef0b5414bd71a00 [cut] <0011> trx.c:512 TRX Data 2385:0:0:10aabdd500aefd7102ab75108bbd50 <0011> trx.c:419 TRX Control recv: |SETSLOT|1 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETSLOT|2 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETSLOT|3 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETSLOT|4 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETSLOT|5 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETSLOT|6 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETSLOT|7 1| <0011> trx.c:220 TRX Control send: |RSP SETSLOT 0 1| <0011> trx.c:419 TRX Control recv: |SETPOWER|10| <0011> trx.c:220 TRX Control send: |RSP SETPOWER 0 10| system ready use the OpenBTSCLI utility to access CLI <0011> trx.c:512 TRX Data 2388:0:0:4b90da4280e504e8e00d00a204d060 [cut] <0011> trx.c:512 TRX Data 2861:0:0:4421420408540070a810001a212280 <0011> trx.c:419 TRX Control recv: |SETPOWER|9| <0011> trx.c:220 TRX Control send: |RSP SETPOWER 0 9| <0011> trx.c:512 TRX Data 2949:0:0:811aa402902001ea40084681028040 [cut] <0011> trx.c:512 TRX Data 4136:0:0:44a542052054286588022012a16200 <0011> trx.c:419 TRX Control recv: |SETPOWER|8| <0011> trx.c:220 TRX Control send: |RSP SETPOWER 0 8| <0011> trx.c:512 TRX Data 4184:0:0:abca74273bbd00fef0b5414bd71a00 [cut] <0011> trx.c:512 TRX Data 4544:0:0:44a542052054286588022012a16200 ALERT 3063667520 TRXManager.cpp:93:clockHandler: TRX clock interface timed out, assuming TRX is dead. <0011> trx.c:512 TRX Data 4592:0:0:abca74273bbd00fef0b5414bd71a00 <0011> trx.c:512 TRX Data 4593:0:0:6193ebb006fec0f1895b448faaec90 <0011> trx.c:512 TRX Data 4594:0:0:37af2071c41b986e0c9a5218b14110 <0011> trx.c:512 TRX Data 4595:0:0:a01acc5b9814c67a7832b353421a10 Aborted (core dumped) On Mon, Feb 25, 2013 at 2:35 PM, Sylvain Munaut <246tnt at gmail.com> wrote: >> That's obvious. > > I would think so, but from the logs, it really looks like the same > phone is trying to act as both. > > Try not using 'mobile' at all and just use any plain old phone. (or > the phone with its original firmware). > > Cheers, > > Sylvain From 246tnt at gmail.com Mon Feb 25 14:03:22 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 25 Feb 2013 15:03:22 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: > This is what happens when using original motorola fw (logs from > openbts, cut where reported) And the osmocon logs ? Cheers, Sylvain From dario.lombardo.ml at gmail.com Mon Feb 25 14:28:33 2013 From: dario.lombardo.ml at gmail.com (Dario Lombardo) Date: Mon, 25 Feb 2013 15:28:33 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=36, flags=0x7) Starting FCCH RecognitionFB0 (3164:6): TOA= 6672, Power= -83dBm, Angle= 644Hz FB1 (3174:8): TOA= 9151, Power= -83dBm, Angle= 180Hz fn_offset=3173 (fn=3174 + attempt=8 + ntdma = 7) delay=9 (fn_offset=3173 + 11 - fn=3174 - 1 scheduling next FB/SB detection task with delay 9 =>FB @ FNR 3173 fn_offset=3173 qbits=1420 Synchronize_TDMA LOST 2436! SB2 (6353:2): TOA= 23, Power= -83dBm, Angle= 167Hz => SB 0x009ce14a: BSIC=18 fn=1956871(1475/ 7/ 1) qbits=0 Synchronize_TDMA =>FB @ FNR 6351 fn_offset=1956870 qbits=4908 LOST 1903! Apart from that, only battery indications are shown. On Mon, Feb 25, 2013 at 3:03 PM, Sylvain Munaut <246tnt at gmail.com> wrote: >> This is what happens when using original motorola fw (logs from >> openbts, cut where reported) > > And the osmocon logs ? > > > Cheers, > > Sylvain From 246tnt at gmail.com Mon Feb 25 14:36:04 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 25 Feb 2013 15:36:04 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: Hi. > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=36, flags=0x7) > Starting FCCH RecognitionFB0 (3164:6): TOA= 6672, Power= -83dBm, Angle= 644Hz > FB1 (3174:8): TOA= 9151, Power= -83dBm, Angle= 180Hz > fn_offset=3173 (fn=3174 + attempt=8 + ntdma = 7) > delay=9 (fn_offset=3173 + 11 - fn=3174 - 1 > scheduling next FB/SB detection task with delay 9 > =>FB @ FNR 3173 fn_offset=3173 qbits=1420 > Synchronize_TDMA > LOST 2436! > SB2 (6353:2): TOA= 23, Power= -83dBm, Angle= 167Hz > => SB 0x009ce14a: BSIC=18 fn=1956871(1475/ 7/ 1) qbits=0 > Synchronize_TDMA > =>FB @ FNR 6351 fn_offset=1956870 qbits=4908 > LOST 1903! Looks like it can't sync to the reference cell. Cheers, Sylvain From dario.lombardo.ml at gmail.com Mon Feb 25 15:31:47 2013 From: dario.lombardo.ml at gmail.com (Dario Lombardo) Date: Mon, 25 Feb 2013 16:31:47 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: I've changed the ref cell, and now I can see BTS MODE: 2 35 in trx logs. I suppose something is working now, since I can see my imsis in "tmsis" output from openbtscli. I can't register to the network, but I think that now is something related to the "core" (openbts/sipauthregister/asterisk), not radio. One question more: is the osmocom transceiver able to handle sms as other transceivers? On Mon, Feb 25, 2013 at 3:36 PM, Sylvain Munaut <246tnt at gmail.com> wrote: > Hi. > >> L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=36, flags=0x7) >> Starting FCCH RecognitionFB0 (3164:6): TOA= 6672, Power= -83dBm, Angle= 644Hz >> FB1 (3174:8): TOA= 9151, Power= -83dBm, Angle= 180Hz >> fn_offset=3173 (fn=3174 + attempt=8 + ntdma = 7) >> delay=9 (fn_offset=3173 + 11 - fn=3174 - 1 >> scheduling next FB/SB detection task with delay 9 >> =>FB @ FNR 3173 fn_offset=3173 qbits=1420 >> Synchronize_TDMA >> LOST 2436! >> SB2 (6353:2): TOA= 23, Power= -83dBm, Angle= 167Hz >> => SB 0x009ce14a: BSIC=18 fn=1956871(1475/ 7/ 1) qbits=0 >> Synchronize_TDMA >> =>FB @ FNR 6351 fn_offset=1956870 qbits=4908 >> LOST 1903! > > Looks like it can't sync to the reference cell. > > Cheers, > > Sylvain From 246tnt at gmail.com Mon Feb 25 15:34:01 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 25 Feb 2013 16:34:01 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: Hi, > I can't register to the network, but I think that now is something > related to the "core" (openbts/sipauthregister/asterisk), not radio. Yes, most likely. > One question more: is the osmocom transceiver able to handle sms as > other transceivers? Yes, it can handle SMS. But not calls. Cheers, Sylvain From dario.lombardo.ml at gmail.com Mon Feb 25 15:36:26 2013 From: dario.lombardo.ml at gmail.com (Dario Lombardo) Date: Mon, 25 Feb 2013 16:36:26 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: On Mon, Feb 25, 2013 at 4:34 PM, Sylvain Munaut <246tnt at gmail.com> wrote: > Yes, it can handle SMS. But not calls. Why not? Is is something software-related, or hardware limit? From 246tnt at gmail.com Mon Feb 25 15:51:27 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 25 Feb 2013 16:51:27 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: > Why not? Because the current code only supports 1 bidirectional timeslot and it's used for the beacon and control channels. > Is is something software-related, or hardware limit? Either ... Watch the talk, it's explained. From dario.lombardo.ml at gmail.com Mon Feb 25 15:57:32 2013 From: dario.lombardo.ml at gmail.com (Dario Lombardo) Date: Mon, 25 Feb 2013 16:57:32 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: Do you think it would be possible to have one single transceiver that drives 2 phones in order to have more TS? On Mon, Feb 25, 2013 at 4:51 PM, Sylvain Munaut <246tnt at gmail.com> wrote: >> Why not? > > Because the current code only supports 1 bidirectional timeslot and > it's used for the beacon and control channels. > > >> Is is something software-related, or hardware limit? > > Either ... Watch the talk, it's explained. From 246tnt at gmail.com Mon Feb 25 16:02:59 2013 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 25 Feb 2013 17:02:59 +0100 Subject: Osmocom Transceiver (was: Osmovom-BB on Raspberry Pi) In-Reply-To: References: Message-ID: > Do you think it would be possible to have one single transceiver that > drives 2 phones in order to have more TS? If there is ONE thing, I _HATE_ above all, is when people make me repeat myself !!! >> Watch the talk, it's explained. From bouchtaoui at gmail.com Mon Feb 25 14:25:00 2013 From: bouchtaoui at gmail.com (nordin) Date: Mon, 25 Feb 2013 15:25:00 +0100 Subject: Osmocom Transceiver In-Reply-To: References: Message-ID: <512B743C.7000204@gmail.com> Assumption is the mother of all fuck. On 25-2-2013 14:33, Dario Lombardo wrote: > That's obvious. I'm using 2 phones. > One as bts, other as subscriber. > > On Mon, Feb 25, 2013 at 2:28 PM, Sylvain Munaut <246tnt at gmail.com> wrote: >>> When the osmocom mobile tries to attach, the output becomes >> WTF are you trying to do ? >> >> You can't use the phone with both the 'transceiver' and the 'mobile' >> application at the same time ! >> >> >> Cheers, >> >> Sylvain -- *Name: Nordin el Bouchtaoui* *Mail client: Thunderbird Mozilla Opensource project* *web: http://www.linux.org* -------------- next part -------------- An HTML attachment was scrubbed... URL: From mr.shahzeb at hotmail.com Mon Feb 25 12:06:16 2013 From: mr.shahzeb at hotmail.com (Shahzeb -) Date: Mon, 25 Feb 2013 17:06:16 +0500 Subject: trouble while using sony erricson J100i Message-ID: hi all i cant understand where i am wrong when i run this command this is the response which i get root at shahzeb-laptop:~/Desktop/toolchain/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c140xor -c ../../target/firmware/board/se_j100/layer1.highram.bin got 1 bytes from modem, data looks like: 00 . and then it gets hanged and nothing happens. i have checked the cable aswell it seems like cable is working i have consulted J100i_cable.pdf for the data cable. i would really appreciate your help thanks shahzeb -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Tue Feb 26 20:30:28 2013 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 26 Feb 2013 21:30:28 +0100 Subject: [ANNOUNCE] OsmoDevCon 2013-04-04 till 2013-04-07, Berlin Message-ID: <20130226203028.GK1262@prithivi.gnumonks.org> Dear fellow Osmcoom developers, it is my pleasure to finally announce the date + venue of OsmoDevCon 2013: Date: April 04 through April 07, 2013 Place: IN-Berlin, Lehrter Str. 53, Berlin Like last year, this is an event for developers of the various Osmocom proejects. Reservation and confirmation of reservation is required. The event is free of charge. The Room is made available by IN-Berlin e.V., an Internet related non-profit organization. Lunch catering will be sponsored (so far by sysmocom GmbH, but if any other sponsors come up, we are happy to share the cost). So all you have to cover is your own travel + accomodation costs, as well as breakfast and dinner. If you are an active developer and cannot afford travel/accomodation, please let me know and I'll see if we can do something about it. If you would like to attend, please send a message to laforge at gnumonks.org applying for registration of the event. The registration deadline is March 5, i.e. one week from now. There is no detailed schedule of talks yet. I will start a separate discussion suggesting / collecting topics in the next couple of days. More information is (and will be made) available at http://openbsc.osmocom.org/trac/wiki/OsmoDevCon2013 Further discussion regarding the event should be directed at the osmocom-event-orga at lists.osmocom.org mailing list, to avoid cross-posting over the various project-specific lists. Best regards and happy hacking, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 190 bytes Desc: Digital signature URL: From arslan.anj at gmail.com Tue Feb 26 23:16:57 2013 From: arslan.anj at gmail.com (Arslan Anjum) Date: Wed, 27 Feb 2013 04:16:57 +0500 Subject: Error: no such instruction: `eor %edx,%ecx,%ecx,ror' Message-ID: Hello All, I can't compile after the last pull. I know that it is an error with toolchain detection but I have tried almost everything. ------------------------------- As you can see the $PATH variable has the address to gnu-arm-elf binary : arslan at arslan-Lenovo-B575:~/osmocom-bb/src$ echo $PATH /home/arslan/arm-elf/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games ------------------------------- and when I list the items in that directory I can clearly see that the binary is there : arslan at arslan-Lenovo-B575:~/arm-elf/bin$ ls arm-elf-addr2line arm-elf-cpp arm-elf-ld arm-elf-size arm-elf-ar arm-elf-g++ arm-elf-nm arm-elf-strings arm-elf-as arm-elf-gcc arm-elf-objcopy arm-elf-strip arm-elf-c++ arm-elf-gcc-4.0.4 arm-elf-objdump arm-elf-cc arm-elf-gccbug arm-elf-ranlib arm-elf-c++filt arm-elf-gcov arm-elf-readelf ------------------------------- But I still get the following error: /home/arslan/osmocom-bb/src/target/firmware/include/asm/swab.h: Assembler messages: /home/arslan/osmocom-bb/src/target/firmware/include/asm/swab.h:32: Error: no such instruction: `eor %edx,%ecx,%ecx,ror' make[4]: *** [gsmtap_util.lo] Error 1 make[4]: Leaving directory `/home/arslan/osmocom-bb/src/shared/libosmocore/build-target/src' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/arslan/osmocom-bb/src/shared/libosmocore/build-target/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/arslan/osmocom-bb/src/shared/libosmocore/build-target' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/arslan/osmocom-bb/src/shared/libosmocore/build-target' make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] Error 2 Regards, Arslan Anjum Research Assitant Lahore University of Management Sciences, Pakistan From peter at stuge.se Wed Feb 27 02:02:33 2013 From: peter at stuge.se (Peter Stuge) Date: Wed, 27 Feb 2013 03:02:33 +0100 Subject: Error: no such instruction: `eor %edx,%ecx,%ecx,ror' In-Reply-To: References: Message-ID: <20130227020233.7834.qmail@stuge.se> Arslan Anjum wrote: > I can't compile after the last pull. Your build is using a host library for the target binary build, which of course can't work. //Peter From arslan.anj at gmail.com Wed Feb 27 05:56:41 2013 From: arslan.anj at gmail.com (Arslan Anjum) Date: Wed, 27 Feb 2013 10:56:41 +0500 Subject: Error: no such instruction: `eor %edx,%ecx,%ecx,ror' In-Reply-To: <20130227020233.7834.qmail@stuge.se> References: <20130227020233.7834.qmail@stuge.se> Message-ID: How do I fix that? Arslan On Wed, Feb 27, 2013 at 7:02 AM, Peter Stuge wrote: > Arslan Anjum wrote: >> I can't compile after the last pull. > > Your build is using a host library for the target binary build, which > of course can't work. > > > //Peter > From peter at stuge.se Wed Feb 27 15:04:39 2013 From: peter at stuge.se (Peter Stuge) Date: Wed, 27 Feb 2013 16:04:39 +0100 Subject: Error: no such instruction: `eor %edx,%ecx,%ecx,ror' In-Reply-To: References: <20130227020233.7834.qmail@stuge.se> Message-ID: <20130227150440.3280.qmail@stuge.se> A: Because it is backwards, confusing and doesn't make sense. Q: Why should I never top-post? Arslan Anjum wrote: > >> I can't compile after the last pull. > > > > Your build is using a host library for the target binary build, which > > of course can't work. > > How do I fix that? By giving the build commands parameters that are appropriate for how you have arranged the many different components on your system. If you have no clue about how the build commands work then probably you have to start with studying that for a while. Key words are autoconf, automake and libtool, sometimes collectively called autotools. //Peter From choukoumoun at gmail.com Tue Feb 26 23:52:10 2013 From: choukoumoun at gmail.com (choukoumoun) Date: Wed, 27 Feb 2013 00:52:10 +0100 Subject: Paging Attack 29C3 Message-ID: <512D4AAA.1030607@gmail.com> hello aliens of osmoland! I saw Nico Golde conference, he did a great job. but the code has not been shared? -------------- next part -------------- An HTML attachment was scrubbed... URL: From osmocom at ngolde.de Wed Feb 27 11:24:00 2013 From: osmocom at ngolde.de (Nico Golde) Date: Wed, 27 Feb 2013 12:24:00 +0100 Subject: Paging Attack 29C3 In-Reply-To: <512D4AAA.1030607@gmail.com> References: <512D4AAA.1030607@gmail.com> Message-ID: <20130227112400.GD14246@ngolde.de> Hi, * choukoumoun [2013-02-27 02:17]: > I saw Nico Golde conference, he did a great job. but the code has not been > shared? Correct because I was too busy cleaning it up. I gave it to selected people who asked me personally already though. I will put it online soon, either as an uncleaned diff or a remote branch in the osmocom git. Cheers Nico -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From akibsayyed at gmail.com Thu Feb 28 10:15:37 2013 From: akibsayyed at gmail.com (Akib Sayyed) Date: Thu, 28 Feb 2013 13:15:37 +0300 Subject: Decoding AMR Message-ID: Dear Sylvain While Decoding AMR do need to just decode and pack it into raw amr frames or we need to think about hysterasis and all parts also also there are total 8 codec modes but in band data have details of on 4 codec modes which one to choose out of 8 codec modes from those 8 modes. -- Akib Sayyed Matrix-Shell akibsayyed at gmail.com akibsayyed at matrixshell.com Mob:- +91-966-514-2243 -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Thu Feb 28 11:37:09 2013 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 28 Feb 2013 12:37:09 +0100 Subject: Decoding AMR In-Reply-To: References: Message-ID: <20130228113709.GS1262@prithivi.gnumonks.org> Dear Akib, I think it is best if you start to read the actual relevant GSM specifications if you want to implement part of it. The key word to search for is probably the 'active code mode set'. At any given point in time, there can only be a set of four active codecs in an AMR connection. The codec currently used within that set is selected with CMI/CMR bits on the L1 of the air interface. The selection of which four codecs are part of the currently active set is explicitly configured by signalling messages on RSL between BTS and BSC, as well as on Layer3 (RR) between BSC and MS. On Thu, Feb 28, 2013 at 01:15:37PM +0300, Akib Sayyed wrote: > Dear Sylvain > > > While Decoding AMR do need to just decode and pack it into raw amr frames > or we need to think about hysterasis and all parts also > > > also there are total 8 codec modes > > but in band data have details of on 4 codec modes > > which one to choose out of 8 codec modes from those 8 modes. > > > > > > > -- > Akib Sayyed > Matrix-Shell > akibsayyed at gmail.com > akibsayyed at matrixshell.com > Mob:- +91-966-514-2243 -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From akibsayyed at gmail.com Thu Feb 28 14:54:27 2013 From: akibsayyed at gmail.com (Akib Sayyed) Date: Thu, 28 Feb 2013 17:54:27 +0300 Subject: Decoding AMR In-Reply-To: <20130228113709.GS1262@prithivi.gnumonks.org> References: <20130228113709.GS1262@prithivi.gnumonks.org> Message-ID: Thanks for Quick response. I tried studying TSM code layer1 and Osmocom layer1 for purpose of implementing them in cellphone it self but i as far as i know that init of some variables required for amr are completed but couldnt be able to figure out what exactly part remaining . also for decoding AMR convolution i made some changes to structures given by sylvain. I didnt know what i was doing but gave me correct output for encoding and decoding. but still i doubt its correctness. It would be great if some one could comment on these files. may be need to pay attention soon On Thu, Feb 28, 2013 at 2:37 PM, Harald Welte wrote: > Dear Akib, > > I think it is best if you start to read the actual relevant GSM > specifications if you want to implement part of it. The key word to > search for is probably the 'active code mode set'. > > I will try to check specs again. i am really doubting about hysteresis part. cause i dont know whether its needed or not while storing raw frames. if any one know please let me know shall save my time. > At any given point in time, there can only be a set of four active > codecs in an AMR connection. The codec currently used within that set > is selected with CMI/CMR bits on the L1 of the air interface. thanks for pointing out. > The selection of which four codecs are part of the currently active set > is > explicitly configured by signalling messages on RSL between BTS and BSC, > as well as on Layer3 (RR) between BSC and MS. > > On Thu, Feb 28, 2013 at 01:15:37PM +0300, Akib Sayyed wrote: > > Dear Sylvain > > > > > > While Decoding AMR do need to just decode and pack it into raw amr frames > > or we need to think about hysterasis and all parts also > > > > > > also there are total 8 codec modes > > > > but in band data have details of on 4 codec modes > > > > which one to choose out of 8 codec modes from those 8 modes. > > > > > > > > > > > > > > -- > > Akib Sayyed > > Matrix-Shell > > akibsayyed at gmail.com > > akibsayyed at matrixshell.com > > Mob:- +91-966-514-2243 > > -- > - Harald Welte > http://laforge.gnumonks.org/ > > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. > A6) > -- Akib Sayyed Matrix-Shell akibsayyed at gmail.com akibsayyed at matrixshell.com Mob:- +91-966-514-2243 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: conv_tch_afs.c Type: text/x-csrc Size: 18111 bytes Desc: not available URL: From laforge at gnumonks.org Thu Feb 28 15:43:08 2013 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 28 Feb 2013 16:43:08 +0100 Subject: Decoding AMR In-Reply-To: References: <20130228113709.GS1262@prithivi.gnumonks.org> Message-ID: <20130228154308.GC1262@prithivi.gnumonks.org> On Thu, Feb 28, 2013 at 05:54:27PM +0300, Akib Sayyed wrote: > I tried studying TSM code layer1 and Osmocom layer1 for purpose of > implementing them in cellphone it self but i as far as i know that init of > some variables required for amr are completed but couldnt be able to > figure out what exactly part remaining . I remain with what I stated before: you first need to understand the detailed operation of AMR in the context of GSM by studying the specs. I'm mostly talking about the encoding of the various bits, signalling of codec mode changes, etc. - not the mathematical background of the actual voice codec. It might also help to study related documents like the IF2 and RTP formats for AMR. Only with that backgorund knowledge _and_ knowledge of the TSM30 L1 code as well as traces from actual AMR calls on A-bis and possibly Um, I think you will be in a position to fully understand the porblem and implement what is needed. Asking for somebody to explain every little detail for you is not the way to solve any problem. If Sylvian, Dieter, Andreas or I sit down, read the code + dosc, and give minute instructions what needs to be done, this consumes more of our time than if we actuall implement it ourselves. If you have _specific_ technical questions, please come back to the list. If you have a specific question, please include a precise reference to the chapter/section of the specification (+ exact version of the document), the exact function or data structure you refer to. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From edachleger at yahoo.com Thu Feb 28 12:01:22 2013 From: edachleger at yahoo.com (Erich Dachleger) Date: Thu, 28 Feb 2013 12:01:22 +0000 (GMT) Subject: trouble loading trx-firmware Message-ID: <1362052882.78529.YahooMailNeo@web171205.mail.ir2.yahoo.com> Hi list, I am trying, with no success so far ,to chain-load the trx-firmware on my c118 with usb-serial-cable.: ------output----- ?./osmocon -p /dev/ttyUSB0 -m c123xor -c ../ ../target/firmware/board/compal_e88/trx.compalram.bin ../ ../target/firmware/board/compal_e88/chainload.highram.bin got 2 bytes from modem, data looks like: 04 81? .. 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 opening file: No such file or directory ------------------------------------ I also tried switching highram-compalram: ./osmocon -p /dev/ttyUSB0 -m c123xor -c ../ ../target/firmware/board/compal_e88/trx.highram.bin ../ ../target/firmware/board/compal_e88/chainload.compalram.bin And also ./osmocon -p /dev/ttyUSB0 -m c123xor -c target/firmware/board/compal_e88/trx.compalram.bin? target/firmware/board/compal_e88/chainload.highram.bin but got same errors. I used the script in the wiki for building the toolchain prior to building the code. ---------------------------------- Any ideas what might be wrong? Regards erich -------------- next part -------------- An HTML attachment was scrubbed... URL: From hyermendain at gmail.com Thu Feb 28 13:24:04 2013 From: hyermendain at gmail.com (Pedro Pires) Date: Thu, 28 Feb 2013 13:24:04 +0000 Subject: trouble loading trx-firmware In-Reply-To: <1362052882.78529.YahooMailNeo@web171205.mail.ir2.yahoo.com> References: <1362052882.78529.YahooMailNeo@web171205.mail.ir2.yahoo.com> Message-ID: Hello Eric if you pass the msg correct you have a space between ../ ../ , this dont have any space. you need to check the correct path. Use the command pwd On Thu, Feb 28, 2013 at 12:01 PM, Erich Dachleger wrote: > Hi list, > I am trying, with no success so far ,to chain-load the trx-firmware on my > c118 with usb-serial-cable.: > > ------output----- > ./osmocon -p /dev/ttyUSB0 -m c123xor -c ../ > ../target/firmware/board/compal_e88/trx.compalram.bin ../ > ../target/firmware/board/compal_e88/chainload.highram.bin > got 2 bytes from modem, data looks like: 04 81 .. > 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 > opening file: No such file or directory > ------------------------------------ > > I also tried switching highram-compalram: > ./osmocon -p /dev/ttyUSB0 -m c123xor -c ../ > ../target/firmware/board/compal_e88/trx.highram.bin ../ > ../target/firmware/board/compal_e88/chainload.compalram.bin > > And also > ./osmocon -p /dev/ttyUSB0 -m c123xor -c > target/firmware/board/compal_e88/trx.compalram.bin > target/firmware/board/compal_e88/chainload.highram.bin > > but got same errors. I used the script in the wiki for building the > toolchain prior to building the code. > ---------------------------------- > > Any ideas what might be wrong? > > Regards erich > > From dario.lombardo.ml at gmail.com Thu Feb 28 14:18:56 2013 From: dario.lombardo.ml at gmail.com (Dario Lombardo) Date: Thu, 28 Feb 2013 15:18:56 +0100 Subject: trouble loading trx-firmware In-Reply-To: <1362052882.78529.YahooMailNeo@web171205.mail.ir2.yahoo.com> References: <1362052882.78529.YahooMailNeo@web171205.mail.ir2.yahoo.com> Message-ID: On Thu, Feb 28, 2013 at 1:01 PM, Erich Dachleger wrote: > ./osmocon -p /dev/ttyUSB0 -m c123xor -c ../ > ../target/firmware/board/compal_e88/trx.compalram.bin ../ > ../target/firmware/board/compal_e88/chainload.highram.bin If I am not wrong, compalram image should be loaded as argument, while highram image should be passed to -c, so this command is wrong. > I also tried switching highram-compalram: > ./osmocon -p /dev/ttyUSB0 -m c123xor -c ../ > ../target/firmware/board/compal_e88/trx.highram.bin ../ > ../target/firmware/board/compal_e88/chainload.compalram.bin > That should be right: you're loading the chainloader that loads the trx. This looks like the command I used to load the TRX. But if you're getting the message "no such file" you're probably pointing to the wrong file names. Do an "ls" from the dir you're running the code to be sure you're pointing to right files. Last but not least: insist. Firmwares in my phones never load at the first try. Dario. From edachleger at yahoo.com Thu Feb 28 15:40:39 2013 From: edachleger at yahoo.com (Erich Dachleger) Date: Thu, 28 Feb 2013 15:40:39 +0000 (GMT) Subject: Vedr: trouble loading trx-firmware In-Reply-To: References: <1362052882.78529.YahooMailNeo@web171205.mail.ir2.yahoo.com> Message-ID: <1362066039.26335.YahooMailNeo@web171202.mail.ir2.yahoo.com> Thanks for the answers. It was the spaces between? "../ ../"? and the first commandline that was the errorcause. erich ________________________________ Fra: Dario Lombardo Til: Erich Dachleger Kopi: "baseband-devel at lists.osmocom.org" Sendt: Torsdag, 28. februar 2013 15.18 Emne: Re: trouble loading trx-firmware On Thu, Feb 28, 2013 at 1:01 PM, Erich Dachleger wrote: >? ./osmocon -p /dev/ttyUSB0 -m c123xor -c ../ > ../target/firmware/board/compal_e88/trx.compalram.bin ../ > ../target/firmware/board/compal_e88/chainload.highram.bin If I am not wrong, compalram image should be loaded as argument, while highram image should be passed to -c, so this command is wrong. > I also tried switching highram-compalram: > ./osmocon -p /dev/ttyUSB0 -m c123xor -c ../ > ../target/firmware/board/compal_e88/trx.highram.bin ../ > ../target/firmware/board/compal_e88/chainload.compalram.bin > That should be right: you're loading the chainloader that loads the trx. This looks like the command I used to load the TRX. But if you're getting the message "no such file" you're probably pointing to the wrong file names. Do an "ls" from the dir you're running the code to be sure you're pointing to right files. Last but not least: insist. Firmwares in my phones never load at the first try. Dario. -------------- next part -------------- An HTML attachment was scrubbed... URL: