Motorola C119

Basem Ahmed eng_basemm at yahoo.com
Sun Sep 4 09:51:32 UTC 2011


Hi All,

When i tried C119 with T191 Cable with the following configuration  (Anything except c140xor and compal_e86): it did not give complete response with Acknowledging from the phone with response like this:

linux-d5zo:/home/basem/osmocom-bb/src/host/osmocon # ./osmocon -p /dev/ttyUSB0 -m c115 ../../target/firmware/board/compal_e88/layer1.compalram.bin 
got 2 bytes from modem, data looks like: 04 81  ..
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

The filesize is larger than 15kb, code on the magic address will be overwritten!
Use loader.bin and upload the application with osmoload instead!

read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): file_size=54104, hdr_len=4, dnload_len=54111
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/54111)
handle_write(): 4096 bytes (8192/54111)
handle_write(): 4096 bytes (12288/54111)
handle_write(): 4096 bytes (16384/54111)
handle_write(): 4096 bytes (20480/54111)
handle_write(): 4096 bytes (24576/54111)
handle_write(): 4096 bytes (28672/54111)
handle_write(): 4096 bytes (32768/54111)
handle_write(): 4096 bytes (36864/54111)
handle_write(): 4096 bytes (40960/54111)
handle_write(): 4096 bytes (45056/54111)
handle_write(): 4096 bytes (49152/54111)
handle_write(): 4096 bytes (53248/54111)
handle_write(): 863 bytes (54111/54111)
handle_write(): finished

But when i tried with " C140XOR and Compal_e86 " it gives me the complete response but only two errors which is the LCD writing is shifted up by one line and the phone did not registered to the network here is the following response :

  Why "show ms 1" is saying:

OsmocomBB# show ms 1
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 the mobile application gives the following :
 linux-d5zo:/home/basem/osmocom-bb/src/host/osmocon # ./osmocon -p /dev/ttyUSB0 -m c140xor ../../target/firmware/board/compal_e88/layer1.compalram.bin 
got 2 bytes from modem, data looks like: 04 81  ..
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

The filesize is larger than 15kb, code on the magic address will be overwritten!
Use loader.bin and upload the application with osmoload instead!

read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): file_size=54104, hdr_len=4, dnload_len=54111
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/54111)
handle_write(): 4096 bytes (8192/54111)
handle_write(): 4096 bytes (12288/54111)
handle_write(): 4096 bytes (16384/54111)
handle_write(): 4096 bytes (20480/54111)
handle_write(): 4096 bytes (24576/54111)
handle_write(): 4096 bytes (28672/54111)
handle_write(): 4096 bytes (32768/54111)
handle_write(): 4096 bytes (36864/54111)
handle_write(): 4096 bytes (40960/54111)
handle_write(): 4096 bytes (45056/54111)
handle_write(): 4096 bytes (49152/54111)
handle_write(): 4096 bytes (53248/54111)
handle_write(): 863 bytes (54111/54111)
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-906-g5589a6b-modified)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: e144263d880014fd
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
======================================================================
Power up simcard:
Assert DSP into Reset
Releasing DSP from Reset
Setting some dsp_api.ndb values
Setting API NDB parameters
DSP Download Status: 0x0001
DSP API Version: 0x0000 0x0000
Finishing download phase
DSP Download Status: 0x0002
DSP API Version: 0x3606 0x0000
LOST 1203!
SIM Request (7): a0 a4 00 00 02 3f 00 
Status 2: 9F 23
SIM Request (5): a0 c0 00 00 23 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 2f e2 
Status 2: 9F 13
SIM Request (5): a0 c0 00 00 13 
Status 1: 90 00
SIM Request (5): a0 b0 00 00 0a 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 7f 20 
Status 2: 9F 23
SIM Request (5): a0 c0 00 00 23 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 6f 07 
Status 2: 9F 13
SIM Request (5): a0 c0 00 00 13 
Status 1: 90 00
SIM Request (5): a0 b0 00 00 09 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 6f 7e 
Status 2: 9F 13
SIM Request (5): a0 c0 00 00 13 
Status 1: 90 00
SIM Request (5): a0 b0 00 00 0b 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 3f 00 
Status 2: 9F 23
SIM Request (5): a0 c0 00 00 23 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 7f 10 
Status 2: 9F 23
SIM Request (5): a0 c0 00 00 23 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 6f 40 
Status 2: 9F 13
SIM Request (5): a0 c0 00 00 13 
Status 1: 90 00
SIM Request (5): a0 b0 00 00 84 
Status 1: 94 08
SIM Request (7): a0 a4 00 00 02 3f 00 
Status 2: 9F 23
SIM Request (5): a0 c0 00 00 23 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 7f 20 
Status 2: 9F 23
SIM Request (5): a0 c0 00 00 23 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 6f 20 
Status 2: 9F 13
SIM Request (5): a0 c0 00 00 13 
Status 1: 90 00
SIM Request (5): a0 b0 00 00 09 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 6f 30 
Status 2: 9F 13
SIM Request (5): a0 c0 00 00 13 
Status 1: 90 00
SIM Request (5): a0 b0 00 00 3c 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 6f 31 
Status 2: 9F 13
SIM Request (5): a0 c0 00 00 13 
Status 1: 90 00
SIM Request (5): a0 b0 00 00 01 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 6f 46 
Status 2: 9F 13
SIM Request (5): a0 c0 00 00 13 
Status 1: 90 00
SIM Request (5): a0 b0 00 00 11 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 6f 78 
Status 2: 9F 13
SIM Request (5): a0 c0 00 00 13 
Status 1: 90 00
SIM Request (5): a0 b0 00 00 02 
Status 1: 90 00
SIM Request (7): a0 a4 00 00 02 6f 7b 
Status 2: 9F 13
SIM Request (5): a0 c0 00 00 13 
Status 1: 90 00
SIM Request (5): a0 b0 00 00 0c 
Status 1: 90 00
L1CTL_RESET_REQ: FULL!L1CTL_PM_REQ start=100 end=104
PM MEAS: ARFCN=100, 28   dBm at baseband, -109 dBm at RF
PM MEAS: ARFCN=100, 30   dBm at baseband, -107 dBm at RF
PM MEAS: ARFCN=101, 29   dBm at baseband, -108 dBm at RF
PM MEAS: ARFCN=102, 26   dBm at baseband, -112 dBm at RF
PM MEAS: ARFCN=103, 34   dBm at baseband, -104 dBm at RF
PM MEAS: ARFCN=104, 25   dBm at baseband, -112 dBm at RF
L1CTL_PM_REQ start=106 end=106
PM MEAS: ARFCN=106, 26   dBm at baseband, -111 dBm at RF
PM MEAS: ARFCN=106, 25   dBm at baseband, -112 dBm at RF
L1CTL_PM_REQ start=108 end=110
PM MEAS: ARFCN=108, 31   dBm at baseband, -106 dBm at RF
PM MEAS: ARFCN=108, 30   dBm at baseband, -107 dBm at RF
PM MEAS: ARFCN=109, 25   dBm at baseband, -112 dBm at RF
PM MEAS: ARFCN=110, 24   dBm at baseband, -113 dBm at RF
L1CTL_PM_REQ start=112 end=121
PM MEAS: ARFCN=112, 28   dBm at baseband, -109 dBm at RF
PM MEAS: ARFCN=112, 27   dBm at baseband, -110 dBm at RF
PM MEAS: ARFCN=113, 32   dBm at baseband, -105 dBm at RF
PM MEAS: ARFCN=114, 29   dBm at baseband, -108 dBm at RF
PM MEAS: ARFCN=115, 29   dBm at baseband, -108 dBm at RF
PM MEAS: ARFCN=116, 30   dBm at baseband, -107 dBm at RF
PM MEAS: ARFCN=117, 31   dBm at baseband, -106 dBm at RF
PM MEAS: ARFCN=118, 33   dBm at baseband, -104 dBm at RF
PM MEAS: ARFCN=119, 29   dBm at baseband, -108 dBm at RF
PM MEAS: ARFCN=120, 45   dBm at baseband, -92  dBm at RF
PM MEAS: ARFCN=121, 65   dBm at baseband, -72  dBm at RF
L1CTL_PM_REQ start=124 end=124
PM MEAS: ARFCN=124, 29   dBm at baseband, -108 dBm at RF
PM MEAS: ARFCN=124, 29   dBm at baseband, -108 dBm at RF
L1CTL_PM_REQ start=762 end=762
PM MEAS: ARFCN=762, 84   dBm at baseband, -54  dBm at RF
PM MEAS: ARFCN=762, 84   dBm at baseband, -53  dBm at RF
L1CTL_PM_REQ start=765 end=768
PM MEAS: ARFCN=765, 41   dBm at baseband, -96  dBm at RF
PM MEAS: ARFCN=765, 42   dBm at baseband, -95  dBm at RF
PM MEAS: ARFCN=766, 38   dBm at baseband, -99  dBm at RF
PM MEAS: ARFCN=767, 57   dBm at baseband, -80  dBm at RF
PM MEAS: ARFCN=768, 46   dBm at baseband, -91  dBm at RF
L1CTL_PM_REQ start=773 end=773
PM MEAS: ARFCN=773, 33   dBm at baseband, -105 dBm at RF
PM MEAS: ARFCN=773, 32   dBm at baseband, -105 dBm at RF
L1CTL_PM_REQ start=775 end=776
PM MEAS: ARFCN=775, 48   dBm at baseband, -89  dBm at RF
PM MEAS: ARFCN=775, 48   dBm at baseband, -89  dBm at RF
PM MEAS: ARFCN=776, 41   dBm at baseband, -96  dBm at RF
L1CTL_PM_REQ start=779 end=779
PM MEAS: ARFCN=779, 51   dBm at baseband, -86  dBm at RF
PM MEAS: ARFCN=779, 52   dBm at baseband, -85  dBm at RF
L1CTL_PM_REQ start=797 end=797
PM MEAS: ARFCN=797, 29   dBm at baseband, -108 dBm at RF
PM MEAS: ARFCN=797, 29   dBm at baseband, -108 dBm at RF
L1CTL_PM_REQ start=816 end=816
PM MEAS: ARFCN=816, 29   dBm at baseband, -108 dBm at RF
PM MEAS: ARFCN=816, 28   dBm at baseband, -109 dBm at RF
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=762, flags=0x7)
Starting FCCH RecognitionFB0 (1419:2): TOA= 1968, Power= -54dBm, Angle= 6913Hz
FB1 (1429:8): TOA= 9431, Power= -53dBm, Angle=  858Hz
  fn_offset=1428 (fn=1429 + attempt=8 + ntdma = 7)m  delay=9 (fn_offset=1428 + 11 - fn=1429 - 1
  scheduling next FB/SB detection task with delay 9
FB1 (1440:1): TOA=  683, Power= -53dBm, Angle=  165Hz
  fn_offset=1439 (fn=1440 + attempt=1 + ntdma = 0)m  delay=9 (fn_offset=1439 + 11 - fn=1440 - 1
  scheduling next FB/SB detection task with delay 9
=>FB @ FNR 1439 fn_offset=1439 qbits=2548
Synchronize_TDMA
LOST 2859!
SB1 (2891:1): TOA=   23, Power= -53dBm, Angle=  135Hz
=> SB 0x01e4ab7f: BSIC=31 fn=2492177(1879/25/11) qbits=0
Synchronize_TDMA
=>FB @ FNR 2890 fn_offset=2492177 qbits=4908
LOST 1903!
L1CTL_RESET_REQ: FULL!EMPTY
L1CTL_FBSB_REQ (arfcn=762, flags=0x7)
Starting FCCH RecognitionFB0 (2492554:3): TOA= 2544, Power= -54dBm, Angle= 6840Hz
L1CTL_RESET_REQ: FULL!L1CTL_FBSB_REQ (arfcn=762, flags=0x7)
Starting FCCH RecognitionFB0 (2492575:9): TOA= 9312, Power= -54dBm, Angle= 6777Hz
FB1 (2492585:8): TOA= 8755, Power= -53dBm, Angle= 1051Hz
  fn_offset=2492583 (fn=2492585 + attempt=8 + ntdma = 6)m  delay=8 (fn_offset=2492583 + 11 - fn=2492585 - 1
  scheduling next FB/SB detection task with delay 8
FB1 (2492605:11): TOA=12503, Power= -53dBm, Angle=  160Hz
  fn_offset=2492603 (fn=2492605 + attempt=11 + ntdma = 9)m  delay=8 (fn_offset=2492603 + 11 - fn=2492605 - 1
  scheduling next FB/SB detection task with delay 8
=> DSP reports FB in bit that is 1179237253 bits in the future?!?
Synchronize_TDMA
LOST 3714!
SB1 (2269562:1): TOA=   29, Power= -53dBm, Angle=    9Hz
=> SB 0x00d6ab7f: BSIC=31 fn=2492615(1879/21/41)=> DSP reports SB in bit that is 1458016052 bits in the future?!?
Synchronize_TDMA
=> DSP reports FB in bit that is 1458016029 bits in the future?!?
LOST 1912!

Thanks
  

________________________________
From: Alexander Huemer <alexander.huemer at xx.vu>
To: Basem Ahmed <eng_basemm at yahoo.com>
Cc: "baseband-devel at lists.osmocom.org" <baseband-devel at lists.osmocom.org>
Sent: Saturday, September 3, 2011 11:24 AM
Subject: Re: Motorola C119

Ahmed,

> it did not work
unfortunately has very little descriptive value.
Without knowing what happens nobody here can help you.
Start with pasting the error messages you get in an email (monospace
font, preferably text-only email) and by telling the ML which cable you
use.

Kind regards
-Alexander Huemer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20110904/b8665c70/attachment.html>


More information about the baseband-devel mailing list