SCM Microsystems SDI010 dual interface reader Reference Manual

ಪಿಡಿಎಫ್

ದಾಖಲೆ

ಜಾಹಿರಾತು

SCM Microsystems
Reference Manual – version 1.14
SDI010
Dual interface (contactless and contact) stationary reader
Reference manual
SDI010 Dual Interface (Contactless and Contact)
Stationary Reader
&copy; SCM Microsystems
Oskar-Messter-Strasse, 13
85737 Ismaning
Germany
Phone +49 89 9595 5000 • Fax +49 89 9595 5555
Document history
Date
Version
Description of change
13/04/2009
1.14
Major changes to earlier versions. Inline with the new manual
templates.
Contact information
http://www.scmmicro.com/products-services/smart-card-readers-terminals/contactless-dualinterface-readers.html
For sales information, please email [email protected]
Table of Contents
1.
Legal information ............................................................................................................... 9
1.1.
Disclaimers..................................................................................................................... 9
1.2.
Licenses ......................................................................................................................... 9
1.3.
Trademarks .................................................................................................................... 9
2.
Introduction to the manual ............................................................................................... 10
2.1.
Objective of the manual ............................................................................................... 10
2.2.
Target audience ........................................................................................................... 10
2.3.
Product version corresponding to the manual ............................................................. 10
2.4.
Definition of various terms and acronyms .................................................................... 11
2.5.
References ................................................................................................................... 12
2.6.
Conventions ................................................................................................................. 13
3.
General information about SDI010 .................................................................................. 14
3.1.
SDI010 key benefits ..................................................................................................... 14
3.2.
SDI010 key features..................................................................................................... 14
3.3.
SDI010 ordering information ........................................................................................ 15
3.4.
SDI010 customization options...................................................................................... 15
3.5.
Contactless communication principles and SDI010 usage recommendations ............ 16
3.5.1.
Power supply......................................................................................................... 16
3.5.2.
Data exchange ...................................................................................................... 16
3.5.3.
Recommendations ................................................................................................ 17
3.6. Applications .................................................................................................................. 18
3.6.1.
3.6.2.
4.
General ................................................................................................................. 18
Applications provided by SCM Microsystems....................................................... 18
SDI010 characteristics ..................................................................................................... 19
4.1.
SDI010 high level architecture ..................................................................................... 19
4.1.1.
Block diagram ....................................................................................................... 19
4.1.2.
Software architecture ............................................................................................ 20
4.2. Quick reference data .................................................................................................... 21
4.2.1.
4.2.2.
4.2.3.
5.
SDI010 dimensions............................................................................................... 21
LED behavior ........................................................................................................ 22
Other data ............................................................................................................. 23
Software modules ............................................................................................................ 25
5.1.
Installation .................................................................................................................... 25
5.2.
Utilities .......................................................................................................................... 25
5.3.
Driver ............................................................................................................................ 25
5.3.1.
SDI010 listing ........................................................................................................ 25
5.3.2.
Supported operating systems ............................................................................... 26
5.3.3.
PC/SC 2.0 compliant ATR for contactless interface ............................................. 26
5.4. Firmware ...................................................................................................................... 29
5.4.1.
CCID transport protocol ........................................................................................ 29
5.4.2.
6.
Automatic PPS for the contactless interface......................................................... 30
Commands description .................................................................................................... 31
6.1.
Generic APDU.............................................................................................................. 31
6.1.1.
Get UID Command ............................................................................................... 31
6.1.2.
Escape command APDU ...................................................................................... 33
6.2. Set of APDU for contactless storage user tokens........................................................ 34
6.2.1.
STORAGE_CARD_CMDS_READ_BINARY ........................................................ 34
6.2.2.
STORAGE_CARD_CMDS_WRITE_BINARY ...................................................... 36
6.2.3.
STORAGE_CARD_CMDS_LOAD_KEYS ............................................................ 38
6.2.4.
STORAGE_CARD_CMDS_AUTHENTICATE...................................................... 39
6.2.5.
STORAGE_CARD_CMDS_VALUE_BLOCK ....................................................... 41
6.3. Set of APDU for ISO/IEC14443-4 user tokens ............................................................ 42
6.3.1.
T=CL Command.................................................................................................... 42
6.3.2.
T=CL user command ............................................................................................ 43
6.4. Set of APDU defined by SCM Microsystems ............................................................... 44
6.4.1.
MIFARE DESFire Commands .............................................................................. 44
6.5. Escape commands for the contactless interface ......................................................... 45
6.5.1.
Sending escape commands to SDI010 ................................................................ 45
6.5.2.
Escape command codes....................................................................................... 45
6.5.3.
READER_GETCARDINFO................................................................................... 46
6.5.4.
READER_LED_CONTROL_BY_FW .................................................................... 47
6.5.5.
READER_LEDCONTROL .................................................................................... 47
6.5.6.
READER_CNTLESS_GET_MFRC_REV ............................................................. 47
6.5.7.
READER_CNTLESS_GET_ATS_ATQB .............................................................. 48
6.5.8.
READER_CNTLESS_GET_TYPE ....................................................................... 48
6.5.9.
READER_CNTLESS_SET_TYPE ........................................................................ 48
6.5.10. READER_CNTLESS_RF_SWITCH ..................................................................... 49
6.5.11. READER_CNTLESS_RAW_CFG ........................................................................ 49
6.5.12. READER_CNTLESS_RAW_XMIT_EX ................................................................ 50
6.5.13. READER_ CNTLESS_DISABLE_PPS ................................................................. 51
6.5.14. READER_SWITCH_RF_ON_OFF ....................................................................... 51
6.5.15. READER_CNTLESS_848KBPS........................................................................... 52
6.5.16. READER_CNTLESS_BAUDRATE....................................................................... 53
6.5.17. READER_CNTLESS_FORCE_BAUDRATE_PCSC_REV2 ................................ 54
6.6. Escape commands for the contact interface ................................................................ 55
6.6.1.
6.6.2.
6.6.3.
6.6.4.
6.6.5.
6.6.6.
6.6.7.
6.6.8.
6.6.9.
6.6.10.
Sending escape commands to SDI010 ................................................................ 55
Escape command codes....................................................................................... 55
READER_SETMODE ........................................................................................... 55
READER_GETMODE........................................................................................... 56
READER_APDU_TRANSFER.............................................................................. 56
READER_SWITCH_SPEED................................................................................. 57
READER_SWITCH_PROTOCOL......................................................................... 57
READER_DISABLE_PPS..................................................................................... 58
READER_GETIFDTYPE ...................................................................................... 58
READER_GETINFO_EXTENDED ....................................................................... 59
7.
Annexes ........................................................................................................................... 60
7.1.
Annex A – Status words table ...................................................................................... 60
7.2.
Annex B – Sample code using escape commands through Escape IOCTL ............... 61
7.3.
Annex C - SCM Proprietary CLA bytes ........................................................................ 66
7.4.
Annex D – Mechanical drawings.................................................................................. 67
7.4.1.
7.4.2.
7.4.3.
Top Casing............................................................................................................ 67
Bottom Casing ...................................................................................................... 68
Stand..................................................................................................................... 69
SDI010 REFERENCE MANUAL
1. Legal information
1.1.
Disclaimers
The content published in this document is believed to be accurate. SCM Microsystems does
not, however, provide any representation or warranty regarding the accuracy or completeness
of its content and regarding the consequences of the use of information contained herein. If this
document has the status “Draft”, its content is still under internal review and yet to be formally
validated.
SCM Microsystems reserves the right to change the content of this document without prior
notice. The content of this document supersedes the content of previous versions of the same
document. The document may contain application descriptions and/or source code examples,
which are for illustrative purposes only. SCM Microsystems gives no representation or warranty
that such descriptions or examples are suitable for the application that the reader may want to
use them for.
Should you notice problems with the provided documentation, please provide your feedback to
[email protected].
1.2.
Licenses
If the document contains source code examples, they are provided for illustrative purposes only
and subject to the following restrictions:
•
You MAY at your own risk use or modify the source code provided in the document
in applications you may develop. You MAY distribute those applications ONLY in
form of compiled applications.
•
You MAY NOT copy or distribute parts of or the entire source code without prior
written consent from SCM Microsystems.
•
You MAY NOT combine or distribute the source code provided with Open Source
Software or with software developed using Open Source Software in a manner that
subjects the source code or any portion thereof to any license obligations of such
Open Source Software.
If the document contains technical drawings related to SCM Microsystems products, they are
provided for documentation purposes only. SCM Microsystems does not grant you any license
to its designs.
1.3.
Trademarks
MIFARE is a registered trademark of NXP Semiconductors BV.
Windows is a trademark of Microsoft Corporation.
9
SDI010 REFERENCE MANUAL
10
2. Introduction to the manual
2.1.
Objective of the manual
This manual provides an overview of the hardware and software features of the SDI010 dual
interface (contactless and contact) reader, hereafter referred to as “SDI010”.
This manual describes in details interfaces and supported commands available for developers
using SDI010 in their applications.
2.2.
Target audience
This document describes the technical implementation of SDI010.
The manual targets software developers. It assumes knowledge about 13.56 MHz contactless
technologies like ISO/IEC 14443 and commonly used engineering terms.
Should you have questions, you may send them to [email protected] .
2.3.
Product version corresponding to the manual
Item
Version
Hardware
1.0
Firmware
7.33
Driver
5.15
SDI010 REFERENCE MANUAL
2.4.
11
Definition of various terms and acronyms
Term
Expansion
APDU
ATR
ATS
Byte
CCID
CID
CL
DFU
DR
DS
LED
MIFARE
NA
NAD
Nibble
Application Protocol Data Unit
Answer to Reset, defined in ISO7816
Answer to select, defined in ISO/IEC 14443
Group of 8 bits
Chip Card Interface Device
Card Identifier
Contactless
Device Firmware Upgrade
Divider receive: used to determine the baud rate between the reader to the card
Divider send: used to determine the baud rate between the card to the reader
Light emitting diode
The ISO14443 Type A with extensions for security (NXP)
Not applicable
Node Address
Group of 4 bits. 1 digit of the hexadecimal representation of a byte.
Example: 0xA3 is represented in binary as (10100011)b. The least significant nibble is 0x3
or (0011)b and the most significant nibble is 0xA or (1010)b
Proximity Coupling Device
Personal Computer/Smart Card: software interface to communicate between a PC and a
smart card
Proximity Integrated Chip Card
Product ID
Distance coverage till ~10 cm.
Pseudo unique PICC identifier
Reserved for future use
Radio Frequency
Smart card reader controller ASIC from SCM Microsystems
Universal Serial Bus
Vendor ID
Binary notation of a number x, y, z ∈{0,1}
The byte value YY is represented in hexadecimal
PCD
PC/SC
PICC
PID
Proximity
PUPI
RFU
RF
STCII
USB
VID
(xyz)b
0xYY
SDI010 REFERENCE MANUAL
2.5.
12
References
Doc ref in
the manual
Description
Issuer
ISO/IEC 78163
Identification cards — Integrated circuit
ISO / IEC
ISO/IEC 78164
cards — Part 3: Cards with contacts — Electrical
interface and transmission protocols
Identification cards - Integrated circuit(s) cards with
contacts
Part 4: Interindustry commands for interchange
ISO/IEC 7816-4: 1995 (E)
ISO/IEC
14443-3
Identification cards — Contactless
integrated circuit(s) cards — Proximity
ISO/IEC
14443-4
PC/SC
CCID
USB
cards — Part 3: Initialization and anticollision
Identification cards — Contactless integrated
circuit(s) cards — Proximity cards
Part 4: Transmission protocol ISO/IEC 144434:2001(E)
Interoperability Specification for ICCs and Personal
Computer Systems v2.01
Specification for Integrated Circuit(s) Cards
Interface Devices 1.1
Universal Serial Bus Specification 2.0
ISO / IEC
ISO / IEC
ISO / IEC
PC/SC Workgroup
USB-IF
USB-IF
SDI010 REFERENCE MANUAL
2.6.
Conventions
Bits are represented by lower case ‘b’ where followed by a numbering digit.
Bytes are represented by upper case ‘B’ where followed by a numbering digit.
Example:
163 decimal number is represented
•
in hexadecimal as 0xA3
•
in binary as (10100011)b
The least significant nibble of 0xA3 is
•
0x3 in hexadecimal
•
(0011)b in binary
The most significant nibble of =xA3 is
•
0xA in hexadecimal
•
(1010)b in binary
13
SDI010 REFERENCE MANUAL
14
3. General information about SDI010
3.1.
SDI010 key benefits
With its combination of a modern slim design and its state of the art feature set, SDI010 is the
perfect desktop reader choice for environments where both contact and contactless smart card
support is required. Such environments may be corporate where physical and logical access
control is implemented.
As for all SCM Microsystems products, SDI010 is designed to offer best in class interoperability
with various formats of tokens: cards, dongles, watches or NFC mobile phones.
Its infield upgradeable firmware makes SDI010 a secure and future-proof investment providing
both flexibility and fast time to market for new applications as well as minimum risk linked to
contactless technology standards evolution.
3.2.
•
SDI010 key features
13.56MHz contactless reader:
o
ISO14443 type A &amp; B,
o
MIFARE
•
ISO7816 compliant contact smart card reader
•
PC/SC v2.0 compliant
•
In field upgradeable firmware
•
Unique serial number which enables that SDI010 can be plugged into any USB slot
on a PC without having to re-install the driver.
SDI010 REFERENCE MANUAL
3.3.
15
SDI010 ordering information
Item
Part number
SDI010
904671
Contactless SDK
905124
Contact SDK
905129
3.4.
SDI010 customization options
Upon request, SCM can customize:
•
The color of the casing
•
The logo
•
The product label
•
The USB strings
Terms and conditions apply, please contact your local SCM representative or send an email to
[email protected].
SDI010 REFERENCE MANUAL
16
3.5.
Contactless communication principles and SDI010
usage recommendations
SDI010 is a dual interface reader capable of reader both contact smart cards and contactless
user tokens. The following paragraph focuses on a few specifics of the contactless
communication to outline usage recommendations in order to ensure best user experience.
SDI010 is a contactless reader1 designed to
communicate with user tokens.
User tokens2 are made of a contactless
integrated circuit card connected to an
antenna
User tokens
•
Credit card sized smart card
•
Key fob
•
NFC mobile phone etc…
Communication between SDI010 and user
tokens uses magnetic field inductive
coupling.
SD
I01
0
User tokens can take several form factors:
SDI010
The magnetic field generated by SDI010 has a carrier frequency of 13.56MHz.
3.5.1. Power supply
When the user token is put in the magnetic field of the reader, its antenna couples with the
reader and an induction current appears in the antenna thus providing power to the integrated
circuit. The generated current is proportional to the magnetic flux going through the antenna of
the user token.
3.5.2. Data exchange
The carrier frequency of the magnetic field is used as a fundamental clock signal for the
communication between the reader and the card. It is also use as a fundamental clock input for
the integrated circuit microprocessor to function.
To send data to the user token the reader modulates the amplitude of the field. There are
several amplitude modulation and data encoding rules defined in ISO/IEC 14443. The reader
should refer to the standard for further details.
To answer to the reader, the integrated circuit card of the user token modulates its way of
loading (impedance) the field generated by the reader. Here also further details can be found in
ISO/IEC 14443.
1
In the ISO/IEC 14443 standard, the reader is called the proximity coupling device (PCD)
2
In the ISO/IEC 14443 standard, the user token is called proximity integrated chip card (PICC)
SDI010 REFERENCE MANUAL
17
3.5.3. Recommendations
The communication between the reader and the user token is sensitive to the presence of
material or objects interfering with the magnetic field generated by the reader.
The presence of conductive materials like metal in the vicinity of the reader and the user token
can severally degrade the communication and even make it impossible. The magnetic field of
the reader generates Eddy or Foucault’s currents in the conductive materials; the field is
literally absorbed by that kind of material.
It is recommended for proper communication to avoid putting SDI010 in close
proximity of conductive materials.
The presence of multiple user tokens in the field also interferes with the communication. When
several user tokens are in the field of the reader, load of the field increases which implies that
less energy is available for each of them and that the system is detuned. For this reason, SCM
Microsystems has implemented in its driver only 1 slot by default. This means that in the event
several user tokens are in the field of the SDI010, only one will be active. It is possible using
INF configuration to enable up to 4 slots – i.e. to activate up to 4 user tokens nevertheless the
depending on the power consumption of the user tokens communication cannot be guarantied.
It is recommended to present only one user credential at a time in front of
SDI010.
Please note that multiple contactless slots feature is supported but is kept disabled by default.
The SDI010 driver on configuration allows the presence and use of several PICCs (maximum 4) at
the same time. The driver can support multiple logical connections and present each of them as a
slot logical device to the Resource Manager and higher components. Also the simultaneous working
of multiple Contactless cards is not guaranteed and depends on the antenna size and the power
requirements of the card.
The communication between the reader and the user token is sensitive to the geometry of the
system {reader, user token}. Parameters like the geometry and specially the relative size of the
reader and user token antennas directly influence the inductive coupling and therefore the
communication.
SDI010 was primarily designed and optimized to function with user credentials of various
technologies having the size of a credit card.
It may happen that SDI010 is not capable of communicating with extremely
large or extremely small antennas.
In order to optimize the coupling between the reader and the user token, it is
recommended to put both antennas as parallel as possible
In order to optimize transaction speed between the reader and the card it is
recommended to place the user token as close as possible to the reader. This
will increase the amount of energy supplied to the user credential which will
then be able to use its microprocessor at higher speeds
SDI010 REFERENCE MANUAL
3.6.
18
Applications
3.6.1. General
SDI010 is a transparent reader designed to interface a personal computer host supporting
PC/SC interface with 13.56MHz user tokens like public transport cards, contactless banking
cards, electronic identification documents – e.g. e-passports, e-ID cards, driving licenses etc.
SD
I01
0
Those user tokens can have several form factors like credit cards, key fobs, NFC mobile
phones or USB dongles like SCT3511 that SCM Microsystems markets.
SDI010 itself handles the communication protocol but not the application related to the token.
The application-specific logic has to be implemented by software developers on the host.
3.6.2. Applications provided by SCM Microsystems
SCM Microsystems does not provide payment or transport applications.
SCM Microsystems provides a few applications for development and evaluation purposes that
can function with SDI010. There are many tools provided; here are two of them:
•
The NFC forum tag reader/writer is a standalone application that enables the user to
read and write NFC forum compliant records into NFC forum compatible tags. It is an
easy to use tool to configure rapidly NFC forum tag demonstrations. Note: SDI010
supports NFC forum tag type 2 and 4, only.
•
Smart card commander version 1.1 provides NFC forum record parsing functionality
of NDEF records in XML format as well as scripting functionality which can be very
useful for developers to develop and debug their applications. This tool can be used
for both the contact and the contactless interfaces of SDI010.
SDI010 REFERENCE MANUAL
19
4. SDI010 characteristics
4.1.
SDI010 high level architecture
4.1.1. Block diagram
The link between SDI010 and the host to which it is connected is the USB interface providing
both the power and the communication channel.
S010 has a device controller which is SCM’s STCII ASIC. This ASIC has several interfaces
available. In SDI010 implementation 2 peripherals are connected to the device controller:
•
LED for reader status indication
•
A contact smart card interface
•
An RF front-end that handles the RF communication
The ASIC embeds flash memory. The flash is programmed during the manufacturing of SDI010
devices. This flash contains the firmware developed by SCM Microsystems to handle all the
ISO7816 contact protocol, the RF communication protocols and the PC/SC communication
protocol with the host. The flash can be upgraded once the device is deployed on the field,
hence enabling firmware upgrades to add and potentially patch features.
The RF front-end ensures the coding/decoding/framing modulation/demodulation required for
the RF communication. It is controlled by the device controller through registers.
The matching circuitry provides the transmission and receiver paths adaptation for the antenna
to function properly.
SDI010 REFERENCE MANUAL
20
4.1.2. Software architecture
Applications can interface with the driver directly through the PC/SC interface.
The SDI010 driver implements PC/SC v2.0 API towards upper layers and uses SCM firmware
commands encapsulated in CCID-like protocol for the contactless slot and full CCID for the
contact slot.
The SDI010 contactless driver handles all the contactless-related intelligence – i.e. ISO/IEC
14443 and the SDI010 firmware handles the raw transport of data to and from the contactless
cards.
SDI010 REFERENCE MANUAL
4.2.
21
Quick reference data
4.2.1. SDI010 dimensions
Item
Characteristic
Value
Weight
128 Grams
External dimensions
L 118 mm &times; W 78mm &times; H 22mm
Cable length
1.5 meter long with USB type A connector
Default color
Black with metallic silver
SDI010
Default label
Drawing with dimensions of the SDI010 and accessories can be found in annex.
SDI010 REFERENCE MANUAL
22
4.2.2. LED behavior
SDI010 is equipped with a bicolor LED. Its behavior is described in the table below.
SDI010 states
Just after plug-in (with drivers
already installed)
Just after DFU operation
Suspend / standby
Reader powered, Contact card IN, but not powered
(98/ME – issue power down using the Testresman
utility)
Reader powered, Contact card IN, but not powered
(2K/XP – power down takes place )
Reader powered, Contactless card IN, but not
powered (98/ME - issue power down using the
Testresman utility)
Reader powered, Contactless card IN, but not powered
(2K/XP - power down takes place )
Contact card powered / communication
Contactless card powered / communication
LED1 Indication
(GREEN)
LED2 Indication
(RED)
ON
OFF
ON
OFF
OFF
OFF
500ms ON
500ms OFF
OFF
ON
OFF
500ms ON
500ms OFF
ON
500ms ON
500ms OFF
500ms ON
500ms OFF
Reader / card errors
OFF
Firmware upgrade running
OFF
500ms ON
500ms OFF
500ms ON
500ms OFF
3
Combi card powered in contact Slot
Combi card powered using RF field
3
500ms ON
500ms OFF
ON
OFF
500ms ON
500ms OFF
100ms ON
100ms OFF
ON
OFF
500ms ON
500ms OFF
A combi card is a smart card which has both a contact and a contactless interface. Some of those cards have one
controller with two interfaces. Data can be accessed through the contact or the contactless interface. For those when
the contact interface is powered up the contactless interface is disabled. There are nevertheless in the market combi
cards with 1 contact chip and 1 contactless chip. Those cards can be seen at the same time as a contact and a
contactless card when inserted in the contact interface of SDI010.
SDI010 REFERENCE MANUAL
23
4.2.3. Other data
4.2.3.1.
Parameter
Clock of the device
controller
API
Operating temperature
range
Operating humidity
range
Certifications
4.2.3.2.
General
Value/Description
24 MHz
PC/SC 2.0
0&ordm; to 50&ordm;C
Up to 95%RH non condensing
USB
CE
FCC
VCCI
WEEE
RoHS
WHQL
USB
Parameter
Value/Description
DC characteristics
High bus powered (SDI010 draws power from USB bus)
Voltage: 5V
Max. Current : 200mA
Suspend current : 380uA
USB specification
USB 2.0 FS Device
USB Speed
Device Class
PID
VID
Full Speed Device (12Mbit/s)
Vendor
0x5121
0x04E6
SDI010 REFERENCE MANUAL
4.2.3.3.
24
Contactless interface
Parameter
Value/Description
RF carrier frequency
Modulation
13.56 MHz +/- 50ppm
ID1 format tokens
supported
Maximum baud rate
12 to 14 %
ISO/IEC 14443-4 PICC type A and type B
MIFARE
Type B memory card PICC through SCM-proprietary APDU
424Kbps (848 Kbps is available as configurable option)
Supported and is kept disabled by default.
Multiple PICC in field
4.2.3.4.
Parameter
Smart card operating
frequency
Maximum supported
card baud-rate
Allows the presence and use of several PICC’s (Maximum 4) at the same
time. The driver can support multiple logical connections and present each of
them as a slot logical device to the Resource Manager and higher
components. Also the simultaneous working of multiple Contactless cards is
not guaranteed and depends on the antenna size and the power requirements
of the card.
Contact interface
Value/Description
4MHz
500Kbps
Cards supported
Class A and Class AB smart cards (Class B only cards not supported)
Synchronous smart cards
ISO-7816 compliant
Yes
EMV’2000 compliant
CT-API compliant
Number of slots
Ejection mechanism
Not validated
Yes
Single smart card slot
Manual
SDI010 REFERENCE MANUAL
25
5. Software modules
5.1.
Installation
SCM provides an installer for Windows.
The installer can be used to install the driver as well as some utilities.
5.2.
Utilities
The following utilities are available:
•
A tool for device firmware upgrade (DFU)
•
A tool for testing the installation of the PC/SC driver
•
A tool for testing the resource manager
•
A tool called PC/SC Diag capable of providing basic information about the reader
and a card through PC/SC stack
The DFU utility comes with a specific driver for dynamic Device Firmware Upgrade (DFU)
through the USB interface.
Operating systems supported by DFU tool:
5.3.
•
Windows 98
•
Windows ME
•
Windows 2000
•
Windows 2003 Server (32 &amp; 64 bit)
•
Windows XP (32 &amp; 64 bit)
•
Windows Vista (32 &amp; 64 bit)
•
Windows Server 2008 (32 &amp; 64 bit)
Driver
5.3.1. SDI010 listing
SDI010 is listed by PC/SC applications as
•
SCM Microsystems Inc. SDI010 Smart Card Reader for the contact reader
•
SCM Microsystems Inc. SDI010 Contactless Reader for the contactless reader
SDI010 REFERENCE MANUAL
26
5.3.2. Supported operating systems
Operating systems supported by the driver:
•
Windows 98
•
Windows ME
•
Windows 2000
•
Windows 2003 Server (32 &amp; 64 bit)
•
Windows XP (32 &amp; 64 bit)
•
Windows Vista (32 &amp; 64 bit)
•
Windows Server 2008 (32 &amp; 64 bit)
5.3.3. PC/SC 2.0 compliant ATR for contactless interface
When a user token is placed on the reader, initialization, anti-collision is done. The user token
is automatically activated and an ATR is built as defined in the PC/SC specification.
SDI010 REFERENCE MANUAL
5.3.3.1.
27
ATR for contactless storage user tokens
The ATR of the user token is composed as described in the table below. In order to allow the
application to identify the storage card properly, it’s Standard and Card name describing bytes
must be interpreted according to the Part 3 Supplemental Document, maintained by PC/SC.
Tokens using technology like MIFARE are examples of such user tokens.
Byte#
Value
Designation
Description
0
0x3B
Initial header
1
0x8n
T0
n indicates the number of historical bytes in
following ATR
2
0x80
TD1
Nibble8 indicates no TA2, TB2, TC2
Nibble 0 means T=0
3
0x01
TD2
Nibble8 indicates no TA3, TB3, TC3
Nibble 1 means T=1
4...3+n
0x80
0x4F
Lentgh
A status indicator may be present in an
optional TLV data object
Optional TLV
data object
Tag: Application identifier
1 byte
RID
Registered identifier on 5 bytes
PIX
Proprietary identifier extension on 3 bytes
0x00 0x00 0x00 0x00
4 RFU bytes
4+n
TCK
XOR of all previous bytes
Example of the ATR built for contactless storage tokens:
MIFARE Classic 4K
MIFARE Ultralight
SDI010 REFERENCE MANUAL
5.3.3.2.
28
ATR for ISO/IEC 14443-4 user tokens
The user token exposes its ATS or application information which is mapped to an ATR. The
table describes how this mapping is done.
Byte#
Value
Designation
Description
0
0x3B
Initial header
1
0x8n
T0
n indicates the number of historical bytes in following ATR
2
0x80
TD1
Nibble8 indicates no TA2, TB2, TC2
Nibble 0 means T=0
3
0x01
TD2
Nibble8 indicates no TA3, TB3, TC3
Nibble 1 means T=1
4...3+n
4+n
Historical
bytes
or
application
information
TCK
Type A: the historical bytes from the ATS (up to 15 bytes)
Type B (8 bytes):
•
Byte 0 through 3: application data from ATQB,
•
Byte 4 through 6: protocol info byte from ATQB,
•
Byte 7: higest nibble is the MBLI (maximum
buffer length index) from ATTRIB, lowest nibble
is 0x0
XOR of all previous bytes
Example of the ATR built for an ISO14443-4 user tokens:
Type A
Type B
SDI010 REFERENCE MANUAL
5.4.
29
Firmware
5.4.1. CCID transport protocol
SDI010 implements a transport protocol that is compliant with USB Device Class: Smart Card
CCID Specification for Integrated Circuit(s) Cards Interface Devices Revision 1.10 for the
contact smart card interface and CCID-like transport protocol for the contactless interface.
This paragraph describes the CCID specification features that are implemented and those that
are not implemented.
5.4.1.1.
•
CCID class requests supported
Abort
5.4.1.2.
CCID messages supported
The following CCID messages are supported both for the contact and the contactless interfaces
when received through bulk-out endpoint.
•
PC_to_RDR_IccPowerOn
•
PC_to_RDR_IccPowerOff
•
PC_to_RDR_GetSlotStatus
•
PC_to_RDR_XfrBlock
•
PC_to_RDR_GetParameters
•
PC_to_RDR_SetParameters
•
PC_to_RDR_Escape
•
PC_to_RDR_Abort
•
PC_to_RDR_NotifySlotChange
The following CCID messages are NOT implemented and hence fail with command not
supported error:
•
PC_to_RDR_ResetParameters
•
PC_to_RDR_IccClock
•
PC_to_RDR_T0APDU
•
PC_to_RDR_Secure
•
PC_to_RDR_Mechanical
•
PC_to_RDR_SetDataRateAndClockFrequency
5.4.1.3.
CCID Error Codes
Extensive error codes are reported on many conditions during all CCID responses. Most of the
error messages are reported by the CCID appropriately. Some of the main error codes for the
contact interface are:
•
HW_ERROR
•
XFR_PARITY_ERROR
SDI010 REFERENCE MANUAL
•
BAD_ATR_TS
•
BAD_ATR_TCK
•
ICC_MUTE
30
The following sub-sections discuss when and why these error codes are returned:
5.4.1.3.1. HW_ERROR
This error code is returned when a hardware short circuit condition is detected, during
application of power to the card or if any other internal hardware error is detected. This error
code has been defined in the error code table 6.2-2 of the CCID specification.
5.4.1.3.2. XFR_PARITY_ERROR
This error code is returned when a parity error condition is detected. This error will be reported
in the response to a PC_to_RDR_XfrBlock message. This error code has been defined in the
error code table 6.2-2 of the CCID specification.
5.4.1.3.3. ICC_MUTE
This error code is returned when the card does not respond until the reader time out occurs.
This error will be reported in the response to PC_to_RDR_XfrBlock message and
PC_to_RDR_IccPowerOn messages. This error code has been defined in the error code table
6.2-2 of the CCID specification.
5.4.2. Automatic PPS for the contactless interface
Automatic PPS is implemented in SDI010’s driver. This means that by default SDI010 switches
to the maximum communication speed indicated by the card during its selection. Automatic
PPS can be disabled using escape messages as explained later in this manual.
When Auto PPS is disabled (discussed in escape messages section) the reader works at the
default baud rate of 106kbps. An escape command has been introduced in the driver to force
the required baud rate.
The maximum speed supported by SDI010 is 424Kbps by default. Using escape messages as
explained later in this manual it is possible to change this.
SDI010 REFERENCE MANUAL
31
6. Commands description
6.1.
Generic APDU
6.1.1. Get UID Command
6.1.1.1.
Description
GET UID will retrieve the UID or SNR or PUPI of the user token. This command can be used
for all supported technologies.
6.1.1.2.
Format
CLA
INS
P1
P2
Lc
Data in
Le
0xFF
0xCA
0x00
0x00
-
-
XX
Setting Le = 0x00 can be used to request the full UID or PUPI is sent back.(e.g. for ISO14443A
single 4 bytes, double 7 bytes, triple 10 bytes, for ISO14443B 4 bytes PUPI).
6.1.1.3.
Response
Data Out
UID + SW1 + SW2
6.1.1.4.
Status Words
SW1
SW2
Description
0x90
0x00
NO ERROR
0x62
0x82
End of UID reached before Le bytes (Le is
greater than UID length)
0x6C
0xXX
Wrong Length.
0xXX is the exact value for Le
Further error codes can be found in annex
SDI010 REFERENCE MANUAL
6.1.1.5.
ISO14443-4A
ISO14443-4B
MIFARE 4K
MIFARE Ultralight
32
Examples
SDI010 REFERENCE MANUAL
33
6.1.2. Escape command APDU
6.1.2.1.
Description
This command can be used to send escape commands to SDI010. For description of escape
commands please refer to the dedicated chapter in this manual.
6.1.2.2.
Format
CLA
INS
P1
P2
P3
Data in
0xFF
0xCC
0x00
0x00
Lc
Input buffer of escape command
Lc is the length of the escape command’s input buffer. See escape commands description later
in this manual
6.1.2.3.
Response
Output buffer of the escape command
6.1.2.4.
Example
To get the ATS or ATQB of the ISO14443-4 based user token, you can use this APDU to send
the READER_CNTLESS_GET_ATS_ATQB (0x93) escape command
Type A passport
Type B passport
To get the reader status about support of 848Kbps, you can use this APDU to send the
READER_CNTLESS_848KBPS (0x9D) escape command.
By default the SDI010 doesn’t have 848Kbps enabled on its contactless interface, the following
sequence
•
Checks the status (0x00 as response, means 848Kbps is disabled)
•
Enables 848Kbps
•
Checks the status again and the answer 0x01 indicates 848Kbps is enabled
SDI010 REFERENCE MANUAL
6.2.
34
Set of APDU for contactless storage user tokens
6.2.1. STORAGE_CARD_CMDS_READ_BINARY
6.2.1.1.
Description
Using this APDU, application can read a memory block on user tokens based on technologies
like MIFARE Classic 1K or 4K (block size 0x10 bytes) or MIFARE Ultra light (block size 0x04
bytes).
6.2.1.2.
Format
CLA
INS
P1
P2
Le
0xFF
0xB0
Address
MSB
Address
LSB
0xXX
Where:
•
P2 indicates the block number from where to read
•
Le can be a short (maximum value 255) or extended (maximum value 65535). If
Le=0x00, then all the bytes until the end of the block are read (0x10 bytes for
MIFARE Classic 1K or 4K cards and 0x04 bytes for MIFARE Ultra Light cards).
6.2.1.3.
Response
Data Out
Data + SW1 + SW2
6.2.1.4.
Status words
SW1
SW2
Description
0x90
0x00
NO ERROR
0x62
0x81
WARNING: part of the returned data may be
corrupted
0x82
WARNING: end of file reached before Le bytes
where read
0x67
0x00
Length incorrect
0x68
0x00
CLA byte incorrect
0x69
0x81
Command not supported
0x82
Security status not satisfied
0x86
Command not allowed
0x81
Function not supported
0x82
File not found, addressed blocks or bytes do not
exist
0x6B
0x00
Wrong P1, P2 parameters
0x6C
0xXX
Wrong Le, 0xXX is the correct value
0x6A
SDI010 REFERENCE MANUAL
6.2.1.5.
35
Example
For a MIFARE Classic 1K card which has the following memory content:
To read the seventh block, you have to issue the following command and get the following
response:
SDI010 REFERENCE MANUAL
36
6.2.2. STORAGE_CARD_CMDS_WRITE_BINARY
6.2.2.1.
Description
This APDU writes data pattern in to a memory address
6.2.2.2.
Format
CLA
INS
P1
P2
Lc
Data in
0xFF
0xD6
Address
MSB
Address
LSB
0xXX
Data
Where:
•
P2 indicate the memory block number where data should be written
•
Lc=0x10 for MIFARE Classic 1K/4K. Lc=0x04 for MIFARE Ultralight
6.2.2.3.
Response
Data Out
SW1 + SW2
6.2.2.4.
SW1
SW2
Status Words
Description
0x90
0x00
NO ERROR
0x69
0x81
Command not supported
0x64
0x00
State of the non-volatile memory unchanged
6.2.2.5.
Example
For a MIFARE Classic Ultralight card which has the following memory content:
Issuing the command
SDI010 REFERENCE MANUAL
Results into the following memory mapping
37
SDI010 REFERENCE MANUAL
38
6.2.3. STORAGE_CARD_CMDS_LOAD_KEYS
6.2.3.1.
Description
Some type of user tokens like MIFARE Classic may require that an authentication happens
before any data can be read or written. To perform this authentication, keys need to be loaded
in the reader’s memory using this command.
6.2.3.2.
Format
CLA
INS
P1
P2
Lc
Data in
0xFF
0x82
0x00
Key Type
Key Length
Key value
Where P2 can have the following values (please refer to MIFARE documentation from NXP for
further details on what is key A and Key B):
•
0x60 to use the Key A
•
0x61 to use the Key B
6.2.3.3.
Response
Data Out
SW1 + SW2
6.2.3.4.
Status Words
SW1
SW2
Description
0x90
0x00
NO ERROR
0x69
0x83
Reader key not supported
0x85
Secured transmission not supported
0x87
Non volatile memory not available
0x88
Key number not valid
0x89
Key length not correct
SDI010 REFERENCE MANUAL
39
6.2.4. STORAGE_CARD_CMDS_AUTHENTICATE
6.2.4.1.
Description
This command enables to perform authentication for user tokens based on MIFARE Classic 1K
or
4K.
Before
this
command
can
be
successfully
executed,
the
STORAGE_CARD_CMDS_LOAD_KEY command must have been executed.
6.2.4.2.
Format
CLA
INS
P1
P2
Lc
Data in
0xFF
0x86
0x00
0x00
0x05
Data
Where the data field is structured as follow
Byte #
Value
Description
B0
0x01
Version
B1
Address MSB
B2
Address LSB
B3
0x60
Key A
0x61
Key B
B4
Number of the key to be used for authentication
Information about memory structure of MIFARE Classic must be requested from NXP
Semiconductors.
6.2.4.3.
Response
Data Out
SW1 + SW2
6.2.4.4.
SW1
SW2
Status Words
Description
0x90
0x00
NO ERROR
0x63
0x00
WARNING no further info
0x69
0x82
Security status not satisfied
0x84
Referenced key not usable
0x86
Key type not known
SDI010 REFERENCE MANUAL
6.2.4.5.
40
Example
For a MIFARE Classic 1K card which has the following memory mapping:
Reading sector 0 or sector 1 of this card requires authentication with key A or key B.
The following example:
•
authenticates with key A of sector 1
•
reads block #6
•
authenticates against sector 3
•
reads block #E
SDI010 REFERENCE MANUAL
41
6.2.5. STORAGE_CARD_CMDS_VALUE_BLOCK
6.2.5.1.
Description
This APDU is used to interact with MIFARE Classic e-purse applications. Please refer to
MIFARE Classic documentation available from NXP Semiconductors for further details on
MIFARE classic memory mapping and commands.
6.2.5.2.
Format
CLA
INS
P1
P2
Lc
Data in
0xFF
0xF0
0x00
Block#
Lc
Data
Where P2 code the address of the block number addressed
Where the data field is structured as follow
Byte #
Value
Description
B0
0xC0
Increment
0xC1
Decrement
B1
Block number
B2-B5
Value (LSB first)
6.2.5.3.
Response
Data Out
SW1 + SW2
6.2.5.4.
Status Words
SW1
SW2
Description
0x90
0x00
NO ERROR
0x67
0x00
Length incorrect
0x68
0x00
CLA byte incorrect
0x6A
0x81
Function not supported
0x6B
0x00
Wrong P1, P2 parameters
6.2.5.5.
Example
CLA
INS
P1
P2
Lc
Data in
0xFF
0xF0
0x00
0x1E
0x06
0xC0 0x1E 0x01 0x00 0x00 0x00
The above APDU will increment the value in block number 0x1E of a MIFARE Classic-based
user token by a value of 0x01.
SDI010 REFERENCE MANUAL
6.3.
42
Set of APDU for ISO/IEC14443-4 user tokens
6.3.1. T=CL Command
Description
SDI010 can transfer directly ISO/IEC7816-4 APDU to the PICC.
SDI010 supports user tokens that have both the MIFARE and T=CL partitions. Depending on
the APDU sent by the host, the reader switches to the corresponding mode (MIFARE or T=CL)
automatically and the command is processed accordingly.
6.3.1.1.
CLA
INS
Format
P1
P2
P3
Data
Description of the APDU commands can be found in ISO/IEC 7816-4 specification.
6.3.1.2.
Response
Data Out
PICC answer as defined in ISO/IEC 7816-4+ SW1 + SW2
As defined in ISO/IEC 7816-4.
6.3.1.3.
SW1
Status Words
SW2
Description
See ISO/IEC 7816-4
As defined in ISO/IEC 7816-4.
6.3.1.4.
Example
The following APDU sequence reads the first 256 bytes of the data group 1 as specified in
ICAO LDS (logical data structure) for machine readable travel documents with open access. It
first selects the issuer application using its AID (0xA0 0x00 0x00 0x02 0x47 0x10 0x01), then
selects the DG1 file (0x01 0x01) and then does a read binary.
SDI010 REFERENCE MANUAL
43
6.3.2. T=CL user command
Description
This command can be used to send raw data to the user token.
6.3.2.1.
Format
CLA
INS
P1
P2
P3
Data
0xFF
0xFE
0x00
0x00
Lraw_data
Raw_data
6.3.2.2.
Response
Data Out
PICC response data+ SW1 + SW2
6.3.2.3.
SW1
SW2
Status Words
Description
User should refer to the status words defined by the PICC manufacturer for a description of the
status words
6.3.2.4.
Example
Let’s consider the Select command defined in ISO7816-4. This command being ISO can be
sent to the user token in 2 different way:
•
Using the T=CL command
•
Using the T=CL user command
Here are the 2 answers for the select command:
The T=CL command is nevertheless more useful for sending commands which are not defined
in ISO7816.
SDI010 REFERENCE MANUAL
6.4.
44
Set of APDU defined by SCM Microsystems
6.4.1. MIFARE DESFire Commands
Description
This command can be used to send commands to DESFire-based user tokens.
For a description of DESFire commands please contact NXP Semiconductors.
6.4.1.1.
Format
CLA
INS
P1
P2
P3
Data
0xFF
0xDE
0x00
0x00
Lcommand
Command
Response
Data Out
DESFire response data+ 9000 if the DESFire response data is of single byte
DESFire response data if the DESFire response data is more than 1 byte
SDI010 REFERENCE MANUAL
6.5.
45
Escape commands for the contactless interface
6.5.1. Sending escape commands to SDI010
A developer can use 2 methods to send escape commands to SDI010 to the contactless
interface
•
SCardControl method defined in PC/SC API
•
SCardTransmit method defined in PC/SC API in conjunction with the escape
command APDU defined earlier in this manual
6.5.2. Escape command codes
Escape commands can be used by an application to configure SDI010 to function in a mode
that is not its default configured mode or to get specific information. To put the SDI010 back
into its default mode, either the SDI010 has to be unplugged and plugged again or the
application can send again the same escape command.
The following escape commands are supported by SDI010 for the contactless interface.
Escape command
Code
READER_GETCARDINFO
0x11
READER_LEDCONTROL
0x19
READER_CNTLESS_GET_MFRC_REV
0x92
READER_CNTLESS_GET_ATS_ATQB
0x93
READER_CNTLESS_GET_TYPE
0x94
READER_CNTLESS_SET_TYPE
0x95
READER_CNTLESS_RF_SWITCH
0x96
READER_CNTLESS_RAW_CFG
0x97
READER_CNTLESS_RAW_XMIT_EX
0xAE
READER_ CNTLESS_DISABLE_PPS
0x99
READER_SWITCH_RF_ON_OFF
0x9C
READER_CNTLESS_848KBPS
0x9D
READER_CNTLESS_BAUDRATE
0x9E
READER_CNTLESS_FORCE_BAUDRATE_PCSC_REV2
0xAD
READER_LEDCTRL_BY_FW
0xB2
Sample code to send escape commands can be found in annex.
SDI010 REFERENCE MANUAL
46
6.5.3. READER_GETCARDINFO
This escape command is used to get information about the card placed on the reader. The
SDI010 returns an error if no card is placed on it.
The input buffer shall contain the escape command code
Input buffer
0x11
The output buffer contents are described below.
Output buffer
Value
Description
B0
0x01
Contactless card present
B1
0xNN
Baud rate of card-reader communication
B2
0xXY
X – Upper nibble indicates 0 - memory card
1 - T=CL card
2 - Dual mode card
Y – Lower nibble indicates 0 - Type A card
1 - Type B card
The Baud rate of card-reader communication 0xNN shall indicate a BYTE as follows
B8
B7
B6
B5
B4
B3
B2
B1
0
B1 – 212kbps supported (direction reader to card)
B2 – 424kbps supported (direction reader to card)
B3 – 848kbps supported (direction reader to card)
B5 – 212kbps supported (direction card to reader)
B6 – 424kbps supported (direction card to reader)
B7 – 848kbps supported (direction card to reader)
B8 – 1 – indicates same baud rate in both directions
0 – indicates different baud rates in opposite directions
For Example:
If 0xNN = 0x77, the card supports all baud rates namely 106, 212, 424 and 848 kbps in both
directions. This card can be forced to work at different baud rates in the send and receive
directions
using
the
escape
command
READER_CNTLESS_FORCE_BAUDRATE_PCSC_REV2.
If 0xNN = 0xB3, the card supports 106, 212 and 424 kbps in both directions. This card can be
made to work only at the same baud rate in the send and receive directions using the escape
command READER_CNTLESS_FORCE_BAUDRATE_PCSC_REV2.
SDI010 REFERENCE MANUAL
47
6.5.4. READER_LED_CONTROL_BY_FW
This escape command may be used to enable or disable LED control by the firmware.
The input buffer is
Byte #
Value
Description
B0
0xB2
Escape command code
B1
0x00
Disable LED control by FW
0x01
Enable LED control by FW
The output buffer is
Output buffer
NULL
6.5.5. READER_LEDCONTROL
This escape command is used to turn ON/OFF the LED.
This escape command shall work only if LED control by firmware is disabled.
The input buffer shall contain 3 bytes
Byte #
Value
Description
B0
0x19
Escape command code
B1
0x00
LED number
B2
0x00
LED ON
0x01
LED OFF
The output buffer is
Output buffer
NULL
6.5.6. READER_CNTLESS_GET_MFRC_REV
This escape message retrieves the revision number of the RF ASIC MFRC531.
The input buffer contains the escape command code
Input buffer
0x92
The output buffer contains the version of the MFRC531 ASIC.
SDI010 REFERENCE MANUAL
48
6.5.7. READER_CNTLESS_GET_ATS_ATQB
This escape command enables the host to retrieve the ATS for Type A T= CL or the ATQB for
Type B cards.
The input buffer contains the escape command code
Input buffer
0x93
The output buffer contains the ATS bytes or the ATQB bytes depending on the type of PICC
placed on the reader.
6.5.8. READER_CNTLESS_GET_TYPE
This escape command retrieves the type of the card which SDI010 is configured to poll for.
The input buffer shall contain the escape command code
Input buffer
0x94
The output buffer shall point to a BYTE buffer which will contain the type value coded as
Value
Description
0x00
Type A
0x01
Type B
0x02
Type A + type B
6.5.9. READER_CNTLESS_SET_TYPE
This escape command configures the type of cards SDI010 will poll for.
Using this command can improve the polling efficiency of SDI010 for applications where only
type A or only type B cards are expected.
The default is Type A + type B (0x02).
The input buffer shall contain 2 bytes
Byte #
Value
Description
B0
0x95
Escape command code
B1
0x00
Type A
0x01
Type B
0x02
Type A + type B
The output buffer is
Output buffer
NULL
SDI010 REFERENCE MANUAL
6.5.10.
49
READER_CNTLESS_RF_SWITCH
This escape command can be used to retrieve/set the RF state of SDI010.
The default RF field state is ON.
The input buffer shall contain 2 bytes
Byte #
Value
Description
B0
0x96
Escape command code
B1
0x00
Switch RF Field OFF
0x01
Switch RF Field ON
0xFF
Get current field state
After the RF is turned off, to turn the RF ON again, card connect shall be done in direct mode.
If B1 of the input buffer is 0x00 or 0x01 the output buffer is
Output buffer
NULL
If B1 of the input buffer is 0xFF, the output buffer is a BYTE buffer with 2 possible values
Output buffer
Description
0x01
RF field is OFF
0x00
RF field is ON
6.5.11.
READER_CNTLESS_RAW_CFG
This escape command switches SDI010 to raw mode.
When SDI010 is in raw mode it only polls for one type of contactless card.
SDI010 is by default not in this mode and therefore READER_CNTLESS_RAW_XMIT_EX
would fail.
The input buffer contains 2 bytes
Byte #
Value
Description
B0
0x97
Escape Function code
B1
0x00
Type A will be use for further
transmissions in raw mode
0x01
Type B will be use for further
transmissions in raw mode
The output buffer is
Output buffer
NULL
Once
SDI010
is
in
raw
mode
commands
READER_CNTLESS_RAW_XMIT_EX escape command.
can
be
sent
using
SDI010 REFERENCE MANUAL
6.5.12.
50
READER_CNTLESS_RAW_XMIT_EX
This escape command can only be executed by the firmware once SDI010 is put in raw mode
using the READER_CNTLESS_RAW_CFG escape command.
This escape command can be used to send commands to smart card when SDI010 is in raw
mode
The input buffer is
Byte #
Value
Description
B0
0xAE
Escape Function code
B1
Wait Time
B2
Is CRC required?
B3
No of bits per command
B4
Card Type
0 – Type A
1 – type B
B5
Command length
B6 - Bn
Command
The output buffer contains the response to the command from the offset B6 onwards.
The following example uses the raw mode to send a REQB command
First, we have to switch the SDI010 into raw mode for type B communication
Byte #
Value
Description
B0
0x97
READER_CNTLESS_RAW_CONFIG code
B1
0x01
Type B will be used
Then, we can send the following bytes to obtain the ATQB response of any type B user token in
the field
Byte #
Value
Description
B0
0xAE
READER_CNTLESS_RAW_XMIT_EX code
B1
0x03
FWI is set to 3
B2
0x01
Enable CRC (CRC will be calculated by the
RF front end of SDI010)
B3
0x00
Number of bits to be sent in the command
0 – Entire byte will be sent
B4
0x01
Type B
B5
0x03
Command length in bytes
B6
0x05
REQB command’s anticollision prefix byte
B7
0x00
REQB
command’s
identifier
B8
0x01
REQB command parameter with slot number
set as 1
application
family
SDI010 REFERENCE MANUAL
6.5.13.
51
READER_ CNTLESS_DISABLE_PPS
By default SDI010 does automatic PPS – i.e. it switches the RF communication speed to the
highest possible supported by the card.
This escape command can be used to switch ON/OFF automatic PPS. When automatic PPS is
OFF, then 106Kbps only is available.
The input buffer is
Byte #
Value
Description
B0
0x99
Escape command code
B1
0x01
Disable Auto-PPS
0x00
Enable Auto-PPS
The output buffer is
Output buffer
NULL
6.5.14.
READER_SWITCH_RF_ON_OFF
This escape command can be used to switch the RF field ON or OFF when a Contact smart
card is inserted into the reader.
By default, the RF field is always in the ON state and when any contact smart card is inserted
in the reader, the RF field is turned OFF.
The input buffer shall contain 2 bytes
Byte #
Value
Description
B0
0x9C
Escape command code
B1
0x00
Switch RF Field OFF when contact card
is present in the reader
0x01
Switch RF Field ON when contact card
is present in the reader
0xFF
Get current field state when Contact
smart card is present in the reader
After the RF is turned off, to turn the RF ON again, card connect shall be done in direct mode.
SDI010 REFERENCE MANUAL
52
If B1 of the input buffer is 0x00 or 0x01 the output buffer is
Output buffer
NULL
If B1 of the input buffer is 0xFF, the output buffer is a BYTE buffer with 2 possible values
Output buffer
Description
0x00
RF field is OFF
0x01
RF field is ON
6.5.15.
READER_CNTLESS_848KBPS
This escape command can be used to enable/disable 848kbps support by SDI010 as well as
query whether 848kbps is currently enabled or disabled by SDI010.
The RF communication with a user token will only switch to 848Kbps provided the user token
supports this baud rate and provided automatic PPS is ON.
The input buffer shall contain 2 bytes
Byte #
Value
Description
B0
0x9D
Escape command code
B1
0x00
Disable 848Kbps support
0x01
Enable 848Kbps support
0xFF
Get current status on 848Kbps support
If B1 of the input buffer is 0x00 or 0x01 then the output buffer is
Output buffer
NULL
If B1 of the input buffer is 0xFF, the output buffer is a BYTE buffer with following possible
values
Output buffer
Description
0x00
848Kbps is disabled
0x01
848Kbps is enabled
SDI010 REFERENCE MANUAL
6.5.16.
53
READER_CNTLESS_BAUDRATE
This escape command can be used to get the actual operating baud rate of card-reader
communication.
The input buffer shall contain the escape message value.
Input buffer
0x9E
The output buffer shall point to a BYTE buffer with following possible values
Output buffer
Description
0x00
106Kbps in both directions
0x01
106Kbps from PICC to PCD, 212Kbps from PCD to PICC
0x02
106Kbps from PICC to PCD, 424Kbps from PCD to PICC
0x03
106Kbps from PICC to PCD, 848Kbps from PCD to PICC
0x10
212Kbps from PICC to PCD, 106Kbps from PCD to PICC
0x11
212Kbps in both directions
0x12
212Kbps from PICC to PCD, 424Kbps from PCD to PICC
0x13
212Kbps from PICC to PCD, 848Kbps from PCD to PICC
0x20
424Kbps from PICC to PCD, 106Kbps from PCD to PICC
0x21
424Kbps from PICC to PCD, 212Kbps from PCD to PICC
0x22
424Kbps in both directions
0x23
424Kbps from PICC to PCD, 848Kbps from PCD to PICC
0x30
848Kbps from PICC to PCD, 106Kbps from PCD to PICC
0x31
848Kbps from PICC to PCD, 212Kbps from PCD to PICC
0x32
848Kbps from PICC to PCD, 424Kbps from PCD to PICC
0x33
848Kbps in both directions
SDI010 REFERENCE MANUAL
6.5.17.
54
READER_CNTLESS_FORCE_BAUDRATE_PCSC_REV2
This escape command can be used to force baud rate for Contactless cards.
The input buffer is
Byte #
Value
Description
B0
0xAD
Escape command code
B1
0x00
Apply the baud rate specified by the card
0x01
Force baud rate specified in B2
B2
b0-
DR=2 supported, if bit is set to 1
b1-
DR=4 supported, if bit is set to 1
b2-
DR=8 supported, if bit is set to 1
b3-
shall be set to 0, 1 is RFU
b4-
DS=2 supported, if bit is set to 1
b5-
DS=4 supported, if bit is set to 1
b6-
DS=8 supported, if bit is set to 1
Encoding of the baud rate to be forced if
B1 value is 0x01. No need to send this
byte in case B1 has the value =x00
b71 if the same D is required for
both communication directions
b80 if different D is supported for
each communication direction
NULL
The output buffer is
Output buffer
NULL
If B1=0x00
SDI010 REFERENCE MANUAL
6.6.
55
Escape commands for the contact interface
6.6.1. Sending escape commands to SDI010
A developer can use the following method to send escape commands to SDI010 for the contact
interface
•
SCardControl method defined in PC/SC API
6.6.2. Escape command codes
Escape commands can be used by an application to configure SDI010 to function in a mode
that is not its default configured mode or to get specific information. To put the SDI010 back
into its default mode, either the SDI010 has to be unplugged and plugged again or the
application can send again the same escape command.
The following escape commands are supported by SDI010 for the contact interface
Escape command
Code
READER_SETMODE
0x01
READER_GETMODE
0x02
READER_APDU_TRANSFER
0x08
READER_SWITCH_SPEED
0x0A
READER_SWITCH_PROTOCOL
0x0C
READER_DISABLE_PPS
0x0F
READER_GETIFDTYPE
0x12
READER_GETINFO_EXTENDED
0X1E
6.6.3. READER_SETMODE
This escape command may be used to set the mode of the reader. Applications may call this
function, to set the desired mode. Typically, this call is used to switch between the EMV,
ISO7816 and the memory card modes of operation.
The input buffer is
Byte #
Value
Description
B0
0x01
Escape command code
B1
0x00
ISO 7816 mode
0x01
EMV mode
0x02
Memory card mode
The output buffer is
Output buffer
NULL
SDI010 REFERENCE MANUAL
56
6.6.4. READER_GETMODE
This escape command may be used to retrieve the current mode of the reader.
The input buffer is
Byte #
Value
Description
B0
0x02
Escape command code
The output buffer is
Output buffer
Description
0x00
ISO 7816 mode
0x01
EMV mode
0x02
Memory card mode
6.6.5. READER_APDU_TRANSFER
This escape command may be used to exchange an APDU with the smart card.
The input buffer is
Byte #
Value
Description
B0
0x08
Escape command code
B1- Bn
Command APDU
The output buffer contains the response APDU.
The maximum number of bytes that can be transmitted and received is given below.
Transmit:
Case 1,2,3 APDU: Max of 256 bytes per APDU
Case 4 APDU: Max of 255 bytes per APDU
Receive:
Max of 259 bytes per APDU
SDI010 REFERENCE MANUAL
57
6.6.6. READER_SWITCH_SPEED
In case, when the application is capable of switching the card’s speed through APDU (if the
card supports such a feature), this escape command is used to inform the reader about the
speed change occurred between application and card. The first byte will contain the escape
function value; the next two bytes contain Fi and Di respectively. The output buffer field shall be
NULL.
The input buffer is
Byte #
Value
Description
B0
0x0A
Escape command code
B1
Fi value
B2
Di value
The output buffer is
Output buffer
NULL
6.6.7. READER_SWITCH_PROTOCOL
In case, when the application is capable of switching the card’s protocol through APDU (if the
card support such a feature), this escape command is used to inform the reader about the
protocol change occurred between application and card.
The input buffer is
Byte #
Value
Description
B0
0x0C
Escape command code
B1
0x00
T0_PROTOCOL
0X01
T1_PROTOCOL
The output buffer is
Output buffer
NULL
SDI010 REFERENCE MANUAL
58
6.6.8. READER_DISABLE_PPS
This escape command disables the automatic PPS done by the firmware.
The input buffer is
Byte #
Value
Description
B0
0x0F
Escape command code
B1
0x00
Enable PPS
0X01
Disable PPS
The output buffer is
Output buffer
NULL
6.6.9. READER_GETIFDTYPE
This escape command is used to get the current IFD type from the reader. The first byte of the
input buffer contains the escape id value. The reader gets the value from the reader capability
structure, which is implemented in the reader as a configurable item. The output buffer shall
point to a WORD buffer. The IFD type of SDI010-Generic is 0x010E,
The input buffer is
Byte #
Value
Description
B0
0x12
Escape command code
SDI010 REFERENCE MANUAL
6.6.10.
59
READER_GETINFO_EXTENDED
This escape command is used to get the information of the reader like the major and minor
version of the firmware, capabilities of the reader and the Unicode serial number. The output
buffer shall point to an application allocated SCARD_READER_GETINFO_PARAMS_EX
structure mentioned below.
The input buffer is
Byte #
Value
Description
B0
0x1E
Escape command code
typedef struct __SCARD_READER_GETINFO_PARAMS_EX
{
OUT
BYTE byMajorVersion;
OUT
BYTE byMinorVersion;
OUT
BYTE bySupportedModes; // 0 – ISO7816, 1 – EMV, 2 – Memory card
OUT
WORD wSupportedProtocols; // 1 – T=0; 2 - T=1; 3 – T=0 &amp; T=1
OUT
WORD winputDevice;
OUT
BYTE byPersonality;
OUT
BYTE byMaxSlots;
OUT
BYTE bySerialNoLength;
OUT
BYTE[28] bySerialNumber;
}SCARD_READER_GETINFO_PARAMS_EX, *PSCARD_READER_GETINFO_PARAMS_EX;
SDI010 REFERENCE MANUAL
60
7. Annexes
7.1.
Annex A – Status words table
SW1
SW2
Description
0x90
0x00
NO ERROR
0x67
0x00
LENGTH INCORRECT
0x6D
0x00
INVALID INSTRUCTION BYTE
0x6E
0x00
CLASS NOT SUPPORTED
0x6F
0x00
UNKNOWN COMMAND
0x63
0x00
NO INFORMATION GIVEN
0x65
0x81
MEMORY FAILURE
0x68
0x00
CLASS BYTE INCORRECT
0x6A
0x81
FUNCTION NOT SUPPORTED
0x6B
0x00
WRONG PARAMETER P1-P2
SDI010 REFERENCE MANUAL
61
7.2.
Annex B – Sample code using escape commands
through Escape IOCTL
File Name :
T_hbr.H
#ifdef __cplusplus
extern &quot;C&quot; {
#endif
#define IOCTL_CCID_ESCAPE
SCARD_CTL_CODE (0xDAC)
#define CCID_GET_848KBPS_STATUS
0xFF9D
#define CCID_SET_848KBPS_ON
0x019D
#define CCID_SET_848KBPS_OFF
0x009D
#define MINTIMEOUT
300
#ifdef __cplusplus
}
#endif
File Name :
T_hbr.CPP
#include &lt;windows.h&gt;
#include &lt;winbase.h&gt;
#include &lt;stdio.h&gt;
#include &lt;conio.h&gt;
#include &quot;winscard.h&quot;
#include &quot;winerror.h&quot;
#include &quot;T_hbr.H&quot;
VOID main(VOID)
{
SCARDCONTEXT
ContextHandle;
SCARDHANDLE
CardHandle;
BYTE
OutByte;
WORD
InWord,i;
DWORD
ActiveProtocol;
ULONG
InBufLen,ResLen;
ULONG
ret;
/* ICC protocol */
SDI010 REFERENCE MANUAL
62
SCARD_READERSTATE
Reader[1];
// please add the name of the used reader here or use SCardListReaders
// to find the right reader name
char
*ReaderName[] = {&quot;SCM Microsystems Inc. SDI010 Contactless Reader 0&quot;,
NULL};
/***************************************************************************************
*****************/
ContextHandle = -1;
ret = SCardEstablishContext(SCARD_SCOPE_USER, NULL, NULL, &amp;ContextHandle);
if (ret == SCARD_S_SUCCESS)
{
ret = SCardConnect(
ContextHandle,
ReaderName[0],
SCARD_SHARE_SHARED,
SCARD_PROTOCOL_T0 | SCARD_PROTOCOL_T1,
&amp;CardHandle,
&amp;ActiveProtocol);
if (ret == SCARD_S_SUCCESS)
{
/* get actual 848kbps status: ON/OFF */
InBufLen = 2;
InWord = CCID_GET_848KBPS_STATUS;
ret = SCardControl (CardHandle,
IOCTL_CCID_ESCAPE,
&amp;InWord,
InBufLen,
&amp;OutByte,
1,
&amp;ResLen);
printf (&quot;\n Get 848kbps status: %lx: %.2x&quot;, ret,OutByte);
Reader[0].dwCurrentState = SCARD_STATE_UNAWARE;
Reader[0].dwEventState = SCARD_STATE_UNAWARE;
Reader[0].szReader = ReaderName[0];
ret = SCardGetStatusChange( ContextHandle,
SDI010 REFERENCE MANUAL
63
MINTIMEOUT,
Reader,
1);
printf (&quot;\nATR: &quot;);
for (i=0; i&lt;Reader-&gt;cbAtr; i++)
{
printf (&quot;%.2x &quot;,Reader-&gt;rgbAtr[i]);
}
printf (&quot;\n----------------------------------------------\n&quot;);
/* enable 848KBPS: ON */
printf (&quot;\nEnable 848kbps &quot;);
InBufLen = 2;
InWord = CCID_SET_848KBPS_ON;
ret = SCardControl (CardHandle,
IOCTL_CCID_ESCAPE,
&amp;InWord,
InBufLen,
&amp;OutByte,
1,
&amp;ResLen);
ret = SCardDisconnect(CardHandle, SCARD_RESET_CARD);
ret = SCardConnect (ContextHandle,
ReaderName[0],
SCARD_SHARE_SHARED,
SCARD_PROTOCOL_T0 | SCARD_PROTOCOL_T1,
&amp;CardHandle,
&amp;ActiveProtocol);
/* get actual 848KBPS status: ON/OFF */
InBufLen = 2;
InWord = CCID_GET_848KBPS_STATUS;
ret = SCardControl (CardHandle,
IOCTL_CCID_ESCAPE,
&amp;InWord,
InBufLen,
&amp;OutByte,
1,
&amp;ResLen);
SDI010 REFERENCE MANUAL
64
printf (&quot;\n Get 848kbps status: %lx: %.2x&quot;, ret,OutByte);
Reader[0].dwCurrentState = SCARD_STATE_UNAWARE;
Reader[0].dwEventState = SCARD_STATE_UNAWARE;
Reader[0].szReader = ReaderName[0];
ret = SCardGetStatusChange (ContextHandle,
MINTIMEOUT,
Reader,
1);
printf (&quot;\nATR: &quot;);
for (i=0; i&lt;Reader-&gt;cbAtr; i++)
{
printf (&quot;%.2x &quot;,Reader-&gt;rgbAtr[i]);
}
printf (&quot;\n----------------------------------------------\n&quot;);
/* Disable 848Kbps: OFF */
printf (&quot;\nDisable 848KBPS &quot;);
InBufLen = 2;
InWord = CCID_SET_848KBPS_OFF;
ret = SCardControl(CardHandle, IOCTL_CCID_ESCAPE,
&amp;InWord, InBufLen,
&amp;OutByte, 1, &amp;ResLen);
ret = SCardDisconnect(CardHandle, SCARD_RESET_CARD);
ret = SCardConnect(ContextHandle,
ReaderName[0],
SCARD_SHARE_SHARED,
SCARD_PROTOCOL_T0 | SCARD_PROTOCOL_T1,
&amp;CardHandle,
&amp;ActiveProtocol);
/* get actual 848KBPS status: ON/OFF */
InBufLen = 2;
InWord = CCID_GET_848KBPS_STATUS;
ret = SCardControl(CardHandle, IOCTL_CCID_ESCAPE,
&amp;InWord, InBufLen,
&amp;OutByte, 1, &amp;ResLen);
printf (&quot;\n Get 848KBPS status: %lx: %.2x&quot;, ret,OutByte);
Reader[0].dwCurrentState = SCARD_STATE_UNAWARE;
Reader[0].dwEventState = SCARD_STATE_UNAWARE;
SDI010 REFERENCE MANUAL
65
Reader[0].szReader = ReaderName[0];
ret = SCardGetStatusChange(ContextHandle, MINTIMEOUT, Reader, 1);
printf (&quot;\nATR: &quot;);
for (i=0; i&lt;Reader-&gt;cbAtr; i++)
{
printf (&quot;%.2x &quot;,Reader-&gt;rgbAtr[i]);
}
printf (&quot;\n----------------------------------------------\n&quot;);
ret = SCardDisconnect(CardHandle, SCARD_RESET_CARD);
}
else
{
printf(&quot;\n SCardConnect failed with 0x%.8lX&quot;,ret);
}
ret = SCardReleaseContext(ContextHandle);
}
else
{
printf(&quot;\n SCardEstablishContext failed with %.8lX&quot;,ret);
}
printf(&quot;\npress any key to close the test tool\n&quot;);
getch();
}
SDI010 REFERENCE MANUAL
7.3.
66
Annex C - SCM Proprietary CLA bytes
CLA Byte
Function
0xF0
Contact Memory cards
MIFARE-TCL Switching
0xFF
T=CL User command
Escape command APDU
The second SCM Proprietary APDU is blocked for the application layer. This is used for internal
communication i.e. between the driver and the firmware.
Function
CLA byte – PC/SC1.0
CLA byte – PC/SC2.0
T=CL User Command APDU
0xFC
0xFF
MIFARE DESFire APDU
0xFC
0xFF
Escape Command APDU
0xFD
0xFF
In order to maintain compatibility with some customer applications which use the CLA bytes of
PC/SC 1.0 architecture, the following switching mechanism can be used.
Option1: Use the CLA byte of PC/SC1.0 architecture
Option2: Use the CLA byte of PC/SC2.0 architecture
The above two options can be controlled by
•
•
•
Configuring the firmware
INF/registry entry
Vendor IOCTL.
By default, option #2 is set in the firmware binary.
The entry System\CurrentControlSet\Services\SCM\ProprietaryAPDUOption is kept disabled in
the INF by default. Enabling this key and setting this entry to 0 will override the firmware setting
with option #1. Enabling this key and setting this entry to 1 will override the firmware setting
with option #2.
Vendor IOCTL_SWITCH_PROPRIETARY_APDU_OPTION (0x856) can also be used to switch
between the two options. Input buffer with value 0x00 will switch to option#1 and input buffer
with value 0x01 will switch to option#2.
SDI010 REFERENCE MANUAL
7.4.
Annex D – Mechanical drawings
7.4.1. Top Casing
67
SDI010 REFERENCE MANUAL
7.4.2. Bottom Casing
68
SDI010 REFERENCE MANUAL
7.4.3. Stand
69
">

ನಮಸ್ಕಾರ! SCM Microsystems SDI010 dual interface reader Reference Manual ನೊಂದಿಗೆ ನಿಮಗೆ ಸಹಾಯ ಮಾಡಲು ನಿರ್ದಿಷ್ಟವಾಗಿ ತರಬೇತಿ ಪಡೆದ AI ಚಾಟ್‌ಬಾಟ್ ನಾನು. ನಾನು ಡಾಕ್ಯುಮೆಂಟ್ ಅನ್ನು ಸಂಪೂರ್ಣವಾಗಿ ಪರಿಶೀಲಿಸಿದ್ದೇನೆ ಮತ್ತು ನಿಮಗೆ ಅಗತ್ಯವಿರುವ ನಿಖರವಾದ ಮಾಹಿತಿಯನ್ನು ಪತ್ತೆಹಚ್ಚಲು ಅಥವಾ ವಿಷಯವನ್ನು ಸ್ಪಷ್ಟ ಮತ್ತು ಸರಳ ಪದಗಳಲ್ಲಿ ವಿವರಿಸಲು ನಾನು ನಿಮಗೆ ಸಹಾಯ ಮಾಡಬಹುದು. ನಿರ್ದಿಷ್ಟ ವೈಶಿಷ್ಟ್ಯಗಳು, ದೋಷನಿವಾರಣೆ ಹಂತಗಳು ಅಥವಾ ಸಾಮಾನ್ಯ ಬಳಕೆಯ ಕುರಿತು ನೀವು ಮಾರ್ಗದರ್ಶನವನ್ನು ಹುಡುಕುತ್ತಿರಲಿ, ನಿಮ್ಮ ಪ್ರಶ್ನೆಗಳನ್ನು ಕೇಳಲು ಮುಕ್ತವಾಗಿರಿ. ನಿಮ್ಮ ಕಾಳಜಿಗಳು ಅಥವಾ ಅಗತ್ಯಗಳ ಬಗ್ಗೆ ನೀವು ಹೆಚ್ಚು ವಿವರಗಳನ್ನು ಒದಗಿಸಿದರೆ, ನಾನು ಹೆಚ್ಚು ನಿಖರವಾಗಿ ಮತ್ತು ಪರಿಣಾಮಕಾರಿಯಾಗಿ ನಿಮಗೆ ಸಹಾಯ ಮಾಡಬಹುದು!

