MF3DX2 NXP | Alldatasheet
Document overview
- Manufacturer or author: Provided By ALLDATASHEET.COM(FREE DATASHEET DOWNLOAD SITE)
- PDF pages: 27
Technical content
MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Rev. 3.2 — 12 June 2019 Product short data sheet
364232 COMPANY PUBLIC
1 General description
1.1 Introduction
MIFARE DESFire EV2 contactless IC (MF3D(H)x2) is the latest addition to the MIFARE DESFire product family introducing new features along with enhanced performance for best user experience. The MIFARE DESFire EV2 is Common Criteria EAL5+ security certified which is the same security certification level as demanded for smart card IC products used e.g. for banking cards or electronic passports. It fully complies with the requirements for fast and highly secure data transmission and flexible application management. This makes it the ideal product for service providers and service operators who want to offer an easy, convenient and secure access to a wide variety of different services. MIFARE DESFire EV2 offers best flexibility when creating multi-application schemes and features such as MIsmartApp with multiple key sets and Transaction MAC are supporting new business models. Smart Cities services, for example, could be utilized with only one MIFARE DESFire EV2 card by combining services such as public transport, car or bike sharing, access to city attractions with citizen services, closed-loop e-payment applications and local loyalty programs. MIFARE DESFire EV2 is based on global open standards for both air interface and cryptographic methods. It is compliant to all levels of ISO/IEC 14443A and supports optional ISO/IEC 7816-4 commands (APDU and file structure supported) and is fully interoperable with existing NFC readers for MIFARE products. Featuring an on-chip backup management system and the mutual three-pass authentication, a MIFARE DESFire EV2 card1 can hold as many applications as the memory can accommodate. Each application can hold up to 32 files with various data configurations. The size of each file is defined at the moment of its creation, making MIFARE DESFire EV2 a truly flexible and convenient product. An automatic anti-tear mechanism is available for all file types, guaranteeing transaction-oriented data integrity. The main characteristics of this device are denoted by its name "DESFire": DES indicates the high level of security using a 3DES or AES hardware cryptographic engine for confidentiality and integrity protection of the transmission data. Fire indicates its outstanding position as a Fast, Innovative, Reliable and Secure IC in the contactless proximity transaction market. MIFARE DESFire EV2 delivers the perfect balance of speed, performance and cost efficiency. Its open concept allows seamless future integration of other ticketing media such as smart paper tickets, banking convergence card, and mobile ticketing based on Near Field Communication (NFC) technology. It is also fully compatible with the existing
1 In this document the term „MIFARE DESFire card“ refers to a MIFARE DESFire IC-based contactless
card.
secure contactless systems worldwide.
1.2 Evolution of MIFARE DESFire products family
with both MIFARE DESFire EV1 and MIFARE DESFire D40 (MF3ICD40). products. The latest generation encompasses the features from the older generation(s). minimum or no changes to their infrastructures.
2 KB, 4KBor 8KBEEPROM
1 PICCkey, 14keys perApp
Figure 1. Evolution of MIFARE DESFire
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Product short data sheet Rev. 3.2 — 12 June 2019 COMPANY PUBLIC 364232 3 / 27
2 Features and benefits
2.1 Features overview
2.1.1 RF interface: ISO/IEC 14443 Type A
- Contactless interface compliant with ISO/IEC 14443-2/3 A
- Low Hmin enabling operating distance up to 100 mm (depending on power provided by the PCD and antenna geometry)
- Fast data transfer: 106 kbit/s, 212 kbit/s, 424 kbit/s, 848 kbit/s
- 7 bytes unique identifier (option for Random ID)
- Uses ISO/IEC 14443-4 transmission protocol
- Configurable FSCI to support up to 128 bytes (256 bytes for 16 and 32 kB) frame size
2.1.2 Non-volatile memory
- 2 kB, 4 kB, 8 kB, 16 kB or 32 kB NV
- Data retention of 25 years
- Write endurance typical 500 000 cycles
- Fast programming cycles (erase/write)
2.1.3 NV-memory organization
- Flexible file system: user can freely define application structures on PICC
- Virtually no limitation on number of applications per PICC (new)
- Up to 32 files in each application (6 file types available: Standard Data file, Back-up Data file, Value file, Linear Record file, Cyclic Record file and Transaction MAC file)
- File size is determined during creation (not for Transaction MAC file)
2.1.4 Security
- Common Criteria certification: EAL5+ (Hardware and Software)
- Unique 7 bytes serial number for each device
- Optional "RANDOM" ID for enhance security and privacy
- Mutual three-pass authentication
- Mutual authentication according to ISO/IEC 7816-4
- Flexible key management: 1 card master key and up to 14 keys per application
- Hardware DES using 56/112/168 bit keys featuring key version
- Hardware AES using 128-bit keys featuring key version
- Data authenticity by 8 byte CMAC
- Data encryption on RF-channel
- Authentication on application level
- Hardware exception sensors
- Self-securing file system
- Backward compatibility to MF3ICD40: 4 byte MAC, CRC 16
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Product short data sheet Rev. 3.2 — 12 June 2019 COMPANY PUBLIC 364232 4 / 27
2.1.5 New features on MIFARE DESFire EV2
- MIsmartApp (Delegated Application Management)
- Memory reuse in DAM applications (Format Application)
- Transaction MAC on application level
- Multiple Key Sets per application with fast key rolling mechanism (up to 16 sets)
- Accessing files from any two applications during a single transaction
- Multiple keys assignments for each file access right (up to 8)
- Virtual Card Architecture for enhanced card/application selection on multi-VC devices with privacy protection
- Proximity Check for protection against Relay Attacks
- Originality Check for proof of genuine NXP’s product
- New EV2 Secure Messaging based on AES (similar with MIFARE Plus’s secure messaging)
2.1.6 ISO/IEC 7816 compatibility
- Supports ISO/IEC 7816-4 file structure (selection by File ID or DF name)
- Supports ISO/IEC 7816-4 APDU message structure
- Supports ISO/IEC 7816-4 APDU wrapper for MIFARE DESFire native commands
- Supports ISO/IEC 7816-4 INS code ‘A4’ for SELECT FILE
- Supports ISO/IEC 7816-4 INS code ‘B0’ for READ BINARY
- Supports ISO/IEC 7816-4 INS code ‘D6’ for UPDATE BINARY
- Supports ISO/IEC 7816-4 INS code ‘B2’ for READ RECORDS
- Supports ISO/IEC 7816-4 INS code ‘E2’ for APPEND RECORD
- Supports ISO/IEC 7816-4 INS code ‘84’ for GET CHALLENGE
- Supports ISO/IEC 7816-4 INS code ‘88’ for INTERNAL AUTHENTICATE
- Supports ISO/IEC 7816-4 INS code ‘82’ for EXTERNAL AUTHENTICATE
2.1.7 Special features
- Transaction-oriented automatic anti-tear mechanism
- Configurable ATS information for card personalization
- Backward compatibility mode to MIFARE DESFire EV1 and D40 (MF3ICD40)
- Optional high input capacitance (70 pF) for small form factor designs (MF3DHx2)
2.2 Summary of key differences between MIFARE DESFire generations
Table 1. Key differences between MIFARE DESFire generations
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Product short data sheet Rev. 3.2 — 12 June 2019 COMPANY PUBLIC 364232 6 / 27
3 Applications
- Secure public transport ticketing
- Multi-application smart city and mobility card
- Secure access management
- Micro-payment and Loyalty
- Student ID
- Road tolling and parking
- Hospitality
- Event ticketing
4 Quick reference data
Table 2. Quick reference data [1][2] [1] Stresses above one or more of the values may cause permanent damage to the device. [2] Exposure to limiting values for extended periods may affect device reliability. [3] Measured with LCR meter.
5 Ordering information
Table 3. Ordering information
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Product short data sheet Rev. 3.2 — 12 June 2019 COMPANY PUBLIC 364232 9 / 27 Type number Package Description Version MF3DA200DU15/02 FFC 12 inch wafer (sawn; 150 μm thickness)[1][2]; 32 K NV, 17 pF input capacitance MF3DH9200DU15/02 FFC 12 inch wafer (sawn; 150 μm thickness)[1][2]; 16 K NV, 70 pF input capacitance MF3DHA200DU15/02 FFC 12 inch wafer (sawn; 150 μm thickness)[1][2]; 32 K NV, 70 pF input capacitance MF3D9200DU75/02 FFC 12 inch wafer (sawn; 75 μm thickness)[1][2]; 16 K NV, 17 pF input capacitance MF3DA200DU75/02 FFC 12 inch wafer (sawn; 75 μm thickness)[1][2]; 32 K NV, 17 pF input capacitance MF3DH9200DU75/02 FFC 12 inch wafer (sawn; 75 μm thickness)[1][2]; 16 K NV, 70 pF input capacitance MF3DHA200DU75/02 FFC 12 inch wafer (sawn; 75 μm thickness)[1][2]; 32 K NV, 70 pF input capacitance MF3D9200DA4/02 MOB4 plastic leadless module carrier package; 16 K NV, 17 pF input capacitance SOT500-2 MF3DA200DA4/02 MOB4 plastic leadless module carrier package; 32 K NV, 17 pF input capacitance SOT500-2 MF3DH9200DA4/02 MOB4 plastic leadless module carrier package; 16 K NV, 70 pF input capacitance SOT500-2 MF3DHA200DA4/02 MOB4 plastic leadless module carrier package; 32 K NV, 70 pF input capacitance SOT500-2 MF3D9200DA6/02 MOB6 plastic leadless module carrier package; 16 K NV, 17 pF input capacitance SOT500-3 MF3DA200DA6/02 MOB6 plastic leadless module carrier package; 32 K NV, 17 pF input capacitance SOT500-3 MF3DH9200DA6/02 MOB6 plastic leadless module carrier package; 16 K NV, 70 pF input capacitance SOT500-3 MF3DHA200DA6/02 MOB6 plastic leadless module carrier package; 32 K NV, 70 pF input capacitance SOT500-3 [1] Delivered on film frame carrier with electronic failed die marking according to SECSII format. [2] See [2]
6 Block diagram
Figure 2. MIFARE DESFire EV2 IC block diagram
7 Functional description
7.1 Introduction
the-shelf development platform for smart card application providers. data storage and 1 file type for storing Transaction MAC as detailed in Section 8.6. also supports the ISO/IEC 7816-4 file structure and APDU. At the PICC level, there is another set of keys and security settings for the PICC owner. have access to the application's files, unless he knows the application keys too. Up to 14 keys, free and never access options per application. Figure 3. MIFARE DESFire EV2 product-based application and file structure
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Product short data sheet Rev. 3.2 — 12 June 2019 COMPANY PUBLIC 364232 12 / 27 MIFARE DESFire EV2 offers a transaction-oriented backup mechanism to prevent inconsistent updating of data storage across multiple files during a tearing situation. When transaction tearing occurs, either all data fields are updated or none is altered. Besides the application file structure support, MIFARE DESFire EV2 offers many optional features such as following:
- Delegated Application Management (MIsmartApp) for giving rights to third-party application creation and management.
- Multiple key set within an application with key rolling mechanism and key migration supported.
- Shared files between two applications, supporting a single transaction over two applications at the same time.
- Multiple keys for each access right of files.
- Transaction MAC on application level, MACing the transacted data with a secret key on the card and served as a proof of transaction to the backend system.
- Virtual Card Architecture providing a privacy protecting mechanism during card selection.
- Proximity Check to prevent against relay attacks.
- Originality Check for verification of genuine MIFARE DESFire EV2 product from NXP or its licensees. The following chapters provide basic description of some functionality on MIFARE DESFire EV2. For a more detailed description of each functionality on MIFARE DESFire EV2, see [1].
7.2 Contactless energy and data transfer
In the MIFARE product-based system, the MIFARE DESFire EV2 is connected to a coil consisting of a few turns embedded in a standard ISO/IEC smart card. A battery is not needed. When the card is positioned in the proximity of the PCD antenna, the high-speed RF communication interface allows data to be transmitted up to 848 kbit/s.
7.3 Anti-collision
An intelligent anti-collision mechanism allows more than one MIFARE DESFire EV2 in the field to be handled simultaneously. The anti-collision algorithm selects each MIFARE DESFire EV2 individually and ensures that the execution of a transaction with a selected MIFARE DESFire EV2 is performed correctly without data corruption resulting from other MIFARE DESFire EV2s in the field.
7.4 UID/serial number
The unique 7 byte (UID) is programmed into a locked part of the NV memory which is reserved for the manufacturer. Due to security and system requirements these bytes are write-protected after being programmed by the IC manufacturer at production time. According to ISO/IEC 14443-3 during the first anti-collision loop the cascade tag returns a value of 88h and also the first 3 bytes of the UID, UID0 to UID2 and BCC. The second anti-collision loop returns bytes UID3 to UID6 and BCC. UID0 holds the manufacturer ID for NXP (04h) according to ISO/IEC 14443-3 and ISO/ IEC 7816-6 AMD 1.
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Product short data sheet Rev. 3.2 — 12 June 2019 COMPANY PUBLIC 364232 13 / 27 MIFARE DESFire EV2 also allows Random ID to be used. In this case, MIFARE DESFire EV2 only uses a single anti-collision loop. The 3 byte random number is generated after RF reset of the MIFARE DESFire EV2.
7.5 Memory organization
The NV memory is organized using a flexible file system. This file system allows multiple numbers of different applications on one MIFARE DESFire EV2. Each application can have multiple files. Every application is represented by its 3 bytes Application IDentifier (AID) and an optional ISO DF Name. 5 different data file types and 1 Transaction MAC file type are supported; see Section 8.6. A guideline to assign DESFire AIDs can be found in the application note MIFARE Application Directory (MAD); see [3]. Each file can be created either at MIFARE DESFire EV2 initialization (card production/ card printing), at MIFARE DESFire EV2 personalization (vending machine) or in the field. If a file or application becomes obsolete in operation, it can be permanently invalidated. Commands which have impact on the file structure itself (e.g. creation or deletion of applications, change of keys) activate an automatic rollback mechanism, which protects the file structure from being corrupted. If this rollback is necessary, it is done without user interaction before carrying out further commands. To ensure data integrity on application level, a transaction-oriented backup is implemented for all file types with backup. It is possible to mix file types with and without backup within one application.
7.6 Available file types
The files within an application can be any of the following types:
- Standard data files
- Backup data files
- Value files with backup
- Linear record files with backup
- Cyclic record files with backup
- Transaction MAC file
7.7 Security
The 7 byte UID is fixed, programmed into each device during production. It cannot be altered and ensures the uniqueness of each device. The UID may be used to derive diversified keys for each ticket. Diversified MIFARE DESFire EV2 keys contribute to gain an effective anti-cloning mechanism and increase the security of the original key. Prior to data transmission a mutual three-pass authentication can be done between MIFARE DESFire EV2 and PCD depending on the configuration employing either 56-bit DES (single DES, DES), 112-bit DES (triple DES, 3DES), 168-bit DES (3 key triple DES, 3K3DES) or AES. During the authentication, the level of security of all further commands during the session is set. In addition, the communication settings of the file/application
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Product short data sheet Rev. 3.2 — 12 June 2019 COMPANY PUBLIC 364232 14 / 27 result in the following options of secure communication between MIFARE DESFire EV2 and PCD:
- Plain data transfer (only possible within the backwards-compatible mode to MF3ICD40 and EV2 secure messaging)
- Plain data transfer with cryptographic checksum (MAC): Authentication with backwards-compatible mode to MF3ICD40: 4 byte MAC; All other authentications based on DES/3DES/AES: 8 byte CMAC
- Encrypted data transfer (secured by CRC before encryption): Authentication with backwards-compatible mode to MF3ICD40: A 16-bit CRC is calculated over the stream and attached. The resulting stream is encrypted using the chosen cryptographic method. All other authentications-based DES/3DES/AES: A 32-bit CRC is calculated over the stream and attached. The resulting stream is encrypted using the chosen cryptographic method. A cryptographic checksum (CMAC) will also be attached when using EV2 secure messaging. Find more information on the security concept of the product in [1]. Be aware not all levels of security are recommended. For new design, the EV2 secure messaging is recommended.
8 DESFire command set
of all commands is provided in [1].
8.1 Secure Messaging Commands
Table 4. Secure messaging commands overview EV1 backwards compatible secure messaging is used. compatible secure messaging is used.
8.2 Memory and Configuration Management Commands
Table 5. Memory and configuration management commands overview deleted memory is released and can be reused. communication setup and configures the ATS string. GetVersion Returns manufacturing related data of the PICC.
8.3 Key Management Commands
Table 6. Key management commands overview ChangeKey Changes any key stored on the PICC. key of the PICC or of one specified application keyset.
GetKeySettings Gets information on the PICC and application master key settings. ChangeKeySettings Changes the master key settings on PICC and application level. GetKeyVersion Reads out the current key version of any key stored on the PICC.
8.4 Application Management Commands
Table 7. Application management commands overview key set are initialized with the Default Application Key. DeleteApplication Permanently deactivates applications on the PICC. SelectApplication Selects one specific application for further access. GetApplicationIDs Returns the Application IDentifiers of all applications on a PICC.
8.5 File Management Commands
Table 8. File management commands overview existing application on the PICC. of an integrated backup mechanism. values within an existing application on the PICC. writing to the file is not possible unless it is cleared.
written one. This wrap is fully transparent for the PCD. feature for the targeted application. GetISOFileIDs Get back the ISO File ID. GetFileSettings Get information on the properties of a specific file. ChangeFileSettings Changes the access parameters of an existing file.
8.6 Data Management Commands
Table 9. Data management commands overview ReadData Reads data from FileType.StandardData or FileType.BackupData. GetValue Reads the currently stored value from FileType.Value. Credit Increases a value stored in a FileType.Value. Debit Decreases a value stored in a FileType.Value. without having full Credit permissions to the file.
8.7 Transaction Management Commands
Table 10. Transaction management commands overview
backend to identify the attacking merchant in case of fraud detected.
8.8 ISO/IEC 7816-4 Standard Commands
Table 11. ISO/IEC 7816-4 support commands overview ISOUpdateBinary Write data to FileType.StandardData and FileType.BackupData files. FileType.CyclicRecord files.
8.9 Virtual Card Commands
Table 12. Virtual Card commands overview ISOSelect Select VC with the given IID. ISOExternalAuthenticate Authenticate PCD before accessing the VC.
8.10 Proximity Check Commands
Table 13. Proximity Check commands overview
8.11 Originality Check Commands
Table 14. Originality Check commands overview
9 Limiting values
Table 15. Limiting values [1][2] In accordance with the Absolute Maximum Rating System (IEC 60134). [1] Stresses above one or more of the limiting values may cause permanent damage to the device. [2] Exposure to limiting values for extended periods may affect device reliability. [4] MIL Standard 883-C method 3015; Human Body Model: C = 100 pF, R = 1.5 kΩ. precautions for handling electrostatic sensitive devices. JESD625-A or equivalent standards.
10 Abbreviations
Table 16. Abbreviations
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Product short data sheet Rev. 3.2 — 12 June 2019 COMPANY PUBLIC 364232 21 / 27
11 References
[1] Data sheet MF3Dx2 MIFARE DESFire EV2 Functional specification, document number: 22602. [2] Data sheet MF3D(H)x2 Wafer specification, document number: 2953. [3] Application note MIFARE Application Directory, document number: 0018. [4] Data sheet MF3D92/MF3DA2 MIFARE DESFire EV2 16 kB and 32 kB contactless smartcard IC, document number: 48273. 2 ... BU-ID document version number 3 ... BU-ID document version number
Table 17. Revision history
20160224 Preliminary short data
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Product short data sheet Rev. 3.2 — 12 June 2019 COMPANY PUBLIC 364232 23 / 27
13 Legal information
13.1 Data sheet status
Document status[1][2] Product status[3] Definition Objective [short] data sheet Development This document contains data from the objective specification for product development. Preliminary [short] data sheet Qualification This document contains data from the preliminary specification. Product [short] data sheet Production This document contains the product specification. [1] Please consult the most recently issued document before initiating or completing a design. [2] The term 'short data sheet' is explained in section "Definitions". [3] The product status of device(s) described in this document may have changed since this document was published and may differ in case of multiple devices. The latest product status information is available on the Internet at URL http://www.nxp.com.
13.2 Definitions
Draft — The document is a draft version only. The content is still under internal review and subject to formal approval, which may result in modifications or additions. NXP Semiconductors does not give any representations or warranties as to the accuracy or completeness of information included herein and shall have no liability for the consequences of use of such information. Short data sheet — A short data sheet is an extract from a full data sheet with the same product type number(s) and title. A short data sheet is intended for quick reference only and should not be relied upon to contain detailed and full information. For detailed and full information see the relevant full data sheet, which is available on request via the local NXP Semiconductors sales office. In case of any inconsistency or conflict with the short data sheet, the full data sheet shall prevail. Product specification — The information and data provided in a Product data sheet shall define the specification of the product as agreed between NXP Semiconductors and its customer, unless NXP Semiconductors and customer have explicitly agreed otherwise in writing. In no event however, shall an agreement be valid in which the NXP Semiconductors product is deemed to offer functions and qualities beyond those described in the Product data sheet.
13.3 Disclaimers
Limited warranty and liability — Information in this document is believed to be accurate and reliable. However, NXP Semiconductors does not give any representations or warranties, expressed or implied, as to the accuracy or completeness of such information and shall have no liability for the consequences of use of such information. NXP Semiconductors takes no responsibility for the content in this document if provided by an information source outside of NXP Semiconductors. In no event shall NXP Semiconductors be liable for any indirect, incidental, punitive, special or consequential damages (including - without limitation - lost profits, lost savings, business interruption, costs related to the removal or replacement of any products or rework charges) whether or not such damages are based on tort (including negligence), warranty, breach of contract or any other legal theory. Notwithstanding any damages that customer might incur for any reason whatsoever, NXP Semiconductors’ aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms and conditions of commercial sale of NXP Semiconductors. Right to make changes — NXP Semiconductors reserves the right to make changes to information published in this document, including without limitation specifications and product descriptions, at any time and without notice. This document supersedes and replaces all information supplied prior to the publication hereof. Suitability for use — NXP Semiconductors products are not designed, authorized or warranted to be suitable for use in life support, life-critical or safety-critical systems or equipment, nor in applications where failure or malfunction of an NXP Semiconductors product can reasonably be expected to result in personal injury, death or severe property or environmental damage. NXP Semiconductors and its suppliers accept no liability for inclusion and/or use of NXP Semiconductors products in such equipment or applications and therefore such inclusion and/or use is at the customer’s own risk. Applications — Applications that are described herein for any of these products are for illustrative purposes only. NXP Semiconductors makes no representation or warranty that such applications will be suitable for the specified use without further testing or modification. Customers are responsible for the design and operation of their applications and products using NXP Semiconductors products, and NXP Semiconductors accepts no liability for any assistance with applications or customer product design. It is customer’s sole responsibility to determine whether the NXP Semiconductors product is suitable and fit for the customer’s applications and products planned, as well as for the planned application and use of customer’s third party customer(s). Customers should provide appropriate design and operating safeguards to minimize the risks associated with their applications and products. NXP Semiconductors does not accept any liability related to any default, damage, costs or problem which is based on any weakness or default in the customer’s applications or products, or the application or use by customer’s third party customer(s). Customer is responsible for doing all necessary testing for the customer’s applications and products using NXP Semiconductors products in order to avoid a default of the applications and the products or of the application or use by customer’s third party customer(s). NXP does not accept any liability in this respect. Limiting values — Stress above one or more limiting values (as defined in the Absolute Maximum Ratings System of IEC 60134) will cause permanent damage to the device. Limiting values are stress ratings only and (proper) operation of the device at these or any other conditions above those given in the Recommended operating conditions section (if present) or the Characteristics sections of this document is not warranted. Constant or repeated exposure to limiting values will permanently and irreversibly affect the quality and reliability of the device. Terms and conditions of commercial sale — NXP Semiconductors products are sold subject to the general terms and conditions of commercial sale, as published at http://www.nxp.com/profile/terms, unless otherwise agreed in a valid written individual agreement. In case an individual agreement is concluded only the terms and conditions of the respective agreement shall apply. NXP Semiconductors hereby expressly objects to applying the customer’s general terms and conditions with regard to the purchase of NXP Semiconductors products by customer.
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Product short data sheet Rev. 3.2 — 12 June 2019 COMPANY PUBLIC 364232 24 / 27 No offer to sell or license — Nothing in this document may be interpreted or construed as an offer to sell products that is open for acceptance or the grant, conveyance or implication of any license under any copyrights, patents or other industrial or intellectual property rights. Quick reference data — The Quick reference data is an extract of the product data given in the Limiting values and Characteristics sections of this document, and as such is not complete, exhaustive or legally binding. Export control — This document as well as the item(s) described herein may be subject to export control regulations. Export might require a prior authorization from competent authorities. Non-automotive qualified products — Unless this data sheet expressly states that this specific NXP Semiconductors product is automotive qualified, the product is not suitable for automotive use. It is neither qualified nor tested in accordance with automotive testing or application requirements. NXP Semiconductors accepts no liability for inclusion and/or use of non- automotive qualified products in automotive equipment or applications. In the event that customer uses the product for design-in and use in automotive applications to automotive specifications and standards, customer (a) shall use the product without NXP Semiconductors’ warranty of the product for such automotive applications, use and specifications, and (b) whenever customer uses the product for automotive applications beyond NXP Semiconductors’ specifications such use shall be solely at customer’s own risk, and (c) customer fully indemnifies NXP Semiconductors for any liability, damages or failed product claims resulting from customer design and use of the product for automotive applications beyond NXP Semiconductors’ standard warranty and NXP Semiconductors’ product specifications. Translations — A non-English (translated) version of a document is for reference only. The English version shall prevail in case of any discrepancy between the translated and English versions.
13.4 Licenses
ICs with DPA Countermeasures functionality NXP ICs containing functionality implementing countermeasures to Differential Power Analysis and Simple Power Analysis are produced and sold under applicable license from Cryptography Research, Inc.
13.5 Trademarks
Notice: All referenced brands, product names, service names and trademarks are the property of their respective owners. MIFARE — is a trademark of NXP B.V. DESFire — is a trademark of NXP B.V.
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Product short data sheet Rev. 3.2 — 12 June 2019 COMPANY PUBLIC 364232 25 / 27 Tables Tab. 1. Key differences between MIFARE DESFire Tab. 5. Memory and configuration management Tab. 7. Application management commands Tab. 10. Transaction management commands Tab. 11. ISO/IEC 7816-4 support commands
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Product short data sheet Rev. 3.2 — 12 June 2019 COMPANY PUBLIC 364232 26 / 27 Figures Fig. 3. MIFARE DESFire EV2 product-based
NXP Semiconductors MF3D(H)x2 MIFARE DESFire EV2 contactless multi-application IC Please be aware that important notices concerning this document and the product(s) described herein, have been included in section 'Legal information'. © NXP B.V. 2019. All rights reserved. For more information, please visit: http://www.nxp.com For sales office addresses, please send an email to: salesaddresses@nxp.com Date of release: 12 June 2019 Document identifier: MF3Dx2_MF3DHx2_SDS Document number: 364232