- baseband-devel - lists.osmocom.org

Not able to download the sources from git clone git://git.osmocom.org/osmocom-bb.git
by karnatinagesh＠gmail.com 13 Sep '11

13 Sep '11

Hi, currently i am not able to download the sources from the git repository. git clone git://git.osmocom.org/osmocom-bb.git is there some issues with the git repository ?. regards, nageswara reddy. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Not-able-to-download-the-sources… Sent from the baseband-devel mailing list archive at Nabble.com.

2 2

Not able to connect to Network using C-115 devices.
by nageswara reddy 08 Sep '11

08 Sep '11

Hi, Finally i am able to compile the GSM Stack code and flash into the Motorol Device C-115. i can see the "layer1.bin" on the display, but my device is not latched on to the N/W. - When i ran the HOST software of Mobile. i can see that SIM reader code is not working, and i can see the IMEI is hardcoded to "0000000000000000". - i captured the response of FBSB(Frequency and Time synchronization Burst), the result is comming as "255". can any one please help me how to resolve these issues so that i can latch on to the N/W. regards, nageswara reddy.

4 3

Osmocom + USRP
by Alexander Chemeris 08 Sep '11

08 Sep '11

Hi Harald and all, I have a client who is interested in an USRP-based MS side implementation. I think that that OsmocomBB is a natural choice for the higher-level stack, but I have only vague idea about its current state. As I understand, burst coding/modulation, reference clock management and GSM clock management should be implemented to get a working MS. Is there anything else to implement? How well is API to Calypso DSP is abstracted in OsmocomBB? (Sorry for my brevity and no googling, I'm abroad on GPRS for few weeks)

2 2

How to change the log setting through vty?
by josephli 08 Sep '11

08 Sep '11

Hello, I have got the logging details of all c files in the directory ../layer23/src/mobile. And now I also want to check the log in the directory of layer23/src/common/lapdm.c. I found the file logging_vty.c is similar to interface_vty.c so I tried several times but it didnt work. Can any one guide me how to use the vty to change the logging setting? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/How-to-change-the-log-setting-th… Sent from the baseband-devel mailing list archive at Nabble.com.

1 0

Motorola C119
by Basem Ahmed 04 Sep '11

04 Sep '11

Hi All, I got new Motorola phone modeled "C119" Its shape like feature Motorola C118 but i tried to programmed with OSMOCON utility with the loader or with the simtest applications but it did not work ,So any help please ? Thanks

3 3

serial issues on fast PC
by Job 03 Sep '11

03 Sep '11

Hi, While testing on a new PC I ran into the following issue. Same phone (C115), same USB cable FTDI RS232 + RS232 -> 3v3, works on a slow Atom PC with latest osmocom-bb git, but fails with fmtool error on a fast i7 core PC. The fail happens after sending the first 4096 bytes with a NACK from the phone. Once in many tries it actually does download something but then fails to run the image. Has anyone seen such behaviour? Any ideas on what might go wrong? If not I'll spend some time to debug it. Best regards, Job

2 2

[PATCH 0/2] Adding embedded and utilities to configure options
by Job 02 Sep '11

02 Sep '11

Hi, Attached are the patches to update configure.ac and some Makefile.am to use more default option selection style. I commented the docdir var in the main Makefile.am. The second patch contains the addition of --disable-utilities and --enable-embedded options. I never made a patch mail before so let me know if anything is missing. Best regards, Job ==== job (2): Adapted configure options to autoconf default behaviour Added autoconf option for utilities and embedded Makefile.am | 2 +- configure.ac | 55 ++++++++++++++++++++++++++++++++++++++-------------- utils/Makefile.am | 2 + 3 files changed, 43 insertions(+), 16 deletions(-) -- 1.7.4.1

3 6

Re: Bug in frequency list generation of libosmocore
by Dieter Spaar 01 Sep '11

01 Sep '11

Hello, appended is another patch for fixing a bug in the calculation of the frequency lists. This time the patch is for the "Range 256 format". The problem is that the operand for the "smod" operation might be negative, in this case the simplified version won't work as expected. In the patch I introduced a separate function for "smod" which takes care of the sign. I have not yet checked if the other formats are also affected, this would be the case if the "smod" operand can be negative. There might be other solutions to fix the problem without the need for a separate function, however I have not thought further about it. A test vector is the following frequency list ("Range 256 format", first byte is the length): 09 8b 1c 83 8c 15 ef 02 2d 30 The correct ARFCNs are 569 571 576 578 586 608 712 715 719 The uncorrected version would instead return: 444 457 460 464 569 576 578 586 608 This means four ARFCNs are wrong which will cause problems if for example the frequency list contains the ARFCNs for hopping. Best regards, Dieter Dieter Spaar, Germany spaar(a)mirider.augusta.de

2 1

900MHz packet radio?
by Paul Gardner-Stephen 01 Sep '11

01 Sep '11

Greetings all, At the Serval Project we have created a mobile mesh telephony system that currently works over wifi.

4 9

Re: baseband-devel Digest, Vol 20, Issue 1
by Paul Gardner-Stephen 01 Sep '11

01 Sep '11

On Thu, Sep 1, 2011 at 7:30 PM, <baseband-devel-request(a)lists.osmocom.org> wrote: Hello, Thank you Dieter and Scott for your fast responses. > ---------- Forwarded message ---------- > From: "Dieter Spaar" <spaar(a)mirider.augusta.de> > To: baseband-devel(a)lists.osmocom.org > Date: Thu, 01 Sep 2011 07:59:31 CEST > Subject: Re: 900MHz packet radio? > Hello Paul, > > On Thu, 1 Sep 2011 13:41:11 +0930, "Paul Gardner-Stephen" <paul(a)servalproject.org> wrote: >> >> So, as the open-source group with the most experience reprogramming >> baseband radios, what is the feasibility of creating a >> proof-of-concept using the types of phones you already work with to >> send and receive arbitrary data packets without reliance on a cell >> tower (even for time synchronisation)? > > It depends a lot on what you want to use on the lower layers > (e.g. Modulation). The TI Calypso based phones have a built-in > GMSK hardware modulator, so it is GMSK. Also the symbolrate is > fixed to the one used by GSM. I had assumed that the modulation would be fixed in this way, and it is not an issue for what I am wanting to do. In fact, it makes a lot of sense to keep the GSM modulation for simplicity. > Then there is the DSP which does the signal processing work. Its > again tied to the GSM standard (format of the burst and length). > It might be possible to put something else into the relativ small > RAM inside the DSP, but this could be a huge effort. This seems to me to be the hardest part of the whole process. When you say a huge effort, do you think it would be possible for someone to be able to get something working if they were able to work on it full-time for a few months? > Besides that you have to modify the hardware of the phone (remove > a filter) so that the phone can receive another phone. But this > is probably the smallest problem of all. Indeed, this is the smallest problem I think. In fact, if we use the part of the ISM915 band that is right next to the GSM band, then my understanding is the filter will only attenuate by a few db -- although I am happy to be corrected on this point. > Best regards, > Dieter > -- > Dieter Spaar, Germany spaar(a)mirider.augusta.de > > > > > ---------- Forwarded message ---------- > From: Scott Weisman <sweisman(a)pobox.com> > To: baseband-devel <baseband-devel(a)lists.osmocom.org> > Date: Thu, 1 Sep 2011 10:18:21 +0300 > Subject: Re: 900MHz packet radio? > I think you would be better taking your existing hardware, which must be somewhat custom to begin with (since it works over wifi) and use something like a HopeRF module (http://www.hoperf.com/) or similar. HopeRF has transceivers with power output up 100mW, data rates up to 256kbps, and a choice of 4 different bands (315, 433, 868, 915). This sounds like it would be a far easier choice to incorporate into your already-working system than hacking OsmocomBB-capable phones. > There is a lot of development from many different companies in this area and quite a bit of hacker activity as well. We are exploring that path simultaneously, and have a batch of the exactly the HopeRF modules that we will use, to demonstrate the range and utility of using the ISM band for long-range mesh telephony. But it is important also that we prove that it can be done using the baseband radio in a phone. We all know that it can if we have the freedom to design the baseband radio from scratch, but that it can also be done it is also important that I show that for handsets where the baseband radio can be reprogrammed without changing the hardware. It all boils down to being able to deflect any straw arguments that might be raised against the feasibility of long-range mesh telephony using baseband radio. Paul. > Scott > > On Thu, Sep 1, 2011 at 7:11 AM, Paul Gardner-Stephen <paul(a)servalproject.org> wrote: >> >> Greetings all, >> >> At the Serval Project we have created a mobile mesh telephony system >> that currently works over wifi. >> >> >From the outset, we have wanted to get it working on the ISM915 and/or >> ISM868 bands that are located adjacent to the GSM 850/900 frequency >> allocations. >> >> My initial investigations and enquiries indicate that this should be >> possible by creative programming of the baseband processor in many >> models of phones. The trick, as I suspect you well know, is the >> difficulty in getting the information and tools required to reprogram >> these radios. >> >> I am now in a position to potentially fund further work on this. >> >> So, as the open-source group with the most experience reprogramming >> baseband radios, what is the feasibility of creating a >> proof-of-concept using the types of phones you already work with to >> send and receive arbitrary data packets without reliance on a cell >> tower (even for time synchronisation)? >> >> I know there are a lot of constraints and problems, but I am most >> interested in creative solutions that can get us to a working >> prototype, however crude, that can be used to demonstrate the >> feasibility of what I am proposing. >> >> If this discussion is off-topic here, I am happy to hold the >> conversation at the serval-project-developers google group, but I am >> equally comfortable with it continuing here. >> >> Thanks in advance, >> Paul Gardner-Stephen. >> Shuttleworth Telecommunications Fellow at Flinders University. >> > > > _______________________________________________ > baseband-devel mailing list > baseband-devel(a)lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/baseband-devel > >

1 0

Re: 900MHz packet radio?
by Dieter Spaar 01 Sep '11

01 Sep '11

Hello Paul, On Thu, 1 Sep 2011 13:41:11 +0930, "Paul Gardner-Stephen" <paul(a)servalproject.org> wrote: > > So, as the open-source group with the most experience reprogramming > baseband radios, what is the feasibility of creating a > proof-of-concept using the types of phones you already work with to > send and receive arbitrary data packets without reliance on a cell > tower (even for time synchronisation)? It depends a lot on what you want to use on the lower layers (e.g. Modulation). The TI Calypso based phones have a built-in GMSK hardware modulator, so it is GMSK. Also the symbolrate is fixed to the one used by GSM. Then there is the DSP which does the signal processing work. Its again tied to the GSM standard (format of the burst and length). It might be possible to put something else into the relativ small RAM inside the DSP, but this could be a huge effort. Besides that you have to modify the hardware of the phone (remove a filter) so that the phone can receive another phone. But this is probably the smallest problem of all. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

1 0

Re: GRPS decode - trying to download firmware to C123
by smithmr103＠gmail.com 31 Aug '11

31 Aug '11

1 0

GRPS decode - trying to download firmware to C123
by smithmr103＠gmail.com 31 Aug '11

31 Aug '11

Hello list, I'm newbee so excuse me for my very basic question. I follow all the instructions on srlabs.de/gprs given by Karsten I have a C123 and a USB / jack 2.5mm - pl2303 based :( All steps are fine until I try to programm the compal ram ;) ./host/osmocon/osmocon -m c123xor -p /dev/ttyUSB0 ./target/firmware/board/compal_e88/layer1.compalram.bin I get : ... PROMPT1... ... PROMPT2... handle_write(): xxxx bytes (xxxx/yyyy) ... ... handle_write(): xxxx bytes (xxxx/yyyy) Received 1 byte : xx Received 1 bytes : yy ... ... Finally I received e.r.r.o.r (byte by byte) NOT ACK RECEIVED... I can also get (not with the same firmware...) : ... PROMPT1... ... PROMPT2... handle_write(): xxxx bytes (xxxx/yyyy) ... ... handle_write(): finished and then... nothing... I'm going to test the cable, as Philipp has told to Pavel. I also bought a RS232 / Jack unlocking Motorola (C123) cable and I own a BlackBox FTDI based USB/RS232 cable... So I'll test it as soon as I receive the cable. Do you think is a matter of cable, who is supposed to be osmocom compatible, or a phone issue or even the USB port... ? Thank you very much for your help and excuse me again with this kind of 'stupid' question about cable. I read almost all the subjects, I did a lot of experimentations in a lot of git branch (master, testing, burst_ind - of course not working with PL2303 ... + d1cb8ea9b784c7acbafbb2fdcedbdf4655c2f6f5 not working too) I think it must work at least in the master branch... Smith

3 5

Suggestion from the PR department
by Ingo Albrecht 31 Aug '11

31 Aug '11

Hey guys I've been noticing the neverending stream of serial cable issues popping up here. To end this, I have a suggestion: how about checking the cable type via sysfs? Greets prom

2 1

GPRS decode:FTDI cable
by list_mailing＠libero.it 30 Aug '11

30 Aug '11

Please, can someone suggest a model for the FTDI cable? I have found different types on internet, but I'd like to buy one it will be definitively ok. Thanks in advance.

2 1

R: Re: GPRS Vs EDGE - Trying to decode my own sessions
by Luca Bongiorni 29 Aug '11

29 Aug '11

Hi all, just to explain what i mean, i've attached a sample and the log from layer23. http://pastebin.com/pepx0tdv As you can see from the log i got the immediate-assign. and the i can see the slots. The only thing that i could be strange is the signal strength that sometimes is good and sometimes reaches -100 dBm. Here is the gprsdecode's output: http://pastebin.com/p7XrtKAt Obviously i tried other ARFCNs of all operators (with different c118/c123, FTDI cable) and i got always the same behaviour. Have you some hints to suggest? Tomorrow i will try with some DP-L10 and pubblish the relative results. P.S: As i already stated, Nohl's samples are well decoded and showed into wireshark. Regards, Luca > Hi Harald, > > Actually i could use some old phones that supports only GPRS (e.g. t68i, t39m, etc..), but these phones are not enough useful and i will explain why: > > - i would like to use a phone that has field-test engineering; > - i would like to set the phone to camp only in a fixed ARFCN. > > I was also trying a Pirelli DP-L10, but unfortunately i can only fix the band and not the arfcn. > > > Btw... after a while i finally found how to force my Blackberry to work on GPRS on a fixed arfcn: > > - Select an arfcn; > - Lock to this cell; [ http://tinyurl.com/3dcc6vm ] > - Disable Uplink 8-PSK; [ http://tinyurl.com/3dxp85d ] > > Finally the phone is ready to start the tests. [ http://tinyurl.com/3rhldrn ] > > > As you can see, that engineering field-test is very useful because is showing which Coding Scheme and TS are used. > > > Unfortunately at this point... even if i tried a lot of times, i could see imm-ass, the TS, but when i'm trying to decode the dumps... nothing is decoded and i cannot even decode third-party sessions that obviously i could find on the same arfcn that i'm using. > > So, at this state of art, I could decode only samples released from Nohl. > Someone else is having same problems? > > > Regards, > > Luca >

1 0

OT: Chinese C118 supply?
by Harald Welte 29 Aug '11

29 Aug '11

Hi all, at the CCC Camp two weeks ago, a Chinese guy approached me, stating that there he has contacts to a considerable supply of very inexpensive C1xx family phones in China. Unfortunately we didn't exchange contact details, so I'm trying this route. If you are the person that has talked to me about this topic, pleaes contact me by private e-mail. I would love to use this opportunity to provide inexpensive C1xx phones to the larger OsmocomBB user community. Thanks in advance, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

GPRS Vs EDGE - Trying to decode my own sessions
by Luca Bongiorni 28 Aug '11

28 Aug '11

Hi all, i'm testing gprsdecode with osmocomBB and using the samples provided from Nohl works well. Using a Blackberry 8300 and my Wind's sim, i tried to dump some my internet sessions. Unfortunately even if i'm locking the MS to a fixed ARFCN, it is "upgrading" from GRPS to EDGE very quickly and i cannot dump an entire session and then decode it on gprsdecode. The only datas i could decode and view on wireshark are few "malformed packets". As i suppose the problem is that i'm not able to fix the MS to work only on gprs. Which phone did Luca use to make his tests? (just a simple one that was not EDGE capable? ) Which was the successful-rate of (third-party) decoded sessions? I'm asking it, because i'm not even able to "see" other's phones sessions... ok, could be possible that everyone else is using only EDGE... but seems strange. Have you some hints for that? Thank you for attention. Regards, Luca

3 4

Re: neighbour cell measurement
by Dieter Spaar 27 Aug '11

27 Aug '11

Hello Andreas, hello Harald, On Thu, 14 Jul 2011 13:44:16 +0200, "Harald Welte" <laforge(a)gnumonks.org> wrote: > > The patches look fine to me. I'd wait for another day if Sylvain or > Dieter have any comments, but otherwise they can be merged. The patches are fine for me. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

3 2

Fwd: Re: neighbour cell measurement
by Andreas Eversberg 27 Aug '11

27 Aug '11

xuchenyu wrote: > > Hello! I think that your neighbour cell measurement code is at the branch > > remotes/origin/laforge/neigh_sb > > > hi xuchenyu, this in an incomplete an experimental code. once finished, it will measure neighbour cells during a call. neighbour cell measurment is supported in idle mode only, if you use master branch, or better "sylvain/testing" branch for some fixes and SIM support. you can enable neighbour cell monitor at VTY: "monitor network 1". regards, andreas

1 0

Re: C115 using loader.compalram.bin&In-Reply
by or_ora＠ovi.com 26 Aug '11

26 Aug '11

1 0

OsmocomBB project Maillist
by jbvl2005＠t-online.de 26 Aug '11

26 Aug '11

Hello Team, would you pls put me in your emaillist ? I am a german guy how interst in this project and other electronic projekts. Is it possible to get a littel help to flash my one motorloa c117 ? Thanks and greets from jens germany :D

1 0

No SIM on GTA02
by radiant radiant 25 Aug '11

25 Aug '11

Hi folks. Running layer1 (no TX) on GTA02 with host applications compiled for GTA02 also. Layer1 seems not able to communicate with SIM card, and so no IMSI etc. Mobile enters in "emergency calls only" mode. Simtest firmware also fails. SIM and phone hardware is checked working with fsogsmd. I cannot find any configure switch to disable/enable SIM, and it has no sense on simtest firmware anyway. Has anything to do with this note on sim.h and the fact that on GTA02 you should cycle the baseband power after osmocon start for romloader to begin? /* Known Bugs: 1.) After powering down the simcard communication stops working */ logs: mobile over layer1 (no TX): ----- <000f> sim.c:1206 init SIM client <0006> gsm48_cc.c:63 init Call Control <0001> gsm48_rr.c:5100 init Radio Ressource process <0005> gsm48_mm.c:1312 init Mobility Management process <0005> gsm48_mm.c:1035 Selecting PLMN SEARCH state, because no SIM. <0002> gsm322.c:5023 init PLMN process <0003> gsm322.c:5024 init Cell Selection process <0003> gsm322.c:5081 Read stored BA list (mcc=XXX mnc=XX $COUNTRY, $NETWORK) <0003> gsm322.c:5081 Read stored BA list (mcc=XXX mnc=XX $COUNTRY, $NETWORK) <0003> gsm322.c:5081 Read stored BA list (mcc=XXX mnc=XX $COUNTRY, $NETWORK) *** Warning: Mobile '1' has default IMEI: 000000000000000 This could relate your identitiy to other users with default IMEI. *** Mobile '1' initialized, please start phone now! <0002> gsm322.c:3804 (ms 1) Event 'EVENT_SWITCH_ON' for automatic PLMN selection in state 'A0 null' <000e> gsm322.c:1356 SIM is removed <0002> gsm322.c:1357 SIM is removed <0002> gsm322.c:800 new state 'A0 null' -> 'A6 no SIM inserted' ----------------- simtest firmware : ----------------SIMTEST----8<----------------- Initializing driver: Power up simcard: (0 bytes) Reset simcard: (0 bytes) 79 f0 ce db f3 cd 8e 7a 10 a1 6c 3a 61 6f 8f (15 bytes) Test Phase 1: Testing bare sim commands... * Testing SELECT: Selecting MF ==> Status word: ffff * Testing SELECT: Selecting DF_GSM ==> Status word: ffff * Testing SELECT: Selecting EF_IMSI ==> Status word: ffff * Testing STATUS: ==> Status word: ffff * Testing READ BINARY: ==> Status word: ffff Data: db 0 0 0 0 0 0 0 0 (9 bytes) ------------END SIMTEST----8<----------------- On the other hand, on GTA02 osmocon or romloader doesn't start if battery is not attached. Keeps staying on "Sending beacon". Regards

1 0

Re: GSM-850
by Dieter Spaar 22 Aug '11

22 Aug '11

Hello Sylvain, On Mon, 22 Aug 2011 16:35:04 +0200, "Sylvain Munaut" <246tnt(a)gmail.com> wrote: > > I think some phones just have swapped IQ lines for easier routing .... This wouldn't explain why the C122 GSM-850/1900 needs the "I/Q-swap" for GSM-850 TX only. And if I remember, Harald tried it with a GSM-900/1800 phone on GSM-850 (of course there are filter issues in this case) and it required the "I/Q-swap" again for GSM-850 only. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

2 1

GSM-850
by Dieter Spaar 22 Aug '11

22 Aug '11

Hello, I don't know if anyone has already successfully used OsmocomBB with GSM-850. It seems that although receiving on GSM-850 works, there are issues when transmitting. The phone produces a signal on the correct ARFCN, however the BTS can't make use of it. The problem seems to be "I/Q-swap", something which can be turned on in the DSP independently for receiving and transmitting. So far it seems that this was not needed, at least for receiving and also for tranmitting when using GSM-900/1800/1900. However for GSM-850 it seems to be essential for transmitting. It is not clear if different phones behave differently, this might be the case. Also it might be the case that some phones require to turn on "I/Q-swap" when receiving on certain bands. Considering all those uncertainties of "I/Q-swap" the appended patch should be considered as a suggestion, it might be neccessary to make it dependend on the phone and also to introduce a similar function for receiving. At least with the patch a C122 GSM-850/1900 phone now works on GSM-850 too. Thank you very much to Harald who remembered that there was this "I/Q-swap" thing for the DSP. Best regards, Dieter Dieter Spaar, Germany spaar(a)mirider.augusta.de

2 1

Preparing mobile for osmocombb
by Pavel Baturko 22 Aug '11

22 Aug '11

Hi All, Do I need to prepare my phone for uploading the firmware with osmocon tool? I tried to load firmware on Motorola C118 and C115 with Prolific PL2303 USB to serial adaptor (computer->usb->com->3.5mm jack->2.5mm jack->phone) and when I briefly press the power-on button of my phone as it's stated in manual - I got no response from phone. Seems it does nothing. Cable seems to be working, because it detect contact with phone's 2.5mm socket when I plug it into phone as - 'got 1 bytes from modem, data looks like: 00 .'. Thanks, Pavel

2 1

libosmocore/osmocombb build error
by Job 21 Aug '11

21 Aug '11

Hi, When building osmocombb with an updated src/shared/libosmocore (0.3.6) the build fails due to make attempting to build utils/osmo-arfcn.c for build-target which does not have stdio. I have no patch as I was not sure what the preferred way to solve it is. Maybe a --disable-utils like for tests? Best regards, Job make[3]: Entering directory `osmocom-bb/src/shared/libosmocore/build-target/utils' CC osmo-arfcn.o ../../utils/osmo-arfcn.c: In function 'arfcn2freq': ../../utils/osmo-arfcn.c:43: warning: incompatible implicit declaration of built-in function 'fprintf' ../../utils/osmo-arfcn.c:43: error: 'stderr' undeclared (first use in this function)

3 4

can we tune osmocombb to 2.4 ghz open band
by Akib Sayyed 20 Aug '11

20 Aug '11

is it possible to tune or use osmocombb to use 2.4 ghz. whole idea is using OpenBTS on 2.4 ghz on BTS side .and osmocombb on 2.4ghz on phone side will it work?? -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

2 1

Enabling PCS bands on the C139 (originally on PCS)
by Lokkju Brennr 20 Aug '11

20 Aug '11

I keep forgetting how to make this work, and it just came up in IRC again, so I thought I would archive the answer to the list: per tnt: in src/target/firmware/board/compal/rffe_dualband.c , the rffe_get_rx_ports might need to have PCS1900 instead of DCS1800 Some phones have different RF wiring and we can't autodetect it ... (the thing is that unless you try manually or look at the PCB you can't really tell ... some PCS phones have it wired to the DCS input ...)

1 0

interact osmocombb with OpenBTS
by josephli 18 Aug '11

18 Aug '11

Hello every, I recently set up the equipment and tried to communicate with the public PLMN and it worked well at that stage. Then I tried to camp on the OpenBTS after switching on the SIM card. When it progressed to location updating request step, the OpenBTS can not receive identity response from MS. The timer t3210 was fired as long as passing a certain period of time and location updating request was sending again iteratively. Anyway location updating was failed. I checked through wireshark from the mobile phone side, showing that MS did send the response however OpenBTS did not receive somehow. Also the timing advance (ta) during that process became 127 which was abnormal, out of the maximum value of 63. I suspected it was also caused by the failure of reception. Is there something wrong about the decoding at OpenBTS side or data packing error at MS side? Is there any way to fix it? Many thanks, Li -- View this message in context: http://baseband-devel.722152.n3.nabble.com/interact-osmocombb-with-OpenBTS-… Sent from the baseband-devel mailing list archive at Nabble.com.

4 5

Failing channel assignment
by Dieter Spaar 12 Aug '11

12 Aug '11

Hello, I noticed some issues in the following situation, I used the "testing" branch (I think it affects both current "testing" branches): - the signalling channel is an SDCCH/8 on a timeslot different from TS0, for example on TS4 - an ASSIGNMENT COMMAND switches to another channel on a different TS than the SDCCH/8, e.g. to TS2 Now the following two problems can happen: 1.) The ASSIGNMENT COMMAND releases the SDCCH/8 with an L1CTL_DM_REL_REQ. Depending on when the L1CTL_DM_REL_REQ is received, it could be that there are still burst scheduled for transmit (e.g. for the SACCH). Due to the L1CTL_DM_REL_REQ, rfch_get_params() will return wrong data (l1s.dedicated.type is now set to GSM_DCHAN_NONE) and the transmit of the bursts happens on the wrong ARFCN and/or TS. My temporary workaround is to clear every item in the scheduler including the current bucket when a L1CTL_DM_REL_REQ is received, this action requires to disable the FIQ, otherwise problems might happen. 2.) There is some code to check for a switch to a lower timeslot in check_lost_frame(). However it can happen that this code gets not triggered although it should: The ASSIGNMENT COMMAND causes a L1CTL_DM_REL_REQ, l1s.dedicated.type is now GSM_DCHAN_NONE ("0"). The next call to check_lost_frame() resets "last_ts" to 0. Now the new channel is assigned (in the example from above its a switch from TS4 to TS 2) and a "LOST" occures, however the required increment of the GSM time does not happen because "last_ts" is 0 although it should be 4. My current workaround is to not reset "last_ts" to 0 in check_lost_frame() but during "L1CTL_RESET_REQ: FULL!". I don't post any patches because my changes are really just ugly workaround which seem to work in (most) situations where it I otherwise observe failures. To really solve this issues something else should be done, maybe put the whole switch of a channel into an atomic operation instead of doing several operations (this is just an idea, maybe there are better solutions). Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

1 0

SMS status?
by Andrew Reusch 12 Aug '11

12 Aug '11

Hi all, I work in a research lab and we're interested in using your stack to send SMS. I've got some time on my hands and a working OpenBTS stack (USRP), so I will probably go ahead and start implementing it in the mobile app. Before I start I just wanted to ask first about the status of mobile-originated SMS? I saw some traffic in the archives a few months back from Gianni about mobile-terminated SMS, but nothing recent about mobile-originated SMS. Barring that, any suggestions on where to start? :) I'm kinda new here. Assuming I get something solid working, I'd of course be willing to contribute it back to the codebase. Thanks, Andrew

3 4

osmocomBB purpose & GSMs
by aik821 aik821 11 Aug '11

11 Aug '11

Hi all, I'm new in these forums and osmocomBB. I was wondering, how does osmocomBB work. install 2 packages, one on the phone and the other on a PC Host? And then you are able to call/sms and anything a GSM phone can do? And you can change the GSM protocol/stack if you want to? So pretty much your PC becomes a GSM terminal? also Are there any simple guides to setup the whole thing? Ahmed

2 1

tx signal strength
by screaming-pain 11 Aug '11

11 Aug '11

Hi all, probably is a silly question but is there a way to set the tx signal strength of the ms? thanks, loretta -- View this message in context: http://baseband-devel.722152.n3.nabble.com/tx-signal-strength-tp3245572p324… Sent from the baseband-devel mailing list archive at Nabble.com.

1 0

Loading firmware on C118
by Павел Батурко 10 Aug '11

10 Aug '11

Hi all, I'm using Motorola C118 and Prolific PL2303 USB to serial adaptor on Ubuntu 10.10. I'm trying to run $ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin and I got got 1 bytes from modem, data looks like: 00 . I press power button and nothing happens. If rub the connector - lines such as I provided above are appears. Is it means that cable is ok? And what could be the problem? Thanks, Pavel

1 0

Bug in frequency list generation of libosmocore
by Dieter Spaar 10 Aug '11

10 Aug '11

Hello, there is a small bug in the calculation of the "Range 1024" format frequency list. A patch is appended. I post it here because I found it while working with OsmocomBB. Best regards, Dieter Dieter Spaar, Germany spaar(a)mirider.augusta.de

1 0

Fwd: i got C115 device . now i am searching for the cable to flash the Build on to the device.
by Alvin Schurman 09 Aug '11

09 Aug '11

---------- Forwarded message ---------- From: Alvin Schurman <alvin.schurman(a)gmail.com> Date: Tue, Aug 9, 2011 at 5:37 PM Subject: Re: i got C115 device . now i am searching for the cable to flash the Build on to the device. To: nagesh reddy <karnatinagesh(a)gmail.com> I too have a C115 at home. I ordered it to flash and so I could experience a little hands-on learning with GPRS. The first thing I noticed was that there was no usb port or data cable input of any kind on the phone. After a little digging, I found that it has a line of JTAG pads under the battery. I wasn't equipped or trained to tackle JTAG so I stopped where you are. Hopefully, you'll get an answer so I can pick up where I left off when I'm back home with my C115. Cheers, Al On Tue, Aug 9, 2011 at 9:48 AM, nagesh reddy <karnatinagesh(a)gmail.com>wrote: > Hi Guys, > > > i got the Motorola C115 device and i want to flash the Build into the > device. from where can i get the cable > so that i can flash the stack and seee. > > > > regards, > nagesh. > > >

1 0

i got C115 device . now i am searching for the cable to flash the Build on to the device.
by nagesh reddy 09 Aug '11

09 Aug '11

Hi Guys, i got the Motorola C115 device and i want to flash the Build into the device. from where can i get the cable so that i can flash the stack and seee. regards, nagesh.

2 1

RRLP support in osmocombb
by Akib Sayyed 07 Aug '11

07 Aug '11

i am bit new to GSM and osmocombb. does osmocombb support RRLP protocol. @herald i saw in your presentation that we can send custom time advance. does that related to RRLP. also can we fake position using osmocombb? -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

1 0

Issue with GSM1800/1900
by Dieter Spaar 04 Aug '11

04 Aug '11

Hello Andreas, there is a small issue with GSM1800/1900 in the mobile application: When a location update is performed, the wrong power capability is set in Mobile Station Classmark 1. As a workaround I fixed it this way: --- ./host/layer23/src/mobile/gsm48_mm.c Mon Jul 25 15:40:50 2011 +++ r:./host/layer23/src/mobile/gsm48_mm.c Thu Aug 04 13:15:09 2011 @@ -2321,7 +2321,11 @@ gsm_print_mcc(subscr->mcc), gsm_print_mnc(subscr->mnc), subscr->lac); /* classmark 1 */ +#if 0 pwr_lev = gsm48_current_pwr_lev(set, rr->cd_now.arfcn); +#else /* cd_now not yet set, take selected cell ARFCN !? */ + pwr_lev = gsm48_current_pwr_lev(set, rr->ms->cellsel.sel_arfcn); +#endif gsm48_encode_classmark1(&nlu->classmark1, sup->rev_lev, sup->es_ind, set->a5_1, pwr_lev); /* MI */ The reason for the the wrong power capability comes from the fact that "rr->cd_now" is not yet set and so the ARFCN is 0 which causes the GSM900 power capability to be used. It is set to "Class 4" in the configuration file per default, however this value is not defined for GSM1800/1900. I am not sure if my workaround is perfect, you are the expert for "mobile" ;-) Although this might sound like not that important (networks with OpenBSC or OpenBTS don't care at all about the value) there are some real networks out there which don't like it. On a related note: The default TX power calibration curve for GSM900 causes too less TX power for GSM1800/1900, expecially for low power settings. I will try to improve my current workaround for this and provide a patch. Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

2 1

Invitation to connect on LinkedIn
by Nageswara Reddy 04 Aug '11

04 Aug '11

I'd like to add you to my professional network on LinkedIn. - Nageswara Nageswara Reddy Sr Tech Leader at Aricent Technologies Bengaluru Area, India Confirm that you know Nageswara Reddy: https://www.linkedin.com/e/-5d8k6r-gqxioekp-57/isd/3755268124/Ee1Qtm6Z/ View Nageswara's profile: http://www.linkedin.com/e/-5d8k6r-gqxioekp-57/LawAMDCaoL5bNI_JVaTOJ82bmKOYl… -- You are receiving Invitation to Connect emails. Click to unsubscribe: http://www.linkedin.com/e/-5d8k6r-gqxioekp-57/LawAMDCaoL5bNI_JVaTOJ82bmKOYl… (c) 2011 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

1 0

returning twice in lapdm.c
by screaming-pain 04 Aug '11

04 Aug '11

Dear all, in the if starting at line 1591 in lapdm.c there are two return, maybe you want to fix this 1591 if (!mctx.dl) { LOGP(DLAPDM, LOGL_NOTICE, "Received frame for unsupported " "SAPI %d!\n", sapi); return -EINVAL; msgb_free(msg); return -EIO; 1597 } Regards, Loretta -- View this message in context: http://baseband-devel.722152.n3.nabble.com/returning-twice-in-lapdm-c-tp321… Sent from the baseband-devel mailing list archive at Nabble.com.

4 7

small bug?
by Job 03 Aug '11

03 Aug '11

Hi, I noticed in src/target/firmware/calypso/dsp.c: static void dsp_pre_boot(const struct dsp_section *bootcode) { dputs("Assert DSP into Reset\n"); calypso_reset_set(RESET_DSP, 1); if (bootcode) { dputs("Loading initial DSP bootcode (API boot mode)\n"); dsp_upload_sections_api(dsp_bootcode, DSP_BASE_API_MIRROR); It seems that the intention is to pass bootcode to dsp_upload_sections_api, but it is still using the hardcoded dsp_bootcode. No functional impact as it is nowhere used with any other bootcode. Best regards, Job

2 1

where is the gprs part source in the osmocom source tree?
by John Wu 03 Aug '11

03 Aug '11

Hi all, I need the GPRS source code for reference, where is it in osmocom source tree?

2 1

C115 using loader.compalram.bin
by Bruce, Bryan 01 Aug '11

01 Aug '11

Hello, I am using a C115 with a t191 cable. We have completed the "Getting Started" steps and have compiled all the necessary code. I are currently trying to run osmocon to download code onto the phone. The following output appears when we run the script: bruceb@ubuntu:~/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 1 bytes from modem, data looks like: 2d - got 1 bytes from modem, data looks like: 34 4 got 1 bytes from modem, data looks like: 29 ) got 1 bytes from modem, data looks like: 28 ( got 1 bytes from modem, data looks like: 32 2 got 1 bytes from modem, data looks like: 39 9 got 1 bytes from modem, data looks like: 30 0 got 1 bytes from modem, data looks like: 20 got 1 bytes from modem, data looks like: 2d - got 1 bytes from modem, data looks like: 34 4 got 1 bytes from modem, data looks like: 29 ) got 1 bytes from modem, data looks like: 0a . got 1 bytes from modem, data looks like: 0d . got 1 bytes from modem, data looks like: 02 . These lines continue and no script indicates anything is being downloaded, as shown on the wiki site. I have unlocked the phone and put it in "earphone" mode beforehand. I have also tried to press the power button as directed to. Are there any suggestions on how to fix this problem? Thank you, Bryan Bruce

2 1

OT: GTA04 - Openmoko
by Benjamin Hagemann 28 Jul '11

28 Jul '11

Hello, a german news website gave me the hint to new infos about the GTA04. english sites: http://projects.goldelico.com/p/gta04-main/ http://lists.goldelico.com/pipermail/gta04-owner/2011-July/000185.html http://www.handheld-linux.com/wiki.php?page=GTA04-Early-Adopter&referer=Neo… and the german news about this topic: pro-linux: OpenMoko GTA04 bald bereit zum Test http://www.pro-linux.de/news/1/17318/openmoko-gta04-bald-bereit-zum-test.ht… -- Have a nice day, Benny gpg 0xFC505AB0 jabber benny(a)benny.de sip benny(a)benny.de

2 1

IMEI numbers, signal strength
by miprom68＠gmail.com 27 Jul '11

27 Jul '11

Can someone help with these? 1) With the GSM debugger phone, how difficult is it to get only IMEI numbers of received packets? 2) Can the debugger phone report the signal strength of received packets? If not, is it possible? 3) Is there any way with mods to get I/Q out of the DSP? 4) Is there any work going on to make a CDMA debugger phone? 5) Are there any GSM phones that have an option to force calls to be made only on 3G/4G? Thank you, Ben

5 13

Tx Support
by iBruno 26 Jul '11

26 Jul '11

Hello community After making the changes to Makefile.inc (src/target/firmware) -include Makefile.inc # Uncomment this line if you want to enable Tx (Transmit) Support. -CFLAGS += -DCONFIG_TX_ENABLE +CFLAGS += -DCONFIG_TX_ENABLE # Uncomment this line if you want to write to flash. #CFLAGS += -DCONFIG_FLASH_WRITE I'm trying to figure out, what to do with this part: enable CONFIG_TX_ENABLE diff --git a/src/target/firmware/Makefile b/src/target/firmware/Makefile index 56e0068..c69aab7 100644 --- a/src/target/firmware/Makefile +++ b/src/target/firmware/Makefile @@ -73,7 +73,7 @@ ANY_APP_LIBS+=calypso/libcalypso.a layer1/liblayer1.a lib/libmini.a comm/libcomm ...Meanwhile I tried to compile, and at the time Makefile.inc is callled starts looping forever.... Makefile.inc:135: warning: overriding commands for target `board/compal_e99/loader.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/loader.highram.size' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.map' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.size' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.map' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.size' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.size' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.size' Makefile.inc:171: warning: overriding commands for target `calypso/libcalypso.a' Makefile.inc:171: warning: ignoring old commands for target `calypso/libcalypso.a' Makefile.inc:171: warning: overriding commands for target `layer1/liblayer1.a' Makefile.inc:171: warning: ignoring old commands for target `layer1/liblayer1.a' Makefile.inc:171: warning: overriding commands for target `comm/libcomm.a' Makefile.inc:171: warning: ignoring old commands for target `comm/libcomm.a' Makefile.inc:171: warning: overriding commands for target `lib/libmini.a' Makefile.inc:171: warning: ignoring old commands for target `lib/libmini.a' Makefile.inc:208: warning: overriding commands for target `clean' Makefile.inc:208: warning: ignoring old commands for target `clean' Makefile.inc:212: warning: overriding commands for target `distclean' Makefile.inc:212: warning: ignoring old commands for target `distclean' ^Cmake: *** [firmware] Interrupt After reviewing the groups & googing, didn't came out with understanding/solution Very appreciated, if help can be given. Thank you Bruno.

1 0

positioning
by Matzi Kratzi 25 Jul '11

25 Jul '11

(In a sort-of-answer to the triangulating mail a while ago:) > i wanted to know is it possible to triangulate any gsm cellphone with osmocombb?? Hi, It would be possible triangulate your own position using osmocombb. Assumption 1 (A1): The base stations of GSM are very stable and can keep running for months or years without interruption. Assumption 2 (A2): Osmocombb has a free running quarter bit counter that it never restarts when power is on. The timings of different cells are calculated relative to this free running counter. To be able to triangulate a phone, we need information about the cells in the area: The GSM TDMA system has a periodicity for broadcasted messages such as sync and SI1. The timing of these can be predetermined as an offset relative to the free running counter in A2. Note that the offset includes the propagation time for the signal from the base station to the mobile station. If the position of the mobile phone with osmocombb (MS) is known, one can get the offset for the first base station broadcasts (dt_BS1). If the MS is moved later to at least three other known positions and the same offsets are calculated, one can calculate the actual offset between the MS free running counter and the BS1 without the propagation time included. At the same time the actual position of the BS is calculated. [1] An MS should do measurements on neighbour cells as well, and can therefor do exactly the same calculations for several BS:s at the same time. An interesting aspect of this is that it is then possible to calculate the difference in timing for several BS:s. If the positions and relative timings for the BS:s in an area are known, it is possible to calculate the position of an MS. This time we do the same calculations, but now the relative timings for the BS:s and the position are known and the same for the MS is unknown. An interesting fact is that osmocombb could use the timings for BS:s from several operators to increase the accuracy of the calculations. Assumption 1 can be held for granted. Assumption 2 could be made true if it is not already true. The concept could probably otherwise be used anyway if that is not accepted. 1 http://en.wikipedia.org/wiki/Multilateration MS Mobile station (phone, modem) BS Base station dt_BSx timing offset from the free running timer to base station number x /Matzi

1 0

Some considerations about IMSI Detach DoS Attack
by Gloria Mazzi 22 Jul '11

22 Jul '11

Hi all, as stated on OsmocomSecurity: "A malicious attacker knowing the IMSI or TMSI of a victim can thus send hand-crafted IMSI DETACH messages to a cell, causing the network to assume the MS is no longer present in the network.This will effectively prevent the delivery of all mobile-terminated (MT) services, such as SMS, voice calls, CSD, ...". Following the theory i've better understood how it works [1]*, but still i have some questions for you: - what could happen if i will clone one SIM (Ki, IMSI) and use it to register on the same network, but on different BTS/LAC, two phones? Which will be rejected as first? Or both? - if i will send an IMSI detach with one of them... also the other (that is phisically in another BTS/LAC) will be disconnected? - what could happen if i will connect a C123 with ./mobile to the network using another SIM and then trying to forge IMSI_DET_IND with victim's IMSI/TMSI and send to the network where the victim is connected (that could mean the same network, but different BTS/LAC), this DoS will still be accomplished? What exactly i would like to know is, if someone already made some experiments on it (obviously on private networks, with a legal experimental license.) and eventually if there are any interesting results. Thank you for attention. Cheers Gloria *[1] - http://www.gsmfordummies.com/gsmevents/detach.shtml

4 5

Telecommunication and Wireless Hacking at CCC CAMP 2011
by Fabio Pietrosanti (naif) 22 Jul '11

22 Jul '11

Hi all, i just wanted to send a summary of all most cool talk that will be at CCC CAMP 2011 related to Telecommunications and Wireless Technologies hacking: Open-source 4G radio - It's time to start WiMAX and LTE hacking http://events.ccc.de/camp/2011/Fahrplan/events/4446.en.html Applied Research on security of TETRA radio - Digital radio technology beyond GSM http://events.ccc.de/camp/2011/Fahrplan/events/4496.en.html GPRS Intercept - Wardriving phone networks http://events.ccc.de/camp/2011/Fahrplan/events/4504.en.html Introduction to Satellite Communications - Installation and Operation of Satellite Systems http://events.ccc.de/camp/2011/Fahrplan/events/4442.en.html Transition Telecom - Telecommunications and networking during energy descent http://events.ccc.de/camp/2011/Fahrplan/events/4459.en.html Anyone missing to the list? -naif

1 1

AW: gpsd and as-needed patches
by Andreas.Eversberg 21 Jul '11

21 Jul '11

hi vlatko, thanx for your patches. i don't have knowledge about gpsd api. before i can apply them, i need to know about gps_waiting() function. the osmo_gpsd_cb() function in common/gps.c is called when there is data to be read from gpsd. this function (like any other function) may not delay or block. (except for the CPU processing time of the function.) if no data is available from gpsd, the function must continue with "goto gps_not_ready;" immidately. what will gps_waiting() do in case there is no (complete) information available? regards, andreas

2 1

gpsd and as-needed patches
by Vlatko Kosturjak 20 Jul '11

20 Jul '11

Hello! Hopefully this is right place to send patches since I don't have access to tracker. I'm sending two patches against latest git version. First one is updating gpsd support since new gpsd have few functions changed: I've #ifdefed each offending function, so you can check each function in configure process or just wrap everything inside same #ifdef, depending on your wish. I have #defined timeout, but it can be done as variable if you think 2000 miliseconds is not good for everybody. Other patch is just quick hack to support --as-needed linker flag, so osmocombb can compile fine on distros which enforce such flag. In order, to read more about flag, read here: http://www.gentoo.org/proj/en/qa/asneeded.xml (In short, order of flags do matter) Hope it helps, -- Vlatko Kosturjak - KoSt

1 0

Is it possible to triangulate cellphone with osmocombb
by Akib Sayyed 18 Jul '11

18 Jul '11

Guys i bit new to osmocombb i wanted to know is it possible to triangulate any gsm cellphone with osmocombb?? -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

1 0

Motorola C116 experiment
by Henk 18 Jul '11

18 Jul '11

Hi, I could not resist buying a C116 for 15 euro, so I compiled osmocombb and connected a 3.3V serial cable. Of course the C116 was not in the supported list, but I was hoping it would work as it seems that it is very similar to the C115. Here is my load attempt: (used -m c123 ) but there's no loading of the image. I am not using TX mode, also I don't have a SIM installed. Anything I can try to get it working? ./osmocon -p /dev/ttyS0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 00 81 .. got 4 bytes from modem, data looks like: 1b f6 02 00 .... got 1 bytes from modem, data looks like: 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=16788, hdr_len=4, dnload_le n=16795 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 got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: 66 f 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 Regards, Henk

6 7

AW: GSM 03.22 bug / unreachable code?
by Andreas.Eversberg 18 Jul '11

18 Jul '11

> while using Smatch on layer23, I discovered a potential problem in GSM > 03.22: There is a loop with an if-statement, and there might be missing > curly braces. hi harald, you are right. patch is committed. thanx, andreas

1 0

USB -FTDI 232RL- RS232 Converter
by iBruno 16 Jul '11

16 Jul '11

Hello I am having troubles, to find the decent cable/interface to get this working properly!! I bough converter USB -FTDI 232RLChip- RS232, Converter. IS giving me 6.60v Output.. and I needed 3.3v. Electronically, what can I do, to adjust for the correct Voltage? My phone didn't fry, besides I got connection! when I load the hello world or layer one, is not completing the task! I believe is because of the amount of power. If you know a cable that works decently, let me know :-) Big thanks to whole community.

2 1

GSM 03.22 bug / unreachable code?
by Harald Welte 16 Jul '11

16 Jul '11

Hi Andreas, while using Smatch on layer23, I discovered a potential problem in GSM 03.22: There is a loop with an if-statement, and there might be missing curly braces. Do you think this is the correct way to fix it? diff --git a/src/host/layer23/src/mobile/gsm322.c b/src/host/layer23/src/mobile/gsm322.c index 210215e..766ffbf 100644 --- a/src/host/layer23/src/mobile/gsm322.c +++ b/src/host/layer23/src/mobile/gsm322.c @@ -983,9 +983,10 @@ static int gsm322_a_user_resel(struct osmocom_ms *ms, struct msgb *msg) /* search current PLMN in list */ llist_for_each_entry(plmn_entry, &plmn->sorted_plmn, entry) { if (plmn_entry->mcc == plmn->mcc - && plmn_entry->mnc == plmn->mnc) + && plmn_entry->mnc == plmn->mnc) { plmn_found = plmn_entry; break; + } } /* abort if list is empty */ -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

neighbour cell measurement
by Andreas.Eversberg 15 Jul '11

15 Jul '11

hi, i would like to commit my well tested neighbour cell measurement code, as well as the improved cell selection / re-selection process soon. with it, it is possible to move with the mobile phone while beeing in idle mode (no call). it tracks neighbour cells and switches if a better cell is detected. i found and fixed many bug issues in mobility management and cell selection process. i did allot of driving tests. in order to do that, the neighbour cell measurement code for layer1 is required. this code must be reviewed first. i splitted it in three patches: neigh_getset.patch [layer1] Adding rffe_set_gain() and rffe_get_gain() to get/set computed gain. rffe_compute_gain() is the new name for rffe_set_gain(). I needed to change this, to solve the name collision with the rffe_set_gain() function, which actually sets the absolute gain. rffe_get_gain() will now read the absolute gain which has been computed by rffe_compute_gain() or set by rffe_set_gain(). neigh_l23.patch [layer23] Adding neighbour cell measurement to L1CTL interface. (layer23) neigh_l1.patch [layer1] Adding neighbour cell measurement code to layer1. When listening to BCCH, layer1 may measure the power level of neighbour cells. A list of neighbour cell frequencies need to be sent to layer1. After the measurement is done, the results are indicated to layer23. andreas

4 3

AW: neighbour cell measurement
by Andreas.Eversberg 15 Jul '11

15 Jul '11

> The patches look fine to me. I'd wait for another day if Sylvain or > Dieter have any comments, but otherwise they can be merged. i will remove some comments and temporary debug prints before committing.

1 0

problems to run ./mobile app
by josephli 15 Jul '11

15 Jul '11

Hello every: When I tried to run ./mobile -i 127.0.0.1, the words Failed to parse the config file: '/root/.osmocom/bb/mobile.cfg' Please check or create config file using:'touch /root/osmocom/bb/mobile.cfg' came out. I checked my directory /ect and there is nothing there. It seems that network between my PC and phone is block so that the application ./mobile can not communicate with phone. However the layer1 can load on the phone and work properly. Can any one tell my how to fix this problem? Cheers, Li -- View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-to-run-mobile-app-tp316… Sent from the baseband-devel mailing list archive at Nabble.com.

2 8

Help me I have a difficult problem
by adel 13 Jul '11

13 Jul '11

Hello I'm having a problem in the start mobile application ~/osmocom-bb$ cd src/host/layer23/src/mobile ~/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. Failed to parse the config file: '/etc/osmocom/osmocom.cfg' Please check or create config file using: 'touch /etc/osmocom/osmocom.cfg' ~/osmocom-bb/src/host/layer23/src/mobile$ Please help me as soon as -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Help-me-I-have-a-difficult-probl… Sent from the baseband-devel mailing list archive at Nabble.com.

11 17

Is data actually sent if "COMPILED WITHOUT TX SUPPORT"?
by Sergey 08 Jul '11

08 Jul '11

Hello! Is any way that data is actually sent to air if on loading "layer1.compalram.bin" 'osmocon' says: "THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!! " ? E.g. when 'mobile' says "sending page response" does it really communicate with the BTS? I'm talking about main branch (not testing) and compiled without TX support. Sorry if it's obvious, I just dont want to find "the very extent permittable by law".

2 1

gsm specifications
by Sergey 06 Jul '11

06 Jul '11

Hello, everyone! I've got c123-compatible phone, the firmware is running and that's really cool. Testing branch even sometimes says that a call has been released, but it doesn't seem to reach the target (no ringing). I would like to debug and maybe contribute, but... But here is a problem: I don't understand GSM and can't find reasonable documents to read. I've looked through a book on gsm "GSM and Personal Communications Handbook", but it doesn't seem to provide enough info. Specifications of GSM I found at http://www.3gpp.org/specification-numbering are too plentiful. Could you please advise some books to understand the protocols? Or could you tell me where to look for specifications and which should be read first (an what to be read at all) ?

4 5

Bounce action notification
by mailman＠lists.osmocom.org 06 Jul '11

06 Jul '11

This is a Mailman mailing list bounce action notice: List: baseband-devel Member: andre(a)ac.nl.eu.org Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman(a)lists.osmocom.org.

1 0

GPSD support
by Victor P 06 Jul '11

06 Jul '11

Hello.I have been trying to use cell_log with bluetooth GPS. I used gpsd v 2.37 and v 2.95, but in both cases I had the error "Osmocom was compiled without gpsd support". Should I use another version of gpsd or mistake in compilation (any patch?)? thank you for helpWith best wishes,Victor

2 1

Success at last - C139 now working Layer1.bin displayed on phone :)
by Raz Sharif 05 Jul '11

