Don't compromise on power - choose this boost converter for superior voltage regulation and consistent results every time!
A
A
Hardware Overview
How does it work?
Boost 7 Click is based on the LT1945, a dual step-up and inverted DC/DC converter from Rohm Semiconductor that boosts an input voltage to a higher level required by an output load. The BD8316GWL switching regulator feature integrated N-channel FETs and power P-channel MOSFETs alongside a Soft Start feature. Each converter inside the LT1945 is designed with up to 200mA current limit generating well-regulated positive and negative outputs of ±3.3V or ±5V, making the BD8316GWL ideal for various portable applications. As mentioned, the BD8316GWL can configure the positive and negative output voltage
in the ±3.3V or ±5V range. The desired output voltage can be selected by positioning SMD jumpers labeled as V- SEL and V+ SEL to an appropriate position. It is also possible to control the activity of the output channels via two mikroBUS™ pins, SB1 and SB2 pins. These pins are routed to a default position of the AN and PWM pins of the mikroBUS™ socket. By setting these pins to a high logic state, we put the converter outputs to an active state, and regulated voltages are available at the output terminals. In the same way, setting these pins to a low logic level disables the channels. 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. Additionally, there is a possibility for the BD8316GWL power supply selection via jumper labeled as VIN SEL to supply the BD8316GWL from an external power supply terminal in the range from 2.5V to 5.5V or with a selected voltage from mikroBUS™ power rails. However, the 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.
![Boost 7 Click hardware overview image](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee0b97a-3334-68f8-91d1-0242ac120005/boost-7-click-inner-img.jpg)
Features overview
Development board
UNI-DS v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different STM32, Kinetis, TIVA, CEC, MSP, PIC, dsPIC, PIC32, and AVR MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, UNI-DS v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the UNI-DS v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector. Communication options such as USB-UART, USB
HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. UNI-DS v8 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
![default](https://cdn.mikroe.com/rent-a-product/request-setup/mcu-cards/mcu-card-16-for-stm32-stm32l442kc.png)
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
256
Silicon Vendor
STMicroelectronics
Pin count
32
RAM (Bytes)
65536
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
![Boost 7 Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee790dd-5856-6bea-aa88-0242ac120009/schematic.webp)
Step by step
Project assembly
Track your results in real time
Application Output
After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.
![UART Application Output Step 1](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-40a0-6b58-88de-02420a00029a/UART-AO-Step-1.jpg)
Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.
![UART Application Output Step 2](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703a-eb29-62fa-ba91-02420a00029a/UART-AO-Step-2.jpg)
In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".
![UART Application Output Step 3](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703b-7543-6fbc-9c69-0242ac120003/UART-AO-Step-3.jpg)
The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
![UART Application Output Step 4](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed703c-068c-66a4-a4fc-0242ac120003/UART-AO-Step-4.jpg)
Software Support
Library Description
This library contains API for Boost 7 Click driver.
Key functions:
boost7_enable_out1
This function enables the OUT1 (V-) by setting the STB1 pin to high logic state.boost7_disable_out1
This function disables the OUT1 (V-) by setting the STB1 pin to low logic state.boost7_enable_out2
This function enables the OUT2 (V+) by setting the STB2 pin to high logic state.
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 Boost 7 Click Example.
*
* # Description
* This example demonstrates the use of Boost 7 click board by controlling
* the V- and V+ outputs state.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and logger.
*
* ## Application Task
* Toggles the V- and V+ outputs state every 5 seconds and displays their state
* on the USB UART.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "boost7.h"
static boost7_t boost7; /**< Boost 7 Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
boost7_cfg_t boost7_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.
boost7_cfg_setup( &boost7_cfg );
BOOST7_MAP_MIKROBUS( boost7_cfg, MIKROBUS_1 );
if ( DIGITAL_OUT_UNSUPPORTED_PIN == boost7_init( &boost7, &boost7_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
log_printf( &logger, " OUT1 (V-) : ENABLED\r\n" );
log_printf( &logger, " OUT2 (V+) : DISABLED\r\n\n" );
boost7_enable_out1 ( &boost7 );
boost7_disable_out2 ( &boost7 );
Delay_ms( 5000 );
log_printf( &logger, " OUT1 (V-) : DISABLED\r\n" );
log_printf( &logger, " OUT2 (V+) : ENABLED\r\n\n" );
boost7_disable_out1 ( &boost7 );
boost7_enable_out2 ( &boost7 );
Delay_ms( 5000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END