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
|
/**
@page Thread_Commissioning application
@verbatim
******************************************************************************
* @file Thread/Thread_Commissioning/readme.txt
* @author MCD Application Team
* @brief Description of the Thread Commissioning application
******************************************************************************
*
* 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 Thread commissioning process.
This application shows a device being able to distribute its parameters
(channel, panid, etc..) to another device thanks to the commissioning.
This application requires two STM32WB55xx_Nucleo boards. One device will act as commissioner.
The other device will act as joiner. In this application, the commissioner will accept a
newcomer to reach a Thread network.
@par Keywords
COAP,Thread
@par Directory contents
- Thread/Thread_Commissioning/Core/Inc/app_common.h Header for all modules with common definition
- Thread/Thread_Commissioning/Core/Inc/app_conf.h Parameters configuration file of the application
- Thread/Thread_Commissioning/Core/Inc/app_entry.h Parameters configuration file of the application
- Thread/Thread_Commissioning/STM32_WPAN/App/app_thread.h Header for app_thread.c module
- Thread/Thread_Commissioning/Core/Inc/hw_conf.h Configuration file of the HW
- Thread/Thread_Commissioning/Core/Inc/main.h Header for main.c module
- Thread/Thread_Commissioning/Core/Inc/stm_logging.h Header for stm_logging.c module
- Thread/Thread_Commissioning/Core/Inc/stm32wbxx_hal_conf.h HAL configuration file
- Thread/Thread_Commissioning/Core/Src/stm32wbxx_it.h Interrupt header file
- Thread/Thread_Commissioning/Core/Inc/system_infra.h System infrastructure header file
- Thread/Thread_Commissioning/Core/Inc/utilities_conf.h Configuration file of the utilities
- Thread/Thread_Commissioning/Core/Src/app_entry.c Initialization of the application
- Thread/Thread_Commissioning/STM32_WPAN/App/app_thread.c Thread application implementation
- Thread/Thread_Commissioning/STM32_WPAN/Target/hw_ipcc.c IPCC Driver
- Thread/Thread_Commissioning/Core/Src/stm32_lpm_if.c Low Power Manager Interface
- Thread/Thread_Commissioning/Core/Src/hw_uart.c UART driver
- Thread/Thread_Commissioning/Core/Src/main.c Main program
- Thread/Thread_Commissioning/Core/Src/stm_logging.c Logging module for traces
- Thread/Thread_Commissioning/Core/Src/stm32xx_it.c Interrupt handlers
- Thread/Thread_Commissioning/Core/Src/system_stm32wbxx.c stm32wbxx system source file
- Thread/Thread_Commissioning/Core/Src/stm32wbxx_hal_msp.c MSP used to handle the Timer
@par Hardware and Software environment
- This application uses two STM32WB55xx devices (Nucleo board and Dongle).
- This example has been tested with an STMicroelectronics STM32WB55 Nucleo or Dongle
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_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 of Thread/Thread_Commissioning application
and load your image into the target memory
- Run the application
Note: when LED1, LED2 and LED3 are toggling it is indicating an error has occurred on application.
Step 1 : At start both devices are not attached to any Thread network. LED1 (blue) is
toggling slowly waiting for a user action. Both devices are in 'disabled' mode.
Step 2 : On one device (Device1) , press on the SW1 push button. Following this action, Device1 will
reach the ‘leader’ state inside the Thread network after a few seconds and act as commissioner.
LED2 (green) should light on.
Note : Device1 behaves as if the user had typed the following Cli commands once it has reached
the 'leader' state.
> commissioner start
> commissioner joiner add * MY_PASSWD
The * wildcard allows any Joiner with the specified Joiner Credential to commission onto the network.
The Joiner Credential is used (along with the Extended PAN ID and Network Name) to generate the
Pre-Shared Key for the Device (PSKd). The PSKd is then used to authenticate a device during Thread
commissioning.
Step 3 : On the other device (Device2), press on the SW3 push button. Following this action, Device2 will
act as joiner using the same credential as specified on the commissioner.
Note : Device2 behaves as if the user had typed the following Cli command:
> joiner start MY_PASSWD
Step4 : The commissioning is now proceeding. This step can take more than 100 seconds. LED1 (blue) is
toggling quickly on Device2.
Step5 : Once the commissioning is completed, the LED1 (blue) stays ‘On’ on both devices and the Thread network
is now established. One device acts as a Leader (Green LED on) and the other device acts as a Child (Red LED on)
Remarks :
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)
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
* <h3><center>© COPYRIGHT STMicroelectronics</center></h3>
*/
|
