simtrace

simtrace@lists.osmocom.org

350 discussions

Fwd: SIMtrace
by Александр Федоров 26 Sep '18

26 Sep '18

-- Fedorov Alexander Mobile: +7-908-212-98-05https://www.linkedin.com/in/wind3style/ <http://www.svyazcom.ru/en/>E-mail:wind3style@gmail.com <http://www.svyazcom.ru> ---------- Forwarded message --------- From: Александр Федоров <wind3style(a)gmail.com> Date: ср, 26 сент. 2018 г. в 17:59 Subject: SIMtrace To: <hwelte(a)hmw-consulting.de> 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 <hwelte(a)hmw-consulting.de> This software is FREE SOFTWARE licensed under GNU GPL [000002] Version 0.5.27-5a40-dirty compiled 20180926-170104 by xmobi@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/ <http://www.svyazcom.ru/en/>E-mail:wind3style@gmail.com <http://www.svyazcom.ru>

4 3

SIM trace.
by Александр Федоров 26 Sep '18

26 Sep '18

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. -- Fedorov Alexander Head of IT-solution department LLC "Svyazcom" Mobile: +7-908-212-98-05http://www.svyazcom.ru/en/E-mail:wind3style@gmail.com <http://www.svyazcom.ru>

2 1

AT91SAM3 Based simtracer and firmware
by Gerard Bakker 26 Sep '18

26 Sep '18

Dear Osmocom, I have a question about the latest build of the simtrace2 based on the AT91SAM3.. 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) 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 .. Is this firmware working already ? (The website @sysmocom says "SIMtrace 2" will be available from late March 2018) Or am I missing something ? Thanks in advance.. Met vriendelijke groet/С наилучшими пожеланиями/With kind regards, [V-Tell] Gerard Bakker | ICT / Voice Engineer V-Tell Netherlands Glotell Telecom B.V. NL-Office +31 63 513 51 23 Willem Dreeslaan 37 NL-Mobile +31 64 202 21 06 2729 ND Zoetermeer, NL RU-Mobile +7 958 964 19 98 www.v-tell.nl<http://www.v-tell.nl/> US-Mobile +1 202 370 70 38 gerard.bakker(a)v-tell.nl<mailto:gerard.bakker@v-tell.nl> This message contains confidential information and is intended only for the individual named. Its content may not be disclosed, copied or transferred to any (third) party in whole or in part without the prior written permission of Glotell B.V. Please notify the sender immediately if you have received this email by mistake and delete this email from your system. Please do not print this email unless it is necessary. It helps to keep the environment forested and litter-free.

2 1

Debian/Ubuntu packages for simtrace2
by Harald Welte 26 Aug '18

26 Aug '18

Dear all, I've just merged changes that will automatically build the latest (tagged version) packages and nightly packages for simtrace2.git for firmware and host utilities. The "latest" have already been triggered: https://build.opensuse.org/package/show/network:osmocom:latest/simtrace2 "nightly" will be available after the next automatic build (7:49 PM UTC) For more information about osmocom nightly and latest binary packages, see https://osmocom.org/projects/cellular-infrastructure/wiki/Binary_Packages Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

OsmoCon 2018 draft schedule announced
by Harald Welte 16 Aug '18

16 Aug '18

Dear Osmocom community, the first schedule of the 2018 incarnation of OsmoCon 2018 has been announced, see http://osmocom.org/news/99 for the announcment and https://pretalx.sysmocom.de/osmocon2018/schedule/ for the actual schedule. At OsmoCon, we are not targetting developers, but more the wider community and Osmocom users. It would be great to meet many of you and hear more about your relation to Osmocom. Tickets are available from https://pretix.sysmocom.de/sysmocom/osmocon2018/, and until August 31st the early bird discount still applies. For those with a community / "just for fun" background and no employer that would cover the ticket, we have a number of subsidized community discount vouchers available. See the OsmoCon 2018 wiki page at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2018 for more information. Looking forward to meeting as many of you as possible in roughly two months from now, Harald Welte -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

RemoteSIM on Simtrace2
by Gabriel K. Gegenhuber 03 Aug '18

03 Aug '18

