January 2011 - baseband-devel - lists.osmocom.org

by Marten Christophe

Hello All, Pls help me, any one who can Kindly give me code or even binary file for sniff code which Sylvain demonstrated in chao meeting, it will solve my purpose, i can See, in video he made the same interface to tune to a ARFCN, TS , and hopping sequence as i requested a long time back to mailling list It will be great help for poor students. my project don't required any a5 creaking so it wont be used as unlawful means. so far i have arranged 12 USRP1 to run openBTS. I just wanted to do the same, which Sylvain have done in video @ chao presentation, except cracking the encryption as i will configure openBTS as a5/0 coz it’s education transmission not necessary to encrypt kindly do me a favour in shake of charity. Pls reply to my query pls help me in the shake of poor students. I promise will keep that code secret and will not disclose to any one else. or pls advise me how i can modify existing code up to that level. Kindly reply on my request , can you pls provide me Sniff software? it will help me allot, my NGO can deploy a pilot project at least Kind Regards,

13 years, 3 months

4
3
0 0

Non Standard Baud Rates?

by MATTHEW EVANS

Hi, I'm trying to get the burst_ind branch working at the higher speed baud rates. I have a USB to Serial FTDI Cable (FT232R) plus the T191. This setup works fine with the main trunk of osmocombb. When I fire up osmocon, layer1 appears to download to the phone and runs successfully. Osmocon then logs 'Received DOWNLOAD ACK from phone, your code is running now!'. The phone has layer1.bin displayed as usual. However it goes no further and just hangs. Could anyone please give any advice on what to try next? Thanks, Matt.

13 years, 3 months

2
1
0 0

Why my phone can't attach the network?

by xuchenyu

Thanks to Tomas and ton, I can run osmocombb on the phone. But the phone can't attach the network, can't make a call, can't recognise the SIM card. I found that this was no BCCH received in wireshark. And when I type some command via telnet localhost, it always output "Command incomplete" Anybody can give me some solution? Thanks! -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Why-my-phone-can-t-attach-the-ne… Sent from the baseband-devel mailing list archive at Nabble.com.

13 years, 3 months

2
1
0 0

Re:radio is not started

by Bogdan Alecu

I guess you have the default configuration: "No Mobile Station defined, creating: MS '1'" After you start "mobile" application, select "enable" and then "write". This will write your configuration to /etc/osmocom/osmocom.cfg After that edit this file and set from no sim to sim reader. Restart the mobile application and it should work.

13 years, 3 months

2
3
0 0

Motorola usb cable

by Dario Lombardo

Hello everydoby I have Motorola-branded prolific usb cable. This cable, once inserted in a port, claims to be a 0307 chipset adapter, and Linux kernel doesn't recognize it: not working. Someone told me that Motorola has changed the label in those cables that claim to be 0307, but they are pl2303. Does anyone have one of these cables working? I've tried many ways, including udev, to make it work, but no success. My next step is to recompile the kernel module, but I was wondering if someone has solved it in another way. Bye Dario.

13 years, 3 months

3
4
0 0

Pirelli DP-L10 support, steve-m/testing branch

by Steve Markgraf

Hi all, last weekend I have grinded down a DP-L10 pcb and traced the TSPACT wiring of this board. I've added support for this phone, along with a few other changes in my branch steve-m/testing. Changes include: * Add support for Pirelli DP-L10 * Add TX support for the gta0x devices * separate board images for the Compal E86 (Motorola C139/C140) (display/keypad backlight now works by default) If anyone wants to test those changes (especially the freerunner TX support, since I have no freerunner), please feel free to do so. I tested the other changes and didn't find any regressions, so if no one else does, we can merge it to master soon. One thing I noticed during testing: The C139/C140 seem to have a different SYSTEM_INHERENT_GAIN, I compared the RX levels of several C118/C123/C155 with several C139/C140, and the reported rx level was always at around 18-20dBm worse than with the C123. Regards, Steve

13 years, 3 months

1
1
0 0

radio is not started

by Muhammad Rasyid Sahputra

Hi, I tried to follow instruction on SIM Reader wiki, but seems I got different result. OsmocomBB> enable OsmocomBB# sim reader 1 OsmocomBB# show subscriber Mobile Subscriber of MS '1': IMSI: Status: U2_NOT_UPDATED IMSI detached LAI: invalid Access barred cells: no Access classes: OsmocomBB# show support Supported features of MS '1': Phase 2 mobile station R-GSM : yes E-GSM : yes P-GSM : yes GSM900 Class: 4 DCS 1800 : yes DCS Class : 1 CECS : no VGCS : no VBS : no SMS : yes SS_IND : yes PS_CAP : no CMSP : no SoLSA : no LCSVA : no LOC_SERV : no A5/1 : yes A5/2 : yes A5/3 : no A5/4 : no A5/5 : no A5/6 : no A5/7 : no A5/1 : yes Channels : SDCCH + TCH/F + TCH/H Full-Rate V1: yes Full-Rate V2: yes Full-Rate V3: no Half-Rate V1: yes Half-Rate V3: no Min RXLEV : -106 OsmocomBB# show ms MS '1' is down, radio is not started IMEI: 000000000000000 IMEISV: 0000000000000000 IMEI generation: fixed automatic network selection state: A0 null cell selection state: C0 null radio ressource layer state: idle mobility management layer state: MM idle, PLMN search from the layer23 part, $ ./mobile -i 127.0.0.1 -d 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. mobile: option requires an argument -- d VTY available on port 4247. No Mobile Station defined, creating: MS '1' <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:3471 init PLMN process <0003> gsm322.c:3472 init Cell Selection process <0003> gsm322.c:3526 No stored BA list Mobile '1' initialized, please start phone now! <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) can't perform location update, and from the error, is that mean the application failed to read the simcard correctly? and what's the meaning of "Mobile '1' initialized, please start phone now!", is it starting the phone by push the power button? if so, since the firmware is loaded I can't make the phone start like using original firmware. If i push the button, it will show message like Found flash of 2097152 bytes at 0x0 with 2 regions Region 0 of 31 pages with 65536 bytes each. Region 1 of 8 pages with 8192 bytes each. key=20 pressed Powering off due to keypress. I am using motorola c118 anw. any clue about this error? Thanks. Best Regards, Rasyid

13 years, 3 months

1
0
0 0

USB fetmocell: What's about the sofware?

by Fabio Pietrosanti (naif)

Hi all, i noticed that article http://www.eetimes.com/electronics-news/4212228/Picochip-shares-femtocell-r… speaking about 3G basestation on USB dongle. That's really cool, i don't know about the hardware, but for sure when those device will be out the hacking perspective would be really interesting for projects like OpenBSC and OsmocomBB . -naif

13 years, 3 months

1
0
0 0

sim reader code / master branch / ...

by Harald Welte

Hi all! In order to avoid the most common problems, I propose exporting something like a feature bitmask on the L1CTL, i.e. * L1CTL user code (layer23) can send a L1CTL_GET_FEAT_REQ request * laye1 in the phone sends a L1CTL_GET_FEAT_RESP with all the bits set to 1 for the features it supports * L1CTL user code (layer23) can then check if all the features it needs are supported by the L1. IF not, it can simply abort or print a warning to the user. We can simply extend the size of the bitmask over time if we need more bits. Obvious bits I would consider are: - is this firmware compiled with TX support? - does this firmware contain a SIM reader driver? - does this firmware support BURST_IND? Maybe we could also include a static header containing a compile timestamp or the git date/revision that the firmware was built, as well as a name of the board. Now I know, nice idea, who will implement it? I currently have othe priorities, but if somebody lurking on this list is looking for a relatively simple way to contribute back to the project (without knowing anything about GSM!) this might be something useful you could do. 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)

