- baseband-devel - lists.osmocom.org

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