This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/simtrace@lists.osmocom.org/.
Myonium myonium at gmail.com>> Hi again, >> >> On Sun, Feb 12, 2012 at 02:46:37PM +0100, Myonium wrote: >> >>> Thank you for the fast reply. >>> Your assumption (speed issue) most probably right. It happened to me >>> with a new “Gemalto .NET v2.0” card which has baud rates up to >>> 223kbps. Would the simtrace device give me the transfer rate? How >>> would you suggest to measure it? >> >> If you look at the serial console, it should even tell you the >> negotiated PPS settings. So far there is no code to export this via USB >> t othe host PC, as far as I remember. However, it would be simple to >> add it in case you don't happen to have a matching serial cable. Please >> let me know. > > I've quickly implemented this, but don't have time to test it right now. > > Please update your simtrace host utility to rev. > b14d0ad2792d3f76ec21e141229840c736a2f23c or later, and use firmware > 4f7ca20bf40b911c035264d86ef0359d20e7ac88 or later. I've attached a > firmware image (for dfu-util flashing) for your reference. > > The simtrace program on the host pc should print something like > PPS(Fi=X/Di=Y) once a PPS happens, using the values that were obtained > from the acual PPS sniffing. Unfortunately ,there seems to be a bug in firmware rev. 4f7ca20bf40b911c035264d86ef0359d20e7ac88. I tested on my device "v1.1p": ATR don’t get through anymore. Just a “b3” byte. The smart card isn’t responding to a reset ... I had to go back to firmware “v0.4”. Than it is working again ... tried the process twice back and forth... will have a look at the code of the new revision next weekend. In the meantime I found a serial cable: On the console I get the following output: found Fi=9 Di=6 computed Fi(9) Di(6) ratio: 16 __pio_irq_demux(43): PIO_ISR_STATUS = 0x11e006d6 RST computed Fi(1) Di(1) ratio: 372 __pio_irq_demux(43): PIO_ISR_STATUS = 0x11800494 RST computed Fi(1) Di(1) ratio: 372 I compiled the firmware “v0.4” with DEBUG=0. About 1 of 5 runs, it works with no bytes lost. In the other 4 runs bytes are swallowed between URB chunks ... What do you think would be the maximum speed the current HW (v1.1) could handle (if tuned a little bit ;-) ? Thanks, Ben