Be charged up and unstoppable with ISL78693 and STM32F410RB
Experience charging at its finest!
Published Oct 08, 2024
Click board™
Charger 23 Click
Dev. board
Nucleo 64 with STM32F410RB MCU
Compiler
NECTO Studio
MCU
STM32F410RB
The easy-to-use and intuitive battery charger can save you time and effort while improving your solution's functionality
A
A
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.
Features overview
Development board
Nucleo-64 with STM32F410RB MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M4
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
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 Nucleo 64 with STM32F410RB MCU 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 23 Click driver.
Key functions:
charger23_enable_deviceThis function enables the device by setting the EN pin to HIGH logic state.charger23_disable_deviceThis function disables the device by setting the EN pin to LOW logic state.charger23_get_charger_stateTThis function returns the charger state.
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 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" );
break;
}
case CHARGER23_STATE_CHARGING:
{
log_printf( &logger, "Charging in one of the three modes\r\n" );
break;
}
case CHARGER23_STATE_FAULT:
{
log_printf( &logger, "Fault\r\n" );
break;
}
default:
{
log_printf( &logger, "Unknown\r\n" );
break;
}
}
Delay_ms ( 100 );
}
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
