From seamless audio streaming to effortless data transfer, our versatile Bluetooth solution is your gateway to a connected world designed to enhance your daily life
A
A
Hardware Overview
How does it work?
BLE 10 Click is based on the PAN1780-AT, a low-power Bluetooth® module that provides BLE connectivity for any embedded application from Panasonic. The PAN1780-AT is based on the Nordic nRF52840 single-chip controller with integrated BlueRadios nBlue™ Bluetooth AT.s LE Command Set. With its ARM® Cortex®-M4F, a 1MB Flash, and 256kb RAM, the PAN1780-AT offers high design flexibility alongside its new channel selection algorithm, which improves its performance in high interference environments. The Bluetooth® 5 features a higher symbol rate of 2Mbps using the high-speed LE 2M PHY or a significantly longer range using the LE Coded PHY. The output power of up to 8dBm and the high sensitivity of the nRF52840 combined with the LE Coded PHY make this module very attractive in long-range applications. The PAN1780-AT communicates with MCU using the UART interface with commonly used UART RX, TX, and hardware flow control pins UART CTS and RTS (Clear to Send and Ready to Send) as its default communication protocol for exchanging AT commands. It operates at
115200bps by default configuration to transmit and exchange data with the host MCU. The PAN1780-AT uses a proprietary GATT profile developed by BlueRadios to stream data; it is not an official Bluetooth® profile. BlueRadios serial port implementation simplifies the user experience, allowing users to stream data similar to how the official Bluetooth® Serial Port Profile (SPP) works on BR/EDR devices. This Click board™ is also equipped with a USB type C connector, which allows the module to be powered and configured by a personal computer (PC). In addition to these features, it also uses several other mikroBUS™ pins. A Reset button routed to the RST pin on the mikroBUS™ socket puts the module into a Reset state, while AN and IO3 pins routed to the AN and PWM pins on the mikroBUS™ socket represent analog signal monitor and GPIO signal, which can be used as Sleep Mode toggle function. In addition, it has four orange LED indicators to indicate various functions such as Sleep mode activation, advertising, received data/commands, and successful module connections.
Two unpopulated headers can also be found on this Click board™, one of which is provided for the optional connection of an external NFC antenna (Type 2 Near Field Communication (NFC-A) for use in simplified pairing and payment solutions), while the second header represents three additional GPIO pins that carry a handful of additional functions whose description can be found in the attached datasheet. This Click board™ can be operated only with a 3.3V logic voltage level. Considering that the board can also be powered via USB, using the additional LDO, the TLV1117 achieves the required voltage of 3.3V to power the module. An LDO and 3V3 mikroBUS™ power rail have protection in the form of diode MAX40200 to prevent any unwanted back voltage. The board must also perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ comes equipped with a library containing functions and an example code that can be used, as a reference, for further development.
Features overview
Development board
Nucleo-64 with STM32L073RZ MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU

Architecture
ARM Cortex-M0
MCU Memory (KB)
192
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
20480
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic

Step by step
Project assembly
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.

2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.

3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.

Software Support
Library Description
This library contains API for BLE 10 Click driver.
Key functions:
ble10_set_device_name
- This function sets the local device nameble10_factory_reset
- This function factory resets the deviceble10_get_temperature
- This function executes get temperature command which returns the current temperature of the module's internal temperature sensor
Open Source
Code example
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.
/*!
* @file main.c
* @brief BLE 10 Click Example.
*
* # Description
* This example reads and processes data from BLE 10 clicks.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver, then performs a factory reset and sets the local device name.
*
* ## Application Task
* Logs all the received events/responses on the USB UART.
* Then checks if there's a specific command string (defined by the GET_TEMP_COMMAND macro)
* received from the GATT Server, and if so, it executes temperature reading command and logs the results.
*
* ## Additional Function
* - static void ble10_clear_app_buf ( void )
* - static err_t ble10_process ( void )
* - static err_t bluetooth2_display_rsp ( char *rsp_end )
*
* @note
* We have used the nRF Connect smartphone application for the test.
* Make sure to configure the GATT Server properly in the nRF Connect application, then you
* will be able to send a desired command from it, once you connect to the click board.
* You can use the Sample configuration for GATT Server which comes with the application installation
* and then send a command via Test Service from the Server.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "ble10.h"
#include "conversions.h"
#include "generic_pointer.h"
#define PROCESS_BUFFER_SIZE 200
// Response and Events macros.
#define RSP_TIMEOUT 20000
#define RSP_OK "OK"
#define RSP_ERROR "ERROR"
#define EVT_DONE "DONE"
#define EVT_RESET "RESET"
#define EVT_GATT_VAL "GATT_VAL"
// Local device name.
#define DEVICE_NAME "BLE 10 Click"
// The command string that will execute temperature reading, which is expected to be received
// from the GATT Server of the connected device.
#define GET_TEMP_COMMAND "get temp"
static ble10_t ble10;
static log_t logger;
static char app_buf[ PROCESS_BUFFER_SIZE ] = { 0 };
static int32_t app_buf_len = 0;
static int32_t app_buf_cnt = 0;
static uint8_t connection_flag = 0;
static uint16_t send_cnt = 0;
/**
* @brief BLE 10 clearing application buffer.
* @details This function clears memory of application buffer and reset it's length and counter.
* @note None.
*/
static void ble10_clear_app_buf ( void );
/**
* @brief BLE 10 data reading function.
* @details This function reads data from device and concatenates data to application buffer.
*
* @return @li @c 0 - Read some data.
* @li @c -1 - Nothing is read.
* @li @c -2 - Application buffer overflow.
*
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t ble10_process ( void );
/**
* @brief BLE 10 display response function.
* @details This function reads data from device until sends @a rsp_end or ERROR message or until
* it exceeds the timeout value.
* @param[in] rsp_end : Response/Event ending string [OK, DONE, RESET, GATT_VAL].
*
* @return @li @c 0 - Read some data.
* @li @c -1 - Nothing is read.
*
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t ble10_display_rsp ( char *rsp_end );
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
ble10_cfg_t ble10_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.
ble10_cfg_setup( &ble10_cfg );
BLE10_MAP_MIKROBUS( ble10_cfg, MIKROBUS_1 );
err_t init_flag = ble10_init( &ble10, &ble10_cfg );
if ( UART_ERROR == init_flag )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
ble10_default_cfg ( &ble10 );
ble10_process( );
ble10_clear_app_buf( );
app_buf_len = 0;
app_buf_cnt = 0;
log_printf( &logger, " - Factory Reset -\r\n" );
ble10_factory_reset ( &ble10 );
ble10_display_rsp ( EVT_RESET );
log_printf( &logger, " - Set Device Name -\r\n" );
ble10_set_device_name ( &ble10, DEVICE_NAME );
ble10_display_rsp ( RSP_OK );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
ble10_process( );
if ( app_buf_len > 0 )
{
Delay_ms( 100 );
ble10_process( );
for ( int32_t buf_cnt = 0; buf_cnt < app_buf_len; buf_cnt++ )
{
log_printf( &logger, "%c", app_buf[ buf_cnt ] );
}
if ( strstr( app_buf, EVT_GATT_VAL ) )
{
char get_temp_cmd[ ] = GET_TEMP_COMMAND;
const char * __generic_ptr msg_ptr = strrchr ( app_buf, ',' ) + 1;
uint8_t msg_len = *( msg_ptr - 2 ) - 48;
if ( msg_len == strlen ( get_temp_cmd ) )
{
char get_temp_hex[ 64 ] = { 0 };
uint8_t get_temp_hex_chr[ 3 ] = { 0 };
uint8_t cnt = 0;
for ( cnt = 0; cnt < strlen ( get_temp_cmd ); cnt++ )
{
uint8_to_hex ( get_temp_cmd[ cnt ], get_temp_hex_chr );
strcat ( get_temp_hex, get_temp_hex_chr );
}
if ( 0 == memcmp ( get_temp_hex, msg_ptr, strlen ( get_temp_hex ) ) )
{
ble10_clear_app_buf( );
log_printf( &logger, " - Get Temperature -\r\n" );
ble10_get_temperature ( &ble10 );
ble10_display_rsp ( RSP_OK );
}
}
}
ble10_clear_app_buf( );
}
Delay_ms( 1 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
static void ble10_clear_app_buf ( void )
{
memset( app_buf, 0, app_buf_len );
app_buf_len = 0;
app_buf_cnt = 0;
}
static err_t ble10_process ( void )
{
int32_t rx_size;
char rx_buff[ PROCESS_BUFFER_SIZE ] = { 0 };
rx_size = ble10_generic_read( &ble10, rx_buff, PROCESS_BUFFER_SIZE );
if ( rx_size > 0 )
{
int32_t buf_cnt = 0;
if ( app_buf_len + rx_size >= PROCESS_BUFFER_SIZE )
{
ble10_clear_app_buf( );
return BLE10_ERROR;
}
else
{
buf_cnt = app_buf_len;
app_buf_len += rx_size;
}
for ( int32_t rx_cnt = 0; rx_cnt < rx_size; rx_cnt++ )
{
if ( rx_buff[ rx_cnt ] != 0 )
{
app_buf[ ( buf_cnt + rx_cnt ) ] = rx_buff[ rx_cnt ];
}
else
{
app_buf_len--;
buf_cnt--;
}
}
return BLE10_OK;
}
return BLE10_ERROR;
}
static err_t ble10_display_rsp ( char *rsp_end )
{
uint32_t timeout = RSP_TIMEOUT;
while ( timeout-- )
{
ble10_process( );
if ( app_buf_len > 0 )
{
for ( int32_t buf_cnt = 0; buf_cnt < app_buf_len; buf_cnt++ )
{
log_printf( &logger, "%c", app_buf[ buf_cnt ] );
}
if ( strstr( app_buf, rsp_end ) )
{
ble10_clear_app_buf( );
Delay_ms( 100 );
ble10_process( );
for ( int32_t buf_cnt = 0; buf_cnt < app_buf_len; buf_cnt++ )
{
log_printf( &logger, "%c", app_buf[ buf_cnt ] );
}
ble10_clear_app_buf( );
log_printf( &logger, "--------------------------------\r\n" );
return BLE10_OK;
}
ble10_clear_app_buf( );
}
Delay_ms ( 1 );
}
return BLE10_ERROR;
}
// ------------------------------------------------------------------------ END