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.comFor completeness: With the un-patched v0.5 version (with byte lost) I get the following serial console output (switching back and forth): WRAP DURING APPEND ff VCC_PHONE off ... VCC_PHONE off VCC_PHONE off VCC_PHONE on RST computed Fi(1) Di(1) ratio: 372 nRST VCC_PHONE on RST computed Fi(1) Di(1) ratio: 372 VCC_PHONE on RST computed Fi(1) Di(1) ratio: 372 VCC_PHONE off VCC_PHONE on nRST VCC_PHONE off VCC_PHONE on RST computed Fi(1) Di(1) ratio: 372 found Fi=9 Di=6 computed Fi(9) Di(6) ratio: 16 RST computed Fi(1) Di(1) ratio: 372 RST computed Fi(1) Di(1) ratio: 372 nRST Begin forwarded message: > From: Myonium <myonium at gmail.com> > Subject: Re: New v0.5 simtrace firmware release > Date: March 26, 2012 9:06:21 PM GMT+02:00 > To: Harald Welte <laforge at gnumonks.org> > Cc: simtrace at lists.osmocom.org > > The output from the serial console is: > > nRST > LEN > BYTES_LEFT > CC_PHONE off > VCC_PHONE off > VCC_PHONE off > .... > VCC_PHONE off > VCC_PHONE off > VCC_PHONE off > VCC_PHONE off > WRAP DURING APPEND > VVCC_PHONE off > RST > computed Fi(1) Di(1) ratio: 372 > VCC_PHONE on > found Fi=9 Di=6 > computed Fi(9) Di(6) ratio: 16 > > I’m using also an Omnikey Cardman 3121. > “Gemalto .NET V2.0” supports baud rates up to 223Kbps. If you want me, I can sent you such a card for testing. Do you feel like testing such a card? > > > On Mar 26, 2012, at 10:43 AM, Harald Welte wrote: > >> It's quite funny. What Fi/Di value is your card using? Any idea what >> the frequency on CLK is? >> >> I have used a card with Fi/Di ratio of 64 on an Omnikey Cardman 3121 and >> was unable to trigger the problem. So in order to reproduce it, the CLK >> frequency and Fi/Di values would help. >> >> Also, when you look at the output of the statistics command on the >> serial line, do you actually see the overrun counter increasing? >