Intermediate
30 min

Make every moment matter with ISL1221 and ATmega328P

Counting the moments

RTC 14 Click with Arduino UNO Rev3

Published Feb 14, 2024

Click board™

RTC 14 Click

Dev Board

Arduino UNO Rev3

Compiler

NECTO Studio

MCU

ATmega328P

Take advantage of this cutting-edge real-time clock technology to achieve precise timing synchronization in your applications

A

A

Hardware Overview

How does it work?

RTC 14 Click is based on the ISL1221, a small micropower real-time clock that provides increased security features and tamper detection from Renesas. This device has time-stamp features in normal and battery modes, timing and crystal compensation, clock/calendar, power fail indicator, periodic or polled alarm, intelligent battery backup switching, and battery-backed user SRAM. With their enhanced security functionality, this RTC is ideally suited for various applications ranging from security, warranty monitoring, data collection, recording, and time-stamping single events, for example, recurring events such as the opening and closing of a security door. As mentioned before, the ISL1221 can time-stamp an external event by either issuing an output signal containing the second, minute, hour, date, month, and year that the triggering event occurred or by stopping the RTC registers from advancing at the moment the event occurs. The device also has

calendar registers for a date, month, year, and day of the week, which is exceptionally accurate through 2099, with automatic leap year correction. The alarm can be set to any clock/calendar value (for example, every minute, every Friday, or at 9:41 AM on September 10). The alarm status is available by checking the Status Register or at the hardware interrupt pin routed to the INT pin of the mikroBUS™ socket. The alarm also contains a repeat mode, allowing a periodic interrupt every minute, every hour, and every day. RTC 14 Click communicates with MCU using the standard I2C 2-Wire interface to read data and configure settings, supporting a Fast Mode operation up to 400kHz. Also, it has a frequency output programmable from 32.768kHz to 1/32Hz, available at the PWM pin of the mikroBUS™ socket and onboard header pin labeled as FO. This feature is used for various timing applications, including clocking the MCU in sleep mode, eliminating

external crystal, and further reducing the BOM. To use features such as external event input or frequency output available on onboard headers, it is necessary to populate the resistors R8 and R9 and thus activate these functions on the headers. Like this one, the most common RTC configuration is a battery-backed up, which maintains time and may hold data in 2 bytes of battery-backed SRAM provided for data storage. That’s why, besides the ISL1221, the RTC 14 Click has a button cell battery holder compatible with the 3000TR battery holder, suitable for 12mm Coin Cell batteries. 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.

RTC 14 Click hardware overview image

Features overview

Development board

Arduino UNO is a versatile microcontroller board built around the ATmega328P chip. It offers extensive connectivity options for various projects, featuring 14 digital input/output pins, six of which are PWM-capable, along with six analog inputs. Its core components include a 16MHz ceramic resonator, a USB connection, a power jack, an

ICSP header, and a reset button, providing everything necessary to power and program the board. The Uno is ready to go, whether connected to a computer via USB or powered by an AC-to-DC adapter or battery. As the first USB Arduino board, it serves as the benchmark for the Arduino platform, with "Uno" symbolizing its status as the

first in a series. This name choice, meaning "one" in Italian, commemorates the launch of Arduino Software (IDE) 1.0. Initially introduced alongside version 1.0 of the Arduino Software (IDE), the Uno has since become the foundational model for subsequent Arduino releases, embodying the platform's evolution.

Arduino UNO Rev3 double side image

Microcontroller Overview

MCU Card / MCU

default

Architecture

AVR

MCU Memory (KB)

32

Silicon Vendor

Microchip

Pin count

28

RAM (Bytes)

2048

You complete me!

Accessories

Click Shield for Arduino UNO has two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the Arduino UNO board without effort. The Arduino Uno, a microcontroller board based on the ATmega328P, provides an affordable and flexible way for users to try out new concepts and build prototypes with the ATmega328P microcontroller from various combinations of performance, power consumption, and features. The Arduino Uno has 14 digital input/output pins (of which six can be used as PWM outputs), six analog inputs, a 16 MHz ceramic resonator (CSTCE16M0V53-R0), a USB connection, a power jack, an ICSP header, and reset button. Most of the ATmega328P microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the Arduino UNO board with our Click Shield for Arduino UNO, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.

Click Shield for Arduino UNO accessories 1 image

Used MCU Pins

mikroBUS™ mapper

Frequency Output
PC0
AN
NC
NC
RST
NC
NC
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
Event Input
PD6
PWM
Interrupt
PC3
INT
NC
NC
TX
NC
NC
RX
I2C Clock
PC5
SCL
I2C Data
PC4
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

RTC 14 Click Schematic schematic

Step by step

Project assembly

Click Shield for Arduino UNO front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Arduino UNO Rev3 as your development board.

Click Shield for Arduino UNO front image hardware assembly
Arduino UNO Rev3 front image hardware assembly
Barometer 13 Click front image hardware assembly
Prog-cut hardware assembly
Arduino UNO Rev3 MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Arduino UNO MCU Step hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

