rtc14 2.0.0.0
Main Page

RTC 14 click

‍RTC 14 Click is a compact add-on board that measures the passage of time. This board features the ISL1221, a low-power RTC with battery-backed SRAM and event detection from Renesas. The ISL1221 tracks time with separate registers for hours, minutes, and seconds, operating in normal and battery mode. It also can timestamp an 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 calendar feature is exceptionally accurate through 2099, with automatic leap year correction.

click Product page


Click library

  • Author : Nenad Filipovic
  • Date : Aug 2021.
  • Type : I2C type

Software Support

We provide a library for the RTC14 Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.

Package can be downloaded/installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.

Library Description

‍This library contains API for RTC14 Click driver.

Standard key functions :

  • rtc14_cfg_setup Config Object Initialization function.
    void rtc14_cfg_setup(rtc14_cfg_t *cfg)
    RTC 14 configuration object setup function.
    RTC 14 Click configuration object.
    Definition rtc14.h:195
  • rtc14_init Initialization function.
    err_t rtc14_init ( rtc14_t *ctx, rtc14_cfg_t *cfg );
    err_t rtc14_init(rtc14_t *ctx, rtc14_cfg_t *cfg)
    RTC 14 initialization function.
    RTC 14 Click context object.
    Definition rtc14.h:174
  • rtc14_default_cfg Click Default Configuration function.
    err_t rtc14_default_cfg ( rtc14_t *ctx );
    err_t rtc14_default_cfg(rtc14_t *ctx)
    RTC 14 default configuration function.

Example key functions :

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.

void application_init ( void )
{
log_cfg_t log_cfg;
rtc14_cfg_t rtc14_cfg;
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.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" );
}
#define RTC14_MAP_MIKROBUS(cfg, mikrobus)
MikroBUS pin mapping.
Definition rtc14.h:159
#define RTC14_SET_HOURS_FORMAT_12
RTC 14 description setting.
Definition rtc14.h:115
#define RTC14_SET_HOURS_FORMAT_12_PM
Definition rtc14.h:118
#define RTC14_DW_THURSDAY
Definition rtc14.h:132
err_t rtc14_set_date(rtc14_t *ctx, rtc14_date_t rtc_date)
RTC 14 set date function.
void application_init(void)
Definition main.c:82

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.

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, "%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 application_task(void)
Definition main.c:134

Additional Function

  • display_day_of_week The function displays the day of the week.
    static void display_day_of_week ( void );

The full application code, and ready to use projects can be installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.

Other Mikroe Libraries used in the example:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.RTC14

Additional notes and informations

Depending on the development board you are using, you may need USB UART click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. UART terminal is available in all MikroElektronika compilers.