Designed to lower the input voltage while maintaining stable performance efficiently, our converter empowers your gadgets with optimal power management
A
A
Hardware Overview
How does it work?
Buck 5 Click is equipped with the MAX17506, a high-efficiency, synchronous step-down DC/DC converter with internal compensation from Analog Devices. This advanced step-down converter IC with an integrated high-side MOSFET requires a minimum number of external components, thanks to the internal feedback loop compensation. It utilizes a peak-current-mode control architecture. While the high side MOSFET is open and the current through the inductor ramps up, an overcurrent event will cause the MOSFET to close, preventing this current from becoming dangerously high. If there is a short circuit condition on the output, the device will reattempt to start after a timeout period, and if the condition is still present at the output, it will be turned off for another timeout period. The MAX5401, a 256-tap digital potentiometer with an SPI Interface made by Analog Devices, is used on the feedback loop to allow adjustment of the output voltage via the SPI interface. It is used in place of the fixed voltage divider found on the reference design of the MAX17506, regulating the output voltage to a programmed value that way. As a result, sending a digital value through the SPI interface to the MAX5401 makes it possible to control the output voltage level in the range from 0.9V to 5.5V. While operating normally (PWM
mode), the high and the low side MOSFETs are switched synchronously with the signal from the internal PWM generator, causing the current through the inductor to ramp up and down, regulating the output voltage that way. The PWM signal's lower pulse width (duty cycle) results in a lower voltage at the output. The low-side MOSFET is placed outside the IC, allowing less DC/DC converter IC dissipation. Besides the PWM mode, the device can also operate in the PFM mode (Pulse Frequency Modulation). This mode allows even higher efficiency for light loads, as the low-side MOSFET is completely unused. The high side MOSFET charges the inductor, letting the load drain it. During this period, the IC is in a hibernation state. This mode results in slightly more ripple at the output, with the added benefit of high efficiency for light loads. It is perfectly suited to power devices in the low power consumption mode (Sleep, Standby, and more). The DCM mode is the compromise mode between PWM and PFM modes. The low-side MOSFET is still unused for light loads, but the PWM pulses are not skipped, and the IC constantly drives the high-side MOSFET. This mode produces ripple at the output, but it is slightly less efficient than the PFM mode for light loads. The MODE/SYNC pin selects different modes. The IC is set to work in DCM
mode with the pull-up resistor by default. The MODE/SYNC pin of the IC is routed to the mikroBUS™ PWM pin (labeled as SYN), allowing the MCU to control the mode. When this pin is set to a LOW logic level, the constant frequency PWM mode is set. The same pin (MODE/SYNC) can synchronize the converter IC (fs) switching frequency when needed. The 39K resistor determines this frequency to about 480 kHz. However, the frequency can be synchronized with an external source from 1.1 x fs to 1.4 x fs. The #RESET pin of the IC is routed to the mikroBUS™ RST pin. This pin signalizes problems with the output voltage. The pin is driven to a LOW logic level when the output voltage drops under 92% of the nominal value or during the thermal shutdown. It is an open drain output, otherwise pulled to a HIGH logic level (when not asserted). To enable the buck converter IC, a HIGH logic level needs to be present at the EN pin of the IC, routed to the mikroBUS™ AN pin (labeled as EN). This allows the MCU to control the Power ON function of the Click board™ effectively. When the IC is enabled, the LED indicator labeled EN indicates that the IC is activated and the step-down conversion is in progress. The soft-start circuit prevents high inrush currents by ramping up the output voltage from 0V to the nominal value.
Features overview
Development board
Fusion for TIVA v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different 32-bit ARM® Cortex®-M based MCUs from Texas Instruments, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over a WiFi network. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for TIVA v8 provides a fluid and immersive working experience, allowing access
anywhere and under any circumstances at any time. Each part of the Fusion for TIVA v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector.
Communication options such as USB-UART, USB HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. Fusion for TIVA v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development 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

Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
Texas Instruments
Pin count
212
RAM (Bytes)
262144
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 5 Click driver.
Key functions:
buck5_power_on
- This function wake up the chipbuck5_reset
- This function reset the chipbuck5_set_output_voltage
- Maximum output voltage is 5.5V (255 set value), and minimum output voltage is 1V (0 set value)
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 Buck5 Click example
*
* # Description
* Buck 5 Click is a high-efficiency buck DC/DC converter, which can provide digitally
* adjusted step-down voltage on its output while delivering a considerable amount of current.
* Buck 5 click accepts a wide voltage range on its input - from 5V to 30V. The output voltage
* may be adjusted via the SPI interface, in the range from 0.9V to approximately 5.5V.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes driver init, and enables the click board.
*
* ## Application Task
* Increases the output voltage by 500mV every 3 seconds from MIN to MAX VOUT.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "buck5.h"
// ------------------------------------------------------------------ VARIABLES
static buck5_t buck5;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
buck5_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.
buck5_cfg_setup( &cfg );
BUCK5_MAP_MIKROBUS( cfg, MIKROBUS_1 );
buck5_init( &buck5, &cfg );
buck5_power_on( &buck5 );
buck5_reset( &buck5 );
}
void application_task ( void )
{
buck5_set_output_voltage( &buck5, BUCK5_VOLTAGE_MIN );
log_printf( &logger, "VOUT: MIN\r\n" );
Delay_ms( 3000 );
buck5_set_output_voltage( &buck5, BUCK5_VOLTAGE_1000mV );
log_printf( &logger, "VOUT: ~1V\r\n" );
Delay_ms( 3000 );
buck5_set_output_voltage( &buck5, BUCK5_VOLTAGE_1500mV );
log_printf( &logger, "VOUT: ~1.5V\r\n" );
Delay_ms( 3000 );
buck5_set_output_voltage( &buck5, BUCK5_VOLTAGE_2000mV );
log_printf( &logger, "VOUT: ~2V\r\n" );
Delay_ms( 3000 );
buck5_set_output_voltage( &buck5, BUCK5_VOLTAGE_2500mV );
log_printf( &logger, "VOUT: ~2.5V\r\n" );
Delay_ms( 3000 );
buck5_set_output_voltage( &buck5, BUCK5_VOLTAGE_3000mV );
log_printf( &logger, "VOUT: ~3V\r\n" );
Delay_ms( 3000 );
buck5_set_output_voltage( &buck5, BUCK5_VOLTAGE_3500mV );
log_printf( &logger, "VOUT: ~3.5V\r\n" );
Delay_ms( 3000 );
buck5_set_output_voltage( &buck5, BUCK5_VOLTAGE_4000mV );
log_printf( &logger, "VOUT: ~4V\r\n" );
Delay_ms( 3000 );
buck5_set_output_voltage( &buck5, BUCK5_VOLTAGE_4500mV );
log_printf( &logger, "VOUT: ~4.5V\r\n" );
Delay_ms( 3000 );
buck5_set_output_voltage( &buck5, BUCK5_VOLTAGE_5000mV );
log_printf( &logger, "VOUT: ~5V\r\n" );
Delay_ms( 3000 );
buck5_set_output_voltage( &buck5, BUCK5_VOLTAGE_MAX );
log_printf( &logger, "VOUT: MAX\r\n" );
Delay_ms( 3000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END