RTC 22 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.
- Author : Stefan Filipovic
- Date : Jun 2024.
- Type : I2C type
This example demonstrates the use of RTC 22 Click board by reading and displaying the time and date values.
- MikroSDK.Board
- MikroSDK.Log
- Click.RTC22
rtc22_cfg_setupConfig Object Initialization function.
void rtc22_cfg_setup ( rtc22_cfg_t *cfg );rtc22_initInitialization function.
err_t rtc22_init ( rtc22_t *ctx, rtc22_cfg_t *cfg );rtc22_set_timeThis function sets the starting time values - second 100th, second, minute and hour.
err_t rtc22_set_time ( rtc22_t *ctx, rtc22_time_t *time );rtc22_read_timeThis function reads the current time values - second 100th, second, minute and hour.
err_t rtc22_read_time ( rtc22_t *ctx, rtc22_time_t *time );rtc22_set_dateThis function sets the starting date values - day of week, day, month and year.
err_t rtc22_set_date ( rtc22_t *ctx, rtc22_date_t *date );Initializes the driver, checks the communication, and sets the starting time and date.
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
rtc22_cfg_t rtc22_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.
rtc22_cfg_setup( &rtc22_cfg );
RTC22_MAP_MIKROBUS( rtc22_cfg, MIKROBUS_POSITION_RTC22 );
if ( I2C_MASTER_ERROR == rtc22_init( &rtc22, &rtc22_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( RTC22_ERROR == rtc22_check_communication ( &rtc22 ) )
{
log_error( &logger, " Check communication." );
for ( ; ; );
}
time.hour = 23;
time.minute = 59;
time.second = 50;
time.second_100th = 0;
if ( RTC22_OK == rtc22_set_time ( &rtc22, &time ) )
{
log_printf( &logger, " Set time: %.2u:%.2u:%.2u\r\n",
( uint16_t ) time.hour, ( uint16_t ) time.minute, ( uint16_t ) time.second );
}
date.day_of_week = RTC22_TUESDAY;
date.day = 31;
date.month = 12;
date.year = 24;
if ( RTC22_OK == rtc22_set_date ( &rtc22, &date ) )
{
log_printf( &logger, " Set date: %s, %.2u.%.2u.20%.2u.\r\n",
rtc22_get_day_of_week_name ( date.day_of_week ),
( uint16_t ) date.day, ( uint16_t ) date.month, ( uint16_t ) date.year );
}
Delay_ms ( 100 );
log_info( &logger, " Application Task " );
}Reads and displays on the USB UART the current time and date values once per second.
void application_task ( void )
{
if ( RTC22_OK == rtc22_read_time ( &rtc22, &time ) )
{
log_printf( &logger, " Time: %.2u:%.2u:%.2u\r\n",
( uint16_t ) time.hour, ( uint16_t ) time.minute, ( uint16_t ) time.second );
}
if ( RTC22_OK == rtc22_read_date ( &rtc22, &date ) )
{
log_printf( &logger, " Date: %s, %.2u.%.2u.20%.2u.\r\n",
rtc22_get_day_of_week_name ( date.day_of_week ),
( uint16_t ) date.day, ( uint16_t ) date.month, ( uint16_t ) date.year );
}
Delay_ms ( 1000 );
}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.
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.