This high-efficiency buck regulator stands as a beacon of power management, delivering superior voltage conversion while minimizing energy losses
A
A
Hardware Overview
How does it work?
MCP16331 Click is based on the MCP16331, a non-synchronous, step-down converter from Microchip capable of stepping input voltages ranging from 4.4V to 50V and output voltage ranging from 2.0V to 24V. More details about the MCP16331 are available in the official datasheet. However, the MCP16331 click is designed to handle an input voltage ranging from 4.5V to 18V and output a voltage ranging from 2,25V to 12V at 500 mA maximum current since it works in a buck-boost topology. To set the output voltage of the MCP16331 click, the MCP4921 - a low-power 12-Bit dual voltage output DAC is used in the feedback loop. The output of this DAC is used to drive the FB pin of the MCP16331, so to set up the output voltage, it is enough to set the DAC output to a specific value. This will cause the FB pin to drive
the switching section of the MCP16331, which will output a desired voltage level as a result. The AN pin of the mikroBUS™ can be used to verify the output voltage and correct the value given to the DAC if needed. The MCP4291 DAC can be configured by the host MCU via the SPI bus pins, routed to the mikroBUS™. The AN pin of the mikroBUS™ is routed to a middle point of a voltage divider on the output. This voltage divider is used to scale down the output voltage so the ADC of the host MCU can successfully convert it. Besides the bit depth of the ADC, this should also be considered when calculating the output voltage value. The MCP16331 click has two screw terminals used to connect the input voltage and the load, and the SMD jumper is used to select the voltage for the DAC IC. This affects the SPI logic
voltage levels, so both 3.3V and 5V MCUs can be used with this Click board™. This sequence is because the enable pin (EN) of the MCP16331 has an internal pull-up resistor that keeps the MCP16331 output stage enabled even if the pin is left unconnected. At power-up, before you set the voltage via SPI, DAC output is unspecified, and the output voltage may be set higher than what your load supports. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via an onboard jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used, as a reference, for further development.
Features overview
Development board
Nucleo 32 with STM32F031K6 MCU board provides an affordable and flexible platform for experimenting with STM32 microcontrollers in 32-pin packages. Featuring Arduino™ Nano connectivity, it allows easy expansion with specialized shields, while being mbed-enabled for seamless integration with online resources. The
board includes an on-board ST-LINK/V2-1 debugger/programmer, supporting USB reenumeration with three interfaces: Virtual Com port, mass storage, and debug port. It offers a flexible power supply through either USB VBUS or an external source. Additionally, it includes three LEDs (LD1 for USB communication, LD2 for power,
and LD3 as a user LED) and a reset push button. The STM32 Nucleo-32 board is supported by various Integrated Development Environments (IDEs) such as IAR™, Keil®, and GCC-based IDEs like AC6 SW4STM32, making it a versatile tool for developers.
Microcontroller Overview
MCU Card / MCU

Architecture
ARM Cortex-M0
MCU Memory (KB)
32
Silicon Vendor
STMicroelectronics
Pin count
32
RAM (Bytes)
4096
You complete me!
Accessories
Click Shield for Nucleo-32 is the perfect way to expand your development board's functionalities with STM32 Nucleo-32 pinout. The Click Shield for Nucleo-32 provides two mikroBUS™ sockets to add any functionality from our ever-growing range of Click boards™. We are fully stocked with everything, from sensors and WiFi transceivers to motor control and audio amplifiers. The Click Shield for Nucleo-32 is compatible with the STM32 Nucleo-32 board, providing an affordable and flexible way for users to try out new ideas and quickly create prototypes with any STM32 microcontrollers, choosing from the various combinations of performance, power consumption, and features. The STM32 Nucleo-32 boards do not require any separate probe as they integrate the ST-LINK/V2-1 debugger/programmer and come with the STM32 comprehensive software HAL library and various packaged software examples. This development platform provides users with an effortless and common way to combine the STM32 Nucleo-32 footprint compatible board with their favorite Click boards™ in their upcoming projects.
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 MCP16331 Click driver.
Key functions:
mcp16331_set_vout
- This function sets the output voltage 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 Mcp16331 Click example
*
* # Description
* This application is buck-boost voltage regulator.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Sends hal pointers, and initializes Click
*
* ## Application Task
* Switches between 5 V and 12 V values
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "mcp16331.h"
// ------------------------------------------------------------------ VARIABLES
static mcp16331_t mcp16331;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
mcp16331_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.
mcp16331_cfg_setup( &cfg );
MCP16331_MAP_MIKROBUS( cfg, MIKROBUS_1 );
mcp16331_init( &mcp16331, &cfg );
}
void application_task ( void )
{
mcp16331_set_vout( &mcp16331, 5000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
mcp16331_set_vout( &mcp16331, 12000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END