2 Mar
2017
2 Mar
'17
8:30 p.m.
Before proceed with oscilloscope, I do a last test using simtrace and a
Samsung Galaxy S3 with this UICC and surprisingly it works, so I have the
ATR APDU: 3b 9f 96 c0 0a 3f c7 a0 80 31 e0 73 fe 21 1b 65 d0 01 74 0e a1
81 0f 9c
From there; Fi=512, Di=32, Protocol T=0, class accepted
by the card: A, B
and C (
https://smartcard-atr.appspot.com/parse?ATR=3b9f96c00a3fc7a08031e073fe211b6…
)
After this, I test over and over again with the same UICC card and an
iPhone6 but never got ATR response, just got "ATR APDU: " and iPhone don't
recognize SIM card. SCR3310 reader never recognizes the card, always "Card
state: Card inserted, Unresponsive card" response.
I test simtrace/iPhone6 and SCR reader using same UICC type from other
operator with same results (but working with simtrace/S.Galaxy S3)
Regards,
Pedro
2017-03-01 13:16 GMT+01:00 Harald Welte <laforge(a)gnumonks.org>rg>:
I think the best way to analyze this is to understand
the exact voltage,
clock rate and Fi/Di values your card is operating on on the working
reader(s). Most likely at least one of the parameters is different on
the non-working readers.
You should be able to figure all the related values out if you talk
CCID directly to the USB device, or extend / "hack up" the ccid driver
you're using. Alternatively, an oscilloscopse should also be able to
tell you related information.
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)