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
|
/**
@page LLD_BLE_Pressbutton example
@verbatim
******************** (C) COPYRIGHT 2020 STMicroelectronics *******************
* @file LLD_BLE/LLD_BLE_Pressbutton/readme.txt
* @author MCD Application Team
* @brief Description of the LLD BLE LLD_BLE_Pressbutton application
******************************************************************************
*
* 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 Example Description
This example is to communicate Over The Air (OTA) using LLD_BLE between 2 boards (one send, other receive)
in BLE Radio format not BLE Stack protocol.
@par Keywords
LLD_BLE, HAL send and receive Packet
@par Directory contents
@par Hardware and Software environment
- This application uses two 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 ?
In order to make the program work, you must do the following:
- Connect 2 STM32WB55xx-Nucleo boards to your PC
- Open your preferred toolchain
- Rebuild all files and load your image into one target memory
- Rebuild all files of LLD_BLE/LLD_BLE_Pressbutton application
and load your image into the other target memory
+ load stm32wb5x_BLE_LLD_fw.bin
- Run the application
If you want to control this application, you can directly press buttons
In this order and described into main.c:
/////////////// OBJECTIVES //////////////////////////
The objectif is to communicate Over The Air (OTA) using LLD_BLE between 2 boards (one send, other receive), in BLE Radio format not BLE Stack protocol.
LLD_BLE is a 2-level stack implemented just over the Hardware and Radio layer.
Lowest Layer also called Low Level or LL
It is just over the Hardware and Radio Layer.
It contains all the API to Set/Configure/Initialize all the parameters for Sending/receiving BLE Radio format packet data OTA
Over LL layer there is HAL level
It contains a reduced number of API to Send/Receive BLE Radio format packet with predefined parameters
It works by calling a set of LL API
It make simple and fast to Send/receive Packet
But It does allow the user to change all the Radio parameters
LL is for user that want to customize the Radio and BLE parameters, it is more complex to implement
HAL is for user that want to Send/Receive in a very simple way less complex, without configuring LL
lld_ble contains LLD API HAL and LL API
app_lld_ble contains Transport Layer Command call from CPU1 to CPU2 + Buffer management + IT Radio management from CPU2
/////////////// APPLICATION //////////////////////////
After power On or Reset (ALL the LED are OFF)
1)Press SW1 (switch API)
In order to change (switch) the communication: based on LL API or HAL API
using LL API is default => BLUE LED is OFF (if SW1 has not been pressed)
using HAL API => BLUE LED is ON
press SW1 switch from one API to another
LL API and HAL API used different AccessAddress (or NetworkID)
Switching implies to re-Init => GREEN and RED LED are OFF
Init must be done at the next step (even if SW1 has not been pressed) or each time SW1 is pressed
2)If GREEN and RED LED are OFF : Press SW2 or SW3 to Init => GREEN and RED LED are ON
3)If GREEN and RED LED are ON :
Press SW2 for Send 500 Chained Packets ===> GREEN is switched off during TX
or
Press SW3 for receiving 400 Packets (HAL) and 500 Packets (LL) ===> RED is switched off during RX
When one board Send : GREEN diode is OFF
When one board Receive: RED diode is OFF
When one board Send and other Receive and communicates with ACK,
Sending board GREEN LED toggle (until end of 1000 TX)
Receiving board RED LED toggle (unitl end of 1000 RX)
At the END GREEN and RED LED are ON
Serial Port Setup TERMINAL
Baud Rate:115200 / Data:8 bits / Parity:none / Stop:1bit / Flow Control:none
/////////////// MAIN CODE //////////////////////////
A set of parameters common to HAL or LL API are proposed
channel / WakeupTime / ReceiveWindowTime are predefined as pressChannel / pressWakeup / pressReceive
networkID=pressID for HAL
networkID=~pressID for LL
TxBuffer is also predefined, presstxBufferTab maximum size is 258
1 for Header (set by user)
1 for Payload Length (set by user / or sw) should be aligned with the payload Length
256 max for Payload
TxBuffer for ACK answer is set as pressAcktxBufferTab
dataRoutine for HAL API Send is pressdataCaseTx=dataRoutine_HAL_TxAck
dataRoutine for HAL API Receive is pressdataCaseRx=dataRoutine_HAL_RxAck
Custom4 is specific for HAL API LLD_BLE_Pressbutton and it is with ACK
dataRoutine for LL API Send is dataRoutine_LL_TxAck
dataRoutine for LL API Receive is dataRoutine_LL_RxAck
* <h3><center>© COPYRIGHT STMicroelectronics</center></h3>
*/
|
