Unlock the full potential of your projects with our BLE 4.2 module, crafted to enable effortless wireless communication while conserving energy. Enhance your experience, and enable seamless connectivity and efficient data transfer in applications ranging from industrial automation to smart home devices.
A
A
Hardware Overview
How does it work?
RN4871 Click is based on the RN4871, a Bluetooth® 4.2 low-energy module from Microchip. This Click is designed to run on a 3.3V power supply. It uses ASCII Command Interface over UART for communication with the target microcontroller, with additional functionality provided by the following pins on the mikroBUS™ line: RST, CS, and INT. The RN4871 Bluetooth Low
Energy module integrates Bluetooth 4.2 baseband controller, onboard Bluetooth stack, digital and analog I/O, and RF power amplifier into one solution. The module contains an integral ceramic chip antenna. The host microcontroller can dynamically configure all products in the RN series with a few simple ASCII commands. The RN4871 supports both peripheral and central Generic
Access Profile (GAP) roles, actively scanning for other connectable devices instead of waiting for incoming connection requests. The peripherals are usually small, low-power devices that broadcast information to the central device, like sensors and monitors. The central device can communicate with multiple peripherals.
Features overview
Development board
Nucleo-64 with STM32F091RC 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)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
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
Schematic
Step by step
Project assembly
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for RN4870 Click driver.
Key functions:
rn4871_read
- This function gets message from 'void rn4871_receive function if flag was setrn4871_receive
- The function receives character by waits for '#' - character to start parsing message, waits for '*' - character to stop parsing message and sets flag if whole and properly formated message is receivedrn4871_connect
- The function connects to slave device with desired register address by secures the connection and entering data stream mode
Open Source
Code example
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* \file
* \brief Rn4871 Click example
*
* # Description
* This example reads and processes data from RN4871 clicks.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes UART driver. Initializes device and parser.
*
* ## Application Task
* If 'MASTER' - connects to 'SLAVE', sends message and disconnects. If 'SLAVE' - waits for connect request
* and message from 'MASTER' and LOGs received message.
*
* ## Additional Function
* - rn4871_process ( ) - The general process of collecting presponce
* that sends a module.
*
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "rn4871.h"
#include "string.h"
#define PROCESS_COUNTER 10
#define PROCESS_RX_BUFFER_SIZE 500
#define PROCESS_PARSER_BUFFER_SIZE 500
// ------------------------------------------------------------------ VARIABLES
// #define DEMO_APP_RECEIVER
#define DEMO_APP_TRANSMITER
static rn4871_t rn4871;
static log_t logger;
uint8_t RN4871_ADDR_MASTER[ 13 ] = {'D', 'F', '0', '0', '0', '0', '0', '6', '8', '7', '9', '0'};
uint8_t RN4871_ADDR_SLAVE[ 13 ] = {'D', 'F', '1', '1', '1', '1', '1', '6', '8', '7', '9', '0'};
uint8_t message_payload[ 17 ] = {'M', 'i', 'k', 'r', 'o', 'E', 'l', 'e', 'k', 't', 'r', 'o', 'n', 'i', 'k', 'a'};
uint8_t dev_type;
uint8_t receive_buffer[ 255 ];
uint8_t msg_flag = 0;
char *ptr;
// ------------------------------------------------------- ADDITIONAL FUNCTIONS
static void rn4871_process ( void )
{
int32_t rsp_size;
char uart_rx_buffer[ PROCESS_RX_BUFFER_SIZE ] = { 0 };
uint8_t check_buf_cnt;
rsp_size = rn4871_generic_read( &rn4871, &uart_rx_buffer, PROCESS_RX_BUFFER_SIZE );
if ( rsp_size > 0 )
{
// Validation of the received data
for ( check_buf_cnt = 0; check_buf_cnt < rsp_size; check_buf_cnt++ )
{
rn4871_receive( &rn4871, uart_rx_buffer[ check_buf_cnt ] );
}
}
}
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
rn4871_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.
rn4871_cfg_setup( &cfg );
RN4871_MAP_MIKROBUS( cfg, MIKROBUS_1 );
rn4871_init( &rn4871, &cfg );
Delay_ms( 100 );
dev_type = RN4871_DEVICETYPE_MASTER;
#ifdef DEMO_APP_TRANSMITER
log_info( &logger, "RN4871 DEVICE TYPE MASTER" );
rn4871_initialize( &rn4871, &RN4871_ADDR_MASTER[ 0 ] );
#endif
#ifdef DEMO_APP_RECEIVER
log_info( &logger, "RN4871 DEVICE TYPE SLAVE" );
rn4871_initialize( &rn4871, &RN4871_ADDR_SLAVE[ 0 ] );
ptr = &receive_buffer[ 7 ];
#endif
memset( &rn4871.device_buffer, 0, 255 );
log_printf( &logger, " >>> app init done <<< \r\n" );
}
void application_task ( void )
{
rn4871_process( );
#ifdef DEMO_APP_TRANSMITER
rn4871_connect( &rn4871, &RN4871_ADDR_SLAVE[ 0 ] );
Delay_ms( 100 );
log_printf( &logger, ">>> sending data <<<\r\n" );
rn4871_send( &rn4871, RN4871_MTYPE_MSG, RN4871_DTYPE_STRING, RN4871_ID_MASTER, &message_payload[ 0 ] );
Delay_ms( 100 );
rn4871_disconnect( &rn4871 );
Delay_ms( 100 );
#endif
#ifdef DEMO_APP_RECEIVER
msg_flag = rn4871_read( &rn4871, &receive_buffer[ 0 ] );
if ( msg_flag == 1 )
{
log_printf( &logger, ">>> data received <<<\r\n" );
log_printf( &logger, ">>> data : " );
log_printf( &logger, "%s\r\n", ptr );
}
#endif
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END