Our PGA solution enables seamless signal amplification with customizable gain settings, making it the ideal choice for your applications where precision and flexibility are paramount
A
A
Hardware Overview
How does it work?
GainAMP Click is based on the LTC6912, a dual channel, low noise, digitally programmable gain amplifier (PGA) from Analog Devices. The click is designed to work on either a 3.3V or 5V power supply. It communicates with the target MCU over the SPI interface, with additional functionality provided by the following pins on the mikroBUS™ line: AN, RST. GainAMP Click also features three
screw terminals and a power indication LED. The gains for both channels are independently programmable, using a 3-wire SPI interface to select voltage gains of 0, 1, 2, 5, 10, 20, 50, and 100V/V (LTC6912-1). All gains are inverting. The LTC6912 consists of 2 matched amplifiers with rail-to-rail outputs. When operated with unity gain, they will also process rail-to-rail input signals.
A half-supply reference generated internally at the AGND pin supports single power supply applications. It operates from single or split supplies from 2.7V to 10.5V in total. A programmable-gain amplifier (PGA) is an electronic amplifier whose gain can be controlled externally (by analog or digital signals).
Features overview
Development board
Nucleo 32 with STM32F031K6 MCU board provides an affordable and flexible platform for experimenting with STM32 microcontrollers in 32-pin packages. Featuring Arduino™ Nano connectivity, it allows easy expansion with specialized shields, while being mbed-enabled for seamless integration with online resources. The
board includes an on-board ST-LINK/V2-1 debugger/programmer, supporting USB reenumeration with three interfaces: Virtual Com port, mass storage, and debug port. It offers a flexible power supply through either USB VBUS or an external source. Additionally, it includes three LEDs (LD1 for USB communication, LD2 for power,
and LD3 as a user LED) and a reset push button. The STM32 Nucleo-32 board is supported by various Integrated Development Environments (IDEs) such as IAR™, Keil®, and GCC-based IDEs like AC6 SW4STM32, making it a versatile tool for developers.
Microcontroller Overview
MCU Card / MCU

Architecture
ARM Cortex-M0
MCU Memory (KB)
32
Silicon Vendor
STMicroelectronics
Pin count
32
RAM (Bytes)
4096
You complete me!
Accessories
Click Shield for Nucleo-32 is the perfect way to expand your development board's functionalities with STM32 Nucleo-32 pinout. The Click Shield for Nucleo-32 provides two mikroBUS™ sockets to add any functionality from our ever-growing range of Click boards™. We are fully stocked with everything, from sensors and WiFi transceivers to motor control and audio amplifiers. The Click Shield for Nucleo-32 is compatible with the STM32 Nucleo-32 board, providing an affordable and flexible way for users to try out new ideas and quickly create prototypes with any STM32 microcontrollers, choosing from the various combinations of performance, power consumption, and features. The STM32 Nucleo-32 boards do not require any separate probe as they integrate the ST-LINK/V2-1 debugger/programmer and come with the STM32 comprehensive software HAL library and various packaged software examples. This development platform provides users with an effortless and common way to combine the STM32 Nucleo-32 footprint compatible board with their favorite Click boards™ in their upcoming projects.
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 GainAMP Click driver.
Key functions:
gainamp_read_an_pin_value
- GainAMP read AN pin value functiongainamp_read_an_pin_voltage
- GainAMP read AN pin voltage level functiongainamp_set_gain
- Function for sets gain of the GainAMP Click
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 GainAMP Click example
*
* # Description
* This is an example that demonstrates the use of the GainAMP Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes SPI module and set CS pin and RST pin as OUTPUT,
* initialization driver init and resets chip.
*
* ## Application Task
* Sets the gain for both channels, channel A and channel B.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "gainamp.h"
static gainamp_t gainamp;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
gainamp_cfg_t gainamp_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.
gainamp_cfg_setup( &gainamp_cfg );
GAINAMP_MAP_MIKROBUS( gainamp_cfg, MIKROBUS_1 );
err_t init_flag = gainamp_init( &gainamp, &gainamp_cfg );
if ( ( SPI_MASTER_ERROR == init_flag ) || ( ADC_ERROR == init_flag ) ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
gainamp_reset( &gainamp );
Delay_ms( 100 );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
gainamp_set_gain( &gainamp, GAINAMP_CHANNEL_A_x1 | GAINAMP_CHANNEL_B_x5 );
Delay_ms( 10000 );
gainamp_set_gain( &gainamp, GAINAMP_CHANNEL_A_x10 | GAINAMP_CHANNEL_B_x100 );
Delay_ms( 10000 );
}
void main ( void )
{
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END