From laforge at gnumonks.org Thu May 2 20:17:23 2013 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 2 May 2013 22:17:23 +0200 Subject: Feedback on micro-SIM (3ff) FPC adapter cables Message-ID: <20130502201723.GI8786@nataraja.gnumonks.org> Hi all, as we are getting more and more inquiries for micro-SIM (3FF) FPC adapters for the SIMtrace, I would like to inquire on this list before we go into productin. My main inquiry is about the orientation. As you know, the current mini-SIM adapters come in four flavors, one for each of the possible orientations. Hoewever, as there are still few phones with 3FF SIM card support, I was hoping we don't need to produce 3FF FPC adapter cables for all four orientations. Does anyone on this list know which orientations exist and which don't? This would help us to proceed quickly with manufacturing the adapters, without spending extensive amounts of time researching on required orientations. 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 laforge at gnumonks.org Thu May 2 20:13:25 2013 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 2 May 2013 22:13:25 +0200 Subject: SIMtrace Hardware Kit (Sysmocom) In-Reply-To: <9C29799BF6A61B44996B87F1F1C8B152064FB63D@uomail.upgrade.local> References: <9C29799BF6A61B44996B87F1F1C8B152064FB63D@uomail.upgrade.local> Message-ID: <20130502201325.GH8786@nataraja.gnumonks.org> Dear Joe, On Tue, Apr 30, 2013 at 12:02:09PM +0100, Joe Loxley wrote: > I was wondering where I would be able to the following item, if it is > through yourselves then please can I obtain a quote for 1 unit. the simtrace mailing list to which you have sent this message is a message for the developer community of the product. SIMtrace hardware is made available by sysmocom in the web shop at https://shop.sysmocom.de/ FYI: As it is an open hardware design, anyone is free to take the schematics, BOM and PCB layout files from the simtrace.git repository and manufacture their own devices, free of any royalties. 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 kevredon at mail.tsaitgaist.info Sat May 4 17:09:18 2013 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Sat, 04 May 2013 10:09:18 -0700 Subject: Feedback on micro-SIM (3ff) FPC adapter cables In-Reply-To: <20130502201723.GI8786@nataraja.gnumonks.org> References: <20130502201723.GI8786@nataraja.gnumonks.org> Message-ID: <1367686941-sup-5278@dennou> for "normal sim" the most frequent I use is with the cable on the short cornered side ---- | |--- ---/ but the reverse one is the second most frequent I have 2 old phones which use the longer side for the cable --- | |-- --/ but have never used the reverse one. for micro-sim, I have only seen 2 versions used (cable on the shorter sides) kevin Excerpts from Harald Welte's message of 2013-05-02 13:17:23 -0700: > Hi all, > > as we are getting more and more inquiries for micro-SIM (3FF) FPC > adapters for the SIMtrace, I would like to inquire on this list before > we go into productin. > > My main inquiry is about the orientation. As you know, the current > mini-SIM adapters come in four flavors, one for each of the possible > orientations. Hoewever, as there are still few phones with 3FF SIM > card support, I was hoping we don't need to produce 3FF FPC adapter > cables for all four orientations. > > Does anyone on this list know which orientations exist and which don't? > This would help us to proceed quickly with manufacturing the adapters, > without spending extensive amounts of time researching on required > orientations. > > Regards, > Harald From Lena at ftw.at Tue May 21 13:53:45 2013 From: Lena at ftw.at (=?ISO-8859-1?Q?Arthur_L=E9na?=) Date: Tue, 21 May 2013 15:53:45 +0200 Subject: Incomplete trace (due to high-speed SIM?) Message-ID: <519B7C69.7000707@ftw.at> Hello. I am trying to trace the communication between a Free Mobile (french operator) and an iPhone 4S. I am using the simtrace tool and libosmocore library taken from the Ubuntu PPA repository given in the user manual (ppa:holger+lp/osmocom). I tried booting the iPhone using 2 different SIMs (this one from Free Mobile and another one) and the trace seems very short using the Free Mobile in comparison to the other one. By parsing the ATRs of both SIMs, I found out that the communication is done at 312500 bits/s with the Free Mobile SIM and only 78125 bits/s (for a clock running at 5MHz). Could this explain the loss of entire ADPUs by the tracer? If yes, is there a way to remedy to this problem (firmware update for example). Best regards, Arthur L?na FYI: the ATRS of both SIM cards Free Mobile: 3B 9E 96 80 1F C7 80 31 E0 73 FE 21 1B 66 D0 01 77 97 0D 00 EC TA(1) = 0x96 Fi=512, Di=32, 16 cycles/ETU (250000 bits/s at 4.00 MHz, 312500 bits/s for fMax=5 MHz) A1: 3B 3F 94 00 80 69 AF 03 0F 07 A4 00 00 06 0E 83 3E 9F 16 TA(1) = 0x94 Fi=512, Di=8, 64 cycles/ETU (62500 bits/s at 4.00 MHz, 78125 bits/s for fMax=5 MHz) From holger at freyther.de Wed May 22 10:23:01 2013 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Wed, 22 May 2013 12:23:01 +0200 Subject: Incomplete trace (due to high-speed SIM?) In-Reply-To: <519B7C69.7000707@ftw.at> References: <519B7C69.7000707@ftw.at> Message-ID: <20130522102301.GP14728@xiaoyu.lan> On Tue, May 21, 2013 at 03:53:45PM +0200, Arthur L?na wrote: > I tried booting the iPhone using 2 different SIMs (this one from > Free Mobile and another one) and the trace seems very short using > the Free Mobile in comparison to the other one. By parsing the ATRs > of both SIMs, I found out that the communication is done at 312500 > bits/s with the Free Mobile SIM and only 78125 bits/s (for a clock > running at 5MHz). Could this explain the loss of entire ADPUs by the > tracer? If yes, is there a way to remedy to this problem (firmware > update for example). Some people reported success by reducing the size of buffered bytes in the firmware. holger