Experience the future of lighting innovation with MCP1643 and STM32F091RC
Light up your world!
Published Feb 26, 2024
Click board™
LED Driver 2 Click
Dev. board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
With our LED driver solution and integrated LED, you can effortlessly enhance user experiences, create custom lighting effects, and ensure clear and intuitive status indications in your projects.
A
A
Hardware Overview
How does it work?
LED driver 2 Click is based on the MCP1643, an LED constant current regulator from Microchip. It is a compact, high-efficiency, fixed frequency, synchronous step-up converter optimized to drive one LED with a constant current. It can be powered by a two-cell alkaline/NiMH/NiCd battery (2.4V) or via the mikroBUS™ power supply pins. LED Driver 2 click also features a 3W High-brightness LED by QT-Brightek. This LED can be dimmed by applying the variable duty cycle PWM signal to the EN pin of the MCP1643 regulator through the PWM pin of the mikroBUS™. MCP1643 is a boost regulator with a low voltage reference of 120mV (VFB). The main feature of the regulator is that it is optimized to keep the current running through the LED - constant by regulating the voltage across the feedback resistor. The VFB pin regulates the voltage across the feedback
resistor to 120 mV, keeping the output LED current regulated. As the feedback resistor (R2 on the provided schematic) is connected to the FB pin and its resistance is 0.4Ω, the maximum current through the LED can easily be calculated by using the following formula: ILED = VFB/R2 = 120mV/0.4Ω = 300mA. The voltage drop on the feedback resistor has to be low to avoid dissipation. In the case of MCP1643, this voltage is set to 120mV, ensuring no dissipation issues. The onboard VIN SEL SMD jumper offers the selection of the input voltage source: it can be set to use a two-cell NiMH battery connected to the VIN terminal (2.4V) or the power supply pin from the mikroBUS™. The voltage from the mikroBUS™ can be set with the VCCIO SMD jumper to either 5V or 3.3V. Since the forward voltage on the high-power LED is 3.2V, the click board comes equipped with the MCP1826,
an LDO regulator by Microchip, which is used to drop the selected mikroBUS™ voltage down to around 2.4V so that the MPC1643 input voltage requirements are met. High brightness 3W LED is already attached to the output of the MCP1643, and it comes soldered on the board, so the circuit is ready to be used immediately. The LED brightness can be regulated by applying a variable duty cycle PWM signal to the EN pin of the MCP1643 regulator (routed to the PWM pin on the mikroBUS™). This changes the current running through the LED linearly, from 0 to the value set by the resistor, depending on the PWM cycle. 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 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
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 LED driver 2 Click driver.
Key functions:
leddriver2_set_duty_cycle- This function sets the PWM duty cycleleddriver2_pwm_stop- This function stops PWM moduleleddriver2_pwm_start- This function starts PWM module
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 LedDriver2 Click example
*
* # Description
* This app enables usage of compact, high-efficiency, fixed frequency,
* synchronous step-up converter, optimized to drive one LED with the constant current.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enables - GPIO,
* PWM initialization set PWM duty cycle and start PWM.
*
* ## Application Task
* This is an example that demonstrates the use of the LED Driver 2 Click board.
* This example shows the automatic control halogen bulb light intensity,
* the first intensity of light is rising and then the intensity of light is falling.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* \author Nikola Peric
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "leddriver2.h"
// ------------------------------------------------------------------ VARIABLES
static leddriver2_t leddriver2;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
leddriver2_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.
leddriver2_cfg_setup( &cfg );
LEDDRIVER2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
leddriver2_init( &leddriver2, &cfg );
leddriver2_pwm_start( &leddriver2 );
}
void application_task ( void )
{
static int8_t duty_cnt = 1;
static int8_t duty_inc = 1;
float duty = duty_cnt / 10.0;
leddriver2_set_duty_cycle ( &leddriver2, duty );
log_printf( &logger, "> Duty: %d%%\r\n", ( uint16_t )( duty_cnt * 10 ) );
Delay_ms( 500 );
if ( 10 == duty_cnt )
{
duty_inc = -1;
}
else if ( 0 == duty_cnt )
{
duty_inc = 1;
}
duty_cnt += duty_inc;
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:LED Drivers