05 Jul '11

Dear all, the last few days I have as you know sent a few mails in my quest to delve into the Osmocomm GSM stack. A few problems later and a few substitutes later such as a C139 phone versus the C115 am I now good to go it would appear. Please see below. I did a lot of RTFM and would also like to to thank the folks who provided me with pointers. I will no doubt have a few more issues so lets see. In summary - The Prolific cable works fine albeit a small cut back on the connector - 2.5mm side C115 is supported but if you can go for the C139 - Too many issues to resolve with C115 maybe due to a specific Firmware variant. If you have the time to hack around I am sure it not difficult to work. Here's my Boot loader dump. Please see below. Thanks Raz http://pastebin.com/A1xf8Wkt

1 0

C139 confirmation of operation from Users please.
by Raz Sharif 05 Jul '11

05 Jul '11

Hi Folks, I recently mailed the group to discuss issue with the C115 Phone and am now trying the C139. It appears to load and i get :- ./osmocon -p /dev/ttyUSB0 -m c140 -c ../../target/firmware/board/compal_e86/layer1.highram.bin ../../target/firmware/board/compal_e86/chainload.compalram.bin read_file(../../target/firmware/board/compal_e86/chainload.compalram.bin): file_size=4132, hdr_len=4, dnload_len=15341 read_file(../../target/firmware/board/compal_e86/chainload.compalram.bin): file_size=4132, hdr_len=4, dnload_len=15341 got 2 bytes from modem, data looks like: 2e c8 .. got 1 bytes from modem, data looks like: 1b . got 4 bytes from modem, data looks like: 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 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/15341) handle_write(): 4096 bytes (8192/15341) handle_write(): 4096 bytes (12288/15341) handle_write(): 3053 bytes (15341/15341) 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: 45 E got 1 bytes from modem, data looks like: 53 S got 1 bytes from modem, data looks like: 16 . Received DOWNLOAD NACK from phone, something went wrong :( 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 got 1 bytes from modem, data looks like: 00 . kbuildsycoca4 running... Also when i run the Mobile app i get :- telnet localhost 4247 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Welcome to the OsmocomBB control interface OsmocomBB> enable OsmocomBB# exit Exit current mode and down to previous mode help Description of the interactive help system list Print command list write Write running configuration to memory, network, or terminal show Show running system information disable Turn off privileged mode command configure Configuration from vty interface copy Copy configuration terminal Set terminal line parameters echo Echo a message back to the vty who Display who is on vty monitor Monitor... no Negate a command or set its defaults off Turn mobiles off (shutdown) and exit sim SIM actions network Network ... call Make a call OsmocomBB# sim % Command incomplete. OsmocomBB# show % Command incomplete. OsmocomBB# Thanks and would be grateful for your support as I appear to be edging forwards. :) and hopefully not backwards. Raz

1 0

Osmocom Loading Issues - TTYUSB0 loopback
by Raz Sharif 04 Jul '11

04 Jul '11

Hi folks, further to my previous email i now ran : I simply pressed the Power Switch a few times but not power on. This is what is recorded. As you will recall i get the FMTool Error and aborted message and never see Prompt2. With no Osmocom programs running can someone please confirm that this output is correct or indeed suggests that the Phones Serial Line or other Firmware or Phone Hardware is causing this error please - would be grateful. Thanks Raz _________________________________________- cat < /dev/ttyUSB0 >| rs.txt 00000000 00 2e 00 1b f6 02 00 41 01 40 66 74 6d 74 6f 6f |.......A.@ftmtoo| 00000010 6c 65 72 72 6f 72 00 00 2f 00 1b f6 02 00 41 01 |lerror../.....A.| 00000020 40 66 74 6d 74 6f 6f 6c 65 72 72 6f 72 00 00 2f |@ftmtoolerror../| 00000030 00 1b f6 02 00 41 01 40 66 74 6d 74 6f 6f 6c 65 |.....A.@ftmtoole| 00000040 72 72 6f 72 00 00 2f 00 1b f6 02 00 41 01 40 66 |rror../.....A.@f| 00000050 74 6d 74 6f 6f 6c 00 00 00 00 00 00 00 00 00 00 |tmtool..........| 00000060 00 00 00 00 00 2f 00 1b f6 02 00 41 01 40 66 74 |...../.....A.@ft| 00000070 6d 74 6f 6f 6c 65 72 72 6f 72 00 |mtoolerror.|

1 0

osmocn question
by eisencah eisenach 04 Jul '11

04 Jul '11

Hi everyone. One remark regarding osmocon : it seems to me that we're reading one byte at the time from the serial port once we're done with downloading code into RAM. That seems quite on overhead (specially on slow machines like mine). I believe we should modify that once dnload.expect_hdlc == 0 we can free up the entire buffer. Is that so or I'm missing something? Mihai.

1 0

Fwd: Please can anyone advise me - FMTOOL Error and no further processing
by Sébastien Lorquet 04 Jul '11

04 Jul '11

Please do not use reply in gmail, but reply to all instead. Otherwise you will only write to the message's author, Sebastien ---------- Forwarded message ---------- From: Raz Sharif <issertiv(a)gmail.com> Date: Sun, Jul 3, 2011 at 9:34 PM Subject: Re: Please can anyone advise me - FMTOOL Error and no further processing To: Sébastien Lorquet <squalyl(a)gmail.com> Sorry yes i did post this message before in an attempt to get some better insight in to the issues. The loopback test i shorted the inside and outermost pins and echo of characters appeared. I think cable is ok. Its a prolific usb to serial. I do not have a serial connector so cannot try the FTD cable option. All software looks ok but the Osmocon.just hangs and FMT tool error. So i am a little stuck to be honest. Sorry for sending this twice. Thanks Raz On 3 Jul 2011 19:29, "Sébastien Lorquet" <squalyl(a)gmail.com> wrote:

4 6

Osmocom FMTool error
by Raz Sharif 02 Jul '11

02 Jul '11

Please could you assist me with some pointers, Good work btw. I am using a C115 with the T191 prolific USB cable. I can talk to the phone but cannot load the Layer1 Stack. I get : ./osmocon -p /dev/ttyUSB0 -m c123 ../../target/firmware/board/compal_e88/layer1.compalram.bin got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 2f / got 1 bytes from modem, data looks like: 00 . got 3 bytes from modem, data looks like: 1b f6 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: 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=51272, hdr_len=4, dnload_len=51279 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 got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . I press the switch once and it just jumps and does the same again and again and again. I read that this maybe a timing issue. I have installed on 64 Bit and 32 bit ubunto on a fast machine and the result is the same. Also i do not see Layer23 command during compile. Please advise me i am happy to do the debugging but any pointers would help me as i am willing to learn from this great work that has been done by you and the team. Thanks Raz

1 0

Please advice - C115 FMTOOL - Ramloader Aborted
by Raz Sharif 02 Jul '11

02 Jul '11

Dear Folks, After much deliberation and waiting I finally rxed a C115 and the T1 Cable USB. I am running Backtrack 5 and have compiled the Osmocomm bundles and all executable seem to be present. When i plug om the Jack cable and press the power switch i get this :- ~/osmocom-bb/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/layer1.compalram.bin got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 2f 00 /. got 4 bytes from modem, data looks like: 1b f6 02 00 .... got 1 bytes from modem, data looks like: 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=48808, hdr_len=4, dnload_len=48815 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 got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . Have have tried with Xor and without. What am I missing folks - please advice as have been at this a while now with same results. Thanks in advance. Raz

4 5

Motorola C115 with OsmocomBB
by Raz Sharif 30 Jun '11

30 Jun '11

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<http://bb.osmocom.org/trac/wiki/MotorolaC123>/C121/C122 series. So far, all our software (written for the MotorolaC123<http://bb.osmocom.org/trac/wiki/MotorolaC123>) is working on the C115/C117, too. The PCB is marked E87, i.e. one number less than the MotorolaC123<http://bb.osmocom.org/trac/wiki/MotorolaC123>(E88). Any feedback would be very appreciated from anyone who has had success with this particular phone from the Users side. Thanks Raz

4 3

replacing the RX filter with a balun on the c139
by Joshua Lackey 30 Jun '11

30 Jun '11

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. Similar to Sylvain's experience, the schematic doesn't match reality. Just as Sylvain describes, the signal from the balanced output appears to be going through inductors rather than capacitors and there isn't a bridging inductor. However on my c139, the unbalanced input is missing the inductor to ground on the EGSM path and is missing the capacitor to ground on the DCS path. (Sylvain had a capacitor to ground on DCS where the schematic has an inductor to ground.) You can find a picture of what I'm looking at here: http://thre.at/c139/c139rxfilters.jpg . I've placed the c139 schematics in that directory as well, http://thre.at/c139 . My guess is that the filters in the schematics had a different unbalanced impedance than the ones they ended up placing on the c139. But I'm not an EE, and that is just a guess. I can't read the markings on the filters I have, so I can't check the unbalanced input from a data sheet. I also don't have a way to measure the components that are there now so I can't try and compute the value. My question is, does this matter? That is, should I use the same balun that Sylvain chose or should I find one with a different unbalanced impedance? Alternatively, should I use the same baluns and just install an inductor (or capacitor on DCS) to ground so that it matches Sylvain's c123? Any ideas? (As an aside, the baluns that Sylvain chose aren't perfect for the US frequency range, but they should work okay.)

4 6

bb.osmocom.org question
by Rebecca Wilson | TwinLinks 29 Jun '11

29 Jun '11

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

2 1

help me i have motorola c123
by adel 29 Jun '11

29 Jun '11

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-tp3… Sent from the baseband-devel mailing list archive at Nabble.com.

2 1

Compile error with gpsd 2.96 in layer23
by Malte Krupa 28 Jun '11

28 Jun '11

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

3 3

[PATCH] Updated GPS code so that it is compatible with new gpsd version.
by Konstantin Weitz 28 Jun '11

28 Jun '11

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

1 0

libosmocore / logging from within libraries
by Harald Welte 27 Jun '11

27 Jun '11

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 <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 2

help me i have motorola c123
by adel 26 Jun '11

26 Jun '11

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-tp3… Sent from the baseband-devel mailing list archive at Nabble.com.

2 1

1 of 4 phones not loading
by Job 26 Jun '11

26 Jun '11

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

1 0

Re: Cygwin Windows --> Accessing serial port.
by Dieter Spaar 25 Jun '11

25 Jun '11

On Sat, 25 Jun 2011 23:13:10 +0530, "R M" <rm.engineer84(a)gmail.com> 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(a)mirider.augusta.de

1 0

Re: Cygwin Windows --> Accessing serial port.
by Dieter Spaar 25 Jun '11

25 Jun '11

Hello Harald, On Sat, 4 Jun 2011 08:46:50 +0200, "Harald Welte" <laforge(a)gnumonks.org> 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(a)mirider.augusta.de

6 8

Layer3 interaction
by Paul Lambert 25 Jun '11

25 Jun '11

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

3 2

Progress with NuttX
by l--putt 24 Jun '11

24 Jun '11

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

1 0

Sending and receiving TCH frames with 'mobile'
by Michael 23 Jun '11

23 Jun '11

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

1 0

the need all people to make
by 麦田守望 22 Jun '11

22 Jun '11

i find a way maybe the phone(motorola) it can to make usrp

1 0

AW: Facing issues in using OSMOCOM
by Andreas.Eversberg 15 Jun '11

15 Jun '11

> 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@gmail.com] Gesendet: Mittwoch, 15. Juni 2011 13:31 An: Andreas.Eversberg Cc: Basem Ahmed; baseband-devel(a)lists.osmocom.org Betreff: Re: Facing issues in using OSMOCOM On Wed, Jun 15, 2011 at 11:35 AM, Andreas.Eversberg <Andreas.Eversberg(a)versatel.de> 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

