Intermediate
20 min

Increase accuracy and reliability in global positioning across different regions and conditions with Mosaic-x5 and PIC32MZ2048EFH100

Compact global navigation satellite system (GNSS) receiver

Mosaic Click with Flip&Click PIC32MZ

Published Apr 09, 2024

Click board™

Mosaic Click

Development board

Flip&Click PIC32MZ

Compiler

NECTO Studio

MCU

PIC32MZ2048EFH100

Provide precise navigation and location-based applications through high-quality global positioning, using multi-band and multi-constellation GNSS satellite signal tracking

A

A

Hardware Overview

How does it work?

Mosaic Click is based on the Mosaic-X5, a compact GNSS receiver from Septentrio. This receiver offers centimeter-level accuracy across multiple bands and satellite constellations such as GPS, GLONASS, Beidou, Galileo, and NavIC. It integrates AIM+ technology for advanced interference mitigation and anti-spoofing, providing unmatched reliability and precision. This technology can neutralize diverse signal interferences, ranging from simple, continuous narrowband signals to complex wideband and pulsed jammers. Designed for mass-market applications like robotics and autonomous technologies, this solution not only ensures low power consumption but also offers a wide range of interface options and delivers RTK positioning. Communication between the Mosaic-X5 and the host MCU is made through a UART interface, using the standard UART RX and TX pins and hardware flow control pins (CTS/RTS). The module communicates at 115200bps by default, allowing efficient data exchange. This Click board™ also incorporates a reset pin (RST) for direct module resetting and a ready indicator (RDY) that signals the module's operational status through logical high

(active) or low (standby or reset) states. Furthermore, the module supports USB connectivity in device mode, adhering to the USB 2.0 standard for high-speed data transfers (up to 480Mbps). It includes options for USB power achieved by an LDO (the MCP1826) or an alternative power switch (the TPS22965), each ensuring the required 3.3V for normal module operation. In addition to the USB interface, it is also equipped with a microSD card slot for external data logging, which can be controlled via a LOG button. This button enables the toggling of SD card logging and manages the card's mounting status, which can be monitored through a green LED indicator marked LOG. If the LOG button is pressed for 100ms to 5 seconds, it toggles SD Card logging ON and OFF. Holding this button for more than 5 seconds and then releasing it unmounts the SD card if it is mounted, and vice versa. The green LOG LED indicator can check the SD card mount status. In addition to the LOG LED, the board also features a general-purpose user-configurable red LED, a yellow PPS (Pulse Per Second) LED, and four test points. TP1 and TP2 are two event timers that can be used to time tag external events with a

time resolution of 20ns, while TR3 and TP4 present the same functions as ON/OFF and Reset features. It is also possible to power off the module with the ON/OFF button and to toggle it between active and standby mode. However, this abrupt power interruption could cause data losses when logging on an external SD card. The board features a u.Fl connector for a GNSS antenna, like the Active GPS Antenna that MIKROE offers, in combination with an IPEX-SMA cable for flexible and efficient connectivity options. In addition, the user can easily choose the external antenna's power supply by choosing between 3.3V and 5V on the VANT SEL jumper. This Click board™ can operate with both 3.3V and 5V logic voltage levels selected via the VCC SEL jumper. Given that the Mosaic-X5 module operates at 3.3V, a logic-level translator, TXB0106, is also used for proper operation and an accurate signal-level translation. 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.

Mosaic Click hardware overview image

Features overview

Development board

Flip&Click PIC32MZ 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 comes with an onboard 32-bit PIC32MZ microcontroller, the PIC32MZ2048EFH100 from Microchip, four mikroBUS™ sockets for Click board™ connectivity, two USB connectors, LED indicators, buttons, debugger/programmer connectors, and two headers compatible with Arduino-UNO pinout. Thanks to innovative manufacturing technology,

it allows you to build gadgets with unique functionalities and features quickly. Each part of the Flip&Click PIC32MZ development kit contains the components necessary for the most efficient operation of the same board. In addition, there is the possibility of choosing the Flip&Click PIC32MZ programming method, using the chipKIT bootloader (Arduino-style development environment) or our USB HID bootloader using mikroC, mikroBasic, and mikroPascal for PIC32. This kit includes a clean and regulated power supply block through the USB Type-C (USB-C) connector. All communication

methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, user-configurable buttons, and LED indicators. Flip&Click PIC32MZ development kit allows 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.

Flip&Click PIC32MZ double image

Microcontroller Overview

MCU Card / MCU

default

Architecture

PIC32

MCU Memory (KB)

2048

Silicon Vendor

Microchip

Pin count

100

RAM (Bytes)

524288

You complete me!

Accessories

Active GPS antenna is designed to enhance the performance of your GPS and GNSS Click boards™. This external antenna boasts a robust construction, making it ideal for various weather conditions. With a frequency range of 1575.42MHz and a 50Ohm impedance, it ensures reliable signal reception. The antenna delivers a gain of greater than -4dBic within a wide angular range, securing over 75% coverage. The bandwidth of +/- 5MHz further guarantees precise data acquisition. Featuring a Right-Hand Circular Polarization (RHCP), this antenna offers stable signal reception. Its compact dimensions of 48.53915mm and a 2-meter cable make it easy to install. The magnetic antenna type with an SMA male connector ensures a secure and convenient connection. If you require a dependable external antenna for your locator device, our active GPS antenna is the perfect solution.

Mosaic Click accessories 1 image

IPEX-SMA cable is a type of RF (radio frequency) cable assembly. "IPEX" refers to the IPEX connector, a miniature coaxial connector commonly used in small electronic devices. "SMA" stands for SubMiniature Version A and is another coaxial connector commonly used in RF applications. An IPEX-SMA cable assembly has an IPEX connector on one end and an SMA connector on the other, allowing it to connect devices or components that use these specific connectors. These cables are often used in applications like WiFi or cellular antennas, GPS modules, and other RF communication systems where a reliable and low-loss connection is required.

Mosaic Click accessories 2 image

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
Module Reset / ID SEL
RE2
RST
UART CTS / ID COMM
RA0
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
Module Ready Indicator
RC14
PWM
UART RTS
RD9
INT
UART TX
RE3
TX
UART RX
RG9
RX
NC
NC
SCL
NC
NC
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

Mosaic Click Schematic schematic

Step by step

Project assembly

Flip&Click PIC32MZ front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Flip&Click PIC32MZ as your development board.

Flip&Click PIC32MZ front image hardware assembly
GNSS2 Click front image hardware assembly
Prog-cut hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
Flip&Click PIC32MZ MB1 Access - 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
Flip&Click PIC32MZ MCU step 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 Mosaic Click driver.

Key functions:

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

  • mosaic_enable_nmea_output - This function enables the NMEA output with the selected message parameters and an output interval

  • mosaic_parse_gga - This function parses the GGA 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 Mosaic Click Example.
 *
 * # Description
 * This example demonstrates the use of Mosaic click by reading and displaying
 * the GNSS coordinates.
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initializes the driver, reads the NMEA version, and enables the NMEA output.
 *
 * ## Application Task
 * Reads the received data, parses the NMEA GGA info from it, and once it receives 
 * the position fix it will start displaying the coordinates on the USB UART.
 *
 * ## Additional Function
 * - static void mosaic_clear_app_buf ( void )
 * - static void mosaic_log_app_buf ( void )
 * - static err_t mosaic_process ( mosaic_t *ctx )
 * - static err_t mosaic_wait_prompt ( mosaic_t *ctx )
 * - static void mosaic_parser_application ( uint8_t *rsp )
 *
 * @author Stefan Filipovic
 *
 */

#include "board.h"
#include "log.h"
#include "mosaic.h"

// Application buffer size
#define APP_BUFFER_SIZE             500
#define PROCESS_BUFFER_SIZE         200

static mosaic_t mosaic;
static log_t logger;

static uint8_t app_buf[ APP_BUFFER_SIZE ] = { 0 };
static int32_t app_buf_len = 0;

/**
 * @brief Mosaic clearing application buffer.
 * @details This function clears memory of application buffer and reset its length.
 * @note None.
 */
static void mosaic_clear_app_buf ( void );

/**
 * @brief Mosaic log application buffer.
 * @details This function logs data from application buffer to USB UART.
 * @note None.
 */
static void mosaic_log_app_buf ( void );

/**
 * @brief Mosaic data reading function.
 * @details This function reads data from device and concatenates data to application buffer. 
 * @param[in] ctx : Click context object.
 * See #mosaic_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 mosaic_process ( mosaic_t *ctx );

/**
 * @brief Mosaic wait prompt function.
 * @details This function waits for a "COM1>" prompt string to appear on UART which indicates
 * the device is ready to receive commands.
 * @param[in] ctx : Click context object.
 * See #mosaic_t object definition for detailed explanation.
 * @return @li @c  0 - Prompt (COM1>) read successfully.
 *         @li @c -2 - Timeout error.
 * See #err_t definition for detailed explanation.
 * @note None.
 */
static err_t mosaic_wait_prompt ( mosaic_t *ctx );

/**
 * @brief Mosaic parser application.
 * @param[in] rsp Response buffer.
 * @details This function logs GNSS data on the USB UART.
 * @return None.
 * @note None.
 */
static void mosaic_parser_application ( uint8_t *rsp );

void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    mosaic_cfg_t mosaic_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.
    mosaic_cfg_setup( &mosaic_cfg );
    MOSAIC_MAP_MIKROBUS( mosaic_cfg, MIKROBUS_1 );
    if ( UART_ERROR == mosaic_init( &mosaic, &mosaic_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }

    if ( MOSAIC_OK != mosaic_wait_prompt( &mosaic ) )
    {
        log_error( &logger, " No connection prompt detected." );
        for ( ; ; );
    }
    mosaic_log_app_buf( );
    mosaic_clear_app_buf( );
    Delay_ms ( 100 );

    mosaic_send_cmd( &mosaic, MOSAIC_CMD_GET_NMEA_VERSION );
    mosaic_wait_prompt( &mosaic );
    mosaic_log_app_buf( );
    mosaic_clear_app_buf( );
    Delay_ms ( 100 );

    mosaic_enable_nmea_output( &mosaic, MOSAIC_SNO_MESSAGES_GGA, MOSAIC_SNO_INTERVAL_SEC1 );
    mosaic_wait_prompt( &mosaic );
    mosaic_log_app_buf( );
    mosaic_clear_app_buf( );
    Delay_ms ( 100 );
    
    log_info( &logger, " Application Task " );
}

void application_task ( void ) 
{
    mosaic_process( &mosaic );
    if ( app_buf_len > ( sizeof ( MOSAIC_NMEA_GGA ) + MOSAIC_GGA_ELEMENT_SIZE ) ) 
    {
        mosaic_parser_application( app_buf );
    }
}

int main ( void ) 
{
    application_init( );
    
    for ( ; ; ) 
    {
        application_task( );
    }

    return 0;
}

static void mosaic_clear_app_buf ( void ) 
{
    memset( app_buf, 0, app_buf_len );
    app_buf_len = 0;
}

static void mosaic_log_app_buf ( void )
{
    for ( int32_t buf_cnt = 0; buf_cnt < app_buf_len; buf_cnt++ )
    {
        log_printf( &logger, "%c", app_buf[ buf_cnt ] );
    }
    log_printf( &logger, "\r\n" );
}

static err_t mosaic_process ( mosaic_t *ctx ) 
{
    uint8_t rx_buf[ PROCESS_BUFFER_SIZE ] = { 0 };
    int32_t overflow_bytes = 0;
    int32_t rx_cnt = 0;
    int32_t rx_size = mosaic_generic_read( ctx, rx_buf, PROCESS_BUFFER_SIZE );
    if ( ( rx_size > 0 ) && ( rx_size <= APP_BUFFER_SIZE ) ) 
    {
        if ( ( app_buf_len + rx_size ) > APP_BUFFER_SIZE ) 
        {
            overflow_bytes = ( app_buf_len + rx_size ) - APP_BUFFER_SIZE;
            app_buf_len = APP_BUFFER_SIZE - rx_size;
            memmove ( app_buf, &app_buf[ overflow_bytes ], app_buf_len );
            memset ( &app_buf[ app_buf_len ], 0, overflow_bytes );
        }
        for ( rx_cnt = 0; rx_cnt < rx_size; rx_cnt++ ) 
        {
            if ( rx_buf[ rx_cnt ] ) 
            {
                app_buf[ app_buf_len++ ] = rx_buf[ rx_cnt ];
            }
        }
        return MOSAIC_OK;
    }
    return MOSAIC_ERROR;
}

static err_t mosaic_wait_prompt ( mosaic_t *ctx )
{
    uint32_t timeout_cnt = 0;
    uint32_t timeout = 120000;
    mosaic_process( ctx );
    while ( 0 == strstr( app_buf, MOSAIC_PROMPT_CMD ) )
    {
        mosaic_process( ctx );
        if ( timeout_cnt++ > timeout )
        {
            mosaic_clear_app_buf( );
            return MOSAIC_ERROR_TIMEOUT;
        }
        Delay_ms( 1 );
    }
    return MOSAIC_OK;
}

static void mosaic_parser_application ( uint8_t *rsp )
{
    uint8_t element_buf[ 100 ] = { 0 };
    if ( MOSAIC_OK == mosaic_parse_gga( rsp, MOSAIC_GGA_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 ] );
            memset( element_buf, 0, sizeof( element_buf ) );
            mosaic_parse_gga( rsp, MOSAIC_GGA_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 ) );
            mosaic_parse_gga( rsp, MOSAIC_GGA_ALTITUDE, element_buf );
            log_printf( &logger, " Altitude: %s m \r\n", element_buf );
            wait_for_fix_cnt = 0;
        }
        else
        {
            if ( wait_for_fix_cnt % 5 == 0 )
            {
                log_printf( &logger, " Waiting for the position fix...\r\n\n" );
                wait_for_fix_cnt = 0;
            }
            wait_for_fix_cnt++;
        }
        mosaic_clear_app_buf(  );
    }
}

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

Additional Support

Resources