baseband-devel

baseband-devel@lists.osmocom.org

2023 discussions

Linux + u-boot port to MT6235
by Marcin Mielczarczyk 07 Jan '12

07 Jan '12

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

13 37

random net disconn. - o2 germany - motorola c123 + c140
by Stefan Bauer 07 Jan '12

07 Jan '12

Dear developers and users, i would like to know the current status of osmocom-bb on the motorola c123 and c140. I have both phones available and serious problems to keep in my operators network (o2 germany - 262 07) longer than a few seconds. I'm using my real sim (sim reader) but the quality seems to be very poor with that kind of devices. Are there any known problems? With several other devices (non osmocom firmware) and the same sim i have no problems at the same location. thanks in advance Stefan

2 1

Newbie DSP Questions
by Avner Ezra 05 Jan '12

05 Jan '12

Hi I'm newbie in DSP and SDR, but I'm really interested in this matter and I want to learn. I have bunch of questions which has short answers, if you can please answer them in easy terms and words, so I can understand them well. I hope this thread will help a lot of other newbies to understand DSP stuff better. I have a Linux with every needed tools like osmocomm, gnuradio, openbts, kalibrate, uhd drivers, ... and USRP N210 hardware ready. Everything works normal and well. A) Sometimes when I scan a network bandwidth like GSM1800 using kalibrate, I see some channels like 820, 538, etc. When I re-scan, I cannot find them. Does this mean that kalibrate finds a channel when a mobile handset has a live conversation or sms send or receive in progress? or what? B) I want to wideband capture for example 125 ARFCN. It needs 25MHz bandwidth which USRP N210 can handle and stream it easily. Even AFAIK I can double this number and capture 250 ARFCN using single N210 (50MHz, in USRPN210 data sheet it says it's capable of streaming 50MHz wide signals). How can I wideband capture 125 ARFCNs? I tried to do it using: ./uhd_rx_cfile.py -f `arfcncalc -a 512 -b 1800 -d` --samp-rate=25000000 -N 200000000 -g 70 b1.cfile What I understood and decided to write such command above: B-1) arfcncalc calculates frequency of first GSM1800 channel (512 ARFCN) which is start point (in above command) B-2) Sampling Rate is the bandwidth I want to capture, in our case it's 25MHz means 125 ARFCN which each ARFCN has 200kHz bandwidth B-3) 200M samples will be received (-N parameter) B-4) Gain value is 70, means it will boost antennas to maximum power to receive signals, I think USRPN210 max. gain is 80 B-5) My decimation rate here using 25M sampling rate and USRP N210 which has 100MHz ADC, will be 4. So if I decided to read cfile I have to use 4 as decimation rate. Please explain and tell me if I'm correct or wrong about above statements. Does this will work and I'll have a 125 ARFCN from 512 to 637 ARFCNs captures into b1.cfile? If so why in http://gnuradio.org/doc/doxygen-3.4/classusrp__source__base.html#adf8529d74… documentation, it says set_rx_freq should set center of frequency, so for example if you want to capture from 512 to 637, you should set frequency to frequency of ARFCN 574? C) How can I seperate and process 200khz by 200khz channels in wideband captured file? Thank you so much for your time Your help and answers will solve problem of a lot of newbies like me. Best Wishes

4 4

phones are not working
by Akib Sayyed 04 Jan '12

04 Jan '12

