Discover the potential of our ZigBee Radio module, meticulously designed to conserve power while delivering robust wireless connectivity, ideal for IoT applications demanding efficiency and reliability.
A
A
Hardware Overview
How does it work?
ZigBee Click is based on the ETRX357, a low power Zigbee Radio module integrating a 2.4 GHz compliant transceiver with many advanced peripherals from Silicon Labs. The ZigBee protocol is a set of standards for wireless connectivity for usage between any devices over short to medium distances. It uses the IEEE 802.15.4 radio specification running on the 2.4GHz band, plus three additional layers for networking, security, and applications. What makes this module unique is its use of a mesh network architecture which, in bucket chain style, passes data from one node to the next until it lands at its destination. The ETRX357 module is pre-loaded with a standalone bootloader that supports over-the-air bootloading as well as serial bootloading of the new firmware, using the FW pin on the ZigBee Click. The module is controlled using the default firmware consisting of simple AT commands. Parameters that define the functionality of the module and also allow standalone functionality are saved in non-volatile memory organized in so-called S-Registers.
The commands and responses pass through the serial port of the ETRX357 as ASCII text, so a simple terminal application will usually suffice. The industry-standard serial wire, JTAG programming, and debugging interfaces together with the standard ARM system debug components help to streamline any custom software development. In addition to this, several MAC functions are also implemented in hardware to help to maintain the strict timing requirements imposed by the ZigBee and IEEE802.15.4 standards. The module is also able to act as a coordinator and Trust Centre through external host control. The AT-style command line supplies all the tools required to set up and manage a Zigbee network by allowing easy access to the low-level functionality of the stack. ZigBee Click communicates with MCU using the UART interface as its default communication protocol, but it is also left the option for the user to use other interfaces such as SPI and I2C if he wants to configure the module and write the library by himself. The selection
between UART and I2C can be done by positioning SMD jumpers labeled as COMM SEL to an appropriate position. Note that all the jumpers must be placed to the same side, or else the Click board™ may become unresponsive. Additional functionality such as reset and interrupt are provided and routed at RST and INT pins of the mikroBUSTM, as well as serial UART connections CTS and RTS, routed on the CS and PWM mikroBUSTM pins. To simplify deployment, the Click boardTM features the CMT-8540S-SMT magnetic buzzer controlled by the ZigBee module used for audible signalization and notification. You can create different sound patterns using the Sound library supported in our compilers. Signal frequency determines the sound pitch, and the duty cycle determines the amplitude (sound volume). This Click board™ is designed to be operated only with a 3.3V logic level. A proper logic voltage level conversion should be performed before the Click board™ is used with MCUs with different logic levels.
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 ZigBee Click driver.
Key functions:
zigbee_send_at
- Function merges two string and sends it to device.zigbee_resp
- Function checking driver buffer string.zigbee_set_pin_rst
- Function setting RST pin status.
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 main.c
* @brief ZigBee Click Example.
*
* # Description
* This is an example that demonstrates the use of the ZigBee Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of driver, UART ISR and then configures device.
* Depending on previous selected device mode it creates new PAN network or joins to one.
*
* ## Application Task
* Host mode: Broadcasts message 'MikroE' every 3 seconds.
* User mode: Checks if something is received.
*
* ## Additional Function
* - void zigbee_clear_app_buf ( void ) - Clearing application buffer function.
* - void resp_wait ( zigbee_t *ctx ) - Function for waiting for complete response.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "zigbee.h"
static zigbee_t zigbee;
static log_t logger;
uint8_t dev_mode;
uint8_t app_mode;
static char app_buf[ ZIGBEE_DEV_BUFFER_MAX ] = { 0 };
char AT_BCAST_MSG[ 15 ] = ":00,MikroE";
char AT_HOST_CFG1[ 10 ] = "00=6314";
char AT_HOST_CFG2[ 20 ] = "0A=0914;password";
char AT_HOST_CFG3[ 50 ] = "09=5A6967426565416C6C69616E63653039;password";
/**
* @brief ZigBee clearing application buffer.
* @details This function clears memory of application buffer and reset it's length and counter.
*/
void zigbee_clear_app_buf ( void );
/**
* @brief ZigBee wait response.
* @details This function is used for waiting for complete response.
*/
void resp_wait ( zigbee_t *ctx );
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
zigbee_cfg_t zigbee_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 " );
app_mode = ZIGBEE_APP_INIT;
dev_mode = ZIGBEE_DEV_USER;
// Click initialization.
zigbee_cfg_setup( &zigbee_cfg );
ZIGBEE_MAP_MIKROBUS( zigbee_cfg, MIKROBUS_1 );
if ( UART_ERROR == zigbee_init( &zigbee, &zigbee_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_printf( &logger, "------------------------------\r\n", app_buf );
log_printf( &logger, " Restarting Device \r\n" );
zigbee_restart( &zigbee );
log_printf( &logger, "------------------------------\r\n", app_buf );
log_printf( &logger, " Sending command : AT \r\n", app_buf );
zigbee_send_cmd( &zigbee, ZIGBEE_CMD_AT );
resp_wait( &zigbee );
log_printf( &logger, "------------------------------\r\n", app_buf );
log_printf( &logger, " Sending command : AT + DASSL \r\n", app_buf );
zigbee_send_cmd( &zigbee, ZIGBEE_CMD_AT_DASSL );
resp_wait( &zigbee );
log_printf( &logger, "------------------------------\r\n", app_buf );
log_printf( &logger, " Sending command : ATZ \r\n", app_buf );
zigbee_send_cmd( &zigbee, ZIGBEE_CMD_ATZ );
resp_wait( &zigbee );
log_printf( &logger, "------------------------------\r\n", app_buf );
log_printf( &logger, " Sending command : ATI \r\n", app_buf );
zigbee_send_cmd( &zigbee, ZIGBEE_CMD_ATI );
resp_wait( &zigbee );
log_printf( &logger, "------------------------------\r\n", app_buf );
log_printf( &logger, " Sending command : AT + N \r\n", app_buf );
zigbee_send_cmd( &zigbee, ZIGBEE_CMD_AT_N );
resp_wait( &zigbee );
if ( ZIGBEE_DEV_HOST == dev_mode )
{
// Setting the device into host mode and creating a network for other devices to connect.
log_printf( &logger, "-----------------------------------\r\n", app_buf );
log_printf( &logger, " Sending command : AT + HOST CFG 1 \r\n", app_buf );
zigbee_send_at( &zigbee, ZIGBEE_CMD_ATS, &AT_HOST_CFG1[ 0 ] );
resp_wait( &zigbee );
log_printf( &logger, "-----------------------------------\r\n", app_buf );
log_printf( &logger, " Sending command : AT + HOST CFG 2 \r\n", app_buf );
zigbee_send_at( &zigbee, ZIGBEE_CMD_ATS, &AT_HOST_CFG2[ 0 ] );
resp_wait( &zigbee );
log_printf( &logger, "-----------------------------------\r\n", app_buf );
log_printf( &logger, " Sending command : AT + HOST CFG 3 \r\n", app_buf );
zigbee_send_at( &zigbee, ZIGBEE_CMD_ATS, &AT_HOST_CFG3[ 0 ] );
resp_wait( &zigbee );
log_printf( &logger, "-----------------------------------\r\n", app_buf );
log_printf( &logger, " Sending command : AT + EN \r\n", app_buf );
zigbee_send_cmd( &zigbee, ZIGBEE_CMD_AT_EN );
resp_wait( &zigbee );
}
else if ( ZIGBEE_DEV_USER == dev_mode )
{
// Setting the device into user mode and joining the existing network.
log_printf( &logger, "-----------------------------------\r\n", app_buf );
log_printf( &logger, " Sending command : AT + JN \r\n", app_buf );
zigbee_send_cmd( &zigbee, ZIGBEE_CMD_AT_JN );
resp_wait( &zigbee );
}
log_printf( &logger, "-----------------------------------\r\n", app_buf );
log_printf( &logger, " Sending command : AT + IDREQ \r\n", app_buf );
zigbee_send_cmd( &zigbee, ZIGBEE_CMD_AT_IDREQ );
resp_wait( &zigbee );
log_printf( &logger, "-----------------------------------\r\n", app_buf );
log_printf( &logger, " Sending command : AT + N \r\n", app_buf );
zigbee_send_cmd( &zigbee, ZIGBEE_CMD_AT_N );
resp_wait( &zigbee );
Delay_ms( 1000 );
app_mode = ZIGBEE_APP_TASK;
log_info( &logger, " Application Task " );
log_printf( &logger, "-----------------------------------\r\n", app_buf );
}
void application_task ( void )
{
if ( ZIGBEE_DEV_HOST == dev_mode )
{
log_printf( &logger, "-----------------------------------\r\n", app_buf );
zigbee_send_at( &zigbee, ZIGBEE_CMD_AT_BCAST, &AT_BCAST_MSG[ 0 ] );
resp_wait( &zigbee );
Delay_ms( 3000 );
}
else if ( ZIGBEE_DEV_USER == dev_mode )
{
resp_wait( &zigbee );
log_printf( &logger, "-----------------------------------\r\n", app_buf );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
void zigbee_clear_app_buf ( void )
{
memset( app_buf, 0, ZIGBEE_DEV_BUFFER_MAX );
}
void resp_wait ( zigbee_t *ctx )
{
uint8_t resp_flag;
for ( ; ; )
{
zigbee_generic_read( &zigbee, app_buf, ZIGBEE_DEV_BUFFER_MAX );
Delay_ms( 50 );
resp_flag = zigbee_resp( ctx, app_buf );
if ( ( ZIGBEE_APP_TASK == app_mode ) && ( ZIGBEE_DEV_USER == dev_mode ) )
{
if ( ( ZIGBEE_OP_WAIT != resp_flag ) )
{
log_printf( &logger, " %s ", app_buf );
zigbee_clear_app_buf( );
}
}
else
{
if ( ( ZIGBEE_OP_OK == resp_flag ) || ( ZIGBEE_OP_ERROR == resp_flag ) )
{
log_printf( &logger, "%s", app_buf );
log_printf( &logger, "\r\n" );
zigbee_clear_app_buf( );
break;
}
}
}
}
// ------------------------------------------------------------------------ END