From kun.guan at gmail.com Mon Jul 18 12:41:50 2011 From: kun.guan at gmail.com (goodgod) Date: Mon, 18 Jul 2011 05:41:50 -0700 (PDT) Subject: Motorola C116 experiment In-Reply-To: <4D66105B.9000803@ac.nl.eu.org> References: <4D66105B.9000803@ac.nl.eu.org> Message-ID: <1310992910301-3179033.post@n3.nabble.com> I face the same problem on my c118, thanks4u information help me quick fix it. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Motorola-C116-experiment-tp2564037p3179033.html Sent from the baseband-devel mailing list archive at Nabble.com. From josephli1029 at hotmail.com Wed Jul 13 02:48:36 2011 From: josephli1029 at hotmail.com (josephli) Date: Tue, 12 Jul 2011 19:48:36 -0700 (PDT) Subject: Help me I have a difficult problem In-Reply-To: <1299102636623-2620895.post@n3.nabble.com> References: <1299003672779-2605211.post@n3.nabble.com> <1299006015.6744.21.camel@chakrita> <1299035377327-2608520.post@n3.nabble.com> <4D6DF83E.4050201@ijskes.org> <1299102636623-2620895.post@n3.nabble.com> Message-ID: <1310525316523-3164590.post@n3.nabble.com> Does Sim IJskes method work? I tried that, but it still shown Failed to parse the config file. Could you tell me how do you fix it? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Help-me-I-have-a-difficult-problem-tp2605211p3164590.html Sent from the baseband-devel mailing list archive at Nabble.com. From issertiv at gmail.com Fri Jul 1 14:51:40 2011 From: issertiv at gmail.com (Raz Sharif) Date: Fri, 1 Jul 2011 15:51:40 +0100 Subject: Please advice - C115 FMTOOL - Ramloader Aborted Message-ID: Dear Folks, After much deliberation and waiting I finally rxed a C115 and the T1 Cable USB. I am running Backtrack 5 and have compiled the Osmocomm bundles and all executable seem to be present. When i plug om the Jack cable and press the power switch i get this :- ~/osmocom-bb/osmocom-bb/src/host/osmocon# ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/layer1.compalram.bin got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 2f 00 /. got 4 bytes from modem, data looks like: 1b f6 02 00 .... got 1 bytes from modem, data looks like: 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 read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): file_size=48808, hdr_len=4, dnload_len=48815 got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . Have have tried with Xor and without. What am I missing folks - please advice as have been at this a while now with same results. Thanks in advance. Raz -------------- next part -------------- An HTML attachment was scrubbed... URL: From screaming-pain at libero.it Fri Jul 1 15:45:49 2011 From: screaming-pain at libero.it (screaming-pain) Date: Fri, 1 Jul 2011 08:45:49 -0700 (PDT) Subject: Please advice - C115 FMTOOL - Ramloader Aborted In-Reply-To: References: Message-ID: <1309535149953-3129757.post@n3.nabble.com> Hi Raz, I have a c115 as well and I use the option -i 10 to load layer1. Anyway, with one of my cables I had problems at the beginning, until I realized that the plastic around the jack was impeding the jack from being properly plugged in. I cut it off and now it works. regards, Loretta -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Please-advice-C115-FMTOOL-Ramloader-Aborted-tp3129690p3129757.html Sent from the baseband-devel mailing list archive at Nabble.com. From steve at steve-m.de Fri Jul 1 15:55:56 2011 From: steve at steve-m.de (Steve Markgraf) Date: Fri, 01 Jul 2011 17:55:56 +0200 Subject: Please advice - C115 FMTOOL - Ramloader Aborted In-Reply-To: <1309535149953-3129757.post@n3.nabble.com> References: <1309535149953-3129757.post@n3.nabble.com> Message-ID: <4E0DEE0C.6000203@steve-m.de> Hi, On 01.07.2011 17:45, screaming-pain wrote: > I have a c115 as well and I use the option -i 10 to load layer1. This option doesn't have any influence on the Compal ramloader code, it is only used for setting the beacon interval in the Calypso/MTK romloader mode. Regards, Steve From steve at steve-m.de Fri Jul 1 15:52:02 2011 From: steve at steve-m.de (Steve Markgraf) Date: Fri, 01 Jul 2011 17:52:02 +0200 Subject: Please advice - C115 FMTOOL - Ramloader Aborted In-Reply-To: References: Message-ID: <4E0DED22.4060105@steve-m.de> Hi, On 01.07.2011 16:51, Raz Sharif wrote: > Have have tried with Xor and without. What am I missing folks - please > advice as have been at this a while now with same results. Maybe your machine is too slow, but you could try this: http://lists.osmocom.org/pipermail/baseband-devel/2011-February/001407.html I'm not sure if the patch still applies correctly though. If that doesn't work, here's another thing to try: http://lists.osmocom.org/pipermail/baseband-devel/2011-January/001053.html Regards, Steve From baseband at hackwerk.org Sat Jul 2 13:37:58 2011 From: baseband at hackwerk.org (Job) Date: Sat, 02 Jul 2011 15:37:58 +0200 Subject: Please advice - C115 FMTOOL - Ramloader Aborted In-Reply-To: <4E0DED22.4060105@steve-m.de> References: <4E0DED22.4060105@steve-m.de> Message-ID: <4E0F1F36.3010609@hackwerk.org> Hi, As I mailed before I also have a non working C115, but I have 3 working so I have something to compare. I suspect a hardware problem on my side, but I tried your tips > Maybe your machine is too slow, but you could try this: > http://lists.osmocom.org/pipermail/baseband-devel/2011-February/001407.html > I'm not sure if the patch still applies correctly though. No it doesn't but I compiled it and it did not help me. > If that doesn't work, here's another thing to try: > http://lists.osmocom.org/pipermail/baseband-devel/2011-January/001053.html Tried that too without result. I also confirmed by breaking the TX line to the phone (from the PC) that this error (FTMTOOL error) then also happens. So it can also be caused by a faulty cable, faulty connector or blown UART pin on the Calypso. Best regards, Job From steve at steve-m.de Sat Jul 2 13:49:10 2011 From: steve at steve-m.de (Steve Markgraf) Date: Sat, 02 Jul 2011 15:49:10 +0200 Subject: Please advice - C115 FMTOOL - Ramloader Aborted In-Reply-To: <4E0F1F36.3010609@hackwerk.org> References: <4E0DED22.4060105@steve-m.de> <4E0F1F36.3010609@hackwerk.org> Message-ID: <4E0F21D6.9030209@steve-m.de> Hi, On 02.07.2011 15:37, Job wrote: > As I mailed before I also have a non working C115, but I have 3 working > so I have something to compare. I suspect a hardware problem on my side, > but I tried your tips Yes, in your case I'd say the RX line of your third phone is somehow broken as well. Regards, Steve From issertiv at gmail.com Sat Jul 2 18:03:08 2011 From: issertiv at gmail.com (Raz Sharif) Date: Sat, 2 Jul 2011 19:03:08 +0100 Subject: Osmocom FMTool error Message-ID: Please could you assist me with some pointers, Good work btw. I am using a C115 with the T191 prolific USB cable. I can talk to the phone but cannot load the Layer1 Stack. I get : ./osmocon -p /dev/ttyUSB0 -m c123 ../../target/firmware/board/compal_e88/layer1.compalram.bin got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 2f / got 1 bytes from modem, data looks like: 00 . got 3 bytes from modem, data looks like: 1b f6 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: 01 . got 1 bytes from modem, data looks like: 40 @ Received PROMPT1 from phone, responding with CMD read_file(../../target/firmware/board/compal_e88/layer1.compalram.bin): file_size=51272, hdr_len=4, dnload_len=51279 got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . I press the switch once and it just jumps and does the same again and again and again. I read that this maybe a timing issue. I have installed on 64 Bit and 32 bit ubunto on a fast machine and the result is the same. Also i do not see Layer23 command during compile. Please advise me i am happy to do the debugging but any pointers would help me as i am willing to learn from this great work that has been done by you and the team. Thanks Raz -------------- next part -------------- An HTML attachment was scrubbed... URL: From issertiv at gmail.com Sun Jul 3 17:45:37 2011 From: issertiv at gmail.com (Raz Sharif) Date: Sun, 3 Jul 2011 18:45:37 +0100 Subject: Please can anyone advise me - FMTOOL Error and no further processing Message-ID: Dear all, I vae the C115 with a T1 USB to Serial cable with the Prolific chipset. When i run osmocon i get :- an its just sits there with no further processing. ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=17120, hdr_len=4, dnload_len=17127 read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): file_size=17120, hdr_len=4, dnload_len=17127 got 1 bytes from modem, data looks like: 00 . got 2 bytes from modem, data looks like: 2f 00 /. got 1 bytes from modem, data looks like: 1b . got 3 bytes from modem, data looks like: f6 02 00 ... got 1 bytes from modem, data looks like: 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 got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 00 . got 1 bytes from modem, data looks like: 00 . I think the cable is ok as when i run my fingers on the tip i get random Zeros so it appears to be talking to the cable. Also when i tried to run Mobile i get the :- even though i created the Mobile.cfg file in /etc/osmoco Failed to parse the config file: '/home/raz/.osmocom/bb/mobile.cfg' Please check or create config file using: 'touch /home/raz/.osmocom/bb/mobile.cfg' I have spent some hours researching the lists and trying various things to no avail but I want to continue until I resolve this issues and use this great stack to learn about the GSM network. Please advise. Great full for any help or pointers but this maybe a timing issue that is difficult to debug. Thanks Raz -------------- next part -------------- An HTML attachment was scrubbed... URL: From squalyl at gmail.com Sun Jul 3 18:26:36 2011 From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=) Date: Sun, 3 Jul 2011 20:26:36 +0200 Subject: Please can anyone advise me - FMTOOL Error and no further processing In-Reply-To: References: Message-ID: Hi, Didn't you post a similar message a few days ago? Sebastien On Sun, Jul 3, 2011 at 7:45 PM, Raz Sharif wrote: > Dear all, I vae the C115 with a T1 USB to Serial cable with the Prolific > chipset. > > When i run osmocon i get :- an its just sits there with no further > processing. > > ./osmocon -p /dev/ttyUSB0 -m c123xor > ../../target/firmware/board/compal_e88/loader.compalram.bin > read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): > file_size=17120, hdr_len=4, dnload_len=17127 > read_file(../../target/firmware/board/compal_e88/loader.compalram.bin): > file_size=17120, hdr_len=4, dnload_len=17127 > got 1 bytes from modem, data looks like: 00 . > got 2 bytes from modem, data looks like: 2f 00 /. > got 1 bytes from modem, data looks like: 1b . > got 3 bytes from modem, data looks like: f6 02 00 ... > got 1 bytes from modem, data looks like: 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 > got 1 bytes from modem, data looks like: 66 f > got 1 bytes from modem, data looks like: 74 t > got 1 bytes from modem, data looks like: 6d m > got 1 bytes from modem, data looks like: 74 t > got 1 bytes from modem, data looks like: 6f o > got 1 bytes from modem, data looks like: 6f o > got 1 bytes from modem, data looks like: 6c l > Received FTMTOOL from phone, ramloader has aborted > got 1 bytes from modem, data looks like: 65 e > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 6f o > got 1 bytes from modem, data looks like: 72 r > got 1 bytes from modem, data looks like: 00 . > got 1 bytes from modem, data looks like: 00 . > > I think the cable is ok as when i run my fingers on the tip i get random > Zeros so it appears to be talking to the cable. > > Also when i tried to run Mobile i get the :- even though i created the > Mobile.cfg file in /etc/osmoco > > Failed to parse the config file: '/home/raz/.osmocom/bb/mobile.cfg' > Please check or create config file using: 'touch > /home/raz/.osmocom/bb/mobile.cfg' > > I have spent some hours researching the lists and trying various things to > no avail but I want to continue until I resolve this issues and use this > great stack to learn about the GSM network. > > Please advise. > > Great full for any help or pointers but this maybe a timing issue that is > difficult to debug. > > Thanks > Raz > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From steve at steve-m.de Sun Jul 3 19:12:18 2011 From: steve at steve-m.de (Steve Markgraf) Date: Sun, 03 Jul 2011 21:12:18 +0200 Subject: Please can anyone advise me - FMTOOL Error and no further processing In-Reply-To: References: Message-ID: <4E10BF12.3060109@steve-m.de> On 03.07.2011 20:26, S?bastien Lorquet wrote: > Didn't you post a similar message a few days ago? Yes, he did. In fact, he posted an almost identical message three times. @Raz Sharif: Please refrain from doing that. I've given you a few pointers in my reply, and if that doesn't help, your cable seems to have some sort defect (timing issue, tx line defective..). Did you do a loopback-test by connecting RX to TX and see if sent data comes back? Regards, Steve From squalyl at gmail.com Sun Jul 3 19:45:01 2011 From: squalyl at gmail.com (=?UTF-8?Q?S=C3=A9bastien_Lorquet?=) Date: Sun, 3 Jul 2011 21:45:01 +0200 Subject: Fwd: Please can anyone advise me - FMTOOL Error and no further processing In-Reply-To: References: Message-ID: Please do not use reply in gmail, but reply to all instead. Otherwise you will only write to the message's author, Sebastien ---------- Forwarded message ---------- From: Raz Sharif Date: Sun, Jul 3, 2011 at 9:34 PM Subject: Re: Please can anyone advise me - FMTOOL Error and no further processing To: S?bastien Lorquet Sorry yes i did post this message before in an attempt to get some better insight in to the issues. The loopback test i shorted the inside and outermost pins and echo of characters appeared. I think cable is ok. Its a prolific usb to serial. I do not have a serial connector so cannot try the FTD cable option. All software looks ok but the Osmocon.just hangs and FMT tool error. So i am a little stuck to be honest. Sorry for sending this twice. Thanks Raz On 3 Jul 2011 19:29, "S?bastien Lorquet" wrote: -------------- next part -------------- An HTML attachment was scrubbed... URL: From issertiv at gmail.com Sun Jul 3 19:53:40 2011 From: issertiv at gmail.com (Raz Sharif) Date: Sun, 3 Jul 2011 20:53:40 +0100 Subject: Please can anyone advise me - FMTOOL Error and no further processing In-Reply-To: References: Message-ID: Apologies for that! In my haste for a resolution of the issue i selected Reply and not Reply All. I will continue to read up some more to eliminate the issues and currently I have no idea what is the problem. Cable T191 or C115 or a Timing issue with the Software that prevents me from getting past the first PROMPT! and FMT Tool Error. Thanks all. Raz On Sun, Jul 3, 2011 at 8:45 PM, S?bastien Lorquet wrote: > Please do not use reply in gmail, but reply to all instead. Otherwise you > will only write to the message's author, > > Sebastien > > > ---------- Forwarded message ---------- > From: Raz Sharif > Date: Sun, Jul 3, 2011 at 9:34 PM > Subject: Re: Please can anyone advise me - FMTOOL Error and no further > processing > To: S?bastien Lorquet > > > Sorry yes i did post this message before in an attempt to get some better > insight in to the issues. > > The loopback test i shorted the inside and outermost pins and echo of > characters appeared. I think cable is ok. Its a prolific usb to serial. > > I do not have a serial connector so cannot try the FTD cable option. > > All software looks ok but the Osmocon.just hangs and FMT tool error. > So i am a little stuck to be honest. > Sorry for sending this twice. > > Thanks > Raz > On 3 Jul 2011 19:29, "S?bastien Lorquet" wrote: > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wbg_1000 at yahoo.com Mon Jul 4 04:55:38 2011 From: wbg_1000 at yahoo.com (eisencah eisenach) Date: Sun, 3 Jul 2011 21:55:38 -0700 (PDT) Subject: Please can anyone advise me - FMTOOL Error and no further processing In-Reply-To: Message-ID: <1309755338.27889.YahooMailClassic@web112115.mail.gq1.yahoo.com> Try shutting off the graphical interface of the OS and run the tools from the consoles. Cheers, Mihai. --- On Sun, 7/3/11, Raz Sharif wrote: From: Raz Sharif Subject: Re: Please can anyone advise me - FMTOOL Error and no further processing To: "OSMoCom Baseband Devel" Date: Sunday, July 3, 2011, 10:53 PM Apologies for that! In my haste for a resolution of the issue i selected Reply and not Reply All. I will continue to read up some more to eliminate the issues and currently I have no idea what is the problem. Cable T191 or C115 or a Timing issue with the Software that prevents me from getting past the first PROMPT! and FMT Tool Error. Thanks all. Raz On Sun, Jul 3, 2011 at 8:45 PM, S?bastien Lorquet wrote: Please do not use reply in gmail, but reply to all instead. Otherwise you will only write to the message's author, Sebastien ---------- Forwarded message ---------- From: Raz Sharif Date: Sun, Jul 3, 2011 at 9:34 PM Subject: Re: Please can anyone advise me - FMTOOL Error and no further processing To: S?bastien Lorquet Sorry yes i did post this message before in an attempt to get some better insight in to the issues. The loopback test i shorted the inside and outermost pins and echo of characters appeared. I think cable is ok. Its a prolific usb to serial. I do not have a serial connector so cannot try the FTD cable option. All software looks ok but the Osmocon.just hangs and FMT tool error. So i am a little stuck to be honest. Sorry for sending this twice. Thanks Raz On 3 Jul 2011 19:29, "S?bastien Lorquet" wrote: -------------- next part -------------- An HTML attachment was scrubbed... URL: From lokkju at gmail.com Mon Jul 4 05:09:33 2011 From: lokkju at gmail.com (Lokkju Brennr) Date: Sun, 3 Jul 2011 22:09:33 -0700 Subject: Please can anyone advise me - FMTOOL Error and no further processing In-Reply-To: <1309755338.27889.YahooMailClassic@web112115.mail.gq1.yahoo.com> References: <1309755338.27889.YahooMailClassic@web112115.mail.gq1.yahoo.com> Message-ID: You're not running in a VM, are you? What hardware is this on? Loki On Sun, Jul 3, 2011 at 9:55 PM, eisencah eisenach wrote: > Try shutting off the graphical interface of the OS and run the tools from > the consoles. > Cheers, > Mihai. > > > --- On *Sun, 7/3/11, Raz Sharif * wrote: > > > From: Raz Sharif > Subject: Re: Please can anyone advise me - FMTOOL Error and no further > processing > To: "OSMoCom Baseband Devel" > Date: Sunday, July 3, 2011, 10:53 PM > > > Apologies for that! > > In my haste for a resolution of the issue i selected Reply and not Reply > All. > > I will continue to read up some more to eliminate the issues and currently > I have no idea what is the problem. Cable T191 or C115 or a Timing issue > with the Software that prevents me from getting past the first PROMPT! and > FMT Tool Error. > > Thanks all. > > Raz > > > > > > On Sun, Jul 3, 2011 at 8:45 PM, S?bastien Lorquet > > wrote: > > Please do not use reply in gmail, but reply to all instead. Otherwise you > will only write to the message's author, > > Sebastien > > > ---------- Forwarded message ---------- > From: *Raz Sharif* > > > Date: Sun, Jul 3, 2011 at 9:34 PM > Subject: Re: Please can anyone advise me - FMTOOL Error and no further > processing > To: S?bastien Lorquet > > > > > Sorry yes i did post this message before in an attempt to get some better > insight in to the issues. > > The loopback test i shorted the inside and outermost pins and echo of > characters appeared. I think cable is ok. Its a prolific usb to serial. > > I do not have a serial connector so cannot try the FTD cable option. > > All software looks ok but the Osmocon.just hangs and FMT tool error. > So i am a little stuck to be honest. > Sorry for sending this twice. > > Thanks > Raz > On 3 Jul 2011 19:29, "S?bastien Lorquet" > > wrote: > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From issertiv at gmail.com Mon Jul 4 06:39:37 2011 From: issertiv at gmail.com (Raz Sharif) Date: Mon, 4 Jul 2011 07:39:37 +0100 Subject: Please can anyone advise me - FMTOOL Error and no further processing In-Reply-To: References: <1309755338.27889.YahooMailClassic@web112115.mail.gq1.yahoo.com> Message-ID: Thanks for the reply. No I am not using VM of any sort. straight Ubuntu workstation. latest release from their Website. ISO installed and OsmocommBB compiled. Using the testing branch of OsmocomBB. Hardware is Dell Optiplex dual core 1 TB HD and 6GB Ram. It is a pretty fast PC to be honest and works with most of the stuff i Use. Cable is a T191 USB to 2.5mm Cable prolific.2303 chipset. lsusb shows the cable as Prolific. Rubbing fingers on the tip of the cable shows some characters so it seem to work but I may be wrong. Phone is a C115 Motorola from Ebay it works fine with a SIM and is just another phone to all intents and purposes. So I was going to try the FTDI USB cable today with the USB-RS32 convertor which is a pain but i kind of guessed by eliminating that it then is the phone or the Software and given that many folks had Cables issues that was the way to go. Any Ideas from fellow Osmocommers out there ?? :) Thanks folks, Raz On Mon, Jul 4, 2011 at 6:09 AM, Lokkju Brennr wrote: > You're not running in a VM, are you? > What hardware is this on? > > Loki > > > On Sun, Jul 3, 2011 at 9:55 PM, eisencah eisenach wrote: > >> Try shutting off the graphical interface of the OS and run the tools from >> the consoles. >> Cheers, >> Mihai. >> >> >> --- On *Sun, 7/3/11, Raz Sharif * wrote: >> >> >> From: Raz Sharif >> Subject: Re: Please can anyone advise me - FMTOOL Error and no further >> processing >> To: "OSMoCom Baseband Devel" >> Date: Sunday, July 3, 2011, 10:53 PM >> >> >> Apologies for that! >> >> In my haste for a resolution of the issue i selected Reply and not Reply >> All. >> >> I will continue to read up some more to eliminate the issues and currently >> I have no idea what is the problem. Cable T191 or C115 or a Timing issue >> with the Software that prevents me from getting past the first PROMPT! and >> FMT Tool Error. >> >> Thanks all. >> >> Raz >> >> >> >> >> >> On Sun, Jul 3, 2011 at 8:45 PM, S?bastien Lorquet >> > wrote: >> >> Please do not use reply in gmail, but reply to all instead. Otherwise you >> will only write to the message's author, >> >> Sebastien >> >> >> ---------- Forwarded message ---------- >> From: *Raz Sharif* >> > >> Date: Sun, Jul 3, 2011 at 9:34 PM >> Subject: Re: Please can anyone advise me - FMTOOL Error and no further >> processing >> To: S?bastien Lorquet >> > >> >> >> Sorry yes i did post this message before in an attempt to get some better >> insight in to the issues. >> >> The loopback test i shorted the inside and outermost pins and echo of >> characters appeared. I think cable is ok. Its a prolific usb to serial. >> >> I do not have a serial connector so cannot try the FTD cable option. >> >> All software looks ok but the Osmocon.just hangs and FMT tool error. >> So i am a little stuck to be honest. >> Sorry for sending this twice. >> >> Thanks >> Raz >> On 3 Jul 2011 19:29, "S?bastien Lorquet" > >> wrote: >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lokkju at gmail.com Mon Jul 4 06:42:50 2011 From: lokkju at gmail.com (Lokkju Brennr) Date: Sun, 3 Jul 2011 23:42:50 -0700 Subject: Please can anyone advise me - FMTOOL Error and no further processing In-Reply-To: References: <1309755338.27889.YahooMailClassic@web112115.mail.gq1.yahoo.com> Message-ID: <6584099630504847845@unknownmsgid> What carrier was the phone for? Sometimes there is custom/odd firmware on them - for instance, it was very tricky getting my tracfone c139s working. Loki On Jul 3, 2011, at 11:39 PM, Raz Sharif wrote: Thanks for the reply. No I am not using VM of any sort. straight Ubuntu workstation. latest release from their Website. ISO installed and OsmocommBB compiled. Using the testing branch of OsmocomBB. Hardware is Dell Optiplex dual core 1 TB HD and 6GB Ram. It is a pretty fast PC to be honest and works with most of the stuff i Use. Cable is a T191 USB to 2.5mm Cable prolific.2303 chipset. lsusb shows the cable as Prolific. Rubbing fingers on the tip of the cable shows some characters so it seem to work but I may be wrong. Phone is a C115 Motorola from Ebay it works fine with a SIM and is just another phone to all intents and purposes. So I was going to try the FTDI USB cable today with the USB-RS32 convertor which is a pain but i kind of guessed by eliminating that it then is the phone or the Software and given that many folks had Cables issues that was the way to go. Any Ideas from fellow Osmocommers out there ?? :) Thanks folks, Raz On Mon, Jul 4, 2011 at 6:09 AM, Lokkju Brennr wrote: > You're not running in a VM, are you? > What hardware is this on? > > Loki > > > On Sun, Jul 3, 2011 at 9:55 PM, eisencah eisenach wrote: > >> Try shutting off the graphical interface of the OS and run the tools from >> the consoles. >> Cheers, >> Mihai. >> >> >> --- On *Sun, 7/3/11, Raz Sharif * wrote: >> >> >> From: Raz Sharif >> Subject: Re: Please can anyone advise me - FMTOOL Error and no further >> processing >> To: "OSMoCom Baseband Devel" >> Date: Sunday, July 3, 2011, 10:53 PM >> >> >> Apologies for that! >> >> In my haste for a resolution of the issue i selected Reply and not Reply >> All. >> >> I will continue to read up some more to eliminate the issues and currently >> I have no idea what is the problem. Cable T191 or C115 or a Timing issue >> with the Software that prevents me from getting past the first PROMPT! and >> FMT Tool Error. >> >> Thanks all. >> >> Raz >> >> >> >> >> >> On Sun, Jul 3, 2011 at 8:45 PM, S?bastien Lorquet >> > wrote: >> >> Please do not use reply in gmail, but reply to all instead. Otherwise you >> will only write to the message's author, >> >> Sebastien >> >> >> ---------- Forwarded message ---------- >> From: *Raz Sharif* >> > >> Date: Sun, Jul 3, 2011 at 9:34 PM >> Subject: Re: Please can anyone advise me - FMTOOL Error and no further >> processing >> To: S?bastien Lorquet >> > >> >> >> Sorry yes i did post this message before in an attempt to get some better >> insight in to the issues. >> >> The loopback test i shorted the inside and outermost pins and echo of >> characters appeared. I think cable is ok. Its a prolific usb to serial. >> >> I do not have a serial connector so cannot try the FTD cable option. >> >> All software looks ok but the Osmocon.just hangs and FMT tool error. >> So i am a little stuck to be honest. >> Sorry for sending this twice. >> >> Thanks >> Raz >> On 3 Jul 2011 19:29, "S?bastien Lorquet" > >> wrote: >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From issertiv at gmail.com Mon Jul 4 07:33:19 2011 From: issertiv at gmail.com (Raz Sharif) Date: Mon, 4 Jul 2011 08:33:19 +0100 Subject: Please can anyone advise me - FMTOOL Error and no further processing In-Reply-To: <6584099630504847845@unknownmsgid> References: <1309755338.27889.YahooMailClassic@web112115.mail.gq1.yahoo.com> <6584099630504847845@unknownmsgid> Message-ID: Well put my T-Mobile SIM in the C115 and it worked fine as a phone SMS etc. unlocked for all Networks I think. Thanks for the reply. Raz On Mon, Jul 4, 2011 at 7:42 AM, Lokkju Brennr wrote: > What carrier was the phone for? Sometimes there is custom/odd firmware on > them - for instance, it was very tricky getting my tracfone c139s working. > > Loki > > > On Jul 3, 2011, at 11:39 PM, Raz Sharif wrote: > > Thanks for the reply. No I am not using VM of any sort. straight Ubuntu > workstation. latest release from their Website. ISO installed and OsmocommBB > compiled. Using the testing branch of OsmocomBB. > > Hardware is Dell Optiplex dual core 1 TB HD and 6GB Ram. It is a pretty > fast PC to be honest and works with most of the stuff i Use. > > Cable is a T191 USB to 2.5mm Cable prolific.2303 chipset. > > lsusb shows the cable as Prolific. > > Rubbing fingers on the tip of the cable shows some characters so it seem to > work but I may be wrong. > > Phone is a C115 Motorola from Ebay it works fine with a SIM and is just > another phone to all intents and purposes. > > So I was going to try the FTDI USB cable today with the USB-RS32 convertor > which is a pain but i kind of guessed by eliminating that it then is the > phone or the Software and given that many folks had Cables issues that was > the way to go. > > Any Ideas from fellow Osmocommers out there ?? :) > > Thanks folks, > > Raz > > On Mon, Jul 4, 2011 at 6:09 AM, Lokkju Brennr < > lokkju at gmail.com> wrote: > >> You're not running in a VM, are you? >> What hardware is this on? >> >> Loki >> >> >> On Sun, Jul 3, 2011 at 9:55 PM, eisencah eisenach < >> wbg_1000 at yahoo.com> wrote: >> >>> Try shutting off the graphical interface of the OS and run the tools from >>> the consoles. >>> Cheers, >>> Mihai. >>> >>> >>> --- On *Sun, 7/3/11, Raz Sharif < issertiv at gmail.com >>> >* wrote: >>> >>> >>> From: Raz Sharif < issertiv at gmail.com> >>> Subject: Re: Please can anyone advise me - FMTOOL Error and no further >>> processing >>> To: "OSMoCom Baseband Devel" < >>> baseband-devel at lists.osmocom.org> >>> Date: Sunday, July 3, 2011, 10:53 PM >>> >>> >>> Apologies for that! >>> >>> In my haste for a resolution of the issue i selected Reply and not Reply >>> All. >>> >>> I will continue to read up some more to eliminate the issues and >>> currently I have no idea what is the problem. Cable T191 or C115 or a Timing >>> issue with the Software that prevents me from getting past the first PROMPT! >>> and FMT Tool Error. >>> >>> Thanks all. >>> >>> Raz >>> >>> >>> >>> >>> >>> On Sun, Jul 3, 2011 at 8:45 PM, S?bastien Lorquet < >>> squalyl at gmail.com> wrote: >>> >>> Please do not use reply in gmail, but reply to all instead. Otherwise you >>> will only write to the message's author, >>> >>> Sebastien >>> >>> >>> ---------- Forwarded message ---------- >>> From: *Raz Sharif* < >>> issertiv at gmail.com> >>> Date: Sun, Jul 3, 2011 at 9:34 PM >>> Subject: Re: Please can anyone advise me - FMTOOL Error and no further >>> processing >>> To: S?bastien Lorquet < >>> squalyl at gmail.com> >>> >>> >>> Sorry yes i did post this message before in an attempt to get some better >>> insight in to the issues. >>> >>> The loopback test i shorted the inside and outermost pins and echo of >>> characters appeared. I think cable is ok. Its a prolific usb to serial. >>> >>> I do not have a serial connector so cannot try the FTD cable option. >>> >>> All software looks ok but the Osmocon.just hangs and FMT tool error. >>> So i am a little stuck to be honest. >>> Sorry for sending this twice. >>> >>> Thanks >>> Raz >>> On 3 Jul 2011 19:29, "S?bastien Lorquet" < >>> squalyl at gmail.com> wrote: >>> >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wbg_1000 at yahoo.com Mon Jul 4 08:27:11 2011 From: wbg_1000 at yahoo.com (eisencah eisenach) Date: Mon, 4 Jul 2011 01:27:11 -0700 (PDT) Subject: osmocn question Message-ID: <1309768031.88097.YahooMailClassic@web112110.mail.gq1.yahoo.com> Hi everyone. One remark regarding osmocon : it seems to me that we're reading one byte at the time from the serial port once we're done with downloading code into RAM. That seems quite on overhead (specially on slow machines like mine). I believe we should modify that once dnload.expect_hdlc == 0 we can free up the entire buffer. Is that so or I'm missing something? Mihai. -------------- next part -------------- An HTML attachment was scrubbed... URL: From issertiv at gmail.com Mon Jul 4 15:27:39 2011 From: issertiv at gmail.com (Raz Sharif) Date: Mon, 4 Jul 2011 16:27:39 +0100 Subject: Osmocom Loading Issues - TTYUSB0 loopback Message-ID: Hi folks, further to my previous email i now ran : I simply pressed the Power Switch a few times but not power on. This is what is recorded. As you will recall i get the FMTool Error and aborted message and never see Prompt2. With no Osmocom programs running can someone please confirm that this output is correct or indeed suggests that the Phones Serial Line or other Firmware or Phone Hardware is causing this error please - would be grateful. Thanks Raz _________________________________________- cat < /dev/ttyUSB0 >| rs.txt 00000000 00 2e 00 1b f6 02 00 41 01 40 66 74 6d 74 6f 6f |.......A. at ftmtoo| 00000010 6c 65 72 72 6f 72 00 00 2f 00 1b f6 02 00 41 01 |lerror../.....A.| 00000020 40 66 74 6d 74 6f 6f 6c 65 72 72 6f 72 00 00 2f |@ftmtoolerror../| 00000030 00 1b f6 02 00 41 01 40 66 74 6d 74 6f 6f 6c 65 |.....A. at ftmtoole| 00000040 72 72 6f 72 00 00 2f 00 1b f6 02 00 41 01 40 66 |rror../.....A. at f| 00000050 74 6d 74 6f 6f 6c 00 00 00 00 00 00 00 00 00 00 |tmtool..........| 00000060 00 00 00 00 00 2f 00 1b f6 02 00 41 01 40 66 74 |...../.....A. at ft| 00000070 6d 74 6f 6f 6c 65 72 72 6f 72 00 |mtoolerror.| -------------- next part -------------- An HTML attachment was scrubbed... URL: From vplrt at yahoo.com Tue Jul 5 11:17:47 2011 From: vplrt at yahoo.com (Victor P) Date: Tue, 5 Jul 2011 04:17:47 -0700 (PDT) Subject: GPSD support Message-ID: <1309864667.55832.YahooMailClassic@web45814.mail.sp1.yahoo.com> Hello.I have been trying to use cell_log with bluetooth GPS. I used gpsd v 2.37 and v 2.95, but in both cases I had the error "Osmocom was compiled without gpsd support". Should I use another version of gpsd or mistake in compilation (any patch?)? thank you for helpWith best wishes,Victor -------------- next part -------------- An HTML attachment was scrubbed... URL: From dario.lombardo at libero.it Wed Jul 6 10:05:02 2011 From: dario.lombardo at libero.it (Dario Lombardo) Date: Wed, 6 Jul 2011 12:05:02 +0200 Subject: GPSD support In-Reply-To: <1309864667.55832.YahooMailClassic@web45814.mail.sp1.yahoo.com> References: <1309864667.55832.YahooMailClassic@web45814.mail.sp1.yahoo.com> Message-ID: Do you have gpsd devel package? You should check the line where autotools test the gpsd support. On Tue, Jul 5, 2011 at 1:17 PM, Victor P wrote: > Hello. > > I have been trying to use cell_log with bluetooth GPS. I used gpsd v 2.37 > and v 2.95, but in both cases I had the error "Osmocom was compiled without > gpsd support". Should I use another version of gpsd or mistake in > compilation (any patch?)? thank you for help > > With best wishes, > > Victor > -------------- next part -------------- An HTML attachment was scrubbed... URL: From issertiv at gmail.com Tue Jul 5 11:33:15 2011 From: issertiv at gmail.com (Raz Sharif) Date: Tue, 5 Jul 2011 12:33:15 +0100 Subject: C139 confirmation of operation from Users please. Message-ID: Hi Folks, I recently mailed the group to discuss issue with the C115 Phone and am now trying the C139. It appears to load and i get :- ./osmocon -p /dev/ttyUSB0 -m c140 -c ../../target/firmware/board/compal_e86/layer1.highram.bin ../../target/firmware/board/compal_e86/chainload.compalram.bin read_file(../../target/firmware/board/compal_e86/chainload.compalram.bin): file_size=4132, hdr_len=4, dnload_len=15341 read_file(../../target/firmware/board/compal_e86/chainload.compalram.bin): file_size=4132, hdr_len=4, dnload_len=15341 got 2 bytes from modem, data looks like: 2e c8 .. got 1 bytes from modem, data looks like: 1b . got 4 bytes from modem, data looks like: 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 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/15341) handle_write(): 4096 bytes (8192/15341) handle_write(): 4096 bytes (12288/15341) handle_write(): 3053 bytes (15341/15341) 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: 45 E got 1 bytes from modem, data looks like: 53 S got 1 bytes from modem, data looks like: 16 . Received DOWNLOAD NACK from phone, something went wrong :( got 1 bytes from modem, data looks like: 66 f got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6d m got 1 bytes from modem, data looks like: 74 t got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 6c l Received FTMTOOL from phone, ramloader has aborted got 1 bytes from modem, data looks like: 65 e got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 6f o got 1 bytes from modem, data looks like: 72 r got 1 bytes from modem, data looks like: 00 . kbuildsycoca4 running... Also when i run the Mobile app i get :- telnet localhost 4247 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Welcome to the OsmocomBB control interface OsmocomBB> enable OsmocomBB# exit Exit current mode and down to previous mode help Description of the interactive help system list Print command list write Write running configuration to memory, network, or terminal show Show running system information disable Turn off privileged mode command configure Configuration from vty interface copy Copy configuration terminal Set terminal line parameters echo Echo a message back to the vty who Display who is on vty monitor Monitor... no Negate a command or set its defaults off Turn mobiles off (shutdown) and exit sim SIM actions network Network ... call Make a call OsmocomBB# sim % Command incomplete. OsmocomBB# show % Command incomplete. OsmocomBB# Thanks and would be grateful for your support as I appear to be edging forwards. :) and hopefully not backwards. Raz -------------- next part -------------- An HTML attachment was scrubbed... URL: From issertiv at gmail.com Tue Jul 5 12:49:53 2011 From: issertiv at gmail.com (Raz Sharif) Date: Tue, 5 Jul 2011 13:49:53 +0100 Subject: Success at last - C139 now working Layer1.bin displayed on phone :) Message-ID: Dear all, the last few days I have as you know sent a few mails in my quest to delve into the Osmocomm GSM stack. A few problems later and a few substitutes later such as a C139 phone versus the C115 am I now good to go it would appear. Please see below. I did a lot of RTFM and would also like to to thank the folks who provided me with pointers. I will no doubt have a few more issues so lets see. In summary - The Prolific cable works fine albeit a small cut back on the connector - 2.5mm side C115 is supported but if you can go for the C139 - Too many issues to resolve with C115 maybe due to a specific Firmware variant. If you have the time to hack around I am sure it not difficult to work. Here's my Boot loader dump. Please see below. Thanks Raz http://pastebin.com/A1xf8Wkt -------------- next part -------------- An HTML attachment was scrubbed... URL: From _paul at bk.ru Wed Jul 6 13:28:31 2011 From: _paul at bk.ru (Sergey) Date: Wed, 06 Jul 2011 17:28:31 +0400 Subject: gsm specifications Message-ID: Hello, everyone! I've got c123-compatible phone, the firmware is running and that's really cool. Testing branch even sometimes says that a call has been released, but it doesn't seem to reach the target (no ringing). I would like to debug and maybe contribute, but... But here is a problem: I don't understand GSM and can't find reasonable documents to read. I've looked through a book on gsm "GSM and Personal Communications Handbook", but it doesn't seem to provide enough info. Specifications of GSM I found at http://www.3gpp.org/specification-numbering are too plentiful.? Could you please advise some books to understand the protocols? Or could you tell me where to look for specifications and which should be read first (an what to be read at all) ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.huemer at xx.vu Wed Jul 6 14:28:34 2011 From: alexander.huemer at xx.vu (Alexander Huemer) Date: Wed, 6 Jul 2011 16:28:34 +0200 Subject: gsm specifications In-Reply-To: References: Message-ID: <20110706142834.GB24240@de.xx.vu> http://openbsc.osmocom.org/trac/wiki/GSMStandards On Wed, Jul 06, 2011 at 05:28:31PM +0400, Sergey wrote: > Hello, everyone! > > I've got c123-compatible phone, the firmware is running and that's really cool. > Testing branch even sometimes says that a call has been released, but it doesn't seem to reach the target (no ringing). > I would like to debug and maybe contribute, but... > > But here is a problem: I don't understand GSM and can't find reasonable documents to read. > I've looked through a book on gsm "GSM and Personal Communications Handbook", but it doesn't seem to provide enough info. > Specifications of GSM I found at http://www.3gpp.org/specification-numbering are too plentiful.? > > Could you please advise some books to understand the protocols? > Or could you tell me where to look for specifications and which should be read first (an what to be read at all) ? > From _paul at bk.ru Wed Jul 6 14:51:29 2011 From: _paul at bk.ru (Sergey) Date: Wed, 06 Jul 2011 18:51:29 +0400 Subject: =?utf-8?Q?Re[2]=3A_gsm_specifications?= In-Reply-To: <20110706142834.GB24240@de.xx.vu> References: <20110706142834.GB24240@de.xx.vu> Message-ID: Thank you! 06 ???? 2011, 18:28 ?? Alexander Huemer : > http://openbsc.osmocom.org/trac/wiki/GSMStandards > > On Wed, Jul 06, 2011 at 05:28:31PM +0400, Sergey wrote: > > Hello, everyone! > > > > I've got c123-compatible phone, the firmware is running and that's really > cool. > > Testing branch even sometimes says that a call has been released, but it > doesn't seem to reach the target (no ringing). > > I would like to debug and maybe contribute, but... > > > > But here is a problem: I don't understand GSM and can't find reasonable > documents to read. > > I've looked through a book on gsm "GSM and Personal Communications > Handbook", but it doesn't seem to provide enough info. > > Specifications of GSM I found at http://www.3gpp.org/specification-numbering > are too plentiful.? > > > > Could you please advise some books to understand the protocols? > > Or could you tell me where to look for specifications and which should be > read first (an what to be read at all) ? > > From _paul at bk.ru Wed Jul 6 17:29:48 2011 From: _paul at bk.ru (Sergey) Date: Wed, 06 Jul 2011 21:29:48 +0400 Subject: =?utf-8?Q?Re[2]=3A_gsm_specifications?= In-Reply-To: <20110706142834.GB24240@de.xx.vu> References: <20110706142834.GB24240@de.xx.vu> Message-ID: I can't pass 'ETSI PDA Validation'. After registration a letter came saying: "In order to validate your account please reply to this message a blank email" The same e-mail comes every time I try to download a new standard. I've tried replying with various kinds of blank e-mails: blank body, with "Re:" and without, deleting original text and not with no luck. Please help me, what have you answered to get access? Maybe I just have to wait some time? > http://openbsc.osmocom.org/trac/wiki/GSMStandards > From laforge at gnumonks.org Wed Jul 6 17:35:40 2011 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 6 Jul 2011 19:35:40 +0200 Subject: gsm specifications In-Reply-To: References: <20110706142834.GB24240@de.xx.vu> Message-ID: <20110706173540.GB25771@prithivi.gnumonks.org> On Wed, Jul 06, 2011 at 09:29:48PM +0400, Sergey wrote: > I can't pass 'ETSI PDA Validation'. > After registration a letter came saying: > "In order to validate your account please reply to this message a blank > email" > Please help me, what have you answered to get access? Sorry, It was many, many years ago that I registerd on the ETSI site, I don't remember how exactly the registration was done. However, if you receive empty messages, I would suggest to contact the ETSI webmaster / secreteriat about that. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From steve at steve-m.de Wed Jul 6 18:06:40 2011 From: steve at steve-m.de (Steve Markgraf) Date: Wed, 06 Jul 2011 20:06:40 +0200 Subject: gsm specifications In-Reply-To: References: <20110706142834.GB24240@de.xx.vu> Message-ID: <4E14A430.1040407@steve-m.de> Hi, On 06.07.2011 19:29, Sergey wrote: > Please help me, what have you answered to get access? Hint: bugmenot.com -> etsi.org Regards, Steve From mailman at lists.osmocom.org Wed Jul 6 13:46:34 2011 From: mailman at lists.osmocom.org (mailman at lists.osmocom.org) Date: Wed, 06 Jul 2011 15:46:34 +0200 Subject: Bounce action notification Message-ID: This is a Mailman mailing list bounce action notice: List: baseband-devel Member: andre at ac.nl.eu.org Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman at lists.osmocom.org. -------------- next part -------------- An embedded message was scrubbed... From: Mail Delivery System Subject: Mail delivery failed: returning message to sender Date: Wed, 06 Jul 2011 15:46:33 +0200 Size: 4519 URL: From _paul at bk.ru Fri Jul 8 04:41:50 2011 From: _paul at bk.ru (Sergey) Date: Fri, 08 Jul 2011 08:41:50 +0400 Subject: =?utf-8?Q?Is_data_actually_sent_if_=22COMPILED_WITHOUT_TX_SUPPORT=22=3F?= Message-ID: Hello! Is any way that data is actually sent to air if on loading "layer1.compalram.bin" 'osmocon' says: "THIS FIRMWARE WAS COMPILED WITHOUT TX SUPPORT!!! " ? E.g. when 'mobile' says "sending page response" does it really communicate with the BTS? I'm talking about main branch (not testing) and compiled without TX support. Sorry if it's obvious, I just dont want to find "the very extent permittable by law". -------------- next part -------------- An HTML attachment was scrubbed... URL: From wpatan at gmail.com Fri Jul 8 12:24:36 2011 From: wpatan at gmail.com (wpatan) Date: Fri, 8 Jul 2011 05:24:36 -0700 (PDT) Subject: Is data actually sent if "COMPILED WITHOUT TX SUPPORT"? In-Reply-To: References: Message-ID: <1310127876346-3151661.post@n3.nabble.com> If it's compiled without TX support.. then it should not transmit anything. -- View this message in context: http://baseband-devel.722152.n3.nabble.com/Is-data-actually-sent-if-COMPILED-WITHOUT-TX-SUPPORT-tp3150672p3151661.html Sent from the baseband-devel mailing list archive at Nabble.com. From josephli1029 at hotmail.com Wed Jul 13 11:24:00 2011 From: josephli1029 at hotmail.com (josephli) Date: Wed, 13 Jul 2011 04:24:00 -0700 (PDT) Subject: problems to run ./mobile app Message-ID: <1310556240002-3165624.post@n3.nabble.com> Hello every: When I tried to run ./mobile -i 127.0.0.1, the words Failed to parse the config file: '/root/.osmocom/bb/mobile.cfg' Please check or create config file using:'touch /root/osmocom/bb/mobile.cfg' came out. I checked my directory /ect and there is nothing there. It seems that network between my PC and phone is block so that the application ./mobile can not communicate with phone. However the layer1 can load on the phone and work properly. Can any one tell my how to fix this problem? Cheers, Li -- View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-to-run-mobile-app-tp3165624p3165624.html Sent from the baseband-devel mailing list archive at Nabble.com. From weberbe at ee.ethz.ch Wed Jul 13 12:00:50 2011 From: weberbe at ee.ethz.ch (weberbe at ee.ethz.ch) Date: Wed, 13 Jul 2011 14:00:50 +0200 Subject: problems to run ./mobile app In-Reply-To: <1310556240002-3165624.post@n3.nabble.com> References: <1310556240002-3165624.post@n3.nabble.com> Message-ID: <20110713140050.21215h8z79wpka2a@email.ee.ethz.ch> Hi Li As the output of mobile indicates, you need to create an empty file located at /root/osmocom/bb/mobile.cfg Then it should work. Ben Quoting josephli : > Hello every: > > When I tried to run ./mobile -i 127.0.0.1, the words > > Failed to parse the config file: '/root/.osmocom/bb/mobile.cfg' > Please check or create config file using:'touch /root/osmocom/bb/mobile.cfg' > > came out. > > I checked my directory /ect and there is nothing there. It seems that > network between my PC and phone is block so that the application ./mobile > can not communicate with phone. However the layer1 can load on the phone and > work properly. > > Can any one tell my how to fix this problem? > > Cheers, > Li > > -- > View this message in context: > http://baseband-devel.722152.n3.nabble.com/problems-to-run-mobile-app-tp3165624p3165624.html > Sent from the baseband-devel mailing list archive at Nabble.com. > From weberbe at ee.ethz.ch Wed Jul 13 12:13:25 2011 From: weberbe at ee.ethz.ch (weberbe at ee.ethz.ch) Date: Wed, 13 Jul 2011 14:13:25 +0200 Subject: problems to run ./mobile app In-Reply-To: <20110713140050.21215h8z79wpka2a@email.ee.ethz.ch> References: <1310556240002-3165624.post@n3.nabble.com> <20110713140050.21215h8z79wpka2a@email.ee.ethz.ch> Message-ID: <20110713141325.17904n5j1sr12mlh@email.ee.ethz.ch> Hi Li Sorry, the actual config file path for you setup should be /root/.osmocom/bb/mobile.cfg instead of /root/osmocom/bb/mobile.cfg Ben Quoting weberbe at ee.ethz.ch: > Hi Li > > As the output of mobile indicates, you need to create an empty file > located at > /root/osmocom/bb/mobile.cfg > Then it should work. > > Ben > > Quoting josephli : > >> Hello every: >> >> When I tried to run ./mobile -i 127.0.0.1, the words >> >> Failed to parse the config file: '/root/.osmocom/bb/mobile.cfg' >> Please check or create config file using:'touch /root/osmocom/bb/mobile.cfg' >> >> came out. >> >> I checked my directory /ect and there is nothing there. It seems that >> network between my PC and phone is block so that the application ./mobile >> can not communicate with phone. However the layer1 can load on the phone and >> work properly. >> >> Can any one tell my how to fix this problem? >> >> Cheers, >> Li >> >> -- >> View this message in context: >> http://baseband-devel.722152.n3.nabble.com/problems-to-run-mobile-app-tp3165624p3165624.html >> Sent from the baseband-devel mailing list archive at Nabble.com. >> > > > > > From josephli1029 at hotmail.com Wed Jul 13 15:25:38 2011 From: josephli1029 at hotmail.com (josephli) Date: Wed, 13 Jul 2011 08:25:38 -0700 (PDT) Subject: problems to run ./mobile app In-Reply-To: <20110713141325.17904n5j1sr12mlh@email.ee.ethz.ch> References: <1310556240002-3165624.post@n3.nabble.com> <20110713140050.21215h8z79wpka2a@email.ee.ethz.ch> <20110713141325.17904n5j1sr12mlh@email.ee.ethz.ch> Message-ID: <1310570738629-3166389.post@n3.nabble.com> Hi Ben I read some person's comment from other posts. Some one advised to create an empty file as sudo mkdir /etc/osmocom sudo touch /etc/osmocom/osmocom.cfg I followed that but it did not work for me. The same error was still there Thanks for your reply, I will try your method tomorrow Cheers Li -- View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-to-run-mobile-app-tp3165624p3166389.html Sent from the baseband-devel mailing list archive at Nabble.com. From weberbe at ee.ethz.ch Wed Jul 13 15:40:20 2011 From: weberbe at ee.ethz.ch (weberbe at ee.ethz.ch) Date: Wed, 13 Jul 2011 17:40:20 +0200 Subject: problems to run ./mobile app In-Reply-To: <1310570738629-3166389.post@n3.nabble.com> References: <1310556240002-3165624.post@n3.nabble.com> <20110713140050.21215h8z79wpka2a@email.ee.ethz.ch> <20110713141325.17904n5j1sr12mlh@email.ee.ethz.ch> <1310570738629-3166389.post@n3.nabble.com> Message-ID: <20110713174020.309918a9q1ccoo6c@email.ee.ethz.ch> OK, the mobile application (current master branch) does no longer use the /etc directory. It uses .osmocom/bb/mobile.cfg in the users home directory instead. See also commit 4be57b9afd0f7a07361a5ac24a271adfd5e302d1. This was actually discussed here http://baseband-devel.722152.n3.nabble.com/Help-me-I-have-a-difficult-problem-td2605211.html Hope this helps Quoting josephli : > Hi Ben > > I read some person's comment from other posts. Some one advised to create an > empty file as > > sudo mkdir /etc/osmocom > sudo touch /etc/osmocom/osmocom.cfg > > I followed that but it did not work for me. The same error was still there > > Thanks for your reply, I will try your method tomorrow > > Cheers > > Li > > -- > View this message in context: > http://baseband-devel.722152.n3.nabble.com/problems-to-run-mobile-app-tp3165624p3166389.html > Sent from the baseband-devel mailing list archive at Nabble.com. > From josephli1029 at hotmail.com Thu Jul 14 03:23:26 2011 From: josephli1029 at hotmail.com (josephli) Date: Wed, 13 Jul 2011 20:23:26 -0700 (PDT) Subject: problems to run ./mobile app In-Reply-To: <20110713174020.309918a9q1ccoo6c@email.ee.ethz.ch> References: <1310556240002-3165624.post@n3.nabble.com> <20110713140050.21215h8z79wpka2a@email.ee.ethz.ch> <20110713141325.17904n5j1sr12mlh@email.ee.ethz.ch> <1310570738629-3166389.post@n3.nabble.com> <20110713174020.309918a9q1ccoo6c@email.ee.ethz.ch> Message-ID: <1310613806546-3168034.post@n3.nabble.com> Hi Ben, Many thanks for helping me. It actually works well by adding the new file in the specific directory. I check the guild on wiki, it told me the wrong information and that is why I stuck there. Now I can see the layer23 searching the cells and layer1 output the information from the command window. But after I start the telnet, it shows that "MS '1' is admin down". Is that mean we need to write a config file to fit the specific network, instead of creating a empty mobile.cfg file? Cheers, Li -- View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-to-run-mobile-app-tp3165624p3168034.html Sent from the baseband-devel mailing list archive at Nabble.com. From weberbe at ee.ethz.ch Thu Jul 14 06:33:13 2011 From: weberbe at ee.ethz.ch (weberbe at ee.ethz.ch) Date: Thu, 14 Jul 2011 08:33:13 +0200 Subject: problems to run ./mobile app In-Reply-To: <1310613806546-3168034.post@n3.nabble.com> References: <1310556240002-3165624.post@n3.nabble.com> <20110713140050.21215h8z79wpka2a@email.ee.ethz.ch> <20110713141325.17904n5j1sr12mlh@email.ee.ethz.ch> <1310570738629-3166389.post@n3.nabble.com> <20110713174020.309918a9q1ccoo6c@email.ee.ethz.ch> <1310613806546-3168034.post@n3.nabble.com> Message-ID: <20110714083313.91686bdmll3c5aqx@email.ee.ethz.ch> Hi Li If you want your phone to be up check this out (quick google search): http://lists.osmocom.org/pipermail/baseband-devel/2011-January/000929.html Hope this helps Ben Quoting josephli : > Hi Ben, > > Many thanks for helping me. > > It actually works well by adding the new file in the specific directory. I > check the guild on wiki, it told me the wrong information and that is why I > stuck there. Now I can see the layer23 searching the cells and layer1 output > the information from the command window. But after I start the telnet, it > shows that "MS '1' is admin down". Is that mean we need to write a config > file to fit the specific network, instead of creating a empty mobile.cfg > file? > > Cheers, > > Li > > -- > View this message in context: > http://baseband-devel.722152.n3.nabble.com/problems-to-run-mobile-app-tp3165624p3168034.html > Sent from the baseband-devel mailing list archive at Nabble.com. > From josephli1029 at hotmail.com Thu Jul 14 09:59:31 2011 From: josephli1029 at hotmail.com (josephli) Date: Thu, 14 Jul 2011 02:59:31 -0700 (PDT) Subject: problems to run ./mobile app In-Reply-To: <20110714083313.91686bdmll3c5aqx@email.ee.ethz.ch> References: <1310556240002-3165624.post@n3.nabble.com> <20110713140050.21215h8z79wpka2a@email.ee.ethz.ch> <20110713141325.17904n5j1sr12mlh@email.ee.ethz.ch> <1310570738629-3166389.post@n3.nabble.com> <20110713174020.309918a9q1ccoo6c@email.ee.ethz.ch> <1310613806546-3168034.post@n3.nabble.com> <20110714083313.91686bdmll3c5aqx@email.ee.ethz.ch> Message-ID: <1310637571005-3168653.post@n3.nabble.com> Hi I checked the 'ms 1' status. It shown as follow Status:U2_NOT_UPDATED IMSI detached LAI:invalid It seems that phone didn't read the sim card information properly. Can you help me to fix it? Cheers Li -- View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-to-run-mobile-app-tp3165624p3168653.html Sent from the baseband-devel mailing list archive at Nabble.com. From josephli1029 at hotmail.com Fri Jul 15 04:03:04 2011 From: josephli1029 at hotmail.com (josephli) Date: Thu, 14 Jul 2011 21:03:04 -0700 (PDT) Subject: problems to run ./mobile app In-Reply-To: <20110714083313.91686bdmll3c5aqx@email.ee.ethz.ch> References: <1310556240002-3165624.post@n3.nabble.com> <20110713140050.21215h8z79wpka2a@email.ee.ethz.ch> <20110713141325.17904n5j1sr12mlh@email.ee.ethz.ch> <1310570738629-3166389.post@n3.nabble.com> <20110713174020.309918a9q1ccoo6c@email.ee.ethz.ch> <1310613806546-3168034.post@n3.nabble.com> <20110714083313.91686bdmll3c5aqx@email.ee.ethz.ch> Message-ID: <1310702584646-3170998.post@n3.nabble.com> It does work for the first time after I enable the sim by ''enable'--'conf t'--'ms 1'--'no shutdown' I really could make a phone call. But after that, when I try to swap another sim card, ms 1 could never wake up again. That's strange, isn't it ? -- View this message in context: http://baseband-devel.722152.n3.nabble.com/problems-to-run-mobile-app-tp3165624p3170998.html Sent from the baseband-devel mailing list archive at Nabble.com. From Andreas.Eversberg at versatel.de Thu Jul 14 10:40:41 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Thu, 14 Jul 2011 12:40:41 +0200 Subject: neighbour cell measurement Message-ID: hi, i would like to commit my well tested neighbour cell measurement code, as well as the improved cell selection / re-selection process soon. with it, it is possible to move with the mobile phone while beeing in idle mode (no call). it tracks neighbour cells and switches if a better cell is detected. i found and fixed many bug issues in mobility management and cell selection process. i did allot of driving tests. in order to do that, the neighbour cell measurement code for layer1 is required. this code must be reviewed first. i splitted it in three patches: neigh_getset.patch [layer1] Adding rffe_set_gain() and rffe_get_gain() to get/set computed gain. rffe_compute_gain() is the new name for rffe_set_gain(). I needed to change this, to solve the name collision with the rffe_set_gain() function, which actually sets the absolute gain. rffe_get_gain() will now read the absolute gain which has been computed by rffe_compute_gain() or set by rffe_set_gain(). neigh_l23.patch [layer23] Adding neighbour cell measurement to L1CTL interface. (layer23) neigh_l1.patch [layer1] Adding neighbour cell measurement code to layer1. When listening to BCCH, layer1 may measure the power level of neighbour cells. A list of neighbour cell frequencies need to be sent to layer1. After the measurement is done, the results are indicated to layer23. andreas -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: neigh_l23.patch Type: application/octet-stream Size: 4043 bytes Desc: neigh_l23.patch URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: neigh_getset.patch Type: application/octet-stream Size: 12673 bytes Desc: neigh_getset.patch URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: neigh_l1.patch Type: application/octet-stream Size: 10122 bytes Desc: neigh_l1.patch URL: From issertiv at gmail.com Thu Jul 14 11:16:03 2011 From: issertiv at gmail.com (Raz Sharif) Date: Thu, 14 Jul 2011 12:16:03 +0100 Subject: neighbour cell measurement In-Reply-To: References: Message-ID: This looks interesting. Can you provide an output of the results when running this code please ? Thanks Raz On Thu, Jul 14, 2011 at 11:40 AM, Andreas.Eversberg < Andreas.Eversberg at versatel.de> wrote: > ** > hi, > > i would like to commit my well tested neighbour cell measurement code, as > well as the improved cell selection / re-selection process soon. with it, it > is possible to move with the mobile phone while beeing in idle mode (no > call). it tracks neighbour cells and switches if a better cell is detected. > i found and fixed many bug issues in mobility management and cell selection > process. i did allot of driving tests. > > in order to do that, the neighbour cell measurement code for layer1 is > required. this code must be reviewed first. i splitted it in three patches: > > > neigh_getset.patch > > [layer1] Adding rffe_set_gain() and rffe_get_gain() to get/set computed > gain. > > rffe_compute_gain() is the new name for rffe_set_gain(). I needed to change > this, to solve the name collision with the rffe_set_gain() function, which > actually sets the absolute gain. > > rffe_get_gain() will now read the absolute gain which has been computed by > rffe_compute_gain() or set by rffe_set_gain(). > > > neigh_l23.patch > > [layer23] Adding neighbour cell measurement to L1CTL interface. (layer23) > > > neigh_l1.patch > > [layer1] Adding neighbour cell measurement code to layer1. > > When listening to BCCH, layer1 may measure the power level of neighbour > cells. A list of neighbour cell frequencies need to be sent to layer1. After > the measurement is done, the results are indicated to layer23. > > > andreas > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Thu Jul 14 11:44:16 2011 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 14 Jul 2011 13:44:16 +0200 Subject: neighbour cell measurement In-Reply-To: References: Message-ID: <20110714114416.GT25905@prithivi.gnumonks.org> Hi Andreas, On Thu, Jul 14, 2011 at 12:40:41PM +0200, Andreas.Eversberg wrote: > i would like to commit my well tested neighbour cell measurement code, > as well as the improved cell selection / re-selection process soon. with great! > in order to do that, the neighbour cell measurement code for layer1 is > required. this code must be reviewed first. i splitted it in three > patches: The patches look fine to me. I'd wait for another day if Sylvain or Dieter have any comments, but otherwise they can be merged. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From Andreas.Eversberg at versatel.de Fri Jul 15 06:15:07 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Fri, 15 Jul 2011 08:15:07 +0200 Subject: AW: neighbour cell measurement Message-ID: > The patches look fine to me. I'd wait for another day if Sylvain or > Dieter have any comments, but otherwise they can be merged. i will remove some comments and temporary debug prints before committing. From 246tnt at gmail.com Fri Jul 15 07:02:10 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Fri, 15 Jul 2011 09:02:10 +0200 Subject: neighbour cell measurement In-Reply-To: References: Message-ID: ?Hi, Here's a few minor comments, shouldn't take more than 10 min to fix them and then you can merge it. (Or tell me if you want me to do it) > neigh_getset.patch - I would expose the set_gain_reg (so no static and put it in the .h), just because it's useful when hacking around and I think it 'belongs' to a TRF API. - I think those file should be updated because they use the old set_reg function src/target/firmware/apps/layer1/main.c src/target/firmware/apps/l1test/main.c You patched the first one by replacing set_reg by compute_gain but altough both take 2 arguments, they are _completely_ different > neigh_l23.patch - There is a L1CTL_MEAS_REQ in comment in l1ctl.h ( it should be NEIGH_PM) - In rx_l1_neigh_pm_ind I don't see where you free the msgb ? It should be freed in the switch() and it's not AFAICT > neigh_l1.patch - In l23_api.c you create a new chan_nr2mf_task_mask function, but then the old one chan_nr2mf_task is now unused, so remove it. Cheers, Sylvain From spaar at mirider.augusta.de Fri Jul 15 09:28:57 2011 From: spaar at mirider.augusta.de (Dieter Spaar) Date: Fri, 15 Jul 2011 09:28:57 CEST Subject: neighbour cell measurement Message-ID: <4e200859.mirider@mirider.augusta.de> Hello Andreas, hello Harald, On Thu, 14 Jul 2011 13:44:16 +0200, "Harald Welte" wrote: > > The patches look fine to me. I'd wait for another day if Sylvain or > Dieter have any comments, but otherwise they can be merged. The patches are fine for me. Best regards, Dieter -- Dieter Spaar, Germany spaar at mirider.augusta.de From laforge at gnumonks.org Sat Jul 16 15:33:30 2011 From: laforge at gnumonks.org (Harald Welte) Date: Sat, 16 Jul 2011 17:33:30 +0200 Subject: GSM 03.22 bug / unreachable code? Message-ID: <20110716153330.GW10557@prithivi.gnumonks.org> Hi Andreas, while using Smatch on layer23, I discovered a potential problem in GSM 03.22: There is a loop with an if-statement, and there might be missing curly braces. Do you think this is the correct way to fix it? diff --git a/src/host/layer23/src/mobile/gsm322.c b/src/host/layer23/src/mobile/gsm322.c index 210215e..766ffbf 100644 --- a/src/host/layer23/src/mobile/gsm322.c +++ b/src/host/layer23/src/mobile/gsm322.c @@ -983,9 +983,10 @@ static int gsm322_a_user_resel(struct osmocom_ms *ms, struct msgb *msg) /* search current PLMN in list */ llist_for_each_entry(plmn_entry, &plmn->sorted_plmn, entry) { if (plmn_entry->mcc == plmn->mcc - && plmn_entry->mnc == plmn->mnc) + && plmn_entry->mnc == plmn->mnc) { plmn_found = plmn_entry; break; + } } /* abort if list is empty */ -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From Andreas.Eversberg at versatel.de Mon Jul 18 07:14:22 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Mon, 18 Jul 2011 09:14:22 +0200 Subject: AW: GSM 03.22 bug / unreachable code? Message-ID: > while using Smatch on layer23, I discovered a potential problem in GSM > 03.22: There is a loop with an if-statement, and there might be missing > curly braces. hi harald, you are right. patch is committed. thanx, andreas From ibruno.macintosh at gmail.com Sat Jul 16 16:18:06 2011 From: ibruno.macintosh at gmail.com (iBruno) Date: Sat, 16 Jul 2011 17:18:06 +0100 Subject: USB -FTDI 232RL- RS232 Converter Message-ID: Hello I am having troubles, to find the decent cable/interface to get this working properly!! I bough converter USB -FTDI 232RLChip- RS232, Converter. IS giving me 6.60v Output.. and I needed 3.3v. Electronically, what can I do, to adjust for the correct Voltage? My phone didn't fry, besides I got connection! when I load the hello world or layer one, is not completing the task! I believe is because of the amount of power. If you know a cable that works decently, let me know :-) Big thanks to whole community. From peter at stuge.se Sat Jul 16 17:12:30 2011 From: peter at stuge.se (Peter Stuge) Date: Sat, 16 Jul 2011 19:12:30 +0200 Subject: USB -FTDI 232RL- RS232 Converter In-Reply-To: References: Message-ID: <20110716171230.21165.qmail@stuge.se> iBruno wrote: > I am having troubles, to find the decent cable/interface to get > this working properly!! There are many cables that are almost right, so it's important to get the right ones. > I bough converter USB -FTDI 232RLChip- RS232, Converter. > IS giving me 6.60v Output.. One part of RS232 is voltage levels, and they are indeed completely wrong for the telephone. They may well destroy the serial port on the phone. > Electronically, what can I do, to adjust for the correct Voltage? I would avoid this. Find a suitable cable instead. Buy a few different ones that are advertised to support the particular phone. > My phone didn't fry, besides I got connection! Stop using the cable. The more you use it the more you risk destroying the serial port in the phone. > not completing the task! I believe is because of the amount of > power. Voltage, but yes probably. > If you know a cable that works decently, let me know :-) FT2232H or FT4232H based cables are the popular ones. Testing with FT2232D (slower USB than H) has not worked so perfectly. I'd recommend buying a cable with a connector especially made for the phone, because a standard 2.5mm plug does not fit without mechanical rework. Low quality plugs that have been reworked to fit may not make a very good connection, which also causes signalling problems. //Peter From Andreas.Eversberg at versatel.de Mon Jul 18 07:36:56 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Mon, 18 Jul 2011 09:36:56 +0200 Subject: AW: The call has been rejected Message-ID: hi josephli, > Read stored BA list mnc=01 the mobile application stores the last cells and neighbour cells (band allocation) of each network. this way the scanning is much faster when restarting. because you use the SIM card with MNC == 02 the first time, there is no band allocation stored for that. the mobile will do a full scan in this case. > while the sim card service I am tesing is actually with mnc 00 and 02. i know that MNC == 0 will not work until i commited improvements of cell selection process last sunday. you should retry that, but first try with an MNC > 0. can you provide debug output when trying a call? also can you provide VTY output of "show ms" before you make the call? regards, andreas From josephli1029 at hotmail.com Mon Jul 18 08:06:59 2011 From: josephli1029 at hotmail.com (josephli) Date: Mon, 18 Jul 2011 01:06:59 -0700 (PDT) Subject: AW: The call has been rejected In-Reply-To: References: <1310725408269-3171584.post@n3.nabble.com> Message-ID: <1310976419453-3178448.post@n3.nabble.com> This is when I try to read sim card in VTY: root at gsm-desktop:~# telnet localhost 4247 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Welcome to the OsmocomBB control interface OsmocomBB> en OsmocomBB# sim reader 1 OsmocomBB# % (MS 1) % SIM failed, replace SIM! Any way, I was asked to replace the sim card. This is when I check the MS 1 status: show ms MS '1' is up, service is limited IMEI: 000000000000000 IMEISV: 0000000000000000 IMEI generation: fixed automatic network selection state: A6 no SIM inserted cell selection state: C7 camped on any cell (ARFCN 115) radio ressource layer state: idle mobility management layer state: MM idle, no IMSI Thing is like the MS is fixed on the frequency band which mnc==01 is allocated. The way I did next is to replace the SIM card that belongs to the service of mnc==01 and it worked fine when I run the command of "sim reader 1". I suspect that when the phone is in idle status, it scans the frequency band with strongest RSSI. After the VTY activated the sim card, the call connects as long as the frequency band and the sim card belonging to the same service provider. Is that the way it temporary works? Regards, Li -- View this message in context: http://baseband-devel.722152.n3.nabble.com/The-call-has-been-rejected-tp3171584p3178448.html Sent from the baseband-devel mailing list archive at Nabble.com. From akibsayyed at gmail.com Mon Jul 18 13:41:28 2011 From: akibsayyed at gmail.com (Akib Sayyed) Date: Mon, 18 Jul 2011 19:11:28 +0530 Subject: Is it possible to triangulate cellphone with osmocombb Message-ID: Guys i bit new to osmocombb i wanted to know is it possible to triangulate any gsm cellphone with osmocombb?? -- Akib Sayyed Matrix-Shell akibsayyed at gmail.com akibsayyed at matrixshell.com Mob:- +91-966-514-2243 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kost at linux.hr Wed Jul 20 21:50:47 2011 From: kost at linux.hr (Vlatko Kosturjak) Date: Wed, 20 Jul 2011 23:50:47 +0200 Subject: gpsd and as-needed patches Message-ID: <20110720215047.GA17771@griffin.linux.hr> Hello! Hopefully this is right place to send patches since I don't have access to tracker. I'm sending two patches against latest git version. First one is updating gpsd support since new gpsd have few functions changed: I've #ifdefed each offending function, so you can check each function in configure process or just wrap everything inside same #ifdef, depending on your wish. I have #defined timeout, but it can be done as variable if you think 2000 miliseconds is not good for everybody. Other patch is just quick hack to support --as-needed linker flag, so osmocombb can compile fine on distros which enforce such flag. In order, to read more about flag, read here: http://www.gentoo.org/proj/en/qa/asneeded.xml (In short, order of flags do matter) Hope it helps, -- Vlatko Kosturjak - KoSt -------------- next part -------------- A non-text attachment was scrubbed... Name: osmocom-configure-patch.diff Type: text/x-diff Size: 559 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: osmocom-gpsd-patch.diff Type: text/x-diff Size: 1227 bytes Desc: not available URL: From Andreas.Eversberg at versatel.de Thu Jul 21 07:54:50 2011 From: Andreas.Eversberg at versatel.de (Andreas.Eversberg) Date: Thu, 21 Jul 2011 09:54:50 +0200 Subject: AW: gpsd and as-needed patches Message-ID: hi vlatko, thanx for your patches. i don't have knowledge about gpsd api. before i can apply them, i need to know about gps_waiting() function. the osmo_gpsd_cb() function in common/gps.c is called when there is data to be read from gpsd. this function (like any other function) may not delay or block. (except for the CPU processing time of the function.) if no data is available from gpsd, the function must continue with "goto gps_not_ready;" immidately. what will gps_waiting() do in case there is no (complete) information available? regards, andreas From kost at linux.hr Thu Jul 21 08:31:24 2011 From: kost at linux.hr (Vlatko Kosturjak) Date: Thu, 21 Jul 2011 10:31:24 +0200 Subject: AW: gpsd and as-needed patches In-Reply-To: References: Message-ID: <4E27E3DC.5020100@linux.hr> Hello Andreas! On 07/21/2011 09:54 AM, Andreas.Eversberg wrote: > hi vlatko, > > thanx for your patches. i don't have knowledge about gpsd api. before i > can apply them, i need to know about gps_waiting() function. > > the osmo_gpsd_cb() function in common/gps.c is called when there is data > to be read from gpsd. this function (like any other function) may not > delay or block. (except for the CPU processing time of the function.) if > no data is available from gpsd, the function must continue with "goto > gps_not_ready;" immidately. > > what will gps_waiting() do in case there is no (complete) information > available? Understand. What I found in the documentation is following: "...gps_waiting() can be used to check whether there is data from the daemon. The second argument is the maximum amount of time to wait (in microseconds) on input before returning. It returns true if there input waiting, false on timeout (no data waiting) or error condition. This function is a convenience wrapper around a select(2) call, and zeros errno on entry; you can test errno after exit to get more information about error conditions. Note that choosing a wait timeout of less than twice the cycle time of your device will be hazardous, as the receiver probably will not supply input often enough to prevent a spurious error indication. For the typical 1-second cycle time of GPSes this implies a minimum 2-second timeout..." From: http://gpsd.berlios.de/libgps.html Since they recommend minimum of 2-second timeout, I have done this way. Since they did not define "hazardous", I experimented with lower timeouts and it's possible to set it without any "hazardous?" effects. Still I don't know what happens if timeout is set to 0 and documentation doesn't say anything (as I understand 0 will be desired). Will try to make small test program and let you know. Kost From lists at infosecurity.ch Fri Jul 22 09:50:19 2011 From: lists at infosecurity.ch (Fabio Pietrosanti (naif)) Date: Fri, 22 Jul 2011 11:50:19 +0200 Subject: Telecommunication and Wireless Hacking at CCC CAMP 2011 Message-ID: <4E2947DB.5000904@infosecurity.ch> Hi all, i just wanted to send a summary of all most cool talk that will be at CCC CAMP 2011 related to Telecommunications and Wireless Technologies hacking: Open-source 4G radio - It's time to start WiMAX and LTE hacking http://events.ccc.de/camp/2011/Fahrplan/events/4446.en.html Applied Research on security of TETRA radio - Digital radio technology beyond GSM http://events.ccc.de/camp/2011/Fahrplan/events/4496.en.html GPRS Intercept - Wardriving phone networks http://events.ccc.de/camp/2011/Fahrplan/events/4504.en.html Introduction to Satellite Communications - Installation and Operation of Satellite Systems http://events.ccc.de/camp/2011/Fahrplan/events/4442.en.html Transition Telecom - Telecommunications and networking during energy descent http://events.ccc.de/camp/2011/Fahrplan/events/4459.en.html Anyone missing to the list? -naif From lists at infosecurity.ch Fri Jul 22 10:55:13 2011 From: lists at infosecurity.ch (Fabio Pietrosanti (naif)) Date: Fri, 22 Jul 2011 12:55:13 +0200 Subject: Telecommunication and Wireless Hacking at CCC CAMP 2011 In-Reply-To: <4E2947DB.5000904@infosecurity.ch> References: <4E2947DB.5000904@infosecurity.ch> Message-ID: <4E295711.6010000@infosecurity.ch> On 7/22/11 11:50 AM, Fabio Pietrosanti (naif) wrote: > Open-source 4G radio - It's time to start WiMAX and LTE hacking > http://events.ccc.de/camp/2011/Fahrplan/events/4446.en.html > > Applied Research on security of TETRA radio - Digital radio technology > beyond GSM > http://events.ccc.de/camp/2011/Fahrplan/events/4496.en.html > > GPRS Intercept - Wardriving phone networks > http://events.ccc.de/camp/2011/Fahrplan/events/4504.en.html > > Introduction to Satellite Communications - Installation and Operation > of Satellite Systems > http://events.ccc.de/camp/2011/Fahrplan/events/4442.en.html > > Transition Telecom - Telecommunications and networking during energy descent > http://events.ccc.de/camp/2011/Fahrplan/events/4459.en.html > > Anyone missing to the list? Stuff you don't see - every day - GNU Radio Internals - how to use the Framework http://events.ccc.de/camp/2011/Fahrplan/events/4453.en.html Hacking community is owning most radio frequencies and protocols! That's cooooool! :-) -naif From miprom68 at gmail.com Fri Jul 22 13:41:36 2011 From: miprom68 at gmail.com (miprom68 at gmail.com) Date: Fri, 22 Jul 2011 09:41:36 -0400 Subject: IMEI numbers, signal strength Message-ID: Can someone help with these? 1) With the GSM debugger phone, how difficult is it to get only IMEI numbers of received packets? 2) Can the debugger phone report the signal strength of received packets? If not, is it possible? 3) Is there any way with mods to get I/Q out of the DSP? 4) Is there any work going on to make a CDMA debugger phone? 5) Are there any GSM phones that have an option to force calls to be made only on 3G/4G? Thank you, Ben -------------- next part -------------- An HTML attachment was scrubbed... URL: From miprom68 at gmail.com Sun Jul 24 02:15:08 2011 From: miprom68 at gmail.com (miprom68 at gmail.com) Date: Sat, 23 Jul 2011 22:15:08 -0400 Subject: IMEI numbers, signal strength In-Reply-To: References: Message-ID: Anyone? On Fri, Jul 22, 2011 at 9:41 AM, wrote: > Can someone help with these? > 1) With the GSM debugger phone, how difficult is it to get only IMEI numbers > of received packets? > 2) Can the debugger phone report the signal strength of received packets? If > not, is it possible? > 3) Is there any way with mods to get I/Q out of the DSP? > 4) Is there any work going on to make a CDMA debugger phone? > 5) Are there any GSM phones that have an option to force calls to be made > only on 3G/4G? > > Thank you, > Ben > > From mad at auth.se Sun Jul 24 15:36:47 2011 From: mad at auth.se (mad) Date: Sun, 24 Jul 2011 17:36:47 +0200 Subject: IMEI numbers, signal strength In-Reply-To: Message-ID: <20110724153647.349af575@mail.auth.se> Hi Ben! > Anyone? > > On Fri, Jul 22, 2011 at 9:41 AM, wrote: > > Can someone help with these? > > 1) With the GSM debugger phone, how difficult is it to get only IMEI > numbers > > of received packets? First of all, it's unclear what exactly you mean by "the GSM debugger phone" as osmocom-bb is primary an implementation of a gsm stack like it's found in any standard cell phone. There is a debug output via gsmtap to e.g. wireshark where you see all received and send frames to/from your osmocom-bb. Inherent to its hardware and open source approach it's possible to get it to dump frames received, independent of normal gsm operation. To do that at the moment it's necessary to do some work of your own, based on existing branches. I will try to answer your questions based on what's theoretically possible. The IMEI is not send very often in conversations between phone and network, in fact the operator configures when (and if) it's requested from the phone. Practically some operators request it when doing an authentication request, others only when a location update using an IMSI happened. And I've never seen it transmitted in the clear, only after encryption started. So answering your question: Very difficult, exept you know the key, e.g. on your own phone and receive at the right moment. > > 2) Can the debugger phone report the signal strength of received packets? > If > > not, is it possible? Yes, the gsmtap output contains the signal strength on every frame. > > 3) Is there any way with mods to get I/Q out of the DSP? I'm not sure, I think Sylvain knows more about that. > > 4) Is there any work going on to make a CDMA debugger phone? As osmocom-bb is (yet) an explicit GSM stack, no. And I've not heard of approaches to do so > > 5) Are there any GSM phones that have an option to force calls to be made > > only on 3G/4G? GSM phones are not capable to use 3G/4G networks. Certainly you mean 3G/4G phones and disallowing 2G/GSM fallback. I've not seen that in featurephones yet (but some may allow that) but I heard it's possible on jailbreaked iphones. You should find something by searching about that. Regards, Mad From 246tnt at gmail.com Sun Jul 24 16:17:45 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sun, 24 Jul 2011 18:17:45 +0200 Subject: IMEI numbers, signal strength In-Reply-To: <20110724153647.349af575@mail.auth.se> References: <20110724153647.349af575@mail.auth.se> Message-ID: >> > 3) Is there any way with mods to get I/Q out of the DSP? > > I'm not sure, I think Sylvain knows more about that. I have not done it, but it's possible to do. But I won't explain how to do it because anyone that would understand those explanations enough to make something of it would already know how to do it ... kind of a chicken and egg problem. Cheers, Sylvain From mad at auth.se Sun Jul 24 17:21:20 2011 From: mad at auth.se (mad) Date: Sun, 24 Jul 2011 19:21:20 +0200 Subject: IMEI numbers, signal strength In-Reply-To: Message-ID: <20110724172120.9adbec4c@mail.auth.se> Hi Sylvain! > >> > 3) Is there any way with mods to get I/Q out of the DSP? > > > > I'm not sure, I think Sylvain knows more about that. > > I have not done it, but it's possible to do. > > But I won't explain how to do it because anyone that would understand > those explanations enough to make something of it would already know > how to do it ... kind of a chicken and egg problem. Ok, I had in my mind that it was mentioned somehow but never cared that much about DSP level yet. BTW, it is possible and you haven't done it yet? I'm suprised! ;-D Regards, Mad From 246tnt at gmail.com Sun Jul 24 17:38:11 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sun, 24 Jul 2011 19:38:11 +0200 Subject: IMEI numbers, signal strength In-Reply-To: <20110724172120.9adbec4c@mail.auth.se> References: <20110724172120.9adbec4c@mail.auth.se> Message-ID: > BTW, it is possible and you haven't done it yet? I'm suprised! ;-D Well it's because I think it's not a good idea ... The DSP has a very good demodulator, way better than airprobe ... why would I bother moving _more_ data out of the DSP to use them with an inferior demodulator ... Cheers, Sylvain From mad at auth.se Sun Jul 24 20:41:12 2011 From: mad at auth.se (mad) Date: Sun, 24 Jul 2011 22:41:12 +0200 Subject: IMEI numbers, signal strength In-Reply-To: Message-ID: <20110724204112.7c636069@mail.auth.se> > > BTW, it is possible and you haven't done it yet? I'm suprised! ;-D > > Well it's because I think it's not a good idea ... > > The DSP has a very good demodulator, way better than airprobe ... why > would I bother moving _more_ data out of the DSP to use them with an > inferior demodulator ... > That's right for GMSK but it would allow to use other modulations than aren't supported by the DSP like 8-PSK(?), 16-QAM and 32-QAM for EDGE. GNU Radio should have dempdulators for that. Of course it's more or less useless without having an implementation for GPRS first. Beside the coolness of using these devices as a frontend for GNU Radio. :-) Regards, Mad From 246tnt at gmail.com Sun Jul 24 20:52:00 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sun, 24 Jul 2011 22:52:00 +0200 Subject: IMEI numbers, signal strength In-Reply-To: <20110724204112.7c636069@mail.auth.se> References: <20110724204112.7c636069@mail.auth.se> Message-ID: Hi, > That's right for GMSK but it would allow to use other modulations than aren't supported by the DSP like 8-PSK(?), 16-QAM and 32-QAM for EDGE. GNU Radio should have dempdulators for that. True ... I tought about that myself. but until someone does it for the USRP first, it's not much use. > Of course it's more or less useless without having an implementation for GPRS first. Have a look at the CCC camp talks :) > Beside the coolness of using these devices as a frontend for GNU Radio. :-) Well capturing a continuous stream of IQ sample (vs a burst) would be pretty hard ... Besides 2 * 16 * 270833 is a lot of data ... about 10 times more than you can send through the serial port so getting them out the DSP into the ARM is only half (ok, make 3/4) of the problem. Cheers, Sylvain From mad at auth.se Sun Jul 24 21:20:42 2011 From: mad at auth.se (mad) Date: Sun, 24 Jul 2011 23:20:42 +0200 Subject: IMEI numbers, signal strength In-Reply-To: Message-ID: <20110724212042.60fadc3c@mail.auth.se> > > Of course it's more or less useless without having an implementation for > GPRS first. > > Have a look at the CCC camp talks :) Ahhh ok, I will. Sadly I won't make it there in person. > > > > Beside the coolness of using these devices as a frontend for GNU Radio. > :-) > > Well capturing a continuous stream of IQ sample (vs a burst) would be > pretty hard ... > Besides 2 * 16 * 270833 is a lot of data ... about 10 times more than > you can send through the serial port so getting them out the DSP into > the ARM is only half (ok, make 3/4) of the problem. > That is quite much indeed. Perhaps some delta encoding and compression on the serial line would do the job if the ARM copes with that, too. Or with reduced sample size. But at least some timeslots for EGPRS should be possible. Regards, Mad From paul at kristianpaul.org Sun Jul 24 18:22:13 2011 From: paul at kristianpaul.org (Cristian Paul =?iso-8859-1?Q?Pe=F1aranda?= Rojas) Date: Sun, 24 Jul 2011 13:22:13 -0500 Subject: IMEI numbers, signal strength In-Reply-To: References: <20110724153647.349af575@mail.auth.se> Message-ID: <20110724182213.GC18023@micro.kristianpaul.co.cc> Why just you, explain it, and thats it.. let the mail list archive and internet bots to solve you worries for later. If somebody dont speak and said, "hey, think this can be done this way..." how you expect others to follow? > But I won't explain how to do it because anyone that would understand > those explanations enough to make something of it would already know > how to do it ... kind of a chicken and egg problem. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From miprom68 at gmail.com Sun Jul 24 18:37:45 2011 From: miprom68 at gmail.com (miprom68 at gmail.com) Date: Sun, 24 Jul 2011 14:37:45 -0400 Subject: IMEI numbers, signal strength In-Reply-To: <20110724153647.349af575@mail.auth.se> References: <20110724153647.349af575@mail.auth.se> Message-ID: Thanks! So, you're saying making an IMEI sniffer would not be easy? Seems like it'd be easier to get just the IMEI numbers from all phones in range than getting voice from just one. Ben On Sun, Jul 24, 2011 at 11:36 AM, mad wrote: > Hi Ben! > >> Anyone? >> >> On Fri, Jul 22, 2011 at 9:41 AM, ? wrote: >> > Can someone help with these? >> > 1) With the GSM debugger phone, how difficult is it to get only IMEI >> numbers >> > of received packets? > > First of all, it's unclear what exactly you mean by "the GSM debugger phone" as osmocom-bb is primary an implementation of a gsm stack like it's found in any standard cell phone. There is a debug output via gsmtap to e.g. wireshark where you see all received and send frames to/from your osmocom-bb. > Inherent to its hardware and open source approach it's possible to get it to dump frames received, independent of normal gsm operation. To do that at the moment it's necessary to do some work of your own, based on existing branches. > I will try to answer your questions based on what's theoretically possible. > > The IMEI is not send very often in conversations between phone and network, in fact the operator configures when (and if) it's requested from the phone. Practically some operators ?request it when doing an authentication request, others only when a location update using an IMSI happened. And I've never seen it transmitted in the clear, only after encryption started. So answering your question: Very difficult, exept you know the key, e.g. on your own phone and receive at the right moment. > >> > 2) Can the debugger phone report the signal strength of received packets? >> If >> > not, is it possible? > > Yes, the gsmtap output contains the signal strength on every frame. > >> > 3) Is there any way with mods to get I/Q out of the DSP? > > I'm not sure, I think Sylvain knows more about that. > >> > 4) Is there any work going on to make a CDMA debugger phone? > > As osmocom-bb is (yet) an explicit GSM stack, no. And I've not heard of approaches to do so > >> > 5) Are there any GSM phones that have an option to force calls to be made >> > only on 3G/4G? > > GSM phones are not capable to use 3G/4G networks. Certainly you mean 3G/4G phones and disallowing 2G/GSM fallback. I've not seen that in featurephones yet (but some may allow that) but I heard it's possible on jailbreaked iphones. You should find something by searching about that. > > > Regards, > ?Mad > > From mad at auth.se Sun Jul 24 20:49:19 2011 From: mad at auth.se (mad) Date: Sun, 24 Jul 2011 22:49:19 +0200 Subject: IMEI numbers, signal strength In-Reply-To: Message-ID: <20110724204919.053362ab@mail.auth.se> > Thanks! So, you're saying making an IMEI sniffer would not be easy? > Seems like it'd be easier to get just the IMEI numbers from all phones > in range than getting voice from just one. > As I said, the phones are not sending their IMEI around all the time, it's not like a MAC in a LAN. Just at specific points (which can be rare) in their interaction with the network they send it out over an encrypted channel. Regards, Mad From miprom68 at gmail.com Tue Jul 26 13:00:34 2011 From: miprom68 at gmail.com (miprom68 at gmail.com) Date: Tue, 26 Jul 2011 09:00:34 -0400 Subject: IMEI numbers, signal strength In-Reply-To: <20110724204919.053362ab@mail.auth.se> References: <20110724204919.053362ab@mail.auth.se> Message-ID: You guys are great. Next stupid question... I've read a lot about how secretive and insecure GSM is, but nothing about IS-95 (the CDMA 2G equivalent). Why not? It is more secure, or do not many phones support it anymore, or does it not have enough worldwide market penetration to be relevant? Ben On Sun, Jul 24, 2011 at 4:49 PM, mad wrote: >> Thanks! So, you're saying making an IMEI sniffer would not be easy? >> Seems like it'd be easier to get just the IMEI numbers from all phones >> in range than getting voice from just one. >> > > As I said, the phones are not sending their IMEI around all the time, it's not like a MAC in a LAN. Just at specific points (which can be rare) in their interaction with the network they send it out over an encrypted channel. > > > Regards, > ?Mad > From laforge at gnumonks.org Wed Jul 27 07:17:13 2011 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 27 Jul 2011 09:17:13 +0200 Subject: IS-95 / CDMA In-Reply-To: References: <20110724204919.053362ab@mail.auth.se> Message-ID: <20110727071713.GB32603@prithivi.gnumonks.org> On Tue, Jul 26, 2011 at 09:00:34AM -0400, miprom68 at gmail.com wrote: > I've read a lot about how secretive and insecure GSM is, but nothing > about IS-95 (the CDMA 2G equivalent). Why not? It is more secure, or > do not many phones support it anymore, or does it not have enough > worldwide market penetration to be relevant? Is that actually still used anywhere on this planet? I know that there are CDMA2K/EV-DO networks, but 2G CDMA? Also, the research always depends on the initiative of individuals. So far, all the people I know in the 'open GSM research' community tend to be from Europe, with a strong focus on Germany. OpenBTS folks are in the US, but their focus is not really that much on the security side. So if you want to do research in other mobile communications systems / protocols, by all means do so. It depends on people like you who have an interest in it to simply do it. osmocom.org would be more than happy to provide you with hosting, trac, git, etc. if you are going to work in that field. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From mazzi.teodolinda.gloria at gmail.com Fri Jul 22 15:48:40 2011 From: mazzi.teodolinda.gloria at gmail.com (Gloria Mazzi) Date: Fri, 22 Jul 2011 17:48:40 +0200 Subject: Some considerations about IMSI Detach DoS Attack Message-ID: Hi all, as stated on OsmocomSecurity: "A malicious attacker knowing the IMSI or TMSI of a victim can thus send hand-crafted IMSI DETACH messages to a cell, causing the network to assume the MS is no longer present in the network.This will effectively prevent the delivery of all mobile-terminated (MT) services, such as SMS, voice calls, CSD, ...". Following the theory i've better understood how it works [1]*, but still i have some questions for you: - what could happen if i will clone one SIM (Ki, IMSI) and use it to register on the same network, but on different BTS/LAC, two phones? Which will be rejected as first? Or both? - if i will send an IMSI detach with one of them... also the other (that is phisically in another BTS/LAC) will be disconnected? - what could happen if i will connect a C123 with ./mobile to the network using another SIM and then trying to forge IMSI_DET_IND with victim's IMSI/TMSI and send to the network where the victim is connected (that could mean the same network, but different BTS/LAC), this DoS will still be accomplished? What exactly i would like to know is, if someone already made some experiments on it (obviously on private networks, with a legal experimental license.) and eventually if there are any interesting results. Thank you for attention. Cheers Gloria *[1] - http://www.gsmfordummies.com/gsmevents/detach.shtml -------------- next part -------------- An HTML attachment was scrubbed... URL: From void at techberto.com Fri Jul 22 16:28:18 2011 From: void at techberto.com (Aleph) Date: Fri, 22 Jul 2011 13:28:18 -0300 Subject: Some considerations about IMSI Detach DoS Attack In-Reply-To: References: Message-ID: On Fri, Jul 22, 2011 at 12:48, Gloria Mazzi < mazzi.teodolinda.gloria at gmail.com> wrote: > Hi all, > > as stated on OsmocomSecurity: > "A malicious attacker knowing the IMSI or TMSI of a victim can thus send > hand-crafted IMSI DETACH messages to a cell, causing the network to assume > the MS is no longer present in the network.This will effectively prevent the > delivery of all mobile-terminated (MT) services, such as SMS, voice calls, > CSD, ...". > > Following the theory i've better understood how it works [1]*, but still i > have some questions for you: > > - what could happen if i will clone one SIM (Ki, IMSI) and use it to > register on the same network, but on different BTS/LAC, two phones? Which > will be rejected as first? Or both? > Both will go to a blacklist that will block new GSM Attach in the same HLR from carrer, unless you use the OpenBSC! :-) > - if i will send an IMSI detach with one of them... also the other (that is > phisically in another BTS/LAC) will be disconnected? > > ...if dettach is promoted by the HLR: Yes. If by the another side: not. > - what could happen if i will connect a C123 with ./mobile to the network > using another SIM and then trying to forge IMSI_DET_IND with victim's > IMSI/TMSI and send to the network where the victim is connected (that could > mean the same network, but different BTS/LAC), this DoS will still be > accomplished? > > there are protections in the HLR / VLR of the GSM System network. What exactly i would like to know is, if someone already made some > experiments on it (obviously on private networks, with a legal experimental > license.) and eventually if there are any interesting results. > > I personally, know the existign protections but I never did experiences or dared to do this kind of experiment in my country for legal reasons, but its the kind of thing I?d like to do withn legal parameters. My experiences were only in experimental networks in faraday cage. > > Thank you for attention. > > Cheers > > Gloria > > > > > > > > *[1] - http://www.gsmfordummies.com/gsmevents/detach.shtml > -- - .... . -... . ... - .-- .- -.-- - --- .--. .-. . -.. .. -.-. - - .... . ..-. ..- - ..- .-. . .. ... - --- .. -. ...- . -. - .. - .- .-.. .- -. -.- .- -.-- """ The best way to predict the future is to invent it , Alan Kay "" /* 0x42 0x69 0x74 0x20 0x46 0x61 0x6e */ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mazzi.teodolinda.gloria at gmail.com Fri Jul 22 17:52:47 2011 From: mazzi.teodolinda.gloria at gmail.com (Gloria Mazzi) Date: Fri, 22 Jul 2011 19:52:47 +0200 Subject: Some considerations about IMSI Detach DoS Attack In-Reply-To: References: Message-ID: Hi Aleph, >> - what could happen if i will clone one SIM (Ki, IMSI) and use it to >> register on the same network, but on different BTS/LAC, two phones? Which >> will be rejected as first? Or both? >> > > Both will go to a blacklist that will block new GSM Attach in the same HLR > from carrer, unless you use the OpenBSC! :-) > > >> - if i will send an IMSI detach with one of them... also the other (that >> is phisically in another BTS/LAC) will be disconnected? >> >> > ...if dettach is promoted by the HLR: Yes. If by the another side: not. > > >> - what could happen if i will connect a C123 with ./mobile to the network >> using another SIM and then trying to forge IMSI_DET_IND with victim's >> IMSI/TMSI and send to the network where the victim is connected (that could >> mean the same network, but different BTS/LAC), this DoS will still be >> accomplished? >> >> > there are protections in the HLR / VLR of the GSM System network. > Could you please suggest me some ETSI specs where i can find more infos about HLR/VLR's security policies to prevent DoS? > > What exactly i would like to know is, if someone already made some >> experiments on it (obviously on private networks, with a legal experimental >> license.) and eventually if there are any interesting results. >> >> > I personally, know the existign protections but I never did experiences or > dared to do this kind of experiment in my country for legal reasons, but its > the kind of thing I?d like to do withn legal parameters. My experiences were > only in experimental networks in faraday cage. > It would be really interesting to analyze its behaviour on real networks, unfortunately as you stated, is quite illegal without a previous authorization from the provider of a pubblic GSM network. Unfotunately i own only an USRP and OpenBTS doesn't have the full support of a pseudo HLR/VLR, so i cannot make further investigations about it. Which results did you reach with OpenBSC? Have you tried to forge some IMSI_DET_IND and trying to DoS other MS, camped to the same BTS? At the state of art, as i can see, this attack is more theorical than practical (i'm talking about real networks' applications). Or am i wrong? Thank you for attention. Cheers Gloria -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.chemeris at gmail.com Fri Jul 22 19:00:41 2011 From: alexander.chemeris at gmail.com (Alexander Chemeris) Date: Fri, 22 Jul 2011 23:00:41 +0400 Subject: Some considerations about IMSI Detach DoS Attack In-Reply-To: References: Message-ID: On Fri, Jul 22, 2011 at 19:48, Gloria Mazzi wrote: > Hi all, > > as stated on OsmocomSecurity: > "A malicious attacker knowing the IMSI or TMSI of a victim can thus send > hand-crafted IMSI DETACH messages to a cell, causing the network to assume > the MS is no longer present in the network.This will effectively prevent the > delivery of all mobile-terminated (MT) services, such as SMS, voice calls, > CSD, ...". > > Following the theory i've better understood how it works [1]*, but still i > have some questions for you: > > - what could happen if i will clone one SIM (Ki, IMSI) and use it to > register on the same network, but on different BTS/LAC, two phones? Which > will be rejected as first? Or both? I can't tell about this attack, but from my experience with using cloned SIM-cards in the real network, The last phone who did a call receives incoming calls. If this (last active) phone is turned off then the second phone doesn't receive incoming calls at all until it does something. And I think this is a natural behavior, because it may happen that some phone loose its battery, then you take SIM off and insert in an other phone, and it should work - and the case with two cloned SIM-cards looks about the same to an operator. PS To make it clear, I cloned my own SIM-cards, because I used multi-SIM card with several numbers on a single SIM. So nothing really illegal. -- Regards, Alexander Chemeris. From mazzi.teodolinda.gloria at gmail.com Fri Jul 22 20:55:57 2011 From: mazzi.teodolinda.gloria at gmail.com (Gloria Mazzi) Date: Fri, 22 Jul 2011 22:55:57 +0200 Subject: Some considerations about IMSI Detach DoS Attack In-Reply-To: References: Message-ID: Hi Alexander, > PS To make it clear, I cloned my own SIM-cards, because I used > multi-SIM card with several numbers on a single SIM. So nothing really > illegal. > Thank you for the infos. I wanted to make the same experiments, unfortunately all providers in my country are no more providing "weak and clonable" SIMs. Which provider's SIMs did you used for that? Is it still possible with some providers around Europe that i could use with roaming procedures? Thank you again for attention. Cheers Gloria -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Fri Jul 22 21:23:56 2011 From: 246tnt at gmail.com (Sylvain Munaut) Date: Fri, 22 Jul 2011 23:23:56 +0200 Subject: Some considerations about IMSI Detach DoS Attack In-Reply-To: References: Message-ID: > - what could happen if i will clone one SIM (Ki, IMSI) and use it to > register on the same network, but on different BTS/LAC, two phones? Which > will be rejected as first? Or both? If you do that, it will send a LOC.UPD.REQ in another LAC ... which is exactly the same as if you moved your phone to that LAC ... it's a perfectly valid situation and it's fully specified. Only the latest registration is valid. > - if i will send an IMSI detach with one of them... also the other (that is > phisically in another BTS/LAC) will be disconnected? As mentionned above : Only one can be active at a time. (the latest location update), so ... not applicable. > - what could happen if i will connect a C123 with ./mobile to the network > using another SIM and then trying to forge IMSI_DET_IND with victim's > IMSI/TMSI and send to the network where the victim is connected (that could > mean the same network, but different BTS/LAC), this DoS will still be > accomplished? Only the behavior if the message is sent in the same LAC is specified. What happens in other situation is implementation dependent. Some network will detach, others won't ... no way to tell and neither behavior is "wrong" per-spec. Most will simply ignore the message. Some will accept it ... Note that the network can also be configured not to use the detact procedure at all and then ignores all detach messages. What happens when a detach is sent _while_ a call is active on the target is also dependent. Some network (including my home network) instantly disconnect the active call. Some other networks don't ... > What exactly i would like to know is, if someone already made some > experiments on it (obviously on private networks, with a legal experimental > license.) and eventually if there are any interesting results. It's been tested on commercial networks (with consenting targets obviously) and it works exactly as expected. And since we're only sending perfectly formed/valid messages to the network, there shouldn't be a problem. The issue here is not a bug, it's a specified behavior / messages that can be exploited. Cheers, Sylvain From matzikratzi at gmail.com Mon Jul 25 06:08:13 2011 From: matzikratzi at gmail.com (Matzi Kratzi) Date: Mon, 25 Jul 2011 08:08:13 +0200 Subject: positioning Message-ID: (In a sort-of-answer to the triangulating mail a while ago:) > i wanted to know is it possible to triangulate any gsm cellphone with osmocombb?? Hi, It would be possible triangulate your own position using osmocombb. Assumption 1 (A1): The base stations of GSM are very stable and can keep running for months or years without interruption. Assumption 2 (A2): Osmocombb has a free running quarter bit counter that it never restarts when power is on. The timings of different cells are calculated relative to this free running counter. To be able to triangulate a phone, we need information about the cells in the area: The GSM TDMA system has a periodicity for broadcasted messages such as sync and SI1. The timing of these can be predetermined as an offset relative to the free running counter in A2. Note that the offset includes the propagation time for the signal from the base station to the mobile station. If the position of the mobile phone with osmocombb (MS) is known, one can get the offset for the first base station broadcasts (dt_BS1). If the MS is moved later to at least three other known positions and the same offsets are calculated, one can calculate the actual offset between the MS free running counter and the BS1 without the propagation time included. At the same time the actual position of the BS is calculated. [1] An MS should do measurements on neighbour cells as well, and can therefor do exactly the same calculations for several BS:s at the same time. An interesting aspect of this is that it is then possible to calculate the difference in timing for several BS:s. If the positions and relative timings for the BS:s in an area are known, it is possible to calculate the position of an MS. This time we do the same calculations, but now the relative timings for the BS:s and the position are known and the same for the MS is unknown. An interesting fact is that osmocombb could use the timings for BS:s from several operators to increase the accuracy of the calculations. Assumption 1 can be held for granted. Assumption 2 could be made true if it is not already true. The concept could probably otherwise be used anyway if that is not accepted. 1 http://en.wikipedia.org/wiki/Multilateration MS Mobile station (phone, modem) BS Base station dt_BSx timing offset from the free running timer to base station number x /Matzi From ibruno.macintosh at gmail.com Tue Jul 26 21:00:00 2011 From: ibruno.macintosh at gmail.com (iBruno) Date: Tue, 26 Jul 2011 22:00:00 +0100 Subject: Tx Support Message-ID: <955A5438-1637-4708-9180-109C4D70A419@gmail.com> Hello community After making the changes to Makefile.inc (src/target/firmware) -include Makefile.inc # Uncomment this line if you want to enable Tx (Transmit) Support. -CFLAGS += -DCONFIG_TX_ENABLE +CFLAGS += -DCONFIG_TX_ENABLE # Uncomment this line if you want to write to flash. #CFLAGS += -DCONFIG_FLASH_WRITE I'm trying to figure out, what to do with this part: enable CONFIG_TX_ENABLE diff --git a/src/target/firmware/Makefile b/src/target/firmware/Makefile index 56e0068..c69aab7 100644 --- a/src/target/firmware/Makefile +++ b/src/target/firmware/Makefile @@ -73,7 +73,7 @@ ANY_APP_LIBS+=calypso/libcalypso.a layer1/liblayer1.a lib/libmini.a comm/libcomm ...Meanwhile I tried to compile, and at the time Makefile.inc is callled starts looping forever.... Makefile.inc:135: warning: overriding commands for target `board/compal_e99/loader.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/loader.highram.size' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.map' Makefile.inc:135: warning: overriding commands for target `board/gta0x/loader.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/loader.highram.size' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.map' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/loader.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/loader.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88loader.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88loader.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/simtest.e88flash.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/simtest.e88flash.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/gta0x/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.map' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/simtest.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/simtest.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88loader.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88loader.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e88/chainload.e88flash.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e88/chainload.e88flash.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e86/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e86/chainload.highram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.compalram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.compalram.size' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/compal_e99/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/compal_e99/chainload.highram.size' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/gta0x/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/gta0x/chainload.highram.size' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.manifest.o' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.manifest.o' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.manifest.p' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.manifest.p' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.elf' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.elf' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.map' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.map' Makefile.inc:135: warning: overriding commands for target `board/pirelli_dpl10/chainload.highram.size' Makefile.inc:135: warning: ignoring old commands for target `board/pirelli_dpl10/chainload.highram.size' Makefile.inc:171: warning: overriding commands for target `calypso/libcalypso.a' Makefile.inc:171: warning: ignoring old commands for target `calypso/libcalypso.a' Makefile.inc:171: warning: overriding commands for target `layer1/liblayer1.a' Makefile.inc:171: warning: ignoring old commands for target `layer1/liblayer1.a' Makefile.inc:171: warning: overriding commands for target `comm/libcomm.a' Makefile.inc:171: warning: ignoring old commands for target `comm/libcomm.a' Makefile.inc:171: warning: overriding commands for target `lib/libmini.a' Makefile.inc:171: warning: ignoring old commands for target `lib/libmini.a' Makefile.inc:208: warning: overriding commands for target `clean' Makefile.inc:208: warning: ignoring old commands for target `clean' Makefile.inc:212: warning: overriding commands for target `distclean' Makefile.inc:212: warning: ignoring old commands for target `distclean' ^Cmake: *** [firmware] Interrupt After reviewing the groups & googing, didn't came out with understanding/solution Very appreciated, if help can be given. Thank you Bruno. -------------- next part -------------- An HTML attachment was scrubbed... URL: From BRYAN.P.BRUCE at saic.com Wed Jul 27 20:10:42 2011 From: BRYAN.P.BRUCE at saic.com (Bruce, Bryan) Date: Wed, 27 Jul 2011 16:10:42 -0400 Subject: C115 using loader.compalram.bin Message-ID: <126AF9962F74524C937DFF9F47B0A3380381A903@0905-its-exmp01.us.saic.com> Hello, I am using a C115 with a t191 cable. We have completed the "Getting Started" steps and have compiled all the necessary code. I are currently trying to run osmocon to download code onto the phone. The following output appears when we run the script: bruceb at ubuntu:~/osmocom-bb/src/host/osmocon$ ./osmocon -p /dev/ttyUSB0 -m c123xor ../../target/firmware/board/compal_e88/loader.compalram.bin got 1 bytes from modem, data looks like: 2d - got 1 bytes from modem, data looks like: 34 4 got 1 bytes from modem, data looks like: 29 ) got 1 bytes from modem, data looks like: 28 ( got 1 bytes from modem, data looks like: 32 2 got 1 bytes from modem, data looks like: 39 9 got 1 bytes from modem, data looks like: 30 0 got 1 bytes from modem, data looks like: 20 got 1 bytes from modem, data looks like: 2d - got 1 bytes from modem, data looks like: 34 4 got 1 bytes from modem, data looks like: 29 ) got 1 bytes from modem, data looks like: 0a . got 1 bytes from modem, data looks like: 0d . got 1 bytes from modem, data looks like: 02 . These lines continue and no script indicates anything is being downloaded, as shown on the wiki site. I have unlocked the phone and put it in "earphone" mode beforehand. I have also tried to press the power button as directed to. Are there any suggestions on how to fix this problem? Thank you, Bryan Bruce -------------- next part -------------- An HTML attachment was scrubbed... URL: From benny at benny.de Thu Jul 28 08:44:25 2011 From: benny at benny.de (Benjamin Hagemann) Date: Thu, 28 Jul 2011 10:44:25 +0200 Subject: OT: GTA04 - Openmoko Message-ID: <20110728084424.GT5941@quelle.benny.de> Hello, a german news website gave me the hint to new infos about the GTA04. english sites: http://projects.goldelico.com/p/gta04-main/ http://lists.goldelico.com/pipermail/gta04-owner/2011-July/000185.html http://www.handheld-linux.com/wiki.php?page=GTA04-Early-Adopter&referer=Neo%20Freerunner and the german news about this topic: pro-linux: OpenMoko GTA04 bald bereit zum Test http://www.pro-linux.de/news/1/17318/openmoko-gta04-bald-bereit-zum-test.html -- Have a nice day, Benny gpg 0xFC505AB0 jabber benny at benny.de sip benny at benny.de -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 190 bytes Desc: Digital signature URL: From laforge at gnumonks.org Thu Jul 28 15:36:25 2011 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 28 Jul 2011 17:36:25 +0200 Subject: OT: GTA04 - Openmoko In-Reply-To: <20110728084424.GT5941@quelle.benny.de> References: <20110728084424.GT5941@quelle.benny.de> Message-ID: <20110728153625.GF30053@prithivi.gnumonks.org> Hi Benjamin, On Thu, Jul 28, 2011 at 10:44:25AM +0200, Benjamin Hagemann wrote: > http://projects.goldelico.com/p/gta04-main/ thanks a lot. However, just for the record: GTA04 is not about any kind of Free / Open Source Software for the baseband processor of the mobile phone. While they are liberating the hardware design and software for the application processor side, the GSM/3G module is a regular off-the-shelf component. I'm not saying that this is something bad or that it is a problem for me. In fact, what the GTA04 folks have been pulling off is a lot of work... Having done significant work on GTA01 / GTA02 hardware, bring-up and system-level software myself, I think I can definitely appreciate the work they are doing. However, as far as OsmocomBB is concerned, it is out of scope and unrelated. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)