From forum at dct.mine.nu Thu Oct 27 22:16:24 2011 From: forum at dct.mine.nu (Forum) Date: Fri, 28 Oct 2011 00:16:24 +0200 Subject: Problems while building osmocomBB In-Reply-To: <4C7D485E.8080700@online.de> References: <4C7D485E.8080700@online.de> Message-ID: <4EA9D838.3060509@dct.mine.nu> I have the same problem her trying to build osmocom. PC:/srv/osmocom-bb/src$ make cd shared/libosmocore/build-target && ../configure \ --host=arm-elf --enable-embedded --disable-shared \ --disable-tests ac_cv_header_sys_select_h=no \ --disable-tests ac_cv_header_sys_socket_h=no \ CFLAGS="-Os -ffunction-sections -I/srv/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs" configure: WARNING: unrecognized options: --disable-shared configure: WARNING: if you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used configure: error: cannot find install-sh, install.sh, or shtool in ".." "../.." "../../.." make: *** [shared/libosmocore/build-target/Makefile] Fehler 1 PC:/srv/osmocom-bb/src$ which shtool /usr/bin/shtool I also copied shtool to the path above ".." without no result. This error message makes no sense? Regards From forum at dct.mine.nu Thu Oct 27 22:43:11 2011 From: forum at dct.mine.nu (Forum) Date: Fri, 28 Oct 2011 00:43:11 +0200 Subject: Error while building osmocomBB In-Reply-To: <4C7D485E.8080700@online.de> References: <4C7D485E.8080700@online.de> Message-ID: <4EA9DE7F.3020800@dct.mine.nu> The problem with the missing shtool has gone after a new clone today from the sources. But now i got an error compiling the sources: ... comm/timer.c:190: warning: unused parameter ?irq? AR comm/libcomm.a LD board/compal_e88/hello_world.compalram.elf apps/hello_world/main.o: In function `console_rx_cb': apps/hello_world/main.c:59: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `sercomm_alloc_msgb': ../../shared/libosmocore/include/osmocom/core/msgb.h:330: undefined reference to `msgb_alloc' comm/libcomm.a(sercomm.o): In function `sercomm_drv_rx_char': comm/sercomm.c:246: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `dispatch_rx_msg': comm/sercomm.c:227: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `sercomm_drv_pull': comm/sercomm.c:161: undefined reference to `msgb_dequeue' comm/sercomm.c:188: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `sercomm_sendmsg': comm/sercomm.c:125: undefined reference to `msgb_enqueue' comm/libcomm.a(sercomm_cons.o): In function `msgb_alloc_headroom': ../../shared/libosmocore/include/osmocom/core/msgb.h:330: undefined reference to `msgb_alloc' make[1]: *** [board/compal_e88/hello_world.compalram.elf] Fehler 1 make[1]: Leaving directory `/srv/osmocom-bb/src/target/firmware' make: *** [firmware] Fehler 2 Regards From lonelysurfer at web.de Tue Oct 11 06:18:37 2011 From: lonelysurfer at web.de (lonelysurfer) Date: Mon, 10 Oct 2011 23:18:37 -0700 (PDT) Subject: burst_ind and TCH In-Reply-To: References: <0022158df35bf87df5049e89e0c2@google.com> Message-ID: <1318313917333-3411749.post@n3.nabble.com> i am looking also for the sync. there are so many funnctions in gsm48_rr.c so i think i have to add more than a few lines? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/burst-ind-and-TCH-tp2683277p3411749.html Sent from the baseband-devel mailing list archive at Nabble.com. From lonelysurfer at web.de Tue Oct 11 13:32:01 2011 From: lonelysurfer at web.de (lonelysurfer) Date: Tue, 11 Oct 2011 06:32:01 -0700 (PDT) Subject: burst_ind and TCH In-Reply-To: References: <0022158df35bf87df5049e89e0c2@google.com> Message-ID: <1318339921799-3412583.post@n3.nabble.com> @27c3 the sync is done with gsm322_sync_to_cell so have a look to gsm322_sync_to_cell() @ gsm322.c perhaps someone is better in c than me and adds this function to the right place -- View this message in context: http://baseband-devel.722152.n3.nabble.com/burst-ind-and-TCH-tp2683277p3412583.html Sent from the baseband-devel mailing list archive at Nabble.com. From viperbjk at live.de Fri Oct 21 11:45:46 2011 From: viperbjk at live.de (Bjoern Kerler) Date: Fri, 21 Oct 2011 11:45:46 +0000 (UTC) Subject: Build fails on OSX Lion References: Message-ID: In serial.c, just change : between #include and #include to the following : //#include #define TIOCGSERIAL 0x541E #define TIOCSSERIAL 0x541F #define ASYNC_SPD_CUST 0x0030 /* Use user-specified divisor */ #define ASYNC_LOW_LATENCY 0x2000 /* Request low latency behaviour */ struct serial_struct { int type; int line; unsigned int port; int irq; int flags; int xmit_fifo_size; int custom_divisor; int baud_base; unsigned short close_delay; char io_type; char reserved_char[1]; int hub6; unsigned short closing_wait; /* time to wait before closing */ unsigned short closing_wait2; /* no longer used... */ unsigned char *iomem_base; unsigned short iomem_reg_shift; unsigned int port_high; int reserved[1]; }; From laforge at gnumonks.org Fri Oct 21 13:24:05 2011 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 21 Oct 2011 15:24:05 +0200 Subject: Build fails on OSX Lion In-Reply-To: References: Message-ID: <20111021132405.GV1745@prithivi.gnumonks.org> Hi Bjoern, On Fri, Oct 21, 2011 at 11:45:46AM +0000, Bjoern Kerler wrote: > In serial.c, just change : > between would you mind submitting a proper patch, i.e. using autotools to detect the presence of OSX header files and using the right include file in that case? -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From lukash at backstep.net Fri Oct 21 15:43:10 2011 From: lukash at backstep.net (Lukas Kuzmiak) Date: Fri, 21 Oct 2011 17:43:10 +0200 Subject: Build fails on OSX Lion In-Reply-To: <20111021132405.GV1745@prithivi.gnumonks.org> References: <20111021132405.GV1745@prithivi.gnumonks.org> Message-ID: There has been a patch from Richard James already, i'm including the patch he sent to baseband-devel in September, however i never managed to get it work (there are couple of typos in the patch), after i fixed those and changed -m c123xor to -m c123 firmware only loads in 1024b parts and then fails after loading. I'm just sending it over to consider the way to handle serial ports on OS X, not sure what's better, this patch looked more OS X native rather than specifying those linux headers, but didn't work properly for me. I'll be happy to test/debug on OS X 10.7 or 10.6 if you've got some idea what could be wrong, OS X kernel is a bit of a mystery for me. cheers, lukash On Fri, Oct 21, 2011 at 3:24 PM, Harald Welte wrote: > Hi Bjoern, > > On Fri, Oct 21, 2011 at 11:45:46AM +0000, Bjoern Kerler wrote: > > In serial.c, just change : > > between > > would you mind submitting a proper patch, i.e. using autotools to detect > the presence of OSX header files and using the right include file in > that case? > > -- > - Harald Welte > http://laforge.gnumonks.org/ > > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6) > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukash at backstep.net Fri Oct 21 15:43:47 2011 From: lukash at backstep.net (Lukas Kuzmiak) Date: Fri, 21 Oct 2011 17:43:47 +0200 Subject: Build fails on OSX Lion In-Reply-To: References: <20111021132405.GV1745@prithivi.gnumonks.org> Message-ID: ... and patch now (sorry). On Fri, Oct 21, 2011 at 5:43 PM, Lukas Kuzmiak wrote: > There has been a patch from Richard James already, i'm including the patch > he sent to baseband-devel in September, however i never managed to get it > work (there are couple of typos in the patch), after i fixed those and > changed -m c123xor to -m c123 firmware only loads in 1024b parts and then > fails after loading. > > I'm just sending it over to consider the way to handle serial ports on OS > X, not sure what's better, this patch looked more OS X native rather than > specifying those linux headers, but didn't work properly for me. > > I'll be happy to test/debug on OS X 10.7 or 10.6 if you've got some idea > what could be wrong, OS X kernel is a bit of a mystery for me. > > cheers, > lukash > > > On Fri, Oct 21, 2011 at 3:24 PM, Harald Welte wrote: > >> Hi Bjoern, >> >> On Fri, Oct 21, 2011 at 11:45:46AM +0000, Bjoern Kerler wrote: >> > In serial.c, just change : >> > between >> >> would you mind submitting a proper patch, i.e. using autotools to detect >> the presence of OSX header files and using the right include file in >> that case? >> >> -- >> - Harald Welte >> http://laforge.gnumonks.org/ >> >> ============================================================================ >> "Privacy in residential applications is a desirable marketing option." >> (ETSI EN 300 175-7 Ch. >> A6) >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: set_custom_baudrate_osx.patch Type: application/octet-stream Size: 1511 bytes Desc: not available URL: From 246tnt at gmail.com Fri Oct 21 16:39:06 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Fri, 21 Oct 2011 18:39:06 +0200 Subject: Build fails on OSX Lion In-Reply-To: References: <20111021132405.GV1745@prithivi.gnumonks.org> Message-ID: The patch has actually already been merged in libosmocore. But it was never pulled into osmocombb. Cheers, Sylvain From laforge at gnumonks.org Fri Oct 21 17:14:38 2011 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 21 Oct 2011 19:14:38 +0200 Subject: Build fails on OSX Lion In-Reply-To: References: <20111021132405.GV1745@prithivi.gnumonks.org> Message-ID: <20111021171438.GA1745@prithivi.gnumonks.org> Hi All, On Fri, Oct 21, 2011 at 06:39:06PM +0200, Sylvain Munaut wrote: > The patch has actually already been merged in libosmocore. > > But it was never pulled into osmocombb. whihc is one more reason to get rid of the copied libosmocore. I think it was useful early on, but now it's causing more problems than benefits. I think we should change it to start * using system-wide libosmocore for host programs * using a 'git clone' command for getting the source for target-cross-compilation Any volunteers? -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From lukash at backstep.net Sun Oct 2 04:01:15 2011 From: lukash at backstep.net (Lukas Kuzmiak) Date: Sun, 2 Oct 2011 06:01:15 +0200 Subject: libosmocore patch to support custom baud rates on OS X In-Reply-To: References: <1317183365.21077.140258148544101@webmail.messagingengine.com> Message-ID: I can confirm this has fixed the error during the compilation, I've run into a different issue however, while building layer23 module(s) I get: ./configure: line 3461: syntax error near unexpected token `LIBOSMOCORE,' ./configure: line 3461: `PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore)' make: *** [host/layer23/Makefile] Error 2 during the configure, anyone run into that issue? Btw, are you using gcc-4.2 from XCode or you've got a separate build environment from some macports/fink/homebrew? Thanks! Lukas On Wed, Sep 28, 2011 at 8:31 AM, Martin Auer wrote: > > Am 28.09.2011 um 06:16 schrieb Richard James: > > > This patch should allow custom baud-rate setting to work on OS X; tested > > on Mac OS X 10.7 with a FT232BL-based adapter. > > > Thanks very much, that solved my problem reported some days ago. > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From catchall at blombo.de Sun Oct 2 04:51:01 2011 From: catchall at blombo.de (Martin Auer) Date: Sun, 2 Oct 2011 06:51:01 +0200 Subject: libosmocore patch to support custom baud rates on OS X In-Reply-To: References: <1317183365.21077.140258148544101@webmail.messagingengine.com> Message-ID: Am 02.10.2011 um 06:01 schrieb Lukas Kuzmiak : > I can confirm this has fixed the error during the compilation, I've run into a different issue however, while building layer23 module(s) I get: > > ./configure: line 3461: syntax error near unexpected token `LIBOSMOCORE,' > ./configure: line 3461: `PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore)' > make: *** [host/layer23/Makefile] Error 2 > > during the configure, anyone run into that issue? > This is an error I had when my PATH Variable was not set correctly. For building on OSX I recently wrote a wiki entry: http://bb.osmocom.org/trac/wiki/GettingStarted_osx > Btw, are you using gcc-4.2 from XCode or you've got a separate build environment from some macports/fink/homebrew? Ports and fink will do. > > Thanks! > Lukas > > On Wed, Sep 28, 2011 at 8:31 AM, Martin Auer wrote: > > Am 28.09.2011 um 06:16 schrieb Richard James: > > > This patch should allow custom baud-rate setting to work on OS X; tested > > on Mac OS X 10.7 with a FT232BL-based adapter. > > > Thanks very much, that solved my problem reported some days ago. > > > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukash at backstep.net Sun Oct 2 20:24:44 2011 From: lukash at backstep.net (Lukas Kuzmiak) Date: Sun, 2 Oct 2011 22:24:44 +0200 Subject: libosmocore patch to support custom baud rates on OS X In-Reply-To: References: <1317183365.21077.140258148544101@webmail.messagingengine.com> Message-ID: Hey Martin, thanks a lot, after a while I noticed my configure(s) were all messed up with /usr/bin/gcc-4.2 instead of arm-elf-gcc-{version} - I had CC=/usr/bin/gcc-4.2 in my /etc/profile and I haven't noticed that for hours, so now everything seems to be working fine with OS X serial baudrate patch. Thanks for help again. Lukas On Sun, Oct 2, 2011 at 6:51 AM, Martin Auer wrote: > Am 02.10.2011 um 06:01 schrieb Lukas Kuzmiak : > > I can confirm this has fixed the error during the compilation, I've run > into a different issue however, while building layer23 module(s) I get: > > ./configure: line 3461: syntax error near unexpected token `LIBOSMOCORE,' > ./configure: line 3461: `PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore)' > make: *** [host/layer23/Makefile] Error 2 > > during the configure, anyone run into that issue? > > > This is an error I had when my PATH Variable was not set correctly. For > building on OSX I recently wrote a wiki entry: > > http://bb.osmocom.org/trac/wiki/GettingStarted_osx > > Btw, are you using gcc-4.2 from XCode or you've got a separate build > environment from some macports/fink/homebrew? > > > Ports and fink will do. > > > Thanks! > Lukas > > On Wed, Sep 28, 2011 at 8:31 AM, Martin Auer < > catchall at blombo.de> wrote: > >> >> Am 28.09.2011 um 06:16 schrieb Richard James: >> >> > This patch should allow custom baud-rate setting to work on OS X; tested >> > on Mac OS X 10.7 with a FT232BL-based adapter. >> > >> Thanks very much, that solved my problem reported some days ago. >> > >> > >> > >> > >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From moser.ronny at gmail.com Sun Oct 2 17:50:27 2011 From: moser.ronny at gmail.com (Ronny Moser) Date: Sun, 2 Oct 2011 19:50:27 +0200 Subject: Ciphermode Message-ID: Hi guys.. I have a question about cipher mode. I saw, that currently a5/1 and a5/2 is implemented. Now, I want to force the phone to use no encryption (A5/0). Is it enough to disable both of these algos? Because when I tried that, I was not longer able to sign in.. Are there any patches that are necessary, or may it be, that the network is not willing to provide a non-encrypted connection? Usually, the phone is using A5/1 and with that algo, everything is working fine.. Thanks for your help. Ronny From 246tnt at gmail.com Sun Oct 2 18:19:10 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sun, 2 Oct 2011 20:19:10 +0200 Subject: Ciphermode In-Reply-To: References: Message-ID: > Are there any patches that are necessary, or may it be, that the > network is not willing to provide a non-encrypted connection? The network will indeed most likely refuse you as you found out. Nothing you can do about it, the network is the master and since the specification says a phone _must_ support A5/1, the network is totally in its right. Cheers, Sylvain From moser.ronny at gmail.com Sun Oct 2 19:41:33 2011 From: moser.ronny at gmail.com (Ronny Moser) Date: Sun, 2 Oct 2011 21:41:33 +0200 Subject: Ciphermode In-Reply-To: References: Message-ID: I didn't know that A5/1 is a must nowadays.. Thanks for the competent information ;) Then I have to search for othr ways .. Thanks, Ronny 2011/10/2 Sylvain Munaut <246tnt at gmail.com>: >> Are there any patches that are necessary, or may it be, that the >> network is not willing to provide a non-encrypted connection? > > The network will indeed most likely refuse you as you found out. > > Nothing you can do about it, the network is the master and since the > specification says a phone _must_ support A5/1, the network is totally > in its right. > > Cheers, > > ? ?Sylvain > From 246tnt at gmail.com Sun Oct 2 19:54:30 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sun, 2 Oct 2011 21:54:30 +0200 Subject: Ciphermode In-Reply-To: References: Message-ID: > I didn't know that A5/1 is a must nowadays.. It's always been a must for the MS to support it. The network doesn't have to, but the phone does. > Then I have to search for othr ways .. Have your own BTS (like nanoBTS, or openBTS, see http://www.ebay.com/itm/220863984566 ) or BTS simulator (like a racal 6103e) Cheers, Sylvain From technosabby at gmail.com Thu Oct 6 01:26:59 2011 From: technosabby at gmail.com (Marten Christophe) Date: Thu, 6 Oct 2011 01:26:59 +0000 Subject: Sniff code.. as shown in c27 video Message-ID: Hello Sylvain, If sniff code has been released as shown in the chao Video conference c27 .. if any sniff code have been merged to any of Osmocom branch, lately i have lost the track of mails and git for quit a some time. Kind Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From akibsayyed at gmail.com Thu Oct 6 18:39:43 2011 From: akibsayyed at gmail.com (Akib Sayyed) Date: Fri, 7 Oct 2011 00:09:43 +0530 Subject: baseband-devel Digest, Vol 21, Issue 4 In-Reply-To: References: Message-ID: only DSP patch is released which allow you to sniff one time slot out of 7. rest code is not published and i guess will never be published On Thu, Oct 6, 2011 at 3:30 PM, wrote: > Send baseband-devel mailing list submissions to > baseband-devel at lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osmocom.org/mailman/listinfo/baseband-devel > or, via email, send a message with subject or body 'help' to > baseband-devel-request at lists.osmocom.org > > You can reach the person managing the list at > baseband-devel-owner at lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of baseband-devel digest..." > > Today's Topics: > > 1. Sniff code.. as shown in c27 video (Marten Christophe) > > > ---------- Forwarded message ---------- > From: Marten Christophe > To: Sylvain Munaut <246tnt at gmail.com> > Date: Thu, 6 Oct 2011 01:26:59 +0000 > Subject: Sniff code.. as shown in c27 video > > Hello Sylvain, > > If sniff code has been released as shown in the chao Video conference c27 > .. if any sniff code have been merged to any of Osmocom branch, lately i > have lost the track of mails and git for quit a some time. > > Kind Regards, > > _______________________________________________ > baseband-devel mailing list > baseband-devel at lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/baseband-devel > > -- 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 rm.engineer84 at gmail.com Sun Oct 9 05:39:49 2011 From: rm.engineer84 at gmail.com (R M) Date: Sun, 9 Oct 2011 11:09:49 +0530 Subject: Vitelcom TSM30 source code Message-ID: Hi, I am looking for Vitelcom TSM30 source code. I tried searching for it in Google. I am not able to find it. The link that is provided in the wiki is dead. Has any one else found it? If yes can you please provide me the link also. Regards RM From msokolov at ivan.Harhan.ORG Wed Oct 12 04:56:56 2011 From: msokolov at ivan.Harhan.ORG (Michael Sokolov) Date: Wed, 12 Oct 2011 04:56:56 GMT Subject: Vitelcom TSM30 source code Message-ID: <1110120456.AA04476@ivan.Harhan.ORG> R M wrote: > I am looking for Vitelcom TSM30 source code. I tried searching for it > in Google. I am not able to find it. I have already helped the OP out off-list. In case anyone else is looking for a copy of that code and all known mirrors have been pulled: I have a copy in my possession, and I've been meaning to put it up on my FTP server, i.e., a new public mirror that would be completely shutdown-proof. (I don't use clouds, I run everything on my own physical HW in my own physical control, housed in my own personal datacenter on my own soil which I have declared to be my own nation with my own laws, so no one in the world can make me take anything down.) However, I am very very technologically-backwards, and my current server HW/OS platform is too ancient to host a 500 MiB blob. (The booty is in the form of an ISO image and appears to contain a huge Windows-based development environment in addition to the actual source.) For ages I've been meaning to set up an additional FTP server on newer HW that can host such big stuff, but that progress is very very slow-going for a bunch of personal reasons. Because I consider it to be my fault that I still haven't followed through with my ages-old promise of setting up that new FTP server, I hereby attempt to make up for it somewhat by making the following offer: if anyone would like a copy of that TSM30 source code, is not able to find it anywhere else, and is not willing to wait however many more months for me to set up that darned server, you can give me your snail mail address and I'll send you a CD-R recorded from that 500 MiB ISO image. With the above out of the way, I happen to have some unanswered questions about the TSM30 phone itself which I wonder if perhaps someone in this community might have some answers to, so I've decided to use this thread (started by someone else to whom I have no relation) to try asking them. :-) (And yes, I've already tried Googling quite extensively.) OK, here we go: 1. Would anyone happen to know the basic specs for the TSM30 phone from an ordinary user's perspective? Which GSM bands does it support? What kind of features does it offer? Judging from a cursory bird's-eye-level look at the source code, it seems to be a few notches above a basic primitive phone like Mot C123, but not quite a smartphone either. I realize that one can probably extract all the answers from the source if one were to study it for months on end (I had no idea it would be this huge!), but I was wondering if anyone already happened to know the answer. Basically I'm trying to decide if it would be worth my while to try to acquire an actual TSM30 hardware unit - which in itself seems to be very non-trivial. 2. Has anyone been able to find a service manual and/or schematics for this phone? 3. Does anyone know the hardware in the TSM30 compares against other Calypso-based phones, such as Mot C123, Openmoko GTA02 or the Leonardo reference design? What are the similarities and differences? TIA a lot for any clues, MS From laforge at gnumonks.org Sun Oct 16 17:50:28 2011 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 16 Oct 2011 19:50:28 +0200 Subject: [ANNOUNCE] First OsmocomGMR code release Message-ID: <20111016175028.GE2396@prithivi.gnumonks.org> First Osmocom GMR code release As some of the readers may already know, a couple of Osmocom developers have been working on a new sub-project: OsmocomGMR. The primary goal of this project is to provide a reusable and clean implementation of the various layers of GMR-1. What is GMR-1 ? Well, it stands for "GEO Mobile Radio" and it's a set of specifications describing a satellite based mobile phone network heavily inspired from GSM. One of the major commercial operators of GMR-1 technology is "Thuraya", providing coverage over Europe/Africa/Asia/Australia. So far the implementation focused on the lowest layers: * Physical layer with FCCH sync and demodulation support for * pi4-CBPSK and pi4-CQPSK bursts. * Channel coding layer (scrambling/puncturing/convolutional coding/crc/interleaving/...) And some ancillary tools to exploit those: * A good capture tool to listen to particular ARFCN(s) and channelize them properly * Wireshark support (BCCH only so far) The first 'demo application' using all of the above provides functionalities similar to what airprobe is for GSM: An air interface protocol analyzer that goes all the way from capturing data off-the-air to sending packets to wireshark for analysis. Limited to BCCH only currently but this will evolve with time. Development was mainly done by Sylvain Munaut, with help from Dimitri Stolnikov (early signal captures and his great capture tool), Harald Welte (initiating the project) and Steve Margraf (testing different setup and antenna ideas). If you'd like to know more, you are encourated to read the wiki (http://gmr.osmocom.org/) and join the mailing list (http://lists.osmocom.org/mailman/listinfo/gmr) -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From dario.lombardo at libero.it Thu Oct 20 08:17:39 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Thu, 20 Oct 2011 10:17:39 +0200 Subject: GPRS decode tutorial Message-ID: Hello everybody Not sure if someone has pointed it out already, but I'm getting stuck following the gprs decode tutorial [...] - Prepare OsmocomBB's burst_ind branch cd ~/gprs_sniffer/osmocom-bb git checkout origin/sylvain/burst_ind git checkout d1cb8ea9b784c7acbafbb2fdcedbdf4655c2f6f5 At this point I get fatal: reference is not a tree: d1cb8ea9b784c7acbafbb2fdcedbdf4655c2f6f5 Next step fails too... pretty obvious... # patch -p1 < ~/gprs_sniffer/gprs_multi.patch can't find file to patch at input line 5 [...] Can someone drive me to the right direction? Thanks! Dario -------------- next part -------------- An HTML attachment was scrubbed... URL: From lukash at backstep.net Thu Oct 20 08:38:18 2011 From: lukash at backstep.net (Lukas Kuzmiak) Date: Thu, 20 Oct 2011 10:38:18 +0200 Subject: GPRS decode tutorial In-Reply-To: References: Message-ID: Hey, osmocom has changed a bit, layer23 has been replaced by ccch_scan, the easiest way would be to open the patch file and patch those files manually, most of the changes will fit if you look for those rows, as I said, patch app_ccch_scan instead of layer23 and you should be fine. lukash On Thu, Oct 20, 2011 at 10:17 AM, Dario Lombardo wrote: > Hello everybody > Not sure if someone has pointed it out already, but I'm getting stuck > following the gprs decode tutorial > > [...] > > - Prepare OsmocomBB's burst_ind branch > > cd ~/gprs_sniffer/osmocom-bb > > git checkout origin/sylvain/burst_ind > git checkout d1cb8ea9b784c7acbafbb2fdcedbdf4655c2f6f5 > > At this point I get > > fatal: reference is not a tree: d1cb8ea9b784c7acbafbb2fdcedbdf4655c2f6f5 > > > Next step fails too... pretty obvious... > > # patch -p1 < ~/gprs_sniffer/gprs_multi.patch > can't find file to patch at input line 5 > [...] > > Can someone drive me to the right direction? > Thanks! > Dario > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From luca.bongiorni1 at studenti.unimi.it Thu Oct 20 08:46:55 2011 From: luca.bongiorni1 at studenti.unimi.it (Luca Bongiorni) Date: Thu, 20 Oct 2011 10:46:55 +0200 Subject: R: GPRS decode tutorial In-Reply-To: <76b094fba506.4e9ffb58@studenti.unimi.it> References: <76b094fba506.4e9ffb58@studenti.unimi.it> Message-ID: <770083acc73d.4e9ffc1f@studenti.unimi.it> Hi Dario, ?i suggest you to download the last Sylvain's burst_ind, because is improved of some features and patch it manually with Nohl's patch. Then you will be able to dump the bursts using ccch_scan, instead of layer23. Cheers, Luca ?> Can someone drive me to the right direction? ?P.S:?http://comments.gmane.org/gmane.comp.mobile.osmocom.baseband.devel/1754 From juantxipazos at yahoo.es Wed Oct 26 01:38:45 2011 From: juantxipazos at yahoo.es (Juantxi) Date: Wed, 26 Oct 2011 03:38:45 +0200 Subject: GPRS decode tutorial References: <76b094fba506.4e9ffb58@studenti.unimi.it> <770083acc73d.4e9ffc1f@studenti.unimi.it> Message-ID: <1CB33D8DBBB14F0DB8D94AA5369A1FBE@Maite> Hello, git not download burst_ind, I need special privilege? thank you ----- Original Message ----- From: "Luca Bongiorni" To: Sent: Thursday, October 20, 2011 10:46 AM Subject: R: GPRS decode tutorial Hi Dario, i suggest you to download the last Sylvain's burst_ind, because is improved of some features and patch it manually with Nohl's patch. Then you will be able to dump the bursts using ccch_scan, instead of layer23. Cheers, Luca > Can someone drive me to the right direction? P.S: http://comments.gmane.org/gmane.comp.mobile.osmocom.baseband.devel/1754 From aegean2000 at 21cn.com Sat Oct 22 11:32:20 2011 From: aegean2000 at 21cn.com (Aegean Chou) Date: Sat, 22 Oct 2011 19:32:20 +0800 Subject: AMR support Message-ID: <20111022113220.0F19E20F840@21cn.com> Hi, all The osmocomBB no AMR support yet now (only FR, HR and EFR). /* no AMR yet */ void dsp_load_tch_param(struct gsm_time *next_time, if (tch_mode) { switch (l1s.tch_mode) { case GSM48_CMODE_SPEECH_V1: *tch_mode = *tch_f_hn ? TCH_FS_MODE : TCH_HS_MODE; break; case GSM48_CMODE_SPEECH_EFR: *tch_mode = *tch_f_hn ? TCH_EFR_MODE : SIG_ONLY_MODE; break; default: *tch_mode = SIG_ONLY_MODE; } } i checked the product datasheet, the C123 can support AMR from the beginning. does anyone can give me some information to patch it? BTW, i havn't 30 source, so i can't reference it. Best regards Aegean Chou From laforge at gnumonks.org Sun Oct 23 07:09:00 2011 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 23 Oct 2011 09:09:00 +0200 Subject: AMR support In-Reply-To: <20111022113220.0F19E20F840@21cn.com> References: <20111022113220.0F19E20F840@21cn.com> Message-ID: <20111023070859.GA2412@prithivi.gnumonks.org> Hi Aegean, On Sat, Oct 22, 2011 at 07:32:20PM +0800, Aegean Chou wrote: > The osmocomBB no AMR support yet now (only FR, HR and EFR). this is correct. > i checked the product datasheet, the C123 can support AMR from > the beginning. does anyone can give me some information to > patch it? AMR in general is relatively complex, at least at least if you want to implement it in a compliant way. There is not only the 'adaptive' aspect, i.e. the negotiation of different codec modes with CMR/CMI/CMC and the associated CmiPhase, but also the RATSCCH signalling for TFO. Furthermore, the situation gets slightly more complicated as the Calypso DSP ROM firmware apparently doesn't support AMR out-of-the-box but needs some DSP code patches. While we already have support for applying such patches, we don't have a license to distribute such patches, i.e. we cannot include them in OsmocomBB without being in copyright violation. So the correct way of implementing this is: * decide which DSP patch to use (from original firmware) * write a script that can extract it out of the original firmware image * include such a script in OsmocomBB * implement the DSP API / L1 related aspects for AMR in Calypso (by looking at TSM30 source code, or legal forms of reverse engineering the original firmware of e.g. a C123) If you would like to contribute patches/code for any of this work, we would be more than happy to review and merge them. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From tianxing at timelink.com.hk Sun Oct 23 13:01:37 2011 From: tianxing at timelink.com.hk (=?gbk?B?zOzQ0A==?=) Date: Sun, 23 Oct 2011 21:01:37 +0800 Subject: GSM Muti-antenna Receiver Message-ID: Hi all: I try make usrp work on Muti-antenna mode , 1 to downlink , 1 to uplink. first , i only decode downlink, it can found FCCH,but can't decode sch. any suggestion? tianxing at tianxing-MS-7345:~/gsm/airprobe-gprs/gsm-receiver/src/python$ ./gsm_reive_usrp_mono.py -c 122 A side: Flex 900 Rx MIMO B B side: Flex 900 Rx MIMO B gain_a: 45.0 gain_b: 45.0 A side: The carrier frequency is set as 959400000.0 B side: The carrier frequency is set as 959400000.0 mux_val = 0x2301 input_rate: 571428.571429 sample rate: 0.527472527473 filter_cutoff: 145000.0 filter_t_width: 10000.0 >>> gr_fir_ccc: using SSE input_rate: 571428.571429 sample rate: 0.527472527473 filter_cutoff: 145000.0 filter_t_width: 10000.0 >>> gr_fir_ccf: using SSE Key: '0000000000000000' Configuration: '0C' Configuration TS: 0 configure_receiver 1319360150.211137 3014114160: fcch found on position: 24508 1319360150.211206 3014114160: freq_offset: -2659.853516 1319360150.254086 3014114160: fcch found on position: 77189 1319360150.254132 3014114160: freq_offset: -261.283386 sch.c:260 ERR: conv_decode 11 1319360150.307770 3014114160: fcch found on position: 135276 1319360150.307814 3014114160: freq_offset: -2574.190186 sch.c:260 ERR: conv_decode 10 1319360150.352075 3014114160: fcch found on position: 188023 1319360150.352120 3014114160: freq_offset: -375.097321 sch.c:260 ERR: conv_decode 8 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gsm_receive_usrp_mono.py Type: application/octet-stream Size: 9172 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gsm_two_receiver.py Type: application/octet-stream Size: 2535 bytes Desc: not available URL: From andreas at eversberg.eu Mon Oct 24 16:13:33 2011 From: andreas at eversberg.eu (jolly) Date: Mon, 24 Oct 2011 18:13:33 +0200 Subject: moving SMS core code into libosmocore Message-ID: <4EA58EAD.6080409@eversberg.eu> hi, i am thinking about moving sms code from openbsc to libsomocore. my idea is to move the core code of openbsc to libosmocore's src/gsm and include/osmocom/gsm/ respectively. one problem is that the transaction structure of osmocombb and openbsc is different. for sms support there could be a common part inside the union of each transaction: struct gsm_trans { ... union { ... struct { uint8_t link_id; /* RSL Link ID to be used for this trans */ int is_mt; /* is this a MO (0) or MT (1) transfer */ enum gsm411_cp_state cp_state; struct osmo_timer_list cp_timer; enum gsm411_rp_state rp_state; struct gsm_sms *sms; } sms; }; }; i would suggest to move the common part to libosmocore and name it "gsm_trans_sms". then both openbsc and osmocombb can use the same sms structure. also the "gsm_sms" structure itself must be generalized and not rely on openbsc structures. (i have not yet looked at it.) to get reference to the private gsm_trans, openbsc and osmocombb can now use "container_of" in the specific sms glue code. any ideas / suggestions? andreas From andreas at eversberg.eu Mon Oct 31 17:39:02 2011 From: andreas at eversberg.eu (Andreas Eversberg) Date: Mon, 31 Oct 2011 18:39:02 +0100 Subject: SMS support for osmocombb Message-ID: <4EAEDD36.3050309@eversberg.eu> hi, i just finished SMS support for osmocombb. everything is committed in my jolly/testing branch. in order to support SMS, i extracted the SMS transcoding from openbsc. (jolly/sms branch) the SMC and SMR layer protocols are extracted and rewritten and use messages between layers and have state machines. they are added to libosmocore also. (jolly/sms branch) openbsc (jolly/sms branch) now uses the SMS layers and transcoding of libosmocore. LAPDm now supports correct handling of SAPI 3 datalink, especially on SACCH. the mobility management and radio ressource layers of osmocombb now support MM connections with SAPI 3. i have tested it on test BTS setup only, so feel free to run it and report bugs. regards, andreas