Provide superior illumination with CAT3224 and STM32F091RC
Your beacon of light in the dark
Published Feb 26, 2024
Click board™
LED Flash Click
Dev Board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
With a focus on innovation and illumination, our purpose is to empower individuals with a cutting-edge LED flashlight solution that ensures longer-lasting and brighter light when you need it most
A
A
Hardware Overview
How does it work?
LED Flash Click is based on the CAT3224, a flash LED driver from ON Semiconductor. The click is designed to run on a 5V power supply. It communicates with the target microcontroller over the following pins on the mikroBUS™ line: AN, RST, PWM, and INT. The CAT3224 is a very high−current integrated flash LED driver which also supports the charging function for a dual−cell supercapacitor applications. Ideal for Li−ion battery−powered systems, it delivers up to 4A LED flash pulses, far beyond the peak current capability of the battery. Dual−mode 1x/2x charge pump charges the stacked supercapacitor to a nominal voltage of 5.4 V, while an active balance control circuit ensures that both capacitor cell voltages remain matched. The driver also features two matched current sources. External resistors
provide the adjustment for the maximum flash mode current (up to 4 A) and the torch mode current (up to 400 mA). A built−in safety timer automatically terminates the flash pulse beyond a maximum duration of 300 ms. The CAT3224 has a shutdown mode that is so low that ON Semiconductor can safely call it "zero" mode. In this mode, it typically uses only 1μA. On the LED Flash click there are three different LED indicators, here is how they operate: CHARGE — When this LED is on the driver is in charge mode; READY — When this LED is on it indicates that the supercapacitor is fully charged; PWR — Indicates if power is present. FLAG is an active−low open−drain output that notifies the microcontroller that the supercapacitor is fully charged by pulling the output low (pin 15 in the
mikroBUS). When using FLAG, this pin should be connected to a positive rail via an external pull−up resistor. TORCH is the torch mode enable pin. When high, the LED current sources are enabled in torch mode. FLASH is the flash mode enable pin. When high, the LED current sources are enabled in flash mode. If FLASH is kept high for longer than 300 ms typical, the LED channels are automatically disabled. LEDA, LEDB are connected internally to the current sources and must be connected to the LED anodes. Each output is independently current regulated. These pins enter a high−impedance ‘zero’ current state whenever the device is placed in shutdown mode or FLASH and TORCH are low.
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.
Microcontroller Overview
MCU Card / MCU
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.
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 STM32F091RC MCU as your development board.
Track your results in real time
Application Output
This Click board can be interfaced and monitored in two ways:
Application Output- Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
UART Terminal- Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Software Support
Library Description
This library contains API for LED Flash Click driver.
Key functions:
ledflash_char_supcap_enable- Charge Supercapacitor Enable functionledflash_flash_enable- Flash Enable functionledflash_flash_rdy_flag- Check Flash Ready Flag function
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 LED Flash Click example
*
* # Description
* This application switching on and off led flash.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enables GPIO, starts write log and issues a warning.
*
* ## Application Task
* This example demonstrates the use of LED Flash Click board by flashing
* with LEDs when ever supercapacitor is at a full voltage.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "ledflash.h"
// ------------------------------------------------------------------ VARIABLES
static ledflash_t ledflash;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
ledflash_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.
ledflash_cfg_setup( &cfg );
LEDFLASH_MAP_MIKROBUS( cfg, MIKROBUS_1 );
ledflash_init( &ledflash, &cfg );
Delay_ms( 100 );
log_printf( &logger, "----------------------------------\r\n" );
log_printf( &logger, " LED Flash Click \r\n" );
log_printf( &logger, "----------------------------------\r\n" );
log_printf( &logger, "/////////////////\r\n" );
log_printf( &logger, " WARNING!!! \r\n" );
log_printf( &logger, " DO NOT LOOK \r\n" );
log_printf( &logger, " INTO THE LEDS, \r\n" );
log_printf( &logger, " WHILE THAY ARE ON!!! \r\n" );
log_printf( &logger, "/////////////////\r\n" );
Delay_ms( 1000 );
}
void application_task ( )
{
uint8_t state;
log_printf( &logger, " Charge Supercapacitor Enable \r\n" );
ledflash_char_supcap_enable( &ledflash );
Delay_ms( 1000 );
state = ledflash_flash_rdy_flag( &ledflash );
if ( state == 0 )
{
log_printf( &logger, " Flash ON! \r\n" );
ledflash_flash_enable( &ledflash );
}
else
{
log_printf( &logger, " Flash OFF! \r\n" );
ledflash_flash_disable( &ledflash );
}
log_printf( &logger, "----------------------------------\r\n" );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
