Using our SPI isolator, you can effectively break electrical connections between different circuit parts, preventing interference, noise, and voltage mismatches that can disrupt data transmission
A
A
Hardware Overview
How does it work?
SPI Isolator 2 Click is based on the ISO7741, a high-performance quad-channel digital isolator capable of galvanic isolation up to 5000Vrms from Texas Instruments. It provides high electromagnetic immunity and low emissions at low power consumption while isolating digital I/Os. It has three forward and one reverse-direction channel and provides a compact solution for isolated SPI data communication. Each isolation channel has a logic input and output buffer separated by a double capacitive silicon dioxide insulation barrier. The ISO7741 digital isolator uses single-ended CMOS-logic switching technology and transmits the digital data across the isolation barrier. The transmitter sends a high-frequency carrier across the isolation barrier to represent one digital state and sends no signal to represent the other digital
state. After advanced signal conditioning, the receiver demodulates the signal and produces the output through a buffer stage. If the Enable pin is in a low logic state, the output signal goes to a Hi-Z state. SPI Isolator 2 Click communicates with MCU using the SPI serial interface with a maximum data rate of 100 Mbps. This Click board™ also comes with two enable pins on each side, which can be used to put the respective outputs in a Hi-Z state for multi-master driving applications and reduce power consumption. The enable pin on the digital side of ISO7741, labeled EN1, is routed on the RST pin of the mikroBUS™ socket, while the other Enable pin is connected to the external connector on the isolated side labeled as EN2. In addition to the connectors to which the isolated SPI data communication lines are
routed, this Click board™ has another additional representing an external power supply terminal. The voltage range is from 2.25 V to 5.5 V for supply logic and external, making it suitable for both 3.3V and 5V MCUs. The ISO7741 can also block high voltages, isolate grounds, and prevent noise currents on a data bus or other circuits from entering the local ground and damaging sensitive circuitry. 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
EasyAVR v7 is the seventh generation of AVR development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 16-bit AVR microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyAVR v7 allows you to connect accessory boards, sensors, and custom electronics more
efficiently than ever. Each part of the EasyAVR v7 development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use a wide range of external power sources, including an external 12V power supply, 7-12V AC or 9-15V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B)
connector. Communication options such as USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets which cover a wide range of 16-bit AVR MCUs. EasyAVR v7 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
Architecture
AVR
MCU Memory (KB)
32
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
2048
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 via UART Mode
1. Once the code example is loaded, pressing the "FLASH" button initiates the build process, and programs it on the created setup.
2. After the programming is completed, click on the Tools icon in the upper-right panel, and select the UART Terminal.
3. After opening the UART Terminal tab, first check the baud rate setting in the Options menu (default is 115200). If this parameter is correct, activate the terminal by clicking the "CONNECT" button.
4. Now 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 SPI Isolator 2 Click driver.
Key functions:
spiisolator2_output_enable
- The function enable or disable output ( isolation ) of the ISO7741spiisolator2_set_cmd
- The function sends the desired command to the ISO7741spiisolator2_write_byte
- The function writes the byte of data to the targeted 8-bit register address of the ISO7741
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 main.c
* @brief SPIIsolator2 Click example
*
* # Description
* This is an example that demonstrates the use of the SPI Isolator 2 click board.
* This board uses the ISO7741 which provides high electromagnetic immunity and low
* emissions at low power consumption while isolating digital I/Os. In this example,
* we write and then read data from the connected EEPROM 5 click to the SPI Isolator 2
* click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes SPI, begins to write log, set write/read memory address, enable output.
*
* ## Application Task
* Enables write to EEPROM, then writes the specified text message, and reads it back.
* All data is being displayed on the USB UART where you can track the program flow.
*
* @author Jelena Milosavljevic
*
*/
#include "board.h"
#include "log.h"
#include "spiisolator2.h"
static spiisolator2_t spiisolator2;
static log_t logger;
static uint8_t demo_data[ 7 ] = { 'M', 'i', 'k', 'r', 'o', 'E', 0 };
static uint8_t read_data[ 7 ] = { 0 };
static uint32_t memory_address = 1234;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
spiisolator2_cfg_t spiisolator2_cfg; /**< Click config object. */
/**
* 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.
spiisolator2_cfg_setup( &spiisolator2_cfg );
SPIISOLATOR2_MAP_MIKROBUS( spiisolator2_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == spiisolator2_init( &spiisolator2, &spiisolator2_cfg ) )
{
log_error( &logger, " Application Init Error. \r\n" );
log_info( &logger, " Please, run program again... \r\n" );
for ( ; ; );
}
Delay_ms( 100 );
spiisolator2_output_enable( &spiisolator2, SPIISOLATOR2_OUT_ENABLE );
log_info( &logger, " Application Task " );
Delay_ms( 100 );
}
void application_task ( void )
{
spiisolator2_set_cmd( &spiisolator2, SPIISOLATOR2_EEPROM5_CMD_WREN );
Delay_ms( 10 );
spiisolator2_multi_write( &spiisolator2,
( ( uint32_t ) SPIISOLATOR2_EEPROM5_CMD_WRITE << 24 ) | memory_address, 4, demo_data, 7 );
log_printf( &logger," Write data : %s\r\n", demo_data );
log_printf( &logger, "- - - - - - - - - - -\r\n" );
Delay_ms( 100 );
spiisolator2_multi_read( &spiisolator2,
( ( uint32_t ) SPIISOLATOR2_EEPROM5_CMD_READ << 24 ) | memory_address, 4, read_data, 7 );
Delay_ms( 1000 );
log_printf( &logger, " Read data : %s\r\n", read_data );
log_printf( &logger, "---------------------\r\n" );
Delay_ms( 5000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END