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 (141793 times)
  2. FAT32 Library (74938 times)
  3. Network Ethernet Library (59299 times)
  4. USB Device Library (49297 times)
  5. Network WiFi Library (45093 times)
  6. FT800 Library (44653 times)
  7. GSM click (31274 times)
  8. mikroSDK (30204 times)
  9. microSD click (27654 times)
  10. PID Library (27559 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

Smart Buck 4 Click

Rating:

0

Author: MIKROE

Last Updated: 2024-10-31

Package Version: 2.1.0.9

mikroSDK Library: 2.0.0.0

Category: Buck

Downloaded: 196 times

Not followed.

License: MIT license  

Smart Buck 4 Click is a compact add-on board that contains a high-frequency synchronous step-down DC-DC converter. This board features the LTS3562, a quad synchronous step-down DC-DC regulator from Analog Devices.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "Smart Buck 4 Click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "Smart Buck 4 Click" changes.

Do you want to report abuse regarding "Smart Buck 4 Click".

  • Information
  • Comments (0)

mikroSDK Library Blog


Smart Buck 4 Click

Smart Buck 4 Click is a compact add-on board that contains a high-frequency synchronous step-down DC-DC converter. This board features the LTS3562, a quad synchronous step-down DC-DC regulator from Analog Devices.

smartbuck4_click.png

Click Product page


Click library

  • Author : Stefan Ilic
  • Date : May 2023.
  • Type : I2C type

Software Support

We provide a library for the Smart Buck 4 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 Smart Buck 4 Click driver.

Standard key functions :

  • smartbuck4_cfg_setup Config Object Initialization function.

    void smartbuck4_cfg_setup ( smartbuck4_cfg_t *cfg );
  • smartbuck4_init Initialization function.

    err_t smartbuck4_init ( smartbuck4_t *ctx, smartbuck4_cfg_t *cfg );
  • smartbuck4_default_cfg Click Default Configuration function.

    err_t smartbuck4_default_cfg ( smartbuck4_t *ctx );

Example key functions :

  • smartbuck4_en_r40_reg Smart Buck 4 enable 400A regulator function.

    void smartbuck4_en_r40_reg ( smartbuck4_t *ctx );
  • smartbuck4_send_command Smart Buck 4 send command function.

    err_t smartbuck4_send_command ( smartbuck4_t *ctx, uint8_t addr, uint8_t data_in );
  • smartbuck4_disable_regulators Smart Buck 4 disable regulators function.

    err_t smartbuck4_disable_regulators ( smartbuck4_t *ctx );

Example Description

This example demonstrates the use of the Smart Buck 4 Click board. This driver provides functions for device configurations and for the setting of the output voltage.

The demo application is composed of two sections :

Application Init

Initialization of I2C module and log UART. After initializing the driver, the default configuration is executed and the outputs are turned off.


void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    smartbuck4_cfg_t smartbuck4_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.
    smartbuck4_cfg_setup( &smartbuck4_cfg );
    SMARTBUCK4_MAP_MIKROBUS( smartbuck4_cfg, MIKROBUS_1 );
    if ( I2C_MASTER_ERROR == smartbuck4_init( &smartbuck4, &smartbuck4_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }

    if ( SMARTBUCK4_ERROR == smartbuck4_default_cfg ( &smartbuck4 ) )
    {
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    }

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

Application Task

Changes the output voltage every 5 seconds, starting from 0.6 V to 3.3V/3.7V depending on the input voltage.


void application_task ( void ) 
{
    for ( uint8_t n_cnt = SMARTBUCK4_REGULATOR_B_600_MV; 
          n_cnt <= SMARTBUCK4_REGULATOR_B_3700_MV; 
          n_cnt += SMARTBUCK4_REGULATOR_B_700_MV )
    {
        err_t error_flag = smartbuck4_send_command( &smartbuck4, SMARTBUCK4_REG_R600B_PROGRAM | 
                                                                 SMARTBUCK4_REG_R400B_PROGRAM | 
                                                                 SMARTBUCK4_REG_LDO_MODE, 
                                                                 SMARTBUCK4_ENABLE_REGULATOR | n_cnt );
        if ( SMARTBUCK4_OK == error_flag )
        {
            log_printf( &logger, " Set output to %d mV. \r\n", 
                        ( SMARTBUCK4_MIN_VOLTAGE + n_cnt * SMARTBUCK4_STEP ) );
        }
        else
        {
            log_error( &logger, " Transmission error occurred." );
            smartbuck4_disable_regulators( &smartbuck4 );
            for ( ; ; );
        }
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
        Delay_ms ( 1000 );
    }
}

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.SmartBuck4

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.


ALSO FROM THIS AUTHOR

Matrix G Click

0

Matrix G Click is a mikroBUS add-on board with two green 5x7 matrices driven by two MAX7219 8-bit LED Display Drivers. The active area of each matrix is 7.62mm high and 5.08 mm wide. 7x5 is a standard resolution for displaying ASCII characters, so the Click is essentially a dual-character display capable of showing letters in more readable typefaces compared to a 14-segment display. The Click communicates with the target MCU through the mikroBUS SPI interface with two separate Chip Select lines for each matrix (CSL for the left, CSR for the right). This board is designed to use a 5V power supply.

[Learn More]

NFC Tag 2 click

6

NFC Tag 2 click carries the NT3H2111 NTAG I2C energy harvesting NFC Forum Type 2 Tag with field detection pin. The click is designed to run on a 3.3V power supply only. It communicates with the target MCU over I2C interface.

[Learn More]

ccRF click

0

This is a sample program which demonstrates the use of ccRF click. Programmer uses RF module for communication between two development systems. Each module can be used as transmitter and receiver.

[Learn More]