30 min

Navigate your world with NEO-M8M and STM32F756ZG

Discover new horizons, effortlessly guided

GNSS 5 Click with UNI Clicker

Published Aug 30, 2023

Click board™

GNSS 5 Click

Development board

UNI Clicker


NECTO Studio



Stay ahead of the game and build smart navigation applications - optimized for speed, precision, and reliability



Hardware Overview

How does it work?

GNSS 5 Click is based on the NEO-M8N, a GNSS receiver module from u-blox. GNSS 5 click is designed to run on a 3.3V power supply. The click communicates with the target microcontroller over the I2C or UART interface, with additional functionality provided by the following pins on the mikroBUS™ line: RST, INT, and PWM. A USB interface (micro USB port), compatible with the USB version 2.0 FS (Full Speed, 12 Mbit/s), can be used for communication as an alternative to the UART. The USB port can also be used as a power supply if you need the click board™ to be a standalone device. The NEO-M8 series of concurrent GNSS modules are built on the

high-performing u-blox M8 GNSS engine in the industry-proven NEO form factor. The NEO-M8 series utilizes concurrent reception of up to three GNSS systems (GPS/Galileo with BeiDou or GLONASS), simultaneously recognizes multiple constellations, and provides outstanding positioning accuracy in scenarios involving urban canyons or weak signals. The u-blox NEO-M8 modules can also benefit from the u-blox AssistNow assistance service. The Online service provides GNNS broadcast parameters, e.g., ephemeris, almanac plus time, or rough position, to reduce the receiver’s time first to fix significantly and improve acquisition sensitivity. Hardware

Backup Mode - If the main supply voltage fails and a battery is connected to V_BCKP, parts of the receiver switch off, but the RTC still runs, providing a timing reference for the receiver. This operating mode enables all relevant data to be saved in the backup RAM to allow a hot or warm start later. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used as a reference for further development.

GNSS 5 Click hardware overview image

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.

UNI clicker double image

Microcontroller Overview

MCU Card / MCU



8th Generation


ARM Cortex-M7

MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


You complete me!


GNSS Active External Antenna is a unique multi-band type of antenna coming from u-Blox that is the perfect selection for high precision GNSS applications, which require highly accurate location abilities such as RTK. The ANN-MB-00 is a multi-band (L1, L2/E5b/B2I) active GNSS antenna with a 5m cable and SMA connector. The antenna supports GPS, GLONASS, Galileo, and BeiDou and includes a high-performance multi-band RHCP dual-feed patch antenna element, a built-in high-gain LNA with SAW pre-filtering, and a 5 m antenna cable with SMA connector, and is waterproof.

GNSS 5 Click accessories image

Used MCU Pins

mikroBUS™ mapper

Power Supply
External Interrupt Input
Timepulse Signal
I2C Clock
I2C Data

Take a closer look


GNSS 5 Click Schematic schematic

Step by step

Project assembly

UNI Clicker front image hardware assembly

Start by selecting your development board and Click board™. Begin with the UNI Clicker as your development board.

UNI Clicker front image hardware assembly
GNSS2 Click front image hardware assembly
SiBRAIN for STM32F745VG front image hardware assembly
Prog-cut hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
UNI Clicker 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 image step 5 hardware assembly
Necto image step 6 hardware assembly
Necto image step 7 hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

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.

Application Output Step 1

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™.

Application Output Step 3

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.

Application Output Step 4

Software Support

Library Description

This library contains API for GNSS 5 Click driver.

Key functions:

  • gnss5_generic_read - This function reads a desired number of data bytes by using UART serial interface

  • gnss5_clear_ring_buffers - This function clears UART tx and rx ring buffers

  • gnss5_parse_gngga - This function parses the GNGGA data from the read response buffer

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 GNSS 5 Click Example.
 * # Description
 * This example demonstrates the use of GNSS 5 click by reading and displaying
 * the GPS coordinates.
 * The demo application is composed of two sections :
 * ## Application Init
 * Initializes the driver and logger.
 * ## Application Task
 * Reads the received data, parses the GNGGA info from it, and once it receives the position fix
 * it will start displaying the coordinates on the USB UART.
 * ## Additional Function
 * - static void gnss5_clear_app_buf ( void )
 * - static err_t gnss5_process ( gnss5_t *ctx )
 * - static void gnss5_parser_application ( char *rsp )
 * @author Stefan Filipovic

#include "board.h"
#include "log.h"
#include "gnss5.h"
#include "string.h"


static gnss5_t gnss5;
static log_t logger;

static char app_buf[ PROCESS_BUFFER_SIZE ] = { 0 };
static int32_t app_buf_len = 0;

 * @brief GNSS 5 clearing application buffer.
 * @details This function clears memory of application buffer and reset its length.
 * @return None.
 * @note None.
static void gnss5_clear_app_buf ( void );

 * @brief GNSS 5 data reading function.
 * @details This function reads data from device and concatenates data to application buffer.
 * @param[in] ctx : Click context object.
 * See #gnss5_t object definition for detailed explanation.
 * @return @li @c  0 - Read some data.
 *         @li @c -1 - Nothing is read.
 * See #err_t definition for detailed explanation.
 * @note None.
static err_t gnss5_process ( gnss5_t *ctx );

 * @brief GNSS 5 parser application function.
 * @details This function parses GNSS data and logs it on the USB UART. It clears app and ring buffers
 * after successfully parsing data.
 * @param[in] ctx : Click context object.
 * See #gnss5_t object definition for detailed explanation.
 * @param[in] rsp Response buffer.
 * @return None.
 * @note None.
static void gnss5_parser_application ( gnss5_t *ctx, char *rsp );

void application_init ( void ) 
    log_cfg_t log_cfg;  /**< Logger config object. */
    gnss5_cfg_t gnss5_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.
    gnss5_cfg_setup( &gnss5_cfg );
    GNSS5_MAP_MIKROBUS( gnss5_cfg, MIKROBUS_1 );
    if ( UART_ERROR == gnss5_init( &gnss5, &gnss5_cfg ) ) 
        log_error( &logger, " Communication init." );
        for ( ; ; );
    log_info( &logger, " Application Task " );

void application_task ( void ) 
    if ( GNSS5_OK == gnss5_process( &gnss5 ) )
        if ( PROCESS_BUFFER_SIZE == app_buf_len )
            gnss5_parser_application( &gnss5, app_buf );

void main ( void ) 
    application_init( );

    for ( ; ; ) 
        application_task( );

static void gnss5_clear_app_buf ( void ) 
    memset( app_buf, 0, app_buf_len );
    app_buf_len = 0;

static err_t gnss5_process ( gnss5_t *ctx ) 
    char rx_buf[ PROCESS_BUFFER_SIZE ] = { 0 };
    int32_t rx_size = 0;
    rx_size = gnss5_generic_read( ctx, rx_buf, PROCESS_BUFFER_SIZE );
    if ( rx_size > 0 ) 
        int32_t buf_cnt = app_buf_len;
        if ( ( ( app_buf_len + rx_size ) > PROCESS_BUFFER_SIZE ) && ( app_buf_len > 0 ) ) 
            buf_cnt = PROCESS_BUFFER_SIZE - ( ( app_buf_len + rx_size ) - PROCESS_BUFFER_SIZE );
            memmove ( app_buf, &app_buf[ PROCESS_BUFFER_SIZE - buf_cnt ], buf_cnt );
        for ( int32_t rx_cnt = 0; rx_cnt < rx_size; rx_cnt++ ) 
            if ( rx_buf[ rx_cnt ] ) 
                app_buf[ buf_cnt++ ] = rx_buf[ rx_cnt ];
                if ( app_buf_len < PROCESS_BUFFER_SIZE )
        return GNSS5_OK;
    return GNSS5_ERROR;

static void gnss5_parser_application ( gnss5_t *ctx, char *rsp )
    char element_buf[ 100 ] = { 0 };
    if ( GNSS5_OK == gnss5_parse_gngga( rsp, GNSS5_GNGGA_LATITUDE, element_buf ) )
        static uint8_t wait_for_fix_cnt = 0;
        if ( strlen( element_buf ) > 0 )
            log_printf( &logger, "\r\n Latitude: %.2s degrees, %s minutes \r\n", element_buf, &element_buf[ 2 ] );
            gnss5_parse_gngga( rsp, GNSS5_GNGGA_LONGITUDE, element_buf );
            log_printf( &logger, " Longitude: %.3s degrees, %s minutes \r\n", element_buf, &element_buf[ 3 ] );
            memset( element_buf, 0, sizeof( element_buf ) );
            gnss5_parse_gngga( rsp, GNSS5_GNGGA_ALTITUDE, element_buf );
            log_printf( &logger, " Altitude: %s m \r\n", element_buf );
            wait_for_fix_cnt = 0;
            if ( wait_for_fix_cnt % 5 == 0 )
                log_printf( &logger, " Waiting for the position fix...\r\n\n" );
                wait_for_fix_cnt = 0;
        gnss5_clear_ring_buffers( ctx );
        gnss5_clear_app_buf( );

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

Additional Support