diff options
Diffstat (limited to 'Projects/P-NUCLEO-WB55.Nucleo/Applications/BLE_Zigbee/BLE_Zigbee_Dyn_NVM/readme.txt')
| -rw-r--r-- | Projects/P-NUCLEO-WB55.Nucleo/Applications/BLE_Zigbee/BLE_Zigbee_Dyn_NVM/readme.txt | 160 |
1 files changed, 0 insertions, 160 deletions
diff --git a/Projects/P-NUCLEO-WB55.Nucleo/Applications/BLE_Zigbee/BLE_Zigbee_Dyn_NVM/readme.txt b/Projects/P-NUCLEO-WB55.Nucleo/Applications/BLE_Zigbee/BLE_Zigbee_Dyn_NVM/readme.txt deleted file mode 100644 index c0d5dae38..000000000 --- a/Projects/P-NUCLEO-WB55.Nucleo/Applications/BLE_Zigbee/BLE_Zigbee_Dyn_NVM/readme.txt +++ /dev/null @@ -1,160 +0,0 @@ -/** - @page BLE_Zigbee_Dyn_NVM example - - @verbatim - ****************************************************************************** - * @file BLE_Zigbee/BLE_Zigbee_Dyn_NVM/readme.txt - * @author MCD Application Team - * @brief Example of application using BLE and Zigbee protocols in dynamic - * concurrent mode with Zigbee persistent data feature. - ****************************************************************************** - * - * Copyright (c) 2020 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 BLE application and Zigbee application in dynamic concurent mode with Zigbee persistent data feature. - -The idea is to present a demo with a Zigbee Network (at least 2 Nucleo Boards, Zb coordinator -running Zigbee_OnOff_Server_Coord application[1] and router running Ble_Zigbee_Dynamic application[2]), -and a BLE connection between 1 Nucleo board running Ble_Zigbee_Dynamic application [2] with either a -smartphone running "ST BLE Sensor" Application (available on App Store and Google Play), or another -Nucleo board running a BLE_p2pClient application[3]. -The STM32WB55xx-Nucleo board running Ble_Zigbee_Dynamic application is capable of switching -dynamically and transparently from BLE network to Zigbee network and vice-versa. - -The demo architecture is summarized in the following figure: - - ______________ ______________ ______________ - / \ / \ / \ - | | | | | | - | | BLE Toggle | Dynamic mode | ZB Toggle | | - | BLE App |<===========>| BLE/ZB App |<===========>| ZB App | - | | | | | (Coord) | - | | | | | | - \______________/ \______________/ \______________/ - [3] [2] [1] - -With the Zigbee NVM feature, the dynamic mode board[2] tries to start from persistence. -This leads to two choices: - - Persistent Data read from NVM are valid -> the router takes back is role in the network. - - No Persistent data found or wrong data,a fresh start is performed, the Zigbee network is automatically created - and BLUE LED (LED1) is ON on all devices. - -Zigbee Persistence Data are updated in NVM. - -If the user power cycle the board[2], Persistent Data are read back and the stack configuration is restored. -The device start from persistence and GREEN LED LED2 is on. - -Push Button SW2 is used to delete Zigbee NVM (fresh start will be done on next start up). - - -@par Keywords - -Zigbee, BLE - -@par Directory contents - - - -@par Hardware and Software environment - - - This example runs on STM32WB55xx devices. - - - 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 ? - -This application requests having the STM32WB5x_BLE_Zigbee_FFD_dynamic_fw.bin binary flashed on the M0 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. - - -Minimum requirements for the demo: -- 1 STM32WB55xx-Nucleo board in BLE Zigbee Dynamic Concurrent mode [2] -- 1 STM32WB55xx-Nucleo board or more for creating Zigbee Network [1] - (see example Zigbee_OnOff_Server_Coord and Zigbee_OnOff_Client_Router for more details on how to use it) -- 1 STM32WB55xx-Nucleo board running a BLE_p2pClient application[3] --- OR -- 1 Smartphone (Android/IOS) with "ST BLE Sensor" Phone Application (available on App Store and Google Play) - Install the "ST BLE Sensor" application on the ios/android device - https://play.google.com/store/apps/details?id=com.st.bluems - https://itunes.apple.com/us/App/st-bluems/id993670214?mt=8 - -In order to make the program work, you must do the following: - - Connect 1 STM32WB55xx-Nucleo boards to your PC - - Open your preferred toolchain - - Rebuild all files and load your image into target memory - - Run the example - -To get the traces in real time, you can connect an HyperTerminal to the STLink Virtual Com Port. - -**** START DEMO **** -By default, after a reset, the ZB/BLE board [2] will start with both BLE and Zigbee modes activated. - -The BLE example implements Point-to-Point communication using BLE component. -1- The ZB/BLE device (P2P Server) starts BLE advertising and simultaneously starts to join the Zigbee Network. -2- The node will then attach the existing Zigbee network (Zb coordinator running Zigbee_OnOff_Server_Coord application [1]). -The blue led turns ON when the Zigbee join is successful. -3- The BLE connection will be started as follows, depending if your BLE device is a smartphone or a 3rd Nucleo board: -3.1 If using a smartphone, then the ST BLE Sensor App (smart Phone Application) scans and can connect to the P2P Server -by selecting = "P2PZBSRV1" entry. --- Once connected, the application starts to search the P2P Services & Characteristics. --- Led Button service, Led Characteristic and Button Characteristic are discovered at this stage (this service is ST specific). --- Pressing the LED button on the App will turn On or Off the Red Led on the ZB/BLE device [2] -3.2 If using a 3rd Nucleo board (running a BLE_p2pClient application [3]), you can start scanning by pressing the SW1 button --- the Blue LED will light up on [3] --- As a result the Green LED starts toggling on the BLE/ZB device [2], every 50 ms --- After scanning complete, the 3rd Nucleo board [3] connects to the P2P server on BLE/ZB [2] dynamic node. At this stage, it can - sends a toggle request to the BLE/ZB device via the SW1 push button. This will make the Red LED on the BLE/ZB device toggling. -4- When the BLE connection is detected by the BLE/ZB device [2], it sends continuously a ZB ON_OFF toggle on the ZB coordinator [1] --- The Red Led toggles on the coordinator [1] (at an approx rate of 70 ms) - - ______________ ______________ ______________ - / \ / \ / \ - | | | | | | - | | BLE Toggle | Dynamic mode | ZB Toggle | | - | BLE App |<===========>| BLE/ZB App |<===========>| ZB App | - | | | | | | - | | | | | | - \______________/ \______________/ \______________/ - [3] [2] [1] - -This Demo illustates the simultaneous BLE and ZB connections, with the red Led toggling on ZB/BLE device [2], reflecting BLE activity, and -the Red Led toggling on the ZB coordinator[1], reflecting ZB activity. - -On BLE Disconnection, The STM32WB55xx-Nucleo board [3] will restart advertising. - - - * <h3><center>© COPYRIGHT STMicroelectronics</center></h3> - */ -
\ No newline at end of file |