baseband-devel June 2017

baseband-devel@lists.osmocom.org

10 participants
13 discussions

Start a nNew thread

Engagetted !

by Sébastien Lorquet

http://www.engadget.com/2010/12/29/researchers-eavesdrop-on-encrypted-gsm-c… Congrats!

11 months, 3 weeks

Calypso BTS

by phreaker1983

I tried to install CalypsoBTS have libosmocore installed, osmo-bts osmobsc, libosmo-netif, libosmo-abis, ortp, trx, libosmo-dsp everything went without errors, following the instructions I created: touch ~/.osmocom/open-bsc.cfg , then when you run : osmo-nitb -c ~/.osmocom/open-bsc.cfg-l ~/.osmocom/hlr.sqlite3-P-C --debug=DRLL:CC:MM:RR:RSL:NM shows me:<0005> bsc_init.c:498 Failed to parse the config file: '/root/.osmocom/open-bsc.cfg' file tried to create as administrator but without success , pleas help me -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Calypso-BTS-tp4026753.html Sent from the baseband-devel mailing list archive at Nabble.com.

5 years, 11 months

OpenBTS OsmocomBB Asterisk

by trixbox.t

Hello! I Need Help I install these three programs OpenBTS, OsmocomBB, Asterisk Then run them, Everything works well OpenBTS sent an SMS to my phones I answered and he checked me I registered into OpenBTS a second phone I tried to transfer SMS between phones - all good but when I try to call from one to another I did not get Asterisk writes ================================================================ *CLI> Retransmission timeout reached on transmission 755803415(a)127.0.0.1 for seqno 179 (Critical Response) -- See wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 32001ms with no response ================================================================ Why? What do I do? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/OpenBTS-OsmocomBB-Asterisk-tp402… Sent from the baseband-devel mailing list archive at Nabble.com.

7 years, 3 months

Re: Phone not receiving calls

by Vadim Yanitskiy

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.

8 years, 2 months

Re: GR-GSM TRX

by Vadim Yanitskiy

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.

8 years, 2 months

Re: Couldn't get connectivity to Motorolla c118 on writing osmocombb

by Anton Gorbachev

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 <baymax254(a)gmail.com>: > 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 <antgorka(a)gmail.com> > 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 <baymax254(a)gmail.com>: >> >>> 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 <antgorka(a)gmail.com> >>> 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 <baymax254(a)gmail.com>: >>>> >>>>> 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 <antgorka(a)gmail.com> >>>>> 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 <baymax254(a)gmail.com>: >>>>>> >>>>>>> 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] >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >

8 years, 3 months

Creating GSM Users Association (GSMUA)

by Mychaela Falconia

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

8 years, 3 months

Mot C139 phones (was: Osmocombb with USRP)

by Mychaela Falconia

> > 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~

8 years, 4 months

Osmocombb with USRP

by Snehasish Kar

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

8 years, 4 months

Osmocombb as a Zombie

by Duarte

Hey guys, first of all I want to express my deep respect for this project, this is truly amazing project and very well developed. Second, I'm doing a few studies regarding GSM security (no, I'm not hacking.) and I need to develop a feature for osmocombb, which is: the ability to turn the L23 app as a zombie (C unix domain socket) waiting for instructions (e.g.: connect to the network with predefined parameters (IMSI), collect RAND, send sms,...). Is there any documentation or flow regarding the code? It's very hard for a non C coder to follow the flow... Or is there someone that can help me in the Architectural level? Thank you.

8 years, 4 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel June 2017