Create your go-to solution for conveying critical information in limited spaces using JSS-5611BUB-21 and STM32F103RB
Clear messaging in miniature: Small 7-segment excellence
Published Oct 08, 2024
Click board™
UT-S 7-SEG R Click
Dev. board
Nucleo 64 with STM32F103RB MCU
Compiler
NECTO Studio
MCU
STM32F103RB
Experience the efficiency of a small-sized red 7-segment display designed to offer clarity and impact in a compact form, making your messages concise and impactful, even in the smallest spaces
A
A
Hardware Overview
How does it work?
The UT-S 7 SEG R drives two LED seven segment displays with the MAX6969, a LED driver integrated circuit, built to drive this kind of displays. The current through the segments is set as constant, by the resistor connected between the GND and the SET pin of the IC. In this case, it is kept at around 23 mA, as per segment requirements. The click can work with both 3.3V and 5V, selectable by the PWR SEL jumper.The used displays are SMD type DSM7UA20101 LED thin displays from VCC company, with medium sized (5.08mm/0.20") numerical characters. The characters can perfectly fit to a smaller dimension housing, and emit a red light.The click uses the SPI communication lines. The data received via the SPI serial interface is kept inside the
internal serial-to-parallel shift register. The reading process happens when the LE (load enable) pin is set to the logic HIGH state. When the LE pin of the click is altered to a logic LOW state, the content of the serial-to-parallel shift register is shifted to the sixteen output latches. The latches are connected to the output pins - from OUT0 to OUT15 respectively, driving the LED segments of the two 7 SEG displays.Outputs can be additionally turned off and on by the OE pin of the click, routed to the #OE pin of the MAX6969 IC itself. The signal is inverted by the means of the additional NPN transistor, so the logic LOW state of the OE pin will turn off the outputs, regardless of the inverted nature of
the #OE pin on the IC itself. The state change on OE pin will not alter the content of the latches, so it can be used to dim the LED segments by applying the PWM signal. For this reason, the OE pin is routed to the PWM pin of the mikroBUS.The serial data is also sent out via the SDO pin of the click during the rising edge of the CLK (clock) signal, so daisy chaining of several devices is also possible. Libraries supported with this click allow for an easy implementation in the code and the included example demonstrates the functionality of the click, using the functions that these libraries provide. The example can also be used as a reference or a starting point for any custom application design.
Features overview
Development board
Nucleo-64 with STM32F103RB 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-M3
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
20480
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 STM32F103RB 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 UT-S 7-SEG R Click driver.
Key functions:
uts7segr_generic_write- This function writes a desired number of data bytes starting from the selected register by using SPI serial interfaceuts7segr_display_state- This function display stateuts7segr_display_number- This function displays number on dispaly matrix.
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 UT-S7-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 Jelena Milosavljevic
*
*/
#include "board.h"
#include "log.h"
#include "uts7segr.h"
static uts7segr_t uts7segr;
static log_t logger;
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
uts7segr_cfg_t uts7segr_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 );
Delay_ms( 100 );
log_info( &logger, " Application Init " );
// Click initialization.
uts7segr_cfg_setup( &uts7segr_cfg );
UTS7SEGR_MAP_MIKROBUS( uts7segr_cfg, MIKROBUS_1 );
err_t init_flag = uts7segr_init( &uts7segr, &uts7segr_cfg );
if ( init_flag == SPI_MASTER_ERROR ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
uts7segr_default_cfg ( &uts7segr );
log_info( &logger, " Application Task " );
}
void application_task ( void ) {
log_info( &logger, "---- Number counter ----" );
for ( uint8_t cnt = 0; cnt < 100; cnt++ ) {
uts7segr_display_number( &uts7segr, cnt, UTS7SEGR_DOT_LEFT );
Delay_ms( 500 );
}
}
void main ( void ) {
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END
