This isolator allows you to bridge the gap between systems with different ground references, ensuring that data is transmitted accurately and without disruptions
A
A
Hardware Overview
How does it work?
SPI Isolator 4 Click is based on the ADuM341E, a quad-channel digital isolator optimized for a serial peripheral interface from Analog Devices. This isolation component provides outstanding performance characteristics by combining high-speed and CMOS technology. It uses a high-frequency carrier to transmit data across the isolation barrier using iCoupler chip scale transformer coils separated by layers of polyimide isolation. Its data channels are independent and available in various configurations with a withstand voltage rating of 5kVrms. Using an ON/OFF keying (OOK) technique and the differential architecture, the ADuM341E has a very low propagation delay and high speed. It operates
with the external supply voltage ranging from 2.25V to 5.5V, providing compatibility with lower voltage systems and enabling voltage translation functionality across the isolation barrier. The ADuM341E architecture is designed for high common-mode transient (CMTI) immunity and high immunity to electrical noise and magnetic interference. Unlike other optocoupler alternatives, DC correctness is ensured without input logic transitions. Two different fail-safe options are available, by which the outputs go into a predetermined state when the input power supply is not applied or the inputs are disabled. SPI Isolator 4 Click communicates with an MCU using the SPI serial interface with a maximum data rate
of 100Mbps. This Click board™ also comes with an SDO line enable control pin, labeled as EN1, routed on the PWM pin of the mikroBUS™ socket. When EN1 is in a high logic state, the SDO line is enabled, and when EN1 is in a low logic state, the SDO line is disabled to the high-Z state. 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
Arduino Mega 2560 is a robust microcontroller platform built around the ATmega 2560 chip. It has extensive capabilities and boasts 54 digital input/output pins, including 15 PWM outputs, 16 analog inputs, and 4 UARTs. With a 16MHz crystal
oscillator ensuring precise timing, it offers seamless connectivity via USB, a convenient power jack, an ICSP header, and a reset button. This all-inclusive board simplifies microcontroller projects; connect it to your computer via USB or power it up
using an AC-to-DC adapter or battery. Notably, the Mega 2560 maintains compatibility with a wide range of shields crafted for the Uno, Duemilanove, or Diecimila boards, ensuring versatility and ease of integration.
Microcontroller Overview
MCU Card / MCU
Architecture
AVR
MCU Memory (KB)
256
Silicon Vendor
Microchip
Pin count
100
RAM (Bytes)
8192
You complete me!
Accessories
Click Shield for Arduino Mega comes equipped with four mikroBUS™ sockets, with two in the form of a Shuttle connector, allowing all the Click board™ devices to be interfaced with the Arduino Mega board with no effort. Featuring an AVR 8-bit microcontroller with advanced RISC architecture, 54 digital I/O pins, and Arduino™ compatibility, the Arduino Mega board offers limitless possibilities for prototyping and creating diverse applications. This board is controlled and powered conveniently through a USB connection to program and debug the Arduino Mega board efficiently out of the box, with an additional USB cable connected to the USB B port on the board. Simplify your project development with the integrated ATmega16U2 programmer and unleash creativity using the extensive I/O options and expansion capabilities. There are eight switches, which you can use as inputs, and eight LEDs, which can be used as outputs of the MEGA2560. In addition, the shield features the MCP1501, a high-precision buffered voltage reference from Microchip. This reference is selected by default over the EXT REF jumper at the bottom of the board. You can choose an external one, as you would usually do with an Arduino Mega board. There is also a GND hook for testing purposes. Four additional LEDs are PWR, LED (standard pin D13), RX, and TX LEDs connected to UART1 (mikroBUS™ 1 socket). This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the Arduino Mega board with Click Shield for Arduino Mega, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for SPI Isolator 4 Click driver.
Key functions:
spiisolator4_generic_write
- SPI Isolator 4 data writing functionspiisolator4_generic_read
- SPI Isolator 4 data reading 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 main.c
* @brief SPIIsolator4 Click example
*
* # Description
* This library contains API for the SPI Isolator 4 click driver.
* This demo application shows an example of an SPI Isolator 4 click wired
* to the nvSRAM 4 click for reading Device ID.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of SPI module and log UART.
* After driver initialization, the app sets the default configuration.
*
* ## Application Task
* This is an example that shows the use of an SPI Isolator 4 click board™.
* Logs Device ID of the nvSRAM 4 click wired to the SPI Isolator 4 board™.
* Results are being sent to the Usart Terminal where you can track their changes.
*
* ## Additional Function
* - static void get_device_id ( void )
*
* @author Mikroe Team
*
*/
#include "board.h"
#include "log.h"
#include "spiisolator4.h"
static spiisolator4_t spiisolator4;
static log_t logger;
static uint32_t device_id;
static void get_device_id ( void ) {
uint8_t rx_data[ 4 ];
spiisolator4_generic_read( &spiisolator4, 0x9F, &rx_data[ 0 ], 4 );
device_id = rx_data[ 0 ];
device_id <<= 8;
device_id |= rx_data[ 1 ];
device_id <<= 8;
device_id |= rx_data[ 2 ];
device_id <<= 8;
device_id |= rx_data[ 3 ];
}
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
spiisolator4_cfg_t spiisolator4_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.
spiisolator4_cfg_setup( &spiisolator4_cfg );
SPIISOLATOR4_MAP_MIKROBUS( spiisolator4_cfg, MIKROBUS_1 );
err_t init_flag = spiisolator4_init( &spiisolator4, &spiisolator4_cfg );
if ( SPI_MASTER_ERROR == init_flag )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
spiisolator4_default_cfg ( &spiisolator4 );
log_info( &logger, " Application Task " );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms( 100 );
}
void application_task ( void )
{
get_device_id( );
log_printf( &logger, " Device ID : 0x%.8LX\r\n", device_id );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END