Enhance the lighting capabilities in your projects with KTD2691 and STM32F410RB
Generate either a flash or a continuous torch light
Published Oct 08, 2024
Click board™
LED Flash 3 Click
Dev Board
Nucleo 64 with STM32F410RB MCU
Compiler
NECTO Studio
MCU
STM32F410RB
Deliver quick bursts of intense light for photography needs or maintain a steady and constant illumination for navigation purposes
A
A
Hardware Overview
How does it work?
LED Flash 3 Click is based on the KTD2691, an inductorless single-flash LED driver from Kinetic Technologies. While working in flash mode, you can program the LED current over the software, but you can also use a hardware strobe pin to control this mode. The software can only program the torch mode and on/off ramp. There are various additional functionalities that this LED driver provides. This includes low voltage protection (LVP), a flash time-out function that sets the maximum time of one flash event, under voltage lock-out (UVLO), thermal shutdown, LED short protection, LED open protection, and more. The LED Flash 3 Click is
equipped with the XPCWHT-L1-R250-00A01, an Xlamp XP-C LED. The LED combines proven lighting-class performance and reliability. It features a white LED with a wide viewing angle and low thermal resistance. In addition, you can add an external similar LED over the available connector. The LED selection can be made over the LED SEL jumper. You can also select the LED driver voltage supply between the 3.3V and 5V over the VCC SEL jumper. LED Flash 3 Click uses a standard 2-wire I2C interface to communicate with the host MCU supporting standard and a fast mode with up to 400kHz clock frequency. The hardware strobe pin is
available over the STB pin. If using the STROBE pin to control the flash mode, there is an option to select when the flash mode is deactivated. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VIO SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this 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.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
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 via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for LED Flash 3 Click driver.
Key functions:
ledflash3_write_reg- LED Flash 3 register writing functionledflash3_set_flash_current- LED Flash 3 set flash current functionledflash3_set_torch_current- LED Flash 3 set torch current function
Open Source
Code example
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* @file main.c
* @brief LED Flash 3 Click example
*
* # Description
* This app demonstrate flash mode on LED Flash 3 Click.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Turning the LED on for a second and off for another second.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "ledflash3.h"
static ledflash3_t ledflash3;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
ledflash3_cfg_t ledflash3_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.
ledflash3_cfg_setup( &ledflash3_cfg );
LEDFLASH3_MAP_MIKROBUS( ledflash3_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == ledflash3_init( &ledflash3, &ledflash3_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( LEDFLASH3_ERROR == ledflash3_default_cfg ( &ledflash3 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task ");
}
void application_task ( void )
{
ledflash3_strobe_pin( &ledflash3 );
Delay_ms( 2000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
