spiisolator4

---

SPI Isolator 4 Click

SPI Isolator 4 Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.

---

Click Library

• Author : Mikroe Team
• Date : Sep 2021.
• Type : SPI type

Software Support

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.

Example Libraries

• MikroSDK.Board
• MikroSDK.Log
• Click.SPIIsolator4

Example Key Functions

• spiisolator4_cfg_setup Config Object Initialization function.

void spiisolator4_cfg_setup ( spiisolator4_cfg_t *cfg );

• spiisolator4_init Initialization function.

err_t spiisolator4_init ( spiisolator4_t *ctx, spiisolator4_cfg_t *cfg );

• spiisolator4_default_cfg Click Default Configuration function.

err_t spiisolator4_default_cfg ( spiisolator4_t *ctx );

• spiisolator4_generic_write SPI Isolator 4 data writing function.

err_t spiisolator4_generic_write ( spiisolator4_t *ctx, uint8_t reg, uint8_t *data_in, uint8_t len );

• spiisolator4_generic_read SPI Isolator 4 data reading function.

err_t spiisolator4_generic_read ( spiisolator4_t *ctx, uint8_t reg, uint8_t *data_out, uint8_t len );

• spiisolator4_set_enable SPI Isolator 4 enable isolator function.

err_t spiisolator4_set_enable ( spiisolator4_t *ctx, spiisolator4_enable_mode_t en_mode );

Application Init

Initialization of SPI module and log UART. After driver initialization, the app sets the default configuration.

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 );
}

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.

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 );
}

Additional Function

• get_device_id SPI Isolator 4 get device ID function.

static void get_device_id ( void );

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.

Additional Notes and Information

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.

---