From wind3style at gmail.com Wed Sep 26 12:22:14 2018 From: wind3style at gmail.com (=?UTF-8?B?0JDQu9C10LrRgdCw0L3QtNGAINCk0LXQtNC+0YDQvtCy?=) Date: Wed, 26 Sep 2018 19:22:14 +0700 Subject: Fwd: SIMtrace In-Reply-To: References: Message-ID: -- Fedorov Alexander Mobile: +7-908-212-98-05https://www.linkedin.com/in/wind3style/ E-mail:wind3style at gmail.com ---------- Forwarded message --------- From: ????????? ??????? Date: ??, 26 ????. 2018 ?. ? 17:59 Subject: SIMtrace To: Hello Harald! I am writing to you from far Siberia. I use SIMtrace v1 and I have some problem. Could you halp me? firmware v0.5 lose data and data in Wireshark isn't corrected: [image: image.png] Can I resolve my problem on V1 Simtrace or I have to buy SIMtrace V2? last version firmware from repository doesn't work correctly at all by looping this DEBUG text: [000001] (C) 2006-2011 by Harald Welte This software is FREE SOFTWARE licensed under GNU GPL [000002] Version 0.5.27-5a40-dirty compiled 20180926-170104 by xmobi at xmobi-B250M-DS3H [000003] DEBUG Interface: 0) Set Pull-up 1) Clear Pull-up 2) Toggle LED1 3) Toggle LED2 9) Reset [000004] RSTC_SR=0x00010200 [000005] LARGE req_ctx[00] initialized at 002055AC, Data: 00200A68 => 00200E28 [000006] LARGE req_ctx[01] initialized at 002055C0, Data: 00200E28 => 002011E8 [000007] LARGE req_ctx[02] initialized at 002055D4, Data: 002011E8 => 002015A8 [000008] LARGE req_ctx[03] initialized at 002055E8, Data: 002015A8 => 00201968 [000009] LARGE req_ctx[04] initialized at 002055FC, Data: 00201968 => 00201D28 [00000A] LARGE req_ctx[05] initialized at 00205610, Data: 00201D28 => 002020E8 [00000B] LARGE req_ctx[06] initialized at 00205624, Data: 002020E8 => 002024A8 [00000C] LARGE req_ctx[07] initialized at 00205638, Data: 002024A8 => 00202868 [00000D] LARGE req_ctx[08] initialized at 0020564C, Data: 00202868 => 00202C28 [00000E] LARGE req_ctx[09] initialized at 00205660, Data: 00202C28 => 00202FE8 [00000F] LARGE req_ctx[10] initialized at 00205674, Data: 00202FE8 => 002033A8 [000010] LARGE req_ctx[11] initialized at 00205688, Data: 002033A8 => 00203768 [000011] LARGE req_ctx[12] initialized at 0020569C, Data: 00203768 => 00203B28 [000012] LARGE req_ctx[13] initialized at 002056B0, Data: 00203B28 => 00203EE8 [000013] LARGE req_ctx[14] initialized at 002056C4, Data: 00203EE8 => 002042A8 [000014] LARGE req_ctx[15] initialized at 002056D8, Data: 002042A8 => 00204668 [000015] LARGE req_ctx[16] initialized at 002056EC, Data: 00204668 => 00204A28 [000016] LARGE req_ctx[17] initialized at 00205700, Data: 00204A28 => 00204DE8 [000017] LARGE req_ctx[18] initialized at 00205714, Data: 00204DE8 => 002051A8 [000018] LARGE req_ctx[19] initialized at 00205728, Data: 002051A8 => 00205568 [000019] Inititalizing usbcmd_gen_init [00001A] udp_open(440): entering [00001B] USART Initializing [00001C] pio_irq_register(109): registering handler 001079bc for PIOA 7 [00001D] RST [00001E] computed Fi(1) Di(1) ratio: 372 -- Fedorov Alexander Mobile: +7-908-212-98-05https://www.linkedin.com/in/wind3style/ E-mail:wind3style at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 187887 bytes Desc: not available URL: From ml at mail.tsaitgaist.info Wed Sep 26 17:14:15 2018 From: ml at mail.tsaitgaist.info (=?iso-8859-1?Q?K=E9vin?= Redon) Date: Wed, 26 Sep 2018 19:14:15 +0200 Subject: AT91SAM3 Based simtracer and firmware In-Reply-To: References: Message-ID: <20180926171415.GB5961@coil> On Mon, Apr 16, 2018 at 08:08:22AM +0000, Gerard Bakker wrote: > Dear Osmocom, > > I have a question about the latest build of the simtrace2 based on the AT91SAM3.. I'm not sure if you mean the AT91SAM7S or the SAM3S. The AT91 prefix only is for the SAM7S, with is the micro-controller used by the simtarce (v1) firmware. SAM3S is the micro-controller used by the simtarce v2 firmware. > Currently we have assembled some boards based on the v1.5 design of the Simtracer received from the git repository git.osmocom.org/simtrace (branch v1.5) the v1.5 simtrace branch has actually two hardware designs: - the kicad one, which still uses the SAM7S - the pcd initial design (never completed and produced), which uses the SAM3S > > If have tried to compile the firmware of the repository git.osmocom.org/simtrace2 But I run in to some issue after the firmware is loaded. > Also I am not able to find the simtrace2 tool to do simtracing after compilation in the host directory .. could you provide more information and logs? what are you trying to do, what did you do, what is the expected result, what is the actual result (with error). > Is this firmware working already ? yes, it is. not every function is implemented for every hardware though (this is WiP), but tracing/sniffing using SAM3S-based simtrace hardware works. You can find more information in the wiki: https://osmocom.org/projects/simtrace2/wiki#simtrace2-sniff There is also some pre-compiled firmware (so you don't need any cross-compiler) available here: http://ftp.osmocom.org/binaries/simtrace2/firmware/ > (The website @sysmocom says "SIMtrace 2" will be available from late March 2018) The hardware is just the "old" simtrace board with an SAM3S micro-controller (nothing else changed). If you can't/don't want to produce it yourself, it is also made available in the sysmocom shop: http://shop.sysmocom.de/products/simtrace The wiki provides more information: https://osmocom.org/projects/simtrace2/wiki tracing works on simtrace, and card emulation works on the sysmoqmod. The firmware is being actively developed and more functionalities will come in the future. > Or am I missing something ? I hope the previous information helps. If you find any issues please report them so I can fix it. thanks, kevin From ml at mail.tsaitgaist.info Wed Sep 26 17:35:54 2018 From: ml at mail.tsaitgaist.info (=?iso-8859-1?Q?K=E9vin?= Redon) Date: Wed, 26 Sep 2018 19:35:54 +0200 Subject: SIM trace. In-Reply-To: References: Message-ID: <20180926173554.GC5961@coil> On Wed, Apr 25, 2018 at 06:34:17PM +0700, ????????? ??????? wrote: > Hello > > I use SImtrace for developing and debugging Java SIM Applet. > The device is pretty good, but there are some APDU errors while SIM > sniffing. > is it possible to fix APDU errors sniffing errors? > > I am attaching example dump with errors. > > Some times, simtrace stop receiving APDU and continue just after > restart simtrace process the wireshark decoding is correct (for the SIM application commands), but the underlying data is broken. the APDU splitting is incorrect (and data has probably been lost), but without detailed additional debug traces (from the serial output) it is pretty hard to analyze the issue. sadly the simtrace v1 firmware is not supported anymore. we wanted to improve the firmware code (also to fix such issues), but the simtrace hardware uses an old AT91SAM7S micro-controller which is end of life. This is replaced by a SAM3S micro-controller, which is pin compatible, but uses a different ARM architecture. Thus we had to re-implement the firmware (from scratch) for this architecture. TLDR: the issue on simtrace v1 firmware won't probably be fixed, but if it appear on the v2 it will. From ml at mail.tsaitgaist.info Wed Sep 26 17:45:06 2018 From: ml at mail.tsaitgaist.info (=?iso-8859-1?Q?K=E9vin?= Redon) Date: Wed, 26 Sep 2018 19:45:06 +0200 Subject: Fwd: SIMtrace In-Reply-To: References:

Message-ID: <20180926174506.GD5961@coil> On Wed, Sep 26, 2018 at 07:22:14PM +0700, ????????? ??????? wrote: > I am writing to you from far Siberia. > I use SIMtrace v1 and I have some problem. > Could you halp me? > firmware v0.5 lose data and data in Wireshark isn't corrected: > [image: image.png] > Can I resolve my problem on V1 Simtrace or I have to buy SIMtrace V2? the SIMtrace v1 firmware for the AT91SAM7S isn't supported anymore and the issue will probably not be fixed. if the error is present in the SIMtrace v2 firmware, it will be fixed. the boards are almost identical. the SIMtrace v1 firmware is for the AT91SAM7S micro-controller. the SIMtrace v2 firmware is for the SAM3S micro-controller. thus if you have some soldering skills you can convert your v1 board into a v2 board by switching the AT91SAM7S micro-controller with an SAM3S4B and flash the v2 firmware. else you will have to by a new SIMtrace V2 (or let it produce, based on the open source hardware files). From laforge at gnumonks.org Wed Sep 26 19:52:06 2018 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 26 Sep 2018 21:52:06 +0200 Subject: SIMtrace v1 vs v2 / Support (was Re: Fwd: SIMtrace) In-Reply-To: <20180926174506.GD5961@coil> References:

