Unlock a new level of precision in UART signal routing with SN74LV4052A and PIC32MZ2048EFM100
Breaking the barriers of serial routing: Redefine your UART connectivity experience!
Published Sep 21, 2023
Click board™
UART MUX Click
Dev. board
Curiosity PIC32 MZ EF
Compiler
NECTO Studio
MCU
PIC32MZ2048EFM100
With our UART line-switching solution, you can confidently address applications such as multi-device communication, data logging, and UART interface management, where precise and flexible routing is essential
A
A
Hardware Overview
How does it work?
UART MUX Click is based on the SN74LV4052A, a dual 4-channel multiplexer and demultiplexer from Texas Instruments. Two control pins are used to switch to one of four available outputs, from a single UART input, from the mikroBUS™. Control pins labeled as A and B, are routed to the mikroBUS™ and can be operated by both 3.3V and 5V MCUs. The fourth control pin is labeled as EN pin, and it is used to enable the internal multiplexing switches of the IC, when is set to a HIGH logic level (it is active HIGH). A and B pins are routed to CS and PWM pins of the mikroBUS™ respectively. The active low Inhibit (INH) tri-state all the channels when high and when low, depending on the A and B inputs, one of the four independent input/outputs is connected to the
UART communication pins. INH pin is routed to the RST pin on the mikroBUS™. The ultra-low leakage current ensures that there is no signal interference from the inputs that are not selected by the A and B pins. A low crosstalk also ensures that the signal on one channel remains clean of interferences caused by other channels. This ensures a reliable operation of the IC and the Click board™ itself. The output signals can be connected via the 2x4 pin headers. Besides RX and TX pins, every output also has dedicated VCC and GND pins avalilable, so that user can easily route multple devices with this Click board™. 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 the limits. More information about the SN74LV4052A 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. 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
Curiosity PIC32 MZ EF development board is a fully integrated 32-bit development platform featuring the high-performance PIC32MZ EF Series (PIC32MZ2048EFM) that has a 2MB Flash, 512KB RAM, integrated FPU, Crypto accelerator, and excellent connectivity options. It includes an integrated programmer and debugger, requiring no additional hardware. Users can expand
functionality through MIKROE mikroBUS™ Click™ adapter boards, add Ethernet connectivity with the Microchip PHY daughter board, add WiFi connectivity capability using the Microchip expansions boards, and add audio input and output capability with Microchip audio daughter boards. These boards are fully integrated into PIC32’s powerful software framework, MPLAB Harmony,
which provides a flexible and modular interface to application development a rich set of inter-operable software stacks (TCP-IP, USB), and easy-to-use features. The Curiosity PIC32 MZ EF development board offers expansion capabilities making it an excellent choice for a rapid prototyping board in Connectivity, IOT, and general-purpose applications.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC32
MCU Memory (KB)
2048
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
524288
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Curiosity PIC32 MZ EF as your development board.
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 UART MUX Click driver.
Key functions:
uartmux_send_command- Send commanduartmux_set_inhibit_communication- Set INT pinuartmux_choose_channel- Choose channel
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 UartMux Click example
*
* # Description
* This example reads and processes data from UART Mux clicks.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes driver.
*
* ## Application Task
* Reads the received data.
*
* ## Additional Function
* - uartmux_process ( ) - The general process of collecting response
* from module.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "uartmux.h"
#include "string.h"
#define PROCESS_COUNTER 10
#define PROCESS_RX_BUFFER_SIZE 500
#define TEXT_TO_SEND "MikroE\r\n"
// ------------------------------------------------------------------ VARIABLES
#define DEMO_APP_RECEIVER
// #define DEMO_APP_TRANSMITER
static uartmux_t uartmux;
static log_t logger;
static uartmux_channel_t channel;
static int32_t rsp_size;
static char uart_rx_buffer[ PROCESS_RX_BUFFER_SIZE ] = { 0 };
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
static void uartmux_process ( void )
{
rsp_size = uartmux_generic_read( &uartmux, &uart_rx_buffer, PROCESS_RX_BUFFER_SIZE, &channel );
if ( rsp_size > 0 )
{
for ( int32_t cnt = 0; cnt < rsp_size; cnt++ )
{
log_printf( &logger, "%c", uart_rx_buffer[ cnt ] );
}
}
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
uartmux_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.
uartmux_cfg_setup( &cfg );
UARTMUX_MAP_MIKROBUS( cfg, MIKROBUS_1 );
uartmux_init( &uartmux, &cfg );
uartmux_set_inhibit_communication( &uartmux, UARTMUX_PIN_STATE_LOW );
}
void application_task ( void )
{
#ifdef DEMO_APP_RECEIVER
uartmux_process( );
#endif
#ifdef DEMO_APP_TRANSMITER
channel.state_a = UARTMUX_STATE_A_CHANNEL_1;
channel.state_b = UARTMUX_STATE_B_CHANNEL_1;
uartmux_generic_write( &uartmux, TEXT_TO_SEND, strlen( TEXT_TO_SEND ), &channel );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
#endif
}
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
