Intermediate
30 min

Create a high-efficiency power manager with LTC3586 and MK22FN512VLH12

The future of battery management

BATT-MAN Click with Kinetis Clicker

Published Aug 03, 2023

Click board™

BATT-MAN Click

Dev.Board

Kinetis Clicker

Compiler

NECTO Studio

MCU

MK22FN512VLH12

Optimize battery performance and prolong its lifespan

A

A

Hardware Overview

How does it work?

BATT-MAN Click is based on the LTC3586, a high-efficiency power manager with boost, buck-boost, and dual buck converters from Analog Devices. It includes a high-efficiency current limited switching PowerPath™ manager with automatic load prioritization, which employs the Bat-Track™ adaptive output control technology, battery charger, and four synchronous switching regulators (two bucks, one buck-boost, and one boost). The LTC3586 has a working mode that sets the PowerPath™ manager never to exceed 1A of the input current. As soon as the device is plugged into the mikroBUS™ socket, it will detect the presence of the voltage from the 5V rail on the input pins (VBUS). PowerPath™ switching regulator will deliver power from VBUS to VOUT via the SW pin. The VOUT is used to drive external loads through the switching regulators, along with the integrated battery charger. If this combined current draw does not exceed the internally set current threshold, the voltage at the VOUT pin (VSYS on the included schematic) will be held at about 0.3V above the battery voltage level - thanks to the Bat-Track™ technology, keeping the losses across the battery charger to a minimum. If the combined current draw is large enough, the current available for the charger will be reduced to provide more current for the connected load. The PowerPath™ manager will always ensure that the connected load has priority over the battery charging. Only the excess power will be used for the charger section of the device. The provided internal ideal diode and the ideal diode controller allow the battery power to be used for the output. Whenever the VSYS drops under the VBAT level or

the load requires more current than is currently available from the input switching regulator, the additional power will be pulled from the battery via the ideal diode. This allows continuous power output for the connected external load as long as the connected battery is charged. The internal ideal diode is supplemented by the external MOSFET transistor, which is controlled by a dedicated GATE pin of the LTC3586 IC. There are several outputs available on BATT-MAN click. There is one LDO output voltage, regulated to 3.3V. This is a low current output, and it can provide about 30mA of current. This output is always on and intended only for very light loads. The second regulated 3.3V output is a high current output, which can provide up to 1A of current. Heavier loads can be connected to this output. Finally, a 5V regulated output can provide up to 800mA of current and is also meant for heavier loads. All these voltage connectors are accessed through the onboard screw terminals for an easy connection. The battery charging section has all the features required for optimized charging and prolonged battery life, including a constant current/voltage battery charger with automatic recharge, automatic termination by safety timer, low voltage trickle charging, and bad cell detection. The battery float voltage is set to 4.2V, perfectly suited for the LiPo batteries available at MikroElektronika online shop. The battery charging section also features the #CHRG pin, which indicates the battery's charging state. It can signalize several states of the battery: charging, not charging, and unresponsive/damaged battery. This is an open drain output, and it is pulled

HIGH to the 3.3V provided by the low current LDO regulator. When the battery is charging, this pin is pulled to a LOW state, and the red LED indicator on the BATT-MAN click is lit. When the battery is not charging, the LED is powered off. A 6.1Hz modulation signal is applied to the charge indicator LED if the connected battery is damaged. The #CHRG pin is routed to the mikroBUS™ AN pin. The #FAULT pin indicates an error in the output voltages. Suppose the feedback voltage of the integrated buck/boost converters fails to reach 8% of the internal reference voltage within 14ms. This pin will be pulled low to indicate the error, and the switching regulators will be shut off. The #FAULT pin is bidirectional, so pulling this pin LOW externally will also disable the switching regulators. This pin is routed to the mikroBUS™ INT pin and pulled HIGH to the 3.3V provided from the low current LDO regulator. The onboard EN Vout switch (SW1) can turn the device on, even without power from the mikroBUS™ 5V rail. In this case, the connected external LiPo battery is mandatory. EN pins of the switching regulators are routed to the mikroBUS™ RST pin, allowing the MCU to shut down the device. If the switch is in the closed position, it will pull the RST line of the mikroBUS™ to a HIGH level via the 3K3 resistor. If the MCU sets the RST pin to a LOW logic level, the RST pin will supersede the switch position, and the logic state of the RST pin will become LOW. Besides the onboard screw terminals used to connect the external load, the click board™ has a standard 2.54mm pitch battery connector to connect the LiPo battery.

BATT-MAN Click hardware overview 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

You complete me!

Accessories

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.

BATT-MAN Click accessories image

Used MCU Pins

mikroBUS™ mapper

Charging indicator
PTB2
AN
Chip Enable
PTB3
RST
NC
NC
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
NC
NC
3.3V
Ground
GND
GND
NC
NC
PWM
Fault indicator
PTD0
INT
NC
NC
TX
NC
NC
RX
NC
NC
SCL
NC
NC
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

BATT-MAN 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 BATT-MAN Click driver.

Key functions:

  • battman_set_enable - This function controls the operation of the board

  • battman_get_charging_indicator - This function shows the charging status

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 BATT-MAN Click example
 * 
 * # Description
 * BATT-MAN click is a very versatile battery operated power manager. When powered via mikroBUS,
 * it will charge the connected Li-Ion/Li-Po 3.7V battery, while providing the output voltage 
 * on all its outputs at the same time.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Initializes the click driver and logger utility and enables the click board.
 * 
 * ## Application Task  
 * Checks the charging indicator status, and in relation to its state 
 * it displays an appropriate message on USB UART.
 * 
 * \author MikroE Team
 *
 */
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "battman.h"

// ------------------------------------------------------------------ VARIABLES

static battman_t battman;
static log_t logger;
static uint8_t chg_flag;

// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init ( void )
{
    log_cfg_t log_cfg;
    battman_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.

    battman_cfg_setup( &cfg );
    BATTMAN_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    battman_init( &battman, &cfg );
    
    battman_set_enable( &battman, 1 );
    log_printf( &logger, "BATT-MAN click enabled.\r\n" );
    chg_flag = 0;
}

void application_task ( void )
{
    if ( !battman_get_charging_indicator ( &battman ) )
    {
        if ( chg_flag == 1 )
        {
            log_printf( &logger, "Charging enabled.\r\n" );
        }
        chg_flag = 0;
    }
    else
    {
        if ( chg_flag == 0 )
        {
            log_printf( &logger, "Charging disabled.\r\n" );
        }
        chg_flag = 1;
    }
}

void main ( void )
{
    application_init( );

    for ( ; ; )
    {
        application_task( );
    }
}


// ------------------------------------------------------------------------ END

Additional Support

Resources