1 0

AW: Facing issues in using OSMOCOM
by Andreas.Eversberg 15 Jun '11

15 Jun '11

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.

3 2

Re: Facing issues in using OSMOCOM
by Basem Ahmed 15 Jun '11

15 Jun '11

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 <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: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 <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: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 <Andreas.Eversberg(a)versatel.de> wrote: From: Andreas.Eversberg <Andreas.Eversberg(a)versatel.de> Subject: Re: Facing issues in using OSMOCOM To: "Basem Ahmed" <eng_basemm(a)yahoo.com> Cc: baseband-devel(a)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.)

2 1

Re: Facing issues in using OSMOCOM
by Andreas.Eversberg 14 Jun '11

14 Jun '11

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.)

1 0

Re: mobile - making a call
by eisencah eisenach 14 Jun '11

14 Jun '11

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 <wbg_1000(a)yahoo.com> wrote: From: eisencah eisenach <wbg_1000(a)yahoo.com> Subject: Re: Fw: Re: mobile - making a call To: baseband-devel(a)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(a)gmail.com> wrote: From: Sylvain Munaut <246tnt(a)gmail.com> Subject: Re: Fw: Re: mobile - making a call To: "eisencah eisenach" <wbg_1000(a)yahoo.com> Cc: baseband-devel(a)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

