Intermediate
30 min

Prevent damage from short circuits and reverse polarity with TPS25940 and MK64FN1M0VDC12

Power path defender: Where control meets reliability

eFuse 4 Click with Clicker 2 for Kinetis

Published Oct 12, 2023

Click board™

eFuse 4 Click

Dev Board

Clicker 2 for Kinetis

Compiler

NECTO Studio

MCU

MK64FN1M0VDC12

Our eFuse solution is engineered to provide advanced circuit protection, offering precise current limiting, fault detection, and overcurrent protection for enhanced reliability and safety

A

A

Hardware Overview

How does it work?

eFuse 4 Click is based on the TPS25940, a smart eFuse with integrated back-to-back FETs and enhanced built-in protection circuitry from Texas Instruments. The TPS25940 provides robust protection for all systems and applications powered by an external power supply from 2.7V to 18V. It also features a full suite of protection and monitoring functions, including a low-power DevSleep™ mode, controllable through a DVS pin routed on the PWM pin of the mikroBUS™ socket, that supports compliance with the SATA™ Device Sleep standard. This Click board™ is designed to protect systems such as enterprise SSD drives against sudden power loss events. It monitors voltages of the input and output terminals to provide true reverse blocking from the output

when a reverse condition or input power fail condition is detected. The TPS25940 allows users to program the overcurrent limit threshold between 1A and 5A via an external I2C-configurable digital potentiometer, the AD5272 from Analog Devices. Besides the overcurrent feature, the TPS25940 has programmable over and undervoltage thresholds for load, source, and device protection. The TPS25940 also provides an additional power-good comparator on the PGD pin, routed on the AN pin of the mikroBUS™ socket, with precision internal reference for output or any other rail voltage monitoring and a fault event indicator on the FLT pin. This fault indicator goes to a low logic state to indicate fault conditions due to under/overvoltage, reverse

voltage, and thermal shutdown events in the event of an overcurrent. A special addition on the plate represents an unpopulated header, which represents a precise current monitor output for health monitoring of the system, alongside the Enable pin routed on the RST pin of the mikroBUS™ socket that controls the ON/OFF state of the internal TPS25940’s FETs. 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.

eFuse 4 Click hardware overview image

Features overview

Development board

Clicker 2 for Kinetis is a compact starter development board 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 ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and

features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or

using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis 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.

Clicker 2 for Kinetis dimensions image

Microcontroller Overview

MCU Card / MCU

default

Architecture

ARM Cortex-M4

MCU Memory (KB)

1024

Silicon Vendor

NXP

Pin count

121

RAM (Bytes)

262144

Used MCU Pins

mikroBUS™ mapper

Power-Good Indicator
PB2
AN
Reset
PB11
RST
NC
NC
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
DevSleep Mode
PA10
PWM
Fault Interrupt
PB13
INT
NC
NC
TX
NC
NC
RX
I2C Clock
PD8
SCL
I2C Data
PD9
SDA
NC
NC
5V
Ground
GND
GND
1

Take a closer look

Schematic

eFuse 4 Click Schematic schematic

Step by step

Project assembly

Clicker 2 for PIC32MZ front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Clicker 2 for Kinetis as your development board.

Clicker 2 for PIC32MZ front image hardware assembly
GNSS2 Click front image hardware assembly
Prog-cut hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
Micro B Connector Clicker 2 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 via Debug Mode

1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.

2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.

DEBUG_Application_Output

Software Support

Library Description

This library contains API for eFuse 4 Click driver.

Key functions:

  • efuse4_set_current_limit - eFuse 4 set current limit function

  • efuse4_set_resistance - eFuse 4 set resistance function

  • efuse4_set_digi_pot - eFuse 4 set normal mode function

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 eFuse 4 Click example
 *
 * # Description
 * This library contains API for the eFuse 4 Click driver.
 * This driver provides the functions to set the current limiting conditions 
 * in order to provide the threshold of the fault conditions.
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initialization of I2C module and log UART.
 * After driver initialization, default settings turn on the device.
 *
 * ## Application Task
 * This example demonstrates the use of the eFuse 4 Click board™.
 * Reading user's input from UART Terminal and using it as an index 
 * for an array of pre-calculated values that define the current limit level.
 * Results are being sent to the UART Terminal, where you can track their changes.
 *
 * @author Nenad Filipovic
 *
 */

#include "board.h"
#include "log.h"
#include "efuse4.h"

static efuse4_t efuse4;
static log_t logger;

const efuse4_current_limit_t limit_value_op[ 7 ] = 
{ 
    EFUSE4_CURRENT_LIMIT_670_mA, 
    EFUSE4_CURRENT_LIMIT_750_mA,
    EFUSE4_CURRENT_LIMIT_990_mA,
    EFUSE4_CURRENT_LIMIT_2080_mA, 
    EFUSE4_CURRENT_LIMIT_3530_mA,
    EFUSE4_CURRENT_LIMIT_4450_mA,
    EFUSE4_CURRENT_LIMIT_5200_mA,
};

static void display_selection ( void ) 
{
    log_printf( &logger, "  To select current limit  \r\n" );
    log_printf( &logger, "  Send one of the numbers: \r\n" );
    log_printf( &logger, "- - - - - - - - - - - - - -\r\n" );
    log_printf( &logger, " '0' - Limited to  670 mA  \r\n" );
    log_printf( &logger, " '1' - Limited to  750 mA  \r\n" );
    log_printf( &logger, " '2' - Limited to  990 mA  \r\n" );
    log_printf( &logger, " '3' - Limited to 2080 mA  \r\n" );
    log_printf( &logger, " '4' - Limited to 3530 mA  \r\n" );
    log_printf( &logger, " '5' - Limited to 4450 mA  \r\n" );
    log_printf( &logger, " '6' - Limited to 5200 mA  \r\n" );  
    log_printf( &logger, "---------------------------\r\n" );
}

void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    efuse4_cfg_t efuse4_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.
    efuse4_cfg_setup( &efuse4_cfg );
    EFUSE4_MAP_MIKROBUS( efuse4_cfg, MIKROBUS_1 );
    if ( I2C_MASTER_ERROR == efuse4_init( &efuse4, &efuse4_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    if ( EFUSE4_ERROR == efuse4_default_cfg ( &efuse4 ) )
    {
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    }
    
    log_info( &logger, " Application Task " );
    log_printf( &logger, "---------------------------\r\n" );
    Delay_ms( 100 );
    
    display_selection( );
    Delay_ms( 100 );
}

void application_task ( void ) 
{  
    static char index;
    
    if ( EFUSE4_ERROR != log_read( &logger, &index, 1 ) ) 
    {
        if ( ( index >= '0' ) && ( index <= '6' ) ) 
        {
            efuse4_set_current_limit ( &efuse4, limit_value_op[ index - 48 ] );
            log_printf( &logger, "  >>> Selected mode %d     \r\n", index - 48 );
            log_printf( &logger, "  Current limit is %d mA   \r\n", limit_value_op[ index - 48 ] );
            log_printf( &logger, "---------------------------\r\n" );
            Delay_ms( 100 );
        }
        else 
        { 
            log_printf( &logger, "    Data not in range!    \r\n" );
            log_printf( &logger, "---------------------------\r\n" );
            display_selection( );
            Delay_ms( 100 );
        }
    }
}

void main ( void ) 
{
    application_init( );

    for ( ; ; ) 
    {
        application_task( );
    }
}

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