diff options
Diffstat (limited to 'Projects/P-NUCLEO-WB55.Nucleo/Applications/Zigbee/Zigbee_SE_Msg_Server_Router/readme.txt')
| -rw-r--r-- | Projects/P-NUCLEO-WB55.Nucleo/Applications/Zigbee/Zigbee_SE_Msg_Server_Router/readme.txt | 128 |
1 files changed, 128 insertions, 0 deletions
diff --git a/Projects/P-NUCLEO-WB55.Nucleo/Applications/Zigbee/Zigbee_SE_Msg_Server_Router/readme.txt b/Projects/P-NUCLEO-WB55.Nucleo/Applications/Zigbee/Zigbee_SE_Msg_Server_Router/readme.txt new file mode 100644 index 000000000..f1c32f5df --- /dev/null +++ b/Projects/P-NUCLEO-WB55.Nucleo/Applications/Zigbee/Zigbee_SE_Msg_Server_Router/readme.txt @@ -0,0 +1,128 @@ +/** + @page Zigbee_SE_Msg_Router application + + @verbatim + ****************************************************************************** + * @file Zigbee/Zigbee_SE_Msg_Server_Router/readme.txt + * @author MCD Application Team + * @brief Description of the Zigbee SE Messaging Cluster application using a + * centralized network. This application concerns only the + * router role. + ****************************************************************************** + * + * Copyright (c) 2019 STMicroelectronics. All rights reserved. + * + * This software component is licensed by ST under Ultimate Liberty license + * SLA0044, the "License"; You may not use this file except in compliance with + * the License. You may obtain a copy of the License at: + * www.st.com/SLA0044 + * + ****************************************************************************** + @endverbatim + +@par Application Description + +How to use SE Messaging cluster on a Centralized Zigbee network with device acting as router (Server). + +The purpose of this application is to show how to create a centralized Zigbee network, and how to communicate +from one node to another one using the SE Messaging cluster. Once the Zigbee mesh network is created, the +user can send messages from Router (server) to Coordinator (client) through the push buttons. + +Press SW1 on server => Send "Hello" +Press SW2 on server => Send "Good Bye" + + Device 1 Device 2 + + --------- --------- + | | ZbZclMsgServerDisplayMessageReq | | + PushB_SW1 => |Server | -----------------------------------> |Client | => "Hello" + | | | | + | | ZbZclMsgServerDisplayMessageReq | | + PushB_SW2 => |Server | -----------------------------------> |Client | => "Good Bye" + | | | | + | | | | + -------- --------- + + +This application requires two STM32WB55xx nucleo boards. + +This application requests having the stm32wb5x_zigbee_full_fw.bin binary flashed on the wireless coprocessor +and the correct binary flashed on the application processor. + +Important note : +================ +As it is a centralized network, to run this application, you need to have one device acting +as coordinator and one device acting as router. + +One board must be flashed with the binary generated by this application (Zigbee/Zigbee_SE_Msg_Server_Router) +The other boards must be flashed with the binary generated by the application named Zigbee/Zigbee_SE_Msg_Client_Coord + +To run the application : + + a) Once the boards have been flashed, boot the different devices one by one (first coordinator and then router). + There must be one board configured in coordinator mode , and one board configured in router mode. + + b) Wait for a few seconds (around 5 sec), in order to let the zigbee mesh network being created. + + c) At this stage, a Zigbee network is automatically created and it is possible to send SE Messaging commands + in unicast mode by pressing on the SW1 or SW2 push button of the Server. + Press on SW1 (resp SW2) . You must see the SE Messages sent from Server to Client in Wireshark logs. + + + ---------- ----------- + |Device 1 |............|Device 2 | + |(Router) | |(Coord.) | + ----------- ----------- + + +@par Hardware and Software environment + + - This example runs on STM32WB55xx devices (Nucleo board) + + - This example has been tested with an STMicroelectronics STM32WB55RG_Nucleo + board and can be easily tailored to any other supported device + and development board. + + - On STM32WB55RG_Nucleo, the jumpers must be configured as described + in this section. Starting from the top left position up to the bottom + right position, the jumpers on the Board must be set as follows: + + CN11: GND [OFF] + JP4: VDDRF [ON] + JP6: VC0 [ON] + JP2: +3V3 [ON] + JP1: USB_STL [ON] All others [OFF] + CN12: GND [OFF] + CN7: <All> [OFF] + JP3: VDD_MCU [ON] + JP5: GND [OFF] All others [ON] + CN10: <All> [OFF] + + +@par How to use it ? + +=> Loading of the stm32wb5x_zigbee_full_fw.bin binary + + This application requests having the stm32wb5x_zigbee_full_fw.bin binary flashed on the Wireless Coprocessor. + If it is not the case, you need to use STM32CubeProgrammer to load the appropriate binary. + All available binaries are located under /Projects/STM32_Copro_Wireless_Binaries directory. + Refer to UM2237 to learn how to use/install STM32CubeProgrammer. + Refer to /Projects/STM32_Copro_Wireless_Binaries/ReleaseNote.html for the detailed procedure to change the + Wireless Coprocessor binary. + +=> Getting traces + To get the traces you need to connect your Board to the Hyperterminal (through the STLink Virtual COM Port). + The UART must be configured as follows: + + - BaudRate = 115200 baud + - Word Length = 8 Bits + - Stop Bit = 1 bit + - Parity = none + - Flow control = none + +=> Running the application + + Refer to the Application description at the beginning of this readme.txt + + * <h3><center>© COPYRIGHT STMicroelectronics</center></h3> + |