Ensure clear and visible information presentation with JS1-5213AE and MK64FX512VDC12
Illuminate your data with decimal precision
Published Jun 18, 2023
Click board™
7seg Click
Dev. board
UNI Clicker
Compiler
NECTO Studio
MCU
MK64FX512VDC12
Straightforward solution for incorporating numeric or hexadecimal displays into electronic applications
A
A
Hardware Overview
How does it work?
7seg Click is based on two seven-segment red LED displays, the JS1-5213AE from Ningbo Junsheng Electronics, driven by the SN74HC595D, an 8-bit serial-in, parallel-out shift register module from Texas Instruments. The JS1-5213AE display consists of seven LEDs arranged in a rectangular fashion, where each of the seven LEDs is called a segment because when illuminated, the segment forms part of a numerical digit (both decimal and hex) to be displayed. With dimensions of 17.5x12.4x8.4mm and a decimal point, these displays are also characterized by a wide viewing
range and ultra-segment intensity. This board is suitable for numeric or hexadecimal displays, such as clocks, timers, counters, or similar applications. As mentioned, this Click board™ communicates with MCU through a standard SPI interface across SN74HC595D with a maximum frequency of 5MHz. In addition to the SPI communication, the 7seg Click uses two additional pins for the direct shift register override function and display activation routed to the RST and PWM pins of the mikroBUS™ socket. Setting the PWM pin to logic high state turns the displays ON. After that, users
can see the functionality of the 7seg click by showing numbers or characters on the left and right displays. 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
UNI Clicker is a compact development board designed as a complete solution that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It supports a wide range of microcontrollers, such as different ARM, PIC32, dsPIC, PIC, and AVR from various vendors like Microchip, ST, NXP, and TI (regardless of their number of pins), four mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a debugger/programmer connector, and two 26-pin headers for interfacing with external electronics. Thanks to innovative manufacturing technology, it allows you to build
gadgets with unique functionalities and features quickly. Each part of the UNI Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the UNI Clicker programming method, using a third-party programmer or CODEGRIP/mikroProg connected to onboard JTAG/SWD header, the UNI Clicker board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Type-C (USB-C) connector, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or using a Li-Po/Li
Ion battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board (plus USB HOST/DEVICE), including the well-established mikroBUS™ socket, a standardized socket for the MCU card (SiBRAIN standard), and several user-configurable buttons and LED indicators. UNI 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
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
640
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
196608
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 UNI Clicker 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 7seg Click driver.
Key functions:
c7seg_display_mode- This function sets display state for 7seg Clickc7seg_write_data_number- This function writes left and right number on 7seg displayc7seg_write_data_character- This function writes left and right character on 7seg display
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
* \brief 7seg Click example
*
* # Description
* Example code consist of two sections: AppInit and AppTask,
* and shows number or character on 7seg display.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Application Init performs Logger and Click Initialization.
*
* ## Application Task
* Application Task shows functionality of the 7seg Click,
* shows number or character on left and right display.
*
* \author Mihajlo Djordjevic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "c7seg.h"
// ------------------------------------------------------------------ VARIABLES
static c7seg_t c7seg;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
c7seg_cfg_t 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.
c7seg_cfg_setup( &cfg );
C7SEG_MAP_MIKROBUS( cfg, MIKROBUS_1 );
c7seg_init( &c7seg, &cfg );
c7seg_default_cfg ( &c7seg );
Delay_ms ( 1000 );
}
void application_task ( void )
{
uint8_t counter;
c7seg_display_mode( &c7seg, C7SEG_DISPLAY_ON );
Delay_ms ( 1000 );
for ( counter = 0; counter < 9; counter ++ )
{
c7seg_write_data_number( &c7seg, counter, counter + 1 );
Delay_ms ( 1000 );
}
Delay_ms ( 1000 );
for ( counter = 65; counter < 90; counter ++ )
{
c7seg_write_data_character( &c7seg, counter, counter + 1 );
Delay_ms ( 1000 );
}
Delay_ms ( 1000 );
c7seg_display_mode( &c7seg, C7SEG_DISPLAY_OFF );
Delay_ms ( 1000 );
}
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;
}
// ------------------------------------------------------------------------ END
