Provide dynamic and eye-catching visual displays for information or advertising
A
A
Hardware Overview
How does it work?
2x4 RGB Click is based on an array of 2x4 RGB LEDs (WL-ICLED 1312121320437) from Würth Elektronik, specially designed for dynamic and colorful lighting applications. These LEDs incorporate an integrated circuit (IC), often called addressable or smart LEDs, allowing for individual control of each diode's red, green, and blue components through pulse width modulation (PWM). This enables precise control over color mixing, creating a broad spectrum of color outputs. To ensure compatibility with both 3.3V and 5V logic systems, the Click board™ features the LSF0102 voltage translator, which provides seamless control
of the LEDs regardless of the MCU's logic level, ensuring reliable performance in various system configurations. 2x4 RGB Click is designed in a unique format supporting the newly introduced MIKROE feature called "Click Snap." Unlike the standardized version of Click boards, this feature allows the main IC area to become movable by breaking the PCB, opening up many new possibilities for implementation. Thanks to the Snap feature, the 1312121320437s can operate autonomously by accessing its signals directly on the pins marked 1-8. Additionally, the Snap part includes a specified and fixed screw hole position,
enabling users to secure the Snap board in their desired location, and an unpopulated header labeled J1 at the top, allowing for daisy-chaining and control of multiple Snap units in a series. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC 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 STM32C031C6 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)
32
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
12K
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
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 2x4 RGB Click driver.
Key functions:
c2x4rgb_set_leds_intensity
- This function sets the brightness and current gain level of all LEDs in the led matrix.c2x4rgb_set_led_color
- This function sets the color of the selected LED in the LED matrix.c2x4rgb_write_led_matrix
- This function writes the LED matrix data from the click context object.
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 2x4 RGB Click Example.
*
* # Description
* This example demonstrates the use of 2x4 RGB click board by cycling through
* a set of colors, gradually increasing the brightness of each LED in a sequence,
* and then decreasing the brightness before moving on to the next color in the array.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration which sets
* the LEDs brightness and current gain to a minimum and the color to black (all LEDs off).
*
* ## Application Task
* Cycles through a set of colors, gradually increases the brightness of each LED
* in a sequence, and then decreases the brightness before moving on to the next
* color in the array. The current color's name and RGB value are logged to the USB UART.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "c2x4rgb.h"
#include "c2x4rgb_delays.h"
static c2x4rgb_t c2x4rgb; /**< 2x4 RGB Click driver object. */
static log_t logger; /**< Logger object. */
static c2x4rgb_color_t color[ C2X4RGB_NUM_COLORS ] =
{
{ C2X4RGB_COLOR_BLACK, "BLACK" },
{ C2X4RGB_COLOR_WHITE, "WHITE" },
{ C2X4RGB_COLOR_RED, "RED" },
{ C2X4RGB_COLOR_LIME, "LIME" },
{ C2X4RGB_COLOR_BLUE, "BLUE" },
{ C2X4RGB_COLOR_YELLOW, "YELLOW" },
{ C2X4RGB_COLOR_CYAN, "CYAN" },
{ C2X4RGB_COLOR_MAGENTA, "MAGENTA" },
{ C2X4RGB_COLOR_SILVER, "SILVER" },
{ C2X4RGB_COLOR_GRAY, "GRAY" },
{ C2X4RGB_COLOR_MAROON, "MAROON" },
{ C2X4RGB_COLOR_OLIVE, "OLIVE" },
{ C2X4RGB_COLOR_GREEN, "GREEN" },
{ C2X4RGB_COLOR_PURPLE, "PURPLE" },
{ C2X4RGB_COLOR_TEAL, "TEAL" },
{ C2X4RGB_COLOR_NAVY, "NAVY" }
};
/**
* @brief 2x4 RGB logic zero function.
* @details This function toggles the data pin with exact high and low time pulse for logic zero.
* @return None.
* @note None.
*/
static void c2x4rgb_logic_zero ( void );
/**
* @brief 2x4 RGB logic one function.
* @details This function toggles the data pin with exact high and low time pulse for logic one.
* @return None.
* @note None.
*/
static void c2x4rgb_logic_one ( void );
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
c2x4rgb_cfg_t c2x4rgb_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.
c2x4rgb_cfg_setup( &c2x4rgb_cfg );
C2X4RGB_MAP_MIKROBUS( c2x4rgb_cfg, MIKROBUS_1 );
if ( DIGITAL_OUT_UNSUPPORTED_PIN ==
c2x4rgb_init( &c2x4rgb, &c2x4rgb_logic_zero, &c2x4rgb_logic_one, &c2x4rgb_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( C2X4RGB_ERROR == c2x4rgb_default_cfg ( &c2x4rgb ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
static uint32_t color_num = 0;
static int8_t led_cnt = 0;
static int8_t brightness = 0;
log_printf( &logger, " Color: %s [%.6LX]\r\n\n", color[ color_num ].name, color[ color_num ].rgb );
Delay_ms ( 100 );
c2x4rgb_set_leds_intensity ( &c2x4rgb, C2X4RGB_LED_BRIGHTNESS_MIN, C2X4RGB_LED_CURRENT_GAIN_DEFAULT );
for ( led_cnt = C2X4RGB_LED_7; led_cnt >= C2X4RGB_LED_0; led_cnt-- )
{
c2x4rgb_set_led_color ( &c2x4rgb, led_cnt, color[ color_num ].rgb );
c2x4rgb_write_led_matrix ( &c2x4rgb );
Delay_ms ( 100 );
}
for ( brightness = C2X4RGB_LED_BRIGHTNESS_MIN; brightness < C2X4RGB_LED_BRIGHTNESS_MAX; brightness++ )
{
c2x4rgb_set_leds_intensity ( &c2x4rgb, brightness, C2X4RGB_LED_CURRENT_GAIN_DEFAULT );
c2x4rgb_write_led_matrix ( &c2x4rgb );
Delay_ms ( 50 );
}
for ( brightness = C2X4RGB_LED_BRIGHTNESS_MAX; brightness >= C2X4RGB_LED_BRIGHTNESS_MIN; brightness-- )
{
c2x4rgb_set_leds_intensity ( &c2x4rgb, brightness, C2X4RGB_LED_CURRENT_GAIN_DEFAULT );
c2x4rgb_write_led_matrix ( &c2x4rgb );
Delay_ms ( 50 );
}
if ( ++color_num >= C2X4RGB_NUM_COLORS )
{
color_num = 0;
}
}
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;
}
static void c2x4rgb_logic_zero ( void )
{
hal_ll_gpio_set_pin_output( &c2x4rgb.din.pin );
DELAY_TOH;
hal_ll_gpio_clear_pin_output( &c2x4rgb.din.pin );
DELAY_TOL;
}
static void c2x4rgb_logic_one ( void )
{
hal_ll_gpio_set_pin_output( &c2x4rgb.din.pin );
DELAY_T1H;
hal_ll_gpio_clear_pin_output( &c2x4rgb.din.pin );
DELAY_T1L;
}
// ------------------------------------------------------------------------ END