Your power, your rules - our Buck-Boost combo empowers you to take charge like never before.
A
A
Hardware Overview
How does it work?
Buck-Boost Click is based on the LTC3129-1, a 1.3μA quiescent current, monolithic, current mode, buck-boost DC/DC converter that can operate over a wide input voltage range of 1.92V to 15V and provide up to 200mA to the load from Analog Devices. The LTC3129-1 is characterized by its low noise and ripple level at the output, high regulating efficiency, and low quiescent current. Eight fixed, user-programmable output voltages can be selected using the three digital programming pins routed to the INT, AN, and CS pins of the mikroBUS™ socket. A proprietary switch control algorithm allows the Buck-Boost converter to regulate output voltage with input voltages above, below, or equal to the output voltage. Transitions between the step-up or step-down operating modes are seamless and free of transients and sub-harmonic switching, making
this product ideal for noise-sensitive applications. Buck-Boost Click possesses two different modes of operation - PWM and Burst Mode, depending on the nature of the application. The PWM mode can be selected by setting the PWM pin of the mikroBUS™ socket to a logic high level and is suitable for working with higher loads connected to the converter output and when extremely low output noise is required. When selecting the PWM mode, LTC3129-1 has a fixed nominal switching frequency of 1.2MHz using an internally compensated average current mode control loop. In this mode, the output voltage's ripple and noise level are minimal. For high-efficiency operation at light loads, automatic Burst Mode operation can be selected, reducing the quiescent current to 1.3µA. Burst mode can be chosen if the PWM pin is set to a logic low level. If the connected load is
light enough, the converter will remain working in Burst mode, running only when necessary to maintain voltage regulation. Otherwise, the PWM mode will automatically engage, providing enough current for the connected load. This Click board™ completely powers itself from the VIN external power supply terminal. Once the power is applied to the VIN terminal, the circuit must also be enabled by setting the RUN pin routed to the RST pin of the mikroBUS™ socket to a high logic level. This will power up the converter, which the PWR LED indicator will indicate. It also includes additional features such as a power-good output with a Power Good LED indicator labeled PGOOD that pulls to the ground when FB drops too far below its regulated voltage. This pin also can sink up to the absolute maximum rating of 15mA when set low.
Features overview
Development board
Nucleo-64 with STM32F091RC MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU

Architecture
ARM Cortex-M0
MCU Memory (KB)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
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
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.

2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.

3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.

Software Support
Library Description
This library contains API for Buck-Boost Click driver.
Key functions:
buckboost_set_mode_fixed_freq
- This function set fixed frequency PWM operation mode of LTC3129-1buckboost_enables_auto_burst_mode
- This function enables automatic burst mode operation of LTC3129-1buckboost_set_2500mv
- This function set the output voltage of 2500mV
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 Buck-Boost Click example
*
* # Description
* The demo application change output voltage from 2500 mV to 15000 mV every 5 seconds.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization device and set default configuration.
*
* ## Application Task
* This is a example which demonstrates the use of Buck Boost Click board.
* Change output voltage from 2500 mV to 15000 mV every 5 seconds.
* All data logs write on usb uart for aproximetly every 5 sec.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "buckboost.h"
// ------------------------------------------------------------------ VARIABLES
static buckboost_t buckboost;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
buckboost_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 ----\r\n");
// Click initialization.
buckboost_cfg_setup( &cfg );
BUCKBOOST_MAP_MIKROBUS( cfg, MIKROBUS_1 );
buckboost_init( &buckboost, &cfg );
buckboost_default_cfg( &buckboost );
log_printf( &logger, "--------------------------------\r\n" );
log_printf( &logger, " Buck Boost Click \r\n" );
log_printf( &logger, "--------------------------------\r\n" );
Delay_ms( 100 );
}
void application_task ( void )
{
log_printf( &logger, " Set Output Voltage of 2500 mV \r\n" );
log_printf( &logger, "--------------------------------\r\n" );
buckboost_set_2500mv( &buckboost );
Delay_ms( 5000 );
log_printf( &logger, " Set Output Voltage of 3300 mV \r\n" );
log_printf( &logger, "--------------------------------\r\n" );
buckboost_set_3300mv( &buckboost );
Delay_ms( 5000 );
log_printf( &logger, " Set Output Voltage of 4100 mV \r\n" );
log_printf( &logger, "--------------------------------\r\n" );
buckboost_set_4100mv( &buckboost );
Delay_ms( 5000 );
log_printf( &logger, " Set Output Voltage of 5000 mV \r\n" );
log_printf( &logger, "--------------------------------\r\n" );
buckboost_set_5000mv( &buckboost );
Delay_ms( 5000 );
log_printf( &logger, " Set Output Voltage of 6900 mV \r\n" );
log_printf( &logger, "--------------------------------\r\n" );
buckboost_set_6900mv( &buckboost );
Delay_ms( 5000 );
log_printf( &logger, " Set Output Voltage of 8200 mV \r\n" );
log_printf( &logger, "--------------------------------\r\n" );
buckboost_set_8200mv( &buckboost );
Delay_ms( 5000 );
log_printf( &logger, " Set Output Voltage of 12000 mV \r\n" );
log_printf( &logger, "--------------------------------\r\n" );
buckboost_set_12000mv( &buckboost );
Delay_ms( 5000 );
log_printf( &logger, " Set Output Voltage of 15000 mV \r\n" );
log_printf( &logger, "--------------------------------\r\n" );
buckboost_set_15000mv( &buckboost );
Delay_ms( 5000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END