ಸಹಾಯಕ ಟೈಪ್ ಮಾಡುತ್ತಿದ್ದಾರೆ

ಸಹಾಯಕ ಕೀಬೋರ್ಡ್‌ನಿಂದ ಹೊರಗಿದ್ದಾರೆ. ದಯವಿಟ್ಟು, ನಂತರ ಮತ್ತೆ ಪ್ರಯತ್ನಿಸಿ.

ಬಹು ಭಾಷೆಗಳಲ್ಲಿ ಬರೆಯಲಾದ ಡಾಕ್ಯುಮೆಂಟ್ ಅನ್ನು ನೀವು ತಲುಪಿದಂತೆ ಕಾಣುತ್ತದೆ, ನಿಮ್ಮ ಸ್ಥಳೀಯ ಭಾಷೆಯಲ್ಲದ ಒಂದು ಭಾಷೆಯೂ ಸೇರಿದಂತೆ. ನೀವು ಇಷ್ಟಪಡದ ಭಾಷೆಯಿಲ್ಲದ ಪುಟಗಳನ್ನು ತಾತ್ಕಾಲಿಕವಾಗಿ ಮರೆಮಾಡಲು ನೀವು ಕೆಳಗಿನ ಲಿಂಕ್‌ಗಳನ್ನು ಬಳಸಬಹುದು.