Illuminate your projects with precision and power using AS1170, XPCWHT-L1-R250-00A01 and STM32F030R8
High-performance LED flash and torch solution
Published Sep 25, 2024
Click board™
LED Flash 4 Click
Dev Board
Nucleo-64 with STM32F030R8 MCU
Compiler
NECTO Studio
MCU
STM32F030R8
Provide powerful and efficient lighting for various portable applications
A
A
Hardware Overview
How does it work?
LED Flash 4 Click is based on the AS1170, a high-current LED driver from ams OSRAM, designed for high-performance LED flash and torch applications. The AS1170 is an inductive, highly efficient DC-DC step-up converter that operates with an external power supply from 2.7V up to 4.4V at a fixed frequency of 4MHz. It includes two internal current sinks, enabling the independent control of two onboard flash LEDs (XPCWHT-L1-R250-00A01), which deliver exceptional light quality. With its soft Start-Up feature, the AS1170 integrates easily into noise-sensitive RF systems. This chip has several protection functions, including flash timeout, overvoltage, overtemperature, undervoltage, and short circuit protection, ensuring reliable operation even in demanding environments. This Click board™ is ideal for use as a flash or torch,
providing significant advantages such as precise control over LED brightness and extended battery life due to the efficient power conversion. LED Flash 4 Click uses a standard 2-wire I2C communication protocol, allowing the host MCU to control the AS1170 with ease. The I2C interface supports clock frequencies up to 400kHz, with the I2C address selectable via the onboard ADDR SEL jumpers, providing flexibility in communication setup. Additionally, the board features an STB (strobe) pin and a digital signal with a pulldown resistor, which controls the strobe time for the flash function, enabling precise timing and synchronization of the LED flash. The AS1170 also incorporates a hardware automatic shutdown mode that activates if no I2C clock signal is detected for 100ms, eliminating the need for an additional
enable input to power down the device when the system shuts down. Besides a VIN terminal for external supplying the AS1170, the board also includes a VOUT terminal that allows the AS1170 to power a 5V system, such as an audio amplifier. This operating mode can be selected via the I2C interface by setting the corresponding register bit (const_v_mode=1). In this mode, the current sinks are disabled, and the LEDs cannot be switched on, making it suitable for powering external devices. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
Nucleo-64 with STM32F030R8 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)
64
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
8192
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 STM32F030R8 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 4 Click driver.
Key functions:
ledflash4_set_led1_current- This function sets the LED1 maximum current in mA.ledflash4_set_led2_current- This function sets the LED2 maximum current in mA.ledflash4_set_stb_pin- This function sets the strobe (STB) pin logic 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 LED Flash 4 Click example
*
* # Description
* This example demonstrates the use of LED Flash 4 click board by toggling
* the LEDs output.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration which sets
* the click in flash mode with the LED current of 50mA for both LEDs. The strobe
* pin is set to active high level type.
* ## Application Task
* Toggles the LEDs output every 2 seconds using the strobe pin, and displays the LEDs
* state on the USB UART.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "ledflash4.h"
static ledflash4_t ledflash4;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
ledflash4_cfg_t ledflash4_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.
ledflash4_cfg_setup( &ledflash4_cfg );
LEDFLASH4_MAP_MIKROBUS( ledflash4_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == ledflash4_init( &ledflash4, &ledflash4_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( LEDFLASH4_ERROR == ledflash4_default_cfg ( &ledflash4 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
log_printf( &logger, " LEDs ON\r\n\n" );
ledflash4_set_stb_pin ( &ledflash4, LEDFLASH4_STROBE_PIN_HIGH );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf( &logger, " LEDs OFF\r\n\n" );
ledflash4_set_stb_pin ( &ledflash4, LEDFLASH4_STROBE_PIN_LOW );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
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
