Beginner
10 min
0

Protect your signals while maintaining uninterrupted communication using ADM3260 and STM32F215ZG

Power and data protection in one elegant package!

I2C Isolator 2 Click with Fusion for ARM v8

Published Nov 02, 2023

Click board™

I2C Isolator 2 Click

Development board

Fusion for ARM v8

Compiler

NECTO Studio

MCU

STM32F215ZG

Redefine your I2C isolation experience with our hot-swappable isolator, where power and data protection merge seamlessly, simplifying your setup and enhancing system reliability.

A

A

Hardware Overview

How does it work?

I2C Isolator 2 Click is based on the ADM3260, a hot-swappable dual I2C isolator with an integrated DC-to-DC converter from Analog Devices. The digital isolator block is on each side of a bidirectional I2C signal. Internally, the I2C interface is split into two unidirectional channels communicating in opposing directions via a dedicated iCoupler isolation channel for each. One channel senses the voltage state of one side and transmits its state to its respective second side.

This isolator can achieve I2C clock speeds of up to 1MHz and supports 3 - 5.5V logic levels. I2C Isolator 2 Click uses a standard 2-Wire I2C interface to allow isolated communication between the host MCU and the connected I2C device. The isolator allows you to disable the I2C communication over the PDIS pin, which, with a High logic level, puts the isolator in standby mode. The I2C Isolator 2 Click is equipped with the VIO ISO jumper, which allows you to work with isolated different logic

levels. The 3V3 is set by default. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VIO 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.

I2C Isolator 2 Click top side image
I2C Isolator 2 Click bottom side image

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.

Fusion for ARM v8 horizontal image

Microcontroller Overview

MCU Card / MCU

default

Type

8th Generation

Architecture

ARM Cortex-M3

MCU Memory (KB)

1024

Silicon Vendor

STMicroelectronics

Pin count

144

RAM (Bytes)

131072

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
NC
NC
RST
NC
NC
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
Power Disable
PD12
PWM
NC
NC
INT
NC
NC
TX
NC
NC
RX
I2C Clock
PB8
SCL
I2C Data
PB9
SDA
Power Supply
5V
5V
Ground
GND
GND
1

Take a closer look

Schematic

I2C Isolator 2 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 Fusion for ARM 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 I2C Isolator 2 Click driver.

Key functions:

  • i2cisolator2_write - This function writes a desired data to I2C bus.

  • i2cisolator2_read - This function reads a desired number of data bytes from I2C bus.

  • i2cisolator2_set_slave_address - This function sets the slave address.

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 I2C Isolator 2 Click example
 * 
 * # Description
 * This example showcases how to initialize, configure and use the I2C Isolator 2 click module.
 * The click provides I2C lines and power isolation for slave devices. In order for this 
 * example to work, you need the EEPROM 3 click.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Initializes the driver and enables the power output.
 * 
 * ## Application Task  
 * Writes the desired message to EEPROM 3 click board and reads it back every 2 seconds.
 * All data is being displayed on the USB UART where you can track the program flow.
 * 
 * @note
 * Make sure to provide the VCC power supply on VCC pin and EEPROM 3 click.
 * 
 * \author MikroE Team
 *
 */
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "i2cisolator2.h"

// ------------------------------------------------------------------ VARIABLES

#define EEPROM3_MEMORY_ADDRESS   0x10000ul
#define EEPROM3_SLAVE_ADDRESS    0x54
#define EEPROM3_DEMO_TEXT        "MikroE - I2C Isolator 2 with EEPROM 3 click!"

static i2cisolator2_t i2cisolator2;
static log_t logger;

// ------------------------------------------------------ ADDITIONAL FUNCTIONS

err_t eeprom3_write_page( uint32_t address, uint8_t *data_in, uint8_t len )
{
    uint8_t data_buf[ 257 ] = { 0 };
    uint8_t slave_addr = ( uint8_t ) ( ( address >> 16 ) & 0x03 ) | EEPROM3_SLAVE_ADDRESS;
    i2cisolator2_set_slave_address ( &i2cisolator2, slave_addr );
    data_buf[ 0 ] = ( uint8_t ) ( ( address >> 8 ) & 0xFF );
    data_buf[ 1 ] = ( uint8_t ) ( address & 0xFF );
    for ( uint8_t cnt = 0; cnt < len; cnt++ )
    {
        data_buf[ cnt + 2 ] = data_in[ cnt ];
    }
    return i2cisolator2_write( &i2cisolator2, data_buf, len + 2 );
}

err_t eeprom3_read_page( uint32_t address, uint8_t *data_out, uint8_t len )
{
    uint8_t data_buf[ 2 ] = { 0 };
    uint8_t slave_addr = ( uint8_t ) ( ( address >> 16 ) & 0x03 ) | EEPROM3_SLAVE_ADDRESS;
    i2cisolator2_set_slave_address ( &i2cisolator2, slave_addr );
    data_buf[ 0 ] = ( uint8_t ) ( ( address >> 8 ) & 0xFF );
    data_buf[ 1 ] = ( uint8_t ) ( address & 0xFF );
    err_t error_flag = i2cisolator2_write( &i2cisolator2, data_buf, 2 );
    error_flag |= i2cisolator2_read( &i2cisolator2, data_out, len );
    return error_flag;
}
// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init ( )
{
    log_cfg_t log_cfg;
    i2cisolator2_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.
    i2cisolator2_cfg_setup( &cfg );
    I2CISOLATOR2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    i2cisolator2_init( &i2cisolator2, &cfg );
    
    i2cisolator2_enable_power( &i2cisolator2, I2CISOLATOR2_POWER_ENABLE );
    Delay_ms( 100 );

    log_info( &logger, " Application Task " );
}

void application_task ( )
{
    uint8_t read_buf[ 100 ] = { 0 };
    if ( I2CISOLATOR2_OK == eeprom3_write_page ( EEPROM3_MEMORY_ADDRESS, EEPROM3_DEMO_TEXT, 
                                                 strlen( EEPROM3_DEMO_TEXT ) ) )
    {
        log_printf( &logger, " Demo text message is written to EEPROM 3 click!\r\n" );
    }
    Delay_ms( 1000 );
    
    if ( I2CISOLATOR2_OK == eeprom3_read_page ( EEPROM3_MEMORY_ADDRESS, read_buf, 
                                                strlen( EEPROM3_DEMO_TEXT ) ) )
    {
        read_buf[ strlen( EEPROM3_DEMO_TEXT ) ] = 0;
        log_printf( &logger, " Read data: \"%s\"\r\n\n", read_buf );
    }
    Delay_ms( 1000 );
}

void main ( )
{
    application_init( );

    for ( ; ; )
    {
        application_task( );
    }
}

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

Additional Support

Resources