-----Ursprüngliche Nachricht-----
Von: Stefan Bauer <stefan.bauer(a)cubewerk.de>
> I'm gonna try to move closer to the BTS tomorrow and collect some informations.
> If the quality stays poor, i can only attach an additional antenna to the phone.
Ok - here is the status - not quite surprising:
I moved closer to the cell. I got associated to the cell with much better quality. Then the channel switch was initiated by the software - without luck - logs attached:
http://www.plzk.de/mobile2.log
Any idea why the channel sync fails several times and even the fallback switch to the serving cell at the end?
I have doubts that it is an antenna/RX-issue. If i use the motorola with original firmware, i have no issues and can immediately start a phone-call.
Thank you in advance
Stefan
-----Ursprüngliche Nachricht-----
Von: Harald Welte <laforge(a)gnumonks.org>
> Are you sure your other phones are using O2 in GSM mode, not 3G? It
> could be that the other phones use 3G and thus have better coverage
> indication.
Hi Harald,
i have a pretty old nokia phone (6310) and it's only able to do GSM. That was used for my comparison.
> > Is it possible, that my provider does not like the random imei-feature
> > of osmocom?
>
> That might very well be, but is completley unrelated to a RF signal
> level as it is measured by your phone (which leads to the problem you
> are observing).
I'm gonna try to move closer to the BTS tomorrow and collect some informations. If the quality stays poor, i can only attach an additional antenna to the phone.
Thank you.
Stefan
-----Ursprüngliche Nachricht-----
Von: Holger Hans Peter Freyther <holger(a)freyther.de>
Gesendet: So 08.01.2012 17:03
Betreff: Re: random net disconn. - o2 germany - motorola c123 + c140
An: baseband-devel(a)lists.osmocom.org;
> On 01/08/2012 04:27 PM, Stefan Bauer wrote:
>
> >
> > PING. Nobody with an idea on my issue?
>
> What about you? Reading the log, do you see anything that looks weird? E.g.
> how likely is it that you simply have bad coverage of O2 for GSM in the area
> you are. What do you think about log entries like this?
Well, the coverage is perfect with my other cell phones at the exactly same position in my office.
Is it possible, that my provider does not like the random imei-feature of osmocom?
Is it best practise to use the real sim and not only extracting the key from original sim and fake it?
thank you
Stefan
-----Ursprüngliche Nachricht-----
> Hi Peter,
>
> please find the log-file of mobile here:
>
> http://www.plzk.de/mobile.log
PING. Nobody with an idea on my issue?
Regards
Stefan
-----Ursprüngliche Nachricht-----
Von: Peter Stuge <peter(a)stuge.se>
Gesendet: Sa 07.01.2012 00:31
Betreff: Re: random net disconn. - o2 germany - motorola c123 + c140
An: baseband-devel(a)lists.osmocom.org;
> Stefan Bauer wrote:
> > serious problems to keep in my operators network (o2 germany -
> > 262 07) longer than a few seconds.
>
> Can you crank up the logging to max and share the logs from a clean
> start of connection through disconnect?
Hi Peter,
please find the log-file of mobile here:
http://www.plzk.de/mobile.log
I hope this will bring some light into my problem.
Thank you in advance
Stefan
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
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
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
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
