TOP Contributors

  1. MIKROE (2784 codes)
  2. Alcides Ramos (405 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (133 codes)
  5. Bugz Bensce (97 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (141629 times)
  2. FAT32 Library (74655 times)
  3. Network Ethernet Library (59128 times)
  4. USB Device Library (49167 times)
  5. Network WiFi Library (44926 times)
  6. FT800 Library (44461 times)
  7. GSM click (31122 times)
  8. mikroSDK (30037 times)
  9. microSD click (27531 times)
  10. PID Library (27512 times)
Libstock prefers package manager

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back
mikroSDK Library

RTC Click

Rating:

0

Author: MIKROE

Last Updated: 2024-10-31

Package Version: 2.1.0.6

mikroSDK Library: 2.0.0.0

Category: RTC

Downloaded: 194 times

Not followed.

License: MIT license  

RTC Click is an accessory board in mikroBus™ form factor. It features the PCF8583 serial real-time clock (RTC)

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "RTC Click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "RTC Click" changes.

Do you want to report abuse regarding "RTC Click".

  • Information
  • Comments (0)

mikroSDK Library Blog


RTC Click

RTC Click is an accessory board in mikroBus™ form factor. It features the PCF8583 serial real-time clock (RTC).

rtc_click.png

Click Product page


Click library

  • Author : MikroE Team
  • Date : jan 2020.
  • Type : I2C type

Software Support

We provide a library for the Rtc 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 form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.

Library Description

This library contains API for Rtc Click driver.

Standard key functions :

  • rtc_c_cfg_setup Config Object Initialization function.

    void rtc_c_cfg_setup ( rtc_c_cfg_t *cfg ); 
  • rtc_c_init Initialization function.

    err_t rtc_c_init ( rtc_c_t *ctx, rtc_c_cfg_t *cfg );

Example key functions :

  • rtc_c_set_time Function sets time: hours, minutes and seconds data to the target register address of PCF8583 chip on RTC Click.

    void rtc_c_set_time ( rtc_c_t *ctx );
  • rtc_c_get_time Function gets time: hours, minutes and seconds data from the target register address of PCF8583 chip on RTC Click.

    void rtc_c_get_time ( rtc_c_t *ctx );
  • rtc_c_enable_disable_counting Function that enables or disables counting on RTC Click.

    void rtc_c_enable_disable_counting ( rtc_c_t *ctx, uint8_t en_dis );

Example Description

This application enables setup and measurement of time with RTC Click.

The demo application is composed of two sections :

Application Init

Initialization driver enable's - I2C, set start time, enable counting and start write log.


void application_init ( void )
{
    log_cfg_t log_cfg;
    rtc_c_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.
    rtc_c_cfg_setup( &cfg );
    RTC_C_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    rtc_c_init( &rtc_c, &cfg );

    log_printf( &logger, "------------------\r\n" );
    log_printf( &logger, "     RTC Click    \r\n" );
    log_printf( &logger, "------------------\r\n" );

    // Set Time: 23h, 59 min, 50 sec and 10 ms
    rtc_c.time.time_hours = 23;
    rtc_c.time.time_minutes = 59;
    rtc_c.time.time_seconds = 50;
    rtc_c.time.time_hun_sec = 10;

    rtc_c_set_time( &rtc_c );
    Delay_100ms( );

    // Start counting
    rtc_c_enable_disable_counting( &rtc_c, 1 );
    Delay_100ms( );

    log_info( &logger, " Application Task " );
}

Application Task

This is an example which demonstrates the use of RTC Click board. RTC Click communicates with register via I2C by write to register and read from register. This example show time when the value of time_seconds is changed. 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.


void application_task ( void )
{
    static uint8_t time_seconds_new = 0xFF;

    rtc_c_get_time( &rtc_c );

    if ( time_seconds_new != rtc_c.time.time_seconds )
    {
        log_printf( &logger, " Time : %.2u:%.2u:%.2u\r\n", 
                    ( uint16_t ) rtc_c.time.time_hours, 
                    ( uint16_t ) rtc_c.time.time_minutes, 
                    ( uint16_t ) rtc_c.time.time_seconds );

        log_printf( &logger, "------------------\r\n" );

        time_seconds_new = rtc_c.time.time_seconds;
    }

    Delay_ms ( 500 );
} 

The full application code, and ready to use projects can be installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.

Other mikroE Libraries used in the example:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.Rtc

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. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.


ALSO FROM THIS AUTHOR

GNSS 10 Click

0

GNSS 10 Click is a compact add-on board that provides fast positioning capability. This board features the NEO-M8J, a standard precision GNSS module built on the high-performing M8 GNSS engine in the industry-proven NEO form factor from u-blox. This module utilizes concurrent reception of up to three GNSS systems (GPS/Galileo together with BeiDou or GLONASS), recognizes multiple constellations simultaneously, and provides outstanding positioning accuracy in scenarios where urban canyon or weak signals are involved. It supports all satellite augmentation systems for even better and faster positioning improvement, comes with a configurable host interface, and advanced jamming and spoofing detection. This Click board™ is ideally suited for industrial and automotive applications.

[Learn More]

Button G Click

0

Button G Click is the simplest solution for adding a single pushbutton to your design. The button itself is transparent, 6.8mm in diameter and has a green LED backlight. When pressed, it sends an interrupt signal to the target board microcontroller. The backlight LED is controlled separately through the mikroBUS PWM pin, so you can program all kinds of patterns (varying level of light intensity or rate of blinking on subsequent button presses). The board can use either a 3.3V or a 5V power supply.

[Learn More]

Mikromedia+ for STM32 ARM - RF Communication Example

5

This is demonstration project how Mikromedia+ for STM communicate over RF. Data is send over simple 'led protocol' (1 byte command). Development board for STM32 with an add-on board nRF Click is used as a receiver device.

[Learn More]