btaudio2

---

BT Audio 2 Click

BT Audio 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 : Feb 2024.
• Type : UART type

Software Support

Example Description

This example demonstrates the use of BT Audio 2 Click board by reading the commands received from remote device and performing adequate actions accordingly.

Example Libraries

• MikroSDK.Board
• MikroSDK.Log
• Click.BTAudio2

Example Key Functions

• btaudio2_cfg_setup Config Object Initialization function.

void btaudio2_cfg_setup ( btaudio2_cfg_t *cfg );

• btaudio2_init Initialization function.

err_t btaudio2_init ( btaudio2_t *ctx, btaudio2_cfg_t *cfg );

• btaudio2_default_cfg Click Default Configuration function.

err_t btaudio2_default_cfg ( btaudio2_t *ctx );

• btaudio2_set_device_name This function sets the local device name.

err_t btaudio2_set_device_name ( btaudio2_t *ctx, uint8_t *device_name );

• btaudio2_make_call This function makes a call to the specified phone number.

err_t btaudio2_make_call ( btaudio2_t *ctx, uint8_t database_index, uint8_t *phone_number );

• btaudio2_volume_up This function increases the volume of a specified gain mask.

err_t btaudio2_volume_up ( btaudio2_t *ctx, uint8_t database_index, uint8_t mask );

Application Init

Initializes the driver and configures the Click board.

void application_init ( void )
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    btaudio2_cfg_t btaudio2_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.
    btaudio2_cfg_setup( &btaudio2_cfg );
    BTAUDIO2_MAP_MIKROBUS( btaudio2_cfg, MIKROBUS_1 );
    if ( UART_ERROR == btaudio2_init( &btaudio2, &btaudio2_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    if ( BTAUDIO2_OK != btaudio2_default_cfg ( &btaudio2 ) )
    {
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    }
    
    if ( BTAUDIO2_OK != btaudio2_set_device_name ( &btaudio2, DEVICE_NAME ) )
    {
        log_error( &logger, " Set device name." );
        for ( ; ; );
    }
    
    log_info( &logger, " Application Task " );
}

Application Task

Reads all the received events and parses them.

void application_task ( void )
{
    if ( BTAUDIO2_OK == btaudio2_read_event ( &btaudio2 ) ) 
    {
        btaudio2_event_handler ( &btaudio2 );
    }
}

Note

We have used the Serial Bluetooth Terminal smartphone application for the test. A smartphone and the Click board must be paired in order to exchange messages with each other. So make sure to pair your device with the Click board and connect it to using the Serial Bluetooth Terminal application, then you will be able to send commands listed below.

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.

---