SCR331-DI Product Technical Manual
0x3B
Proprietary
0xFX
X indicates the number of bytes following
0x91
Proprietary
0x00
Proprietary
0xFF
Proprietary
0x91
Proprietary
0x81
Proprietary
0x71
Proprietary
0xFE
Proprietary
0x40
Proprietary
0x00
Proprietary
TYPEB
TYPE B parameter should be 0x42 as per PCSC2.0 specification
PUPI Length
Length of PUPI bytes that follow
PUPI
PUPI bytes of Length PUPI Length
CARD_PARAM1 CARD_PARAM1
CARD_PARAM2 CARD_PARAM2
CARD_PARAM3 CARD_PARAM3
TCk
The TCk byte in T = 1 protocol
¾
For Type B contact-less card the possible PUPI_LEN is 4.
¾
TYPE B parameter should be 0x42 as per PCSC2.0 specification
¾
CARD_PARAM1 indicates whether the card support memory card or T=CL card.
CARD_PARAM1 value of 0x00 indicates TYPE B memory card and value of 0x01 indicates
TYPE B T=CL card.
¾
CARD_PARAM2 contains Baud rate integer value
¾
CARD_PARAM3 contains Wait time integer, CID supported and NAD information. The higher
nibble contains the wait time integer. The bit 0 (lsb) of the lower nibble is a boolean indicating
whether the card supports NAD addressing and bit 1 of the lower nibble is a boolean
indicating whether the card supports CID.
4.5.5 PICC T=1 Emulation
PICC transmission part is simulated as PCSC 1.0 based T=1 protocol. All PCSC host APDU are
transferred in to the SCR331-DI firmware as CCID messages. As far as the SCR331-DI firmware is
concerned, it should accept only CCID messages for both ICC and PICC implementation. So the
application provides does not bother about the implementation of Host applications
.
IND.SCR331-DI.MANUAL.VER.1.8
VER1.8
Page 17 of 36
