baseband-devel June 2011

baseband-devel@lists.osmocom.org

39 participants
51 discussions

by Andreas.Eversberg

can you send the full mobile output? (from start of application until it halts) > <0002> gsm322.c:3176 (ms 1) Event 'EVENT_SIM_INSERT' for automatic PLMN selection in state 'A0 null' > <000d> gsm322.c:1090 Start search of last registered PLMN (mcc=420 mnc=01 Saudi Arabia, Al Jawal) > <0002> gsm322.c:1094 Use RPLMN (mcc=420 mnc=01 Saudi Arabia, Al Jawal) > <0002> gsm322.c:530 new state 'A0 null' -> 'A1 trying RPLMN' > <0003> gsm322.c:3396 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in state 'C0 null' > <000d> gsm322.c:3007 Selecting network (mcc=420 mnc=01 Saudi Arabia, Al Jawal) > <0003> gsm322.c:3013 Start stored cell selection. > <0003> gsm322.c:559 new state 'C0 null' -> 'C2 stored cell selection' can you send me the your ~/.osmocom/bb/1.ba file? don't worry, it will only contain band allocations you have received so far. (rename it an see, if the problem still exists.)

13 years, 9 months

Re: mobile - making a call

by eisencah eisenach

Hello everyone. After some more digging turns out that removing the "Status 1: 90 00" from the firrmware the SIM response gets back to the upper layers. What I've also noticed is that when the SIM response wasn't getting to the mobile application a L1CTL_RESET was following. My question is : would this L1CTL_RESET have the effect of removing pending packets from the queue? Cause that would sort of explain why the delay introduced by the debug printing would influence the overall behaviour. Thanks, Mihai. --- On Sun, 5/15/11, eisencah eisenach <wbg_1000(a)yahoo.com> wrote: From: eisencah eisenach <wbg_1000(a)yahoo.com> Subject: Re: Fw: Re: mobile - making a call To: baseband-devel(a)lists.osmocom.org Date: Sunday, May 15, 2011, 5:52 PM Hi again. So after some digging I'm quite sure the ADPU response doesn't make it back into the upper layers. My question is , case the osmocon output contains some weird characters (see bellow), I should assume that at that point something went wrong with the serial link? Also is there some flag to compile the firmware such that the prints have no effect, as to offload the serial link? Thanks, Mihai. L1CTL_DATA_REQ (link_id=0x00) ul=00811fe0, ul->payload=00811fe4, data_ind=00811fe4, data_ind->data=00811fe4 l3h=00811fe4 SIM Request (7): a0 a4 00 00 02 6f 20 Status 2: 9F 0F SIM Request (5): a0 c0 00 00 0f Status 1: 90 00 SIM Request (14): a0 d6 00 00 09 ff 49 fd 1a 49 8f 70 00 01 Status 2: 90ï¿½ï¿½Qï¿½ï¿½L1CTL_PARAM_REQ (ta=1, tx_power=6) L1CTL_DATA_REQ (link_id=0x00) ul=00811fe0, ul->payload=00811fe4, data_ind=00811fe4, data_ind->data=00811fe4 l3h=00811fe4 L1CTL_DATA_REQ (link_id=0x00) ul=008123c4, ul->payload=008123c8, data_ind=008123c8, data_ind->data=008123c8 l3h=008123c8 --- On Sat, 5/7/11, Sylvain Munaut <246tnt(a)gmail.com> wrote: From: Sylvain Munaut <246tnt(a)gmail.com> Subject: Re: Fw: Re: mobile - making a call To: "eisencah eisenach" <wbg_1000(a)yahoo.com> Cc: baseband-devel(a)lists.osmocom.org Date: Saturday, May 7, 2011, 11:07 AM > So any ideea where to look for the answer to the UPDATE_BINARY message? No not really ... But there is a good reason the SIM driver is not in master ... it sucks at several level, including blocking behavior in interrupt context IIRC, so it's totally plausible your machine speed triggers some weird things. My advice would be to: - Cleanup the SIM driver - Bypass it in the code and try to access a real PCSC device locally rather than the built in SIM reader. Both are non-trivial of course. Cheers, Sylvain

13 years, 9 months

Fw: Re: Facing issues in using OSMOCOM

by Basem Ahmed

Also we are sure about the correct setup of ARM tool chain!! any help please about such issue. --- On Mon, 6/13/11, Basem Ahmed <eng_basemm(a)yahoo.com> wrote: From: Basem Ahmed <eng_basemm(a)yahoo.com> Subject: Re: Facing issues in using OSMOCOM To: "baseband-devel" <baseband-devel(a)lists.osmocom.org> Date: Monday, June 13, 2011, 11:41 AM Hi All GNUMonks, I am adding the log output here for reference as suggesed by Sylvain: Mobile Output: <000e> sim.c:949 command successfull <000e> sim.c:571 GET RESPONSE (len=19) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0) <000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:277 READ BINARY (offset=0 len=2) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0) <000e> sim.c:876 received APDU (len=2 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:151 sending result to callback function (type=0) <0004> subscriber.c:442 received ACC 0040 from SIM <0004> subscriber.c:556 Requesting SIM file 0x6f7b <000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000e> sim.c:241 SELECT (file=0x6f7b) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4) <000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13) <000e> sim.c:949 command successfull <000e> sim.c:571 GET RESPONSE (len=19) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0) <000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:277 READ BINARY (offset=0 len=12) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0) <000e> sim.c:876 received APDU (len=12 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:151 sending result to callback function (type=0) <0004> subscriber.c:518 (ms 1) Done reading SIM card (IMSI=420012300358346 Saudi Arabia, Al Jawal) <0004> subscriber.c:530 -> SIM card registered to 420 01 (Saudi Arabia, Al Jawal) <0004> gsm48_mm.c:4160 (ms 1) Received 'MMR_REG_REQ' event <0002> gsm322.c:3176 (ms 1) Event 'EVENT_SIM_INSERT' for automatic PLMN selection in state 'A0 null' <000d> gsm322.c:1090 Start search of last registered PLMN (mcc=420 mnc=01 Saudi Arabia, Al Jawal) <0002> gsm322.c:1094 Use RPLMN (mcc=420 mnc=01 Saudi Arabia, Al Jawal) <0002> gsm322.c:530 new state 'A0 null' -> 'A1 trying RPLMN' <0003> gsm322.c:3396 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in state 'C0 null' <000d> gsm322.c:3007 Selecting network (mcc=420 mnc=01 Saudi Arabia, Al Jawal) <0003> gsm322.c:3013 Start stored cell selection. <0003> gsm322.c:559 new state 'C0 null' -> 'C2 stored cell selection' Layer1: Output read_file(../../target/firmware/board/compal_e86/layer1.compalram.bin): file_size=54736, hdr_len=4, dnload_len=54743 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/54743) handle_write(): 4096 bytes (8192/54743) handle_write(): 4096 bytes (12288/54743) handle_write(): 4096 bytes (16384/54743) handle_write(): 4096 bytes (20480/54743) handle_write(): 4096 bytes (24576/54743) handle_write(): 4096 bytes (28672/54743) handle_write(): 4096 bytes (32768/54743) handle_write(): 4096 bytes (36864/54743) handle_write(): 4096 bytes (40960/54743) handle_write(): 4096 bytes (45056/54743) handle_write(): 4096 bytes (49152/54743) handle_write(): 4096 bytes (53248/54743) handle_write(): 1495 bytes (54743/54743) 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-g5bbea93-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 1174! 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 --- On Sun, 6/12/11, Basem Ahmed <eng_basemm(a)yahoo.com> wrote: From: Basem Ahmed <eng_basemm(a)yahoo.com> Subject: Re: Facing issues in using OSMOCOM To: "baseband-devel" <baseband-devel(a)lists.osmocom.org> Cc: "Sylvain Munaut" <246tnt(a)gmail.com> Date: Sunday, June 12, 2011, 9:55 PM Dear All, sorry for the previous mistake .Actually I am trying to run the Mobile project but i have some issues there .let me telling you all the procedures i made : 1-git clone the osmocom project2-make the checkout (git checkout origin/sylvain/testing )3-compiling the project(it works after some modification of TX transmitter enable)4-run the loader.compalram.bin(running perfectly)5-run the layer1.comalram.bin6-run telnet localhost and enabling the ms 17-run the mobile the project8-press the power on buttonsfor mobile application ===>it keeps running perfectly exactly as you did in the demo and its says it complete reading the SIM and giving my network name but it stop before checking the network signals at the line:selection network(mcc=420 aljawal )start stored cell selection<003> gsm322.c:559 new state 'C0 null' ->'C2 stored cell Selection' .for the layer1 application===>it downloading successfully and it keeps synchronized with mobile application keep SIM requesting till the line:sim request (5): a0 b0 00 00 0cStaus 1:90 00 Hoping to hear from you soon. regard,--- On Sun, 6/12/11, Sylvain Munaut <246tnt(a)gmail.com> wrote: From: Sylvain Munaut <246tnt(a)gmail.com> Subject: Re: Facing issues in using OSMOCOM To: "Basem Ahmed" <eng_basemm(a)yahoo.com>, "baseband-devel" <baseband-devel(a)lists.osmocom.org> Date: Sunday, June 12, 2011, 7:21 PM > How are you? Refer to below mail. I read the mailing list, please do not send to me directly. Only CC me (and CC, not a separate mail forward please) if you're posting a patch and you want me to review it and merge it. If I have an answer, I will answer ... (but in this case, from your description it seems like a 'mobile' problem which I virtually never use, so I may not have an answer at all) > I am able to download the loader.compalram.bin and layer1.compalram.bin and running the mobile project. I am also using the telnet for configuration. But it is stopping at following some state mentioned in attached file. Sorry, but if you attach .docx file, there is zero chance I'm gonna look at it. 1) .docx is a proprietary format, don't expect people can read it 2) Even if this was a open document ( .ods or so ), I don't use office suite at all. 3) A .txt attachement still requires me to download it and look at it ... 4) In general, to maximize your chance of getting an answer, you have to do your best to minimize the work to be done by the people you want to help you. In this particular case: - You properly included a description of your setup and up to where you got, that's great. - What's missing is a 'snippet' of the log with the 'state' it seems locked it. - Then at the end of the mail, cut and paste the complete logs (both from osmocon and from the mobile app). - If possible avoid HTML mail as well ... (don't take all this bad and/or personally, just trying to help you maximize your chance of getting the answers you're looking for). Cheers, Sylvain

