Intermediate
30 min
0

Bipolar voltage booster made easy with LT3582 and PIC18F2685

Dual voltage dynamo

Boost-INV Click with EasyPIC v8

Published Nov 01, 2023

Click board™

Boost-INV Click

Development board

EasyPIC v8

Compiler

NECTO Studio

MCU

PIC18F2685

From positive to negative, we've got your voltage covered!

A

A

Hardware Overview

How does it work?

Boost-INV Click is based on the LT3582, a programmable boost and inverting DC/DC converter with OTP memory from Analog Devices. This IC is a dual circuit, offering a boost DC/DC converter and an inverter in one package. The boost converter can provide up to 12.78V on the output while driving the load with up to 350mA. The inverter can provide -13.95V, offering up to 600mA to the connected load, before the current limiting is activated. The boost converter uses an advanced switching scheme with the source-grounded NMOS as the main switching element, controlling the off-time and the peak current. The programmable voltage divider on the output provides the feedback voltage needed for the regulation. The inverter topology allows a single inductor to be used on the output, simplifying the design. As mentioned, the LT3582 features programmable parameters, which can be accessed via the I2C interface. These parameters include configuring the output voltages, power sequencing, and output voltage ramp rates. An onboard OTP non-volatile memory can be programmed with values that will be used at the startup. The command register (CMDR) is reset to 0x00h upon powering up, which turns off the outputs and sets the device to read parameters

stored in the OTP area. If the OTP memory area is empty, it is necessary to set up working parameters first (output voltage, power-up sequence, charging current for the ramp-up capacitors, and more) before using the device. It is worth mentioning that there are three bits in the CMDR register, referred to as RSEL0, RSEL1, and RSEL2 in the LT3582 datasheet, which redirects the device to use either registers or the OTP memory. When set to 0, the device uses parameters stored in the OTP memory. Note that 0x00h is the default value of the CMDR register, meaning settings stored in the OTP will be used by default after powering on. It is possible to dynamically change the values of the output voltages and other configurable working parameters. However, turning off the device (SWOFF bit of the CMDR register) is highly recommended before modifying working parameters since large output voltage changes can cause large current spikes on the switching circuitry if performed in real time while the switching circuit is running. Programming the OTP requires an external power source, which is fairly filtered (possibly with a filtering capacitor on the output). Voltage drop under 13V might trigger the FAULT bit and render the device unusable.

This voltage ranges from 13V to 15V. The Click board™ has the standard 2.54mm (100mil) header. Once the programming voltage is connected (VPP pad), the WOTP bit of the CMDR register initiates the programming. The complete algorithm with a detailed description of the OTP programming procedure can be found in the LT3582 datasheet. An onboard SMD jumper labeled as VSEL allows selection between the 3.3V and 5V power rail from mikroBUS™, routing it to the voltage input pin of the LT3582 IC. The I2C pull-up resistors are also connected to this voltage, allowing communication with both 3.3V and 5V MCUs. The Click board™ also offers the I2C address selection jumper, labeled as the I2C ADD. This jumper selects between two possible 7-bit addresses: the left position sets the I2C slave address to 0x49h, while the right position sets the address to 0x69h. Note that this is the 7-bit address only - to get the complete I2C address, an R/W bit needs to be added at the end. Input screw terminals allow secure connection for the load and are clearly labeled to avoid confusion: the V- pin offers the negative voltage, while the V+ pin outputs positive voltage. GND pins are connected to the common ground of the Click board™.

Boost-INV Click hardware overview image

Features overview

Development board

EasyPIC v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports many high pin count 8-bit PIC microcontrollers from Microchip, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer. 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, EasyPIC v8 provides a fluid and immersive working experience, allowing access anywhere and under any

circumstances at any time. Each part of the EasyPIC v8 development board contains the components necessary for the most efficient operation of the same board. In addition to the advanced integrated CODEGRIP programmer/debugger module, which offers many valuable programming/debugging options and seamless integration with the Mikroe software environment, the board 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 DEVICE, and CAN are also included, including the well-established mikroBUS™ standard, two display options (graphical and character-based LCD), and several different DIP sockets. These sockets cover a wide range of 8-bit PIC MCUs, from the smallest PIC MCU devices with only eight up to forty pins. EasyPIC 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.

EasyPIC v8 horizontal image

Microcontroller Overview

MCU Card / MCU

default

Architecture

PIC

MCU Memory (KB)

96

Silicon Vendor

Microchip

Pin count

28

RAM (Bytes)

3328

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
Chip Enable
RA0
RST
NC
NC
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
NC
NC
PWM
NC
NC
INT
NC
NC
TX
NC
NC
RX
I2C Clock
RC3
SCL
I2C Data
RC4
SDA
Power Supply
5V
5V
Ground
GND
GND
2

Take a closer look

Schematic

Boost-INV Click Schematic schematic

