NTAG X DNA

This is only a wrapper layer to abstract the different NTAG X DNA implementations. With this wrapper it is possible to support more than one NTAG X DNA implementation in parallel, by adapting this wrapper. More...

Collaboration diagram for NTAG X DNA:

Modules
	Component : Software
	Software implementation of the NTAG X DNA commands. Here the NTAG X DNA commands are framed and exchanged to tag.
	ErrorCodes
	Error Codes received from tag and the equivalent Reader Library error codes.
	Defines
	Commands_SecureMessaging
	Describes about the NTAG X DNA Secure Messaging related commands.
	Commands_MemoryConfiguration
	Describes about the NTAG X DNA Memory and Configuration Management commands.
	Commands_SymmetricKeyManagement
	Describes about the NTAG X DNA Symmetric Key Management commands.
	Commands_ASymmetricKeyManagement
	Describes about the NTAG X DNA ASymmetric Key Management commands.
	Commands_CertificateKeyManagement
	Describes about the NTAG X DNA Certificate Management commands.
	Commands_FileManagement
	Describes about the NTAG X DNA File Management commands.
	Commands_DataManagement
	Describes about the NTAG X DNA Data Management commands.
	Commands_CryptoAPI
	Describes about the NTAG X DNA Crypto API commands.
	Commands_GPIOManagement
	Describes about the NTAG X DNA GPIO management commands.
	Commands_ISO7816
	Describes about the NTAG X DNA ISO/IEC 7816-4 Standard commands.
	Commands_Utility
	Describes about the NTAG X DNA Utility functions. These are not part of actual NTAG X DNA data sheet rather its for internal purpose.

Detailed Description

This is only a wrapper layer to abstract the different NTAG X DNA implementations. With this wrapper it is possible to support more than one NTAG X DNA implementation in parallel, by adapting this wrapper.

Note

• Below are the initialization(s) supported by this component.
  • Software Initialization
• This component requires CCM cryptography for SIGMA-I Authentication. For that, during Software Initialization call, mBedTLS component of CryptoSym be used for Encryption, MACing contexts. For Random Number Generator context use mBedTLS component of CryptoRng.
• The AL component uses two internal buffers for processing. One is named as Command Buffer and another as Processing Buffer.
• Memory for these internal buffers needs to be passed by the user during initialization.
• The internal buffer size should not be less than minimum. Minimum sizes are,
  • Command Buffer, the wCmdBufSize should be >= Minimum Command Buffer Size
  • Processing Buffer, the wPrsBufSize should be >= Minimum Processing Buffer Size
    • If the sizes are less than minimum, Parameter Size error will be returned.
• Processing buffer size should not be less than Command buffer size else Parameter Size error will be returned.
• After completion of the application, call below interfaces to clear all the internal buffers, its sizes, dependent components like CryptoSym and CryptASym etc...
  • De-Initialize Software Component
• It's must to Initialize the component again after calling De-Initialization.
• During Initialization of HAL component, make sure the transmit and response buffer size are not less than the maximum data that will be received.
• Call GetConfig with Additional Information as Configuration identifier when any of the interface returns General Failure or ISO7816 General Failure.