Track your results in real time

Application Output

After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.

Application Output Step 1

After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.

Application Output Step 3

Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.

Application Output Step 4

Software Support

Library Description

This library contains API for RTC 14 Click driver.

Key functions:

  • rtc14_get_time - RTC 14 get time function

  • rtc14_set_time - RTC 14 set time function

  • rtc14_get_date - RTC 14 get date function

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 main.c
 * @brief RTC14 Click example
 *
 * # Description
 * This is an example that demonstrates the use of the RTC 14 click board™.
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initialization of I2C module, log UART and additional pins.
 * After driver initialization and default settings,
 * the app set the time to 11:59:50 PM ( 12-hour format ) 
 * and set date to Thursday 05.08.2021.
 *
 * ## Application Task
 * This is an example that shows the use of a RTC 14 click board™.
 * In this example, we read and display the current time ( AM or PM ) 
 * and date ( day of the week ), which we also previously set.
 * Results are being sent to the Usart Terminal where you can track their changes.
 * All data logs write on USB changes every 1 sec.
 *
 * ## Additional Function
 * - static void display_day_of_week ( void ) - The function displays the day of the week.
 *
 * @author Nenad Filipovic
 *
 */

#include "board.h"
#include "log.h"
#include "rtc14.h"

static rtc14_t rtc14;
static log_t logger;
static uint8_t new_sec = 255;
static rtc14_time_t time;
static rtc14_date_t date;

static void display_day_of_week ( void ) 
{
    switch ( date.day_of_week ) 
    {
        case RTC14_DW_SUNDAY: 
        {
            log_printf( &logger, "Su\r\n" );
            break;
        }
        case RTC14_DW_MONDAY: 
        {
            log_printf( &logger, "Mo\r\n" );
            break;
        }
        case RTC14_DW_TUESDAY: 
        {
            log_printf( &logger, "Tu\r\n" );
            break;
        }
        case RTC14_DW_WEDNESDAY: 
        {
            log_printf( &logger, "We\r\n" );
            break;
        }
        case RTC14_DW_THURSDAY: 
        {
            log_printf( &logger, "Th\r\n" );
            break;
        }
        case RTC14_DW_FRIDAY: 
        {
            log_printf( &logger, "Fr\r\n" );
            break;
        }
        case RTC14_DW_SATURDAY: 
        {
            log_printf( &logger, "Sa\r\n" );
            break;
        }
    }
}

void application_init ( void ) 
{
    log_cfg_t log_cfg;      /**< Logger config object. */
    rtc14_cfg_t rtc14_cfg;  /**< Click config object. */

    /** 
     * 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 " );

    // Click initialization.
    rtc14_cfg_setup( &rtc14_cfg );
    RTC14_MAP_MIKROBUS( rtc14_cfg, MIKROBUS_1 );
    err_t init_flag = rtc14_init( &rtc14, &rtc14_cfg );
    if ( I2C_MASTER_ERROR == init_flag ) 
    {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );
    }

    rtc14_default_cfg ( &rtc14 );
    Delay_ms( 100 );
    
    time.hours_format = RTC14_SET_HOURS_FORMAT_12;
    time.am_pm = RTC14_SET_HOURS_FORMAT_12_PM;
    time.hours = 11;
    time.min = 59;
    time.sec = 50;
    rtc14_set_time( &rtc14, time );
    Delay_ms( 100 );
    
    date.day_of_week = RTC14_DW_THURSDAY;
    date.day = 5;
    date.month = 8;
    date.year = 21;
    rtc14_set_date( &rtc14, date );
    Delay_ms( 100 );
    
    log_info( &logger, " Application Task " );
    log_printf( &logger, "- - - - - - - - - - -\r\n" );
}

void application_task ( void ) 
{    
    rtc14_get_time( &rtc14, &time );
    Delay_ms( 1 );
    rtc14_get_date( &rtc14, &date );
    Delay_ms( 1 );
    
    if ( time.sec != new_sec ) 
    {       
        log_printf( &logger, "  Date : %.2d-%.2d-%.2d ", ( uint16_t ) date.day, ( uint16_t ) date.month, ( uint16_t ) date.year );
        display_day_of_week( );
        log_printf( &logger, "  Time : %.2d:%.2d:%.2d ", ( uint16_t ) time.hours, ( uint16_t ) time.min, ( uint16_t ) time.sec );
        log_printf( &logger, "%cM\r\n", ( time.am_pm == RTC14_SET_HOURS_FORMAT_12_PM ? 'P' : 'A' ) );
        log_printf( &logger, "- - - - - - - - - - -\r\n" );
        new_sec = time.sec;
        Delay_ms( 1 );
    }
}

void main ( void ) 
{
    application_init( );

    for ( ; ; ) 
    {
        application_task( );
    }
}

// ------------------------------------------------------------------------ END

Additional Support

Resources

Love this project?

'Buy This Kit' button takes you directly to the shopping cart where you can easily add or remove products.