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
|
/**
@page Thread_SED_Coap_Multicast application
@verbatim
******************************************************************************
* @file Thread/Thread_SED_Coap_Multicast/readme.txt
* @author MCD Application Team
* @brief Description of the Thread Coap Multicast application
******************************************************************************
*
* Copyright (c) 2019-2021 STMicroelectronics.
* All rights reserved.
*
* This software is licensed under terms that can be found in the LICENSE file
* in the root directory of this software component.
* If no LICENSE file comes with this software, it is provided AS-IS.
*
******************************************************************************
@endverbatim
@par Application Description
How to exchange a Coap message using the Thread protocol.
This application requires two STM32WB55xx boards.
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 communicates primarily with a single Router.
An MTD device can only have the following roles:
- End Device, Sleepy End Device
An FTD device can have the following roles:
- End Device, Sleepy End Device, REED, Router, Leader
In our Application which uses two devices, one device will act as a Leader (Router) in FTD mode
and the other one will act as a SleepyEndDevice in MTD mode.
The device that will act as a Leader must be flashed with the FTD application:
use the Thread FTD application Thread_FTD_Coap_Multicast.
The other device that will act as a SleepyEndDevice can be flashed with this MTD application.
After the reset of the 2 boards, one board (Device 1) will automatically reach the
Leader mode (Green LED2 ON) and the other one (Device 2) will automatically reach the
Sleepy End Device mode (Red LED3 ON) after a few seconds.
At this stage, these two boards belong to the same Thread network and Device 2 will
send every second a Coap request to Device 1 in order to light on/off its blue LED.
___________________________ ___________________________
| Device 2 (MTD) | | Device 1 (FTD) |
|_________________________| |_________________________|
| | | |
| | | |
| Timer [1sec] |======> COAP =========>| BLUE LED ON/OFF |
| | Resource "light" | |
| | Mode : Multicast | |
| | | |
| | | |
--------------------------- ---------------------------
| Role : SleepyEndDevice | | Role : Leader |
| | | |
| LED : Red | | LED : Green |
| | | |
|_________________________| |_________________________|
@par Keywords
COAP,Thread
@par Directory contents
- Thread/Thread_SED_Coap_Multicast/Core/Inc/app_common.h Header for all modules with common definition
- Thread/Thread_SED_Coap_Multicast/Core/Inc/app_conf.h Parameters configuration file of the application
- Thread/Thread_SED_Coap_Multicast/Core/Inc/app_entry.h Parameters configuration file of the application
- Thread/Thread_SED_Coap_Multicast/STM32_WPAN/App/app_thread.h Header for app_thread.c module
- Thread/Thread_SED_Coap_Multicast/Core/Inc/hw_conf.h Configuration file of the HW
- Thread/Thread_SED_Coap_Multicast/Core/Inc/main.h Header for main.c module
- Thread/Thread_SED_Coap_Multicast/Core/Inc/stm_logging.h Header for stm_logging.c module
- Thread/Thread_SED_Coap_Multicast/Core/Inc/stm32wbxx_hal_conf.h HAL configuration file
- Thread/Thread_SED_Coap_Multicast/Core/Src/stm32wbxx_it.h Interrupt header file
- Thread/Thread_SED_Coap_Multicast/Core/Inc/system_infra.h System infrastructure header file
- Thread/Thread_SED_Coap_Multicast/Core/Inc/utilities_conf.h Configuration file of the utilities
- Thread/Thread_SED_Coap_Multicast/Core/Src/app_entry.c Initialization of the application
- Thread/Thread_SED_Coap_Multicast/STM32_WPAN/App/app_thread.c Thread application implementation
- Thread/Thread_SED_Coap_Multicast/STM32_WPAN/Target/hw_ipcc.c IPCC Driver
- Thread/Thread_SED_Coap_Multicast/Core/Src/stm32_lpm_if.c Low Power Manager Interface
- Thread/Thread_SED_Coap_Multicast/Core/Src/hw_uart.c UART driver
- Thread/Thread_SED_Coap_Multicast/Core/Src/main.c Main program
- Thread/Thread_SED_Coap_Multicast/Core/Src/stm_logging.c Logging module for traces
- Thread/Thread_SED_Coap_Multicast/Core/Src/stm32xx_it.c Interrupt handlers
- Thread/Thread_SED_Coap_Multicast/Core/Src/system_stm32wbxx.c stm32wbxx system source file
@par Hardware and Software environment
- This application uses two STM32WB55xx devices (Nucleo board and dongle)
- This example has been tested with an STMicroelectronics STM32WB55xx_Usb_Dongle
board and can be easily tailored to any other supported device
and development board.
@par How to use it ?
For Device 1 (FTD), this application requests having the stm32wb5x_Thread_FTD_fw.bin binary flashed on the Wireless Coprocessor.
For Device 2 (MTD), this application requests having the stm32wb5x_Thread_MTD_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.
In order to make the program work, you must do the following:
- Connect 2 STM32WB55xx boards to your PC
One Board (Device 1) must be configured in FTD.
-> Refer to the Thread/Thread_FTD_Coap_Multicast application example and follow the associated readme.txt
The second Board (Device 2) must be configured in MTD
-> Open your preferred toolchain
-> Rebuild all files of Thread/Thread_SED_Coap_Multicast application
and load your image into the other target memory
- Run the application
Note: when LED1, LED2 and LED3 are toggling it is indicating an error has occurred on application.
If you want to control this application, you can directly send and
retrieve Cli commands connecting an HyperTerminal with the ST_Link cable.
(Refer to the Thread_Cli_Cmd application for more details)
* <h3><center>© COPYRIGHT STMicroelectronics</center></h3>
*/
|
