Hello,
I am planning to use the nano sim based mobile phone. Could you please tell
me if its possible to use the SIM TRACER for the same. For example samsung
galaxy S9. By looking at the wiki I see the sim tracer would fit in for
standard sim slot, will the end point of the flex PCB fit the nano sim
holder of S9 ?.
Could any one please guide me on the same.
Best regards,
Sunil
Hello Osmocom community,
My hardware arrived and was exited to test it out.
But I get an error message: "Cannot read string: Resource temporarily
unavailable".
This happens when I run commands "./simtrace2-list" and
"./simtrace2-sniff". List command lists devices nicely.
Sniff command enters main loop but no communication is sniffed.
Have attached also a screenshot below.
But it happens 50% of the time, other than that it might start without the
warning message but does not track any communication from the SIM.
The SIM works nicely through SimTrace2 hardware, but sniffing does not.
I have made sure to follow the steps in Wiki and made sure that the
permissions are granted.
Help appreciated,
Ken-Tristan Peterson IoT Hacker & Community Manager
Mobile: +372 53 331 735
kentristan.peterson(a)1oT.mobi
<https://1ot.mobi/>
Dear fellow Osmocom developers,
I'm a bit surprised to notice that not more people have signed up for
OsmoDevCon 2019. I guess it was mostly an oversight when the date was
originally announced, and not a lack of interest? ;)
All details about the event are available at the related wiki page at:
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2019
Please enter your name at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCon2019#Requested
in case you would like to attend. Registering early allows proper
planning. Thanks!
Looking forward to meeting old and new Osmocom developers in April 2019.
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)
Dear all,
I would like to get your input as to when we should schedule OsmoDevCon 2019.
NOTE: OsmoDevCon is our "for developers by developers" event, not to be confused
with OsmoCon, our public conference.
If we want to stay with the usual "Friday through Monday in April" arrangement,
we have the following options:
April 05-08, 2019
April 12-15, 2019
April 26-29, 2019
The one missing weekend in the list above is the easter weekend, which is probably
a good idea to exclude as flights and hotels are more expensive during that time,
and people might have other plans during holidays.
I would like to invite anyone planning to attend the Osmocom Developer Conference 2019
to participate in the poll at https://dudle.inf.tu-dresden.de/OsmoDevCon2019/ to
state their availability/preference. The Dudle only shows the first day of the four
days of OsmoDevCon.
Looking forward to your feedback so we can settle on a date soon. Thanks!
Kind 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)
--
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>
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>
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.
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)
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)
