From luca.bongiorni1 at studenti.unimi.it Fri May 6 10:27:11 2011 From: luca.bongiorni1 at studenti.unimi.it (Luca Bongiorni) Date: Fri, 06 May 2011 12:27:11 +0200 Subject: No subject Message-ID: <7450b565249bb.4dc3e91f@studenti.unimi.it> From kevredon at mail.tsaitgaist.info Fri May 6 12:44:07 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Fri, 06 May 2011 14:44:07 +0200 Subject: SPI flash In-Reply-To: <20110506093426.GB5155@prithivi.gnumonks.org> References: <20110506093426.GB5155@prithivi.gnumonks.org> Message-ID: <4DC3ED17.1010908@mail.tsaitgaist.info> Hi, I never tried WSON, but I think it's still possible to solder it. To do it (as most of the smd), I use a heating plate and a hot air gun (with soldering paste), and not a soldering iron. So it might also work with this package. But the SOIC package is easier for others. Even it's it two time the price, it's not too expensive. So you can choose any. Kevin On 06.05.2011 11:34, Harald Welte wrote: > Hi! > > I think one of the big concerns is to use components that can still be > soldered manually (like SOIC-8). All the larger-than-32MBit (4MByte) > SPI flashes that I could find were in smaller cases with no leads > extending from the case (like WSON). > > This one looks fine to me, and is available from digikey: > http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=SST25VF032B-80-4I-S2AF-ND > datasheet: http://ww1.microchip.com/downloads/en/DeviceDoc/S71327_04.pdf > > Regards, > Harald > From kevredon at mail.tsaitgaist.info Sat May 7 20:12:23 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Sat, 07 May 2011 22:12:23 +0200 Subject: SIMtrace v0.6 schema Message-ID: <4DC5A7A7.20601@mail.tsaitgaist.info> Hi, here the schema. all the components are on it, but I don't know if the electrical part is right. Any comments/advices are welcome. schema : https://gsm.tsaitgaist.info/SIMtrace/v0.6/SIMtrace.ps source (KiCAD) : https://gsm.tsaitgaist.info/SIMtrace/v0.6/ From philipp.maier at runningserver.com Sat May 7 21:34:49 2011 From: philipp.maier at runningserver.com (Philipp Fabian Benedikt Maier) Date: Sat, 07 May 2011 23:34:49 +0200 Subject: SIMtrace v0.6 schema In-Reply-To: <4DC5A7A7.20601@mail.tsaitgaist.info> References: <4DC5A7A7.20601@mail.tsaitgaist.info> Message-ID: <4DC5BAF9.3040306@runningserver.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Kevin. > here the schema. > all the components are on it, but I don't know if the electrical part is > right. > Any comments/advices are welcome. > > schema : > https://gsm.tsaitgaist.info/SIMtrace/v0.6/SIMtrace.ps > source (KiCAD) : > https://gsm.tsaitgaist.info/SIMtrace/v0.6/ I took a look at your shema, here are my thoughts: The SC_SW line controls all analog switch pins. I think you should be a bit more selective here. To create a situation like this for example: VCC, RST, CLK are connected through and I/O is connected to the man in the middle who can manipulate the traffic in realtime. I have looked at the QS3245 datasheet. It has only one OE input pin ;-/ With your current design you will have do generate the smartcard clock yourself, you could use the clock from the target (with care!) when you can switch at least I/O seperatly. You can leave the VPP away, it is deprecated. (save PCB-Space ;-) Maybe you can leave Jtag away (save even more PCB-Space ;-) the AT91SAM7 series have fancy bootloaders - but maybe you will need the JTAG for debugging so it is your decision. You should give the BATT-PWR/USB-PWR construct a short test. Maybe it is problematic when one power source drives into another that is switched off. regards. Philipp - -- ______________________________________ Philipp Fabian Benedikt Maier philipp.maier at runningserver.com Funk: DO5DXT http://www.runningserver.com http://www.diskettenschlitz.de ______________________________________ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNxbr1AAoJECnygI88j3oSzkkIAIvD77CZfOKHcnwmsZf5lWOH yBfRdjVkEMNmx0y4NIzDRd/XyiPgbSKGfRAvuxqZ9CXYT5xrD+vli6i0r8HeY+Lf YcS/onQmFjsE8X7s9+6mcgek8RembqO3nbxh2vo05bilLQ4zAdNDfIwiKhL2JF5o rxiD3+xjgywWb46uyspHpjOm8hAQJkP7TxRtMJ60OqbzTx2B7nyIf/Z+u5idaJqH IiYmttmEng3kJ1DP0Larlvobw9bG6WY8CTXvae2K1Y87qWzeuKkIAN0/2Dqig7lV dNG3n4vHlnHZfS6iIxHfaL4cJ+TjH18yn+T48j7SXptlMfklTloEHvlb0t7tqeY= =ARUX -----END PGP SIGNATURE----- From roh at hyte.de Sun May 8 07:17:34 2011 From: roh at hyte.de (Joachim Steiger) Date: Sun, 08 May 2011 09:17:34 +0200 Subject: subscribe Message-ID: <4DC6438E.1090006@hyte.de> From laforge at gnumonks.org Sun May 8 09:55:02 2011 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 8 May 2011 11:55:02 +0200 Subject: SIMtrace v0.6 schema In-Reply-To: <4DC5A7A7.20601@mail.tsaitgaist.info> References: <4DC5A7A7.20601@mail.tsaitgaist.info> Message-ID: <20110508095502.GF16877@prithivi.gnumonks.org> Hi Kevin, thanks for posting your most recent schematics. On Sat, May 07, 2011 at 10:12:23PM +0200, Kevin Redon wrote: > here the schema. > all the components are on it, but I don't know if the electrical part is > right. > Any comments/advices are welcome. 1) Regarding dexters mail: I defintely would want JTAG, it helps a lot for debugging. We don't have to solder the connector for production units after R&D has finished. 2) It might be an idea to use a 2.5mm jack (like Compal phones) for the DBGU, instead of the FTDI-6pin-header. I guess more people in and around the Osmocom projects have a T191 cable than a FT232 cable with the 6-pin header. What do the others think? It may be worth putting both footprints (for the 6-pin cable and the 2.5mm jack) on the PCB. This way we can later still decide which one to place on the board. 3) It might be nice to have an ADC input connected to the VCC_OUT line, to be able to measure the SIM card supply voltage as it is output by the phone. ADCREF of course would have to be connected, too. 4) It is generally good 'style' to connect the nWP to some I/O line of the CPU (together with a pull-down). This way the memory is write-protected by default. Only if the CPU sets the GPIO to high, it can write to the flash. 5) I think the IN/OUT naming is a bit misleading. E.g. "VCC_OUT" is the source of the VCC power, i.e. the phone. It may be better to call the signals leading to the phone {VPP,I/O,CLK,RST,VCC}_PHONE and the signals leading to the sim {VPP,I/O,CLK,RST,VCC}_SIM 6) The USB pull-up mechanism is missing. This is required for properly signalling a USB bus reset to the host controller. Please refer to the OpenPCD schematics for an example circuit. It just requires one transistor and some resistors. It has also proven useful to connect the nRESET to that pull-up circuit to make sure a cpu-reset leads to a bus reset as well. 7) A 5.6V Zener diode makes sense as over-voltage protection at the USB 5V power supply line 8) The two 47uF capacitors at the 3.3V line and the 22uF capacitor at the 5V line might be above the USB specifications for capacitive load. See Section 7.2.4.1 of the USB spec, where I believe it says you can only put a cumulative capacitance of 10uF at the downstream end of a Vbus. We might ignore that, or use something like a LM3525 (or even a TI TPS2151 which is a LDO with built-in in-rush current limiter). OpenPCD1 v0.4 is not being sold anymore exactly due to this problem. 9) I would only use a jumper for the TEST singal, as we probably only need it very rarely during sam7dfu testing/porting. After that, we will use USB DFU for updates 10) However, it is useful to have a push-button for DFU-mode activation, this is a simple switch between Vcc and a GPIO. Normally, DFU is activated over USB itself. However, if the firmware is dead, this BOOTLOADER switch can help with recovery (once again, see OpenPCD) 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 Sun May 8 11:40:46 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Sun, 08 May 2011 13:40:46 +0200 Subject: SIMtrace v0.6 schema In-Reply-To: <20110508095502.GF16877@prithivi.gnumonks.org> References: <4DC5A7A7.20601@mail.tsaitgaist.info> <20110508095502.GF16877@prithivi.gnumonks.org> Message-ID: <4DC6813E.5050807@mail.tsaitgaist.info> Thanks for the fast analysis > > 2) It might be an idea to use a 2.5mm jack (like Compal phones) for the > DBGU, instead of the FTDI-6pin-header. I guess more people in and > around the Osmocom projects have a T191 cable than a FT232 cable with > the 6-pin header. What do the others think? I would choose jack 2.5 only, but I will put both. > > 3) It might be nice to have an ADC input connected to the VCC_OUT line, > to be able to measure the SIM card supply voltage as it is output > by the phone. ADCREF of course would have to be connected, too. I will add it. > > 4) It is generally good 'style' to connect the nWP to some I/O line of > the CPU (together with a pull-down). ack > 5) I think the IN/OUT naming is a bit misleading. E.g. "VCC_OUT" is the > source of the VCC power, i.e. the phone. It may be better to call > the signals leading to the phone {VPP,I/O,CLK,RST,VCC}_PHONE and the > signals leading to the sim {VPP,I/O,CLK,RST,VCC}_SIM ack > > 6) The USB pull-up mechanism is missing. This is required for properly > signalling a USB bus reset to the host controller. Please refer to > the OpenPCD schematics for an example circuit. It just requires one > transistor and some resistors. It has also proven useful to connect > the nRESET to that pull-up circuit to make sure a cpu-reset leads to > a bus reset as well. > > 7) A 5.6V Zener diode makes sense as over-voltage protection at the USB > 5V power supply line I will have a look for it > > 8) The two 47uF capacitors at the 3.3V line and the 22uF capacitor at > the 5V line might be above the USB specifications for capacitive > load. See Section 7.2.4.1 of the USB spec, where I believe it says > you can only put a cumulative capacitance of 10uF at the downstream > end of a Vbus. We might ignore that, or use something like a > LM3525 (or even a TI TPS2151 which is a LDO with built-in in-rush > current limiter). OpenPCD1 v0.4 is not being sold anymore exactly > due to this problem. didn't know than, I will change the ld1117 with a tps73633 (less expensive then TPS2151, and fits perfectly). I don't understand why the capacitor at the 3.3v line affect USB, but I will minimize it. > > 9) I would only use a jumper for the TEST singal, as we probably only > need it very rarely during sam7dfu testing/porting. After that, we > will use USB DFU for updates ack > > 10) However, it is useful to have a push-button for DFU-mode activation, > this is a simple switch between Vcc and a GPIO. Normally, DFU is > activated over USB itself. However, if the firmware is dead, this > BOOTLOADER switch can help with recovery (once again, see OpenPCD) I will take the openPCD design > > Regards, > Harald WiP, Kevin From kevredon at mail.tsaitgaist.info Sun May 8 15:00:59 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Sun, 08 May 2011 17:00:59 +0200 Subject: SIMtrace v0.7 Message-ID: <4DC6B02B.6070208@mail.tsaitgaist.info> Hi The corrections have been applied. I hope I did not forget anything. The main changes : - reset is a jumper - bootloader switch added - 100k resistors used (instead of 4.7k, I hope it does not break anything) - jack connector added (for the debug) - WP from flash connected - USB voltage regulator TPS73633 used (lower capacitance) - USB buffer used instead of the openPCB solution (thus no pull-up and reset connection). saves space and complexity - pin renamed - QS3244 instead of QS3245 used, I/O and other pins are controlled separately - ... To make the changes I used the AT91SAM7X-EK Evaluation Board User Guide. The overall capacitance is reduced, but I think the 22uF for the battery should be kept. files : https://gsm.tsaitgaist.info/SIMtrace/v0.7/ good luck, Kevin From kevredon at mail.tsaitgaist.info Sun May 8 17:02:57 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Sun, 08 May 2011 19:02:57 +0200 Subject: softSIM Message-ID: <4DC6CCC1.50705@mail.tsaitgaist.info> Hi, softSIM is out : http://bb.osmocom.org/trac/wiki/softSIM It's not fully implemented but already working (I hope). The osmocomBB use/cooperation will come out soon. Other tools are coming next week (I need to clean them). Have fun, tsaitgaist From laforge at gnumonks.org Sun May 8 17:55:36 2011 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 8 May 2011 19:55:36 +0200 Subject: SIMtrace v0.6 schema In-Reply-To: <4DC6813E.5050807@mail.tsaitgaist.info> References: <4DC5A7A7.20601@mail.tsaitgaist.info> <20110508095502.GF16877@prithivi.gnumonks.org> <4DC6813E.5050807@mail.tsaitgaist.info> Message-ID: <20110508175536.GB11457@prithivi.gnumonks.org> Hi Kevin, On Sun, May 08, 2011 at 01:40:46PM +0200, Kevin Redon wrote: > > 2) It might be an idea to use a 2.5mm jack (like Compal phones) for the > > DBGU, instead of the FTDI-6pin-header. I guess more people in and > > around the Osmocom projects have a T191 cable than a FT232 cable with > > the 6-pin header. What do the others think? > > I would choose jack 2.5 only, but I will put both. ok, thanks. > > 8) The two 47uF capacitors at the 3.3V line and the 22uF capacitor at > > the 5V line might be above the USB specifications for capacitive > > load. See Section 7.2.4.1 of the USB spec, where I believe it says > > you can only put a cumulative capacitance of 10uF at the downstream > > end of a Vbus. We might ignore that, or use something like a > > LM3525 (or even a TI TPS2151 which is a LDO with built-in in-rush > > current limiter). OpenPCD1 v0.4 is not being sold anymore exactly > > due to this problem. > > didn't know than, I will change the ld1117 with a tps73633 (less > expensive then TPS2151, and fits perfectly). ok. > I don't understand why the capacitor at the 3.3v line affect USB, but I > will minimize it. The problem is that in power-on, the capacitive load on the 3.3V side normally also becomes visible as a capacitive load on the 5V side (as the regulator basically is 'switched through' at the moment you have the raising edge of supply power. > > 10) However, it is useful to have a push-button for DFU-mode activation, > > this is a simple switch between Vcc and a GPIO. Normally, DFU is > > activated over USB itself. However, if the firmware is dead, this > > BOOTLOADER switch can help with recovery (once again, see OpenPCD) > > I will take the openPCD design If you look at the OpenPCD design, the I/O pin has a pull-down, and the switch goes to Vcc. In your v0.7 schematics you now have no pull-down and a series resistor for Vcc. I think we should use the OpenPCD way as it is known working. -- - 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 Sun May 8 18:04:29 2011 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 8 May 2011 20:04:29 +0200 Subject: SIMtrace v0.7 In-Reply-To: <4DC6B02B.6070208@mail.tsaitgaist.info> References: <4DC6B02B.6070208@mail.tsaitgaist.info> Message-ID: <20110508180429.GC11457@prithivi.gnumonks.org> On Sun, May 08, 2011 at 05:00:59PM +0200, Kevin Redon wrote: > Hi > > The corrections have been applied. I hope I did not forget anything. thanks a lot. > The main changes : > - reset is a jumper just to be precies: it's the TEST pin, not RESET (schematics is ok!) > - bootloader switch added see my comment from the last mail > - 100k resistors used (instead of 4.7k, I hope it does not break anything) yes, it should work. and if we run into problems, it's very easy to solder different resistors to the same footprint. > - jack connector added (for the debug) > - WP from flash connected great. Does the SAM7 have an internal pull-down on nWP? If not, we should add one, just to be sure the power-up default state is LOW. > - USB voltage regulator TPS73633 used (lower capacitance) Ok, let's try that one. > - USB buffer used instead of the openPCB solution (thus no pull-up and > reset connection). saves space and complexity I am not familiar with USB buffers? How do they work? I couldn't find a data sheet for USBBUF02 or USBBUF02W6. Also, I don't see how this solves the problem, sorry. Some more explanation: When the AT91SAM7 is reset (software-reset or hardware-reset), it needs to generate a USB bus reset in order to tell the host PC to re-enumerate. This is required as the SAM7 has no information about the USB protocol state before the ARM CPU was reset. The other reason is: When we switch from DFU into normal mode (or the other way around), we again need to be able to issue a USB reset from software (via GPIO) and ask the host to re-enumerate. This is required as we expose different interface/configuration descriptors depending on DFU / normal mode. So I don't really see a choice but to have a software-controlled USB reset option. Once again, we know that this part is working in OpenPCD 0.4 (we had a couple of earlier versions, and they all had some shortcomings). It's really useful to have both the nRESET as well as the GPIO controlled usb-pullup (called UDP_PUP) in OpenPCD. If we don't do this properly, we will have to disconnect/reconnect the device from USB very often. Doing this from software is much easier and fail-proof. > - QS3244 instead of QS3245 used, I/O and other pins are controlled > separately great. -- - 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 Mon May 9 08:35:54 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Mon, 09 May 2011 10:35:54 +0200 Subject: SIMtrace v0.7 In-Reply-To: <20110508180429.GC11457@prithivi.gnumonks.org> References: <4DC6B02B.6070208@mail.tsaitgaist.info> <20110508180429.GC11457@prithivi.gnumonks.org> Message-ID: <4DC7A76A.8040506@mail.tsaitgaist.info> corrections added : https://gsm.tsaitgaist.info/SIMtrace/v0.7+/ >> - bootloader switch added > > see my comment from the last mail pull-down added >> - jack connector added (for the debug) >> - WP from flash connected > > great. Does the SAM7 have an internal pull-down on nWP? If not, we > should add one, just to be sure the power-up default state is LOW. pull-down added > > I am not familiar with USB buffers? How do they work? It's not a buffer (just me not knowing what I do). It's just and emi filter, replacing the R and C for the USB. > > So I don't really see a choice but to have a software-controlled USB > reset option. Once again, we know that this part is working in OpenPCD > 0.4 (we had a couple of earlier versions, and they all had some > shortcomings). It's really useful to have both the nRESET as well as > the GPIO controlled usb-pullup (called UDP_PUP) in OpenPCD. That is the part I never understood in openPCD. What was the purpose of USB_PUP ? Now I understand (finally). Thus I did the same as openPCD now. Waiting for next corrections, Kevin From kevredon at mail.tsaitgaist.info Mon May 9 08:41:23 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Mon, 09 May 2011 10:41:23 +0200 Subject: SIMtrace v0.7 In-Reply-To: <4DC7A76A.8040506@mail.tsaitgaist.info> References: <4DC6B02B.6070208@mail.tsaitgaist.info> <20110508180429.GC11457@prithivi.gnumonks.org> <4DC7A76A.8040506@mail.tsaitgaist.info> Message-ID: <4DC7A8B3.5060301@mail.tsaitgaist.info> >> >> I am not familiar with USB buffers? How do they work? > It's not a buffer (just me not knowing what I do). > It's just and emi filter, replacing the R and C for the USB. > For those interested : http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=497-3743-1-ND From laforge at gnumonks.org Mon May 9 09:27:41 2011 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 9 May 2011 11:27:41 +0200 Subject: SIMtrace v0.7+ In-Reply-To: <4DC7A76A.8040506@mail.tsaitgaist.info> References: <4DC6B02B.6070208@mail.tsaitgaist.info> <20110508180429.GC11457@prithivi.gnumonks.org> <4DC7A76A.8040506@mail.tsaitgaist.info> Message-ID: <20110509092741.GH21397@prithivi.gnumonks.org> Hi Kevin, On Mon, May 09, 2011 at 10:35:54AM +0200, Kevin Redon wrote: > corrections added : https://gsm.tsaitgaist.info/SIMtrace/v0.7+/ Ok, this looks fine to me now, I think you can go ahead with component placement + routing. Feel free to post links to the gerber (or rendered to PDF) once you have it. I'll take care of ordering the prototype PCBs (and the BOM from digikey) once the gerber is finalized. 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 Mon May 9 09:20:15 2011 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 9 May 2011 11:20:15 +0200 Subject: USB EMI filter (Re: SIMtrace v0.7) In-Reply-To: <4DC7A8B3.5060301@mail.tsaitgaist.info> References: <4DC6B02B.6070208@mail.tsaitgaist.info> <20110508180429.GC11457@prithivi.gnumonks.org> <4DC7A76A.8040506@mail.tsaitgaist.info> <4DC7A8B3.5060301@mail.tsaitgaist.info> Message-ID: <20110509092015.GG21397@prithivi.gnumonks.org> On Mon, May 09, 2011 at 10:41:23AM +0200, Kevin Redon wrote: > >> I am not familiar with USB buffers? How do they work? > > > It's not a buffer (just me not knowing what I do). > > It's just and emi filter, replacing the R and C for the USB. > > For those interested : > http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=497-3743-1-ND looks fine, especially as it includes ESD protection. -- - 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 Mon May 9 12:09:51 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Mon, 09 May 2011 14:09:51 +0200 Subject: USB EMI filter (Re: SIMtrace v0.7) In-Reply-To: <20110509092015.GG21397@prithivi.gnumonks.org> References: <4DC6B02B.6070208@mail.tsaitgaist.info> <20110508180429.GC11457@prithivi.gnumonks.org> <4DC7A76A.8040506@mail.tsaitgaist.info> <4DC7A8B3.5060301@mail.tsaitgaist.info> <20110509092015.GG21397@prithivi.gnumonks.org> Message-ID: <4DC7D98F.4070306@mail.tsaitgaist.info> filter, replacing the R and C for the USB. >> >> For those interested : >> http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=497-3743-1-ND > > looks fine, especially as it includes ESD protection. > should I use this IC (saves place and complexity, costs as much), or should I leave as it is (like openPCD) From kevredon at mail.tsaitgaist.info Mon May 9 17:26:58 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Mon, 09 May 2011 19:26:58 +0200 Subject: SIMtrace v0.8 Message-ID: <4DC823E2.7010200@mail.tsaitgaist.info> hi, here v0.8 : https://gsm.tsaitgaist.info/SIMtrace/v0.8/ Compared to v0.7+, I added 2 1n4148 after the parallel voltage regulator outputs. I wanted to avoid the regulators to fuzz each other, but I don't know if it's right. Maybe an additional zener diode is also required. Now I'm looking for the parts and footprints. Kevin From philipp.maier at runningserver.com Mon May 9 19:11:23 2011 From: philipp.maier at runningserver.com (Philipp Fabian Benedikt Maier) Date: Mon, 09 May 2011 21:11:23 +0200 Subject: SIMtrace v0.8 In-Reply-To: <4DC823E2.7010200@mail.tsaitgaist.info> References: <4DC823E2.7010200@mail.tsaitgaist.info> Message-ID: <4DC83C5B.9060202@runningserver.com> Hallo Kevin. > here v0.8 : https://gsm.tsaitgaist.info/SIMtrace/v0.8/ > Compared to v0.7+, I added 2 1n4148 after the parallel voltage regulator > outputs. > I wanted to avoid the regulators to fuzz each other, but I don't know if > it's right. Maybe an additional zener diode is also required. Hmm. The diodes will cause a voltage loss of about 0,7V ;-/ Maybe you will need something more tricky or just add a little switch. I think nobody will change the power supply method every minute. regards. Philipp -- ______________________________________ Philipp Fabian Benedikt Maier philipp.maier at runningserver.com Funk: DO5DXT http://www.runningserver.com http://www.diskettenschlitz.de ______________________________________ From philipp.maier at runningserver.com Mon May 9 19:18:00 2011 From: philipp.maier at runningserver.com (Philipp Fabian Benedikt Maier) Date: Mon, 09 May 2011 21:18:00 +0200 Subject: SIMtrace v0.8 In-Reply-To: <4DC823E2.7010200@mail.tsaitgaist.info> References: <4DC823E2.7010200@mail.tsaitgaist.info> Message-ID: <4DC83DE8.90501@runningserver.com> Hi! Or maybe you could do this: 3xMigon ----->|------+ +--------+ | | | +----------+ 3,3V +-------- | | Reg. | USB 5V ----->|------+ +---+----+ | _|_ Simple, but effective ;-) And you need only one regulator. regards. Philipp -- ______________________________________ Philipp Fabian Benedikt Maier philipp.maier at runningserver.com Funk: DO5DXT http://www.runningserver.com http://www.diskettenschlitz.de ______________________________________ From laforge at gnumonks.org Mon May 9 19:07:59 2011 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 9 May 2011 21:07:59 +0200 Subject: SIMtrace v0.8 In-Reply-To: <4DC823E2.7010200@mail.tsaitgaist.info> References: <4DC823E2.7010200@mail.tsaitgaist.info> Message-ID: <20110509190759.GD24043@prithivi.gnumonks.org> Hi Kevin, On Mon, May 09, 2011 at 07:26:58PM +0200, Kevin Redon wrote: > here v0.8 : https://gsm.tsaitgaist.info/SIMtrace/v0.8/ > Compared to v0.7+, I added 2 1n4148 after the parallel voltage regulator > outputs. > I wanted to avoid the regulators to fuzz each other, but I don't know if > it's right. Maybe an additional zener diode is also required. I understand the intention, but I doubt it's a good idea. First, the 1N4148 is quite low-power/low-current, i.e. it will be the weakest element in the chain. Second, it's a silicium diode and thus causes a voltage drop of 0.7V, i.e. we will have 3.3-0.7= 2.6V only, which is really bad. I think you should just leave them out. You could simplify the design by removing the DC/DC converter (SC120) and simply attach the battery connector to the +5V input. The TPS73633 is a ultra-low-drop regulator, i.e. from voltages >= 3.375V on it will provide a stable 3.3V output. This means a battery pack with 3 or 4 1.2V cells should do just fine. What do you think? We can save the step-up regulator and loose the design risk of leaking power from the USB into the step-up regulator at the same time... 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 Tue May 10 07:57:29 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Tue, 10 May 2011 09:57:29 +0200 Subject: SIMtrace v0.8 In-Reply-To: <4DC83DE8.90501@runningserver.com> References: <4DC823E2.7010200@mail.tsaitgaist.info> <4DC83DE8.90501@runningserver.com> Message-ID: <4DC8EFE9.7050209@mail.tsaitgaist.info> then it would be 4xAAA/AA (3xAA will only work if fully charged) the other idea would be : 0.7-4.5 --- VREG 5V --->|----+ | +--- VREG 3.3V | USB 5V ---------------->|----+ or another nice idea (like the arduino does for the 5v) : BATT --- VREG 3.3V ---+ | FDN304 -- 3.3V | VUSB --- VREG 3.3V ---+ as you wish, Kevin On 09.05.2011 21:18, Philipp Fabian Benedikt Maier wrote: > Hi! > > Or maybe you could do this: > > 3xMigon ----->|------+ +--------+ > | | | > +----------+ 3,3V +-------- > | | Reg. | > USB 5V ----->|------+ +---+----+ > | > _|_ > > Simple, but effective ;-) And you need only one regulator. > > regards. > Philipp From keytwo at gmail.com Tue May 10 09:55:22 2011 From: keytwo at gmail.com (K2) Date: Tue, 10 May 2011 11:55:22 +0200 Subject: packet-gsm_sim wireshark Message-ID: It is assumed in the dissector that the TERMINAL PROFILE has a len of 17, which is not the case with the SIM i'm currently using. I fixed it replacing with: case 0x10: /* TERMINAL PROFILE */ offset += DATA_OFFS; if(p3 >= 1) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b1, ett_tprof_b1, tprof_b1_fields, FALSE); if(p3 >= 2) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b2, ett_tprof_b2, tprof_b2_fields, FALSE); if(p3 >= 3) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b3, ett_tprof_b3, tprof_b3_fields, FALSE); if(p3 >= 4) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b4, ett_tprof_b4, tprof_b4_fields, FALSE); if(p3 >= 5) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b5, ett_tprof_b5, tprof_b5_fields, FALSE); if(p3 >= 6) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b6, ett_tprof_b6, tprof_b6_fields, FALSE); if(p3 >= 7) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b7, ett_tprof_b7, tprof_b7_fields, FALSE); if(p3 >= 8) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b8, ett_tprof_b8, tprof_b8_fields, FALSE); if(p3 >= 9) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b9, ett_tprof_b9, tprof_b9_fields, FALSE); if(p3 >= 10) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b10, ett_tprof_b10, tprof_b10_fields, FALSE); if(p3 >= 11) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b11, ett_tprof_b11, tprof_b11_fields, FALSE); if(p3 >= 12) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b12, ett_tprof_b12, tprof_b12_fields, FALSE); if(p3 >= 13) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b13, ett_tprof_b13, tprof_b13_fields, FALSE); if(p3 >= 14) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b14, ett_tprof_b14, tprof_b14_fields, FALSE); if(p3 >= 15) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b15, ett_tprof_b15, tprof_b15_fields, FALSE); if(p3 >= 16) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b16, ett_tprof_b16, tprof_b16_fields, FALSE); if(p3 >= 17) proto_tree_add_bitmask(tree, tvb, offset++, hf_tprof_b17, ett_tprof_b17, tprof_b17_fields, FALSE); /* FIXME */ break; -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Tue May 10 15:00:34 2011 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 10 May 2011 17:00:34 +0200 Subject: packet-gsm_sim wireshark In-Reply-To: References: Message-ID: <20110510150034.GF9012@prithivi.gnumonks.org> Hi K2, On Tue, May 10, 2011 at 11:55:22AM +0200, K2 wrote: > It is assumed in the dissector that the TERMINAL PROFILE has a len of 17, > which is not the case with the SIM i'm currently using. > I fixed it replacing with: Thanks. If you have some time to do the indentation according to the remeaining file and submit a patch against our git tree, I'm happy to merge it! 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 Tue May 10 15:11:41 2011 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 10 May 2011 17:11:41 +0200 Subject: SIMtrace v0.8 In-Reply-To: <4DC8EFE9.7050209@mail.tsaitgaist.info> References: <4DC823E2.7010200@mail.tsaitgaist.info> <4DC83DE8.90501@runningserver.com> <4DC8EFE9.7050209@mail.tsaitgaist.info> Message-ID: <20110510151141.GI9012@prithivi.gnumonks.org> Hi Kevin, On Tue, May 10, 2011 at 09:57:29AM +0200, Kevin Redon wrote: > then it would be 4xAAA/AA (3xAA will only work if fully charged) fine with me. I honestly don't care about the number of batteries... and the PCB will not be smaller than 4x AAA/AA anyway. > the other idea would be : > > 0.7-4.5 --- VREG 5V --->|----+ > | > +--- VREG 3.3V > | > USB 5V ---------------->|----+ that should work, but you should use something like a 1N4001 as the diode, to cope with more current. However, I would want to have that tested on a breadboard before sending the gerber off for PCB manufacturing, just to make sure the power supply side is working. We still have a problem if somebody decides USB _and_ the battery power supply :/ In fact, now that I'm thinking off it, we should use one of those jacks which disconnnect one contact when plugging in the power supply. This way we can actually interrupt the USB 5V once a power supply plug has been plugged in. This should be done independent of the decision on the voltage regulator. > or another nice idea (like the arduino does for the 5v) : looks not that trivil to me, as you don't only need the FDN304 but also the LM358 op-amp and external circuitry. Probably a bit overkill. So I think we should route the 5V USB via the power plug, and simply use a low-drop-out 3.3V regulator, like in the current schematics. This way the LDO input will be USB 5V _until_ somebody plugs in an external power supply or battery pack, which will have to provide at least 3.4V for stable operation. 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 Thu May 12 08:14:03 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Thu, 12 May 2011 10:14:03 +0200 Subject: SIMtrace v0.8 In-Reply-To: <20110510151141.GI9012@prithivi.gnumonks.org> References: <4DC823E2.7010200@mail.tsaitgaist.info> <4DC83DE8.90501@runningserver.com> <4DC8EFE9.7050209@mail.tsaitgaist.info> <20110510151141.GI9012@prithivi.gnumonks.org> Message-ID: <4DCB96CB.6050206@mail.tsaitgaist.info> I'm back. I was looking around for a solution for such a trivial task (power switching), and there is no easy answer. >> the other idea would be : >> >> 0.7-4.5 --- VREG 5V --->|----+ >> | >> +--- VREG 3.3V >> | >> USB 5V ---------------->|----+ > not effective. > > In fact, now that I'm thinking off it, we should use one of those jacks > which disconnnect one contact when plugging in the power supply. This > way we can actually interrupt the USB 5V once a power supply plug has > been plugged in. This should be done independent of the decision on the > voltage regulator. most dc jack can provide such a solution, but I think the USB 5v should be used if the two sources are connected. USBVCC is more stable, moreover if the user leaves it connected the battery will be drained. Another point is that the normally closed circuit uses the barrel (normally the jack is used to plug wall power, cutting the board battery line). Having +5v on the barrel is not common (if the user has an of-the-self power adaptor). > >> or another nice idea (like the arduino does for the 5v) : > > looks not that trivil to me, as you don't only need the FDN304 but also > the LM358 op-amp and external circuitry. Probably a bit overkill. > agree > So I think we should route the 5V USB via the power plug, and simply use > a low-drop-out 3.3V regulator, like in the current schematics. This way > the LDO input will be USB 5V _until_ somebody plugs in an external power > supply or battery pack, which will have to provide at least 3.4V for > stable operation. > yes, I also like this solution, but has drawbacks (see above) I found two other solutions : - using a automatic power switching mux (TPS2115). too expensive and take to much space. - using a manual switch to select the power source > >> then it would be 4xAAA/AA (3xAA will only work if fully charged) > > fine with me. I honestly don't care about the number of batteries... > and the PCB will not be smaller than 4x AAA/AA anyway. > that is the decision I took. Simple, cost effective, saves place. > that should work, but you should use something like a 1N4001 as the > diode, to cope with more current 1N5819 allows 1A, it should be enough. 1N4001 has a forward voltage of 1.0V, 1N5819 only 0.6-0.7V. here the schema : https://gsm.tsaitgaist.info/SIMtrace/v0.9/ I now an doing the BOM. I'm half-way through, but it takes time. Kevin From kevredon at mail.tsaitgaist.info Fri May 13 08:03:19 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Fri, 13 May 2011 10:03:19 +0200 Subject: SIMtrace v0.9+ Message-ID: <4DCCE5C7.5020006@mail.tsaitgaist.info> Hi, The BOM (bill of material) is ready. I finished the netlist, footprint drawing, and footprint selection. all available at : https://gsm.tsaitgaist.info/SIMtrace/v0.9+/ next task : place the components on the board (i'll try smart card size) and route the lines. Kevin From laforge at gnumonks.org Fri May 13 09:39:24 2011 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 13 May 2011 11:39:24 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <4DCCE5C7.5020006@mail.tsaitgaist.info> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> Message-ID: <20110513093924.GI25011@prithivi.gnumonks.org> Hi Kevin, On Fri, May 13, 2011 at 10:03:19AM +0200, Kevin Redon wrote: > I finished the netlist, footprint drawing, and footprint selection. > all available at : https://gsm.tsaitgaist.info/SIMtrace/v0.9+/ I've just had a look at the the schematics and it looks fine to me now. > next task : place the components on the board (i'll try smart card size) > and route the lines. My guess is that it will be too hard to fit everything into smartcard size (on a two-layer PCB with only one side of SMD components). But feel free to try. 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 Fri May 13 10:12:39 2011 From: laforge at gnumonks.org (Harald Welte) Date: Fri, 13 May 2011 12:12:39 +0200 Subject: simtrace hardware kicad project now part of simtrace.git Message-ID: <20110513101239.GK25011@prithivi.gnumonks.org> Hi all! The kicad project for the simtrace hardware that Kevin has been working on is now available as part of the simtrace.git repository on git.osmocom.org. This will allow us to document the revision history of any modifications to the hardware in the commit messages, and it allows us to see differences between individual versions. 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 hwelte at sysmocom.de Fri May 13 16:39:18 2011 From: hwelte at sysmocom.de (Harald Welte) Date: Fri, 13 May 2011 18:39:18 +0200 Subject: Osmocom project vs. sysmocom GmbH Message-ID: <20110513163918.GU25011@prithivi.gnumonks.org> Hi all! As some of you already know, Holger and I have recently started a new company called "sysmocom - systems for mobile communications GmbH". The process of establishing the new company has now formally concluded. Before some rumours start to spread, we would like to clarify some points and make sure there is mutual understanding between the Osmocom community and the sysmocom company. sysmocom is intended to provide commercial offerings related to the Osmocom projects. This is not entirely new. Especially on the network side, people like Holger and I have been doing quite a lot of paid development to bring those projects forward. We would not have many of the features we have today, if it wasn't for customers who actually pay us for development of OpenBSC, OsmoBSC, OsmoSGSN and the various side projects more targetted at a real network operator like cellmgr-ng, bsc-nat, gb_proxy - just to name a few. However, this has always only been freelancing development of Software. With sysmocom, we want to go one step further and work on hardware products related to the various Free Software projects. Right now I don't want to talk too much about unfinished products, but we are working towards an inexpensive BTS product, we are funding the prototypes for Osmocom SIMtrace, and we will likely also see stuff like OpenBSC appliances. Given our past involvement and exposure into other projects that share a split Free Software / business set-up, we think we understand very well where potential issues of conflict between the two sides may be. Let me make some more clarification what this is not about: * sysmocom is not about creating proprietary derivates of Osmocom software. We work on Free Software which is publicly available under OSI approved and FSF endorsed licenses. We may offer proprietary hardware and sometimes software - but those are independent projects from existing Osmocom software. * we specifically will not have a public and a non-public version of the same program with differences in features. * sysmocom is not a VC-funded startup. It's a very small company run out of personal funds with no intention to take external funding or grow rapidly. Nobody but Holger and I determine where it goes and what it does. * sysmocom does not hold any copyright on the Free Software projects. The copyrights stay distributed with the major authors such as Holger, Onwaves, Sylvain, Dieter, Andreas and myself. None of the others have any affiliation with sysmocom. I have (personally, unrelated to sysmocom) asked some of the smaller contributors for a copyright transfer to make sure we could do the AGPLv3 transition, or future re-licensing decisions without having to ask dozens and dozens of people. sysmocom does not seek to control the Free Software projects. * we will maintain a strict separation between the community side of things and the business side. Unlike some other popular projects, we will not end up in a situation where the osmocom.org websites will be full of advertisements and hidden links that lure you on the company website. * we will keep a strict separation of naming. Osmocom is for the FOSS projects, sysmocom for the business. The company will use the term "Osmocom" only in descriptive context, not as a product name, brand or for advertisement. If you do have any concerns, please feel free to share them. However, I'd like to avoid cross-posting them throguh different mailing lists. Please follow-up-to openbsc at lists.osmocom.org Regards, Harald -- - Harald Welte http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Schivelbeiner Str. 5 * 10439 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 482 bytes Desc: Digital signature URL: From holger at freyther.de Fri May 13 20:42:58 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Fri, 13 May 2011 22:42:58 +0200 Subject: softSIM In-Reply-To: <4DC6CCC1.50705@mail.tsaitgaist.info> References: <4DC6CCC1.50705@mail.tsaitgaist.info> Message-ID: <4DCD97D2.8040701@freyther.de> On 05/08/2011 07:02 PM, Kevin Redon wrote: > Hi, > > softSIM is out : http://bb.osmocom.org/trac/wiki/softSIM > It's not fully implemented but already working (I hope). > The osmocomBB use/cooperation will come out soon. > Other tools are coming next week (I need to clean them). Hi Kevin, did you forget to push the code to the git repository? holger From kevredon at mail.tsaitgaist.info Sun May 15 11:01:35 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Sun, 15 May 2011 13:01:35 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <4DCCE5C7.5020006@mail.tsaitgaist.info> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> Message-ID: <4DCFB28F.4050801@mail.tsaitgaist.info> Hi, The routing has been done. Drawing and gerber are available. As I never work with fabrication, I have no idea if I did it right/wrong. https://gsm.tsaitgaist.info/SIMtrace/v0.9+/ Kevin On 13.05.2011 10:03, Kevin Redon wrote: > Hi, > > The BOM (bill of material) is ready. > I finished the netlist, footprint drawing, and footprint selection. > all available at : https://gsm.tsaitgaist.info/SIMtrace/v0.9+/ > > next task : place the components on the board (i'll try smart card size) > and route the lines. > > Kevin From holger at freyther.de Sun May 15 12:52:04 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Sun, 15 May 2011 14:52:04 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <4DCFB28F.4050801@mail.tsaitgaist.info> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> <4DCFB28F.4050801@mail.tsaitgaist.info> Message-ID: <4DCFCC74.1070808@freyther.de> On 05/15/2011 01:01 PM, Kevin Redon wrote: > Hi, > > The routing has been done. > Drawing and gerber are available. > As I never work with fabrication, I have no idea if I did it right/wrong. > https://gsm.tsaitgaist.info/SIMtrace/v0.9+/ > > Hi could you do a git status and add the missing files? thanks holger From kevredon at mail.tsaitgaist.info Sun May 15 17:18:47 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Sun, 15 May 2011 19:18:47 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <4DCFCC74.1070808@freyther.de> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> <4DCFB28F.4050801@mail.tsaitgaist.info> <4DCFCC74.1070808@freyther.de> Message-ID: <4DD00AF7.7090507@mail.tsaitgaist.info> Hi, there is not public git repo for SIMtrace (is there ?). But I'm happy to push the one I have locally, if you wish and if harald wants to setup a git for that. kevin On 15.05.2011 14:52, Holger Hans Peter Freyther wrote: > On 05/15/2011 01:01 PM, Kevin Redon wrote: >> Hi, >> >> The routing has been done. >> Drawing and gerber are available. >> As I never work with fabrication, I have no idea if I did it right/wrong. >> https://gsm.tsaitgaist.info/SIMtrace/v0.9+/ >> >> > > Hi could you do a git status and add the missing files? > > thanks > holger > > From kevredon at mail.tsaitgaist.info Sun May 15 17:20:56 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Sun, 15 May 2011 19:20:56 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <20110513093924.GI25011@prithivi.gnumonks.org> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> <20110513093924.GI25011@prithivi.gnumonks.org> Message-ID: <4DD00B78.8040008@mail.tsaitgaist.info> > > My guess is that it will be too hard to fit everything into smartcard > size (on a two-layer PCB with only one side of SMD components). But > feel free to try. It fits :). There is even some free space. all the components are on one side. The other side is only for gnd, and vias. Kevin From holger at freyther.de Sun May 15 17:22:25 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Sun, 15 May 2011 19:22:25 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <4DD00AF7.7090507@mail.tsaitgaist.info> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> <4DCFB28F.4050801@mail.tsaitgaist.info> <4DCFCC74.1070808@freyther.de> <4DD00AF7.7090507@mail.tsaitgaist.info> Message-ID: <4DD00BD1.3000009@freyther.de> On 05/15/2011 07:18 PM, Kevin Redon wrote: > Hi, > > there is not public git repo for SIMtrace (is there ?). > But I'm happy to push the one I have locally, if you wish and if harald > wants to setup a git for that. http://lists.osmocom.org/pipermail/simtrace/2011-May/000028.html From kevredon at mail.tsaitgaist.info Sun May 15 18:08:45 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Sun, 15 May 2011 20:08:45 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <4DD00BD1.3000009@freyther.de> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> <4DCFB28F.4050801@mail.tsaitgaist.info> <4DCFCC74.1070808@freyther.de> <4DD00AF7.7090507@mail.tsaitgaist.info> <4DD00BD1.3000009@freyther.de> Message-ID: <4DD016AD.40906@mail.tsaitgaist.info> Hi, > > http://lists.osmocom.org/pipermail/simtrace/2011-May/000028.html > my mail server had an issue, I think this is one of the mails I lost. Oups. Now the drawings are available in git (see in pcb folder). Thanks for the forward, Kevin From holger at freyther.de Sun May 15 18:37:26 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Sun, 15 May 2011 20:37:26 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <4DD016AD.40906@mail.tsaitgaist.info> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> <4DCFB28F.4050801@mail.tsaitgaist.info> <4DCFCC74.1070808@freyther.de> <4DD00AF7.7090507@mail.tsaitgaist.info> <4DD00BD1.3000009@freyther.de> <4DD016AD.40906@mail.tsaitgaist.info> Message-ID: <4DD01D66.2010203@freyther.de> On 05/15/2011 08:08 PM, Kevin Redon wrote: > Hi, >> >> http://lists.osmocom.org/pipermail/simtrace/2011-May/000028.html >> > > my mail server had an issue, I think this is one of the mails I lost. Oups. > Now the drawings are available in git (see in pcb folder). Hi again, thanks for pushing. Then let me repeat another question. I tried to look at your SIM emulation but there does not seem to be any source in the repository yet. Do you think you could share it? From kevredon at mail.tsaitgaist.info Sun May 15 21:32:14 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Sun, 15 May 2011 23:32:14 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <4DD01D66.2010203@freyther.de> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> <4DCFB28F.4050801@mail.tsaitgaist.info> <4DCFCC74.1070808@freyther.de> <4DD00AF7.7090507@mail.tsaitgaist.info> <4DD00BD1.3000009@freyther.de> <4DD016AD.40906@mail.tsaitgaist.info> <4DD01D66.2010203@freyther.de> Message-ID: <4DD0465E.3010203@mail.tsaitgaist.info> I already pushed some time ago, but it seems the git repo is down, harald needs to repair it. (Correct me if I am just clumsy with my git inexperience.) I can send you the code meanwhile if you want. On 15.05.2011 20:37, Holger Hans Peter Freyther wrote: > On 05/15/2011 08:08 PM, Kevin Redon wrote: >> Hi, >>> >>> http://lists.osmocom.org/pipermail/simtrace/2011-May/000028.html >>> >> >> my mail server had an issue, I think this is one of the mails I lost. Oups. >> Now the drawings are available in git (see in pcb folder). > > Hi again, > > thanks for pushing. Then let me repeat another question. I tried to look at > your SIM emulation but there does not seem to be any source in the repository > yet. Do you think you could share it? > > From holger at freyther.de Mon May 16 06:49:09 2011 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Mon, 16 May 2011 08:49:09 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <4DD0465E.3010203@mail.tsaitgaist.info> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> <4DCFB28F.4050801@mail.tsaitgaist.info> <4DCFCC74.1070808@freyther.de> <4DD00AF7.7090507@mail.tsaitgaist.info> <4DD00BD1.3000009@freyther.de> <4DD016AD.40906@mail.tsaitgaist.info> <4DD01D66.2010203@freyther.de> <4DD0465E.3010203@mail.tsaitgaist.info> Message-ID: <4DD0C8E5.5000200@freyther.de> On 05/15/2011 11:32 PM, Kevin Redon wrote: > I already pushed some time ago, but it seems the git repo is down, > harald needs to repair it. (Correct me if I am just clumsy with my git > inexperience.) > I can send you the code meanwhile if you want. > What is the error you get on push? I could help you with permissions on the git repo... From kevredon at mail.tsaitgaist.info Mon May 16 08:55:05 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Mon, 16 May 2011 10:55:05 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <4DD0C8E5.5000200@freyther.de> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> <4DCFB28F.4050801@mail.tsaitgaist.info> <4DCFCC74.1070808@freyther.de> <4DD00AF7.7090507@mail.tsaitgaist.info> <4DD00BD1.3000009@freyther.de> <4DD016AD.40906@mail.tsaitgaist.info> <4DD01D66.2010203@freyther.de> <4DD0465E.3010203@mail.tsaitgaist.info> <4DD0C8E5.5000200@freyther.de> Message-ID: <4DD0E669.8010003@mail.tsaitgaist.info> > > What is the error you get on push? I could help you with permissions on the > git repo... > > ok, repaired. It was just my inexperience. The repo was re-init (I think) and I did not try to repush the origin/master completely. sorry for that, kevin From laforge at gnumonks.org Sun May 22 10:56:01 2011 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 22 May 2011 12:56:01 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <4DCCE5C7.5020006@mail.tsaitgaist.info> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> Message-ID: <20110522105601.GM4243@prithivi.gnumonks.org> Hi Kevin, I've had a look at the current .brd file and I think it's looking pretty good. My only comment: The P2 DEBUG connector only makes sense if it is a one-row (1x6) connector that fits the existing ready-built FTDI cables. Turning the connector into a 2x3 layout makes it mechanically incompatible with those cables. So either we keep it 1x6, or we simply remove it and force people to use the 2.5mm jack. Please let me know once you consider the .brd files finished, I would be more than happy to order some pcb samples from pcbpool asap. 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 Sun May 22 13:58:44 2011 From: kevredon at mail.tsaitgaist.info (Kevin Redon) Date: Sun, 22 May 2011 15:58:44 +0200 Subject: SIMtrace v0.9+ In-Reply-To: <20110522105601.GM4243@prithivi.gnumonks.org> References: <4DCCE5C7.5020006@mail.tsaitgaist.info> <20110522105601.GM4243@prithivi.gnumonks.org> Message-ID: <4DD91694.70503@mail.tsaitgaist.info> Hi, > > My only comment: The P2 DEBUG connector only makes sense if it is a > one-row (1x6) connector that fits the existing ready-built FTDI cables. > Turning the connector into a 2x3 layout makes it mechanically > incompatible with those cables. changed. not well aligned (does not fit well in the reserved space), but enough for the prototype. gerbers are also available Kevin From laforge at gnumonks.org Sun May 29 21:46:23 2011 From: laforge at gnumonks.org (Harald Welte) Date: Sun, 29 May 2011 23:46:23 +0200 Subject: SIMtrace PCB and components have been ordered Message-ID: <20110529214623.GE4532@prithivi.gnumonks.org> Hi Kevin and others, I've just ordered 4 prototype PCBs as well as components for at least 10 units. I'll keep you posted about the progress. We should have them in less than two weeks. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)