blob: f7e22a255f2ef966a8892ab25ce10d8167a904e3 (
plain)
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_Coap_Generic application
@verbatim
******************************************************************************
* @file Thread/Thread_Coap_Generic/readme.txt
* @author MCD Application Team
* @brief Description of Coap Generic 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 build Thread application based on Coap messages.
This application requires two STM32WB55xx_Dongle 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 (or child) communicates primarily with a single Router.
In our Application which uses two devices, one device will act as a Leader (Router)
and the other one will act as an End Device(mode child).
After the reset of the 2 boards, one board will be in Leader mode (Green LED2 ON)
The other one will be in Child mode (Red LED3 ON).
Let's name indifferently one board A and one board B.
To send a COAP command from board A to board B, press the SW1 Push-Button on board A.
The board B will receive the COAP command to light on its blue LED1.
Pressing again same push-button will light off the blue LED1. And so-on.
Same COAP commands can be sent from board B to board A.
___________________________ ___________________________
| Device 1 | | Device 2 |
|_________________________| |_________________________|
| | | |
| | | |
| Push Button --> |======> COAP =========>| BLUE LED TOGGLE (ON/OFF)|
| | Resource "light" | |
| | Mode: Multicast | |
| | Type: Non-Confirmable | |
| | Code: Put | |
| | | |
| | | |
*************** WAIT 5 Seconds (configurable with WAIT_TIMEOUT) *************
| | | |
| | | |
| |=====> COAP ==========>|--------> |
| | Resource "light" | | |
| | Mode: Multicast | CoapRequestHandler() |
| | Type: Confirmable | | |
| | Code: Put | | |
| | | v |
| | | CoapSendDataResponse() |
| | | | |
| | | v |
| CoapDataRespHandler()<--|<===== COAP <==========| <------- |
| | | |
| | | | | |
--------------------------- ---------------------------
| Role : Child | | Role : Leader |
| | | |
| LED : Red | | LED : Green |
| | | |
|_________________________| |_________________________|
@par Keywords
COAP,Thread
@par Directory contents
- Thread/Thread_Coap_Generic/Core/Inc/app_common.h Header for all modules with common definition
- Thread/Thread_Coap_Generic/Core/Inc/app_conf.h Parameters configuration file of the application
- Thread/Thread_Coap_Generic/Core/Inc/app_entry.h Parameters configuration file of the application
- Thread/Thread_Coap_Generic/STM32_WPAN/App/app_thread.h Header for app_thread.c module
- Thread/Thread_Coap_Generic/Core/Inc/hw_conf.h Configuration file of the HW
- Thread/Thread_Coap_Generic/Core/Inc/main.h Header for main.c module
- Thread/Thread_Coap_Generic/Core/Inc/stm_logging.h Header for stm_logging.c module
- Thread/Thread_Coap_Generic/Core/Inc/stm32wbxx_hal_conf.h HAL configuration file
- Thread/Thread_Coap_Generic/Core/Src/stm32wbxx_it.h Interrupt header file
- Thread/Thread_Coap_Generic/Core/Inc/utilities_conf.h Configuration file of the utilities
- Thread/Thread_Coap_Generic/Core/Src/app_entry.c Initialization of the application
- Thread/Thread_Coap_Generic/STM32_WPAN/App/app_thread.c Thread application implementation
- Thread/Thread_Coap_Generic/STM32_WPAN/Target/hw_ipcc.c IPCC Driver
- Thread/Thread_Coap_Generic/Core/Src/stm32_lpm_if.c Low Power Manager Interface
- Thread/Thread_Coap_Generic/Core/Src/hw_timerserver.c Timer Server Driver
- Thread/Thread_Coap_Generic/Core/Src/hw_uart.c UART driver
- Thread/Thread_Coap_Generic/Core/Src/main.c Main program
- Thread/Thread_Coap_Generic/Core/Src/stm_logging.c Logging module for traces
- Thread/Thread_Coap_Generic/Core/Src/stm32xx_it.c Interrupt handlers
- Thread/Thread_Coap_Generic/Core/Src/system_stm32wbxx.c stm32wbxx system source file
@par Hardware and Software environment
- This example runs on STM32WB55xx devices (Nucleo board and dongle).
- This example has been tested with an STMicroelectronics STM32WB55xx_Dongle
board and can be easily tailored to any other supported device
and development board.
@par How to use it ?
This application requests having the stm32wb5x_Thread_FTD_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
- Open your preferred toolchain
- Rebuild all files and load your image into target memory
- Run the example
Note: when LED1, LED2 and LED3 are toggling it is indicating an error has occurred on application.
* <h3><center>© COPYRIGHT STMicroelectronics</center></h3>
*/
|
