Electronic Components Datasheet Search
  English  ▼

X  

A30 Datasheet(PDF) 33 Page - NXP Semiconductors

Part # A30
Description  Secure Authenticator
PDF  209 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Manufacturer  NXP [NXP Semiconductors]
Direct Link  http://www.nxp.com
Logo NXP - NXP Semiconductors

A30 Datasheet(HTML) 33 Page - NXP Semiconductors

Back Button A30 Datasheet HTML 29Page - NXP Semiconductors A30 Datasheet HTML 30Page - NXP Semiconductors A30 Datasheet HTML 31Page - NXP Semiconductors A30 Datasheet HTML 32Page - NXP Semiconductors A30 Datasheet HTML 33Page - NXP Semiconductors A30 Datasheet HTML 34Page - NXP Semiconductors A30 Datasheet HTML 35Page - NXP Semiconductors A30 Datasheet HTML 36Page - NXP Semiconductors A30 Datasheet HTML 37Page - NXP Semiconductors Next Button
Zoom Inzoom in Zoom Outzoom out
 33 / 209 page
background image
NXP Semiconductors
A30
Secure Authenticator
6.3.8.2 SDM Read Counter Limit
To allow limiting the number of reads that can be done with a single device applying Secure Dynamic
Messaging, an optional SDM Read Counter Limit can be configured. There are two main use cases:
• Limit the number of usages from the card side. Typically this can also be controlled from the back end
verifying the SDM for Read protected message.
• Limit the number of traces that can be collected on the symmetric crypto processing. This way the attack
potential via side-channel attacks can be further reduced.
The number of reads that can be executed for an SDM configured file can be limited by setting an SDM Read
Counter Limit (SDMReadCtrLimit). This is an unsigned integer of 3 bytes, related with SDMReadCtr. On the
interface, the SDMReadCtrLimit is represented LSB first. The SDMReadCtrLimit can be enabled by setting a
customized value with ChangeFileSettings. It can be retrieved with GetFileSettings.
Once the SDMReadCtr equals the SDMReadCtrLimit, no reading of the file with ReadData or ISOReadBinary
in not authenticated state can be executed. If authenticated, reading is always possible even if
SDMReadCtrLimit is reached, applying the regular secure messaging. If the SDMReadCtrLimit is disabled with
ChangeFileSettings, this is also equivalent to putting it to the maximum value: 0xFFFFFF.
6.3.8.3 PICCData
The PICCData holds metadata of the targeted PICC and file, consisting of the UID and/or the SDMReadCtr.
Whether PICCData is transmitted in plain or encrypted depends on the configuration of the SDMMetaRead
access rights on the file, see Section 7. If the SDMMetaRead access right is configured for free access (0xE),
PICCData is plain and is defined according to Table 15.
ASCII mirroring is reflected by the function EncodeASCII(), which means that each hexadecimal
character of the hexadecimal representation will be ASCII encoded using capitals. For example, the UID
0x04E141124C2880 becomes: 0x30 34h 0x45 31h 0x34 31h 0x31 32h 0x34 43h 0x32 38h 0x38 30h.
Mode
PICCData Value
Length with 7-byte UID
ASCII
EncodeASCII(UID)
UIDLength = 14 (i.e. 2*UIDLen)
ASCII
EncodeASCII(SDMReadCtr)
SDMReadCtrLength = 6 (i.e. 2 × 3)
Table 15. PICCData: plain encoding and lengths
The SDMReadCtr, as defined in Section 6.3.8.1, is represented MSB first for the ASCII case. If the
SDMMetaRead access right is configured for an application key, PICCData is encrypted as defined in
Section 6.3.8.4. In this case, the input plaintext for the encryption is always in binary encoding, while the output
ciphertext will be ASCII encoded.
The PICCData is mirrored within the file. This is configured with ChangeFileSettings via the related offsets.
In the case of plain mirroring (i.e. access right SDMMetaRead = 0xE):
• UIDOffset configures the UID mirroring position. It is only given if UID mirroring is enabled.
• SDMReadCtrOffset configures the SDMReadCtr mirroring position. It is only given if SDMReadCtr mirroring
is enabled. It is possible to enable the SDMReadCtr but without mirroring by putting SDMReadCtrOffset to
0xFFFFFF. In this case, it can be retrieved with the GetFileCounters command.
If UID and SDMReadCtr are mirrored within the file, they shall not overlap:
• UIDOffset ≥ SDMReadCtrOffset + SDMReadCtrLength OR SDMReadCtrOffset ≥ UIDOffset + UIDLength.
In the case of encrypted mirroring (i.e. SDMMetaRead = 0x0..0x4), PICCDataOffset configures the PICCData
mirroring. The encryption is outlined in Section 6.3.8.4.
A30
All information provided in this document is subject to legal disclaimers.
© 2025 NXP B.V. All rights reserved.
Product data sheet
Rev. 3.0 — 27 January 2025
Document feedback
976730
33 / 209



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