Make your gadgets work efficiently by managing their power needs in a smart and compact way
A
A
Hardware Overview
How does it work?
Smart Buck 2 Click is based on the TPS62363, a 3A processor supply with remote sense from Texas Instruments. The converter has a programable output voltage for digital voltage scaling in a range of 0.5V up to 1.77V in 10mV steps. It is focused on high-output voltage accuracy and features soft start, programmable slew rate at voltage transition, overtemperature protection, input undervoltage detection and lockout, differential load sensing, DCS-Control™ architecture for fast and precise transient regulation, and more. Also, it offers a high-efficiency step-down conversion, where the area of
highest efficiency is towards low currents while the processor is operating in retention mode, as well as towards the highest output currents, increasing the battery ON time. The TPS62363 converter features a power save mode to gain efficiency at light output current conditions. The device automatically transitions in both directions between pulse width modulation (PWM) operation at high load and pulse frequency modulation (PFM) operation at light load current. This maintains high efficiency at both light and heavy load currents. In PFM Mode, the device generates single switching pulses when require
to maintain the programmed output voltage. Smart Buck 2 Click uses a standard 2-wire I2C interface to communicate with the host MCU. The TPS62363 supports Standard, Fast, and High-Speed modes with a clock frequency of up to 3.4MHz. 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, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used for further development.
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.
Microcontroller Overview
MCU Card / MCU
![default](https://dbp-cdn.mikroe.com/catalog/mcus/resources/MK64FN1M0VDC12.jpg)
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
![Smart Buck 2 Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee972a3-43bf-6c14-b898-02420a00025b/smart-buck-2-click-v100-Schematic-1.png)
Step by step
Project 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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed554e-d80f-6694-8cb9-02420a000272/AP-Step1.jpg)
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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed5550-3c0f-6800-a19f-02420a000272/AP-Step3.jpg)
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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed5550-d4d0-6b20-a348-02420a000272/AP-Step4.jpg)
Software Support
Library Description
This library contains API for Smart Buck 2 Click driver.
Key functions:
smartbuck2_set_voltage
- Smart Buck 2 set voltage function.smartbuck2_get_voltage
- Smart Buck 2 get voltage 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 Smart Buck 2 Click example
*
* # Description
* This library contains API for the Smart Buck 2 Click board™.
* This driver provides functions for device configurations
* and for the sets and reads the output voltage.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of I2C module and log UART.
* After driver initialization, the app executes a default configuration.
*
* ## Application Task
* This example demonstrates the use of the Smart Buck 2 Click board™.
* The demo application changes the output voltage in steps of 100mv every 3 seconds
* and displays the output voltage value.
* Results are sent to the UART Terminal, where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "smartbuck2.h"
#define DEMO_VOUT_STEP_100MV 100
static smartbuck2_t smartbuck2;
static log_t logger;
static uint16_t vout_mv = SMARTBUCK2_VOUT_MIN;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
smartbuck2_cfg_t smartbuck2_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.
smartbuck2_cfg_setup( &smartbuck2_cfg );
SMARTBUCK2_MAP_MIKROBUS( smartbuck2_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == smartbuck2_init( &smartbuck2, &smartbuck2_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( SMARTBUCK2_ERROR == smartbuck2_default_cfg ( &smartbuck2 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
Delay_ms( 100 );
}
void application_task ( void )
{
if ( SMARTBUCK2_OK == smartbuck2_set_voltage( &smartbuck2, vout_mv ) )
{
Delay_ms( 100 );
if ( SMARTBUCK2_OK == smartbuck2_get_voltage( &smartbuck2, &vout_mv ) )
{
log_printf( &logger, " Output voltage: %u [mV]\r\n", vout_mv );
}
}
vout_mv += DEMO_VOUT_STEP_100MV;
if ( vout_mv > SMARTBUCK2_VOUT_MAX )
{
vout_mv = SMARTBUCK2_VOUT_MIN;
}
Delay_ms( 3000 );
}
int main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END