This page details the features of the NFC HAL for MicroRead module in Open NFC stack. If you are interested in the features of the MicroRead or SecuRead hardware; please check the product details on Inside Secure‘s website.

The NFC HAL for MicroRead module fully supports the NFC HAL protocol used by Open NFC stack. This means that all features available in the Open NFC stack can be used with a MicroRead or SecuRead controller.

The NFC HAL for MicroRead module does not embed any cryptographic function. An application using Open NFC has to implement the cryptography and use the low-level data exchange API in order to access the protected contents on the cards that require cryptography. High-level APIs are not available for these cards.

Here is the detailed status of the reader mode (“full support” means complete read/write/lock access to the card):

• Picopass: full support
• MiFare UL, UL C: full support
• MiFare Plus, DesFire: Cryptography must be provided separately. NDEF API can be used if the card is already formatted.
• Topaz, Topaz 512, Jewel: full support
• FeliCa: Cryptography must be provided separately. NDEF API can be used if the card is already formatted.
• My-d Move, My-d NFC: full support
• Kovio tag, Kovio 2K RFID: tag is fully read during detection, write operation not available.
• Smart MX: Communication via 7816 API is OK
• Micropass: NDEF API available if card formatted as Type 4; low-level API available.
• Type 4+: communication available via 7816 API and Type 4 API.
• ICODE, Tag-It: full support
• B Prime cards such as Calypso: Low-level API available, cryptography must be provided separately to actually exchange data with the card.

In terms of card emulation, this module and hardware fully supports the ISO 14443 4-A and 4-B protocols. The card emulation can be served from the application (via Open NFC), or from a secure element. The access policy can be configured separately for each standard (for example, 4-A being served by the UICC and 4-B by an eSE).

In terms of peer-to-peer, the module fully supports all the features from the Open NFC stack, as described here.

SecuRead

If your hardware is a SecuRead, you also have access to the SE API in the Open NFC stack, including functions like WSEGetInfo, WSEOpenConnection, … Please check the Open NFC API specification for more information on how to use this feature.

Note however that the SE features require additional work in the porting process; please refer as usual to the documentation included for more information.