Voltage boost for superior energy thanks to the MAX17222 and STM32F031K6
Get a boost for success
Published Oct 01, 2024
Click board™
Nano Power Click
Dev. board
Nucleo 32 with STM32F031K6 MCU
Compiler
NECTO Studio
MCU
STM32F031K6
Create a boost (step-up) DC-DC converter with extremely high efficiency and low input voltage aimed at the low-power IoT market, battery-powered sensors, and other devices
A
A
Hardware Overview
How does it work?
Nano Power Click is based on the MAX17222, a nano power synchronous boost converter with True Shutdown™ technology, from Analog Devices. The device operates in several modes, allowing optimal utilization of the available power. The device will automatically switch to a different working mode depending on the connected load, providing optimal conditions for a given situation. The MAX17222 uses the pulse frequency modulation control (PFM) topology, which allows high efficiency over a wide range of output currents. The PFM control allows continuous and discontinuous (CCM and DCM) switching modes. Operation of the MAX17222 changes with the connected load, as mentioned above. When the load is very light, the device operates in the Ultra Low Power Mode (ULPM), and the switching is performed in discontinuous mode (DCM). The ULPM is typically used when the device connected at the output is in standby or power-down mode, draining a low current. As the current requirement increases, the MAX17222 device switches to the Low Power mode and further to the High Power mode (LPM and HPM). These modes result in cleaner output and less ripple than the ULPM
mode. When working in HPM, the continuous switching mode (CCM) is used (with no pulses being skipped), providing low noise, ripple-free output voltage, which is suitable for various sensor measurements, A/D conversions, wireless communication, and other noise and ripple-sensitive applications. The EN pin of the MAX17222 is used to enable this device. When a transition from LOW to HIGH logic state appears at this pin (rising edge), it will activate the IC, and regulated 5V will appear at the output (providing the proper input voltage is present). This pin is routed to the mikroBUS™ CS pin, labeled EN. The device will remain enabled, even if the input voltage drops to 0.4V, thanks to the internal ETP section of the MAX17222 IC. Holding the EN pin to a HIGH logic state once the conversion is started results in slightly increased power consumption. The Power LED indicator is connected to the 5V rail of the mikroBUS™ and does not affect the power consumption on the connected external power supply. The power consumption calculations in the datasheet remain true and are not affected by any external components of this Click board™. The Power LED indicates the presence of the
mikroBUS™ voltage, signaling that the EN pin can be controlled via the host MCU. The external power supply can be connected to the input terminals between the VIN and GND, ranging from 0.95V up to 5.5V. However, for an optimal operation of the Nanopower click, the input voltage should be lower than the output voltage. The Nanopower click allows a maximum peak current of 500mA before the current limit protection activates. The output voltage is fixed at 5V by a single resistor, connected between the SEL pin of the IC and GND. This resistor is 0 Ω, and it is basically - an SMD jumper. Using other values (listed in the datasheet of the MAX17222 IC) makes it possible to change the output voltage to a value different than 5V. Please consult the datasheet to select the resistor for the given output voltage properly. The control of the Nanopower click is extremely simple, and it is reduced to controlling a single pin. However, provided library offers functions that simplify and speed up application development even more. The included example application demonstrates their use. This application can be used as a reference for custom projects.
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
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 Nano Power Click driver.
Key functions:
nanopw_enable_device- This function enables and disables the device
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 Nano Power Click example
*
* # Description
* This aplication performs control of the device's voltage.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes GPIO driver.
*
* ## Application Task
* Turns device on for 5 seconds and than turns device off for 10 seconds,
* then the output voltage starts to fall.
* When input voltage rises from 0.8V to 5.5V,
* the output voltage rises from 5.1V to 5.25V.
* When input voltage is less than 0.8V, the output voltage is less than 5V.
*
*
* \author Petar Suknjaja
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "nanopower.h"
// ------------------------------------------------------------------ VARIABLES
static nanopower_t nanopower;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
nanopower_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.
nanopower_cfg_setup( &cfg );
NANOPOWER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
nanopower_init( &nanopower, &cfg );
}
void application_task ( void )
{
log_printf(&logger,"Device enabled\r\n");
nanopw_enable_device( &nanopower, NANOPW_ENABLE_DEVICE );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf(&logger,"Device disabled\r\n");
nanopw_enable_device( &nanopower, NANOPW_DISABLE_DEVICE );
// 10 seconds delay
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
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
