From thayyil at yandex.com Mon May 1 12:59:11 2017 From: thayyil at yandex.com (thayyil09 yil) Date: Mon, 01 May 2017 18:29:11 +0530 Subject: osmocombb for qcom Message-ID: <6958681493643551@web11g.yandex.ru> is it possible to add new project page to osmocom site. as i mentioned earlear sourcecode already available for qcom i think none intrested in it. is it true .why? From nhofmeyr at sysmocom.de Tue May 2 10:09:00 2017 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Tue, 2 May 2017 12:09:00 +0200 Subject: osmocom-bb moved to gerrit In-Reply-To: <9e982d6e-0f5f-a6d1-e9f1-a395d59a51aa@sysmocom.de> References: <20170426142857.GB518@my.box> <9e982d6e-0f5f-a6d1-e9f1-a395d59a51aa@sysmocom.de> Message-ID: <20170502100900.GD2407@ass40.sysmocom.de> On Thu, Apr 27, 2017 at 12:10:09PM +0200, Max wrote: > It worked for me with *gcc-arm-none-eabi* package on Ubuntu - in this case the build Is installed on the OsmocomBuild1 build slave. (already was installed) ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From antgorka at gmail.com Wed May 3 19:11:30 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Wed, 3 May 2017 22:11:30 +0300 Subject: OsmocomBB full Opensouce? In-Reply-To: References: Message-ID: Dear collegues, Could you please help me to understand one thing.. If I understood everything correct, osmocombb project consist of all the code for GSM stack L1-L3 functionality but Calypdo DSP code is not Opensource and layer1.bin ask non-opensource DSP module to do execute L1 tasks from ghis list: https://osmocom.org/projects/baseband/wiki/TSM30Layer1#DSP-Tasks Of cource we can patch DSP and ask it to do whatever we want, like send raw bursts to the host, but now osmocombb uses mostly DSP firmware written by Texas Instruments, not its own opdnsource. Is it correct or not? Thanks in advance! -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Thu May 4 07:14:35 2017 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 4 May 2017 09:14:35 +0200 Subject: OsmocomBB full Opensouce? In-Reply-To: References: Message-ID: <20170504071435.xibuzcmxayxed2rt@nataraja> Hi Anton, On Wed, May 03, 2017 at 10:11:30PM +0300, Anton Gorbachev wrote: > If I understood everything correct, osmocombb project consist of all the > code for GSM stack L1-L3 functionality but Calypdo DSP code is not > Opensource and layer1.bin ask non-opensource DSP module to do execute L1 > tasks from ghis list: Correct. The DSP implements the PHY layer, which is proprietary. However, as the DSP is ROM code running on a different processor, with different address space, RAM and instruction set, there is no issue in terms of GPL licensing. The GPL-licensed OsmocomBB code simply instructs the other processor to do what's needed. > Of cource we can patch DSP and ask it to do whatever we want, like send raw > bursts to the host, but now osmocombb uses mostly DSP firmware written by > Texas Instruments, not its own opdnsource. Correct. We never claimed that the PHY layer (DSP code) was FOSS. There was once an university project about creating a software PHY compatible with OsmocomBB, but unfortunately (like way too often in academic research) the results were not contributed back as FOSS: http://www.benkeser.com/osmophy.pdf There are some ideas floating around of doing a new run of this using OsmoTRX as basis, but I don't know if there is any actual progress yet. Vadim should be able to say more about it. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From axilirator at gmail.com Thu May 4 09:28:07 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Thu, 4 May 2017 16:28:07 +0700 Subject: OsmocomBB full Opensouce? Message-ID: Hi Anton, > There are some ideas floating around of doing a new run of this using > OsmoTRX as basis, but I don't know if there is any actual progress yet. > Vadim should be able to say more about it. Yeah, I started to work on SDR based PHY about a year ago, but so far I was busy with libosmocore development. Right now almost everything (including libosmocoding of course) is in master branch, so it's good point to resume this work. If you would like to contribute this direction or something else, we are always open for that, so feel free! The source code is currently on GitHub: https://github.com/axilirator/osmocom-bb/ BTW: Harald, is it possible to create a new branch for that work in the project's repo? If yes, I can send you my public key in PM. Thanks! With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From antgorka at gmail.com Thu May 4 09:43:56 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Thu, 4 May 2017 12:43:56 +0300 Subject: OsmocomBB full Opensouce? In-Reply-To: References: Message-ID: Hi, Thank you for the clarification. Actually I am just driving into Osmocom projects, trying what already is and I definetely need more time to upderstand all the processes. Maybe later I can participate in developments or something. Kind regards, Anton 2017-05-04 12:28 GMT+03:00 Vadim Yanitskiy : > Hi Anton, > > > There are some ideas floating around of doing a new run of this using > > OsmoTRX as basis, but I don't know if there is any actual progress yet. > > Vadim should be able to say more about it. > > Yeah, I started to work on SDR based PHY about a year ago, but so far > I was busy with libosmocore development. Right now almost everything > (including libosmocoding of course) is in master branch, so it's good > point to resume this work. > > If you would like to contribute this direction or something else, we are > always open for that, so feel free! The source code is currently on GitHub: > > https://github.com/axilirator/osmocom-bb/ > > BTW: Harald, is it possible to create a new branch for that work in the > project's repo? If yes, I can send you my public key in PM. Thanks! > > > With best regards, > Vadim Yanitskiy. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Thu May 4 09:35:23 2017 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 4 May 2017 11:35:23 +0200 Subject: OsmocomBB full Opensouce? In-Reply-To: References: Message-ID: <20170504093523.nix3kgkla2eyaxvr@nataraja> Hi Vadim, On Thu, May 04, 2017 at 04:28:07PM +0700, Vadim Yanitskiy wrote: > BTW: Harald, is it possible to create a new branch for that work in the > project's repo? If yes, I can send you my public key in PM. Thanks! As OsmocomBB has moved to gerrit now (I believe?), you should be able to push your branches to gerrit, which will then replicate it to git.osmocom.org. SSH key can be self-registered in gerrit (which you most likely already have). 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 samir.s.abed at gmail.com Thu May 4 14:38:07 2017 From: samir.s.abed at gmail.com (samir) Date: Thu, 4 May 2017 17:38:07 +0300 Subject: Phone not receiving calls Message-ID: <2FEBC2B6-EFA8-4C52-8B1D-085FC8E22914@gmail.com> Hello, I test osmocombb for some time with motorola c115. I can make calls but not always receive calls. I tried 2 sim cards one of them is working fine but the other doesn?t receive anything. I really need some help to solve my problem. thanks in advance. From nhofmeyr at sysmocom.de Thu May 4 16:05:21 2017 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Thu, 4 May 2017 18:05:21 +0200 Subject: OsmocomBB full Opensouce? In-Reply-To: <20170504093523.nix3kgkla2eyaxvr@nataraja> References: <20170504093523.nix3kgkla2eyaxvr@nataraja> Message-ID: <20170504160521.GD8279@ass40.sysmocom.de> On Thu, May 04, 2017 at 11:35:23AM +0200, Harald Welte wrote: > As OsmocomBB has moved to gerrit now (I believe?) yes it has. ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From antgorka at gmail.com Fri May 5 14:52:54 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Fri, 5 May 2017 17:52:54 +0300 Subject: CalypsoBTS no sync, ms hang Message-ID: Dear colleagues, I am trying to setup CalypsoBTS with two c113 phones. Don't you know why can't I sync to any commercial cell with transceiver from branch jolly/testing? What I have: Motorola c113 and c113a, tried both. All other apps like, RSSI, mobile, ccch_scan works like a charm. What I am doing: Built jolly/testing according to maual https://osmocom.org/projects/baseband/wiki/CalypsoBTS Load firmware ./osmocon -r 99 -m c123xor -p /dev/ttyUSB0 -c ../../target/firmware/board/compal_e88/trx.highram.bin Found several strongest cells with RSSI and cell_log. Trying to sync: ./transceiver -a 50 -r 99 -e 1 Here is the log: 50 41 1 <000c> l1ctl.c:77 Tx Reset Req (1) <000c> l1ctl_link.c:171 Sending: '0d 00 00 00 01 00 00 00 ' <0012> l1ctl.c:383 Reset received: Starting sync. <000c> l1ctl.c:95 Sync Req <000c> l1ctl_link.c:171 Sending: '01 00 00 00 00 32 00 64 27 10 03 20 03 07 00 00 00 ' After that phone hangs, no reaction in osmocon on key pressures, holding on power off button... The last messages are: L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=50, flags=0x7) Starting FCCH RecognitionFB0 (2515:4): TOA= 3552, Power= -64dBm, Angle= 1328Hz FB1 (2525:8): TOA= 8543, Power= -64dBm, Angle= 114Hz fn_offset=2523 (fn=2525 + attempt=8 + ntdma = 6) delay=8 (fn_offset=2523 + 11 - fn=2525 - 1 scheduling next FB/SB detection task with delay 8 =>FB @ FNR 2523 fn_offset=2523 qbits=3988 Synchronize_TDMA LOST 3398! I tried different cells, maybe I need to wait some time to warm the crystal? But can it be so important? Kind regards, Anton -------------- next part -------------- An HTML attachment was scrubbed... URL: From antgorka at gmail.com Fri May 5 20:35:54 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Fri, 5 May 2017 23:35:54 +0300 Subject: CalypsoBTS no sync, ms hang In-Reply-To: References: Message-ID: Dear developers, Sorry for the previous question. I found that the solution is simple. The bug described here http://cgit.osmocom.org/osmocom-bb/commit/?id=a903b3c1ee27047c79728b18ff6340d23d1aad2e isn't fixed in branch jolly/testing I am using for calypsoBTS. So all I needed is just implement the fix and recompile from sources. Kind regards, Anton 2017-05-05 17:52 GMT+03:00 Anton Gorbachev : > Dear colleagues, > > I am trying to setup CalypsoBTS with two c113 phones. > > Don't you know why can't I sync to any commercial cell with transceiver > from branch jolly/testing? > > What I have: > Motorola c113 and c113a, tried both. > All other apps like, RSSI, mobile, ccch_scan works like a charm. > > What I am doing: > Built jolly/testing according to maual > https://osmocom.org/projects/baseband/wiki/CalypsoBTS > > Load firmware > ./osmocon -r 99 -m c123xor -p /dev/ttyUSB0 -c ../../target/firmware/board/ > compal_e88/trx.highram.bin > > Found several strongest cells with RSSI and cell_log. > Trying to sync: > ./transceiver -a 50 -r 99 -e 1 > Here is the log: > 50 > 41 > 1 > <000c> l1ctl.c:77 Tx Reset Req (1) > <000c> l1ctl_link.c:171 Sending: '0d 00 00 00 01 00 00 00 ' > <0012> l1ctl.c:383 Reset received: Starting sync. > <000c> l1ctl.c:95 Sync Req > <000c> l1ctl_link.c:171 Sending: '01 00 00 00 00 32 00 64 27 10 03 20 03 > 07 00 00 00 ' > > After that phone hangs, no reaction in osmocon on key pressures, holding > on power off button... > > The last messages are: > L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=50, flags=0x7) > Starting FCCH RecognitionFB0 (2515:4): TOA= 3552, Power= -64dBm, Angle= > 1328Hz > FB1 (2525:8): TOA= 8543, Power= -64dBm, Angle= 114Hz > fn_offset=2523 (fn=2525 + attempt=8 + ntdma = 6) > delay=8 (fn_offset=2523 + 11 - fn=2525 - 1 > scheduling next FB/SB detection task with delay 8 > =>FB @ FNR 2523 fn_offset=2523 qbits=3988 > Synchronize_TDMA > LOST 3398! > > I tried different cells, maybe I need to wait some time to warm the > crystal? But can it be so important? > > Kind regards, > Anton > -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Fri May 5 22:33:09 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Sat, 6 May 2017 05:33:09 +0700 Subject: Phone not receiving calls Message-ID: Hi, Don't get me wrong, but your current description sounds like "I have a problem, but I wouldn't say any details about that". Please provide at least mobile application logs, and also try to figure out some things yourself: 1) What is difference between both SIM cards you use? 2) Does mobile with "non-working" SIM perform successful LU? 3) Does mobile with "non-working" SIM receive any Paging Request? 4) Does one answer to Paging Request by sending Paging Response? 5) Then, does the L1 switch to a dedicated channel? 6) What is happening on a dedicated channel? 7) ... ? OsmocomBB is not for end users, so you should do / learn a lot of things yourself. After all, the source code is always available. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Fri May 5 22:42:24 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Sat, 6 May 2017 05:42:24 +0700 Subject: CalypsoBTS no sync, ms hang Message-ID: > isn't fixed in branch jolly/testing I am using for calypsoBTS. > So all I needed is just implement the fix and recompile from sources. You can also use an older version of toolchain as a temporary solution: https://github.com/axilirator/gnu-arm-installer - in this repo I have fixed some installation (texinfo) related issues. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From samir.s.abed at gmail.com Sat May 6 07:27:13 2017 From: samir.s.abed at gmail.com (samir) Date: Sat, 6 May 2017 10:27:13 +0300 Subject: Phone not receiving calls In-Reply-To: References: Message-ID: Hi, On May 6, 2017, at 1:33 AM, Vadim Yanitskiy wrote: > Hi, > > Don't get me wrong, but your current description sounds like > "I have a problem, but I wouldn't say any details about that". > Please provide at least mobile application logs, and also try > to figure out some things yourself: > > 1) What is difference between both SIM cards you use? both SIM cards are the same (only imsi is different) > 2) Does mobile with "non-working" SIM perform successful LU? Yes, it connects normally and can perform calls and send SMS. > 3) Does mobile with "non-working" SIM receive any Paging Request? No, nothing is received. From antgorka at gmail.com Sat May 6 18:42:38 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Sat, 6 May 2017 21:42:38 +0300 Subject: CalypsoBTS no sync, ms hang In-Reply-To: References: Message-ID: Yes, I saw it and wanted to try if my fix doesn't work. Thanks! But as I told, sync is ok now with additional code to the constructor and gcc 4.8 :) 6 ??? 2017 ?. 1:42 ???????????? "Vadim Yanitskiy" ???????: > > isn't fixed in branch jolly/testing I am using for calypsoBTS. > > So all I needed is just implement the fix and recompile from sources. > > You can also use an older version of toolchain as a temporary > solution: https://github.com/axilirator/gnu-arm-installer - in this > repo I have fixed some installation (texinfo) related issues. > > With best regards, > Vadim Yanitskiy. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thayyil at yandex.com Sun May 7 20:21:30 2017 From: thayyil at yandex.com (thayyil09 yil) Date: Mon, 08 May 2017 01:51:30 +0530 Subject: to qcom hexagon porting Message-ID: <6104951494188490@web10j.yandex.ru> what are problem should i expect while porting to qcom hexagon is it a bad idea From craig_comstock at yahoo.com Mon May 8 03:53:33 2017 From: craig_comstock at yahoo.com (Craig Comstock) Date: Mon, 8 May 2017 03:53:33 +0000 (UTC) Subject: to qcom hexagon porting References: <480116106.4442676.1494215613816.ref@mail.yahoo.com> Message-ID: <480116106.4442676.1494215613816@mail.yahoo.com> > what are problem should i expect > while porting to qcom hexagon > is it a bad idea There would be a lot of questions and things to research. I am not familiar with qcom hexagon SDK. I am a little familiar with osmocom-bb source code and 2G GSM details. I am currently in the very beginning stages of porting osmocom-bb to the MediaTek 6260/6261 chip which supports 2G. I also have ideas to try and work through 3G on a MediaTek 6735 (ZTE Obsidian phone). Recently there have been mentions of re-writing the PHY layer of osmocom-bb for an SDR platform like LimeSDR. https://github.com/axilirator/osmocom-bb So at the current time I assume that osmocom-bb communicates with the DSP chip on the motorola phones in a way that abstracts the PHY layer details away and relies on the proprietary Texas Instruments firmware in the DSP as-is. So I would imagine you might have to implement the PHY layer and also the interface to the PHY layer. There was a discussion about this recently on IRC #osmocom. It seems the thought was that qcom had released enough with their Hexagon SDK to allow development of a PHY layer + whatever else. Some links of interest. https://developer.qualcomm.com/ - SDK https://github.com/ttsou/openphy - LTE PHY for Ettus USRP https://androiddatahost.com/fgd43 - qcom flash image loader I have a few qcom modems that I'd be happy to do experiment on if that helps. -Craig From inode at wayreth.eu.org Mon May 8 04:58:01 2017 From: inode at wayreth.eu.org (inode) Date: Mon, 8 May 2017 06:58:01 +0200 Subject: CalypsoBTS + GPRS and SDR suggestion Message-ID: Hi everybody, I'm pretty new to the GSM/UMTS environment and I'm doing some tests. Currently I need to analyze some IoT devices that use 2G network to comunicate via GPRS. I setup CalypsoBTS to work with 2 old motorola c123, I know that isn't the best way to do that, but I would like to have a cheap solution. I got the setup working with a normal phone and the BTS seems to work correctly (using jolly/testing), but from my understanding it support only GSM calls and SMS and GPRS is not implemented into the transceiver. I'm wrong or this part has not been implemented yet? If needed to use a GPRS BTS can you suggest the best cheap SDR to use with OsmoBTS? (I saw BladeRF and LimeSDR but I was unable to understand if they are full supported via OsmoBTS) Thank you in advance. inode -------------- next part -------------- An HTML attachment was scrubbed... URL: From mychaela.falconia at gmail.com Mon May 8 06:15:14 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Sun, 7 May 2017 22:15:14 -0800 Subject: CalypsoBTS + GPRS and SDR suggestion In-Reply-To: References: Message-ID: inode wrote: > If needed to use a GPRS BTS can you suggest the best cheap SDR to use with > OsmoBTS? (I saw BladeRF and LimeSDR but I was unable to understand if they > are full supported via OsmoBTS) I am also interested in the answer to this question, but for a completely different reason. I am making my own boards with the Calypso chipset, intended to be a superior alternative to the very cripped Mot C1xx phones, I've already made the first batch of boards and they work nicely (it is my understanding that one of them was demonstrated at OsmoDevCon), and I am currently working on a few outstanding minor hardware issues, as well as professional quality RF calibration. Once I have all of the outstanding hw and calibration issues solved and I build a slightly larger batch, my boards will become available on a retail basis. However, my FreeCalypso board (FCDEV3B) is intended to serve as a GSM *mobile station* development board, *not* a poor man's BTS. But looking at the traffic on this mailing list, it seems that more people use Mot C1xx phones and OsmocomBB for CalypsoBTS purposes than for GSM work in the Calypso's native MS role, thus I need to have some prepared canned answer to give to those people. My newly made Calypso-based GSM MS development boards will *not* be dirt-cheap like dumpster-sourced Mot C1xx phones, they will probably cost about the same as the full version of bladeRF, and using an expensive board meant for the GSM MS role as a poor man's BTS makes absolutely no sense. Thus when people will inevitably ask me if my FCDEV3B can run CalypsoBTS, I would like to be able to point them to some different product, SDR or otherwise, that is better suited for the BTS role. My question is: which SDR or other BTS product should I recommend to those CalypsoBTS-seeking people? TIA, Mychaela From laforge at gnumonks.org Mon May 8 08:17:41 2017 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 8 May 2017 10:17:41 +0200 Subject: CalypsoBTS + GPRS and SDR suggestion In-Reply-To: References: Message-ID: <20170508081741.eewmct2zk3euszr5@nataraja> Hi inode, this list is about osmocom-bb, and not about the osmocom projects about networks-side gsm. OsmoTRX, OsmoBTS & Co are discussed on the openbsc at lists.osmocom.org mailing list. Please consider asking your questions there. On Mon, May 08, 2017 at 06:58:01AM +0200, inode wrote: > but from my understanding it support only GSM calls > and SMS and GPRS is not implemented into the transceiver. I'm wrong or this > part has not been implemented yet? I have never used the "calypsobts" hack. But osmo-trx + osmo-bts-trx have support of voice, SMS and GRPS services. As SMS is using the same signaling channels, this should definitely work even with the CalypsoBTS. For GPRS, you'd need to support the GPRS related coding schemes and an interface to OsmoPCU. Also, given that CalypsoBTS can only provide single (or two?) timeslot, there are a long list of reasons why it would not work straight-forward. But technically also possible to make work. > If needed to use a GPRS BTS can you suggest the best cheap SDR to use with > OsmoBTS? (I saw BladeRF and LimeSDR but I was unable to understand if they > are full supported via OsmoBTS) Please raise this (and continue any related discussion) on the other mailing list. 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 axilirator at gmail.com Mon May 8 21:52:39 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Tue, 9 May 2017 04:52:39 +0700 Subject: CalypsoBTS + GPRS and SDR suggestion Message-ID: Hi, > I setup CalypsoBTS to work with 2 old motorola c123, I know that isn't the > best way to do that, but I would like to have a cheap solution. I got the > setup working with a normal phone and the BTS seems to work correctly > (using jolly/testing), but from my understanding it support only GSM calls > and SMS and GPRS is not implemented into the transceiver. I'm wrong or this > part has not been implemented yet? Right, isn't implemented. When you run OsmoBTS, it first does some basic configuration of transceiver, including timeslot type setting. PDCH has its own dedicated type, which is being indicated by the SETSLOT command. So you can look at OsmocomBB sources, and check whether the transceiver handles this type or not. > Also, given that CalypsoBTS can only provide single (or two?) timeslot, > there are a long list of reasons why it would not work straight-forward. > But technically also possible to make work. With two Calypso phones it becomes possible to serve two timeslots. Basically, second phone serves one TCH timeslot, but (if I am correct) PDCH has no fundamental differences from TCH, so its support could be implemented too. After a quick look at OsmoTRX source code, I can assume, that the only difference between TCH channel combinations (I, II and III) and PDCH channel combination (XIII) is a fillerModulus value. Correct me if I am wrong. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve at steve-m.de Tue May 9 00:12:49 2017 From: steve at steve-m.de (Steve Markgraf) Date: Tue, 9 May 2017 02:12:49 +0200 Subject: CalypsoBTS + GPRS and SDR suggestion In-Reply-To: References: Message-ID: <73c2c130-288e-ed43-4a86-f165aeaa2e26@steve-m.de> Hi, On 08.05.2017 23:52, Vadim Yanitskiy wrote: > With two Calypso phones it becomes possible to serve two timeslots. > Basically, second phone serves one TCH timeslot, but (if I am correct) > PDCH has no fundamental differences from TCH, so its support could be > implemented too. > > After a quick look at OsmoTRX source code, I can assume, that the only > difference between TCH channel combinations (I, II and III) and PDCH > channel combination (XIII) is a fillerModulus value. Correct me if I am > wrong. Actually GPRS works fine with CalypsoBTS for years. Last time I've tested this was last year, and there was a small patch required in order to allow a PDCH in TS1 with the 'nanoBTS', but that's it. I've put it here: https://steve-m.de/files/calypso_bts/ Regards, Steve From laforge at gnumonks.org Tue May 9 04:51:31 2017 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 9 May 2017 06:51:31 +0200 Subject: CalypsoBTS + GPRS and SDR suggestion In-Reply-To: References: Message-ID: <20170509045131.dx7mojcrbl5wkbg2@nataraja> Dear all, according to a comment from Steve Markgraf (Cc) on IRC, PDCH is supported on CalypsoBTS. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From robert.steve07 at gmail.com Tue May 9 13:05:11 2017 From: robert.steve07 at gmail.com (robert) Date: Tue, 9 May 2017 16:05:11 +0300 Subject: Phone not receiving calls In-Reply-To: References: Message-ID: I had the same problem but couldn?t fix it. I guess nothing could be done. On May 6, 2017, at 10:27 AM, samir wrote: > Hi, > > On May 6, 2017, at 1:33 AM, Vadim Yanitskiy wrote: > >> Hi, >> >> Don't get me wrong, but your current description sounds like >> "I have a problem, but I wouldn't say any details about that". >> Please provide at least mobile application logs, and also try >> to figure out some things yourself: >> >> 1) What is difference between both SIM cards you use? > both SIM cards are the same (only imsi is different) > >> 2) Does mobile with "non-working" SIM perform successful LU? > Yes, it connects normally and can perform calls and send SMS. > >> 3) Does mobile with "non-working" SIM receive any Paging Request? > No, nothing is received. > From mychaela.falconia at gmail.com Tue May 9 15:37:50 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Tue, 9 May 2017 07:37:50 -0800 Subject: Creating GSM Users Association (GSMUA) Message-ID: Hello FreeCalypso and Osmocom communities, I am in the process of creating an informal organisation representing the interests of those members of the GSM universe whose interests are not represented by GSMA etc, and I am inviting you to join me in this venture. I propose that we name our informal organisation GSMUA, standing for GSM Users Association, and my vision for this GSMUA is to be a counter-body (antibody?) to the official GSMA. I just registered the gsmua.org domain name, but there is no website or mailing list set up yet. If someone from the Osmocom camp would like to host the server infrastructure for gsmua.org, I will happily point the DNS to you, otherwise the FreeCalypso family can host it on our server. My vision for GSMUA is to represent the interests of GSM end users (empowered end users who wish to fully own and control all aspects of their user equipment while operating on public mobile networks in a fully spec-compliant manner), small boutique manufacturers of GSM devices (both MS/user equipment and network infrastructure), small community network operators and others whose interests are not represented by GSMA etc, especially in cases where our interests are in direct conflict with the interests of big players such as giant device manufacturers, giant commercial network operators and governments. A key goal of GSMUA is to be project-neutral, that is, every person and every small company belonging to any of the categories listed above (empowered end user, small boutique device manufacturer, small community network operator etc) should be fully welcome regardless of which specific project they are associated with. As of today there are at least two different projects offering GSM MS implementations (OsmocomBB and FreeCalypso) and at least two different projects offering network-side GSM implementations (Osmocom and OpenBTS), and I hope that this number of available alternatives will continue to grow: freedom of choice is always a good thing. But at the present time there exists no neutral soil on which members of different projects with a common interest (GSM networks and devices serving the interests of end users rather than big corporations and governments) and a common enemy (just named) can meet, and this lack of neutral meeting ground is the problem which GSMUA is meant to solve. I also have one practical application for GSMUA in mind already: to manage and legitimize recycling of wasted IMEI number ranges. By the official rules of GSMA etc each different *type* of GSM mobile equipment requires a different TAC, i.e., a range of at least 1 million IMEI numbers. So if a small boutique GSM device manufacturer makes a boutique MS device of which no more than 100 units will ever be made, 999900 IMEI numbers have to be wasted by the official rules. While I don't know of any manufacturer who got a range of 1 million IMEIs and only made 100 devices, we do have examples like Openmoko GTA01/02 and Pirelli DP-L10. In the case of Openmoko GTA02 I've been told that about 15 thousand units were made in total; in the case of Pirelli DP-L10 it appears that the total number produced was somewhere under 100 thousand. In each case a full range of 1 million IMEIs was allocated, and at least 900 thousand numbers out of each range are currently unused and wasted. If a small boutique manufacturer wishes to offer a boutique GSM MS product to the general public and wishes to ship each unit with a world-unique IMEI that stands a good chance of being accepted as valid by common GSM networks, and the product in question does not qualify for IMEI allocation by the official rules (e.g., the product is a development board specifically intended for users to run their own firmware and connect to live public networks with it, taking full personal responsibility for their actions) - the situation I found myself in with my GSM MS development board - I feel that the small boutique manuf in question should be empowered to squat on a small subrange of someone else's IMEI range if it is known beyond reasonable doubt to be wasted and unused. However, this recycling of wasted IMEI number ranges could be better organized and given at least some aura of semi-legitimacy if there were a community body set up to manage it, and this is where my proposed GSMUA can come in. Once we get our GSMUA up and running and assign a group of volunteers to be IMEI recycling managers, any small GSM or 3G+ device manufacturer who needs a small range of IMEI numbers will be able to request one from GSMUA, and we will allocate and assign these small subranges out of whatever wasted range we decide to squat on, ensuring that each requestor gets a different subrange. So these are my ideas, and I would like to see them turn into reality. We are going to need a simple website and a community mailing list at gsmua.org, and for the IMEI recycling service we will need a small group of volunteers to serve as its managers - I and Das Signal from FreeCalypso will be happy to serve on that panel, but it would be nice to also have someone from the Osmocom camp for better neutrality. Bright Blessings, Mychaela Falconia, Mother of FreeCalypso From antgorka at gmail.com Tue May 9 15:41:50 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Tue, 9 May 2017 18:41:50 +0300 Subject: CalypsoBTS and modern OsmoBSC Message-ID: Dear colleagues, I am trying to set up CalypsoBTS with the last version of OsmoNTIB and branch jolly/testing (so using two phones). I found that the manual from the main site is outdated. It doesn't work with the config provided os I am trying to figure out how to tune it manually. If I understood it correct, I have to setup calypso bts as bts of type nanoBTS, correct? I can sync with commercial cell, I can run OsmoBSC and OsmoBTS but I still cannot find my network from my personal phone in searching mode. Could you please tell me what can be wrong? I tried both GSM900 and DSC1800, different channels selected after RSSI checking... Both phones are w/o filter rework, they are motorola c113 and c113a. In logs of osmo-bts I can see: <0000> rsl.c:246 Tx RSL RF RESource INDication <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with response: 'RSP SETTSC -1' <0000> rsl.c:2353 (bts=0,trx=0,ts=0,ss=0) Rx RSL BCCH_INFO In osmo-bsc log everything looks fine: <001e> input/ipa.c:263 accept()ed new link from 127.0.0.1 to port 3003 <0005> abis_nm.c:2513 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) IPACCESS(0xe1): RSL CONNECT ACK <0005> abis_nm.c:698 OC=CHANNEL(03) INST=(00,00,00) Set Channel Attributes ACK <0004> bsc_init.c:288 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 29 using MCC=1 MNC=1 LAC=5 CID=5 BSIC=5 <0003> system_information.c:544 Serving cell: 29 <0003> bsc_init.c:105 SI1: 55 06 19 00 00 00 00 00 00 00 00 00 00 00 00 10 00 00 00 e5 04 00 2b Here below are my configs: ======================================= osmo-bts.cfg phy 0 instance 0 bts 0 band GSM900 ipa unit-id 1801 0 oml remote-ip 127.0.0.1 rtp jitter-buffer 0 paging queue-size 200 paging lifetime 0 ms-power-loop -60 timing-advance-loop settsc setbsic trx 0 phy 0 instance 0 ========================================= open-bsc.cfg phy 0 instance 0 bts 0 band GSM900 ipa unit-id 1801 0 oml remote-ip 127.0.0.1 rtp jitter-buffer 0 paging queue-size 200 paging lifetime 0 ms-power-loop -60 timing-advance-loop settsc setbsic trx 0 phy 0 instance 0 root at osmobox:~/.osmocom# cat open-bsc.cfg ! ! OpenBSC (0.15.0.754-c6e8) configuration saved from vty !! ! log stderr logging filter all 1 logging color 1 logging print category 0 logging timestamp 0 logging level all everything logging level rll everything logging level cc everything logging level mm everything logging level rr everything logging level rsl everything logging level nm everything logging level mncc notice logging level pag notice logging level meas notice logging level sccp notice logging level msc notice logging level mgcp notice logging level ho notice logging level db notice logging level ref notice logging level gprs debug logging level ns info logging level bssgp debug logging level llc debug logging level sndcp debug logging level nat notice logging level ctrl notice logging level smpp debug logging level filter debug logging level ranap debug logging level sua debug logging level lglobal notice logging level llapd notice logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp notice logging level lstats notice logging level lgsup notice logging level loap notice logging level lss7 notice logging level lsccp notice logging level lsua notice logging level lm3ua notice log file logfile logging filter all 0 logging color 1 logging print category 0 logging timestamp 0 logging level all everything logging level rll notice logging level cc notice logging level mm notice logging level rr notice logging level rsl notice logging level nm info logging level mncc notice logging level pag notice logging level meas notice logging level sccp notice logging level msc notice logging level mgcp notice logging level ho notice logging level db notice logging level ref notice logging level gprs debug logging level ns info logging level bssgp debug logging level llc debug logging level sndcp debug logging level nat notice logging level ctrl notice logging level smpp debug logging level filter debug logging level ranap debug logging level sua debug logging level lglobal notice logging level llapd notice logging level linp notice logging level lmux notice logging level lmi notice logging level lmib notice logging level lsms notice logging level lctrl notice logging level lgtp notice logging level lstats notice logging level lgsup notice logging level loap notice logging level lss7 notice logging level lsccp notice logging level lsua notice logging level lm3ua notice ! stats interval 5 ! line vty no login ! e1_input e1_line 0 driver ipa e1_line 0 port 0 no e1_line 0 keepalive network network country code 1 mobile network code 1 short name HomeGSM long name HomeGSM auth policy closed authorized-regexp .* location updating reject cause 13 encryption a5 0 neci 0 paging any use tch 0 rrlp mode none mm info 0 handover 0 handover window rxlev averaging 10 handover window rxqual averaging 1 handover window rxlev neighbor averaging 10 handover power budget interval 6 handover power budget hysteresis 3 handover maximum distance 9999 timer t3101 10 timer t3103 0 timer t3105 40 timer t3107 0 timer t3109 0 timer t3111 0 timer t3113 60 timer t3115 0 timer t3117 0 timer t3119 0 timer t3122 10 timer t3141 0 dyn_ts_allow_tch_f 0 subscriber-keep-in-ram 0 bts 0 type nanobts band GSM900 cell_identity 5 location_area_code 5 base_station_id_code 5 ms max power 0 cell reselection hysteresis 4 rxlev access min 0 periodic location update 30 radio-link-timeout 32 channel allocator ascending rach tx integer 9 rach max transmission 7 channel-descrption attach 1 channel-descrption bs-pa-mfrms 5 channel-descrption bs-ag-blks-res 1 early-classmark-sending forbidden ip.access unit_id 1801 0 ip.access rsl-ip 127.0.0.1 oml ip.access stream_id 255 line 0 neighbor-list mode automatic codec-support fr hr amr gprs mode none no force-combined-si trx 0 rf_locked 0 arfcn 29 nominal power 23 max_power_red 0 rsl e1 tei 0 timeslot 0 phys_chan_config CCCH+SDCCH4 hopping enabled 0 timeslot 1 phys_chan_config TCH/H hopping enabled 0 timeslot 2 phys_chan_config TCH/H hopping enabled 0 timeslot 3 phys_chan_config TCH/H hopping enabled 0 timeslot 4 phys_chan_config TCH/H hopping enabled 0 timeslot 5 phys_chan_config TCH/H hopping enabled 0 timeslot 6 phys_chan_config TCH/H hopping enabled 0 timeslot 7 phys_chan_config TCH/H hopping enabled 0 mncc-int default-codec tch-f amr default-codec tch-h amr nitb subscriber-create-on-demand assign-tmsi -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Tue May 9 17:44:40 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Wed, 10 May 2017 00:44:40 +0700 Subject: CalypsoBTS and modern OsmoBSC Message-ID: Hi, > I found that the manual from the main site is outdated. Yeah, still couldn't find some time to update the wiki. > If I understood it correct, I have to setup calypso bts > as bts of type nanoBTS, correct? Why do you think so? No, CalypsoBTS has nothing related toip.access nanoBTS. From the other side, we don't have a dedicated type for OsmoBTS, so you can use 'sysmoBTS'. > I can sync with commercial cell, I can run OsmoBSC and > OsmoBTS but I still cannot find my network from my personal > phone in searching mode. Please watch a great Sylvain's talk, where he explained almost everything you need to know: "Further hacks on the Calypso platform" https://media.ccc.de/v/29c3-5226-en-further_hacks_calypso_h264 In short: BTS should transmit a continuous beacon on C0 to be detected. Normal MS can't do that. CalypsoBTS was hacked to perform the following timeslot layout: Tt_R_ttt, where 'T' means TX on Downlink, 'R' means RX on Uplink, and 't' means channel filling - dummy bursts. Phone cannot RX and TX at the same time, so one phone serves only one TS. With two phones you have the following layout: TT_RRttt, so you have two timeslots served. This is why you will have some detection troubles even with working BSS setup :/ > In logs of osmo-bts I can see: > > <0000> rsl.c:246 Tx RSL RF RESource INDication > <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with > response: 'RSP SETTSC -1' > <0000> rsl.c:2353 (bts=0,trx=0,ts=0,ss=0) Rx RSL BCCH_INFO Just delete the 'settsc' line from your config, because CalypsoBTS transceiver only supports 'setbsic'. Have a fun! With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From antgorka at gmail.com Tue May 9 20:20:45 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Tue, 9 May 2017 23:20:45 +0300 Subject: CalypsoBTS and modern OsmoBSC In-Reply-To: References: Message-ID: Hi Vadim! Thank you for the comments. I will check your advices. Actually I already watched everything on youtube and other resources? But it needs more time to perceive all the info correctly... 9 ??? 2017 ?. 20:44 ???????????? "Vadim Yanitskiy" ???????: > Hi, > > > I found that the manual from the main site is outdated. > > Yeah, still couldn't find some time to update the wiki. > > > If I understood it correct, I have to setup calypso bts > > as bts of type nanoBTS, correct? > > Why do you think so? No, CalypsoBTS has nothing related > toip.access nanoBTS. From the other side, we don't have > a dedicated type for OsmoBTS, so you can use 'sysmoBTS'. > > > I can sync with commercial cell, I can run OsmoBSC and > > OsmoBTS but I still cannot find my network from my personal > > phone in searching mode. > > Please watch a great Sylvain's talk, where he explained > almost everything you need to know: > > "Further hacks on the Calypso platform" > https://media.ccc.de/v/29c3-5226-en-further_hacks_calypso_h264 > > In short: BTS should transmit a continuous beacon on C0 to be > detected. Normal MS can't do that. CalypsoBTS was hacked to > perform the following timeslot layout: Tt_R_ttt, where > 'T' means TX on Downlink, 'R' means RX on Uplink, and 't' means > channel filling - dummy bursts. Phone cannot RX and TX at the > same time, so one phone serves only one TS. With two phones > you have the following layout: TT_RRttt, so you have two > timeslots served. > > This is why you will have some detection troubles even with > working BSS setup :/ > > > In logs of osmo-bts I can see: > > > > <0000> rsl.c:246 Tx RSL RF RESource INDication > > <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with > > response: 'RSP SETTSC -1' > > <0000> rsl.c:2353 (bts=0,trx=0,ts=0,ss=0) Rx RSL BCCH_INFO > > Just delete the 'settsc' line from your config, because CalypsoBTS > transceiver only supports 'setbsic'. > > Have a fun! > > > With best regards, > Vadim Yanitskiy. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From antgorka at gmail.com Wed May 10 07:51:39 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Wed, 10 May 2017 10:51:39 +0300 Subject: CalypsoBTS and modern OsmoBSC In-Reply-To: References: Message-ID: Hello again, I set up bts like sysmobts but it seems there are some other issues. If I understood it correct I must specify phys_channel_confif for all TS of the BTS. Otherwise OsmoBTS cannot get settings from OsmoBSC. What config should I set for TS2-TS7? And will "slotmask 1 1 0 0 0 0 0 0" affect somehow the OsmoBTS behaviour? Now I can find my networks (sometimes :) but when my phone found it OsmoBTS crashes with the following message...: <0006> scheduler.c:1506 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 <0006> scheduler.c:1506 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 <0006> scheduler.c:1506 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 <0000> rsl.c:558 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with response: 'RSP NOHANDOVER -1' <0001> bts.c:208 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL <0006> scheduler.c:240 Exit scheduler for trx=0 <0006> scheduler.c:216 Init scheduler for trx=0 2017-05-09 23:20 GMT+03:00 Anton Gorbachev : > Hi Vadim! > > Thank you for the comments. I will check your advices. Actually I already > watched everything on youtube and other resources? But it needs more time > to perceive all the info correctly... > > 9 ??? 2017 ?. 20:44 ???????????? "Vadim Yanitskiy" > ???????: > > Hi, >> >> > I found that the manual from the main site is outdated. >> >> Yeah, still couldn't find some time to update the wiki. >> >> > If I understood it correct, I have to setup calypso bts >> > as bts of type nanoBTS, correct? >> >> Why do you think so? No, CalypsoBTS has nothing related >> toip.access nanoBTS. From the other side, we don't have >> a dedicated type for OsmoBTS, so you can use 'sysmoBTS'. >> >> > I can sync with commercial cell, I can run OsmoBSC and >> > OsmoBTS but I still cannot find my network from my personal >> > phone in searching mode. >> >> Please watch a great Sylvain's talk, where he explained >> almost everything you need to know: >> >> "Further hacks on the Calypso platform" >> https://media.ccc.de/v/29c3-5226-en-further_hacks_calypso_h264 >> >> In short: BTS should transmit a continuous beacon on C0 to be >> detected. Normal MS can't do that. CalypsoBTS was hacked to >> perform the following timeslot layout: Tt_R_ttt, where >> 'T' means TX on Downlink, 'R' means RX on Uplink, and 't' means >> channel filling - dummy bursts. Phone cannot RX and TX at the >> same time, so one phone serves only one TS. With two phones >> you have the following layout: TT_RRttt, so you have two >> timeslots served. >> >> This is why you will have some detection troubles even with >> working BSS setup :/ >> >> > In logs of osmo-bts I can see: >> > >> > <0000> rsl.c:246 Tx RSL RF RESource INDication >> > <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with >> > response: 'RSP SETTSC -1' >> > <0000> rsl.c:2353 (bts=0,trx=0,ts=0,ss=0) Rx RSL BCCH_INFO >> >> Just delete the 'settsc' line from your config, because CalypsoBTS >> transceiver only supports 'setbsic'. >> >> Have a fun! >> >> >> With best regards, >> Vadim Yanitskiy. >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From antgorka at gmail.com Wed May 10 12:48:10 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Wed, 10 May 2017 15:48:10 +0300 Subject: CalypsoBTS and modern OsmoBSC In-Reply-To: References: Message-ID: OK, I reassembled all the files with "old" toolchain and now I can see network but when I try to do a location update or add subscriver manually I get Segmentation fault (core dumped) In syslog: May 10 15:08:33 osmobox kernel: [ 740.703083] osmo-nitb[2517]: segfault at 6e656d70 ip b778b589 sp bf84ba40 error 4 in libdbdsqlite3.so[b7788000+8000] It seems there is some issue with HLR's sqlite. Did you meet such error before? I found also this thread http://lists.osmocom.org/pipermail/openbsc/2015-October/000578.html Should I use x64 bit architexture to solve it? Do you have working setup of calypsoBTS? What OS do you use for that? Kind regards. 2017-05-10 10:51 GMT+03:00 Anton Gorbachev : > Hello again, > > I set up bts like sysmobts but it seems there are some other issues. > If I understood it correct I must specify phys_channel_confif for all TS > of the BTS. > Otherwise OsmoBTS cannot get settings from OsmoBSC. What config should I > set for TS2-TS7? > And will "slotmask 1 1 0 0 0 0 0 0" affect somehow the OsmoBTS behaviour? > > Now I can find my networks (sometimes :) but when my phone found it > OsmoBTS crashes with the following message...: > > <0006> scheduler.c:1506 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 > <0006> scheduler.c:1506 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 > <0006> scheduler.c:1506 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 > <0000> rsl.c:558 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK > <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with > response: 'RSP NOHANDOVER -1' > <0001> bts.c:208 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL > <0006> scheduler.c:240 Exit scheduler for trx=0 > <0006> scheduler.c:216 Init scheduler for trx=0 > > 2017-05-09 23:20 GMT+03:00 Anton Gorbachev : > >> Hi Vadim! >> >> Thank you for the comments. I will check your advices. Actually I already >> watched everything on youtube and other resources? But it needs more time >> to perceive all the info correctly... >> >> 9 ??? 2017 ?. 20:44 ???????????? "Vadim Yanitskiy" >> ???????: >> >> Hi, >>> >>> > I found that the manual from the main site is outdated. >>> >>> Yeah, still couldn't find some time to update the wiki. >>> >>> > If I understood it correct, I have to setup calypso bts >>> > as bts of type nanoBTS, correct? >>> >>> Why do you think so? No, CalypsoBTS has nothing related >>> toip.access nanoBTS. From the other side, we don't have >>> a dedicated type for OsmoBTS, so you can use 'sysmoBTS'. >>> >>> > I can sync with commercial cell, I can run OsmoBSC and >>> > OsmoBTS but I still cannot find my network from my personal >>> > phone in searching mode. >>> >>> Please watch a great Sylvain's talk, where he explained >>> almost everything you need to know: >>> >>> "Further hacks on the Calypso platform" >>> https://media.ccc.de/v/29c3-5226-en-further_hacks_calypso_h264 >>> >>> In short: BTS should transmit a continuous beacon on C0 to be >>> detected. Normal MS can't do that. CalypsoBTS was hacked to >>> perform the following timeslot layout: Tt_R_ttt, where >>> 'T' means TX on Downlink, 'R' means RX on Uplink, and 't' means >>> channel filling - dummy bursts. Phone cannot RX and TX at the >>> same time, so one phone serves only one TS. With two phones >>> you have the following layout: TT_RRttt, so you have two >>> timeslots served. >>> >>> This is why you will have some detection troubles even with >>> working BSS setup :/ >>> >>> > In logs of osmo-bts I can see: >>> > >>> > <0000> rsl.c:246 Tx RSL RF RESource INDication >>> > <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with >>> > response: 'RSP SETTSC -1' >>> > <0000> rsl.c:2353 (bts=0,trx=0,ts=0,ss=0) Rx RSL BCCH_INFO >>> >>> Just delete the 'settsc' line from your config, because CalypsoBTS >>> transceiver only supports 'setbsic'. >>> >>> Have a fun! >>> >>> >>> With best regards, >>> Vadim Yanitskiy. >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From antgorka at gmail.com Thu May 11 10:43:10 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Thu, 11 May 2017 13:43:10 +0300 Subject: CalypsoBTS and modern OsmoBSC In-Reply-To: References: Message-ID: OK, I tried Ubuntu 14.04 amd64 and Segmantation error disappeared. I can connect to my network, register subscribers, perform USSD but now I cannot receive SMS. In NITB logs I can see an error. <0022> gsm0411_smc.c:331 SMC(0) cannot release yet current state: WAIT_CP_ACK Don't you know what can it mean? More details: <0002> gsm_04_08.c:1016 <- CM SERVICE REQUEST serv_type=0x04 MI(TMSI)=3404602319 <0002> gsm_04_08_utils.c:662 -> CM SERVICE ACK <0002> gsm_subscriber.c:341 Subscriber 250996689298609 ATTACHED LAC=0 <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 ESTABLISH INDICATION <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 ESTABLISH INDICATION <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 DATA INDICATION <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=9 <0001> transaction.c:71 subscr=0x26a3110, net=0x255cd50 <0022> gsm0411_smc.c:331 SMC(0) cannot release yet current state: WAIT_CP_ACK <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 DATA INDICATION <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=9 <0000> chan_alloc.c:486 (bts=0,trx=0,ts=1,ss=0) starting release sequence <0004> abis_rsl.c:1221 (bts=0,trx=0,ts=1,ss=0) state ACTIVE -> RELEASE REQUESTED <0000> abis_rsl.c:1191 (bts=0,trx=0,ts=1,ss=0) RSL RLL RELEASE REQ (link_id=0x43, reason=1) <0003> gsm_04_08_utils.c:251 Sending Channel Release: Chan: Number: 0 Type: 3 <0004> abis_rsl.c:767 (bts=0,trx=0,ts=1,ss=0) DEACTivate SACCH CMD <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 RELEASE CONFIRMATION <0004> abis_rsl.c:2022 (bts=0,trx=0,ts=1,ss=0) waiting for SAPI=0 to be released. <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=0 RELEASE INDICATION <0004> abis_rsl.c:1715 (bts=0,trx=0,ts=1,ss=0) T3111 expired: releasing RF Channel <0004> abis_rsl.c:859 (bts=0,trx=0,ts=1,ss=0) RF Channel Release <0004> abis_rsl.c:929 (bts=0,trx=0,ts=1,ss=0) RF CHANNEL RELEASE ACK <0004> abis_rsl.c:1221 (bts=0,trx=0,ts=1,ss=0) state RELEASE REQUESTED -> NONE 2017-05-10 15:48 GMT+03:00 Anton Gorbachev : > OK, > > I reassembled all the files with "old" toolchain and now I can see network > but when I try to do a location update or add subscriver manually I get > > Segmentation fault (core dumped) > > In syslog: > May 10 15:08:33 osmobox kernel: [ 740.703083] osmo-nitb[2517]: segfault > at 6e656d70 ip b778b589 sp bf84ba40 error 4 in libdbdsqlite3.so[b7788000+ > 8000] > > > It seems there is some issue with HLR's sqlite. > Did you meet such error before? > > I found also this thread > http://lists.osmocom.org/pipermail/openbsc/2015-October/000578.html > > Should I use x64 bit architexture to solve it? Do you have working setup > of calypsoBTS? What OS do you use for that? > > Kind regards. > > 2017-05-10 10:51 GMT+03:00 Anton Gorbachev : > >> Hello again, >> >> I set up bts like sysmobts but it seems there are some other issues. >> If I understood it correct I must specify phys_channel_confif for all TS >> of the BTS. >> Otherwise OsmoBTS cannot get settings from OsmoBSC. What config should I >> set for TS2-TS7? >> And will "slotmask 1 1 0 0 0 0 0 0" affect somehow the OsmoBTS behaviour? >> >> Now I can find my networks (sometimes :) but when my phone found it >> OsmoBTS crashes with the following message...: >> >> <0006> scheduler.c:1506 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 >> <0006> scheduler.c:1506 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 >> <0006> scheduler.c:1506 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 >> <0000> rsl.c:558 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK >> <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with >> response: 'RSP NOHANDOVER -1' >> <0001> bts.c:208 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL >> <0006> scheduler.c:240 Exit scheduler for trx=0 >> <0006> scheduler.c:216 Init scheduler for trx=0 >> >> 2017-05-09 23:20 GMT+03:00 Anton Gorbachev : >> >>> Hi Vadim! >>> >>> Thank you for the comments. I will check your advices. Actually I >>> already watched everything on youtube and other resources? But it needs >>> more time to perceive all the info correctly... >>> >>> 9 ??? 2017 ?. 20:44 ???????????? "Vadim Yanitskiy" >>> ???????: >>> >>> Hi, >>>> >>>> > I found that the manual from the main site is outdated. >>>> >>>> Yeah, still couldn't find some time to update the wiki. >>>> >>>> > If I understood it correct, I have to setup calypso bts >>>> > as bts of type nanoBTS, correct? >>>> >>>> Why do you think so? No, CalypsoBTS has nothing related >>>> toip.access nanoBTS. From the other side, we don't have >>>> a dedicated type for OsmoBTS, so you can use 'sysmoBTS'. >>>> >>>> > I can sync with commercial cell, I can run OsmoBSC and >>>> > OsmoBTS but I still cannot find my network from my personal >>>> > phone in searching mode. >>>> >>>> Please watch a great Sylvain's talk, where he explained >>>> almost everything you need to know: >>>> >>>> "Further hacks on the Calypso platform" >>>> https://media.ccc.de/v/29c3-5226-en-further_hacks_calypso_h264 >>>> >>>> In short: BTS should transmit a continuous beacon on C0 to be >>>> detected. Normal MS can't do that. CalypsoBTS was hacked to >>>> perform the following timeslot layout: Tt_R_ttt, where >>>> 'T' means TX on Downlink, 'R' means RX on Uplink, and 't' means >>>> channel filling - dummy bursts. Phone cannot RX and TX at the >>>> same time, so one phone serves only one TS. With two phones >>>> you have the following layout: TT_RRttt, so you have two >>>> timeslots served. >>>> >>>> This is why you will have some detection troubles even with >>>> working BSS setup :/ >>>> >>>> > In logs of osmo-bts I can see: >>>> > >>>> > <0000> rsl.c:246 Tx RSL RF RESource INDication >>>> > <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with >>>> > response: 'RSP SETTSC -1' >>>> > <0000> rsl.c:2353 (bts=0,trx=0,ts=0,ss=0) Rx RSL BCCH_INFO >>>> >>>> Just delete the 'settsc' line from your config, because CalypsoBTS >>>> transceiver only supports 'setbsic'. >>>> >>>> Have a fun! >>>> >>>> >>>> With best regards, >>>> Vadim Yanitskiy. >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Thu May 11 10:58:23 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Thu, 11 May 2017 13:58:23 +0300 Subject: CalypsoBTS and modern OsmoBSC In-Reply-To: References: Message-ID: Hi, > (bts=0,trx=0,ts=1,ss=0) Why SMS transmission is on TS1? Which channel configuration do you use? With best regards, Vadim Yanitskiy. 2017-05-11 13:43 GMT+03:00 Anton Gorbachev : > OK, > > I tried Ubuntu 14.04 amd64 and Segmantation error disappeared. I can > connect to my network, register subscribers, perform USSD but now I cannot > receive SMS. > In NITB logs I can see an error. <0022> gsm0411_smc.c:331 SMC(0) cannot > release yet current state: WAIT_CP_ACK > > Don't you know what can it mean? > > More details: > > <0002> gsm_04_08.c:1016 <- CM SERVICE REQUEST serv_type=0x04 > MI(TMSI)=3404602319 > <0002> gsm_04_08_utils.c:662 -> CM SERVICE ACK > <0002> gsm_subscriber.c:341 Subscriber 250996689298609 ATTACHED LAC=0 > <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 ESTABLISH INDICATION > <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 ESTABLISH INDICATION > <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 DATA INDICATION > <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=9 > <0001> transaction.c:71 subscr=0x26a3110, net=0x255cd50 > <0022> gsm0411_smc.c:331 SMC(0) cannot release yet current state: > WAIT_CP_ACK > <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 DATA INDICATION > <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=9 > <0000> chan_alloc.c:486 (bts=0,trx=0,ts=1,ss=0) starting release sequence > <0004> abis_rsl.c:1221 (bts=0,trx=0,ts=1,ss=0) state ACTIVE -> RELEASE > REQUESTED > <0000> abis_rsl.c:1191 (bts=0,trx=0,ts=1,ss=0) RSL RLL RELEASE REQ > (link_id=0x43, reason=1) > <0003> gsm_04_08_utils.c:251 Sending Channel Release: Chan: Number: 0 > Type: 3 > <0004> abis_rsl.c:767 (bts=0,trx=0,ts=1,ss=0) DEACTivate SACCH CMD > <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 RELEASE CONFIRMATION > <0004> abis_rsl.c:2022 (bts=0,trx=0,ts=1,ss=0) waiting for SAPI=0 to be > released. > <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=0 RELEASE INDICATION > <0004> abis_rsl.c:1715 (bts=0,trx=0,ts=1,ss=0) T3111 expired: releasing RF > Channel > <0004> abis_rsl.c:859 (bts=0,trx=0,ts=1,ss=0) RF Channel Release > <0004> abis_rsl.c:929 (bts=0,trx=0,ts=1,ss=0) RF CHANNEL RELEASE ACK > <0004> abis_rsl.c:1221 (bts=0,trx=0,ts=1,ss=0) state RELEASE REQUESTED -> > NONE > > > > > 2017-05-10 15:48 GMT+03:00 Anton Gorbachev : > >> OK, >> >> I reassembled all the files with "old" toolchain and now I can see >> network but when I try to do a location update or add subscriver manually I >> get >> >> Segmentation fault (core dumped) >> >> In syslog: >> May 10 15:08:33 osmobox kernel: [ 740.703083] osmo-nitb[2517]: segfault >> at 6e656d70 ip b778b589 sp bf84ba40 error 4 in >> libdbdsqlite3.so[b7788000+8000] >> >> >> It seems there is some issue with HLR's sqlite. >> Did you meet such error before? >> >> I found also this thread >> http://lists.osmocom.org/pipermail/openbsc/2015-October/000578.html >> >> Should I use x64 bit architexture to solve it? Do you have working setup >> of calypsoBTS? What OS do you use for that? >> >> Kind regards. >> >> 2017-05-10 10:51 GMT+03:00 Anton Gorbachev : >> >>> Hello again, >>> >>> I set up bts like sysmobts but it seems there are some other issues. >>> If I understood it correct I must specify phys_channel_confif for all TS >>> of the BTS. >>> Otherwise OsmoBTS cannot get settings from OsmoBSC. What config should I >>> set for TS2-TS7? >>> And will "slotmask 1 1 0 0 0 0 0 0" affect somehow the OsmoBTS behaviour? >>> >>> Now I can find my networks (sometimes :) but when my phone found it >>> OsmoBTS crashes with the following message...: >>> >>> <0006> scheduler.c:1506 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 >>> <0006> scheduler.c:1506 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 >>> <0006> scheduler.c:1506 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 >>> <0000> rsl.c:558 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK >>> <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with >>> response: 'RSP NOHANDOVER -1' >>> <0001> bts.c:208 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL >>> <0006> scheduler.c:240 Exit scheduler for trx=0 >>> <0006> scheduler.c:216 Init scheduler for trx=0 >>> >>> 2017-05-09 23:20 GMT+03:00 Anton Gorbachev : >>> >>>> Hi Vadim! >>>> >>>> Thank you for the comments. I will check your advices. Actually I >>>> already watched everything on youtube and other resources? But it needs >>>> more time to perceive all the info correctly... >>>> >>>> 9 ??? 2017 ?. 20:44 ???????????? "Vadim Yanitskiy" < >>>> axilirator at gmail.com> ???????: >>>> >>>> Hi, >>>>> >>>>> > I found that the manual from the main site is outdated. >>>>> >>>>> Yeah, still couldn't find some time to update the wiki. >>>>> >>>>> > If I understood it correct, I have to setup calypso bts >>>>> > as bts of type nanoBTS, correct? >>>>> >>>>> Why do you think so? No, CalypsoBTS has nothing related >>>>> toip.access nanoBTS. From the other side, we don't have >>>>> a dedicated type for OsmoBTS, so you can use 'sysmoBTS'. >>>>> >>>>> > I can sync with commercial cell, I can run OsmoBSC and >>>>> > OsmoBTS but I still cannot find my network from my personal >>>>> > phone in searching mode. >>>>> >>>>> Please watch a great Sylvain's talk, where he explained >>>>> almost everything you need to know: >>>>> >>>>> "Further hacks on the Calypso platform" >>>>> https://media.ccc.de/v/29c3-5226-en-further_hacks_calypso_h264 >>>>> >>>>> In short: BTS should transmit a continuous beacon on C0 to be >>>>> detected. Normal MS can't do that. CalypsoBTS was hacked to >>>>> perform the following timeslot layout: Tt_R_ttt, where >>>>> 'T' means TX on Downlink, 'R' means RX on Uplink, and 't' means >>>>> channel filling - dummy bursts. Phone cannot RX and TX at the >>>>> same time, so one phone serves only one TS. With two phones >>>>> you have the following layout: TT_RRttt, so you have two >>>>> timeslots served. >>>>> >>>>> This is why you will have some detection troubles even with >>>>> working BSS setup :/ >>>>> >>>>> > In logs of osmo-bts I can see: >>>>> > >>>>> > <0000> rsl.c:246 Tx RSL RF RESource INDication >>>>> > <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with >>>>> > response: 'RSP SETTSC -1' >>>>> > <0000> rsl.c:2353 (bts=0,trx=0,ts=0,ss=0) Rx RSL BCCH_INFO >>>>> >>>>> Just delete the 'settsc' line from your config, because CalypsoBTS >>>>> transceiver only supports 'setbsic'. >>>>> >>>>> Have a fun! >>>>> >>>>> >>>>> With best regards, >>>>> Vadim Yanitskiy. >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From antgorka at gmail.com Thu May 11 11:11:33 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Thu, 11 May 2017 14:11:33 +0300 Subject: CalypsoBTS and modern OsmoBSC In-Reply-To: References: Message-ID: Hi Vadim, Here is what I see now [image: ?????????? ??????????? 1] I use the following configs now (attached). BTW, I cannot receive calls also, it's trying to dial for a minute maybe and then drop the connection. In logs I can see that TCH/H is being tryed to be allocated.. It seems slotmask directive doesn't affec the behaviour at all. I cannot anyway set only two timeslots in open-bsc.cfg. If so I get an error during OML processes. 2017-05-11 13:58 GMT+03:00 Vadim Yanitskiy : > Hi, > > > (bts=0,trx=0,ts=1,ss=0) > > Why SMS transmission is on TS1? > Which channel configuration do you use? > > With best regards, > Vadim Yanitskiy. > > 2017-05-11 13:43 GMT+03:00 Anton Gorbachev : > >> OK, >> >> I tried Ubuntu 14.04 amd64 and Segmantation error disappeared. I can >> connect to my network, register subscribers, perform USSD but now I cannot >> receive SMS. >> In NITB logs I can see an error. <0022> gsm0411_smc.c:331 SMC(0) cannot >> release yet current state: WAIT_CP_ACK >> >> Don't you know what can it mean? >> >> More details: >> >> <0002> gsm_04_08.c:1016 <- CM SERVICE REQUEST serv_type=0x04 >> MI(TMSI)=3404602319 >> <0002> gsm_04_08_utils.c:662 -> CM SERVICE ACK >> <0002> gsm_subscriber.c:341 Subscriber 250996689298609 ATTACHED LAC=0 >> <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 ESTABLISH INDICATION >> <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 ESTABLISH INDICATION >> <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 DATA INDICATION >> <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=9 >> <0001> transaction.c:71 subscr=0x26a3110, net=0x255cd50 >> <0022> gsm0411_smc.c:331 SMC(0) cannot release yet current state: >> WAIT_CP_ACK >> <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 DATA INDICATION >> <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=9 >> <0000> chan_alloc.c:486 (bts=0,trx=0,ts=1,ss=0) starting release sequence >> <0004> abis_rsl.c:1221 (bts=0,trx=0,ts=1,ss=0) state ACTIVE -> RELEASE >> REQUESTED >> <0000> abis_rsl.c:1191 (bts=0,trx=0,ts=1,ss=0) RSL RLL RELEASE REQ >> (link_id=0x43, reason=1) >> <0003> gsm_04_08_utils.c:251 Sending Channel Release: Chan: Number: 0 >> Type: 3 >> <0004> abis_rsl.c:767 (bts=0,trx=0,ts=1,ss=0) DEACTivate SACCH CMD >> <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=3 RELEASE CONFIRMATION >> <0004> abis_rsl.c:2022 (bts=0,trx=0,ts=1,ss=0) waiting for SAPI=0 to be >> released. >> <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=0 RELEASE INDICATION >> <0004> abis_rsl.c:1715 (bts=0,trx=0,ts=1,ss=0) T3111 expired: releasing >> RF Channel >> <0004> abis_rsl.c:859 (bts=0,trx=0,ts=1,ss=0) RF Channel Release >> <0004> abis_rsl.c:929 (bts=0,trx=0,ts=1,ss=0) RF CHANNEL RELEASE ACK >> <0004> abis_rsl.c:1221 (bts=0,trx=0,ts=1,ss=0) state RELEASE REQUESTED -> >> NONE >> >> >> >> >> 2017-05-10 15:48 GMT+03:00 Anton Gorbachev : >> >>> OK, >>> >>> I reassembled all the files with "old" toolchain and now I can see >>> network but when I try to do a location update or add subscriver manually I >>> get >>> >>> Segmentation fault (core dumped) >>> >>> In syslog: >>> May 10 15:08:33 osmobox kernel: [ 740.703083] osmo-nitb[2517]: segfault >>> at 6e656d70 ip b778b589 sp bf84ba40 error 4 in >>> libdbdsqlite3.so[b7788000+8000] >>> >>> >>> It seems there is some issue with HLR's sqlite. >>> Did you meet such error before? >>> >>> I found also this thread >>> http://lists.osmocom.org/pipermail/openbsc/2015-October/000578.html >>> >>> Should I use x64 bit architexture to solve it? Do you have working setup >>> of calypsoBTS? What OS do you use for that? >>> >>> Kind regards. >>> >>> 2017-05-10 10:51 GMT+03:00 Anton Gorbachev : >>> >>>> Hello again, >>>> >>>> I set up bts like sysmobts but it seems there are some other issues. >>>> If I understood it correct I must specify phys_channel_confif for all >>>> TS of the BTS. >>>> Otherwise OsmoBTS cannot get settings from OsmoBSC. What config should >>>> I set for TS2-TS7? >>>> And will "slotmask 1 1 0 0 0 0 0 0" affect somehow the OsmoBTS >>>> behaviour? >>>> >>>> Now I can find my networks (sometimes :) but when my phone found it >>>> OsmoBTS crashes with the following message...: >>>> >>>> <0006> scheduler.c:1506 Set a5/0 uplink for SACCH/4(0) on trx=0 ts=0 >>>> <0006> scheduler.c:1506 Set a5/0 downlink for SDCCH/4(0) on trx=0 ts=0 >>>> <0006> scheduler.c:1506 Set a5/0 downlink for SACCH/4(0) on trx=0 ts=0 >>>> <0000> rsl.c:558 (bts=0,trx=0,ts=0,ss=0) Tx CHAN ACT ACK >>>> <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with >>>> response: 'RSP NOHANDOVER -1' >>>> <0001> bts.c:208 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL >>>> <0006> scheduler.c:240 Exit scheduler for trx=0 >>>> <0006> scheduler.c:216 Init scheduler for trx=0 >>>> >>>> 2017-05-09 23:20 GMT+03:00 Anton Gorbachev : >>>> >>>>> Hi Vadim! >>>>> >>>>> Thank you for the comments. I will check your advices. Actually I >>>>> already watched everything on youtube and other resources? But it needs >>>>> more time to perceive all the info correctly... >>>>> >>>>> 9 ??? 2017 ?. 20:44 ???????????? "Vadim Yanitskiy" < >>>>> axilirator at gmail.com> ???????: >>>>> >>>>> Hi, >>>>>> >>>>>> > I found that the manual from the main site is outdated. >>>>>> >>>>>> Yeah, still couldn't find some time to update the wiki. >>>>>> >>>>>> > If I understood it correct, I have to setup calypso bts >>>>>> > as bts of type nanoBTS, correct? >>>>>> >>>>>> Why do you think so? No, CalypsoBTS has nothing related >>>>>> toip.access nanoBTS. From the other side, we don't have >>>>>> a dedicated type for OsmoBTS, so you can use 'sysmoBTS'. >>>>>> >>>>>> > I can sync with commercial cell, I can run OsmoBSC and >>>>>> > OsmoBTS but I still cannot find my network from my personal >>>>>> > phone in searching mode. >>>>>> >>>>>> Please watch a great Sylvain's talk, where he explained >>>>>> almost everything you need to know: >>>>>> >>>>>> "Further hacks on the Calypso platform" >>>>>> https://media.ccc.de/v/29c3-5226-en-further_hacks_calypso_h264 >>>>>> >>>>>> In short: BTS should transmit a continuous beacon on C0 to be >>>>>> detected. Normal MS can't do that. CalypsoBTS was hacked to >>>>>> perform the following timeslot layout: Tt_R_ttt, where >>>>>> 'T' means TX on Downlink, 'R' means RX on Uplink, and 't' means >>>>>> channel filling - dummy bursts. Phone cannot RX and TX at the >>>>>> same time, so one phone serves only one TS. With two phones >>>>>> you have the following layout: TT_RRttt, so you have two >>>>>> timeslots served. >>>>>> >>>>>> This is why you will have some detection troubles even with >>>>>> working BSS setup :/ >>>>>> >>>>>> > In logs of osmo-bts I can see: >>>>>> > >>>>>> > <0000> rsl.c:246 Tx RSL RF RESource INDication >>>>>> > <000b> trx_if.c:397 transceiver (phy0.0) rejected TRX command with >>>>>> > response: 'RSP SETTSC -1' >>>>>> > <0000> rsl.c:2353 (bts=0,trx=0,ts=0,ss=0) Rx RSL BCCH_INFO >>>>>> >>>>>> Just delete the 'settsc' line from your config, because CalypsoBTS >>>>>> transceiver only supports 'setbsic'. >>>>>> >>>>>> Have a fun! >>>>>> >>>>>> >>>>>> With best regards, >>>>>> Vadim Yanitskiy. >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 119035 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: open-bsc.cfg Type: application/octet-stream Size: 3574 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: osmo-bts.cfg Type: application/octet-stream Size: 1440 bytes Desc: not available URL: From nhofmeyr at sysmocom.de Thu May 11 12:59:52 2017 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Thu, 11 May 2017 14:59:52 +0200 Subject: CalypsoBTS and modern OsmoBSC In-Reply-To: References: Message-ID: <20170511125952.GE6617@my.box> Please, again, no-one should *ever* send image bitmaps of text screenshots to a mailing list! ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From antgorka at gmail.com Thu May 11 15:12:23 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Thu, 11 May 2017 18:12:23 +0300 Subject: Timeslot allocation Message-ID: Dear colleagues, Could you please tell me when I am wrong in my assumptions? My story is about beacon channel. >From different resourses I got the information that we transmit bcch data (fcch,sch,bcch) which is required for MS to find our network. OK? On the pictures it's drawn like we transmit BCCH on C0T0. So DL TS1-7 can be used for i.e. TCH. So if we want just to create bts which can be found by MS and that's all, we may not transmit on TS1-7 at all. OK? When we are talking about CalypsoBTS we say that we must transmit several burst in a row. So here I am a bit confused. So if we want to just transmit bcch messages we can transmit every TS0 and rest on TS1-7. Why not? Why I can see in manuals and videos pictures like Ttt_R_tt? Why do I need these dummy "t" bursts? Why one burst is "t" and another is "T"? Sure I understand that we must receive something for normal BTS operation like RACH and need some time to switch Tx/Rx. But why we just cannot use mask like T_R_T_R_ ...? I understood that we cant use mask TTT_RR because calypso phone was not hacked to receive two bursts in a row. Thanks in advance! -------------- next part -------------- An HTML attachment was scrubbed... URL: From antgorka at gmail.com Thu May 11 18:01:20 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Thu, 11 May 2017 21:01:20 +0300 Subject: CalypsoBTS and modern OsmoBSC In-Reply-To: <20170511125952.GE6617@my.box> References: <20170511125952.GE6617@my.box> Message-ID: Hi, I could setup calypsoBTS, send sms and even do voice calls but only for few seconds. Then capypsoBTS crashes. @Vadim, I remember you wrote somewhere you could setup calls for several minutes? Maybe there are some amr settings or I need to use another codec or something, don't you remember which setting did you use for voice call routine? What I can see in logs after I stop hearing anything: OsmoBTS: <0006> scheduler_trx.c:702 TCH/H(0) has not been served !! No prim for trx=0 ts=1 at fn=1119261 to transmit. <0006> scheduler_trx.c:535 TCH/H(1) Transmitting 'bad AMR frame' trx=0 ts=1 at fn=1119262. <0006> scheduler_trx.c:702 TCH/H(1) has not been served !! No prim for trx=0 ts=1 at fn=1119262 to transmit. <0006> scheduler.c:524 TCH RTS.ind: chan=TCH/H(0) chan_nr=0x11 fn=1119269 ts=1 trx=0 <0006> scheduler.c:423 PH-DATA.req: chan_nr=0x11 link_id=0x00 fn=1119269 ts=1 trx=0 <0006> scheduler.c:446 TCH.req: chan_nr=0x11 fn=1119269 ts=1 trx=0 <0006> scheduler.c:524 TCH RTS.ind: chan=TCH/H(1) chan_nr=0x19 fn=1119270 ts=1 trx=0 <0006> scheduler.c:423 PH-DATA.req: chan_nr=0x19 link_id=0x00 fn=1119270 ts=1 trx=0 <0006> scheduler.c:446 TCH.req: chan_nr=0x19 fn=1119270 ts=1 trx=0 <0006> scheduler_trx.c:354 Missing TCH bursts detected, sending BFI for TCH/H(0) <0006> scheduler_trx.c:535 TCH/H(0) Transmitting 'bad AMR frame' trx=0 ts=1 at fn=1119265. <0006> scheduler_trx.c:702 TCH/H(0) has not been served !! No prim for trx=0 ts=1 at fn=1119265 to transmit. <0006> scheduler_trx.c:354 Missing TCH bursts detected, sending BFI for TCH/H(1) <0006> scheduler_trx.c:535 TCH/H(1) Transmitting 'bad AMR frame' trx=0 ts=1 at fn=1119266. <0006> scheduler_trx.c:702 TCH/H(1) has not been served !! No prim for trx=0 ts=1 at fn=1119266 to transmit. <0006> scheduler.c:524 TCH RTS.ind: chan=TCH/H(0) chan_nr=0x11 fn=1119274 ts=1 trx=0 <0006> scheduler.c:446 TCH.req: chan_nr=0x11 fn=1119274 ts=1 trx=0 <0006> scheduler_trx.c:535 TCH/H(0) Transmitting 'bad AMR frame' trx=0 ts=1 at fn=1119269. <0006> scheduler_trx.c:702 TCH/H(0) has not been served !! No prim for trx=0 ts=1 at fn=1119269 to transmit. OsmoBSC: <0001> gsm_04_08.c:3894 (bts 0 trx 0 ts 1 ti 8 sub 44680) Received 'SETUP' from MS in state 0 (NULL) <0001> gsm_04_08.c:3899 Unknown transaction ID 8, creating new trans. <0001> transaction.c:71 subscr=0xd67f60, net=0xc08d50 <0001> gsm_04_08.c:1623 new state NULL -> INITIATED <0001> gsm_04_08.c:2302 Subscriber 250996689298609 (44680) sends SETUP to 43926 <0001> gsm_04_08.c:1685 (bts 0 trx 0 ts 1 ti 8 sub 44680) Sending 'MNCC_SETUP_IND' to MNCC. <0001> gsm_04_08.c:3796 (bts 0 trx 0 ts 1 ti 08 sub 44680) Received 'MNCC_CALL_PROC_REQ' from MNCC in state 1 (INITIATED) <0001> gsm_04_08.c:1623 new state INITIATED -> MO_CALL_PROC <0001> gsm_04_08.c:143 (bts 0 trx 0 ts 1 ti 80) Sending 'CALL_PROC' to MS. <0001> gsm_04_08.c:3796 (bts 0 trx 0 ts 1 ti 08 sub 44680) Received 'MNCC_LCHAN_MODIFY' from MNCC in state 3 (MO_CALL_PROC) <000a> bsc_api.c:404 Sending (bts=0,trx=0,ts=1,ss=0) ChanModify for speech: SPEECH_AMR on channel TCH_H <0003> gsm_04_08_utils.c:512 -> CHANNEL MODE MODIFY mode=0x41 <0001> transaction.c:71 subscr=0xd77ad0, net=0xc08d50 <0002> gsm_subscriber.c:190 Subscriber 250202101944311 not paged yet. <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=0 DATA INDICATION <0003> gsm_04_08_utils.c:537 CHANNEL MODE MODIFY ACK <0004> abis_rsl.c:2268 (bts=0,trx=0,ts=1,ss=0) IPAC_BIND speech_mode=0x15 RTP_PAYLOAD=98 <0003> osmo_msc.c:76 MSC assign complete (do nothing). <0004> abis_rsl.c:1608 (bts=0,trx=0,ts=1,ss=0) CHANNEL MODE MODIFY ACK <0004> abis_rsl.c:2449 (bts=0,trx=0,ts=1,ss=0) IPAC_CRCX_ACK LOCAL_IP=127.0.0.1 LOCAL_PORT=10880 CON_ID=0 <0000> chan_alloc.c:352 (bts=0,trx=0,ts=1,pchan=TCH/H) Allocating lchan=1 as TCH_H <0004> abis_rsl.c:1863 (bts=0,trx=0,ts=1,ss=1) Activating ARFCN(866) SS(1) lctype TCH_H r=PAGING ra=0x2d ta=0 <0004> abis_rsl.c:585 (bts=0,trx=0,ts=1,pchan=TCH/H) Tx RSL Channel Activate with act_type=INITIAL <0004> abis_rsl.c:1221 (bts=0,trx=0,ts=1,ss=1) state NONE -> ACTIVATION REQUESTED <0004> abis_rsl.c:1587 (bts=0,trx=0,ts=1,ss=1) CHANNEL ACTIVATE ACK <0004> abis_rsl.c:1221 (bts=0,trx=0,ts=1,ss=1) state ACTIVATION REQUESTED -> ACTIVE <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=1) SAPI=0 ESTABLISH INDICATION <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=6 <0003> gsm_04_08.c:1462 PAGING RESPONSE: MI(TMSI)=2399361011 <0003> gsm_04_08.c:1495 <- Channel was requested by 250202101944311 <0001> gsm_04_08.c:1755 Paging subscr 43926 succeeded! <0001> gsm_04_08.c:2226 starting timer T303 with 30 seconds <0001> gsm_04_08.c:1623 new state NULL -> CALL_PRESENT <0001> gsm_04_08.c:143 (bts 0 trx 0 ts 1 ti 00) Sending 'SETUP' to MS. <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=1) SAPI=0 DATA INDICATION <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=3 <0001> gsm_04_08.c:3894 (bts 0 trx 0 ts 1 ti 0 sub 43926) Received 'CALL_CONF' from MS in state 6 (CALL_PRESENT) <0001> gsm_04_08.c:1665 stopping pending timer T303 <0001> gsm_04_08.c:2226 starting timer T310 with 180 seconds <0001> gsm_04_08.c:1623 new state CALL_PRESENT -> MO_TERM_CALL_CONF <0001> gsm_04_08.c:1685 (bts 0 trx 0 ts 1 ti 0 sub 43926) Sending 'MNCC_CALL_CONF_IND' to MNCC. <0001> gsm_04_08.c:3796 (bts 0 trx 0 ts 1 ti 00 sub 43926) Received 'MNCC_LCHAN_MODIFY' from MNCC in state 9 (MO_TERM_CALL_CONF) <000a> bsc_api.c:404 Sending (bts=0,trx=0,ts=1,ss=1) ChanModify for speech: SPEECH_AMR on channel TCH_H <0003> gsm_04_08_utils.c:512 -> CHANNEL MODE MODIFY mode=0x41 <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=1) SAPI=0 DATA INDICATION <0003> gsm_04_08_utils.c:537 CHANNEL MODE MODIFY ACK <0004> abis_rsl.c:2268 (bts=0,trx=0,ts=1,ss=1) IPAC_BIND speech_mode=0x15 RTP_PAYLOAD=98 <0003> osmo_msc.c:76 MSC assign complete (do nothing). <0004> abis_rsl.c:1608 (bts=0,trx=0,ts=1,ss=1) CHANNEL MODE MODIFY ACK <0004> abis_rsl.c:2449 (bts=0,trx=0,ts=1,ss=1) IPAC_CRCX_ACK LOCAL_IP=127.0.0.1 LOCAL_PORT=52342 CON_ID=0 <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=1) SAPI=0 DATA INDICATION <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=3 <0001> gsm_04_08.c:3894 (bts 0 trx 0 ts 1 ti 0 sub 43926) Received 'ALERTING' from MS in state 9 (MO_TERM_CALL_CONF) <0001> gsm_04_08.c:1665 stopping pending timer T310 <0001> gsm_04_08.c:2226 starting timer T301 with 180 seconds <0001> gsm_04_08.c:1623 new state MO_TERM_CALL_CONF -> CALL_RECEIVED <0001> gsm_04_08.c:1685 (bts 0 trx 0 ts 1 ti 0 sub 43926) Sending 'MNCC_ALERT_IND' to MNCC. <0001> gsm_04_08.c:3796 (bts 0 trx 0 ts 1 ti 08 sub 44680) Received 'MNCC_ALERT_REQ' from MNCC in state 3 (MO_CALL_PROC) <0001> gsm_04_08.c:1623 new state MO_CALL_PROC -> CALL_DELIVERED <0001> gsm_04_08.c:143 (bts 0 trx 0 ts 1 ti 80) Sending 'ALERTING' to MS. <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=1) SAPI=0 DATA INDICATION <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=3 <0001> gsm_04_08.c:3894 (bts 0 trx 0 ts 1 ti 0 sub 43926) Received 'CONNECT' from MS in state 7 (CALL_RECEIVED) <0001> gsm_04_08.c:1665 stopping pending timer T301 <0001> gsm_04_08.c:1623 new state CALL_RECEIVED -> CONNECT_REQUEST <0001> gsm_04_08.c:1685 (bts 0 trx 0 ts 1 ti 0 sub 43926) Sending 'MNCC_SETUP_CNF' to MNCC. <0001> gsm_04_08.c:3796 (bts 0 trx 0 ts 1 ti 00 sub 43926) Received 'MNCC_SETUP_COMPL_REQ' from MNCC in state 8 (CONNECT_REQUEST) <0001> gsm_04_08.c:1623 new state CONNECT_REQUEST -> ACTIVE <0001> gsm_04_08.c:143 (bts 0 trx 0 ts 1 ti 00) Sending 'CONNECT_ACK' to MS. <0001> gsm_04_08.c:3796 (bts 0 trx 0 ts 1 ti 08 sub 44680) Received 'MNCC_SETUP_RSP' from MNCC in state 4 (CALL_DELIVERED) <0001> gsm_04_08.c:2226 starting timer T313 with 30 seconds <0001> gsm_04_08.c:1623 new state CALL_DELIVERED -> CONNECT_IND <0001> gsm_04_08.c:143 (bts 0 trx 0 ts 1 ti 80) Sending 'CONNECT' to MS. <0001> gsm_04_08.c:1939 Setting up TCH map between (bts=0,trx=0,ts=1,TCH_H) and (bts=0,trx=0,ts=1,TCH_H) <0004> abis_rsl.c:2307 (bts=0,trx=0,ts=1,ss=1) IPAC_MDCX IP=127.0.0.1 PORT=30002 RTP_PAYLOAD=98 RTP_PAYLOAD2=0 CONN_ID=0 speech_mode=0x05 <0004> abis_rsl.c:2307 (bts=0,trx=0,ts=1,ss=0) IPAC_MDCX IP=127.0.0.1 PORT=30000 RTP_PAYLOAD=98 RTP_PAYLOAD2=0 CONN_ID=0 speech_mode=0x05 <0004> abis_rsl.c:2459 (bts=0,trx=0,ts=1,ss=1) IPAC_MDCX_ACK LOCAL_IP=127.0.0.1 LOCAL_PORT=52342 CON_ID=0 <0004> abis_rsl.c:2459 (bts=0,trx=0,ts=1,ss=0) IPAC_MDCX_ACK LOCAL_IP=127.0.0.1 LOCAL_PORT=10880 CON_ID=0 <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=0 DATA INDICATION <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=3 <0001> gsm_04_08.c:3894 (bts 0 trx 0 ts 1 ti 8 sub 44680) Received 'CONNECT_ACK' from MS in state 28 (CONNECT_IND) <0001> gsm_04_08.c:1665 stopping pending timer T313 <0001> gsm_04_08.c:1623 new state CONNECT_IND -> ACTIVE <0001> gsm_04_08.c:1685 (bts 0 trx 0 ts 1 ti 8 sub 44680) Sending 'MNCC_SETUP_COMPL_IND' to MNCC. <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=0) SAPI=0 DATA INDICATION <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=3 <0001> gsm_04_08.c:3894 (bts 0 trx 0 ts 1 ti 8 sub 44680) Received 'DISCONNECT' from MS in state 10 (ACTIVE) <0001> gsm_04_08.c:1623 new state ACTIVE -> DISCONNECT_IND <0001> gsm_04_08.c:1685 (bts 0 trx 0 ts 1 ti 8 sub 44680) Sending 'MNCC_DISC_IND' to MNCC. <0001> gsm_04_08.c:3796 (bts 0 trx 0 ts 1 ti 08 sub 44680) Received 'MNCC_REL_REQ' from MNCC in state 12 (DISCONNECT_IND) <0001> gsm_04_08.c:2226 starting timer T308 with 10 seconds <0001> gsm_04_08.c:1623 new state DISCONNECT_IND -> RELEASE_REQ <0001> gsm_04_08.c:143 (bts 0 trx 0 ts 1 ti 80) Sending 'RELEASE' to MS. <0001> gsm_04_08.c:3796 (bts 0 trx 0 ts 1 ti 00 sub 43926) Received 'MNCC_DISC_REQ' from MNCC in state 10 (ACTIVE) <0001> gsm_04_08.c:2226 starting timer T306 with 30 seconds <0001> gsm_04_08.c:1623 new state ACTIVE -> DISCONNECT_IND <0001> gsm_04_08.c:143 (bts 0 trx 0 ts 1 ti 00) Sending 'DISCONNECT' to MS. <0000> abis_rsl.c:2051 (bts=0,trx=0,ts=1,ss=1) SAPI=0 DATA INDICATION <0000> gsm_04_08.c:3999 Dispatching 04.08 message, pdisc=3 <0001> gsm_04_08.c:3894 (bts 0 trx 0 ts 1 ti 0 sub 43926) Received 'DISCONNECT' from MS in state 12 (DISCONNECT_IND) <0001> gsm_04_08.c:1665 stopping pending timer T306 <0001> gsm_04_08.c:1623 new state DISCONNECT_IND -> DISCONNECT_IND <0001> gsm_04_08.c:1685 (bts 0 trx 0 ts 1 ti 0 sub 43926) Sending 'MNCC_DISC_IND' to MNCC. <0001> gsm_04_08.c:3796 (bts 0 trx 0 ts 1 ti 00 sub 43926) Received 'MNCC_REL_REQ' from MNCC in state 12 (DISCONNECT_IND) <0001> gsm_04_08.c:2226 starting timer T308 with 10 seconds <0001> gsm_04_08.c:1623 new state DISCONNECT_IND -> RELEASE_REQ <0001> gsm_04_08.c:143 (bts 0 trx 0 ts 1 ti 00) Sending 'RELEASE' to MS. <0001> gsm_04_08.c:3796 (bts 0 trx 0 ts 1 ti 08 sub 44680) Received 'MNCC_DISC_REQ' from MNCC in state 19 (RELEASE_REQ) <0001> gsm_04_08.c:3804 Message unhandled at this state. <0001> gsm_04_08.c:2226 starting timer T308 with 10 seconds <0001> gsm_04_08.c:143 (bts 0 trx 0 ts 1 ti 80) Sending 'RELEASE' to MS. <0001> gsm_04_08.c:2226 starting timer T308 with 10 seconds <0001> gsm_04_08.c:143 (bts 0 trx 0 ts 1 ti 00) Sending 'RELEASE' to MS. <0001> gsm_04_08.c:1685 (bts 0 trx 0 ts 1 ti 8 sub 44680) Sending 'MNCC_REL_CNF' to MNCC. <0001> gsm_04_08.c:1623 new state RELEASE_REQ -> NULL <0000> chan_alloc.c:486 (bts=0,trx=0,ts=1,ss=0) starting release sequence <0004> abis_rsl.c:1221 (bts=0,trx=0,ts=1,ss=0) state ACTIVE -> RELEASE REQUESTED <0003> gsm_04_08_utils.c:251 Sending Channel Release: Chan: Number: 0 Type: 3 <0004> abis_rsl.c:767 (bts=0,trx=0,ts=1,ss=0) DEACTivate SACCH CMD <0001> gsm_04_08.c:1685 (bts 0 trx 0 ts 1 ti 0 sub 43926) Sending 'MNCC_REL_CNF' to MNCC. <0001> gsm_04_08.c:1623 new state RELEASE_REQ -> NULL <0000> chan_alloc.c:486 (bts=0,trx=0,ts=1,ss=1) starting release sequence <0004> abis_rsl.c:1221 (bts=0,trx=0,ts=1,ss=1) state ACTIVE -> RELEASE REQUESTED <0003> gsm_04_08_utils.c:251 Sending Channel Release: Chan: Number: 1 Type: 3 Meanwhile I will try to collect more debug logs.. P.S. I am doing pure GSM call, w/o SIP. Maybe call from MS to VoIP will be more stable... 2017-05-11 15:59 GMT+03:00 Neels Hofmeyr : > Please, again, no-one should *ever* send image bitmaps of text screenshots > to a > mailing list! > > ~N > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From maurizio.agazzini at gmail.com Thu May 4 11:46:00 2017 From: maurizio.agazzini at gmail.com (Maurizio Agazzini) Date: Thu, 4 May 2017 13:46:00 +0200 Subject: CalypsoBTS + GPRS and SDR suggestion Message-ID: Hi everybody, I'm pretty new to the GSM/UMTS environment and I'm doing some tests. Currently I need to analyze some IoT devices that use 2G network to comunicate via GPRS. I setup CalypsoBTS to work with 2 old motorola c123, I know that isn't the best way to do that, but I would like to have a cheap solution. I got the setup working with a normal phone and the BTS seems to work correctly (using jolly/testing), but from my understanding it support only GSM calls and SMS and GPRS is not implemented into the transceiver. I'm wrong or this part has not been implemented yet? If needed to use a GPRS BTS can you suggest the best cheap SDR to use with OsmoBTS? (I saw BladeRF and LimeSDR but I was unable to understand if they are full supported via OsmoBTS) Thank you in advance. inode -------------- next part -------------- An HTML attachment was scrubbed... URL: From serg at tvman.us Tue May 9 19:44:43 2017 From: serg at tvman.us (Serg l) Date: Tue, 9 May 2017 15:44:43 -0400 Subject: Creating GSM Users Association (GSMUA) In-Reply-To: References: Message-ID: Hi Mychaela, You brought up a tricky subject and I definitely would be interested to hear some feedback from someone who dealt with various government bodies in different countries. Website hosting is the easy part :) Thanks, -Serg On Tue, May 9, 2017 at 11:37 AM, Mychaela Falconia < mychaela.falconia at gmail.com> wrote: > Hello FreeCalypso and Osmocom communities, > > I am in the process of creating an informal organisation representing > the interests of those members of the GSM universe whose interests are > not represented by GSMA etc, and I am inviting you to join me in this > venture. I propose that we name our informal organisation GSMUA, > standing for GSM Users Association, and my vision for this GSMUA is to > be a counter-body (antibody?) to the official GSMA. I just registered > the gsmua.org domain name, but there is no website or mailing list set > up yet. If someone from the Osmocom camp would like to host the > server infrastructure for gsmua.org, I will happily point the DNS to > you, otherwise the FreeCalypso family can host it on our server. > > My vision for GSMUA is to represent the interests of GSM end users > (empowered end users who wish to fully own and control all aspects of > their user equipment while operating on public mobile networks in a > fully spec-compliant manner), small boutique manufacturers of GSM > devices (both MS/user equipment and network infrastructure), small > community network operators and others whose interests are not > represented by GSMA etc, especially in cases where our interests are > in direct conflict with the interests of big players such as giant > device manufacturers, giant commercial network operators and > governments. > > A key goal of GSMUA is to be project-neutral, that is, every person > and every small company belonging to any of the categories listed > above (empowered end user, small boutique device manufacturer, small > community network operator etc) should be fully welcome regardless of > which specific project they are associated with. As of today there > are at least two different projects offering GSM MS implementations > (OsmocomBB and FreeCalypso) and at least two different projects > offering network-side GSM implementations (Osmocom and OpenBTS), and I > hope that this number of available alternatives will continue to grow: > freedom of choice is always a good thing. But at the present time > there exists no neutral soil on which members of different projects > with a common interest (GSM networks and devices serving the interests > of end users rather than big corporations and governments) and a > common enemy (just named) can meet, and this lack of neutral meeting > ground is the problem which GSMUA is meant to solve. > > I also have one practical application for GSMUA in mind already: to > manage and legitimize recycling of wasted IMEI number ranges. By the > official rules of GSMA etc each different *type* of GSM mobile > equipment requires a different TAC, i.e., a range of at least 1 million > IMEI numbers. So if a small boutique GSM device manufacturer makes a > boutique MS device of which no more than 100 units will ever be made, > 999900 IMEI numbers have to be wasted by the official rules. While I > don't know of any manufacturer who got a range of 1 million IMEIs and > only made 100 devices, we do have examples like Openmoko GTA01/02 and > Pirelli DP-L10. In the case of Openmoko GTA02 I've been told that > about 15 thousand units were made in total; in the case of Pirelli > DP-L10 it appears that the total number produced was somewhere under > 100 thousand. In each case a full range of 1 million IMEIs was > allocated, and at least 900 thousand numbers out of each range are > currently unused and wasted. > > If a small boutique manufacturer wishes to offer a boutique GSM MS > product to the general public and wishes to ship each unit with a > world-unique IMEI that stands a good chance of being accepted as valid > by common GSM networks, and the product in question does not qualify > for IMEI allocation by the official rules (e.g., the product is a > development board specifically intended for users to run their own > firmware and connect to live public networks with it, taking full > personal responsibility for their actions) - the situation I found > myself in with my GSM MS development board - I feel that the small > boutique manuf in question should be empowered to squat on a small > subrange of someone else's IMEI range if it is known beyond reasonable > doubt to be wasted and unused. > > However, this recycling of wasted IMEI number ranges could be better > organized and given at least some aura of semi-legitimacy if there > were a community body set up to manage it, and this is where my > proposed GSMUA can come in. Once we get our GSMUA up and running and > assign a group of volunteers to be IMEI recycling managers, any small > GSM or 3G+ device manufacturer who needs a small range of IMEI numbers > will be able to request one from GSMUA, and we will allocate and > assign these small subranges out of whatever wasted range we decide to > squat on, ensuring that each requestor gets a different subrange. > > So these are my ideas, and I would like to see them turn into reality. > We are going to need a simple website and a community mailing list at > gsmua.org, and for the IMEI recycling service we will need a small > group of volunteers to serve as its managers - I and Das Signal from > FreeCalypso will be happy to serve on that panel, but it would be nice > to also have someone from the Osmocom camp for better neutrality. > > Bright Blessings, > Mychaela Falconia, > Mother of FreeCalypso > _______________________________________________ > Community mailing list > Community at freecalypso.org > https://www.freecalypso.org/mailman/listinfo/community > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nhofmeyr at sysmocom.de Mon May 15 16:31:06 2017 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Mon, 15 May 2017 18:31:06 +0200 Subject: Osmocombb as a Zombie In-Reply-To: References: Message-ID: <20170515163106.GC11723@my.box> On Wed, Feb 15, 2017 at 10:02:49PM +0000, Duarte wrote: > (no, I'm not hacking.) In the Osmocom community, I believe "hacking" is meant to churn at a problem / play with technology. IMHO it's a common misunderstanding by the main stream that hacking means breaking into something. Well, but it's the main stream. http://www.catb.org/~esr/jargon/html/H/hack.html http://www.catb.org/~esr/writings/cathedral-bazaar/hacker-history/ In the terms of these texts, I believe Osmocom belongs to the hacker culture. IOW if you're running OsmocomBB, you're most certainly hacking by definition :) (at least by our definition) ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From samir.s.abed at gmail.com Tue May 16 08:05:47 2017 From: samir.s.abed at gmail.com (samir) Date: Tue, 16 May 2017 11:05:47 +0300 Subject: Phone not receiving calls In-Reply-To: References: Message-ID: <37C1E029-3D84-4DD5-86A3-F076CF203771@gmail.com> I need some help at least where I must start. I want to modify the code to fix this problem. On May 9, 2017, at 4:05 PM, robert wrote: > I had the same problem but couldn?t fix it. I guess nothing could be done. > > > On May 6, 2017, at 10:27 AM, samir wrote: > >> Hi, >> >> On May 6, 2017, at 1:33 AM, Vadim Yanitskiy wrote: >> >>> Hi, >>> >>> Don't get me wrong, but your current description sounds like >>> "I have a problem, but I wouldn't say any details about that". >>> Please provide at least mobile application logs, and also try >>> to figure out some things yourself: >>> >>> 1) What is difference between both SIM cards you use? >> both SIM cards are the same (only imsi is different) >> >>> 2) Does mobile with "non-working" SIM perform successful LU? >> Yes, it connects normally and can perform calls and send SMS. >> >>> 3) Does mobile with "non-working" SIM receive any Paging Request? >> No, nothing is received. >> > From axilirator at gmail.com Tue May 16 08:14:14 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Tue, 16 May 2017 11:14:14 +0300 Subject: Phone not receiving calls In-Reply-To: <37C1E029-3D84-4DD5-86A3-F076CF203771@gmail.com> References: <37C1E029-3D84-4DD5-86A3-F076CF203771@gmail.com> Message-ID: Hi, > Please provide at least mobile application logs What are you waiting for? :) With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From samir.s.abed at gmail.com Tue May 16 08:41:50 2017 From: samir.s.abed at gmail.com (samir) Date: Tue, 16 May 2017 11:41:50 +0300 Subject: Phone not receiving calls In-Reply-To: References: <37C1E029-3D84-4DD5-86A3-F076CF203771@gmail.com> Message-ID: <20A0564A-E0E1-4777-93EF-E558FEB7740B@gmail.com> I made some research and tests and found the following: - the mobile can connect normally and to any BTS near it and perform calls and send SMS without any problem. - when I try to call it from another phone, it doesn?t get paged and the operator informs me that the called mobile phone cannot be reached. - it doesn?t receive any SMS. - the only time it can get paged is immediately after it connects to the BTS or right after ending a call. For example if I call a number using the motorola, just after hanging if someone calls the motorola it will receive the call. - I read a little about paging groups so I edited the mobile code to print the value of the time slot, it is always 0 so maybe this is the problem. On May 16, 2017, at 11:14 AM, Vadim Yanitskiy wrote: > Hi, > > > Please provide at least mobile application logs > > What are you waiting for? :) > > With best regards, > Vadim Yanitskiy. From domi at tomcsanyi.net Tue May 16 08:50:22 2017 From: domi at tomcsanyi.net (=?utf-8?B?VG9tY3PDoW55aSwgRG9tb25rb3M=?=) Date: Tue, 16 May 2017 10:50:22 +0200 (CEST) Subject: Phone not receiving calls In-Reply-To: <20A0564A-E0E1-4777-93EF-E558FEB7740B@gmail.com> References: <37C1E029-3D84-4DD5-86A3-F076CF203771@gmail.com> <20A0564A-E0E1-4777-93EF-E558FEB7740B@gmail.com> Message-ID: <8EB4E529-9D36-4648-BE45-54374456FB09@tomcsanyi.net> I'm sorry to step into this, but I couldn't stop myself as this is getting a little bit ridiculous: Please provide exactly the output of the mobile application (the log) in text form (no screenshots please) so we can see what's going on in your setup. Cheers, Domi 2017. m?j. 16. d?tummal, 10:42 id?pontban samir ?rta: > I made some research and tests and found the following: > > - the mobile can connect normally and to any BTS near it and perform calls and send SMS without any problem. > - when I try to call it from another phone, it doesn?t get paged and the operator informs me that the called mobile phone cannot be reached. > - it doesn?t receive any SMS. > - the only time it can get paged is immediately after it connects to the BTS or right after ending a call. For example if I call a number using the motorola, just after hanging if someone calls the motorola it will receive the call. > - I read a little about paging groups so I edited the mobile code to print the value of the time slot, it is always 0 so maybe this is the problem. > > >> On May 16, 2017, at 11:14 AM, Vadim Yanitskiy wrote: >> >> Hi, >> >>> Please provide at least mobile application logs >> >> What are you waiting for? :) >> >> With best regards, >> Vadim Yanitskiy. > From samir.s.abed at gmail.com Tue May 16 09:34:22 2017 From: samir.s.abed at gmail.com (samir) Date: Tue, 16 May 2017 12:34:22 +0300 Subject: Phone not receiving calls In-Reply-To: <8EB4E529-9D36-4648-BE45-54374456FB09@tomcsanyi.net> References: <37C1E029-3D84-4DD5-86A3-F076CF203771@gmail.com> <20A0564A-E0E1-4777-93EF-E558FEB7740B@gmail.com> <8EB4E529-9D36-4648-BE45-54374456FB09@tomcsanyi.net> Message-ID: <25A1A95E-FE77-4724-8E75-FA9015DDB3D3@gmail.com> I connected the phone and tried to call it. The log is attached. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: log.txt URL: -------------- next part -------------- On May 16, 2017, at 11:50 AM, Tomcs?nyi, Domonkos wrote: > I'm sorry to step into this, but I couldn't stop myself as this is getting a little bit ridiculous: > Please provide exactly the output of the mobile application (the log) in text form (no screenshots please) so we can see what's going on in your setup. > > Cheers, > > Domi > > 2017. m?j. 16. d?tummal, 10:42 id?pontban samir ?rta: > >> I made some research and tests and found the following: >> >> - the mobile can connect normally and to any BTS near it and perform calls and send SMS without any problem. >> - when I try to call it from another phone, it doesn?t get paged and the operator informs me that the called mobile phone cannot be reached. >> - it doesn?t receive any SMS. >> - the only time it can get paged is immediately after it connects to the BTS or right after ending a call. For example if I call a number using the motorola, just after hanging if someone calls the motorola it will receive the call. >> - I read a little about paging groups so I edited the mobile code to print the value of the time slot, it is always 0 so maybe this is the problem. >> >> >>> On May 16, 2017, at 11:14 AM, Vadim Yanitskiy wrote: >>> >>> Hi, >>> >>>> Please provide at least mobile application logs >>> >>> What are you waiting for? :) >>> >>> With best regards, >>> Vadim Yanitskiy. >> From laforge at gnumonks.org Tue May 16 16:27:08 2017 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 16 May 2017 18:27:08 +0200 Subject: libosmocore embedded build Message-ID: <20170516162708.fimenn7qgsehu5pp@nataraja> Dear all, when we originally moved a lot of generic code from OpenBSC to libosmo{core,gsm} to re-use it from OsmocomBB, we created an 'embedded' build of libosmocore, which can use [most of] the library code also in deeply embedded, OS-less 'bare metal' microcontroller environments. The ability to build libosmocore this way has been broken for many years, but I've fixed that in recent libosmocore master. Below command works for me [tm]: ./configure --prefix=/usr/local/arm-none-eabi \ --host=arm-none-eabi \ --enable-embedded \ --disable-shared \ CFLAGS="-Os -ffunction-sections -fdata-sections -nostartfiles -nodefaultlibs" What we'd need now is: 1) make sure embedded builds continue to work by building libosmocore for embedded as part of the jenkins setup (using gcc-arm-none-eabi debian package). Any volunteers? 2) start to use this embedded build from simtrace2 firmware, osmocom-bb and the upcoming fimrware for the RFDN[1]. So far, * osmocom-bb uses an old clone of libosmocore, * simtrace2 is using some copy+pasted fork of some libosmocore files * rfdn is using some copy+pasted fork of some libosmocore files The above is no longer required. 3) consider if we can shrink the resource requirements of some libosmocore parts. One issue coming up are the static buffers in osmo_hexdump[] or the like. If your total processor RAM is 8k or 16k, then spending 4k on the buffer for hex-dumping is indeed a bit excessive. Any help is appreciated, particularly on the jenkins side. Regards, Harald [1] (1:8 splitter-combiner with adjustible step attenuators, part of the osmo-gsm-tester setup we're building at sysmocom). Code will be released as soon as the hardware is validated. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Tue May 16 16:18:45 2017 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 16 May 2017 18:18:45 +0200 Subject: removing ancient libosmocore fork from osmocom-bb.git Message-ID: <20170516161845.p5fvmrpizqmjogju@nataraja> Dear all, when we initially crated OsmocomBB, we moved the code that it shared with the pre-existing OpenBSC project into libosmocore.git, where libosmocore and libosmogsm are built. As libosmocore was quite a bit in flux (and we didn't have jenkins+gerrit yet), we decided to have a local clone of libosmocore.git as a git-subtree module inside osmocom-bb.git Meanwhile, upstream libosmocore received more and more code, and none of that was ever built with an 'arm-non-eabi' toolchain and --enable-embedded. I've been working quite a bit during the last week on making that embedded build work again. The idea is to be able to configure + build libosmocore.git master using something like ./configure --prefix=/usr/local/arm-none-eabi \ --host=arm-none-eabi \ --enable-embedded \ --disable-shared \ CFLAGS="-Os -ffunction-sections -fdata-sections -nostartfiles -nodefaultlibs" and then install it onto the host pc. I've used /usr/local/arm-none-eabi as the prefix, but it could of course be anywhere. The above already works for me on Debian unstable using libosmocore.git master. I have some patches pending in laforge/sercomm and laforge/pseudotalloc, but those are not mandatory to make the build work The local clone of libosmocore in OsmocomBB src/shared/libosmocore will be removed, and the Makefiles of osmocom-bb instructed to use the system-installed libosmocore from /usr/local/arm-none-eabi (see my 'laforge/remove-libosmocore' branch in). This also already "works" on my Debian unstable system, in as far as there are no unresolved symbols or other compilation/linking issues, and the firmware images are generated. I have not tested any of the resulting binaries yet, and as I'm travelling without compatible hardware (and overloaded), it's unlikely that I'll be able to test it soon. Nevertheless, this is what I would like to move to. If anyone wants to try if he can build the embedded libosmocore and resulting osmocom-bb from laforge/remove-libosmocore branch, please do so and report your progress/success/issues here. Next steps (after validating the above) are: * remove old sercomm.c code from osmocom-bb and use the new code from libosmocore * remove 'talloc emulation' from osmocom-bb and use pseudotalloc from libosmocore.git (plus an embedded 'malloc' like umm_malloc) Further ideas: * create Debian/Ubuntu package of cross-compiled libosmocore for embedded-arm, which we can add to the Osmocom nightly builds apt repository. * have an (optional?) osmocom-bb makefile step to git clone + configure + make install libosmocore Anyone interested in helping out with this, please feel free to join in. 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 craig_comstock at yahoo.com Wed May 17 00:19:24 2017 From: craig_comstock at yahoo.com (Craig Comstock) Date: Tue, 16 May 2017 19:19:24 -0500 Subject: removing ancient libosmocore fork from osmocom-bb.git In-Reply-To: <20170516161845.p5fvmrpizqmjogju@nataraja> References: <20170516161845.p5fvmrpizqmjogju@nataraja> Message-ID: I will try this on Debian stable. On May 16, 2017 11:18:45 AM CDT, Harald Welte wrote: >Dear all, > >when we initially crated OsmocomBB, we moved the code that it shared >with the pre-existing OpenBSC project into libosmocore.git, where >libosmocore and libosmogsm are built. As libosmocore was quite a bit >in >flux (and we didn't have jenkins+gerrit yet), we decided to have a >local >clone of libosmocore.git as a git-subtree module inside osmocom-bb.git > >Meanwhile, upstream libosmocore received more and more code, and none >of that was ever built with an 'arm-non-eabi' toolchain and >--enable-embedded. > >I've been working quite a bit during the last week on making that >embedded build work again. > >The idea is to be able to configure + build libosmocore.git master >using >something like > >./configure --prefix=/usr/local/arm-none-eabi \ > --host=arm-none-eabi \ > --enable-embedded \ > --disable-shared \ > CFLAGS="-Os -ffunction-sections -fdata-sections -nostartfiles >-nodefaultlibs" > >and then install it onto the host pc. I've used >/usr/local/arm-none-eabi as the prefix, but it could of course be >anywhere. > >The above already works for me on Debian unstable using libosmocore.git >master. I have some patches pending in laforge/sercomm and >laforge/pseudotalloc, but those are not mandatory to make the build >work > >The local clone of libosmocore in OsmocomBB src/shared/libosmocore will >be removed, and the Makefiles of osmocom-bb instructed to use the >system-installed libosmocore from /usr/local/arm-none-eabi (see my >'laforge/remove-libosmocore' branch in). This also already "works" on >my Debian unstable system, in as far as there are no unresolved symbols >or other compilation/linking issues, and the firmware images are >generated. I have not tested any of the resulting binaries yet, and as >I'm travelling without compatible hardware (and overloaded), it's >unlikely that I'll be able to test it soon. > >Nevertheless, this is what I would like to move to. If anyone wants to >try if he can build the embedded libosmocore and resulting osmocom-bb >from laforge/remove-libosmocore branch, please do so and report your >progress/success/issues here. > >Next steps (after validating the above) are: >* remove old sercomm.c code from osmocom-bb and use the new code from > libosmocore >* remove 'talloc emulation' from osmocom-bb and use pseudotalloc from > libosmocore.git (plus an embedded 'malloc' like umm_malloc) > >Further ideas: >* create Debian/Ubuntu package of cross-compiled libosmocore for > embedded-arm, which we can add to the Osmocom nightly builds apt > repository. >* have an (optional?) osmocom-bb makefile step to git clone + configure > + make install libosmocore > >Anyone interested in helping out with this, please feel free to join >in. > >Regards, > Harald >-- >- Harald Welte >http://laforge.gnumonks.org/ >============================================================================ >"Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6) -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From craig_comstock at yahoo.com Wed May 17 02:12:54 2017 From: craig_comstock at yahoo.com (Craig Comstock) Date: Wed, 17 May 2017 02:12:54 +0000 (UTC) Subject: removing ancient libosmocore fork from osmocom-bb.git References: <288539054.745564.1494987174366.ref@mail.yahoo.com> Message-ID: <288539054.745564.1494987174366@mail.yahoo.com> Looks like in package libnewlib-dev for stretch (unstable) we have sys/select.h but in jessie (stable) it is not included. https://packages.debian.org/stretch/libnewlib-dev https://packages.debian.org/jessie/libnewlib-dev craig at box:~/libosmocore$ ./configure --prefix=/usr/local/arm-none-eabi --host=arm-none-eabi --enable-embedded --disable-shared CFLAGS="-Os -ffunction-sections -fdata-sections -nostartfiles -nodefaultlibs" craig at box:~/libosmocore$ make make all-recursive make[1]: Entering directory '/home/craig/libosmocore' Making all in include make[2]: Entering directory '/home/craig/libosmocore/include' make all-am make[3]: Entering directory '/home/craig/libosmocore/include' make[3]: Nothing to be done for 'all-am'. make[3]: Leaving directory '/home/craig/libosmocore/include' make[2]: Leaving directory '/home/craig/libosmocore/include' Making all in src make[2]: Entering directory '/home/craig/libosmocore/src' make all-am make[3]: Entering directory '/home/craig/libosmocore/src' CC select.lo select.c:27:24: fatal error: sys/select.h: No such file or directory #include ^ compilation terminated. Makefile:510: recipe for target 'select.lo' failed make[3]: *** [select.lo] Error 1 make[3]: Leaving directory '/home/craig/libosmocore/src' Makefile:373: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/home/craig/libosmocore/src' Makefile:519: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/craig/libosmocore' Makefile:382: recipe for target 'all' failed make: *** [all] Error 2 -------------------------------------------- On Tue, 5/16/17, Harald Welte wrote: Subject: removing ancient libosmocore fork from osmocom-bb.git To: baseband-devel at lists.osmocom.org Date: Tuesday, May 16, 2017, 11:18 AM Dear all, when we initially crated OsmocomBB, we moved the code that it shared with the pre-existing OpenBSC project into libosmocore.git, where libosmocore and libosmogsm are built.? As libosmocore was quite a bit in flux (and we didn't have jenkins+gerrit yet), we decided to have a local clone of libosmocore.git as a git-subtree module inside osmocom-bb.git Meanwhile, upstream libosmocore received more and more code, and none of that was ever built with an 'arm-non-eabi' toolchain and --enable-embedded. I've been working quite a bit during the last week on making that embedded build work again. The idea is to be able to configure + build libosmocore.git master using something like ./configure??? --prefix=/usr/local/arm-none-eabi \ ??? ??? --host=arm-none-eabi \ ??? ??? --enable-embedded \ ??? ??? --disable-shared \ ??? ??? CFLAGS="-Os -ffunction-sections -fdata-sections -nostartfiles -nodefaultlibs" and then install it onto the host pc.? I've used /usr/local/arm-none-eabi as the prefix, but it could of course be anywhere. The above already works for me on Debian unstable using libosmocore.git master. I have some patches pending in laforge/sercomm and laforge/pseudotalloc, but those are not mandatory to make the build work The local clone of libosmocore in OsmocomBB src/shared/libosmocore will be removed, and the Makefiles of osmocom-bb instructed to use the system-installed libosmocore from /usr/local/arm-none-eabi (see my 'laforge/remove-libosmocore' branch in).? This also already "works" on my Debian unstable system, in as far as there are no unresolved symbols or other compilation/linking issues, and the firmware images are generated.? I have not tested any of the resulting binaries yet, and as I'm travelling without compatible hardware (and overloaded), it's unlikely that I'll be able to test it soon. Nevertheless, this is what I would like to move to.? If anyone wants to try if he can build the embedded libosmocore and resulting osmocom-bb from laforge/remove-libosmocore branch, please do so and report your progress/success/issues here. Next steps (after validating the above) are: * remove old sercomm.c code from osmocom-bb and use the new code from ? libosmocore * remove 'talloc emulation' from osmocom-bb and use pseudotalloc from ? libosmocore.git (plus an embedded 'malloc' like umm_malloc) Further ideas: * create Debian/Ubuntu package of cross-compiled libosmocore for ? embedded-arm, which we can add to the Osmocom nightly builds apt ? repository. * have an (optional?) osmocom-bb makefile step to git clone + configure ? + make install libosmocore Anyone interested in helping out with this, please feel free to join in. 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 dr.blobb at gmail.com Wed May 17 09:51:02 2017 From: dr.blobb at gmail.com (=?UTF-8?Q?Andr=C3=A9_Boddenberg?=) Date: Wed, 17 May 2017 11:51:02 +0200 Subject: libosmocore embedded build In-Reply-To: <20170516162708.fimenn7qgsehu5pp@nataraja> References: <20170516162708.fimenn7qgsehu5pp@nataraja> Message-ID: Hi all, >> 1) make sure embedded builds continue to work by building libosmocore >> for embedded as part of the jenkins setup (using gcc-arm-none-eabi >> debian package). Any volunteers? Here, I'd like to do this. Afaics we need some modifications in libosmocore/contrib/jenkins.sh or an additional libosmocore/contrib/jenkins-arm-none-eabi.sh script to build the arm-none-eabi flavor. Any preferences? I have sufficient permission to create a test job on Jenkins. to verify that the build slave (gcc-arm-none-eabi) can build libosmocore with changed ./configure invokation. In case of missing dependencies on the build slave I'd reach out do you. But before starting, I need some clarification about the changed arguments of ./configure invokation, because: >> Below command works for me [tm]: >> ./configure --prefix=/usr/local/arm-none-eabi \ >> --host=arm-none-eabi \ >> --enable-embedded \ >> --disable-shared \ >> CFLAGS="-Os -ffunction-sections -fdata-sections -nostartfiles -nodefaultlibs" does only succeed when adding "--enable-static" to the arguments. Can I simply add "--enable-static" or is my build environment not sane? If not how can I fix it? Regards, Andr? From axilirator at gmail.com Wed May 17 10:47:22 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Wed, 17 May 2017 13:47:22 +0300 Subject: removing ancient libosmocore fork from osmocom-bb.git Message-ID: Hi Harald and Craig, > select.c:27:24: fatal error: sys/select.h: No such file or directory > #include I have the same issue with: gcc-arm-none-eabi 4.8.2-14ubuntu1+6 binutils-arm-none-eabi 2.24-2ubuntu2+4 libnewlib-arm-none-eabi 2.1.0-3 > * remove 'talloc emulation' from osmocom-bb and use pseudotalloc from > libosmocore.git (plus an embedded 'malloc' like umm_malloc) Why do we need this hack (pseudotalloc)? What if we could cross-compile libtalloc too, and link it against core? > * have an (optional?) osmocom-bb makefile step to git clone + configure > + make install libosmocore Great idea! What about to have libosmocore as a git submodule inside OsmocomBB (like OpenCL headers in hashcat)? Also, I think it would be good to make libosmocore more modular, because it could allow us to create more flexible builds (e.g. to compile only what we need, not a whole library). This makes sense in case of low RAM / ROM embedded systems. What do you think? With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From craig_comstock at yahoo.com Wed May 17 12:13:42 2017 From: craig_comstock at yahoo.com (Craig Comstock) Date: Wed, 17 May 2017 12:13:42 +0000 (UTC) Subject: removing ancient libosmocore fork from osmocom-bb.git References: <625437386.1176565.1495023222032.ref@mail.yahoo.com> Message-ID: <625437386.1176565.1495023222032@mail.yahoo.com> I got around this error by adding a #if (!EMBEDDED) around all of select.c and moving the #include "../config.h" to the top. diff --git a/src/select.c b/src/select.c index 8ed7f1b..e51e50a 100644 --- a/src/select.c +++ b/src/select.c @@ -20,6 +20,8 @@ * MA 02110-1301, USA. */ +#include "../config.h" +#if (!EMBEDDED) #include #include #include @@ -30,7 +32,6 @@ #include #include -#include "../config.h" #ifdef HAVE_SYS_SELECT_H @@ -235,3 +236,4 @@ struct osmo_fd *osmo_fd_get_by_fd(int fd) /*! @} */ #endif /* _HAVE_SYS_SELECT_H */ +#endif /* !EMBEDDED */ After that the next error in building is related to talloc. make[3]: Entering directory '/home/craig/libosmocore/src' CC select.lo CC utils.lo In file included from ../include/osmocom/core/utils.h:4:0, from utils.c:30: ../include/osmocom/core/talloc.h:4:20: fatal error: talloc.h: No such file or directory #include I didn't see the laforge/pseudotalloc branch. Did you forget to push it? How is this dealt with currently in osmocom-bb for embedded? Thanks, Craig From laforge at gnumonks.org Wed May 17 14:08:10 2017 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 17 May 2017 15:08:10 +0100 Subject: removing ancient libosmocore fork from osmocom-bb.git In-Reply-To: References: Message-ID: <20170517140810.mgzvmll3wdebppp6@nataraja> Hi Vadim, On Wed, May 17, 2017 at 01:47:22PM +0300, Vadim Yanitskiy wrote: > Hi Harald and Craig, > > > select.c:27:24: fatal error: sys/select.h: No such file or directory > > #include > > I have the same issue with: > > gcc-arm-none-eabi 4.8.2-14ubuntu1+6 > binutils-arm-none-eabi 2.24-2ubuntu2+4 > libnewlib-arm-none-eabi 2.1.0-3 Ok, so I'll have some homework to check build in a Debian stable VM and make that work. Will let you know once I'm done with that. > > * remove 'talloc emulation' from osmocom-bb and use pseudotalloc from > > libosmocore.git (plus an embedded 'malloc' like umm_malloc) > > Why do we need this hack (pseudotalloc)? Because talloc is large both in terms of runtime memory overhead (for each allocation) and in terms of code footprint,. > What if we could cross-compile libtalloc too, and link it against core? That's possible, but we're talking about microcontrollers with something like 16kBytes of RAM in total, or maybe less. You cannot afford that amount of overhead. > > * have an (optional?) osmocom-bb makefile step to git clone + configure > > + make install libosmocore > > Great idea! What about to have libosmocore as a git submodule inside > OsmocomBB (like OpenCL headers in hashcat)? I'm not sure if we'd want that. I haven't really worked much with submodules yet, though, so my position is not a strong one here. > Also, I think it would be good to make libosmocore more modular, > because it could allow us to create more flexible builds (e.g. to compile > only what we need, not a whole library). This makes sense in case of > low RAM / ROM embedded systems. What do you think? linking statically with -ffunction-sections and -fdata-sections will result the linker in garbage collecting (removing) any functions that are not used. So I don't think there is any need for a more modular library, to be honest. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Wed May 17 14:03:05 2017 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 17 May 2017 15:03:05 +0100 Subject: libosmocore embedded build In-Reply-To: References: <20170516162708.fimenn7qgsehu5pp@nataraja> Message-ID: <20170517140305.iaoflv4pczt3o6a4@nataraja> Hi Andre, On Wed, May 17, 2017 at 11:51:02AM +0200, Andr? Boddenberg wrote: > >> 1) make sure embedded builds continue to work by building libosmocore > >> for embedded as part of the jenkins setup (using gcc-arm-none-eabi > >> debian package). Any volunteers? > > Here, I'd like to do this. great! > Afaics we need some modifications in libosmocore/contrib/jenkins.sh or > an additional libosmocore/contrib/jenkins-arm-none-eabi.sh script to > build the arm-none-eabi flavor. Any preferences? I don't know anything about the jenkins setup, so I defer here to the people more familiar with it. > I have sufficient permission to create a test job on Jenkins. to > verify that the build slave (gcc-arm-none-eabi) can > build libosmocore with changed ./configure invokation. In case of > missing dependencies on the build slave I'd reach out do you. sure, thanks. > But before starting, I need some clarification about the changed > arguments of ./configure invokation, because: > > >> Below command works for me [tm]: > >> ./configure --prefix=/usr/local/arm-none-eabi \ > >> --host=arm-none-eabi \ > >> --enable-embedded \ > >> --disable-shared \ > >> CFLAGS="-Os -ffunction-sections -fdata-sections -nostartfiles -nodefaultlibs" > > does only succeed when adding "--enable-static" to the arguments. '--enable-static' will just enable the linking/generation of a static library. It will not disable the dynamic library and do any of the other things. > Can I simply add "--enable-static" or is my build environment not > sane? If not how can I fix it? Ah, I think now I understand. You're saying that the above command quoted from my mail only works if you _also_ add --enable-static? This is interesting, but yes you can simply add it. We could also change the configure.ac to add the --disable-shared and --enable-static automatically when using '--enable-embedded'. We coul dalso do the same for the CFLAGS, as they should be the same for whatever embedded microcontroller one would want to build for. The --host and --prefix should not have any default values, though, and should always be specified by the caller. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From holger at freyther.de Wed May 17 15:00:06 2017 From: holger at freyther.de (Holger Freyther) Date: Wed, 17 May 2017 23:00:06 +0800 Subject: removing ancient libosmocore fork from osmocom-bb.git In-Reply-To: <20170517140810.mgzvmll3wdebppp6@nataraja> References: <20170517140810.mgzvmll3wdebppp6@nataraja> Message-ID: <47447D57-BBE7-4256-97F1-A64747FF9C30@freyther.de> > On 17. May 2017, at 22:08, Harald Welte wrote: > > Hi Vadim, > Hey, >>> * remove 'talloc emulation' from osmocom-bb and use pseudotalloc from >>> libosmocore.git (plus an embedded 'malloc' like umm_malloc) >> >> Why do we need this hack (pseudotalloc)? > > Because talloc is large both in terms of runtime memory overhead (for > each allocation) and in terms of code footprint,. related to that. How confident are you we don't rely on the hierarchical feature of talloc inside the libosmo* (or your more narrow list)? Maybe we add some kind of runtime test/probe for that? holger From nhofmeyr at sysmocom.de Wed May 17 16:06:02 2017 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 17 May 2017 18:06:02 +0200 Subject: libosmocore embedded build In-Reply-To: <20170516162708.fimenn7qgsehu5pp@nataraja> References: <20170516162708.fimenn7qgsehu5pp@nataraja> Message-ID: <20170517160602.GA21386@my.box> On Tue, May 16, 2017 at 06:27:08PM +0200, Harald Welte wrote: > 1) make sure embedded builds continue to work by building libosmocore > for embedded as part of the jenkins setup (using gcc-arm-none-eabi > debian package). Any volunteers? For the jenkins side, it's probably easiest for me to add it, unless Holger jumps in. About the cross-compile, do we have a doc or readme that describes it? ~N -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Wed May 17 16:15:59 2017 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 17 May 2017 18:15:59 +0200 Subject: libosmocore embedded build In-Reply-To: References: <20170516162708.fimenn7qgsehu5pp@nataraja> Message-ID: <20170517161559.GC21386@my.box> On Wed, May 17, 2017 at 11:51:02AM +0200, Andr? Boddenberg wrote: > Hi all, > > >> 1) make sure embedded builds continue to work by building libosmocore > >> for embedded as part of the jenkins setup (using gcc-arm-none-eabi > >> debian package). Any volunteers? > > Here, I'd like to do this. Afaics we need some modifications in oof, I replied before reading the rest of the thread. Andr?, please go ahead, I have enough on my todo list. Let me know of anything that needs to be installed or configured in our jenkins! (BTW, I kind of lost track of the status on our builds re-using previous build artifacts, feel free to bump on that... would be nice to get this into "production") ~N -- - Neels Hofmeyr http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Gesch?ftsf?hrer / Managing Directors: Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From nhofmeyr at sysmocom.de Wed May 17 16:18:40 2017 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Wed, 17 May 2017 18:18:40 +0200 Subject: libosmocore embedded build In-Reply-To: <20170517140305.iaoflv4pczt3o6a4@nataraja> References: <20170516162708.fimenn7qgsehu5pp@nataraja> <20170517140305.iaoflv4pczt3o6a4@nataraja> Message-ID: <20170517161840.GD21386@my.box> On Wed, May 17, 2017 at 03:03:05PM +0100, Harald Welte wrote: > > Afaics we need some modifications in libosmocore/contrib/jenkins.sh or > > an additional libosmocore/contrib/jenkins-arm-none-eabi.sh script to > > build the arm-none-eabi flavor. Any preferences? Let's have a separate script. We can then decide per-job or per-build-slave which parts we'd like to build. ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From laforge at gnumonks.org Wed May 17 17:44:05 2017 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 17 May 2017 18:44:05 +0100 Subject: removing ancient libosmocore fork from osmocom-bb.git In-Reply-To: <47447D57-BBE7-4256-97F1-A64747FF9C30@freyther.de> References: <20170517140810.mgzvmll3wdebppp6@nataraja> <47447D57-BBE7-4256-97F1-A64747FF9C30@freyther.de> Message-ID: <20170517174405.fg6vgynkhammbtfl@nataraja> Hi Holger, On Wed, May 17, 2017 at 11:00:06PM +0800, Holger Freyther wrote: > >>> * remove 'talloc emulation' from osmocom-bb and use pseudotalloc from > >>> libosmocore.git (plus an embedded 'malloc' like umm_malloc) > >> > >> Why do we need this hack (pseudotalloc)? > > > > Because talloc is large both in terms of runtime memory overhead (for > > each allocation) and in terms of code footprint,. > > related to that. How confident are you we don't rely on the hierarchical > feature of talloc inside the libosmo* (or your more narrow list)? Not libosmo* in general, but just libosmo{core,gsm,dsp,crypt,codec}. However, I think we already use it in some places, although I don't think we *rely* on it). So e.g. in osmo_fsm if you allocate child fsm's from a parent, the children get the parent as context. However, the fsm code itself doesn't rely on automatic free()ing of children. There are also other features like a destructor callback which we don't use anywhere AFAIK. > Maybe we add some kind of runtime test/probe for that? That could be an idea, but then that would come as a runtime overhead on the non-embedded builds? I think it's not really something to worry too much about it, given that memory leaks in tiny embedded microcontrollers are found *very* quickly. If there was a leak of some sort, chances are high that you catch it already after a handful of allocations due to OOM. It's also questionable whether some of the more complex constructs like FSMs are going to be used in such environments to begin with. I think even the logging system in its current form might want some simplification if we want to use it there. Also, the timers could do without rb-tree to reduce code footprint, ... Yes, it's not nice to have that kind of possibillity for hidden errors, but at least I'm happy with it, and there are not too many people working on simtrace and related firmware anyway... -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From dr.blobb at gmail.com Thu May 18 10:08:08 2017 From: dr.blobb at gmail.com (=?UTF-8?Q?Andr=C3=A9_Boddenberg?=) Date: Thu, 18 May 2017 12:08:08 +0200 Subject: libosmocore embedded build In-Reply-To: <20170517161840.GD21386@my.box> References: <20170516162708.fimenn7qgsehu5pp@nataraja> <20170517140305.iaoflv4pczt3o6a4@nataraja> <20170517161840.GD21386@my.box> Message-ID: Hi all, a test job for the libosmocore arm-none-eabi build is created [1]. Another multi-configuration axis (arch) has been added and a combination filter has been applied to not run arm builds on FreeBSD. Do we actually want to cross-compile on FreeBSD as well? The arm build does not succeed (yet) [2]. Can someone else may have a quick look at log [2] to point me in the right direction? Afaics build dependencies are available but the compilation itself fails. OT: the debian8_amd64 build [3] publishes XML test results. :) Regards, Andr? [1] https://jenkins.osmocom.org/jenkins/job/TEST_libosmocore_arm_none_eabi/ [2] https://jenkins.osmocom.org/jenkins/job/TEST_libosmocore_arm_none_eabi/arch=arm-none-eabi,label=linux_amd64_debian8/10/console [3] https://jenkins.osmocom.org/jenkins/job/TEST_libosmocore_arm_none_eabi/arch=amd64,label=linux_amd64_debian8/ From craig_comstock at yahoo.com Thu May 18 15:42:01 2017 From: craig_comstock at yahoo.com (Craig Comstock) Date: Thu, 18 May 2017 15:42:01 +0000 (UTC) Subject: libosmocore embedded build References: <523878719.609260.1495122121893.ref@mail.yahoo.com> Message-ID: <523878719.609260.1495122121893@mail.yahoo.com> > Can someone else may have a > quick look at log [2] to point me in the > right direction? Afaics build dependencies are > available but the > compilation itself > fails. > [2] https://jenkins.osmocom.org/jenkins/job/TEST_libosmocore_arm_none_eabi/arch=arm-none-eabi,label=linux_amd64_debian8/10/console Looks like the tests are failing. My build seems to work but when I run "make check-am" in tests I get a different error related to talloc. This is on a Debian 8 stable box using arm-none-eabi and newlib from debian packages. Maybe the make of timer_test fails and doesn't log somehow? I"m not sure. craig at z500:~/libosmocore/tests$ vi timer/timer_test. timer_test.c timer_test.ok craig at z500:~/libosmocore/tests$ vi timer/timer_test.c craig at z500:~/libosmocore/tests$ make check-am make timer/timer_test sms/sms_test ussd/ussd_test smscb/smscb_test bits/bitrev_test a5/a5_test conv/conv_test auth/milenage_test lapd/lapd_test gsm0808/gsm0808_test gsm0408/gsm0408_test gb/bssgp_fc_test gb/gprs_bssgp_test gb/gprs_ns_test gprs/gprs_test kasumi/kasumi_test gea/gea_test logging/logging_test fr/fr_test codec/codec_test loggingrb/loggingrb_test strrb/strrb_test vty/vty_test comp128/comp128_test utils/utils_test smscb/gsm0341_test stats/stats_test ctrl/ctrl_test bitvec/bitvec_test msgb/msgb_test bits/bitcomp_test tlv/tlv_test gsup/gsup_test oap/oap_test fsm/fsm_test write_queue/wqueue_test socket/socket_test coding/coding_test conv/conv_gsm0503_test abis/abis_test endian/endian_test sercomm/sercomm_test make[1]: Entering directory '/home/craig/libosmocore/tests' CC timer/timer_test.o In file included from timer/timer_test.c:31:0: ../include/osmocom/core/talloc.h:4:20: fatal error: talloc.h: No such file or directory #include ^ compilation terminated. Makefile:1336: recipe for target 'timer/timer_test.o' failed make[1]: *** [timer/timer_test.o] Error 1 make[1]: Leaving directory '/home/craig/libosmocore/tests' Makefile:1529: recipe for target 'check-am' failed make: *** [check-am] Error 2 From laforge at gnumonks.org Thu May 18 10:54:01 2017 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 18 May 2017 11:54:01 +0100 Subject: libosmocore embedded build In-Reply-To: References: <20170516162708.fimenn7qgsehu5pp@nataraja> <20170517140305.iaoflv4pczt3o6a4@nataraja> <20170517161840.GD21386@my.box> Message-ID: <20170518105401.y5qrxx6fytvlkmm7@nataraja> Hi Andre! On Thu, May 18, 2017 at 12:08:08PM +0200, Andr? Boddenberg wrote: > a test job for the libosmocore arm-none-eabi build is created [1]. > Another multi-configuration axis (arch) has been added and a > combination filter has been applied to not run arm builds on FreeBSD. great. > Do we actually want to cross-compile on FreeBSD as well? no. > The arm build does not succeed (yet) [2]. > > Can someone else may have a quick look at log [2] to point me in the > right direction? Afaics build dependencies are available but the > compilation itself fails. The build completes, but 'make check' fails. I think 'make check' does only make sense for host builds, but not for embedded. We cannot execute the test cases anyway, even if we were able to build them. I cannot fix it right now in the autoconf (i.e. do nothing for 'make check'), so feel free to disable 'make check' in the build script as an interim workaround. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Thu May 18 18:24:30 2017 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 18 May 2017 19:24:30 +0100 Subject: OsmocomBB compile testing / Re: libosmocore embedded build In-Reply-To: References: <20170516162708.fimenn7qgsehu5pp@nataraja> <20170517140305.iaoflv4pczt3o6a4@nataraja> <20170517161840.GD21386@my.box> Message-ID: <20170518182430.g6jtc3ib54hwnhuy@nataraja> Hi Andre and others. We currently have a series of patches from Vadim pending in gerrit for OsmocomBB. They cannot move ahead, as we have no compile testing / jenkins job which would give this a +1. To resolve this, we should also start to have a jenkins compile testing job for OsmocomBB. The "host" (PC) part of the code is built against regular libosmocore, just like e.g. openbsc or osmo-bts. That should be possible even so far, and it might make sense to start with that. Basically you need to: * git clone osmocom-bb * cd src/host/layer23 * regular 'autoreconf -fi && ./configure && make' compile-testing the 'embedded' (firmware) part is not possible easily in the current master. However, as a second step, and after the libosmocore embedded build has run (and it is installed to /usr/local/arm-none-eabi), and if you use the laforge/remove-libosmocore branch in OsmocomBB, you should also be able to compile-test the firmware using * git clone osmocom-bb * cd src/target/firmware && make There currently is no "make check" tests for either the host utilities or the firmware, and of course we have no clue if the resulting binaries will do anything useful on an actual pone [yet!], but I still think the two steps above would be very useful to move ahead, and to unify the patch submission/review/verification/approval/merge process in gerrit with what we have established for the network-side projects like OsmoBTS & co. 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 craig_comstock at yahoo.com Thu May 18 18:48:06 2017 From: craig_comstock at yahoo.com (Craig Comstock) Date: Thu, 18 May 2017 18:48:06 +0000 (UTC) Subject: OsmocomBB compile testing / Re: libosmocore embedded build References: <678000730.767348.1495133286217.ref@mail.yahoo.com> Message-ID: <678000730.767348.1495133286217@mail.yahoo.com> I was thinking about how to setup an automated real device test for the repo and/or PRs especially. I have devices and cables, just was thinking about how to automate the re-loading of firmware (via an interface to the power button I suppose). Any work ongoing on this front? I'd be happy to contribute as I have a server I'm going to use for nano3g, calypsobts, development. -Craig -------------------------------------------- On Thu, 5/18/17, Harald Welte wrote: Subject: OsmocomBB compile testing / Re: libosmocore embedded build To: "Andr? Boddenberg" Cc: baseband-devel at lists.osmocom.org, "OpenBSC" , "Vadim Yanitskiy" Date: Thursday, May 18, 2017, 1:24 PM Hi Andre and others. We currently have a series of patches from Vadim pending in gerrit for OsmocomBB.? They cannot move ahead, as we have no compile testing / jenkins job which would give this a +1. To resolve this, we should also start to have a jenkins compile testing job for OsmocomBB.? The "host" (PC) part of the code is built against regular libosmocore, just like e.g. openbsc or osmo-bts.? That should be possible even so far, and it might make sense to start with that. Basically you need to: * git clone osmocom-bb * cd src/host/layer23 * regular 'autoreconf -fi && ./configure && make' compile-testing the 'embedded' (firmware) part is not possible easily in the current master.? However, as a second step, and after the libosmocore embedded build has run (and it is installed to /usr/local/arm-none-eabi), and if you use the laforge/remove-libosmocore branch in OsmocomBB, you should also be able to compile-test the firmware using * git clone osmocom-bb * cd src/target/firmware && make There currently is no "make check" tests for either the host utilities or the firmware, and of course we have no clue if the resulting binaries will do anything useful on an actual pone [yet!], but I still think the two steps above would be very useful to move ahead, and to unify the patch submission/review/verification/approval/merge process in gerrit with what we have established for the network-side projects like OsmoBTS & co. 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 axilirator at gmail.com Thu May 18 21:13:20 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Fri, 19 May 2017 00:13:20 +0300 Subject: libosmocore embedded build Message-ID: Hi, > The arm build does not succeed (yet) [2]. > > Can someone else may have a quick look at log [2] to point me in the > right direction? Afaics build dependencies are available but the > compilation itself fails. As I can see from the console output, build fails because we are trying to test disabled features, which we haven't compiled. Fixed by fixeria ;) https://gerrit.osmocom.org/#/c/2682/1 With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dr.blobb at gmail.com Fri May 19 09:57:45 2017 From: dr.blobb at gmail.com (=?UTF-8?Q?Andr=C3=A9_Boddenberg?=) Date: Fri, 19 May 2017 11:57:45 +0200 Subject: libosmocore embedded build In-Reply-To: <20170518105401.y5qrxx6fytvlkmm7@nataraja> References: <20170516162708.fimenn7qgsehu5pp@nataraja> <20170517140305.iaoflv4pczt3o6a4@nataraja> <20170517161840.GD21386@my.box> <20170518105401.y5qrxx6fytvlkmm7@nataraja> Message-ID: Hi Harald, thanks a lot for your clarification. The "make check" and "make distcheck"[1] have been disabled as an interim workaround. Now, all multi-configuration axes (FreeBSD_amd64, debian8_amd64, arm-none-eabi) are successful. [2] If the build job is "sane" for everyone(?), I'd push the jenkins-arm-none-eabi.sh build script to gerrit for review and apply changes to libosmocore and libosmocore_gerrit job after a successful patch submission. Does everyone agree? Regards, Andr? [1] http://jenkins.osmocom.org/jenkins/job/TEST_libosmocore_arm_none_eabi/arch=arm-none-eabi,label=linux_amd64_debian8/12/console [2] http://jenkins.osmocom.org/jenkins/job/TEST_libosmocore_arm_none_eabi/ From dr.blobb at gmail.com Wed May 24 12:59:22 2017 From: dr.blobb at gmail.com (=?UTF-8?Q?Andr=C3=A9_Boddenberg?=) Date: Wed, 24 May 2017 14:59:22 +0200 Subject: OsmocomBB compile testing / Re: libosmocore embedded build In-Reply-To: <20170518182430.g6jtc3ib54hwnhuy@nataraja> References: <20170516162708.fimenn7qgsehu5pp@nataraja> <20170517140305.iaoflv4pczt3o6a4@nataraja> <20170517161840.GD21386@my.box> <20170518182430.g6jtc3ib54hwnhuy@nataraja> Message-ID: Hi Harald, > To resolve this, we should also start to have a jenkins compile testing > job for OsmocomBB. The "host" (PC) part of the code is built against > regular libosmocore, just like e.g. openbsc or osmo-bts. That should be > possible even so far, and it might make sense to start with that. Probably done [1][2], although I disabled following line to let OsmocomBB build succeed: libosmocore/contrib/verify_value_string_arrays_are_terminated.py $(find . -name "*.[hc]") Is it okay to disable this verification? Regards, Andr? [1] https://gerrit.osmocom.org/#/c/2726/ [2] https://jenkins.osmocom.org/jenkins/view/Jenkins-Gerrit/job/osmocomBB-gerrit/ From laforge at gnumonks.org Wed May 24 22:50:04 2017 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 25 May 2017 00:50:04 +0200 Subject: OsmocomBB build verification Message-ID: <20170524225004.sje6fsebwtk2fvsn@nataraja> Hi Vadim, see attachment. This was my 'test ballon': We now have automatic jenkins build verification at least for the host part of OsmocomBB. Please re-push your patch series again into jenkins, so they will get build-verified. -- - 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 embedded message was scrubbed... From: Jenkins Builder Subject: osmocom-bb[master]: osmocon.c: strip unused variable Date: Wed, 24 May 2017 22:43:56 +0000 Size: 2393 URL: From axilirator at gmail.com Sat May 27 07:20:28 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Sat, 27 May 2017 10:20:28 +0300 Subject: OsmocomBB build verification In-Reply-To: <20170524225004.sje6fsebwtk2fvsn@nataraja> References: <20170524225004.sje6fsebwtk2fvsn@nataraja> Message-ID: Hi Harald and Andr?, > gerrit verification[1] is in place for osmocom-bb. I am happy to know about that. Thanks! All my changes were verified. We still have a lack of unit tests for OsmocomBB. I'll try to do something with that. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Mon May 29 08:14:07 2017 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 29 May 2017 10:14:07 +0200 Subject: Creating GSM Users Association (GSMUA) In-Reply-To: References: Message-ID: <20170529081407.deqbb2gdycpcf7uf@nataraja> Hi Mychaela, sorry for the late response. I think there is a legitimate need (for decades!) to represent the users at entities like GSMA or (much more importantly) the 3GPP and ETSI. 3GPP (and lesser extent ETSI) is where the relevant specifiations are written. Such an user representation would have a role to * identify where (new) specifications infringe on users rights * make sure the industry at least hears about what's in the best interest of users before they discard all of that and implement whatever they want anyway * Raise public awareness about new proposals for specifications that are particularly problematic from a user point of view, therby assert pressure on the standardizations body before it is too late (spec finalied). The areas that I can think of are mostly related to privacy, data protection, and general "digital rights". However, doing the above is fundamentally a lobbying organization, and requires significant funding, starting from membership fees to the relevant standard bodies, to paying for all the related travel expenses to attend the relevant meetings, and people with lots of time on their hands to read the respective draft standards, etc. I think it would be great to do something here, but I think we as the "super technical, ultra nerdy" people working on Free Software (and harwere) in the telecom sphere are typically not in posession of the right skillset to do so. It's much more about social skills than about technical skills. Regarding your proposal: It seems like a contradiction in terms to me if you establish something called an 'user association' while your interest is (at least partially) to represent "boutique manufacturers" regarding IMEI allocations. That's not really of the interest of a *user*. I think the least concern of a user is how and where a manufacturer gets his IMEI allocated. Yes, I agree there is something that can be done regarding TAC allocation (like IEEE OUI / MAC address allocation or USB vid/pid allocation). But that's not a topic for users. 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 samir.s.abed at gmail.com Mon May 29 10:22:00 2017 From: samir.s.abed at gmail.com (samir) Date: Mon, 29 May 2017 13:22:00 +0300 Subject: Phone not receiving calls In-Reply-To: References: <37C1E029-3D84-4DD5-86A3-F076CF203771@gmail.com> Message-ID: <2C807AA1-1ED9-4A52-8DB3-2C3DB85E2DDD@gmail.com> Hi, Did the logs that I provided help ? On May 16, 2017, at 11:14 AM, Vadim Yanitskiy wrote: > Hi, > > > Please provide at least mobile application logs > > What are you waiting for? :) > > With best regards, > Vadim Yanitskiy. From laforge at gnumonks.org Mon May 29 12:42:38 2017 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 29 May 2017 14:42:38 +0200 Subject: OsmocomBB compile testing / Re: libosmocore embedded build In-Reply-To: <678000730.767348.1495133286217@mail.yahoo.com> References: <678000730.767348.1495133286217.ref@mail.yahoo.com> <678000730.767348.1495133286217@mail.yahoo.com> Message-ID: <20170529124238.6aloft3r4qz5wmxo@nataraja> Hi Craig, On Thu, May 18, 2017 at 06:48:06PM +0000, Craig Comstock wrote: > I was thinking about how to setup an automated real device test for > the repo and/or PRs especially. I have devices and cables, just was > thinking about how to automate the re-loading of firmware (via an > interface to the power button I suppose). I think there has been some work by Peter and/or Kevin (Cc) on setting up OsmocomBB phones with a power supply (emulating a battery) and using some serial handshake line (next to the UART) to simulate power button presses in the past. Peter? Kevin? It would be great if you'd be willing to set up such as system, document it and then integate it. I think you don't even need your own base setation. Simple test cases for OsmocomBB could include: * running bcch_scan and check that certain (known strong) cells in the neigbhorhood are found * trying to register to a given network using unknwon/expired IMSI and confirming that the channel is established and a LU REJECT is received With such a test rig we could then automatically test every new libosmocore and osmcoom-bb commit to verify that it still performs basic receive and even basic rx+tx functionality. > Any work ongoing on this front? I don't think there's much happening in OsmocomBB for many years, sadly. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From craig_comstock at yahoo.com Mon May 29 18:47:21 2017 From: craig_comstock at yahoo.com (Craig Comstock) Date: Mon, 29 May 2017 13:47:21 -0500 Subject: OsmocomBB compile testing / Re: libosmocore embedded build In-Reply-To: <20170529124238.6aloft3r4qz5wmxo@nataraja> References: <678000730.767348.1495133286217.ref@mail.yahoo.com> <678000730.767348.1495133286217@mail.yahoo.com> <20170529124238.6aloft3r4qz5wmxo@nataraja> Message-ID: <84BD1A94-3BAB-4DB0-851F-7FD2877A37C4@yahoo.com> I have two c139s wired up for JTAG and many others I can fiddle with. I'll give it a shot! Craig On May 29, 2017 7:42:38 AM CDT, Harald Welte wrote: >Hi Craig, > >On Thu, May 18, 2017 at 06:48:06PM +0000, Craig Comstock wrote: > >> I was thinking about how to setup an automated real device test for >> the repo and/or PRs especially. I have devices and cables, just was >> thinking about how to automate the re-loading of firmware (via an >> interface to the power button I suppose). > >I think there has been some work by Peter and/or Kevin (Cc) on setting >up OsmocomBB phones with a power supply (emulating a battery) and using >some serial handshake line (next to the UART) to simulate power button >presses in the past. Peter? Kevin? > >It would be great if you'd be willing to set up such as system, >document >it and then integate it. > >I think you don't even need your own base setation. Simple test cases >for OsmocomBB could include: > >* running bcch_scan and check that certain (known strong) cells in the > neigbhorhood are found > >* trying to register to a given network using unknwon/expired IMSI and > confirming that the channel is established and a LU REJECT is received > >With such a test rig we could then automatically test every new >libosmocore and osmcoom-bb commit to verify that it still performs >basic >receive and even basic rx+tx functionality. > >> Any work ongoing on this front? > >I don't think there's much happening in OsmocomBB for many years, >sadly. > >-- >- Harald Welte >http://laforge.gnumonks.org/ >============================================================================ >"Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6) -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From snehasish.cse at LIVE.COM Wed May 31 20:37:02 2017 From: snehasish.cse at LIVE.COM (Snehasish Kar) Date: Wed, 31 May 2017 20:37:02 +0000 Subject: Osmocombb with USRP Message-ID: Hi I needed some information from you, I want to implement a GSM Mobile stack with USRP as RF Frontend. Is it possible to build the DSP part of osmocommbb in a different TI DSP board other than calypso. As it is very difficult to find calypso phones now a days. BR Snehasish -------------- next part -------------- An HTML attachment was scrubbed... URL: From snehasish.cse at LIVE.COM Wed May 31 20:44:55 2017 From: snehasish.cse at LIVE.COM (Snehasish Kar) Date: Wed, 31 May 2017 20:44:55 +0000 Subject: Osmocombb with USRP Message-ID: Hi Herald I needed some information from you, I want to implement a GSM Mobile stack with USRP as RF Frontend. Is it possible to build the DSP part of osmocommbb in a different TI DSP board other than calypso. As it is very difficult to find calypso phones now a days. BR Snehasish -------------- next part -------------- An HTML attachment was scrubbed... URL: