Step into a world of seamless signal routing with our CMOS analog multiplexing solution. Engineered for precision and flexibility, it empowers you to channel and manage various signals with efficiency and accuracy
A
A
Hardware Overview
How does it work?
MUX Click is based on the MUX509, a precise analog multiplexing IC from Texas Instruments. The MUX509 can be used with a wide range of power supplies. It can handle dual and single power supplies and symmetrical and non-symmetrical ones. This allows it to be used in a wide range of different applications. Another property of the MUX509 is that it has dual inputs and dual output. Three control pins switch one of four input pairs to a single output pair. Control pins labeled A0 and A1 are routed to the mikroBUS™ and can be operated by both 3.3V and 5V MCUs. The third control pin, labeled as EN pin, is used to enable the output when set to a HIGH logic level (active HIGH). A0 and A1 pins are routed to the RST and PWM pins of the mikroBUS™, respectively, while the EN pin is routed to the CS pin on the mikroBUS™. The MUX509 IC is targeted toward working with differential signals rather than single-ended inputs. Each input comprises two pins: SNA, and SNB, where N represents the channel number from 1 to 4. When a specific
channel is selected (N), the SNA and SNB pins will be routed to the DA and DB output pins. Each signal pair is equipped with a 100nF parallel capacitor and 100Ω series resistance for improved stability. The input and the output signal pins are routed to the standard 2.54mm pitch 2x5 pins header on the Click board™. The ultra-low leakage current ensures no signal interference from the inputs not selected by the A0 and A1 pins. Low crosstalk also ensures that the signal on one channel remains clean of interferences caused by other channels. The break-before-make switching action prevents any two inputs from being switched simultaneously at the output. This ensures the reliable operation of the IC and the Click board™ itself. MUX click does not use the power from the mikroBUS™ power rails, except for the LED indicator. Instead, a three-pole screw terminal connects an external power supply. Considering the minimum input voltage of 10V or ±5V, a power supply should be connected to this terminal before operating the Click board™.
Depending on the type of the used power supply (single supply or symmetrical/dual supply), it should be connected to the power supply input terminal, accordingly: GND is the reference ground connection, VSS is the negative voltage connection terminal (GND if a single power supply is used), and VDD is the positive voltage connection terminal. The input and output signals can be connected via the 2x5 pins header. As mentioned, the MUX509 IC supports rail-to-rail operation, supporting input and output signals ranging from VSS (or GND) up to VDD. Independent power supply input allows the user to work with a wide range of signal amplitudes, depending on the application requirements, as long as the power supply stays within limits. More information about the MUX509 can be found in the attached datasheet. However, the Click board™ comes equipped with a library that contains easy-to-use functions and a usage example that may be used as a reference for the development.
Features overview
Development board
Nucleo-64 with STM32F103RB MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M3
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
20480
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
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
This Click board can be interfaced and monitored in two ways:
Application Output
- Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
UART Terminal
- Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Software Support
Library Description
This library contains API for MUX Click driver.
Key functions:
mux_active_mux_channel
- Select active MUX channelmux_device_disable
- Disable MUX device functionmux_device_enable
- Enable MUX device function
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
* \brief MUX Click example
*
* # Description
* Sets the current active channel. Changes the channel every 5 sec.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes GPIO module and sets RST, CS and PWM pins as OUTPUT.
*
* ## Application Task
* Changes currently active channel every 5 sec.
*
* \author Luka Filipovic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "mux.h"
// ------------------------------------------------------------------ VARIABLES
static mux_t mux;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
mux_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.
mux_cfg_setup( &cfg );
MUX_MAP_MIKROBUS( cfg, MIKROBUS_1 );
mux_init( &mux, &cfg );
Delay_ms ( 100 );
log_printf( &logger, " MUX Click\r\n" );
log_printf( &logger, "------------------------\r\n" );
mux_device_enable( &mux );
log_printf( &logger, " Enable MUX device\r\n" );
log_printf( &logger, "------------------------\r\n" );
Delay_ms ( 100 );
}
void application_task ( void )
{
uint16_t n_cnt;
for ( n_cnt = MUX_CHANNEL_1A_AND_1B; n_cnt < MUX_CHANNEL_END; n_cnt++ )
{
log_printf( &logger, " CHANNEL S%u\r\n", n_cnt );
log_printf( &logger, "------------------------\r\n" );
mux_active_mux_channel( &mux, n_cnt );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
/*!
* \file
* \brief MUX Click example
*
* # Description
* Sets the current active channel. Changes the channel every 5 sec.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes GPIO module and sets RST, CS and PWM pins as OUTPUT.
*
* ## Application Task
* Changes currently active channel every 5 sec.
*
* \author Luka Filipovic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "mux.h"
// ------------------------------------------------------------------ VARIABLES
static mux_t mux;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
mux_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.
mux_cfg_setup( &cfg );
MUX_MAP_MIKROBUS( cfg, MIKROBUS_1 );
mux_init( &mux, &cfg );
Delay_ms ( 100 );
log_printf( &logger, " MUX Click\r\n" );
log_printf( &logger, "------------------------\r\n" );
mux_device_enable( &mux );
log_printf( &logger, " Enable MUX device\r\n" );
log_printf( &logger, "------------------------\r\n" );
Delay_ms ( 100 );
}
void application_task ( void )
{
uint16_t n_cnt;
for ( n_cnt = MUX_CHANNEL_1A_AND_1B; n_cnt < MUX_CHANNEL_END; n_cnt++ )
{
log_printf( &logger, " CHANNEL S%u\r\n", n_cnt );
log_printf( &logger, "------------------------\r\n" );
mux_active_mux_channel( &mux, n_cnt );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
/*!
* \file
* \brief MUX Click example
*
* # Description
* Sets the current active channel. Changes the channel every 5 sec.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes GPIO module and sets RST, CS and PWM pins as OUTPUT.
*
* ## Application Task
* Changes currently active channel every 5 sec.
*
* \author Luka Filipovic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "mux.h"
// ------------------------------------------------------------------ VARIABLES
static mux_t mux;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
mux_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.
mux_cfg_setup( &cfg );
MUX_MAP_MIKROBUS( cfg, MIKROBUS_1 );
mux_init( &mux, &cfg );
Delay_ms ( 100 );
log_printf( &logger, " MUX Click\r\n" );
log_printf( &logger, "------------------------\r\n" );
mux_device_enable( &mux );
log_printf( &logger, " Enable MUX device\r\n" );
log_printf( &logger, "------------------------\r\n" );
Delay_ms ( 100 );
}
void application_task ( void )
{
uint16_t n_cnt;
for ( n_cnt = MUX_CHANNEL_1A_AND_1B; n_cnt < MUX_CHANNEL_END; n_cnt++ )
{
log_printf( &logger, " CHANNEL S%u\r\n", n_cnt );
log_printf( &logger, "------------------------\r\n" );
mux_active_mux_channel( &mux, n_cnt );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END