| Electronic Components Datasheet Search |
|
A30 Datasheet(PDF) 10 Page - NXP Semiconductors |
|
|
|||||||||||||||||||||||||||||
A30 Datasheet(HTML) 10 Page - NXP Semiconductors |
|
10 / 209 page ![]() NXP Semiconductors A30 Secure Authenticator In general, A30, supports Extended Length fields for Lc and Le, see [4]. However, for some commands the supported input size is restricted as specified in the command definition. Field Description Length Response data field Response data if any, absent if no response data up to Le Response trailer status byte (SW1SW2) 2 Table 5. ISO/IEC 7816-4 response fields The field length and presence might vary for different commands, refer to the specific command description in Section 7. 6.2.3 Command chaining A30 supports standard ISO/IEC 14443-4 [3] command chaining in the following cases: • the PICC supports ISO/IEC 14443-4 chaining to allow larger command or response frames than the supported buffer size for variants of the following commands: – Native commands wrapped into ISO/IEC 7816-4 APDU: ReadData, WriteData, see Section 7. – Standard ISO/IEC 7816-4 commands: ISOReadBinary, ISOUpdateBinary i.e. every command where a larger frame size can occur. • the PICC automatically split a response in several frames to fit with the FSD frame size supported by the PCD and communicated in the RATS. When a PCD applies ISO/IEC 14443-4 chaining, see [3], it must assure the reassembled INF field containing the command header (i.e. ISO/IEC 7816-4 header bytes and/or (Cmd || CmdHeader)) fits within the PICC’s buffer (FSC) communicated in the ATS. If not, the PICC may respond with LENGTH_ERROR. The ISO/IEC 14443-4 chaining does not influence the secure messaging. This means that the secure messaging mechanisms are applied as if the command or response would have been sent in a single large frame. With regard to command execution, commands are handled as if they were received in one large frame, except for write commands where the total frame size can be larger than the supported FSC (WriteData and ISOUpdateBinary). In this case, command execution is started before the complete command is received. For single frame write operations or chained frames that fit within the supported FSC it is ensured that either the data is completely written or not at all. 6.3 Authentication and Secure Messaging 6.3.1 Authentication overview The A30 supports several mutual authentication protocols: • symmetric mutual authentication: this authentication is initiated by AuthenticateEV2First or AuthenticateEV2NonFirst. The protocol is inherited and compatible with NTAG42x and MIFARE DESFire. It is based on AES-128 or AES-256. • asymmetric mutual authentication: this authentication is initiated by ISOGeneralAuthenticate. It is based on 256-bit ECC. Both mutual authentication methods initiate an EV2 secure messaging channel, see Section 6.3.6 based on AES-128 or AES-256 session keys. Each authentication option can be used with different keys and on different I/O interfaces. However, the A30 only supports a single authentication session. The authentication session applies to the I/O interface, which 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 10 / 209 |
|
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 |
| 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 |