13 years, 9 months

Re: Facing issues in using OSMOCOM

by Basem Ahmed

Hi All GNUMonks, I am adding the log output here for reference as suggesed by Sylvain: Mobile Output: <000e> sim.c:949 command successfull <000e> sim.c:571 GET RESPONSE (len=19) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0) <000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:277 READ BINARY (offset=0 len=2) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0) <000e> sim.c:876 received APDU (len=2 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:151 sending result to callback function (type=0) <0004> subscriber.c:442 received ACC 0040 from SIM <0004> subscriber.c:556 Requesting SIM file 0x6f7b <000e> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000e> sim.c:241 SELECT (file=0x6f7b) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xa4) <000e> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x13) <000e> sim.c:949 command successfull <000e> sim.c:571 GET RESPONSE (len=19) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xc0) <000e> sim.c:876 received APDU (len=19 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:277 READ BINARY (offset=0 len=12) <000e> sim.c:187 sending APDU (class 0xa0, ins 0xb0) <000e> sim.c:876 received APDU (len=12 sw1=0x90 sw2=0x00) <000e> sim.c:949 command successfull <000e> sim.c:151 sending result to callback function (type=0) <0004> subscriber.c:518 (ms 1) Done reading SIM card (IMSI=420012300358346 Saudi Arabia, Al Jawal) <0004> subscriber.c:530 -> SIM card registered to 420 01 (Saudi Arabia, Al Jawal) <0004> gsm48_mm.c:4160 (ms 1) Received 'MMR_REG_REQ' event <0002> gsm322.c:3176 (ms 1) Event 'EVENT_SIM_INSERT' for automatic PLMN selection in state 'A0 null' <000d> gsm322.c:1090 Start search of last registered PLMN (mcc=420 mnc=01 Saudi Arabia, Al Jawal) <0002> gsm322.c:1094 Use RPLMN (mcc=420 mnc=01 Saudi Arabia, Al Jawal) <0002> gsm322.c:530 new state 'A0 null' -> 'A1 trying RPLMN' <0003> gsm322.c:3396 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in state 'C0 null' <000d> gsm322.c:3007 Selecting network (mcc=420 mnc=01 Saudi Arabia, Al Jawal) <0003> gsm322.c:3013 Start stored cell selection. <0003> gsm322.c:559 new state 'C0 null' -> 'C2 stored cell selection' Layer1: Output read_file(../../target/firmware/board/compal_e86/layer1.compalram.bin): file_size=54736, hdr_len=4, dnload_len=54743 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/54743) handle_write(): 4096 bytes (8192/54743) handle_write(): 4096 bytes (12288/54743) handle_write(): 4096 bytes (16384/54743) handle_write(): 4096 bytes (20480/54743) handle_write(): 4096 bytes (24576/54743) handle_write(): 4096 bytes (28672/54743) handle_write(): 4096 bytes (32768/54743) handle_write(): 4096 bytes (36864/54743) handle_write(): 4096 bytes (40960/54743) handle_write(): 4096 bytes (45056/54743) handle_write(): 4096 bytes (49152/54743) handle_write(): 4096 bytes (53248/54743) handle_write(): 1495 bytes (54743/54743) 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-g5bbea93-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 1174! 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 --- On Sun, 6/12/11, Basem Ahmed <eng_basemm(a)yahoo.com> wrote: From: Basem Ahmed <eng_basemm(a)yahoo.com> Subject: Re: Facing issues in using OSMOCOM To: "baseband-devel" <baseband-devel(a)lists.osmocom.org> Cc: "Sylvain Munaut" <246tnt(a)gmail.com> Date: Sunday, June 12, 2011, 9:55 PM Dear All, sorry for the previous mistake .Actually I am trying to run the Mobile project but i have some issues there .let me telling you all the procedures i made : 1-git clone the osmocom project2-make the checkout (git checkout origin/sylvain/testing )3-compiling the project(it works after some modification of TX transmitter enable)4-run the loader.compalram.bin(running perfectly)5-run the layer1.comalram.bin6-run telnet localhost and enabling the ms 17-run the mobile the project8-press the power on buttonsfor mobile application ===>it keeps running perfectly exactly as you did in the demo and its says it complete reading the SIM and giving my network name but it stop before checking the network signals at the line:selection network(mcc=420 aljawal )start stored cell selection<003> gsm322.c:559 new state 'C0 null' ->'C2 stored cell Selection' .for the layer1 application===>it downloading successfully and it keeps synchronized with mobile application keep SIM requesting till the line:sim request (5): a0 b0 00 00 0cStaus 1:90 00 Hoping to hear from you soon. regard,--- On Sun, 6/12/11, Sylvain Munaut <246tnt(a)gmail.com> wrote: From: Sylvain Munaut <246tnt(a)gmail.com> Subject: Re: Facing issues in using OSMOCOM To: "Basem Ahmed" <eng_basemm(a)yahoo.com>, "baseband-devel" <baseband-devel(a)lists.osmocom.org> Date: Sunday, June 12, 2011, 7:21 PM > How are you? Refer to below mail. I read the mailing list, please do not send to me directly. Only CC me (and CC, not a separate mail forward please) if you're posting a patch and you want me to review it and merge it. If I have an answer, I will answer ... (but in this case, from your description it seems like a 'mobile' problem which I virtually never use, so I may not have an answer at all) > I am able to download the loader.compalram.bin and layer1.compalram.bin and running the mobile project. I am also using the telnet for configuration. But it is stopping at following some state mentioned in attached file. Sorry, but if you attach .docx file, there is zero chance I'm gonna look at it. 1) .docx is a proprietary format, don't expect people can read it 2) Even if this was a open document ( .ods or so ), I don't use office suite at all. 3) A .txt attachement still requires me to download it and look at it ... 4) In general, to maximize your chance of getting an answer, you have to do your best to minimize the work to be done by the people you want to help you. In this particular case: - You properly included a description of your setup and up to where you got, that's great. - What's missing is a 'snippet' of the log with the 'state' it seems locked it. - Then at the end of the mail, cut and paste the complete logs (both from osmocon and from the mobile app). - If possible avoid HTML mail as well ... (don't take all this bad and/or personally, just trying to help you maximize your chance of getting the answers you're looking for). Cheers, Sylvain

13 years, 9 months

Re: Facing issues in using OSMOCOM

by Sylvain Munaut

> How are you? Refer to below mail. I read the mailing list, please do not send to me directly. Only CC me (and CC, not a separate mail forward please) if you're posting a patch and you want me to review it and merge it. If I have an answer, I will answer ... (but in this case, from your description it seems like a 'mobile' problem which I virtually never use, so I may not have an answer at all) > I am able to download the loader.compalram.bin and layer1.compalram.bin and running the mobile project. I am also using the telnet for configuration. But it is stopping at following some state mentioned in attached file. Sorry, but if you attach .docx file, there is zero chance I'm gonna look at it. 1) .docx is a proprietary format, don't expect people can read it 2) Even if this was a open document ( .ods or so ), I don't use office suite at all. 3) A .txt attachement still requires me to download it and look at it ... 4) In general, to maximize your chance of getting an answer, you have to do your best to minimize the work to be done by the people you want to help you. In this particular case: - You properly included a description of your setup and up to where you got, that's great. - What's missing is a 'snippet' of the log with the 'state' it seems locked it. - Then at the end of the mail, cut and paste the complete logs (both from osmocon and from the mobile app). - If possible avoid HTML mail as well ... (don't take all this bad and/or personally, just trying to help you maximize your chance of getting the answers you're looking for). Cheers, Sylvain

13 years, 9 months

Facing issues in using OSMOCOM

by Basem Ahmed

Hi GNUGeeks, I am trying to use OSMOCOM project for calling purpose. I tried the current master and remotes/origin/sylvain/testing branch also. My Linux version is OpenSUSE 11.2 (2.6.31.5-0.1-default) and mobile model is C139. And we used the model c140xor in the loader osmocon loader command. I am able to download the loader.compalram.bin and layer1.compalram.bin and running the mobile project. I am also using the telnet for configuration. But it is stopping at following some state mentioned in attached file. Hoping to read soon from you guys. Regards,Basem

13 years, 9 months

Error while compiling the stack

by nagesh reddy

Hi, i am getting the below error when i try to compile the GSM stack sources. administrator@administrator-desktop:~/osmocom-bb/src$ make cd shared/libosmocore && autoreconf -i /bin/sh: autoreconf: not found make: *** [shared/libosmocore/configure] Error 127 can any one try to help me. regards, nagesh.

13 years, 9 months

Calypso JTAG

by Drasko DRASKOVIC

Hi all, did anyone succeeded on attaching to JTAG port of Calypso ? I was looking at the docs here : http://bb.osmocom.org/trac/wiki/MotorolaC123, especially this : http://bb.osmocom.org/trac/attachment/wiki/MotorolaC123/compal_testpads.png, so I was wondering if someone has used JTAG, specifficaly with OpenOCD or UrJTAG ? I am planning to do some work on NuttX port, and I think that JTAG debugging would be very convenient for this kind of low level task. Also, I think that JTAG RAM flashing should be faster than current Osmocon RS232 method. Did anyone tried this and can osmocon be instructed that the code is already present in RAM, i.e. JTAG uploaded ? Best regards, Drasko

13 years, 9 months

IP hacking..

by Marten Christophe

Hello List, Sorry for out of scope question. Can any one suggest me community or mailing list for IP sniffing IP network hacking or account hacking, I'm planning to join for ethical hacking courses. Kind Regards,

13 years, 9 months

Searching for a studendt WAS( ANN: osmo-pcap a PCAP Client and Server application)

by Holger Hans Peter Freyther

On 06/03/2011 04:32 PM, Holger Hans Peter Freyther wrote: Hi all, I would like to get more students involved and would be interested in acting as a mentor. For the below osmo-pcap codebase I have a set of bite sized tasks (of different size) and it would be great if we could get some students to pick some of these. The only requirement should be interest to learn to program in C, some self motivation (e.g. use your favorite search engine before asking) but besides that the skills are not that important. cheers holger > Hi, > > I wrote a very primitive client and server for PCAP. The osmo_pcap_client will > use libpcap to sniff on a local link, we have the usual VTY interface to > configure it, one can change the filter and the device at runtime. > > There is also a very simple server that authenticates clients based on the > remote address, that will write the pcap files to disk. The files will be > rotated based on time and size, but also when the Link Header of a client is > changing. The traffic is not encrypted yet but that is on the todolist. > > The code can be found in our git repository[1]. > > holger > > [1] http://cgit.osmocom.org/cgit/osmo-pcap/ >

13 years, 9 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

baseband-devel June 2011