Re: radio is not started

I just newcomer in osmocombb so I guess still miss various concept here. I tried to clarify (several question mark below) the stuff which I hope don't bore anyone here :). 1). sylvain branch: yes. I am using sylvain test branch and uncomment the TX part as written in SIM Reader wiki for firmware Makefile. 2). osmocon This is the utility to upload osmocombb firmware from laptop to my motorola c118 through usb cable. and here's the output I got, $ ./osmocon -p /dev/tty.usbserial -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin ... ... Received PROMPT1 from phone, responding with CMD read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=16864, hdr_len=4, dnload_len=16871 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(): 1023 bytes (1023/16871) handle_write(): 1024 bytes (2047/16871) handle_write(): 1024 bytes (3071/16871) handle_write(): 1024 bytes (4095/16871) handle_write(): 1024 bytes (5119/16871) handle_write(): 1024 bytes (6143/16871) handle_write(): 1024 bytes (7167/16871) handle_write(): 1024 bytes (8191/16871) handle_write(): 1024 bytes (9215/16871) handle_write(): 1024 bytes (10239/16871) handle_write(): 1024 bytes (11263/16871) handle_write(): 1024 bytes (12287/16871) handle_write(): 1024 bytes (13311/16871) handle_write(): 1024 bytes (14335/16871) handle_write(): 1024 bytes (15359/16871) handle_write(): 1024 bytes (16383/16871) handle_write(): 488 bytes (16871/16871) 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! Received DOWNLOAD ACK from phone, your code is running now! OSMOCOM Loader (revision osmocon_v0.0.0-757-gc4483bf-modified) ====================================================================== Running on compal_e88 in environment compalram Found flash of 2097152 bytes at 0x0 with 2 regions Is above output good enough to think that firmware is already downloaded by motorola c118 and the osmocombb firmware is running well there? 3). mobile application since layer1 stuff is handled by osmocombb firmware which run on the phone by now, mobile application will handle layer2 and layer3. I believe this mean, mobile application will perform logical process of GSM call flow for full location update to the operator network. But to do so, Ki information is needed. And this is where sim reader feature come into the play?to read the Ki (and also IMSI?) information from the operator simcard? here's the output I got, $ sudo ./mobile -i 127.0.0.1 Password: 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:3471 init PLMN process <0003> gsm322.c:3472 init Cell Selection process Mobile '1' initialized, please start phone now! VTY available on port 4247. At this point, the mobile application communicate to the osmocombb firmware through /tmp/osmocom_l2 socket, while also open VTY connection on port 4247 right? In other words, to communicate with mobile application which will send command to the firmware in my motorola c118 through /tmp/osmocom_l2, we can use telnet to localhost port 4247? 4) VTY communication $ telnet localhost 4247 Trying ::1... telnet: connect to address ::1: Connection refused Trying fe80::1... telnet: connect to address fe80::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Welcome to the OpenBSC Control interface OsmocomBB> en OsmocomBB# show subs Mobile Subscriber of MS '1': No SIM present. at this state, no sim present yet. and we can ask mobile communication to read the simcard using this command: OsmocomBB# sim read 1 after running this command, if I see from console where mobile application run earlier, it shows the output: ... ... <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) and if I put command from VTY to show information about subscriber saved inside my simcard, OsmocomBB# show subs 1 Mobile Subscriber of MS '1': IMSI: Status: U2_NOT_UPDATED IMSI detached LAI: invalid Access barred cells: no Access classes: At this point, I come into conclusion that the mobile application tried to read the simcard (this is shown by <000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)) but failed as it can't show what is the IMSI of my simcard?thus location update process will failed since information such as IMSI and Ki was failed to be retrieved? 5) Mobile application configuration I think the VTY shell is similar to router configuration, where it could load previous saved simcard configuration, or MS name to be used, etc. Thus modify the MS name won't change the situation as locup is still failed? Please Advise. Thanks. Regards, Rasyid On Jan 21, 2011, at 6:19 PM, Bogdan Alecu wrote: