10 min

Upgrade your projects to the next level with PIC18F85K22

Expand, connect, create!

Terminal Click with UNI-DS v8

Published Nov 08, 2023

Click board™

Terminal Click

Development board



NECTO Studio



Experience seamless integration with our mikroBUS™ socket expansion solution, making your projects more versatile.



Hardware Overview

How does it work?

Terminal Click consists of a high-quality PCB that can be connected to the mikroBUS™ as any other click board. On the top of the Terminal click, a 2x8 pin header is placed. Each of the header pins is corresponding to a pin on the mikroBUS™ being used. These are simply wired in parallel. Thanks to the stacking headers, the connection with the click board™ remains firm and stable. Besides . Having this kind of stacking topology, allows for easy pin access and manipulation of the stacked click boards™, retaining a perfect connection quality at all times. When there's a need to attach

external equipment to the development system, the desired mikroBUS™ socket can be populated with Terminal click, allowing even more connections. This makes the stacking capacity almost unlimited. However, attention should be paid not to make the lines attached to the mikroBUS™ too long. In situations like this, the frequency of the communication might need to be stepped down a bit, in order to compensate for the longer mikroBUS™ signal lines. Lines of the mikroBUS™ to which Terminal click is attached, are shared through the top 16-pin header, which

mirrors pins of the connected mikroBUS™. Therefore, a care should be taken when working with the Terminal click and connecting an external device to it, because the same pins on the mikroBUS™ are shared, either for the communication (SPI, UART, I2C) or for some other purpose (RST, INT, or other pins used as GPIO). Since all the stacked click boards™ share the same power rails, a Terminal click also shares the power rails, which makes it compatible with any click board™ and development systems.

Terminal 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



8th Generation



MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


Used MCU Pins

mikroBUS™ mapper

Analog Output
SPI Chip Select
SPI Clock
Power Supply
PWM Input
I2C Clock
I2C Data
Power Supply

Take a closer look


Terminal 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 Terminal Click driver.

Key functions:

  • terminal_set_pin_high - This function sets the output voltage on the specified pin to high.

  • terminal_set_pin_low - This function sets the output voltage on the specified pin to low.

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 Terminal Click example
 * # Description
 * This example showcases how to initialize, configure and use the Terminal click. It is a simple
 * GPIO click which is used like an adapter for connecting and stacking other clicks and external
 * equimpent.
 * The demo application is composed of two sections :
 * ## Application Init 
 * This function initializes and configures the click and logger modules.
 * ## Application Task  
 * This function sets the output on all the pins (one by one) on the left side to high, going
 * from top to bottom and then does the same with the ones on the right side, after which it 
 * sets all pins to high and after one second sets them back to low.
 * \author MikroE Team
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "terminal.h"

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

static terminal_t terminal;
static log_t logger;

static digital_out_t *pin_addr[ 12 ] =
    &terminal.mosi,    // 0 MOSI
    &terminal.miso,    // 1 MISO
    &terminal.sck,     // 2 SCK
    &terminal.cs,      // 3 CS
    &terminal.rst,     // 4 RST
    &,      // 5 AN
    &terminal.pwm,     // 6 PWM
    &terminal.int_pin, // 7 INT
    &terminal.tx_pin,  // 8 TX
    &terminal.rx_pin,  // 9 RX
    &terminal.scl,     // 10 SCL
    &terminal.sda      // 11 SDA

// ------------------------------------------------------- ADDITIONAL FUNCTIONS

static void blink ( digital_out_t *pin ) 
    terminal_set_pin_high( pin );
    Delay_100ms( );
    terminal_set_pin_low( pin );

static void all_on ( )
   int i;

   for( i = 0; i < 12; i++ )
        terminal_set_pin_high( pin_addr[ i ] );

static void all_off ( )
   int i;

   for( i = 0; i < 12; i++ )
        terminal_set_pin_low( pin_addr[ i ] );

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

void application_init ( )
    log_cfg_t log_cfg;
    terminal_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.

    terminal_cfg_setup( &cfg );
    terminal_init( &terminal, &cfg );

void application_task ( )
    int i;

    for( i = 0; i < 12; i++ )
        blink( pin_addr[ i ] );

    all_on( );
    Delay_1sec( );
    all_off( );

void main ( )
    application_init( );

    for ( ; ; )
        application_task( );

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

Additional Support