Create smarter and more interactive digital experiences with ST25DV16K and MSP432P401R
Touch and transform: NFC readers reshaping your digital landscape
Published Oct 18, 2023
Click board™
NFC Tag 4 Click
Dev Board
Fusion for Tiva v8
Compiler
NECTO Studio
MCU
MSP432P401R
Embrace the NFC experience and see how it extends from simple data sharing to device control, offering a more connected and efficient way of interacting with your digital world
A
A
Hardware Overview
How does it work?
NFC Tag 4 Click is based on the ST25DV16, a compact NFC tag IC from STMicroelectronics. The Click board™ itself has a reasonably small number of components because most of the interface and EEPROM memory circuitry is already integrated on the ST25DV16K IC. The I2C / SMBus compatible serial interface lines, along with the GPO pin, which also works in the open drain configuration, are pulled up by the onboard resistors. The 2-Wire lines are routed to the respective I2C lines of the mikroBUS™ (SCK and SDA), while the GPO pin of the main IC is routed to the INT pin of the mikroBUS™. The ST25DV16K uses the I2C/SMBus compatible communication interface, offering a fast transfer mode (FTM), to achieve a fast link between RF and contact worlds, via a 256 byte buffer called Mailbox. This mailbox dynamic buffer of 256 byte can be filled or emptied via either RF or I2C. There is also the INT pin available, which
indicates incoming event to the contact side, like RF Field changes, RF activity in progress, RF writing completion or Mailbox message availability. The built in energy harvesting element can deliver µW of power when external conditions make it possible. The integrated RF management allows the NFC Tag 4 click to ignore RF requests. All these features can be programmed by setting static and/or dynamic registers of the ST25DV16K. ST25DVxxx can be partially customized using configuration registers located in the E2 system area. More information about all the registers can be found in the ST25DV16K datasheet. However, provided library contains functions that simplify the use of the NFC Tag 4 click. The included application example demonstrates their functionality and it can be used as a reference for custom design. In order to make sure that no external components are required in order to use
it, this Click Board™ contains the integrated trace antenna on the PCB. The antenna coil is correctly tuned and can be used to power and access the device using the ISO/IEC 15693 and ISO 18000-3 mode 1 protocols. Power is transferred to the ST25DV16K by radio frequency at 13.56 MHz via coupling antennas of the NFC Tag 4 click and the NFC Reader being used. The ISO 15693 standard defines the carrier frequency (fC) of the operating field as 13.56 MHz ±7 kHz. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used as a reference for further development.
Features overview
Development board
Fusion for TIVA v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different 32-bit ARM® Cortex®-M based MCUs from Texas Instruments, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over a WiFi network. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for TIVA v8 provides a fluid and immersive working experience, allowing access
anywhere and under any circumstances at any time. Each part of the Fusion for TIVA v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector.
Communication options such as USB-UART, USB HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. Fusion for TIVA v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
256
Silicon Vendor
Texas Instruments
Pin count
100
RAM (Bytes)
65536
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Fusion for Tiva v8 as your development board.
Track your results in real time
Application Output via UART Mode
1. Once the code example is loaded, pressing the "FLASH" button initiates the build process, and programs it on the created setup.
2. After the programming is completed, click on the Tools icon in the upper-right panel, and select the UART Terminal.
3. After opening the UART Terminal tab, first check the baud rate setting in the Options menu (default is 115200). If this parameter is correct, activate the terminal by clicking the "CONNECT" button.
4. Now terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
Software Support
Library Description
This library contains API for NFC Tag 4 Click driver.
Key functions:
nfctag4_password_present- This function presents password to device in order to open I2C security sessionnfctag4_enable_mailbox- This function enables or disables mailbox functionalitynfctag4_enable_rf- This function enables or disables RF functionality
Open Source
Code example
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* \file
* \brief NfcTag4 Click example
*
* # Description
* This example showcases how to configure and use the NFC Tag 4 click. The click is an NFC tag
* interface which uses the I2C serial interface and an RF link interface in order to communicate.
* The example requires the ST25 NFC Tap application which can be downloaded to your phone.
*
* The demo application is composed of two sections :
*
* ## Application Init
* This function initializes and configures the logger and click modules.
*
* ## Application Task
* This function waits for the interrupt signal, after which it expects data transfers. Once
* some data has been detected it will open a communication channel with the device transmitting
* it and show the received data in the UART console.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "nfctag4.h"
// ------------------------------------------------------------------ VARIABLES
static nfctag4_t nfctag4;
static log_t logger;
static uint8_t aux_buffer[ 258 ];
static uint16_t i;
static uint16_t message_length = 0;
static transfer_info info;
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
void nfctag4_wait_for_int ()
{
uint16_t timer_counter = 0;
uint8_t int_pin_flag = 0;
int_pin_flag = nfctag4_int_get( &nfctag4 );
while ( ( int_pin_flag == 1 ) && ( timer_counter <= 300 ) )
{
Delay_ms( 1 );
timer_counter++;
int_pin_flag = nfctag4_int_get( &nfctag4 );
}
if ( timer_counter <= 300 )
{
int_pin_flag = nfctag4_int_get( &nfctag4 );
while ( int_pin_flag == 0 )
{
int_pin_flag = nfctag4_int_get( &nfctag4 );
}
}
timer_counter = 0;
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
nfctag4_cfg_t cfg;
/**
* Logger initialization.
* Default baud rate: 115200
* Default log level: LOG_LEVEL_DEBUG
* @note If USB_UART_RX and USB_UART_TX
* are defined as HAL_PIN_NC, you will
* need to define them manually for log to work.
* See @b LOG_MAP_USB_UART macro definition for detailed explanation.
*/
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, "---- Application Init ----" );
nfctag4_cfg_setup( &cfg );
NFCTAG4_MAP_MIKROBUS( cfg, MIKROBUS_1 );
nfctag4_init( &nfctag4, &cfg );
nfctag4_default_cfg( &nfctag4 );
}
void application_task ( void )
{
nfctag4_wait_for_int( );
info.memory_area = NFCTAG4_MEMORY_DYNAMIC;
info.register_address = NFCTAG4_DYNAMIC_REG_MB_CTRL;
info.n_registers = 1;
nfctag4_i2c_get( &nfctag4, &info, aux_buffer );
if ( ( aux_buffer[ 0 ] & 0x04 ) == ( 0x04 ) )
{
nfctag4_wait_for_int( );
info.memory_area = NFCTAG4_MEMORY_DYNAMIC;
info.register_address = NFCTAG4_DYNAMIC_REG_MB_LEN;
info.n_registers = 1;
nfctag4_i2c_get( &nfctag4, &info, aux_buffer );
message_length = aux_buffer[ 0 ];
message_length++;
nfctag4_wait_for_int( );
info.memory_area = NFCTAG4_MEMORY_MAILBOX;
info.register_address = NFCTAG4_MAILBOX_REG_BYTE_0;
info.n_registers = message_length;
nfctag4_i2c_get( &nfctag4, &info, aux_buffer );
log_printf( &logger, "************* MESSAGE ***************\r\n" );
log_printf( &logger, " ** Message length: %u Bytes**\r\n", message_length );
for ( i = 0; i < message_length; i++ )
{
log_printf( &logger, " %u : 0x%x\r\n", i, ( uint16_t ) aux_buffer[ i ] );
}
log_printf( &logger, "************** END ****************\r\n" );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
