@struct nfc_barcode_info
@brief Thinfilm NFC Barcode information
@struct nfc_context
@brief NFC library context
Struct which contains internal options, references, pointers, etc. used by library
@struct nfc_dep_info
@brief NFC target information in D.E.P. (Data Exchange Protocol) see ISO/IEC 18092 (NFCIP-1)
@struct nfc_device
@brief NFC device information
@struct nfc_felica_info
@brief NFC FeLiCa tag information
@struct nfc_iso14443a_info
@brief NFC ISO14443A tag (MIFARE) information
@struct nfc_iso14443b2ct_info
@brief NFC ISO14443-2B ASK CTx tag information
@struct nfc_iso14443b2sr_info
@brief NFC ISO14443-2B ST SRx tag information
@struct nfc_iso14443b_info
@brief NFC ISO14443B tag information
@struct nfc_iso14443bi_info
@brief NFC ISO14443B’ tag information
@struct nfc_iso14443biclass_info
@brief NFC ISO14443BiClass tag information
@struct nfc_jewel_info
@brief NFC Jewel tag information
@struct nfc_modulation
@brief NFC modulation structure
@struct nfc_target
@brief NFC target structure
@internal
@struct pn53x_data
@brief PN53x data structure
@internal
@struct pn53x_io
@brief PN53x I/O structure
If this option is enabled, frames that carry less than 4 bits are allowed.
According to the standards these frames should normally be handles as
invalid frames.
If the NFC device should only listen to frames, it could be useful to let
it gather multiple frames in a sequence. They will be stored in the internal
FIFO of the PN53X chip. This could be retrieved by using the receive data
functions. Note that if the chip runs out of bytes (FIFO = 64 bytes long),
it will overwrite the first received frames, so quick retrieving of the
received data is desirable.
The internal CRYPTO1 co-processor can be used to transmit messages
encrypted. This option is automatically activated after a successful MIFARE
Classic authentication.
This option can be used to enable or disable the electronic field of the
NFC device.
This option can be used to enable or disable the auto-switching mode to
ISO14443-4 is device is compliant.
In initiator mode, it means that NFC chip will send RATS automatically when
select and it will automatically poll for ISO14443-4 card when ISO14443A is
requested.
In target mode, with a NFC chip compliant (ie. PN532), the chip will
emulate a 14443-4 PICC using hardware capability
Use automatic frames encapsulation and chaining.
Force the chip to switch in ISO14443-A
Force the chip to switch in ISO14443-B
Force the chip to run at 106 kbps
Let the PN53X chip handle the CRC bytes. This means that the chip appends
the CRC bytes to the frames that are transmitted. It will parse the last
bytes from received frames as incoming CRC bytes. They will be verified
against the used modulation and protocol. If an frame is expected with
incorrect CRC bytes this option should be disabled. Example frames where
this is useful are the ATQA and UID+BCC that are transmitted without CRC
bytes during the anti-collision phase of the ISO14443-A protocol.
Parity bits in the network layer of ISO14443-A are by default generated and
validated in the PN53X chip. This is a very convenient feature. On certain
times though it is useful to get full control of the transmitted data. The
proprietary MIFARE Classic protocol uses for example custom (encrypted)
parity bits. For interoperability it is required to be completely
compatible, including the arbitrary parity bits. When this option is
disabled, the functions to communicating bits should be used.
The default configuration defines that the PN53X chip will try indefinitely
to invite a tag in the field to respond. This could be desired when it is
certain a tag will enter the field. On the other hand, when this is
uncertain, it will block the application. This option could best be compared
to the (NON)BLOCKING option used by (socket)network programming.
Timeout between ATR_REQ and ATR_RES
When the device is in initiator mode, a target is considered as mute if no
valid ATR_RES is received within this timeout value.
Default value for this property is 103 ms on PN53x based devices.
Timeout value to give up reception from the target in case of no answer.
Default value for this property is 52 ms).
Default command processing timeout
Property value’s (duration) unit is ms and 0 means no timeout (infinite).
Default value is set by driver layer
Thinfilm NFC Barcode (Not supported by PN531)
JIS X 6319-4 (Sony Felica) http://en.wikipedia.org/wiki/FeliCa
JIS X 6319-4 (Sony Felica) http://en.wikipedia.org/wiki/FeliCa
ISO14443-A (NXP MIFARE) http://en.wikipedia.org/wiki/MIFARE
ISO14443-B http://en.wikipedia.org/wiki/ISO/IEC_14443 (Not supported by PN531)
ISO14443-B http://en.wikipedia.org/wiki/ISO/IEC_14443 (Not supported by PN531 nor PN532)
ISO14443-B http://en.wikipedia.org/wiki/ISO/IEC_14443 (Not supported by PN531 nor PN532)
ISO14443-B http://en.wikipedia.org/wiki/ISO/IEC_14443 (Not supported by PN531 nor PN532)
Jewel Topaz (Innovision Research & Development) (Not supported by PN531)
Undefined modulation
Configure the PN53x to accept to be initialized only as DEP target
Configure the PN532 to accept to be initialized only as ISO/IEC14443-4 PICC
Configure the PN53x to accept all initiator mode
Configure the PN53x to accept to be initialized only in passive mode
DEP active 106 kbps
DEP active 212 kbps
DEP active 424 kbps
DEP passive 106 kbps
DEP passive 212 kbps
DEP passive 424 kbps
FeliCa 212 kbps card
FeliCa 424 kbps card
Generic passive 106 kbps (ISO/IEC14443-4A, mifare, DEP)
Generic passive 212 kbps (FeliCa, DEP)
Generic passive 424 kbps (FeliCa, DEP)
Passive 106 kbps ISO/IEC 14443-4A
Passive 106 kbps ISO/IEC14443-4B
Passive 106 kbps ISO/IEC 14443-4B with TCL flag
Innovision Jewel tag
Mifare card
Undefined target type