Skip to content

Latest commit

 

History

History
151 lines (118 loc) · 4.99 KB

README.md

File metadata and controls

151 lines (118 loc) · 4.99 KB

SPI Isolator 8 Click

SPI Isolator 8 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 : Nenad Filipovic
  • Date : Aug 2023.
  • Type : SPI type

Software Support

Example Description

This example demonstrates the use of SPI Isolator 8 Click board™ by reading the manufacturer ID and device ID of the connected Flash 11 Click board™.

Example Libraries

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.SPIIsolator8

Example Key Functions

  • spiisolator8_cfg_setup Config Object Initialization function.
void spiisolator8_cfg_setup ( spiisolator8_cfg_t *cfg );
  • spiisolator8_init Initialization function.
err_t spiisolator8_init ( spiisolator8_t *ctx, spiisolator8_cfg_t *cfg );
  • spiisolator8_default_cfg Click Default Configuration function.
void spiisolator8_default_cfg ( spiisolator8_t *ctx );
  • spiisolator8_transfer SPI Isolator 8 data transfer function.
err_t spiisolator8_transfer ( spiisolator8_t *ctx, uint8_t *data_in, uint8_t *data_out, uint8_t len );
  • spiisolator8_enc_enable SPI Isolator 8 enable side 1 function.
void spiisolator8_enc_enable ( spiisolator8_t *ctx );
  • spiisolator8_enp_enable SPI Isolator 8 enable side 2 function.
void spiisolator8_enp_enable ( spiisolator8_t *ctx );

Application Init

The initialization of SPI module, log UART, and additional pins. After the driver init, the application enabled both isolated sides of the device.

void application_init ( void )
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    spiisolator8_cfg_t spiisolator8_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.
    spiisolator8_cfg_setup( &spiisolator8_cfg );
    SPIISOLATOR8_MAP_MIKROBUS( spiisolator8_cfg, MIKROBUS_1 );
    if ( SPI_MASTER_ERROR == spiisolator8_init( &spiisolator8, &spiisolator8_cfg ) )
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    spiisolator8_default_cfg ( &spiisolator8 );
    Delay_ms ( 100 );
    
    log_info( &logger, " Application Task " );
    log_printf( &logger, " -----------------------\r\n" );
    Delay_ms ( 100 );
}

Application Task

The demo application reads and checks the manufacturer ID and device ID of the connected Flash 11 Click board™. Results are being sent to the UART Terminal, where you can track their changes.

void application_task ( void )
{
    static uint8_t cmd_get_id[ 6 ] = { FLASH11_CMD_GET_ID };
    static uint8_t read_id[ 6 ] = { 0 };
    if ( SPIISOLATOR8_OK == spiisolator8_transfer( &spiisolator8, &cmd_get_id[ 0 ], &read_id[ 0 ], 6 ) )
    {
        if ( ( FLASH11_MANUFACTURER_ID == read_id[ 4 ] ) && ( FLASH11_DEVICE_ID == read_id[ 5 ] ) )
        {
            log_printf( &logger, " Manufacturer ID: 0x%.2X\r\n", ( uint16_t ) read_id[ 4 ] );
            log_printf( &logger, " Device ID: 0x%.2X    \r\n", ( uint16_t ) read_id[ 5 ] );
            log_printf( &logger, " -----------------------\r\n" );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
            Delay_ms ( 1000 );
        }
    }
}

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.