We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]
Rating:
Author: MIKROE
Last Updated: 2024-10-31
Package Version: 2.1.0.14
mikroSDK Library: 2.0.0.0
Category: BT/BLE
Downloaded: 150 times
Not followed.
License: MIT license
The BT-EZ Click is a Click board™ which provide BLE connectivity for any embedded application.
Do you want to subscribe in order to receive notifications regarding "BT-EZ Click" changes.
Do you want to unsubscribe in order to stop receiving notifications regarding "BT-EZ Click" changes.
Do you want to report abuse regarding "BT-EZ Click".
DOWNLOAD LINK | RELATED COMPILER | CONTAINS |
---|---|---|
4348_bt_ez_click.zip [475.32KB] | mikroC AI for ARM GCC for ARM Clang for ARM mikroC AI for PIC mikroC AI for PIC32 XC32 GCC for RISC-V Clang for RISC-V mikroC AI for dsPIC XC16 |
|
The BT-EZ Click is a Click board™ which provide BLE connectivity for any embedded application.
We provide a library for the BtEz 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 from compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.
This library contains API for BtEz Click driver.
Config Object Initialization function.
void btez_cfg_setup ( btez_cfg_t *cfg );
Initialization function.
BTEZ_RETVAL btez_init ( btez_t ctx, btez_cfg_t cfg );
Generic write function.
void btez_generic_write ( btez_t ctx, char data_buf, uint16_t len );
Generic read function.
int32_t btez_generic_read ( btez_t ctx, char data_buf, uint16_t max_len );
Send command function.
void btez_send_command ( btez_t ctx, char command );
This example reads and processes data from BT-EZ clicks.
The demo application is composed of two sections :
Initializes the driver and configures the Click board.
void application_init ( void )
{
log_cfg_t log_cfg;
btez_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.
btez_cfg_setup( &cfg );
BTEZ_MAP_MIKROBUS( cfg, MIKROBUS_1 );
btez_init( &btez, &cfg );
Delay_ms ( 100 );
log_printf( &logger, "Configuring the module...\r\n" );
config_mode = 1;
btez_module_reset( &btez );
btez_process( );
btez_send_command( &btez, CMD_PING );
btez_process( );
btez_send_command( &btez, CMD_DEVICE_NAME );
btez_process( );
btez_send_command( &btez, CMD_SAVE );
btez_process( );
btez_send_command( &btez, CMD_GDN );
btez_process( );
config_mode = 0;
log_printf( &logger, "The module has been configured.\r\n" );
Delay_1sec( );
}
Checks for the received data, reads it and replies with a certain message.
void application_task ( void )
{
btez_process( );
}
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.
The full application code, and ready to use projects can be installed directly from compilers IDE(recommended) or found on LibStock page or mikroE GitHub accaunt.
Other mikroE Libraries used in the example:
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.