Beginner
10 min

Measure distances across 8x8 configurable zones for detailed spatial mapping with VL53L8CH and STM32G474RE

Time-of-Flight sensing solution for AI apps with a wide 65° diagonal FoV

LightRanger 12 Click with Nucleo 64 with STM32G474RE MCU

Published Feb 13, 2025

Click board™

LightRanger 12 Click

Dev Board

Nucleo 64 with STM32G474RE MCU

Compiler

NECTO Studio

MCU

STM32G474RE

Achieve precise distance measurement and spatial mapping with multizone ToF technology

A

A

Hardware Overview

How does it work?

LightRanger 12 Click is based on the VL53L8CH, an 8x8 multizone Time-of-Flight (ToF) sensor from STMicroelectronics, designed for AI applications with exceptional performance under ambient light conditions. This sensor offers a wide 65° diagonal field of view (45° x 45° square), making it ideal for precise distance measurement and spatial mapping applications. It introduces a Compact and Normalized Histogram (CNH) data output format, specifically made for artificial intelligence applications that demand multizone raw data from a high-performance optical sensor, including AI-driven robotics, smart appliances like coffee machines and beverage dispensers, smart home solutions, and advanced recognition systems. The VL53L8CH integrates a powerful new-generation Vertical-Cavity Surface-Emitting Laser (VCSEL) and two advanced metasurface lenses, enhancing its optical capabilities. The VCSEL emits an invisible 940 nm IR light that is Class 1 certified, ensuring eye safety while maintaining high performance. It also provides unparalleled flexibility by allowing users to configure up to 64 zones (8x8 grid), adjust histogram resolution to 128 bins, and define bin widths. Each zone's infrared signal is transmitted to the host as raw histogram data, complementing the standard ToF sensor outputs, such as ranging distances up to 400 cm, signal

levels, and reflectance. By combining raw histogram data with traditional ranging capabilities, the VL53L8CH unlocks endless possibilities beyond standard distance measurement. It can detect and differentiate between solid materials like carpet, wood, glass, mirrors and fluids such as water, oil, or chemicals. This makes it possible to identify the location and size of a cup in coffee machines or beverage dispensers, detect floor materials for robotic navigation, or develop advanced AI-driven features like gesture motion recognition, hand posture detection, and even shape or motion analysis. Additionally, the sensor is suited for applications like people counting in smart homes and buildings. Sensor data are accessed through the I2C or SPI interface, with a maximum frequency of 1MHz for I2C and 3MHz for SPI communication. The selection is made by positioning SMD jumpers labeled COMM SEL appropriately. Note that all the jumpers' positions must be on the same side, or the Click board™ may become unresponsive. In addition to the interface pins, this board uses several other pins. The SNC pin on the mikroBUS™ socket offers dual functionality: it can serve as a synchronization input, enabling the sensor to align its measurements with external events or signals for precise timing and coordination in applications requiring high

accuracy, or it can act as a general-purpose open-drain input/output pin, providing added versatility for control or signaling tasks tailored to specific application needs. The LP pin allows users to toggle the I2C communication ON or OFF while in low-power mode, which is particularly useful for changing the I2C address in multi-device systems. Lastly, the INT pin provides an interrupt signal to indicate when a ranging measurement is available, ensuring data handling and real-time responsiveness. The VL53L8CH does not require a specific Power-Up sequence but requires a voltage of 1.8V for its interface and logic part to work correctly. Therefore, a small regulating LDO, the AP2112, provides a 1.8V out of selected mikroBUS™ power rail. Since the sensor operates on 1.8V, this Click board™ also features the TXB0108E voltage-level translator, allowing the VL53L8CH to work properly with 3.3V and 5V MCU. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC 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.

LightRanger 12 Click hardware overview image

Features overview

Development board

Nucleo-64 with STM32G474R 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.

Nucleo 64 with STM32G474RE MCU double side image

Microcontroller Overview

MCU Card / MCU

STM32G474RE front image

Architecture

ARM Cortex-M4

MCU Memory (KB)

512

Silicon Vendor

STMicroelectronics

Pin count

64

RAM (Bytes)

128k

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.

Click Shield for Nucleo-64 accessories 1 image

Used MCU Pins

mikroBUS™ mapper

Synchronization / GPIO
PA15
AN
ID SEL
PC12
RST
SPI Select / ID COMM
PB12
CS
SPI Clock
PB3
SCK
SPI Data OUT
PB4
MISO
SPI Data IN
PB5
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
Low Power I2C Enable
PC8
PWM
Interrupt
PC14
INT
NC
NC
TX
NC
NC
RX
I2C Clock
PB8
SCL
I2C Data
PB9
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Click board™ Schematic

