I have simtrace working with a debian VM.
It works consistently with 2G cards, but stop working with 3G let cards. Seems to boot and then stops.
Has this been fixed?
I read about reducing the buffer in the firmware, but this is a challenge creating a bin file as arm-elf is no longer supported and creating a cross compiling toolchain with modern compiler is posing problems.
Do you have a bin firmware file with a reduced buffer that works with sim lte cards?
Hi,
I got the hardware kit of the SIMtrace.
It booted successfully (I guess because I got the red light on the board).
Then I connected the jumper to the test pin (I read the user manual so I
act according to it). When it booted up, I got green and red lights.
After I tried to power it on again without the jumper, I got nothing (no
light) and no recognition with lsusb command.
I tried to connect the board to other PC, and still no lights.
How can I fix it?
Thanks in advance!
Bests,
Gal
Hi all,
My name is Richard Hughes and I work for Red Hat. I'm the maintainer
of fwupd, an open source firmware update system designed for Linux.
We're updating thousands of devices every month safely and securely
using the fwupd and the Linux Vendor Firmware Service. I'm also the
guy behind the OpenHardware ColorHug device, so I'm particularly
interested in making firmware updates easy to apply on open source and
free software devices. I see SIMtrace is using DFU, and fwupd can
already talk to DFU-using devices using the libdfu library so I don't
think any actual additional code would be required in fwupd. For your
device, it would just be creating a cabinet with the required metadata
included.
If this is interesting, please see http://www.fwupd.org/ or email me
back for more details. I can create you a dummy account on the LVFS if
you'd like to upload some test firmware. If your device doesn't have
any firmware updates, and you don't plan of issuing any, please
disregard this email. Thanks for reading!
Richard.
hello team,
sorry this is a test email.
not sure if this email reach the list.
I am just wondering on where to check if new version of simtrace is on the road map, or not...
thanks so much for the great work!!
Victor
Hello --
Do you have a package for iPhone?
Cheers,
Stephen
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential,
proprietary, and/or privileged information protected by law. If you are not
the intended recipient, you may not use, copy, or distribute this e-mail
message or its attachments. If you believe you have received this e-mail
message in error, please contact the sender by reply e-mail and destroy all
copies of the original message.
Hi,
I want to share with you complete MitM solution. The project is based on
at91work. The solution allows to specify which file or instruction you want
to modify. You might also edit SIM files on the fly - apdu is not sent on
the basic channel so communication with phone is not interrupted. Simtrace
firmware has two variants: apdu forwarding and PC/SC reader.
Detailed information can be found in
https://github.com/kamwar/simlab/wikihttps://github.com/kamwar/simlabTrace/wiki
Best Regards,
Kamil
Dear all,
IN-Berlin has confirmed the dates in April where we could book the
venue.
Can those eligible + interested in attending please quickly indicate
their preference at http://doodle.com/poll/if263cpxieavsqiq ?
Thanks!
Disclaimer: OsmoDevCon is an invitation-only event for developers with
proven history of contributing to any of the Osmocom projects. The fact
that there is a public poll about the scheduling of the event and/or
your participation in that poll does not mean a particular applicant is
invited.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
Hi Holger,
On Thu, Feb 04, 2016 at 08:12:19AM +0100, Holger Freyther wrote:
> I think some of us would like to move to redmine and start using
> public tickets more frequently. So in case we move there are some
> topics to be discussed and I would like to start with a couple of them
> right now.
Thanks for getting the public discussion about this started.
To give some more background to the mailing list:
* The trac installations at osmocom.org are pretty much
underused/dormant. The only part that's used is the Wiki.
* Osmocom started when a single project (OpenBSC) got a sister project
(OsmocomBB) and has grown into many projects. Running a single trac
instance for each project on a separate dns hostname is overkill.
Also, as code is shifted around between libraries and programs, we'd
appreciate some flexibility.
* at sysmocom internally we have successfully used redmine for dozens of
different projects. The project hierarchy can be changed as needed on
the fly, and issues can relate to issues of other projects, shifted
from project to project, etc.
* Quite a bit of the work we do at sysmocom on the Osmocom software
should have the issue tracker for bugs and features in the public, but
as our internal redmine is so much easier than the public trac setup,
we kept using the internal redmine.
So my plan moving forward is to migrate all Osmocom projects (initially
those related to GSM) to a public redmine, and then keep all issues
updated there. This would give more visibility into the work we're
doing, such as the EDGE PCU, the 3G NITB + SGSN, the HNB-GW, etc.
> Redmine has a global linear sequence of ticket numbers. If we move
> from many tracs to a single redmine we can either:
>
> * not import tickets
> * only import from one project
> * deal with changing ticket numbers
I think not importing tickets or dealing wih changing numbers is the way
to go.
> In terms of installations the GMR trac is broken in regard to tickets,
> there are some for SDR that are probably not being fixed anytime soon,
> baseband might be relevant and OpenBSC is unlikely to be relevant. I
> don't think we have ever used ticket reference in OpenBSC commit
> messages so in terms of OpenBSC having changing ticket numbers would
> not be a big deal. E.g. we could add a custom field with the old trac
> number?
If there is automatic import/conversion available, I'd prefer to import
the OsmocomBB, SIMtrace, (non-spam) Security and OpenBSC tickets, even
though most of them are probably stale and outdated for years. They're
still part of the history. Changing the numbers doesn't matter, as we
don't refer to them.
> We have external references that should be redirected to the new
> place. Is there any way besides maintaining a list in the
> apache2/nginx configuration and making redirects as we find broken
> references? Can we proactively manage this? Is anybody willing to come
> up with a script and nginx configuration for doing this?
I'm not aware of any tools that might be able to help here.
Indeed, it would be great if anyone would volunteer to generate a script
to generate the redirects.
I guess the old format is e.g.
http://openbsc.osmocom.org/trac/wiki/nanoBTS/Internals
and the new URL would be something like
http://projects.osmocom.org/redmine/openbsc/wiki/nanoBTS/Internals
Or should we strip even the redmine from the URL?
And should we have a rewrite for http://openbsc.osmocom.org/redmine to
http://projects.osmocom.org/redmine/openbsc ?
Any ideas?
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)
