From baymax254 at gmail.com Thu Jun 1 04:30:48 2017 From: baymax254 at gmail.com (baymax Robo) Date: Thu, 1 Jun 2017 09:30:48 +0500 Subject: Couldn't get connectivity to Motorolla c118 on writing osmocombb Message-ID: Hi, I am trying to write osmocombb to Motorolla c118 phone by following the given [1] guide.I have successfully compiled firmware binaries but having issues while writing them to phone. I connected motorolla c118 via USB Serial To RS232 TTL to 2.5mm audio jack, using the given guide [2] When I run this command $ dmesg | grep tty I get the following output [ 0.000000] console [tty0] enabled [ 14.946936] usb 3-6: pl2303 converter now attached to ttyUSB0 [ 973.747957] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 [ 1484.595816] usb 3-6: pl2303 converter now attached to ttyUSB0 [ 1845.344494] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 [ 2643.566407] usb 3-6: pl2303 converter now attached to ttyUSB1 And on running this $ sudo cu -l /dev/ttyUSB1 -s 115200 I get a connected message but no further progress is done. When i press Power button briefly, no activity is shown. I have tried with two phones but no success on any. I have checked the connectivity between headphone jack and USB serial chip via voltmeter, it is fine as well. Also tried by doing Master reset on phone but no use. What can be issue and how can i fix it. ? Kindly ignore any mistakes, i am new to this domain, couldn't find much help on google as well :( [1] https://osmocom.org/projects/baseband/wiki/Software_Getting_Started https://osmocom.org/projects/baseband/wiki/Osmocon [2] http://www.linuxx.eu/2014/09/osmocombb-hardware-and-software-setup.html [2] -------------- next part -------------- An HTML attachment was scrubbed... URL: From antgorka at gmail.com Thu Jun 1 06:16:04 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Thu, 1 Jun 2017 09:16:04 +0300 Subject: Couldn't get connectivity to Motorolla c118 on writing osmocombb In-Reply-To: References: Message-ID: Hi, Are you sure the jack is being plugged on the whole length? Did you get success with minicom test? I would recommend you to disassemble phone and check whether the jack plugged an the whole length. Do you use virtualized OS or normal? If virtualized, try to play with the settings. KR, Anton 2017-06-01 7:30 GMT+03:00 baymax Robo : > Hi, > > I am trying to write osmocombb to Motorolla c118 phone by following the > given [1] guide.I have successfully compiled firmware binaries but having > issues while writing them to phone. > > I connected motorolla c118 via USB Serial To RS232 TTL to 2.5mm audio > jack, using the given guide [2] > > When I run this command > > $ dmesg | grep tty > > I get the following output > > [ 0.000000] console [tty0] enabled > [ 14.946936] usb 3-6: pl2303 converter now attached to ttyUSB0 > [ 973.747957] pl2303 ttyUSB0: pl2303 converter now disconnected from > ttyUSB0 > [ 1484.595816] usb 3-6: pl2303 converter now attached to ttyUSB0 > [ 1845.344494] pl2303 ttyUSB0: pl2303 converter now disconnected from > ttyUSB0 > [ 2643.566407] usb 3-6: pl2303 converter now attached to ttyUSB1 > > And on running this > > $ sudo cu -l /dev/ttyUSB1 -s 115200 > > I get a connected message but no further progress is done. When i press > Power button briefly, no activity is shown. I have tried with two phones > but no success on any. I have checked the connectivity between headphone > jack and USB serial chip via voltmeter, it is fine as well. Also tried by > doing Master reset on phone but no use. What can be issue and how can i fix > it. ? > > Kindly ignore any mistakes, i am new to this domain, couldn't find much > help on google as well :( > > [1] > https://osmocom.org/projects/baseband/wiki/Software_Getting_Started > https://osmocom.org/projects/baseband/wiki/Osmocon > > [2] > http://www.linuxx.eu/2014/09/osmocombb-hardware-and-software-setup.html > > [2] > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From baymax254 at gmail.com Thu Jun 1 06:57:17 2017 From: baymax254 at gmail.com (baymax Robo) Date: Thu, 1 Jun 2017 11:57:17 +0500 Subject: Couldn't get connectivity to Motorolla c118 on writing osmocombb In-Reply-To: References:

Message-ID: Hi, Thanks for replying back. I am not using virtualized environment. No success with minicom test. What exactly do you mean by jack is being plugged on the whole length, i didn't get it. On Thu, Jun 1, 2017 at 11:16 AM, Anton Gorbachev wrote: > Hi, > > Are you sure the jack is being plugged on the whole length? > Did you get success with minicom test? > I would recommend you to disassemble phone and check whether the jack > plugged an the whole length. > Do you use virtualized OS or normal? If virtualized, try to play with the > settings. > > KR, > Anton > > 2017-06-01 7:30 GMT+03:00 baymax Robo : > >> Hi, >> >> I am trying to write osmocombb to Motorolla c118 phone by following the >> given [1] guide.I have successfully compiled firmware binaries but having >> issues while writing them to phone. >> >> I connected motorolla c118 via USB Serial To RS232 TTL to 2.5mm audio >> jack, using the given guide [2] >> >> When I run this command >> >> $ dmesg | grep tty >> >> I get the following output >> >> [ 0.000000] console [tty0] enabled >> [ 14.946936] usb 3-6: pl2303 converter now attached to ttyUSB0 >> [ 973.747957] pl2303 ttyUSB0: pl2303 converter now disconnected from >> ttyUSB0 >> [ 1484.595816] usb 3-6: pl2303 converter now attached to ttyUSB0 >> [ 1845.344494] pl2303 ttyUSB0: pl2303 converter now disconnected from >> ttyUSB0 >> [ 2643.566407] usb 3-6: pl2303 converter now attached to ttyUSB1 >> >> And on running this >> >> $ sudo cu -l /dev/ttyUSB1 -s 115200 >> >> I get a connected message but no further progress is done. When i press >> Power button briefly, no activity is shown. I have tried with two phones >> but no success on any. I have checked the connectivity between headphone >> jack and USB serial chip via voltmeter, it is fine as well. Also tried by >> doing Master reset on phone but no use. What can be issue and how can i fix >> it. ? >> >> Kindly ignore any mistakes, i am new to this domain, couldn't find much >> help on google as well :( >> >> [1] >> https://osmocom.org/projects/baseband/wiki/Software_Getting_Started >> https://osmocom.org/projects/baseband/wiki/Osmocon >> >> [2] >> http://www.linuxx.eu/2014/09/osmocombb-hardware-and-software-setup.html >> >> [2] >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mychaela.falconia at gmail.com Thu Jun 1 07:07:06 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Wed, 31 May 2017 23:07:06 -0800 Subject: Osmocombb with USRP In-Reply-To: References: Message-ID: On 5/31/17, Snehasish Kar wrote: > [...] it is very difficult to find calypso phones now a days. That statement cannot be true, as I just went to ebay, searched for C139 and got 33 listings; 30 of them are USA units (850+1900 MHz bands), but 3 are from the UK and thus presumably the 900+1800 MHz version. There are also newly made Calypso devices: https://www.freecalypso.org/fcdev3b.html I designed and built the above Calypso board for the purpose of running my own FreeCalypso firmware which is more demanding than OsmocomBB and for which Mot C1xx phones aren't good enough, but OsmocomBB runs on my board just fine as well. However, if you are only interested in OsmocomBB and not FreeCalypso firmware, then buying my expensive board will be a waste of money, as it offers absolutely no advantage over the obscenely cheap Mot C1xx phones for OsmocomBB purposes. M~ From antgorka at gmail.com Thu Jun 1 07:16:23 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Thu, 1 Jun 2017 10:16:23 +0300 Subject: Couldn't get connectivity to Motorolla c118 on writing osmocombb In-Reply-To: References:

Message-ID: Hi, Check the picture https://osmocom.org/attachments/download/2091/motorola_c123_hello_world.jpg I mean the outer plastic case of the phone may not allow your jack to be inserted at the whole length to thoe whole even if it looks like OK. It depends on your jack case shape. KR, Anton 2017-06-01 9:57 GMT+03:00 baymax Robo : > Hi, > > Thanks for replying back. > > I am not using virtualized environment. No success with minicom test. What > exactly do you mean by jack is being plugged on the whole length, i didn't > get it. > > > On Thu, Jun 1, 2017 at 11:16 AM, Anton Gorbachev > wrote: > >> Hi, >> >> Are you sure the jack is being plugged on the whole length? >> Did you get success with minicom test? >> I would recommend you to disassemble phone and check whether the jack >> plugged an the whole length. >> Do you use virtualized OS or normal? If virtualized, try to play with the >> settings. >> >> KR, >> Anton >> >> 2017-06-01 7:30 GMT+03:00 baymax Robo : >> >>> Hi, >>> >>> I am trying to write osmocombb to Motorolla c118 phone by following the >>> given [1] guide.I have successfully compiled firmware binaries but having >>> issues while writing them to phone. >>> >>> I connected motorolla c118 via USB Serial To RS232 TTL to 2.5mm audio >>> jack, using the given guide [2] >>> >>> When I run this command >>> >>> $ dmesg | grep tty >>> >>> I get the following output >>> >>> [ 0.000000] console [tty0] enabled >>> [ 14.946936] usb 3-6: pl2303 converter now attached to ttyUSB0 >>> [ 973.747957] pl2303 ttyUSB0: pl2303 converter now disconnected from >>> ttyUSB0 >>> [ 1484.595816] usb 3-6: pl2303 converter now attached to ttyUSB0 >>> [ 1845.344494] pl2303 ttyUSB0: pl2303 converter now disconnected from >>> ttyUSB0 >>> [ 2643.566407] usb 3-6: pl2303 converter now attached to ttyUSB1 >>> >>> And on running this >>> >>> $ sudo cu -l /dev/ttyUSB1 -s 115200 >>> >>> I get a connected message but no further progress is done. When i press >>> Power button briefly, no activity is shown. I have tried with two phones >>> but no success on any. I have checked the connectivity between headphone >>> jack and USB serial chip via voltmeter, it is fine as well. Also tried by >>> doing Master reset on phone but no use. What can be issue and how can i fix >>> it. ? >>> >>> Kindly ignore any mistakes, i am new to this domain, couldn't find much >>> help on google as well :( >>> >>> [1] >>> https://osmocom.org/projects/baseband/wiki/Software_Getting_Started >>> https://osmocom.org/projects/baseband/wiki/Osmocon >>> >>> [2] >>> http://www.linuxx.eu/2014/09/osmocombb-hardware-and-software-setup.html >>> >>> [2] >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Thu Jun 1 07:25:19 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Thu, 1 Jun 2017 14:25:19 +0700 Subject: Osmocombb with USRP Message-ID: Hi, > I want to implement a GSM Mobile stack with USRP as RF Frontend. Well, I am currently working on that. I don't stick on a specific SDR device like mentioned one. > Is it possible to build the DSP part of osmocommbb in a different > TI DSP board other than calypso. In case of SDR, DSP part should be done on computer side, like OsmoTRX does. And some low-level GSM L1 part is already implemented and could be used by MS implementation too. If you would like to cooperate me in this direction, have a look at: https://github.com/axilirator/osmocom-bb Right now I am doing some code refactoring, and further commits will be posted at http://gerrit.osmocom.org/ With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From baymax254 at gmail.com Thu Jun 1 07:27:45 2017 From: baymax254 at gmail.com (baymax Robo) Date: Thu, 1 Jun 2017 12:27:45 +0500 Subject: Couldn't get connectivity to Motorolla c118 on writing osmocombb In-Reply-To: References:

Message-ID: Oh okay. The headphone jack is working fine, i have tested it. And helloworld isn't working. Can you tell some other method to test phones connectivity with my system. On Thu, Jun 1, 2017 at 12:16 PM, Anton Gorbachev wrote: > Hi, > > Check the picture > https://osmocom.org/attachments/download/2091/ > motorola_c123_hello_world.jpg > > I mean the outer plastic case of the phone may not allow your jack to be > inserted at the whole length to thoe whole even if it looks like OK. > It depends on your jack case shape. > > KR, > Anton > > 2017-06-01 9:57 GMT+03:00 baymax Robo : > >> Hi, >> >> Thanks for replying back. >> >> I am not using virtualized environment. No success with minicom test. >> What exactly do you mean by jack is being plugged on the whole length, i >> didn't get it. >> >> >> On Thu, Jun 1, 2017 at 11:16 AM, Anton Gorbachev >> wrote: >> >>> Hi, >>> >>> Are you sure the jack is being plugged on the whole length? >>> Did you get success with minicom test? >>> I would recommend you to disassemble phone and check whether the jack >>> plugged an the whole length. >>> Do you use virtualized OS or normal? If virtualized, try to play with >>> the settings. >>> >>> KR, >>> Anton >>> >>> 2017-06-01 7:30 GMT+03:00 baymax Robo : >>> >>>> Hi, >>>> >>>> I am trying to write osmocombb to Motorolla c118 phone by following the >>>> given [1] guide.I have successfully compiled firmware binaries but having >>>> issues while writing them to phone. >>>> >>>> I connected motorolla c118 via USB Serial To RS232 TTL to 2.5mm audio >>>> jack, using the given guide [2] >>>> >>>> When I run this command >>>> >>>> $ dmesg | grep tty >>>> >>>> I get the following output >>>> >>>> [ 0.000000] console [tty0] enabled >>>> [ 14.946936] usb 3-6: pl2303 converter now attached to ttyUSB0 >>>> [ 973.747957] pl2303 ttyUSB0: pl2303 converter now disconnected from >>>> ttyUSB0 >>>> [ 1484.595816] usb 3-6: pl2303 converter now attached to ttyUSB0 >>>> [ 1845.344494] pl2303 ttyUSB0: pl2303 converter now disconnected from >>>> ttyUSB0 >>>> [ 2643.566407] usb 3-6: pl2303 converter now attached to ttyUSB1 >>>> >>>> And on running this >>>> >>>> $ sudo cu -l /dev/ttyUSB1 -s 115200 >>>> >>>> I get a connected message but no further progress is done. When i press >>>> Power button briefly, no activity is shown. I have tried with two phones >>>> but no success on any. I have checked the connectivity between headphone >>>> jack and USB serial chip via voltmeter, it is fine as well. Also tried by >>>> doing Master reset on phone but no use. What can be issue and how can i fix >>>> it. ? >>>> >>>> Kindly ignore any mistakes, i am new to this domain, couldn't find much >>>> help on google as well :( >>>> >>>> [1] >>>> https://osmocom.org/projects/baseband/wiki/Software_Getting_Started >>>> https://osmocom.org/projects/baseband/wiki/Osmocon >>>> >>>> [2] >>>> http://www.linuxx.eu/2014/09/osmocombb-hardware-and-software-setup.html >>>> >>>> [2] >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Thu Jun 1 07:30:42 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Thu, 1 Jun 2017 14:30:42 +0700 Subject: Phone not receiving calls In-Reply-To: <2C807AA1-1ED9-4A52-8DB3-2C3DB85E2DDD@gmail.com> References:

<37C1E029-3D84-4DD5-86A3-F076CF203771@gmail.com> <2C807AA1-1ED9-4A52-8DB3-2C3DB85E2DDD@gmail.com> Message-ID: Hi, > Did the logs that I provided help ? I had a quick look only, so for now I can say nothing. If I find something, I'll let you know. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From samir.s.abed at gmail.com Thu Jun 1 09:26:52 2017 From: samir.s.abed at gmail.com (samir) Date: Thu, 1 Jun 2017 12:26:52 +0300 Subject: Phone not receiving calls In-Reply-To: References:

<37C1E029-3D84-4DD5-86A3-F076CF203771@gmail.com> <2C807AA1-1ED9-4A52-8DB3-2C3DB85E2DDD@gmail.com> Message-ID: <1E18D3F9-1920-42C0-AB9C-0F7C5BCF81DD@gmail.com> Something has changed recently as my phone is not paged at all even when using the SIM cards that were previously working fine. Now all my SIM cards do not receive calls. I didn?t change anything in the configuration since the last time it was working. On Jun 1, 2017, at 10:30 AM, Vadim Yanitskiy wrote: > Hi, > > > Did the logs that I provided help ? > > I had a quick look only, so for now I can say nothing. > If I find something, I'll let you know. > > With best regards, > Vadim Yanitskiy. From domi at tomcsanyi.net Thu Jun 1 10:01:00 2017 From: domi at tomcsanyi.net (=?utf-8?B?VG9tY3PDoW55aSwgRG9tb25rb3M=?=) Date: Thu, 1 Jun 2017 12:01:00 +0200 (CEST) Subject: Phone not receiving calls In-Reply-To: <1E18D3F9-1920-42C0-AB9C-0F7C5BCF81DD@gmail.com> References:

<37C1E029-3D84-4DD5-86A3-F076CF203771@gmail.com> <2C807AA1-1ED9-4A52-8DB3-2C3DB85E2DDD@gmail.com> <1E18D3F9-1920-42C0-AB9C-0F7C5BCF81DD@gmail.com> Message-ID: <8528DE3C-A960-4F5F-BBCE-C58B89C8F039@tomcsanyi.net> Are you registered to the network succesfully? Does a Location Update happen? Cheers, Domi 2017. j?n. 1. d?tummal, 11:28 id?pontban samir ?rta: > Something has changed recently as my phone is not paged at all even when using the SIM cards that were previously working fine. Now all my SIM cards do not receive calls. I didn?t change anything in the configuration since the last time it was working. > > >> On Jun 1, 2017, at 10:30 AM, Vadim Yanitskiy wrote: >> >> Hi, >> >>> Did the logs that I provided help ? >> >> I had a quick look only, so for now I can say nothing. >> If I find something, I'll let you know. >> >> With best regards, >> Vadim Yanitskiy. > From samir.s.abed at gmail.com Thu Jun 1 10:39:16 2017 From: samir.s.abed at gmail.com (samir) Date: Thu, 1 Jun 2017 13:39:16 +0300 Subject: Phone not receiving calls In-Reply-To: <8528DE3C-A960-4F5F-BBCE-C58B89C8F039@tomcsanyi.net> References:

<37C1E029-3D84-4DD5-86A3-F076CF203771@gmail.com> <2C807AA1-1ED9-4A52-8DB3-2C3DB85E2DDD@gmail.com> <1E18D3F9-1920-42C0-AB9C-0F7C5BCF81DD@gmail.com> <8528DE3C-A960-4F5F-BBCE-C58B89C8F039@tomcsanyi.net> Message-ID: Yes, I can register normally and make outgoing calls without any problem. Also location update is done periodically with success. Calls are received only if they occur immediately after the location update (before the phone releases the channel). On Jun 1, 2017, at 1:01 PM, Tomcs?nyi, Domonkos wrote: > Are you registered to the network succesfully? Does a Location Update happen? > > Cheers, > Domi > > > 2017. j?n. 1. d?tummal, 11:28 id?pontban samir ?rta: > >> Something has changed recently as my phone is not paged at all even when using the SIM cards that were previously working fine. Now all my SIM cards do not receive calls. I didn?t change anything in the configuration since the last time it was working. >> >> >>> On Jun 1, 2017, at 10:30 AM, Vadim Yanitskiy wrote: >>> >>> Hi, >>> >>>> Did the logs that I provided help ? >>> >>> I had a quick look only, so for now I can say nothing. >>> If I find something, I'll let you know. >>> >>> With best regards, >>> Vadim Yanitskiy. >> From 246tnt at gmail.com Thu Jun 1 11:46:30 2017 From: 246tnt at gmail.com (Sylvain Munaut) Date: Thu, 1 Jun 2017 13:46:30 +0200 Subject: Phone not receiving calls In-Reply-To: References:

<37C1E029-3D84-4DD5-86A3-F076CF203771@gmail.com> <2C807AA1-1ED9-4A52-8DB3-2C3DB85E2DDD@gmail.com> <1E18D3F9-1920-42C0-AB9C-0F7C5BCF81DD@gmail.com> <8528DE3C-A960-4F5F-BBCE-C58B89C8F039@tomcsanyi.net> Message-ID: Send a .pcap capture of the initial phone registering (and long enough to include all the SI messages broadcasted by the cell). Cheers, Sylvain From axilirator at gmail.com Thu Jun 1 12:56:16 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Thu, 1 Jun 2017 19:56:16 +0700 Subject: Osmocombb with USRP In-Reply-To: References: Message-ID: Hi again, > I am in! Great! > let me know what to do! > Is it capable of baseband processing > both gsm uplink and downlink signals? Let me explain some basics first. In current OsmocomBB we have an osmocon application, which forwards L1CTL (GSM Layer 1 Control Messages) between host software (GSM L2 & L3 applications such as mobile) and phone's custom firmware through serial link (sercomm). Since we are going to use SDR based PHY for GSM L1, similar application is still required. I named one as 'trxcon'. Just like osmocon, it acts as a bridge between existing L2 & L3 applications and another application (modified OsmoTRX or GR-GSM based TRX), providing an UNIX socket (/tmp/osmocom_l2). layer23 app <-> trxcon <-> transceiver <-> SDR I am currently working on trxcon application, doing some code refactoring and integration of osmo-fsm (Finite State Machine) framework. One consists of: - L1CTL link - UNIX socket handlers; - L1CTL handlers - REQ / RSP / IND handlers; - TRX interface - CTRL / DATA interface for TRX; - TDMA scheduler - WIP right now... Basically this application is similar to OsmoBTS. Regarding to transceiver, we can use OsmoTRX here, but some code modifications are required in this case (see 'ms' branch). For now I decided to use GR-GSM blocks from Piotr Krysik, and have written a simple transceiver implementation, which you can find here: https://github.com/axilirator/gr-gsmtrx As there are currently no GR-GSM blocks, which allow to transmit UL data, we are limited to RX only mode. But I had a great discussion with the author, and he is going to work on required blocks. That is a brief introduction. Feel free to ask me if you have any related questions, and feel free to push your commits for review! You can also find me @fixeria in IRC #osmocom room. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Thu Jun 1 14:30:18 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Thu, 1 Jun 2017 21:30:18 +0700 Subject: Osmocombb with USRP In-Reply-To: References:

Message-ID: > your device, current supports both uplink and downlink rx Wrong. What do you mean by 'device'? I can only receive DL bursts for now. As soon as I integrate TDMA scheduler, it will be possible to decode raw bursts to L3 packets and forward them higher layers. > It can be further be connected to any standard L2/L3 > stack for further processing What do you mean by 'standard stack'? Some simple applications like ccch_scan already able to tune SDR to required ARFCN and to start burst detection. > Do you have some cfile What for? You can tune to any of surrounding carriers, and test the implementation against the real networks. Moreover you can use RTL-SDR while we don't have TX capabilities. P.S. Please sign in to the baseband-devel mailing lists and CC to baseband-devel at lists.osmocom.org because your messages aren't displayed there. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From axilirator at gmail.com Thu Jun 1 17:44:28 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Fri, 2 Jun 2017 00:44:28 +0700 Subject: Osmocombb with USRP In-Reply-To: References:

Message-ID: >> Wrong. What do you mean by 'device'? > I mean your baseband application is only able to > decode both uplink as well as downlink? > What about decoding the uplink? I believe > integrating the TDMA scheduler will enable it right? We don't need to decode UL on MS side. Please, don't cause me to repeat myself: only DL is supported for now. We need to decode DL bursts, and to encode UL messages. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From snehasish.cse at LIVE.COM Thu Jun 1 14:49:28 2017 From: snehasish.cse at LIVE.COM (Snehasish Kar) Date: Thu, 1 Jun 2017 14:49:28 +0000 Subject: Osmocombb with USRP In-Reply-To: References:

, Message-ID: Hello >Wrong. What do you mean by 'device'? Sorry for that. I mean your baseband application is only able to decode both uplink as well as downlink? >I can only receive DL bursts for now. What about decoding the uplink? I believe integrating the TDMA scheduler will enable it right? >What do you mean by 'standard stack'? By standard stack I meant the ccch_scan itself. >What for? You can tune to any of surrounding carriers, and >test the implementation against the real networks. Moreover >you can use RTL-SDR while we don't have TX capabilities. I will try that >P.S. Please sign in to the baseband-devel mailing >lists and CC to baseband-devel at lists.osmocom.org >because your messages aren't displayed there. Already did that, so I am able to receive other messages from the group. BR Snehasish -------------- next part -------------- An HTML attachment was scrubbed... URL: From mychaela.falconia at gmail.com Fri Jun 2 06:01:34 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Thu, 1 Jun 2017 22:01:34 -0800 Subject: Creating GSM Users Association (GSMUA) In-Reply-To: <20170529081407.deqbb2gdycpcf7uf@nataraja> References: <20170529081407.deqbb2gdycpcf7uf@nataraja> Message-ID: Hi Harald, Thank you for taking the time to respond to my GSMUA idea. I agree with you that representing the interests of users at GSMA/ETSI/3GPP would a task beyond our means, but I still see social value in creating our own totally informal group purely for mutual support and camaraderie. Throughout human history members of various oppressed minorities have banded together for mutual support, even if that support is purely emotional and nothing more, and I am currently experiencing an unmet need for such a group with regard to GSM/2G. > 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. My idea of a recycled IMEI registry was just one potential application for GSMUA, and the overall idea of GSMUA still appeals to me even if we don't pursue the recycled IMEI registry idea. As for representing boutique manufacturers of end user devices in a user association alongside with actual end users, I don't see much of a contradiction, as the interests of the two are expected to coincide. Boutique manufacturers are fundamentally different from mainstream ones: while mainstream manufs act as users' enemies for all practical purposes (they prefer to serve the interests of carriers and/or governments instead, and their entire "security" model sees the user as the enemy), boutique manufs exist for no purpose except to serve the interests of underrepresented end users, and given that FLOSS development typically proceeds by scratching one's own itch, a real-life boutique manuf of GSM devices will almost certainly make those devices for his or her own personal use first and foremost, and then offer them for sale in extremely small volume to others of a like mind. In my original proposal I outlined the following list of parties whom I see as the target audience for my proposed GSMUA: * Empowered end users; * Small boutique manufacturers for devices for said empowered end users; * Small community and other non-mainstream network operators, i.e., those who operate networks for the empowered end users and their FLOSS devices to connect to. A key goal of GSMUA is to be a truly neutral meeting ground where all of the above can come together, with everyone being equally welcome regardless of specific project affiliation, if any. The closest thing that exists so far where all kinds of different people with an interest in cellular telephony can come together are your OsmoCon and OsmoDevCon get-togethers, but those are limited to projects that fall under the Osmocom umbrella, and do not include non-Osmocom projects in the same general space. My vision for GSMUA is to be more inclusive and more neutral, a place where people from Osmocom, FreeCalypso, OpenBTS, YateBTS and others (as well as just persons who are simply interested in the general subject matter, but not affiliated or involved with any specific project) can come together (at least online if not physically) without any of them being in a dominant position. The very fact that this discussion we are having right now has to be cross-posted to 3 different mailing lists is an indication of the problem which my GSMUA proposal is meant to solve: there presently exists no truly neutral, truly general community mailing list where *everyone* with an interest in non-big-bucks GSM and other cellular networks can interact with others in the same field, regardless of whether their specific interest is in running their own network, making their own end user phones, or just using one or both of those as a highly intelligent, highly empowered end user, and without being specific to any one particular project. One specific reason why I feel there is a need for people on the empowered-end-user mobile device side to meet with people on the network infrastructure and network operations side is the imminent threat of GSM/2G shutdown by the uncaring major network operators. There exist people in the world, myself included, for whom life without GSM/2G would be absolutely intolerable, as GSM/2G is the only cellular technology for which there exist practically usable FLOSS implementations on the MS/UE side. In both USA and Canada there is only one GSM/2G operator left, and if T-Mobile USA and Rogers completely shut down their GSM/2G networks in another year or two, and reallocate every last 200 kHz channel in both 1900 and 850 MHz bands to their stinking 3G/4G/whatever services so no one else can set up replacement community networks, users of Calypso phones will be completely screwed. This is where people in the OpenBTS/OpenBSC/etc projects can come to the rescue. As I understand it, there are both commercial and community operators who run their own GSM/2G networks using BTS hardware and software built and maintained by the Osmocom/OpenBTS/etc community, and because of the imminent shutdown of GSM/2G services in "first world" regions, I feel that a bridge needs to be built ASAP between users of 2G-only Calypso phones on one end and those non-mainstream community network operators on the other end. To put it simply, if the evil first world governments take away the last remaining bit of spectrum from GSM/2G users, we (the latter users) need to know which remote third world village we should flee to where we can set up our own OpenBTS/OpenBSC/OsmoNITB/etc GSM/2G network without having radio regulators show up with tanks the next morning to shut it down, or where such a community network already exists. To put the matter in perspective, I will be giving a presentation about FreeCalypso at REcon in Montreal just two weeks from now, and the subject of imminent GSM/2G shutdown will be unavoidable. Unless there exists another person in the world who is as crazy as me and who would be willing and able to carry out a project similar to FreeCalypso, but using leaked Qualcomm or MTK sources for some 3G-capable or even LTE-capable chip instead of TI's 2G-only ones (seems rather unlikely to me that anyone else can be insane enough to do such a thing), creating a GSM village in some remote 3rd world location that would welcome refugees from the "first world" fleeing from 3G/4G tyranny seems like the most proper solution which I should advocate for. M~ From snehasish.cse at LIVE.COM Thu Jun 1 12:31:56 2017 From: snehasish.cse at LIVE.COM (Snehasish Kar) Date: Thu, 1 Jun 2017 12:31:56 +0000 Subject: Osmocombb with USRP In-Reply-To: References: Message-ID: Hello Vadim That sounds really cool. But is it capable of baseband processing both GSM uplink and downlink signals. In your code available at https://github.com/axilirator/osmocom-bb which is the DSP module for SDR and what are its dependenices? BR Snehasish ________________________________ From: Vadim Yanitskiy Sent: Thursday, June 1, 2017 12:55:19 PM To: snehasish.cse at live.com Cc: baseband-devel Subject: Re: Osmocombb with USRP Hi, > I want to implement a GSM Mobile stack with USRP as RF Frontend. Well, I am currently working on that. I don't stick on a specific SDR device like mentioned one. > Is it possible to build the DSP part of osmocommbb in a different > TI DSP board other than calypso. In case of SDR, DSP part should be done on computer side, like OsmoTRX does. And some low-level GSM L1 part is already implemented and could be used by MS implementation too. If you would like to cooperate me in this direction, have a look at: https://github.com/axilirator/osmocom-bb Right now I am doing some code refactoring, and further commits will be posted at http://gerrit.osmocom.org/ With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From antgorka at gmail.com Mon Jun 5 07:14:26 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Mon, 5 Jun 2017 10:14:26 +0300 Subject: Couldn't get connectivity to Motorolla c118 on writing osmocombb In-Reply-To: References:

Message-ID: Hi, Which USB-TTL converter do you use? What is the output of PuTTY and mincom? Post it here. Try using -m c123 instead of -m c123xor KR, Anton 2017-06-05 8:30 GMT+03:00 baymax Robo : > HI again, > > I replaced my ttl converter, now my phone is able to communicate via > serial port but osmocon is unable to write hello world binary. The output > of following command is given > > $ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/ > compal_e88/hello_world.compalram.bin > > > output: > > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: f7 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 72 r > got 3 bytes from modem, data looks like: 82 bf 7d ..} > got 1 bytes from modem, data looks like: fd . > got 1 bytes from modem, data looks like: 7f . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: a6 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: d2 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: 0a . > got 1 bytes from modem, data looks like: 3a : > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 4d M > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: da . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: f7 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 82 . > got 1 bytes from modem, data looks like: bf . > got 1 bytes from modem, data looks like: 7d } > got 1 bytes from modem, data looks like: fd . > got 1 bytes from modem, data looks like: 7f . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: a6 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: d2 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: 0a . > got 1 bytes from modem, data looks like: 3a : > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 4d M > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: da . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: fb . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 82 . > got 1 bytes from modem, data looks like: bf . > got 1 bytes from modem, data looks like: 7d } > got 1 bytes from modem, data looks like: fd . > got 1 bytes from modem, data looks like: 7f . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: a6 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: d2 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: 0a . > got 1 bytes from modem, data looks like: 3a : > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 4d M > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: da . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: fb . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 82 . > got 1 bytes from modem, data looks like: bf . > got 1 bytes from modem, data looks like: 7d } > got 1 bytes from modem, data looks like: fd . > got 1 bytes from modem, data looks like: 7f . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: a6 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: d2 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: 0a . > got 1 bytes from modem, data looks like: 3a : > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 4d M > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: da . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: f7 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 82 . > got 1 bytes from modem, data looks like: bf . > got 1 bytes from modem, data looks like: 7d } > got 1 bytes from modem, data looks like: fd . > got 1 bytes from modem, data looks like: 7f . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: a6 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: d2 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: 0a . > got 1 bytes from modem, data looks like: 3a : > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 4d M > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: da . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: ff . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: f7 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 82 . > got 1 bytes from modem, data looks like: bf . > got 1 bytes from modem, data looks like: 7d } > got 1 bytes from modem, data looks like: fd . > got 1 bytes from modem, data looks like: 7f . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: a6 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: d2 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: 0a . > got 1 bytes from modem, data looks like: 3a : > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 4d M > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: da . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: f7 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 82 . > got 1 bytes from modem, data looks like: bf . > got 1 bytes from modem, data looks like: 7d } > got 1 bytes from modem, data looks like: fd . > got 1 bytes from modem, data looks like: 7f . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: a6 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: d2 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: 0a . > got 1 bytes from modem, data looks like: 3a : > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 4d M > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: da . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: fb . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 82 . > got 1 bytes from modem, data looks like: bf . > got 1 bytes from modem, data looks like: 7d } > got 1 bytes from modem, data looks like: fd . > got 1 bytes from modem, data looks like: 7f . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: a6 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: d2 . > got 1 bytes from modem, data looks like: 51 Q > got 1 bytes from modem, data looks like: 0a . > got 1 bytes from modem, data looks like: 3a : > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 4d M > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: a3 . > got 1 bytes from modem, data looks like: da . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > > > and output on putty is unreadable. Kindly guide me what's wrong and how > can it be fixed. > Thanks > > On Thu, Jun 1, 2017 at 12:39 PM, Anton Gorbachev > wrote: > >> If you cannot get @ftmtoolerror with minicom then your jack is NOT >> working or your TTL converter is broken (was burnt during soldering?:) >> >> If you have another OS (e.g. Windows machine) you can put the device in >> the PC, find out which serial line it is using, >> run PuTTY, set Destination to Serial, COM9 (or what you find out), >> speed 115200, connect. >> Then push the power button on motorola, you must see @ftmtoolerror there. >> If not, try another jack, another TTL converter, remove phone plastic case >> as I told already.. >> >> No more ideas :) >> >> KR, >> Anton >> >> >> 2017-06-01 10:27 GMT+03:00 baymax Robo : >> >>> Oh okay. The headphone jack is working fine, i have tested it. And >>> helloworld isn't working. Can you tell some other method to test phones >>> connectivity with my system. >>> >>> On Thu, Jun 1, 2017 at 12:16 PM, Anton Gorbachev >>> wrote: >>> >>>> Hi, >>>> >>>> Check the picture >>>> https://osmocom.org/attachments/download/2091/motorola_c123_ >>>> hello_world.jpg >>>> >>>> I mean the outer plastic case of the phone may not allow your jack to >>>> be inserted at the whole length to thoe whole even if it looks like OK. >>>> It depends on your jack case shape. >>>> >>>> KR, >>>> Anton >>>> >>>> 2017-06-01 9:57 GMT+03:00 baymax Robo : >>>> >>>>> Hi, >>>>> >>>>> Thanks for replying back. >>>>> >>>>> I am not using virtualized environment. No success with minicom test. >>>>> What exactly do you mean by jack is being plugged on the whole length, i >>>>> didn't get it. >>>>> >>>>> >>>>> On Thu, Jun 1, 2017 at 11:16 AM, Anton Gorbachev >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Are you sure the jack is being plugged on the whole length? >>>>>> Did you get success with minicom test? >>>>>> I would recommend you to disassemble phone and check whether the jack >>>>>> plugged an the whole length. >>>>>> Do you use virtualized OS or normal? If virtualized, try to play with >>>>>> the settings. >>>>>> >>>>>> KR, >>>>>> Anton >>>>>> >>>>>> 2017-06-01 7:30 GMT+03:00 baymax Robo : >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I am trying to write osmocombb to Motorolla c118 phone by following >>>>>>> the given [1] guide.I have successfully compiled firmware binaries but >>>>>>> having issues while writing them to phone. >>>>>>> >>>>>>> I connected motorolla c118 via USB Serial To RS232 TTL to 2.5mm >>>>>>> audio jack, using the given guide [2] >>>>>>> >>>>>>> When I run this command >>>>>>> >>>>>>> $ dmesg | grep tty >>>>>>> >>>>>>> I get the following output >>>>>>> >>>>>>> [ 0.000000] console [tty0] enabled >>>>>>> [ 14.946936] usb 3-6: pl2303 converter now attached to ttyUSB0 >>>>>>> [ 973.747957] pl2303 ttyUSB0: pl2303 converter now disconnected >>>>>>> from ttyUSB0 >>>>>>> [ 1484.595816] usb 3-6: pl2303 converter now attached to ttyUSB0 >>>>>>> [ 1845.344494] pl2303 ttyUSB0: pl2303 converter now disconnected >>>>>>> from ttyUSB0 >>>>>>> [ 2643.566407] usb 3-6: pl2303 converter now attached to ttyUSB1 >>>>>>> >>>>>>> And on running this >>>>>>> >>>>>>> $ sudo cu -l /dev/ttyUSB1 -s 115200 >>>>>>> >>>>>>> I get a connected message but no further progress is done. When i >>>>>>> press Power button briefly, no activity is shown. I have tried with two >>>>>>> phones but no success on any. I have checked the connectivity between >>>>>>> headphone jack and USB serial chip via voltmeter, it is fine as well. Also >>>>>>> tried by doing Master reset on phone but no use. What can be issue and how >>>>>>> can i fix it. ? >>>>>>> >>>>>>> Kindly ignore any mistakes, i am new to this domain, couldn't find >>>>>>> much help on google as well :( >>>>>>> >>>>>>> [1] >>>>>>> https://osmocom.org/projects/baseband/wiki/Software_Getting_Started >>>>>>> https://osmocom.org/projects/baseband/wiki/Osmocon >>>>>>> >>>>>>> [2] >>>>>>> http://www.linuxx.eu/2014/09/osmocombb-hardware-and-software >>>>>>> -setup.html >>>>>>> >>>>>>> [2] >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From baymax254 at gmail.com Mon Jun 5 07:33:29 2017 From: baymax254 at gmail.com (baymax Robo) Date: Mon, 5 Jun 2017 12:33:29 +0500 Subject: Couldn't get connectivity to Motorolla c118 on writing osmocombb In-Reply-To: References:

