NFC 5 Click
NFC 5 Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.
Click Library
- Author : Stefan Filipovic
- Date : Nov 2023.
- Type : I2C/SPI type
Software Support
Example Description
This example demonstrates the use of NFC 4 Click board by reading MIFARE ISO/IEC 14443 type A tag UID.
Example Libraries
- MikroSDK.Board
- MikroSDK.Log
- Click.NFC5
Example Key Functions
- nfc5_cfg_setup Config Object Initialization function.
void nfc5_cfg_setup(nfc5_cfg_t *cfg)
NFC 5 configuration object setup function.
NFC 5 Click configuration object.
Definition nfc5.h:1135
- nfc5_init Initialization function.
err_t nfc5_init(nfc5_t *ctx, nfc5_cfg_t *cfg)
NFC 5 initialization function.
struct nfc5_s nfc5_t
NFC 5 Click context object.
- nfc5_default_cfg Click Default Configuration function.
err_t nfc5_default_cfg(nfc5_t *ctx)
NFC 5 default configuration function.
- nfc5_get_mifare_tag_uid This function reads the UID of a mifare tag.
err_t nfc5_get_mifare_tag_uid(nfc5_t *ctx, uint8_t *uid, uint8_t *uid_len)
NFC 5 get mifare tag UID function.
- nfc5_write_reg This function writes a desired data to the selected register.
err_t nfc5_write_reg(nfc5_t *ctx, uint8_t reg, uint8_t data_in)
NFC 5 write register function.
- nfc5_read_reg This function reads a desired data from the selected register.
err_t nfc5_read_reg(nfc5_t *ctx, uint8_t reg, uint8_t *data_out)
NFC 5 read register function.
Application Init
Initializes the driver and performs the Click default configuration.
{
log_cfg_t log_cfg;
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, " Application Init " );
err_t init_flag =
nfc5_init( &nfc5, &nfc5_cfg );
if ( ( I2C_MASTER_ERROR == init_flag ) || ( SPI_MASTER_ERROR == init_flag ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
#define NFC5_MAP_MIKROBUS(cfg, mikrobus)
MikroBUS pin mapping.
Definition nfc5.h:824
void application_init(void)
Definition main.c:32
@ NFC5_ERROR
Definition nfc5.h:1162
Application Task
If there's a tag detected, it reads its UID and displays it on the USB UART every 500ms.
{
uint8_t tag_uid_len = 0;
{
log_printf( &logger, " TAG UID: " );
for ( uint8_t cnt = 0; cnt < tag_uid_len; cnt++ )
{
log_printf( &logger, "0x%.2X ", ( uint16_t ) tag_uid[ cnt ] );
}
log_printf( &logger, "\r\n----------------------------------\r\n" );
Delay_ms ( 500 );
}
}
#define NFC5_NFCA_CASCADE_3_UID_LEN
Definition nfc5.h:377
void application_task(void)
Definition main.c:69
@ NFC5_OK
Definition nfc5.h:1161
Note
Only ISO14443-A type tags are compatible with this example. We recommend MIKROE-1475 - an RFiD tag 13.56MHz compliant with ISO14443-A standard.
Application Output
This Click board can be interfaced and monitored in two ways:
- Application Output - Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
- UART Terminal - Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Additional Notes and Information
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.