Our outstanding buck converter solution, the pocket-sized powerhouse, transforms voltage seamlessly, providing a reliable and efficient energy source for your projects.
A
A
Hardware Overview
How does it work?
Nano Power 3 Click is based on the RPL-3.0-R, a buck converter with an integrated inductor from Recom Power. This thermally-enhanced converter uses, as input, voltage from 4 up to 18VDC, thus allowing 5V and 12V supply rails to be used. It's fully protected against continuous short circuits, output overcurrent, or over-temperature faults. To set the output voltage on the VOUT terminal, the Nano Power 3 Click uses the MAX5419, a 256-tap nonvolatile digital potentiometer from Analog Devices. This potentiometer features the power-on recall of the wiper position from nonvolatile EEPROM memory. The nominal resistance of this
potentiometer is 200kΩ, and with an onboard resistor, it makes a voltage divider that feeds the feedback input of the buck converter. You select the output voltage value by setting the resistance value on this potentiometer. Nano Power 3 Click uses a standard 2-Wire I2C interface of the MAX5419 to communicate with the host MCU, supporting Fast mode and data rates of up to 400Kbps. The I2C address can be set over the ADDR SEL jumper with 0 selected by default. In addition to the digital potentiometer control, you can also control the buck converter by turning it OFF via the CTR pin. The PG pin serves as the buck
converter Power Good condition output, which interrupts the host MCU according to meeting one of the overvoltage or undervoltage thresholds and sink current capability. The buck converter's output voltage can be read over the AN pin of the mikroBUS™ socket. 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.
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
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 Nano Power 3 Click driver.
Key functions:
nanopower3_set_ctr_pin
- Nano Power 3 set CTRL pin state function.nanopower3_set_wiper_pos
- Nano Power 3 set wiper position function.nanopower3_set_voltage
- Nano Power 3 set output voltage 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 main.c
* @brief Nano Power 3 Click example
*
* # Description
* This library contains API for the Nano Power 3 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 1 V.
*
* ## Application Task
* This example demonstrates the use of the Nano Power 3 Click board™ by changing
* output voltage every 5 seconds starting from 1 V up to 4.5 V.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "nanopower3.h"
static nanopower3_t nanopower3;
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. */
nanopower3_cfg_t nanopower3_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.
nanopower3_cfg_setup( &nanopower3_cfg );
NANOPOWER3_MAP_MIKROBUS( nanopower3_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == nanopower3_init( &nanopower3, &nanopower3_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( NANOPOWER3_ERROR == nanopower3_default_cfg ( &nanopower3 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
for ( uint8_t n_cnt = NANOPOWER3_1V_OUT_VOLTAGE; n_cnt <= NANOPOWER3_4V5_OUT_VOLTAGE; n_cnt++ )
{
nanopower3_set_voltage( &nanopower3, 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 ( NANOPOWER3_1V_OUT_VOLTAGE ):
{
log_printf( &logger, " 1V\r\n" );
break;
}
case ( NANOPOWER3_1V2_OUT_VOLTAGE ):
{
log_printf( &logger, " 1.2V\r\n" );
break;
}
case ( NANOPOWER3_1V5_OUT_VOLTAGE ):
{
log_printf( &logger, " 1.5V\r\n" );
break;
}
case ( NANOPOWER3_1V8_OUT_VOLTAGE ):
{
log_printf( &logger, " 1.8V\r\n" );
break;
}
case ( NANOPOWER3_2V_OUT_VOLTAGE ):
{
log_printf( &logger, " 2V\r\n" );
break;
}
case ( NANOPOWER3_2V5_OUT_VOLTAGE ):
{
log_printf( &logger, " 2.5V\r\n" );
break;
}
case ( NANOPOWER3_3V_OUT_VOLTAGE ):
{
log_printf( &logger, " 3V\r\n" );
break;
}
case ( NANOPOWER3_3V3_OUT_VOLTAGE ):
{
log_printf( &logger, " 3.3V\r\n" );
break;
}
case ( NANOPOWER3_3V5_OUT_VOLTAGE ):
{
log_printf( &logger, " 3.5V\r\n" );
break;
}
case ( NANOPOWER3_4V_OUT_VOLTAGE ):
{
log_printf( &logger, " 4V\r\n" );
break;
}
case ( NANOPOWER3_4V5_OUT_VOLTAGE ):
{
log_printf( &logger, " 4.5V\r\n" );
break;
}
default:
{
log_printf( &logger, " ERROR\r\n" );
}
}
}
// ------------------------------------------------------------------------ END