<20180926174506.GD5961@coil> Message-ID: <20180926195206.GN753@nataraja> Dear Kevin and SIMtrace user list, On Wed, Sep 26, 2018 at 07:45:06PM +0200, K?vin Redon wrote: > the SIMtrace v1 firmware for the AT91SAM7S isn't supported anymore and the issue will probably not be fixed. To clarify this: It will not be fixed by Kevin or me, the original authors. But: SIMtrace is and always was an open hardware and open source software project, where anyone can fix any bug or extend it in whichever way. We're happy to merge bugfixes by the community, or provide commit access to any developer who has an interest in maintaining or extending SIMtrace v1 firmware. There is also the option of porting the SIMtrace v2 firmware tree to the SIMtrace v1 hardware. It shouldn't be all that hard, as all the peripherals around the CPU core are identical, and almost only the CPU core changed from SAM7S (SIMtrace v1) to SAM3S (SIMtrace v2). > if the error is present in the SIMtrace v2 firmware, it will be fixed. This means: It will be fixed by Kevin and/or me, the original creators of SIMtrace. 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 min.xu at min-info.net Wed Sep 26 21:29:51 2018 From: min.xu at min-info.net (Min Xu) Date: Wed, 26 Sep 2018 11:29:51 -1000 Subject: SIMtrace In-Reply-To: References: Message-ID: Hi I made most of the recent changes to the v1 firmware to increase its stability. As far as I can tell, the changes I submitted was reliable and we use it with lots of phones and sim cards. If you are seeing the device looping the text from the beginning of the BOOT [000001] ...then that means your device is REBOOTING a lot. Perhaps check USB cable? or USB connector or other USB issues? If Wireshark was not able to sync to the GSMTAP ATR data (although we don't use Wireshark dissector, we use our own dissector), it mostly likely means you are not using the version where additional bytes were inserted into the simtrace response header to account the length of USB data transfer. I have not been tracking the current / latest built firmware so I don't know if the fields in question are added both in the firmware and in the desktop software. For reference, please look at this the mailing list archive for Nov 2017 ( http://lists.osmocom.org/pipermail/simtrace/2017-November/000746.html ) and Sep 2013 http://lists.osmocom.org/pipermail/simtrace/2013-September/thread.html Also, please double check that the board does not power up the Phone side SIM interface, see: http://lists.osmocom.org/pipermail/simtrace/2017-November/000746.html Best Regards On Wed, Sep 26, 2018 at 2:36 AM > From: "????????? ???????" > To: simtrace at lists.osmocom.org > Cc: > Bcc: > Date: Wed, 26 Sep 2018 19:22:14 +0700 > Subject: Fwd: SIMtrace > > -- > Fedorov Alexander > Mobile: +7-908-212-98-05https://www.linkedin.com/in/wind3style/ E-mail:wind3style at gmail.com > > > > > > ---------- Forwarded message --------- > From: ????????? ??????? > Date: ??, 26 ????. 2018 ?. ? 17:59 > Subject: SIMtrace > To: > > > Hello Harald! > > I am writing to you from far Siberia. > I use SIMtrace v1 and I have some problem. > Could you halp me? > firmware v0.5 lose data and data in Wireshark isn't corrected: > [image: image.png] > Can I resolve my problem on V1 Simtrace or I have to buy SIMtrace V2? > > last version firmware from repository doesn't work correctly at all by > looping this DEBUG text: > [000001] (C) 2006-2011 by Harald Welte > This software is FREE SOFTWARE licensed under GNU GPL > [000002] Version 0.5.27-5a40-dirty compiled 20180926-170104 by > xmobi at xmobi-B250M-DS3H > > [000003] > DEBUG Interface: > 0) Set Pull-up 1) Clear Pull-up 2) Toggle LED1 3) Toggle LED2 > 9) Reset > [000004] RSTC_SR=0x00010200 > [000005] LARGE req_ctx[00] initialized at 002055AC, Data: 00200A68 => > 00200E28 > [000006] LARGE req_ctx[01] initialized at 002055C0, Data: 00200E28 => > 002011E8 > [000007] LARGE req_ctx[02] initialized at 002055D4, Data: 002011E8 => > 002015A8 > [000008] LARGE req_ctx[03] initialized at 002055E8, Data: 002015A8 => > 00201968 > [000009] LARGE req_ctx[04] initialized at 002055FC, Data: 00201968 => > 00201D28 > [00000A] LARGE req_ctx[05] initialized at 00205610, Data: 00201D28 => > 002020E8 > [00000B] LARGE req_ctx[06] initialized at 00205624, Data: 002020E8 => > 002024A8 > [00000C] LARGE req_ctx[07] initialized at 00205638, Data: 002024A8 => > 00202868 > [00000D] LARGE req_ctx[08] initialized at 0020564C, Data: 00202868 => > 00202C28 > [00000E] LARGE req_ctx[09] initialized at 00205660, Data: 00202C28 => > 00202FE8 > [00000F] LARGE req_ctx[10] initialized at 00205674, Data: 00202FE8 => > 002033A8 > [000010] LARGE req_ctx[11] initialized at 00205688, Data: 002033A8 => > 00203768 > [000011] LARGE req_ctx[12] initialized at 0020569C, Data: 00203768 => > 00203B28 > [000012] LARGE req_ctx[13] initialized at 002056B0, Data: 00203B28 => > 00203EE8 > [000013] LARGE req_ctx[14] initialized at 002056C4, Data: 00203EE8 => > 002042A8 > [000014] LARGE req_ctx[15] initialized at 002056D8, Data: 002042A8 => > 00204668 > [000015] LARGE req_ctx[16] initialized at 002056EC, Data: 00204668 => > 00204A28 > [000016] LARGE req_ctx[17] initialized at 00205700, Data: 00204A28 => > 00204DE8 > [000017] LARGE req_ctx[18] initialized at 00205714, Data: 00204DE8 => > 002051A8 > [000018] LARGE req_ctx[19] initialized at 00205728, Data: 002051A8 => > 00205568 > [000019] Inititalizing usbcmd_gen_init > [00001A] udp_open(440): entering > [00001B] USART Initializing > [00001C] pio_irq_register(109): registering handler 001079bc for PIOA 7 > [00001D] RST > [00001E] computed Fi(1) Di(1) ratio: 372 > > -- > Fedorov Alexander > Mobile: +7-908-212-98-05https://www.linkedin.com/in/wind3style/ E-mail:wind3style at gmail.com > > > > _______________________________________________ > simtrace mailing list > simtrace at lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/simtrace > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 187887 bytes Desc: not available URL: