Intermediate
30 min
0

Transform voltage like never before with MPM3530 and TM4C129ENCPDT

Sync your power needs

Buck 13 Click with UNI Clicker

Published Aug 01, 2023

Click board™

Buck 13 Click

Development board

UNI Clicker

Compiler

NECTO Studio

MCU

TM4C129ENCPDT

Ensure your electronics receive the necessary power, minimizing waste and enhancing performance

A

A

Hardware Overview

How does it work?

Buck 13 Click is based on the MPM3530, a 55V 3A ultra-low profile DC-to-DC power module by Monolithic Power Systems (MPS). This IC is a valley current mode controlled power module, meaning that it responds faster than the traditional peak current mode control, thus, a better response to transients. This IC requires minimal external components, making the whole device robust and easy to work with. The feedback voltage on the FB pin determines the output voltage. Therefore, Buck 13 click has a fixed voltage divider calculated to ensure stable, the most frequently used, 3.3V output. The MPM3530 operates at a high switching frequency of 520 kHz, which allows a good compromise between the efficiency and the device's size, with no external coil needed and a minimal number of other external components. This Click board™ also uses the MCP3001, a 10-bit A/D converter (ADC) which uses the SPI interface from Microchip. It allows monitoring of the

output voltage over the SPI interface. This ADC is powered by the +5V mikroBUS™ power rail. The same voltage is also used to supply the MCP1541 voltage reference. That way, the stable 4.096V reference voltage is obtained to ensure precise output voltage measurement. The Click board™ itself requires an external power supply to be connected at the input terminal, labeled as VIN. The VOUT terminal provides the connected load with the regulated 3.3V voltage. The over-current protection is based on cycle-by-cycle limiting of the inductor current. If the output voltage starts to drop during the current limiting interval, causing the FB voltage to drop under 50% of the internal reference, the device enters the hiccup mode, shutting down the output. After a fixed period, the device will try to re-enable the output. If the short-circuit condition still exists, it will shut down the output again, repeating the whole process until the short-circuit condition disappears. The hiccup

mode greatly reduces the short-circuit current, protecting the device when the output is shorted to ground. Thanks to its ability to work with the high-duty cycle of the internal switching PWM signal, the MPM3530 requires the input voltage to be only about 0.7V above the output voltage to maintain the regulation. However, if the input voltage drops under 3.5V, the device cannot operate properly. Therefore, the under-voltage protection shuts down the device as a protection measure. The under-voltage protection is disabled once the input voltage exceeds 3.9V. This small hysteresis of 0.4V prevents erratic behavior in border cases. As mentioned before, the voltage of the power supply at the input terminal should stay within the range between 4V and 55V. However, the voltage at the input should be approximately 5.7V to 6V, at least, to provide good regulation at the output.

Buck 13 Click hardware overview image

Features overview

Development board

UNI Clicker 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 supports a wide range of microcontrollers, such as different ARM, PIC32, dsPIC, PIC, and AVR from various vendors like Microchip, ST, NXP, and TI (regardless of their number of pins), four mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a debugger/programmer connector, and two 26-pin headers for interfacing with external electronics. Thanks to innovative manufacturing technology, it allows you to build

gadgets with unique functionalities and features quickly. Each part of the UNI Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the UNI Clicker programming method, using a third-party programmer or CODEGRIP/mikroProg connected to onboard JTAG/SWD header, the UNI Clicker board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Type-C (USB-C) connector, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or using a Li-Po/Li

Ion battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board (plus USB HOST/DEVICE), including the well-established mikroBUS™ socket, a standardized socket for the MCU card (SiBRAIN standard), and several user-configurable buttons and LED indicators. UNI Clicker 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.

UNI clicker double image

Microcontroller Overview

MCU Card / MCU

default

Type

8th Generation

Architecture

ARM Cortex-M4

MCU Memory (KB)

1024

Silicon Vendor

Texas Instruments

Pin count

128

RAM (Bytes)

262144

Used MCU Pins

mikroBUS™ mapper

Enable
PD0
AN
NC
NC
RST
SPI Chip Select
PH0
CS
SPI Clock
PQ0
SCK
SPI Data OUT
PQ3
MISO
NC
NC
MOSI
NC
NC
3.3V
Ground
GND
GND
NC
NC
PWM
NC
NC
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

Schematic

Buck 13 Click Schematic schematic

Step by step

Project assembly

UNI Clicker front image hardware assembly

Start by selecting your development board and Click board™. Begin with the UNI Clicker as your development board.

UNI Clicker front image hardware assembly
GNSS2 Click front image hardware assembly
SiBRAIN for STM32F745VG front image hardware assembly
Prog-cut hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
UNI Clicker Access MB 1 - 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
Necto image step 7 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 Buck 13 Click driver.

Key functions:

  • buck13_enable - Enables the Buck 13 output

  • buck13_get_adc - Gets the ADC values from the module

  • buck13_get_voltage - Gets the 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 
 * \brief Buck13 Click example
 * 
 * # Description
 * This example switches the output of the Buck13 and logs the output voltage 
 * on the Vout terminal.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Initializes SPI serial interface and turns OFF the Buck 13 output as default state.
 * 
 * ## Application Task  
 * Displays the output voltage every 2 seconds.
 * 
 * *note:* 
 * Input voltage range must be from 6.5 to 50V.
 * Output voltage is about 3.3V.
 * Current limit is 3A.
 * 
 * \author Petar Suknjaja
 *
 */
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "buck13.h"

// ------------------------------------------------------------------ VARIABLES

static buck13_t buck13;
static log_t logger;
static uint16_t out_voltage;

// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init ( void )
{
    log_cfg_t log_cfg;
    buck13_cfg_t cfg;

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

    buck13_cfg_setup( &cfg );
    BUCK13_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    buck13_default_cfg ( &buck13 );
    buck13_init( &buck13, &cfg );
    log_info( &logger, "Buck 13 is enabled now" );
}

void application_task ( void )
{
    //  Task implementation.

    buck13_enable( &buck13, BUCK13_ENABLE ); 
    out_voltage = buck13_get_voltage( &buck13 );
    log_printf( &logger, "Vout =  %d mV\r\n", out_voltage );
    
    Delay_ms( 2000 );
}

void main ( void )
{
    application_init( );

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

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

Additional Support

Resources