Step by step

Project assembly

EasyPIC v8 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the EasyPIC v8 as your development board.

EasyPIC v8 front image hardware assembly
LTE IoT 5 Click front image hardware assembly
MCU DIP 28 hardware assembly
LTE IoT 5 Click complete accessories setup image hardware assembly
EasyPIC v8 28pin-DIP Access - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
NECTO Compiler Selection Step Image hardware assembly
NECTO Output Selection Step Image hardware assembly
Necto image step 6 hardware assembly
Necto DIP image step 7 hardware assembly
Necto image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Necto PreFlash Image hardware 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

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

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

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

Software Support

Library Description

This library contains API for Boost-INV Click driver.

Key functions:

  • boostinv_enable - Functions for enable chip

  • boostinv_set_positive_voltage - Functions for set positive output voltage

  • boostinv_set_negative_voltage - Functions for set negative output voltage

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 
 * \brief BoostInv Click example
 * 
 * # Description
 * Changes the positive and negative output voltage. Input Voltage 3.3V.
 * Positive output voltage goes from 3200mV, 7750mV, 12000mV and 7750mV.
 * Negative output voltage goes from -1450mV, -6700mV, -11050mV and -6700mV.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Initializes I2C module and sets EN ( RST ) pin as output.
 * 
 * ## Application Task  
 * Changes the positive and negative output voltage every 5 sec.
 * 
 * \author Luka FIlipovic
 *
 */
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "boostinv.h"

// ------------------------------------------------------------------ VARIABLES

static boostinv_t boostinv;
static log_t logger;

// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init ( void )
{
    log_cfg_t log_cfg;
    boostinv_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.

    boostinv_cfg_setup( &cfg );
    BOOSTINV_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    boostinv_init( &boostinv, &cfg );
    
    boostinv_default_cfg ( &boostinv );
    log_printf( &logger, "     Boost INV Click\r\n" );
    log_printf( &logger, "-------------------------\r\n" );
    Delay_ms( 100 );
}

void application_task ( void )
{
    // Sets Positive output voltage
    
    log_printf( &logger, " Positive output voltage \r\n" );
    log_printf( &logger, "- - - - - - - - - - - - -\r\n" );
    log_printf( &logger, "          3200 mV\r\n" );
    log_printf( &logger, "-------------------------\r\n" );
    boostinv_set_positive_voltage( &boostinv, BOOSTINV_VOLTAGE_POSITIVE_3200_mV );
    Delay_ms( 5000 );
    
    log_printf( &logger, "          7750 mV\r\n" );
    log_printf( &logger, "-------------------------\r\n" );
    boostinv_set_positive_voltage( &boostinv, BOOSTINV_VOLTAGE_POSITIVE_7750_mV );
    Delay_ms( 5000 );
    
    log_printf( &logger, "        12000 mV\r\n" );
    log_printf( &logger, "-------------------------\r\n" );
    boostinv_set_positive_voltage( &boostinv, BOOSTINV_VOLTAGE_POSITIVE_12000_mV );
    Delay_ms( 5000 );
    
    log_printf( &logger, "         7750 mV\r\n" );
    log_printf( &logger, "-------------------------\r\n" );
    boostinv_set_positive_voltage( &boostinv, BOOSTINV_VOLTAGE_POSITIVE_7750_mV );
    Delay_ms( 5000 );
    
    // Sets Negative output voltage
    
    log_printf( &logger, " Negative output voltage \r\n" );
    log_printf( &logger, "- - - - - - - - - - - - -\r\n" );
    log_printf( &logger, "        -1450 mV\r\n" );
    log_printf( &logger, "-------------------------\r\n" );
    boostinv_set_negative_voltage( &boostinv, BOOSTINV_VOLTAGE_NEGATIVE_1450_mV );
    Delay_ms( 5000 );
    
    log_printf( &logger, "       - 6700 mV\r\n" );
    log_printf( &logger, "-------------------------\r\n" );
    boostinv_set_negative_voltage( &boostinv, BOOSTINV_VOLTAGE_NEGATIVE_6700_mV );
    Delay_ms( 5000 );
    
    log_printf( &logger, "       - 11050 mV\r\n" );
    log_printf( &logger, "-------------------------\r\n" );
    boostinv_set_negative_voltage( &boostinv, BOOSTINV_VOLTAGE_NEGATIVE_11050_mV );
    Delay_ms( 5000 );
    
    log_printf( &logger, "       - 6700 mV\r\n" );
    log_printf( &logger, "-------------------------\r\n" );
    boostinv_set_negative_voltage( &boostinv, BOOSTINV_VOLTAGE_NEGATIVE_6700_mV );
    Delay_ms( 5000 );
}

void main ( void )
{
    application_init( );

    for ( ; ; )
    {
        application_task( );
    }
}


// ------------------------------------------------------------------------ END

Additional Support

Resources