1 0

Fw: Re: Facing issues in using OSMOCOM
by Basem Ahmed 13 Jun '11

13 Jun '11

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 <eng_basemm(a)yahoo.com> wrote: From: Basem Ahmed <eng_basemm(a)yahoo.com> Subject: Re: Facing issues in using OSMOCOM To: "baseband-devel" <baseband-devel(a)lists.osmocom.org> 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 <eng_basemm(a)yahoo.com> wrote: From: Basem Ahmed <eng_basemm(a)yahoo.com> Subject: Re: Facing issues in using OSMOCOM To: "baseband-devel" <baseband-devel(a)lists.osmocom.org> Cc: "Sylvain Munaut" <246tnt(a)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(a)gmail.com> wrote: From: Sylvain Munaut <246tnt(a)gmail.com> Subject: Re: Facing issues in using OSMOCOM To: "Basem Ahmed" <eng_basemm(a)yahoo.com>, "baseband-devel" <baseband-devel(a)lists.osmocom.org> 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

1 0

Re: Facing issues in using OSMOCOM
by Basem Ahmed 13 Jun '11

13 Jun '11

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 <eng_basemm(a)yahoo.com> wrote: From: Basem Ahmed <eng_basemm(a)yahoo.com> Subject: Re: Facing issues in using OSMOCOM To: "baseband-devel" <baseband-devel(a)lists.osmocom.org> Cc: "Sylvain Munaut" <246tnt(a)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(a)gmail.com> wrote: From: Sylvain Munaut <246tnt(a)gmail.com> Subject: Re: Facing issues in using OSMOCOM To: "Basem Ahmed" <eng_basemm(a)yahoo.com>, "baseband-devel" <baseband-devel(a)lists.osmocom.org> 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

1 0

Re: Facing issues in using OSMOCOM
by Sylvain Munaut 12 Jun '11

12 Jun '11

> 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

3 2

Facing issues in using OSMOCOM
by Basem Ahmed 12 Jun '11

12 Jun '11

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

1 0

Error while compiling the stack
by nagesh reddy 08 Jun '11

08 Jun '11

Hi, i am getting the below error when i try to compile the GSM stack sources. administrator@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.

2 1

Calypso JTAG
by Drasko DRASKOVIC 08 Jun '11

08 Jun '11

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

2 3

IP hacking..
by Marten Christophe 08 Jun '11

08 Jun '11

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,

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel