- baseband-devel - lists.osmocom.org

sim reading hanged
by Akib Sayyed 02 Jun '13

02 Jun '13

while running mobile app. mobile app stuck giving following output <000f> sim.c:151 sending result to callback function (type=0) <0005> subscriber.c:379 received KEY from SIM <0005> subscriber.c:601 Requesting SIM file 0x6f30 <000f> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004) <000f> sim.c:241 SELECT (file=0x6f30) <000f> sim.c:187 sending APDU (class 0xa0, ins 0xa4) <000f> sim.c:876 received APDU (len=0 sw1=0x9f sw2=0x0f) <000f> sim.c:949 command successfull <000f> sim.c:571 GET RESPONSE (len=15) <000f> sim.c:187 sending APDU (class 0xa0, ins 0xc0) <000f> sim.c:876 received APDU (len=15 sw1=0x90 sw2=0x00) <000f> sim.c:949 command successfull <000f> sim.c:1065 selected file (len 249) <000f> sim.c:277 READ BINARY (offset=0 len=249) <000f> sim.c:187 sending APDU (class 0xa0, ins 0xb0) output of layer1 is SIM Response (17): 00 00 00 0b 6f 7e 04 00 11 ff 1b 21 02 00 00 90 00 LOST 1923! LOST 1827! SIM Request (5): a0 b0 00 00 0b SIM Response (13): ff ff ff ff ff ff ff 00 00 ff 01 90 00 SIM Request (7): a0 a4 00 00 02 6f 20 SIM Response (2): 9f 0f SIM Request (5): a0 c0 00 00 0f LOST 1878! LOST 1873! SIM Response (17): 00 00 00 09 6f 20 04 00 11 ff bb 01 02 00 00 90 00 SIM Request (5): a0 b0 00 00 09 SIM Response (11): ff ff ff ff ff ff ff ff 07 90 00 SIM Request (7): a0 a4 00 00 02 6f 30 SIM Response (2): 9f 0f SIM Request (5): a0 c0 00 00 0f LOST 1880! LOST 1870! SIM Response (17): 00 00 00 f9 6f 30 04 00 11 ff bb 21 02 00 00 90 00 SIM Request (5): a0 b0 00 00 f9 LOST 1880! LOST 1870! Please help me solve this issue -- Akib Sayyed Matrix-Shell akibsayyed(a)gmail.com akibsayyed(a)matrixshell.com Mob:- +91-966-514-2243

1 0

[PATCH] * Bugfix in Firmware: initialising variables
by Bhaskar11 28 May '13

28 May '13

2 3

Suggestions required to implement Calypso BTS with GPRS (minimal)
by Altaf 27 May '13

27 May '13

I have been successful in running the calypso BTS and registering phones to it. I have also examined the source code implemented. I am currently doing an Internship in Berlin and the company wants to demonstrate to it customers that 2G services are not secure. Basically we are designing a securtiy demonstrator. We want to do man-in-the-middle attacks with the existing open source s/w. So we thought a B100 USrp would be the need of the hour. But I am really interested working with the calypso phones because I am comfortable with the source code and have already worked on it. I want to try (do) implementing the GPRS functionality to this calypso BTS. Since the work is mostly involved at Layer1 or lets say transceiver. I tried running OpenBTS-gprs version and resulted with some info. The mframe_sched in the trx doesnt contain info about the how to handle packet channels or the multiframes do not have the Packet channels. So when the BTS assigns (on CCCH) a dedicated channel and the calypso phone fails to receive uplink or doesnt provide a way for the phone to access the BTS. I understand the working of trx and want to add this GPRS functionality to trx. I am aiming to implement minimal GPRS functionality. I have also seen how OpenBTS-gprs has triggers this packet channel or the way multiframes handle PDCH, PTCH.. By observing them I can get some idea. In this regard I request from you few suggestions such as where I have to work more and what are the challenges I will face. your suggestions are valuable to me. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Suggestions-required-to-implemen… Sent from the baseband-devel mailing list archive at Nabble.com.

1 0

Re: flashing problem fixed
by Bhaskar11 23 May '13

23 May '13

The two patches I have posted (separately) relating to "msgb_pull" use in Osmocom and firmware are required to fix the flashing problem! With these patches, I am able to use all the flash functions now. I still need to load the file "loader.e88loader.bin" which does not appear in my compile, as mentioned in a separate email. I bricked a phone by aborting the flashing at that stage! :-( Any advice on this will be appreciated. B. On Thu, May 23, 2013 at 5:51 PM, Akib Sayyed <akibsayyed(a)gmail.com> wrote: > bhaskar > > Have you solved issue with flashing. > > > On Thu, May 23, 2013 at 4:44 PM, Bhaskar11 <niceguy108(a)gmail.com> wrote: > >> Patched in format according to guidelines. >> >> B. >> >> > > > -- > Akib Sayyed > Matrix-Shell > akibsayyed(a)gmail.com > akibsayyed(a)matrixshell.com > Mob:- +91-966-514-2243 > >

1 0

Patch by email
by Bhaskar11 23 May '13

23 May '13

I have some problem sending patches by "git send-email" since I am working in a Windows system. My next email is an experimental workaround. Please let me know if it works ok. B.

1 0

PATCH: Bugfix in Firmware loader main.c: Assigning correct value to data pointer
by Bhaskar11 23 May '13

23 May '13

Patched in format according to guidelines. B.

2 1

[PATCH] Bugfix in Firmware primfbsb.c "return" with a value in function returning void
by Bhaskar11 23 May '13

23 May '13

1 0

[PATCH] * Bugfix in firmware trf5151.c: Setting correct mask for ARFCN value
by Bhaskar11 23 May '13

23 May '13

1 0

Some Patch files
by Bhaskar11 23 May '13

23 May '13

Here are some bug fix and corrections patches. This is my first attempt, so please forgive errors and let me know if there is any problem. B.

4 5

Re: bad crc in osmoload [SOLVED!] (updated patch)
by Bhaskar11 23 May '13

23 May '13

Here is a better Patch more consistent with rest of OsmocomBB coding style and more elegant. Please ignore previous patch offered (which works also but is relatively kludgy). B. On Wed, May 22, 2013 at 10:57 PM, Bhaskar11 <niceguy108(a)gmail.com> wrote: > Solved the "bad crc" problem in Osmoload. > > The bug was inadvertently introduced in osmoload.c in update SHA > ID 6ce46e7a86f4de0b1eef9c641ef6cfb49f1255cd on 9.9..2012 when msgb_get() > was replaced by msgb_pull() as part of a large scale change. Looks like no > one else had tried a "osmoload memdump" since then. > > Am enclosing patch to fix this bug. > > B. > > > > On Tue, May 14, 2013 at 5:26 PM, Bhaskar11 <niceguy108(a)gmail.com> wrote: > >> Hi all, >> >> I'm trying to flash RSSI app to my C118 following instructions on >> http://bb.osmocom.org/trac/wiki/flashing. >> >> First step Osmocon with loader works fine. >> >> Second step with "osmoload memdump 0x000000 0x2000 compal_loader.bin" >> gives the following output: >> >> Dumping 8192 bytes of memory at 0x0 to file compal_loader.bin >> >> bad crc 4190 (not 0000) at offset 0x00000000 >> bad crc f041 (not b209) at offset 0x000000f0 >> bad crc f041 (not 79d3) at offset 0x000001e0 >> ... >> bad crc f041 (not fe61) at offset 0x00001e00 >> bad crc 8257 (not 4cd6) at offset 0x00001ef0 >> bad crc a401 (not 0000) at offset 0x00001fe0done. >> >> Would appreciate any guidance on what I can do to set this right. >> >> A general question: >> If I flash RSSI app succesfully, can I later restore the original C118 >> code and use the cell as before? (assuming I have saved the full memory >> dump to disk!) Or is that gone for good? >> >> Thanks for your guidance. >> >> B. >> >> >> >

2 1