From wbg_1000 at yahoo.com Tue Jun 14 06:49:46 2011 From: wbg_1000 at yahoo.com (eisencah eisenach) Date: Mon, 13 Jun 2011 23:49:46 -0700 (PDT) Subject: mobile - making a call Message-ID: <248811.2332.qm@web112112.mail.gq1.yahoo.com> Hello everyone. After some more digging turns out that removing the "Status 1: 90 00"? from the firrmware the SIM response gets back to the upper layers. What I've also noticed is that when the SIM response wasn't getting to the mobile application a L1CTL_RESET was following. My question is : would this L1CTL_RESET have the effect of removing pending packets from the queue? Cause that would sort of explain why the delay introduced by the debug printing would influence the overall behaviour. Thanks, Mihai. --- On Sun, 5/15/11, eisencah eisenach wrote: From: eisencah eisenach Subject: Re: Fw: Re: mobile - making a call To: baseband-devel at lists.osmocom.org Date: Sunday, May 15, 2011, 5:52 PM Hi again. So after some digging I'm quite sure the ADPU response doesn't make it back into the upper layers. My question is , case the osmocon output contains some weird characters (see bellow), I should assume that at that point something went wrong with the serial link? Also is there some flag to compile the firmware such that the prints have no effect, as to offload the serial link? Thanks, Mihai. L1CTL_DATA_REQ (link_id=0x00) ul=00811fe0, ul->payload=00811fe4, data_ind=00811fe4, data_ind->data=00811fe4 l3h=00811fe4 SIM Request (7): a0 a4 00 00 02 6f 20 Status 2: 9F 0F SIM Request (5): a0 c0 00 00 0f Status 1: 90 00 SIM Request (14): a0 d6 00 00 09 ff 49 fd 1a 49 8f 70 00 01 Status 2: 90??????Q??????L1CTL_PARAM_REQ (ta=1, tx_power=6) L1CTL_DATA_REQ (link_id=0x00) ul=00811fe0, ul->payload=00811fe4, data_ind=00811fe4, data_ind->data=00811fe4 l3h=00811fe4 L1CTL_DATA_REQ (link_id=0x00) ul=008123c4, ul->payload=008123c8, data_ind=008123c8, data_ind->data=008123c8 l3h=008123c8 --- On Sat, 5/7/11, Sylvain Munaut <246tnt at gmail.com> wrote: From: Sylvain Munaut <246tnt at gmail.com> Subject: Re: Fw: Re: mobile - making a call To: "eisencah eisenach" Cc: baseband-devel at lists.osmocom.org Date: Saturday, May 7, 2011, 11:07 AM > So any ideea where to look for the answer to the UPDATE_BINARY message? No not really ... But there is a good reason the SIM driver is not in master ... it sucks at several level, including blocking behavior in interrupt context IIRC, so it's totally plausible your machine speed triggers some weird things. My advice would be to: - Cleanup the SIM driver - Bypass it in the code and try to access a real PCSC device locally rather than the built in SIM reader. Both are non-trivial of course. Cheers, ? ? Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at dodekatex.de Wed Jun 29 09:00:50 2011 From: lists at dodekatex.de (Philipp) Date: Wed, 29 Jun 2011 11:00:50 +0200 Subject: replacing the RX filter with a balun on the c139 In-Reply-To: <20110526200630.GA41133@thre.at> References: <20110526200630.GA41133@thre.at> Message-ID: <4E0AE9C2.4050300@dodekatex.de> Hi, On 26.05.2011 22:06, Joshua Lackey wrote: > I've been going over Sylvain's report on removing the RX filters, > http://www.246tnt.com/gsm/rx_filter.html, and I had some slight > differences on the c139 that I'm hoping someone can help me with. > this site is currently unavailable. Does anyone has a mirror? Thanks, Philipp From gyoutubeg at yahoo.com.br Thu Jun 30 10:54:24 2011 From: gyoutubeg at yahoo.com.br (Gerard) Date: Thu, 30 Jun 2011 10:54:24 +0000 (UTC) Subject: replacing the RX filter with a balun on the c139 References: <20110526200630.GA41133@thre.at> <4E0AE9C2.4050300@dodekatex.de> Message-ID: I have one PDF of this page, dont know how to post here. From drasko.draskovic at gmail.com Wed Jun 1 23:22:04 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Thu, 2 Jun 2011 01:22:04 +0200 Subject: Testing protocol stack with OsmocomBB (cheap way) In-Reply-To: <1306795368.15043.23.camel@deckard> References: <20110530085654.767746elephttr5i@email.ee.ethz.ch> <1306773998.9713.0.camel@deckard> <1306793904.15043.13.camel@deckard> <1306795368.15043.23.camel@deckard> Message-ID: On Tue, May 31, 2011 at 12:42 AM, Gianni Tedesco wrote: >> What troubles me the most is these kind of information that are >> missing, for example : >> - start this application first, then this one >> - LOST message is OK >> - there is no SIM simulated, and you can not do anything without SIM, >> which is not supported on the master >> - connect this to this to get logs in Wireshark >> - etc... >> >> Some kind of a tutorial that would prevent every starter to get stuck. > > Sure. Although it is a goal of the project to bring awareness, > knowledge, access to GSM to a wider audience, osmocom is still highly > experimental software and that means that to do anything useful with it > you are going to need to be very comfortable with figuring out these > sorts of issues anyway. I mean, at this stage it's still very much for > hackers who are ready to roll their sleeves up and get stuck in. Yes, this is basically my intention. But every beginning is hard ;). > I must say, ?I didn't even know of sylvains driver (non obvious branch > name) or cell_log and had to write my own SIM access code to get going - > it was a fun night :) What do you consider by this, i.e. what was exactly that you did ? Worked on the SIM controller driver or something else ? Can I reuse this approach to get things moving ? BR, Drasko From gianni at scaramanga.co.uk Thu Jun 2 06:06:57 2011 From: gianni at scaramanga.co.uk (Gianni Tedesco) Date: Thu, 02 Jun 2011 07:06:57 +0100 Subject: Testing protocol stack with OsmocomBB (cheap way) In-Reply-To: References: <20110530085654.767746elephttr5i@email.ee.ethz.ch> <1306773998.9713.0.camel@deckard> <1306793904.15043.13.camel@deckard> <1306795368.15043.23.camel@deckard> Message-ID: <1306994817.3628.0.camel@deckard> On Thu, 2011-06-02 at 01:22 +0200, Drasko DRASKOVIC wrote: > On Tue, May 31, 2011 at 12:42 AM, Gianni Tedesco > wrote: > >> What troubles me the most is these kind of information that are > >> missing, for example : > >> - start this application first, then this one > >> - LOST message is OK > >> - there is no SIM simulated, and you can not do anything without SIM, > >> which is not supported on the master > >> - connect this to this to get logs in Wireshark > >> - etc... > >> > >> Some kind of a tutorial that would prevent every starter to get stuck. > > > > Sure. Although it is a goal of the project to bring awareness, > > knowledge, access to GSM to a wider audience, osmocom is still highly > > experimental software and that means that to do anything useful with it > > you are going to need to be very comfortable with figuring out these > > sorts of issues anyway. I mean, at this stage it's still very much for > > hackers who are ready to roll their sleeves up and get stuck in. > Yes, this is basically my intention. But every beginning is hard ;). > > > I must say, I didn't even know of sylvains driver (non obvious branch > > name) or cell_log and had to write my own SIM access code to get going - > > it was a fun night :) > > What do you consider by this, i.e. what was exactly that you did ? > Worked on the SIM controller driver or something else ? > Can I reuse this approach to get things moving ? It's all on the mailing list and recent. Although I think Nico Golde's SAP driver is the way this is going to go. So if you need SIM and don't want to use the phone SIM, try that. Gianni From gianni at scaramanga.co.uk Thu Jun 2 07:41:13 2011 From: gianni at scaramanga.co.uk (Gianni Tedesco) Date: Thu, 02 Jun 2011 08:41:13 +0100 Subject: Testing protocol stack with OsmocomBB (cheap way) In-Reply-To: References: <20110530085654.767746elephttr5i@email.ee.ethz.ch> <1306773998.9713.0.camel@deckard> <1306793904.15043.13.camel@deckard> Message-ID: <1307000473.6137.3.camel@deckard> On Tue, 2011-05-31 at 00:31 +0200, Drasko DRASKOVIC wrote: > On Tue, May 31, 2011 at 12:18 AM, Gianni Tedesco > wrote: > > On Tue, 2011-05-31 at 00:05 +0200, Drasko DRASKOVIC wrote: > >> Hi Gianni, > >> after few hours of searching through the wiki pages, I have not been > >> able to find the document you were mentioning that would explain > >> attaching to cell and have some packet transfered through protocol > >> stack up to the Wireshark. > >> > >> Are you sure that this document still exist and not have been removed/replaced ? > >> > >> All I have found that can resemble is this : > >> http://bb.osmocom.org/trac/wiki/layer23 > >> but I guess that this is not what you are talking about, as it gives > >> no detailed instructions for the things I want to obtain (i.e. which > >> applications to start, in which order, what are things to observe, > >> etc...). > > > > Pretty much, but also look at the page for your specific phone model and > > http://bb.osmocom.org/trac/wiki/osmocon > > > > Basically you just need to use osmocon to load the layer1 firmware, > > power the phone up and then if 'mobile' (or whatever app you want) is > > running, it should be "all systems go". You can run > > mobile/cell_log/whatever before or after booting the phone and it'll be > > fine. > > > >> I tried some basic test by watching OsocomBB video presentations, as > >> these are closest instructions and recepies on tools usage I have > >> found to get one up and running, and I described troubles I have been > >> facing in previous mail - I tried to guess what can be the right > >> scenario as I find no docs, but I am still not able to synchronize to > >> any cell, nor have some packets coming... > > > > It's not a complicated scenario and is well explained on the wiki: > > > > We have a firmware for the phone that we compiled on the PC > > > > We have a data cable between phone and PC > > > > The firmware does low level things > > > > Other apps running on the PC do high level things (eg. mobile phone) > > > > We use a loader program (osmocon) to load the firmware from the PC on to > > the phone via the cable. > > > > After the firmware is running on the phone, we can run high level apps > > on the PC (mobile, cell_log, etc). > > > > The high level apps communicate to the phone via the communication > > channel setup by the loader. > > > > Most (all?) of the high level apps have a command line switch which > > tells them to transmit GSMTAP logs to a specific IP address. > > > > You can use tcpdump to capture the GSMTAP info and view it in wireshark. > > Yes, thanks. I gotten that. What I meant is more like some > instructions how to get the system running, this what I am trying to > achieve. Now, as you can see there is a lot of information spread all > around and I have hard time to get them together in a meaningful > picture. > > What troubles me the most is these kind of information that are > missing, for example : > - start this application first, then this one Actually, either way round should be fine. > - LOST message is OK Hmm, maybe this one is scary but there's a LOT of different messages. > - there is no SIM simulated, and you can not do anything without SIM, > which is not supported on the master True > - connect this to this to get logs in Wireshark Well OK, but if you've used tcpdump, wireshark etc. this is no big deal > - etc... I think we've covered it tbh > Some kind of a tutorial that would prevent every starter to get stuck. Ask Harald for wiki access and go for it. > Thanks for your help, things are beginning to be clearer. nps Gianni From drasko.draskovic at gmail.com Fri Jun 3 22:44:21 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Sat, 4 Jun 2011 00:44:21 +0200 Subject: Testing protocol stack with OsmocomBB (cheap way) In-Reply-To: <20110530085654.767746elephttr5i@email.ee.ethz.ch> References: <20110530085654.767746elephttr5i@email.ee.ethz.ch> Message-ID: On Mon, May 30, 2011 at 8:56 AM, wrote: > As this is all you want just use the signal from any commercial BTS in your > area. OsmocomBB is able to capture System Information Messages and Paging > Requests and forward the content to Wireshark. Hi weberbe, can you explain in some more details how this can be done ? So far I did not succeed to attach to any cell, not to get some packets from it. At which moment can we observe the packets which are coming : 1) During the initial measurements or 2) Only after we attach to a cell What should be set up, what applications run and in which order to obtain some packet logging in Wireshark. I am running master branch - so, no SIM working. Best regards, Drasko From weberbe at ee.ethz.ch Sun Jun 5 07:22:17 2011 From: weberbe at ee.ethz.ch (weberbe at ee.ethz.ch) Date: Sun, 05 Jun 2011 09:22:17 +0200 Subject: Testing protocol stack with OsmocomBB (cheap way) In-Reply-To: References: <20110530085654.767746elephttr5i@email.ee.ethz.ch> Message-ID: <20110605092217.53555uutr0zyhdwp@email.ee.ethz.ch> Hi Drasko I am not so sure why you are not succeeding in recording anything in wireshark. From what I have seen from your other posts you are doing it the right way. Well, here is what should happen anyway: 1) The phone measures the receive power of all the channels it can handle unless you specified to stick to a specific channel in the mobile application. 2) The channels with the highest receive power are most likely to be beacon carriers. So the phone will try to synchronize in frequency and time to such a carrier. The synchronization in time will retrieve the current frame number und the BSIC of the base station. 3) If the synchronization is successfull, the phone will monitor various logical channels on the beacon carrier: The broadcast control channel (BCCH), common control channel (CCCH) and the paging channel (PCH) (and maybe some more, I am not so sure). The packets received on these channels will be dumped on wireshark or whatever you are using. As soon as all system information (SI) messages from BCCH are decoded, the phone can camp on this cell. In order to achieve this you need osmocon, mobile and wireshark to be running. Hope this helps Ben Quoting "Drasko DRASKOVIC" : > On Mon, May 30, 2011 at 8:56 AM, wrote: >> As this is all you want just use the signal from any commercial BTS in your >> area. OsmocomBB is able to capture System Information Messages and Paging >> Requests and forward the content to Wireshark. > > Hi weberbe, > can you explain in some more details how this can be done ? > > So far I did not succeed to attach to any cell, not to get some > packets from it. > > At which moment can we observe the packets which are coming : > 1) During the initial measurements or > 2) Only after we attach to a cell > > What should be set up, what applications run and in which order to > obtain some packet logging in Wireshark. > > I am running master branch - so, no SIM working. > > Best regards, > Drasko > From weberbe at ee.ethz.ch Sun Jun 5 07:08:02 2011 From: weberbe at ee.ethz.ch (weberbe at ee.ethz.ch) Date: Sun, 05 Jun 2011 09:08:02 +0200 Subject: Invitation In-Reply-To: <4DE350C5.6090301@infosecurity.ch> References: <20110530090811.92964aoxdlov50t7@email.ee.ethz.ch> <4DE350C5.6090301@infosecurity.ch> Message-ID: <20110605090802.17833to6omcqfmtu@email.ee.ethz.ch> Hi naif As for now we are not publishing anything. Corresponding reports have first to be written. Ben Quoting "Fabio Pietrosanti (naif)" : > On 5/30/11 9:08 AM, weberbe at ee.ethz.ch wrote: >> Hi list >> >> First of all: Thanks to all of you who actively develop OsmocomBB. >> Second: In the past few months I worked on an interface between a GSM >> transceiver and ABB towards the mobile application from OsmocomBB. The >> findings will be presented Tuesday, May 31, 1.55 pm in ETZ J64 at ETH in >> Zurich (Gloriastrasse 35, 8092 Z?rich). You are all invited. >> The goal of this project was to understand the GSM protocol flow better >> in order to be able to extend the hardware towards higher layers. To >> this end, the mobile application (L2 and L3) was used. > > For who will not be able to be there to look the presentation in Zurich, > there will be a website with published papers / source codes about it? > > -naif > From holger at freyther.de Sun Jun 5 07:49:35 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Sun, 05 Jun 2011 09:49:35 +0200 Subject: Invitation In-Reply-To: <20110605090802.17833to6omcqfmtu@email.ee.ethz.ch> References: <20110530090811.92964aoxdlov50t7@email.ee.ethz.ch> <4DE350C5.6090301@infosecurity.ch> <20110605090802.17833to6omcqfmtu@email.ee.ethz.ch> Message-ID: <4DEB350F.9010901@freyther.de> On 06/05/2011 09:08 AM, weberbe at ee.ethz.ch wrote: > Hi naif > > As for now we are not publishing anything. Corresponding reports have first to > be written. What is the threat you are protecting against? From weberbe at ee.ethz.ch Sun Jun 5 09:03:43 2011 From: weberbe at ee.ethz.ch (weberbe at ee.ethz.ch) Date: Sun, 05 Jun 2011 11:03:43 +0200 Subject: Invitation In-Reply-To: <4DEB350F.9010901@freyther.de> References: <20110530090811.92964aoxdlov50t7@email.ee.ethz.ch> <4DE350C5.6090301@infosecurity.ch> <20110605090802.17833to6omcqfmtu@email.ee.ethz.ch> <4DEB350F.9010901@freyther.de> Message-ID: <20110605110343.193726db487pazcf@email.ee.ethz.ch> Hi Holger I am working at an university. Correspondingly, insights that are not ready to be published will have to wait for publication. A proper report is among other things missing at the moment in order to make a publication feasible. Ben Quoting "Holger Hans Peter Freyther" : > On 06/05/2011 09:08 AM, weberbe at ee.ethz.ch wrote: >> Hi naif >> >> As for now we are not publishing anything. Corresponding reports >> have first to >> be written. > > What is the threat you are protecting against? > From holger at freyther.de Sun Jun 5 09:31:09 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Sun, 05 Jun 2011 11:31:09 +0200 Subject: Invitation In-Reply-To: <20110605110343.193726db487pazcf@email.ee.ethz.ch> References: <20110530090811.92964aoxdlov50t7@email.ee.ethz.ch> <4DE350C5.6090301@infosecurity.ch> <20110605090802.17833to6omcqfmtu@email.ee.ethz.ch> <4DEB350F.9010901@freyther.de> <20110605110343.193726db487pazcf@email.ee.ethz.ch> Message-ID: <4DEB4CDD.6040303@freyther.de> On 06/05/2011 11:03 AM, weberbe at ee.ethz.ch wrote: > Hi Holger > > I am working at an university. Correspondingly, insights that are not ready to > be published will have to wait for publication. A proper report is among other > things missing at the moment in order to make a publication feasible. So you are afraid that if you publish code that someone else will come by, gets your code to run, knows which kind of measurements you did, reruns them, comes to a conclusion by himself and publishes faster than you do? From holger at freyther.de Sun Jun 5 12:16:38 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Sun, 05 Jun 2011 14:16:38 +0200 Subject: Invitation In-Reply-To: <4DEB4CDD.6040303@freyther.de> References: <20110530090811.92964aoxdlov50t7@email.ee.ethz.ch> <4DE350C5.6090301@infosecurity.ch> <20110605090802.17833to6omcqfmtu@email.ee.ethz.ch> <4DEB350F.9010901@freyther.de> <20110605110343.193726db487pazcf@email.ee.ethz.ch> <4DEB4CDD.6040303@freyther.de> Message-ID: <4DEB73A6.5090503@freyther.de> On 06/05/2011 11:31 AM, Holger Hans Peter Freyther wrote: > So you are afraid that if you publish code that someone else will come by, > gets your code to run, knows which kind of measurements you did, reruns them, > comes to a conclusion by himself and publishes faster than you do? And to keep it short. I am quite annoyed by (some) academics right now and wonder if we should somehow handle it with an official statement or change to the infrastructure. osmocom is certainly a Free Software/hacker project. I want to share my code because it just feels natural to do so and it is very enjoyable to work with clever and intelligent (human) beings! Now there is a group of people that are not Free Software developers and/or hackers, I don't mind if they lurk, take the code, play with it, run with it, in contrast I am happy if this code is useful to them. What I do mind is if someone is posing like he wants to be a member of our community, happily receives free support but when it comes to making a contribution, refuses to do so. comments? ideas? holger From squalyl at gmail.com Sun Jun 5 14:42:30 2011 From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=) Date: Sun, 5 Jun 2011 16:42:30 +0200 Subject: Invitation In-Reply-To: <4DEB73A6.5090503@freyther.de> References: <20110530090811.92964aoxdlov50t7@email.ee.ethz.ch> <4DE350C5.6090301@infosecurity.ch> <20110605090802.17833to6omcqfmtu@email.ee.ethz.ch> <4DEB350F.9010901@freyther.de> <20110605110343.193726db487pazcf@email.ee.ethz.ch> <4DEB4CDD.6040303@freyther.de> <4DEB73A6.5090503@freyther.de> Message-ID: not an active contributor, but you have my support on this matter. Sebastien On Sunday, June 5, 2011, Holger Hans Peter Freyther wrote: > On 06/05/2011 11:31 AM, Holger Hans Peter Freyther wrote: > >> So you are afraid that if you publish code that someone else will come by, >> gets your code to run, knows which kind of measurements you did, reruns them, >> comes to a conclusion by himself and publishes faster than you do? > > And to keep it short. I am quite annoyed by (some) academics right now and > wonder if we should somehow handle it with an official statement or change to > the infrastructure. > > osmocom is certainly a Free Software/hacker project. I want to share my code > because it just feels natural to do so and it is very enjoyable to work with > clever and intelligent (human) beings! > > Now there is a group of people that are not Free Software developers and/or > hackers, I don't mind if they lurk, take the code, play with it, run with it, > in contrast I am happy if this code is useful to them. What I do mind is if > someone is posing like he wants to be a member of our community, happily > receives free support but when it comes to making a contribution, refuses to > do so. > > comments? ideas? > > holger > > From drasko.draskovic at gmail.com Wed Jun 1 23:19:14 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Thu, 2 Jun 2011 01:19:14 +0200 Subject: Meaning of LOST message In-Reply-To: <20110531064402.GI14428@prithivi.gnumonks.org> References: <20110531064402.GI14428@prithivi.gnumonks.org> Message-ID: On Tue, May 31, 2011 at 8:44 AM, Harald Welte wrote: > Hi, > > On Mon, May 30, 2011 at 11:41:58PM +0200, Drasko DRASKOVIC wrote: > >> LOST 3054! >> >> What would this LOST 3054! say ? It does not sound good anyway, but at >> this point I am not skilled enough to read OsmocomBB logs. > > This is the output of some code I wrote a while ago in order to detect > when our CPU is too busy in the GSM L1 and thus looses one interrupt. > When we enter the L1S (synchronouos part of L1) in FIQ mode, further > FIQs are disabled and remain disabled until L1S returns from FIQ. > > If the overall time takes longer than the 4000 quarter-bit-clocks > between two TDMA interrupts, then we print that LOST message. > > However, the LOST detection logic is not 100% perfect, either. ?So if > you see the occasional message here and there it is fine. ?If you see a > sequence of them, I would say it is an indication of a problem. Hi Harald, thanks for this explanation. Seen that I had problems connecting, which seems to be due to missing SIM, I suspected on things. Since I do not have experience to dig into the logs yet, I asked for some explanations. This make it more clear, and I will investigate SIM problems now. BR, Drasko From rm.engineer84 at gmail.com Wed Jun 1 04:28:17 2011 From: rm.engineer84 at gmail.com (R M) Date: Wed, 1 Jun 2011 09:58:17 +0530 Subject: Memeories present in a mobile phone Message-ID: Hi, What sort of memories does a mobile phone have ? Do they have something like Flash, ROM and RAM or only Flash memory? Regards, RM From gianni at scaramanga.co.uk Wed Jun 1 04:57:48 2011 From: gianni at scaramanga.co.uk (Gianni Tedesco) Date: Wed, 01 Jun 2011 05:57:48 +0100 Subject: Memeories present in a mobile phone In-Reply-To: References: Message-ID: <1306904268.7096.2.camel@deckard> On Wed, 2011-06-01 at 09:58 +0530, R M wrote: > Hi, > > What sort of memories does a mobile phone have ? > > > Do they have something like Flash, ROM and RAM or only Flash memory? Flash, for firmware image etc. RAM because...well, what would it do without that? ROM... yeah all kinds of mask ROM's for the DSP etc. Don't forget the SIM card, it has probably the most important ROM... your encryption key. But you can find all this out from google, from the project wiki Gianni From rm.engineer84 at gmail.com Sat Jun 4 05:58:13 2011 From: rm.engineer84 at gmail.com (R M) Date: Sat, 4 Jun 2011 11:28:13 +0530 Subject: Memeories present in a mobile phone In-Reply-To: <1306904268.7096.2.camel@deckard> References: <1306904268.7096.2.camel@deckard> Message-ID: Hi, I just went through the wiki. From it I understand that DSP code is in mask rom. Does this mean we cannot change any DSP part of the system ? Regards, RM On 6/1/11, Gianni Tedesco wrote: > On Wed, 2011-06-01 at 09:58 +0530, R M wrote: >> Hi, >> >> What sort of memories does a mobile phone have ? >> >> >> Do they have something like Flash, ROM and RAM or only Flash memory? > > Flash, for firmware image etc. > > RAM because...well, what would it do without that? > > ROM... yeah all kinds of mask ROM's for the DSP etc. > > Don't forget the SIM card, it has probably the most important ROM... > your encryption key. > > But you can find all this out from google, from the project wiki > > Gianni > > From m.krupa at nafn.de Wed Jun 1 14:32:46 2011 From: m.krupa at nafn.de (Malte Krupa) Date: Wed, 1 Jun 2011 16:32:46 +0200 Subject: Compile error with gpsd 2.96 in layer23 Message-ID: <20110601143246.GG6751@blackbook> Dear folks, I recently played with osmocomBB and wanted to try out the cell_log and gsmmap feature. Therefore I tried to rebuild osmocomBB (sylvains testing tree) with gpsd 2.96 installed on archlinux kernel 2.6.38. If there is more information needed, just tell me! Error while "$make": Making all in src make[2]: Entering directory `/home/temal/dev/pkg/osmotemp/osmocom-bb/src/host/layer23/src' Making all in common make[3]: Entering directory `/home/temal/dev/pkg/osmotemp/osmocom-bb/src/host/layer23/src/common' CC l1ctl.o CC l1l2_interface.o CC sap_interface.o CC lapdm.o CC logging.o CC networks.o CC sim.o sim.c: In function ?gsm_sim_reply?: sim.c:146:11: warning: variable ?payload? set but not used [-Wunused-but-set-variable] CC sysinfo.o CC gps.o gps.c: In function ?osmo_gpsd_cb?: gps.c:73:2: error: too few arguments to function ?gps_waiting? /usr/include/gps.h:1435:13: note: declared here gps.c:77:2: warning: implicit declaration of function ?gps_poll? [-Wimplicit-function-declaration] gps.c: In function ?osmo_gpsd_open?: gps.c:114:2: error: too few arguments to function ?gps_open? /usr/include/gps.h:1430:12: note: declared here make[3]: *** [gps.o] Error 1 make[3]: Leaving directory `/home/temal/dev/pkg/osmotemp/osmocom-bb/src/host/layer23/src/common' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/temal/dev/pkg/osmotemp/osmocom-bb/src/host/layer23/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/temal/dev/pkg/osmotemp/osmocom-bb/src/host/layer23' make: *** [host/layer23/layer23] Error 2 From holger at freyther.de Wed Jun 1 15:21:22 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Wed, 01 Jun 2011 17:21:22 +0200 Subject: Compile error with gpsd 2.96 in layer23 In-Reply-To: <20110601143246.GG6751@blackbook> References: <20110601143246.GG6751@blackbook> Message-ID: <4DE658F2.2020505@freyther.de> On 06/01/2011 04:32 PM, Malte Krupa wrote: > Dear folks, > > I recently played with osmocomBB and wanted to try out the > cell_log and gsmmap feature. > Therefore I tried to rebuild osmocomBB (sylvains testing tree) with gpsd > 2.96 installed on archlinux kernel 2.6.38. > > If there is more information needed, just tell me! well, you could try to a) check the ChangeLog of GPSD if there was a change in the API. b) patch it. holger From konnew at gmx.de Tue Jun 28 03:49:40 2011 From: konnew at gmx.de (Konstantin Weitz) Date: Tue, 28 Jun 2011 03:49:40 +0000 (UTC) Subject: Compile error with gpsd 2.96 in layer23 References: <20110601143246.GG6751@blackbook> <4DE658F2.2020505@freyther.de> Message-ID: Holger Hans Peter Freyther freyther.de> writes: > > On 06/01/2011 04:32 PM, Malte Krupa wrote: > > Dear folks, > > > > I recently played with osmocomBB and wanted to try out the > > cell_log and gsmmap feature. > > Therefore I tried to rebuild osmocomBB (sylvains testing tree) with gpsd > > 2.96 installed on archlinux kernel 2.6.38. > > > > If there is more information needed, just tell me! > > well, you could try to > > a) check the ChangeLog of GPSD if there was a change in the API. > b) patch it. > > holger > > Apply this patch and it should work Change $REPLACE$ to b/src/host/layer23/src/common/gps.c before applying the patch From konnew at gmx.de Tue Jun 28 03:41:27 2011 From: konnew at gmx.de (Konstantin Weitz) Date: Mon, 27 Jun 2011 20:41:27 -0700 Subject: [PATCH] Updated GPS code so that it is compatible with new gpsd version. Message-ID: --- src/host/layer23/src/common/gps.c | 11 ++++++++--- 1 files changed, 8 insertions(+), 3 deletions(-) diff --git a/src/host/layer23/src/common/gps.c $REPLACE$ index 38aae2c..ffdaa1a 100644 --- a/src/host/layer23/src/common/gps.c +++ b/src/host/layer23/src/common/gps.c @@ -70,11 +70,14 @@ int osmo_gpsd_cb(struct osmo_fd *bfd, unsigned int what) goto gps_not_ready; /* gps has no data */ - if (gps_waiting(gdata)) + + // 10 seconds timeout, only place where + // logic was changed to upgrade to new gpsd + if (gps_waiting(gdata,10000000)) goto gps_not_ready; /* polling returned an error */ - if (gps_poll(gdata)) + if (gps_read(gdata)) goto gps_not_ready; /* data are valid */ @@ -111,7 +114,9 @@ int osmo_gpsd_open(void) gps_bfd.when = BSC_FD_READ; gps_bfd.cb = osmo_gpsd_cb; - gdata = gps_open(g.gpsd_host, g.gpsd_port); + gdata = malloc(sizeof(struct gps_data_t)); + + gps_open(g.gpsd_host, g.gpsd_port, gdata); if (gdata == NULL) { LOGP(DGPS, LOGL_ERROR, "Can't connect to gpsd\n"); return -1; -- 1.7.5.2 From holger at freyther.de Tue Jun 28 06:48:37 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Tue, 28 Jun 2011 08:48:37 +0200 Subject: Compile error with gpsd 2.96 in layer23 In-Reply-To: References: <20110601143246.GG6751@blackbook> <4DE658F2.2020505@freyther.de> Message-ID: <4E097945.4070805@freyther.de> On 06/28/2011 05:49 AM, Konstantin Weitz wrote: > Apply this patch and it should work > > Change $REPLACE$ to b/src/host/layer23/src/common/gps.c > before applying the patch > Will it work with gpsd < 2.96? My assumption is that it does not, would you mind making it work for before and after 2.96? holger From anoopbaskharan at gmail.com Thu Jun 2 00:39:42 2011 From: anoopbaskharan at gmail.com (Sam) Date: Thu, 02 Jun 2011 00:39:42 +0000 Subject: Participating in osmocombb development Message-ID: <4de6dbe2.8aecd80a.2c66.0311@mx.google.com> Hi, I would like to participate in the development of osmocomBB. I am communication engineer with good knowledge in EDGE/GPRS. With regards, Sam From laforge at gnumonks.org Thu Jun 2 18:33:35 2011 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 2 Jun 2011 20:33:35 +0200 Subject: Participating in osmocombb development In-Reply-To: <4de6dbe2.8aecd80a.2c66.0311@mx.google.com> References: <4de6dbe2.8aecd80a.2c66.0311@mx.google.com> Message-ID: <20110602183335.GM30930@prithivi.gnumonks.org> Hi Sam, On Thu, Jun 02, 2011 at 12:39:42AM +0000, Sam wrote: > I would like to participate in the development of osmocomBB. I am > communication engineer with good knowledge in EDGE/GPRS. Well, as of now we don't have any support for GPRS at all. Adding support for GPRS is a big task, as right now the scheduler in our L1 does only support classic circuit-switched GSM. So you would have to implement the GPRS (52 multiframe, ...) scheduling, as well as the RLC/MAC layer as a start. Have you been using OsmocomBB at all so far? If not, I strongly suggest you get a compatible phone and familiarize yourself with our tools, their usage and the software architecture. 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 drasko.draskovic at gmail.com Fri Jun 3 22:38:59 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Sat, 4 Jun 2011 00:38:59 +0200 Subject: Participating in osmocombb development In-Reply-To: <4de6dbe2.8aecd80a.2c66.0311@mx.google.com> References: <4de6dbe2.8aecd80a.2c66.0311@mx.google.com> Message-ID: On Thu, Jun 2, 2011 at 2:39 AM, Sam wrote: > Hi, > > I would like to participate in the development of osmocomBB. I am communication engineer with good knowledge in EDGE/GPRS. Hi Sam, I just posted some instructions as a response to mail sent by Pramod (similar inquery like yours). I hope you will benefit from this also. If you have further questions or need clarification, please do not hesitate to ask. On the other hand, I encourage you to share your beginning experiences and describe problems you are facing, so we can have a small base of references that helps people who are beginning with the project. Best regards, Drasko From pramodcs47 at gmail.com Thu Jun 2 02:43:32 2011 From: pramodcs47 at gmail.com (pramod krishna) Date: Thu, 2 Jun 2011 08:13:32 +0530 Subject: Interested to join the project Message-ID: HI This is pramod. I am currently working with mobile platforms. How can i contribute to your project or start working with your project. -- Pramod Be happy -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Thu Jun 2 18:31:36 2011 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 2 Jun 2011 20:31:36 +0200 Subject: Interested to join the project In-Reply-To: References: Message-ID: <20110602183135.GL30930@prithivi.gnumonks.org> Hi, On Thu, Jun 02, 2011 at 08:13:32AM +0530, pramod krishna wrote: > This is pramod. I am currently working with mobile platforms. How can i > contribute to your project or start working with your project. Well, usually you start by using + playing around with the existing code, i.e. getting a compatible phone, the right cable and get experience in using the various tools we provide. Once you have done that, you will probably run into some bugs or shortcomings that you can fix. You can start reading the code and understanding it. If at that point you need some more input into what needs to be done, we can giev you some specific tasks/assignments. Cheers, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From drasko.draskovic at gmail.com Fri Jun 3 22:34:43 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Sat, 4 Jun 2011 00:34:43 +0200 Subject: Interested to join the project In-Reply-To: References: Message-ID: On Thu, Jun 2, 2011 at 4:43 AM, pramod krishna wrote: > HI > ?This is pramod. I am currently working with mobile platforms. How can i > contribute to your project or start working with your project. Hi Pramod, I can list few instructions how to quickly start with OsmocomBB project : 1) Get one of supported target phones. This will be your dev-board. List of the phones can be found on the OsmocomBB site. I reccomend you to start with Motorola C123 as it is the project's primary target and it is probably best supported. 2) Get the appropriate CalypsoSerialCable, or T191 Unlock Cable (http://bb.osmocom.org/trac/wiki/CalypsoSerialCable) so you can connect your phone to the development host and upload your firmware. I suggest you USB variant, as I had problems with two RS232 models - none worked correctly giving 5V output instead of needed 3.3V. 3) Get crosss-compiler, if you not already have one. You can compile it your self (I personally prefer this method) - there various scripts and you can even use crosstool-ng for this (http://freshmeat.net/projects/crosstool-ng/). In any case you will find instructions here : http://bb.osmocom.org/trac/wiki/GnuArmToolchain 4) Get and build OsmocomBB with your new toolchain. Insrtuctions are here : http://bb.osmocom.org/trac/wiki/GettingStarted OK, now you are ready to start playing with OsmocomBB : 5) Check out if your equipment runs well by executing one Hello World on your phone. Locate osmocon program and do : $ ./osmocon -p /dev/ttyUSB1 -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin Now press shortly ON button on your phone (do not hold, you don't really want to turn it on and start phone's bootloader which will load the Motorola's soft). As you can see from the command line, I am using USB cable connected to my phone, and I am using Motorola C123. This loads hello_world binary into the RAM and execute it. You should see "Hello World" message on your display, which will flash. N.B :Press "ON/OFF" button to turn this OFF __before__ disconnecting from osmocon program ! 6) If all that works, you are ready to load some real protocol stack software. First : $ ./osmocon -p /dev/ttyUSB1 -m c123xor ../../target/firmware/board/compal_e88/layer1.compalram.bin (still do not press ON button) then : $ ./mobile -i 127.0.0.1 It wil open a Unix socket and will be ready to exchange messages with Layer1 phone in your RAM via RS232 cable. You can now press ON button (shortly, again), and system will start running - Layer1 will be uploaded to phone's RAM and mobile application will act as Layer23 part of the PS, getting all the measurements from neighbor cells, etc... 7) At this point you would probably want to telnet to OsmocomBB : $ telnet localhost 4247 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Welcome to the OsmocomBB control interface OsmocomBB> At this point probably nothing will work. It is because you either do not have SIM card inserted in your phone, or even if you have it - OsmocomBB code on the master branch has a broken SIM controller driver. You can get some more information here : http://bb.osmocom.org/trac/wiki/SIMReader At this point there are 3 existing strategies : 1. Check out Sylvain's testing branch for a working on-phone SIM driver 2. Use the SAP interface to a PC/SC smartcard reader with SIM inserted. 3. If you want to use GSM test set instead of real network, use test sim functionality of mobile Since option 3) is out of the question for me, because I do not have private GSM network, and option 1) seems more advanced soulution for what I want to obtain, I am trying at this point to investigate option 2), i.e. to use PC/SC smartcard reader with SIM inserted. Seems like you will need the SIM to get any signal routed through Wireshark, but I am not sure. I will have to post this question to the list and see if someone can help us from here on. I hope this helps, and I encourage you to share your experiences and beginner problems at this list, as I am doing. Many people who are starting with this project will surely benefit from these experiences, and do not expect more advanced hackers to write these long explanations - this should be done by the people who are catching up and are helping others catch up fast. Best regards, Drasko From drasko.draskovic at gmail.com Fri Jun 3 23:10:25 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Sat, 4 Jun 2011 01:10:25 +0200 Subject: Interested to join the project In-Reply-To: References: Message-ID: And yes, I just forgot, but I think it would be also very instructive for you to study some of these video presentations : 27c3: Running your own GSM stack on a phone : http://www.youtube.com/watch?v=ihbRtTzc0NI 25c3: Anatomy of smartphone hardware : http://www.youtube.com/watch?v=8eewZ6jkNyY&feature=related DEFCON 18: Practical Cellphone Spying : http://www.youtube.com/watch?v=wjYAAmHvt-g Intercepting GSM Traffic : http://vimeo.com/24117925 25c3: Running your own GSM network : http://www.youtube.com/watch?v=e_9hPRF5fzA&feature=related 27C3] (en) Wideband GSM Sniffing : http://www.youtube.com/watch?v=lsIriAdbttc Shmoocon 2010: GSM: SRSLY? : http://www.youtube.com/watch?v=bO5McFJBg6k&feature=related HAR 2009: Airprobe : http://www.youtube.com/watch?v=5NyH6HgjmKY&playnext=1&list=PLC202877A407A850E Black Hat USA 2010: Attacking GSM Base Station Systems and Mobile Phone Base Bands : http://www.youtube.com/watch?v=Cx8iWWg-Ch0&feature=related Blackhat 2010 Attacking Phone Privacy Karsten Nohl : http://www.youtube.com/watch?v=M-ooPfZcuGQ&feature=related HAR 2009: Cracking A5 GSM encryption : http://www.youtube.com/watch?v=inazpikhFtY&NR=1 LayerOne 2008 - David Hulton - Intercepting Mobile Phone/GSM : http://www.youtube.com/watch?v=U8VikEf-mdU&feature=related [27C3] (en) SMS-o-Death : http://www.youtube.com/watch?v=8bkg3AjY6fs&feature=related Brucon 2010: GSM security: fact and fiction : http://www.youtube.com/watch?v=MjD8nrMI8m0 and presentation slides for this one : http://www.google.fr/url?sa=t&source=web&cd=4&ved=0CC8QFjAD&url=http%3A%2F%2Fwww.cs.ru.nl%2F~fabianbr%2FBruCON_2010_-_GSM_Security_Fact_and_Fiction.pdf&ei=0GjpTe_qEomo8QPu1JGdAQ&usg=AFQjCNGQuR3NS5I39uOUjN506---E3qpmA&sig2=ujrqPKxtYlxYWIriQ0uXfw Some GSM lectures that might help : RohitAcademy : http://www.youtube.com/user/RohitAcademy#p/u This should give you a broader picture what is this about and quickly lead you to other sources... BR, Drasko On Sat, Jun 4, 2011 at 12:34 AM, Drasko DRASKOVIC wrote: > On Thu, Jun 2, 2011 at 4:43 AM, pramod krishna wrote: >> HI >> ?This is pramod. I am currently working with mobile platforms. How can i >> contribute to your project or start working with your project. > > Hi Pramod, > I can list few instructions how to quickly start with OsmocomBB project : > > 1) Get one of supported target phones. This will be your dev-board. > List of the phones can be found on the OsmocomBB site. I reccomend you > to start with Motorola C123 as it is the project's primary target and > it is probably best supported. > > 2) Get the appropriate CalypsoSerialCable, or T191 Unlock Cable > (http://bb.osmocom.org/trac/wiki/CalypsoSerialCable) so you can > connect your phone to the development host and upload your firmware. I > suggest you USB variant, as I had problems with two RS232 models - > none worked correctly giving 5V output instead of needed 3.3V. > > 3) Get crosss-compiler, if you not already have one. You can compile > it your self (I personally prefer this method) - there various scripts > and you can even use crosstool-ng for this > (http://freshmeat.net/projects/crosstool-ng/). In any case you will > find instructions here : > http://bb.osmocom.org/trac/wiki/GnuArmToolchain > > 4) Get and build OsmocomBB with your new toolchain. Insrtuctions are > here : http://bb.osmocom.org/trac/wiki/GettingStarted > > OK, now you are ready to start playing with OsmocomBB : > > 5) Check out if your equipment runs well by executing one Hello World > on your phone. Locate osmocon program and do : > $ ./osmocon -p /dev/ttyUSB1 -m c123xor > ../../target/firmware/board/compal_e88/hello_world.compalram.bin > > Now press shortly ON button on your phone (do not hold, you don't > really want to turn it on and start phone's bootloader which will load > the Motorola's soft). > > As you can see from the command line, I am using USB cable connected > to my phone, and I am using Motorola C123. This loads hello_world > binary into the RAM and execute it. You should see "Hello World" > message on your display, which will flash. > > N.B :Press "ON/OFF" button to turn this OFF __before__ disconnecting > from osmocon program ! > > 6) If all that works, you are ready to load some real protocol stack > software. First : > $ ./osmocon -p /dev/ttyUSB1 -m c123xor > ../../target/firmware/board/compal_e88/layer1.compalram.bin > (still do not press ON button) > then : > $ ./mobile -i 127.0.0.1 > It wil open a Unix socket and will be ready to exchange messages with > Layer1 phone in your RAM via RS232 cable. You can now press ON button > (shortly, again), and system will start running - Layer1 will be > uploaded to phone's RAM and mobile application will act as Layer23 > part of the PS, getting all the measurements from neighbor cells, > etc... > > 7) At this point you would probably want to telnet to OsmocomBB : > $ telnet localhost 4247 > Trying ::1... > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > Welcome to the OsmocomBB control interface > OsmocomBB> > > At this point probably nothing will work. It is because you either do > not have SIM card inserted in your phone, or even if you have it - > OsmocomBB code on the master branch has a broken SIM controller > driver. You can get some more information here : > http://bb.osmocom.org/trac/wiki/SIMReader > > At this point there are 3 existing strategies : > 1. Check out Sylvain's testing branch for a working on-phone SIM driver > 2. Use the SAP interface to a PC/SC smartcard reader with SIM inserted. > 3. If you want to use GSM test set instead of real network, use test sim > ?functionality of mobile > > Since option 3) is out of the question for me, because I do not have > private GSM network, and option 1) seems more advanced soulution for > what I want to obtain, I am trying at this point to investigate option > 2), i.e. to use PC/SC smartcard reader with SIM inserted. > > Seems like you will need the SIM to get any signal routed through > Wireshark, but I am not sure. I will have to post this question to the > list and see if someone can help us from here on. > > I hope this helps, and I encourage you to share your experiences and > beginner problems at this list, as I am doing. Many people who are > starting with this project will surely benefit from these experiences, > and do not expect more advanced hackers to write these long > explanations - this should be done by the people who are catching up > and are helping others catch up fast. > > Best regards, > Drasko > From jl at thre.at Thu Jun 2 20:11:48 2011 From: jl at thre.at (Joshua Lackey) Date: Thu, 2 Jun 2011 16:11:48 -0400 Subject: gsm850 and host/layer23/src/mobile Message-ID: <20110602201148.GA19279@thre.at> I'm having issues getting the mobile application to work and I'm wondering if this is a gsm850 problem. I have a couple of debugging ideas but I thought I would post here just in case the answer is obvious to someone else. I'm testing on both a c118 and a c139. I'm using the remotes/origin/sylvain/testing branch and this does have quadband support. I've edited target/firmware/Makefile and defined CONFIG_TX_ENABLE. I have a valid SIM in my phone that works with both phones using the default Motorola firmware. The 'sim reader 1' command is able to gather (most of) the necessary information. (The access class is not correctly read from the SIM but I haven't bothered tracking down why yet -- I just hardcoded an access class of 0xffff.) The mobile program correctly scans the frequency ranges and finds a good tower and then attempts to do a location update. It generates a RACH channel request and then (appears to) send it. The problem is that the phone never receives an immediate assignment response. The log shows multiple immediate assignments received, but none match the request reference (RA and FN the burst was sent in.) So it appears that the tower never receives the channel request I send. The only test I have done so far is to monitor the uplink frequency with a USRP (uhd_fft.py) during the location update procedure. It looks like the phone is actually transmitting at the correct times, but I am not positive. (I'd have to write some custom code before I can definitively say one way or the other.) The only other idea I have right now is that perhaps the timing advance calculation is incorrect. There are a couple of constants used without any explanation and I guess it is possible that these constants don't work for my configuration. I'm going to start going through these constants to determine if I can find a value that works. Any other ideas to try here? Anyone else gotten this to work in the US? From 246tnt at gmail.com Thu Jun 2 21:45:30 2011 From: 246tnt at gmail.com (246tnt at gmail.com) Date: Thu, 02 Jun 2011 21:45:30 +0000 Subject: gsm850 and host/layer23/src/mobile In-Reply-To: <20110602201148.GA19279@thre.at> Message-ID: <000e0cdff81c5714b104a4c18e08@google.com> Hi, > I'm testing on both a c118 and a c139. If they're natively 850 / 1900 you might need to change in src/target/firmware/board/compal/rffe_dualband.c , in the rffe_get_rx_ports(), replace the PORT_DCS1800 by PORT_PCS1900 (to indicate that the antenna high band output is connected to the RITA PCS port and not the DCS port ... It's a board variation not handled by the build system ...) But that shouldn't affect operation at 850. > I'm using the remotes/origin/sylvain/testing branch and this does have > quadband support. I've edited target/firmware/Makefile and defined > CONFIG_TX_ENABLE. Is it with a recent checkout ? In particular does it have this commit : 16ec2358a014f290be47e87e3489f98769681979 > The mobile program correctly scans the frequency ranges and finds a good > tower and then attempts to do a location update. It generates a RACH > channel request and then (appears to) send it. > The problem is that the phone never receives an immediate assignment > response. The log shows multiple immediate assignments received, but > none match the request reference (RA and FN the burst was sent in.) When I was in the US, I tested this and had the exact same problem, so when I came back I did some testing and found some wrong settings in the RFFE for the 850 band using a spectrum analyzer and I fixed them. But obviously I couldn't test with a real BTS (because I'm not in the US and the racal 6103e doesn't support GSM850) The main symptom was a very weak signal viewed by the spectrum analyzer ... but obviously the USRP can't actually "trigger" off a particular signal so I'm not sure if you can measure that. > The only test I have done so far is to monitor the uplink frequency with > a USRP (uhd_fft.py) during the location update procedure. It looks like > the phone is actually transmitting at the correct times, but I am not > positive. (I'd have to write some custom code before I can definitively > say one way or the other.) You might have to do that ... If you have two receive board you can probably capture the BCCH and uplink at the same time and if you do a time capture 'long enough' the RACH power spikes should be obvious. and then you can check where they are in relation to the FCCH. > The only other idea I have right now is that perhaps the timing advance > calculation is incorrect. There are a couple of constants used without > any explanation and I guess it is possible that these constants don't > work for my configuration. I'm going to start going through these > constants to determine if I can find a value that works. There is no timing advance whatsoever during a RACH ... Cheers, Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From jl at thre.at Thu Jun 2 23:13:33 2011 From: jl at thre.at (Joshua Lackey) Date: Thu, 2 Jun 2011 19:13:33 -0400 Subject: gsm850 and host/layer23/src/mobile In-Reply-To: <000e0cdff81c5714b104a4c18e08@google.com> References: <20110602201148.GA19279@thre.at> <000e0cdff81c5714b104a4c18e08@google.com> Message-ID: <20110602231333.GA27866@thre.at> Quoting 246tnt at gmail.com (246tnt at gmail.com): > >I'm testing on both a c118 and a c139. > > If they're natively 850 / 1900 you might need to change in > src/target/firmware/board/compal/rffe_dualband.c , in the > rffe_get_rx_ports(), replace the PORT_DCS1800 by PORT_PCS1900 (to indicate > that the antenna high band output is connected to the RITA PCS port and not > the DCS port ... It's a board variation not handled by the build system ...) Yep, did that. [...] > >I'm using the remotes/origin/sylvain/testing branch and this does have > >quadband support. I've edited target/firmware/Makefile and defined > >CONFIG_TX_ENABLE. > > Is it with a recent checkout ? > > In particular does it have this commit : > 16ec2358a014f290be47e87e3489f98769681979 Yes, it is current as of yesterday evening and has that commit. [...] > When I was in the US, I tested this and had the exact same problem, so when > I came back I did some testing and found some wrong settings in the RFFE > for the 850 band using a spectrum analyzer and I fixed them. Ah, good. It looks like you had to change trf6151_pll_tx() quite a bit. Is there anything there that you are unsure of? Something I can test? > But obviously I couldn't test with a real BTS (because I'm not in the US > and the racal 6103e doesn't support GSM850) I'll experiment with OpenBTS and try both GSM900 and GSM850 configurations. > The main symptom was a very weak signal viewed by the spectrum analyzer ... > but obviously the USRP can't actually "trigger" off a particular signal so > I'm not sure if you can measure that. Well, I can monitor the uplink frequency and compare the signal amplitude between the standard Motorola firmware and the osmocom code. If there is still a weak signal problem, it should be fairly obvious. > >The only test I have done so far is to monitor the uplink frequency with > >a USRP (uhd_fft.py) during the location update procedure. It looks like > >the phone is actually transmitting at the correct times, but I am not > >positive. (I'd have to write some custom code before I can definitively > >say one way or the other.) > > You might have to do that ... If you have two receive board you can > probably capture the BCCH and uplink at the same time and if you do a time > capture 'long enough' the RACH power spikes should be obvious. and then you > can check where they are in relation to the FCCH. > > > >The only other idea I have right now is that perhaps the timing advance > >calculation is incorrect. There are a couple of constants used without > >any explanation and I guess it is possible that these constants don't > >work for my configuration. I'm going to start going through these > >constants to determine if I can find a value that works. > > There is no timing advance whatsoever during a RACH ... Erm, yes. The timing advance is calculated from where the RACH is received. Thinking about it more, that code shouldn't be band-dependent anyway. If you have any other ideas, I'd be glad to test them out. I'll at least try the above and figure out how strong the tx signal is. Not sure what I can do after that though. From 246tnt at gmail.com Fri Jun 3 11:00:47 2011 From: 246tnt at gmail.com (246tnt at gmail.com) Date: Fri, 03 Jun 2011 11:00:47 +0000 Subject: gsm850 and host/layer23/src/mobile In-Reply-To: <20110602231333.GA27866@thre.at> Message-ID: <0015174c43427eecfa04a4ccaab1@google.com> Hi, > Ah, good. It looks like you had to change trf6151_pll_tx() quite a bit. > Is there anything there that you are unsure of? Something I can test? No, I looked at it again this morning and it looks fine. You can try to enable the warning (define at the top of the file) It shouldn't throw any (check that DCS is disabled in your mobile config or else it will throw some when doing power measurement in a bad band for your phone). > > But obviously I couldn't test with a real BTS (because I'm not in the US > > and the racal 6103e doesn't support GSM850) > I'll experiment with OpenBTS and try both GSM900 and GSM850 > configurations. Ah yes, I guess I could test with OpenBTS as well. > Well, I can monitor the uplink frequency and compare the signal > amplitude between the standard Motorola firmware and the osmocom code. > If there is still a weak signal problem, it should be fairly obvious. Yes, but with _fft software alone it's not easy because RACH is very short and so what you see on the screen is not really the power. A real analyzer can be set to trigger on power level to capture 'only' the RACH and analyze the power in that. A time graph might work tough. (or possibly waterfall with a very short fft size). > If you have any other ideas, I'd be glad to test them out. I'll at > least try the above and figure out how strong the tx signal is. Not > sure what I can do after that though. You can look at the parameter chosen in the trf pll settings (A / B / Band) and post them here along with the ARFCN so I can check if they've been selected correctly. I don't have much other ideas. Cheers, Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From karnatinagesh at gmail.com Fri Jun 3 10:20:39 2011 From: karnatinagesh at gmail.com (nagesh reddy) Date: Fri, 3 Jun 2011 15:50:39 +0530 Subject: Does any one know where can we get the old Motorola devices in bangalore(India). Message-ID: Hi All, i also wanted to contribute to this Project and already i had downloaded the source and started looking into the code. i want to test it on some device but i am not able to get the motorola devices here in India , bangalore. if anyone can help me in getting these devices it will be helpfull. regards, nageswara reddy. -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at freyther.de Fri Jun 3 18:37:19 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Fri, 03 Jun 2011 20:37:19 +0200 Subject: Searching for a studendt WAS( ANN: osmo-pcap a PCAP Client and Server application) In-Reply-To: <4DE8F080.1010002@freyther.de> References: <4DE8F080.1010002@freyther.de> Message-ID: <4DE929DF.3030205@freyther.de> On 06/03/2011 04:32 PM, Holger Hans Peter Freyther wrote: Hi all, I would like to get more students involved and would be interested in acting as a mentor. For the below osmo-pcap codebase I have a set of bite sized tasks (of different size) and it would be great if we could get some students to pick some of these. The only requirement should be interest to learn to program in C, some self motivation (e.g. use your favorite search engine before asking) but besides that the skills are not that important. cheers holger > Hi, > > I wrote a very primitive client and server for PCAP. The osmo_pcap_client will > use libpcap to sniff on a local link, we have the usual VTY interface to > configure it, one can change the filter and the device at runtime. > > There is also a very simple server that authenticates clients based on the > remote address, that will write the pcap files to disk. The files will be > rotated based on time and size, but also when the Link Header of a client is > changing. The traffic is not encrypted yet but that is on the todolist. > > The code can be found in our git repository[1]. > > holger > > [1] http://cgit.osmocom.org/cgit/osmo-pcap/ > From m.krupa at nafn.de Sat Jun 4 00:50:42 2011 From: m.krupa at nafn.de (Malte Krupa) Date: Sat, 4 Jun 2011 02:50:42 +0200 Subject: Searching for a studendt WAS( ANN: osmo-pcap a PCAP Client and Server application) In-Reply-To: <4DE929DF.3030205@freyther.de> References: <4DE8F080.1010002@freyther.de> <4DE929DF.3030205@freyther.de> Message-ID: <20110604005042.GA8807@blackbook.Speedport_W_504V_Typ_A> On Fri, Jun 03, 2011 at 08:37:19PM +0200, Holger Hans Peter Freyther wrote: On 06/03/2011 04:32 PM, Holger Hans Peter Freyther wrote: > > Hi all, > > I would like to get more students involved and would be interested in acting > as a mentor. For the below osmo-pcap codebase I have a set of bite sized tasks > (of different size) and it would be great if we could get some students to > pick some of these. Hi Holger, I'm a student and become more and more interested in the Osmocom(BB) project. I got the osmocomBB starter package (FTDI cable+Motorola/Compal C123) and try to write a patch for layer23+gpsd 2.96 at the moment. Ok, I'm trying to understand the existing code ... but I think I make some progress. ;) Also I got the possibility to lecture about OsmocomBB on monday in front of some students ... maybe one or two will be have a look at it. > > The only requirement should be interest to learn to program in C, some self > motivation (e.g. use your favorite search engine before asking) but besides > that the skills are not that important. > I've already completed the a first semester in C and assembly. My knowledge is limited but I'm very interested to learn more ... maybe because C++/Java bores me to death. Let me know if and how you want to start! Regards, Malte From dario.lombardo at libero.it Tue Jun 7 07:29:46 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Tue, 07 Jun 2011 09:29:46 +0200 Subject: Searching for a studendt WAS( ANN: osmo-pcap a PCAP Client and Server application) In-Reply-To: <20110604005042.GA8807@blackbook.Speedport_W_504V_Typ_A> References: <4DE8F080.1010002@freyther.de> <4DE929DF.3030205@freyther.de> <20110604005042.GA8807@blackbook.Speedport_W_504V_Typ_A> Message-ID: <4DEDD36A.6050201@libero.it> On 06/04/2011 02:50 AM, Malte Krupa wrote: > > Hi Holger, > > I'm a student and become more and more interested in the Osmocom(BB) project. > > I got the osmocomBB starter package (FTDI cable+Motorola/Compal C123) > and try to write a patch for layer23+gpsd 2.96 at the moment. Ok, I'm trying to > understand the existing code ... but I think I make some progress. ;) Hi I wrote the gpsd support, so I think I could give you some support about it. Another user noticed some kind of bug I didn't have time to debug/fix, so I appreciate if you take some time to test and fix it. Have a nice day Dario. From drasko.draskovic at gmail.com Fri Jun 3 23:41:28 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Sat, 4 Jun 2011 01:41:28 +0200 Subject: SIM related question Message-ID: Hi all, after loading L1 to RAM and starting mobile app, "show cell" is giving me : OsmocomBB# show cell 1 arfcn |MCC |MNC |LAC |cell ID|forb.LA|prio |min-db |max-pwr|rx-lev -------+-------+-------+-------+-------+-------+-------+-------+-------+------- and OsmocomBB# network search 1 logs : <0002> gsm322.c:3099 (ms 1) Event 'EVENT_USER_RESEL' for automatic PLMN selection in state 'A6 no SIM inserted' <0002> gsm322.c:3106 Event unhandled at this state. I have inserted SIM in the phone, and I know that SIM controller driver is not functional on the master branch. However, is there something that can be done even in this state to have some packet logging in Wireshark ? I.e. do we need SIM for any communication over Um. I guess not, and I want to start at this state, and observe some packets that are traversing the stack for educational reasons. Can somebody point me how this can be done (with current master and no SIM functional). Best regards, Drasko From gianni at scaramanga.co.uk Sat Jun 4 08:01:35 2011 From: gianni at scaramanga.co.uk (Gianni Tedesco) Date: Sat, 04 Jun 2011 09:01:35 +0100 Subject: SIM related question In-Reply-To: References: Message-ID: <1307174496.21711.3.camel@deckard> On Sat, 2011-06-04 at 01:41 +0200, Drasko DRASKOVIC wrote: > Hi all, > after loading L1 to RAM and starting mobile app, "show cell" is giving me : > > OsmocomBB# show cell 1 > arfcn |MCC |MNC |LAC |cell ID|forb.LA|prio |min-db |max-pwr|rx-lev > -------+-------+-------+-------+-------+-------+-------+-------+-------+------- > > and > > OsmocomBB# network search 1 > logs : > <0002> gsm322.c:3099 (ms 1) Event 'EVENT_USER_RESEL' for automatic > PLMN selection in state 'A6 no SIM inserted' > <0002> gsm322.c:3106 Event unhandled at this state. OK > I have inserted SIM in the phone, and I know that SIM controller > driver is not functional on the master branch. > > However, is there something that can be done even in this state to > have some packet logging in Wireshark ? Yes, the fact that you cannot subscribe to the network has nothing to do with the gsmtap stuff which happens at a lower level. > I.e. do we need SIM for any communication over Um. I guess not, and I > want to start at this state, and observe some packets that are > traversing the stack for educational reasons. You guess correctly. Did you try to capture the gsmtap packets already as I had described before? What happened? > Can somebody point me how this can be done (with current master and no > SIM functional). what valuye did you pass to mobile for the -i parameter? eg: mobile -i 224.0.0.1 then just tcpdump -s0 host 224.0.0.1 -w my-gsmptap-capture-file.pcap ... Gianni From drasko.draskovic at gmail.com Fri Jun 3 23:50:46 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Sat, 4 Jun 2011 01:50:46 +0200 Subject: Calypso JTAG Message-ID: Hi all, did anyone succeeded on attaching to JTAG port of Calypso ? I was looking at the docs here : http://bb.osmocom.org/trac/wiki/MotorolaC123, especially this : http://bb.osmocom.org/trac/attachment/wiki/MotorolaC123/compal_testpads.png, so I was wondering if someone has used JTAG, specifficaly with OpenOCD or UrJTAG ? I am planning to do some work on NuttX port, and I think that JTAG debugging would be very convenient for this kind of low level task. Also, I think that JTAG RAM flashing should be faster than current Osmocon RS232 method. Did anyone tried this and can osmocon be instructed that the code is already present in RAM, i.e. JTAG uploaded ? Best regards, Drasko From laforge at gnumonks.org Wed Jun 8 06:48:16 2011 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 8 Jun 2011 08:48:16 +0200 Subject: Calypso JTAG In-Reply-To: References: Message-ID: <20110608064816.GW12563@prithivi.gnumonks.org> On Sat, Jun 04, 2011 at 01:50:46AM +0200, Drasko DRASKOVIC wrote: > did anyone succeeded on attaching to JTAG port of Calypso ? > > I was looking at the docs here : > http://bb.osmocom.org/trac/wiki/MotorolaC123, especially this : > http://bb.osmocom.org/trac/attachment/wiki/MotorolaC123/compal_testpads.png, > so I was wondering if someone has used JTAG, specifficaly with OpenOCD > or UrJTAG ? I think I remember somebody had experimented with OpenOCD, and there was some problem related to the initial reset of the CPU. Something regarding the PLL setup, perhaps? But apart from that, it seemed to be working. (of course only on those phones that expose JTAG, which specifically is _not_ the C123 we have seen, but only C115, C117 and C155). I don't remember who did that, though. Let's hope they still read this list and respond separately. We didn't really make use of it as most people have C123, and also we have not really needed it during our development of the existing code. 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 drasko.draskovic at gmail.com Wed Jun 8 08:55:03 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Wed, 8 Jun 2011 10:55:03 +0200 Subject: Calypso JTAG In-Reply-To: <20110608064816.GW12563@prithivi.gnumonks.org> References: <20110608064816.GW12563@prithivi.gnumonks.org> Message-ID: On Wed, Jun 8, 2011 at 8:48 AM, Harald Welte wrote: > On Sat, Jun 04, 2011 at 01:50:46AM +0200, Drasko DRASKOVIC wrote: > >> did anyone succeeded on attaching to JTAG port of Calypso ? >> >> I was looking at the docs here : >> http://bb.osmocom.org/trac/wiki/MotorolaC123, especially this : >> http://bb.osmocom.org/trac/attachment/wiki/MotorolaC123/compal_testpads.png, >> so I was wondering if someone has used JTAG, specifficaly with OpenOCD >> or UrJTAG ? > > I think I remember somebody had experimented with OpenOCD, and there was > some problem related to the initial reset of the CPU. Something > regarding the PLL setup, perhaps? ?But apart from that, it seemed to be > working. Hi Harald, Good news. Normally PLL and RAM (and all other) configuration can be done by OpenOCD scripts just after reset (during reset-init procedure of OpenOCD). Since there is bootcode already implemented, it would should be a matter of rewriting this C/ASM initialization into OpenOCD Jim TCL start-up scripts (but I guess it is just a few reg writes...) > (of course only on those phones that expose JTAG, which specifically is > ?_not_ the C123 we have seen, Hmm... I was little bit confused so I needed clarification. When you say that C123 do not expose JTAG, what are then TDI, TDO and TMS pins here : http://bb.osmocom.org/trac/attachment/wiki/MotorolaC123/compal_testpads.png ? I thought that they are standard JTAG signals and that we can connect JTAG probe connector directly there. After that alls should work with OpenOCD because it have great support for ARM7TDMI. > but only C115, C117 and C155). I tried to look for a schematic for C115/C117, but link on Osmocom site seems to be dead : http://files.shrak-mobile.com/schem/motorola/C115_schem.rar I'll search on the net later this evening... > I don't remember who did that, though. ?Let's hope they still read this > list and respond separately. > > We didn't really make use of it as most people have C123, and also we > have not really needed it during our development of the existing code. Well, it is true that for PS development it is not essential. However, I think that for the platform development - RTOS, BSP/HAL, drivers, etc... it can be really handy. It is powerful tool, and it would be a shame not to use it if it is only a matter of soldering 5 pins... I am primarily looking at this for a OS porting/debugging purposes. BR, Drasko From laforge at gnumonks.org Wed Jun 8 12:52:48 2011 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 8 Jun 2011 14:52:48 +0200 Subject: Calypso JTAG In-Reply-To: References: <20110608064816.GW12563@prithivi.gnumonks.org> Message-ID: <20110608125248.GZ12563@prithivi.gnumonks.org> Hi Drasko, On Wed, Jun 08, 2011 at 10:55:03AM +0200, Drasko DRASKOVIC wrote: > > (of course only on those phones that expose JTAG, which specifically is > > ?_not_ the C123 we have seen, > > Hmm... I was little bit confused so I needed clarification. When you > say that C123 do not expose JTAG, what are then TDI, TDO and TMS pins > here : > http://bb.osmocom.org/trac/attachment/wiki/MotorolaC123/compal_testpads.png ? > I thought that they are standard JTAG signals and that we can connect > JTAG probe connector directly there. After that alls should work with > OpenOCD because it have great support for ARM7TDMI. Sorry, which part of the paragraph below the picture is unclear to you? ============== On the C123 the following pads are usable * TP27 -- DLPWR (download power on), connects to Iota:RPWON * TP14 -- RxD Modem * TP13 -- TxD Modem * TP9 -- CTS Modem * TP39 -- GND On most phones other pads are grounded and not usable (like in the scan above). Known exceptions * C115 and C117 have all test pads * C155 has JTAG but not IRDA UART test pads ============== 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 rm.engineer84 at gmail.com Sat Jun 4 06:18:47 2011 From: rm.engineer84 at gmail.com (R M) Date: Sat, 4 Jun 2011 11:48:47 +0530 Subject: Cygwin Windows --> Accessing serial port. Message-ID: Hi, I am trying out osmocombb code in dell laptop running windows 7. It does't contain serial ports. I am using a USB to serial converter instead. How can I access the usb port to which the USB to serial converter is attached in cygwin ? Can someone who has done this, help me in this ? Regards, RM From laforge at gnumonks.org Sat Jun 4 06:46:50 2011 From: laforge at gnumonks.org (Harald Welte) Date: Sat, 4 Jun 2011 08:46:50 +0200 Subject: Cygwin Windows --> Accessing serial port. In-Reply-To: References: Message-ID: <20110604064650.GG17178@prithivi.gnumonks.org> Hi! On Sat, Jun 04, 2011 at 11:48:47AM +0530, R M wrote: > I am using a USB to serial converter instead. How can I access the usb > port to which the USB to serial converter is attached in cygwin ? I think the quesetion is a generic cygwin / windows 7 question. It is probably better suited to a cygwin mailing list / forum than this list. All you need to know is the device name of usb-serial converters on widows 7 with cygwin. > Can someone who has done this, help me in this ? i have never heard of somebody doing this on windows 7. Almost everyone here uses Linux or MacOS. And the only prominent Windows user involved in the project is working with Windows XP. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From drasko.draskovic at gmail.com Sat Jun 4 07:28:42 2011 From: drasko.draskovic at gmail.com (Drasko DRASKOVIC) Date: Sat, 4 Jun 2011 09:28:42 +0200 Subject: Cygwin Windows --> Accessing serial port. In-Reply-To: <20110604064650.GG17178@prithivi.gnumonks.org> References: <20110604064650.GG17178@prithivi.gnumonks.org> Message-ID: On Sat, Jun 4, 2011 at 8:46 AM, Harald Welte wrote: >> Can someone who has done this, help me in this ? > > i have never heard of somebody doing this on windows 7. ?Almost everyone > here uses Linux or MacOS. ?And the only prominent Windows user involved > in the project is working with Windows XP. Hi RM, I guess that installing Linux at least in some virtual machine on your Windows box would save you the Cygwin troubles and help you focus more on the project itself, rather than waste time with your environment. BR, Drasko From spaar at mirider.augusta.de Sat Jun 4 09:42:09 2011 From: spaar at mirider.augusta.de (Dieter Spaar) Date: Sat, 04 Jun 2011 09:42:09 CEST Subject: Cygwin Windows --> Accessing serial port. Message-ID: <4de9fdf1.mirider@mirider.augusta.de> Hello Harald, On Sat, 4 Jun 2011 08:46:50 +0200, "Harald Welte" wrote: > > i have never heard of somebody doing this on windows 7. Almost everyone > here uses Linux or MacOS. And the only prominent Windows user involved > in the project is working with Windows XP. At least on my Cygwin installation under Windows XP the serial port is accessible as "/dev/ttySx" (x is "0" for COM1, "1" for COM2 and so on). All the USB to serial converters I am aware of are virtual COM ports on Windows which means that they are accessible the same way, e.g. if the virtual COM port is "COM7" it can be be accessed as "/dev/ttyS6", Best regards, Dieter -- Dieter Spaar, Germany spaar at mirider.augusta.de From rm.engineer84 at gmail.com Mon Jun 6 18:10:21 2011 From: rm.engineer84 at gmail.com (R M) Date: Mon, 6 Jun 2011 23:40:21 +0530 Subject: Cygwin Windows --> Accessing serial port. In-Reply-To: <4de9fdf1.mirider@mirider.augusta.de> References: <4de9fdf1.mirider@mirider.augusta.de> Message-ID: Hi, Thanks. I was able to access the serial port. I ran the following command ./osmocon -p /dev/ttyS5 -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin in cygwin I then held the power on button of the phone for some time. I got some output on the cygwin console.It isn't the expected output as per the wiki. After disconnecting, I tried to run the same command and nothing is happening. Can some one please suggest me what steps I need to take to solve the problem. I am using Motorola C115 phone. Regards, RM On Sat, Jun 4, 2011 at 12:12 PM, Dieter Spaar wrote: > Hello Harald, > > On Sat, 4 Jun 2011 08:46:50 +0200, "Harald Welte" > wrote: > > > > i have never heard of somebody doing this on windows 7. Almost everyone > > here uses Linux or MacOS. And the only prominent Windows user involved > > in the project is working with Windows XP. > > At least on my Cygwin installation under Windows XP the serial port > is accessible as "/dev/ttySx" (x is "0" for COM1, "1" for COM2 and > so on). All the USB to serial converters I am aware of are virtual > COM ports on Windows which means that they are accessible the same > way, e.g. if the virtual COM port is "COM7" it can be be accessed > as "/dev/ttyS6", > > Best regards, > Dieter > -- > Dieter Spaar, Germany spaar at mirider.augusta.de > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From john.otten at gd-ais.com Mon Jun 6 18:43:28 2011 From: john.otten at gd-ais.com (Otten, John E.) Date: Mon, 6 Jun 2011 13:43:28 -0500 Subject: Cygwin Windows --> Accessing serial port. In-Reply-To: References: <4de9fdf1.mirider@mirider.augusta.de> Message-ID: <30BDEE89A8C3644BB0CD6DD88B380F932AB2F795DD@EADC01-MABPRD01.ad.gd-ais.com> Don't hold the power on button. You should just press and release the power button to start the bootloader. Regards, John Hi, Thanks. I was able to access the serial port. I ran the following command ./osmocon -p /dev/ttyS5 -m c123xor ../../target/firmware/board/compal_e88/hello_world.compalram.bin in cygwin I then held the power on button of the phone for some time. I got some output on the cygwin console.It isn't the expected output as per the wiki. After disconnecting, I tried to run the same command and nothing is happening. Can some one please suggest me what steps I need to take to solve the problem. I am using Motorola C115 phone. Regards, RM On Sat, Jun 4, 2011 at 12:12 PM, Dieter Spaar > wrote: Hello Harald, On Sat, 4 Jun 2011 08:46:50 +0200, "Harald Welte" > wrote: > > i have never heard of somebody doing this on windows 7. Almost everyone > here uses Linux or MacOS. And the only prominent Windows user involved > in the project is working with Windows XP. At least on my Cygwin installation under Windows XP the serial port is accessible as "/dev/ttySx" (x is "0" for COM1, "1" for COM2 and so on). All the USB to serial converters I am aware of are virtual COM ports on Windows which means that they are accessible the same way, e.g. if the virtual COM port is "COM7" it can be be accessed as "/dev/ttyS6", Best regards, Dieter -- Dieter Spaar, Germany spaar at mirider.augusta.de -------------- next part -------------- An HTML attachment was scrubbed... URL: From rm.engineer84 at gmail.com Sun Jun 12 17:41:37 2011 From: rm.engineer84 at gmail.com (R M) Date: Sun, 12 Jun 2011 23:11:37 +0530 Subject: Cygwin Windows --> Accessing serial port. In-Reply-To: <30BDEE89A8C3644BB0CD6DD88B380F932AB2F795DD@EADC01-MABPRD01.ad.gd-ais.com> References: <4de9fdf1.mirider@mirider.augusta.de> <30BDEE89A8C3644BB0CD6DD88B380F932AB2F795DD@EADC01-MABPRD01.ad.gd-ais.com> Message-ID: Hi, I am a bit confused about the kind of cable I need to use. I have read the wiki about the calypso serial cable at http://bb.osmocom.org/trac/wiki/CalypsoSerialCable It says: The Calypso phones typically all have a serial port @ 3.3V levels on the 2.5mm earphone jack. Those cables are sometimes called *T191 unlock cable*. You can either buy ready-made cables, e.g. at: - USB variant - gsmliberty.net - fonefunshop.co.uk - gsmserver - RS232 variant, you still need a separate standard USB/RS232 cable - handy-style.de - cellcorner.com - USB/RS232 cable - tronisoft.com (FTDI and Prolific cables) If you click on cellcorner.com, you get a serial version of T191 unlock cable. I have purchased a similar cable not from that link but from a local shop near my home. (I am from India). The reason I have purchased the serial version is that the local shop only has the serial version. You have said in the wiki for the serial version, I still need a separate standard USB/RS232 cable. Why do I need a USB/RS232 cable ? If its a laptop, I can understand that they don't come with a serial port so you need the converter. Many PCs come with a serial port. Can I not connect the serial version of the T191 unlock cable to PC serial port? As far as I understand, the T191 unlock cable is used to convert RS232 signal level to 3.3V required by C128. I have a laptop and not a PC. It doesn't have a serial port. Since I was able to get hold of a serial version of T191 unlock cable as I told you in the begining of the mail, I also purchased a USB to Serial converter. Its a BAFO BF-810. Its based on Prolific chipset. So I connected first the USB/RS232 converter ju(BAFO BF-810) and then the serial version of the T191 unlock cable. Is this the right way ? OR Can I just connect the USB/R232 converter (based on Prolific chipset) and the use a cable which contains DB9 female on one side and 2.5mm jack on the other? I am asking the second question because you have mentioned in the wiki under Hints and Warnings like this: If you don't use a 3.3V (low voltage TTL, LVCMOS) serial port you can fry your phone! (internally, it connects to the IO-pins of the baseband processor which run at 2.8V). *Don't connect directly to your PCs serial port (running at +/- 12V!).* Regards, RM On Tue, Jun 7, 2011 at 12:13 AM, Otten, John E. wrote: > Don?t hold the power on button. You should just press and release the > power button to start the bootloader. > > > > Regards, > > John > > > > Hi, > > > > Thanks. > > I was able to access the serial port. > > > > I ran the following command > > > > ./osmocon -p /dev/ttyS5 -m c123xor > ../../target/firmware/board/compal_e88/hello_world.compalram.bin in cygwin > > > > I then held the power on button of the phone for some time. I got some > output on the cygwin console.It isn't the expected output as per the wiki. > > > > After disconnecting, I tried to run the same command and nothing is > happening. > > > > Can some one please suggest me what steps I need to take to solve the > problem. > > > > I am using Motorola C115 phone. > > > > Regards, > > RM > > On Sat, Jun 4, 2011 at 12:12 PM, Dieter Spaar > wrote: > > Hello Harald, > > > On Sat, 4 Jun 2011 08:46:50 +0200, "Harald Welte" > wrote: > > > > i have never heard of somebody doing this on windows 7. Almost everyone > > here uses Linux or MacOS. And the only prominent Windows user involved > > in the project is working with Windows XP. > > At least on my Cygwin installation under Windows XP the serial port > is accessible as "/dev/ttySx" (x is "0" for COM1, "1" for COM2 and > so on). All the USB to serial converters I am aware of are virtual > COM ports on Windows which means that they are accessible the same > way, e.g. if the virtual COM port is "COM7" it can be be accessed > as "/dev/ttyS6", > > Best regards, > Dieter > -- > Dieter Spaar, Germany spaar at mirider.augusta.de > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.huemer at xx.vu Sun Jun 12 18:20:53 2011 From: alexander.huemer at xx.vu (Alexander Huemer) Date: Sun, 12 Jun 2011 20:20:53 +0200 Subject: Cygwin Windows --> Accessing serial port. In-Reply-To: References: <4de9fdf1.mirider@mirider.augusta.de> <30BDEE89A8C3644BB0CD6DD88B380F932AB2F795DD@EADC01-MABPRD01.ad.gd-ais.com> Message-ID: <20110612182053.GB16178@de.xx.vu> On Sun, Jun 12, 2011 at 11:11:37PM +0530, R M wrote: > Why do I need a USB/RS232 cable ? > > If its a laptop, I can understand that they don't come with a serial port so > you need the converter. > > Many PCs come with a serial port. > > Can I not connect the serial version of the T191 unlock cable to PC serial > port? You could, but the RS232 ports that are often present on ATX-style mainboards provide 12V, which is too much for the phone. > > As far as I understand, the T191 unlock cable is used to convert RS232 > signal level to 3.3V required by C128. no. A serial T191 cable does nothing by itself. > > Since I was able to get hold of a serial version of T191 unlock cable as I > told you in the begining of the mail, I also purchased a USB to Serial > converter. Its a BAFO BF-810. > Its based on Prolific chipset. Unfortunately the prolific chips seem to not work as well for this purpose as the FTDI chips. > > So I connected first the USB/RS232 converter ju(BAFO BF-810) and then the > serial version of the T191 unlock cable. > > Is this the right way ? > OR > Can I just connect the USB/R232 converter (based on Prolific chipset) and > the use a cable which contains DB9 female on one side and 2.5mm jack on the > other? I don't get the difference between those two ways. > > I am asking the second question because you have mentioned in the wiki under > Hints and Warnings like this: > > If you don't use a 3.3V (low voltage TTL, LVCMOS) serial port you can fry > your phone! (internally, it connects to the IO-pins of the baseband > processor which run at 2.8V). *Don't connect directly to your PCs serial > port (running at +/- 12V!).* This warning wants to tell you that you should use a USB<-->RS232 converter and not use an onboard port of a PC. Kind regards -Alex From squalyl at gmail.com Sun Jun 12 18:53:49 2011 From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=) Date: Sun, 12 Jun 2011 20:53:49 +0200 Subject: Cygwin Windows --> Accessing serial port. In-Reply-To: <20110612182053.GB16178@de.xx.vu> References: <4de9fdf1.mirider@mirider.augusta.de> <30BDEE89A8C3644BB0CD6DD88B380F932AB2F795DD@EADC01-MABPRD01.ad.gd-ais.com> <20110612182053.GB16178@de.xx.vu> Message-ID: If you want to use a basic serial port, use a 3.3V version of the good ol' MAX232 (maybe MAX202? can't remember) Sebastien On Sun, Jun 12, 2011 at 8:20 PM, Alexander Huemer wrote: > On Sun, Jun 12, 2011 at 11:11:37PM +0530, R M wrote: > > Why do I need a USB/RS232 cable ? > > > > If its a laptop, I can understand that they don't come with a serial port > so > > you need the converter. > > > > Many PCs come with a serial port. > > > > Can I not connect the serial version of the T191 unlock cable to PC > serial > > port? > You could, but the RS232 ports that are often present on ATX-style > mainboards provide 12V, which is too much for the phone. > > > > As far as I understand, the T191 unlock cable is used to convert RS232 > > signal level to 3.3V required by C128. > no. A serial T191 cable does nothing by itself. > > > > Since I was able to get hold of a serial version of T191 unlock cable as > I > > told you in the begining of the mail, I also purchased a USB to Serial > > converter. Its a BAFO BF-810. > > Its based on Prolific chipset. > Unfortunately the prolific chips seem to not work as well for this > purpose as the FTDI chips. > > > > So I connected first the USB/RS232 converter ju(BAFO BF-810) and then > the > > serial version of the T191 unlock cable. > > > > Is this the right way ? > > OR > > Can I just connect the USB/R232 converter (based on Prolific chipset) and > > the use a cable which contains DB9 female on one side and 2.5mm jack on > the > > other? > I don't get the difference between those two ways. > > > > I am asking the second question because you have mentioned in the wiki > under > > Hints and Warnings like this: > > > > If you don't use a 3.3V (low voltage TTL, LVCMOS) serial port you can fry > > your phone! (internally, it connects to the IO-pins of the baseband > > processor which run at 2.8V). *Don't connect directly to your PCs serial > > port (running at +/- 12V!).* > This warning wants to tell you that you should use a USB<-->RS232 > converter and not use an onboard port of a PC. > > Kind regards > -Alex > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zachso at arcor.de Sun Jun 12 19:15:45 2011 From: zachso at arcor.de (Arne) Date: Sun, 12 Jun 2011 21:15:45 +0200 Subject: Cygwin Windows --> Accessing serial port. In-Reply-To: References: <4de9fdf1.mirider@mirider.augusta.de> <30BDEE89A8C3644BB0CD6DD88B380F932AB2F795DD@EADC01-MABPRD01.ad.gd-ais.com> <20110612182053.GB16178@de.xx.vu> Message-ID: <20110612211545.062d91ba@lucille.fritz.box> the 3v3 version of max232 is max3232, but this isnt what he needs. RM, you need a usb->RS232 only if you have no RS232 at one of you computers/notebooks available. if you have a normal RS232-port you have already everything you need and can use you cable bye arne On Sun, 12 Jun 2011 20:53:49 +0200 S?bastien Lorquet wrote: > If you want to use a basic serial port, use a 3.3V version of the > good ol' MAX232 (maybe MAX202? can't remember) > > Sebastien > > On Sun, Jun 12, 2011 at 8:20 PM, Alexander Huemer > wrote: > > > On Sun, Jun 12, 2011 at 11:11:37PM +0530, R M wrote: > > > Why do I need a USB/RS232 cable ? > > > > > > If its a laptop, I can understand that they don't come with a > > > serial port > > so > > > you need the converter. > > > > > > Many PCs come with a serial port. > > > > > > Can I not connect the serial version of the T191 unlock cable to > > > PC > > serial > > > port? > > You could, but the RS232 ports that are often present on ATX-style > > mainboards provide 12V, which is too much for the phone. > > > > > > As far as I understand, the T191 unlock cable is used to convert > > > RS232 signal level to 3.3V required by C128. > > no. A serial T191 cable does nothing by itself. > > > > > > Since I was able to get hold of a serial version of T191 unlock > > > cable as > > I > > > told you in the begining of the mail, I also purchased a USB to > > > Serial converter. Its a BAFO BF-810. > > > Its based on Prolific chipset. > > Unfortunately the prolific chips seem to not work as well for this > > purpose as the FTDI chips. > > > > > > So I connected first the USB/RS232 converter ju(BAFO BF-810) and > > > then > > the > > > serial version of the T191 unlock cable. > > > > > > Is this the right way ? > > > OR > > > Can I just connect the USB/R232 converter (based on Prolific > > > chipset) and the use a cable which contains DB9 female on one > > > side and 2.5mm jack on > > the > > > other? > > I don't get the difference between those two ways. > > > > > > I am asking the second question because you have mentioned in the > > > wiki > > under > > > Hints and Warnings like this: > > > > > > If you don't use a 3.3V (low voltage TTL, LVCMOS) serial port you > > > can fry your phone! (internally, it connects to the IO-pins of > > > the baseband processor which run at 2.8V). *Don't connect > > > directly to your PCs serial port (running at +/- 12V!).* > > This warning wants to tell you that you should use a USB<-->RS232 > > converter and not use an onboard port of a PC. > > > > Kind regards > > -Alex > > > > From rm.engineer84 at gmail.com Sat Jun 18 13:58:18 2011 From: rm.engineer84 at gmail.com (R M) Date: Sat, 18 Jun 2011 19:28:18 +0530 Subject: Cygwin Windows --> Accessing serial port. In-Reply-To: <20110612211545.062d91ba@lucille.fritz.box> References: <4de9fdf1.mirider@mirider.augusta.de> <30BDEE89A8C3644BB0CD6DD88B380F932AB2F795DD@EADC01-MABPRD01.ad.gd-ais.com> <20110612182053.GB16178@de.xx.vu> <20110612211545.062d91ba@lucille.fritz.box> Message-ID: Hi, If I have a prolific usb to serial converter can I be sure that the voltage levels that I get is 3.3V and not 5V. My serial cable seems to be fine. I have done a loopback test and its echoing whatever I have typed using hyperterminal. My mobile phone's audio jack is also fine. I am able to use the hands free feature and listen to the voice. I hence feel that the 2.5mm male connector of the serial cable is not properly connecting to the audio jack of the phone though it sits properly. Is there a way?I can rectify this without buying a new serial cable? Regards, RM On Mon, Jun 13, 2011 at 12:45 AM, Arne wrote: > > the 3v3 version of max232 is max3232, but this isnt what he needs. > > RM, you need a usb->RS232 only if you have no RS232 at one of you > computers/notebooks available. if you have a normal RS232-port you have > already everything you need and can use you cable > > bye > arne > > > On Sun, 12 Jun 2011 20:53:49 +0200 > S?bastien Lorquet wrote: > > > If you want to use a basic serial port, use a 3.3V version of the > > good ol' MAX232 (maybe MAX202? can't remember) > > > > Sebastien > > > > On Sun, Jun 12, 2011 at 8:20 PM, Alexander Huemer > > wrote: > > > > > On Sun, Jun 12, 2011 at 11:11:37PM +0530, R M wrote: > > > > Why do I need a USB/RS232 cable ? > > > > > > > > If its a laptop, I can understand that they don't come with a > > > > serial port > > > so > > > > you need the converter. > > > > > > > > Many PCs come with a serial port. > > > > > > > > Can I not connect the serial version of the T191 unlock cable to > > > > PC > > > serial > > > > port? > > > You could, but the RS232 ports that are often present on ATX-style > > > mainboards provide 12V, which is too much for the phone. > > > > > > > > As far as I understand, the T191 unlock cable is used to convert > > > > RS232 signal level to 3.3V required by C128. > > > no. A serial T191 cable does nothing by itself. > > > > > > > > Since I was able to get hold of a serial version of T191 unlock > > > > cable as > > > I > > > > told you in the begining of the mail, I also purchased a USB to > > > > Serial converter. Its a BAFO BF-810. > > > > Its based on Prolific chipset. > > > Unfortunately the prolific chips seem to not work as well for this > > > purpose as the FTDI chips. > > > > > > > > So I connected first the USB/RS232 converter ?ju(BAFO BF-810) and > > > > then > > > the > > > > serial version of the T191 unlock cable. > > > > > > > > Is this the right way ? > > > > ? ?OR > > > > Can I just connect the USB/R232 converter (based on Prolific > > > > chipset) and the use a cable which contains DB9 female on one > > > > side and 2.5mm jack on > > > the > > > > other? > > > I don't get the difference between those two ways. > > > > > > > > I am asking the second question because you have mentioned in the > > > > wiki > > > under > > > > Hints and Warnings like this: > > > > > > > > If you don't use a 3.3V (low voltage TTL, LVCMOS) serial port you > > > > can fry your phone! (internally, it connects to the IO-pins of > > > > the baseband processor which run at 2.8V). *Don't connect > > > > directly to your PCs serial port (running at +/- 12V!).* > > > This warning wants to tell you that you should use a USB<-->RS232 > > > converter and not use an onboard port of a PC. > > > > > > Kind regards > > > -Alex > > > > > > > > From rm.engineer84 at gmail.com Sat Jun 25 17:43:10 2011 From: rm.engineer84 at gmail.com (R M) Date: Sat, 25 Jun 2011 23:13:10 +0530 Subject: Cygwin Windows --> Accessing serial port. In-Reply-To: References: <4de9fdf1.mirider@mirider.augusta.de> <30BDEE89A8C3644BB0CD6DD88B380F932AB2F795DD@EADC01-MABPRD01.ad.gd-ais.com> <20110612182053.GB16178@de.xx.vu> <20110612211545.062d91ba@lucille.fritz.box> Message-ID: Hi Dieter, I was going through the archieves and I came across a mail that you sent on the topic of noisy cabe. I have copy pasted the msg below: My experience: I work under Windows with Cygwin so the OS internals how the serial port is handled are (totally) different than Linux. With the non-blocking variant of "osmocon" it was nearly impossible to download the code to the phone in a reliable way. So I had to apply an ugly hack to my version which basically switches the serial connection to "blocking mode" during the download phase. This way it works rather reliable here (regardless of using a "real" RS232 port or an USB to serial converter). So you might experience the same problem instead of a bad cable. You can try the attached patch to "osmocom.c". The patch is not for the latest GIT version, however it should be quite easy to apply it to the current on. Again, its an ugly hack, but it works for me. Best regards, Dieter I too work under cygwin environment but under windows 7. I am not able to download the code on to my phone though my cable seems to be fine. (I am using the Prolific USB to serial converter and have performed a loop back test to verfiy the cable) Can you please provide me the patch for the present version of osmocon.c as you mentioned in the mail as I am unable to apply the patch manually. Thanks and Regards, RM On Sat, Jun 18, 2011 at 7:28 PM, R M wrote: > Hi, > > If I have a prolific usb to serial converter can I be sure that the > voltage levels that I get is 3.3V and not 5V. > > My serial cable seems to be fine. I have done a loopback test and its > echoing whatever I have typed using hyperterminal. > > My mobile phone's audio jack is also fine. I am able to use the hands > free feature and listen to the voice. > > I hence feel that the 2.5mm male connector of the serial cable is not > properly connecting to the audio jack of the phone though it sits > properly. > > Is there a way?I can rectify this without buying a new serial cable? > > Regards, > RM > > On Mon, Jun 13, 2011 at 12:45 AM, Arne wrote: >> >> the 3v3 version of max232 is max3232, but this isnt what he needs. >> >> RM, you need a usb->RS232 only if you have no RS232 at one of you >> computers/notebooks available. if you have a normal RS232-port you have >> already everything you need and can use you cable >> >> bye >> arne >> >> >> On Sun, 12 Jun 2011 20:53:49 +0200 >> S?bastien Lorquet wrote: >> >> > If you want to use a basic serial port, use a 3.3V version of the >> > good ol' MAX232 (maybe MAX202? can't remember) >> > >> > Sebastien >> > >> > On Sun, Jun 12, 2011 at 8:20 PM, Alexander Huemer >> > wrote: >> > >> > > On Sun, Jun 12, 2011 at 11:11:37PM +0530, R M wrote: >> > > > Why do I need a USB/RS232 cable ? >> > > > >> > > > If its a laptop, I can understand that they don't come with a >> > > > serial port >> > > so >> > > > you need the converter. >> > > > >> > > > Many PCs come with a serial port. >> > > > >> > > > Can I not connect the serial version of the T191 unlock cable to >> > > > PC >> > > serial >> > > > port? >> > > You could, but the RS232 ports that are often present on ATX-style >> > > mainboards provide 12V, which is too much for the phone. >> > > > >> > > > As far as I understand, the T191 unlock cable is used to convert >> > > > RS232 signal level to 3.3V required by C128. >> > > no. A serial T191 cable does nothing by itself. >> > > > >> > > > Since I was able to get hold of a serial version of T191 unlock >> > > > cable as >> > > I >> > > > told you in the begining of the mail, I also purchased a USB to >> > > > Serial converter. Its a BAFO BF-810. >> > > > Its based on Prolific chipset. >> > > Unfortunately the prolific chips seem to not work as well for this >> > > purpose as the FTDI chips. >> > > > >> > > > So I connected first the USB/RS232 converter ?ju(BAFO BF-810) and >> > > > then >> > > the >> > > > serial version of the T191 unlock cable. >> > > > >> > > > Is this the right way ? >> > > > ? ?OR >> > > > Can I just connect the USB/R232 converter (based on Prolific >> > > > chipset) and the use a cable which contains DB9 female on one >> > > > side and 2.5mm jack on >> > > the >> > > > other? >> > > I don't get the difference between those two ways. >> > > > >> > > > I am asking the second question because you have mentioned in the >> > > > wiki >> > > under >> > > > Hints and Warnings like this: >> > > > >> > > > If you don't use a 3.3V (low voltage TTL, LVCMOS) serial port you >> > > > can fry your phone! (internally, it connects to the IO-pins of >> > > > the baseband processor which run at 2.8V). *Don't connect >> > > > directly to your PCs serial port (running at +/- 12V!).* >> > > This warning wants to tell you that you should use a USB<-->RS232 >> > > converter and not use an onboard port of a PC. >> > > >> > > Kind regards >> > > -Alex >> > > >> > > >> >> > From spaar at mirider.augusta.de Sat Jun 25 19:53:33 2011 From: spaar at mirider.augusta.de (Dieter Spaar) Date: Sat, 25 Jun 2011 19:53:33 CEST Subject: Cygwin Windows --> Accessing serial port. Message-ID: <4e063cbe.mirider@mirider.augusta.de> On Sat, 25 Jun 2011 23:13:10 +0530, "R M" wrote: > > Can you please provide me the patch for the present version of > osmocon.c as you mentioned in the mail as I am unable to apply the > patch manually. I don't have a patch for the current version as I currently don't work with OsmocomBB. Best regards, Dieter -- Dieter Spaar, Germany spaar at mirider.augusta.de From b.alecu at yahoo.com Sun Jun 5 08:58:16 2011 From: b.alecu at yahoo.com (Bogdan Alecu) Date: Sun, 5 Jun 2011 01:58:16 -0700 (PDT) Subject: Dialling in roaming Message-ID: <893675.90653.qm@web46216.mail.sp1.yahoo.com> Hello, I've noticed during some tests made with a SIM in roaming that when I called myself I see my local number showed instead of the E.164 format number. In Wireshark I see that the numbering plan is set to unknown in this case (but this happens only when I select a specific operator). I started then to dial local numbers (while in roaming) and I could call any local number, from any network, without having to use the country code. Is this something that operators do? Cheers, Bogdan -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Sun Jun 5 09:48:07 2011 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 5 Jun 2011 11:48:07 +0200 Subject: Dialling in roaming In-Reply-To: <893675.90653.qm@web46216.mail.sp1.yahoo.com> References: <893675.90653.qm@web46216.mail.sp1.yahoo.com> Message-ID: <20110605094806.GC3422@prithivi.gnumonks.org> Hi Bogdan, On Sun, Jun 05, 2011 at 01:58:16AM -0700, Bogdan Alecu wrote: > I've noticed during some tests made with a SIM in roaming that when I > called myself I see my local number showed instead of the E.164 format > number. In Wireshark I see that the numbering plan is set to unknown > in this case (but this happens only when I select a specific > operator). I started then to dial local numbers (while in roaming) and > I could call any local number, from any network, without having to use > the country code. Is this something that operators do? What you describe seems to be the normal behavior that I've seen ever since first using a GSM phone in something like 1995. Please remember, when you are on roaming you are part of the local network. So by default, you see the phone numbers like any normal home subscriber of that network. You are being served by the same MSC, only the authentication and billing is done via your home operator. This is why even back in the early 1990ies, the phone user manuals always suggested to store even domestic phone numbers always in the international format (+49... in my case). Because if you're on roaming to another country, you will have to use the prefix of your home country to still reach those numbers. CAMEL has the potential to have your home operator manipulate those numbers, but I'm not sure if anyone does that. 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 b.alecu at yahoo.com Sun Jun 5 10:05:31 2011 From: b.alecu at yahoo.com (Bogdan Alecu) Date: Sun, 5 Jun 2011 03:05:31 -0700 (PDT) Subject: Dialling in roaming In-Reply-To: <20110605094806.GC3422@prithivi.gnumonks.org> Message-ID: <307762.31759.qm@web46212.mail.sp1.yahoo.com> Hi Harald, What you say it's quite interesting because that does not happen all the times. In fact, I always thought that you should always dial with country code when in roaming, even if you are dialing the local numbers. Why that: because with other SIMs from my home country, being registered on another roaming network I wasn't able to dial local numbers. Also all of the operators say that you should always dial with the country code when in roaming, no matter the destination. --- On Sun, 6/5/11, Harald Welte wrote: From: Harald Welte Subject: Re: Dialling in roaming To: "Bogdan Alecu" Cc: baseband-devel at lists.osmocom.org Date: Sunday, June 5, 2011, 9:48 AM Hi Bogdan, On Sun, Jun 05, 2011 at 01:58:16AM -0700, Bogdan Alecu wrote: > I've noticed during some tests made with a SIM in roaming that when I > called myself I see my local number showed instead of the E.164 format > number. In Wireshark I see that the numbering plan is set to unknown > in this case (but this happens only when I select a specific > operator). I started then to dial local numbers (while in roaming) and > I could call any local number, from any network, without having to use > the country code. Is this something that operators do? What you describe seems to be the normal behavior that I've seen ever since first using a GSM phone in something like 1995. Please remember, when you are on roaming you are part of the local network.? So by default, you see the phone numbers like any normal home subscriber of that network.? You are being served by the same MSC, only the authentication and billing is done via your home operator. This is why even back in the early 1990ies, the phone user manuals always suggested to store even domestic phone numbers always in the international format (+49... in my case).? Because if you're on roaming to another country, you will have to use the prefix of your home country to still reach those numbers. CAMEL has the potential to have your home operator manipulate those numbers, but I'm not sure if anyone does that. Regards, ??? Harald -- - Harald Welte ? ? ? ? ???http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? (ETSI EN 300 175-7 Ch. A6) -------------- next part -------------- An HTML attachment was scrubbed... URL: From technosabby at gmail.com Wed Jun 8 11:13:16 2011 From: technosabby at gmail.com (Marten Christophe) Date: Wed, 8 Jun 2011 11:13:16 +0000 Subject: IP hacking.. Message-ID: Hello List, Sorry for out of scope question. Can any one suggest me community or mailing list for IP sniffing IP network hacking or account hacking, I'm planning to join for ethical hacking courses. Kind Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From karnatinagesh at gmail.com Wed Jun 8 11:28:15 2011 From: karnatinagesh at gmail.com (nagesh reddy) Date: Wed, 8 Jun 2011 16:58:15 +0530 Subject: Error while compiling the stack Message-ID: Hi, i am getting the below error when i try to compile the GSM stack sources. administrator at administrator-desktop:~/osmocom-bb/src$ make cd shared/libosmocore && autoreconf -i /bin/sh: autoreconf: not found make: *** [shared/libosmocore/configure] Error 127 can any one try to help me. regards, nagesh. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ml at mail.tsaitgaist.info Wed Jun 8 13:40:22 2011 From: ml at mail.tsaitgaist.info (tsaitgaist) Date: Wed, 08 Jun 2011 15:40:22 +0200 Subject: Error while compiling the stack In-Reply-To: References: Message-ID: <4DEF7BC6.8010606@mail.tsaitgaist.info> Hi, Please read the output > /bin/sh: autoreconf: not found autreconf is missing. install it kevin From eng_basemm at yahoo.com Sun Jun 12 15:20:53 2011 From: eng_basemm at yahoo.com (Basem Ahmed) Date: Sun, 12 Jun 2011 08:20:53 -0700 (PDT) Subject: Facing issues in using OSMOCOM Message-ID: <488627.55132.qm@web125902.mail.ne1.yahoo.com> Hi GNUGeeks, I am trying to use OSMOCOM project for calling purpose. I tried the current master and remotes/origin/sylvain/testing branch also. My Linux version is OpenSUSE 11.2 (2.6.31.5-0.1-default) and mobile model is C139. And we used the model c140xor in the loader osmocon loader command. I am able to download the loader.compalram.bin and layer1.compalram.bin and running the mobile project.? I am also using the telnet for configuration.? But it is stopping at following some state mentioned in attached file. Hoping to read soon from you guys. Regards,Basem -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Hi GNUGeeks.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 154817 bytes Desc: not available URL: From 246tnt at gmail.com Sun Jun 12 16:21:08 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sun, 12 Jun 2011 18:21:08 +0200 Subject: Facing issues in using OSMOCOM In-Reply-To: <458944.68910.qm@web125906.mail.ne1.yahoo.com> References: <458944.68910.qm@web125906.mail.ne1.yahoo.com> Message-ID: > How are you? Refer to below mail. I read the mailing list, please do not send to me directly. Only CC me (and CC, not a separate mail forward please) if you're posting a patch and you want me to review it and merge it. If I have an answer, I will answer ... (but in this case, from your description it seems like a 'mobile' problem which I virtually never use, so I may not have an answer at all) > I am able to download the loader.compalram.bin and layer1.compalram.bin and running the mobile project.? I am also using the telnet for configuration.? But it is stopping at following some state mentioned in attached file. Sorry, but if you attach .docx file, there is zero chance I'm gonna look at it. 1) .docx is a proprietary format, don't expect people can read it 2) Even if this was a open document ( .ods or so ), I don't use office suite at all. 3) A .txt attachement still requires me to download it and look at it ... 4) In general, to maximize your chance of getting an answer, you have to do your best to minimize the work to be done by the people you want to help you. In this particular case: - You properly included a description of your setup and up to where you got, that's great. - What's missing is a 'snippet' of the log with the 'state' it seems locked it. - Then at the end of the mail, cut and paste the complete logs (both from osmocon and from the mobile app). - If possible avoid HTML mail as well ... (don't take all this bad and/or personally, just trying to help you maximize your chance of getting the answers you're looking for). Cheers, Sylvain From squalyl at gmail.com Sun Jun 12 18:51:14 2011 From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=) Date: Sun, 12 Jun 2011 20:51:14 +0200 Subject: Facing issues in using OSMOCOM In-Reply-To: References: <458944.68910.qm@web125906.mail.ne1.yahoo.com> Message-ID: Hi, the 10-line contents in the docx file can be posted inline in a text-only email. No need for a hammer to crush a mosquito ;-) Sebastien On Sun, Jun 12, 2011 at 6:21 PM, Sylvain Munaut <246tnt at gmail.com> wrote: > > How are you? Refer to below mail. > > I read the mailing list, please do not send to me directly. Only CC me > (and CC, not a separate mail forward please) if you're posting a patch > and you want me to review it and merge it. > > If I have an answer, I will answer ... (but in this case, from your > description it seems like a 'mobile' problem which I virtually never > use, so I may not have an answer at all) > > > > I am able to download the loader.compalram.bin and layer1.compalram.bin > and running the mobile project. I am also using the telnet for > configuration. But it is stopping at following some state mentioned in > attached file. > > Sorry, but if you attach .docx file, there is zero chance I'm gonna look at > it. > > 1) .docx is a proprietary format, don't expect people can read it > 2) Even if this was a open document ( .ods or so ), I don't use office > suite at all. > 3) A .txt attachement still requires me to download it and look at it ... > 4) In general, to maximize your chance of getting an answer, you have > to do your best to minimize the work to be done by the people you want > to help you. In this particular case: > > - You properly included a description of your setup and up to where > you got, that's great. > - What's missing is a 'snippet' of the log with the 'state' it seems > locked it. > - Then at the end of the mail, cut and paste the complete logs (both > from osmocon and from the mobile app). > - If possible avoid HTML mail as well ... > > > (don't take all this bad and/or personally, just trying to help you > maximize your chance of getting the answers you're looking for). > > > Cheers, > > Sylvain > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From eng_basemm at yahoo.com Sun Jun 12 18:55:39 2011 From: eng_basemm at yahoo.com (Basem Ahmed) Date: Sun, 12 Jun 2011 11:55:39 -0700 (PDT) Subject: Facing issues in using OSMOCOM In-Reply-To: Message-ID: <275898.42371.qm@web125910.mail.ne1.yahoo.com> Dear All, sorry for the previous mistake .Actually I am trying to run the Mobile project but i have some issues there .let me telling you all the procedures i made : 1-git clone the osmocom project2-make the checkout (git checkout origin/sylvain/testing )3-compiling the project(it works after some modification of TX transmitter enable)4-run the loader.compalram.bin(running perfectly)5-run the layer1.comalram.bin6-run telnet localhost and enabling the ms 17-run the mobile the project8-press the power on buttonsfor mobile application ? ?===>it keeps running perfectly exactly as you did in the demo and its says it complete reading the SIM and giving my?network?name but it stop before checking the?network?signals ?at the line:selection network(mcc=420 aljawal ?)start stored cell selection<003> gsm322.c:559 new state 'C0 null' ->'C2 stored cell Selection' .for the layer1 application===>it downloading successfully and it keeps?synchronized?with mobile application keep SIM requesting till the line:sim request (5): a0 b0 00 00 0cStaus 1:90 00 Hoping to hear from you soon. regard,--- On Sun, 6/12/11, Sylvain Munaut <246tnt at gmail.com> wrote: From: Sylvain Munaut <246tnt at gmail.com> Subject: Re: Facing issues in using OSMOCOM To: "Basem Ahmed" , "baseband-devel" Date: Sunday, June 12, 2011, 7:21 PM > How are you? Refer to below mail. I read the mailing list, please do not send to me directly. Only CC me (and CC, not a separate mail forward please) if you're posting a patch and you want me to review it and merge it. If I have an answer, I will answer ...? (but in this case, from your description it seems like a 'mobile' problem which I virtually never use, so I may not have an answer at all) > I am able to download the loader.compalram.bin and layer1.compalram.bin and running the mobile project.? I am also using the telnet for configuration.? But it is stopping at following some state mentioned in attached file. Sorry, but if you attach .docx file, there is zero chance I'm gonna look at it. 1) .docx is a proprietary format, don't expect people can read it 2) Even if this was a open document ( .ods or so ), I don't use office suite at all. 3) A .txt attachement still requires me to download it and look at it ... 4) In general, to maximize your chance of getting an answer, you have to do your best to minimize the work to be done by the people you want to help you. In this particular case: - You properly included a description of your setup and up to where you got, that's great. - What's missing is a 'snippet' of the log with the 'state' it seems locked it. - Then at the end of the mail, cut and paste the complete logs (both from osmocon and from the mobile app). - If possible avoid HTML mail as well ... (don't take all this bad and/or personally, just trying to help you maximize your chance of getting the answers you're looking for). Cheers, ? ? Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From eng_basemm at yahoo.com Mon Jun 13 08:41:12 2011 From: eng_basemm at yahoo.com (Basem Ahmed) Date: Mon, 13 Jun 2011 01:41:12 -0700 (PDT) Subject: Facing issues in using OSMOCOM Message-ID: <957351.22759.qm@web125908.mail.ne1.yahoo.com> Hi All GNUMonks, I am adding the log output here for reference as suggesed by Sylvain: Mobile Output: <000e> sim.c:949 command successfull <000e> sim.c:571 GET RESPONSE (len=19) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0) <000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:277 READ BINARY (offset=0 len=2) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0) <000e> sim.c:876 received APDU (len=2 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:151 sending result to callback function (type=0) <0004> subscriber.c:442 received ACC 0040 from SIM <0004> subscriber.c:556 Requesting SIM file 0x6f7b <000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000e> sim.c:241 SELECT (file=0x6f7b) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4) <000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13) <000e> sim.c:949 command successfull <000e> sim.c:571 GET RESPONSE (len=19) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0) <000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:277 READ BINARY (offset=0 len=12) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0) <000e> sim.c:876 received APDU (len=12 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:151 sending result to callback function (type=0) <0004> subscriber.c:518 (ms 1) Done reading SIM card (IMSI=420012300358346 Saudi Arabia, Al Jawal) <0004> subscriber.c:530 -> SIM card registered to 420 01 (Saudi Arabia, Al Jawal) <0004> gsm48_mm.c:4160 (ms 1) Received 'MMR_REG_REQ' event <0002> gsm322.c:3176 (ms 1) Event 'EVENT_SIM_INSERT' for automatic PLMN selection in state 'A0 null' <000d> gsm322.c:1090 Start search of last registered PLMN (mcc=420 mnc=01? Saudi Arabia, Al Jawal) <0002> gsm322.c:1094 Use RPLMN (mcc=420 mnc=01? Saudi Arabia, Al Jawal) <0002> gsm322.c:530 new state 'A0 null' -> 'A1 trying RPLMN' <0003> gsm322.c:3396 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in state 'C0 null' <000d> gsm322.c:3007 Selecting network (mcc=420 mnc=01? Saudi Arabia, Al Jawal) <0003> gsm322.c:3013 Start stored cell selection. <0003> gsm322.c:559 new state 'C0 null' -> 'C2 stored cell selection' Layer1: Output read_file(../../target/firmware/board/compal_e86/layer1.compalram.bin): file_size=54736, hdr_len=4, dnload_len=54743 got 1 bytes from modem, data looks like: 1b? . got 1 bytes from modem, data looks like: f6? . got 1 bytes from modem, data looks like: 02? . got 1 bytes from modem, data looks like: 00? . got 1 bytes from modem, data looks like: 41? A got 1 bytes from modem, data looks like: 02? . got 1 bytes from modem, data looks like: 43? C Received PROMPT2 from phone, starting download handle_write(): 4096 bytes (4096/54743) handle_write(): 4096 bytes (8192/54743) handle_write(): 4096 bytes (12288/54743) handle_write(): 4096 bytes (16384/54743) handle_write(): 4096 bytes (20480/54743) handle_write(): 4096 bytes (24576/54743) handle_write(): 4096 bytes (28672/54743) handle_write(): 4096 bytes (32768/54743) handle_write(): 4096 bytes (36864/54743) handle_write(): 4096 bytes (40960/54743) handle_write(): 4096 bytes (45056/54743) handle_write(): 4096 bytes (49152/54743) handle_write(): 4096 bytes (53248/54743) handle_write(): 1495 bytes (54743/54743) handle_write(): finished got 1 bytes from modem, data looks like: 1b? . got 1 bytes from modem, data looks like: f6? . got 1 bytes from modem, data looks like: 02? . got 1 bytes from modem, data looks like: 00? . got 1 bytes from modem, data looks like: 41? A got 1 bytes from modem, data looks like: 03? . got 1 bytes from modem, data looks like: 42? B Received DOWNLOAD ACK from phone, your code is running now! OSMOCOM Layer 1 (revision osmocon_v0.0.0-906-g5bbea93-modified) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: e144263d880014fd ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== Power up simcard: Assert DSP into Reset Releasing DSP from Reset Setting some dsp_api.ndb values Setting API NDB parameters DSP Download Status: 0x0001 DSP API Version: 0x0000 0x0000 Finishing download phase DSP Download Status: 0x0002 DSP API Version: 0x3606 0x0000 LOST 1174! SIM Request (7): a0 a4 00 00 02 3f 00 Status 2: 9F 23 SIM Request (5): a0 c0 00 00 23 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 2f e2 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 0a Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 7f 20 Status 2: 9F 23 SIM Request (5): a0 c0 00 00 23 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 07 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 09 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 7e Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 0b Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 3f 00 Status 2: 9F 23 SIM Request (5): a0 c0 00 00 23 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 7f 10 Status 2: 9F 23 SIM Request (5): a0 c0 00 00 23 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 40 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 84 Status 1: 94 08 SIM Request (7): a0 a4 00 00 02 3f 00 Status 2: 9F 23 SIM Request (5): a0 c0 00 00 23 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 7f 20 Status 2: 9F 23 SIM Request (5): a0 c0 00 00 23 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 20 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 09 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 30 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 3c Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 31 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 01 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 46 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 11 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 78 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 02 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 7b Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 0c Status 1: 90 00 --- On Sun, 6/12/11, Basem Ahmed wrote: From: Basem Ahmed Subject: Re: Facing issues in using OSMOCOM To: "baseband-devel" Cc: "Sylvain Munaut" <246tnt at gmail.com> Date: Sunday, June 12, 2011, 9:55 PM Dear All, sorry for the previous mistake .Actually I am trying to run the Mobile project but i have some issues there .let me telling you all the procedures i made : 1-git clone the osmocom project2-make the checkout (git checkout origin/sylvain/testing )3-compiling the project(it works after some modification of TX transmitter enable)4-run the loader.compalram.bin(running perfectly)5-run the layer1.comalram.bin6-run telnet localhost and enabling the ms 17-run the mobile the project8-press the power on buttonsfor mobile application ? ?===>it keeps running perfectly exactly as you did in the demo and its says it complete reading the SIM and giving my?network?name but it stop before checking the?network?signals ?at the line:selection network(mcc=420 aljawal ?)start stored cell selection<003> gsm322.c:559 new state 'C0 null' ->'C2 stored cell Selection' .for the layer1 application===>it downloading successfully and it keeps?synchronized?with mobile application keep SIM requesting till the line:sim request (5): a0 b0 00 00 0cStaus 1:90 00 Hoping to hear from you soon. regard,--- On Sun, 6/12/11, Sylvain Munaut <246tnt at gmail.com> wrote: From: Sylvain Munaut <246tnt at gmail.com> Subject: Re: Facing issues in using OSMOCOM To: "Basem Ahmed" , "baseband-devel" Date: Sunday, June 12, 2011, 7:21 PM > How are you? Refer to below mail. I read the mailing list, please do not send to me directly. Only CC me (and CC, not a separate mail forward please) if you're posting a patch and you want me to review it and merge it. If I have an answer, I will answer ...? (but in this case, from your description it seems like a 'mobile' problem which I virtually never use, so I may not have an answer at all) > I am able to download the loader.compalram.bin and layer1.compalram.bin and running the mobile project.? I am also using the telnet for configuration.? But it is stopping at following some state mentioned in attached file. Sorry, but if you attach .docx file, there is zero chance I'm gonna look at it. 1) .docx is a proprietary format, don't expect people can read it 2) Even if this was a open document ( .ods or so ), I don't use office suite at all. 3) A .txt attachement still requires me to download it and look at it ... 4) In general, to maximize your chance of getting an answer, you have to do your best to minimize the work to be done by the people you want to help you. In this particular case: - You properly included a description of your setup and up to where you got, that's great. - What's missing is a 'snippet' of the log with the 'state' it seems locked it. - Then at the end of the mail, cut and paste the complete logs (both from osmocon and from the mobile app). - If possible avoid HTML mail as well ... (don't take all this bad and/or personally, just trying to help you maximize your chance of getting the answers you're looking for). Cheers, ? ? Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From Andreas.Eversberg at versatel.de Tue Jun 14 11:07:29 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Tue, 14 Jun 2011 13:07:29 +0200 Subject: Facing issues in using OSMOCOM Message-ID: can you send the full mobile output? (from start of application until it halts) > <0002> gsm322.c:3176 (ms 1) Event 'EVENT_SIM_INSERT' for automatic PLMN selection in state 'A0 null' > <000d> gsm322.c:1090 Start search of last registered PLMN (mcc=420 mnc=01 Saudi Arabia, Al Jawal) > <0002> gsm322.c:1094 Use RPLMN (mcc=420 mnc=01 Saudi Arabia, Al Jawal) > <0002> gsm322.c:530 new state 'A0 null' -> 'A1 trying RPLMN' > <0003> gsm322.c:3396 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in state 'C0 null' > <000d> gsm322.c:3007 Selecting network (mcc=420 mnc=01 Saudi Arabia, Al Jawal) > <0003> gsm322.c:3013 Start stored cell selection. > <0003> gsm322.c:559 new state 'C0 null' -> 'C2 stored cell selection' can you send me the your ~/.osmocom/bb/1.ba file? don't worry, it will only contain band allocations you have received so far. (rename it an see, if the problem still exists.) From eng_basemm at yahoo.com Wed Jun 15 08:17:43 2011 From: eng_basemm at yahoo.com (Basem Ahmed) Date: Wed, 15 Jun 2011 01:17:43 -0700 (PDT) Subject: Facing issues in using OSMOCOM Message-ID: <962959.70826.qm@web125909.mail.ne1.yahoo.com> B-Mobile Output: linux-d5zo:/home/basem/osmocom-bb/src/host/osmocon # ./osmocon -p /dev/ttyUSB0 -m c140xor ../../target/firmware/board/compal_e88/layer1.compalram.bin?got 2 bytes from modem, data looks like: 04 81 ?..got 5 bytes from modem, data looks like: 1b f6 02 00 41 ?....Agot 1 bytes from modem, data looks like: 01 ?.got 1 bytes from modem, data looks like: 40 ?@Received PROMPT1 from phone, responding with CMD The filesize is larger than 15kb, code on the magic address will be overwritten!Use loader.bin and upload the application with osmoload instead! read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): file_size=54104, hdr_len=4, dnload_len=54111got 1 bytes from modem, data looks like: 1b ?.got 1 bytes from modem, data looks like: f6 ?.got 1 bytes from modem, data looks like: 02 ?.got 1 bytes from modem, data looks like: 00 ?.got 1 bytes from modem, data looks like: 41 ?Agot 1 bytes from modem, data looks like: 02 ?.got 1 bytes from modem, data looks like: 43 ?CReceived PROMPT2 from phone, starting downloadhandle_write(): 4096 bytes (4096/54111)handle_write(): 4096 bytes (8192/54111)handle_write(): 4096 bytes (12288/54111)handle_write(): 4096 bytes (16384/54111)handle_write(): 4096 bytes (20480/54111)handle_write(): 4096 bytes (24576/54111)handle_write(): 4096 bytes (28672/54111)handle_write(): 4096 bytes (32768/54111)handle_write(): 4096 bytes (36864/54111)handle_write(): 4096 bytes (40960/54111)handle_write(): 4096 bytes (45056/54111)handle_write(): 4096 bytes (49152/54111)handle_write(): 4096 bytes (53248/54111)handle_write(): 863 bytes (54111/54111)handle_write(): finishedgot 1 bytes from modem, data looks like: 1b ?.got 1 bytes from modem, data looks like: f6 ?.got 1 bytes from modem, data looks like: 02 ?.got 1 bytes from modem, data looks like: 00 ?.got 1 bytes from modem, data looks like: 41 ?Agot 1 bytes from modem, data looks like: 03 ?.got 1 bytes from modem, data looks like: 42 ?BReceived DOWNLOAD ACK from phone, your code is running now! OSMOCOM Layer 1 (revision osmocon_v0.0.0-906-g5589a6b-modified)======================================================================Device ID code: 0xb4fbDevice Version code: 0x0000ARM ID code: 0xfff3cDSP ID code: 0x0128Die ID code: e144263d880014fd======================================================================REG_DPLL=0x2413CNTL_ARM_CLK=0xf0a1CNTL_CLK=0xff91CNTL_RST=0xfff3CNTL_ARM_DIV=0xfff9======================================================================Power up simcard:Assert DSP into ResetReleasing DSP from ResetSetting some dsp_api.ndb valuesSetting API NDB parametersDSP Download Status: 0x0001DSP API Version: 0x0000 0x0000Finishing download phaseDSP Download Status: 0x0002DSP API Version: 0x3606 0x0000LOST 1203!SIM Request (7): a0 a4 00 00 02 3f 00?Status 2: 9F 23SIM Request (5): a0 c0 00 00 23?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 2f e2?Status 2: 9F 13SIM Request (5): a0 c0 00 00 13?Status 1: 90 00SIM Request (5): a0 b0 00 00 0a?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 7f 20?Status 2: 9F 23SIM Request (5): a0 c0 00 00 23?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 07?Status 2: 9F 13SIM Request (5): a0 c0 00 00 13?Status 1: 90 00SIM Request (5): a0 b0 00 00 09?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 7e?Status 2: 9F 13SIM Request (5): a0 c0 00 00 13?Status 1: 90 00SIM Request (5): a0 b0 00 00 0b?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 3f 00?Status 2: 9F 23SIM Request (5): a0 c0 00 00 23?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 7f 10?Status 2: 9F 23SIM Request (5): a0 c0 00 00 23?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 40?Status 2: 9F 13SIM Request (5): a0 c0 00 00 13?Status 1: 90 00SIM Request (5): a0 b0 00 00 84?Status 1: 94 08SIM Request (7): a0 a4 00 00 02 3f 00?Status 2: 9F 23SIM Request (5): a0 c0 00 00 23?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 7f 20?Status 2: 9F 23SIM Request (5): a0 c0 00 00 23?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 20?Status 2: 9F 13SIM Request (5): a0 c0 00 00 13?Status 1: 90 00SIM Request (5): a0 b0 00 00 09?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 30?Status 2: 9F 13SIM Request (5): a0 c0 00 00 13?Status 1: 90 00SIM Request (5): a0 b0 00 00 3c?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 31?Status 2: 9F 13SIM Request (5): a0 c0 00 00 13?Status 1: 90 00SIM Request (5): a0 b0 00 00 01?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 46?Status 2: 9F 13SIM Request (5): a0 c0 00 00 13?Status 1: 90 00SIM Request (5): a0 b0 00 00 11?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 78?Status 2: 9F 13SIM Request (5): a0 c0 00 00 13?Status 1: 90 00SIM Request (5): a0 b0 00 00 02?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 7b?Status 2: 9F 13SIM Request (5): a0 c0 00 00 13?Status 1: 90 00SIM Request (5): a0 b0 00 00 0c?Status 1: 90 00L1CTL_RESET_REQ: FULL!L1CTL_PM_REQ start=100 end=104PM MEAS: ARFCN=100, 28 ? dBm at baseband, -109 dBm at RFPM MEAS: ARFCN=100, 30 ? dBm at baseband, -107 dBm at RFPM MEAS: ARFCN=101, 29 ? dBm at baseband, -108 dBm at RFPM MEAS: ARFCN=102, 26 ? dBm at baseband, -112 dBm at RFPM MEAS: ARFCN=103, 34 ? dBm at baseband, -104 dBm at RFPM MEAS: ARFCN=104, 25 ? dBm at baseband, -112 dBm at RFL1CTL_PM_REQ start=106 end=106PM MEAS: ARFCN=106, 26 ? dBm at baseband, -111 dBm at RFPM MEAS: ARFCN=106, 25 ? dBm at baseband, -112 dBm at RFL1CTL_PM_REQ start=108 end=110PM MEAS: ARFCN=108, 31 ? dBm at baseband, -106 dBm at RFPM MEAS: ARFCN=108, 30 ? dBm at baseband, -107 dBm at RFPM MEAS: ARFCN=109, 25 ? dBm at baseband, -112 dBm at RFPM MEAS: ARFCN=110, 24 ? dBm at baseband, -113 dBm at RFL1CTL_PM_REQ start=112 end=121PM MEAS: ARFCN=112, 28 ? dBm at baseband, -109 dBm at RFPM MEAS: ARFCN=112, 27 ? dBm at baseband, -110 dBm at RFPM MEAS: ARFCN=113, 32 ? dBm at baseband, -105 dBm at RFPM MEAS: ARFCN=114, 29 ? dBm at baseband, -108 dBm at RFPM MEAS: ARFCN=115, 29 ? dBm at baseband, -108 dBm at RFPM MEAS: ARFCN=116, 30 ? dBm at baseband, -107 dBm at RFPM MEAS: ARFCN=117, 31 ? dBm at baseband, -106 dBm at RFPM MEAS: ARFCN=118, 33 ? dBm at baseband, -104 dBm at RFPM MEAS: ARFCN=119, 29 ? dBm at baseband, -108 dBm at RFPM MEAS: ARFCN=120, 45 ? dBm at baseband, -92 ?dBm at RFPM MEAS: ARFCN=121, 65 ? dBm at baseband, -72 ?dBm at RFL1CTL_PM_REQ start=124 end=124PM MEAS: ARFCN=124, 29 ? dBm at baseband, -108 dBm at RFPM MEAS: ARFCN=124, 29 ? dBm at baseband, -108 dBm at RFL1CTL_PM_REQ start=762 end=762PM MEAS: ARFCN=762, 84 ? dBm at baseband, -54 ?dBm at RFPM MEAS: ARFCN=762, 84 ? dBm at baseband, -53 ?dBm at RFL1CTL_PM_REQ start=765 end=768PM MEAS: ARFCN=765, 41 ? dBm at baseband, -96 ?dBm at RFPM MEAS: ARFCN=765, 42 ? dBm at baseband, -95 ?dBm at RFPM MEAS: ARFCN=766, 38 ? dBm at baseband, -99 ?dBm at RFPM MEAS: ARFCN=767, 57 ? dBm at baseband, -80 ?dBm at RFPM MEAS: ARFCN=768, 46 ? dBm at baseband, -91 ?dBm at RFL1CTL_PM_REQ start=773 end=773PM MEAS: ARFCN=773, 33 ? dBm at baseband, -105 dBm at RFPM MEAS: ARFCN=773, 32 ? dBm at baseband, -105 dBm at RFL1CTL_PM_REQ start=775 end=776PM MEAS: ARFCN=775, 48 ? dBm at baseband, -89 ?dBm at RFPM MEAS: ARFCN=775, 48 ? dBm at baseband, -89 ?dBm at RFPM MEAS: ARFCN=776, 41 ? dBm at baseband, -96 ?dBm at RFL1CTL_PM_REQ start=779 end=779PM MEAS: ARFCN=779, 51 ? dBm at baseband, -86 ?dBm at RFPM MEAS: ARFCN=779, 52 ? dBm at baseband, -85 ?dBm at RFL1CTL_PM_REQ start=797 end=797PM MEAS: ARFCN=797, 29 ? dBm at baseband, -108 dBm at RFPM MEAS: ARFCN=797, 29 ? dBm at baseband, -108 dBm at RFL1CTL_PM_REQ start=816 end=816PM MEAS: ARFCN=816, 29 ? dBm at baseband, -108 dBm at RFPM MEAS: ARFCN=816, 28 ? dBm at baseband, -109 dBm at RFL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=762, flags=0x7)Starting FCCH RecognitionFB0 (1419:2): TOA= 1968, Power= -54dBm, Angle= 6913HzFB1 (1429:8): TOA= 9431, Power= -53dBm, Angle= ?858Hz? fn_offset=1428 (fn=1429 + attempt=8 + ntdma = 7)m ?delay=9 (fn_offset=1428 + 11 - fn=1429 - 1? scheduling next FB/SB detection task with delay 9FB1 (1440:1): TOA= ?683, Power= -53dBm, Angle= ?165Hz? fn_offset=1439 (fn=1440 + attempt=1 + ntdma = 0)m ?delay=9 (fn_offset=1439 + 11 - fn=1440 - 1? scheduling next FB/SB detection task with delay 9=>FB @ FNR 1439 fn_offset=1439 qbits=2548Synchronize_TDMALOST 2859!SB1 (2891:1): TOA= ? 23, Power= -53dBm, Angle= ?135Hz=> SB 0x01e4ab7f: BSIC=31 fn=2492177(1879/25/11) qbits=0Synchronize_TDMA=>FB @ FNR 2890 fn_offset=2492177 qbits=4908LOST 1903!L1CTL_RESET_REQ: FULL!EMPTYL1CTL_FBSB_REQ (arfcn=762, flags=0x7)Starting FCCH RecognitionFB0 (2492554:3): TOA= 2544, Power= -54dBm, Angle= 6840HzL1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=762, flags=0x7)Starting FCCH RecognitionFB0 (2492575:9): TOA= 9312, Power= -54dBm, Angle= 6777HzFB1 (2492585:8): TOA= 8755, Power= -53dBm, Angle= 1051Hz? fn_offset=2492583 (fn=2492585 + attempt=8 + ntdma = 6)m ?delay=8 (fn_offset=2492583 + 11 - fn=2492585 - 1? scheduling next FB/SB detection task with delay 8FB1 (2492605:11): TOA=12503, Power= -53dBm, Angle= ?160Hz? fn_offset=2492603 (fn=2492605 + attempt=11 + ntdma = 9)m ?delay=8 (fn_offset=2492603 + 11 - fn=2492605 - 1? scheduling next FB/SB detection task with delay 8=> DSP reports FB in bit that is 1179237253 bits in the future?!?Synchronize_TDMALOST 3714!SB1 (2269562:1): TOA= ? 29, Power= -53dBm, Angle= ? ?9Hz=> SB 0x00d6ab7f: BSIC=31 fn=2492615(1879/21/41)=> DSP reports SB in bit that is 1458016052 bits in the future?!?Synchronize_TDMA=> DSP reports FB in bit that is 1458016029 bits in the future?!?LOST 1912! Configuration for both : OsmocomBB# show runnOsmocomBB# show running-config? Current configuration:!!line vty?no login!gps device /dev/ttyACM0gps baudrate defaultno gps enable!ms 1?layer2-socket /tmp/osmocom_l2?sap-socket /tmp/osmocom_sap?sim reader?network-selection-mode auto?imei 000000000000000 0?imei-fixed?no emergency-imsi?no call-waiting?no auto-answer?no clip?no clir?tx-power auto?no simulated-delay?no stick?location-updating?codec full-speed prefer?codec half-speed?no abbrev?support? sms? a5/1? a5/2? p-gsm? e-gsm? r-gsm? no gsm-850? dcs? no pcs? class-900 4? class-850 4? class-dcs 1? class-pcs 1? channel-capability sdcch+tchf+tchh? full-speech-v1? full-speech-v2? half-speech-v1? min-rxlev -106? dsc-max 90?exit?test-sim? imsi 001010000000000? ki xor 00 00 00 00 00 00 00 00 00 00 00 00?? no barred-access? no rplmn? hplmn-search foreign-country?exit?no shutdownexit!endOsmocomBB# Connection closed by foreign host. Dear Andreas , Good day Sir , Actually i have two experiments for mobile project using Motorola C139 one with compal_e88 and the other with compal_e86 and here is the out put for both : First using compal E86: A- Layer 1 output: linux-d5zo:/home/basem/osmocom-bb/src/host/osmocon # ./osmocon -p /dev/ttyUSB0 -m c140xor ../../target/firmware/board/compal_e86/layer1.compalram.bin? got 2 bytes from modem, data looks like: 04 81 ?..got 5 bytes from modem, data looks like: 1b f6 02 00 41 ?....Agot 1 bytes from modem, data looks like: 01 ?.got 1 bytes from modem, data looks like: 40 ?@Received PROMPT1 from phone, responding with CMD The filesize is larger than 15kb, code on the magic address will be overwritten!Use loader.bin and upload the application with osmoload instead! read_file(../../target/firmware/board/compal_e86/layer1.compalram.bin): file_size=54736, hdr_len=4, dnload_len=54743got 1 bytes from modem, data looks like: 1b ?.got 1 bytes from modem, data looks like: f6 ?.got 1 bytes from modem, data looks like: 02 ?.got 1 bytes from modem, data looks like: 00 ?.got 1 bytes from modem, data looks like: 41 ?Agot 1 bytes from modem, data looks like: 02 ?.got 1 bytes from modem, data looks like: 43 ?CReceived PROMPT2 from phone, starting downloadhandle_write(): 4096 bytes (4096/54743)handle_write(): 4096 bytes (8192/54743)handle_write(): 4096 bytes (12288/54743)handle_write(): 4096 bytes (16384/54743)handle_write(): 4096 bytes (20480/54743)handle_write(): 4096 bytes (24576/54743)handle_write(): 4096 bytes (28672/54743)handle_write(): 4096 bytes (32768/54743)handle_write(): 4096 bytes (36864/54743)handle_write(): 4096 bytes (40960/54743)handle_write(): 4096 bytes (45056/54743)handle_write(): 4096 bytes (49152/54743)handle_write(): 4096 bytes (53248/54743)handle_write(): 1495 bytes (54743/54743)handle_write(): finishedgot 1 bytes from modem, data looks like: 1b ?.got 1 bytes from modem, data looks like: f6 ?.got 1 bytes from modem, data looks like: 02 ?.got 1 bytes from modem, data looks like: 00 ?.got 1 bytes from modem, data looks like: 41 ?Agot 1 bytes from modem, data looks like: 03 ?.got 1 bytes from modem, data looks like: 42 ?BReceived DOWNLOAD ACK from phone, your code is running now! OSMOCOM Layer 1 (revision osmocon_v0.0.0-906-g5589a6b-modified)======================================================================Device ID code: 0xb4fbDevice Version code: 0x0000ARM ID code: 0xfff3cDSP ID code: 0x0128Die ID code: e144263d880014fd======================================================================REG_DPLL=0x2413CNTL_ARM_CLK=0xf0a1CNTL_CLK=0xff91CNTL_RST=0xfff3CNTL_ARM_DIV=0xfff9======================================================================Power up simcard:Assert DSP into ResetReleasing DSP from ResetSetting some dsp_api.ndb valuesSetting API NDB parametersDSP Download Status: 0x0001DSP API Version: 0x0000 0x0000Finishing download phaseDSP Download Status: 0x0002DSP API Version: 0x3606 0x0000LOST 346!SIM Request (7): a0 a4 00 00 02 3f 00?Status 2: 9F 22SIM Request (5): a0 c0 00 00 22?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 2f e2?Status 2: 9F 0FSIM Request (5): a0 c0 00 00 0f?Status 1: 90 00SIM Request (5): a0 b0 00 00 0a?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 7f 20?Status 2: 9F 22SIM Request (5): a0 c0 00 00 22?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 07?Status 2: 9F 0FSIM Request (5): a0 c0 00 00 0f?Status 1: 90 00SIM Request (5): a0 b0 00 00 09?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 7e?Status 2: 9F 0FSIM Request (5): a0 c0 00 00 0f?Status 1: 90 00SIM Request (5): a0 b0 00 00 0b?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 3f 00?Status 2: 9F 22SIM Request (5): a0 c0 00 00 22?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 7f 10?Status 2: 9F 22SIM Request (5): a0 c0 00 00 22?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 40?Status 2: 9F 0FSIM Request (5): a0 c0 00 00 0f?Status 1: 90 00SIM Request (5): a0 b0 00 00 1c?Status 1: 94 08SIM Request (7): a0 a4 00 00 02 3f 00?Status 2: 9F 22SIM Request (5): a0 c0 00 00 22?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 7f 20?Status 2: 9F 22SIM Request (5): a0 c0 00 00 22?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 20?Status 2: 9F 0FSIM Request (5): a0 c0 00 00 0f?Status 1: 90 00SIM Request (5): a0 b0 00 00 09?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 30?Status 2: 9F 0FSIM Request (5): a0 c0 00 00 0f?Status 1: 90 00SIM Request (5): a0 b0 00 00 2c?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 31?Status 2: 9F 0FSIM Request (5): a0 c0 00 00 0f?Status 1: 90 00SIM Request (5): a0 b0 00 00 01?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 46?Status 2: 9F 0FSIM Request (5): a0 c0 00 00 0f?Status 1: 90 00SIM Request (5): a0 b0 00 00 11?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 78?Status 2: 9F 0FSIM Request (5): a0 c0 00 00 0f?Status 1: 90 00SIM Request (5): a0 b0 00 00 02?Status 1: 90 00SIM Request (7): a0 a4 00 00 02 6f 7b?Status 2: 9F 0FSIM Request (5): a0 c0 00 00 0f?Status 1: 90 00SIM Request (5): a0 b0 00 00 1e?Status 1: 90 00 B-Mobile Output: linux-d5zo:/home/basem/osmocom-bb/src/host/layer23/src/mobile # ./mobile -i 127.0.0.1Copyright (C) 2008-2010 ...Contributions by ... License GPLv2+: GNU GPL version 2 or later This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law. <000e> sim.c:1206 init SIM client<0005> gsm48_cc.c:61 init Call Control<0001> gsm48_rr.c:5052 init Radio Ressource process<0004> gsm48_mm.c:1239 init Mobility Management process<0004> gsm48_mm.c:990 Selecting PLMN SEARCH state, because no SIM.<0002> gsm322.c:3556 init PLMN process<0003> gsm322.c:3557 init Cell Selection process<0003> gsm322.c:3614 Read stored BA list (mcc=420 mnc=01 ?Saudi Arabia, Al Jawal)Mobile '1' initialized, please start phone now!VTY available on port 4247.<0004> subscriber.c:556 Requesting SIM file 0x2fe2<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:697 go MF<000e> sim.c:241 SELECT (file=0x3f00)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x22)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=34)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=34 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:241 SELECT (file=0x2fe2)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=15)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=10)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=10 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:229 received ICCID 89966321051209484485 from SIM<0004> subscriber.c:556 Requesting SIM file 0x6f07<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:706 requested path is longer, go child DFgsm<000e> sim.c:241 SELECT (file=0x7f20)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x22)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=34)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=34 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:241 SELECT (file=0x6f07)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=15)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=9)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=9 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:259 received IMSI 420032210948448 from SIM<0004> subscriber.c:556 Requesting SIM file 0x6f7e<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:241 SELECT (file=0x6f7e)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=15)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=11)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=11 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:295 received LOCI from SIM (mcc=420 mnc=03 lac=0x0529 U1)<0004> subscriber.c:556 Requesting SIM file 0x6f40<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:697 go MF<000e> sim.c:241 SELECT (file=0x3f00)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x22)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=34)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=34 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:706 requested path is longer, go child DFtelecom<000e> sim.c:241 SELECT (file=0x7f10)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x22)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=34)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=34 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:241 SELECT (file=0x6f40)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=15)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=28)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=28 sw1=0x94 sw2=0x08)<000e> sim.c:952 command failed<000e> sim.c:151 sending result to callback function (type=1)<0004> subscriber.c:608 SIM reading failed, ignoring!<0004> subscriber.c:556 Requesting SIM file 0x6f20<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:697 go MF<000e> sim.c:241 SELECT (file=0x3f00)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x22)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=34)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=34 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:706 requested path is longer, go child DFgsm<000e> sim.c:241 SELECT (file=0x7f20)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x22)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=34)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=34 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:241 SELECT (file=0x6f20)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=15)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=9)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=9 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:342 received KEY from SIM<0004> subscriber.c:556 Requesting SIM file 0x6f30<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:241 SELECT (file=0x6f30)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=15)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=44)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=44 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:380 received PLMN selector (mcc=420 mnc=03) from SIM<0004> subscriber.c:380 received PLMN selector (mcc=424 mnc=01) from SIM<0004> subscriber.c:380 received PLMN selector (mcc=424 mnc=02) from SIM<0004> subscriber.c:556 Requesting SIM file 0x6f31<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:241 SELECT (file=0x6f31)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=15)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=1)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=1 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:401 received HPPLMN 5 (30 mins) from SIM<0004> subscriber.c:556 Requesting SIM file 0x6f46<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:241 SELECT (file=0x6f46)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=15)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=17)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=17 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:424 received SPN mobily from SIM<0004> subscriber.c:556 Requesting SIM file 0x6f78<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:241 SELECT (file=0x6f78)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=15)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=2)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=2 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:442 received ACC 0100 from SIM<0004> subscriber.c:556 Requesting SIM file 0x6f7b<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:241 SELECT (file=0x6f7b)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=15)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=30)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=30 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:518 (ms 1) Done reading SIM card (IMSI=420032210948448 Saudi Arabia, Mobily)<0004> subscriber.c:530 -> SIM card registered to 420 03 (Saudi Arabia, Mobily)<0004> gsm48_mm.c:4160 (ms 1) Received 'MMR_REG_REQ' event<0002> gsm322.c:3176 (ms 1) Event 'EVENT_SIM_INSERT' for automatic PLMN selection in state 'A0 null'<000d> gsm322.c:1090 Start search of last registered PLMN (mcc=420 mnc=03 ?Saudi Arabia, Mobily)<0002> gsm322.c:1094 Use RPLMN (mcc=420 mnc=03 ?Saudi Arabia, Mobily)<0002> gsm322.c:530 new state 'A0 null' -> 'A1 trying RPLMN'<0003> gsm322.c:3396 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in state 'C0 null'<000d> gsm322.c:3007 Selecting network (mcc=420 mnc=03 ?Saudi Arabia, Mobily)<0003> gsm322.c:3016 Start normal cell selection.<0003> gsm322.c:559 new state 'C0 null' -> 'C1 normal cell selection' Second using compal E88: linux-d5zo:/home/basem/osmocom-bb/src/host/layer23/src/mobile # ./mobile -i 127.0.0.1Copyright (C) 2008-2010 ...Contributions by ... License GPLv2+: GNU GPL version 2 or later This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law. <000e> sim.c:1206 init SIM client<0005> gsm48_cc.c:61 init Call Control<0001> gsm48_rr.c:5052 init Radio Ressource process<0004> gsm48_mm.c:1239 init Mobility Management process<0004> gsm48_mm.c:990 Selecting PLMN SEARCH state, because no SIM.<0002> gsm322.c:3556 init PLMN process<0003> gsm322.c:3557 init Cell Selection process<0003> gsm322.c:3614 Read stored BA list (mcc=420 mnc=01 ?Saudi Arabia, Al Jawal)Mobile '1' initialized, please start phone now!VTY available on port 4247.<0004> subscriber.c:556 Requesting SIM file 0x2fe2<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:697 go MF<000e> sim.c:241 SELECT (file=0x3f00)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x23)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=35)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=35 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:241 SELECT (file=0x2fe2)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=19)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=10)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=10 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:229 received ICCID 8996601230003583462 from SIM<0004> subscriber.c:556 Requesting SIM file 0x6f07<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:706 requested path is longer, go child DFgsm<000e> sim.c:241 SELECT (file=0x7f20)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x23)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=35)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=35 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:241 SELECT (file=0x6f07)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=19)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=9)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=9 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:259 received IMSI 420012300358346 from SIM<0004> subscriber.c:556 Requesting SIM file 0x6f7e<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:241 SELECT (file=0x6f7e)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=19)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=11)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=11 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:295 received LOCI from SIM (mcc=420 mnc=01 lac=0x012f U1)<0004> subscriber.c:556 Requesting SIM file 0x6f40<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:697 go MF<000e> sim.c:241 SELECT (file=0x3f00)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x23)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=35)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=35 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:706 requested path is longer, go child DFtelecom<000e> sim.c:241 SELECT (file=0x7f10)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x23)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=35)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=35 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:241 SELECT (file=0x6f40)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=19)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=132)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=132 sw1=0x94 sw2=0x08)<000e> sim.c:952 command failed<000e> sim.c:151 sending result to callback function (type=1)<0004> subscriber.c:608 SIM reading failed, ignoring!<0004> subscriber.c:556 Requesting SIM file 0x6f20<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:697 go MF<000e> sim.c:241 SELECT (file=0x3f00)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x23)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=35)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=35 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:706 requested path is longer, go child DFgsm<000e> sim.c:241 SELECT (file=0x7f20)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x23)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=35)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=35 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:241 SELECT (file=0x6f20)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=19)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=9)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=9 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:342 received KEY from SIM<0004> subscriber.c:556 Requesting SIM file 0x6f30<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:241 SELECT (file=0x6f30)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=19)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=60)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=60 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:556 Requesting SIM file 0x6f31<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:241 SELECT (file=0x6f31)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=19)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=1)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=1 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:401 received HPPLMN 5 (30 mins) from SIM<0004> subscriber.c:556 Requesting SIM file 0x6f46<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:241 SELECT (file=0x6f46)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=19)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=17)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=17 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:635 SIM reading failed, file invalid<0004> subscriber.c:556 Requesting SIM file 0x6f78<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:241 SELECT (file=0x6f78)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=19)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=2)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=2 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:442 received ACC 0040 from SIM<0004> subscriber.c:556 Requesting SIM file 0x6f7b<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)<000e> sim.c:241 SELECT (file=0x6f7b)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)<000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13)<000e> sim.c:949 command successfull<000e> sim.c:571 GET RESPONSE (len=19)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0)<000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:277 READ BINARY (offset=0 len=12)<000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0)<000e> sim.c:876 received APDU (len=12 sw1=0x90 sw2=0x00)<000e> sim.c:949 command successfull<000e> sim.c:151 sending result to callback function (type=0)<0004> subscriber.c:518 (ms 1) Done reading SIM card (IMSI=420012300358346 Saudi Arabia, Al Jawal)<0004> subscriber.c:530 -> SIM card registered to 420 01 (Saudi Arabia, Al Jawal)<0004> gsm48_mm.c:4160 (ms 1) Received 'MMR_REG_REQ' event<0002> gsm322.c:3176 (ms 1) Event 'EVENT_SIM_INSERT' for automatic PLMN selection in state 'A0 null'<000d> gsm322.c:1090 Start search of last registered PLMN (mcc=420 mnc=01 ?Saudi Arabia, Al Jawal)<0002> gsm322.c:1094 Use RPLMN (mcc=420 mnc=01 ?Saudi Arabia, Al Jawal)<0002> gsm322.c:530 new state 'A0 null' -> 'A1 trying RPLMN'<0003> gsm322.c:3396 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in state 'C0 null'<000d> gsm322.c:3007 Selecting network (mcc=420 mnc=01 ?Saudi Arabia, Al Jawal)<0003> gsm322.c:3013 Start stored cell selection.<0003> gsm322.c:559 new state 'C0 null' -> 'C2 stored cell selection'<0003> gsm322.c:2456 Getting PM for ARFCN 100 twice. Overwriting the first! Please fix prim_pm.c<0003> gsm322.c:2468 Found signal (ARFCN 103 rxlev -104 (6))<0003> gsm322.c:2456 Getting PM for ARFCN 106 twice. Overwriting the first! Please fix prim_pm.c<0003> gsm322.c:2468 Found signal (ARFCN 108 rxlev -106 (4))<0003> gsm322.c:2456 Getting PM for ARFCN 108 twice. Overwriting the first! Please fix prim_pm.c<0003> gsm322.c:2456 Getting PM for ARFCN 112 twice. Overwriting the first! Please fix prim_pm.c<0003> gsm322.c:2468 Found signal (ARFCN 113 rxlev -105 (5))<0003> gsm322.c:2468 Found signal (ARFCN 117 rxlev -106 (4))<0003> gsm322.c:2468 Found signal (ARFCN 118 rxlev -104 (6))<0003> gsm322.c:2468 Found signal (ARFCN 120 rxlev -92 (18))<0003> gsm322.c:2468 Found signal (ARFCN 121 rxlev -72 (38))<0003> gsm322.c:2456 Getting PM for ARFCN 124 twice. Overwriting the first! Please fix prim_pm.c<0003> gsm322.c:2468 Found signal (ARFCN 762(DCS) rxlev -54 (56))<0003> gsm322.c:2456 Getting PM for ARFCN 762(DCS) twice. Overwriting the first! Please fix prim_pm.c<0003> gsm322.c:2468 Found signal (ARFCN 762(DCS) rxlev -53 (57))<0003> gsm322.c:2468 Found signal (ARFCN 765(DCS) rxlev -96 (14))<0003> gsm322.c:2456 Getting PM for ARFCN 765(DCS) twice. Overwriting the first! Please fix prim_pm.c<0003> gsm322.c:2468 Found signal (ARFCN 765(DCS) rxlev -95 (15))<0003> gsm322.c:2468 Found signal (ARFCN 766(DCS) rxlev -99 (11))<0003> gsm322.c:2468 Found signal (ARFCN 767(DCS) rxlev -80 (30))<0003> gsm322.c:2468 Found signal (ARFCN 768(DCS) rxlev -91 (19))<0003> gsm322.c:2468 Found signal (ARFCN 773(DCS) rxlev -105 (5))<0003> gsm322.c:2456 Getting PM for ARFCN 773(DCS) twice. Overwriting the first! Please fix prim_pm.c<0003> gsm322.c:2468 Found signal (ARFCN 773(DCS) rxlev -105 (5))<0003> gsm322.c:2468 Found signal (ARFCN 775(DCS) rxlev -89 (21))<0003> gsm322.c:2456 Getting PM for ARFCN 775(DCS) twice. Overwriting the first! Please fix prim_pm.c<0003> gsm322.c:2468 Found signal (ARFCN 775(DCS) rxlev -89 (21))<0003> gsm322.c:2468 Found signal (ARFCN 776(DCS) rxlev -96 (14))<0003> gsm322.c:2468 Found signal (ARFCN 779(DCS) rxlev -86 (24))<0003> gsm322.c:2456 Getting PM for ARFCN 779(DCS) twice. Overwriting the first! Please fix prim_pm.c<0003> gsm322.c:2468 Found signal (ARFCN 779(DCS) rxlev -85 (25))<0003> gsm322.c:2456 Getting PM for ARFCN 797(DCS) twice. Overwriting the first! Please fix prim_pm.c<0003> gsm322.c:2456 Getting PM for ARFCN 816(DCS) twice. Overwriting the first! Please fix prim_pm.c<0003> gsm322.c:2396 Found 15 frequencies.<0003> gsm322.c:276 Sync to ARFCN=762(DCS) rxlev=-53 (No sysinfo yet, ccch mode NONE)<0003> gsm322.c:2486 Channel synched. (ARFCN=762(DCS), snr=9, BSIC=31)<0001> gsm322.c:2513 using DSC of 90<0003> gsm48_rr.c:4656 Channel provides data.<0001> sysinfo.c:711 Ignoring SYSTEM INFORMATION 4 until SI 1 is received.<0001> gsm48_rr.c:1869 New SYSTEM INFORMATION 4 (mcc 000 mnc 000 lac 0x0000)<0001> sysinfo.c:692 New SYSTEM INFORMATION 3 (mcc 420 mnc 01 lac 0x012f)<0001> gsm48_rr.c:1835 Changing CCCH_MODE to 1<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:1801 New SYSTEM INFORMATION 2ter<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2129 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> sysinfo.c:599 Now decoding previously received SYSTEM INFORMATION 4<0001> sysinfo.c:432 Serving cell ARFCN #0: 797<0001> sysinfo.c:432 Serving cell ARFCN #1: 816<0001> sysinfo.c:446 Hopping ARFCN: 0 (bit 797)<0001> sysinfo.c:446 Hopping ARFCN: 1 (bit 816)<0001> gsm48_rr.c:1714 New SYSTEM INFORMATION 1<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2338 IMMEDIATE ASSIGNMENT:<0001> gsm48_rr.c:2350 ?(ta 0/0m ra 0x00 chan_nr 0x0e MAIO 0 HSN 43 TS 6 SS 0 TSC 6)<0001> gsm48_rr.c:2366 Not for us, no request.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:1743 New SYSTEM INFORMATION 2<0003> gsm322.c:1624 Cell ARFCN 762(DCS): Cell found, (rxlev=-53 mcc=420 mnc=01 lac=012f ?Saudi Arabia, Al Jawal)<0003> gsm322.c:1635 Cell ARFCN 762(DCS) selected.<0003> gsm322.c:1955 Tune to frequency 762.<0003> gsm322.c:270 Sync to ARFCN=762(DCS) rxlev=-53 (Sysinfo, ccch mode NON-COMB)<0003> gsm322.c:1997 Cell available.<0003> gsm322.c:3396 (ms 1) Event 'EVENT_CELL_FOUND' for Cell selection in state 'C2 stored cell selection'<000d> gsm322.c:2798 Camping normally on cell (ARFCN=762(DCS) mcc=420 mnc=01 ?Saudi Arabia, Al Jawal)<0003> gsm322.c:559 new state 'C2 stored cell selection' -> 'C3 camped normally'<0004> gsm48_mm.c:4092 (ms 1) Received 'MM_EVENT_CELL_SELECTED' event in state MM IDLE, PLMN search<0004> gsm48_mm.c:901 new MM IDLE state PLMN search -> location updating needed<0004> gsm48_mm.c:901 new MM IDLE state location updating needed -> attempting to update<0004> gsm48_mm.c:2150 Do Loc. upd. for IMSI attach.<000d> gsm48_mm.c:2083 Perform location update (MCC 420, MNC 01 LAC 0x012f)<0004> gsm48_mm.c:2205 LOCATION UPDATING REQUEST<0004> gsm48_mm.c:2227 ?using LAI (mcc 420 mnc 01 lac 0x012f)<0004> gsm48_mm.c:2235 ?using TMSI 0x2804a1b5<0004> gsm48_mm.c:906 new state MM IDLE, attempting to update -> wait for RR connection (location updating)<0001> gsm48_rr.c:5019 (ms 1) Message 'RR_EST_REQ' received in state idle<000d> gsm48_rr.c:1245 Establish radio link due to mobility management request<0003> gsm322.c:3396 (ms 1) Event 'EVENT_LEAVE_IDLE' for Cell selection in state 'C3 camped normally'<0003> gsm322.c:3034 Going to camping (normal) ARFCN 762(DCS).<0003> gsm322.c:270 Sync to ARFCN=762(DCS) rxlev=-53 (Sysinfo, ccch mode NON-COMB)<0001> gsm48_rr.c:363 new state idle -> connection pending<0001> gsm48_rr.c:1384 CHANNEL REQUEST: 00 (Location Update with NECI)<0003> gsm322.c:2486 Channel synched. (ARFCN=762(DCS), snr=11, BSIC=31)<0001> gsm322.c:2513 using DSC of 90<0003> gsm48_rr.c:4656 Channel provides data.<0001> gsm48_rr.c:1516 RANDOM ACCESS (requests left 5)<0001> gsm48_rr.c:1573 RANDOM ACCESS (Tx-integer 50 combined no S(lots) 0 ra 0x0a)<0001> gsm48_rr.c:1612 Use MS-TXPWR-MAX-CCH power value 0 (30 dBm)<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:2077 PAGING ignored, we are not camping.<0001> gsm48_rr.c:609 MON: f=762 lev=-51 snr= 0 ber= 32 LAI=420 01 012f ID=2dcf<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info<0001> gsm48_rr.c:609 MON: no cell info^CSignal 2 received.<0004> gsm48_mm.c:4096 (ms 1) Received 'MM_EVENT_IMSI_DETACH' event in state wait for RR connection (location updating)<0004> gsm48_mm.c:1862 IMSI detach delayed.<0001> gsm48_rr.c:609 MON: no cell info OsmocomBB#?show?ms 1MS?'1'?is?up,?MM?connection?active??IMEI:?000000000000000?????IMEISV:?0000000000000000?????IMEI?generation:?fixed??automatic?network?selection?state:?A1?trying?RPLMN??cell?selection?state:?C3?camped?normally??radio?ressource?layer?state:?connection?pending??mobility?management?layer?state:?wait?for?RR?connection?(location?updating) I am hoping to read soon from you people. Regards,Basem --- On Tue, 6/14/11, Andreas.Eversberg wrote: From: Andreas.Eversberg Subject: Re: Facing issues in using OSMOCOM To: "Basem Ahmed" Cc: baseband-devel at lists.osmocom.org Date: Tuesday, June 14, 2011, 2:07 PM can you send the full mobile output? (from start of application until it halts) >??? <0002> gsm322.c:3176 (ms 1) Event 'EVENT_SIM_INSERT' for automatic PLMN selection in state 'A0 null' >??? <000d> gsm322.c:1090 Start search of last registered PLMN (mcc=420 mnc=01? Saudi Arabia, Al Jawal) >??? <0002> gsm322.c:1094 Use RPLMN (mcc=420 mnc=01? Saudi Arabia, Al Jawal) >??? <0002> gsm322.c:530 new state 'A0 null' -> 'A1 trying RPLMN' >??? <0003> gsm322.c:3396 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in state 'C0 null' >??? <000d> gsm322.c:3007 Selecting network (mcc=420 mnc=01? Saudi Arabia, Al Jawal) >??? <0003> gsm322.c:3013 Start stored cell selection. >??? <0003> gsm322.c:559 new state 'C0 null' -> 'C2 stored cell selection' can you send me the your ~/.osmocom/bb/1.ba file? don't worry, it will only contain band allocations you have received so far. (rename it an see, if the problem still exists.) -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Wed Jun 15 08:31:30 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Wed, 15 Jun 2011 10:31:30 +0200 Subject: Facing issues in using OSMOCOM In-Reply-To: <962959.70826.qm@web125909.mail.ne1.yahoo.com> References: <962959.70826.qm@web125909.mail.ne1.yahoo.com> Message-ID: > The filesize is larger than 15kb, code on the magic address will be overwritten! > Use loader.bin and upload the application with osmoload instead! Well, that sounds like a pretty explicit warning ... maybe you should try what it says. From Andreas.Eversberg at versatel.de Wed Jun 15 09:35:09 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Wed, 15 Jun 2011 11:35:09 +0200 Subject: AW: Facing issues in using OSMOCOM Message-ID: mine is >50k. why am i not getting the same warning? > Well, that sounds like a pretty explicit warning ... maybe you should > try what it says. From eng_basemm at yahoo.com Wed Jun 15 11:27:57 2011 From: eng_basemm at yahoo.com (Basem Ahmed) Date: Wed, 15 Jun 2011 04:27:57 -0700 (PDT) Subject: AW: Facing issues in using OSMOCOM In-Reply-To: Message-ID: <652994.58277.qm@web125905.mail.ne1.yahoo.com> Hi, I think it is not a problem of osmocon, it is a problem of mobile application because osmocon is able to upload the whole file. Even I tried the osmoload like:?./osmoload -m c140xor ?-l /tmp/...... LAYER1.COMPALRAM.PATH?but it says model is not supported. One more thing I am using C139 Motorola and it is compal_e86. But when I select the firmware of e86 it hangs as showed in outpu below but when I select e88 it is able to select the cell. But there is some issue in RR and MM.?Is it a problem of Motorola C139 ?Model?? Any body tried using it. Why "show ms 1" is saying: OsmocomBB#?show?ms 1MS?'1'?is?up,?MM?connection?active??IMEI:?000000000000000?????IMEISV:?0000000000000000?????IMEI?generation:?fixed??automatic?network?selection?state:?A1?trying?RPLMN??cell?selection?state:?C3?camped?normally??radio?ressource?layer?state:?connection?pending??mobility?management?layer?state:?wait?for?RR?connection?(location?updating) I am hoping read soon from you. Regards,Basem --- On Wed, 6/15/11, Andreas.Eversberg wrote: From: Andreas.Eversberg Subject: AW: Facing issues in using OSMOCOM To: "Sylvain Munaut" <246tnt at gmail.com>, "Basem Ahmed" Cc: baseband-devel at lists.osmocom.org Date: Wednesday, June 15, 2011, 12:35 PM mine is >50k. why am i not getting the same warning? > Well, that sounds like a pretty explicit warning ... maybe you should > try what it says. -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Wed Jun 15 11:31:18 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Wed, 15 Jun 2011 13:31:18 +0200 Subject: Facing issues in using OSMOCOM In-Reply-To: References: Message-ID: On Wed, Jun 15, 2011 at 11:35 AM, Andreas.Eversberg wrote: > mine is >50k. why am i not getting the same warning? Because you're using a C123 that doesn't require a 'MAGIC' marker when doing the code download. But when using the c140xor, osmocon will have to insert a specific marker at a specific address for the bootloader to accept the file and if the file is > 15 k, that marker will overwrite part of the binary which will lead to something that can crash at any time (because whatever code is overwritten will vary depending on a bunch of factors) Sylvain From Andreas.Eversberg at versatel.de Wed Jun 15 12:10:19 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Wed, 15 Jun 2011 14:10:19 +0200 Subject: AW: Facing issues in using OSMOCOM Message-ID: > Because you're using a C123 that doesn't require a 'MAGIC' marker when > doing the code download. netbook ~ # osmocom-roaming/src/host/osmocon/osmocon -p /dev/ttyUSB0 -m c140xor osmocom-roaming/src/target/firmware/board/compal_e88/layer1.compalram.bin got 1 bytes from modem, data looks like: 00 . does not seem so. but anyway: it is not a problem of the application "mobile". the process of one phone gets stuck while waiting for power measurement replay. the process of the other phone waits for the RACH confirm but never receives it. it looks pretty much like a broken layer1 or serial connection. -----Urspr?ngliche Nachricht----- Von: Sylvain Munaut [mailto:246tnt at gmail.com] Gesendet: Mittwoch, 15. Juni 2011 13:31 An: Andreas.Eversberg Cc: Basem Ahmed; baseband-devel at lists.osmocom.org Betreff: Re: Facing issues in using OSMOCOM On Wed, Jun 15, 2011 at 11:35 AM, Andreas.Eversberg wrote: > mine is >50k. why am i not getting the same warning? Because you're using a C123 that doesn't require a 'MAGIC' marker when doing the code download. But when using the c140xor, osmocon will have to insert a specific marker at a specific address for the bootloader to accept the file and if the file is > 15 k, that marker will overwrite part of the binary which will lead to something that can crash at any time (because whatever code is overwritten will vary depending on a bunch of factors) Sylvain From eng_basemm at yahoo.com Mon Jun 13 15:55:33 2011 From: eng_basemm at yahoo.com (Basem Ahmed) Date: Mon, 13 Jun 2011 08:55:33 -0700 (PDT) Subject: Fw: Re: Facing issues in using OSMOCOM Message-ID: <783126.41766.qm@web125905.mail.ne1.yahoo.com> Also we are sure about the?correct?setup of ARM tool chain!! any help please about such issue. --- On Mon, 6/13/11, Basem Ahmed wrote: From: Basem Ahmed Subject: Re: Facing issues in using OSMOCOM To: "baseband-devel" Date: Monday, June 13, 2011, 11:41 AM Hi All GNUMonks, I am adding the log output here for reference as suggesed by Sylvain: Mobile Output: <000e> sim.c:949 command successfull <000e> sim.c:571 GET RESPONSE (len=19) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0) <000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:277 READ BINARY (offset=0 len=2) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0) <000e> sim.c:876 received APDU (len=2 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:151 sending result to callback function (type=0) <0004> subscriber.c:442 received ACC 0040 from SIM <0004> subscriber.c:556 Requesting SIM file 0x6f7b <000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000e> sim.c:241 SELECT (file=0x6f7b) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4) <000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13) <000e> sim.c:949 command successfull <000e> sim.c:571 GET RESPONSE (len=19) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0) <000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:277 READ BINARY (offset=0 len=12) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0) <000e> sim.c:876 received APDU (len=12 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:151 sending result to callback function (type=0) <0004> subscriber.c:518 (ms 1) Done reading SIM card (IMSI=420012300358346 Saudi Arabia, Al Jawal) <0004> subscriber.c:530 -> SIM card registered to 420 01 (Saudi Arabia, Al Jawal) <0004> gsm48_mm.c:4160 (ms 1) Received 'MMR_REG_REQ' event <0002> gsm322.c:3176 (ms 1) Event 'EVENT_SIM_INSERT' for automatic PLMN selection in state 'A0 null' <000d> gsm322.c:1090 Start search of last registered PLMN (mcc=420 mnc=01? Saudi Arabia, Al Jawal) <0002> gsm322.c:1094 Use RPLMN (mcc=420 mnc=01? Saudi Arabia, Al Jawal) <0002> gsm322.c:530 new state 'A0 null' -> 'A1 trying RPLMN' <0003> gsm322.c:3396 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in state 'C0 null' <000d> gsm322.c:3007 Selecting network (mcc=420 mnc=01? Saudi Arabia, Al Jawal) <0003> gsm322.c:3013 Start stored cell selection. <0003> gsm322.c:559 new state 'C0 null' -> 'C2 stored cell selection' Layer1: Output read_file(../../target/firmware/board/compal_e86/layer1.compalram.bin): file_size=54736, hdr_len=4, dnload_len=54743 got 1 bytes from modem, data looks like: 1b? . got 1 bytes from modem, data looks like: f6? . got 1 bytes from modem, data looks like: 02? . got 1 bytes from modem, data looks like: 00? . got 1 bytes from modem, data looks like: 41? A got 1 bytes from modem, data looks like: 02? . got 1 bytes from modem, data looks like: 43? C Received PROMPT2 from phone, starting download handle_write(): 4096 bytes (4096/54743) handle_write(): 4096 bytes (8192/54743) handle_write(): 4096 bytes (12288/54743) handle_write(): 4096 bytes (16384/54743) handle_write(): 4096 bytes (20480/54743) handle_write(): 4096 bytes (24576/54743) handle_write(): 4096 bytes (28672/54743) handle_write(): 4096 bytes (32768/54743) handle_write(): 4096 bytes (36864/54743) handle_write(): 4096 bytes (40960/54743) handle_write(): 4096 bytes (45056/54743) handle_write(): 4096 bytes (49152/54743) handle_write(): 4096 bytes (53248/54743) handle_write(): 1495 bytes (54743/54743) handle_write(): finished got 1 bytes from modem, data looks like: 1b? . got 1 bytes from modem, data looks like: f6? . got 1 bytes from modem, data looks like: 02? . got 1 bytes from modem, data looks like: 00? . got 1 bytes from modem, data looks like: 41? A got 1 bytes from modem, data looks like: 03? . got 1 bytes from modem, data looks like: 42? B Received DOWNLOAD ACK from phone, your code is running now! OSMOCOM Layer 1 (revision osmocon_v0.0.0-906-g5bbea93-modified) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: e144263d880014fd ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== Power up simcard: Assert DSP into Reset Releasing DSP from Reset Setting some dsp_api.ndb values Setting API NDB parameters DSP Download Status: 0x0001 DSP API Version: 0x0000 0x0000 Finishing download phase DSP Download Status: 0x0002 DSP API Version: 0x3606 0x0000 LOST 1174! SIM Request (7): a0 a4 00 00 02 3f 00 Status 2: 9F 23 SIM Request (5): a0 c0 00 00 23 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 2f e2 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 0a Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 7f 20 Status 2: 9F 23 SIM Request (5): a0 c0 00 00 23 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 07 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 09 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 7e Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 0b Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 3f 00 Status 2: 9F 23 SIM Request (5): a0 c0 00 00 23 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 7f 10 Status 2: 9F 23 SIM Request (5): a0 c0 00 00 23 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 40 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 84 Status 1: 94 08 SIM Request (7): a0 a4 00 00 02 3f 00 Status 2: 9F 23 SIM Request (5): a0 c0 00 00 23 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 7f 20 Status 2: 9F 23 SIM Request (5): a0 c0 00 00 23 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 20 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 09 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 30 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 3c Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 31 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 01 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 46 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 11 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 78 Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 02 Status 1: 90 00 SIM Request (7): a0 a4 00 00 02 6f 7b Status 2: 9F 13 SIM Request (5): a0 c0 00 00 13 Status 1: 90 00 SIM Request (5): a0 b0 00 00 0c Status 1: 90 00 --- On Sun, 6/12/11, Basem Ahmed wrote: From: Basem Ahmed Subject: Re: Facing issues in using OSMOCOM To: "baseband-devel" Cc: "Sylvain Munaut" <246tnt at gmail.com> Date: Sunday, June 12, 2011, 9:55 PM Dear All, sorry for the previous mistake .Actually I am trying to run the Mobile project but i have some issues there .let me telling you all the procedures i made : 1-git clone the osmocom project2-make the checkout (git checkout origin/sylvain/testing )3-compiling the project(it works after some modification of TX transmitter enable)4-run the loader.compalram.bin(running perfectly)5-run the layer1.comalram.bin6-run telnet localhost and enabling the ms 17-run the mobile the project8-press the power on buttonsfor mobile application ? ?===>it keeps running perfectly exactly as you did in the demo and its says it complete reading the SIM and giving my?network?name but it stop before checking the?network?signals ?at the line:selection network(mcc=420 aljawal ?)start stored cell selection<003> gsm322.c:559 new state 'C0 null' ->'C2 stored cell Selection' .for the layer1 application===>it downloading successfully and it keeps?synchronized?with mobile application keep SIM requesting till the line:sim request (5): a0 b0 00 00 0cStaus 1:90 00 Hoping to hear from you soon. regard,--- On Sun, 6/12/11, Sylvain Munaut <246tnt at gmail.com> wrote: From: Sylvain Munaut <246tnt at gmail.com> Subject: Re: Facing issues in using OSMOCOM To: "Basem Ahmed" , "baseband-devel" Date: Sunday, June 12, 2011, 7:21 PM > How are you? Refer to below mail. I read the mailing list, please do not send to me directly. Only CC me (and CC, not a separate mail forward please) if you're posting a patch and you want me to review it and merge it. If I have an answer, I will answer ...? (but in this case, from your description it seems like a 'mobile' problem which I virtually never use, so I may not have an answer at all) > I am able to download the loader.compalram.bin and layer1.compalram.bin and running the mobile project.? I am also using the telnet for configuration.? But it is stopping at following some state mentioned in attached file. Sorry, but if you attach .docx file, there is zero chance I'm gonna look at it. 1) .docx is a proprietary format, don't expect people can read it 2) Even if this was a open document ( .ods or so ), I don't use office suite at all. 3) A .txt attachement still requires me to download it and look at it ... 4) In general, to maximize your chance of getting an answer, you have to do your best to minimize the work to be done by the people you want to help you. In this particular case: - You properly included a description of your setup and up to where you got, that's great. - What's missing is a 'snippet' of the log with the 'state' it seems locked it. - Then at the end of the mail, cut and paste the complete logs (both from osmocon and from the mobile app). - If possible avoid HTML mail as well ... (don't take all this bad and/or personally, just trying to help you maximize your chance of getting the answers you're looking for). Cheers, ? ? Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From b8.adel at gmail.com Mon Jun 20 09:47:42 2011 From: b8.adel at gmail.com (adel) Date: Mon, 20 Jun 2011 02:47:42 -0700 (PDT) Subject: help me i have motorola c123 Message-ID: <1308563262342-3085529.post@n3.nabble.com> hello i have Motorola c123 The following are my steps: 1- $ cd osmocom-bb $ git checkout -b testing remotes/origin/sylvain/testing fatal: git checkout: branch testing already exists 2- ~/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/layer1.compalram.bin got 2 bytes from modem, data looks like: 2f 00 /. got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): file_size=51320, hdr_len=4, dnload_len=51327 got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 43 C Received PROMPT2 from phone, starting download handle_write(): 4096 bytes (4096/51327) handle_write(): 4096 bytes (8192/51327) handle_write(): 4096 bytes (12288/51327) handle_write(): 4096 bytes (16384/51327) handle_write(): 4096 bytes (20480/51327) handle_write(): 4096 bytes (24576/51327) handle_write(): 4096 bytes (28672/51327) handle_write(): 4096 bytes (32768/51327) handle_write(): 4096 bytes (36864/51327) handle_write(): 4096 bytes (40960/51327) handle_write(): 4096 bytes (45056/51327) handle_write(): 4096 bytes (49152/51327) handle_write(): 2175 bytes (51327/51327) handle_write(): finished got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 03 . got 1 bytes from modem, data looks like: 42 B Received DOWNLOAD ACK from phone, your code is running now! OSMOCOM Layer 1 (revision osmocon_v0.0.0-786-g937023b) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: df0d1621a400d808 ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!! Assert DSP into Reset Releasing DSP from Reset Setting some dsp_api.ndb values Setting API NDB parameters DSP Download Status: 0x0001 DSP API Version: 0x0000 0x0000 Finishing download phase DSP Download Status: 0x0002 DSP API Version: 0x3606 0x0000 LOST 1968! 3- ~/osmocom-bb/src/host/layer23/src/mobile$ ./mobile Copyright (C) 2008-2010 ... Contributions by ... License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. <000e> sim.c:1206 init SIM client <0005> gsm48_cc.c:61 init Call Control <0001> gsm48_rr.c:4944 init Radio Ressource process <0004> gsm48_mm.c:1220 init Mobility Management process <0004> gsm48_mm.c:971 Selecting PLMN SEARCH state, because no SIM. <0002> gsm322.c:3472 init PLMN process <0003> gsm322.c:3473 init Cell Selection process Mobile '1' initialized, please start phone now! VTY available on port 4247. <0004> subscriber.c:556 Requesting SIM file 0x2fe2 <000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000e> sim.c:697 go MF <000e> sim.c:241 SELECT (file=0x3f00) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4) I wait and wait and nothing happens to keep as is? What is the solution to this problem? I hope someone can help me as soon as -- View this message in context: http://baseband-devel.722152.n3.nabble.com/help-me-i-have-motorola-c123-tp3085529p3085529.html Sent from the baseband-devel mailing list archive at Nabble.com. From ninja at infosec-id.com Sun Jun 26 17:29:23 2011 From: ninja at infosec-id.com (Muhammad Rasyid Sahputra) Date: Sun, 26 Jun 2011 20:29:23 +0300 Subject: help me i have motorola c123 In-Reply-To: <1308563262342-3085529.post@n3.nabble.com> References: <1308563262342-3085529.post@n3.nabble.com> Message-ID: Hi, you need to perform: telnet localhost 4247 then you'll get a console interface to interact with mobile application On Mon, Jun 20, 2011 at 12:47 PM, adel wrote: > hello > i have Motorola c123 The following are my steps: > 1- > $ cd osmocom-bb > $ git checkout -b testing remotes/origin/sylvain/testing > fatal: git checkout: branch testing already exists > 2- > ~/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123xor > ../../target/firmware/board/compal_e88/layer1.compalram.bin > got 2 bytes from modem, data looks like: 2f 00 /. > got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A > got 1 bytes from modem, data looks like: 01 . > got 1 bytes from modem, data looks like: 40 @ > Received PROMPT1 from phone, responding with CMD > read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): > file_size=51320, hdr_len=4, dnload_len=51327 > got 1 bytes from modem, data looks like: 1b . > got 1 bytes from modem, data looks like: f6 . > got 1 bytes from modem, data looks like: 02 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 41 A > got 1 bytes from modem, data looks like: 02 . > got 1 bytes from modem, data looks like: 43 C > Received PROMPT2 from phone, starting download > handle_write(): 4096 bytes (4096/51327) > handle_write(): 4096 bytes (8192/51327) > handle_write(): 4096 bytes (12288/51327) > handle_write(): 4096 bytes (16384/51327) > handle_write(): 4096 bytes (20480/51327) > handle_write(): 4096 bytes (24576/51327) > handle_write(): 4096 bytes (28672/51327) > handle_write(): 4096 bytes (32768/51327) > handle_write(): 4096 bytes (36864/51327) > handle_write(): 4096 bytes (40960/51327) > handle_write(): 4096 bytes (45056/51327) > handle_write(): 4096 bytes (49152/51327) > handle_write(): 2175 bytes (51327/51327) > handle_write(): finished > got 1 bytes from modem, data looks like: 1b . > got 1 bytes from modem, data looks like: f6 . > got 1 bytes from modem, data looks like: 02 . > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 41 A > got 1 bytes from modem, data looks like: 03 . > got 1 bytes from modem, data looks like: 42 B > Received DOWNLOAD ACK from phone, your code is running now! > > > OSMOCOM Layer 1 (revision osmocon_v0.0.0-786-g937023b) > ====================================================================== > Device ID code: 0xb4fb > Device Version code: 0x0000 > ARM ID code: 0xfff3 > cDSP ID code: 0x0128 > Die ID code: df0d1621a400d808 > ====================================================================== > REG_DPLL=0x2413 > CNTL_ARM_CLK=0xf0a1 > CNTL_CLK=0xff91 > CNTL_RST=0xfff3 > CNTL_ARM_DIV=0xfff9 > ====================================================================== > > > THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!! > Assert DSP into Reset > Releasing DSP from Reset > Setting some dsp_api.ndb values > Setting API NDB parameters > DSP Download Status: 0x0001 > DSP API Version: 0x0000 0x0000 > Finishing download phase > DSP Download Status: 0x0002 > DSP API Version: 0x3606 0x0000 > LOST 1968! > > 3- > ~/osmocom-bb/src/host/layer23/src/mobile$ ./mobile > Copyright (C) 2008-2010 ... > Contributions by ... > > License GPLv2+: GNU GPL version 2 or later > <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. > > <000e> sim.c:1206 init SIM client > <0005> gsm48_cc.c:61 init Call Control > <0001> gsm48_rr.c:4944 init Radio Ressource process > <0004> gsm48_mm.c:1220 init Mobility Management process > <0004> gsm48_mm.c:971 Selecting PLMN SEARCH state, because no SIM. > <0002> gsm322.c:3472 init PLMN process > <0003> gsm322.c:3473 init Cell Selection process > Mobile '1' initialized, please start phone now! > VTY available on port 4247. > <0004> subscriber.c:556 Requesting SIM file 0x2fe2 > <000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) > <000e> sim.c:697 go MF > <000e> sim.c:241 SELECT (file=0x3f00) > <000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4) > > I wait and wait and nothing happens to keep as is? > What is the solution to this problem? > I hope someone can help me as soon as > > > > -- > View this message in context: > http://baseband-devel.722152.n3.nabble.com/help-me-i-have-motorola-c123-tp3085529p3085529.html > Sent from the baseband-devel mailing list archive at Nabble.com. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Andreas.Eversberg at versatel.de Tue Jun 21 07:32:13 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Tue, 21 Jun 2011 09:32:13 +0200 Subject: cell re-selection Message-ID: hi, i did a lot of resarch and testing on cell selection and re-selection process the last two week. the cell selection process, network selection process (manual and automatic) and mobility management process were already implemented in OsmocomBB a long time, but turned out to be buggy and incomplete. i made test drives to check the process and debugged it. the re-selection process is new. it is used to track surrounding cells while listening to the BCCH of the current cell (camping on a cell). special extension to the layer1 firmare is used to measure neighbour cells. if an neighbour cell becomes 'better', the mobile switches to that cell, depening on different criteria. now it is possible to move with OsmocomBB. the re-selection process is not handover! handover is a process where a phone switches between cells while doing a call. handover is one next step to implement. the process is a little more complex, because it requires not only neighbour cell measurements, but also syncing to them without interrupting the traffic channel. most layer 3 stuff of handover is already implemented. if you like to play and test your moving OsmocomBB, you can check out the "jolly/roaming" branch. it contains the extension to layer1, as well as sim reader and fixes from "sylvain/testing" branch. use both "mobile" and "layer1" firmware from this branch. in order to see some process at VTY, you can do: enable monitor network 1 (continously display the strongest cell and neighbour cells) show ms 1 (to see current states) show neighbour-cells 1 (to see a more detailed current list of neighbours) andreas From 775725965 at qq.com Wed Jun 22 13:01:05 2011 From: 775725965 at qq.com (=?gbk?B?wvPM78rYzfs=?=) Date: Wed, 22 Jun 2011 21:01:05 +0800 Subject: the need all people to make Message-ID: i find a way maybe the phone(motorola) it can to make usrp -------------- next part -------------- An HTML attachment was scrubbed... URL: From mvoelske at googlemail.com Thu Jun 23 10:22:16 2011 From: mvoelske at googlemail.com (Michael) Date: Thu, 23 Jun 2011 12:22:16 +0200 Subject: Sending and receiving TCH frames with 'mobile' Message-ID: Hello List, as part of my research, I'm trying to use the 'mobile' app to send and receive data on traffic channels. That is, I want to replace the audio stream from the phone's microphone/speaker by something else supplied by the computer attached to the phone. I realize this feature isn't fully implemented in osmocom-BB currently, and I'm willing to write some code to make it work (and share my results with this list if there's any interest). Here's what I've done so far: - merged the sylvain/traffic and jolly/voice branches - added some code to mobile that writes the payload of downlink frames to a user-specified file once a call has been established As far as the receiving end goes, this seems to work. I'm still unclear as to where I should start on the sending side -- I do expect it to be somewhat more complex. Any pointers -- or a rough outline of what is left to be done to make this work -- would be much appreciated. Kind regards, Michael Voelske From ichgeh at l--putt.de Fri Jun 24 08:17:58 2011 From: ichgeh at l--putt.de (l--putt) Date: Fri, 24 Jun 2011 10:17:58 +0200 Subject: Progress with NuttX Message-ID: <4E044836.3030801@l--putt.de> Hi list, with a bit of help from Harald, I finally managed to push my commits. Hence, we have: - platform support for Calypso (timers, irq, ...) - char device driver for keypad (/dev/keypad) - some hacks reusing old drivers for SPI/poweroff and sercomm The console currently outputs in osmocon while you have to write to the loader interface with a python script. Flushing is kind of a problem too. Haven't checked how to fix those two, so any volunteers? Bye, Stefan From the.real.sens0r at gmail.com Sat Jun 25 14:09:38 2011 From: the.real.sens0r at gmail.com (Paul Lambert) Date: Sat, 25 Jun 2011 16:09:38 +0200 Subject: Layer3 interaction Message-ID: Hello, since I am new to this list, I want to take the opportunity to thank your for your efforts. It is just awesome that one can do phonecalls with an open-source baseband stack. I'm new to the project and I'm searching a method to send prepared packets (Layer 3) to my basestation in my lab. I'm searching now for the best way to do so, is there already a script allowing me to perform that task? I couldn't find one when I searched. If there is none available I would try to build one using code located in layer23. I would be glad if you could point me to the method if there is already something available. With best regards From laforge at gnumonks.org Sat Jun 25 15:55:12 2011 From: laforge at gnumonks.org (Harald Welte) Date: Sat, 25 Jun 2011 17:55:12 +0200 Subject: Layer3 interaction In-Reply-To: References: Message-ID: <20110625155512.GD11159@prithivi.gnumonks.org> Hi, On Sat, Jun 25, 2011 at 04:09:38PM +0200, Paul Lambert wrote: > I'm new to the project and I'm searching a method to send prepared > packets (Layer 3) to my basestation in my lab. I'm searching now for > the best way to do so, is there already a script allowing me to > perform that task? I couldn't find one when I searched. If there is > none available I would try to build one using code located in layer23. Unfortunately a number of people have indicated they did so, but nobody wants to release their code. Welcome to the world of elite security folks who are too concerned about giving away anything to their competitors :/ I'm more than happy to merge any such code. Before you start, I suggest contacting the baseband-devel list to get some input... I bet andreas and sylvain have great ideas how this could e integrated best. 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 246tnt at gmail.com Sat Jun 25 17:11:35 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sat, 25 Jun 2011 19:11:35 +0200 Subject: Layer3 interaction In-Reply-To: <20110625155512.GD11159@prithivi.gnumonks.org> References: <20110625155512.GD11159@prithivi.gnumonks.org> Message-ID: > Before you start, I suggest contacting the baseband-devel list to get > some input... I bet andreas and sylvain have great ideas how this could > e integrated best. I guess something like openbsc / openbts would be good : Some vty command to establish a 'bare' channel and exchange L3 packets on a UDP socket with external application ? Or possibly map that to TCP / (DCCP ?) connection: When an application connects, it establishes a channel to the BTS then you exchange packets and when you close the socket it releases it. In any case both should be fairly easy to implement using the ccch_scan code as base. Cheers, Sylvain Munaut From baseband at hackwerk.org Sun Jun 26 10:37:34 2011 From: baseband at hackwerk.org (Job) Date: Sun, 26 Jun 2011 12:37:34 +0200 Subject: 1 of 4 phones not loading Message-ID: <4E070BEE.3070108@hackwerk.org> Hi, I've got 4 C115 phones (all same firmware). One is not loading and reporting the ftmtool error. The others are loading fine. Could this be caused by a blown RX input on the chip? Or could there other reasons why it does not work. I tried both an FTDI cable and a buspirate. Best regards, Job output: ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 2 bytes from modem, data looks like: 04 01 .. got 5 bytes from modem, data looks like: 1b f6 02 00 41 ....A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=17132, hdr_len=4, dnload_len=17139 got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r From laforge at gnumonks.org Mon Jun 27 09:00:37 2011 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 27 Jun 2011 11:00:37 +0200 Subject: libosmocore / logging from within libraries Message-ID: <20110627090037.GF19993@prithivi.gnumonks.org> Hi! As more and more code is moving into libraries (like I just did with the LAPDm code, and like pablo is working on with libosmo-abis), we needed a solution how to allocate and use the LOGP subsystem constants like DRSL, DRR, ... from within libraries. The existing logging code wasn't really prepared for that. I've now come um with a hack to extend it while preserving compatibility to applications: * we use negative numbers starting from -1 for library-internal subsystems * those numbers get converted to a positive index into the various arrays at run-time. So -1 ends up one entry higher in the array than the last application-providede log category/subsystem. As part of this change, the array allocations are now dynamic, i.e there is no maximum limit for the number of log categories that an application can register with the core. Only for libraries (even outside libosmocore), we have compile-time registration, i.e. the 'struct log_info_cat' and the D* constant need to be defined inside libosmocore. I think this is an acceptable compromise. Furthermore, if LOGP()/DEBUGP() ever see a subsystem number that it doesn't know, it will assign it to the new 'DLGLOBAL' (Debug Library GLOBAL) category, i.e. there cna be no array overflows. This ensures that even an external library using a 'newer' D* constant will not crash or otherwise fail, it will simply log in a slightly different way. 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 meierk at informatik.uni-freiburg.de Mon Jun 27 11:32:58 2011 From: meierk at informatik.uni-freiburg.de (Konrad Meier) Date: Mon, 27 Jun 2011 13:32:58 +0200 Subject: libosmocore / logging from within libraries In-Reply-To: <20110627090037.GF19993@prithivi.gnumonks.org> References: <20110627090037.GF19993@prithivi.gnumonks.org> Message-ID: <4E086A6A.3030801@informatik.uni-freiburg.de> 27.06.2011 11:00, schrieb Harald Welte: > Hi! > > As more and more code is moving into libraries (like I just did with the > LAPDm code, and like pablo is working on with libosmo-abis), we needed a > solution how to allocate and use the LOGP subsystem constants like DRSL, > DRR, ... from within libraries. > > The existing logging code wasn't really prepared for that. I've now > come um with a hack to extend it while preserving compatibility to > applications: > > * we use negative numbers starting from -1 for library-internal > subsystems > * those numbers get converted to a positive index into the various > arrays at run-time. So -1 ends up one entry higher in the array > than the last application-providede log category/subsystem. > > As part of this change, the array allocations are now dynamic, i.e there > is no maximum limit for the number of log categories that an application > can register with the core. > > Only for libraries (even outside libosmocore), we have compile-time > registration, i.e. the 'struct log_info_cat' and the D* constant need to > be defined inside libosmocore. I think this is an acceptable > compromise. > > Furthermore, if LOGP()/DEBUGP() ever see a subsystem number that it > doesn't know, it will assign it to the new 'DLGLOBAL' (Debug Library > GLOBAL) category, i.e. there cna be no array overflows. > > This ensures that even an external library using a 'newer' D* constant > will not crash or otherwise fail, it will simply log in a slightly > different way. > > Regards, > Harald Hi Harald, Quick fix for openbsc: index 6800021..fb5ce7a 100644 --- a/openbsc/tests/debug/debug_test.c +++ b/openbsc/tests/debug/debug_test.c @@ -25,7 +25,7 @@ int main(int argc, char **argv) { struct log_target *stderr_target; - log_init(&log_info); + log_init(&log_info, NULL); stderr_target = log_target_create_stderr(); log_add_target(stderr_target); log_set_all_filter(stderr_target, 1); Regards Konrad From laforge at gnumonks.org Mon Jun 27 12:23:41 2011 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 27 Jun 2011 14:23:41 +0200 Subject: libosmocore / logging from within libraries In-Reply-To: <4E086A6A.3030801@informatik.uni-freiburg.de> References: <20110627090037.GF19993@prithivi.gnumonks.org> <4E086A6A.3030801@informatik.uni-freiburg.de> Message-ID: <20110627122341.GK19993@prithivi.gnumonks.org> On Mon, Jun 27, 2011 at 01:32:58PM +0200, Konrad Meier wrote: > Quick fix for openbsc: thanks, I always keep forgetting the tests... -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From rebecca.wilson at twinlinks.net Tue Jun 28 12:09:07 2011 From: rebecca.wilson at twinlinks.net (Rebecca Wilson | TwinLinks) Date: 28 Jun 2011 08:09:07 -0400 Subject: bb.osmocom.org question Message-ID: Hello, I'd like to propose a 3-way link swap with your website http://bb.osmocom.org, where you receive 2 links in exchange for one of yours. 3-way linking is a very effective link building strategy. Since you're getting the links from third party websites, they appear totally natural to search engine algorithms. Such inbound links help your website rank higher in Google and other search engines. Our partner sites that link to your site are at least 3 years old with a minimum pagerank of PR3. Visit http://twinlinks.net to submit your website. Thanks, Rebecca Wilson Founder & CEO, TwinLinks From laforge at gnumonks.org Wed Jun 29 08:58:59 2011 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 29 Jun 2011 10:58:59 +0200 Subject: bb.osmocom.org question In-Reply-To: References: Message-ID: <20110629085859.GE24601@prithivi.gnumonks.org> Hello Ms. Wilson, On Tue, Jun 28, 2011 at 08:09:07AM -0400, Rebecca Wilson | TwinLinks wrote: > I'd like to propose a 3-way link swap with your website > http://bb.osmocom.org, where you receive 2 links in exchange for one > of yours. Please go away and _never_ contact any of the *.osmocom.org *.gnumonks.org, *.netfilter.org domain names / email adresses again about any of your offers. 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 b8.adel at gmail.com Wed Jun 29 07:50:38 2011 From: b8.adel at gmail.com (adel) Date: Wed, 29 Jun 2011 00:50:38 -0700 (PDT) Subject: help me i have motorola c123 Message-ID: <1309333838570-3120656.post@n3.nabble.com> hello all people i have problem i don't send call with my phone c123 any one have key of this problem help me . 0001> gsm48_rr.c:2338 IMMEDIATE ASSIGNMENT: <0001> gsm48_rr.c:2350 (ta 1/553m ra 0xec chan_nr 0x41 MAIO 0 HSN 4 TS 1 SS 0 TSC 6) <0001> gsm48_rr.c:2366 Not for us, no request. <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1890111e (not for us) <0009> gsm48_rr.c:2040 TMSI 02d01331 (not for us) <0001> gsm48_rr.c:609 MON: f=699 lev=-79 snr= 0 ber= 2 LAI=603 02 01d7 ID=b7b8 <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1838b73d (not for us) <0009> gsm48_rr.c:2040 TMSI 1d2818a9 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 03f86c30 (not for us) <0009> gsm48_rr.c:2040 TMSI 1268a36c (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 08a0c21b (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 10d86969 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 0b50e58e (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 0b308821 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 07c0435c (not for us) <0009> gsm48_rr.c:2040 TMSI 17107708 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 18309cae (not for us) <0009> gsm48_rr.c:2040 TMSI 018817cd (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 17d86dd2 (not for us) <0001> gsm48_rr.c:609 MON: f=699 lev=-79 snr= 0 ber= 0 LAI=603 02 01d7 ID=b7b8 <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 06a045e3 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 12f0772b (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 13681856 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 0d80715b (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1d1827a2 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1480220a (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1c4817ff (not for us) <0001> gsm48_rr.c:2338 IMMEDIATE ASSIGNMENT: <0001> gsm48_rr.c:2350 (ta 0/0m ra 0x1a chan_nr 0x41 MAIO 2 HSN 4 TS 1 SS 0 TSC 6) <0001> gsm48_rr.c:2366 Not for us, no request. <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1e589e44 (not for us) <0009> gsm48_rr.c:2040 TMSI 12f8d23a (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1878ddb0 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 05e0ac9c (not for us) <0009> gsm48_rr.c:2040 TMSI 1140c7c9 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI f6088640 (not for us) <0001> gsm48_rr.c:609 MON: f=699 lev=-79 snr= 0 ber= 10 LAI=603 02 01d7 ID=b7b8 <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI e2084634 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 02e03cd5 (not for us) <0001> gsm48_rr.c:2338 IMMEDIATE ASSIGNMENT: <0001> gsm48_rr.c:2350 (ta 0/0m ra 0x89 chan_nr 0x49 MAIO 0 HSN 4 TS 1 SS 1 TSC 6) <0001> gsm48_rr.c:2366 Not for us, no request. <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 03d8da99 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1ca8a7da (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1c70794c (not for us) <0001> gsm48_rr.c:609 MON: f=699 lev=-80 snr= 0 ber= 5 LAI=603 02 01d7 ID=b7b8 <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 07f042d5 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 0c40eb0c (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 0e509fe2 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1b186325 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1b70f22f (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1190da2f (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 054875f6 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1a303414 (not for us) <0009> gsm48_rr.c:2040 TMSI 0bb0eda9 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 055873d6 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 13f016ed (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 0f98765b (not for us) <0001> gsm48_rr.c:609 MON: f=699 lev=-79 snr= 0 ber= 0 LAI=603 02 01d7 ID=b7b8 <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 0bf8436d (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1b386004 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1fa01aa4 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 0b68f048 (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 1ec87dbd (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 11f0f27e (not for us) <0009> gsm48_rr.c:2040 TMSI 1078250f (not for us) <0009> gsm48_rr.c:2081 PAGING REQUEST 1 <0009> gsm48_rr.c:2040 TMSI 02f03d94 (not for us) <0009> gsm48_rr.c:2040 TMSI 121027b7 (not for us) -- View this message in context: http://baseband-devel.722152.n3.nabble.com/help-me-i-have-motorola-c123-tp3120656p3120656.html Sent from the baseband-devel mailing list archive at Nabble.com. From screaming-pain at libero.it Wed Jun 29 08:40:46 2011 From: screaming-pain at libero.it (screaming-pain) Date: Wed, 29 Jun 2011 01:40:46 -0700 (PDT) Subject: help me i have motorola c123 In-Reply-To: <1309333838570-3120656.post@n3.nabble.com> References: <1309333838570-3120656.post@n3.nabble.com> Message-ID: <1309336846124-3120771.post@n3.nabble.com> mmm... I can't see anything in your log that can be helpful to understand the problem Anyway are you sure you are using the right branch? You should use the testing branch I think, and enable tx in \src\target\firmware\Makefile Loretta -- View this message in context: http://baseband-devel.722152.n3.nabble.com/help-me-i-have-motorola-c123-tp3120656p3120771.html Sent from the baseband-devel mailing list archive at Nabble.com. From issertiv at gmail.com Thu Jun 30 16:18:17 2011 From: issertiv at gmail.com (Raz Sharif) Date: Thu, 30 Jun 2011 17:18:17 +0100 Subject: Motorola C115 with OsmocomBB Message-ID: Hi Folks, just wanted to know if anyone actually tried the Motorola C115 with OsmocomBB ? It appears to be difficult to source compatible phones in the UK but I did manage to get this C115 Model and wanted confirmation before hacking away at it only to find it is not going to play. The wiki states : Motorola C115/C117 It seems to be 99.9% identical with the MotorolaC123/C121/C122 series. So far, all our software (written for the MotorolaC123) is working on the C115/C117, too. The PCB is marked E87, i.e. one number less than the MotorolaC123(E88). Any feedback would be very appreciated from anyone who has had success with this particular phone from the Users side. Thanks Raz -------------- next part -------------- An HTML attachment was scrubbed... URL: From deacon at volny.cz Thu Jun 30 17:41:35 2011 From: deacon at volny.cz (Tomas Kopsa) Date: Thu, 30 Jun 2011 19:41:35 +0200 Subject: Motorola C115 with OsmocomBB In-Reply-To: References: Message-ID: <4E0CB54F.8090307@volny.cz> I have Motorola C115 and C121, both models works fine with OsmocomBB (behaviour is identical). Tomas > Hi Folks, just wanted to know if anyone actually tried the Motorola > C115 with OsmocomBB ? > > It appears to be difficult to source compatible phones in the UK but I > did manage to get this C115 Model and wanted confirmation before > hacking away at it only to find it is not going to play. > > The wiki states : > > Motorola C115/C117 > > It seems to be 99.9% identical with the MotorolaC123 > /C121/C122 series. > > So far, all our software (written for the MotorolaC123 > ) is working on the > C115/C117, too. > > The PCB is marked E87, i.e. one number less than the MotorolaC123 > (E88). > > > Any feedback would be very appreciated from anyone who has had success > with this particular phone from the Users side. > > Thanks > > Raz -------------- next part -------------- An HTML attachment was scrubbed... URL: From baseband at hackwerk.org Thu Jun 30 18:02:01 2011 From: baseband at hackwerk.org (Job) Date: Thu, 30 Jun 2011 20:02:01 +0200 Subject: Motorola C115 with OsmocomBB In-Reply-To: References: Message-ID: <4E0CBA19.2060303@hackwerk.org> Hi, > Hi Folks, just wanted to know if anyone actually tried the Motorola C115 > with OsmocomBB ? Yes, I have a couple and they work. Bought them on ebay as C118 and they turned out to be refurbished C115 inside. I just load the e88 firmwares and also tried the testing branch. Worked fine with a SIM on the local network. Best regards, Job From gyoutubeg at yahoo.com.br Thu Jun 30 18:34:09 2011 From: gyoutubeg at yahoo.com.br (Gerard) Date: Thu, 30 Jun 2011 18:34:09 +0000 (UTC) Subject: Motorola C115 with OsmocomBB References: Message-ID: Hello, i have one C115 and it worked for me. Just one note, the layer23 app don't tune on DCS , just gsm 900. My C115 is a brazilian model.