Energize your single-cell Li-Ion battery with RT9532 and TM4C129ENCPDT
One charger, limitless power
Published Jul 01, 2023
Click board™
Charger 13 Click
Dev. board
Fusion for Tiva v8
Compiler
NECTO Studio
MCU
TM4C129ENCPDT
Ensure uninterrupted operation of your solution with dependable battery charger technology
A
A
Hardware Overview
How does it work?
Charger 13 Click is based on the RT9532, a fully integrated single-cell Li-ion battery charger from Richtek Technology that is ideal for portable applications. The RT9532 optimizes the charging task using a control algorithm including pre-charge, fast, and constant voltage modes. The input voltage range of the VIN pin can be as high as 28V. When the input voltage exceeds the OVP threshold, it will turn off the charging MOSFET to avoid overheating the chip. Besides its small physical size, the low number of external components makes this IC ideal for various applications. The 4.2V factory preset reference voltage simplifies design. The RT9532 is
designed with reliability in mind: the IC prevents draining the battery below the critical level, offers prequel charging (for deeply depleted batteries), features overvoltage protection, charging status monitoring, and more. The Click board™ itself is equipped with indicators to monitor both the charging process and power distribution: CHARGE LED indicates the charge-in-progress status, and STATUS LED indicates the power status during the charging process. On the left side of the click board is an input screw terminal with corresponding markings, where an external voltage as high as 28V can be applied. The connector on the right side is reserved
for a Li-Ion battery with GND and VBAT+ markings. When connected to a power source, the green STATUS LED will indicate it, while the red – CHARGING LED will indicate the charging is in progress and will turn off once the battery charging is finished. 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. 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.
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
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
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Fusion for Tiva v8 as your development board.
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for Charger 13 Click driver.
Key functions:
charger13_enable- This function enable battery charging by cleared to LOW state of the EN ( PWM ) pin of the Charger 13 Clickcharger13_disable- This function disable battery charging by sets to HIGH state of the EN ( PWM ) pin of the Charger 13 Clickcharger13_check- This function check if the battery is charging of the Charger 13 Click
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* \file
* \brief Charger 13 Click example
*
* # Description
* This demo application charges the battery.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization device.
*
* ## Application Task
* This is an example which demonstrates the use of Charger 13 click board.
* This example shows the automatic control of the Charger 13 click,
* waits for valid user input and executes functions based on a set of valid commands
* and check the battery charge status.
* Results are being sent to the Usart Terminal where you can track their changes.
* All data logs on usb uart for approximately every 1 sec when the data value changes.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "charger13.h"
// ------------------------------------------------------------------ VARIABLES
static charger13_t charger13;
static log_t logger;
uint8_t charger_flag;
uint8_t enable_flag;
uint8_t status_flag;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
charger13_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 ----\r\n" );
// Click initialization.
charger13_cfg_setup( &cfg );
CHARGER13_MAP_MIKROBUS( cfg, MIKROBUS_1 );
charger13_init( &charger13, &cfg );
Delay_100ms( );
charger_flag = 2;
enable_flag = 0;
log_printf( &logger, "-------------------------\r\n" );
log_printf( &logger, " 'E' : Enable \r\n" );
log_printf( &logger, " 'D' : Disable \r\n" );
log_printf( &logger, "-------------------------\r\n" );
log_printf( &logger, "Charging Status : Disable\r\n" );
log_printf( &logger, "-------------------------\r\n" );
Delay_100ms( );
}
void application_task ( void )
{
if ( enable_flag == 0 )
{
enable_flag = 1;
charger13_enable( &charger13 );
log_printf( &logger, "Charging Status : Enabled\r\n" );
log_printf( &logger, "-------------------------\r\n" );
}
else if ( enable_flag == 1 )
{
enable_flag = 0;
charger13_disable( &charger13 );
log_printf( &logger, "Charging Status : Disable\r\n" );
log_printf( &logger, "-------------------------\r\n" );
}
status_flag = charger13_check( &charger13 );
if ( status_flag != charger_flag )
{
charger_flag = charger13_check( &charger13 );
if ( charger_flag == 0 )
{
log_printf( &logger, " Battery is charging \r\n" );
log_printf( &logger, "-------------------------\r\n" );
}
else
{
log_printf( &logger, " Battery does not charge \r\n" );
log_printf( &logger, "-------------------------\r\n" );
}
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
