tester2

---

Tester 2 Click

Tester 2 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 : Stefan Filipovic
• Date : Sep 2024.
• Type : GPIO type

Software Support

Example Description

This example demonstrates the use of Tester 2 Click board by controlling all LEDs on the Click board together and in sequential pin toggling with different delays.

Example Libraries

• MikroSDK.Board
• MikroSDK.Log
• Click.Tester2

Example Key Functions

• tester2_cfg_setup Config Object Initialization function.

void tester2_cfg_setup ( tester2_cfg_t *cfg );

• tester2_init Initialization function.

err_t tester2_init ( tester2_t *ctx, tester2_cfg_t *cfg );

• tester2_toggle_all This function toggles all mikroBUS pins together a desired number of times with the selected delay between each toggle.

void tester2_toggle_all ( tester2_t *ctx, uint16_t num_toggles, uint16_t toggle_delay_ms );

• tester2_toggle_seq This function toggles all mikroBUS pins one by one with the selected delay between each toggle.

void tester2_toggle_seq ( tester2_t *ctx, uint16_t toggle_delay_ms );

Application Init

Initializes the driver and logger.

void application_init ( void )
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    tester2_cfg_t tester2_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.
    tester2_cfg_setup( &tester2_cfg );
    TESTER2_MAP_MIKROBUS( tester2_cfg, MIKROBUS_1 );
    if ( DIGITAL_OUT_UNSUPPORTED_PIN == tester2_init( &tester2, &tester2_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    log_info( &logger, " Application Task " );
}

Application Task

Toggles all pins together 5 times with a 500ms delay between each toggle, then toggles each pin sequentially with a 300ms delay between toggling each pin.

void application_task ( void )
{
    log_printf( &logger, " Toggling all pins together 5 times with 500ms delay\r\n\n" );
    tester2_toggle_all ( &tester2, 5, 500 );

    log_printf( &logger, " Toggling all pins sequentially with 300ms delay\r\n\n" );
    tester2_toggle_seq ( &tester2, 300 );
}

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.

---