30 min

Be charged up and unstoppable with ISL78693 and STM32F215RE

Experience charging at its finest!

Charger 23 Click with Fusion for ARM v8

Published May 14, 2023

Click board™

Charger 23 Click

Development board

Fusion for ARM v8


NECTO Studio



The easy-to-use and intuitive battery charger can save you time and effort while improving your solution's functionality



Hardware Overview

How does it work?

Charger 23 Click is based on the ISL78693, an integrated charger for single-cell Lithium chemistry batteries from Renesas. The ISL78693 functions as a traditional linear charger. The ISL78693 charges a battery as a linear charger in the Constant Current (CC) and Constant Voltage (CV) profile. Its constant charge current is selectable via onboard jumper CURR SEL between 250 and 500mA. The charge voltage is also characterized by an accuracy of 1% over the entire recommended operating condition range. The charger automatically recharges the battery when the voltage typically drops below a recharge threshold of 3.3V. When the input supply is absent, the ISL78693 draws less than 1µA current from the battery. This Click board™ communicates with the host MCU using several pins of the mikroBUS™ socket.

The charger can be enabled or disabled using the EN pin of the mikroBUS™ socket, offering a switch operation to turn the ON/OFF charger. In addition, the ISL78693 also has two indication signals to indicate the charge status. The ST pin is a status open-drain that turns to a low logic state at the beginning of a charge cycle until the End-of-charge (EOC) condition is qualified. Once the EOC condition is qualified, the ST pin goes to a HIGH logic state. The fault pin (FLT) turns low when fault conditions occur, such as the external battery temperature fault, a charge time fault, or battery removal. Besides mikroBUS™ pins, their visual representation is also via red and yellow LEDs marked with STATUS and FAULT. An NTC function is also available to monitor the battery temperature and ensure a safe charging temperature range.

Apart from monitoring, it is also possible to detect the removal of the battery. To use this function, switching the SEN EN jumper to the YES position and connecting an external NTC to the SENSE header pins is necessary. This Click board™ can only be operated from a 5V logic voltage level. Therefore, the board must perform appropriate logic voltage conversion before using MCUs with different logic levels. Additionally, there is a possibility for the ISL78693 power supply selection via jumper labeled as VIN SEL to supply the ISL78693 from an external 5V power supply or with a 5V mikroBUS™ power rail. However, the 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.

Charger 23 Click hardware overview image

Features overview

Development board

Fusion for ARM v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different ARM® Cortex®-M based MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for ARM v8 provides a fluid and immersive working experience, allowing access anywhere and under any

circumstances at any time. Each part of the Fusion for ARM v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector.

Communication options such as USB-UART, USB HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. Fusion for ARM v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.

Fusion for ARM v8 horizontal image

Microcontroller Overview

MCU Card / MCU



8th Generation


ARM Cortex-M3

MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


You complete me!


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.

Charger 23 Click accessories image

Used MCU Pins

mikroBUS™ mapper

Charge Status
Power Supply
Fault Indicator
Power Supply

Take a closer look


Charger 23 Click Schematic schematic

Step by step

Project assembly

Fusion for PIC v8 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Fusion for ARM v8 as your development board.

Fusion for PIC v8 front image hardware assembly
GNSS2 Click front image hardware assembly
SiBRAIN for PIC32MZ1024EFK144 front image hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
v8 SiBRAIN Access MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
NECTO Compiler Selection Step Image hardware assembly
NECTO Output Selection Step Image hardware assembly
Necto image step 6 hardware assembly
Necto image step 7 hardware assembly
Necto image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Necto PreFlash Image hardware assembly

Track your results in real time

Application Output

After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.

UART Application Output Step 1

Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.

UART Application Output Step 2

In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".

UART Application Output Step 3

The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.

UART Application Output Step 4

Software Support

Library Description

This library contains API for Charger 23 Click driver.

Key functions:

  • charger23_enable_device This function enables the device by setting the EN pin to HIGH logic state.

  • charger23_disable_device This function disables the device by setting the EN pin to LOW logic state.

  • charger23_get_charger_state TThis function returns the charger state.

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 main.c
 * @brief Charger 23 Click Example.
 * # Description
 * This example demonstrates the use of Charger 23 click board by enabling the device
 * and then reading and displaying the charger status.
 * The demo application is composed of two sections :
 * ## Application Init
 * Initializes the driver and enables the device.
 * ## Application Task
 * Reads the charger state and displays it on the USB UART on change.
 * @note
 * Depending on the CURR SEL onboard jumper position this click board is able to
 * charge batteries of 250mAh or 500mAh rated capacity.
 * @author Stefan Filipovic

#include "board.h"
#include "log.h"
#include "charger23.h"

static charger23_t charger23;   /**< Charger 23 Click driver object. */
static log_t logger;    /**< Logger object. */

void application_init ( void ) 
    log_cfg_t log_cfg;  /**< Logger config object. */
    charger23_cfg_t charger23_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.
    charger23_cfg_setup( &charger23_cfg );
    CHARGER23_MAP_MIKROBUS( charger23_cfg, MIKROBUS_1 );
    if ( DIGITAL_OUT_UNSUPPORTED_PIN == charger23_init( &charger23, &charger23_cfg ) ) 
        log_error( &logger, " Communication init." );
        for ( ; ; );
    charger23_enable_device ( &charger23 );
    log_info( &logger, " Application Task " );

void application_task ( void ) 
    static uint8_t chg_state_old = CHARGER23_STATE_UNKNOWN;
    uint8_t chg_state = charger23_get_charger_state ( &charger23 );
    if ( chg_state_old != chg_state )
        chg_state_old = chg_state;
        log_printf( &logger, "\r\n Charger state: " );
        switch ( chg_state )
            case CHARGER23_STATE_IDLE:
                log_printf( &logger, "Charge completed with no fault (Inhibit) or Standby\r\n" );
            case CHARGER23_STATE_CHARGING:
                log_printf( &logger, "Charging in one of the three modes\r\n" );
            case CHARGER23_STATE_FAULT:
                log_printf( &logger, "Fault\r\n" );
                log_printf( &logger, "Unknown\r\n" );
        Delay_ms ( 100 );

void main ( void ) 
    application_init( );

    for ( ; ; ) 
        application_task( );

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

Additional Support