SCM SCL3711 Reference Manual
  1. Manuals
  2. Brands
  3. SCM Manuals
  4. Other
  5. SCL3711
  6. Reference manual

SCM SCL3711 Reference Manual

Multiprotocol contactless mobile reader scm scl3711
Hide thumbs
Table of Contents

Advertisement

Quick Links

SCM Microsystems
Reference Manual – version 1.3
SCL3711
Multiprotocol contactless mobile reader

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SCL3711 and is the answer not in the manual?

Questions and answers

Summary of Contents for SCM SCL3711

  • Page 1 SCM Microsystems Reference Manual – version 1.3 SCL3711 Multiprotocol contactless mobile reader...
  • Page 3 Reference manual SCL3711 Multiprotocol Contactless mobile Reader © SCM Microsystems Oskar-Messter-Strasse, 13 85737 Ismaning Germany Phone +49 89 9595 5000 • Fax +49 89 9595 5555...
  • Page 4 Document history Date Version Description of change 16/02/2009 Initial version 06/03/2009 Review and update by product management 18/03/2009 Final review for release 01/04/2009 Update – added examples of APDU sequences for a few commands + corrected a few typos Contact information http://www.scmmicro.com/products-services/smart-card-readers-terminals/contactless-dual- interface-readers.html For sales information, please email...

  • Page 5: Table Of Contents

    3.2. SCL3711 key features....................12 3.3. SCL3711 ordering information ..................13 3.4. SCL3711 customization options................... 13 3.5. Contactless communication principles and SCL3711 usage recommendations ..14 3.5.1. Power supply......................14 3.5.2. Data exchange ...................... 14 3.5.3. Recommendations ....................15 3.6.
  • Page 6 Set of APDU for ISO/IEC 14443-4 user tokens ............38 6.3.1. T=CL Command....................38 6.4. Set of APDU defined by SCM Microsystems ............... 39 6.4.1. Commands for communicating with NFC Forum Tags Type 1 tags..... 39 6.4.2. Commands for communicating with NFC Forum Tags Type 2......45 6.4.3.

  • Page 7: 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...

  • Page 8: Introduction To The Manual

    2.1. Objective of the manual This manual provides an overview of the hardware and software features of the SCL3711 multiprotocol mobile contactless reader, hereafter referred to as “SCL3711”. This manual describes in details interfaces and supported commands available for developers using SCL3711 in their applications.

  • Page 9: Definition Of Various Terms And Acronyms

    Distance coverage till ~10 cm. PUPI Pseudo unique PICC identifier Reserved for future use Radio Frequency STCIII Smart card reader controller ASIC from SCM Microsystems SW1 SW2 Status word defined in ISO7816 Universal Serial Bus Vendor ID (xyz)b Binary notation of a number x, y, z ∈{0,1}...

  • Page 10: References

    Interoperability Specification for ICCs and PC/SC Workgroup Personal Computer Systems v2.01 User manual of the NFC wrapper. This manual SCM Microsystems wrapper is part of SCM’s Contactless SDK. CCID Specification for Integrated Circuit(s) Cards USB-IF Interface Devices 1.1 Universal Serial Bus Specification 2.0...

  • Page 11: Conventions

    SCL3711 R EFERENCE ANUAL 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 in decimal is represented • in hexadecimal as 0xA3 •...

  • Page 12: General Information About Scl3711

    The state of the art multi-protocol feature set of SCL3711 qualifies it to be used in a wide range of applications such as payment, loyalty and ID schemes, or to enable devices with NFC connectivity.

  • Page 13: Scl3711 Ordering Information

    SCL3711 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 sales@scmmicro.com.

  • Page 14: Contactless Communication Principles And Scl3711 Usage Recommendations

    NFC mobile phone etc… Communication between SCL3711 and user tokens uses magnetic field inductive coupling. The magnetic field generated by SCL3711 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.

  • Page 15: Recommendations

    For this reason, SCM Microsystems has implemented in its driver the support for 1 slot only.

  • Page 16: Applications

    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. SCL3711 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.

  • Page 17: Scl3711 Characteristics

    SCL3711 high level architecture 4.1.1. Block diagram The link between SCL3711 and the host to which it is connected is the USB interface providing both the power and the communication channel. SCL3711 is based designed around an NFC controller which handles the USB communication to the host and the RF communication.

  • Page 18: Quick Reference Data

    BLACK Textured Finish Default logo SCM logo SCL3711 Default label Drawing with dimensions of the SCL3711 and accessories can be found in annex. 4.2.2. LED behavior The LED behavior of the SCL3711 is given below. SCL3711 states LED Indication (GREEN)
  • Page 19 Vendor 0x5591 0x04E6 PC/SC 2.0 NFC forum tag type 1 through SCM-specific APDU NFC forum tag type 2 through PC/SC-defined APDUs NFC forum tag type 3 through SCM-specific APDU ID1 format tokens supported NFC forum tag type 4 through PC/SC APDUs ISO/IEC 14443-4 PICC type A and type B MIFARE, Non-Secure FeliCa™...

  • Page 20: Software Modules

    No installer is available for installing the version of the driver this manual covers. To manually install the driver, please follow the following steps • Extract the content of the ZIP file SCM Microsystems has sent you • Plug-in the SCL3711 •...

  • Page 21: Utilities

    & NFC device: SCL3711 is listed by PC/SC applications as SCM Microsystems Inc. SCL3711 reader & NFC device N. Where N=0 if only one SCL3711 is connected but is incremented in case several SCL3711 are connected to the host.

  • Page 22: Pc/Sc 2.0 Compliant Atr

    PC/SC (see http://msdn.microsoft.com/en- us/library/aa379474(VS.85).aspx) should be used to send the 0x90 IOCTL to SCL3711 in order to determine what type of technology is the user token based on. The output buffer is a BYTE with the following meaning: Technology Value...
  • Page 23 SCL3711 R EFERENCE ANUAL 5.3.3.2. ATR for type A memory 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.
  • Page 24 SCL3711 R EFERENCE ANUAL 5.3.3.3. ATR for an NFC Forum tag type 1 user token (Topaz) Byte# Value Designation Description 0x3B Initial header 0x82 TD1 present. 2 historical bytes in following 0x80 Nibble8 indicates no TA2, TB2, TC2 and TD2 present...
  • Page 25 SCL3711 R EFERENCE ANUAL 5.3.3.4. ATR for a NFC Forum tag type 3 user token (FeliCa) Byte# Value Designation Description 0x3B Initial header 0x8C present. historical bytes following ATR 0x80 Nibble8 indicates no TA2, TB2, TC2 and TD2 present Nibble 0 means T=0...
  • Page 26 SCL3711 R EFERENCE ANUAL 5.3.3.5. 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 0x3B Initial header...

  • Page 27: Firmware

    5.4. Firmware 5.4.1. Transport protocol SCL3711 implements a transport protocol which is proprietary to NXP Semiconductors. 5.4.2. Automatic PPS Automatic PPS implemented is implemented. SCL3711 will automatically switch the highest baud rate commonly supported by the SCL3711 and the user token...

  • Page 28: Commands Description

    SCL3711 R EFERENCE ANUAL 6. Commands description 6.1. Generic APDUs 1.1.1. Get UID Command 6.1.1.1. Description This command will retrieve the UID or SNR or PUPI of the user token. This command can be used for all supported contactless technologies.

  • Page 29: Get Data Command

    SCL3711 R EFERENCE ANUAL 1.1.2. Get DATA Command 6.1.1.5. Description This command can be used to retrieve the ATS of an ISO/IEC14443-4A user token only. 6.1.1.6. Format 0xFF 0xCA 0x01 0x00 0x00 6.1.1.7. Response Data Out ATS + SW1 + SW2 6.1.1.8.

  • Page 30: Set Of Apdu For Contactless Storage User Tokens

    SCL3711 R EFERENCE ANUAL 6.2. 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).
  • Page 31 SCL3711 R EFERENCE ANUAL 6.2.1.5. 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:...

  • Page 32: Storage_Card_Cmds_Write_Binary

    SCL3711 R EFERENCE ANUAL 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 Data in 0xFF 0xD6 0x00 Block # 0xXX Data Where: • P2 indicate the memory block number where data should be written •...
  • Page 33 SCL3711 R EFERENCE ANUAL Will have the following effect on the memory content...

  • Page 34: Storage_Card_Cmds_Load_Keys

    SCL3711 R EFERENCE ANUAL 6.2.3. STORAGE_CARD_CMDS_LOAD_KEYS 6.2.3.1. Description Some type of user tokens like MIFARE Classic may require that the an authentication happens before any data can be read or written. To encrypt perform this authentication, keys need to be loaded in the reader’s memory using this command.

  • Page 35: Storage_Card_Cmds_Authenticate

    SCL3711 R EFERENCE ANUAL 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 Before this command successfully executed, STORAGE_CARD_CMDS_LOAD_KEY command must have been executed. 6.2.4.2. Format Data in 0xFF 0x86 0x00...
  • Page 36 SCL3711 R EFERENCE ANUAL 6.2.4.5. Example For a MIFARE Classic 1K card which has the following memory mapping: Authenticating with Key A against sector 0 would require sending the following sequence of APDU Authenticating with Key A against sector 1 or 2 would require sending the following sequence...

  • Page 37: Storage_Card_Cmds_Value_Block

    SCL3711 R EFERENCE ANUAL 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.

  • Page 38: Set Of Apdu For Iso/Iec 14443-4 User Tokens

    Set of APDU for ISO/IEC 14443-4 user tokens 6.3.1. T=CL Command 6.3.1.1. Description Using this command, SCL3711 transfers directly ISO/IEC7816-4 APDU to the user token. 6.3.1.2. Format Data Description of the APDU commands can be found in ISO/IEC 7816-4 specification.

  • Page 39: Set Of Apdu Defined By Scm Microsystems

    SCL3711 R EFERENCE ANUAL 6.4. Set of APDU defined by SCM Microsystems 6.4.1. Commands for communicating with NFC Forum Tags Type 1 tags Commands for Static and Dynamic Memory Models Read Identification (RID) • Read All Blocks 0 – Eh (RALL) •...
  • Page 40 SCL3711 R EFERENCE ANUAL 6.4.1.2. Read All Blocks (RALL) Description The RALL command reads-out the two header ROM bytes and the whole of the static memory blocks 0x0-0xE. Format Data 0xFF 0x52 0x00 0x00 0x00 Response Data SW1 SW2 HR0 HR1 120 bytes (Blocks 0x0 – 0xE)
  • Page 41 SCL3711 R EFERENCE ANUAL 6.4.1.3. Read Byte (READ) Description This command reads a single EEPROM memory byte within the static memory model area of blocks 0x0-0xE. Format Data 0xFF 0x54 0x00 Byte Address 0x00 Where P2 is coded as follow...
  • Page 42 SCL3711 R EFERENCE ANUAL 6.4.1.5. Write-No-Erase Byte (WRITE-NE) Description This command writes a byte value on an individual memory byte within the static memory model area of blocks 0x0-0xE. This command does not erase the value of the targeted byte before writing the new data.
  • Page 43 SCL3711 R EFERENCE ANUAL 6.4.1.6. Read Segment (RSEG) Description This command reads out a complete segment of memory. Format Data 0xFF 0x5A 0x00 Segment 0x00 Address Where P2 is coded as follow Bit # Value Description b0 – b3 (0000)b b4 –...
  • Page 44 SCL3711 R EFERENCE ANUAL 6.4.1.8. Write-Erase 8 bytes (WRITE-E8) Description This command erases a memory block and then writes a value to it. Format Data 0xFF 0x5E 0x00 Block 0x08 8 bytes of data to be Address written Where P2 codes the block address (value between 0x00 and 0xFF)

  • Page 45: Commands For Communicating With Nfc Forum Tags Type 2

    6.4.3. Commands for communication with NFC Forum Tags Type 3 This section describes APDUs SCM Microsystems defined for the following FeliCa™ non- secure commands. For further details on FeliCa™ the reader should contact Sony corporation. Some description can also be found in the JIS X 6319-4 (Japanese Industry Standard) or the...
  • Page 46 SCL3711 R EFERENCE ANUAL 6.4.3.2. Request Service Description <TBC> Format Data 0xFF 0x42 Number of 0x00 2 * P1 Service Code List / services/areas Area Code List Response Data SW1 SW2 8 bytes IDm + No. of Service or areas(n)

  • Page 47: Commands For Communicating With Nfc Forum Tags Type 4

    To interact with NFC Forum tag type 4 tags, ISO/IEC 7816-4-defined APDU are used and sent through SCL3711 using the T=CL command described earlier in this manual. The reader can find in NFC Forum tag type 4 specification both the definition of the APDU...

  • Page 48: Annexes

    SCL3711 R EFERENCE ANUAL 7. Annexes 7.1. Annex A 7.1.1. Status words table 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 AUTHENTICATION ERROR...

  • Page 49: Annex B - Mechanical Drawings

    SCL3711 R EFERENCE ANUAL 7.2. Annex B – Mechanical drawings...

Table of Contents