30 min

Create a solution for clear and impactful messaging using JSS-5611BUB-21 and PIC32MZ1024EFK144

Red means readable: Large 7-segment brilliance

UT-L 7-SEG R Click with Fusion for PIC v8

Published Sep 09, 2023

Click board™

UT-L 7-SEG R Click

Development board

Fusion for PIC v8


NECTO Studio



Our large red 7-segment display is engineered to provide unmatched visibility, combining size and clarity to ensure your messages and data are conveyed with maximum impact and readability



Hardware Overview

How does it work?

UT-L 7-SEG R Click is based on two red JSS-5611BUB-21s, ultra-thin single-digit numeric displays from Ningbo Junsheng Electronics. This high-intensity and reliable blue source color device is made with Indium-Gallium-Nitride light-emitting diode conducting material. It features low current operation, high light output, excellent character appearance, and is mechanically rugged. The display can work on 5V and 3.3V and has a common anode as its internal design. It consists of seven red LED segments that form an 8

number and the eighth segment as a decimal point, or DP. The communication between the host MCU and the UT-L 7-SEG R Click is established via an industry-standard shift-register-plus-latch-type serial interface and the MAX6969, 16-port constant-current LED driver from Analog Devices. This driver has a 4-wire serial interface using four inputs and a data output. The output-enable input (OE) gates to all 16 outputs ON and OFF and is fast enough to be used as a PWM input for LED intensity control. The constant-current

outputs are programmed together to around 15mA using a single external resistor. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the PWR 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.

UT-L 7-SEG R Click hardware overview image

Features overview

Development board

Fusion for PIC 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 PIC, dsPIC, PIC24, and PIC32 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, Fusion for PIC v8 provides a fluid and immersive working experience, allowing access anywhere and under any

circumstances at any time. Each part of the Fusion for PIC v8 development board contains the components necessary for the most efficient operation of the same board. In addition to the advanced integrated CODEGRIP programmer/debugger module, which offers many valuable programming/debugging options and seamless integration with the Mikroe software environment, the board 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 are also included, including the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options (graphical and character-based LCD). Fusion for PIC 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.

Fusion for PIC v8 horizontal image

Microcontroller Overview

MCU Card / MCU



8th Generation



MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


Used MCU Pins

mikroBUS™ mapper

SPI Clock
Power Supply
Light Intensity Control
Power Supply

Take a closer look


UT-L 7-SEG R 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 Fusion for PIC v8 as your development board.

Fusion for PIC v8 front image hardware assembly
Buck 22 Click front image hardware assembly
SiBRAIN for PIC32MZ1024EFK144 front image hardware assembly
v8 SiBRAIN 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 UT-L 7-SEG R Click driver.

Key functions:

  • utl7segr_generic_write - This function writes a desired number of data bytes starting from the selected register by using SPI serial interface

  • utl7segr_display_state - This function turns display on and off.

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 UT-L7-SEGR Click example
 * # Description
 * The demo application shows basic usage of the UT 7 SEG display.
 * The demo application is composed of two sections :
 * ## Application Init 
 * Configuring clicks and log objects.
 * Settings the click in the default configuration.
 * ## Application Task  
 * Draws numbers from 0 to 99 on the screen.
 * @author Stefan Ilic

#include "board.h"
#include "log.h"
#include "utl7segr.h"

static utl7segr_t utl7segr;
static log_t logger;

void application_init ( void ) {
    log_cfg_t log_cfg;            /**< Logger config object. */
    utl7segr_cfg_t utl7segr_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.

    utl7segr_cfg_setup( &utl7segr_cfg );
    UTL7SEGR_MAP_MIKROBUS( utl7segr_cfg, MIKROBUS_1 );
    err_t init_flag  = utl7segr_init( &utl7segr, &utl7segr_cfg );
    if ( init_flag == SPI_MASTER_ERROR ) {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );

        for ( ; ; );

    utl7segr_default_cfg ( &utl7segr );
    log_info( &logger, " Application Task " );

void application_task ( void ) {  
    log_info( &logger, "---- Number counter ----" );

    for ( uint8_t cnt = 0; cnt < 100; cnt++ ) {
        utl7segr_display_number( &utl7segr, cnt, UTL7SEGR_DOT_LEFT );
        Delay_ms( 500 );

void main ( void ) {
    application_init( );

    for ( ; ; ) {
        application_task( );

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

Additional Support