From laforge at osmocom.org Tue Jun 1 17:07:44 2021 From: laforge at osmocom.org (Harald Welte) Date: Tue, 1 Jun 2021 19:07:44 +0200 Subject: Cardem under Manjaro/Arch: Some Troubleshooting In-Reply-To: References:

<42c57b1e-332c-0e40-b5b4-a66b756360c6@cs.ru.nl>

Message-ID: Hi Katherina and list, I think I've now fixed master, so 'cardem' versions from e33c2907bcc113fca8e189bc69c36383615523e9 (current master) upwards should work at least for basic use cases. At least they do on those phones I've tested so far (which is not a lot yet, admittedly). I've also updated our CI to actually build 'simtrace-cardem-dfu' images and publish those at https://ftp.osmocom.org/binaries/simtrace2/ which now has the build like https://ftp.osmocom.org/binaries/simtrace2/firmware/all/simtrace-cardem-dfu-0.7.0.106-79650.bin I'm currently looking at a potential problem regarding to PTS, where the log output of simtrace2-cardem-pcsc looks like this: ... everything looks great but then a block like his happens: SIMtrace <- 01 01 00 00 00 00 10 00 06 00 00 00 02 00 94 04 SIMtrace IRQ 01 04 00 00 00 00 15 00 13 00 00 00 00 00 01 01 0a 80 25 00 00 SIMtrace IRQ STATUS: flags=0x13, fi=1, di=1, wi=10 wtime=9600 SIMtrace IRQ 01 04 00 00 00 00 15 00 03 00 00 00 00 00 01 01 0a 80 25 00 00 SIMtrace IRQ STATUS: flags=0x3, fi=1, di=1, wi=10 wtime=9600 -> 01 07 00 00 00 00 15 00 04 ff 10 11 fe 00 00 ff 10 11 fe 00 00 => PTS req: ff 10 11 fe 00 00 -> 01 06 00 00 00 00 13 00 01 00 00 00 05 00 00 a4 00 04 02 => DATA: flags=1, 00 a4 00 04 02 : <= osmo_st2_cardem_request_pb_and_rx(a4, 2) SIMtrace <- 01 01 00 00 00 00 0f 00 08 00 00 00 01 00 a4 -> 01 06 00 00 00 00 10 00 02 00 00 00 02 00 3f 00 => DATA: flags=2, 3f 00 : SW=0x6e00, len_rx=0 <= osmo_st2_cardem_request_sw_tx(6e 00) SIMtrace <- 01 01 00 00 00 00 10 00 06 00 00 00 02 00 6e 00 -> 01 06 00 00 00 00 13 00 01 00 00 00 05 00 00 a4 00 04 02 => DATA: flags=1, 00 a4 00 04 02 : <= osmo_st2_cardem_request_pb_and_rx(a4, 2) SIMtrace <- 01 01 00 00 00 00 0f 00 08 00 00 00 01 00 a4 -> 01 06 00 00 00 00 10 00 02 00 00 00 02 00 3f 00 => DATA: flags=2, 3f 00 : SW=0x6e00, len_rx=0 <= osmo_st2_cardem_request_sw_tx(6e 00) SIMtrace <- 01 01 00 00 00 00 10 00 06 00 00 00 02 00 6e 00 where we see a PTS is happening, and afterwards a seemingly innocent APDU like "00 a4 00 04 02 3f 00" (SELECT MF) results in SW 6e00: Checking errors - Class not supported -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at osmocom.org Tue Jun 8 13:28:11 2021 From: laforge at osmocom.org (Harald Welte) Date: Tue, 8 Jun 2021 15:28:11 +0200 Subject: Announcement of "OsmoDevCall" on June 11, 2021 Message-ID: Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall at June 11, 2021 at 20:00 CEST at https://meeting4.franken.de/b/har-xbc-bsx-wvs This meeting will have the following schedule: 20:00 meet + greet 20:15 presentation by keith: "Screen Sharing peek at TIC A.C. infrastructure in Oaxaca" 21:00 USSE: unstructured supplementary social event [*] 22:00 close of call TIC A.C. is an operator of Osmocom based community cellular networks in indigenous communities of the Mexican state of Oaxaca. Keith works with Rhizomatica and TIC A.C. and will give us some live insight into how they operate Attendance is free of charge and open to anyone with an interest in Osmocom. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From pro100monetka at gmail.com Wed Jun 9 09:13:08 2021 From: pro100monetka at gmail.com (Joe Koteyko) Date: Wed, 9 Jun 2021 12:13:08 +0300 Subject: Sim card traffic is not shown in the simtrace-sniff application Message-ID: Hello! We purchased your product (simtrace2) to produce sniff sim cards. I did all the steps to install simtrace2 for HostPC (Preconditions, Compiling, Accessing) I made sure that the computer recognizes the simtrace2 device via the simtrace2-list application. But when the simtrace2-sniff application is launched, only the application greeting, the usb device used and the inscription "Entering main loop" are shown. When sending messages to a sim card, the light indicators on the simtrace2 board start to respond to this SMS, but nothing happens in the output of the simtrace2-sniff application on the computer. What could be the reason for this problem? Please help me figure it out, if possible. Best regards, Dmitry -- *WITH BEST WISHES * DMITRY KRYMOV -------------- next part -------------- An HTML attachment was scrubbed... URL: