Personalize your energy management with LMR36015 and MK64FN1M0VDC12
Voltage control at its finest
Published Aug 01, 2023
Click board™
Buck 11 Click
Dev. board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Achieve stable and regulated output voltage that matches the specific requirements of electronic devices
A
A
Hardware Overview
How does it work?
Buck 11 Click is based on the LMR36015, a synchronous step-down converter from Texas Instruments. This advanced integrated step-down converter requires a minimum number of external components readily available on the market. It utilizes a peak-current-mode control architecture, which ensures good efficiency and automatic PFM/PWM mode switching. The LMR36015 buck converter features over-current, under-voltage, and thermal protection, making Buck 11 click a robust and reliable power supply solution. The feedback voltage on the FB pin determines the output voltage. The output voltage is set to 3.3V, making it usable with most embedded applications, allowing them to be powered from the same source, like the rest of the application, which may use a higher voltage for its operation. This is a common-case scenario in various field applications requiring a relatively high voltage, i.e.,
for servos, step motors, displays, and more. When there is an overload at the output, the low-side MOSFET will allow the inductor current to drop. It will remain open until the current through the inductor falls below the limit. If the FB voltage drops too much during the overload, the device enters the hiccup mode, in which the device attempts to periodically restarts itself. The LMR36015 can automatically switch between PWM and PFM modes, depending on the current through the load. At very light loads, the device is operated in PFM mode. In this mode, the high-side MOSFET is operated in bursts, after which the LMR36015 waits for the current through the inductor to drop below the limit. This way, the device is idle while the light load consumes energy stored within the coil. This greatly improves the efficiency when a light load is used. While operated in PWM mode, the output MOSFETs
are driven with the constant PWM frequency of 400kHz, using the pulse width modulation to control the output voltage. This provides good voltage regulation and a low output voltage ripple. Featuring the HotRod™ technology, the LMR36015 occupies a small area on the PCB. Combined with the low count of external components it requires, the LMR36015 leaves enough space for an additional IC to be used. This click uses the MCP3221, a 12-bit A/D converter (ADC) that uses the I2C interface from Microchip. It allows monitoring of the output voltage over the I2C interface. This ADC is powered by the +5V mikroBUS™ power rail. The same voltage is used as a reference. 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.
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
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
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Clicker 2 for Kinetis as your development board.
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
This library contains API for Buck 11 Click driver.
Key functions:
buck11_read_adc- ADC Read functionbuck11_get_vout- Get VOUT functionbuck11_get_averaged_vout- Get averaged VOUT function
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
* \brief Buck11 Click example
*
* # Description
* This aplication control voltage using Buck 11.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes I2C serial interface and selects the desired VDD voltage value
* and VOUT value resolution (to get VOUT value in Volts).
*
* ## Application Task
* Reads the averaged VOUT voltage calculated to Volts by performing a 30 conversions
* in one measurement cycle. The measured results will be showed on the uart terminal every 300 milliseconds.
*
* *note:*
* The user should measure the VDD voltage value and enter this measured value to the function as VDD value to get
* more accurate measurement. This VDD voltage is used as reference voltage for the AD conversion.
*
* The input voltage (VIN) range is from 4.2V to 60V.
* The output current (IOUT) value should not be greater than 1.5A.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "buck11.h"
// ------------------------------------------------------------------ VARIABLES
static buck11_t buck11;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
uint8_t vout_resol;
log_cfg_t log_cfg;
buck11_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.
buck11_cfg_setup( &cfg );
BUCK11_MAP_MIKROBUS( cfg, MIKROBUS_1 );
buck11_init( &buck11, &cfg );
Delay_ms( 500 );
buck11_set_vdd_value( 4.935 );
vout_resol = BUCK11_VOUT_VOLTS;
log_printf( &logger, "** Buck 11 is initialized ** \r\n" );
log_printf( &logger, "************************************* \r\n" );
Delay_ms( 200 );
}
void application_task ( )
{
float vout_value;
uint8_t vout_resol;
vout_value = buck11_get_averaged_vout( &buck11, vout_resol, 30 );
log_printf( &logger, "VOUT: %f", vout_value );
if ( vout_resol == BUCK11_VOUT_VOLTS )
{
log_printf( &logger, " V \r\n" );
}
else
{
log_printf( &logger, " mV \r\n" );
}
log_printf( &logger, "************************************* \r\n" );
Delay_ms( 300 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
