Experience the art of signal convergence with TMUX1208 and STM32F101ZG
Where signals converge, choices expand!
Published Aug 18, 2023
Click board™
MUX 3 Click
Dev Board
Fusion for ARM v8
Compiler
NECTO Studio
MCU
STM32F101ZG
Crafted for versatility and precision, our general-purpose CMOS multiplexer empowers you to effortlessly manage and direct various signals, expanding your options for seamless connectivity
A
A
Hardware Overview
How does it work?
MUX 3 Click is based on the TMUX1208, a 5-V Bidirectional 8:1, 1-Channel Multiplexer from Texas Instruments. The TMUX1208 is a general-purpose complementary metal-oxide semiconductor (CMOS) multiplexer (MUX). A wide operating supply of 1.08 V to 5.5 V allows use in various applications, from personal electronics to building automation applications. The device supports bidirectional analog and digital signals on the source (Sx) and drain (D) pins ranging from GND to VDD. All logic inputs have 1.8 V logic-compatible thresholds, ensuring TTL and CMOS logic compatibility when operating in the valid supply voltage range. Fail-Safe Logic circuitry allows voltages on the control pins to be applied before the supply pin, protecting the device from
potential damage. Break-before-make delay is a safety feature that prevents two inputs from connecting when switching devices. The output first breaks from the on-state switch before making the connection with the next on-state switch. The time delay between the break and the make is known as the break-before-make delay. One useful application for the TMUX1208 features is multiplexing various signals into an ADC integrated into an MCU. Utilizing an integrated ADC in the MCU allows a system to minimize cost with a potential tradeoff of system performance when compared to an external ADC. The multiplexer allows for multiple inputs/sensors to be monitored with a single ADC pin of the device, which is critical in systems with limited I/O. Given
all the features the TMUX1208 offers, the MUX 3 Click is best used for Analog and Digital Multiplexing / Demultiplexing, HVAC: Heating, Ventilation, and Air Conditioning, Smoke Detectors, Video Surveillance, Electronic Point of Sale, Battery-Powered Equipment, Appliances, Consumer Audio. 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.
Features overview
Development board
Fusion for ARM 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 ARM® Cortex®-M based 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, Fusion for ARM v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the Fusion for ARM 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. Fusion for ARM 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
Type
8th Generation
Architecture
ARM Cortex-M3
MCU Memory (KB)
1024
Silicon Vendor
STMicroelectronics
Pin count
144
RAM (Bytes)
81920
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Fusion for ARM v8 as your development board.
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.
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.
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".
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.
Software Support
Library Description
This library contains API for MUX 3 Click driver.
Key functions:
mux3_set_channel- Set active MUX channel 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
* \brief MUX 3 Click example
*
* # Description
* This application sets multiplexing one input channel to eight single-ended output channels.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization driver enable's - GPIO, also write log.
*
* ## Application Task
* This is an example which demonstrates the use of MUX 3 Click board.
* Sets the current active and changes the channel every 1 sec.
* Results are being sent to the Usart Terminal where you can track their changes.
* All data logs write on Usart Terminal changes for every 1 sec.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "mux3.h"
// ------------------------------------------------------------------ VARIABLES
static mux3_t mux3;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
mux3_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.
mux3_cfg_setup( &cfg );
MUX3_MAP_MIKROBUS( cfg, MIKROBUS_1 );
mux3_init( &mux3, &cfg );
}
void application_task ( void )
{
mux3_set_channel( &mux3, MUX3_ENABLE_CHANNEL_S1 );
log_printf( &logger, "Active channel: S1\r\n" );
Delay_1sec( );
mux3_set_channel( &mux3, MUX3_ENABLE_CHANNEL_S2 );
log_printf( &logger, "Active channel: S2\r\n" );
Delay_1sec( );
mux3_set_channel( &mux3, MUX3_ENABLE_CHANNEL_S3 );
log_printf( &logger, "Active channel: S3\r\n" );
Delay_1sec( );
mux3_set_channel( &mux3, MUX3_ENABLE_CHANNEL_S4 );
log_printf( &logger, "Active channel: S4\r\n" );
Delay_1sec( );
mux3_set_channel( &mux3, MUX3_ENABLE_CHANNEL_S5 );
log_printf( &logger, "Active channel: S5\r\n" );
Delay_1sec( );
mux3_set_channel( &mux3, MUX3_ENABLE_CHANNEL_S6 );
log_printf( &logger, "Active channel: S6\r\n" );
Delay_1sec( );
mux3_set_channel( &mux3, MUX3_ENABLE_CHANNEL_S7 );
log_printf( &logger, "Active channel: S7\r\n" );
Delay_1sec( );
mux3_set_channel( &mux3, MUX3_ENABLE_CHANNEL_S8 );
log_printf( &logger, "Active channel: S8\r\n" );
Delay_1sec( );
mux3_set_channel( &mux3, MUX3_DISABLE_ALL_CHANNELS );
log_printf( &logger, "Active channel: none\r\n" );
log_printf( &logger, "-------------------\r\n" );
Delay_1sec( );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
