Shuttle click

Shuttle click is a mikroBUS™ socket expansion board, which provides an easy and elegant solution for stacking up to four click boards™ on a single mikroBUS™. It is a perfect solution for expanding the capacity of the development system with additional mikroBUS™ sockets when there is a demand for using more click boards™ than the used development system is able to support.

click Product page

Click library

• Author : MikroE Team
• Date : Jan 2020.
• Type : GPIO type

Software Support

We provide a library for the Shuttle Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.

Package can be downloaded/installed directly form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.

Library Description

This library contains API for Shuttle Click driver.

Standard key functions :

• Config Object Initialization function.

  void shuttle_cfg_setup ( shuttle_cfg_t *cfg );

• Initialization function.

  SHUTTLE_RETVAL shuttle_init ( shuttle_t ctx, shuttle_cfg_t cfg );

• Click Default Configuration function.

  void shuttle_default_cfg ( shuttle_t *ctx );

Example key functions :

• This function sets the output voltage on the specified pin to high.

  void shuttle_set_pin_high ( digital_out_t *pin );

• This function sets the output voltage on the specified pin to low.

  void shuttle_set_pin_low ( digital_out_t *pin );

Examples Description

This example showcases how to initialize, configure and use the Terminal click. It is a simple GPIO click which uses high-quality PCB design, four ICD BOX headers and flat ribbon cables to enable stable communication and easy stacking of other click modules.

The demo application is composed of two sections :

Application Init

This function initializes and configures the click and logger modules.

void application_init ( )
{
    log_cfg_t log_cfg;
    shuttle_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.

    shuttle_cfg_setup( &cfg );
    SHUTTLE_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    shuttle_init( &shuttle, &cfg );
}

Application Task

This function sets the output on all the pins (one by one) on the left side to high, going from top to bottom and then does the same with the ones on the right side, after which it sets all pins to high and after one second sets them back to low.

void application_task ( )
{
    int i;

    for( i = 0; i < 12; i++ )
    {
        blink( pin_addr[ i ] );
    }

    all_on( );
    Delay_1sec( );
    all_off( );
}  

The full application code, and ready to use projects can be installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.

Other mikroE Libraries used in the example:

• MikroSDK.Board
• MikroSDK.Log
• Click.Shuttle

Additional notes and informations

Depending on the development board you are using, you may need USB UART click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.