Hi all, I've got my hands on a simtrace2 device - first of all thanks for your great work and thanks for making this project open source! So far I've tried out the sniffing functionality which is working flawlessly - however I struggle to get the remote-sim functionality working. I've built (make BOARD=simtrace APP=cardem) the cardemulation-firmware of the current master-branch (0.4.131-8f70) and flashed the resulting simtrace-cardem-dfu.bin using dfu-util. Furthermore I compiled the host binaries, triggered a reset on my simtrace2 device to make sure it's in runtime mode and then executed the remote-sim program (sudo ./simtrace2-remsim -V 1d50 -P 60e3 -C 1 -I 0 -A `sudo ./simtrace2-list | cut -d = -f 2 | cut -d , -f 1 | tail -1`). The simtrace2 device, as well as an USB-CCID compliant omnikey cardreader are attached to my linux computer as described in the QMOD manual. During runtime mode the red LED on the simtrace2 is blinking, while the green LED is off. I noticed that when the simtrace2-remsim program tries to send an ATR to the simtrace2 device via usb (cardem_request_set_atr), the libusb_bulk_transfer function is blocking, before returning LIBUSB_ERROR_TIMEOUT. The serial debugging-output I got on the simtrace2 doesn't show any futher information (last state is "-I- USB is now configured"). When I reset the usb-modem that is connected to the simtrace2 device I get the following messages on the debug-serial: -I- Changed to ISO 7816-3 state 1 reset de-asserted -I- WT updated to 9600 -I- Changed to ISO 7816-3 state 0 reset asserted -I- Changed to ISO 7816-3 state 1 reset de-asserted [...] while the simtrace2-remsim program is also receiving some garbage: URB: -> 03 00 00 00 00 00 0c 00 04 00 00 00 unknown simtrace msg type 0x00 URB: -> 03 00 00 00 00 00 0c 00 08 00 00 00 unknown simtrace msg type 0x00 URB: -> 03 00 00 00 00 00 0c 00 04 00 00 00 unknown simtrace msg type 0x00 [...] I've also tried several older versions/commits - however I didn't get any of them working properly. When using version 0.4.13-ba2a (from this commit: https://git.osmocom.org/simtrace2/commit/?id=ba2ad563cc0e389213a3f6f6ebe79d…) I was able to send the ATR to the simtrace and directly entered the main loop on the host program. The serial debugging-output (after a manual modem-reset) also looked somehow more promising, but didn't work either: -I- 0: VCC activated -I- 0: CLK activated -I- 0: RST released -I- 0: computed Fi(1) Di(1) ratio: 372 -I- 0: send_tpdu_header: 00 a4 00 04 02 -I- 0: VCC deactivated -I- 0: CLK deactivated -I- 0: VCC activated -I- 0: CLK activated -I- 0: VCC deactivated -I- 0: CLK deactivated [...] I've also tried a few different modems/dongles (Huawei, ZTE) which also didn't really change anything. Am I missing something? Is the remote-sim functionality supposed to work on the current master branch? If not, could anyone hint me to a version/commit that should work? Would love to get some feedback - thanks in advance and keep up the good work! Greetings from Vienna, Gabriel

2 1

Problem in accessing SIMTrace 2
by Andrei Mikhailov 30 Jul '18

30 Jul '18

Dears, I have received SIMTrace 2 just now and I tried to connect it to PC with the same parameter as for previous version of SIMTrace. But I found that USB VENDOR ID and USB PRODUCT ID were changed. For the previous version they were 0x16c0 and 0x0762 correspondingly. All host sources at git://git.osmocom.org/simtrace.git repository use this parameters. Now I can see that VENDOR ID is 0x1d50 and PRODUCT ID is 0x60e3. Could you please help me to find USB connectivity parameters for the SIMTrace device which I received? -- /Best regards, Andrei Mikhailov /

3 6

CLA
by tchen 01 Jul '18

01 Jul '18

I noticed the modem issued command with CLA 0 (usim) or a0 (gsm)... just wondering what cause it to use 0 or a0??? Or does it try different CLA automatically

2 1

RESET error counter (0x2c) or unblock chv
by Thomas Chen 30 Jun '18

30 Jun '18

i am getting somethin like 00 2c 00 01 00 00 20 00 01 00 00 2c 00 81 00 i see somewhere 0x20 is defined as "verify chv" and 0x2c is defined as "unblock chv" but i also see somewhere else saying 0x2c is "reset error counter" can someone point me to where these commands are defined, and what kind of response are expected from SIM ??? thanks tom --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 2

Migrating simtrace2.git to gerrit / build verification
by Harald Welte 29 Jun '18

29 Jun '18

Hi Kevin and wider SIMtrace community, I've finally managed to set up a build verification jobs for the simtrace2 firmware, and in the process migrate simtrace2.git to gerrit. * https://jenkins.osmocom.org/jenkins/job/master-simtrace2/ is automatically * building the master branch for all apps/boards, * building the master branch of the host software * executing actual unit tests (currently only cardem) in "firmware/test" * https://jenkins.osmocom.org/jenkins/job/gerrit-simtrace2/ is triggered by gerrit and will perform automatic verification of any patches submitted for review (using the above-mentioned tests) In case anyone hasn't worked with gerrit before, please see https://osmocom.org/projects/cellular-infrastructure/wiki/gerrit for detailed information on how to set it up. @Kevin: You don't appear to have a gerrit account yet, so I couldn't give you the proper credentials. Let me know once you created the account, so I can give you credentials so you can continue to push to kredon/simtrace or related branches. Write access to the git.osmocom.org/simtrace2.git repository has been removed, only gerrit will replicate to that repository. I've also pushed tons of Kevin's fixes to master, leaving mainly the work on the "trace" firmware in "kredon/simtrace". You can rebase your branch cleanly on top of master. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

← Newer
1
...
11
12
13
14
15
16
17
...
35
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

simtrace