Charge up and be ready with LTC3225 and STM32G474RE
Reliable power, uninterrupted performance
Published Nov 08, 2024
Click board™
UPS Click
Dev. board
Nucleo 64 with STM32G474RE MCU
Compiler
NECTO Studio
MCU
STM32G474RE
Say goodbye to slow charging and unreliable power sources - experience seamless operations with our ultimate UPS solution
A
A
Hardware Overview
How does it work?
UPS Click is based on the LTC3225, a 150mA supercapacitor charger from Analog Devices, used to charge two serially connected capacitors with a controlled current and constant voltage. The LTC3225 has the unique ability to maintain constant voltage levels on both of the connected supercapacitors by monitoring their voltages. This improves the lifecycle of the supercapacitors, protecting them from overvoltage. When a voltage difference occurs during charging (depending on the dissimilarities between the two used supercapacitors), the voltage across one of them might rise enough to cause damage. Unlike other balancing techniques that use resistors to discharge the capacitor, which has a greater voltage, the LTC3225 automatically adjusts the charging currents of two capacitors until their charging speed is equal. The difference between the charging currents can be increased or decreased by 50%. When the Cout voltage reaches its nominal value (selected by the pull-up resistor on the Vsel pin to 5.3V), the internal charge pump is turned off, allowing the IC to enter the low power mode. The recharging cycle is automatically restarted when the voltage of the supercapacitors drops under a threshold. The output terminals are used to connect an external load. There are two screw terminals routed to the output pins of each capacitor. Two supercapacitors are serially connected: the high-side capacitor has its positive pin connected to the Cout (a regulated voltage output pin),
while the low-side capacitor has its negative pin connected to the GND. The negative pin of the high-side supercapacitor and the positive pin of the low-side supercapacitor are connected together and routed to the CX pin of the LTC3225, which is maintained at Cout/2. Therefore, the voltage across a single terminal is Cout/2, so to use the full range of the output voltage, a load should be connected between the high-side terminal labeled with the “+” sign and the low-side terminal labeled with the “-” sign. These terminals can also be used to connect additional supercapacitors since the supercapacitors are in parallel with the connected load. When the power source is turned off, the output voltage (Cout) depends only on used supercapacitors. These two supercapacitors have an equivalent capacitance of 1.65F, and they will become the only elements that provide power for the connected load when the power supply is removed. According to the capacitor discharging formula, these capacitors will discharge through the connected load, and the output voltage will exponentially decrease. The #SHDN pin can put the device in the low-power shutdown mode by applying a LOW logic level. This pin is routed to the RST pin of the mikroBUS™, labeled as SDN. It is pulled to a HIGH logic level by an onboard pull-up resistor. It is possible to read the output voltage value by using the voltage divider connected between the GND and the Cout. When the supercapacitors are fully charged, with the Cout
voltage level of 5.3V, the value on the middle point of the voltage divider will be about 1.7V. The middle point of the voltage divider is routed to the AN pin of the mikroBUS™, allowing an easy analog-to-digital conversion by the host MCU. This pin is labeled as SEN on the Click board™. The PGOOD pin of LTC3225 IC is routed to the mikroBUS™ CS pin and labeled as PGD. This pin is an open-drain output, and it is pulled to a HIGH logic level by an onboard resistor. When the output voltage reaches a value 6% below the nominal value, this pin is de-asserted. When the voltage drops under 7.2% below its nominal value, this pin is asserted and pulled to a LOW logic level. It can be used to monitor the state of the output supercapacitors. The Click board™ uses a power supply from the mikroBUS™. Moving the onboard SMD jumper labeled JP1 makes it possible to select either a 3.3V or 5V rail as the input power source. It also selects the IC operating voltage, allowing interfacing with both the 5V and 3.3V MCUs. Regardless of the selected operating voltage, the output voltage is always 5.3V, as set by the Vsel pin of the UPS click. UPS click uses only the GPIO pins of the MCU for setting states on its pins; therefore, it is extremely easy to work with. 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 STM32G474R 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)
512
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
128k
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.
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 STM32G474RE 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 UPS Click driver.
Key functions:
usp_set_mode- Functions for settings chip modeups_get_power_good- Functions for reading PGD 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
* \brief UPS Click example
*
* # Description
* This application is charger, that provides continuous power for a load connected to the output terminals.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes Driver init and setting chip mode as ACTIVE
*
* ## Application Task
* Checks the state of PGD (Power Good), PGD goes high when Vout is within 6% of target value (4.98V)
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "ups.h"
// ------------------------------------------------------------------ VARIABLES
static ups_t ups;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
ups_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.
ups_cfg_setup( &cfg );
UPS_MAP_MIKROBUS( cfg, MIKROBUS_1 );
ups_init( &ups, &cfg );
usp_set_mode( &ups, UPS_MODE_ACTIVE );
}
void application_task ( )
{
uint8_t pgd_state;
pgd_state = ups_get_power_good( &ups );
if ( pgd_state != 0 )
{
log_printf( &logger, "---> Power Good \r\n" );
}
Delay_1sec( );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
