30 min

Switch between various analog inputs dynamically with ADG1438 and STM32F439ZG

Unveil possibilities with analog multiplexing

MUX 9 Click with UNI-DS v8

Published Aug 21, 2023

Click board™

MUX 9 Click

Development board



NECTO Studio



Optimize resource utilization, and enable several analog inputs to be efficiently combined and transmitted, saving space, energy, and resources



Hardware Overview

How does it work?

MUX 9 Click is based on the ADG1438, a serially controlled, 8-channel analog multiplexer from Analog Devices. Each switch is software-controlled (by a bit of the appropriate register) and conducts equally well in both directions, making it ideal for standard multiplexing and demultiplexing. Because each switch is independently controlled by an individual bit, this allows having any, all, or none of the switches on (logic 1 in a particular bit position turns the switch ON, whereas Logic 0 turns the switch OFF). This feature may be handy in the demultiplexing application, where the user may wish to direct one signal from the drain terminal, marked as D, to several outputs (sources). This Click board™ communicates with the MCU

through a standard SPI interface (compatible with SPI, QSPI™, MICROWIRE™, and DSP interface standards) supporting the most common SPI mode, SPI Mode 1, with a maximum frequency of 50MHz. During the Power-Up sequence, the internal shift register contains all zeros, and all switches are in the OFF state and remain so until a valid write takes place. This state can also be achieved with the help of an active-low reset pin, controlled via the RST pin of the mikroBUS™ socket. All switches are off by setting this pin to a low logic level, and the appropriate registers are cleared to 0. As for the input signal range, it extends over the power supply rails' capacity. The ADG1438 is specified for a wide supply

range ±15V/+12V/±5V, where all channels exhibit break-before-make switching action, preventing momentary shorting when switching channels. Also, these switches' ultra-low on-resistance and on-resistance flatness make them ideal solutions for data acquisition and gain switching applications where low distortion is critical. 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.

MUX 9 Click top side image
MUX 9 Click bottom side image

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.

UNI-DS v8 horizontal image

Microcontroller Overview

MCU Card / MCU



8th Generation


ARM Cortex-M4

MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


Used MCU Pins

mikroBUS™ mapper

SPI Chip Select
SPI Clock
Power Supply
Power Supply

Take a closer look


MUX 9 Click Schematic schematic

Step by step

Project assembly

Fusion for PIC v8 front image hardware assembly

Start by selecting your development board and Click board™. Begin with the UNI-DS v8 as your development board.

Fusion for PIC v8 front image hardware assembly
GNSS2 Click front image hardware assembly
SiBRAIN for PIC32MZ1024EFK144 front image hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
v8 SiBRAIN Access MB 1 - 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 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 MUX 9 Click driver.

Key functions:

  • mux9_active_channel - MUX 9 active channel function

  • mux9_reset - MUX 9 reset function

  • mux9_disable - MUX 9 disable function

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 MUX 9 Click example
 * # Description
 * This example demonstrates the use of MUX 9 click board™.
 * The demo application is composed of two sections :
 * ## Application Init
 * Initializes the driver and performs the reset.
 * ## Application Task
 * This is an example that shows the use of a MUX 9 click board™.
 * This example shows switching channels (from CH 1 to CH 8) on and off.
 * Results are being sent to the Usart Terminal where you can track their changes.
 * @author Nenad Filipovic

#include "board.h"
#include "log.h"
#include "mux9.h"

static mux9_t mux9;
static log_t logger;

void application_init ( void )
    log_cfg_t log_cfg;    /**< Logger config object. */
    mux9_cfg_t mux9_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.
    mux9_cfg_setup( &mux9_cfg );
    MUX9_MAP_MIKROBUS( mux9_cfg, MIKROBUS_1 );
    if ( SPI_MASTER_ERROR == mux9_init( &mux9, &mux9_cfg ) )
        log_error( &logger, " Communication init." );
        for ( ; ; );

    mux9_reset( &mux9 );
    log_info( &logger, " Application Task " );
    log_printf( &logger, " -----------\r\n" );

void application_task ( void )
    for ( uint8_t ch_pos = MUX9_SELECT_CH_1; ch_pos <= MUX9_SELECT_CH_8; ch_pos++ )
        if ( MUX9_OK == mux9_active_channel( &mux9, ch_pos ) )
            log_printf( &logger, " The Channel %d is activated. \r\n", ( uint16_t ) ch_pos );
            Delay_ms( 1000 );
    log_printf( &logger, " -----------\r\n" );
    Delay_ms( 1000 );

void main ( void )
    application_init( );

    for ( ; ; )
        application_task( );

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

Additional Support