| Electronic Components Datasheet Search |
|
A30 Datasheet(PDF) 68 Page - NXP Semiconductors |
|
|
|||||||||||||||||||||||||||||
A30 Datasheet(HTML) 68 Page - NXP Semiconductors |
|
68 / 209 page ![]() NXP Semiconductors A30 Secure Authenticator 6.8.2 Read Certificate Repository It is possible to read a certificate from a repository or to read a repository’s metadata using the ReadCertRepo command. Reading metadata does not require any authentication; if reading metadata in a secure tunnel then CommMode.MAC is applied. Reading a certificate directly from the repository requires access as defined in the Read access condition set during repository creation/reset. If reading using a standard APDU then the maximum response data length is 239 bytes. The format of the ReadCertRepo command is defined in Section 7.7.2. 6.9 Application Management A30 groups user data into an application. Within an application data is further grouped into files, as described in Section 6.10. A30 only holds one application, which is pre-configured at delivery, as defined in Section 6.9.2. In Section 6.9.1, it is detailed how applications can be selected. 6.9.1 Application Selection An application can only be selected with ISOSelectFile, see Section 6.15.1.4. 6.9.2 Application Definition A30 comes pre-configured with one application. It shall have the following properties for application selection: • DFName: 0xD2760000850101 • ISOFile Identifier: 0xE110 6.10 File Management A30 maintains user data into files of specific types listed in Section 6.10.1. Files are managed through creation, information retrieval and update functions respectively specified in Section 6.10.4, Section 6.10.3 and Section 6.10.2.3. File access can be restricted with an access right management specified in Section 6.10.2. 6.10.1 File Types A30 supports the following types of data storage: • raw data as specified in Section 6.10.1.1 • monotonic counters as specified in Section 6.10.1.2 All A30 files are defined with a file number and the communication mode that has to be used when accessing the file data. The file number is coded over 1 byte. It is unique per file in an application. The communication mode is defined in Section 6.3.6.6. 6.10.1.1 FileType.StandardData FileType.StandardData stores the data as raw data byte per byte. Data is accessed by chunk of byte at a certain offset in the data file and with a certain length in byte. A FileType.StandardData file is created with CreateStdDataFile, see Section 6.10.4.1. As defined in Section 6.10.6, A30 holds three FileType.StandardData files at delivery. Next to this, the user can create additional files. 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 68 / 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 |