13 years, 3 months

4
5
0 0

Re: wiki: SIMReader Was: Sim on C115 & C118

by Dobrica Pavlinusic

On Mon, Jan 17, 2011 at 11:46:50AM -0800, Bogdan Alecu wrote: > Hello, > > Sorry for writing you directly to your email. Thank you very much for the wiki. I was wondering if you have some knowledge about the "sim test" mode. I tried it by filling in the IMSI and MCC MNC. After I start the layer2 in a few seconds layer1 crashes. What I am trying to achieve is to send a IMSI detach to the network for the specified IMSI. Maybe you could give me a hand with this. This is often second question after getting SIM working, so I want to share what I know. However, I'm not an expert, and most of this is gathered from presentations and speaking with people who know more than I do, so I wanted to bounce this against mailing list for additional comments. As far as I understand it, to connect to provider network, you need provider's ki which is shared secret between network and sim card. There are some practical attacks on older sim cards which are used by multi-network sim cards. It seems there is limited number of brute-force interations that cards support before disabling themself and that changed somehow in recent cards. Best SIM explanation I found so far is on 27C3 wiki about GSM network: http://events.ccc.de/congress/2010/wiki/GSM#Why_do_I_need_to_buy_your_SIM_c… > --- On Mon, 1/17/11, Dobrica Pavlinusic <dpavlin(a)rot13.org> wrote: > > > From: Dobrica Pavlinusic <dpavlin(a)rot13.org> > Subject: wiki: SIMReader Was: Sim on C115 & C118 > To: "Bogdan Alecu" <b.alecu(a)yahoo.com> > Cc: dario.lombardo(a)libero.it, baseband-devel(a)lists.osmocom.org > Date: Monday, January 17, 2011, 7:05 PM > > > On Mon, Jan 17, 2011 at 10:24:51AM -0800, Bogdan Alecu wrote: > > I was going to ask the same question because I have same problem with sim reader mode. However I haven't used Sylvain test. I will and come back with an update. > > There seems to be sufficiant interest for using SIM reader, so I created > page on wiki which might serve as good pointer: > > http://bb.osmocom.org/trac/wiki/SIMReader > > -- > Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org > Unix addict. Internet consultant. http://www.rot13.org/~dpavlin > > > > -- Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin

13 years, 3 months

4
6
0 0

Why my C118 can't send DOWNLOAD ACK?

by xuchenyu

~/src/osmocom-bb/src/host/osmocon$ ./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 1 bytes from modem, data looks like: 1b . got 2 bytes from modem, data looks like: 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=50932, hdr_len=4, dnload_len=50939 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/50939) handle_write(): 4096 bytes (8192/50939) handle_write(): 4096 bytes (12288/50939) handle_write(): 4096 bytes (16384/50939) handle_write(): 4096 bytes (20480/50939) handle_write(): 4096 bytes (24576/50939) handle_write(): 4096 bytes (28672/50939) handle_write(): 4096 bytes (32768/50939) handle_write(): 4096 bytes (36864/50939) handle_write(): 4096 bytes (40960/50939) handle_write(): 4096 bytes (45056/50939) handle_write(): 4096 bytes (49152/50939) handle_write(): 1787 bytes (50939/50939) handle_write(): finished It stopped here for very long time, I have tried with XOR and without XOR for many times! Please help me to verify this issue! thanks very much! -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Why-my-C118-can-t-send-DOWNLOAD-… Sent from the baseband-devel mailing list archive at Nabble.com.

13 years, 3 months

2
1
0 0

Toolchain tests, problems and a few workarounds...

by Wolfram Sang

Hi, at 27c3, I tested some toolchains with osmocom-bb and found a few build-problems, even with the recommended gnuarm-3.4.3. I want to document them here, so other people can find hints about it. *** GNUARM 3.4.3 TOOLCHAIN master branch ============= ../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory Holger suggested to manually remove this line. It is fixed upstream in libosmocore and osmocom-bb needs to be synced to it. Please do :) remotes/origin/steve-m/loader_sciphone ====================================== 1) First problem is: In file included from ../../include/osmocore/msgb.h:23, from ../../src/msgb.c:27: /home/wsa/Dev/osmocom-bb/src/target/firmware/include/stdint.h:13:25: stdint.h: No such file or directory Cherry-picking e0a605819c39187a494e43cf591f2e79a9d9903f (stdint.h: Next attempt at making this work with various compilers) helps. 2) It then runs into the problem of the master branch. 3) After this is fixed, I get ../../../src/codec/gsm610.c:24:20: stdint.h: No such file or directory ../../../src/codec/gsm610.c:33: error: parse error before "gsm610_bitorder" which needs 733c894c18c127ce5c023e39609b7d2b9e748e7e (build: Use absolute path in the CFLAGS for libosmocore target build) as a fix. 4) This then, leads to: arm-elf-ld: address 0x400054d4 of board/mt62xx/loader.mtkram.elf section .text is not within region LRAM which is sadly also present when you just cherry-pick the main patch d04761d19c432201f7c0f10c72f788fb695d466a ([WIP] Modify loader for use as first stage bootloader on MT62xx devices) on top of current master + its build fix. So, does it seem sensible to simply rebase this branch to master which would eliminate the first three problems? Or at least cherry-pick the above fixes? Also, the workarounds for gcc3 do not look very sustainable (see custom stdint.h). Is it a mid-term option to remove that stuff if a reliable pre-built gcc4 is available? (I am working on that, see below). BTW the linker error was not further worked on yet. I got a prebuilt binary now. It is possibly helpful to put it on the G2-wikipage, so people wanting to work on the Linux-support only are spared from the above hassle. *** CUSTOM 4.3.2 TOOLCHAIN every branch ============ The configure-stage of libosmocom already fails for the target with error 77. The config.log says in detail: configure:3231: checking whether the C compiler works configure:3253: arm-elf-gcc -Os -ffunction-sections -I/home/wsa/Dev/osmocom-bb/src/target/firmware/include conftest.c >&5 /home/opt/OSELAS.Toolchain-1.99.3/arm-elf/gcc-4.3.2-newlib-1.16.0-binutils-2.18/bin/../lib/gcc/arm-elf/4.3.2/../../../../arm-elf/lib/libc.a(lib_a-exit.o): In function `exit': /home/mkl/himalia-pengutronix/toolchain/releases/OSELAS.Toolchain-1.99.3.6/platform-arm-elf-gcc-4.3.2-newlib-1.16.0-binutils-2.18/build-target/newlib-1.16.0/newlib/libc/stdlib/exit.c:65: undefined reference to `_exit' /home/opt/OSELAS.Toolchain-1.99.3/arm-elf/gcc-4.3.2-newlib-1.16.0-binutils-2.18/bin/../lib/gcc/arm-elf/4.3.2/../../../../arm-elf/lib/libc.a(lib_a-sbrkr.o): In function `_sbrk_r': /home/mkl/himalia-pengutronix/toolchain/releases/OSELAS.Toolchain-1.99.3.6/platform-arm-elf-gcc-4.3.2-newlib-1.16.0-binutils-2.18/build-target/newlib-1.16.0/newlib/libc/reent/sbrkr.c:60: undefined reference to `_sbrk' 27c3 was too interesting ;) so I haven't fixed this yet. The Mac-toolchains also throw this and I also have seen it on the list before, so I hope I can work on it the next days. So much for now. It would be nice if someone with write-access to the repo could comment on my questions and/or fix the low-hanging fruits. I will hopefully be able to send some updates soon, too (famous last words). It was great to meet you all in person! All the best, Wolfram

13 years, 3 months

1
1
0 0

Re: R: Re: C115 loader.compalram.bin

by Tomas Kopsa

Hi Lia, I have tested another cable (USB <-> 2,5 jack, speacial for Compal phones) - it is the same chip (Prolific) and I am able to load firmware too. Although it is the same chip, there is a difference that this one makes the osmocon printing those messages instantly when phone is not connected: got 1 bytes from modem, data looks like: f5 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: f5 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: f5 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: fd . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: f5 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: fd . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: ea . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: ea . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: ea . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: ea . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: fd . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: ea If I connect phone, printing stops. Here is what happened when I tried to load firmware without xor (-m c123) and pressed the button: (This happened every attempt without xor flag) Received PROMPT2 from phone, starting download handle_write(): 1087 bytes (1087/50947) 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 . If you have USB adapter (I guess you have), you dont need to check model, check 'lsusb' [root@amilo osmocon]# lsusb Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub *Bus 002 Device 017: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port* If you have Prolific, which is very common, I encourage you to use xor flag. You can also try to switch on your phone to check if original firmware boots. I experienced during my early tests, that phone crashed (probably SRAM) and it was unable to boot even original fw. In case phone is crashed, reconnect battery and it will fix itself. Here is the ACK after hello world load: handle_write(): 768 bytes (17919/19787) handle_write(): 768 bytes (18687/19787) handle_write(): 768 bytes (19455/19787) handle_write(): 332 bytes (19787/19787) 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 Hello World (revision osmocon_v0.0.0-754-gb5abcb6-modified) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: efce3b1ce1001255 ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ============================================== Looking forward your response, Tomas > Hi Tomas, > > thanks for your feedback. > > Actually, I've tried both flags (woth/without xor extension), but hte > result is the same. > > So, in your opinioni, the problem could depend on the cable? > > I don't have the cable model now, but I can send you this information > Tuesday. > > Thanks again. > > cheers. > > lia > > ----Messaggio originale---- > Da: deacon(a)volny.cz > Data: 16-gen-2011 4.26 > A: <list_mailing(a)libero.it> > ubut Ogg: Re: C115 loader.compalram.bin > > Hello, > I have C115 too and I use '-m c123xor' switch, the phone mostly > boots on 1st button push (I never reacher full load with '-m c123'). > > ./osmocon -p /dev/ttyUSB0 -m c123xor > ../../target/firmware/board/compal_e88/hello_world.compalram.bin > ./osmocon -p /dev/ttyUSB0 -m c123xor > ../../target/firmware/board/compal_e88/loader.compalram.bin > ./osmocon -p /dev/ttyUSB0 -m c123xor > ../../target/firmware/board/compal_e88/layer1.compalram.bin > > I have FTDI USB<->RS232 + Calypso serial. When load fails (with > xor), I have a feeling that it helps reconnection cable to the phone. > (I have also Calypso USB cable which I haven't tested yet, will > report later.) > > - Tomas > > >>> Hello. >>> I'm trying to load the loader.compalram.bin. >>> The behaviour is very strange because sometimes the download is complete and >>> successfull, sometimes; in particular, in this case, the download is complete, >>> but any ACK is sent back from the mobile phone (see below). >>> ./osmocon -p /dev/ttyUSB0 -m c123 ../.. >>> /target/firmware/board/compal_e99/loader.compalram.bin >>> got 2 bytes from modem, data looks like: 2e c8 .. >>> 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_e99/loader.compalram.bin): >>> file_size=21752, hdr_len=4, dnload_len=21759 >>> 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/21759) >>> handle_write(): 4096 bytes (8192/21759) >>> handle_write(): 4096 bytes (12288/21759) >>> handle_write(): 4096 bytes (16384/21759) >>> handle_write(): 4096 bytes (20480/21759) >>> handle_write(): 1279 bytes (21759/21759) >>> handle_write(): finished >>> >>> >>> The target phone is C115. I tried compal_exx and the result is the same :-( >>> >>> Please, can someone help me to understand the reasons? >>> Thanks in advance. >>> >>> >>> >>> >> > > >

13 years, 3 months

6
6
0 0

[PATCH] Makefile: be more robust against toolchains without syscalls

by Michael Grzeschik

Several toolchains are missing syscalls provided by the libc used. For example, if the newlib was build with the configure flag "--disable-newlib-supplied-syscalls". To prevent the configure check for things like "_exit" in osmocom the CFLAGS+="-nostartfiles -nodefaultlibs" helps a lot. Signed-off-by: Michael Grzeschik <mgr(a)xviews.de> Acked-by: Wolfram Sang <wolfram(a)the-dreams.de> --- src/Makefile | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/Makefile b/src/Makefile index a0dea5d..b3594c1 100644 --- a/src/Makefile +++ b/src/Makefile @@ -39,7 +39,7 @@ shared/libosmocore/build-target/Makefile: shared/libosmocore/configure shared/li cd shared/libosmocore/build-target && ../configure \ --host=arm-elf-linux --disable-vty --enable-panic-infloop \ --disable-shared --disable-talloc --disable-tests \ - CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include" + CC="$(CROSS_TOOL_PREFIX)gcc" CFLAGS="-Os -ffunction-sections -I$(TOPDIR)/target/firmware/include -nostartfiles -nodefaultlibs" shared/libosmocore/build-target/src/.libs/libosmocore.a: shared/libosmocore/build-target/Makefile cd shared/libosmocore/build-target && make -- 1.7.2.3

13 years, 3 months

3
2
0 0

AW: you know phone maybe can made USRP

by Andreas.Eversberg

sylvain, looks like you are talking to a spam bot. (harald already did earlier :)

13 years, 3 months

1
0
0 0

you know phone maybe can made USRP

by 麦田守望

do you know Which phone can made USRP thanks

13 years, 3 months

3
2
0 0

RE: Sim on C115 & C118

by Bogdan Alecu

I was going to ask the same question because I have same problem with sim reader mode. However I haven't used Sylvain test. I will and come back with an update.

13 years, 3 months

3
3
0 0

Problem compiling OsmocomBB on BT4 RC2

by quem tu quiseres

Hi, I just started playing around with this great project and am ashamed to say I'm stumped with an annoying error when compiling. I'm compiling on a Backtrack 4 RC2 (*buntu based distro) and that may be why I'm having problems. Basically I downloaded the proper packages as per the instructions on the wiki, exported the PATH and all that, but when I run make I get this error: cd shared/libosmocore/build-target && ../configure \ --host=arm-elf-linux --disable-vty --enable-panic-infloop \ --disable-shared --disable-talloc --disable-tests \ CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections -I/root/GSM/osmocom-bb/src/target/firmware/include" configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. configure: error: cannot find install-sh or install.sh in ".." "../.." "../../.." make: *** [shared/libosmocore/build-target/Makefile] Error 1 Attached is my config.log and you can see the PATH are there. The error can be seen on this line in the log "configure:1766: error: cannot find install-sh or install.sh in ".." "../.." "../../.." Now i've checked to see if I have autoconf and automake installed (I do, I have autoconf 2.61 and automake 1.10) since my searches on the internet seem to indicate that maybe the problem. Now I usually do all my own leg work and I read and read before asking questions, but I'm afraid I can't resolve this on my own. Before I spend another afternoon searching for the solution, I remembered to ask here. Anyone have any hints on what I'm doing wrong? Do I need different automake or autoconf versions? Thanks and keep up the great work. It's been fascinating to watch the evolution of GSM hacking these last few years.

13 years, 3 months

10
13
0 0

Sim on C115 & C118

by Dario Lombardo

Hello everybody I'm trying to run the "mobile" application on a C115 and a C118 phone. I want to use the real sim, so I used "sim reader" in the config. Both phones have the same behaviour: <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:3471 init PLMN process <0003> gsm322.c:3472 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) no more output beyond this point. Phones work correctly with other softwares, sim works correctly. I get no response from the sim. Is the card reader working on these phones? If yes, does anyone have suggestions to solve this issue? Thanks a lot to everybody. Dario.

13 years, 3 months

2
1
0 0

C115 loader.compalram.bin

by list_mailing＠libero.it

Hello. I'm trying to load the loader.compalram.bin. The behaviour is very strange because sometimes the download is complete and successfull, sometimes; in particular, in this case, the download is complete, but any ACK is sent back from the mobile phone (see below). ./osmocon -p /dev/ttyUSB0 -m c123 ../.. /target/firmware/board/compal_e99/loader.compalram.bin got 2 bytes from modem, data looks like: 2e c8 .. 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_e99/loader.compalram.bin): file_size=21752, hdr_len=4, dnload_len=21759 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/21759) handle_write(): 4096 bytes (8192/21759) handle_write(): 4096 bytes (12288/21759) handle_write(): 4096 bytes (16384/21759) handle_write(): 4096 bytes (20480/21759) handle_write(): 1279 bytes (21759/21759) handle_write(): finished The target phone is C115. I tried compal_exx and the result is the same :-( Please, can someone help me to understand the reasons? Thanks in advance.

13 years, 3 months

2
1
0 0

running voice data/encryption on compal?

by Aaron Zauner

hi, a while ago i've read that someone managed to have an active phone call over osmocom for about 20mins. i woundered if it is theoretically & technically possible to have an active, serious (thus not a5) encryption running for voice or data calls on the stack? thanks in advance & greetings from vienna ;) azet

13 years, 3 months

8
10
0 0

[PATCH libosmocore] gsm 03.41: fix GSM341_MSG_CODE macro argument

by Alex Badea

One usage of the "ms" argument is typoed as "msg". Fix it to prevent subtle future failures. Also paranthesize the macro argument for good measure. Signed-off-by: Alex Badea <vamposdecampos(a)gmail.com> --- This was found by visual inspection. include/osmocore/protocol/gsm_03_41.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/include/osmocore/protocol/gsm_03_41.h b/include/osmocore/protocol/gsm_03_41.h index 3b1b7c9..54365cb 100644 --- a/include/osmocore/protocol/gsm_03_41.h +++ b/include/osmocore/protocol/gsm_03_41.h @@ -40,7 +40,7 @@ struct gsm341_etws_message { uint8_t data[0]; } __attribute__((packed)); -#define GSM341_MSG_CODE(ms) (ms->serial.code_lo | (msg->serial.code_hi << 4)) +#define GSM341_MSG_CODE(ms) ((ms)->serial.code_lo | ((ms)->serial.code_hi << 4)) /* Section 9.3.2.1 - Geographical Scope */ #define GSM341_GS_CELL_WIDE_IMMED 0 -- 1.7.0.4

13 years, 3 months

2
1
0 0

open cell phone hardware questions

by Scott Weisman

Hi everyone. I'm admittedly more a lurker than an active participant in this project. I find it very fascinating and regard its objectives as important. I recently watched several of the C3 presentations, from this and previous years. Having open, documented hardware and software seems to be an important goal in itself. Just knowing about all the potential weaknesses in the software stacks of most phones, as well as hidden "features" like SMS messages that could, theoretically, do things like remotely enable the phone mic, among other things (things that are certainly technically possible, and also due to the closed nature of the software, completely unknown) are of grave concern to me. Now, given that the supported phone hardware is old and not reliably available, I was wondering if anyone knows if the Calypso and other chips in these old phones are still available for new designs? How much interest would there be, say, in an open, but VERY SIMPLE, actual phone? Kind of like the Pandora project, but without the ambition to make the most advanced portable game player possible. The Osmocom software would then be very easily portable to such a device. Given the seemingly widespread interest and enthusiasm for the Osmocom, OpenBTS, and OpenBSC projects, a real, genuinely open phone (not a pseudo-open phone like the FreeRunner) might possibly have enough interest, and be buildable for a low-enough cost, to merit further discussion. Anyone want to discuss this?

13 years, 3 months

3
3
0 0

TODO: OsmocomBB to continually iterate over all cells and dump SI

by Harald Welte

Hi! A number of people want to do some long-term evaluation of their cellular environment and would be interested in an 'app' for OsmocomBB that continuously scans the spectrum and dumps the cell parameters such as * ARFCN, Signal Level, SNR * frequency synch offset * SCH info (BCC/NCC) * SI (at least 1-4) from BCCH I would love to do it, but I simply don't have the time. I thought maybe somebody on this list is looking for a relatively simple task and has some time. I think this is a great project to work with OsmocomBB without having to go into the details. The algorithm would look something like STATE 1: Power Scan * do power measurement over all supported bands * pick strongest N carriers and iterate over them STATE 2: FCCH/SCH acquisition * try to get lock on the carrier * if not, go back to next carrier from power scan * if yes, continue with STATE 3 STATE 3: Wait until all relevant SI have been received * generate GSMTAP output for the SI messages (or timeout) * go back to STATE 2 for next strongest ARFCN * after last ARFCN, re-start from STATE 1 This is basically the initial step of the GSM 03.22 cell (re)selection that we already have as part of the 'mobile' program. So all the code is there, but what's needed is a separate rady-made app, not requiring any user interaction. It should also include some e.g. shell script that automatically generates a new pcap file every N minutes/hours, and make sure to never overwrite any existing PCAP file. In the end, having this running for an extended period of time should simply produce a large number of PCAP files without any manual interaction. Lock-ups in any state should be detected by timers, singalling a proper L1_RESET to make sure it continues. Unplugging / re-plugging the phone should also not require any re-start of the program. Optional extensions: * software to aggregate info from the pcap files (remove duplicate entries, e.g.) * optional logging of GPS coordinates from a GPS receiver If anyone has some time to give this some work, I'd most appreciate it. Please inform the mailing list to ensure no duplicate work is created. 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)

13 years, 3 months

4
3
0 0

i need help i use MTK chip to do a GSM USRP For my love girl

by 麦田守望

i need help i will USE MTK6219+6129 to do a GSM USRP i need baseband Firmware or USB interface to Connection PC the all base openbts

13 years, 3 months

3
2
0 0

Is this true? ----> Re: ＵＳＥ　ＭＴＫ　ｃｈｉｐ　ｐｈｏｎｅ　ｆｏｒ　ＤＩＹ　ｙｏｕｒｓｅｌｆ　ＢＴＳ

by SoftwareRadioGuy

Everyone, Is it true you can use a MTK Chipset as a DIY GSM BTS/USRP ? I've emailed this fellow who posted this back in December 2010 but have gotten no reply to date. This would be excellent for use on something I'm working on in Africa for about 50 - 100 IMPOVERISHED villages. Awaiting anyone's input on this. Thank you SoftwareDefinesRadio 2010/12/15 <baseband-devel-request(a)lists.osmocom.org> > > > Today's Topics: > > 1. Price Cheap of USRP for openbts and GSM ( ???? ) > > > ---------- Forwarded message ---------- > From: "麦田守望" <775725965(a)qq.com> > To: "baseband-devel" <baseband-devel(a)lists.osmocom.org> > Date: Wed, 15 Dec 2010 14:18:50 +0800 > Subject: Price Cheap of USRP for openbts and GSM > > Hello everybody > you may have USRP ＵＳＥＭＴＫｃｈｉｐｐｈｏｎｅｆｏｒＤＩＹｙｏｕｒｓｅｌｆＢＴＳ Simple ａｎｄ > Practical ｉｆｉｎｄ Developmentｅｒ Contact ｍｅ > >

13 years, 3 months

2
1
0 0

problems on ubuntu (64bit?)

by mki

if i boot the c118 from a ubuntu 10.04 lts (64bit) or a g20 arm minipc i get this here /opt/osmocom/bin/osmocon -m c123 -p /dev/ttyUSB0 /opt/osmocom/firmware/board/compal_e88/layer1.compalram.bin got 2 bytes from modem, data looks like: 2f 81 /. got 5 bytes from modem, data looks like: 00 f6 02 00 41 ....A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ 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 . if i boot it from my mac book or a ubuntu (32bit) i get this: osmocon -m c123xor -p /dev/tty.usbserial sylvain/osmocom-bb/src/target/firmware/board/compal_e88/layer1.compalram.bin got 6 bytes from modem, data looks like: 00 00 00 00 00 00 ...... got 1 bytes from modem, data looks like: 2f / got 1 bytes from modem, data looks like: 81 . 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: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(sylvain/osmocom-bb/src/target/firmware/board/compal_e88/layer1.compalram.bin): file_size=54152, hdr_len=4, dnload_len=54159 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(): 1023 bytes (1023/54159) handle_write(): 1024 bytes (2047/54159) handle_write(): 1024 bytes (3071/54159) handle_write(): 1024 bytes (4095/54159) handle_write(): 1024 bytes (5119/54159) handle_write(): 1024 bytes (6143/54159) handle_write(): 1024 bytes (7167/54159) handle_write(): 1024 bytes (8191/54159) handle_write(): 1024 bytes (9215/54159) handle_write(): 1024 bytes (10239/54159) handle_write(): 1024 bytes (11263/54159) handle_write(): 1024 bytes (12287/54159) handle_write(): 1024 bytes (13311/54159) handle_write(): 1024 bytes (14335/54159) handle_write(): 1024 bytes (15359/54159) handle_write(): 1024 bytes (16383/54159) handle_write(): 1024 bytes (17407/54159) handle_write(): 1024 bytes (18431/54159) handle_write(): 1024 bytes (19455/54159) handle_write(): 1024 bytes (20479/54159) handle_write(): 1024 bytes (21503/54159) handle_write(): 1024 bytes (22527/54159) handle_write(): 1024 bytes (23551/54159) handle_write(): 1024 bytes (24575/54159) handle_write(): 1024 bytes (25599/54159) handle_write(): 1024 bytes (26623/54159) handle_write(): 1024 bytes (27647/54159) handle_write(): 1024 bytes (28671/54159) handle_write(): 1024 bytes (29695/54159) handle_write(): 1024 bytes (30719/54159) handle_write(): 1024 bytes (31743/54159) handle_write(): 1024 bytes (32767/54159) handle_write(): 1024 bytes (33791/54159) handle_write(): 1024 bytes (34815/54159) handle_write(): 1024 bytes (35839/54159) handle_write(): 1024 bytes (36863/54159) handle_write(): 1024 bytes (37887/54159) handle_write(): 1024 bytes (38911/54159) handle_write(): 1024 bytes (39935/54159) handle_write(): 1024 bytes (40959/54159) handle_write(): 1024 bytes (41983/54159) handle_write(): 1024 bytes (43007/54159) handle_write(): 1024 bytes (44031/54159) handle_write(): 1024 bytes (45055/54159) handle_write(): 1024 bytes (46079/54159) handle_write(): 1024 bytes (47103/54159) handle_write(): 1024 bytes (48127/54159) handle_write(): 1024 bytes (49151/54159) handle_write(): 1024 bytes (50175/54159) handle_write(): 1024 bytes (51199/54159) handle_write(): 1024 bytes (52223/54159) handle_write(): 1024 bytes (53247/54159) handle_write(): 912 bytes (54159/54159) 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-737-ga4e3431-modified) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: c1900c14ae021565 ====================================================================== 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 1880! -- its working :-) I have tried to copy the firmware from the working machine to the bad machines but the result is the same. Is it possible that the usb driver from ubuntu 10.04 lts 64bit is silly???? cable (akku-king) phone all is the same on every plattform. Have some body an Idea? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-on-ubuntu-64bit-tp22208… Sent from the baseband-devel mailing list archive at Nabble.com.

13 years, 3 months

2
4
0 0

OSX build

by MATTHEW EVANS

Hi All, I'm really struggling to get the latest source to build on OSX. Would anyone be kind enough to offer some assistance to getting this compiled? Build fails with: ./configure: line 3461: syntax error near unexpected token `LIBOSMOCORE,' ./configure: line 3461: `PKG_CHECK_MODULES(LIBOSMOCORE, libosmocore)' Any help or advice would be appreciated! Many Thanks, Matt.

13 years, 3 months

2
1
0 0

C123: reading SIM stuck

by Frank Rosengart

Hi, just for curiosity, I would like to get the osmocomBB running on the Motorola C123. Everything works fine (radio starts scanning for networks) if I use the test SIM feature. But reading a real SIM plugged into the phone does not work for me. The 'mobile' app shows: <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) -end- Any hints where to start debugging? (does neither work with 3 different SIMs: swisscom, blau, super-sim) BTW: Are there any plans to support external SIM readers via PC/SC etc.? Thanks Frank

13 years, 3 months

4
4
0 0

GSM Codes with Osmocombb

by Tim Ehlers

Hi, I'm playing around with Osmocom for a while now. My final goal is to use it as a stationary phone on a PC to be able to remotly control the phone. I checked out the sylvain/testing tree, to use my SIM card and managed to be able to make and receive calls. Very amazing so far. :-) Now I tried to send GSM codes (like *#21#, oder *21*{NUMBER}#) to set and unset call diverts. It seems, that "call 1 *21*{NUMBER}#" does not work. Normal GSM cellphones seem to handle these codes not as a normal call. Does anybody know how one could send GSM codes to the network? Thanks Tim

13 years, 3 months

3
2
0 0

where to get osmocom-supported phones

by Scott Weisman

I know this has been asked before, but I can't find the email(s). eBay in the past has generally had a few GSM900/1800 Osmocom-supported phones, although the prices weren't always great. I managed to get a V171 that way from a Hong Kong source (for about US$20 including shipping). However, the only phones that seem available today are all GSM850/1900. Someone a while back gave a link to Polish site where you could buy phones for even cheaper. Does someone have that site, or other sites that might be useful? Thanks, Scott

13 years, 3 months

2
1
0 0

osmocom on windows

by Enzo Zordan

Hello from Argentina, I'm a 26 years old student of Electronical Engineering, I'm realy very interesting in this project, I have a C115, so I'll try to compile the code, but I'm not Linux user yet. Can I run this in Windows? If not... I'll download a live cd distribution of linux =) I want to use this c115 as a test field. Best regards buddy Enzo.

13 years, 3 months

3
2
0 0

simtrace simtrace_usb.h

by ml＠mail.tsaitgaist.info

Hi in simtrace/at91sam7/host, simtrace_usb.h is symbolically linked to sunbeam/home/laforge/projects/git/openpcd/firmware/include/simtrace_usb.h this might not be generic enough to keep it linked, it could point to ../../../openpcd/firmware/include/simtrace_usb.h or will openpcd and simtrace be merged, or combined in any way ? thanks, kevin

13 years, 3 months

2
1
0 0

sam7utils

by ml＠mail.tsaitgaist.info

Hi, I'm trying to flash simtrace on an at91sam7s, using samba. sam7utils compiles well under amd64, but does not work. It does not output anything and quits. the only indication on dmesg is : usb 4-1: usbfs: interface 0 claimed by cdc_acm while 'sam7' sets config #1 Sam_I_Am works great on amd64, but the firmware format is not the same. Does anyone knows how to convert main_simtrace.samba to a valid intel hex ? Kevin

13 years, 3 months

2
2
0 0

stuck in A1 Trying RPLMN while using testing branch? - change toolchain

by Dobrica Pavlinusic

Yesterday I asked on #osmocom irc channel about my problems with using provider card and testing branch of osmocom-bb to connect to network. I was stuck in "A1 Trying RPLMN", and I didn't see any response received with all debugging turned on. Today, I decided to change my arm toolchain to gnu-arm recommended at http://bb.osmocom.org/trac/wiki/GettingStarted I recompiled, and it worked without problems. I'm writing this e-mail as future reference since I saw few people having problem with this on irc. -- Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin

13 years, 3 months

1
0
0 0

connect to a specific network with the mobil app

by mki

I hink my mobil is always connecting to the net with the most power. is there a way to connect to a specific network? Down her my config and tries to connect to t-mobile. if i type in the vty: local# network select 1 262 01 Network not in list! local# network search 1 local# my config: local# sh run Current configuration: ! service advanced-vty ! line vty no login ! gps device /dev/ttyACM0 gps baudrate default no gps enable ! ms 1 layer2-socket /tmp/osmocom_l2 sap-socket /tmp/osmocom_sap sim none 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 dcs class-900 4 class-dcs 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 shutdown exit ! end -- View this message in context: http://baseband-devel.722152.n3.nabble.com/connect-to-a-specific-network-wi… Sent from the baseband-devel mailing list archive at Nabble.com.

13 years, 3 months

1
1
0 0

Re: Osmocon not loading

by Bogdan Alecu

I used the steps from here http://bb.osmocom.org/trac/wiki/GnuArmToolchain to build the toolchain. I also tried with and without xor, no results.

13 years, 3 months

4
9
0 0

RE: AW: AW: Osmocom-BB

by Sebastian ---

no,display shows nothing. Osmocon shows: r00t@r00t-laptop:~/install/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 2 bytes from modem, data looks like: 2f 81 /. got 1 bytes from modem, data looks like: 00 . 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 @ 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: 2f / got 1 bytes from modem, data looks like: 81 . got 1 bytes from modem, data looks like: 00 . 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: 01 . got 1 bytes from modem, data looks like: 40 @ 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: 2f / got 1 bytes from modem, data looks like: 81 . got 1 bytes from modem, data looks like: 00 . 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: 01 . got 1 bytes from modem, data looks like: 40 @ 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: 2e . got 1 bytes from modem, data looks like: c8 . 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: 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=21740, hdr_len=4, dnload_len=21747 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(): 1023 bytes (1023/21747) handle_write(): 768 bytes (1791/21747) handle_write(): 768 bytes (2559/21747) handle_write(): 768 bytes (3327/21747) handle_write(): 768 bytes (4095/21747) handle_write(): 768 bytes (4863/21747) handle_write(): 768 bytes (5631/21747) handle_write(): 768 bytes (6399/21747) handle_write(): 768 bytes (7167/21747) handle_write(): 768 bytes (7935/21747) handle_write(): 768 bytes (8703/21747) handle_write(): 768 bytes (9471/21747) handle_write(): 768 bytes (10239/21747) handle_write(): 768 bytes (11007/21747) handle_write(): 768 bytes (11775/21747) handle_write(): 768 bytes (12543/21747) handle_write(): 768 bytes (13311/21747) handle_write(): 768 bytes (14079/21747) handle_write(): 768 bytes (14847/21747) handle_write(): 768 bytes (15615/21747) handle_write(): 768 bytes (16383/21747) handle_write(): 768 bytes (17151/21747) handle_write(): 768 bytes (17919/21747) handle_write(): 768 bytes (18687/21747) handle_write(): 768 bytes (19455/21747) handle_write(): 768 bytes (20223/21747) handle_write(): 768 bytes (20991/21747) handle_write(): 756 bytes (21747/21747) 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! Received DOWNLOAD ACK from phone, your code is running now! OSMOCOM Loader (revision osmocon_v0.0.0-740-g34bbb12-modified) ====================================================================== Running on compal_e88 in environment compalram Found flash of 2097152 bytes at 0x0 with 2 regions I have to press Power on few times before it loads. Subject: AW: AW: Osmocom-BB Date: Fri, 7 Jan 2011 15:59:21 +0100 From: Andreas.Eversberg(a)versatel.de To: seppel18(a)hotmail.com does the mobile show "layer1.bin" on the display after startup? did the firmware actually load on the phone? p.s. do you mind if we CC to the mailing list, so others can help or profit from the final solution? Von: Sebastian --- [mailto:seppel18@hotmail.com] Gesendet: Freitag, 7. Januar 2011 15:51 An: Andreas.Eversberg Betreff: RE: AW: Osmocom-BB still shows "MS '1' is down, radio is not started" Subject: AW: Osmocom-BB Date: Fri, 7 Jan 2011 09:43:32 +0100 From: Andreas.Eversberg(a)versatel.de To: seppel18(a)hotmail.com CC: baseband-devel(a)lists.osmocom.org hi, can you try the following steps: 1. start osmocon 2. start mobile (be sure it is not shutdown) 3. press the power button on the phone to start the loading process after loading the binary into the phone, the phone should indicate power on to the mobile process. andreas Von: Sebastian --- [mailto:seppel18@hotmail.com] Gesendet: Freitag, 7. Januar 2011 01:37 An: Andreas.Eversberg Betreff: Osmocom-BB Hi Thanks for your Help. Now it says ms 1 is still down "radio not started". Osmocon is running (with ramloader) and layer2 socket is available. hi sebastian, there are three ways to bing it down: - "enable" -> "conf t" -> "ms 1" -> "shutdown" - the layer2 socket does not exist on startup (osmocon loader not started) - the shutdown state is stored in the config (doing "write" when it is down) just bring it up after starting osmocon: - "enable" -> "conf t" -> "ms 1" -> "no shutdown" and don't forget "write" the config, so it must not be done on every startup. andreas

13 years, 3 months

2
2
0 0

Osmocon not loading

by Bogdan Alecu

Hello, I have managed to compile everything, I connected my phone trough USB but when I try to run ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin I do not get the " Received PROMPT1 from phone, responding with CMD" message All I get is this: root@ubuntu:/home/trepx/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 2 bytes from modem, data looks like: f1 06 .. got 5 bytes from modem, data looks like: 72 82 bf 7d fd r..}. got 1 bytes from modem, data looks like: 7f . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: a6 . got 1 bytes from modem, data looks like: 0a . got 1 bytes from modem, data looks like: 3a : got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 4d M got 1 bytes from modem, data looks like: da . root@ubuntu:/home/trepx/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 2 bytes from modem, data looks like: f1 06 .. got 4 bytes from modem, data looks like: a6 51 d2 51 .Q.Q got 1 bytes from modem, data looks like: 4d M got 1 bytes from modem, data looks like: a3 . got 1 bytes from modem, data looks like: a3 . got 1 bytes from modem, data looks like: 00 . I have waited for 10 minutes and still nothing. Any idea how to make it work? Regards, Bogdan

