MIFARE DUOX

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

Collaboration diagram for MIFARE DUOX:

Modules
	Component : Software
	Software implementation of the MIFARE DUOX commands. Here the MIFARE DUOX commands are framed and exchanged to PICC.
	ErrorCodes
	Error Codes received from PICC and the equivalent Reader Library error codes.
	Defines
	Commands_SecureMessaging
	Describes about the MIFARE DUOX Secure Messaging related commands.
	Commands_MemoryConfiguration
	Describes about the MIFARE DUOX Memory and Configuration Management commands.
	Commands_SymmetricKeyManagement
	Describes about the MIFARE DUOX Symmetric Key Management commands.
	Commands_ASymmetricKeyManagement
	Describes about the MIFARE DUOX ASymmetric Key Management commands.
	Commands_ApplicationManagement
	Describes about the MIFARE DUOX Application Management commands.
	Commands_FileManagement
	Describes about the MIFARE DUOX File Management commands.
	Commands_DataManagement
	Describes about the MIFARE DUOX Data Management commands.
	Commands_TransactionManagement
	Describes about the MIFARE DUOX Transaction Management commands.
	Commands_CryptographicSupport
	Describes about the MIFARE DUOX Cryptographic Support commands.
	Commands_GPIOManagement
	Describes about the MIFARE DUOX GPIO commands.
	Commands_ISO7816
	Describes about the MIFARE DUOX ISO/IEC 7816-4 Standard commands.
	Commands_EVCharging
	Describes about the MIFARE DUOX EV Charging commands.
	Commands_Utility
	Describes about the MIFARE DUOX Utility functions. These are not part of actual MIFARE DUOX data sheet rather its for internal purpose.

Detailed Description

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

Note

• Below are the initializations supported by this component.
  • Software Initialization
• 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
• Its 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 PICC frame size.
• Call GetConfig with Additional Information as Configuration identifier when any of the interface returns General Failure or ISO7816 General Failure.