1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
|
/**
@page Ble_Thread_Dyn_SED example
@verbatim
******************************************************************************
* @file BLE_Thread/Ble_Thread_Dyn_SED/readme.txt
* @author MCD Application Team
* @brief Example of application using BLE and Thread (acting as sleep end device)
* in dynamic concurrent mode.
******************************************************************************
*
* 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 Thread application (acting as sleep end device) in dynamic concurrent mode.
This application requires 1 STM32WB55xx-Nucleo board with Dynamic Concurrent Mode Application and at least one
STM32WB55xx-Nucleo with Thread FTD copro wireless and Thread_FTD_Coap_Multicast application.
Dynamic means that application can perform at the same time BLE or Thread activities.
The idea is to present a demo with a Thread Network (1 Nucleo Boards
running Ble_Thread_Dyn_SED application and at least 1 Nucleo Boards running Thread_FTD_Coap_Multicast Application),
and a a BLE connection between a smartphone running "ST BLE Sensor" Application (available on App Store and Google Play),
or another Nucleo board running a BLE_p2pClient application.
The STM32WB55xx-Nucleo board running Ble_Thread_Dyn_SED application is capable of BLE and OpenThread activity at the same time.
@par Keywords
COAP,THREAD,BLE
@par Directory contents
- BLE_Thread/Ble_Thread_Dyn_SED/STM32_WPAN/App/app_ble.h Header for app_ble.c module
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Core/Inc/app_common.h Header for all modules with common definition
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Core/Inc/app_conf.h Parameters configuration file of the application
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Core/Inc/app_entry.h Parameters configuration file of the application
- BLE_Thread/Ble_Thread_Dyn_SED/STM32_WPAN/App/app_thread.h Header for app_thread.c module
- BLE_Thread/Ble_Thread_Dyn_SED/STM32_WPAN/App/ble_conf.h BLE Services configuration
- BLE_Thread/Ble_Thread_Dyn_SED/STM32_WPAN/App/ble_dbg_conf.h BLE Traces configuration of the BLE services
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Core/Inc/hw_conf.h Configuration file of the HW
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Inc/main.h Header for main.c module
- BLE_Thread/Ble_Thread_Dyn_SED/STM32_WPAN/App/p2p_server_app.h Header for BLE P2P Server application
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Inc/stm32wbxx_hal_conf.h HAL configuration file
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Inc/stm32wbxx_it.h Interrupt handlers header file
- BLE_Thread/Ble_Thread_Dyn_SED/STM32_WPAN/App/app_ble.c BLE Profile implementation
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Core/Src/app_entry.c Initialization of the application
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Src/app_thread.c Thread application implementation
- BLE_Thread/Ble_Thread_Dyn_SED/STM32_WPAN/Target/hw_ipcc.c IPCC Driver
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Core/Src/stm32_lpm_if.c Low Power Manager Interface
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Core/Src/hw_timerserver.c Timer Server based on RTC
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Core/Src/hw_uart.c UART Driver
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Src/main.c Main program
- BLE_Thread/Ble_Thread_Dyn_SED/STM32_WPAN/App/p2p_server_app.c BLE P2P Server application implementation
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Src/stm32wbxx_it.c Interrupt handlers
- BLE_Thread/Ble_Thread_Dyn_SED/Core/Src/system_stm32wbxx.c stm32wbxx system source file
@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_Thread_dynamic_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 load the proper
Wireless Coprocessor binary.
Minimum requirements for the demo:
- 1 STM32WB55xx-Nucleo board in BLE Thread Dynamic Concurrent mode
(Copro wireless :stm32wb5x_BLE_Zigbee_RFD_dynamic_fw.bin + Ble_Thread_Dyn_SED application)
- 1 STM32WB55xx-Nucleo board running Thread FTD COAP Generic Application
(Copro wireless :stm32wb5x_Thread_FTD_fw.bin + Thread_FTD_Coap_Multicast application)
- 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 each STM32WB55xx-Nucleo boards to your PC
- Open your preferred toolchain
- Rebuild all files and load your image into target memory
- Run the example
If you want to control this application, you can directly send and
retrieve OpenThread Cli commands connecting an HyperTerminal via an UART RS232 cable using
the following connections :
RXD : CN10(Pin35)
TXD : CN10(Pin37)
(Refer to the THREAD_Cli_Cmd application for more details)
To get the traces in real time, you can connect an HyperTerminal to the STLink Virtual Com Port.
For the Cli control and for the traces, the UART must be configured as follows:
- BaudRate = 115200 baud
- Word Length = 8 Bits
- Stop Bit = 1 bit
- Parity = none
- Flow control = none
**** START DEMO ****
First start the board running the Thread_FTD_Coap_Multicast Application which will turn into a Leader role (RED LED)
Then start the board with Ble_Thread_Dyn_SED, it'll join the Leader and receive child role. As soon as it receives child role
it'll start SED features and start Low Power.
This can be checked with a power shield or any power meter.
By default, after a reset, the board will start both protocols BLE and OpenThread.
So you BLE activity and OpenThread activity can be done in parallel :
**** BLE ACTIVITY ****
The BLE activity demonstrates a Point-to-Point communication using BLE component.
The Peripheral device (P2P Server) starts advertising after reset.
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).
**** THREAD ACTIVITY ****
After reset, OpenThread is started and nodes tries to build up a Thread network or attach to a existing one
(at least 1 boards running Thread_FTD_Coap_Multicast application).
In a Thread network, nodes are split into two forwarding roles: Router or End Device.
The Thread Leader is a Router that is responsible for managing the set of Routers in a
Thread network. An End Device (or child) communicates primarily with a single Router.
In our Application which uses at least two devices, one device will act as a Leader (Router)
and the other will act as child.
After the network building, one board will be in Leader mode the other one will be in Child mode.
The SED will then start to send every seconds a multicast COAP Message which will toggle LED (Blue) of the receivers.
**** EXTPA ****
The Dory is not able to transmit with a power higher than 5 dbm (TBC). As such it is
possible to use the EXT PA as an additional supply source.
Signals:
The EXTPA consists of three signals.
- Analogic signal : power supply, constant value.
- Enable/Disable: 0 when the RF is in Sleep/not initialized, 1 otherwise.
- RX/TX : 1 during a transmission, 0 otherwise.
___________________________________________________
| RF status: | Sleep mode | RX mode | TX mode |
|_________________|____________|_________|_________|
| Enable/Disable: | 0 | 1 | 1 |
|_________________|____________|_________|_________|
| RX/TX: | N/A | 0 | 1 |
|_________________|____________|_________|_________|
|Analogic signal: | N/A |
|_________________|________________________________|
NOTE: The RX/TX signal must be wired on the PB0 I/O (C10-22 on Nucleo).
The Enable/Disable signal by default is mapped on PB9 (C10-5 on Nucleo).
You can change this setting in app_conf.h, by editing GPIO_EXT_PA_EN_PIN and GPIO_EXT_PA_EN_PORT.
Power setting:
The firmware is not aware of the power brought by the ExtPA. It is up to the system integrator to
configure the application to get the desired power.
For instance, if the ExtPA provides an additional power of 10dbm and the desired power for a TX is 12dbm.
The application must be configured to set the power at 2dbm.
M0 firmware:
The M0 firmware remains unchanged. It has been tested with the binary listed above.
EXTPA enabling:
The EXTPA support is not enabled by default.
In hw_conf.h, set CFG_HW_EXTPA_ENABLED to 1.
* <h3><center>© COPYRIGHT STMicroelectronics</center></h3>
*/
|
