Charge Li-Ion or Polymer batteries with nPM1100 and STM32F745ZG
Charge smart - charge safe
Published Dec 10, 2023
Click board™
Charger 19 Click
Dev Board
UNI Clicker
Compiler
NECTO Studio
MCU
STM32F745ZG
Comprehensive solution for battery charging needs, with a focus on efficiency, versatility, and safety
A
A
Hardware Overview
How does it work?
Charger 19 Click is based on the nPM1100, an integrated power management IC from Nordic Semiconductor. It supports charging batteries at up to 400mA. The charging current can be selected over the CHARGE SEL jumper (100, 200, 400mA). The low quiescent current extends battery life for shipping and storage in Ship mode or in operation with auto-controlled hysteretic buck mode for high efficiency down to 1μA loads. The Ship mode isolates the battery, can be activated by the host MCU, and deactivated over the onboard SHIP MODE RST key button or by connecting the Charger 19 Click to a VBUS power supply. The VBUS can be supplied with power over the USB C connector or the VBUS header with a voltage of 4.1 up to 5.5V. The battery can be connected to the BATT connector with properly
labeled polarity. It can also deliver up to 150mA of current to power external components with regulated voltage over the VOUTB terminal. The output voltage can be set in a range of 1.8 – 3.0V by the host MCU, according to the table in the datasheet. There is also a system voltage output terminal VSYS, which is automatically enabled after a power-on reset and indicated by the VSYS LED. In addition, there are CHG and ERR LEDs, which indicate the device's charging status. The nPM1100 implements a thermal regulation based on battery temperature. There is an NTC SEL jumper to choose between the onboard 10K resistor or an external NTC thermistor, which can be connected over the NTC EXT connector. Finally, the termination voltage can be set over the VTERM SEL jumper between 4.1V and 4.2V
(4.1V set by default). Charger 19 Click uses a general purpose IO pins to communicate with the host MCU. The mentioned shipping mode can be activated over the SAC pin. You can always monitor the battery charging level over the analog AN pin and voltage divider. The buck regulator output voltage can be set over the VS1 and VS2 pins, but only when no connected device exists. You can connect the device to VOUTB after you set the output voltage. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this 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.
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-M7
MCU Memory (KB)
1024
Silicon Vendor
STMicroelectronics
Pin count
144
RAM (Bytes)
327680
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.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
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
After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.
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™.
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.
Software Support
Library Description
This library contains API for Charger 19 Click driver.
Key functions:
charger19_set_vout- Charger 19 set output voltage function.charger19_set_ship_mode- Charger 19 set Ship mode function.charger19_get_vbat- Charger 19 get battery voltage function.
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 19 Click Example.
*
* # Description
* This example demonstrates the use of Charger 19 click board by enabling the device
* and then reading and displaying the battery voltage.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and enables the device, sets the output
* voltage to 3 V.
*
* ## Application Task
* Tracking charging status, reading battery voltage.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "charger19.h"
static charger19_t charger19; /**< Charger 19 Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
charger19_cfg_t charger19_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.
charger19_cfg_setup( &charger19_cfg );
CHARGER19_MAP_MIKROBUS( charger19_cfg, MIKROBUS_1 );
if ( ADC_ERROR == charger19_init( &charger19, &charger19_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( CHARGER19_ERROR == charger19_default_cfg ( &charger19 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
float voltage = 0;
if ( CHARGER19_OK == charger19_get_vbat ( &charger19, &voltage ) )
{
log_printf( &logger, " Battery Voltage : %.3f[V]\r\n\n", voltage );
Delay_ms( 1000 );
}
}
int main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