hello guys i am facing problem with registering phone on network what i am using cellphone: motorola c139 cable : FDTI FT232RL cable given on ccc aug ++++++++++++++++++++++++++++++++++++++++ command used to load ./host/osmocon/osmocon -m c140xor -p /dev/ttyUSB0 -c ./target/firmware/board/compal_e86/layer1.highram.bin ./target/firmware/board/compal_e86/chainload.compalram.bin ++++++++++++++++++++++++++++++++++++++++ show ms 1 command o/p MS '1' is up, MM connection active IMEI: 000000000000000 IMEISV: 0000000000000000 IMEI generation: fixed automatic network selection state: A1 trying RPLMN MCC=404 MNC=90 (India, AirTel) cell selection state: connected mode 1 ARFCN=613(DCS) MCC=404 MNC=90 LAC=0x0c2f CELLID=0x0aa2 (India, AirTel) radio ressource layer state: connection pending mobility management layer state: wait for RR connection (location updating) ++++++++++++++++++++++++++++++++++++++++ other tools tried : celllog works fine ++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++ Other issue details getting error FTM_TOOL error what i am using cellphone: motorola c123 cable : FDTI FT232RL cable given on ccc aug ++++++++++++++++++++++++++++++++++++++++ command used to load ./host/osmocon/osmocon -m c123xor -p /dev/ttyUSB0 ./target/firmware/board/compal_e88/layer1.compalram.bin ++++++++++++++++++++++++++++++++++++++++ here is log of error from c123 root@akib-laptop:~/osmocom_org/osmocom-bb/src# ./host/osmocon/osmocon -m c123xor -p /dev/ttyUSB0 ./target/firmware/board/compal_e88/layer1.compalram.bin got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 04 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/layer1.compalram.bin): file_size=55840, hdr_len=4, dnload_len=55847 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/55847) handle_write(): 4096 bytes (8192/55847) handle_write(): 4096 bytes (12288/55847) handle_write(): 4096 bytes (16384/55847) handle_write(): 4096 bytes (20480/55847) handle_write(): 4096 bytes (24576/55847) handle_write(): 4096 bytes (28672/55847) handle_write(): 4096 bytes (32768/55847) handle_write(): 4096 bytes (36864/55847) handle_write(): 4096 bytes (40960/55847) handle_write(): 4096 bytes (45056/55847) handle_write(): 4096 bytes (49152/55847) handle_write(): 4096 bytes (53248/55847) handle_write(): 2599 bytes (55847/55847) handle_write(): finished got 1 bytes from modem, data looks like: 1b . got 1 bytes from modem, data looks like: f6 . got 1 bytes from modem, data looks like: 02 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 45 E got 1 bytes from modem, data looks like: 53 S got 1 bytes from modem, data looks like: 16 . Received DOWNLOAD NACK from phone, something went wrong :( got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r ^C +++++++++++++++++++++++ Note: phones are locked to perticular provider -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

1 0

[osmocom-bb] [PATCH] Update .gitignore file for libosmocore
by Paul Wise 03 Jan '12

03 Jan '12

--- src/shared/libosmocore/.gitignore | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/src/shared/libosmocore/.gitignore b/src/shared/libosmocore/.gitignore index c77c750..5e75539 100644 --- a/src/shared/libosmocore/.gitignore +++ b/src/shared/libosmocore/.gitignore @@ -50,3 +50,6 @@ doc/html.tar src/crc*gen.c include/osmocom/core/crc*gen.h + +build-host +build-target -- 1.7.7.3

2 4

R: GPRS decode tutorial
by Luca Bongiorni 02 Jan '12

02 Jan '12

Hi Dario, i suggest you to download the last Sylvain's burst_ind, because is improved of some features and patch it manually with Nohl's patch. Then you will be able to dump the bursts using ccch_scan, instead of layer23. Cheers, Luca > Can someone drive me to the right direction? P.S: http://comments.gmane.org/gmane.comp.mobile.osmocom.baseband.devel/1754

3 2

Re: Compling pb with Ubuntu 11.04 64 bits
by Holger Hans Peter Freyther 01 Jan '12

01 Jan '12

On 01/01/2012 03:34 PM, Eric Tyberghien wrote: > Hi all > Hi Gustav, it is your third mail (one private, two to the list) but it is sadly not much of a dialogue. There is nothing wrong with Ubuntu 11.10 (11.04...) but apparently you changed more than jut 11.10 -> 11.04. From the little information you provide one can see you at least changed the place where you keep the sourcecode. So please keep your environment stable because otherwise you wasted the time of the ones that were kind enough to respond. So the path to success: 1.) Think, try to understand what happens 2.) Provide context when you are writing an email, what do you do, why do you do this? what you think should happen 3.) include complete output.... In this specific case: Find where the sourcecode of msgb_free is (the answer will be msgb.c), find the msgb.o (compiled object file) that was compiled for ARM. Look if there is a msgb_free in it (objdump,nm..) or if there is something wrong with this file (ls, file, readelf). My guess is that you did something funny during compile and ended up with a zero byte msgb.o. cheers holger

1 0

Compling pb with Ubuntu 11.04 64 bits
by Eric Tyberghien 01 Jan '12

01 Jan '12

Hi all I'll upgrade a Ubuntu 11.04 64 bits to 11.10 and it seems something was wrong. Now I have reinstall an "old" Ubuntu 11.04 64 bits from scratch and the compile process is fairly better but I obtain this failure : apps/hello_world/main.o: In function `console_rx_cb': apps/hello_world/main.c:59: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `sercomm_alloc_msgb': ../../shared/libosmocore/include/osmocom/core/msgb.h:330: undefined reference to `msgb_alloc' comm/libcomm.a(sercomm.o): In function `sercomm_drv_rx_char': comm/sercomm.c:246: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `dispatch_rx_msg': comm/sercomm.c:227: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `sercomm_drv_pull': comm/sercomm.c:161: undefined reference to `msgb_dequeue' comm/sercomm.c:188: undefined reference to `msgb_free' comm/libcomm.a(sercomm.o): In function `sercomm_sendmsg': comm/sercomm.c:125: undefined reference to `msgb_enqueue' comm/libcomm.a(sercomm_cons.o): In function `msgb_alloc_headroom': ../../shared/libosmocore/include/osmocom/core/msgb.h:330: undefined reference to `msgb_alloc' make[1]: *** [board/compal_e88/hello_world.compalram.elf] error 1 make[1]: Leaving directory `/srv/osmocom-bb/src/target/firmware' make: *** [firmware] error 2 Any idea Regards

1 0

Re: Compiling failure with Ubuntu 11.10 64 bits
by Holger Hans Peter Freyther 01 Jan '12

01 Jan '12

On 01/01/2012 12:45 AM, Eric Tyberghien wrote: > Hi all > The config.log file is like that I think the relevant part is not in the log file. Put it somewhere and post a link, or preferable go through it yourself once more. Are you sure that autoconf/automake deal well with the encoding of your accents in the directories? thanks

1 0

Re: Compiling failure with Ubuntu 11.10 64 bits
by Peter Stuge 01 Jan '12

01 Jan '12

Eric Tyberghien wrote: > I'm using Ubuntu 11.10 64 bits and I try to compile osmocom-bb but > it fails due to the enable-linker-buid-id option not supported by > the ld linker How do you come to that conclusion? > make[1]: quittant le répertoire « > /home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-target » Please keep in mind to always export LANG=C LC_ALL=C when posting output, so that there are no translations from english which both make everything more difficult to understand and usually also are very very bad translations. Never send localized output unless asking on a local-only mailing list. > cd shared/libosmocore/build-host && ../configure Who runs this command? You or make? > checking whether the C compiler works... no > configure: error: in > `/home/erict/Téléchargements/osmocom-bb/src/shared/libosmocore/build-host': > configure: error: C compiler cannot create executables > See `config.log' for more details > make: *** [sharedroland(a)redhat.com> > /libosmocore/build-host/Makefile] Erreur 77 .. > $ ./configure configure -v --with-pkgversion=Ubuntu/Linaro 4.6.1-9ubuntu3 > --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs > --enable-languages=c,c++,fortran,objc,obj-c++,go --prefix=/usr > --program-suffix=-4.6 --enable-shared --disable-linker-build-id > --with-system-zlib --libexecdir=/usr/lib --without-included-gettext > --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 > --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu > --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin > --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic > --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu > --target=x86_64-linux-gnu Who is running the above and why? > configure:2839: checking for x86_64-linux-gnu-gcc > configure:2855: found /usr/bin/x86_64-linux-gnu-gcc So this is the compiler that would be used. > Thread model: posix > gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) > configure:3155: $? = 0 > configure:3144: x86_64-linux-gnu-gcc -V >&5 > x86_64-linux-gnu-gcc: error: unrecognized option '-V' > x86_64-linux-gnu-gcc: fatal error: no input files > compilation terminated. > configure:3155: $? = 4 > configure:3144: x86_64-linux-gnu-gcc -qversion >&5 > x86_64-linux-gnu-gcc: error: unrecognized option '-qversion' > x86_64-linux-gnu-gcc: fatal error: no input files > compilation terminated. > configure:3155: $? = 4 > configure:3175: checking whether the C compiler works > configure:3197: x86_64-linux-gnu-gcc conftest.c >&5 > /usr/local/bin/ld: unrecognized option '--build-id' > /usr/local/bin/ld: use the --help option for usage information > collect2: ld returned 1 exit status Find why /usr/bin/x86_64-linux-gnu-gcc invokes /usr/local/bin/ld. > Any idea ? I think you have simply created a broken build environment on your system. I have no idea how you did that, but you seem to just have a mess of toolchains. You need to clean that up and set up the neccessary system and target toolchains. Nothing more, nothing less. //Peter

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel