Beginner
10 min
0

Create stunning displays and interactive experiences with FT900 and MK64FX512VDC12

Visual experiences that leave a lasting impression

Matrix RGB Click with UNI-DS v8

Published Sep 04, 2023

Click board™

Matrix RGB Click

Development board

UNI-DS v8

Compiler

NECTO Studio

MCU

MK64FX512VDC12

Our solution is explicitly designed to provide the essential power and control required for driving 16x32 RGB LED matrices, offering a gateway to brilliant visual displays, animations, and real-time data presentations

A

A

Hardware Overview

How does it work?

Matrix RGB Click is based on the FT900, a complete System-on-Chip 32-bit RISC microcontroller from FTDI Chip. The FT900 runs at a frequency of 100MHz and is equipped with 256Kb Flash memory. The firmware inside the FT900 can be updated over unpopulated the 10-pin Prog header. Although this Click board™ is a 3.3V only, it still can use the 5V power rail of the mikroBUS™ socket to power the programmer if needed. The Matrix RGB Click can’t power the panel by itself, and neither does it have any power line connected to it. To power the RGB LED panel (or panels), you need to have an appropriate power adapter. The FT900 is connected to the A, B, and C row selections, and R1, G1, and B1 top row and R2, G2, and B2 bottom row shift registers (there are nine shift registers for each panel). The shift registers drive LED colors and rows effectively. In

addition, the FT900 is connected to the clock pins (CLK), latch pins (STB), and enable pins (OE) of the shift registers over the HUB75 RGB LED Panel connector. Row selection registers are used to make rewrites appear more fluent. Adding more than one RGB LED panel does not require extra pins; everything is done in the software. The FT900 on Matrix RGB Click uses an SPI serial interface to communicate with the host MCU over the mikroBUS™ socket, supporting data transfer with 25MHz. After filling the buffer with data of a text size, color, start row, start column, and then finally data, the host MCU will wait for the RDY pin to be set HIGH and then send the data to the FT900. After receiving data, the FT900 will perform the action based on the data it just received. In addition, the FT900 can be reset via the RST pin and put to sleep via the SLP pin. To use this Click

board™, you need to have one or more RGB panels and a power adapter, so make sure to buy them along with this Click board™. A complete Matrix RGB development kit is also available. It includes Matrix RGB click, 32x32 RGB LED Matrix Panel - 6mm pitch, 12V-3A power supply with EU plug (can power up to two panels). It is possible to drive more than 16 of these matrices, even up to 32, but flickering may occur. This Click board™ can only be operated with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ comes equipped with a library containing functions and an example code that can be used as a reference for further development.

Matrix RGB Click hardware overview image

Features overview

Development board

UNI-DS v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different STM32, Kinetis, TIVA, CEC, MSP, PIC, dsPIC, PIC32, and AVR MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, UNI-DS v8 provides a fluid and immersive working experience, allowing access anywhere and under any

circumstances at any time. Each part of the UNI-DS v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector. Communication options such as USB-UART, USB

HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. UNI-DS v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.

UNI-DS v8 horizontal image

Microcontroller Overview

MCU Card / MCU

default

Type

8th Generation

Architecture

ARM Cortex-M4

MCU Memory (KB)

640

Silicon Vendor

NXP

Pin count

121

RAM (Bytes)

196608

You complete me!

Accessories

The high-brightness RGB LED matrix panel features 1024 RGB LEDs meticulously arranged in a 32x32 grid on the front, ensuring stunning clarity and color accuracy. The LEDs are spaced at a 6mm grid, creating a seamless and captivating visual experience. The panel itself boasts a compact yet impactful size, measuring 190x190mm. The package includes a convenient IDC cable for seamless connectivity and a power cable to keep your display powered up. Upgrade your projects and designs with this versatile LED matrix panel, perfect for adding a touch of brilliance to any setting.

Matrix RGB Click accessories image

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
Reset
PC5
RST
SPI Chip Select
PB20
CS
SPI Clock
PB21
SCK
SPI Data OUT
PB23
MISO
SPI Data IN
PB22
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
Sleep Mode
PE6
PWM
Data-Ready
PC18
INT
NC
NC
TX
NC
NC
RX
NC
NC
SCL
NC
NC
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

Matrix RGB Click Schematic schematic

Step by step

Project assembly

Fusion for PIC v8 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the UNI-DS v8 as your development board.

Fusion for PIC v8 front image hardware assembly
GNSS2 Click front image hardware assembly
SiBRAIN for PIC32MZ1024EFK144 front image hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
v8 SiBRAIN Access MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
NECTO Compiler Selection Step Image hardware assembly
NECTO Output Selection Step Image hardware assembly
Necto image step 6 hardware assembly
Necto image step 7 hardware assembly
Necto image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Necto PreFlash Image hardware assembly

Track your results in real time

Application Output

After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.

UART Application Output Step 1

Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.

UART Application Output Step 2

In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".

UART Application Output Step 3

The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.

UART Application Output Step 4

Software Support

Library Description

This library contains API for Matrix RGB Click driver.

Key functions:

  • matrixrgb_set_power - Set Power

  • matrixrgb_set_brightness - Set Brightness

  • matrixrgb_write_pixel - Write Pixel

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 
 * \brief MatrixRGB Click example
 * 
 * # Description
 * This application is used for powering 16x32 RGB LED matrices.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Initializes driver, reset device and initializes
 * firmware depend on pattern used alongside with fonts
 * 
 * ## Application Task  
 * Test of panel brightnes, draws red cross on
 * the panel using pixel write function, writes text on panel using
 * write text function and finaly displays image on the panel.
 * 
 * \author MikroE Team
 *
 */
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "matrixrgb.h"
#include "matrixrgb_fonts.h"
#include "matrixrgb_images.h"

// ------------------------------------------------------------------ VARIABLES

static matrixrgb_t matrixrgb;
static log_t logger;

// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init ( void )
{
    log_cfg_t log_cfg;
    matrixrgb_cfg_t cfg;
    matrixrgb_font_t font_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.

    matrixrgb_cfg_setup( &cfg );
    MATRIXRGB_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    matrixrgb_init( &matrixrgb, &cfg );

    matrixrgb_device_reset( &matrixrgb );

    matrixrgb_pattern_settings ( &matrixrgb, MATRIXRGB_PATTERN_1_MAP_5MM, 1000 );
    matrixrgb_set_power( &matrixrgb, 1 );
    Delay_ms( 1000 );
    
    font_cfg.p_font       = Arial9x9;
    font_cfg.color        = 0xFFFF;
    font_cfg.orientation  = MATRIXRGB_FONT_HORIZONTAL;
    
    matrixrgb_set_font ( &matrixrgb, &font_cfg );
    
    matrixrgb_fill_screen( &matrixrgb, 0xFFFF );
    Delay_ms( 1000 );
}

void application_task ( )
{
    uint16_t test;

    // Brightness Test
    for ( test = 5; test < 50; test++ )
    {
        matrixrgb_set_brightness( &matrixrgb, test );
        Delay_ms( 50 );
    }

    for ( test = 50; test > 5; test-- )
    {
        matrixrgb_set_brightness( &matrixrgb, test );
        Delay_ms( 50 );
    }

    // Pixel Write Test
    matrixrgb_fill_screen( &matrixrgb, 0x0000 );
    for ( test = 0; test < 32; test++ )
    {
        matrixrgb_write_pixel( &matrixrgb, test, test, 0xF100 );
        Delay_ms( 100 );
    }
    for ( test = 32; test > 0; test-- )
    {
        matrixrgb_write_pixel( &matrixrgb, 31 - test, test, 0xF100 );
        Delay_ms( 100 );
    }
    Delay_ms( 2000 );
    

    //Text Write Test
    matrixrgb_fill_screen( &matrixrgb, 0x0000 );
    matrixrgb_write_text( &matrixrgb, "RGB", 6, 5 );
    matrixrgb_write_text( &matrixrgb, "Demo", 4, 20 );
    Delay_ms( 5000 );
    
    // Image Test
    matrixrgb_draw_image( &matrixrgb, mikroe_logo_32x32_bmp );
    Delay_ms( 1000 );
}

void main ( void )
{
    application_init( );

    for ( ; ; )
    {
        application_task( );
    }
}

// ------------------------------------------------------------------------ END

Additional Support

Resources