nrfxlib API 0.1.0
|
enum nfc_t4t_event_t |
#include <nfc/include/nfc_t4t_lib.h>
Enumerator | |||||||
---|---|---|---|---|---|---|---|
NFC_T4T_EVENT_NONE | This ID is never used. Dummy value for completeness. | ||||||
NFC_T4T_EVENT_FIELD_ON | External Reader polling detected. | ||||||
NFC_T4T_EVENT_FIELD_OFF | External Reader polling ended. | ||||||
NFC_T4T_EVENT_NDEF_READ | External Reader has read static NDEF-Data from Emulation. A Read operation happened on last byte of NDEF-Data. | ||||||
NFC_T4T_EVENT_NDEF_UPDATED | External Reader has written to length information of NDEF-Data from Emulation. The usual behavior of a Reader-Writer that accesses NDEF information for update is to set the length to zero at the beginning of the update process. It then writes the content of NDEF-Data. When all content is written it will update the length information inside the NDEF file. This event will be generated every time an update to the length is happening. This length information is residing in the first 2 bytes of the NDEF-Content container and is called 'NLEN'. Since this callback is triggered on any access to these bytes the returned data_length information might not be consistent (e.g. in case of only a single byte write to the length).
| ||||||
NFC_T4T_EVENT_DATA_TRANSMITTED | In Raw mode it signals that the data from nfc_t4t_response_pdu_send have been sent out. | ||||||
NFC_T4T_EVENT_DATA_IND | In Raw mode delivers the APDU fragments All NFC_T4T_EVENT_DATA_IND events that have the NFC_T4T_DI_FLAG_MORE flag set belong to the same APDU. The first NFC_T4T_EVENT_DATA_IND without NFC_T4T_DI_FLAG_MORE flag signals the completeness of the APDU. The Application then has to reply with a call to nfc_t4t_response_pdu_send. The library will handle internally the fragmentation of the response towards the Reader-Writer. The data of the response PDU must be kept valid until the next callback from the library happens (e.g. next NFC_T4T_EVENT_DATA_IND or NFC_T4T_EVENT_FIELD_OFF).
|