help me i have motorola c123

adel b8.adel at gmail.com
Mon Jun 20 09:47:42 UTC 2011


hello 
i have Motorola c123 The following are my steps:
1-
$ cd osmocom-bb
$ git checkout -b testing remotes/origin/sylvain/testing
fatal: git checkout: branch testing already exists
2-
~/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123xor
../../target/firmware/board/compal_e88/layer1.compalram.bin
got 2 bytes from modem, data looks like: 2f 00  /.
got 5 bytes from modem, data looks like: 1b f6 02 00 41  ....A
got 1 bytes from modem, data looks like: 01  .
got 1 bytes from modem, data looks like: 40  @
Received PROMPT1 from phone, responding with CMD
read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin):
file_size=51320, hdr_len=4, dnload_len=51327
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/51327)
handle_write(): 4096 bytes (8192/51327)
handle_write(): 4096 bytes (12288/51327)
handle_write(): 4096 bytes (16384/51327)
handle_write(): 4096 bytes (20480/51327)
handle_write(): 4096 bytes (24576/51327)
handle_write(): 4096 bytes (28672/51327)
handle_write(): 4096 bytes (32768/51327)
handle_write(): 4096 bytes (36864/51327)
handle_write(): 4096 bytes (40960/51327)
handle_write(): 4096 bytes (45056/51327)
handle_write(): 4096 bytes (49152/51327)
handle_write(): 2175 bytes (51327/51327)
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-786-g937023b)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: df0d1621a400d808
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
======================================================================


THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!!
Assert DSP into Reset
Releasing DSP from Reset
Setting some dsp_api.ndb values
Setting API NDB parameters
DSP Download Status: 0x0001
DSP API Version: 0x0000 0x0000
Finishing download phase
DSP Download Status: 0x0002
DSP API Version: 0x3606 0x0000
LOST 1968!

3- 
~/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.

<000e> sim.c:1206 init SIM client
<0005> gsm48_cc.c:61 init Call Control
<0001> gsm48_rr.c:4944 init Radio Ressource process
<0004> gsm48_mm.c:1220 init Mobility Management process
<0004> gsm48_mm.c:971 Selecting PLMN SEARCH state, because no SIM.
<0002> gsm322.c:3472 init PLMN process
<0003> gsm322.c:3473 init Cell Selection process
Mobile '1' initialized, please start phone now!
VTY available on port 4247.
<0004> subscriber.c:556 Requesting SIM file 0x2fe2
<000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)
<000e> sim.c:697 go MF
<000e> sim.c:241 SELECT (file=0x3f00)
<000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4)

I wait and wait and nothing happens to keep as is?
What is the solution to this problem?
I hope someone can help me as soon as



--
View this message in context: http://baseband-devel.722152.n3.nabble.com/help-me-i-have-motorola-c123-tp3085529p3085529.html
Sent from the baseband-devel mailing list archive at Nabble.com.




More information about the baseband-devel mailing list