Intermediate
30 min

Power your day the smart way with MAX1501 and STM32F091RC

Charge with unmatched performance!

Charger 12 Click with Nucleo-64 with STM32F091RC MCU

Published Feb 26, 2024

Click board™

Charger 12 Click

Dev. board

Nucleo-64 with STM32F091RC MCU

Compiler

NECTO Studio

MCU

STM32F091RC

Ready to see the transformative impact of our high-performance battery charger on your solution? Let's embark on the journey together.

A

A

Hardware Overview

How does it work?

Charger 12 Click is based on the MAX1501, a highly integrated, linear battery charger with thermal regulation for portable applications from Analog Devices. The MAX1501 is an efficient Lithium-Ion battery charger, thanks to Microprocessor-Controlled specific charge algorithms for Li-Ion batteries to achieve optimal capacity and safety in the shortest charging time possible. 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. A digital potentiometer sets the fast charge constant current, the MCP4161, an 8-bit digital potentiometer from Microchip, with an external 1.5KΩ resistor in series. Thanks to proprietary programmable die temperature regulation, MAX1501 can limit the charge current based on the temperature during high power or ambient conditions. This thermal regulation optimizes the charge cycle time while maintaining device reliability. The MAX1501 IC is designed with reliability in mind: the IC prevents draining the battery below the protects it from overheating

(if the thermistor is used), critical level, offers prequel charging (for deeply depleted batteries), features overvoltage protection, charging status monitoring and more. The Click board™ is equipped with indicators to monitor the charging process and power distribution: CHARGE LED indicates the charge-in-progress status, and FAULT LED indicates an error during the charging process. The digital potentiometer on Charger 12 click is MCP4161 which offers a wide range of product offerings using an SPI interface. WiperLock technology allows application-specific calibration settings to be secured in EEPROM. This digital pot is tied with a charger IC over its wiper (P0W) pin. Battery charging can be controlled by assigning values on MCP4161 from 0 to 10-kilo ohms. As there is a 1.5K resistor in series, it can never be 0 ohms on the MAX1501 charger's PROG pin. However, maximum resistance cannot exceed 11.5 kiloohms. Fast charging can be regulated with 10K on the PROG pin to get 130 mA. To get 1000 mA digital potentiometer needs to go down to 0Ohm, along with an external resistor, which

makes 1.5K. Communication with a digital potentiometer on this Click, controlling the charger, is done through the SPI interface. On the left side of the click board is an input screw terminal with corresponding markings, where the recommended external voltage of 6V can be applied. The left screw terminal is reserved for a Lithium Iron Phosphate battery with GND and VBAT+ markings. The green PWR LED will indicate it when connected to a power source. Red LED1 and green LED2 can be used for visual charge monitoring. These two LEDs are multipurpose and can be used for various things. 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.

Charger 12 Click hardware overview image

Features overview

Development board

Nucleo-64 with STM32F091RC 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.

Nucleo 64 with STM32F091RC MCU double side image

Microcontroller Overview

MCU Card / MCU

default

Architecture

ARM Cortex-M0

MCU Memory (KB)

256

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.

Click Shield for Nucleo-64 accessories 1 image

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 12 Click accessories image

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
Charging Enable
PC12
RST
Chip Enable
PB12
CS
SPI Clock
PB3
SCK
NC
NC
MISO
SPI Data IN
PB5
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
Mode Selection
PC8
PWM
Input Voltage Range Indicator
PC14
INT
NC
NC
TX
NC
NC
RX
NC
NC
SCL
NC
NC
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Click board™ Schematic

Charger 12 Click Schematic schematic

Step by step

Project assembly

Click Shield for Nucleo-64 accessories 1 image hardware assembly

Start by selecting your development board and Click board™. Begin with the Nucleo-64 with STM32F091RC MCU as your development board.

Click Shield for Nucleo-64 accessories 1 image hardware assembly
Nucleo 64 with STM32F401RE MCU front image hardware assembly
LTE IoT 5 Click front image hardware assembly
Prog-cut hardware assembly
LTE IoT 5 Click complete accessories setup image hardware assembly
Nucleo-64 with STM32XXX MCU Access MB 1 Mini B Conn - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Clicker 4 for STM32F4 HA MCU Step hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

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 12 Click driver.

Key functions:

  • charger12_generic_transfer - Generic transfer

  • charger12_mode_select - Charger mode selection

  • charger12_spi_set_register - This function set spi register

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 Charger12 Click example
 * 
 * # Description
 * This application charges the batery.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Iniztializes SPI driver.
 * 
 * ## Application Task  
 * Executes additional functions based on user input.
 * 
 * *note:* 
 * Additional Functions :

 * - charger12_case_Plus()  - Increments Wiper position.
 * - charger12_case_Minus() - Decrements Wiper position.
 * - charger12_case_One()   - Selects 1st mode of operation.
 * - charger12_case_Two()   - Selects 2nd mode of operation.
 * - charger12_case_Three() - Selects 3rd mode of operation.
 * - charger12_case_Four()  - Selects 4th mode of operation.
 * 
 * \author MikroE Team
 *
 */
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "charger12.h"

// ------------------------------------------------------------------ VARIABLES

static charger12_t charger12;
static log_t logger;

void charger12_case_plus( )
{
   log_printf( &logger, "> Wiper incremented" );
    charger12_spi_increment_wiper( &charger12 );
    log_printf( &logger, "\r\n" );
}

void charger12_case_minus( )
{
    log_printf( &logger, "> Wiper decremented" );
    charger12_spi_increment_wiper( &charger12 );
   log_printf( &logger, "\r\n" );
}

void charger12_case_one( )
{
    charger12_mode_select( &charger12, CHARGER12_MODE_Li );
    log_printf( &logger, "> Mode : Li+ Charge");
    log_printf( &logger, "\r\n" );
}

void charger12_case_two( )
{
    charger12_mode_select( &charger12, CHARGER12_MODE_NiMh_NiCd );
    log_printf( &logger, "> Mode : NiMH/NiCd Charge" );
    log_printf( &logger, "\r\n" );
}

void charger12_case_three( )
{
    charger12_mode_select( &charger12, CHARGER12_MODE_DISABLE );
    log_printf( &logger, "> Mode : Disable" );
    log_printf( &logger, "\r\n" );
}

void charger12_case_four( )
{
    charger12_mode_select( &charger12, CHARGER12_MODE_NO_BATTERY );
    log_printf( &logger, "> Mode : No Battery" );
    log_printf( &logger, "\r\n" );
}

void application_init ( void )
{
    log_cfg_t log_cfg;
    charger12_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 ----" );

    //  Click initialization.

    charger12_cfg_setup( &cfg );
    CHARGER12_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    charger12_init( &charger12, &cfg );

    Delay_ms(100);
    charger12_mode_select( &charger12, CHARGER12_MODE_DISABLE );
    Delay_ms(100);
    log_printf( &logger, "> App init done" );
}

void application_task ( void )
{
    charger12_case_plus(  );
    Delay_ms( 1000 );
  
    charger12_case_minus( );
    Delay_ms( 1000 );

    charger12_case_one( );
    Delay_ms( 1000 );     

    charger12_case_two( );
    Delay_ms( 1000 );   

    charger12_case_three( );
    Delay_ms( 1000 );

    charger12_case_four( );
    Delay_ms( 1000 );
}

void main ( void )
{
    application_init( );

    for ( ; ; )
    {
        application_task( );
    }
}


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

Additional Support

Resources

Love this project?

'Buy This Kit' button takes you directly to the shopping cart where you can easily add or remove products.