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/.
Vishal Vaidhyanathan Vishal.Vaidhyanathan at privoro.comHi Holger, You said simtrace doesn’t show PTS related information. Is there an option to enable it and see it on Wireshark? How do I enable debug mode? Thanks, Vishal > On Jul 14, 2017, at 10:23 AM, Holger Freyther <holger at freyther.de> wrote: > > >> On 14. Jul 2017, at 19:13, Vishal Vaidhyanathan <Vishal.Vaidhyanathan at privoro.com> wrote: >> >> Hi, > > Hi! > > >> Sorry about that. Didn’t realize I was taking it private. I’ve a couple more questions. If the ATR comes back at 9600, doesn’t it stay the same until we send PPS? > > Right. > >> So I went through that link, according to that, after ATR, we use the Fi and Di values to calculate UART Baud rate and send commands in that rate? But I want to know what baud rate the phone uses? Does it change using PPS? Wireshark doesn’t show any PPS after ATR. Does that mean the phone read the ATR and adjusted the clock accordingly? Basically I’m trying to sniff the entire phone communication to SIM in a file and I need the correct Baud rate to do that? > > You are right. If you look at process_byte it will not forward PTS related bytes (goto out_silent). At least in the debug output of the SIMtrace you should be able to see fi/di changes. > > holger > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: Message signed with OpenPGP URL: <http://lists.osmocom.org/pipermail/simtrace/attachments/20170717/aec7c8d8/attachment.bin>