Boost a low voltage from a connected battery to a stable USB-C 5V output with TPS81256 and STM32F031K6
Complete DC/DC step-up power converter intended for battery-powered portable applications
Published Oct 01, 2024
Click board™
Battery Source Click
Dev. board
Nucleo 32 with STM32F031K6 MCU
Compiler
NECTO Studio
MCU
STM32F031K6
Increase voltage from a lower battery level to a standard USB-Type C 5V for powering various portable electronics
A
A
Hardware Overview
How does it work?
Battery Source Click is based on the TPS81256, a high-efficiency step-up converter in a MicroSiP™ package from Texas Instruments. The TPS81256 features a high-frequency synchronous step-up DC/DC converter optimized for battery-powered portable applications. It boosts power from a connected battery (input range from 2.5V to 5.5V) and delivers it via a USB Type-C connector as 5V/1A. The TPS81256 includes a switching regulator, inductor, and input/output capacitors operating at a regulated 4MHz switching frequency. It enters Power-Save mode at light load currents, maintaining high efficiency across the entire load range. The PFM mode reduces the supply current
to 43μA (typical) during light load operation, extending battery life. Additionally, it supports more than 3W output power over a full Li-Ion battery voltage range and has an input current of less than 1µA (typical) in shutdown mode, maximizing battery life. It is ideal for low-power applications that require efficient power management. This board also features an output enable function implemented via the MAX40200, allowing users to control the power delivery on the USB-C output connector digitally. This control is achieved through the EN pin of the mikroBUS™ socket, enabling precise power flow management. Additionally, the board includes a red LED indicator labeled
ENABLE, which provides a clear visual indication of active output. This allows for easy and convenient monitoring of the board's status and ensures that users can quickly verify when the output is active. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL 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.
Li-Polymer Battery is the ideal solution for devices that demand a dependable and long-lasting power supply while emphasizing mobility. Its compatibility with mikromedia boards ensures easy integration without additional modifications. With a voltage output of 3.7V, the battery meets the standard requirements of many electronic devices. Additionally, boasting a capacity of 2000mAh, it can store a substantial amount of energy, providing sustained power for extended periods. This feature minimizes the need for frequent recharging or replacement. Overall, the Li-Polymer Battery is a reliable and autonomous power source, ideally suited for devices requiring a stable and enduring energy solution. You can find a more extensive choice of Li-Polymer batteries in our offer.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Nucleo 32 with STM32F031K6 MCU as your development board.
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 Battery Source Click driver.
Key functions:
batterysource_set_output- This function is used to set output state of Battery Source Click.
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 main.c
* @brief Battery Source Click Example.
*
* # Description
* This example demonstrates the use of Battery Source Click board,
* by changing state of the output.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and disables the output.
*
* ## Application Task
* Enabling output for 5 seconds, then disabling it for 5 seconds.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "batterysource.h"
static batterysource_t batterysource; /**< Battery Source Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
batterysource_cfg_t batterysource_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.
batterysource_cfg_setup( &batterysource_cfg );
BATTERYSOURCE_MAP_MIKROBUS( batterysource_cfg, MIKROBUS_1 );
if ( DIGITAL_OUT_UNSUPPORTED_PIN == batterysource_init( &batterysource, &batterysource_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
batterysource_set_output( &batterysource, BATTERYSOURCE_DISABLE_OUTPUT );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
log_printf( &logger, " Output is enabled \r\n" );
batterysource_set_output( &batterysource, BATTERYSOURCE_ENABLE_OUTPUT );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " Output is disabled \r\n" );
batterysource_set_output( &batterysource, BATTERYSOURCE_DISABLE_OUTPUT );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
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
Additional Support
Resources
Category:Boost
