Advanced
30 min

Achieve reliable motor control with TB67H453FNG and STM32G474RE

Single-channel H-Bridge driver featuring built-in current monitoring

DC Motor 28 Click - FNG with Nucleo 64 with STM32G474RE MCU

Published Mar 13, 2025

Click board™

DC Motor 28 Click - FNG

Dev. board

Nucleo 64 with STM32G474RE MCU

Compiler

NECTO Studio

MCU

STM32G474RE

Control brushed DC motors in industrial automation, robotics, and motion control applications

A

A

Hardware Overview

How does it work?

DC Motor 28 Click - FNG is based on the TB67H453FNG, a single-channel H-Bridge driver from Toshiba Semiconductor, designed to drive brushed DC motors with high precision and reliability. This IC is capable of controlling a single brushed DC motor in both directions or two brushed DC motors in a single direction (individual half bridge control mode). With an operating voltage range from 4.5V to 44V and a maximum output current of 3.5A, it provides a robust and versatile motor control solution suitable for a variety of applications like industrial automation, robotics, or general-purpose motor-driven systems. One of the key features of the TB67H453FNG is its integrated current monitoring function, accessible through the SEN pin. This pin outputs a current level proportional to the current flowing through the low-side MOSFETs in the H-Bridge, allowing for precise current measurement and monitoring. Additionally, the IC is equipped with multiple protection mechanisms, including overtemperature detection, overcurrent protection, and undervoltage lockout, and a VREF trimmer, which enables users to set the output current threshold, further enhancing control over motor operation. The device also offers

low power consumption, including a standby mode that minimizes energy usage when the motor is not in operation. Motor control is managed through the IN1 and IN2 pins, which manage the H-Bridge operation. The PMODE SEL switch determines the control mode, and its settings are locked once the Sleep mode (SLP signal) is applied High and the driver operates. To modify the PMODE configuration, the SLP signal must first be set to LOW before adjusting the PMODE switch. Once the desired setting is selected, the SLP signal is re-applied, allowing the device to register the new mode. The PMODE SEL switch allows the user to choose between different functions. Setting it to Low activates Phase/Enable interface, setting it to High enables PWM (IN1/IN2) interface and setting it to Hi-Z (Open) switches to individual half bridge control mode. The IMODE SEL switch is used to set the current control mode and the behavior of the overcurrent detection (ISD). The switch configures the driver for either constant current PWM mode or fixed off time control, with options for auto recovery or latched response to overcurrent. In Fixed Off Time Control Mode, the H-Bridge switches to short brake for a fixed period when the motor current

exceeds the threshold, while in Constant Current PWM Control Mode, the H-Bridge switches to short brake until the next control signal input edge is asserted after the motor current exceeds the threshold. The IMODE SEL switch follows the same adjustment procedure as PMODE SEL, requiring the SLP signal to be cycled before changes take effect. To enhance safety and diagnostics, the TB67H453FNG includes an error detection system that continuously monitors for irregular overcurrent conditions. If an anomaly is detected, the MOSFETs are automatically turned off to prevent damage. The status of these error conditions can be observed via the FLT pin, while a red FAULT LED provides a clear visual indication of any detected faults. 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.

DC Motor 28 Click - FNG 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

DC Motor (RS-555) is a high-performance brushed DC motor (RS-555SH-2770) ideal for applications requiring reliable and efficient motion. It operates at 18V–30V DC (nominal 24V) with a no-load speed of 9100 rpm and delivers 22.7W power at maximum efficiency. Featuring a 3.175mm shaft, CW/CCW rotation, and an oil-bearing system, it ensures smooth and durable operation. Common applications include pumps, juicers, humidifiers, and water purifiers.

DC Motor 28 Click - FNG accessories 1 image

Used MCU Pins

mikroBUS™ mapper

Current Monitor Output
PA15
AN
Sleep Mode / ID SEL
PC12
RST
H-Bridge Control / ID COMM
PB12
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
H-Bridge Control
PC8
PWM
Fault Indicator
PC14
INT
NC
NC
TX
NC
NC
RX
NC
NC
SCL
NC
NC
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Click board™ Schematic

DC Motor 28 Click - FNG 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

DC Motor 28 Click - FNG 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 the DC Motor 28 Click - FNG. It initializes the Click driver, calibrates the offset for accurate current measurements, and then controls the motor in different states while measuring and logging the output current in milliamps (mA).

Key functions:

  • dcmotor28fng_cfg_setup - Config Object Initialization function.

  • dcmotor28fng_init - Initialization function.

  • dcmotor28fng_drive_motor - This function drives the motor in the selected PWM control mode state.

  • dcmotor28fng_calib_offset - This function calibrates the zero current offset value.

  • dcmotor28fng_get_out_current - This function reads the current output measurement in mA.

Application Init
Initializes the logger and the DC Motor 28 Click - FNG driver and performs offset calibration for current measurements.

Application Task
Controls the motor in a sequence of states: FORWARD, BRAKE, REVERSE, and COAST. In each state, the output current is measured and logged, providing insights into the motor's performance and consumption.

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 DC Motor 28 FNG Click Example.
 *
 * # Description
 * This example demonstrates the use of the DC Motor 28 FNG Click board. It initializes the Click driver, 
 * calibrates the offset for accurate current measurements, and then controls the motor in different states 
 * while measuring and logging the output current in milliamps (mA).
 *
 * The demo application is composed of two sections:
 *
 * ## Application Init
 * Initializes the logger and the DC Motor 28 FNG Click driver and performs offset calibration for current
 * measurements.
 *
 * ## Application Task
 * Controls the motor in a sequence of states: FORWARD, BRAKE, REVERSE, and COAST. In each state, the output 
 * current is measured and logged, providing insights into the motor's performance and consumption.
 *
 * @note
 * Ensure the PMODE switch is set to position 1 (HIGH), the motor is properly connected to the board
 * OUT1 and OUT2 terminals, and the proper power supply is connected to the input terminal.
 *
 * @author Stefan Filipovic
 *
 */

#include "board.h"
#include "log.h"
#include "dcmotor28fng.h"

static dcmotor28fng_t dcmotor28fng;   /**< DC Motor 28 FNG Click driver object. */
static log_t logger;    /**< Logger object. */

void application_init ( void )
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    dcmotor28fng_cfg_t dcmotor28fng_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.
    dcmotor28fng_cfg_setup( &dcmotor28fng_cfg );
    DCMOTOR28FNG_MAP_MIKROBUS( dcmotor28fng_cfg, MIKROBUS_1 );
    if ( ADC_ERROR == dcmotor28fng_init( &dcmotor28fng, &dcmotor28fng_cfg ) )
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    if ( DCMOTOR28FNG_ERROR == dcmotor28fng_calib_offset ( &dcmotor28fng ) )
    {
        log_error( &logger, " Offset calibration." );
        for ( ; ; );
    }
    
    log_info( &logger, " Application Task " );
}

void application_task ( void ) 
{
    float current = 0;

    log_printf( &logger, " Motor state : FORWARD\r\n" );
    dcmotor28fng_drive_motor ( &dcmotor28fng, DCMOTOR28FNG_MOTOR_FORWARD );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    if ( DCMOTOR28FNG_OK == dcmotor28fng_get_out_current ( &dcmotor28fng, &current ) ) 
    {
        log_printf( &logger, " Current : %.3f mA\r\n\n", current );
    }

    log_printf( &logger, " Motor state : BRAKE\r\n" );
    dcmotor28fng_drive_motor ( &dcmotor28fng, DCMOTOR28FNG_MOTOR_BRAKE );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    if ( DCMOTOR28FNG_OK == dcmotor28fng_get_out_current ( &dcmotor28fng, &current ) ) 
    {
        log_printf( &logger, " Current : %.3f mA\r\n\n", current );
    }

    log_printf( &logger, " Motor state : REVERSE\r\n" );
    dcmotor28fng_drive_motor ( &dcmotor28fng, DCMOTOR28FNG_MOTOR_REVERSE );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    if ( DCMOTOR28FNG_OK == dcmotor28fng_get_out_current ( &dcmotor28fng, &current ) ) 
    {
        log_printf( &logger, " Current : %.3f mA\r\n\n", current );
    }

    log_printf( &logger, " Motor state : COAST\r\n" );
    dcmotor28fng_drive_motor ( &dcmotor28fng, DCMOTOR28FNG_MOTOR_COAST );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    if ( DCMOTOR28FNG_OK == dcmotor28fng_get_out_current ( &dcmotor28fng, &current ) ) 
    {
        log_printf( &logger, " Current : %.3f mA\r\n\n", current );
    }
}

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.