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
Fusion for TIVA 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 32-bit ARM® Cortex®-M based MCUs from Texas Instruments, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over a WiFi network. 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 TIVA v8 provides a fluid and immersive working experience, allowing access
anywhere and under any circumstances at any time. Each part of the Fusion for TIVA 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 TIVA 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.
Microcontroller Overview
MCU Card / MCU
![default](https://cdn.mikroe.com/rent-a-product/request-setup/mcu-cards/mcu-card-3-for-tiva-tm4c129encpdt.png)
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
Texas Instruments
Pin count
128
RAM (Bytes)
262144
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
![Charger 19 Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee97280-b704-6a9e-ad55-02420a00025b/charger-19-click-v100-Schematic-1.png)
Step by step
Project 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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-40a0-6b58-88de-02420a00029a/UART-AO-Step-1.jpg)
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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-eb29-62fa-ba91-02420a00029a/UART-AO-Step-2.jpg)
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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703b-7543-6fbc-9c69-0242ac120003/UART-AO-Step-3.jpg)
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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703c-068c-66a4-a4fc-0242ac120003/UART-AO-Step-4.jpg)
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