LightRanger 12 Click Schematic schematic

Step by step

Project assembly

Click Shield for Nucleo-64 accessories 1 image hardware assembly

Start by selecting your development board and Click board™. Begin with the Nucleo 64 with STM32G474RE MCU as your development board.

Click Shield for Nucleo-64 accessories 1 image hardware assembly
Nucleo 64 with STM32G474RE MCU front image hardware assembly
LTE Cat.1 6 Click front image hardware assembly
Prog-cut hardware assembly
LTE Cat.1 6 Click complete accessories setup image hardware assembly
Nucleo-64 with STM32GXXX MCU Access MB 1 Micro B Conn - 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 image step 6 hardware assembly
Clicker 4 for STM32F4 HA 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

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

LightRanger 12 Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.

Example Description
This example demonstrates the use of LightRanger 12 Click board by reading and displaying 8x8 zones measurements on the USB UART.

Key functions:

  • lightranger12_cfg_setup - Config Object Initialization function.

  • lightranger12_init - Initialization function.

  • lightranger12_default_cfg - Click Default Configuration function.

  • lightranger12_get_int_pin - This function returns the INT (interrupt) pin logic state.

  • lightranger12_get_resolution - This function gets the current resolution (4x4 or 8x8).

  • lightranger12_get_ranging_data - This function gets the ranging data, using the selected output and the resolution.

Application Init
Initializes the driver and performs the Click default configuration.

Application Task
Reads all zone measurements approximately every 200ms and logs them to the USB UART as an 8x8 map. The silicon temperature measurement in degrees Celsius is also displayed.

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 LightRanger 12 Click example
 *
 * # Description
 * This example demonstrates the use of LightRanger 12 Click board by reading and displaying
 * 8x8 zones measurements on the USB UART.
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initializes the driver and performs the Click default configuration.
 *
 * ## Application Task
 * Reads all zone measurements approximately every 200ms and logs them to the USB UART as an 8x8 map. 
 * The silicon temperature measurement in degrees Celsius is also displayed.
 *
 * @author Stefan Filipovic
 *
 */

#include "board.h"
#include "log.h"
#include "lightranger12.h"

static lightranger12_t lightranger12;
static log_t logger;

void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    lightranger12_cfg_t lightranger12_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.
    lightranger12_cfg_setup( &lightranger12_cfg );
    LIGHTRANGER12_MAP_MIKROBUS( lightranger12_cfg, MIKROBUS_1 );
    if ( I2C_MASTER_ERROR == lightranger12_init( &lightranger12, &lightranger12_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    if ( LIGHTRANGER12_ERROR == lightranger12_default_cfg ( &lightranger12 ) )
    {
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    }
    
    log_info( &logger, " Application Task " );
}

void application_task ( void ) 
{
    err_t error_flag = LIGHTRANGER12_OK;
    lightranger12_results_data_t results;
    uint8_t resolution = 0;
    uint8_t map_side = 0;

    // Wait for a data ready interrupt
    while ( lightranger12_get_int_pin ( &lightranger12 ) );

    error_flag |= lightranger12_get_resolution ( &lightranger12, &resolution );
    error_flag |= lightranger12_get_ranging_data ( &lightranger12, &results );
    if ( LIGHTRANGER12_OK == error_flag )
    {
        map_side = ( LIGHTRANGER12_RESOLUTION_4X4 == resolution ) ? 4 : 8;
        log_printf ( &logger, "----------------------- %ux%u MAP (mm) -----------------------\r\n", 
                    ( uint16_t ) map_side, ( uint16_t ) map_side );
        for ( uint8_t cnt_0 = 1; cnt_0 <= map_side; cnt_0++ )
        {
            for ( uint8_t cnt_1 = 1; cnt_1 <= map_side; cnt_1++ )
            {
                // Checking the zone measurement validity (5 & 9 means ranging OK)
                if ( ( 5 == results.target_status[ cnt_0 * map_side - cnt_1 ] ) ||
                     ( 9 == results.target_status[ cnt_0 * map_side - cnt_1 ] ) )
                {
                    log_printf ( &logger, "%d\t", results.distance_mm[ cnt_0 * map_side - cnt_1 ] );
                }
                else
                {
                    log_printf ( &logger, "NOK\t" );
                }
            }
            log_printf ( &logger, "\r\n" );
            Delay_ms ( 5 );
        }
        log_printf ( &logger, "Silicon temperature : %d degC\r\n", ( int16_t ) results.silicon_temp_degc );
        log_printf ( &logger, "------------------------------------------------------------\r\n\n" );
    }
}

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

Additional Support

Resources

Love this project?

'Buy This Kit' button takes you directly to the shopping cart where you can easily add or remove products.