Create a solution for clear and impactful messaging using JSS-5611BUB-21 and PIC32MZ1024EFH064
Red means readable: Large 7-segment brilliance
Published Sep 09, 2023
Click board™
UT-L 7-SEG R Click
Dev Board
PIC32MZ clicker
Compiler
NECTO Studio
MCU
PIC32MZ1024EFH064
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
A
A
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.
Features overview
Development board
PIC32MZ Clicker is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit PIC32MZ microcontroller with FPU from Microchip, a USB connector, LED indicators, buttons, a mikroProg connector, and a header for interfacing with external electronics. Thanks to its compact design with clear and easy-recognizable silkscreen markings, it provides a fluid and immersive working experience, allowing access anywhere and under
any circumstances. Each part of the PIC32MZ Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the PIC32MZ Clicker programming method, using USB HID mikroBootloader, or through an external mikroProg connector for PIC, dsPIC, or PIC32 programmer, the Clicker board also includes a clean and regulated power supply module for the development kit. The USB Micro-B connection can provide up to 500mA of current, which is more than enough to operate all onboard
and additional modules. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several buttons and LED indicators. PIC32MZ Clicker is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC32
MCU Memory (KB)
1024
Silicon Vendor
Microchip
Pin count
64
RAM (Bytes)
524288
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the PIC32MZ clicker as your development board.
Track your results in real time
Application Output
After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.
After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.
Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.
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 interfaceutl7segr_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
