Osmocom-bb Making a call

Hello. *Can someone help me out at this point of the Osmocom-bb project [making a call].... I am done with all the steps involved in the project. 1. i have added the /.osmocom/bb/mobile.cfg 2. i am in the branch sylvian/testing I used git checkout --track -b remotes/origin/sylvian/testing command to enter this branch. It worked right... Am i RIGHT here? 3. when i download the firmware layer 1 on the phone it worked pretty good. it says..* 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! battery_compal_e88_init: starting up OSMOCOM Layer 1 (revision osmocon_v0.0.0-1348-g083a2dc) ====================================================================== Device ID code: 0xb4fb Device Version code: 0x0000 ARM ID code: 0xfff3 cDSP ID code: 0x0128 Die ID code: f2d81c119e039be2 ====================================================================== 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 1161! BAT-ADC: 549 6 0 0 1023 349 328 204 Charger at 51 mV. Battery at 3753 mV. Charging at 0 mA. Battery capacity is 69%. Battery range is 3199..3999 mV. Battery full at 468 LSB .. full at 585 LSB Charging at 239 LSB (204 mA). BCICTL2=0x3ff battery-info.flags=0x00000000 bat_compal_e88_chg_state=0 * 4. when i launch the MOBILE application it says like* 000f> sim.c:1223 init SIM client <0006> gsm48_cc.c:63 init Call Control <0007> gsm480_ss.c:231 init SS <0017> gsm411_sms.c:63 init SMS <0001> gsm48_rr.c:5479 init Radio Ressource process <0005> gsm48_mm.c:1315 init Mobility Management process <0005> gsm48_mm.c:1037 Selecting PLMN SEARCH state, because no SIM. <0002> gsm322.c:5025 init PLMN process <0003> gsm322.c:5026 init Cell Selection process Mobile '1' initialized, please start phone now! VTY available on port 4247. <0005> subscriber.c:601 Requesting SIM file 0x2fe2 <000f> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000f> sim.c:697 go MF <000f> sim.c:241 SELECT (file=0x3f00) 000f> sim.c:949 command successfull <000f> sim.c:151 sending result to callback function (type=0) <0005> subscriber.c:360 received SMSP from SIM (sca=+49232********000) <0005> subscriber.c:561 (ms 1) Done reading SIM card (IMSI=26****************654 Germany, E-Plus) <0005> subscriber.c:573 -> SIM card registered to 262 03 (Germany, E-Plus) <0005> gsm48_mm.c:4379 (ms 1) Received 'MMR_REG_REQ' event <0002> gsm322.c:3806 (ms 1) Event 'EVENT_SIM_INSERT' for automatic PLMN selection in state 'A0 null' <000e> gsm322.c:1372 Start search of last registered PLMN (mcc=262 mnc=03 Germany, E-Plus) <0002> gsm322.c:1376 Use RPLMN (mcc=262 mnc=03 Germany, E-Plus) <0002> gsm322.c:800 new state 'A0 null' -> 'A1 trying RPLMN' <0003> gsm322.c:4037 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in state 'C0 null' <000e> gsm322.c:3619 Selecting PLMN (mcc=262 mnc=03 Germany, E-Plus) <0003> gsm322.c:3628 Start normal cell selection. <0003> gsm322.c:823 new state 'C0 null' -> 'C1 normal cell selection' <0003> gsm322.c:2791 Scanning power for all frequencies. * Here its starts to search for frequencies and cells..... and see what happens.... * <0003> gsm322.c:2852 Scanning frequencies. (0..0) <0003> gsm322.c:2913 Done with power scanning range. <0003> gsm322.c:2791 Scanning power for all frequencies. <0003> gsm322.c:2852 Scanning frequencies. (512(DCS)..512(DCS)) <0003> gsm322.c:2913 Done with power scanning range. <0003> gsm322.c:2791 Scanning power for all frequencies. <0003> gsm322.c:2852 Scanning frequencies. (975..975) <0003> gsm322.c:2913 Done with power scanning range. <0003> gsm322.c:2791 Scanning power for all frequencies. <0003> gsm322.c:2813 Found no frequency. This repeats all the TIME........ *I am able to login to the vty terminal and able to execute some instructions..... * enable show ms show subscriber etc* when I try to make a call..... see what happens* <0009> mnccms.c:570 Make call to 01747180018 <0009> mnccms.c:150 support TCH/H also <0009> mnccms.c:174 support full rate v2 <0009> mnccms.c:178 support full rate v1 <0009> mnccms.c:187 support half rate v1 <0006> transaction.c:76 ms 1 allocates transaction (proto 3 trans_id 255 callref 1 mem 0x8cf7370) <0006> gsm48_cc.c:243 new state NULL -> MM_CONNECTION_PEND <0006> gsm48_cc.c:507 Sending MMCC_EST_REQ <0005> gsm48_mm.c:3774 (ms 1) Received 'MMCC_EST_REQ' event in state MM idle <0005> gsm48_mm.c:3777 -> substate PLMN search <0005> gsm48_mm.c:3779 -> callref 1, transaction_id 255 <0005> gsm48_mm.c:3042 Init MM Connection, not in normal state. <0006> gsm48_cc.c:2161 (ms 1) Received 'MMCC_REL_IND' in CC state MM_CONNECTION_PEND <0006> gsm48_cc.c:196 (ms 1 ti ff) Sending 'MNCC_REL_IND' to MNCC. <0006> gsm48_cc.c:243 new state MM_CONNECTION_PEND -> NULL <0006> transaction.c:104 ms 1 frees transaction (mem 0x8cf7370) <0009> mnccms.c:372 Call has been released (cause 21) <0009> mnccms.c:71 (call 1) Call removed. 0003> gsm322.c:2889 Getting PM for ARFCN 858(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 859(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 860(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 861(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 862(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 863(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 864(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 865(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 866(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 867(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 868(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 869(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 870(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 871(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 872(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 873(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 874(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 875(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 876(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 877(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 878(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 879(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 880(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 881(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 882(DCS) twice. Overwriting the first! Please fix prim_pm.c <0003> gsm322.c:2889 Getting PM for ARFCN 883(DCS) twice I even find this sometimes................ can someone fix this for me.... where could be the error...... Looking forward for a helping hand..... Thank you.. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972… Sent from the baseband-devel mailing list archive at Nabble.com.