Intermediate
30 min

Unleash efficiency and performance with step-down/step-up regulator based on MIC23099 and MK22FN512VLH12

AA/AAA cell buck-boost

MIC23099 Click with Kinetis Clicker

Published Aug 01, 2023

Click board™

MIC23099 Click

Dev.Board

Kinetis Clicker

Compiler

NECTO Studio

MCU

MK22FN512VLH12

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.

MIC23099 Click top side image
MIC23099 Click bottom side image

Features overview

Development board

Kinetis Clicker is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit ARM Cortex-M4 microcontroller, the MK22FN512VLH12 from NXP Semiconductor, a USB connector, LED indicators, buttons, a mikroProg connector, and a header for interfacing with external electronics. Thanks to its compact design with clear and easy-recognizable silkscreen markings, it provides a fluid and immersive working experience, allowing access

anywhere and under any circumstances. Each part of the Kinetis Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Kinetis Clicker programming method, using USB HID mikroBootloader, or through an external mikroProg connector for Kinetis programmer, the Clicker board also includes a clean and regulated power supply module for the development kit. The USB-MiniAB connection provides up to 500mA of current, which is more than enough to operate all

onboard and additional modules. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several buttons and LED indicators. Kinetis 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.

Kinetis Clicker double side image

Microcontroller Overview

MCU Card / MCU

default

Architecture

ARM Cortex-M4

MCU Memory (KB)

512

Silicon Vendor

NXP

Pin count

64

RAM (Bytes)

131072

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
NC
NC
RST
Enable
PTC4
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
NC
NC
PWM
Power Good Indicator
PTD0
INT
NC
NC
TX
NC
NC
RX
NC
NC
SCL
NC
NC
SDA
NC
NC
5V
Ground
GND
GND
1

Take a closer look

Schematic

MIC23099 Click Schematic schematic

Step by step

Project assembly

Kinetis Clicker front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Kinetis Clicker as your development board.

Kinetis Clicker front image hardware assembly
GNSS2 Click front image hardware assembly
Prog-cut hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
Kinetis Mini B Connector Clicker Access - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Kinetis Clicker HA MCU/Select Step hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

Track your results in real time

Application Output

After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.

Application Output Step 1

After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.

Application Output Step 3

Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.

Application Output Step 4

Software Support

Library Description

This library contains API for MIC23099 Click driver.

Key functions:

  • mic23099_default_cfg - This function executes default configuration for MIC23099 Click

  • mic23099_check_power_good - This function checks the state of Power Good output pin

Open Source

Code example

This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.

/*!
 * \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

Additional Support

Resources