Don't just manage voltage, master it! Our synchronous buck converter navigates voltage challenges with precision for optimal power performance.
A
A
Hardware Overview
How does it work?
Step Down 9 Click is based on the MAX20406, an automotive fully integrated synchronous silent switcher buck converter from Analog Devices. It is a low EMI emission buck converter with integrated high-side and low-side switches and can operate in dropout by running at a 99% duty cycle. The Step Down 9 Click uses a TPL0501 digital potentiometer in a resistor divider configuration for an external output voltage adjustment. The TPL0501 is a single-channel digital potentiometer with an SPI interface from Texas Instruments. It has a 256-position resolution and 100KΩ of end-to-end resistance. As mentioned, the Step Down 9 Click uses the TPL0501 and its 3-Wire SPI serial interface to communicate with the host MCE, supporting clock frequency of up to 25MHz. The
voltage quality can be monitored by observing the PGOOD signal over the PG pin of the mikroBUS™ socket. The enable EN pin is an input for circuit activation, active with a HIGH logic state. This Click board™ is also equipped with a 5-pin header that lets you use additional features of the MAX20406. The converter can use dual-phase operation for high-current applications, which is intended for forced-PWM mode only. If in forced-PWM mode, the SYO pin will be 180 degrees out of phase with the controller clock. If in Skip mode, then no clock will be present on the SYO pin. To set the skip mode, connect the SYI pin to the GND; otherwise, the forced-PWM mode will be selected if you connect the SYI to BIAS. VEA is an internal voltage loop error-amplifier output needed for
dual-phase operation. The MAX20406 can be configured as a controller or a target. While SYO is connected to the BIAS and the converter is enabled, there will be a procedure to detect if it is a controller or a target. In controller configuration, you can use a VEA pin to connect to a VEA of a target to ensure balanced current sharing between two phases. For more info, check the MAX20406’s datasheet. 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 for further development.
Features overview
Development board
EasyAVR v7 is the seventh generation of AVR development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 16-bit AVR microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyAVR v7 allows you to connect accessory boards, sensors, and custom electronics more
efficiently than ever. Each part of the EasyAVR v7 development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use a wide range of external power sources, including an external 12V power supply, 7-12V AC or 9-15V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B)
connector. Communication options such as USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets which cover a wide range of 16-bit AVR MCUs. EasyAVR v7 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development 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
AVR
MCU Memory (KB)
64
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
4096
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 Step Down 9 Click driver.
Key functions:
stepdown9_set_en_pin
- Step Down 9 set EN pin state function.stepdown9_set_wiper_pos
- Step Down 9 set wiper position.stepdown9_set_output
- Step Down 9 set output voltage.
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 Step Down 9 Click example
*
* # Description
* This library contains API for the Step Down 9 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.6 V.
*
* ## Application Task
* This example demonstrates the use of the Step Down 9 Click board™ by changing
* output voltage every 5 seconds starting from 1.6 V up to 10 V.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "stepdown9.h"
static stepdown9_t stepdown9;
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. */
stepdown9_cfg_t stepdown9_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.
stepdown9_cfg_setup( &stepdown9_cfg );
STEPDOWN9_MAP_MIKROBUS( stepdown9_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == stepdown9_init( &stepdown9, &stepdown9_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( STEPDOWN9_ERROR == stepdown9_default_cfg ( &stepdown9 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
for ( uint8_t n_cnt = STEPDOWN9_VOUT_1V6; n_cnt <= STEPDOWN9_VOUT_10V; n_cnt++ )
{
stepdown9_set_output( &stepdown9, 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 ( STEPDOWN9_VOUT_1V6 ):
{
log_printf( &logger, " 1.6V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_2V ):
{
log_printf( &logger, " 2V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_2V5 ):
{
log_printf( &logger, " 2.5V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_3V ):
{
log_printf( &logger, " 3V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_3V3 ):
{
log_printf( &logger, " 3.3V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_3V5 ):
{
log_printf( &logger, " 3.5V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_4V ):
{
log_printf( &logger, " 4V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_4V5 ):
{
log_printf( &logger, " 4.5V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_5V ):
{
log_printf( &logger, " 5V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_5V5 ):
{
log_printf( &logger, " 5.5V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_6V ):
{
log_printf( &logger, " 6V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_6V5 ):
{
log_printf( &logger, " 6.5V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_7V ):
{
log_printf( &logger, " 7V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_7V5 ):
{
log_printf( &logger, " 7.5V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_8V ):
{
log_printf( &logger, " 8V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_8V5 ):
{
log_printf( &logger, " 8.5V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_9V ):
{
log_printf( &logger, " 9V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_9V5 ):
{
log_printf( &logger, " 9.5V\r\n" );
break;
}
case ( STEPDOWN9_VOUT_10V ):
{
log_printf( &logger, " 10V\r\n" );
break;
}
default:
{
log_printf( &logger, " ERROR\r\n" );
}
}
}
// ------------------------------------------------------------------------ END