Incorporate a high-performance real-time clock into your solution and boost your timing control
A
A
Hardware Overview
How does it work?
RTC 3 Click is based on the BQ32000, a real-time clock from Texas Instruments presenting a compatible replacement for industry standard real-time clocks. The BQ32000 features an automatic backup supply with an integrated trickle charger for an automatic switchover to a backup power supply providing additional reliability (the circuit maintains the backup charge with an onboard supercapacitor). It also comes with a programmable calibration adjustment from –63ppm to +126ppm and clock frequency derived from an onboard 32.768KHz oscillator. The BQ32000 communicates with the MCU using the standard I2C 2-Wire interface with a maximum
frequency of 400kHz. Its time registers are updated once per second, with registers updated simultaneously to prevent a time-keeping glitch. It should be noted that when the BQ32000 switches from the main power supply to the backup supply, the time-keeping register cannot be accessed via the I2C interface. The access to these registers is only with supply voltage present. The time-keeping registers can take up to one second to update after the device switches from the backup power supply to the main power supply. The BQ32000 also includes an automatic leap year correction and general interrupt or oscillator fail flag indicating the status of the RTC oscillator
routed to the INT pin of the mikroBUS™ socket. The RTC classifies a leap year as any year evenly divisible by 4. Using this rule allows for reliable leap-year compensation until 2100. The host MCU must compensate for years that fall outside this rule. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
Flip&Click PIC32MZ is a compact development board designed as a complete solution that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit PIC32MZ microcontroller, the PIC32MZ2048EFH100 from Microchip, four mikroBUS™ sockets for Click board™ connectivity, two USB connectors, LED indicators, buttons, debugger/programmer connectors, and two headers compatible with Arduino-UNO pinout. Thanks to innovative manufacturing technology,
it allows you to build gadgets with unique functionalities and features quickly. Each part of the Flip&Click PIC32MZ development kit contains the components necessary for the most efficient operation of the same board. In addition, there is the possibility of choosing the Flip&Click PIC32MZ programming method, using the chipKIT bootloader (Arduino-style development environment) or our USB HID bootloader using mikroC, mikroBasic, and mikroPascal for PIC32. This kit includes a clean and regulated power supply block through the USB Type-C (USB-C) connector. All communication
methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, user-configurable buttons, and LED indicators. Flip&Click PIC32MZ development kit allows you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping 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
Architecture
PIC32
MCU Memory (KB)
2048
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
524288
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Track your results in real time
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.
Software Support
Library Description
This library contains API for RTC 3 Click driver.
Key functions:
rtc3_set_time
- Function sets time: hours, minutes and seconds data to the target register address of PCF8583 chip on RTC 3 Clickrtc3_get_time
- Function gets time: hours, minutes and seconds data from the target register address of PCF8583 chip on RTC 3 Clickrtc3_set_calibration
- Function set calibration by write CAL_CFG1 register of BQ32000 chip
Open Source
Code example
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.
/*!
* \file
* \brief Rtc3 Click example
*
* # Description
* This application enables time measurment over RTC3 click.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enable's - I2C,
* set start time and date, enable counting and start write log.
*
* ## Application Task
* This is a example which demonstrates the use of RTC 3 Click board.
* RTC 3 Click communicates with register via I2C by write to register and read from register,
* set time and date, get time and date, enable and disable counting
* and set frequency by write configuration register.
* Results are being sent to the Usart Terminal where you can track their changes.
* All data logs write on usb uart changes for every 1 sec.
*
* *note:*
* Time stats measuring correctly but from 0 seconds, after 10 seconds.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "rtc3.h"
// ------------------------------------------------------------------ VARIABLES
static rtc3_t rtc3;
static log_t logger;
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
void display_log_day_of_the_week ( uint8_t day_of_the_week )
{
if ( day_of_the_week == 1 )
{
log_printf( &logger, " Monday \r\n" );
}
if ( day_of_the_week == 2 )
{
log_printf( &logger, " Tuesday \r\n" );
}
if ( day_of_the_week == 3 )
{
log_printf( &logger, " Wednesday \r\n" );
}
if ( day_of_the_week == 4 )
{
log_printf( &logger, " Thursday \r\n" );
}
if ( day_of_the_week == 5 )
{
log_printf( &logger, " Friday \r\n" );
}
if ( day_of_the_week == 6 )
{
log_printf( &logger, " Saturday \r\n" );
}
if ( day_of_the_week == 7 )
{
log_printf( &logger, " Sunday \r\n" );
}
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
rtc3_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 ----" );
// Click initialization.
rtc3_cfg_setup( &cfg );
RTC3_MAP_MIKROBUS( cfg, MIKROBUS_1 );
rtc3_init( &rtc3, &cfg );
/// Set Time: 23h, 59 min, 50 sec
rtc3.time.time_hours = 23;
rtc3.time.time_minutes = 59;
rtc3.time.time_seconds = 50;
rtc3_set_time( &rtc3 );
// Set Date: 1 ( Day of the week ), 31 ( day ), 12 ( month ) and 2018 ( year )
rtc3.date.day_of_the_week = 1;
rtc3.date.date_day = 31;
rtc3.date.date_month = 12;
rtc3.date.date_year = 2018;
rtc3_set_date( &rtc3 );
// Start counting
rtc3_enable_disable_counting( &rtc3, 1 );
Delay_100ms( );
Delay_ms( 1000 );
}
void application_task ( void )
{
// Task implementation.
uint8_t time_seconds_new = 0xFF;
rtc3_get_time( &rtc3 );
rtc3_get_date( &rtc3 );
if ( time_seconds_new != rtc3.time.time_seconds )
{
if ( ( ( rtc3.time.time_hours | rtc3.time.time_minutes | rtc3.time.time_seconds ) == 0 ) && ( ( rtc3.date.date_day | rtc3.date.date_month ) == 1 ) )
{
log_printf( &logger, " Happy New Year \r\n" );
log_printf( &logger, "------------------\r\n" );
}
log_printf( &logger, " Time : %d:%d:%d \r\n Date: %d.%d.20%d.\r\n------------------\r\n", (uint16_t)rtc3.time.time_hours, (uint16_t)rtc3.time.time_minutes,
(uint16_t)rtc3.time.time_seconds,
(uint16_t)rtc3.date.date_day, (uint16_t)rtc3.date.date_month, (uint16_t)rtc3.date.date_year );
time_seconds_new = rtc3.time.time_seconds;
}
Delay_ms( 200 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END