Effectively expand the capabilities of your I2C bus using TCA9546A and MK64FN1M0VDC12
Switch and multiplex signals with ease
Published Sep 10, 2023
Click board™
I2C MUX Click
Dev Board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
Our I2C multiplexer is designed to enhance and simplify your I2C communication by providing seamless control over multiple I2C devices, allowing you to efficiently manage address conflicts and streamline data exchange
A
A
Hardware Overview
How does it work?
I2C MUX Click is based on the TCA9546A, a quad bidirectional translating switch controlled via the I2C bus from texas instruments. The SCL/SDA upstream pair fans out to four downstream pairs, or channels. Any individual SCn/SDn channel or combination of channels can be selected, determined by the contents of the programmable control register. An active-low reset (RESET) input allows the TCA9546A to recover from a situation in which one of the downstream I2C buses is stuck in a low state. Pulling RESET low resets the I2C state machine and causes all the channels to be deselected, as does the internal power-on reset function. The pass gates of the switches are constructed such that the VCC pin can be used to limit the maximum high voltage, which will be passed by the TCA9546A. This allows the use of different bus voltages on each pair, so that 1.8-V, 2.5-V, or 3.3-V parts can communicate with 5-V parts without any additional protection. The slave
devices can be connected to four headers located on the top of the I2C MUX click. The TCA9546A supports Standard-Mode (100 kHz) and Fast-Mode (400 kHz) operation. This way, the bus can be used to manage a single 8-bit control register in which the four least significant bits control the enabling and disabling of the 4 switch channels of I2C data flow. The I2C bus is for two-way two-line communication between different ICs or modules. The two lines are a serial data line (SDA) and a serial clock line (SCL). Both lines must be connected to a positive supply via a pullup resistor when connected to the output stages of a device. Data transfer can be initiated only when the bus is not busy. One data bit is transferred during each clock pulse. The data on the SDA line must remain stable during the high period of the clock pulse, as changes in the data line at this time are interpreted as control signals. Applications of the TCA9546A contains an I2C (or SMBus) master
device and up to four I2C slave devices. The downstream channels are ideally used to resolve the I2C slave address conflicts. For example, if four identical digital temperature sensors are needed in the application, one sensor can be connected at each channel: 0, 1, 2, and 3. When the temperature at a specific location needs to be read, the appropriate channel can be enabled and all other channels switched off, the data can be retrieved, and the I2C master can move on and read the next channel. 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
Clicker 2 for Kinetis is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and
features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or
using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping 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
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
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 Clicker 2 for Kinetis as your development board.
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 I2C MUX Click driver.
Key functions:
i2cmux_hw_reset- This function resets I2C MUX 2 click board by clearing the RST pin for 100msi2cmux_set_channel- This function sets channel of the I2C MUX click boardi2cmux_generic_read- This function reads data from the desired register.
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 I2cMux Click example
*
* # Description
* This example demonstrates the use of I2C MUX Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initalizes the driver, preforms hardware reset, then enables channel 0 and
* makes an initial log.
*
* ## Application Task
* Reads the device ID of a Spectrometer click (dev ID: 0x24) and displays it
* on the USB UART each second.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "i2cmux.h"
// ------------------------------------------------------------------ VARIABLES
static i2cmux_t i2cmux;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
i2cmux_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.
i2cmux_cfg_setup( &cfg );
I2CMUX_MAP_MIKROBUS( cfg, MIKROBUS_1 );
i2cmux_init( &i2cmux, &cfg );
Delay_ms( 100 );
i2cmux_hw_reset( &i2cmux );
Delay_ms( 100 );
i2cmux_set_channel( &i2cmux, I2CMUX_CMD_SET_CH_0, 0x39 );
log_printf( &logger, " Please connect a Spectrometer click to channel 0\r\n" );
log_printf( &logger, "-------------------------------\r\n" );
Delay_ms( 2000 );
}
void application_task ( void )
{
uint8_t rx_data;
i2cmux_generic_read( &i2cmux, 0x92, &rx_data, 1 );
log_printf( &logger, " The click device ID is: 0x%.2X\r\n", ( uint16_t ) rx_data );
log_printf( &logger, "-------------------------------\r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