Message-ID: Thanks for responding Anton. I have attached putty output in email. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: puttyoutput.png Type: image/png Size: 12676 bytes Desc: not available URL: From antgorka at gmail.com Mon Jun 5 07:36:16 2017 From: antgorka at gmail.com (Anton Gorbachev) Date: Mon, 5 Jun 2017 10:36:16 +0300 Subject: Couldn't get connectivity to Motorolla c118 on writing osmocombb In-Reply-To: References:

Message-ID: You should not put images to maillists. And you didn't respond all other questions :) Please attach minicom output in text form here. And tell us which USB-TTL converter do you use. What is the chip? KR, Anton 2017-06-05 10:33 GMT+03:00 baymax Robo : > Thanks for responding Anton. I have attached putty output in email. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From baymax254 at gmail.com Mon Jun 5 07:50:37 2017 From: baymax254 at gmail.com (baymax Robo) Date: Mon, 5 Jun 2017 12:50:37 +0500 Subject: Couldn't get connectivity to Motorolla c118 on writing osmocombb In-Reply-To: References:

Message-ID: My USB-TTL is *CP2102 MODULES USB TO TTL.*My putty output is this.. I could't copy the text, therefore i attached the image. *?r??}?Q?Q :M????r??}?Q?Q* This alien-language text comes when i briefly press the power button. I have also tried using -m c123 but it is not working. On Mon, Jun 5, 2017 at 12:36 PM, Anton Gorbachev wrote: > You should not put images to maillists. > And you didn't respond all other questions :) > > Please attach minicom output in text form here. > And tell us which USB-TTL converter do you use. > What is the chip? > > KR, > Anton > > 2017-06-05 10:33 GMT+03:00 baymax Robo : > >> Thanks for responding Anton. I have attached putty output in email. >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Mon Jun 5 08:48:16 2017 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 5 Jun 2017 10:48:16 +0200 Subject: Couldn't get connectivity to Motorolla c118 on writing osmocombb In-Reply-To: References:

Message-ID: Does the phone have any operator branding by any chance ? like tracphone or other stuff that's not motorola ? Cheers, Sylvain From baymax254 at gmail.com Tue Jun 6 03:24:40 2017 From: baymax254 at gmail.com (baymax Robo) Date: Tue, 6 Jun 2017 08:24:40 +0500 Subject: Couldn't get connectivity to Motorolla c118 on writing osmocombb In-Reply-To: References:

Message-ID: No the phone has no operator branding. On Mon, Jun 5, 2017 at 1:48 PM, Sylvain Munaut <246tnt at gmail.com> wrote: > Does the phone have any operator branding by any chance ? like > tracphone or other stuff that's not motorola ? > > Cheers, > > Sylvain > -------------- next part -------------- An HTML attachment was scrubbed... URL: From baymax254 at gmail.com Wed Jun 7 06:34:55 2017 From: baymax254 at gmail.com (baymax Robo) Date: Wed, 7 Jun 2017 11:34:55 +0500 Subject: Couldn't get connectivity to Motorolla c118 on writing osmocombb In-Reply-To: References:

Message-ID: Hi, just found out this while surfing. It can be the problem of voltage, but when i checked via voltmeter; the voltage were as required i-e approx 3.3Volts. What can be other possible causes?? On Tue, Jun 6, 2017 at 8:24 AM, baymax Robo wrote: > No the phone has no operator branding. > > On Mon, Jun 5, 2017 at 1:48 PM, Sylvain Munaut <246tnt at gmail.com> wrote: > >> Does the phone have any operator branding by any chance ? like >> tracphone or other stuff that's not motorola ? >> >> Cheers, >> >> Sylvain >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thayyil at yandex.com Fri Jun 9 16:21:55 2017 From: thayyil at yandex.com (thayyil09 yil) Date: Fri, 09 Jun 2017 21:51:55 +0530 Subject: Osmocombb as a Zombie In-Reply-To: References: Message-ID: <106981497025315@web6g.yandex.ru> It's very hard for a non C coder to follow the flow.. yes its hard to follow without knowing hw and lowlevel C because lang C is not OOP supported so it makes difficulty representing concept is there someone that can help me in the Architectural level they have only few diagrams to show overview by that we cant understand code because code is not in OOP BUT one thing they seperated each c files for specific task like oop does for example transiver driver code is in rf folder and they added heading in each file for understanding its purpose From thayyil at yandex.com Fri Jun 9 16:27:57 2017 From: thayyil at yandex.com (thayyil09 yil) Date: Fri, 09 Jun 2017 21:57:57 +0530 Subject: Osmocombb with USRP In-Reply-To: References:

Message-ID: <114301497025677@web6g.yandex.ru> i did the search for more than a year none of them export to INDIA. i found 8$ like offers but only available in usa america like places are heaven for us.. From mychaela.falconia at gmail.com Fri Jun 9 17:15:21 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Fri, 9 Jun 2017 09:15:21 -0800 Subject: Osmocombb with USRP In-Reply-To: <114301497025677@web6g.yandex.ru> References:

<114301497025677@web6g.yandex.ru> Message-ID: On 6/9/17, thayyil09 yil wrote regarding Mot C1xx phone availability: > i did the search for more than a year > none of them export to INDIA. > > i found 8$ like offers but only available in usa > > america like places are heaven for us.. If you like, I would be glad to resell you some of the ebay-sourced C139 units in my stash (I have about 50 of them IIRC), and I won't have any problem with shipping to India or anywhere else in the world, but these C139 phones probably won't do you any good as they are all 850+1900 MHz units, whereas you probably need 900+1800 MHz in India. As I already mentioned, I do have a Calypso modem board of my own design and make (FreeCalypso FCDEV3B), primarily intended for running my own FreeCalypso firmware but also capable of running OsmocomBB just fine (certainly no worse than Mot C1xx phones), and it has a 900/1800/1900 MHz triband radio front-end. I am not yet at the point where I can sell these boards, but I am hoping to get there in another few months: I need to make another batch of boards first, and before I order the assembly of that next batch, I need to resolve all of the little issues found on the first batch. But these newly made FreeCalypso GSM MS development boards certainly won't be cheap; I have not yet figured out what the retail price will be, but I estimate somewhere around $500 USD. M~ From thayyil at yandex.com Fri Jun 9 18:04:32 2017 From: thayyil at yandex.com (thayyil09 yil) Date: Fri, 09 Jun 2017 23:34:32 +0530 Subject: Creating GSM Users Association (GSMUA) In-Reply-To: References: <20170529081407.deqbb2gdycpcf7uf@nataraja> Message-ID: <247401497031472@web42j.yandex.ru> michela are you kidding ( dont worrry iam a kid at twentees) calypso bb starts from leaked Docs ( if not sorry ) so why qcom code leak is ugly osmocom is for open softwear not for any specific hardware so keeping updated with mainstream hardware is the way so we may have to throw old one ( realy i never bcos i love it like my pet .old is Gold for me ) but in concept its the way ( hope you understand it ) greetings for your GSMUA . iam sure and will there for any help. i hope they will host your project. its happy to know your the mother of freecalypso. in softwear world you maybe first mom :) and i here for osmocom on qcom == osmodroidbb.wordpress.com if you mind helping me just put your hands on qcom leaked code i stucked at understanding code. still now i cant find where tmsi like layer3 things handling in qcom modem proc leaked code From thayyil at yandex.com Fri Jun 9 18:45:16 2017 From: thayyil at yandex.com (thayyil09 yil) Date: Sat, 10 Jun 2017 00:15:16 +0530 Subject: Osmocombb with USRP In-Reply-To: References:

<114301497025677@web6g.yandex.ru> Message-ID: <392751497033916@web36m.yandex.ru> > If you like, I would be glad to resell you some of the ebay-sourced > C139 units in my stash yes i want . price From mychaela.falconia at gmail.com Fri Jun 9 19:21:24 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Fri, 9 Jun 2017 11:21:24 -0800 Subject: Mot C139 phones (was: Osmocombb with USRP) Message-ID: > > If you like, I would be glad to resell you some of the ebay-sourced > > C139 units in my stash > > yes i want . price Hmm, I haven't really given it a serious thought until now. I can do $50 USD per phone plus an extra $50 USD for my time to pack the phone(s) in a box, take the box to the Post Office and fill out their customs forms, i.e., $100 for one phone, $150 for 2 phones, $200 for 3 phones etc. I do need to reiterate though that all of these C139 phones are the North American version and can only receive 850 and 1900 MHz bands, *not* 900 or 1800 MHz, thus I don't see how they can be useful to you in India if your local GSM services are in the bands which these phones can't receive. M~ From mychaela.falconia at gmail.com Sat Jun 10 02:18:37 2017 From: mychaela.falconia at gmail.com (Mychaela Falconia) Date: Fri, 9 Jun 2017 18:18:37 -0800 Subject: Creating GSM Users Association (GSMUA) In-Reply-To: <247401497031472@web42j.yandex.ru> References: <20170529081407.deqbb2gdycpcf7uf@nataraja> <247401497031472@web42j.yandex.ru> Message-ID: thayyil09 yil wrote: > michela are you kidding ( dont worrry iam a kid at twentees) Kidding about what? > calypso bb starts from leaked Docs ( if not sorry ) I don't know what you mean by "calypso bb", but OsmocomBB started from not only leaked docs, but also leaked *source code* for TI's original firmware for the chipset in question. Even though OsmocomBB people have chosen (for license worship reasons) not to make any direct reuse of TI's original code beyond a couple of L1 header files, they have extensively studied those TI firmware source leaks in order to gain the knowledge of how to operate the Calypso hardware and how to command the Calypso's DSP ROM to perform the functions it needs to perform for GSM functionality. See here for more juicy details regarding those two OsmocomBB L1 header files I just mentioned: https://www.freecalypso.org/pipermail/community/2017-April/000361.html > so why qcom code leak is ugly Where did I say that it is ugly? I have not yet had a chance to look at that QC code you keep talking about - I only downloaded it earlier today and don't have time currently to look at it in any depth, thus I am not qualified to judge whether it is ugly or beautiful or somewhere in between. > osmocom is for open softwear not for any specific hardware I am not a member of Osmocom, instead I lead my own project (FreeCalypso) in the same general space, hence the arguments regarding what Osmocom is or is not have no direct applicability to me or to my non-Osmocom project. > keeping updated with mainstream hardware is the way There is no such thing as "the way"; it may be YOUR way, but it is not *my* way. > its happy to know your the mother of freecalypso. > in softwear world you maybe first mom :) Well, some of us (me included) subscribe to the view that our poor planet is *way* overpopulated, hence engaging in biological procreation (imposing more living and resource-consuming humans on the poor planet) is akin to a crime. As a result, those of us with maternal instincts have to find a different outlet for those instincts, such as becoming the mother of a FLOSS project. :) Also leaders of FLOSS projects commonly take on titles such as principal developer, maintainer or even BDFL - but I prefer Mother. :) > and i here for osmocom on qcom == osmodroidbb.wordpress.com I assume you are talking about the QC source leak described on this page: http://syshwid.blogspot.in/2016/10/build-qualcomm-modem-msm8626.html (yes, I can read Russian just fine, it's one of my native languages) When you first posted about it back in April, I went to that page and the https://drop.me/B439WM mirror it talks about was down - appeared to have been taken down. But when I tried it again earlier today while in the process of composing this response to you, it worked, so I was finally able to download this QC source you've been talking about. However, even if this leak is 100% real source and not a semi-src (the Russian hacker says he was able to make a complete build from this source, but it doesn't mean that everything is really rebuilt from source - there could be major important pieces that are in the form of linkable binary objects, and it would take a lot of work to analyze the source to see which is the case), I have my doubts that this MSM8x26 platform would make a good replacement for FreeCalypso. I see the following (potential) problems: * According to the marketing info that I could easily find for this chip(set), it seems to be CDMA/3GPP2-oriented, which is not what I am interested in. That marketing info seems to imply that the chip supports UMTS/WCDMA too, but says nothing about GSM support. I principally refuse to use any chip, chipset or device that does not support GSM, i.e., I am potentially interested in having support for UMTS/WCDMA and maybe even LTE *in addition* to GSM/2G, but never instead of. Furthermore, one of my absolute requirements is to be able to invert the preference order for network search, i.e., have the modem always preferentially choose GSM/2G networks if such service is available, fall back to 3G/UMTS only if no GSM is available, and use LTE (or more properly VoLTE only, *without* LTE Internet service) only as the last resort when neither 2G nor 3G is available. * This MSM8x26 chip(set) has a ton of extra hardware for making those smartphones which I detest: 4 CPU cores, a powerful GPU and gawd knows what other crap. I desire a phone that can only make plain old phone calls and absolutely positively nothing else, based on a processor that has just enough horsepower to make those plain old phone calls and not one iota more, thus having all that extra application processor power would be a problem for me. * Where are the chip datasheets and reference board schematics and so forth that would be needed in order to make our own board with the chip(set) you are advocating for? Being able to build my own hardware starting from just chips is an absolute requirement for me, as I am NOT willing to use an Android slab phone, even it has a liberated baseband - I want a phone in my own personally preferred form factor (a "dumbphone" *without* Android), hence I need to be able to build my own hw in order to package it in the FF I desire. Overall, it is pretty clear to me that we are on different paths with very different interests and goals. M~ From laforge at gnumonks.org Sat Jun 10 09:15:28 2017 From: laforge at gnumonks.org (Harald Welte) Date: Sat, 10 Jun 2017 11:15:28 +0200 Subject: On using leaked source code (was Re: Creating GSM Users Association (GSMUA)) In-Reply-To: References: <20170529081407.deqbb2gdycpcf7uf@nataraja> <247401497031472@web42j.yandex.ru> Message-ID: <20170610091528.oqx2zh4tlhojgqwh@nataraja> Hi Mychaela, [this is getting slightly off-topic, so I'm removing the openbsc at lists.osmocom.org list] On Fri, Jun 09, 2017 at 06:18:37PM -0800, Mychaela Falconia wrote: > I don't know what you mean by "calypso bb", but OsmocomBB started from > not only leaked docs, but also leaked *source code* for TI's original > firmware for the chipset in question. Correct. As the given source code was proven on-line in the public for more than half a year, with thousands of downloads counted by the hosting platform, no copyright holder would still have had a valid claim that the information contained therein would be a "trade secret". So we could use the information learned from there, but we can of course not re-use any copyrightable portion of the code, as that would infringe on copyright. > Even though OsmocomBB people have chosen (for license worship reasons) > not to make any direct reuse of TI's original code [...] It doesn't matter what license we chose for our code. As soon as we incorporate copyrightable portions of third party source code without explicit permission of its copyright holder, we are in violation of copyright. That's both a civil and criminal offence in many jurisdictions, including those where the developers at the time (mostly EU) reside in. So our procedure was not "for license worship reasons", but for the simple reason that we wanted to ensure both our own personal freedom as well as the continued freedom of the code we wrote, with no attack surface for any copyright holder to take it down (and/or extort "damages" or the like). 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 thayyil at yandex.com Mon Jun 12 20:17:05 2017 From: thayyil at yandex.com (thayyil09 yil) Date: Tue, 13 Jun 2017 01:47:05 +0530 Subject: Mot C139 phones (was: Osmocombb with USRP) In-Reply-To: References: Message-ID: <3315981497298625@web19g.yandex.ru> > etc. > > all of these C139 phones are the only receive 850 and 1900 MHz bands, > *not* 900 or 1800 MHz, thus I don't see how they can be useful to you > in India if your local GSM services are in the bands which these > phones can't receive. oh sorry i forgot it . your right . here also 4g is working in frequency 2xxx ( they says 3g band sharing for 4g ) so mot cxx canceled . From thayyil at yandex.com Mon Jun 12 21:13:24 2017 From: thayyil at yandex.com (thayyil09 yil) Date: Tue, 13 Jun 2017 02:43:24 +0530 Subject: Creating GSM Users Association (GSMUA) In-Reply-To: References: <20170529081407.deqbb2gdycpcf7uf@nataraja> <247401497031472@web42j.yandex.ru> Message-ID: <3694761497302004@web28m.yandex.ru> > >>> it becomes offtopic sorry i will divert it now >i said kidding because i felt you worrried much like a kid :) sorry laugh it off > I don't know what you mean by "calypso bb", but OsmocomBB started while i writing your in mind so osmocom becomes calypso > But when I tried it again earlier today > while in the process of composing this response to you, thank you for spending your time on this > * According to the marketing info that I could easily find for this > chip(set), it seems to be CDMA/3GPP2-oriented, no it supports GSm . source contain gsm related files. and practical realworld chips used in sony and lg supports gsm > Being able to build my own > hardware starting from just chips is an absolute requirement for me, yes i got it .. your with a specific hardware . > Overall, it is pretty clear to me that we are on different paths with > very different interests and goals. sorry for last coments i mistaken you as osmocom member from starting. your right qcom leaks canot be complete replacement for calypso . but i suggested another way which dosent need datasheets or any hw info # i suggested to add a compatiblity layer on top of layer1 code of qcom leak . ( do we need hw info ) so layer2 3 of osmocombb can communicate with it.( if no hw specific info have to send recive) . i agree its not much usefull for hw geek because datasheets unavialable so custom board difficult (schematcs may avilabel because phones ) and in softwear side extending proprietery code and hosting only extended part related legal view is out of my knowlege. From axilirator at gmail.com Thu Jun 22 13:11:37 2017 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Thu, 22 Jun 2017 20:11:37 +0700 Subject: GR-GSM TRX In-Reply-To: References: <24ff07f7-6aae-a965-6b31-f39f495d0d3e@gmail.com> <4f4c5b88-9298-f889-cf6b-51394dca382b@gmail.com> <9e2324a4-3724-befa-988a-8239d17a4e55@gmail.com> <70bb1b58-ccaf-d6b6-6bba-6adf798df203@gmail.com>

Message-ID: Hi Piotr, I just wrote a simple (more or less working) GNURadio block for connection with OsmocomBB. It is named "TRX Interface" and currently only capable to transform (in Osmocom bursts are followed by a bit different header) and send received bursts through the UDP link. If you remember, I had a problem with UDP source port. So, I spent some time and finally solved this challenge. My first idea was to inherit the existing 'Socket PDU' implementation and I started to look for a way I could do that. After a few minutes of searching, I have found your mails with the same question, and a brief answer from Sylvain, that it is impossible :( So, I have copied actual implementation, stripped out everything related to TCP and implemented a feature to set UDP source port. Now I am able to receive all DL bursts, coming from GR-GSM to my trxcon application. At the moment I am working on TDMA scheduler, which is almost finished. It's time to start writing GR-GSM blocks for burst transmission. The following thoughts / questions are in my mind: - TX should be simpler than RX, because we don't need to detect bursts and correct any errors. - Both receiver and transmitter should be time synchronized. I think, the SCH clock from the 'GSM Receiver' block may be easily shared. Moreover, actual clock indications could be forwarded to my block. - If I am correct, to transmit a burst, one should be converted to symbols. How can we do that? - We cannot simply use the existing 'GMSK Mod' block, because GSM uses TDMA. Right? If so, point me to the right direction. P.S. This message is posted at the baseband-devel mailing list. With best regards, Vadim Yanitskiy. -------------- next part -------------- An HTML attachment was scrubbed... URL: