Intermediate
30 min

Convert a higher input voltage to a lower output easily with TPS628510 and MK64FN1M0VDC12

Synchronous step-down supremacy!

Step Down 5 Click with Clicker 2 for Kinetis

Published Aug 01, 2023

Click board™

Step Down 5 Click

Dev.Board

Clicker 2 for Kinetis

Compiler

NECTO Studio

MCU

MK64FN1M0VDC12

Unlocking the full potential of modern electronics, our step-down converter harmonizes power requirements, paving the way for energy-conscious innovations

A

A

Hardware Overview

How does it work?

Step Down 5 Click is based on the TPS628510, a synchronous step-down converter from Texas Instruments, providing interface-configurable output voltage range from 0.6V to 5.5V suitable for point-of-load and post-regulation applications. This synchronous switch mode power converter is based on a peak current mode control topology and achieves fast and stable operation with an internally compensated control loop. It provides up to 0.5A load current over a wide input supply range from 2.7V to 6V and has excellent load and line regulation. In addition, it is characterized by high efficiency over a wide range of load output voltage from 0.6V to 5.5V, which can be easily adjusted using a digital potentiometer, the MCP4661 from Microchip. The TPS628510 supports

forced fixed frequency PWM operation with the MD pin of the mikroBUS™ socket set to a high logic level. Its switching frequency is internally fixed at 2.25MHz. When the MD pin is set to a low logic level, the TPS628510 operates in power save mode (PFM) at a low output current and automatically transfers to fixed-frequency PWM mode at a higher output current. In PFM mode, the switching frequency decreases linearly based on the load to sustain high efficiency down to a very low output current. Alternatively, the TPS628510 can be synchronized to an external clock signal from 1.8MHz to 4MHz, applied to the MD pin. An internal PLL allows you to change from an internal clock to an external clock during operation. Besides the operational mode

selection pin, this Click board™ also has a power-good function routed to the PG pin of the mikroBUS™ socket, indicating that the output reached desired regulation and the possibility for the MCP4661 to choose the least significant bit (LSB) of its I2C slave address by positioning SMD jumpers labeled as ADDR SEL to an appropriate position marked as 0 and 1. 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.

Step Down 5 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

NC
NC
AN
NC
NC
RST
NC
NC
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
Mode Selection
PA10
PWM
Power Good Indicator
PB13
INT
NC
NC
TX
NC
NC
RX
I2C Clock
PD8
SCL
I2C Data
PD9
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

Step Down 5 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

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 Step Down 5 Click driver.

Key functions:

  • stepdown5_set_wiper_0_pos - Step Down 5 set wiper 0 position

  • stepdown5_set_r1_resistance - Step Down 5 set potentiometer 0 resistance

  • stepdown5_set_output - Step Down 5 set output voltage

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 Step Down 5 Click example
 *
 * # Description
 * This library contains API for the Step Down 5 Click driver.
 * This driver provides the functions to set the output voltage treshold.
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initialization of I2C module and log UART.
 * After driver initialization, default settings sets output voltage to 0.6 V.
 *
 * ## Application Task
 * This example demonstrates the use of the Step Down 5 Click board™ by changing 
 * output voltage every 5 seconds starting from 0.6 V up to 3.3 V.
 * 
 *
 * @author Stefan Ilic
 *
 */

#include "board.h"
#include "log.h"
#include "stepdown5.h"

static stepdown5_t stepdown5;
static log_t logger;

/**
 * @brief Output level printing function.
 * @details This function is used to log value of the selected voltage to UART terminal.
 * @param[in] sel_level : Selected voltage level.
 * @return Nothing.
 * @note None.
 */
static void print_selected_output_level ( uint8_t sel_level );

void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    stepdown5_cfg_t stepdown5_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.
    stepdown5_cfg_setup( &stepdown5_cfg );
    STEPDOWN5_MAP_MIKROBUS( stepdown5_cfg, MIKROBUS_1 );
    if ( I2C_MASTER_ERROR == stepdown5_init( &stepdown5, &stepdown5_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    if ( STEPDOWN5_ERROR == stepdown5_default_cfg ( &stepdown5 ) )
    {
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    }
    
    log_info( &logger, " Application Task " );
}

void application_task ( void ) 
{
    for ( uint8_t n_cnt = STEPDOWN5_OUTPUT_0V6; n_cnt <= STEPDOWN5_OUTPUT_3V3; n_cnt++ )
    {
        stepdown5_set_output( &stepdown5, n_cnt );
        log_printf( &logger, " Selected output is:" );
        print_selected_output_level ( n_cnt );
        Delay_ms( 5000 );
    }
}

void main ( void ) 
{
    application_init( );

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

static void print_selected_output_level ( uint8_t sel_level )
{
    switch ( sel_level )
    {
        case ( STEPDOWN5_OUTPUT_0V6 ):
        {
            log_printf( &logger, " 0.6V\r\n" );
            break;
        }
        case ( STEPDOWN5_OUTPUT_1V5 ):
        {
            log_printf( &logger, " 1.5V\r\n" );
            break;
        }
        case ( STEPDOWN5_OUTPUT_2V5 ):
        {
            log_printf( &logger, " 2.5V\r\n" );
            break;
        }
        case ( STEPDOWN5_OUTPUT_3V3 ):
        {
            log_printf( &logger, " 3.3V\r\n" );
            break;
        }
        default:
        {
            log_printf( &logger, " ERROR\r\n" );
        }
    }
}

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

Additional Support

Resources