13 years, 3 months

3
2
0 0

Newbie: C123 + layer1.compalram.bin + layer23

by Nicolas Bareil

Hello, I try to use the 'host23/mobile' application on a C123 but without success. I followed Steve's instructions[1] with today's git tree (d95eddad): 1. osmocon -p /dev/ttyS0 -m c123xor layer1.compalram.bin 2. ./host/layer23/src/mobile/mobile 3. Power on the phone (output of theses commands is thereafter) But I'm not sure it really works: the firmware seems to freeze (not responding to the power button anymore) and the last output of 'mobile' is: <0003> gsm322.c:257 Sync to ARFCN=104 rxlev=-65 (No sysinfo yet, ccch mode NONE) Based on the low rxlevel, I guess it is not acquiring any meaningful signal? In [2], Steve said the internal antenna was switched off when the cable is plugged in, is it still true? I tried to RTFM but I am stuck here. Thanks for your patience, Footnotes: [1] http://baseband-devel.722152.n3.nabble.com/Running-osmocombb-on-a-Motorol-C… [2] http://lists.osmocom.org/pipermail/baseband-devel/2010-May/000435.html ,---- | % osmocon -p /dev/ttyS0 -m c123xor layer1.compalram.bin | ... | Received DOWNLOAD ACK from phone, your code is running now! | | OSMOCOM Layer 1 (revision osmocon_v0.0.0-598-gd95edda) | ====================================================================== | Device ID code: 0xb4fb | Device Version code: 0x0000 | ARM ID code: 0xfff3 | cDSP ID code: 0x0128 | Die ID code: ebd8283cba021198 | ====================================================================== | 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 7478! | L1CTL_RESET_REQ: FULL!L1CTL_PM_REQ start=0 end=124 | PM MEAS: ARFCN=0, 27 dBm at baseband, -110 dBm at RF | PM MEAS: ARFCN=0, 26 dBm at baseband, -112 dBm at RF | PM MEAS: ARFCN=1, 30 dBm at baseband, -107 dBm at RF | PM MEAS: ARFCN=2, 29 dBm at baseband, -108 dBm at RF | PM MEAS: ARFCN=3, 43 dBm at baseband, -94 dBm at RF | PM MEAS: ARFCN=4, 32 dBm at baseband, -105 dBm at RF | ../.. | PM MEAS: ARFCN=1023, 33 dBm at baseband, -104 dBm at RF | L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=104, flags=0x7) | Starting FCCH RecognitionFB0 (1748:10): TOA=11712, Power=-106dBm, Angle=-22058Hz | FB0 (1775:11): TOA=12528, Power= -65dBm, Angle=-3818Hz | FB0 (1796:5): TOA= 5280, Power= -68dBm, Angle=-16117Hz | FB0 (1799:1): TOA= 96, Power=-109dBm, Angle= 7082Hz `---- ,---- | % ./host/layer23/src/mobile/mobile | ... | Failed to connect to '/tmp/osmocom_sap'. | Failed during sap_open(), no SIM reader | <000e> sim.c:1206 init SIM client | <0005> gsm48_cc.c:61 init Call Control | <0001> gsm48_rr.c:5330 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:3466 init PLMN process | <0003> gsm322.c:3467 init Cell Selection process | <0003> gsm322.c:3521 No stored BA list | VTY available on port 4247. | Mobile initialized, please start phone now! | <0002> gsm322.c:3093 (ms 1) Event 'EVENT_SWITCH_ON' for automatic PLMN selection in state 'A0 null' | <000d> gsm322.c:1055 SIM is removed | <0002> gsm322.c:1056 SIM is removed | <0002> gsm322.c:511 new state 'A0 null' -> 'A6 no SIM inserted' | <0003> gsm322.c:3313 (ms 1) Event 'EVENT_SWITCH_ON' for Cell selection in state 'C0 null' | <0003> gsm322.c:2986 Switch on without SIM. | <0003> gsm322.c:540 new state 'C0 null' -> 'C6 any cell selection' | <0003> gsm322.c:2404 Getting PM for frequency 0 twice. Overwriting the first! Please fix prim_pm.c | <0003> gsm322.c:2415 Found signal (frequency 3 rxlev -94 (16)) | <0003> gsm322.c:2415 Found signal (frequency 8 rxlev -86 (24)) | <0003> gsm322.c:2415 Found signal (frequency 16 rxlev -93 (17)) | ... | <0003> gsm322.c:2415 Found signal (frequency 819 rxlev -97 (13)) | <0003> gsm322.c:2404 Getting PM for frequency 955 twice. Overwriting the first! Please fix prim_pm.c | <0003> gsm322.c:2415 Found signal (frequency 982 rxlev -98 (12)) | ... | <0003> gsm322.c:2415 Found signal (frequency 1004 rxlev -91 (19)) | <0003> gsm322.c:2415 Found signal (frequency 1007 rxlev -89 (21)) | <0003> gsm322.c:2415 Found signal (frequency 1009 rxlev -97 (13)) | <0003> gsm322.c:2415 Found signal (frequency 1010 rxlev -86 (24)) | <0003> gsm322.c:2415 Found signal (frequency 1011 rxlev -67 (43)) | <0003> gsm322.c:2415 Found signal (frequency 1012 rxlev -86 (24)) | <0003> gsm322.c:2415 Found signal (frequency 1013 rxlev -80 (30)) | <0003> gsm322.c:2415 Found signal (frequency 1014 rxlev -87 (23)) | <0003> gsm322.c:2415 Found signal (frequency 1021 rxlev -82 (28)) | <0003> gsm322.c:2415 Found signal (frequency 1022 rxlev -98 (12)) | <0003> gsm322.c:2348 Found 97 frequencies. | <0003> gsm322.c:257 Sync to ARFCN=104 rxlev=-65 (No sysinfo yet, ccch mode NONE) `----

13 years, 3 months

4
7
0 0

AW: Osmocom-BB

by Andreas.Eversberg

hi, can you try the following steps: 1. start osmocon 2. start mobile (be sure it is not shutdown) 3. press the power button on the phone to start the loading process after loading the binary into the phone, the phone should indicate power on to the mobile process. andreas ________________________________ Von: Sebastian --- [mailto:seppel18@hotmail.com] Gesendet: Freitag, 7. Januar 2011 01:37 An: Andreas.Eversberg Betreff: Osmocom-BB Hi Thanks for your Help. Now it says ms 1 is still down "radio not started". Osmocon is running (with ramloader) and layer2 socket is available. hi sebastian, there are three ways to bing it down: - "enable" -> "conf t" -> "ms 1" -> "shutdown" - the layer2 socket does not exist on startup (osmocon loader not started) - the shutdown state is stored in the config (doing "write" when it is down) just bring it up after starting osmocon: - "enable" -> "conf t" -> "ms 1" -> "no shutdown" and don't forget "write" the config, so it must not be done on every startup. andreas

13 years, 3 months

1
0
0 0

OsmocomBB support in Motorola C168

by rakesh mukundan

Hi All. I am a newbie to OssmocomBB, though I have been reading the mails, never actually got a chance to start working. But after watching the 27C3 video, now I am totally inspired :) The problem I am facing the unavailability of the hardware, the only phone available to me as of now is Motorola C168, Can anyone tell me if it will be compact able with OsmocomBB? I have searched in the mailing list archives but could find an answer :( Thanks in Advance Regards ----- Rakesh Mukundan http://simplified-security.blogspot.com/

13 years, 3 months

3
2
0 0

MT612X RF Transceiver Data Sheet

by Fadil Berisha

I need programming Data Sheet for MT612X RF Transceiver, especially data for programming serial interface, internal registers, vco etc. Does somebody know link to get data? I did some google search and come to this link: http://code.google.com/p/ptmtk/source/checkout There, under directory mtk_datasheet found MT612X IC data with electrical data, pin description etc. There is also, reference phone design and detailed programming data sheet for Baseband processors MT6217, MT6219 and MT6253. Knowing that is under developing osmocomBB driver for MT, I thought this might interest you! koliqi

13 years, 3 months

1
0
0 0

Dropping the layer23 application?

by Holger Hans Peter Freyther

Hi all, I think the layer23 app was great when Dieter and others worked on the TX part of Osmocom but right now it has the potential of disturbing a real network. So it could be changed in a way that it checks if the firmware has TX disabled (maybe even make TX disabling a runtime setting), and then still follow the first assignment, never transmit anything and on a CIPHER MODE COMMAND switch back to the BCCH (or when no enc is used at the release message). comments? holger

13 years, 3 months

2
1
0 0

AW: administratively down?

by Andreas.Eversberg

hi sebastian, there are three ways to bing it down: - "enable" -> "conf t" -> "ms 1" -> "shutdown" - the layer2 socket does not exist on startup (osmocon loader not started) - the shutdown state is stored in the config (doing "write" when it is down) just bring it up after starting osmocon: - "enable" -> "conf t" -> "ms 1" -> "no shutdown" and don't forget "write" the config, so it must not be done on every startup. andreas ________________________________ Von: baseband-devel-bounces(a)lists.osmocom.org [mailto:baseband-devel-bounces@lists.osmocom.org] Im Auftrag von Sebastian --- Gesendet: Mittwoch, 5. Januar 2011 21:57 An: baseband-devel(a)lists.osmocom.org Betreff: administratively down? Next Problem: ./mobile says "MS '1' is administratively down". I tried everything..put osmocom.cfg in /etc/osmocom .... How can I bring it "UP"? (Like in Cisco world :)

13 years, 3 months

1
0
0 0

Compile Errors

by Sebastian ---

Hi, I use Ubuntu 9.10, when i try to Compile Osmocom, i get this: root@r00t-laptop:~# cd /home/r00t/install/osmocom-bb/src root@r00t-laptop:~/install/osmocom-bb/src# make cd shared/libosmocore/build-target && ../configure \ --host=arm-elf-linux --disable-vty --enable-panic-infloop \ --disable-shared --disable-talloc --disable-tests \ CC="/home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc" CFLAGS="-Os -ffunction-sections -I/home/r00t/install/osmocom-bb/src/target/firmware/include" configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-elf-linux-strip... no checking for strip... strip checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make sets $(MAKE)... (cached) yes checking for arm-elf-linux-gcc... /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... yes checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc accepts -g... yes checking for /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc... gcc3 checking build system type... i686-pc-linux-gnulibc1 checking host system type... arm-elf-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc... /home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld checking if the linker (/home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... no checking for arm-elf-linux-dumpbin... no checking for arm-elf-linux-link... no checking for dumpbin... no checking for link... link -dump -symbols configure: WARNING: using cross tools not prefixed with host triplet checking the name lister (link -dump -symbols) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 805306365 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld option to reload object files... -r checking for arm-elf-linux-objdump... no checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for arm-elf-linux-ar... no checking for ar... ar checking for arm-elf-linux-strip... strip checking for arm-elf-linux-ranlib... no checking for ranlib... ranlib checking command to parse link -dump -symbols output from /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc object... failed checking how to run the C preprocessor... /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... no checking for inttypes.h... no checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... no checking for objdir... .libs checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports -fno-rtti -fno-exceptions... no checking for /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc option to produce PIC... -fPIC -DPIC checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc PIC flag -fPIC -DPIC works... yes checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc static flag -static works... yes checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports -c -o file.o... yes checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports -c -o file.o... (cached) yes checking whether the /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc linker (/home/r00t/install/gnuarm-3.4.3/arm-elf/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... no checking whether to build static libraries... yes checking for ANSI C header files... (cached) yes checking execinfo.h usability... no checking execinfo.h presence... no checking for execinfo.h... no checking sys/select.h usability... no checking sys/select.h presence... no checking for sys/select.h... no checking if /home/r00t/install/gnuarm-3.4.3/bin/arm-elf-gcc supports -fvisibility=hidden... no configure: creating ./config.status config.status: creating libosmocore.pc config.status: creating libosmocodec.pc config.status: creating libosmovty.pc config.status: creating include/osmocom/Makefile config.status: creating include/osmocom/vty/Makefile config.status: creating include/osmocom/codec/Makefile config.status: creating include/osmocom/crypt/Makefile config.status: creating include/osmocore/Makefile config.status: creating include/osmocore/protocol/Makefile config.status: creating include/Makefile config.status: creating src/Makefile config.status: creating src/vty/Makefile config.status: creating src/codec/Makefile config.status: creating tests/Makefile config.status: creating tests/timer/Makefile config.status: creating tests/sms/Makefile config.status: creating tests/msgfile/Makefile config.status: creating tests/ussd/Makefile config.status: creating Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands cd shared/libosmocore/build-target && make make[1]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target' make all-recursive make[2]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target' Making all in include make[3]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include' Making all in osmocom make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' Making all in codec make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec' make[5]: Für das Ziel »all« ist nichts zu tun. make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec' Making all in crypt make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt' make[5]: Für das Ziel »all« ist nichts zu tun. make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt' make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' make[5]: Für das Ziel »all-am« ist nichts zu tun. make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' Making all in osmocore make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' Making all in protocol make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol' make[5]: Für das Ziel »all« ist nichts zu tun. make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol' make[5]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' make[5]: Für das Ziel »all-am« ist nichts zu tun. make[5]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include' make[4]: Für das Ziel »all-am« ist nichts zu tun. make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include' make[3]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/include' Making all in src make[3]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/src' Making all in . make[4]: Betrete Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/src' CC rate_ctr.lo ../../src/rate_ctr.c:24:22: inttypes.h: No such file or directory make[4]: *** [rate_ctr.lo] Fehler 1 make[4]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/src' make[3]: *** [all-recursive] Fehler 1 make[3]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target/src' make[2]: *** [all-recursive] Fehler 1 make[2]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target' make[1]: *** [all] Fehler 2 make[1]: Verlasse Verzeichnis '/home/r00t/install/osmocom-bb/src/shared/libosmocore/build-target' make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] Fehler 2 root@r00t-laptop:~/install/osmocom-bb/src#

13 years, 3 months

11
14
0 0

administratively down?

by Sebastian ---

Next Problem: ./mobile says "MS '1' is administratively down". I tried everything..put osmocom.cfg in /etc/osmocom .... How can I bring it "UP"? (Like in Cisco world :)

13 years, 3 months

1
0
0 0

HP 8922 at Helmut Singer

by Harald Welte

Hi, just in case anyone is looking for a HP 8922 MS tester, there is one available from Helmut Singer. It has an 'ok but not ridiculously cheap' price, based on Dieter and my experience. http://www.helmut-singer.de/stock/1552426140.html The 8922 is particularly well suited for layer 1 testing + development. I personally don't have one (only Racal 6103), and don't want to put another 20kg of old measurement equipment in my lab... -- - 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)

13 years, 3 months

2
1
0 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel January 2011