Hi all,
I have meanwhile solved the first half of the bug that was causing a lot
of problems during the CCC Camp 2011.
In git commit fa7297b93f4187bce9439bb676874815f66d8f21 to openpcd.git,
I have made the following changes:
* make sure SIMtrace remains completely passive even in case of
(alleged) parity errors
* prevent an IRQ storm by properly clearing error flags in the USART,
which have lead to a watchdog triggered reset which in turn caused
a USB disconnect
So right now, you should not see the "No SIM card" or "SIM card error"
in the display of your phone, no matter what phone / simcard is used.
However, the data logged by SIMtrace still is incorrect in those cases.
I hope to release a fix for that soon.
The updated 'main_simtrace.bin' firmware is attached to this mail. You
can install it by using
"dfu-util -d 16c0:0762 -a0 -D ./main_simtrace.bin -R"
which should produce something like:
=======
dfu-util - (C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.
This program is Free Software and has ABSOLUTELY NO WARRANTY
dfu-util does currently only support DFU version 1.0
Opening USB Device 0x16c0:0x0762...
Claiming USB DFU Runtime Interface...
Determining device status: state = appIDLE, status = 0
Device really in Runtime Mode, send DFU detach request...
Resetting USB...
Opening USB Device...
Found Runtime: [0x16c0:0x0762] devnum=41, cfg=0, intf=0, alt=0,
name="SimTrace DFU Interface - Application Partition"
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Device returned transfer size 256
bytes_per_hash=415
Copying data from PC to DFU device
Starting download: [##################################################]
finished!
state(7) = dfuMANIFEST, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!
can't detach: error sending control message: Broken pipe
Resetting USB to switch back to runtime mode
========
After that, the new firmware has been programmed into your SIMtrace and
you can immediately use it again (no reset/re-plug/... needed)
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)
Hi all,
I have a stupid schematic question. I read section 6.2 of the SAM7 datasheet
(as in the git tree) and it mentions that besides TST high also
PA0, PA1 and PA2 needs to be high, and PA0, PA1 should not be low as this
leads to unpredictable results.
So I wonder about the following:
- PA0 is not connected, default state should be high
- PA1 is connected with a trace that leads to PA6
- PA2 is connected with a trace that leads to PA4
will PA4, PA6 work like a pull down (I am not sure of Table 10-3)?
cheers
holger
Hello!
I skimmed over the schematic and noticed that the power output from the
FTDI cable is connected directly to the 3.3V line. In my experience the
output from the FTDI cable is 5V even though it is the 3.3V version. I
have actually fried some designs due to this.
I'm not 100% sure about this, but my tips is to check it before you
connect it.
Best regards,
/Stefan
Hi all,
there is a doc/ directory in the simtrace source and the documentation is done
with docbook. The result of the document can be seen here[1].
It is still missing proof reading, sections on building the patched wireshark,
building the firmware and more content.
comments welcome
holger
[1] http://bb.osmocom.org/trac/attachment/wiki/SIMtrace/usermanual.pdf
Hi all!
I know it's a bit on short hand notice now, but maybe somebody is
interested in doing a SIMtrace poster that we can put up in the Radio
Village at the CCC Camp.
It doesn't have to be super-fancy / super-glossy, just something that
draws a bit of attention that SIMtrace is present there, and what it is.
Some ideas for bullet points:
* trace communication between phone and SIM
* man-in-the-middle
* analyze + debug SIM Toolkit
* analyze proactive SIM
* SIM firewall
* SIM card emulation
Printing the poster shouldn't be a problem, if somebody just wants to do
the design as SVG.
Thanks in advance if anyone finds time for doing it...
--
- 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)
Hi!
It took me quite a long time to fix all the bugs I discovered in the
at91lib USB stack, particularly in the CCID code. The next problem was
that the core USB code could not deal wit devices that implement
multiple configurations correctly.
But finally I got it to work. There is now a multi-configuration
project which is part of the git://git.gnumonks.org/at91work.git git
repository. Curious people can type 'make' in the
usb-device-multi-project sub-directory, which will render a
usb-device-multi-project-simtrace-at91sam7s128-flash_dfu.bin
file.
That file can be flashed into the simtrace using dfu-util like this:
dfu-util -a0 -D ./usb-device-multi-project-simtrace-at91sam7s128-flash_dfu.bin -R
The firmware doesn't really do anything yet, but it should show up on
USB as a device with three configurations (one for sniffer, one for
reader and one for MITM).
I've started to port over my sniffer code from the openpcd repository,
but I'm not sure when I'll have time to finish it. Maybe still before
the camp, we'll see...
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)
Hi all,
the 100 SIMtrace production units have recently arrived from the SMT
factory. While this is good news, there are some bad news as well:
1) blocking capacitor C12 too far from LDO causing power oscillations
This problem can easily be re-worked by manually soldering a
capacitor immediately to the LDO input pin. Even though 60-75% of
the units seem to work without the re-work, we're adding it to make
sure there are no issues later on.
2) something like 20 to 25% of the units have some problem related to
the initial programming of the SAM-BA loader. Everything works fine
if the flashing is been done via JTAG, or later using sam7dfu +
dfu-util. The problem is still under investigation, but despite
something like 6 hours debugging and soldering additional capacitors,
even replacing the entire SAM7S have not rendered any results.
Please don't ask me to ship some units yet, as we are still testing
them. As per our original schedule, we will start to sell them at the
CCC Camp and then offer a webshop from the second half of August
onwards.
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)