Skip to content

Files

Latest commit

46bc571 · Mar 27, 2025

History

History

shuttle


Shuttle Click

Shuttle 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 : Jan 2020.
  • Type : GPIO type

Software Support

Example 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.

Example Libraries

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

Example Key Functions

  • shuttle_cfg_setup Config Object Initialization function.
void shuttle_cfg_setup ( shuttle_cfg_t *cfg );
  • shuttle_init Initialization function.
err_t shuttle_init ( shuttle_t *ctx, shuttle_cfg_t *cfg );
  • shuttle_default_cfg Click Default Configuration function.
void shuttle_default_cfg ( shuttle_t *ctx );
  • shuttle_set_pin_high This function sets the output voltage on the specified pin to high.
void shuttle_set_pin_high ( digital_out_t *pin );
  • shuttle_set_pin_low This function sets the output voltage on the specified pin to low.
void shuttle_set_pin_low ( digital_out_t *pin );

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

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.