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

Engagetted !

by Sébastien Lorquet

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

6 months, 1 week

5
5
0 0

Receiving on TS=1 ?

by Sylvain Munaut

Hi, I've hacked something together to quickly test non-combined CCCH. However, I've hit a problem when trying to receive anything on another timeslot than 0. The TX side seems to work fine as the BTS can see my location update request and answers with a reject, but on the MS side, I never see the reject and wireshark only shows invalid incohrent data on the RX. The frames for SDCCH/8 show really nothing valid (looks like random bytes), things like 09 80 7f 47 49 06 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 09 00 47 d5 2d 06 1e 00 00 69 7c a0 91 3d 22 ff ab fe 6c 4f 56 4f 36 ... while the frames for the associated SAACH show at least something gsm-like : 03 03 01 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b 2b but that's not quite a SI5/6 ... To RX/TX on TS=1, I just delayed the RX/TX window by 625 bits (4 * 156.25) when I'm in dedicated channel mode by chaning the 'start' in l1s_tx_win_ctrl / l1s_rx_win_ctrl Is there something else that should be done ? Cheers, Sylvain

11 years, 9 months

2
5
0 0

burst_ind and TCH

by Mad

Hi Sylvain, hi list! I'm experimenting with burst_ind and TCHs right now and ran into some problem I couldn't solve yet. After receiving an Assignment Command for a hopping TCH/F I call l1ctl_tx_dm_est_req_h1() with all necessary parameters and tch_mode GSM48_CMODE_SPEECH_V1 or _EFR. After that I do get burst indications containing the received bits on up- and downlink for the active arfcn on each consecutive frame number. BUT the rx level measurements are most of the time very low and sporadic higher, surely not from that nearby bts and the very close cellphone. It looks like the layer1 doesn't "hit" the right timeslot on the right arfcn at the right time. There are some possible sources of error leading to that, like hopping parameters, channel number and MA list. But I checked these and I took all of them directly from the ASS CMD, the MA as word list in ascending order, like in layer23 IMM ASS handling. The specific AC doesn't have any specialties like Starting Time or "before time" parameters. So my question is if there is some obvious pitfall I'm missing and are there any suggestions how to debug that? Regards, Mad

11 years, 9 months

4
5
0 0

bursts****.dat

by Victor P

Hi, I am trying to use burst_ind branch of osmocom. I have noticed that layer23 creates bursts****.dat files when it indicates uplink. What data are written to these files and what should I use to see its data? Thank you.

11 years, 10 months

5
6
0 0

Use OsmocomBB as OpenBTS / airprobe clock generator

by Harald Welte

Hi! Recently we've had the idea of using OsmocomBB with a simple firmware that synchronizes to an existing GSM networks FCCH and use the resulting 13MHz clock to drive the USRP for airprobe or OpenBTS. Ideally, we would even use the Calypso-internal PLL (for ARM or DSP) to multiply it up to the required 52 MHz. However, neither the Openmoko nor the Compal/Motorola phones expose any of the 3 clock output pads :( So the only choice is to use something along the lines of the http://focus.ti.com/docs/prod/folders/print/cdcvf25084.html as a quad clock multiplier and attach it to the CLK13OUT signal of the phone. The chip is available for 9 USD in single quantities at digikey, and possibly cheaper at other sources. Combined with a sub-20EUR phone it might be a very cheap but still accurate frequency source for OpenBTS - at least as long as there are any commercial gsm networks available. 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)

12 years, 1 month

8
17
0 0

Linux + u-boot port to MT6235

by Marcin Mielczarczyk

Hi All! That's true, I managed to run U-Boot on MT6235, but linux kernel is not fully functional yet (it's fresh stuff as I managed to ran it on Tuesday and then I was off to conference). For MT6235 development I chose Sciphone G2, which is pretty cheap. After some time I managed to download code to SRAM (just 64KB) using MTK's FlashTool. MTK FlashTool communicates over UART directly with MT6235 bootloader and sends its own chunk of code (about 58KB) which is executed in SRAM and communicates with FlashTool. I found on pudn.com some pack to customize code loaded by FlashTool, thanks to which I could download my own code to SRAM (without JTAG). The problem was that it had to be linked with some security libraries which occupied about 56KB and not much memory left for my own code. Then I decided to try find JTAG pins to get all control on MT6235. That took me sometime, but finally I succeeded. The other bigger issue was initializing DRAM controller to be able to download bigger code (linux kernel + uboot) to external RAM. In sciphone there is problem that all interesting chips are under metal shield which is pretty havily soldered. In this case I couldn't read what kind of RAM memory is mounted without destroying the board (I don't have such soldering machine which could unsolder so big metal shield). Thanks to JTAG I could attach to target and then dump DRAM controller registers from processor running MTK's software, but setting these values after processor start and configuration of PLL didn't work. I decided to disassemble bootloader which could show me how DRAM controller is initialized and how code fron NAND is loaded (to be able to flash U-Boot and kernel to NAND so MT6235 will start my code automatically and I will not have to use JTAG). Currently I have knowledge how internal MT6235 bootloader is loading code from memory during startup and I also extracted procedure of DRAM controller initialization. Thanks to that I'm able to run U-Boot from the very begining of processor startup. The problem is that I have just one piece of Sciphone G2 and I don't want to flash it yet to not break existing code in it. Thanks to running device I'm able to attach with JTAG and check how peripherals are configured (i.e. LCD, MMC, etc.). I have backup of flash, but I'm not 100% sure if I will flash it back, phone will startup. That's why I bought second piece of Sciphone G2 and should receive it today or on Tuesday (this Monday is holiday in Poland). In this case I'll flash U-Boot to NAND and try to make it working. Then we could load the rest of code from U-Boot (to RAM or NAND over serial). You can see how my setup looks on attached picture. The good thing about it is that the same bootloader is used in MT622x, so it should be fairly easy to do the same on phones based on that SoCs (but unfortuantely it's just ARM7). If it comes to code, of course I can share it on "git.osmocom.org". Currently it's just basic port of U-Boot and not much for linux kernel, but I'm working on this now so I'll push it when it'll be ready. Currently I'm working on driver for NAND memory for U-Boot, so we could flash linux kernel. When that will be ready I'll push the code. Then I'll switch to linux kernel and when it'll be functional I also push the code. At this stage you will not need to have JTAG and you could load the code over serial in U-Boot. If it comes to GSM I didn't work with it before. I actualy worked 6 months in L2/3 team for LTE (on RRC) but it's different story. That could be really outstanding thing if we could run first phone ever with whole code open (from BB up to APP). BR, Marcin

12 years, 3 months

13
37
0 0

Problems while building osmocomBB

by Begerad Stefan

Hi guys, I dunno if that is the right place for my concern about building the osmocomBB source. Here is what I already have done: - downloading the sources for osmocomBB and GNU toolchain for ARM, - setting the PATH for the arm-elf-* executables, - calling make in the src directory. Now, this appears as response of the make command in the terminal: cd shared/libosmocore/build-host && ../configure configure: error: cannot find install-sh, install.sh, or shtool in ".." "../.." "../../.." make: *** [shared/libosmocore/build-host/Makefile] Error 1. If you need details about my system, you can look at the following snippet from the config.log file: This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by libosmocore configure UNKNOWN, which was generated by GNU Autoconf 2.65. Invocation command line was $ ../configure ## --------- ## ## Platform. ## ## --------- ## hostname = ubuntu-stefan uname -m = x86_64 uname -r = 2.6.32-24-generic uname -s = Linux uname -v = #41-Ubuntu SMP Thu Aug 19 01:38:40 UTC 2010 /usr/bin/uname -p = unknown /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin PATH: /usr/games PATH: /home/stefan/osmocomBB/gnuarm-4.0.2/bin ## ----------- ## ## Core tests. ## ## ----------- ## configure:2032: error: cannot find install-sh, install.sh, or shtool in ".." "../.." "../../..". So, I would be very glad, if someone could give me a hint to solve the problem. Thank you in advance. Regards, begy

12 years, 5 months

2
2
0 0

Motorola C116 experiment

by Henk

Hi, I could not resist buying a C116 for 15 euro, so I compiled osmocombb and connected a 3.3V serial cable. Of course the C116 was not in the supported list, but I was hoping it would work as it seems that it is very similar to the C115. Here is my load attempt: (used -m c123 ) but there's no loading of the image. I am not using TX mode, also I don't have a SIM installed. Anything I can try to get it working? ./osmocon -p /dev/ttyS0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 00 81 .. got 4 bytes from modem, data looks like: 1b f6 02 00 .... got 1 bytes from modem, data looks like: 41 A got 1 bytes from modem, data looks like: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=16788, hdr_len=4, dnload_le n=16795 got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o Regards, Henk

12 years, 9 months

6
7
0 0

Help me I have a difficult problem

by adel

Hello I'm having a problem in the start mobile application ~/osmocom-bb$ cd src/host/layer23/src/mobile ~/osmocom-bb/src/host/layer23/src/mobile$ ./mobile Copyright (C) 2008-2010 ... Contributions by ... License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Failed to parse the config file: '/etc/osmocom/osmocom.cfg' Please check or create config file using: 'touch /etc/osmocom/osmocom.cfg' ~/osmocom-bb/src/host/layer23/src/mobile$ Please help me as soon as -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Help-me-I-have-a-difficult-probl… Sent from the baseband-devel mailing list archive at Nabble.com.

12 years, 9 months

11
17
0 0

hmm, sorry, data cable question

by labad jala

Hello techies! I am new to the list and I acquired a c139. I'd like to buy a rs232/jack 2,5mm named t191 flash (and not unlock) cable. They look 100% the same (even stickers). Is this important? I understand that I have also to use a rs232/usb adapter. The one I have (U232P9 with link/tx/rx leds) gives +/-9,4 v. So my concern is to not fry the Moto..Any advise welcome. Cheers.

12 years, 11 months

8
10
0 0

about voice

by shrek wu

hi all, About voice，I have one question. In the latest git code, when I use bb to call other phone, it will product a file voice.raw. How I can play the voice.raw? which kind of format? 16bit or 8 bit pcm?16khz and 8khz?LSE or MSE? In fact i used the cooledit to play it, both 16khz and 8khz, it has only noise. Other question, I want to input voice from pc that run BB, then the voice can be sent by C123. But I found the voice that be sent by C123 is C123 input voice. Can we realize the idea? Best Regards Shrek W

12 years, 11 months

10
15
0 0

buzzer driver

by José Luis Pereira

Hi all, my name is Jose Pereira, and i'm very interested in helping you with some code! I've wrote the buzzer driver for calypso, not so sure if will help you of anything, but was just for experimenting :) Anyway, i send the patch in attachement. The interface can be simply #include <calypso/buzzer.h> buzzer_mode_pwt(1); buzzer_volume(40); buzzer_note(NOTE(NOTE_E,OCTAVE_5)); Please let me know what do you think of the code, and in what way i can further help. Best regards, -- José Pereira http://onaips.blogspot.com

13 years

2
1
0 0

unknown error

by royfarji india

while compiling i am getting the following error: "libosmocore.a" file in wrong format. arm-elf-objcopy --gap-fill=0xff -O binary board/pirelli_dpl10/layer1.highram.elf board/pirelli_dpl10/layer1.highram.bin arm-elf-ld -nostartfiles -nostdlib -nodefaultlibs --gc-sections --cref -T board/compal/ram.lds -Bstatic -Map board/compal_e88/loader.compalram.map -o board/compal_e88/loader.compalram.elf --start-group apps/loader/main.o abb/twl3025.o rf/trf6151.o display/font_r8x8.o display/font_r8x8_horiz.o display/st7558.o display/td014.o display/ssd1783.o display/display.o flash/cfi_flash.o board/common/calypso_uart.o board/common/calypso_pwl.o board/compal/rffe_dualband.o board/compal/rf_power.o board/compal_e88/init.o board/compal_e88/loader.compalram.manifest.o board/compal/start.ram.o board/compal/exceptions_redirected.o board/compal/handlers.o calypso/libcalypso.a layer1/liblayer1.a lib/libmini.a comm/libcomm.a ../../shared/libosmocore/build-target/src/.libs/libosmocore.a --end-group arm-elf-ld: ../../shared/libosmocore/build-target/src/.libs/libosmocore.a(crc16.o): Relocations in generic ELF (EM: 3) ../..*/shared/libosmocore/build-target/src/.libs/libosmocore.a: could not read symbols: File in wrong format*make[1]: *** [board/compal_e88/loader.compalram.elf] Error 1 make[1]: Leaving directory `/home/roy/osmocom-bb/src/target/firmware' make: *** [firmware] Error 2 roy@roy:~/osmocom-bb/src$ PLEASE HELP!!!!!!!!

13 years

3
2
0 0

Airprob compiling error

by Marten Christophe

Hello All, while I'm configuring airprobe/gsm-receiver i'm getting error, plz help me ===== checking for libosmocore >= 0.1.13... Requested 'libosmocore >= 0.1.13' but version of Osmocom Core Library is UNKNOWN <<<<<< ===== configure: error: Library requirements (libosmocore >= 0.1.13) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. <<<<<<<< ========= plz help me to tell how i can set PKG_CONFIG_PATH for libosmocore Kind Regards,

13 years

3
5
0 0

How to build osmocon for the target?

by Dave Schmidt

Hello everyone! I'm trying to run osmocombb on Neo Freerunner. Read and hopefully understood http://bb.osmocom.org/trac/wiki/{CalypsoRomloader,osmocon,OpenMoko}. One thing I completely miss is how to build osmocon for the target phone to be able to run ./osmocon -i 13 -m romload -p /dev/ttySAC0 layer1.highram.bin In the source tree, osmocon is built only for the host, and I do not see any configuration options to enable it also for the phone... Thanks in advance, D.

13 years

4
3
0 0

Funding from CELF to work on Osmocom integration

by Pierre Pronchery

Hi baseband-developers, I am looking for a freelance developer, preferably (provably) knowledgeable about the Osmocom project, to work together on a project potentially funded by CELF; the objective is to use Osmocom through a telephony GUI to make regular phone calls. I would like to use the "Phone" project from DeforaOS as the GUI, but feel free to mention if you are from a different project and want to step in. Some background information: CELF is otherwise known as the CE Linux Forum. It's supposed to merge with the Linux foundation eventually: http://www.linuxfoundation.org/news-media/announcements/2010/10/linux-found… What brings me here is their "CELF Open Project Proposal 2011": http://elinux.org/CELF_Open_Project_Proposal_2011 « The CELF Open Project Proposal is a process whereby members of the public can submit to the CE Linux Forum ideas and proposals for projects that they think should be worked on to enhance embedded Linux » FWIW, it was mentioned in the Openmoko Community Updates for February 2011: http://wiki.openmoko.org/wiki/Community_Updates/2011-02-01#General_News This is how I got to know about it right before the deadline, and had to rush to submit my current project idea, which is to integrate Osmocom with a Linux-based telephony GUI: http://elinux.org/Add_Osmocore_support_to_the_DeforaOS_Phone_GSM_stack About Osmocom: http://bb.osmocom.org/trac/ « OsmocomBB is an Free Software / Open Source GSM Baseband software implementation » The submission was accepted, and I am now required to send a bid for the project. Needs to be estimated: - how much time would be needed (and availabilities), - how much money would be needed, - which issues can be anticipated. I will also welcome suggestions as to which hardware to use for this task. Technically, the proposal is about integrating Osmocom with a Linux-based smartphone environment, so I'm not speaking about improving the LCD support for feature phones. Something like the Openmoko Freerunner is closer to what I have in mind, which is also what I'm currently using (and as you may know, it has a Calypso-based GSM baseband, which is supported by Osmocom already). Before I conclude, let me mention that I want definite answers about people who will be serious about this. Feel free to forward this message to anyone else whom you know and should also participate to this project. My current estimation is that three to four weeks should be sufficient for two people to: - expose and glue a more "UI-developer-friendly" API, probably closer to the Telnet interface (see layer23/src/mobile/vty_interface.c) - make sure everything is as reliable as possible (eg baseband initialization...) - likewise, make sure the GUI and Osmocom are integrated correctly - test, test, test. HTH, -- khorben

13 years

2
1
0 0

Forward of moderated message

by osmocom-announce-bounces＠lists.osmocom.org

13 years

1
0
0 0

Does the jolly/bts tree work?

by cbalke＠charter.net

I got two phones working with osmocom-bb. I compiled jolly/bts and it runs with two phones. I also compiled openbsc and connected the bts application to it. The problem is that timer T200 expires. I also get TX TCH/F errors before the timer expires on the bts application side. I am not sure if this is because of a configuration error on my part, or if the code was never completed enough to link a phone to it. I have tried using the default nanobts configuration file, but it does not work. If it isn't completed yet, what needs to be done? Is there anything that needs to be changed in the default nanobts configuration file? Just so you know, The reason why my email display name is not here, is because I am using backtrack linux and webmail to post this. Thank you for taking the time to help me, Calvin E. Balke

13 years

2
1
0 0

[ADM] New commitlog mailing list

by Harald Welte

Hi all! We haven't had a functioning commit log mailinglist since mid-2009, when the revision control system of openbsc was converted from svn to git. Especially today, with the large number of separate git repositories on http://cgit.osmocom.org/, it is very easy to loose track of what other developers are doing. The new mailing list 'osmocom-commitlog' (renamed from openbsc-commits) will receive updates from all repositories on git.osmocom.org. Feel free to subscribe at http://lists.osmocom.org/mailman/listinfo/osmocom-commitlog Cheers, 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

2
2
0 0

[ADM] Problems with osmocom git server

by Harald Welte

Hi all! We're sorry to report that there are some problems with our git repositories at the moment, resulting in 'early EOF / index-pack failed' messages when users are attempting to clone one of our repositories. The problem has been thoroughly analyzed, but even after many hours of analysis, no solution has been found yet. Your best chance is to keep re-trying the clone, in 5-10% of the cases it will succeed. More technical details are available at this posting to the git mailing list: http://article.gmane.org/gmane.comp.version-control.git/169909 Sorry for the inconvenience. -- - 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

2
2
0 0

git help

by bch2011＠sina.cn

$ git clone git://git.osmocom.org/osmocom-bb.git Cloning into osmocom-bb... remote: Counting objects: 10960, done. remote: Compressing objects: 100% (2599/2599), done. fatal: The remote end hung up unexpectedly8 MiB | 23 KiB/s fatal: early EOF fatal: index-pack failed

13 years, 1 month

2
1
0 0

git error

by bch2011＠sina.cn

$ git clone git://git.osmocom.org/osmocom-bb.git Cloning into osmocom-bb... remote: Counting objects: 10960, done. remote: Compressing objects: 100% (2599/2599), done. fatal: The remote end hung up unexpectedly8 MiB | 23 KiB/s fatal: early EOF fatal: index-pack failed  

13 years, 1 month

2
1
0 0

bcch_scan initialization and L1

by weberbe＠ee.ethz.ch

Hi everbody I'm currently working on a project at our university where we are trying to connect bcch_scan with our existing hardware/software. The latter consists of L1 implementation partly in hardware and partly in software. The software part is also used to provide the interface towards bcch_scan. So far, the software interface does not do much it just provides the necessary domain sockets and dumps everything it receives from bcch_scan. Now, my question is whether there is some kind of initialization sequences sent from bcch_scan to the phone. And is there any other info you can provide about the messages sent from bcch_scan to the phone and the other way round? Naturally, I tried to find this out myself by looking though the source but didn't get very far. Oh and by the way, the ultimate goal of this project is that we can use bcch_scan to test our L1 hardware. This would be pretty cool Thanks in advance Benjamin

13 years, 1 month

2
2
0 0

Mediatek RF development informations

by Marcin.Mielczarczyk＠tieto.com

Hi list, I'd like to give you some informations about findings on Mediatek's RF. Sciphone G2 has MT6140 transceiver which seems to be different than MT6139. MT6140 has much more registers to configure at init time (CW0 - CW12, CW15) while MT6139 has just 5 registers (CW0, CW1, CW2, CW9 and CW11). Common registers for MT6140 and MT6139 has also different fields (i.e. register CW0 has reset bit on different offset on MT6140). These findings where first discovered during sniffing of BSI interface. After some time I also found source code for Mediatek's SoCs family on Google Code pages: http://code.google.com/p/mobile-phone-mtk-project/ You can find there source code with drivers for Mediatek RF part (MT6139, MT6140, Murata antenna switches and Mediatek Power Amplifiers). Source code is located under "l1/l1d" directory. This part is delivered as source code because Mediatek wants to give customers chance to change RF electronic components (customers are able to write thair own drivers). The rest of layer 1 code (code which calls RF drivers and uses DSP) is delivered as library "l1.lib". Thanks to above code I confirmed my concernings about difference between MT6139 and MT6140. I prepared initial version of drivers for BPI, BSI, BFE (Baseband Front End) and MT6140 and placed them in U-Boot. MT6140 driver is based on Harald's MT6139 driver from OsmocomBB. It's initial driver which just configures needed peripherals (BSI, BPI, BFE, TDMA, APC, MT6140, MURA465 and RF3159) and performs TX on given ARFCN channel. U-Boot command for that is following: Rf_tx <arfcn> After execution, using spectrum analyzer you should see transmission on given frequency (so far I just tested on low band). This code doesn't use APC yet, but driver is already written, it just needs to be tested (it means that TX has currently very low power). If it comes to RF part, documentation which is available is sufficient, I already know how to configure hardware and I don't expect bigger problems here, that's why I started investigations on DSP. MT6235 has two DSP processors (master and slave). These procesors are from Analog Devices family ADSP-218x. Most probably it's ADSP-2181 (it's just assumption, I haven't found any statement about it). Thanks to code mentioned above it's possible to identify DSP functions and disassemble them. Above code is compiled for MT6223 (ARM7) SoC and it provides symbols table (file: BIRDCELLTEL23_08B_NEP_162_PCB01_gsm_MT6223_S00.sym). Most of this code is also available on Sciphone G2 (comparing binary files) and I'm able to identify addresses of functions and break in these functions using JTAG. It means that I can debug on real hardware, that's really convenient and easy to understand what's going on. I already disassembled functions for DSP init and patch loading over IDMA port (probably DSP code is executed from ROM) and I'll continue this task. Hopefully we'll be able to start sending real TX data soon. -- Recently I received patches with Linux drivers for Sciphone's USB port from Krzysztof Antonowicz and I wanted to thank for his effort. Right now it's possible to use Sciphone as Mass Storage device and it'll be possible to run Ethernet gadget. Unfortunatelly I can't clone Linux/Uboot repository right now and I didn't deliver patches for RF and USB. As soon as I'll succeed cloning of repository, I'll deliver functionality which I described above. I'll also backport drivers I'm writing now to OsmocomBB. Best regards, Marcin

13 years, 1 month

1
0
0 0

Re: [PATCH OSMOCOM-BB] src: use new libosmogsm and include/osmocom/[gsm|core] path to headers

by Harald Welte

Hi Pablo, On Tue, Mar 22, 2011 at 05:16:58PM +0100, pablo(a)gnumonks.org wrote: > This patch also renames hexdump in osmocon.c and osmoload.c > to avoid clashing with hexdump defined in libosmocore. This > is a workaround, it's planned to fix the namespace pollution > of the library soon. how did you test this patch? Did you first update the libosmocore copy inside osmocom-bb.git using 'git-subtree', and then apply + test your patch? Did you make sure that new libosmocore will also build using the cross-compiler for the phone firmware (see + use the osmocom-bb/src/Makefile) ? Also, for the future: please note the mailing list for osmocom-bb is 'baseband-deve(a)lists.osmocom.org', not the openbsc list... Thanks, 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, 1 month

2
1
0 0

Linux + u-boot port to MT6235

by Harald Welte

Hi All! At my OpenBSC / OsmocomBB talk here at the Embedded Linux Conference Europe, one of the attendees (Marcin, see Cc) came to me after the talk and told me he had recently done a u-boot and Linux kernel port to the MT6235 (that's the ARM926 based chipsets found in the touchscreen MTK phones). He said he has no understanding of GSM or the existing MTK firmware, but is interested in working together with us to try to make the GSM part work. I think that chipset is very intesting, as we could implement the layer1 inside the Linux kernel (and submit that mainline, yay!) and run our layer2 and layer3 implementations as userspace processes on the Linux system, together with the user interface. The performance of those devices should be somewhere between the Openmoko GTA01 and GTA02, and the GSM stack is certainly not going to eat away a lot of the CPU either. I have asked Marcin to write mail to the OsmocomBB mailing list on where we can find the code. He has so far downloaded the code using JTAG. Combining his code with our ramloader might remove that JTAG dependency... Marcin: if you want to push your u-boot / kernel to git.osmocom.org, or want a separate trac installation for your mtk-linux work, pleaes let me know, I'd be happy to host that. 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, 1 month

2
1
0 0

Compiling issue

by Derek Murphy

I'm running Ubuntu 10.10 and having a couple of issues. I've got both options for the toolchain work, only one is in the path at a time while testing. With one of them it seems to compile fine: I can use ./osmocom with something like hello world and this works. However when I go to look at layer23 the binary has not been compiled and I have this error in the conf.log: configure:3833: checking for gps_waiting in -lgps configure:3858: gcc -o conftest -g -O2 conftest.c -lgps >&5 /usr/bin/ld: cannot find -lgps collect2: ld returned 1 exit status configure:3858: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "" | #define PACKAGE_TARNAME "" | #define PACKAGE_VERSION "" | #define PACKAGE_STRING "" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "" | #define PACKAGE "layer23" | #define VERSION "0.0.0" | /* end confdefs.h. */ I'm sure most of these are environment error but wanted to check. In the update-libosmocore.sh I get an error that git-subtree doesn't exist. I found git subtree as a third party install that was not in the documentation but it's command is git subtree versus being git-subtree. Any thoughts would be appreciated.

13 years, 1 month

1
1
0 0

Re: Vcc c155?

by Henk

Well the datacable for c155 is a T191 so 3.3v. This is not the answer to your question but i hope it helps. ;)

13 years, 1 month

6
7
0 0

osmocon on gta02

by suraev＠stud.ntnu.no

Hello. I've updated & rebuilt osmocom and now I can't use osmocon on gta02 anymore :( Previously I started it like: ./osmocon -i 13 -m romload -p /dev/ttySAC0 layer1.highram.bin power-cycle modem and it started to load firmware. However with recent version firmware is loaded even without power-cycle! When I use hello_world.highram.bin I got exactly the same output as before. But when I use layer1.highram.bin I have problems running osmoload -l /tmp/loader ping Query timed out. What went wrong and how do I fix it? best regards, Max.

13 years, 1 month

1
2
0 0

problem with dream g2

by francisco flores

hi im francisco from argentina . i can compiled the code for sciphone dream g2 . i make the serial cable but no work is necesary configuration phone? o the conversor usb to serial? because i conect the cable a usb from mi pc and no work

13 years, 1 month

1
0
0 0

Re: require your help

by Henk

Hmm lets continue on the list... Well try to keep it simple, probably some config is needed from top level makefiles. This is what i use: export PATH=$PATH:/home/xxxyyyx/prj/toolchain/arm-elf/bin cd src make -e CROSS_TOOL_PREFIX=arm-elf- On Thu, Mar 17, 2011 at 1:16 PM, royfarji india <roy.techie(a)gmail.com> wrote: > Hello henk, > Sorry to bother you for this.I am a student and have little trouble in > building osmocom.I require your help please. > While building the project osmocom I get this error saying that the header > file 'signal.h' is missing in osmocore.I am just uanble to figure it how it > is unable to include the header file.By the way I am using the gnuarm-3.4.3 > as shown on the osmocom-bb website.One more query please - as to exactly > where do we have to put the armtoolchain(meaning which directory).Waiting > eagerly for your reply. > > > > roy@roy:~/osmocom-bb$ cd src > roy@roy:~/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="arm-elf-gcc" CFLAGS="-Os -ffunction-sections > -I/home/roy/osmocom-bb/src/target/firmware/include -nostartfiles > -nodefaultlibs" > 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... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking whether make sets $(MAKE)... (cached) yes > checking for arm-elf-linux-gcc... 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 arm-elf-gcc accepts -g... yes > checking for arm-elf-gcc option to accept ISO C89... none needed > checking for style of include used by make... GNU > checking dependency style of arm-elf-gcc... gcc3 > checking build system type... i686-pc-linux-gnu > 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 arm-elf-gcc... > /home/roy/osmocom-bb/gnuarm-3.4.3/arm-elf/bin/ld > checking if the linker (/home/roy/osmocom-bb/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/roy/osmocom-bb/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 arm-elf-gcc > object... failed > checking how to run the C preprocessor... 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 arm-elf-gcc supports -fno-rtti -fno-exceptions... no > checking for arm-elf-gcc option to produce PIC... -fPIC -DPIC > checking if arm-elf-gcc PIC flag -fPIC -DPIC works... yes > checking if arm-elf-gcc static flag -static works... yes > checking if arm-elf-gcc supports -c -o file.o... yes > checking if arm-elf-gcc supports -c -o file.o... (cached) yes > checking whether the arm-elf-gcc linker > (/home/roy/osmocom-bb/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 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 tests/smscb/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]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' > make all-recursive > make[2]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' > Making all in include > make[3]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include' > Making all in osmocom > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' > Making all in codec > make[5]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec' > make[5]: Nothing to be done for `all'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec' > Making all in crypt > make[5]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt' > make[5]: Nothing to be done for `all'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt' > make[5]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' > make[5]: Nothing to be done for `all-am'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' > Making all in osmocore > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' > Making all in protocol > make[5]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol' > make[5]: Nothing to be done for `all'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol' > make[5]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' > make[5]: Nothing to be done for `all-am'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include' > make[4]: Nothing to be done for `all-am'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include' > make[3]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include' > Making all in src > make[3]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src' > Making all in . > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src' > make[4]: Nothing to be done for `all-am'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src' > Making all in vty > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty' > Making all in codec > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec' > make[3]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src' > Making all in tests > make[3]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests' > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests' > make[4]: Nothing to be done for `all-am'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests' > make[3]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests' > make[3]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' > make[3]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' > make[2]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' > make[1]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' > cd shared/libosmocore/build-host && ../configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking whether make sets $(MAKE)... (cached) yes > checking for gcc... 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... no > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking for style of include used by make... GNU > checking dependency style of gcc... gcc3 > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-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 gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) 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 /usr/bin/ld option to reload object files... -r > checking for objdump... objdump > checking how to recognize dependent libraries... pass_all > checking for ar... ar > checking for strip... strip > checking for ranlib... ranlib > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking how to run the C preprocessor... 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... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for dlfcn.h... yes > checking for objdir... .libs > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC -DPIC > checking if gcc PIC flag -fPIC -DPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.o... (cached) yes > checking whether the gcc linker (/usr/bin/ld) supports shared libraries... > yes > checking whether -lc should be explicitly linked in... no > 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... yes > checking whether to build static libraries... yes > checking for ANSI C header files... (cached) yes > checking execinfo.h usability... yes > checking execinfo.h presence... yes > checking for execinfo.h... yes > checking sys/select.h usability... yes > checking sys/select.h presence... yes > checking for sys/select.h... yes > checking if gcc supports -fvisibility=hidden... yes > 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 tests/smscb/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-host && make > make[1]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host' > make all-recursive > make[2]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host' > Making all in include > make[3]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include' > Making all in osmocom > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom' > Making all in vty > make[5]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/vty' > make[5]: Nothing to be done for `all'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/vty' > Making all in codec > make[5]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/codec' > make[5]: Nothing to be done for `all'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/codec' > Making all in crypt > make[5]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/crypt' > make[5]: Nothing to be done for `all'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/crypt' > make[5]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom' > make[5]: Nothing to be done for `all-am'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom' > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom' > Making all in osmocore > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore' > Making all in protocol > make[5]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol' > make[5]: Nothing to be done for `all'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol' > make[5]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore' > make[5]: Nothing to be done for `all-am'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore' > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore' > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include' > make[4]: Nothing to be done for `all-am'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include' > make[3]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include' > Making all in src > make[3]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src' > Making all in . > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src' > make[4]: Nothing to be done for `all-am'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src' > Making all in vty > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/vty' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/vty' > Making all in codec > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/codec' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/codec' > make[3]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src' > Making all in tests > make[3]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests' > Making all in timer > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/timer' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/timer' > Making all in sms > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/sms' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/sms' > Making all in ussd > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/ussd' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/ussd' > Making all in smscb > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/smscb' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/smscb' > Making all in msgfile > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/msgfile' > make[4]: Nothing to be done for `all'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/msgfile' > make[4]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests' > make[4]: Nothing to be done for `all-am'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests' > make[3]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests' > make[3]: Entering directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host' > make[3]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host' > make[2]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host' > make[1]: Leaving directory > `/home/roy/osmocom-bb/src/shared/libosmocore/build-host' > make -C host/layer23 > make[1]: Entering directory `/home/roy/osmocom-bb/src/host/layer23' > Making all in include > make[2]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include' > Making all in osmocom > make[3]: Entering directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom' > Making all in bb > make[4]: Entering directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb' > Making all in common > make[5]: Entering directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/common' > make[5]: Nothing to be done for `all'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/common' > Making all in misc > make[5]: Entering directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/misc' > make[5]: Nothing to be done for `all'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/misc' > Making all in mobile > make[5]: Entering directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/mobile' > make[5]: Nothing to be done for `all'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/mobile' > make[5]: Entering directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb' > make[5]: Nothing to be done for `all-am'. > make[5]: Leaving directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb' > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb' > make[4]: Entering directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom' > make[4]: Nothing to be done for `all-am'. > make[4]: Leaving directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom' > make[3]: Leaving directory > `/home/roy/osmocom-bb/src/host/layer23/include/osmocom' > make[3]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include' > make[3]: Nothing to be done for `all-am'. > make[3]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include' > make[2]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include' > Making all in src > make[2]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/src' > Making all in common > make[3]: Entering directory > `/home/roy/osmocom-bb/src/host/layer23/src/common' > CC l1ctl.o > l1ctl.c:33: fatal error: osmocore/signal.h: No such file or directory > compilation terminated. > make[3]: *** [l1ctl.o] Error 1 > make[3]: Leaving directory > `/home/roy/osmocom-bb/src/host/layer23/src/common' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/src' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23' > make: *** [host/layer23/layer23] Error 2 >

13 years, 1 month

1
0
0 0

Vcc c155?

by Sergio Basan

Hi I want to join the team. But, What is the Vcc of motorola c155? Sorry, I could not find this trifling matter on the Internet.

13 years, 1 month

1
0
0 0

Vcc c155?

by Sergio Basan

Hi I want to join the team. But, What is the Vcc of motorola c155? Sorry, I could not find this trifling matter on the Internet.

13 years, 1 month

1
0
0 0

cell_log and kalibrator

by suraev＠stud.ntnu.no

Hey. Did I got it right that instead of using at commands and gprs-capable modem for clock calibration (as in http://gnuradio.org/redmine/wiki/1/OpenBTSClockCalibration) we can use output of [power] section of cell_log? Have somebody tried this? Above-mentioned page says that it "is obvious how the values were obtained" for executing ./kal script. As a matter of fact - it's not, at least not for newbies :( For example I got following in cell_log: arfcn 740 -99 -105 -109 -108 -110 -107 -108 -103 -109 -108 -110 -100 Seems like pretty good signal strength. No I should run ./kal -f NNN -u adjust clock in my usrp and run ./kal again. But what's the formula for obtaining NNN from arfcn 740? Can you advise me on some improving reading? thank you, Max.

13 years, 1 month

2
1
0 0

quad-band support

by Andreas.Eversberg

hi, i like to introduce support for additional bands for osmocom/layer23: - GSM 850 - PCS (1900) - GSM 480 and GSM 450 all bands can be enabled/disabled individually via VTY settings. by default, only 900 and DCS (1800) are enabled. note that the bands must be supported by the phone's tranceiver in order use them. to test it in the US, change your VTY settings like this: enable configure terminal ms 1 (or whatever your instance name is) support no p-gsm no e-gsm no r-gsm gsm-850 no dcs pcs end write of course you may enable all four bands, but this makes no sense, because your hardware does not support all bands. you will find the support in the jolly/quadband branch. it will be merged, if it is fully tested. be sure to set "ulimit unlimited" in your shell to get a core dump in case of a crash, so you can use gdb to locate where it happened: "gdb ./mobile core" everything else should work as usual. regards, andreas

13 years, 1 month

2
1
0 0

AW: quad-band support

by Andreas.Eversberg

please note: remove the ".ba" files from your osmocom config dir when switching back to mobile of master branch. this is because the structure of the band allocation file has changed. the new file includes a version string that must match, so there is no need to remove the file when upgrading in the future or when changing to the quadband branch.

13 years, 1 month

1
0
0 0

compile problems using patch

by royfarji india

I had some compilation problems in buiding osmocom-bb using gnuarm-3.4.3. I have used the patch present at: http://baseband-devel.722152.n3.nabble.com/PATCH-Adjust-top-level-Makefile-… please help roy@roy:~$ cd osmocom-bb roy@roy:~/osmocom-bb$ cd src roy@roy:~/osmocom-bb/src$ make cd shared/libosmocore/build-target && make make[1]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' make all-recursive make[2]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' Making all in include make[3]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include' Making all in osmocom make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' Making all in codec make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec' Making all in crypt make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt' make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' Making all in osmocore make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' Making all in protocol make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol' make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include' make[3]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include' Making all in src make[3]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src' Making all in . make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src' Making all in vty make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty' Making all in codec make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec' make[3]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src' Making all in tests make[3]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests' Making all in timer make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer' CCLD timer_test timer_test.o: In function `main': /home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer/../../../tests/timer/timer_test.c:66: undefined reference to `bsc_schedule_timer' /home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer/../../../tests/timer/timer_test.c:67: undefined reference to `bsc_schedule_timer' /home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer/../../../tests/timer/timer_test.c:68: undefined reference to `bsc_schedule_timer' timer_test.o: In function `timer_fired': /home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer/../../../tests/timer/timer_test.c:51: undefined reference to `bsc_schedule_timer' /home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer/../../../tests/timer/timer_test.c:52: undefined reference to `bsc_del_timer' ../../src/.libs/libosmocore.so: undefined reference to `msgb_dequeue' ../../src/.libs/libosmocore.so: undefined reference to `bsc_nearest_timer' ../../src/.libs/libosmocore.so: undefined reference to `msgb_enqueue' ../../src/.libs/libosmocore.so: undefined reference to `bsc_prepare_timers' ../../src/.libs/libosmocore.so: undefined reference to `bsc_timer_check' ../../src/.libs/libosmocore.so: undefined reference to `msgb_free' ../../src/.libs/libosmocore.so: undefined reference to `msgb_alloc' ../../src/.libs/libosmocore.so: undefined reference to `get_string_value' ../../src/.libs/libosmocore.so: undefined reference to `get_value_string' ../../src/.libs/libosmocore.so: undefined reference to `bsc_update_timers' collect2: ld returned 1 exit status make[4]: *** [timer_test] Error 1 make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests/timer' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' make: *** [shared/libosmocore/build-target/src/.libs/libosmocore.a] Error 2 roy@roy:~/osmocom-bb/src$

13 years, 1 month

1
0
0 0

AW: Order of functions to transmit and receive using layer1

by Andreas.Eversberg

hi, > I was wondering how to transmit and receive using layer1. I have > been reading some of the gsm specs. I have been looking around in the > source code a lot, and there many functions that are used for transmit > and receive. Which are the right few to use? there are only two types of data between L1 and L2: data frames and channel request burst. all the other functions control the radio and the channel in which to communicate. the layer 1 is controlled by the radio ressource protocol (gsm48_rr.c). in order to understand the channel multiplexing, you should read GSM TS 05.02. > Is there any way to send > a text message to a different phone by simulating a base station? osmocom is not (yet) able to control baseband hardware to act as a BTS. > Do I > need two phones or one phone to transmit and receive as a base station? in order to have more than a BCCH, you need two phones. one phone is not able to send and receive at a time. continuouly transmission is required for other phones to find a cell. > Is there any way to make a half duplex base station on a BCCH channel > with only one subscriber phone at a time, and what would that entail > code-wise? you can limit the number of active calls by limiting the number of channels on the BTS, but you cannot limit the number of phones camping on the BTS. > Would it be legal to run a very low power base station in the USA on a different unused cellular band/frequency? you need to check the FCC for laws and test licenses. > I have a lot of > free time since I do school at home and I could probably help develop > some new parts of the osmocom-bb project if you want me to. I know C, > some x86 assembly, and a few other languages. I have also had practice > fixing compile-time errors, and bugs in code. I apologize if this is > too many questions. You don't have to answer them all if you don't want to. if you are really interested. you should start reading with TS 04.08. this is what i did. it describes all the three "layer 3" protocols. Thank you for helping, Calvin E. Balke

13 years, 1 month

1
0
0 0

DSP dump from C116

by Henk

Hi all, I am trying to get a dump of the DSP code, but after 2 lines of hex the device seems to get stuck. Some watchdog or so, missing something in the initialization sequence? According to the docs the cDSP ID seems to indicate a version B dsp... Any ideas what I can do to investigate? - Henk ./osmocon -p /dev/ttyS0 -m c123 ../../target/firmware/board/compal_e88/compal_dsp_dump.compalram.bin Output: (I had commented the register locations to see if it helped...) OSMOCOM Compal DSP Dumper (revision osmocon_v0.0.0-780-gb7a4d8d-modified) ====================================================================== Device ID code: 0xb4fb ==> CalypsoLite Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 ==> Version B Die ID code: 168f2c10cb001251 ====================================================================== Assert DSP into Reset Releasing DSP from Reset DSP bootloader version 0x0100 DSP dump: DROM [09000-0dfff] 09000 : 0006 0052 ff7d 009a ffc8 fd21 00b7 ffbf fef7 0009 ff2e fe97 0071 02ce 0719 03f2 09010 : 04be 0625 0359 0535 08e4 033b 0620 078d 02cd 07c5 089e 0346 0494 071f 02d1 03e8

13 years, 1 month

3
3
0 0

hi all

by 麦田守望

can you tell me the osmocom is a free phone software Project or other is it make a GSM Network for free ? i think to make a samll GSM network for free i think use usb interface phone

13 years, 1 month

3
2
0 0

c123 boot wihtout battery

by its sead

hi list, I would like to run the c123(s) without the LI battery with direct 5V power supply only. Without battery the c123 display just blinks and no PROMPT1 can be received. Anyone knows a way how this might work ? (- like bypass or bridge this 3 pin battery pins) thanks for your help (sorry for the lame add) -- Schon gehört? GMX hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://www.gmx.net/de/go/toolbar

13 years, 1 month

3
2
0 0

Order of functions to transmit and receive using layer1

by Calvin Balke

I was wondering how to transmit and receive using layer1. I have been reading some of the gsm specs. I have been looking around in the source code a lot, and there many functions that are used for transmit and receive. Which are the right few to use? Is there any way to send a text message to a different phone by simulating a base station? Do I need two phones or one phone to transmit and receive as a base station? Is there any way to make a half duplex base station on a BCCH channel with only one subscriber phone at a time, and what would that entail code-wise? Would it be legal to run a very low power base station in the USA on a different unused cellular band/frequency? I have a lot of free time since I do school at home and I could probably help develop some new parts of the osmocom-bb project if you want me to. I know C, some x86 assembly, and a few other languages. I have also had practice fixing compile-time errors, and bugs in code. I apologize if this is too many questions. You don't have to answer them all if you don't want to. Thank you for helping, Calvin E. Balke

13 years, 1 month

2
1
0 0

Sorry for this kind of mail: but please help||

by royfarji india

Hello everyone, Sorry to bother you all.I am a student and desire to become researchers like you all out there. While building the project osmocom I got an unique error which no-one in the mailing lists have got yet.It says that the header file 'signal.h' is missing in osmocore.I am just uanble to figure it how it is unable to include the header file. please help.Also I am attaching the file of compilation.By the way I am using the gnuarm-3.4.3 as shown on the osmocom-bb website.

13 years, 1 month

2
2
0 0

compile errors

by royfarji india

Hello everyone, Sorry to bother you all.I am a student and desire to become researchers like you all out there. While building the project osmocom I got an unique error which no-one in the mailing lists have got yet.It says that the header file 'signal.h' is missing in osmocore.I am just uanble to figure it how it is unable to include the header file. please help.By the way I am using the gnuarm-3.4.3 as shown on the osmocom-bb website. roy@roy:~/osmocom-bb$ cd src roy@roy:~/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="arm-elf-gcc" CFLAGS="-Os -ffunction-sections -I/home/roy/osmocom-bb/src/target/firmware/include -nostartfiles -nodefaultlibs" 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... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make sets $(MAKE)... (cached) yes checking for arm-elf-linux-gcc... 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 arm-elf-gcc accepts -g... yes checking for arm-elf-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of arm-elf-gcc... gcc3 checking build system type... i686-pc-linux-gnu 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 arm-elf-gcc... /home/roy/osmocom-bb/gnuarm-3.4.3/arm-elf/bin/ld checking if the linker (/home/roy/osmocom-bb/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/roy/osmocom-bb/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 arm-elf-gcc object... failed checking how to run the C preprocessor... 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 arm-elf-gcc supports -fno-rtti -fno-exceptions... no checking for arm-elf-gcc option to produce PIC... -fPIC -DPIC checking if arm-elf-gcc PIC flag -fPIC -DPIC works... yes checking if arm-elf-gcc static flag -static works... yes checking if arm-elf-gcc supports -c -o file.o... yes checking if arm-elf-gcc supports -c -o file.o... (cached) yes checking whether the arm-elf-gcc linker (/home/roy/osmocom-bb/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 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 tests/smscb/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]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' make all-recursive make[2]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' Making all in include make[3]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include' Making all in osmocom make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' Making all in codec make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/codec' Making all in crypt make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom/crypt' make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocom' Making all in osmocore make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' Making all in protocol make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore/protocol' make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include/osmocore' make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include' make[3]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/include' Making all in src make[3]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src' Making all in . make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src' Making all in vty make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/vty' Making all in codec make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src/codec' make[3]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/src' Making all in tests make[3]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests' make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests' make[3]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target/tests' make[3]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' make[3]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' make[2]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' make[1]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-target' cd shared/libosmocore/build-host && ../configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make sets $(MAKE)... (cached) yes checking for gcc... 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... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-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 gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) 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 /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking how to run the C preprocessor... 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... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no 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... yes checking whether to build static libraries... yes checking for ANSI C header files... (cached) yes checking execinfo.h usability... yes checking execinfo.h presence... yes checking for execinfo.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking if gcc supports -fvisibility=hidden... yes 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 tests/smscb/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-host && make make[1]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host' make all-recursive make[2]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host' Making all in include make[3]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include' Making all in osmocom make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom' Making all in vty make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/vty' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/vty' Making all in codec make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/codec' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/codec' Making all in crypt make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/crypt' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom/crypt' make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom' make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocom' Making all in osmocore make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore' Making all in protocol make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore/protocol' make[5]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore' make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include/osmocore' make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include' make[3]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/include' Making all in src make[3]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src' Making all in . make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src' Making all in vty make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/vty' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/vty' Making all in codec make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/codec' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src/codec' make[3]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/src' Making all in tests make[3]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests' Making all in timer make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/timer' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/timer' Making all in sms make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/sms' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/sms' Making all in ussd make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/ussd' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/ussd' Making all in smscb make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/smscb' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/smscb' Making all in msgfile make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/msgfile' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests/msgfile' make[4]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests' make[3]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host/tests' make[3]: Entering directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host' make[3]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host' make[2]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host' make[1]: Leaving directory `/home/roy/osmocom-bb/src/shared/libosmocore/build-host' make -C host/layer23 make[1]: Entering directory `/home/roy/osmocom-bb/src/host/layer23' Making all in include make[2]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include' Making all in osmocom make[3]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom' Making all in bb make[4]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb' Making all in common make[5]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/common' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/common' Making all in misc make[5]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/misc' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/misc' Making all in mobile make[5]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/mobile' make[5]: Nothing to be done for `all'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb/mobile' make[5]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb' make[5]: Nothing to be done for `all-am'. make[5]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb' make[4]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom/bb' make[4]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom' make[4]: Nothing to be done for `all-am'. make[4]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom' make[3]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include/osmocom' make[3]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/include' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include' make[2]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/include' Making all in src make[2]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/src' Making all in common make[3]: Entering directory `/home/roy/osmocom-bb/src/host/layer23/src/common' CC l1ctl.o l1ctl.c:33: fatal error: osmocore/signal.h: No such file or directory compilation terminated. make[3]: *** [l1ctl.o] Error 1 make[3]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/src/common' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/roy/osmocom-bb/src/host/layer23' make: *** [host/layer23/layer23] Error 2

13 years, 1 month

1
0
0 0

AW: no reception, 3 bars on original firmware

by Andreas.Eversberg

hi calvin, > I am having trouble getting any signal at all. the signal is around -111 > dBm on every channel with the rf gain set on high. The original as harald said, it seems that your phone uses 850 and 1900mhz bands. the filters inside only pass these frequencies. the BTS' in europe use different frequencies than in the US. the current layer23 will only support 900mhz and 1800mhz bands so far. i didn't care about other bands, because i have no way to test it. i can add new bands to layer23. your mail gives me some motivation to implement this finally. the support of DCS and PCS in parallel is quite tricky. maybe i will finish this weekend and you may try that out. regards, andreas

13 years, 1 month

1
0
0 0

no reception, 3 bars on original firmware

by Calvin Balke

You don't have to answer this right now if you don't want to, it can wait. I have been working on this for a few months. I have never posted on this mailing list before, but I have read many of the other posts. Just so you know, I am currently 14 years old and I have autism(which is the reason why I am obsessed with computers and electronics). I am having trouble getting any signal at all. the signal is around -111 dBm on every channel with the rf gain set on high. The original firmware works fine with an at&t sim card and has 3 bars. The linux distro that I am running is backtrack 4. While trying to diagnose this, I tried mobile and layer23 on a known good channel from a nokia 3100 series phone in netmonitor mode. and in scanning mode on most of the branches that I compiled. I have looked on the wiki and google. I have also tried to figure out how parts of the source code work. I have even tried this on two different boards, the compal_e88 and compal_e86. Has anybody else had this problem? Where exactly is the antenna switch? That could be the problem, if it connects to the headset slot. I have a homemade t191 cable, that uploads the firmware just fine, but I am wondering about the LOST message after the dsp download. What does the LOST message mean? Thank you for your help, Calvin

13 years, 1 month

2
1
0 0

Re: how to decompile a linux kernel zImage

by burebista

I found another phone witch looks like it runs Android OS on a MT6516 processor, you can find it here http://www.voldltd.com/sdp/1100371/4/pd-5258987/7588204-2080998/H6_Android_…, it's a VOLD VD-H6. I send them an email but for now no response, I haven't found a ROM to look into it, but the manufacturer is "VOLD Company Limited" and on their website it says that is Android on MT6516, so they need to have the driver for it.

13 years, 1 month

1
0
0 0

MT6516 processor Android / Linux kernel driver

by burebista

I found another mobile witch run Android on a MT6516 processor, you can find it here http://www.voldltd.com/sdp/1100371/4/pd-5258987/7588204-2080998/H6_Android_…, it's a VOLD VD-H6, I'm still trying to get as much info from the Star A3000 Android ROM and from the datasheet. I hope that in the near future this processor will be supported by Linux/Android. For now you can find the A3000 kernel config file on the thread "Re: how to decompile a linux kernel zImage". Help is welcomed.

13 years, 1 month

2
1
0 0

MTK RF

by 麦田守望

can you help me what is the mtk RF chip MT6219 3 wire Control word ， what is it mean

13 years, 1 month

2
1
0 0

I wanna make sure why LOCATION UPDATE REQUEST is always faild

by zhengfanf

hello, when i run osmocom i meet a problem that LOCATION UPDATE REQUEST is always faild, the details are in the following: 1, my hardware environment: a Moto C118 mobile; a cheap RS232 com port to jack port data cable (unkown chip); a USB2 to RS232 converter using FTDI chip; i5 CPU with GIGABYTE motherbord running with Ubuntu 9.04; 2, i run the command osmocon, mobile, and telnet as below in seprate terminals in order. ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/layer1.compalram.bin ./mobile -i 127.0.0.1 telnet localhost 4247 en sim reader 1 3, after that osmocom is working, but things doesn't happed what i wish, LOCATION UPDATE REQUEST is always faild so that the phone can not make calls. -in command mobile running terminial i grubbed the following log: " <0001> gsm48_rr.c:2006 PAGING ignored, we are not camping. writing msgb to gsmtap fd: Connection refused <0001> gsm48_rr.c:694 timer T3126 has fired <000d> gsm48_rr.c:699 Requesting channel failed <0001> gsm48_rr.c:363 new state connection pending -> idle <0003> gsm322.c:3318 (ms 1) Event 'EVENT_RET_IDLE' for Cell selection in state 'C3 camped normally' <0003> gsm322.c:2889 Selecting frequency 22. after LOC.UPD. <0003> gsm322.c:251 Sync to ARFCN=22 rxlev=-56 (Sysinfo, ccch mode NON-COMB) <0003> gsm322.c:540 new state 'C3 camped normally' -> 'C3 camped normally' <0004> gsm48_mm.c:3695 (ms 1) Received 'RR_REL_IND' from RR in state wait for RR connection (location updating) <0004> gsm48_mm.c:2589 RR link released after loc. upd. <000d> gsm48_mm.c:2533 Location update failed <000d> gsm48_mm.c:2543 Try location update later <0004> gsm48_mm.c:2545 Loc. upd. failed, retry #0 <0004> gsm48_mm.c:391 starting T3211 (loc. upd. retry delay) with 15.0 seconds <0004> gsm48_mm.c:4083 (ms 1) Received 'MM_EVENT_CELL_SELECTED' event in state wait for RR connection (location updating) <0004> gsm48_mm.c:1055 We are in registered LAI as returning to MM IDLE <0004> gsm48_mm.c:892 new state wait for RR connection (location updating) -> MM IDLE, normal service <0003> gsm322.c:2433 Channel synched. (ARFCN=22, snr=13, BSIC=10) <0001> gsm322.c:2460 using DSC of 90 <0003> gsm48_rr.c:4548 Channel provides data. writing msgb to gsmtap fd: Connection refused writing msgb to gsmtap fd: Connection refused <0001> gsm48_rr.c:609 MON: f=22 lev=-52 snr= 0 ber= 62 LAI=460 00 11a5 ID=629a writing msgb to gsmtap fd: Connection refused <0001> gsm48_rr.c:2265 IMMEDIATE ASSIGNMENT: <0001> gsm48_rr.c:2286 (ta 1/553m ra 0x7f chan_nr 0x0e ARFCN 22 TS 6 SS 0 TSC 2) <0001> gsm48_rr.c:2291 Not for us, no request. " -it shows that LOCATION UPDATE REQUEST is faild and it will be retry, and use command "OsmocomBB# show ms" also can find that the mobile is trying hard to get location update successfully: " OsmocomBB# show ms MS '1' is up, MM connection active IMEI: 000000000000000 IMEISV: 0000000000000000 IMEI generation: fixed automatic network selection state: A1 trying RPLMN cell selection state: C3 camped normally radio ressource layer state: connection pending mobility management layer state: wait for RR connection (location updating) OsmocomBB# show ms MS '1' is up, service is normal IMEI: 000000000000000 IMEISV: 0000000000000000 IMEI generation: fixed automatic network selection state: A1 trying RPLMN cell selection state: C3 camped normally (ARFCN 22) radio ressource layer state: idle mobility management layer state: MM idle, normal service OsmocomBB# show ms MS '1' is up, service is normal IMEI: 000000000000000 IMEISV: 0000000000000000 IMEI generation: fixed automatic network selection state: A1 trying RPLMN cell selection state: C3 camped normally (ARFCN 22) radio ressource layer state: idle mobility management layer state: MM idle, normal service OsmocomBB# show ms MS '1' is up, MM connection active IMEI: 000000000000000 IMEISV: 0000000000000000 IMEI generation: fixed automatic network selection state: A1 trying RPLMN cell selection state: C3 camped normally radio ressource layer state: connection pending mobility management layer state: wait for RR connection (location updating) " -and in command osmocon terminal, i found the log may show the LOCATION UPDATE REQUEST faild reasons. " Received PROMPT1 from phone, responding with CMD read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): file_size=53948, hdr_len=4, dnload_len=53955 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/53955) handle_write(): 4096 bytes (8192/53955) handle_write(): 4096 bytes (12288/53955) handle_write(): 4096 bytes (16384/53955) handle_write(): 4096 bytes (20480/53955) handle_write(): 4096 bytes (24576/53955) handle_write(): 4096 bytes (28672/53955) handle_write(): 4096 bytes (32768/53955) handle_write(): 4096 bytes (36864/53955) handle_write(): 4096 bytes (40960/53955) handle_write(): 4096 bytes (45056/53955) handle_write(): 4096 bytes (49152/53955) handle_write(): 4096 bytes (53248/53955) handle_write(): 707 bytes (53955/53955) 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-757-gc4483bf-modified) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: 71c60b1d89021625 ====================================================================== REG_DPLL=0x2413 CNTL_ARM_CLK=0xf0a1 CNTL_CLK=0xff91 CNTL_RST=0xfff3 CNTL_ARM_DIV=0xfff9 ====================================================================== Power up simcard: 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 1634! " " SB2 (2663816:2): TOA= 26, Power= -60dBm, Angle= 132Hz => SB 0x003cf629: BSIC=10 fn=1331917(1004/15/ 1)=> DSP reports SB in bit that is 965199799 bits in the future?!? Synchronize_TDMA => DSP reports FB in bit that is 965199776 bits in the future?!? LOST 1908! nb_cmd(0) and rxnb.msg != NULLL1CTL_PARAM_REQ (ta=0, tx_power=5) L1CTL_RACH_REQ (ra=0x0a, offset=8 combined=0) L1CTL_PARAM_REQ (ta=0, tx_power=5) L1CTL_RACH_REQ (ra=0x0a, offset=236 combined=0) L1CTL_PARAM_REQ (ta=0, tx_power=5) L1CTL_RACH_REQ (ra=0x0d, offset=248 combined=0) L1CTL_PARAM_REQ (ta=0, tx_power=5) L1CTL_RACH_REQ (ra=0x06, offset=240 combined=0) L1CTL_PARAM_REQ (ta=0, tx_power=5) L1CTL_RACH_REQ (ra=0x04, offset=217 combined=0) L1CTL_DM_REL_REQL1CTL_RESET_REQ: FULL!L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=22, flags=0x7) Starting FCCH RecognitionEMPTY FB0 (1334018:5): TOA= 5040, Power= -57dBm, Angle= 2049Hz FB1 (1334028:8): TOA= 8755, Power= -57dBm, Angle= 223Hz fn_offset=1334026 (fn=1334028 + attempt=8 + ntdma = 6)m delay=8 (fn_offset=1334026 + 11 - fn=1334028 - 1 scheduling next FB/SB detection task with delay 8 =>FB @ FNR 1334026 fn_offset=1334026 qbits=4836 Synchronize_TDMA LOST 3717! SB1 (2668059:1): TOA= 27, Power= -59dBm, Angle= -9Hz => SB 0x0111f729: BSIC=10 fn=1334038(1006/ 4/31)=> DSP reports SB in bit that is 959894800 bits in the future?!? Synchronize_TDMA => DSP reports FB in bit that is 959894777 bits in the future?!? LOST 1909! nb_cmd(0) and rxnb.msg != NULLL1CTL_RESET_REQ: FULL!EMPTY L1CTL_FBSB_REQ (arfcn=22, flags=0x7) Starting FCCH RecognitionFB0 (1337271:8): TOA= 9312, Power= -56dBm, Angle=-3405Hz FB1 (1337282:9): TOA= 9999, Power= -56dBm, Angle= 5216Hz fn_offset=1337280 (fn=1337282 + attempt=9 + ntdma = 7)m delay=8 (fn_offset=1337280 + 11 - fn=1337282 - 1 scheduling next FB/SB detection task with delay 8 FB1 (1337302:11): TOA=12507, Power= -56dBm, Angle= 431Hz fn_offset=1337300 (fn=1337302 + attempt=11 + ntdma = 9)m delay=8 (fn_offset=1337300 + 11 - fn=1337302 - 1 scheduling next FB/SB detection task with delay 8 =>FB @ FNR 1337300 fn_offset=1337300 qbits=4844 Synchronize_TDMA LOST 3719! SB1 (2674604:1): TOA= 24, Power= -56dBm, Angle= 263Hz => SB 0x000af829: BSIC=10 fn=1337312(1008/ 2/41)=> DSP reports SB in bit that is 951713547 bits in the future?!? Synchronize_TDMA => DSP reports FB in bit that is 951713524 bits in the future?!? LOST 1905! nb_cmd(0) and rxnb.msg != NULLL1CTL_PARAM_REQ (ta=0, tx_power=5) L1CTL_RACH_REQ (ra=0x0f, offset=13 combined=0) L1CTL_PARAM_REQ (ta=0, tx_power=5) L1CTL_RACH_REQ (ra=0x0a, offset=233 combined=0) L1CTL_PARAM_REQ (ta=0, tx_power=5) L1CTL_RACH_REQ (ra=0x0a, offset=237 combined=0) L1CTL_PARAM_REQ (ta=0, tx_power=5) L1CTL_RACH_REQ (ra=0x0e, offset=240 combined=0) L1CTL_PARAM_REQ (ta=0, tx_power=5) L1CTL_RACH_REQ (ra=0x04, offset=241 combined=0) L1CTL_DM_REL_REQL1CTL_RESET_REQ: FULL!L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=22, flags=0x7) Starting FCCH RecognitionFB0 (1339424:4): TOA= 3792, Power= -53dBm, Angle= 2044Hz FB1 (1339434:8): TOA= 8755, Power= -52dBm, Angle= 295Hz fn_offset=1339432 (fn=1339434 + attempt=8 + ntdma = 6)m delay=8 (fn_offset=1339432 + 11 - fn=1339434 - 1 scheduling next FB/SB detection task with delay 8 =>FB @ FNR 1339432 fn_offset=1339432 qbits=4836 Synchronize_TDMA LOST 3717! " -i found the value of LOST is too big, and i tried to look for reasons in codes and found function "check_lost_frame()" below (in sync.c, lines 180 to 205). After read this code, i think it's delays of physical layer caused so so much LOST value. " /* Lost TDMA interrupt detection. This works by starting a hardware timer * that is clocked by the same master clock source (VCTCXO). We expect * 1875 timer ticks in the duration of a TDMA frame (5000 qbits / 1250 bits) */ /* Timer for detecting lost IRQ */ #define TIMER_TICKS_PER_TDMA 1875 #define TIMER_TICK_JITTER 1 static int last_timestamp; static inline void check_lost_frame(void) { int diff, timestamp = hwtimer_read(1); if (last_timestamp < timestamp) last_timestamp += (4*TIMER_TICKS_PER_TDMA); diff = last_timestamp - timestamp; /* allow for a bit of jitter */ if (diff < TIMER_TICKS_PER_TDMA - TIMER_TICK_JITTER || diff > TIMER_TICKS_PER_TDMA + TIMER_TICK_JITTER) printf("LOST %d!\n", diff); last_timestamp = timestamp; } " 4, here, i want some help to figure out whether physical delays caused big LOST value, and big LOST value caused LOCATION UPDATE REQUEST failed? if it's the problem of the physical layer, i want to make sure which part should be held responsible: -is that the cheap RS232 com port to jack port data cable caused the delays? -or is the USB2 to RS232 converter caused the delays? -or is that some bugs in layer1.compalram.bin caused the delays? i really want some experienced engineer to help me fix up the problem. Thanks! Best Regards! zheng 2011-03-09

13 years, 1 month

2
2
0 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel March 2011