Unleash efficiency and performance with step-down/step-up regulator based on MIC23099 and STM32F407ZG
AA/AAA cell buck-boost
Published Aug 01, 2023
Click board™
MIC23099 Click
Dev Board
UNI Clicker
Compiler
NECTO Studio
MCU
STM32F407ZG
Efficiently manage the power supply for electronic devices that require a voltage different from that provided by a single AA or AAA battery
A
A
Hardware Overview
How does it work?
MIC23099 Click is based on the MIC23099, a single AA/AAA cell step-down/step-up regulator with battery monitoring from Microchip. This Click is designed to run on a 3.3V power supply. It communicates with the target microcontroller over the following pins on the mikroBUS™ line: CS, INT. MIC23099 Click has three screw terminals (Buck 1V, GND, and Boost 3V3) which are outputs
for connecting some external consumers. The low-battery level is indicated by an onboard STAT LED. The MIC23099 is not a battery charger but needs a battery to work properly. The battery is not included. The MIC23099 is a high-efficiency, low-noise, dual output, integrated power management solution for single-cell alkaline or NiMH battery applications. Both converters are
designed to operate with a minimum switching frequency of 80 kHz for the buck and 100 kHz for the boost to minimize switching artifacts in the audio band. The high-current boost has a maximum switching frequency of 1 MHz, minimizing the solution footprint. The MIC23099 incorporates both battery management functions and fault protection.
Features overview
Development board
UNI Clicker is a compact development board designed as a complete solution that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It supports a wide range of microcontrollers, such as different ARM, PIC32, dsPIC, PIC, and AVR from various vendors like Microchip, ST, NXP, and TI (regardless of their number of pins), four mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a debugger/programmer connector, and two 26-pin headers for interfacing with external electronics. Thanks to innovative manufacturing technology, it allows you to build
gadgets with unique functionalities and features quickly. Each part of the UNI Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the UNI Clicker programming method, using a third-party programmer or CODEGRIP/mikroProg connected to onboard JTAG/SWD header, the UNI Clicker board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Type-C (USB-C) connector, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or using a Li-Po/Li
Ion battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board (plus USB HOST/DEVICE), including the well-established mikroBUS™ socket, a standardized socket for the MCU card (SiBRAIN standard), and several user-configurable buttons and LED indicators. UNI Clicker is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping 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
STMicroelectronics
Pin count
144
RAM (Bytes)
196608
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 UNI Clicker as your development board.
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for MIC23099 Click driver.
Key functions:
mic23099_default_cfg- This function executes default configuration for MIC23099 Clickmic23099_check_power_good- This function checks the state of Power Good output pin
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 MIC23099 Click example
*
* # Description
* MIC23099 click represent single AA/AAA cell step-down/step-up regulator
* with battery monitoring.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Application Init performs Logger and Click initialization.
*
* ## Application Task
* This example demonstrates the use of MIC23099 Click board by checking
* the state of power good pin and sends note via UART Terminal
* if the state is low.
*
* \author Mihajlo Djordjevic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "mic23099.h"
// ------------------------------------------------------------------ VARIABLES
static mic23099_t mic23099;
static log_t logger;
static uint8_t new_stat;
static uint8_t old_stat;
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
mic23099_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_printf( &logger, "--------------------------\r\n" );
log_printf( &logger, " Application Init\r\n" );
Delay_ms ( 1000 );
// Click initialization.
mic23099_cfg_setup( &cfg );
MIC23099_MAP_MIKROBUS( cfg, MIKROBUS_1 );
mic23099_init( &mic23099, &cfg );
log_printf( &logger, "--------------------------\r\n" );
log_printf( &logger, " ---- MIC23099 Click ---- \r\n" );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms ( 1000 );
mic23099_default_cfg( &mic23099 );
Delay_ms ( 1000 );
new_stat = MIC23099_DISABLE;
old_stat = MIC23099_ENABLE;
log_printf( &logger, " -- Initialization done --\r\n" );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms ( 1000 );
}
void application_task ( void )
{
new_stat = mic23099_check_power_good( &mic23099 );
if ( new_stat == MIC23099_ENABLE && old_stat == MIC23099_DISABLE )
{
old_stat = MIC23099_ENABLE;
}
if ( new_stat == MIC23099_DISABLE && old_stat == MIC23099_ENABLE )
{
log_printf( &logger, " Change battery and reset. \r\n" );
log_printf( &logger, "------------------------------\r\n" );
old_stat = MIC23099_DISABLE;
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
