Electronic Components Datasheet Search
  English  ▼
ALLDATASHEET.NET

X  

MF2DL1000DA4/02 Datasheet(PDF) 27 Page - NXP Semiconductors

Part # MF2DL1000DA4/02
Description  MIFARE DESFire Light contactless application IC
PDF  132 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Manufacturer  NXP [NXP Semiconductors]
Direct Link  http://www.nxp.com
Logo NXP - NXP Semiconductors

MF2DL1000DA4/02 Datasheet(HTML) 27 Page - NXP Semiconductors

Back Button MF2DL1000DA4/02 Datasheet HTML 23Page - NXP Semiconductors MF2DL1000DA4/02 Datasheet HTML 24Page - NXP Semiconductors MF2DL1000DA4/02 Datasheet HTML 25Page - NXP Semiconductors MF2DL1000DA4/02 Datasheet HTML 26Page - NXP Semiconductors MF2DL1000DA4/02 Datasheet HTML 27Page - NXP Semiconductors MF2DL1000DA4/02 Datasheet HTML 28Page - NXP Semiconductors MF2DL1000DA4/02 Datasheet HTML 29Page - NXP Semiconductors MF2DL1000DA4/02 Datasheet HTML 30Page - NXP Semiconductors MF2DL1000DA4/02 Datasheet HTML 31Page - NXP Semiconductors Next Button
Zoom Inzoom in Zoom Outzoom out
 27 / 132 page
background image
NXP Semiconductors
MF2DL(H)x0
MIFARE DESFire Light contactless application IC
MF2DL_H_x0
All information provided in this document is subject to legal disclaimers.
© NXP B.V. 2019. All rights reserved.
Product data sheet
Rev. 3.3 — 5 April 2019
COMPANY PUBLIC
430733
27 / 132
be interrupted by other commands. On any command different from AuthenticateEV2First
- Part2 received after the successful execution of the first part, the PICC aborts the
ongoing authentication.
During this authentication phase, the PICC accepts messages from the PCD that are
longer than the lengths derived from this specification as long as LenCap is correct.
This feature is to support the upgradability to following generations of MF2DL(H)x0. The
PCD rejects answers from the PICC when they don’t have the proper length. Note that if
present, PCDcap2:1:Bit1 must not be set, otherwise LRP authentication is targeted, see
Section 9.2.5.
Upon reception of AuthenticateEV2First, the PICC validates the targeted key. If the key
does not exist, AuthenticateEV2First is rejected.
The PICC generates a random 16-byte challenge RndB and send this encrypted to
the PCD, according to Section 9.1.4. Additionally, the PICC resets CmdCtr to zero and
generate a random Transaction Identifier (TI).
Upon reception of the AuthenticateEV2First response from the PICC, the PCD also
generates a random 16-byte challenge RndA. The PCD encrypts, on his turn, the
concatenation of RndA with RndB', which is the received challenge after decryption
and rotating it left by one byte. Within AuthenticateEV2First - Part2, this is sent to the
PICC. Upon reception of AuthenticateEV2First - Part2, the PICC decrypts the second
message and validates the received RndB'. If not as expected, the command is rejected.
Else it generates RndA' by rotating left the received RndA by one byte. This is returned
together with the generated TI. Also, the PICC sends 12 bytes of capabilities to the PCD:
6 bytes of PICC capabilities PDcap2 and 6 bytes of PCD capabilities PCDcap2 that were
received on the command (sent back for verification).
The use of those capabilities, and the negotiation process is described in Section 9. Note
that part of PDCap will be configurable with SetConfiguration. PCDcap2 is used to refer
both to the value sent from the PCD to the PICC and to the value used in the encrypted
response message from the PICC to the PCD where in this case the PCDcap2 is the
adjusted version of the originally sent PCDcap2: i.e. truncated or padded with zero bytes
to a length of 6 bytes if needed.
On successful execution of the authentication protocol, the session keys
SesAuthMACKey and SesAuthENCKey are generated according to Section 9.1.7. The
PICC is in EV2 authenticated state and the Secure Messaging is activated. On any
failure during the protocol or if one of the OriginalityKey were targeted, the PICC ends up
in not authenticated state.
If there is a mismatch between the capabilities expected by the PCD and the capabilities
presented by the PICC to the PCD (both the PDcap2 and the echoed/adjusted
PCDcap2), it is the responsibility of the PCD to take the proper actions based on the
application the PCD is running. This decision is outside the scope of this specification.
9.1.6 AuthenticateEV2NonFirst Command
This section defines the Non-First Authentication, which is recommended to be used if
Secure Messaging is already active, see Table 17. In this procedure both, the PICC as
well as the PCD show in an encrypted way that they possess the same secret, i.e. the
same key. This authentication is supported with AES keys.
The authentication consists of two parts: AuthenticateEV2NonFirst - Part1 and
AuthenticateEV2NonFirst - Part2. Detailed command definition can be found in
Section 11.4.2. This command is rejected if there is no active authentication, except if the



Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100  ...More


Datasheet Download

Go To PDF Page


Link URL



Does ALLDATASHEET help your business so far?  [ DONATE ] 

About Alldatasheet   |   Advertisement   |   Contact us   |   Privacy Policy   |   Link to Datasheet    |   Link Exchange   |   Manufacturer List
All Rights Reserved©Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn
Indian : Alldatasheet.in  |   Mexican : Alldatasheet.com.mx  |   British : Alldatasheet.co.uk  |   New Zealand : Alldatasheet.co.nz
Family Site : ic2ic.com  |   icmetro.com